1. A method of identifying an electronic device for performing a task from a plurality of electronic devices, the method comprising:

sampling audio input with a microphone at each of two or more of the plurality of electronic devices;

identifying a first electronic device of the plurality of electronic devices for determining tasks associated with the sampled audio input, wherein identifying the first electronic device of the plurality of electronic devices for determining tasks associated with the sampled audio input comprises: determining respective speech qualities in the audio input sampled at the two or more electronic devices;

determining, with the first electronic device, the task based on the sampled audio input;

identifying a second electronic device of the plurality of electronic devices for performing the task; and

performing the task with the second electronic device, wherein the second electronic device is not the first electronic device.

2. The method of claim 1, further comprising:

after sampling audio input, providing an output indicating that the task has been determined based on the sampled audio input, wherein the output is provided by an electronic device of the plurality of electronic devices other than the first electronic device.

3. The method of claim 2, wherein the output is provided by an electronic device of the plurality of electronic devices other than the first electronic device and the second electronic device.

4. The method of claim 1, wherein sampling audio input comprises determining whether the audio input comprises a spoken trigger, and wherein the method further comprises:

in accordance with a determination that the audio input includes the spoken trigger,

providing a first output confirming sampling of the audio input; and

after sampling the audio input, providing an output indicating that the task has been determined based on the sampled audio input,

wherein the first output and the second output have different characteristics, an

Wherein the first output is provided by the two or more electronic devices.

5. The method of claim 4, wherein the spoken trigger comprises a predetermined phrase.

6. The method of any of claims 1 and 2, wherein identifying the first one of the plurality of electronic devices to determine a task associated with the sampled audio input comprises:

determining respective sound pressure levels of the sampled audio inputs at the two or more electronic devices; and

identifying an electronic device having a highest sound pressure level of the two or more electronic devices as the first electronic device.

7. The method of claim 1, wherein identifying the first one of the plurality of electronic devices to determine a task associated with the sampled audio input comprises:

determining whether the two or more electronic devices that are sampling audio input include a wearable electronic device; and

identifying the wearable electronic device as the first electronic device.

8. The method of claim 1, wherein identifying the second electronic device of the plurality of electronic devices to perform the task comprises:

determining a signal strength of a wireless communication between the first electronic device and at least one other electronic device of the plurality of electronic devices; and

identifying the electronic device with the highest signal strength as the second electronic device.

9. The method of claim 1, wherein identifying the second electronic device of the plurality of electronic devices to perform the task comprises:

obtaining an indication of a display screen size of an electronic device of the plurality of electronic devices;

determining whether the indication satisfies a requirement of the task;

in accordance with a determination that the indication satisfies the requirement, identifying the electronic device as the second electronic device; and is

In accordance with a determination that the indication does not satisfy the requirement, forgoing identification of the electronic device as the second electronic device.

10. The method of claim 1, wherein identifying the second electronic device of the plurality of electronic devices to perform the task comprises:

determining whether an electronic device of the plurality of electronic devices is a mobile electronic device;

in accordance with a determination that the electronic device is a mobile electronic device, identifying the electronic device as the second electronic device; and is

In accordance with a determination that the electronic device is not a mobile electronic device, forgoing identification of the electronic device as the second electronic device.

11. The method of claim 1, wherein identifying the second electronic device of the plurality of electronic devices to perform the task comprises:

determining whether an electronic device of the plurality of electronic devices is being powered by a power outlet;

in accordance with a determination that the electronic device is being powered by a power outlet, identifying the electronic device as the second electronic device; and is

In accordance with a determination that the electronic device is not powered by a power outlet, forgoing identification of the electronic device as the second electronic device.

12. The method of claim 1, wherein identifying the second electronic device of the plurality of electronic devices to perform the task comprises:

identifying the second electronic device based on the task.

13. The method of claim 1, further comprising:

delaying execution of the task with the second electronic device until a criterion is met; and

providing an output indicative of the criteria for performing the task.

14. The method of claim 1, further comprising:

prompting a user for input prior to performing the task with the second electronic device, wherein the second electronic device performs the task after receiving the prompted input.

15. The method of claim 14, wherein prompting the user for input prior to performing the task with the second electronic device comprises:

identifying a third electronic device of the plurality of electronic devices, the third electronic device having an input interface configured to detect the prompted input.

16. The method of claim 15, wherein receiving the prompted input comprises receiving an input within a biometric sensor.

17. A computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device, cause the electronic device to:

sampling audio input with a microphone at each of two or more of the plurality of electronic devices;

identifying a first electronic device of the plurality of electronic devices for determining tasks associated with the sampled audio input, wherein identifying the first electronic device of the plurality of electronic devices for determining tasks associated with the sampled audio input comprises: determining respective speech qualities in the audio input sampled at the two or more electronic devices;

determining, with the first electronic device, the task based on the sampled audio input;

identifying a second electronic device of the plurality of electronic devices for performing the task; and

performing the task with the second electronic device, wherein the second electronic device is not the first electronic device.

18. The computer-readable storage medium of claim 17, the one or more programs further comprising instructions that cause the electronic device to:

after sampling audio input, providing an output indicating that the task has been determined based on the sampled audio input, wherein the output is provided by an electronic device of the plurality of electronic devices other than the first electronic device.

19. The computer-readable storage medium of claim 18, wherein the output is provided by an electronic device of the plurality of electronic devices other than the first electronic device and the second electronic device.

20. The computer readable storage medium of claim 17, wherein sampling audio input comprises determining whether the audio input comprises a spoken trigger, and wherein the one or more programs further comprise instructions that cause the electronic device to:

in accordance with a determination that the audio input includes the spoken trigger,

providing a first output confirming sampling of the audio input; and

after sampling the audio input, providing an output indicating that the task has been determined based on the sampled audio input,

wherein the first output and the second output have different characteristics, an

Wherein the first output is provided by the two or more electronic devices.

21. The computer-readable storage medium of claim 20, wherein the spoken trigger comprises a predetermined phrase.

22. The computer-readable storage medium of any of claims 17 and 18, wherein identifying the first one of the plurality of electronic devices to determine a task associated with a sampled audio input comprises:

determining respective sound pressure levels of the sampled audio inputs at the two or more electronic devices; and

identifying an electronic device having a highest sound pressure level of the two or more electronic devices as the first electronic device.

23. The computer-readable storage medium of claim 17, wherein identifying the first one of the plurality of electronic devices to determine a task associated with the sampled audio input comprises:

determining whether the two or more electronic devices that are sampling audio input include a wearable electronic device; and

identifying the wearable electronic device as the first electronic device.

24. The computer-readable storage medium of claim 17, wherein identifying the second one of the plurality of electronic devices to perform the task comprises:

determining a signal strength of a wireless communication between the first electronic device and at least one other electronic device of the plurality of electronic devices; and

identifying the electronic device with the highest signal strength as the second electronic device.

25. The computer-readable storage medium of claim 17, wherein identifying the second one of the plurality of electronic devices to perform the task comprises:

obtaining an indication of a display screen size of an electronic device of the plurality of electronic devices;

determining whether the indication satisfies a requirement of the task;

in accordance with a determination that the indication satisfies the requirement, identifying the electronic device as the second electronic device; and is

In accordance with a determination that the indication does not satisfy the requirement, forgoing identification of the electronic device as the second electronic device.

26. The computer-readable storage medium of claim 17, wherein identifying the second one of the plurality of electronic devices to perform the task comprises:

determining whether an electronic device of the plurality of electronic devices is a mobile electronic device;

in accordance with a determination that the electronic device is a mobile electronic device, identifying the electronic device as the second electronic device; and is

In accordance with a determination that the electronic device is not a mobile electronic device, forgoing identification of the electronic device as the second electronic device.

27. The computer-readable storage medium of claim 17, wherein identifying the second one of the plurality of electronic devices to perform the task comprises:

determining whether an electronic device of the plurality of electronic devices is being powered by a power outlet;

in accordance with a determination that the electronic device is being powered by a power outlet, identifying the electronic device as the second electronic device; and is

In accordance with a determination that the electronic device is not powered by a power outlet, forgoing identification of the electronic device as the second electronic device.

28. The computer-readable storage medium of claim 17, wherein identifying the second one of the plurality of electronic devices to perform the task comprises:

identifying the second electronic device based on the task.

29. The computer-readable storage medium of claim 17, further comprising:

delaying execution of the task with the second electronic device until a criterion is met; and

providing an output indicative of the criteria for performing the task.

30. The computer-readable storage medium of claim 17, the one or more programs further comprising instructions that cause the electronic device to:

prompting a user for input prior to performing the task with the second electronic device, wherein the second electronic device performs the task after receiving the prompted input.

31. The computer-readable storage medium of claim 30, wherein prompting the user for input prior to performing the task with the second electronic device comprises:

identifying a third electronic device of the plurality of electronic devices, the third electronic device having an input interface configured to detect the prompted input.

32. The computer-readable storage medium of claim 31, wherein receiving the prompted input comprises receiving an input within a biometric sensor.

33. An electronic device, comprising:

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:

sampling audio input with a microphone at each of two or more of the plurality of electronic devices;

identifying a first electronic device of the plurality of electronic devices for determining tasks associated with the sampled audio input, wherein identifying the first electronic device of the plurality of electronic devices for determining tasks associated with the sampled audio input comprises: determining respective speech qualities in the audio input sampled at the two or more electronic devices;

determining, with the first electronic device, the task based on the sampled audio input;

identifying a second electronic device of the plurality of electronic devices for performing the task; and

performing the task with the second electronic device, wherein the second electronic device is not the first electronic device.

34. The electronic device of claim 33, the one or more programs further comprising instructions for:

after sampling audio input, providing an output indicating that the task has been determined based on the sampled audio input, wherein the output is provided by an electronic device of the plurality of electronic devices other than the first electronic device.

35. The electronic device of claim 34, wherein the output is provided by an electronic device of the plurality of electronic devices other than the first electronic device and the second electronic device.

36. The electronic device of claim 33, wherein sampling audio input comprises determining whether the audio input comprises a spoken trigger, and wherein the one or more programs further comprise instructions to:

in accordance with a determination that the audio input includes the spoken trigger,

providing a first output confirming sampling of the audio input; and

after sampling the audio input, providing an output indicating that the task has been determined based on the sampled audio input,

wherein the first output and the second output have different characteristics, an

Wherein the first output is provided by the two or more electronic devices.

37. The electronic device of claim 36, wherein the spoken trigger comprises a predetermined phrase.

38. The electronic device of any of claims 33 and 34, wherein identifying the first one of the plurality of electronic devices to determine a task associated with a sampled audio input comprises:

determining respective sound pressure levels of the sampled audio inputs at the two or more electronic devices; and

identifying an electronic device having a highest sound pressure level of the two or more electronic devices as the first electronic device.

39. The electronic device of claim 33, wherein identifying the first one of the plurality of electronic devices to determine a task associated with the sampled audio input comprises:

determining whether the two or more electronic devices that are sampling audio input include a wearable electronic device; and

identifying the wearable electronic device as the first electronic device.

40. The electronic device of claim 33, wherein identifying the second electronic device of the plurality of electronic devices to perform the task comprises:

determining a signal strength of a wireless communication between the first electronic device and at least one other electronic device of the plurality of electronic devices; and

identifying the electronic device with the highest signal strength as the second electronic device.

41. The electronic device of claim 33, wherein identifying the second electronic device of the plurality of electronic devices to perform the task comprises:

obtaining an indication of a display screen size of an electronic device of the plurality of electronic devices;

determining whether the indication satisfies a requirement of the task;

in accordance with a determination that the indication satisfies the requirement, identifying the electronic device as the second electronic device; and is

In accordance with a determination that the indication does not satisfy the requirement, forgoing identification of the electronic device as the second electronic device.

42. The electronic device of claim 33, wherein identifying the second electronic device of the plurality of electronic devices to perform the task comprises:

determining whether an electronic device of the plurality of electronic devices is a mobile electronic device;

in accordance with a determination that the electronic device is a mobile electronic device, identifying the electronic device as the second electronic device; and is

In accordance with a determination that the electronic device is not a mobile electronic device, forgoing identification of the electronic device as the second electronic device.

43. The electronic device of claim 33, wherein identifying the second electronic device of the plurality of electronic devices to perform the task comprises:

determining whether an electronic device of the plurality of electronic devices is being powered by a power outlet;

in accordance with a determination that the electronic device is being powered by a power outlet, identifying the electronic device as the second electronic device; and is

In accordance with a determination that the electronic device is not powered by a power outlet, forgoing identification of the electronic device as the second electronic device.

44. The electronic device of claim 33, wherein identifying the second electronic device of the plurality of electronic devices to perform the task comprises:

identifying the second electronic device based on the task.

45. The electronic device of claim 33, the one or more programs further comprising instructions for:

delaying execution of the task with the second electronic device until a criterion is met; and

providing an output indicative of the criteria for performing the task.

46. The electronic device of claim 33, the one or more programs further comprising instructions for:

prompting a user for input prior to performing the task with the second electronic device, wherein the second electronic device performs the task after receiving the prompted input.

47. The electronic device of claim 46, wherein prompting the user for input prior to performing the task with the second electronic device comprises:

identifying a third electronic device of the plurality of electronic devices, the third electronic device having an input interface configured to detect the prompted input.

48. The electronic device of claim 47, wherein receiving the prompted input comprises receiving an input within a biometric sensor.

Background

This relates generally to multi-device systems and more particularly to intelligent identification of devices in a multi-device system.

Disclosure of Invention

The present invention provides systems and processes for intelligent device identification. In one exemplary process, the audio input may be sampled with a microphone at each of two or more of the plurality of electronic devices. A first electronic device of the plurality of electronic devices for determining a task associated with the sampled audio input may be identified. The process may determine a task based on the audio input sampled with the first electronic device and identify a second electronic device of the plurality of electronic devices to perform the task. The second electronic device will perform the task. In some examples, the second electronic device is not the first electronic device.

In one exemplary process, data indicative of a task may be received. The task may be associated with an audio input. The process may determine, at the first electronic device, whether the first electronic device or the second electronic device is to perform the task. In accordance with a determination that the task is associated with the first electronic device, the task may be performed by the first electronic device. In accordance with a determination that the task is associated with the second electronic device, data indicative of the task may be caused to be transmitted to the second electronic device.

Drawings

Fig. 1A is a block diagram illustrating a multifunction device with a touch-sensitive display in accordance with some embodiments of the present disclosure.

Fig. 1B is a block diagram illustrating exemplary components for event processing according to some embodiments of the present disclosure.

Fig. 2 illustrates a multifunction device with a touch screen according to some embodiments of the present disclosure.

Fig. 3 is a block diagram of an exemplary multi-function device with a display and a touch-sensitive surface, according to some embodiments of the present disclosure.

Figure 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device according to some embodiments.

FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface separate from a display, in accordance with some embodiments.

Fig. 5A-5B illustrate block diagrams of exemplary architectures for devices according to some embodiments of the present disclosure.

Fig. 6A-6F illustrate a plurality of electronic devices according to various examples.

Fig. 7A-7C illustrate a plurality of electronic devices according to various examples.

Fig. 8A-8E illustrate a process for identifying an electronic device to perform a task, according to various examples.

Fig. 9A-9C illustrate a process for identifying an electronic device to perform a task, according to various examples.

Fig. 10 illustrates a functional block diagram of an electronic device according to various examples.

Detailed Description

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

The virtual assistant service may be provided by any number of devices of the user. For example, a user may use a mobile device and a wearable device at the same time, each of which may provide a respective virtual assistant service. Since a user may request one or more devices to perform a task while using and/or approaching multiple devices, there is a need for intelligent identification of the devices to perform the respective tasks such that the user request is intuitively satisfied.

Although the following description uses the terms first, second, etc. to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first touch may be termed a second touch, and similarly, a second touch may be termed a first touch, without departing from the scope of various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.

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.

Embodiments of electronic devices, user interfaces for such devices, and related processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, those from Apple IncDevice and iPodAn apparatus, andan apparatus. Other portable electronic devices are optionally used, such as laptops or tablets with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).

In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and/or joystick.

The device may support a variety of applications, such as one or more of the following: a mapping application, a rendering application, a word processing application, a website creation application, a disc editing application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

Various applications executing on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and/or varied for different applications and/or within respective applications. In this way, the general physical architecture of the device (e.g., a touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and clear to the user.

1. Exemplary device for performing language input correction

Attention is now directed to embodiments of portable devices having touch sensitive displays. FIG. 1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and may sometimes be referred to or called a "touch-sensitive display system". Device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, an input/output (I/O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting intensity of contacts on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

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 thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto, 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 substitute 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 contact intensity as an attribute of user input allows a 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 a device or component of a device is in contact with a touch-sensitive surface of a user (e.g., a finger, palm, or other portion of a 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 "press click" or "release 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, even when there is no change in the smoothness of the touch sensitive surface, the movement of the touch sensitive surface may optionally be interpreted or sensed by the user as a "roughness" of the touch sensitive surface. While such interpretation of touch by a user will be limited by the user's individualized sensory perception, sensory perception of many touches is 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 described sensory perception of a typical (or ordinary) user.

It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 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. 1A 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 102 may include one or more computer-readable storage media. The computer-readable storage medium may be tangible and non-transitory. The computer-readable storage medium may store instructions for performing processes 800 and 900 described below. The memory 102 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 122 may control other components of device 100 to access memory 102.

Peripheral interface 118 may be used to couple the input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in the memory 102 to perform various functions of the device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may be implemented on separate chips.

RF (radio frequency) circuitry 108 receives and transmits RF signals, also called electromagnetic signals. The RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 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 108 optionally communicates with networks such as the internet, also known as the World Wide Web (WWW), intranets, and/or wireless networks (e.g., a cellular telephone network, a wireless Local Area Network (LAN), and/or a Metropolitan Area Network (MAN)), and other devices via wireless communication. RF circuitry 108 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 technologies, including, but not limited to, global system for mobile communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), evolution, data only (EV-DO), HSPA +, 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 power consumption (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 protocols (e.g., Internet Message Access Protocol (IMAP), and/or Post Office Protocol (POP))), Instant messaging (e.g., extensible messaging and presence protocol (XMPP), session initiation protocol 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 time of filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. The audio circuitry 110 receives audio data from the peripheral interface 118, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electric signal into a sound wave audible to a human. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals to audio data and transmits the audio data to the peripheral interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripheral interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., 212 in fig. 2). The headset jack provides an interface between the audio circuitry 110 and a removable audio input/output peripheral such as an output-only headset or a headset having both an output (e.g., a monaural headset or a binaural headset) and an input (e.g., a microphone).

The I/O subsystem 106 couples input/output peripheral devices on the device 100, such as the touch screen 112 and other input control devices 116, to a peripheral interface 118. The I/O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive/transmit electrical signals from/to other input control devices 116. Other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, and the like. In some alternative embodiments, one or more input controllers 160 are 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., 208 in fig. 2) optionally include an up/down button for volume control of the speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206 in fig. 2).

A quick press of the push button unlocks the touch screen 112 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 application 7,657,849, which are incorporated herein by reference in their entirety. Pressing the push button (e.g., 206) longer may turn the device 100 on or off. The user can customize the functionality of one or more buttons. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

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

Touch screen 112 has a touch-sensitive surface, sensor, or group of sensors that accept input from a user based on tactile sensation and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 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 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to a finger of the user.

The touch screen 112 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. Touch screen 112 and display controller 156 may detect contact and any movement or break 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 touch screen 112. In one exemplary embodiment, projected mutual capacitance sensing technology is used, such as that in Apple Inc. (Cupertino, California)And iPodThe technology found in (1).

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

The touch sensitive display in some embodiments of touch screen 112 may be as described in the following patent applications: (1) U.S. patent application No. 11/381,313 entitled "Multipoint Touch Surface Controller" filed on 2.5.2006; (2) U.S. patent application No. 10/840,862 entitled "Multipoint touch screen" filed on 6.5.2004; (3) U.S. patent application No. 10/903,964 entitled "Gestures For Touch Sensitive Input Devices" filed on 30.7.2004; (4) U.S. patent application No. 11/048,264 entitled "Gestures For Touch Sensitive Input Devices" filed on 31/1/2005; (5) U.S. patent application 11/038,590 entitled "model-Based Graphical User Interfaces For Touch Sensitive Input Devices" filed on 18.1.2005; (6) U.S. patent application No. 11/228,758 entitled "Virtual Input Device On A Touch Screen User Interface" filed On 16.9.2005; (7) U.S. patent application No. 11/228,700 entitled "Operation Of A Computer With A Touch Screen Interface," filed on 16.9.2005; (8) U.S. patent application 11/228,737 entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keys" filed on 16.9.2005; and (9) U.S. patent application 11/367,749 entitled "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 112 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 112 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 large 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 100 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 that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

The device 100 also includes a power system 162 for powering the various components. The power system 162 may include a power management system, one or more power sources (e.g., batteries, 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 100 may also include one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to an optical sensor controller 158 in the I/O subsystem 106. The optical sensor 164 may include a Charge Coupled Device (CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The optical sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. In conjunction with imaging module 143 (also referred to as a camera module), optical sensor 164 may capture still images or video. In some embodiments, the optical sensor is located on the back of device 100 opposite touch screen display 112 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, an optical sensor is located on the front of the device so that an image of the user is available for the video conference while the user views other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 164 may be changed by the user (e.g., by rotating a lens and sensor in the device housing) so that a single optical sensor 164 may be used with a touch screen display for both video conferencing and still image and/or video image capture.

Device 100 optionally further comprises one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 in the I/O subsystem 106. Contact intensity sensor 165 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 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some implementations, at least one contact intensity sensor is juxtaposed or adjacent to the touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

The device 100 may also include one or more proximity sensors 166. Fig. 1A shows a proximity sensor 166 coupled to the peripheral interface 118. Alternatively, the proximity sensor 166 may be coupled to the input controller 160 in the I/O subsystem 106. The Proximity sensor 166 may be as described In U.S. patent application 11/241,839, "Proximity Detector In Handheld Device"; 11/240,788, "Proximaty Detector In Handdheld Device"; 11/620,702, "Using Ambient Light Sensor To Automation restriction Sensor Output"; 11/586,862, "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11/638,251, "Methods And Systems For Automatic Configuration Of Periphers," which is hereby incorporated by reference in its entirety. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally further comprises one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to a tactile feedback controller 161 in I/O subsystem 106. Tactile output generator 167 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 165 receives haptic feedback generation instructions from haptic feedback module 133 and generates haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112), and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., into/out of the surface of device 100) or laterally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

Device 100 may also include one or more accelerometers 168. Fig. 1A shows accelerometer 168 coupled to peripheral interface 118. Alternatively, accelerometer 168 may be coupled to input controller 160 in I/O subsystem 106. Accelerometer 168 may perform 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 Accelerometer", both U.S. patent publications are incorporated herein by reference in their entirety. In some embodiments, the 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. In addition to one or more accelerometers 168, device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information regarding the position and orientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or set of instructions) 128, a contact/motion module (or set of instructions) 130, a graphics module (or set of instructions) 132, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and an application program (or set of instructions) 136. Further, in some embodiments, memory 102 (fig. 1A) or 370 (fig. 3) stores device/global internal state 157, as shown in fig. 1A, and fig. 3. Device/global internal state 157 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 112; sensor status, including information obtained from the various sensors of the device and the input control device 116; and location information regarding the location and/or attitude of the device.

Operating system 126 (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.

Communication module 128 facilitates communication with other devices through one or more external ports 124, and further includes functionality for processing by RF circuitry 108 and/or external ports 124Various software components of the received data. External port 124 (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.) a multi-pin (e.g., 30-pin) connector that is the same as or similar to and/or compatible with the 30-pin connector used on the device.

Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or a physical click wheel). The contact/motion module 130 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 contact disconnection). The contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact optionally includes determining velocity (magnitude), velocity (magnitude and direction), and/or 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 130 and the display controller 156 detect a contact on the touch panel.

In some embodiments, the contact/motion module 130 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 100). For example, the mouse "click" threshold of a trackpad or touch screen display may be set to any one of a wide range of predefined thresholds without changing the trackpad or touch screen 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 130 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 particular 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 an 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 132 includes various known software components for rendering and displaying graphics on touch screen 112 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 132 stores data to be used to represent graphics. Each graphic is optionally assigned a corresponding code. The graphic module 132 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 156.

Haptic feedback module 133 includes various software components for generating instructions for use by one or more haptic output generators 167 to produce haptic outputs at one or more locations on device 100 in response to user interaction with device 100.

Text input module 134, which may be a component of graphics module 132, provides a soft keyboard for entering text in a variety of applications, such as contacts 137, email 140, instant message 141, browser 147, and any other application that requires text input. In particular, the text input module 134 may include one or more geometric models and one or more language models for language input correction, as described below.

The GPS module 135 determines the location of the device and provides this information for various applications (e.g., to the phone 138 for location-based dialing; to the camera 143 as picture/video metadata; and to applications that provide location-based services such as weather desktop widgets, local yellow pages desktop widgets, and map/navigation desktop widgets).

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

a contacts module 137 (sometimes referred to as an address book or contact list);

a phone module 138;

a video conferencing module 139;

an email client module 140;

an Instant Messaging (IM) module 141;

fitness support module 142;

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

an image management module 144;

a video player module;

a music player module;

a browser module 147;

a calendar module 148;

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

a desktop applet creator module 150 for forming a user-created desktop applet 149-6;

a search module 151;

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

a notepad module 153;

a map module 154; and/or

Online video module 155.

Examples of other applications 136 that may be stored in memory 102 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 touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 may be used to manage contact lists or contact lists (e.g., stored in memory 102 or in application internal state 192 of contacts module 137 in memory 370), including: adding one or more names to an address book; deleting one or more names from the address book; associating one or more telephone numbers, one or more email addresses, one or more physical addresses, 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 138, video conferencing module 139, email 140, or instant message 141; and so on.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, phone module 138 may be used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in contacts module 137, modify the entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As noted above, wireless communication may use any of a number of communication standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephony module 138, video conference module 139 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 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions to create, send, receive, and manage emails in response to user instructions. In conjunction with the image management module 144, the email client module 140 makes it very easy to create and send emails with still images or video images captured by the camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for: the method includes 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 Message Service (MMS) protocol for a phone-based instant message, or using XMPP, SIMPLE, or IMPS for an internet-based instant message), receiving the 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 sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, fitness support module 142 includes executable instructions to create a fitness (e.g., having a time, distance, and/or karhunen burning goal); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating a sensor for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.

In conjunction with touch screen 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions for: capturing still images or video (including video streams) and storing them in the memory 102, modifying features of the still images or video, or deleting the still images or video from the memory 102.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 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 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse 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 RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do, etc.) according to user instructions.

In conjunction with the RF circuitry 108, the touch screen 112, the display controller 156, the contact/motion module 130, the graphics module 132, the text input module 134, and the browser module 147, the desktop applet module 149 is a mini-application (e.g., a weather desktop applet 149-1, a stock market desktop applet 149-2, a calculator desktop applet 149-3, an alarm desktop applet 149-4, and a dictionary desktop applet 149-5) or a mini-application created by a user (e.g., a user created desktop applet 149-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 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the desktop applet creator module 150 may be used by a user to create a desktop applet (e.g., to turn a user-specified portion of a web page into a desktop applet).

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search memory 102 for text, music, sound, images, videos, and/or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speakers 111, RF circuitry 108, and browser module 147, video and music player module 152 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 touch screen 112 or on an external display connected via external port 124). In some embodiments, the device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple inc.).

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notepad module 153 includes executable instructions to create and manage notepads, backlogs, and the like according to user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 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 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions for: allowing a user to access, browse, receive (e.g., by streaming and/or downloading), playback (e.g., on a touch screen or on an external display connected via external port 124), send an email with a link to a particular online video, and otherwise manage online video 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 141 instead of email client module 140. 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 152 in FIG. 1A). In some implementations, memory 102 may store a subset of the modules and data structures identified above. Further, memory 102 may store additional modules and data structures not described above.

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

The set of predefined functions performed exclusively by the touch screen and/or the touchpad optionally includes navigating between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 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. 1B is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 (FIG. 1A) or memory 370 (FIG. 3) includes event classifier 170 (e.g., in operating system 126) and corresponding application 136-1 (e.g., any of the aforementioned applications 137-151,155,380-390).

Event sorter 170 receives the event information and determines application 136-1 and application view 191 of application 136-1 to which the event information is to be delivered. The event sorter 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes an application internal state 192 that indicates one or more current application views that are displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event classifier 170 to determine which application(s) are currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which to deliver event information.

In some embodiments, the application internal state 192 includes additional information, such as one or more of: resume information to be used when the application 136-1 resumes execution, user interface state information indicating information being displayed by the application 136-1 or information that is ready for display by the application, 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.

Event monitor 171 receives event information from peripheral interface 118. The event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information that it receives from I/O subsystem 106 or sensors, such as proximity sensor 166, one or more accelerometers 168, and/or microphone 113 (via audio circuitry 110). Information received by peripheral interface 118 from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

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

In some embodiments, event classifier 170 further includes hit view determination module 172 and/or active event recognizer determination module 173.

When touch-sensitive display 112 displays more than one view, hit view determination module 172 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 hierarchical 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 172 receives information related to sub-events of the touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 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 172, 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 active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, the active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 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 actively participating views.

The event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers event information to event recognizers determined by active event recognizer determination module 173. In some embodiments, the event dispatcher module 174 stores event information in an event queue, which is retrieved by the respective event receiver 182.

In some embodiments, the operating system 126 includes an event classifier 170. Alternatively, the application 136-1 includes an event classifier 170. In other embodiments, the event classifier 170 is a stand-alone module or is part of another module (e.g., the contact/motion module 130) stored in the memory 102.

In some embodiments, the application 136-1 includes a plurality of event handlers 190 and one or more application views 191, where each application view includes instructions for handling touch events occurring within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, the respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit (not shown) or a higher-level object from which the application 136-1 inherits methods and other properties. In some implementations, the respective event handlers 190 include one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 may utilize or call data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

The corresponding event recognizer 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies events from the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event identifier 180 further includes at least a subset of: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).

The event receiver 182 receives event information from the event sorter 170. The event information includes information about a sub-event (e.g., 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 relates to 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 184 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 184 includes event definitions 186. Event definition 186 contains definitions of events (e.g., predefined sub-event sequences), such as event 1(187-1), event 2(187-2), and others. In some embodiments, sub-events in event (187) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1(187-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 duration, a first lift-off (touch end) for a predetermined duration, a second touch (touch start) on the displayed object for a predetermined duration, and a second lift-off (touch end) for a predetermined duration. As another example, event 2(187-2) is defined as a drag on a displayed object. For example, dragging includes a predetermined length of time of touch (or contact) on a displayed object, movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

In some embodiments, event definition 187 includes definitions of events for respective user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view that displays three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 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 190, the event comparator uses the results of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 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 187 further includes a delay action that delays the delivery of the event information until it has been determined that the sequence of sub-events does or does not correspond to the event type of the event recognizer.

When the respective event recognizer 180 determines that the sequence of sub-events does not match any event in the event definition 186, the respective event recognizer 180 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 180 includes metadata 183 with configurable attributes, tags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, the metadata 183 includes configurable attributes, flags, and/or lists that indicate how or how the event recognizers interact with each other. In some embodiments, metadata 183 includes configurable attributes, flags, 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 180 activates an event handler 190 associated with the event. In some embodiments, the respective event identifier 180 delivers event information associated with the event to the event handler 190. Activating an event handler 190 is different from sending (and deferring) sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a flag associated with the recognized event and the event handler 190 associated with the flag retrieves the flag and performs a predefined process.

In some embodiments, the event delivery instructions 188 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 series of sub-events or to actively participating views. Event handlers associated with the series of sub-events or with actively participating views receive the event information and perform a predetermined process.

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

In some embodiments, one or more event handlers 190 include, or have access to, data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. 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 100, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, optionally in conjunction with single or multiple keyboard presses or presses; contact movements on the touchpad, such as taps, drags, scrolls, and the like; inputting by a stylus; movement of the device; verbal instructions; detected eye movement; inputting biological characteristics; and/or any combination thereof, is optionally used as input corresponding to sub-events defining the event to be identified.

Fig. 2 illustrates a portable multifunction device 100 with a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within the User Interface (UI) 200. In this and 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 202 (not drawn to scale in the figure) or with one or more styluses 203 (not drawn to scale in the figure). 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 100. In some specific implementations, or in some cases, inadvertent contact with a graphic does not select a 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 corresponding application.

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

In some embodiments, device 100 includes touch screen 112, menu buttons 204, push buttons 206 for powering the device on/off and for locking the device, one or more volume adjustment buttons 208, a Subscriber Identity Module (SIM) card slot 210, a headset jack 212, and docking/charging external port 124. Pressing the button 206 optionally serves to turn the device on/off by depressing the button and holding the button in a depressed state for a predefined interval of time; locking the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or unlocking the device or initiating an unlocking process. In an alternative embodiment, device 100 also accepts voice input through microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on touch screen 112, and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.

Fig. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. The device 300 need not be portable. In some embodiments, the device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (e.g., a child learning toy), a gaming system, or a control device (e.g., a home controller or an industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communications between system components. Device 300 includes an input/output (I/O) interface 330 with a display 340, typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 (e.g., similar to one or more tactile output generators 167 described above with reference to fig. 1A) for generating tactile outputs on device 300, sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch-sensitive sensors, and/or contact intensity sensors (similar to one or more contact intensity sensors 165 described above with reference to fig. 1A)). Memory 370 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 370 optionally includes one or more storage devices located remotely from one or more CPUs 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to those stored in memory 102 of portable multifunction device 100 (fig. 1A), or a subset thereof. Further, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk editing module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

Each of the aforementioned elements in fig. 3 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 the above-described functions. 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 370 may store a subset of the modules and data structures described above. In addition, memory 370 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 100.

Fig. 4A illustrates an exemplary user interface of an application menu on portable multifunction device 100 according to some embodiments. A similar user interface may be implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof:

one or more signal strength indicators 402 for one or more wireless communications (such as cellular signals and Wi-Fi signals);

time 404;

a Bluetooth indicator 405;

a battery status indicator 406;

tray 408 with common application icons such as:

an icon 416 of the phone module 138 labeled "phone," optionally including an indicator 414 of the number of missed calls or voice messages;

an icon 418 of the email client module 140 labeled "mail", optionally including an indicator 410 of the number of unread emails;

icon 420 of the browser module 147, labeled "browser"; and

icon 422 labeled "iPod" for video and music player module 152 (also known as iPod (trademark of Apple inc.) module 152); and

icons for other applications, such as:

icon 424 of IM module 141 labeled "message";

icon 426 of calendar module 148 labeled "calendar";

icon 428 of image management module 144 labeled "photo";

icon 430 of camera module 143 labeled "camera";

icon 432 for online video module 155 labeled "online video";

an icon 434 of the O stock desktop applet 149-2 labeled "stock market";

icon 436 of map module 154 labeled "map";

icon 438 labeled "weather" for weather desktop applet 149-1;

icon 440 of alarm clock desktop applet 149-4 labeled "clock";

icon 442 labeled "fitness support" for fitness support module 142;

icon 444 of O notepad module 153 labeled "notepad"; and

an icon 446 labeled "settings" for setting applications or modules provides access to the settings of the device 100 and its various applications 136.

Note that the icon labels shown in fig. 4A are merely exemplary. For example, icon 422 of video and music player module 152 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. 4B illustrates an exemplary user interface on a device (e.g., device 300 of fig. 3) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of fig. 3) separate from a display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting the intensity of contacts on touch-sensitive surface 451, and/or one or more tactile output generators 359 for generating tactile outputs for a user of device 300.

Although some of the examples that follow will be given with reference to input on touch screen display 112 (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. 4B. In some implementations, the touch-sensitive surface (e.g., 451 in fig. 4B) has a major axis (e.g., 452 in fig. 4B) that corresponds to a major axis (e.g., 453 in fig. 4B) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in fig. 4B) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in fig. 4B, 460 corresponds to 468 and 462 corresponds to 470). Thus, when the touch-sensitive surface (e.g., 451 in FIG. 4B) is separated from the display (450 in FIG. 4B) of the multifunction device, user inputs (e.g., contacts 460 and 462 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., instead of detecting a contact, followed by ceasing to detect a 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. 5A illustrates an exemplary personal electronic device 500. The device 500 includes a body 502. In some embodiments, device 500 may include some or all of the features described with respect to devices 100 and 300 (e.g., fig. 1A-4B). In some embodiments, the device 500 has a touch-sensitive display screen 504, referred to hereinafter as a touch screen 504. Instead of or in addition to the touch screen 504, the device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some implementations, touch screen 504 (or touch-sensitive surface) may have one or more intensity sensors for detecting the intensity of an applied contact (e.g., a touch). One or more intensity sensors of the touch screen 504 (or touch-sensitive surface) may provide output data representing the intensity of a touch. The user interface of device 500 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 500.

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 on 11.11.2013, each of which is hereby incorporated by reference in its entirety.

In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) may be in physical form. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, may allow for attachment of the device 500 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 500.

Fig. 5B illustrates an exemplary personal electronic device 500. In some embodiments, the apparatus 500 may include some or all of the components described with reference to fig. 1A, 1B, and 3. The device 500 has a bus 512 that operatively couples an I/O portion 514 with one or more computer processors 516 and a memory 518. I/O portion 514 may be connected to display 504, which may have touch sensitive component 522 and optionally also touch intensity sensitive component 524. Further, I/O section 514 may connect with communications unit 530 for receiving applications and operating system data using Wi-Fi, bluetooth, Near Field Communication (NFC), cellular, and/or other wireless communications technologies. Device 500 may include input mechanisms 506 and/or 508. For example, the input mechanism 506 may be a rotatable input device or a depressible input device as well as a rotatable input device. In some examples, the input mechanism 508 may be a button.

In some examples, the input mechanism 508 may be a microphone. Personal electronic device 500 may include various sensors, such as a GPS sensor 532, an accelerometer 534, an orientation sensor 540 (e.g., a compass), a gyroscope 536, a motion sensor 538, and/or combinations thereof, all of which may be operatively connected to I/O section 514.

The memory 518 of the personal electronic device 500 may be a non-transitory computer-readable storage medium for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described below, including process 800 (fig. 8A-8E) and process 900 (e.g., fig. 9A-9C), for example. The computer-executable instructions may also be stored and/or transmitted within any non-transitory computer-readable storage medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. The personal electronic device 500 is not limited to the components and configuration of fig. 5B, 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 100,300, and/or 500 (FIGS. 1,3, and 5). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) may 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, if an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in fig. 3 or touch-sensitive surface 451 in fig. 4B) 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 in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in fig. 1A or touch screen 112 in fig. 4A) 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 according to the detected input. In some implementations, 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 focus from one button to another using tab or arrow keys); in these implementations, the focus selector moves according to movement of the focus 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 (rather than other user interface elements shown on the display of the device).

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 intensity increase of contact, and/or before or after detecting intensity decrease 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 feature strengths 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 feature intensity. For example, the touch-sensitive surface may receive a continuous swipe contact that transitions from a starting position and reaches an ending position where the strength of the contact increases. In this example, the characteristic strength of the contact at the end position may be based on only a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only a 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 determining the characteristic 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 the device will perform 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 this intensity, the device will perform a different operation than the operation typically associated with clicking a button of a physical mouse or trackpad. In some implementations, 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 below which a contact 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 the light press intensity threshold or the deep press intensity threshold. Generally, these intensity thresholds are consistent between different sets of user interface drawings, unless otherwise noted.

The increase in the characteristic intensity of the contact 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. An increase in the characteristic intensity of the contact 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 the characteristic intensity of the contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting liftoff 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 that the respective contact intensity increases 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 the respective contact intensity above a press input intensity threshold and a subsequent decrease in the contact intensity below the press input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in the respective contact intensity 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 less 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 a respective contact intensity increasing above a press input intensity threshold and a subsequent decrease in the contact intensity below a hysteresis intensity threshold corresponding to the press input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in the respective contact intensity below the hysteresis intensity threshold (e.g., an "up stroke" 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.

2. Exemplary techniques for Intelligent device identification

Fig. 6A-6F illustrate exemplary techniques for smart device identification, according to some embodiments. These drawings are also used to illustrate a process including the processes in fig. 8A to 8E and fig. 9A to 9C described below.

FIG. 6A shows electronic devices 602,604,606, and 608 of a user 600. In some embodiments, one or more of the devices 602-608 can be any of the devices 104, 122,200,400, and 1000 (fig. 1, 2, 4, and 10). In some examples, the electronic device 602 is a wearable electronic device, such as a smart watch, and is powered off when in the down position, as shown. In some examples, electronic device 604 is a mobile device such as a mobile phone, electronic device 606 is an electronic device with relatively large display capabilities such as a television, and electronic device 608 is a device with audio output capabilities such as a speaker dock. Although the illustrated example is described herein with reference to electronic devices 602-608, it should be appreciated that a lesser or greater number of devices may be used in other implementations.

Fig. 6B shows the user 600 lifting the electronic device 602 to a raised position. In response to the movement, the device 602 turns on a touch screen of the electronic device 602. Upon the touch screen of the electronic device 602 being turned on, the electronic device 602 also begins sampling audio input through its microphone to listen for voice input from the user 600. One or more other electronic devices, such as electronic devices 604,606, and 608, may also begin sampling audio input to listen for speech input from user 600. Each of the electronic devices 604,606, and 608 may begin sampling audio input in response to detecting the proximity of the user 600, or may continuously sample audio input.

As shown, the user 600 can provide voice instructions 612 when one or more of the electronic devices 602-608 sample audio input. Each electronic device 602-608 detects the voice instruction 612 when the audio input is sampled and determines whether the voice instruction 612 contains a phrase for triggering a virtual assistant service of the respective device. For each of the electronic devices 602-608, the virtual assistant is triggered if it is determined that the sampled input comprises a voice trigger. Optionally, an output may also be provided indicating that the sampled audio input comprises a voice trigger. The output may be visual (e.g., display a notification or LED to toggle back), audible, and/or tactile. If it is determined that the sampled audio input does not contain a spoken trigger, the audio input may be further sampled for a predetermined amount of time or indefinitely.

In the illustrated example, the voice trigger is the phrase "hey, Siri". Thus, the voice instructions 612 trigger the respective virtual assistant in each electronic device that samples the voice instructions 612. In addition to the voice trigger, the voice instructions 612 also include a natural language input (e.g., "incoming television series") that at least one of the virtual assistants of the respective devices parses (e.g., manipulates) into one or more tasks.

In some examples, the natural language input is parsed into one or more tasks by a single device in the electronic device 602 and 608. For example, once the speech audio input is sampled, one of the electronic devices 602 and 608 may be identified as the first device for determining tasks based on the sampled audio input. For example, a first device for determining a task may be identified based on a set of prioritization rules. For example, the first device may be the device whose sampled audio input has the highest speech quality, sound pressure level, and/or volume. In another example, the first device may be the device closest to the user 600. In yet another example, the first device may be identified based on a type of the respective device. For example, in a system including a mobile device and other non-wearable devices, the mobile device may be the first device to determine a task. In a system including a wearable device, the wearable device may be a first device for determining a task. Accordingly, in the illustrated example, the device 602 may be identified as a device for determining tasks based on sampled audio input.

The tasks may be determined locally or remotely. A device, such as electronic device 602, may determine a task locally using the sampled audio input, or may transmit data representing the sampled audio input to one or more servers. The task may be determined by one or more servers based on the transmitted data and provided to the device. Optionally, one or more devices may provide an output after determining the task. Referring to fig. 6C-6F, any one of the electronic devices 602-608 may respectively provide an output for confirming that the task has been determined. In some examples, after the task determination, the plurality of devices provide an output. The manner in which the output is provided may indicate, for example, which devices are used to determine the task.

Once the task has been determined, one of the electronic devices 602-608 may be identified as a second device for performing the task. The second device may be identified by the first device and may also be the first device or a device different from the first device. In some examples, the second device may be identified based on task requirements. For example, a task may require that the task be performed by a device having a particular capability (e.g., function). For example, in the example shown, the task may be for playback of a certain collection of television programs and require display functionality. Accordingly, the electronic device 602 can determine which of the electronic devices 602 and 608 satisfies the display capability requirement. In other embodiments, the task may need to be performed with the mobile device. In yet another embodiment, the task may need to be performed with a device plugged into an electrical outlet. If none of the electronic devices 602-608 can satisfy the requirements of the task, one or more of the devices 602-608 may forgo performing the task.

Since multiple devices may satisfy the task requirements, the second device may additionally or alternatively be identified according to multiple prioritization rules. In some examples, the second device may be the device that is "best suited" to perform the task. For example, for a task directed to video playback, the second device may be an electronic device with a maximum display. In the illustrated example, the electronic device 602 can determine that the electronic device 606 is most suitable for video playback based on, for example, the relative display sizes of the electronic device 602 and 606. For the task for the mapping function, the second device may be a mobile device. In some examples, the second device may be identified based on previous usage. For example, a device that is typically used to perform a task may be identified as performing a subsequent iteration of that or a similar task. In some embodiments, the second device may be identified based on a signal strength between the first device and each of the other devices.

Once the second device is identified, the task may be provided by the first device to the second device. As shown in fig. 6C, in response to sampling the audio input containing the instructions 612, the electronic device 602 provides the task to the electronic device 606, which in turn performs the task by playing the requested episode. In some examples, the tasks are provided by device 602 directly to device 606, and in other examples, via one or more intermediate devices (such as device 604). Once the task has been received by the second device, the second device may perform the task.

In some examples, the second device may delay execution of the task. For example, a task may include one or more criteria that must be met before the task is performed. For example, the task may require the user to stop driving (e.g., as determined by GPS) before the task is performed, and/or may require a particular form of connection (e.g., bluetooth) before the task is performed.

As another example, a task may require a user to be authenticated prior to performing the task. Referring to fig. 7A, a user may provide an audio input 702 requesting playback of an R-level movie, and the request may be resolved, for example, by the device 602 to a task to play back the R-level movie on the electronic device 606. Due to the nature of the movie rating, the task may first require the user to authenticate. Authentication may be implemented using biometric authentication (e.g., fingerprint authentication) and/or credential authentication (e.g., username and password). Referring to FIG. 7B, the device 604 may provide input requests 712,714, respectively, requesting input of a biometric (e.g., fingerprint identification). As shown in fig. 7C, the user may provide biometric input and the device 604 may authenticate the user. In some examples, the device 604 may provide outputs 722,724 confirming authentication completion and that an R-rated movie is being played on the device 606, respectively. It should be understood that authentication may be employed using any of the electronic devices 602 through 608, including but not limited to devices for parsing and/or performing tasks.

3. Process for identifying an electronic device to perform a task

Fig. 8A-8E illustrate a process for identifying an electronic device to perform a task, according to various examples. In some examples, process 800 may be employed using, for example, a digital assistant implemented on one or more electronic devices. In some examples, process 800 may be performed using a client-server system (e.g., system 100) implementing a digital assistant. It should be appreciated that in other examples, the various blocks of process 800 may be distributed among one or more computers, systems or electronic devices in any suitable manner. For example, in some examples, process 800 may be performed entirely on an electronic device (e.g., devices 104,200, 400). Further, while the following discussion describes process 800 as being performed by a digital assistant system (e.g., system 100), it should be appreciated that the process or any particular portion of the process is not limited to being performed by any particular device, combination of devices, or implementation.

At block 802, audio input may be sampled at each of two or more of a plurality of electronic devices (e.g., device 104,200,400). In particular, audio input may be received from users of multiple electronic devices. The audio input may be received during or as part of an interaction with a corresponding or same digital assistant, wherein the digital assistant is implemented on each of a plurality of electronic devices. In some examples, the audio input may be received via a microphone (e.g., microphone 113) of the electronic device. The received audio input may be processed (e.g., using audio circuitry 210 or one or more processors 220) and converted into a representation, such as an electronic signal (digital or analog) or one or more audio files.

In some examples, the audio input may represent and/or include a user request. For example, the audio input may include a request to play the latest episode of the game of rights, thereby requesting to play the latest episode of the TV series game of rights. Further, in some examples, the audio input may not explicitly contain a user request, but rather may suggest the user request based on the context in which the audio input was received. In particular, the user request may be implied based on the input field and/or application for which the audio input is intended. For example, the audio input may include the word "restaurant" when the focus is currently on the search field of the mapping application. In this example, the audio input may represent a user request to obtain restaurant location information in a particular geographic area.

It should be appreciated that in some examples, text input may be received at block 802 instead of audio input. For example, textual input from the user representing a user request may be received via a suitable user interface on one or more of the plurality of electronic devices. Examples of suitable user interfaces for receiving text input may include virtual keyboards, handwriting recognition interfaces, gesture recognition interfaces, and the like.

In some examples, sampling the audio input at block 802 may include determining whether the audio input includes a voice trigger. The voice trigger may include any predetermined keyword, phrase, or other voice input that triggers one or more of the plurality of electronic devices to analyze subsequent input for a user request. For example, the voice trigger may include the phrase "hey, Siri". In response, each electronic device may sample a subsequent audio input. In some examples, an output may be provided that confirms sampling of the audio output. For example, the output may be provided in accordance with a determination that the audio input comprises a voice trigger.

At block 806, a first electronic device of a plurality of electronic devices for determining a task associated with the sampled audio input may be identified. In some examples, the electronic device is identified based on a quality of speech received by the device. The voice quality may differ, for example, based on a distance between the user and each of the plurality of electronic devices and/or one or more other acoustic characteristics of the operating environment of the plurality of electronic devices. In an example where the plurality of devices includes a mobile phone and a television, the mobile phone may be identified with the mobile phone closer to the user. In some examples, identifying the first electronic device includes determining a respective speech quality in the audio input sampled at each of the two or more electronic devices. The speech quality may be determined, for example, based on acoustic ambient noise, minimum volume, maximum volume, volume change, frequency, or a combination thereof.

The devices may be further identified based on a predetermined set of prioritization rules that specify which type of electronic device will prioritize over other types of electronic devices. For example, in some examples, identifying the first electronic device includes determining whether the two or more electronic devices include a wearable electronic device (e.g., a smart watch). If so, the wearable electronic device is identified as the first electronic device.

In some examples, identifying the first electronic device includes determining a respective sound pressure level of the sampled audio input at each of the two or more electronic devices. The electronic device identified as having the highest sound pressure level may be identified as the first electronic device.

At block 818, a task may be determined based on the sampled audio input. In some examples, the task may be determined by the first electronic device. In at least one embodiment, the first electronic device locally parses the audio input into tasks. That is, the audio input is parsed at the first electronic device. In other embodiments, the audio input is parsed remotely. For example, the first electronic device may communicate with a service, such as a cloud-based virtual assistant service, and provide audio input to the service, which may then parse the audio input into tasks. The task may then be provided by the service to the first electronic device. Exemplary tasks may include, but are not limited to, any number of playback, mapping, lookup, and storage functions.

In some examples, after the audio input has been sampled, an output may be provided that confirms that the task has been determined based on the sampled audio input. The output may be provided by one or more electronic devices and may be visual, auditory, and/or tactile. In some examples, the output serves as confirmation that the user's audio input has been received. In some examples, the output is provided by an electronic device of a plurality of electronic devices other than the first electronic device. For example, a user may speak into the wearable electronic device, and another electronic device (such as a speaker base) may output audio that emits "i am playing your playlist". In some examples, the output is provided by an electronic device of the plurality of electronic devices other than the first electronic device that samples and/or parses the audio input and the second electronic device that performs the task. For example, a user may speak into a first electronic device (e.g., a mobile phone) and a wearable electronic device (e.g., a smart watch) of the user may provide an output, such as a vibration indicating that a task is being provided to a third device (e.g., a television).

In some examples, a first output may be provided that confirms sampling of the audio input, and after the audio input has been sampled, a second output may be provided that indicates that a task has been determined based on the sampled audio input. In some examples, the first output and the second output have different characteristics. In some examples, the first output may be provided by two or more electronic devices. For example, in some embodiments, ones of the plurality of electronic devices provide relatively fewer perceptible indications (such as illumination of an LED) to indicate that the audio input is being sampled, while particular electronic devices provide relatively more perceptible indications, such as audible (e.g., verbal) indications to indicate that the sampled audio input is being interpreted. In this way, the user is made aware that one or more electronic devices are processing audio input, but the selected electronic device provides confirmation that a task will be performed based on the audio input.

At block 824, a second electronic device for performing a task may be identified. For example, the second electronic device may be identified by the first electronic device, another electronic device of the plurality of devices, and/or a service for resolving audio input (block 818).

In some examples, identifying the second electronic device includes determining a signal strength of wireless communication (e.g., bluetooth LE, WiFi) between the first electronic device and one or more other electronic devices of the plurality of electronic devices. For example, signal strength may be measured using signal reliability and/or data throughput. The electronic device with the highest signal strength may be identified as the second electronic device.

In some examples, the second electronic device may be identified by obtaining an indication of a display screen size of an electronic device of the plurality of electronic devices. A determination may then be made as to whether the indication meets the requirements of the task. For example, it may be determined whether a task requires a screen size that is greater than a threshold size or less than a threshold size. In accordance with a determination that the indication meets the requirements, the electronic device may be identified as a second electronic device. For example, a first electronic device may identify the electronic device as a second electronic device. In accordance with a determination that the indication is unsatisfactory, the electronic device may not be identified as the second electronic device. For example, a first electronic device may forgo identifying the electronic device as a second electronic device.

In some examples, the second electronic device may be identified by determining whether an electronic device of the plurality of electronic devices is a mobile electronic device. In some examples, the mobile device may be any device that is battery powered. In accordance with a determination that the electronic device is a mobile device, the electronic device may be identified as a second electronic device. For example, a first electronic device may identify the electronic device as a second electronic device. In accordance with a determination that the electronic device is not a mobile device, the electronic device cannot be identified as a second electronic device. For example, a first electronic device may forgo identifying the electronic device as a second electronic device.

In some examples, the second electronic device may be identified by determining whether an electronic device of the plurality of electronic devices is powered by the power outlet. In accordance with a determination that the electronic device is powered by the electrical outlet, the electronic device may be identified as a second electronic device. For example, a first electronic device may identify the electronic device as a second electronic device. In accordance with a determination that the electronic device is not powered by the electrical outlet, the electronic device is not identifiable as a second electronic device. For example, a first electronic device may forgo identifying the electronic device as a second electronic device.

In some examples, the second electronic device may be determined based on the task. For example, as described, the task may specify one or more requirements, and an electronic device best suited to perform the task according to the specified one or more requirements may be selected. For example, a task may require the use of a mapping service, and thus a device having cellular and/or internet connectivity, such as a mobile phone, may be determined.

At block 868, the task may be performed, for example, using a second electronic device. In some examples, the second electronic device is not the first electronic device.

Optionally, the user is prompted for input prior to performing the task using the second electronic device. The input provided in this manner may include biometric input and/or input of a password or other credential. In some examples, a biometric sensor, such as a fingerprint reader, may be used to receive the prompted input. After receiving the prompted input, the second electronic device performs the task. In some examples, a third electronic device of the plurality of electronic devices is identified. The third electronic device may have an input interface configured to detect the alert input.

Optionally, execution of the task may be delayed until the criteria are met. In some examples, the delaying may be performed by the second electronic device. Criteria relied upon in this manner may include criteria for user activity and/or the status of one or more electronic devices. For example, a first criterion may require that the user has stopped driving as determined by the GPS coordinates, and a second criterion may include bluetooth connectivity. In some examples, an output may be provided, for example by the second electronic device, which provides criteria for performing the task. The output providing criteria may be visual, auditory and/or tactile.

Fig. 9A-9C illustrate a process for identifying an electronic device to perform a task, according to various examples. In some examples, process 900 may be employed using, for example, a digital assistant implemented on one or more electronic devices. In some examples, process 900 may be performed using a client-server system (e.g., system 100) implementing a digital assistant. It should be appreciated that the various blocks of process 900 may be distributed among one or more computers, systems or electronic devices in any suitable manner. For example, in some examples, process 900 may be performed entirely on an electronic device (e.g., device 104,200,400). Further, while the following discussion describes process 900 as being performed by a digital assistant system (e.g., system 100), it should be appreciated that the process or any particular portion of the process is not limited to being performed by any particular device, combination of devices, or implementation.

At block 902, data indicative of a task may be received at a first electronic device (e.g., device 104,200,400). The data indicative of the task may be data representative of the task, data corresponding to the task, data associated with the task, and/or data from which the task may be otherwise derived. This data indicative of the task may be received from a user of the first electronic device. In some examples, the data indicative of the task may be received during or as part of an interaction with a corresponding or same digital assistant implemented on the first electronic device. In some embodiments, the tasks are parsed locally, and in other embodiments are parsed remotely (e.g., server-side). Tasks include, but are not limited to, any number of playback, mapping, lookup, and storage functions. In some examples, the task is associated with an audio input. The audio input may include a talk trigger (e.g., "hey, Siri") and/or one or more user requests or commands.

In some examples, receiving data indicative of the task includes receiving audio input via a microphone (e.g., microphone 113) of the first electronic device. The received audio input may be processed (e.g., using audio circuitry 210 or one or more processors 220) and converted into a representation, such as an electronic signal (digital or analog) or one or more audio files. In response to receiving the audio input, data indicative of the task may be generated based on the received audio input. The data indicative of the task may be generated by the first electronic device.

In some examples, receiving data indicative of the task includes receiving audio input via a microphone (e.g., microphone 113) of the first electronic device. Data representing the received audio input may be provided (e.g., transmitted) to one or more servers, and data indicative of the task may be received from the one or more servers. In some examples, the task is determined by the one or more servers based on data representative of the received audio input.

It should be appreciated that in some examples, text input may be received at block 902 instead of audio input. For example, textual input from the user representing a user request may be received via a suitable user interface on one or more of the plurality of electronic devices. Examples of suitable user interfaces for receiving text input may include virtual keyboards, handwriting recognition interfaces, gesture recognition interfaces, and the like.

At block 914, a determination is made as to whether the first electronic device or the second electronic device is to perform the task. In some examples, the determination is made with the first electronic device.

In some examples, determining whether the first electronic device or the second electronic device is to perform the task includes determining whether the task is associated with the first electronic device or the second electronic device according to a plurality of prioritization rules. In some examples, the prioritization rules may be task-specific and/or device-specific. For example, prioritization rules may specify which devices are to perform respective tasks based on the type, capabilities, and/or usage (e.g., recency of use, frequency of use, tasks performed during use) of each electronic device. Determining whether the task is associated with the first electronic device or the second electronic device according to the plurality of prioritization rules may include determining whether the task is associated with the first electronic device or the second electronic device based on a display capability of the first electronic device, a mobility of the first electronic device, or a combination thereof. An electronic device with a larger display may be determined as the electronic device performing the task. As another example, the determining may include determining whether the task is associated with the first electronic device or the second electronic device based on previous usage of the first electronic device and the second electronic device. The electronic device that has been used recently may be determined as the electronic device that performs the task, or the electronic device that has performed the specific task recently may be determined as the electronic device that performs the task.

At block 922, in accordance with a determination that the task is associated with the first electronic device, the task may be performed with the first electronic device.

In some examples, performing the task with the first electronic device includes performing a first task associated with a first user and a second task associated with a second user different from the first user. For example, the first electronic device may perform playback of a song for the first user and provide an indication to a restaurant for the second user.

In some examples, performing the task with the first electronic device includes authenticating a user associated with the first electronic device. The first electronic device may authenticate the user using one or more credentials, such as a username and password or numeric keys. In at least one embodiment, authenticating a user with a first electronic device includes receiving a biometric input (e.g., a fingerprint). In response to authenticating the user, a task is performed.

At block 932, in accordance with a determination that the task is associated with the second electronic device, data indicative of the task is caused to be transmitted to the second electronic device. For example, causing the data to be transmitted in this manner may include using the second electronic device to provide data indicative of the task to the third electronic device, or may include causing another electronic device to provide data indicative of the task to the third electronic device.

4. Additional exemplary electronic devices

The operations described above with reference to fig. 8A-8E are optionally implemented by the components depicted in fig. 1A, 2, 4, 6A-6B, 7A. For example, sampling operation 802, identifying operations 806 and 824, determining operation 818, and performing operation 868 are optionally implemented by I/O processing module 728, STT processing module 730, natural language processing module 732, and task stream processing module 736. The I/O processing module 728 may receive voice input representing a user request and may receive metadata associated with the voice input. STT processing module 730 may determine a text string corresponding to the speech input. Natural language processing module 732 may determine whether to perform natural language processing on the text string based on the metadata. In response to determining that natural language processing is to be performed on the text string, natural language processing module 732 may further determine whether the metadata identifies one or more fields that correspond to the user request. In response to determining that the metadata identifies one or more domains corresponding to the user request, natural language processing module 732 may use the text string and generate a structured query representing actionable intents associated with the one or more domains based on the one or more domains. Task flow processing module 736 may execute the task flow associated with the structured query. The task flow processing module 736 may determine whether results satisfying the user request are obtained from executing the task flow. In response to determining that a result satisfying the user request is obtained from executing the task stream, I/O processing module 728 may output data content including the result.

As another example, sampling operation 802, identifying operations 806 and 824, determining operation 818, and performing operation 868 are optionally implemented by digital assistant client module 229 and application program 236. The digital assistant client module 229 may receive voice input from the microphone 213 representing a user request. Digital assistant client module 229 may use RF circuitry 208 to transmit voice input and metadata associated with the voice input. The metadata may identify one or more domains of the ontology, and the one or more domains correspond to the user request. The digital assistant client module may use the RF circuitry 208 to receive data content to facilitate satisfying user requests. The data content may be derived from the speech input. The digital assistant client module 229 may determine whether the data content satisfies the user request. In response to determining that the data content satisfies the user request, the digital assistant client module 229 and the application program 236 may output a result based on the data content.

Fig. 10 illustrates a functional block diagram of an electronic device 1000 configured in accordance with the principles of various described examples. The functional blocks of the device can optionally be implemented by hardware, software, or a combination of hardware and software that perform the principles of the various described examples. Those skilled in the art will appreciate that the functional blocks described in fig. 10 may optionally be combined or separated into sub-blocks in order to implement the principles of the various described examples. Thus, the description herein optionally supports any possible combination, separation, or further definition of the functional blocks described herein.

As shown in fig. 10, the electronic device 1000 may include a microphone 1002 and a processing unit 1008 coupled to the microphone 1002. In some examples, the processing unit 1008 may include a receiving unit 1010, a determining unit 1012, an executing unit 1014, a triggering unit 1016, and optionally a providing unit 1018, a generating unit 1020, a transmitting unit 1022, and a validating unit 924.

The processing unit 1008 is configured to receive (e.g., with the receiving unit 1010), at the first electronic device, data indicative of a task, wherein the task is associated with an audio input; it is determined (e.g., with determining unit 1012) with the first electronic device whether the first electronic device or the second electronic device is to perform the task. In accordance with a determination that the task is associated with the first electronic device, performing (e.g., with the execution unit 1014) the task with the first electronic device; and in accordance with a determination that the task is associated with the second electronic device, cause data indicative of the task to be transmitted (e.g., with the initiation unit 1016) to the second electronic device.

In some examples, causing the data indicative of the task to be provided to the second electronic device includes providing (e.g., with providing unit 1018) the data indicative of the task to a third electronic device.

In some examples, receiving includes receiving an audio input at the microphone 1002, and in response to receiving the audio input, generating (e.g., with the generation unit 1020) data indicative of the task with the first electronic device based at least in part on the received audio input.

In some examples, receiving includes receiving audio input at the microphone 1002; transmitting (e.g., with transmission unit 1022) data representing the received audio input to one or more servers; and receive (e.g., with receiving unit 1010) data from the one or more servers indicating the task, wherein the task is determined by the one or more servers based on the data representing the received audio input.

In some examples, the determining includes determining (e.g., with determining unit 1012) whether the task is associated with the first electronic device or the second electronic device according to a plurality of prioritization rules.

In some examples, determining whether the task is associated with the first electronic device or the second electronic device according to the plurality of prioritization rules includes determining (e.g., with determining unit 1012) whether the task is associated with the first electronic device or the second electronic device based on a display capability of the first electronic device, a mobility of the first electronic device, or a combination thereof.

In some examples, determining whether the task is associated with the first electronic device or the second electronic device according to the plurality of prioritization rules includes determining (e.g., with determining unit 1012) whether the task is associated with the first electronic device or the second electronic device based on previous usage of the first electronic device and the second electronic device.

In some examples, performing the task with the first electronic device includes performing (e.g., with the execution unit 1014) a first task associated with a first user, and wherein the processing unit is further configured to perform (e.g., with the execution unit 1014) a second task associated with a second user different from the first user with the first electronic device.

In some examples, performing the task with the first electronic device includes authenticating (e.g., with authentication unit 1024) a user associated with the first electronic device; and in response to authenticating the user, the task is executed (e.g., with execution unit 1014).

In some examples, authenticating the user includes receiving (e.g., with receiving unit 1010) biometric input.

The operations described above with reference to fig. 9A-9C are optionally implemented by components depicted in fig. 1A, 2, 4, 6A-6B, 7A, or 10. For example, the receiving operation 902, the determining operation 914, the performing operation 922, and the causing operation 932 are optionally implemented by an I/O processing module 728, an STT processing module 730, a natural language processing module 732, and a task stream processing module 736. The I/O processing module 728 may receive voice input representing a user request and may receive metadata associated with the voice input. STT processing module 730 may determine a text string corresponding to the speech input. Natural language processing module 732 may determine whether to perform natural language processing on the text string based on the metadata. In response to determining that natural language processing is to be performed on the text string, natural language processing module 732 may further determine whether the metadata identifies one or more fields that correspond to the user request. In response to determining that the metadata identifies one or more domains corresponding to the user request, natural language processing module 732 may use the text string and generate a structured query that represents actionable intents associated with the one or more domains based on the one or more domains. Task flow processing module 736 may execute the task flow associated with the structured query. The task flow processing module 736 may determine whether results satisfying the user request are obtained from executing the task flow. Obtaining from executing a task stream in response to a determination

As another example, receiving operation 902, determining operation 914, performing operation 922, and causing operation 932 are optionally implemented by digital assistant client module 229 and application program 236. The digital assistant client module 229 may receive voice input from the microphone 213 representing a user request. Digital assistant client module 229 may use RF circuitry 208 to transmit voice input and metadata associated with the voice input. The metadata may identify one or more domains of the ontology, and the one or more domains correspond to the user request. The digital assistant client module may use the RF circuitry 208 to receive data content to facilitate satisfying user requests. The data content may be derived from the speech input. The digital assistant client module 229 may determine whether the data content satisfies the user request. In response to determining that the data content satisfies the user request, digital assistant client module 229 and application 236 may output results based on the data content.

Exemplary methods, non-transitory computer-readable storage media, systems, and electronic devices are listed in the following items:

1. a method of identifying an electronic device for performing a task from a plurality of electronic devices, the method comprising:

sampling audio input with a microphone at each of two or more of a plurality of electronic devices;

a first electronic device of the plurality of electronic devices to determine a task associated with the sampled audio input is identified.

Determining, with the first electronic device, a task based on the sampled audio input;

identifying a second electronic device of the plurality of electronic devices for performing the task; and

performing the task with the second electronic device, wherein the second electronic device is not the first electronic device.

2. The method of item 1, further comprising:

after sampling the audio input, providing an output indicating that a task has been determined based on the sampled audio input, wherein the output is provided by an electronic device of the plurality of electronic devices other than the first electronic device.

3. The method of item 2, wherein the output is provided by an electronic device of the plurality of electronic devices other than the first electronic device and the second electronic device.

4. The method of any of items 1-3, wherein sampling the audio input comprises determining whether the audio input comprises a spoken trigger, and wherein the method further comprises:

in accordance with a determination that the audio input includes a spoken trigger,

providing a first output confirming sampling of the audio input; and

after sampling the audio input, providing an output indicating that a task has been determined based on the sampled audio input,

wherein the first output and the second output have different characteristics, an

Wherein the first output is provided by two or more electronic devices.

5. The method of item 4, wherein the spoken trigger comprises a predetermined phrase.

6. The method of any of items 1-5, wherein identifying a first electronic device of the plurality of electronic devices for determining a task associated with the sampled audio input comprises:

respective speech qualities in audio inputs sampled at two or more electronic devices are determined.

7. The method of any of items 1-6, wherein identifying a first electronic device of a plurality of electronic devices for determining a task associated with the sampled audio input comprises:

determining respective sound pressure levels of sampled audio inputs at two or more electronic devices; and

an electronic device having a highest sound pressure level of the two or more electronic devices is identified as the first electronic device.

8. The method of any of items 1-7, wherein identifying a first electronic device of a plurality of electronic devices for determining a task associated with the sampled audio input comprises:

determining whether the two or more electronic devices that are sampling audio input include a wearable electronic device; and

the wearable electronic device is identified as a first electronic device.

9. The method of any of items 1-8, wherein identifying a second electronic device of the plurality of electronic devices for performing the task comprises:

determining a signal strength of a wireless communication between a first electronic device and at least one other electronic device of a plurality of electronic devices; and

the electronic device with the highest signal strength is identified as the second electronic device.

10. The method of any of items 1-9, wherein identifying a second electronic device of the plurality of electronic devices for performing the task comprises:

obtaining an indication of a display screen size of one of a plurality of electronic devices;

determining whether the indication satisfies a requirement of the task;

in accordance with a determination that the indication satisfies a requirement, identifying the electronic device as a second electronic device; and

in accordance with a determination that the indication does not satisfy the requirement, refraining from identifying the electronic device as a second electronic device.

11. The method of any of items 1-10, wherein identifying a second electronic device of the plurality of electronic devices for performing the task comprises:

determining whether an electronic device of a plurality of electronic devices is a mobile electronic device;

in accordance with a determination that the electronic device is a mobile electronic device, identifying the electronic device as a second electronic device; and

in accordance with a determination that the electronic device is not a mobile electronic device, refraining from identifying the electronic device as a second electronic device.

12. The method of any of items 1-11, wherein identifying a second electronic device of the plurality of electronic devices for performing the task comprises:

determining whether an electronic device of a plurality of electronic devices is being powered by a power outlet;

in accordance with a determination that the electronic device is being powered by the power outlet, identifying the electronic device as a second electronic device; and

identifying the electronic device as a second electronic device based on determining that the electronic device is not powered by the power outlet;

13. the method of any of items 1-8, wherein identifying a second electronic device of the plurality of electronic devices for performing the task comprises:

a second electronic device is identified based on the task.

14. The method of any of items 1-13, further comprising:

delaying execution of the task with the second electronic device until the criterion is met; and

an output is provided that indicates criteria for performing the task.

15. The method of any of items 1-14, further comprising:

the user is prompted for input prior to performing the task with the second electronic device, wherein the second electronic device performs the task after receiving the prompt input.

16. The method of item 15, wherein prompting the user for input prior to performing the task with the second electronic device comprises:

a third electronic device of the plurality of electronic devices is identified, the third electronic device having an input interface configured to detect a prompt input.

17. The method of item 16, wherein receiving a prompt input comprises receiving an input within a biometric sensor.

18. A method of identifying an electronic device for performing a task from a plurality of electronic devices, the method comprising:

receiving, at a first electronic device, data indicative of a task, wherein the task is associated with audio input;

determining, with the first electronic device, whether the first electronic device or the second electronic device is to perform the task;

in accordance with a determination that the task is associated with the first electronic device, performing the task with the first electronic device; and

in accordance with a determination that the task is associated with the second electronic device, data indicative of the task is caused to be transmitted to the second electronic device.

19. The method of item 18, wherein causing data indicative of the task to be provided to the second electronic device comprises:

data indicative of the task is provided to a third electronic device.

20. The method of any of items 18 to 19, wherein receiving comprises:

receiving an audio input at a microphone of a first electronic device; and

in response to receiving the audio input, data indicative of the task is generated with the first electronic device based at least in part on the received audio input.

21. The method of any of items 18 to 20, wherein receiving comprises:

receiving an audio input at a microphone of a first electronic device;

transmitting data representing the received audio input to one or more servers; and

data indicative of a task is received from one or more servers, wherein the task is determined by the one or more servers based on the data representative of the received audio input.

22. The method of any of items 18 to 21, wherein determining comprises:

whether the task is associated with the first electronic device or the second electronic device is determined according to a plurality of prioritization rules.

23. The method of item 22, wherein determining whether the task is associated with the first electronic device or the second electronic device according to a plurality of prioritization rules comprises:

determining whether the task is associated with the first electronic device or the second electronic device based on a display capability of the first electronic device, a mobility of the first electronic device, or a combination thereof.

24. The method of item 22, wherein determining whether the task is associated with the first electronic device or the second electronic device according to a plurality of prioritization rules comprises:

determining whether the task is associated with the first electronic device or the second electronic device based on previous usage of the first electronic device and the second electronic device.

25. The method of any of items 18-24, wherein performing the task with the first electronic device includes performing a first task associated with a first user, and wherein the method further comprises:

performing, with the first electronic device, a second task associated with a second user different from the first user.

26. The method of any of items 18 to 25, wherein performing the task with the first electronic device comprises:

authenticating a user associated with a first electronic device; and

in response to authenticating the user, a task is performed.

27. The method of item 26, wherein authenticating the user comprises receiving a biometric input.

28. One or more non-transitory computer-readable storage media storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors, cause the one or more processors to:

sampling audio input with a microphone at each of two or more of a plurality of electronic devices;

a first electronic device of the plurality of electronic devices to determine a task associated with the sampled audio input is identified.

Determining, with the first electronic device, a task based on the sampled audio input;

identifying a second electronic device of the plurality of electronic devices for performing the task; and

the task is performed with a second electronic device, wherein the second electronic device is not the first electronic device.

29. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device, cause the electronic device to:

receiving, at a first electronic device, data indicative of a task, wherein the task is associated with audio input;

determining, with the first electronic device, whether the first electronic device or the second electronic device is to perform the task;

in accordance with a determination that the task is associated with the first electronic device, performing the task with the first electronic device; and

in accordance with a determination that the task is associated with the second electronic device, data indicative of the task is caused to be transmitted to the second electronic device.

30. A system, comprising:

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

Comprising instructions for:

sampling audio input with a microphone at each of two or more of a plurality of electronic devices;

a first electronic device of the plurality of electronic devices to determine a task associated with the sampled audio input is identified.

Determining, with the first electronic device, a task based on the sampled audio input;

identifying a second electronic device of the plurality of electronic devices for performing the task; and

performing the task with the second electronic device, wherein the second electronic device is not the first electronic device.

31. An electronic device, comprising:

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

Comprising instructions for:

receiving, at a first electronic device, data indicative of a task, wherein the task is associated with an audio input;

determining, with the first electronic device, whether the first electronic device or the second electronic device is to perform a task;

in accordance with a determination that the task is associated with the first electronic device, performing the task with the first electronic device; and

in accordance with a determination that the task is associated with the second electronic device, data indicative of the task is caused to be transmitted to the second electronic device.

32. A system, comprising:

means for sampling audio input with a microphone at each of two or more of a plurality of electronic devices;

means for identifying a first electronic device of the plurality of electronic devices for determining a task associated with the sampled audio input.

Means for determining, with the first electronic device, a task based on the sampled audio input;

means for identifying a second electronic device of the plurality of electronic devices for performing the task; and

means for performing the task with the second electronic device, wherein the second electronic device is not the first electronic device.

33. An electronic device, comprising:

means for receiving, at a first electronic device, data indicative of a task, wherein the task is associated with an audio input;

means for determining, with the first electronic device, whether the first electronic device or the second electronic device is to perform a task;

in accordance with a determination that the task is associated with the first electronic device, performing the task with the first electronic device; and

in accordance with a determination that the task is associated with the second electronic device, cause data indicative of the task to be transmitted to the second electronic device.

34. A system, comprising:

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 comprising instructions for performing the method of items 1-17.

35. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors, cause the one or more processors to perform the method of any of items 1-17.

36. A system, comprising:

means for performing the method of any of items 1 to 17.

37. An electronic device, comprising:

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 comprising instructions for performing the method of items 18-27.

38. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device, cause the electronic device to perform the method of any of items 18-27.

39. An electronic device, comprising:

means for performing the method of any of items 18 to 27.

40. An electronic device, comprising:

a processing unit configured to:

receiving, at a first electronic device, data indicative of a task, wherein the task is associated with an audio input;

determining, with the first electronic device, whether the first electronic device or the second electronic device is to perform a task;

in accordance with a determination that the task is associated with the first electronic device, performing the task with the first electronic device; and is

In accordance with a determination that the task is associated with the second electronic device, data indicative of the task is caused to be transmitted to the second electronic device.

41. The electronic device of item 40, wherein causing data indicative of the task to be provided to the second electronic device comprises:

data indicative of the task is provided to a third electronic device.

42. The electronic device of any of items 40-41, wherein receiving comprises:

receiving an audio input at a microphone of a first electronic device; and

in response to receiving the audio input, data indicative of the task is generated with the first electronic device based at least in part on the received audio input.

43. The electronic device of any of items 40-42, wherein receiving comprises:

receiving an audio input at a microphone of a first electronic device;

transmitting data representing the received audio input to one or more servers; and

data indicative of a task is received from one or more servers, wherein the task is determined by the one or more servers based on the data representative of the received audio input.

44. The electronic device of any of items 40-43, wherein determining comprises:

whether the task is associated with the first electronic device or the second electronic device is determined according to a plurality of prioritization rules.

45. The electronic device of item 44, wherein determining whether the task is associated with the first electronic device or the second electronic device according to the plurality of prioritization rules comprises:

determining whether the task is associated with the first electronic device or the second electronic device based on a display capability of the first electronic device, a mobility of the first electronic device, or a combination thereof.

46. The electronic device of item 44, wherein determining whether the task is associated with the first electronic device or the second electronic device according to the plurality of prioritization rules comprises:

determining whether the task is associated with the first electronic device or the second electronic device based on previous usage of the first electronic device and the second electronic device.

47. The electronic device of any of items 40-46, wherein performing the task with the first electronic device includes performing a first task associated with a first user, and wherein the processing unit is further configured to:

performing, with the first electronic device, a second task associated with a second user different from the first user.

48. The electronic device of any of items 40-47, wherein performing the task with the first electronic device comprises:

authenticating a user associated with a first electronic device; and

in response to authenticating the user, a task is performed.

49. The electronic device of item 48, wherein authenticating the user comprises receiving a biometric input.

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 appended claims.