Digital Assistant Hardware Abstraction

Abstract

The present disclosure relates to digital assistant hardware abstractions. The present disclosure relates to intelligent automated assistants, and more particularly, to intelligent context sharing and task execution among a collection of devices with intelligent automated assistant capabilities. An exemplary method includes, at a first electronic device participating in a context sharing group associated with a first location: receiving user voice input; receiving an aggregated context for the context sharing group from a context collector; providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device; receiving a command to perform one or more tasks and a device identifier corresponding to a second electronic device from the remote device; and sending the command to the second electronic device based on the device identifier, wherein the command causes the second electronic device to perform the one or more tasks.

Description

[0001] Division Statement

[0002] This application is a divisional application of the Chinese invention patent application with the application date of September 21, 2020, the invention name of which is “Digital Assistant Hardware Abstraction” and the application number is: 202010998524.X. Technical Field

[0003] The present disclosure relates generally to intelligent automated assistants, and more particularly, to intelligent context sharing and task execution among a collection of devices with intelligent automated assistant capabilities. Background Art

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

[0005] A location such as a home or office may contain multiple devices with digital assistant capabilities. Therefore, it may be desirable for the multiple devices to share contextual information with each other so that the digital assistants of the multiple devices can intelligently coordinate the performance of tasks in response to user requests based on, for example, events that have occurred (and recently occurred) at each device, the user's location relative to each device, and / or what device capabilities are required for the task. In this way, even if the user does not directly provide the user request to the digital assistant of the device, the task requested by the user can be performed at one of the multiple devices. This, in turn, creates the appearance of a single digital assistant interacting with the user across the multiple devices, rather than multiple separate digital assistants at each of the multiple devices.

[0006] Example methods are disclosed herein. One example method includes, at a first electronic device: joining a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device. After joining the context sharing group, selecting one of the at least two electronic devices as a context collector for the context sharing group, wherein selecting the context collector includes: determining a first context collector score corresponding to the first electronic device based at least on the strength of connectivity between the first electronic device and a wireless network at the first location; receiving one or more context collector scores corresponding to at least the second electronic device from at least the second electronic device; and determining which of the electronic devices included in the context sharing group to select as the context collector for the context sharing group based on the first context collector score and the one or more context collector scores corresponding to at least the second electronic device. Based on the determination to select the first electronic device as the context collector, receiving context information from at least the second electronic device in response to at least the second electronic device experiencing a device state change.

[0007] Another exemplary method includes, at a first electronic device participating in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device and a context collector: receiving user voice input; receiving an aggregated context of the context sharing group from the context collector; after receiving the aggregated context, providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device that is not participating in the context sharing group; receiving a command for performing one or more tasks and a device identifier corresponding to the second electronic device from the remote device, wherein the remote device determines the one or more tasks and the device identifier based on the data corresponding to the user voice input and the context information included in the at least a portion of the aggregated context; and sending the command to the second electronic device based on the device identifier, wherein the command causes the second electronic device to perform the one or more tasks.

[0008] Another exemplary method includes, at one or more servers: receiving user voice input and at least a portion of an aggregate context of the context sharing group from a first electronic device participating in a context sharing group associated with a first location, wherein the context sharing group is a collection of multiple electronic devices, each of which shares context information with at least one other electronic device included in the collection; determining a user intent based on the user voice input; determining one or more tasks corresponding to the user intent; identifying a second electronic device among the multiple electronic devices to perform the one or more tasks based on the one or more tasks and context information included in the at least a portion of the aggregate context; and sending a command for performing the one or more tasks and a device identifier corresponding to the second electronic device to the first electronic device, wherein the first electronic device sends the command to the second electronic device based on the device identifier, and wherein the command causes the second electronic device to perform the one or more tasks.

[0009] Another exemplary method includes, at a first electronic device participating in a context sharing group associated with a first location, wherein the context sharing group is a set of multiple electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes a context collector: receiving user voice input; receiving an aggregated context of the context sharing group from the context collector; after receiving the aggregated context, providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device that is not participating in the context sharing group, wherein the remote device determines multiple tasks based on the data corresponding to the user voice input; receiving from the remote device: a first command for performing a first group of tasks among the multiple tasks and a second command for performing a second group of tasks among the multiple tasks; and a first device identifier corresponding to a second electronic device among the multiple electronic devices and a second device identifier corresponding to a third electronic device among the multiple electronic devices; sending the first command to the second electronic device based on the first device identifier, wherein the first command causes the second electronic device to perform the first group of tasks; and sending the second command to the third electronic device based on the second device identifier, wherein the second command causes the third electronic device to perform the second group of tasks.

[0010] Another exemplary method includes, at a system including at least a first electronic device and a second electronic device participating in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes a context collector: receiving a first user voice input at the first electronic device; outputting a first digital assistant response at the first electronic device based on the first user voice input, wherein the first electronic device sends context information including a digital assistant conversation session history of the first electronic device to the context collector after outputting the first digital assistant response; receiving a second user voice input at the second electronic device; receiving an updated aggregate context of the context sharing group at the second electronic device from the context collector, wherein the updated aggregate context includes the digital assistant conversation session history of the first electronic device; and outputting a second digital assistant response at the second electronic device based on the second user voice input and the digital assistant conversation history of the first electronic device.

[0011] Another exemplary method includes, at a first electronic device participating in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device participating in the set, and wherein the set includes at least a second electronic device and a context collector: receiving user voice input, wherein the user voice input includes a digital assistant trigger; in response to detecting the digital assistant trigger, sending a first trigger notification to the context collector, wherein the first trigger notification indicates a first time when the digital assistant trigger ends based on the first electronic device; receiving a second trigger notification from the context collector, wherein the second trigger notification indicates a second time when the digital assistant trigger ends based on the second electronic device; determining whether the second time is within a predetermined time range before the first time; and based on determining that the second time is within the predetermined time range before the first time, forgoing further processing of the user voice input.

[0012] The present invention discloses an example non-transitory computer-readable storage medium. An example non-transitory computer-readable storage medium stores one or more programs. The one or more programs include instructions that, when executed by one or more processors of a first electronic device, cause the first electronic device to: join a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device; after joining the context sharing group, select one of the at least two electronic devices as a context collector for the context sharing group, wherein selecting the context collector includes: determining a first context collector score corresponding to the first electronic device based at least on the strength of connectivity between the first electronic device and a wireless network at the first location; receiving one or more context collector scores corresponding to at least the second electronic device from at least the second electronic device; and determining which of the electronic devices included in the context sharing group to select as the context collector for the context sharing group based on the first context collector score and the one or more context collector scores corresponding to at least the second electronic device; and receiving context information from at least the second electronic device in response to at least the second electronic device experiencing a device state change, based on the determination to select the first electronic device as the context collector.

[0013] Another exemplary non-transitory computer-readable storage medium stores one or more programs, which include instructions that, when executed by one or more processors of a first electronic device, cause the first electronic device to: when the first electronic device participates in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device and a context collector: receive user voice input; receive an aggregated context of the context sharing group from the context collector; after receiving the aggregated context, provide at least a portion of the aggregated context and data corresponding to the user voice input to a remote device that is not participating in the context sharing group; receive a command for performing one or more tasks and a device identifier corresponding to the second electronic device from the remote device, wherein the remote device determines the one or more tasks and the device identifier based on the data corresponding to the user voice input and the context information included in the at least a portion of the aggregated context; and send the command to the second electronic device based on the device identifier, wherein the command causes the second electronic device to perform the one or more tasks.

[0014] Another exemplary non-transitory computer-readable storage medium stores one or more programs, which include instructions that, when executed by one or more processors of one or more servers, cause the one or more servers to: receive user voice input and at least a portion of an aggregated context of the context sharing group from a first electronic device participating in a context sharing group associated with a first location, wherein the context sharing group is a collection of multiple electronic devices, each of which shares context information with at least one other electronic device included in the collection; determine a user intent based on the user voice input; determine one or more tasks corresponding to the user intent; identify a second electronic device among the multiple electronic devices to perform the one or more tasks based on the one or more tasks and the context information included in the at least a portion of the aggregated context; and send a command for performing the one or more tasks and a device identifier corresponding to the second electronic device to the first electronic device, wherein the first electronic device sends the command to the second electronic device based on the device identifier, and wherein the command causes the second electronic device to perform the one or more tasks.

[0015] Another exemplary non-transitory computer-readable storage medium stores one or more programs, the one or more programs including instructions that, when executed by one or more processors of a first electronic device, cause the first electronic device to: when the first electronic device participates in a context sharing group associated with a first location, wherein the context sharing group is a collection of multiple electronic devices, each of the electronic devices shares context information with at least one other electronic device included in the collection, and wherein the collection includes a context collector: receive user voice input; receive an aggregated context of the context sharing group from the context collector; and after receiving the aggregated context, provide at least a portion of the aggregated context and a context corresponding to the user voice input to a remote device that does not participate in the context sharing group. corresponding data, wherein the remote device determines a plurality of tasks based on the data corresponding to the user voice input; receives from the remote device: a first command for performing a first group of tasks among the plurality of tasks and a second command for performing a second group of tasks among the plurality of tasks; and a first device identifier corresponding to a second electronic device among the plurality of electronic devices and a second device identifier corresponding to a third electronic device among the plurality of electronic devices; sends the first command to the second electronic device based on the first device identifier, wherein the first command causes the second electronic device to perform the first group of tasks; and sends the second command to the third electronic device based on the second device identifier, wherein the second command causes the third electronic device to perform the second group of tasks.

[0016] A non-transitory computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by one or more processors of a first electronic device, cause the first electronic device to: when the first electronic device and a second electronic device participate in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes a context collector: receive a first user voice input at the first electronic device; output a first digital assistant response at the first electronic device based on the first user voice input, wherein the first electronic device sends context information including a digital assistant conversation session history of the first electronic device to the context collector after outputting the first digital assistant response; receive a second user voice input at the second electronic device; receive an updated aggregated context of the context sharing group from the context collector at the second electronic device, wherein the updated aggregated context includes the digital assistant conversation session history of the first electronic device; and output a second digital assistant response at the second electronic device based on the second user voice input and the digital assistant conversation history of the first electronic device.

[0017] A non-transitory computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by one or more processors of a first electronic device, cause the first electronic device to: when the first electronic device participates in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device participating in the set, and wherein the set includes at least a second electronic device and a context collector: receive user voice input, wherein the user voice input includes a digital assistant trigger; in response to detecting the digital assistant trigger, send a first trigger notification to the context collector, wherein the first trigger notification indicates that the digital assistant trigger is based on a first time when the first electronic device ends; receive a second trigger notification from the context collector, wherein the second trigger notification indicates that the digital assistant trigger is based on a second time when the second electronic device ends; determine whether the second time is within a predetermined time range before the first time; and based on determining that the second time is within the predetermined time range before the first time, abandon further processing of the user voice input.

[0018] Disclosed herein are exemplary electronic devices and systems. An exemplary first electronic device includes one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: joining a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device. After joining the context sharing group, selecting one of the at least two electronic devices as a context collector for the context sharing group, wherein selecting the context collector includes: determining a first context collector score corresponding to the first electronic device based at least on the strength of connectivity between the first electronic device and a wireless network at the first location; receiving one or more context collector scores corresponding to at least the second electronic device from at least the second electronic device; and determining which of the electronic devices included in the context sharing group to select as the context collector for the context sharing group based on the first context collector score and the one or more context collector scores corresponding to at least the second electronic device. Based on the determination to select the first electronic device as the context collector, context information is received from at least the second electronic device in response to at least the second electronic device experiencing a device state change.

[0019] Another exemplary first electronic device includes one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: when the first electronic device participates in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device and a context collector: receiving user voice input; receiving an aggregated context of the context sharing group from the context collector; after receiving the aggregated context, providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device that is not participating in the context sharing group; receiving a command for performing one or more tasks and a device identifier corresponding to the second electronic device from the remote device, wherein the remote device determines the one or more tasks and the device identifier based on the data corresponding to the user voice input and the context information included in the at least a portion of the aggregated context; and sending the command to the second electronic device based on the device identifier, wherein the command causes the second electronic device to perform the one or more tasks.

[0020] An exemplary system includes one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: receiving user voice input and at least a portion of an aggregate context of the context sharing group from a first electronic device participating in a context sharing group associated with a first location, wherein the context sharing group is a collection of multiple electronic devices, each of which shares context information with at least one other electronic device included in the collection; determining a user intent based on the user voice input; determining one or more tasks corresponding to the user intent; identifying a second electronic device among the multiple electronic devices to perform the one or more tasks based on the one or more tasks and the context information included in the at least a portion of the aggregate context; and sending a command for performing the one or more tasks and a device identifier corresponding to the second electronic device to the first electronic device, wherein the first electronic device sends the command to the second electronic device based on the device identifier, and wherein the command causes the second electronic device to perform the one or more tasks.

[0021] Another exemplary first electronic device includes one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs include instructions for the following operations: when the first electronic device participates in a context sharing group associated with a first location, wherein the context sharing group is a collection of multiple electronic devices, each of the electronic devices shares context information with at least one other electronic device included in the collection, and wherein the collection includes a context collector: receiving user voice input; receiving an aggregated context of the context sharing group from the context collector; after receiving the aggregated context, providing at least a portion of the aggregated context and Data corresponding to the user voice input, wherein the remote device determines multiple tasks based on the data corresponding to the user voice input; receiving from the remote device: a first command for performing a first group of tasks among the multiple tasks and a second command for performing a second group of tasks among the multiple tasks; and a first device identifier corresponding to a second electronic device among the multiple electronic devices and a second device identifier corresponding to a third electronic device among the multiple electronic devices; sending the first command to the second electronic device based on the first device identifier, wherein the first command causes the second electronic device to perform the first group of tasks; and sending the second command to the third electronic device based on the second device identifier, wherein the second command causes the third electronic device to perform the second group of tasks.

[0022] Another exemplary system includes one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: when a first electronic device and a second electronic device participate in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of the electronic devices shares context information with at least one other electronic device included in the set, and wherein the set includes a context collector: receiving a first user voice input at the first electronic device; outputting a first digital assistant response at the first electronic device based on the first user voice input, wherein the first electronic device sends context information including a digital assistant conversation session history of the first electronic device to the context collector after outputting the first digital assistant response; receiving a second user voice input at the second electronic device; receiving an updated aggregated context of the context sharing group at the second electronic device from the context collector, wherein the updated aggregated context includes the digital assistant conversation session history of the first electronic device; and outputting a second digital assistant response at the second electronic device based on the second user voice input and the digital assistant conversation history of the first electronic device.

[0023] Another exemplary first electronic device includes one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: when the first electronic device participates in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of the electronic devices shares context information with at least one other electronic device participating in the set, and wherein the set includes at least a second electronic device and a context collector: receiving user voice input, wherein the user voice input includes a digital assistant trigger; in response to detecting the digital assistant trigger, sending a first trigger notification to the context collector, wherein the first trigger notification indicates that the digital assistant trigger is based on a first time when the first electronic device ends; receiving a second trigger notification from the context collector, wherein the second trigger notification indicates that the digital assistant trigger is based on a second time when the second electronic device ends; determining whether the second time is within a predetermined time range before the first time; and based on determining that the second time is within the predetermined time range before the first time, abandoning further processing of the user voice input.

[0024] An exemplary first electronic device includes means for joining a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device. After joining the context sharing group, means for selecting one of the at least two electronic devices as a context collector for the context sharing group, wherein selecting the context collector comprises: determining a first context collector score corresponding to the first electronic device based at least on the strength of connectivity between the first electronic device and a wireless network at the first location; receiving one or more context collector scores corresponding to at least the second electronic device from at least the second electronic device; and determining which of the electronic devices included in the context sharing group to select as the context collector for the context sharing group based on the first context collector score and the one or more context collector scores corresponding to at least the second electronic device. In response to at least the second electronic device experiencing a device state change, means for receiving context information from at least the second electronic device based on the determination to select the first electronic device as the context collector.

[0025] Another exemplary first electronic device includes a device for the following operations: when the first electronic device participates in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device and a context collector: receiving user voice input; a device for receiving an aggregated context of the context sharing group from the context collector; after receiving the aggregated context, a device for providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device that does not participate in the context sharing group; a device for receiving a command for performing one or more tasks and a device identifier corresponding to the second electronic device from the remote device, wherein the remote device determines the one or more tasks and the device identifier based on the data corresponding to the user voice input and the context information included in the at least a portion of the aggregated context; and a device for sending the command to the second electronic device based on the device identifier, wherein the command causes the second electronic device to perform the one or more tasks.

[0026] Another exemplary system includes a device for performing the following operations: a device for receiving user voice input and at least a portion of an aggregate context of the context sharing group from a first electronic device participating in a context sharing group, the context sharing group being associated with a first location, wherein the context sharing group is a set of multiple electronic devices, each of which shares context information with at least one other electronic device included in the set; a device for determining a user intent based on the user voice input; a device for determining one or more tasks corresponding to the user intent; a device for identifying a second electronic device among the multiple electronic devices to perform the one or more tasks based on the one or more tasks and the context information included in the at least a portion of the aggregate context; and a device for sending a command for performing the one or more tasks and a device identifier corresponding to the second electronic device to the first electronic device, wherein the first electronic device sends the command to the second electronic device based on the device identifier, and wherein the command causes the second electronic device to perform the one or more tasks.

[0027] Another exemplary first electronic device includes a device for the following operations: when the first electronic device participates in a context sharing group associated with a first location, wherein the context sharing group is a set of multiple electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes a context collector: receiving user voice input; a device for receiving an aggregated context of the context sharing group from the context collector; after receiving the aggregated context, a device for providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device that does not participate in the context sharing group, wherein the remote device determines multiple tasks based on the data corresponding to the user voice input; a device for receiving the following from the remote device: a first command for performing a first group of tasks in the multiple tasks and a second command for performing a second group of tasks in the multiple tasks; and a first device identifier corresponding to a second electronic device in the multiple electronic devices and a second device identifier corresponding to a third electronic device in the multiple electronic devices; a device for sending the first command to the second electronic device based on the first device identifier, wherein the first command causes the second electronic device to perform the first group of tasks; and a device for sending the second command to the third electronic device based on the second device identifier, wherein the second command causes the third electronic device to perform the second group of tasks.

[0028] Another exemplary system includes an apparatus for the following operations: when a first electronic device and a second electronic device participate in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device included in the set, and wherein the set includes a context collector: receiving a first user voice input at the first electronic device; an apparatus for outputting a first digital assistant response based on the first user voice input at the first electronic device, wherein the first electronic device sends context information including a digital assistant conversation session history of the first electronic device to the context collector after outputting the first digital assistant response; an apparatus for receiving a second user voice input at the second electronic device; an apparatus for receiving an updated aggregate context of the context sharing group from the context collector at the second electronic device, wherein the updated aggregate context includes the digital assistant conversation session history of the first electronic device; and an apparatus for outputting a second digital assistant response based on the second user voice input and the digital assistant conversation history of the first electronic device at the second electronic device.

[0029] Another exemplary first electronic device includes a device for the following operations: when the first electronic device participates in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of which shares context information with at least one other electronic device participating in the set, and wherein the set includes at least a second electronic device and a context collector: receiving user voice input, wherein the user voice input includes a digital assistant trigger; in response to detecting the digital assistant trigger, sending a first trigger notification to the context collector, wherein the first trigger notification indicates that the digital assistant trigger is based on a first time when the first electronic device ends; receiving a second trigger notification from the context collector, wherein the second trigger notification indicates that the digital assistant trigger is based on a second time when the second electronic device ends; determining whether the second time is within a predetermined time range before the first time; and based on determining that the second time is within the predetermined time range before the first time, abandoning further processing of the user voice input.

[0030] In some examples, determining a first context collector score for a first electronic device based at least on the strength of connectivity between the first electronic device and a wireless network at a first location, and subsequently determining which of the electronic devices included in a context sharing group to select as the context collector for the context sharing group based on the first context collector score and one or more context collector scores corresponding to at least a second electronic device, can improve a user's digital assistant experience. Specifically, determining the first context collector score based at least on the strength of connectivity between the first electronic device and the wireless network at the first location helps ensure that an electronic device with a strong connection to the wireless network is selected as the context collector, as the context collector selection is based on the determined context collector score. This, in turn, improves the stability of the context collector, as the context collector is less likely to lose its connection to the wireless network and leave the context sharing group. This allows the collector to consistently receive and transmit context information to the electronic devices participating in the context sharing group, allowing the electronic device's digital assistant to respond to user requests based on the context information provided to and received from the context collector.

[0031] In some examples, providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device that is not participating in the context sharing group allows the remote device to determine one or more tasks and device identifiers based on the data corresponding to the user voice input and the context information included in at least a portion of the aggregated context, thereby improving the user's digital assistant experience. Specifically, by performing the above operations, the remote device is able to, for example, more accurately determine the user intent corresponding to the user voice input because the context information included in the aggregated context informs the remote device of the user's context when the user voice input is provided relative to all devices participating in the context sharing group rather than only the first electronic device that receives the user voice input. This in turn allows the remote device to determine the best electronic device for responding to the user based on the one or more tasks corresponding to the determined user intent and the context information included in the aggregated context. Therefore, even if the first electronic device receives the user voice input, the first electronic device can send one or more tasks to another electronic device that is more suitable for performing the one or more tasks (e.g., located closer to the user, with better device capabilities for performing the one or more tasks, etc.) based on the device identifier provided by the remote device. Thus, the first electronic device provides an aggregated context to the remote device, and the first electronic device sends one or more tasks to the second electronic device based on the received device identifier, allowing the digital assistants of the electronic devices participating in the context sharing group to intelligently coordinate the execution of tasks with each other, which creates the appearance of a single digital assistant interacting with the user across multiple devices, rather than multiple separate digital assistants at each of the multiple devices.

[0032] In some examples, identifying a second electronic device from among multiple electronic devices participating in a context sharing group to perform the one or more tasks based on one or more tasks and context information included in at least a portion of the aggregated context of the context sharing group can improve the user's digital assistant experience. Specifically, as described above, the electronic device that receives the user's digital assistant request may not be the optimal device for performing the requested task. For example, the electronic device that receives the user's request may not be the optimal device because it may have a small display (or no display at all), the request may relate to an event occurring at another electronic device (e.g., an alarm, a timer, media playback, etc.), and / or there may be another electronic device that is more conveniently located relative to the user. Therefore, because the aggregated context includes contextual information indicating, for example, device capabilities, device location, and current and / or previous device activity and user interactions (associated with multiple devices participating in the context sharing group), a remote device (e.g., one or more servers) can identify a second, more appropriate electronic device for performing the one or more tasks based on the context information, rather than simply indicating the electronic device that received the user's request to perform the one or more tasks. This, in turn, improves the user's digital assistant experience because it creates the appearance of a single digital assistant that intelligently interacts with the user across multiple devices to provide the best response to the user's request.

[0033] Sending a first command for performing a first set of tasks in a plurality of tasks to a second electronic device and sending a second command for performing a second set of tasks in a plurality of tasks to a third electronic device can improve the user's digital assistant experience. Specifically, when a user's digital assistant request requires the performance of multiple tasks (such as, for example, the output of a digital assistant response and the display of corresponding data / information), assigning the execution of certain tasks to different devices helps ensure that those tasks are being performed by the best device. For example, while the second electronic device may have suitable audio capabilities for providing a digital assistant response, it may have a small display (or no display at all). Therefore, instead of displaying data / information on a small display (or no display at all), the second electronic device can be instructed via a first command to provide an audio digital assistant response, while a third electronic device (e.g., having a larger display than the second electronic device) can be instructed to display the corresponding data / information. This, in turn, improves the user's digital assistant experience because it creates the appearance of a single digital assistant that intelligently interacts with the user across multiple devices in order to provide the best response to the user's request.

[0034] In some examples, outputting a second digital assistant response at a second electronic device based on the second user voice input and the digital assistant conversation history of the first electronic device can improve the user's digital assistant experience. Specifically, using the digital assistant conversation history of the first electronic device to determine the second digital assistant response allows the digital assistant of the second electronic device to provide a digital assistant response that is based on and / or facilitates the first user input, even if the first user input is provided to the first electronic device rather than the second electronic device. In this way, the user of the second electronic device can provide a digital assistant request in a more natural and conversational manner (e.g., provided in the second user input), and if certain aspects of the request have already been introduced in the first user input, those aspects do not have to be repeated. For example, if the first user voice input includes a user request "Hey, Siri, what's the weather in Palo Alto?", the user of the second electronic device can then request weather information about New York by providing a second user voice input "Hey, Siri, what's the weather in New York?" instead of having to repeat that weather information is desired (e.g., "Hey, Siri, what's the weather in New York?"). This, in turn, improves the user's digital assistant experience because it creates the appearance of a single digital assistant interacting with the user across multiple devices, rather than multiple separate digital assistants at each of the multiple devices.

[0035] In some examples, determining whether a digital assistant trigger included in a user voice input is within a predetermined time range before a first time when the digital assistant trigger ends according to a first electronic device based on a second time ended by a second electronic device, and abandoning further processing of the user voice input based on determining that the second time is within the predetermined time range before the first time, can improve the user's digital assistant experience. Specifically, if the digital assistant trigger detection of an electronic device is delayed, the electronic device will begin processing the user voice input even if another nearby electronic device (which does not have delayed digital assistant trigger detection) has already begun processing the user voice input and / or has already provided a response to the user voice input. This, in turn, can result in multiple devices providing responses to the same user voice input at different times, which can result in a poor digital assistant experience for the user (e.g., due to user confusion and / or annoyance). Therefore, abandoning further processing of the user voice input when the electronic device determines that another electronic device has detected the digital assistant trigger (within a predetermined time range) will ensure that multiple devices do not provide responses to the same user voice input at different times, which in turn will improve the user's digital assistant experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 A block diagram illustrating systems and environments for implementing a digital assistant according to various examples.

[0037] Figure 2AA block diagram of a portable multifunction device that implements the client-side portion of a digital assistant according to various examples is shown.

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

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

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

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

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

[0043] Figure 6A A personal electronic device according to various examples is shown.

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

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

[0046] Figure 7B Shown in accordance with various examples Figure 7A The capabilities of the digital assistant shown in .

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

[0048] Figure 8 Systems and techniques for selecting a context collector for a context sharing group according to various examples are presented.

[0049] Figure 9 Systems and techniques for performing one or more tasks in a context-sharing group according to various examples are shown.

[0050] Figure 10 Systems and techniques are shown for suppressing delayed digital assistant trigger detection using context collectors of context sharing groups according to various examples.

[0051] Figure 11is a block diagram illustrating a system for task determination and device selection in a context sharing group according to various examples.

[0052] FIG. 12A to FIG. 12B Systems and techniques for multimodal task performance in context-sharing groups according to various examples are presented.

[0053] Figure 13 Systems and techniques for conducting a persistent digital assistant session across multiple devices participating in a context sharing group according to various examples are shown.

[0054] 14A to 14C A flowchart representing a process for a context collector to select a context sharing group is shown, according to various examples.

[0055] FIG. 15A to FIG. 15B Flowcharts representing processes for performing one or more tasks in a context-sharing group are shown, according to various examples.

[0056] 16A to 16E A flow diagram representing a process for identifying electronic devices participating in a context sharing group to perform one or more tasks is shown, according to various examples.

[0057] 17A to 17C A flowchart representing a process for multimodal task performance in a context-sharing group is shown, according to various examples.

[0058] 18A to 18B A flowchart representing a process for persisting a digital assistant session across multiple electronic devices participating in a context sharing group is shown according to various examples.

[0059] Figures 19A to 19B A flowchart representing a process for suppressing delayed digital assistant trigger detection using a context collector of a context sharing group according to various examples is shown. DETAILED DESCRIPTION

[0060] In the following description of the examples, reference is made to the accompanying drawings, which show, by way of illustration, specific examples that may be implemented. It should be understood that other examples may be used and structural changes may be made without departing from the scope of the various examples.

[0061] 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 simply used to distinguish one element from another. For example, without departing from the scope of the various described examples, a first input may be referred to as a second input, and similarly, a second input may be referred to as a first input. Both the first input and the second input are inputs, and in some cases, are independent and distinct inputs.

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

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

[0064] 1. System and Environment

[0065] Figure 1 A block diagram of a system 100 according to various examples is shown. In some examples, the system 100 implements a digital assistant. The terms "digital assistant," "virtual assistant," "intelligent automated assistant," or "automated digital assistant" refer to any information processing system that interprets natural language input in spoken and / or textual form to infer user intent and performs actions based on the inferred user intent. For example, to act on an inferred user intent, the system performs one or more of the following steps: identifying a task flow having steps and parameters designed to implement the inferred user intent, inputting specific requirements into the task flow based on the inferred user intent; executing the task flow by calling a program, method, service, API, etc.; and generating an output response to the user in an audible (e.g., voice) and / or visual form.

[0066] Specifically, digital assistants are capable of accepting user requests that are at least partially in the form of natural language commands, requests, statements, narrations, and / or inquiries. Typically, user requests seek an informational answer from the digital assistant or the performance of a task. A satisfactory response to a user request includes providing the requested informational answer, performing the requested task, or a combination of the two. For example, a user asks the digital assistant a question such as, "Where am I now?" Based on the user's current location, the digital assistant responds, "You are near the West Gate of Central Park." The user also requests a task, such as, "Please invite my friends to my girlfriend's birthday party next week." In response, the digital assistant may acknowledge the request by saying, "Okay, right away," and then send appropriate calendar invitations on behalf of the user to each of the user's friends listed in the user's electronic address book. While performing the requested task, the digital assistant sometimes interacts with the user in a continuous conversation involving multiple information exchanges over an extended period of time. There are many other ways to interact with a digital assistant to request information or perform various tasks. In addition to providing verbal responses and taking programmed actions, digital assistants also provide responses in other visual or audio forms, such as text, alerts, music, videos, animations, and the like.

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

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

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

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

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

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

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

[0074] Although Figure 1 The digital assistant shown in includes both a client-side portion (e.g., DA client 102) and a server-side portion (e.g., DA server 106), but in some examples, the functionality of the digital assistant is implemented as a stand-alone application installed on a user device. Furthermore, the division of functionality between the client and server portions of the digital assistant can vary in different implementations. For example, in some examples, the DA client is a thin client that provides only user-facing input and output processing functionality and delegates all other functionality of the digital assistant to a backend server.

[0075] 2. Electronic devices

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

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

[0078] As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of a device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device that will be detected by a user using the user's sense of touch. For example, when a device or a component of the device is in contact with a surface that is touch-sensitive to a user (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation that corresponds to a perceived change in a physical characteristic of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "release click" on 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 was physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when the smoothness of the touch-sensitive surface does not change, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. While such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user.

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

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

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

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

[0083] RF (radio frequency) circuitry 208 receives and transmits RF signals, also known as electromagnetic signals. RF circuitry 208 converts electrical signals into / from electromagnetic signals and communicates with communication networks and other communication devices via the electromagnetic signals. RF circuitry 208 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a subscriber identity module (SIM) card, memory, and the like. RF circuitry 208 optionally communicates with networks and other devices via wireless communications, such as the Internet (also known as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuitry 208 optionally includes well-known circuitry for detecting near-field communication (NFC) fields, such as via a short-range communication radio. Wireless communication optionally uses any of a variety of communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolution, Data Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g, IEEE 802.11g, IEEE 802.11g, IEEE 802.11b, IEEE 802.11f, IEEE 802.11g ...g, IEEE 802.11g, IEEE 802.11g, 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 for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols that have not yet been developed as of the filing date of this document.

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

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

[0086] A quick press of the push button releases the lock on the touch screen 212 or initiates the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image," which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 306) turns the device 200 on or off. The user can customize the function of one or more buttons. The touch screen 212 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

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

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

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

[0090] In some embodiments, the touch-sensitive display of the touch screen 212 is similar to the multi-touch-sensitive trackpads described in U.S. Patents 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman), and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, the touch screen 212 displays visual output from the device 200, whereas a touch-sensitive trackpad does not provide visual output.

[0091] In some embodiments, the touch-sensitive display of the touch screen 212 is as described in the following applications: (1) U.S. patent application 11 / 381,313, entitled “Multipoint Touch Surface Controller,” filed on May 2, 2006; (2) U.S. patent application No. 10 / 840,862, entitled “Multipoint Touchscreen,” filed on May 6, 2004; (3) U.S. patent application No. 10 / 903,964, entitled “Gestures For Touch Sensitive Input Devices,” filed on July 30, 2004; (4) U.S. patent application No. 11 / 048,264, entitled “Gestures For Touch Sensitive Input Devices,” filed on January 31, 2005; (5) U.S. patent application No. 11 / 050,264, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed on January 18, 2005 Devices”; (6) U.S. Patent Application No. 11 / 228,758, filed on September 16, 2005, entitled “Virtual Input Device Placement On A Touch Screen User Interface”; (7) U.S. Patent Application No. 11 / 228,700, filed on September 16, 2005, entitled “Operation Of A Computer With A Touch Screen Interface”; (8) U.S. Patent Application No. 11 / 228,737, filed on September 16, 2005, entitled “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”; and (9) U.S. Patent Application No. 11 / 367,749, filed on March 3, 2006, entitled “Multi-Functional Hand-Held Device”. All of these applications are incorporated herein by reference in their entirety.

[0092] The touch screen 212 has, for example, a video resolution exceeding 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user makes contact with the touch screen 212 using any suitable object or appendage, such as a stylus, a finger, or the like. In some embodiments, the user interface is designed to operate primarily through finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of a finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the user's desired action.

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

[0094] Device 200 also includes a power system 262 for powering the various components. Power system 262 includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power fault detection circuitry, 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.

[0095] Device 200 also includes one or more optical sensors 264 . Figure 2A An optical sensor coupled to the optical sensor controller 258 in the I / O subsystem 206 is shown. The optical sensor 264 includes a charge-coupled device (CCD) or complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 264 receives light projected from the environment through one or more lenses and converts the light into data representing an image. In conjunction with the imaging module 243 (also called a camera module), the optical sensor 264 captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 200, facing away from the touch screen display 212 on the front of the device, so that the touch screen display can be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that the user's image can be captured for video conferencing while viewing other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 264 can be changed by the user (for example, by rotating the lens and sensor in the device housing), so that a single optical sensor 264 can be used with the touch screen display for both video conferencing and still image and / or video image acquisition.

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

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

[0098] Device 200 optionally also includes one or more tactile output generators 267 . Figure 2AA tactile output generator is shown coupled to a tactile feedback controller 261 in the I / O subsystem 206. The tactile output generator 267 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components for converting electrical signals into tactile outputs on the device). The contact force sensor 265 receives tactile feedback generation instructions from the tactile feedback module 233 and generates tactile outputs on the device 200 that can be felt by a user of the device 200. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 212) and optionally generates tactile outputs by moving the touch-sensitive surface vertically (e.g., inward / outward toward the surface of the device 200) or laterally (e.g., back and forth in the same plane as the surface of the device 200). In some embodiments, at least one tactile output generator sensor is located on the back of the device 200, opposite the touch screen display 212 located on the front of the device 200.

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

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

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

[0102] The communication module 228 facilitates communication with other devices via one or more external ports 224 and also includes various software components for processing data received by the RF circuit 208 and / or the external ports 224. The external ports 224 (e.g., Universal Serial Bus (USB), FireWire, etc.) are suitable for coupling directly to other devices or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external ports are connected to (trademark of Apple Inc.) devices.

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

[0104] In some embodiments, the contact / motion module 230 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 200). For example, a mouse "click" threshold for a touchpad or touchscreen can be set to any one of a large range of predefined thresholds without changing the touchpad or touchscreen display hardware. In addition, in some embodiments, a software setting is provided to the user of the device for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).

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

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

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

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

[0109] Text input module 234 , which in some examples is part of graphics module 232 , provides a soft keyboard for entering text in various applications (eg, contacts 237 , email 240 , IM 241 , browser 247 , and any other application requiring text input).

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

[0111] The digital assistant client module 229 includes various client-side digital assistant instructions to provide client-side functionality of the digital assistant. For example, the digital assistant client module 229 is capable of accepting voice input (e.g., speech input), text input, touch input, and / or gesture input through various user interfaces of the portable multifunction device 200 (e.g., microphone 213, one or more accelerometers 268, touch-sensitive display system 212, one or more optical sensors 264, other input control devices 216, etc.). The digital assistant client module 229 is also capable of providing output in the form of audio (e.g., speech output), visual output, and / or tactile output through various output interfaces of the portable multifunction device 200 (e.g., speaker 211, touch-sensitive display system 212, one or more tactile output generators 267, etc.). For example, the output is provided as speech, sound, alarm, text message, menu, graphic, video, animation, vibration, and / or a combination of two or more of the above. During operation, the digital assistant client module 229 communicates with the DA server 106 using the RF circuit 208.

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

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

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

[0115] In some examples, the digital assistant client module 229 selectively provides information stored on the portable multifunction device 200 (e.g., user data 231) in response to a request from the DA server 106. In some examples, the digital assistant client module 229 also elicits additional input from the user via a natural language dialog or other user interface upon request by the DA server 106. The digital assistant client module 229 transmits the additional input to the DA server 106 to assist the DA server 106 in inferring intent and / or fulfilling the user intent expressed in the user request.

[0116] Reference below 7A to 7C A more detailed description of the digital assistant is provided. It should be appreciated that the digital assistant client module 229 may include any number of submodules of the digital assistant module 726 described below.

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

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

[0119] Telephone module 238;

[0120] Video conferencing module 239;

[0121] Email client module 240;

[0122] Instant messaging (IM) module 241;

[0123] Fitness support module 242;

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

[0125] Image management module 244;

[0126] Video player module;

[0127] Music player module;

[0128] Browser module 247;

[0129] Calendar module 248;

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

[0131] A widget creator module 250 for forming user-created widgets 249-6;

[0132] Search module 251;

[0133] Video and music player module 252, which combines the video player module and the music player module;

[0134] Notepad module 253;

[0135] Map module 254; and / or

[0136] Online video module 255.

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

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

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

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

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

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

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

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

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

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

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

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

[0149] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the touch / motion module 230, the graphics module 232, the text input module 234 and the browser module 247, the desktop widget creator module 250 is used by users to create desktop widgets (for example, to turn a user-specified portion of a web page into a desktop widget).

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

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

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

[0153] In combination with the RF circuit 208, the touch screen 212, the display controller 256, the touch / motion module 230, the graphics module 232, the text input module 234, the GPS module 235 and the browser module 247, the map module 254 is used to receive, display, modify and store maps and data associated with the maps (e.g., driving directions, data related to stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

[0154] In conjunction with the touch screen 212, display controller 256, contact / motion module 230, graphics module 232, audio circuit 210, speaker 211, RF circuit 208, text input module 234, email client module 240, and browser module 247, the online video module 255 includes instructions that allow a user to access, browse, receive (e.g., by streaming and / or downloading), play back (e.g., on the touch screen or on a connected external display via external port 224), send an email with a link to a particular online video, and otherwise manage online videos in one or more file formats (e.g., H.264). In some embodiments, the instant messaging module 241 is used instead of the email client module 240 to send a link to a particular online video. Additional descriptions of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.

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

[0156] In some embodiments, the device 200 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 touch pad. By using the touch screen and / or the touch pad as the primary input control device for the operation of the device 200, the number of physical input control devices (such as push buttons, dials, etc.) on the device 200 is reduced.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0172] The event receiver 282 receives event information from the event classifier 270. The event information includes information about sub-events such as touches or touch movements. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of a touch, the event information also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (for example, from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

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

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

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

[0176] When a corresponding event recognizer 280 determines that a sub-event sequence does not match any event in event definitions 286, the corresponding event recognizer 280 enters the 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 ongoing touch-based gesture.

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

[0178] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 280 activates the event handler 290 associated with the event. In some embodiments, the corresponding event recognizer 280 delivers event information associated with the event to the event handler 290. Activating the event handler 290 is different from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 280 throws a flag associated with the identified event, and the event handler 290 associated with the flag obtains the flag and performs a predefined process.

[0179] In some embodiments, event delivery instructions 288 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and performs a predetermined process.

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

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

[0182] It should be understood that the above discussion of event handling for user touches on a touch-sensitive display also applies to other forms of user input utilizing input devices to operate the multifunction device 200, and not all user input is initiated on a touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holddowns; contact movement on a trackpad, such as taps, drags, scrolls, etc.; stylus input; movement of the device; spoken commands; detected eye movement; biometric input; and / or any combination thereof, are optionally used as input corresponding to sub-events defining the event to be recognized.

[0183] Figure 3A portable multifunction device 200 with a touch screen 212 is shown according to some embodiments. The touch screen optionally displays one or more graphics within a user interface (UI) 300. In this embodiment and other embodiments described below, a user can select one or more of the graphics by, for example, making gestures on the graphics using one or more fingers 302 (not drawn to scale in the figure) or one or more styluses 303 (not drawn to scale in the figure). In some embodiments, selection of the one or more graphics occurs 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 (from left to right, from right to left, up and / or down), and / or rolling of the finger that has made contact with the device 200 (from right to left, from left to right, up and / or down). In some embodiments or in some cases, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

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

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

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

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

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

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

[0191] Time 504;

[0192] Bluetooth indicator 505;

[0193] Battery status indicator 506;

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

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

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

[0197] o An icon 520 labeled "Browser" of the browser module 247; and

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

[0199] Icons for other applications, such as:

[0200] o Icon 524 labeled “Messages” of the IM module 241;

[0201] o Icon 526 labeled “Calendar” of the calendar module 248;

[0202] o Icon 528 labeled “Photos” of the image management module 244;

[0203] o Icon 530 labeled “Camera” of camera module 243;

[0204] o Icon 532 labeled “Online Video” of the online video module 255;

[0205] o Icon 534 labeled "Stock Market" of the Stock Market widget 249-2;

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

[0207] o Icon 538 labeled "Weather" of the Weather widget 249-1;

[0208] o Icon 540 labeled “Clock” of the Alarm Clock widget 249-4;

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

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

[0211] o An icon 546 labeled “Settings” for a settings application or module that provides access to settings for the device 200 and its various applications 236.

[0212] It should be pointed out that Figure 5A The icon labels shown in are exemplary only. For example, icon 522 for video and music player module 252 is optionally labeled "Music" or "Music Player." Other labels are optionally used for various application icons. In some embodiments, the label of a respective application icon includes the 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.

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

[0214] Although some of the examples that follow will be given with reference to input on a touch screen display 212 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 5B In some embodiments, the touch-sensitive surface (e.g., Figure 5B 551) has a main axis (e.g., Figure 5B 553) corresponding to the main axis (for example, Figure 5B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 5B , 560 corresponds to 568 and 562 corresponds to 570 ) at contact with touch-sensitive surface 551 (e.g., Figure 5B 560 and 562 in ). Thus, on a touch-sensitive surface (e.g., Figure 5B 551) and a display of a multi-function device (e.g., Figure 5B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 560 and 562 and their movement) is separated, the device is used to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0215] In addition, although the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap gestures, finger swipe gestures), it should be understood that in some embodiments, one or more of these finger inputs are replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of contact), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). For another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detecting the contact, followed by ceasing to detect the contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or mice and finger contacts are optionally used simultaneously.

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

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

[0218] In some embodiments, the device 600 has one or more input mechanisms 606 and 608. Input mechanisms 606 and 608 (if included) are physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 600 has one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 600 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, wristbands, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 600.

[0219] Figure 6BAn exemplary personal electronic device 600 is shown. In some embodiments, the device 600 includes a Figure 2A 、 Figure 2B and Figure 4 Some or all of the components described. The device 600 has a bus 612 that operatively couples an I / O portion 614 to one or more computer processors 616 and a memory 618. The I / O portion 614 is connected to a display 604, which may have a touch-sensitive component 622 and, optionally, a touch intensity-sensitive component 624. In addition, the I / O portion 614 is connected to a communication unit 630 for receiving application and operating system data using Wi-Fi, Bluetooth, near-field communication (NFC), cellular, and / or other wireless communication technologies. The device 600 includes input mechanisms 606 and / or 608. For example, the input mechanism 606 is a rotatable input device or a depressible input device and a rotatable input device. In some examples, the input mechanism 608 is a button.

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

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

[0222] As used herein, the term "indicator" refers to, for example, a display on device 200, 400, and / or 600 ( Figure 2A 、 Figure 4 and Figure 6A-6B ) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) each constitute an affordance.

[0223] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 4 Touchpad 455 or Figure 5B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 551 in FIG, the particular user interface element is adjusted according to the detected input. In the case of a touch screen display (e.g., a touch screen display) that enables direct interaction with user interface elements on the touch screen display Figure 2A touch-sensitive display system 212 or Figure 5A In some implementations of the touch screen 212 in FIG, 20 , a contact detected on the touch screen acts as a “focus selector” such that when input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted according to the detected input. In some implementations, the focus moves from one area of the user interface to another area of the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves according to the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is generally a user interface element (or contact on the touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a trackpad or touch screen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

[0224] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted off, before or after contact begins to move, before contact ends, before or after contact is detected to increase in intensity, and / or before or after contact is detected to decrease in intensity). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half-maximum value of the contact intensity, the 90% maximum value of the contact intensity, etc. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation), rather than to determine whether to perform the first operation or the second operation.

[0225] In some embodiments, a portion of a gesture is identified for use in determining the characteristic strength. For example, a touch-sensitive surface receives 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 ending position is based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., the portion of the swipe contact that is located only at the ending position). In some embodiments, a smoothing algorithm is applied to the strength of the swipe contact before determining the characteristic strength of the contact. For example, the smoothing algorithm optionally includes one or more of the following: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow peaks or dips in the strength of the swipe contact to achieve the purpose of determining the characteristic strength.

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

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

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

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

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

[0231] 3. Digital Assistant System

[0232] Figure 7A A block diagram of a digital assistant system 700 according to various examples is shown. In some examples, the digital assistant system 700 is implemented on a stand-alone computer system. In some examples, the digital assistant system 700 is distributed across multiple computers. In some examples, some of the modules and functions of the digital assistant are divided into a server portion and a client portion, where the client portion is located on one or more user devices (e.g., device 104, device 122, device 200, device 400, or device 600) and communicates with the server portion (e.g., server system 108) over one or more networks, such as Figure 1 In some examples, the digital assistant system 700 is Figure 1 It should be noted that the digital assistant system 700 is only one example of a digital assistant system, and that the digital assistant system 700 may have more or fewer components than shown, combine two or more components, or have a different configuration or arrangement of components. Figure 7A The various components shown in the drawings are implemented in hardware, software instructions for execution by one or more processors, firmware (including one or more signal processing integrated circuits and / or application specific integrated circuits), or a combination thereof.

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

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

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

[0236] In some examples, the network communication interface 708 includes one or more wired communication ports 712 and / or wireless transmission and reception circuitry 714. The one or more wired communication ports receive and send communication signals via one or more wired interfaces such as Ethernet, Universal Serial Bus (USB), FIREWIRE, etc. The wireless circuitry 714 receives RF signals and / or optical signals from a communication network and other communication devices and sends RF signals and / or optical signals to a communication network and other communication devices. Wireless communication uses any of a variety of communication standards, protocols, and technologies, such as GSM, EDGE, CDMA, TDMA, Bluetooth, Wi-Fi, VoIP, Wi-MAX, or any other suitable communication protocol. The network communication interface 708 enables communication between the digital assistant system 700 and other devices over a network, such as the Internet, an intranet, and / or a wireless network such as a cellular telephone network, a wireless local area network (LAN), and / or a metropolitan area network (MAN).

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

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

[0239] The communication module 720 facilitates communication between the digital assistant system 700 and other devices via the network communication interface 708. For example, the communication module 720 facilitates communication between the digital assistant system 700 and other devices (such as Figure 2A 、 Figure 4 、 Figures 6A to 6B The communication module 720 also includes various components for processing data received by the wireless circuit 714 and / or the wired communication port 712.

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

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

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

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

[0244] In some examples, such as Figure 7B As shown in FIG, the I / O processing module 728 can be Figure 7A The I / O devices 716 in the Figure 7AThe network communication interface 708 in interacts with a user device (e.g., device 104, device 200, device 400, or device 600) to obtain user input (e.g., voice input) and provide a response to the user input (e.g., as voice output). The I / O processing module 728 optionally obtains context information associated with the user input from the user device along with or shortly after receiving the user input. The context information includes user-specific data, vocabulary, and / or preferences related to the user input. In some examples, the context information also includes the software state and hardware state of the user device at the time the user request is received, and / or information related to the user's surrounding environment at the time the user request is received. In some examples, the I / O processing module 728 also sends follow-up questions related to the user request to the user and receives answers from the user. When the user request is received by the I / O processing module 728 and the user request includes voice input, the I / O processing module 728 forwards the voice input to the STT processing module 730 (or speech recognizer) for speech-to-text conversion.

[0245] The STT processing module 730 includes one or more ASR systems 758. The one or more ASR systems 758 can process the speech input received by the I / O processing module 728 to generate recognition results. Each ASR system 758 includes a front-end speech preprocessor. The front-end speech preprocessor extracts representative features from the speech input. For example, the front-end speech preprocessor performs a Fourier transform on the speech input to extract spectral features that characterize the speech input as a sequence of representative multidimensional vectors. In addition, each ASR system 758 includes one or more speech recognition models (e.g., acoustic models and / or language models) and implements one or more speech recognition engines. Examples of speech recognition models include hidden Markov models, Gaussian mixture models, deep neural network models, n-gram language models, and other statistical models. Examples of speech recognition engines include engines based on dynamic time warping and engines based on weighted finite state transformers (WFST). One or more speech recognition models and one or more speech recognition engines are used to process the extracted representative features of the front-end speech preprocessor to produce intermediate recognition results (e.g., phonemes, phoneme strings and subwords), and ultimately produce text recognition results (e.g., words, word strings, or symbol sequences). In some examples, the voice input is at least partially processed by a third-party service or processed on the user's device (e.g., device 104, device 200, device 400 or device 600) to produce recognition results. Once the STT processing module 730 produces a recognition result containing a text string (e.g., a word, or a sequence of words, or a sequence of symbols), the recognition result is transmitted to the natural language processing module 732 for intention inference. In some examples, the STT processing module 730 produces multiple candidate text representations of the voice input. Each candidate text representation is a sequence of words or symbols corresponding to the voice input. In some examples, each candidate text representation is associated with a voice recognition confidence score. Based on the speech recognition confidence score, the STT processing module 730 ranks the candidate text representations and provides the n best (e.g., the n highest ranked) candidate text representations to the natural language processing module 732 for intent inference, where n is a predetermined integer greater than zero. For example, in one example, only the highest ranked (n=1) candidate text representation is delivered to the natural language processing module 732 for intent inference. For another example, the five highest ranked (n=5) candidate text representations are delivered to the natural language processing module 732 for intent inference.

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

[0247] In some examples, the STT processing module 730 includes a vocabulary of recognizable words and / or accesses the vocabulary via the phonetic alphabet conversion module 731. Each vocabulary word is associated with one or more candidate pronunciations of the word represented in the speech recognition phonetic alphabet. Specifically, the vocabulary of recognizable words includes words associated with multiple candidate pronunciations. For example, the vocabulary includes words associated with and In some examples, the candidate pronunciations for a word are associated with candidate pronunciations for the word "tomato". Additionally, vocabulary words are associated with custom candidate pronunciations based on previous speech input from the user. Such custom candidate pronunciations are stored in the STT processing module 730 and associated with a particular user via a user profile on the device. In some examples, the candidate pronunciations for a word are determined based on the spelling of the word and one or more linguistic and / or phonetic rules. In some examples, the candidate pronunciations are manually generated, for example, based on a known standard pronunciation.

[0248] In some examples, candidate pronunciations are ranked based on their prevalence. For example, Ranked higher than Because the former is the more common pronunciation (e.g., among all users, for users in a particular geographic region, or for any other suitable subset of users). In some examples, candidate pronunciations are ranked based on whether they are custom candidate pronunciations associated with the user. For example, custom candidate pronunciations are ranked higher than standard candidate pronunciations. This can be used to identify proper nouns that have unique pronunciations that deviate from the standard pronunciation. In some examples, candidate pronunciations are associated with one or more phonetic features such as geographic origin, country, or ethnicity. For example, a candidate pronunciation associated with the United States, while the candidate pronunciation Associated with the United Kingdom. In addition, the ranking of the candidate pronunciations is based on one or more characteristics of the user (e.g., geographic origin, country, race, etc.) in a user profile stored on the device. For example, it may be determined from the user profile that the user is associated with the United States. Based on the user being associated with the United States, the candidate pronunciations are ranked (Associated with the United States) Comparable candidate pronunciations (associated with the United Kingdom) is ranked higher. In some examples, one of the ranked candidate pronunciations may be selected as the predicted pronunciation (e.g., the most likely pronunciation).

[0249] When speech input is received, the STT processing module 730 is used to determine (e.g., using an acoustic model) a phoneme corresponding to the speech input and then attempts to determine (e.g., using a language model) a word that matches the phoneme. For example, if the STT processing module 730 first identifies a phoneme sequence corresponding to a portion of the speech input It may then determine based on the lexical index 744 that the sequence corresponds to the word "tomato".

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

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

[0252] In some examples, in addition to the sequence of words or symbols obtained from the STT processing module 730, the natural language processing module 732 also receives contextual information associated with the user request, for example, from the I / O processing module 728. The natural language processing module 732 optionally uses the contextual information to clarify, supplement, and / or further qualify the information included in the candidate text representation received from the STT processing module 730. The contextual information includes, for example, user preferences, the hardware and / or software state of the user's device, sensor information collected before, during, or shortly after the user's request, previous interactions (e.g., conversations) between the digital assistant and the user, and the like. As described herein, in some examples, the contextual information is dynamic and changes with the time, location, content, and other factors of the conversation.

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

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

[0255] In addition, the attribute nodes "cuisine", "price range", "telephone number" and "location" are child nodes of the attribute node "restaurant", and are all connected to the "restaurant reservation" node (i.e., executable intent node) through the intermediate attribute node "restaurant". Figure 7C As shown, ontology 760 also includes a "Set Reminder" node (i.e., another executable intent node). The attribute nodes "Date / Time" (for setting reminders) and "Subject" (for reminders) are both connected to the "Set Reminder" node. Since the attribute "Date / Time" is related to both the task of making a restaurant reservation and the task of setting a reminder, the attribute node "Date / Time" is connected to both the "Restaurant Reservation" node and the "Set Reminder" node in ontology 760.

[0256] Executable intent nodes, along with their linked attribute nodes, are described as "domains". In this discussion, each domain is associated with a corresponding executable intent and refers to a set of nodes (and the relationships between these nodes) associated with a particular executable intent. For example, Figure 7CThe knowledge ontology 760 shown in includes an example of a restaurant reservation domain 762 and an example of a reminder domain 764 within the knowledge ontology 760. The restaurant reservation domain includes an executable intent node "restaurant reservation", attribute nodes "restaurant", "date / time" and "party size", and child attribute nodes "cuisine", "price range", "phone number" and "location". The reminder domain 764 includes an executable intent node "set reminder" and attribute nodes "subject" and "date / time". In some examples, the knowledge ontology 760 is composed of multiple domains. Each domain shares one or more attribute nodes with one or more other domains. For example, in addition to the restaurant reservation domain 762 and the reminder domain 764, the "date / time" attribute node is also associated with many different domains (e.g., a scheduling domain, a travel booking domain, a movie ticket domain, etc.).

[0257] although Figure 7C Two exemplary domains within the knowledge ontology 760 are shown, but other domains include, for example, "find a movie," "make a phone call," "find directions," "schedule a meeting," "send a message," and "provide answers to questions," "read a list," "provide navigation instructions," "provide instructions for a task," and the like. The "send message" domain is associated with the "send message" executable intent node and further includes attribute nodes such as "one or more recipients," "message type," and "message body." The attribute node "recipients" is further defined by, for example, child attribute nodes such as "recipient name" and "message address."

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

[0259] In some examples, nodes associated with multiple related executable intents are clustered under a "superdomain" in the knowledge ontology 760. For example, the "travel" superdomain includes a cluster of attribute nodes and executable intent nodes related to travel. The executable intent nodes related to travel include "flight booking", "hotel booking", "car rental", "route planning", "find points of interest", etc. The executable intent nodes under the same superdomain (e.g., the "travel" superdomain) have multiple common attribute nodes. For example, the executable intent nodes for "flight booking", "hotel booking", "car rental", "get directions", and "find points of interest" share one or more of the attribute nodes "starting location", "destination", "departure date / time", "arrival date / time", and "party size".

[0260] In some examples, each node in the knowledge ontology 760 is associated with a set of words and / or phrases related to the attribute or executable intent represented by the node. The corresponding set of words and / or phrases associated with each node is a so-called "vocabulary" associated with the node. The corresponding set of words and / or phrases associated with each node is stored in the vocabulary index 744 associated with the attribute or executable intent represented by the node. For example, return Figure 7B For example, the vocabulary associated with the node for the "restaurant" attribute includes words such as "food," "drinks," "cuisine," "hunger," "eat," "pizza," "fast food," "meal," etc. For another example, the vocabulary associated with the node for the "make phone call" executable intent includes words and phrases such as "call," "make a phone call," "dial," "talk to," "call the number," "call," etc. The vocabulary index 744 optionally includes words and phrases in different languages.

[0261] The natural language processing module 732 receives candidate text representations (e.g., one or more text strings or one or more symbol sequences) from the STT processing module 730 and, for each candidate representation, determines which nodes the words in the candidate text representation refer to. In some examples, if a word or phrase in the candidate text representation is found (via the vocabulary index 744) to be associated with one or more nodes in the knowledge ontology 760, the word or phrase "triggers" or "activates" those nodes. Based on the number and / or relative importance of the activated nodes, the natural language processing module 732 selects one of the executable intents as the task that the user intends the digital assistant to perform. In some examples, the domain with the most "triggered" nodes is selected. In some examples, the domain with the highest confidence (e.g., based on the relative importance of its various triggered nodes) is selected. In some examples, the domain is selected based on a combination of the number and importance of the triggered nodes. In some examples, additional factors are also considered in the process of selecting the node, such as whether the digital assistant has previously correctly interpreted a similar request from the user.

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

[0263] It should be recognized that in some examples, the natural language processing module 732 is implemented using one or more machine learning mechanisms (e.g., neural networks). Specifically, the one or more machine learning mechanisms are configured to receive candidate text representations and context information associated with the candidate text representations. Based on the candidate text representations and the associated context information, the one or more machine learning mechanisms are configured to determine an intent confidence score based on a set of candidate executable intents. The natural language processing module 732 may select one or more candidate executable intents from a set of candidate executable intents based on the determined intent confidence scores. In some examples, a knowledge ontology (e.g., knowledge ontology 760) is also utilized to select one or more candidate executable intents from a set of candidate executable intents.

[0264] Additional details of searching ontologies based on symbolic strings are described in U.S. Utility Patent Application Serial No. 12 / 341,743, filed on December 22, 2008, entitled “Method and Apparatus for Searching Using An Active Ontology,” the entire disclosure of which is incorporated herein by reference.

[0265] In some examples, once the natural language processing module 732 identifies an executable intent (or domain) based on the user request, the natural language processing module 732 generates a structured query representing the identified executable intent. In some examples, the structured query includes parameters for one or more nodes within the executable intent's domain, and at least some of the parameters are populated with specific information and requirements specified in the user request. For example, a user may say, "Make me a reservation at a sushi restaurant for 7 p.m." In this case, the natural language processing module 732 is able to correctly identify the executable intent as "restaurant reservation" based on the user input. According to the knowledge ontology, a structured query for the "restaurant reservation" domain includes parameters such as {cuisine}, {time}, {date}, {number of people in the party}, etc. In some examples, based on the voice input and text derived from the voice input using the STT processing module 730, the natural language processing module 732 generates a partial structured query for the restaurant reservation domain, where the partial structured query includes the parameters {cuisine = "sushi"} and {time = "7 p.m."}. However, in this example, the user utterance does not contain sufficient information to complete the structured query associated with the domain. Therefore, based on the currently available information, other necessary parameters such as {number of people in the party} and {date} are not specified in the structured query. In some examples, the natural language processing module 732 populates some parameters of the structured query with the received contextual information. For example, in some examples, if the user requests a sushi restaurant "nearby," the natural language processing module 732 populates the {location} parameter in the structured query with the GPS coordinates from the user's device.

[0266] In some examples, the natural language processing module 732 identifies multiple candidate executable intents for each candidate text representation received from the STT processing module 730. In addition, in some examples, a corresponding structured query is generated (partially or fully) for each identified candidate executable intent. The natural language processing module 732 determines an intent confidence score for each candidate executable intent and ranks the candidate executable intents based on the intent confidence score. In some examples, the natural language processing module 732 transmits the generated one or more structured queries (including any completed parameters) to the task flow processing module 736 ("task flow processor"). In some examples, one or more structured queries for the m best (e.g., the m highest ranked) candidate executable intents are provided to the task flow processing module 736, where m is a predetermined integer greater than zero. In some examples, one or more structured queries for the m best candidate executable intents are provided to the task flow processing module 736 along with the corresponding one or more candidate text representations.

[0267] Additional details for inferring user intent based on multiple candidate executable intents determined based on multiple candidate textual representations of speech input are described in U.S. utility patent application Ser. No. 14 / 298,725, entitled “System and Method for Inferring User Intent From Speech Inputs,” filed on June 6, 2014, the entire disclosure of which is incorporated herein by reference.

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

[0269] As described above, to complete a structured query, the task flow processing module 736 may need to initiate additional conversations with the user to obtain additional information and / or clarify potentially ambiguous utterances. When such interaction is necessary, the task flow processing module 736 invokes the dialog flow processing module 734 to participate in the conversation with the user. In some examples, the dialog flow processing module 734 determines how (and / or when) to request additional information from the user and receives and processes user responses. Questions are presented to the user and responses are received from the user via I / O processing module 728. In some examples, the dialog flow processing module 734 presents the dialog output to the user via audible and / or visual output and receives input from the user via verbal or physical (e.g., click) responses. Continuing with the above example, when the task flow processing module 736 invokes the dialog flow processing module 734 to determine the "party size" and "date" information for the structured query associated with the domain "restaurant reservation," the dialog flow processing module 734 generates questions such as "How many people are in your party?" and "What day do you want to reserve a reservation?" and transmits them to the user. Once the answer is received from the user, the dialog flow processing module 734 fills the structured query with the missing information, or passes the information to the task flow processing module 736 to complete the missing information based on the structured query.

[0270] Once the task flow processing module 736 has completed the structured query for the executable intent, the task flow processing module 736 begins to execute the final task associated with the executable intent. Therefore, the task flow processing module 736 executes the steps and instructions in the task flow model according to the specific parameters contained in the structured query. For example, the task flow model for the executable intent "restaurant reservation" includes steps and instructions for contacting a restaurant and actually requesting a reservation for a specific party size at a specific time. For example, using a structured query such as: {restaurant reservation, restaurant = ABC Cafe, date = 3 / 12 / 2012, time = 7pm, party size = 5}, the task flow processing module 736 may perform the following steps: (1) Log into the server of ABC Cafe or such A restaurant reservation system, (2) entering date, time, and party size information into a form on the website, (3) submitting the form, and (4) making a calendar entry for the reservation in the user's calendar.

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

[0272] For example, if a restaurant has enabled an online reservation service, the restaurant submits a service model that specifies the necessary parameters for making a reservation and transmits the values of the necessary parameters to the API of the online reservation service. When requested by the task flow processing module 736, the service processing module 738 can use the web address stored in the service model to establish a network connection with the online reservation service and send the necessary parameters for the reservation (e.g., time, date, party size) to the online reservation interface in a format according to the API of the online reservation service.

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

[0274] In an example where the task flow processing module 736 receives multiple structured queries from the natural language processing module 732, the task flow processing module 736 first processes the first structured query of the received structured queries in an attempt to complete the first structured query and / or perform one or more tasks or actions represented by the first structured query. In some examples, the first structured query corresponds to the highest-ranked executable intent. In other examples, the first structured query is selected from the structured queries received based on a combination of the corresponding speech recognition confidence score and the corresponding intent confidence score. In some examples, if the task flow processing module 736 encounters an error during processing of the first structured query (e.g., due to an inability to determine the necessary parameters), the task flow processing module 736 may continue to select and process a second structured query corresponding to a lower-ranked executable intent in the received structured queries. For example, the second structured query is selected based on the speech recognition confidence score of the corresponding candidate text representation, the intent confidence score of the corresponding candidate executable intent, the missing necessary parameters in the first structured query, or any combination thereof.

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

[0276] In some examples, instead of using the speech synthesis processing module 740 (or in addition), speech synthesis is performed on a remote device (e.g., server system 108), and the synthesized speech is sent to the user device for output to the user. For example, this may occur in some implementations where the output of the digital assistant is generated at the server system. And because the server system typically has more processing power or more resources than the user device, it is possible to obtain higher quality speech output than client-side synthesis would achieve.

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

[0278] 4. Systems and Techniques for Selecting Context Collectors for a Context Sharing Group

[0279] Figure 8 1 shows systems and techniques for selecting a context collector for a device circle according to various examples. System 800 includes a user device 802, a public device 804, a user device 806, and a user device 808. User device 802, user device 806, and user device 808 are all client devices (e.g., user device 104, 122, 200, 400, or 600). For example, user device 802 is User device 806 is an Apple User equipment 808 is Client devices are registered to a single user. For example, user device 802 may be registered to a first user, and user device 806 and user device 808 may be registered to a second user. Public device 804 is a smart speaker that has the same or similar digital assistant capabilities as the various user devices. Public devices are electronic devices that are not registered to a single user or that are registered to multiple users (e.g., so that the public device can be used by multiple users without additional user registration and / or user authentication requirements). For example, public device 804 is Another example of a public device is a smart TV (e.g., Apple ).

[0280] The system 800 also includes a network 810. The network 810 is a wireless communication network (e.g., network 110). In some examples, the system 800 includes one or more remote devices (e.g., one or more remote servers (e.g., DA server 106), a local server, a cloud computing system, etc.). It should be appreciated that in these examples, any operations performed by the user device 802, the public device 804, the user device 806, and / or the user device 808 may alternatively be performed by the one or more remote devices. For example, the one or more servers may perform the operations of a corresponding DA client module (e.g., DA client module 229) of the user device 802, the public device 804, the user device 806, and / or the user device 808.

[0281] As indicated by arrow 812, user device 802 connects to network 810. At this point in the process, public device 804, user device 806, and user device 808 are also connected to network 810. After user device 802 connects to network 810, it joins context sharing group 814, which also includes public device 804, user device 806, and user device 808. A "context sharing group" (also known as a "device circle") is a collection of two or more electronic devices (e.g., within a specific location) that share context information with at least one electronic device participating in the context sharing group (e.g., with the context collector of the context sharing group). Context sharing group 814 is associated with a specific location (e.g., a home, office, etc.). Thus, the electronic devices participating in context sharing group 814 are each located in an area (e.g., a room, floor, etc.) of the specific location. In some examples, context sharing group 814 is not associated with a specific location, so the electronic devices participating in context sharing group 814 do not need to be located in a single location (e.g., the electronic devices may be located in two separate homes).

[0282] In some examples, in response to experiencing a "device state change" (device state changes are described in more detail below), electronic devices participating in a context sharing group automatically share context information with a "context collector" of the context sharing group. A context collector is an electronic device that receives, aggregates, and stores context information from electronic devices participating in the context sharing group. In addition, the context collector provides the "aggregate context" of the context sharing group (which includes context information received from one or more electronic devices participating in the context sharing group) to one or more electronic devices participating in the context sharing group (e.g., in response to a request for aggregate context information received from one or more electronic devices). In some examples, the context collector of the context sharing group is an electronic device participating in the context sharing group (e.g., a user device or a public device). In other examples, the context collector is a remote device that does not participate in the context sharing group and therefore does not share its own context information with the electronic devices participating in the context sharing group. Examples of remote devices that can be used as context collectors include one or more servers (e.g., DA server 106), one or more cloud computing systems, one or more local servers, etc.

[0283] The following will refer to Figure 8 As described above, the electronic device participating in the context sharing group is first “selected” (ie, chosen) as a context collector before it starts receiving context information from other electronic devices participating in the context sharing group and aggregating context information. Figure 8and the corresponding description below discuss the selection of a single context collector for the context sharing group 814 , but in some examples, the context sharing group 814 includes more than one context collector (eg, two or three context collectors).

[0284] In some examples, user device 802 automatically joins context sharing group 814 in response to connecting to network 810. In some examples, user device 802 must be connected to network 810 in order to join context sharing group 814. In these examples, each of the electronic devices participating in context sharing group 814 is also connected to network 810. In other words, in these examples, each electronic device participating in context sharing group 814 must be connected to network 810. In some examples, user device 802 joins context sharing group 814 without having to connect to network 810. In some of these examples, user device 802 joins context sharing group 814 when a communication connection (e.g., a short-range communication connection (e.g., a Bluetooth connection, a Bluetooth Low Energy (BTLE) connection, etc.)) is established with at least one electronic device already participating in the context sharing group (e.g., with public device 804).

[0285] In some examples, the user device 802 must register with the context sharing group 814 in order to join the context sharing group 814. For example, registering the user device 802 with the context sharing group 814 may include a user of the user device 802 registering the user device 802 via a context sharing group-enabled software application stored on the user device 802 (e.g., via , registering the user device 802 with the context sharing group 814 via a website with context sharing group functionality. This may include the user device 802 registering with an already existing context sharing group 814 (e.g., created by another electronic device participating in the context sharing group 814), or creating a context sharing group 814 and subsequently registering with the context sharing group 814 after the context sharing group 814 is created. In some examples, registering with the context sharing group 814 includes the user device 802 granting access to / allowing the other electronic devices registered in the context sharing group 814 to receive, share, store, and / or utilize context information, personal information (e.g., email address, home address, payment information, etc.), and / or user data (e.g., the user's media, contacts, voice profile, preferences, etc.) associated with the user device 802 (including context information, user data, and / or personal information stored locally on the user device 802 and / or remotely on one or more remote devices (e.g., synchronized from the user device 802 to one or more servers)).

[0286] In the above example, before the user device 802 joins the context sharing group 814, the user device 802 determines whether it is registered in the context sharing group 814. Then, the user device 802 joins the context sharing group 813 only if it determines that it is registered in the context sharing group 814. If the user device 802 determines that it is not registered in the context sharing group 814, the user device 802 abandons joining the context sharing group 814.

[0287] After user device 802 joins context sharing group 814 (e.g., immediately thereafter or shortly thereafter (e.g., a few minutes later)), the electronic devices participating in context sharing group 814 perform context collector "election," which is a process used to elect (i.e., select) one of the electronic devices participating in context sharing group 814 as the context collector for the context sharing group. As described above, in some examples, more than one electronic device participating in context sharing group 814 is elected as the context collector. In some examples, user device 802 (and other electronic devices participating in context sharing group 814) performs context collector election in response to joining context sharing group 814 (e.g., immediately thereafter). In some examples, user device 802 (and other electronic devices participating in context sharing group 814) performs context collector election in response to an electronic device participating in context sharing group 814 (e.g., the current context collector) leaving the context sharing group (e.g., disconnecting from network 810, disconnecting from a communication connection with another electronic device participating in context sharing group 814, and / or leaving a specific location associated with context sharing group 814). Note that, as will be discussed below, electronic devices participating in the context sharing group 814 may perform context collector election even if the context sharing group 814 already includes a context collector, and even if the context sharing group 814 only allows a single context collector.

[0288] Context collector selection begins with user device 802 (and each of the other electronic devices participating in context sharing group 814) determining a collector score based on the strength of connectivity between user device 802 and network 810 and / or based on the power state of user device 802 (e.g., wired power connection versus battery power and / or remaining battery power). For example, a stronger connection between user device 802 and network 810 will result in a higher context collector score. Similarly, the more stable the power supply of user device 802, the higher the context collector score of user device 802 will be (e.g., wired power connection is more stable than battery power, and full battery power is more stable than low battery power). In some examples, the collector score is also based on how frequently user device 802 moves in and out of context sharing group 814 (e.g., how frequently user device 802 connects to / disconnects from network 810 and / or how frequently user device 802 enters and / or leaves a particular location associated with context sharing group 814). In some examples, the context collector score is also based on how consistently user device 802 maintains context information in its memory. In some examples, the context collector score is also based on the stability of the communication connection between the user device 802 and other electronic devices participating in the context sharing group 814. In some examples, the context collector score is also based on the reachability of the user device 802 to the other electronic devices participating in the context sharing group 814 (e.g., the more devices that the user device 802 can reach through various networks / other communication protocols, the higher the context collector score). The above factors considered in determining the context collector score emphasize the stability of the electronic device's participation in the context sharing group, its ability to communicate with other electronic devices, and / or its ability to store context information, because it is desirable for the context sharing group 814 to have a context collector that is available as frequently as possible to receive, aggregate, store, and / or send context information.

[0289] As indicated by arrow 816, after user device 802 determines the context collector score, user device 802 sends the context collector score (e.g., data corresponding to the context collector score) to each other electronic device participating in context sharing group 814 (i.e., public device 804, user device 806, and user device 808) via network 810. In some examples, user device 802 also sends a context collector indication (also referred to as a context collector "flag") indicating whether user device 802 is currently the context collector. For example, user device 802 sends the context collector indication simultaneously with or shortly after sending the context collector score. The context collector indication of the user device 802 will indicate that the user device 802 is the context collector if (1) the user device 802 was previously elected as the context collector after joining the context sharing group 814 (i.e., after connecting to the network 810 as indicated by arrow 812) and / or if (2) the user device 802 was elected as the context collector when the user device 802 last participated in the context sharing group 814 (i.e., before leaving the context sharing group 814 and rejoining the context sharing group 814 after connecting to the network 810 as indicated by arrow 812). Otherwise, the context collector indication will indicate that the user device 802 is not the context collector.

[0290] As indicated by arrow 818, public device 804, user device 806, and user device 808 each send their respective context collector scores (and, in some examples, their respective context collector indications) to user device 802 before, simultaneously with, or shortly after user device 802 sends its context collector score (and, in some examples, its context collector indication, as indicated by arrow 816). Figure 8 814 , the public device 804 , the user device 806 , and the user device 808 also transmit their respective context collector scores (and, in some examples, their respective context collector indications) to each other. Thus, following arrows 816 and 818 , each electronic device participating in the context sharing group 814 will have a context collector score (and, in some examples, such a context collector indication) corresponding to each of the other electronic devices participating in the context sharing group 814 .

[0291] After receiving the context collector score, the user device 802 (and the other electronic devices participating in the context sharing group 814) determines which electronic device among the electronic devices participating in the context sharing group 814 will be selected as the context collector based on the context collector score. The other electronic devices also make this determination based on the provided context collector score. Determining which electronic device among the electronic devices included in the context sharing group 814 will be selected as the context collector includes the user device 802 comparing its own context collector score with the context collector scores received from the public device 804, the user device 806, and the user device 808. The other electronic devices also compare their own context collector scores with the received scores. Then, based on this comparison, the user device 802 (and the other electronic devices participating in the context sharing group 814) identifies the highest context collector score and selects the electronic device with the highest context collector score as the context collector.

[0292] Because public device 804, user device 806, and user device 808 make the above determinations based on the same data and information as user device 802, they each also select the same electronic device as user device 802 as the context collector. Therefore, electronic devices participating in context sharing group 814 will know whether they have been selected as the context collector based on their own context collector score comparison. However, in some examples, each electronic device participating in context sharing group 814 sends a selection indication to the other electronic devices, indicating the context collector selected by each electronic device.

[0293] In the above example where user device 802, public device 804, user device 806, and user device 808 each send a context collection indication, determining which electronic device among the electronic devices participating in context sharing group 814 will be selected as the context collector also includes user device 802 (and the other electronic devices participating in context sharing group 814) determining whether context sharing group 814 currently includes a context collector based on the received context collector indication. In these examples, if user device 802 determines that context sharing group 814 already includes a context collector, user device 802 selects the existing context collector as the context collector for context sharing group 814, regardless of the context collector score comparison result. If user device 802 determines that context sharing group 814 already includes two or more context collectors, user device 802 selects a context collector based on the determined context collector scores (as described above). This, in turn, improves the stability of the context collector because it ensures that the context collector of context sharing group 814 will not change unless the existing context collector leaves context sharing group 814.

[0294] Note that in the above example where the context sharing group 814 includes more than one (e.g., two) context collectors, if the received context collector indication indicates that the context sharing group 814 includes more than the allowed number of context collectors, the user device 802 (and other electronic devices participating in the context sharing group 814) will select a context collector based on a comparison of the determined context collector scores. For example, if the context sharing group may include two context collectors, and the received context collector indication indicates that there are currently two context collectors participating in the context sharing group 814, the user device 802 will select these two existing context collectors regardless of the context collector score comparison result. However, if the received context collector indication indicates that there are currently three or more context collectors participating in the context sharing group 814, the user device 802 will select a context collector based on a comparison of the determined context collector scores.

[0295] For example, if user device 802 (and other electronic devices participating in context sharing group 814) selects user device 802 as the context collector for context sharing group 814, user device 802 will establish a communication connection with public device 804, user device 806, and user device 808 (via network 810) so that user device 802 can receive context information from one or more of those electronic devices and send the aggregate context of the context sharing group (e.g., a stored set of context information received from one or more (e.g., each) electronic device participating in context sharing group 814) to one or more of those electronic devices (e.g., in response to a received request for the aggregate context). If one of public device 804, user device 806, and user device 808 is selected as the context collector, those devices will similarly establish a communication connection with another electronic device participating in context sharing group 814.

[0296] As described above, in some examples, in response to experiencing a "device state change," electronic devices participating in a context sharing group automatically share context information with a context collector of the context sharing group. Examples of device state changes include media playback, activation (e.g., opening) of a stored software application, a timer event (e.g., a timer of the electronic device rings), an alarm event (e.g., an alarm of the electronic device rings), a change in power state (e.g., the electronic device is powered on or off), a change in display visibility (e.g., the display of the electronic device is repositioned from a display-down position to a display-up position (making the display visible to a user of the electronic device in the display-up position)), detection of a digital assistant trigger word or phrase (e.g., "Hey, Siri," "Siri," etc.), initiation of a digital assistant conversation session via pressing or holding a physical button on the device, and termination of a digital assistant conversation session (e.g., after the digital assistant of the electronic device provides / outputs a digital assistant response to a user request).

[0297] For example, Figure 8 As shown, once alarm event 820 begins, user device 808 undergoes a device state change. Accordingly, user device 808 sends context information associated with user device 808 to the selected context collector of context sharing group 814 shortly after alarm event 820 begins (e.g., immediately after or a few seconds after the alarm event (e.g., 0.5 seconds after, 1 second after, etc.)). As shown by arrow 822a, if user device 802 is selected as the context collector, user device 808 sends the context information to user device 802. Alternatively, as shown by arrow 822b, if public device 804 is selected as the context collector, user device 808 sends the context information to public device 804. In addition to sending the context information to the context collector (e.g., user device 802 or public device 804), user device 808 also sends a device identification (also referred to as a device identifier) to the context collector (e.g., along with the context information). In some examples, the device identifier is predetermined (e.g., a predetermined serial number, etc.). In some examples, the device identifier is randomly generated (eg, a randomly generated number) by the user device 808. In some examples, the user device 808 is assigned a device identifier by a context collector of the context sharing group 814 upon joining the context sharing group 814.

[0298] In response to receiving the device identifier, the context collector stores an association between the user device 808 and the device identifier. Figure 9Described in more detail, the stored association between the electronic device and its device identifier is used to send a command to a specific electronic device. Specifically, in some examples, the context collector notifies the electronic devices participating in the context sharing group of the stored associations so that each electronic device can relay / send a command (e.g., a command received from a remote device) to the one or more other electronic devices based on the device identifiers corresponding to the one or more other electronic devices. When the context information received from the user device 808 is added to the stored aggregate context of the context sharing group 814, the context collector also associates the device identifier corresponding to the user device 808 with the context information. In this way, the context information can be organized based on the associated device identifiers of the context information included in the aggregate context. As will be described below with reference to Figure 9 As described in more detail, one or more remote devices (eg, one or more servers) use the device identifiers included in the aggregated context when selecting one or more electronic devices to perform one or more tasks in response to a user request.

[0299] The context information sent by an electronic device (e.g., user device 808) in response to experiencing a device state change includes various types of context information associated with the electronic device. Examples of context information sent by an electronic device in response to experiencing a device state change include device state change information (e.g., state change type (e.g., timer event, alarm event, end of digital assistant conversation session, etc.), state change time, etc.), device capability information (e.g., device type, processing capability, memory availability, display information (e.g., whether the device has a display and / or the size of the display), speaker information (e.g., whether the device has a speaker and / or the loudness of the speaker), etc.), and context state information (e.g., device location (e.g., based on GPS data from GPS module 235 and / or from a software application with context sharing group functionality (e.g., )), display visibility (e.g., display up or display down), user attention information (e.g., whether the user is currently viewing the device display (e.g., based on information from optical sensors 264 on the front and / or back of the device)), strength of the network connection (e.g., to network 810), battery charge, power type (e.g., battery versus wired power), etc.).

[0300] As described above, the selected context collector of the context sharing group 814 receives the above-mentioned context information from one or more electronic devices participating in the context sharing group 814, and then aggregates the context information and stores it in an aggregated context. In addition, the context collector updates the aggregated context when it receives additional context information from the one or more electronic devices. For example, if the user device 808 will experience another device state change after the alarm event 820, the user device 808 sends its latest / most recent context information to the context collector of the context sharing group 814, so that the context collector can incorporate the new context information associated with the user device 808 into the aggregated context and / or remove outdated / previous context information associated with the user device 808 from the aggregated context (e.g., remove previous context information that is different / conflicting with the newly received context information).

[0301] In some examples, the context collector only stores the most recent context information received from each electronic device participating in the context sharing group 814 (because the context collector removes / deletes previously received context information associated with the same device after receiving new context information associated with the same device). In some examples, the context collector stores the context information associated with the electronic device for a predetermined period of time (e.g., 1 hour, 1 day, 1 week, etc.) before removing / deleting the context information associated with the electronic device. In some examples, the context collector stores context information associated with the electronic device from a predetermined number of previous context information transmissions (e.g., 3, 5, 10, etc.). For example, the context collector may store context information from the last five context information transmissions from each electronic device. In some examples, the context collector stores a short event history for each electronic device. In some embodiments, this short history is based on the type of event. For example, the context collector may store data corresponding to the last three alarm events for each electronic device. In some examples, when an electronic device leaves the context sharing group 814, the context collector removes / deletes the context information for that electronic device.

[0302] Then, as will be referred to below Figure 9 and Figures 11 to 13 Described in more detail, in response to receiving a request for an aggregated context from one or more electronic devices participating in the context sharing group 814, the context collector sends the aggregated context (or at least a portion of the aggregated context) to the one or more electronic devices. In some examples, sending the aggregated context to the one or more electronic devices enables the one or more electronic devices to obtain a digital assistant response to the user request based on the aggregated context (or at least a portion of the aggregated context).

[0303] 5. Systems and techniques for performing tasks in context-sharing groups

[0304] Figure 9 Systems and techniques for performing one or more tasks in a context sharing group are shown according to various examples. System 900 includes a public device 904, a user device 906, a public device 908, and a user device 910, all of which participate in a context sharing group 914 (which is associated with a particular location (e.g., home, office, etc.)). User device 906 and user device 910 are both client devices (e.g., user devices 104, 122, 200, 400, or 600). For example, user device 906 and user device 910 are both In the example described below, user device 906 is registered to user 902, while user device 910 is not registered to user 902. Public device 904 is a smart speaker with the same or similar digital assistant capabilities as the user device. Public device 908 is a smart TV with the same or similar digital assistant capabilities as the user device (the connected display is not shown). Public device 908 is a context collector for context sharing group 914 (e.g., because public device 908 was previously selected as a context collector). As described above with reference to Figure 8 As discussed, the public device is not registered to a single user, or is registered to multiple users (e.g., such that the public device can be used by multiple users without additional user registration and / or user authentication requirements). For example, the public device 904 is Public device 910 is

[0305] The system 900 also includes a network 912 and a server 916 (e.g., DA server 106). The network 912 is a wireless communication network (e.g., network 110). As shown, the public device 904, the user device 906, the public device 908, and the user device 910 communicate with each other via the network 912 and with the server 916 (and are therefore each connected to the network 912). In addition, the server 916 is a remote device that does not participate in the context sharing group 914. In some examples, the system 900 includes one or more other remote devices (e.g., a local server, a cloud computing system, etc.) in place of the server 916. It should be appreciated that in these examples, any operations performed by the public device 904, the user device 906, the public device 908, and / or the user device 910 may alternatively be performed by the server 916. For example, the server 916 may execute the operations of the corresponding DA client modules (e.g., DA client module 229) of the public device 904, the user device 906, the public device 908, the user device 806, and / or the user device 910.

[0306] like Figure 9As shown, user 902 provides user voice input 918 (e.g., “Hey, Siri, stop the timer” or “Hey, Siri, play music”) that is received by public device 904. User voice input 918 includes a digital assistant trigger. A digital assistant trigger is a word or phrase that initiates a conversation session with the digital assistant of the electronic device (e.g., “Hey, Siri,” “Siri,” etc.). Thus, upon receiving user voice input 918, public device 904 detects the digital assistant trigger (e.g., determines that user voice input 918 includes a digital assistant trigger), determines that user voice input 918 represents a digital assistant request (based on detection of the digital assistant trigger), and begins processing user voice input 918 to determine and / or obtain a response to user voice input 918 (e.g., perform one or more tasks and / or output a digital assistant response).

[0307] Typically, from the time the public device / user device detects the digital assistant trigger, the public device / user device requires less than 2 seconds (e.g., 1 second, 1.5 seconds, etc.) to begin processing the user voice input as described above. During this period, the public device / user device communicates (e.g., via a wireless network (e.g., network 912) and / or a short-range communication connection (e.g., Bluetooth, BTLE, etc.)) with one or more nearby electronic devices (e.g., a second public device / user device participating in the same context sharing group) that also receives the user voice input and detects the digital assistant trigger included in the user voice input to determine which device should process the received user voice input.

[0308] However, in some examples, a public device / user device (e.g., participating in a context sharing group) receiving the user voice input requires more than 2 seconds (e.g., 3 seconds, 5 seconds, etc.) to detect the digital assistant trigger included in the voice input, and thus misses the opportunity to communicate with other nearby electronic devices that detect the digital assistant trigger within the two-second window and determine which device will respond to the user voice input. Therefore, even if another public device / user device (which does not have delayed digital assistant trigger detection) has already begun processing the user voice input and / or has already provided a response to the user voice input, the public device / user device with delayed digital assistant trigger detection will also begin processing the user voice input. This, in turn, can result in multiple devices (participating in the same context sharing group) providing responses to the same user voice input at different times, which can lead to a poor user experience (e.g., due to user confusion and / or annoyance). For example, if user device 906 also receives user voice input 918 but detects the digital assistant trigger 3 seconds after public device 904 detects the digital assistant trigger included therein, the result is that user device 906 and public device 904 can each provide a response to user voice input 918 (e.g., at different times). Therefore, it may be desirable to suppress delayed digital assistant trigger detection by public devices and / or user devices.

[0309] Figure 10 Systems and techniques for suppressing delayed digital assistant trigger detection using context collectors of a context sharing group according to various examples are shown. System 1000 is similar to system 900. Specifically, system 1000 includes a public device 1004 (corresponding to public device 904), a user device 1006 (corresponding to user device 906), and a public device 1008 (corresponding to public device 908), all of which participate in a context sharing group 1012 (corresponding to context sharing group 914). System 1000 also includes a network 1010 (corresponding to network 912). For simplicity, the user device corresponding to user device 910 and the server corresponding to server 916 are not shown. As with system 900, in the example described below, public device 1008 is the context collector of context sharing group 1012 (e.g., because public device 1008 was previously selected as the context collector).

[0310] It should be appreciated that in these examples, any operations performed by the public device 1004, the user device 1006, and the public device 1008 may alternatively be performed by one or more servers (e.g., a server corresponding to the server 916) and / or one or more other remote devices (e.g., a cloud computing system). For example, one or more servers may perform the operations of the corresponding DA client modules (e.g., the DA client module 229) of the public device 1004, the user device 1006, and / or the public device 1008.

[0311] like Figure 10 As shown, user device 1002 provides user voice input 1014 that includes a digital assistant trigger (e.g., corresponding to user voice input 918 (e.g., “Hey, Siri, stop the timer” or “Hey, Siri, play music.”)). User voice input 1014 is received by public device 1004 and user device 1006 (e.g., because public device 1004 and user device 1006 are located near each other (e.g., in the same room)). However, public device 1004 detects the digital assistant trigger before user device 1006. Therefore, while the user device is still determining whether user voice input 1014 includes a digital assistant trigger, public device 1004 initiates the digital assistant conversation session. In addition, as shown by arrow 1016, public device 1004 sends context information (and a device identifier corresponding to public device 1004) to public device 1008 (because detection of the digital assistant trigger is a device state change and public device 1008 is a context collector). For example, public device 1004 sends the context information and the device identifier in response to detecting the digital assistant trigger.

[0312] Because the device state change of the public device 1004 is the detection of a digital assistant trigger, the context information sent to the public device 1008 includes a trigger notification (e.g., along with other device state change information). The trigger notification includes a digital assistant trigger end time, which is the time when the digital assistant trigger ends according to the public device 1004 (e.g., the time when the public device 1004 stops receiving the audio signal corresponding to the digital assistant trigger). In some examples, the trigger notification also includes data indicating the energy level (e.g., decibel level) of the digital assistant trigger (e.g., the energy level of the audio signal corresponding to the digital assistant trigger). In some examples, the first trigger notification also includes data indicating a confidence score corresponding to the public device 1004's confidence that the user voice input 1014 includes a digital assistant trigger.

[0313] After receiving the context information and trigger notification from the public device 1004, the public device 1008 updates the aggregate context of the context sharing group 1012 to include the context information and trigger notification. In addition, as indicated by arrow 1017, in response to receiving the trigger notification, the public device 1008 retrieves the trigger notifications already included in the aggregate context (associated with one or more other electronic devices participating in the context sharing group) and sends them to the public device 1004 (e.g., trigger notifications received within a predetermined time period (e.g., within the last 30 seconds, within the last minute, within the last 5 minutes, etc.)). In some examples, the public device 1008 sends the aggregate context (including the received trigger notifications) to the public device 1004, rather than just sending the trigger notifications. As will be described in more detail below with respect to the user device 1006, the public device 1004 uses the trigger notifications received from the public device 1008 (e.g., data included in the trigger notifications) to determine whether it should suppress its own digital assistant trigger detection (and thereby forgo further processing of the user voice input 1014).

[0314] However, in this case, public device 1004 does not suppress detection of the digital assistant trigger (e.g., because public device 1004 is the first electronic device to detect the digital assistant trigger included in user voice input 1014) and continues to process user voice input 1014 (e.g., to determine / obtain a response to user voice input 1014 (e.g., perform one or more tasks and / or output a digital assistant response)). Therefore, as indicated by arrow 1018, public device 1004 sends a request for the aggregated context of context sharing group 1012 to public device 1008. As indicated by arrow 1020, in response to receiving the request for the aggregated context, public device 1008 sends the aggregated context to public device 1004. In some of the above examples in which public device 1008 sends the aggregated context at arrow 1017 instead of just sending the trigger notification, arrows 1018 and 1020 do not occur because the public device has already received the aggregated context. After the public device 1004 receives the aggregate context (as indicated by arrow 1020, or in some examples, as indicated by arrow 1017) and determines that it should continue processing the user voice input 1014, the public device 1004 obtains a response to the user voice input 1014 based on the user voice input 1014 and the context information included in the aggregate context (as will be described below with reference to FIG. Figure 9 described in more detail).

[0315] As indicated by arrow 1022, in response to detecting the digital assistant trigger included in the user voice input 1014, the user device 1006 sends the context information (and the device identifier corresponding to the user device 1006) to the public device 1008 (because the detection of the digital assistant trigger is a device state change and the public device 1008 is the context collector). Note that although Figure 10 User device 1006 is shown sending context information to public device 1008 after arrow 1020, but user device 1006 may send context information at any time after public device 1004 detects the digital assistant trigger and sends the context information to public device 1008 (as shown by arrow 1016). For example, user device 1006 may send context information to public device 1008 before public device 1004 receives the aggregated context from public device 1008 (represented by arrow 1020). As described above, because the device state change of user device 1006 is the detection of a digital assistant trigger, the context information sent to public device 1008 includes a trigger notification corresponding to the detection of the digital assistant trigger by user device 1006. The trigger notification sent by user device 1006 includes the same type of data and information that was previously included in the trigger notification sent by public device 1004 (e.g., data indicating the time when the digital assistant trigger ended (e.g., the time when user device 1006 stopped receiving the audio signal corresponding to the digital assistant trigger)).

[0316] After receiving the context information and trigger notification from user device 1006, public device 1008 updates the aggregate context of context sharing group 1012 to include the context information and trigger notification. In addition, as shown by arrow 1024, in response to receiving the trigger notification from user device 1006, public device 1008 retrieves the trigger notifications already included in the aggregate context (associated with one or more other electronic devices participating in the context sharing group, including public device 1004) and sends them to user device 1006 (e.g., trigger notifications received within a predetermined time period (e.g., within the last 30 seconds, within the last minute, within the last 5 minutes, etc.)). In some examples, public device 1008 sends the aggregate context (including the received trigger notification) to user device 1006 instead of sending only the trigger notification.

[0317] In some examples, in addition to sending the context information and trigger notifications to the public device 1008 (via the network 1010), the user device 1006 also sends the trigger notification (e.g., data corresponding to the trigger notification) to one or more electronic devices with which the user device 1006 shares a short-range communication connection (e.g., Bluetooth, BTLE, etc.). For example, if the user device 1006 and the public device 1004 share a BTLE connection, the user device 1006 will send the trigger notification directly to the public device 1004 via the BTLE connection (e.g., before or shortly after sending the context information and trigger notification to the public device 1008). Then, in response to receiving the trigger notification from the user device 1006, the one or more electronic devices send their own trigger notifications to the user device 1006 via their respective short-range communication connections. For example, the one or more electronic devices send trigger notifications corresponding to the digital assistant triggers detected by them within a predetermined time period (e.g., within the last 5 seconds, within the last 30 seconds, within the last minute, etc.).

[0318] After receiving a trigger notification from a public device 1008 (and in some examples, from one or more electronic devices with which the user device 1006 shares a short-range communication connection), the user device 1006 determines whether it should suppress its own digital assistant trigger detection (and therefore forgo further processing of the user voice input 1014). Specifically, the user device 1006 determines whether each trigger notification it has received (e.g., within the last second) is "reasonable" based on the digital assistant trigger end time included in each trigger notification (i.e., the time at which the digital assistant trigger ends according to the electronic device). A trigger notification is reasonable if its digital assistant trigger end time falls within a predetermined time range (e.g., 750 milliseconds, 500 milliseconds, 100 milliseconds, etc.) before the digital assistant trigger end time of the user device 1006 (i.e., the time at which the digital assistant trigger included in the user voice input 1014 ends according to the user device 1006).

[0319] If the user device 1006 determines that one or more of the trigger notifications it has received are reasonable (i.e., include a digital assistant trigger end time that falls within a predetermined time range before the digital assistant trigger end time of the user device 1006), the user device 1006 forgoes further processing of the user voice input 1014. For example, if the user device 1006 determines that a trigger notification corresponding to the public device 1004 (e.g., received from the public device 1008 and / or received from the public device 1004) is reasonable, the user device forgoes further processing of the user voice input 1014, such that the public device 1004 will be the only electronic device to provide a response to the user voice input 1014. However, in some examples, the public device 1004 receives one or more reasonable trigger notifications corresponding to one or more other electronic devices that detected the digital assistant trigger (e.g., from the public device 1008 (e.g., as indicated by arrow 1017)), and therefore also forgoes further processing of the user voice input 1014 (e.g., instead of sending a request for an aggregated context to the public device 1008 (e.g., as indicated by arrow 1018)).

[0320] If the user device 1006 determines that none of the trigger notifications it has received are reasonable (i.e., none of the trigger notifications include a digital assistant trigger end time that falls within a predetermined time range before the digital assistant trigger end time of the user device 1006), the user device 1006 continues to process the user voice input 1014 (e.g., by sending a request for the aggregate context to the public device 1008). This situation would occur, for example, under the following conditions: (1) the trigger notification of the user device 1006 corresponds to a digital assistant trigger that is detected 30 seconds after the public device 1004 detects the digital assistant trigger included in the user voice input 1014, and (2) the predetermined time range is 500 milliseconds before the digital assistant trigger end time corresponding to the digital assistant trigger detected by the user device 1006. In this example, the digital assistant trigger end time of the public device 1004 clearly does not fall within the 500 millisecond time range before the digital assistant trigger end time of the user device 1006. Therefore, the user voice input received by the user device 1006 represents a separate user request that the user device 1006 should continue to process (e.g., separate from the user request of the user voice input 1014).

[0321] return Figure 9In some examples, user voice input 918 does not include a digital assistant trigger. For example, public device 904 may receive user voice input 918 during a digital assistant conversation session initiated in response to user 902 pressing or holding a physical button on public device 904. In these examples, public device 904 determines that user voice input 918 represents a digital assistant request and begins processing user voice input 918 (e.g., as indicated by arrow 920) to determine and / or obtain a response to user voice input 918 without determining whether it should suppress detection of a digital assistant trigger (e.g., as described above with reference to Figure 10 Note that in these examples, initiating the digital assistant conversation session via pressing or holding a physical button on public device 904 represents a device state change, and thus public device 904 sends context information (and a device identifier corresponding to public device 904) to public device 908 in response to initiating the conversation session.

[0322] As indicated by arrow 920, in response to receiving user voice input 918 (or, in some examples, in response to detecting a digital assistant trigger included in user voice input 918), public device 904 sends (via network 912) to public device 908 (i.e., the context collector for context sharing group 914) a request for public device 908 to send the aggregated context of context sharing group 914 to public device 904. Because the detection of the digital assistant trigger is a device state change, public device 904 also sends the context information (and a device identifier corresponding to public device 904) to public device 908 before sending the request for the aggregated context (although this step is not included in the description). Figure 9 shown in ).

[0323] As shown by arrow 922, after receiving a request for an aggregated context from public device 904, public device 908 sends the aggregated context (or, in some examples, at least a portion of the aggregated context) to public device 904. In some examples, the request for the aggregated context causes public device 908 to send the aggregated context (e.g., data corresponding to the aggregated context) or at least a portion of the aggregated context to public device 904. The aggregated context sent to public device 904 includes context information (e.g., device state change information, context state information, device capability information, etc.) associated with at least public device 904, user device 906, and user device 910 (e.g., because public device 904, user device 906, and user device 910 each recently sent context information to public device 908 in response to experiencing a device state change (e.g., a timer event). Specifically, the context information is associated with at least public device 904, user device 906, and user device 910 based on a device identifier that public device 908 receives along with the context information from at least public device 904, user device 906, and user device 910. In some examples, the aggregated context does not include any other type of device identification or identifying information other than the device identifier received with the context information included in the aggregated context. This, in turn, helps ensure the anonymity of the electronic devices participating in the context sharing group 914 when the aggregated context is received by the server 916 (e.g., as indicated by arrow 924).

[0324] In other examples, the aggregate context does include (in addition to the device identification) other types of device identification and / or information identifying the registered user of each electronic device. This, in turn, allows the server 916 to determine whether the electronic devices participating in the context sharing group are registered to a single user or to two or more different users (because this information may affect the commands provided by the server 916). In some examples, the device identification and / or information identifying the registered user of each electronic device included in the aggregate context allows the server 916 to determine whether the user voice input is provided by a registered user. In addition, as described below, in some examples, the server 916 uses this additional identification information to access and / or utilize user data stored on the server 916 and associated with one or more electronic devices in the electronic devices (e.g., user data that the electronic devices participating in the context sharing group 914 previously synchronized / sent to the remote device (e.g., during automatic and / or periodic user data synchronization)).

[0325] As indicated by arrow 924 , after receiving the aggregated context from the public device 908 , the public device 904 provides (eg, transmits) data corresponding to the user voice input 918 and at least a portion of the aggregated context to the server 916 .

[0326] In some examples, the public device 904 provides audio data corresponding to the user voice input 918 to the server 916. In some examples, the public device 904 performs speech-to-text processing of the user voice input 918 (e.g., using the STT processing module 730) and provides text data corresponding to the user voice input 918 (e.g., a text representation of the user voice input 918) to the server 916. In some examples, the public device 904 also performs natural language processing of the text data corresponding to the user voice input 918 (e.g., using the natural language processing module 732) and provides the results of the natural language processing (e.g., one or more user intents) to the server 916.

[0327] In some examples, the public device 904 provides all aggregated context to the server 916. In some examples, the public device 904 determines which context information included in the aggregated context is relevant to the user voice input 918 (e.g., when the public device 904 performs natural language processing of the user voice input 918) and provides only the relevant context information to the server 916. In some examples, the public device 904 determines which context information is relevant based on one or more domains of an active knowledge ontology (e.g., knowledge ontology 760) corresponding to the user voice input 918 (e.g., by identifying context information that is relevant or associated with one or more domains corresponding to the user voice input 918). In some examples, the public device 904 removes personal information (e.g., email address, home address, payment information, etc.) and / or user data (e.g., user preferences, media, contacts, voice profile, etc.) included in the aggregated context before providing it to the server 916. In some examples, the public device 904 encrypts the personal information and / or user data included in the aggregated context before providing it to the server 916.

[0328] In some examples, before sending at least a portion of the aggregated context to the server 916, the public device 904 sends a request to the electronic devices participating in the context sharing group 914 (including the user device 906, the public device 908, and the user device 910) for each device to provide the public device 904 with an indication of whether it has detected a digital assistant trigger included in the user voice input 918. In some examples, the public device 904 requests each electronic device to provide the public device 904 with an indication of whether the electronic device has detected a digital assistant trigger within a predetermined time period (e.g., within the last 2 seconds, 5 seconds, or 10 seconds). In response to receiving the request, the electronic device sends the requested indication (also referred to as a trigger indication) along with its corresponding device identifier.

[0329] After receiving a trigger indication (indicating whether each of the one or more electronic devices in the electronic device participating in the context sharing group 914 detects a digital assistant trigger included in the user voice input 918) from one or more electronic devices (e.g., all), the public device 904 incorporates the trigger indication into the aggregate context based on the device identifier received with the trigger indication. Specifically, the public device 904 incorporates the trigger indication received from each electronic device into the context information of the electronic device included in at least a portion of the aggregate context (based on the device identifier of each electronic device). For example, the public device 904 incorporates the trigger indication received from the user device 906 into the context information associated with the device identifier of the user device 906 included in at least a portion of the aggregate context. In some examples, the trigger indication includes data indicating the energy level (e.g., decibel level) of the detected digital assistant trigger (e.g., the energy level of the digital assistant trigger when received by the electronic device). In some examples, the trigger indication includes a confidence score corresponding to the electronic device (e.g., the user device 906) regarding the confidence that the user voice input 918 includes the digital assistant trigger.

[0330] Note that in some examples, user devices participating in a context sharing group are unaware of other user devices that are also participating in the context sharing group (and are not context collectors). For example, user device 906 is unaware of user device 910. Therefore, in these examples, user devices cannot directly send trigger indication requests or trigger indications to other user devices. Therefore, in these examples, the user device sends a trigger indication request to the context collector of the context sharing group, allowing the context collector to send the trigger indication request to all other electronic devices participating in the context sharing group. The context collector then sends all received trigger indications back to the user device that sent the trigger indication request to the context collector. For example, to receive a trigger indication from user device 910, user device 906 sends a trigger indication request to public device 908, allowing public device 908 to send the trigger indication request to both user device 910 and public device 904. Consequently, the public device receives trigger indications from public device 904 and user device 910 and then sends those trigger indications (along with its own trigger indication) to user device 906. In some examples, the user device 906 sends the trigger indication request directly to the public device 904 (eg, in addition to sending the request to the public device 908 ) because the user device 906 is still aware that the public device participates in the context sharing group 914 .

[0331] As will be described in greater detail below, in some examples, server 916 determines the physical proximity of user device 906, public device 908, and / or user device 910 to public device 904 (e.g., within a particular location associated with context sharing group 914) based on trigger indications corresponding to user device 906, public device 908, and / or user device 910 included in the aggregated context. For example, based on the trigger indications (e.g., data included in the trigger indications), server 916 may determine whether user device 906 or public device 908 is closer to public device 904 and / or whether user device 906 or public device 908 is within the same area of the location associated with context sharing group 914 as public device 904 (e.g., within the same room or office). In some examples, each individual device determines its own physical proximity to public device 904. In these examples, the trigger indication includes data indicating the physical proximity of an associated electronic device (e.g., user device 906, public device 908, or user device 910) to the public device 904, and thus, based on the data included in the trigger indication, the server 916 is notified of the proximity of each device to the public device 904 (rather than the server 916 determining the physical proximity of each device to the public device 904).

[0332] As will be referenced below Figure 11 Described in more detail, upon receiving data corresponding to user voice input 918, server 916 (specifically, one or more modules of server 916) processes the data corresponding to user voice input 918 (e.g., based on the context information included in the aggregated context) and determines one or more user intents corresponding to the user voice input 918, one or more tasks corresponding to the one or more user intents, one or more electronic devices participating in the context sharing group 914 that will perform the one or more tasks, and one or more commands for performing the one or more tasks. Note that in some examples, the public device 904 does not send the data corresponding to the user voice input 918 and the aggregated context to the server 916. In these examples, the public device 904 (specifically, one or more modules of the public device) processes the data corresponding to the user voice input 918 (e.g., based on the context information included in the aggregated context) and performs the determinations listed above (rather than the server 916 performing them).

[0333] Figure 111 is a block diagram illustrating a system for task determination and device selection in a context sharing group according to various examples. System 1100 is implemented on one or more remote devices that are communicatively connected (e.g., via one or more networks (e.g., network 912)) to one or more electronic devices (e.g., one or more user devices and / or one or more public devices) participating in a context sharing group (e.g., context sharing group 914). For example, system 1100 is implemented on server 916. In some examples, system 1100 is implemented as one or more electronic devices (e.g., public device 904, user device 906, public device 908, and / or user device 910) participating in a context sharing group. In some examples, the modules and functions of system 1100 are distributed between the one or more remote devices and the one or more electronic devices participating in the context sharing group.

[0334] System 1100 is implemented using hardware, software, or a combination of hardware and software to perform the functions discussed herein. Furthermore, system 1100 is exemplary, and thus system 1100 may have more or fewer components than those shown, may combine two or more components, or may have a different configuration or arrangement of components. Although the following discussion describes functions performed at a single module of system 1100, it should be understood that these functions may be performed at other modules of system 1100, and that these functions may be performed at more than one module of system 1100.

[0335] To illustrate the examples discussed herein, refer to Figure 9 The various components of system 900 are described with reference to system 1100. Unless otherwise noted, system 1100 is implemented on server 916 in the examples described below.

[0336] System 1100 includes a voice input receiver module 1102. The voice input receiver module 1102 receives data corresponding to user voice input (e.g., audio data, text data, natural language processing results, etc.) from electronic devices participating in the context sharing group (e.g., from the public device 904). For example, the voice input receiver module 1102 receives data corresponding to user voice input 918 from the public device 904 (e.g., as shown by arrow 924). In some examples, the voice input receiver module 1102 receives user voice input directly from the user. For example, when the system 1100 or only the voice input receiver module 1102 is implemented on the public device 904, the voice input receiver module 1102 receives user voice input 918 directly from the user 902 (because the public device 904 receives user voice input 918 from the user 902). After the voice input receiver module 1102 receives the data corresponding to the user voice input, the voice input receiver module 1102 provides the data corresponding to the user voice input to the user intent module 1106.

[0337] System 1100 includes an aggregated context receiver module 1104. Aggregated context receiver module 1104 receives at least a portion of the aggregated context of the context sharing group from electronic devices participating in the context sharing group (e.g., from public device 904). As described above, at least a portion of the aggregated context includes one or more device identifiers corresponding to one or more electronic devices participating in the context sharing group. For example, aggregated context receiver module 1104 receives at least a portion of the aggregated context of context sharing group 914 from public device 904 (e.g., as shown by arrow 924). In some examples, aggregated context receiver module 1104 receives at least a portion of the aggregated context from a context collector of the context sharing group. For example, when system 1100 or only aggregated context receiver module 1104 is implemented on public device 904, aggregated context receiver module 1104 receives at least a portion of the aggregated context from public device 908 (the context collector of context sharing group 914) (because public device 904 receives at least a portion of the aggregated context from public device 908 (e.g., as shown by arrow 922)). After receiving at least a portion of the aggregated context of the context sharing group, the aggregated context receiver module 1104 provides the context information (e.g., device state change information, context state information and / or device capability information) and a device identifier associated with the context information to the user intent module 1106, the device selection module 1110 and / or the command module 1112.

[0338] The system 1100 includes a user intent module 1106. The user intent module 1106 determines one or more user intents based on data corresponding to the user voice input (received from the voice input receiver module 1102). For example, the user intent module 1106 determines one or more user intents based on data corresponding to the user voice input 918. After determining one or more user intents, the user intent module 1106 provides the one or more user intents to the task determination module 1108.

[0339] In some examples, determining one or more user intents includes the user intent module 1106 performing speech-to-text processing, natural language processing, etc. based on data corresponding to the user voice input. In these examples, the user intent module 1106 includes a speech-to-text processing module (e.g., the STT processing module 730), a natural language processing module (e.g., the natural language processing module 732), etc. For example, if the data corresponding to the user voice input 918 is audio data (e.g., an audio signal of the user voice input 918), then determining one or more user intents includes the user intent module 1106 performing speech-to-text processing based on the audio data. For another example, if the data corresponding to the user voice input 918 is text data (e.g., a text representation of the user voice input 918), then determining one or more user intents includes the user intent module 1106 performing natural language processing based on the text data (but not speech-to-text processing because the user voice input 918 has already been recognized (e.g., recognized by the public device 904)).

[0340] In some examples where user intent module 1106 performs speech-to-text processing on data corresponding to user voice input, user intent module 1106 determines one or more recognition results (e.g., one or more candidate text representations) corresponding to the user voice input based on user data associated with the user providing the user voice input (e.g., stored contacts, user voice profiles, media (e.g., songs), etc.). For example, if user voice input 918 includes a unique and / or uncommon word and / or name (e.g., "Hey, Siri, call Daenerys Targaryen."), user intent module 1106 may utilize voice profile data associated with user 902 (e.g., voice profile data associated with stored contacts of user 902) to identify the unique and / or uncommon word and / or name. For example, user intent module 1106 may match the utterance "Daenerys Targaryen" included in user voice input 918 (e.g., an audio signal or intermediate recognition result corresponding to the utterance) with the utterance of the stored contact name "Daenerys Targaryen" included in the user voice profile of user 902.

[0341] In some examples, the user data utilized by the user intent module 1106 includes user data stored on an electronic device that provides data corresponding to the user voice input to the voice input receiver module 1102 (e.g., the public device 904). For example, when sending data corresponding to the user voice input 918 to the server 916, the public device 904 may send the stored user data to the server 916 (e.g., the user data may be included in the aggregate context). The user intent module 1106 may then access and utilize the user data. In some examples, the user data utilized by the user intent module 1106 includes user data stored on a remote device (e.g., the server 916) that is implementing the user intent module 1106. For example, the user data may already be stored on the server 916 because the public device 904 has previously synchronized / sent the user data to the server 916 (e.g., during automatic and / or periodic user data synchronization).

[0342] In some examples, the user data utilized by the user intent module 1106 includes user data associated with an electronic device that (1) participates in the context sharing group and (2) does not provide data corresponding to the user voice input to the voice input receiver module 1102. For example, the user data used by the user intent module 1106 when performing speech-to-text processing of data corresponding to the user voice input 918 may include user data that the user device 906 previously synchronized / sent to the server 916. For example, if the user voice input 918 includes the unique name "Daenerys Targaryen," the user intent module 1106 may recognize the unique name based on voice profile data associated with the user 902 that the user device 906 previously synchronized / sent to the server 916. In this example, the user data associated with the user device 906 is not stored on the public device 904 and is not synchronized / sent to the server 916 by the public device 904.

[0343] In some examples, an electronic device (e.g., user device 906, public device 908, or user device 910) that participates in a context sharing group and does not provide data corresponding to the user voice input to the voice input receiver module 1102 must be registered to the user (e.g., user 902) that provided the user voice input so that the user intent module 1106 can utilize the user data associated with the electronic device. For example, if the user device 906 is not registered to the user 902, the user intent module 1106 will not be able to utilize the user data associated with the user device 906 to recognize the unique name "Daenerys Targaryen" included in the user voice input 918. In some examples, the user intent module 1106 only utilizes user data from the former electronic device if the electronic device registered to the user providing the user voice input participates in the same context sharing group as the electronic device receiving the user voice input. For example, if the electronic device registered to the user 902 does not participate in the context sharing group 914, the user intent module 1106 cannot access the user data associated with the electronic device when processing data corresponding to the user voice input 918. For another example, if user device 906 is registered to user 902, but user device 906 leaves context sharing group 914 (e.g., by disconnecting from network 912) before user intent module 1106 receives data corresponding to user voice input 918, user intent module 1106 will not be able to utilize user data associated with user device 906 (e.g., stored on server 916) to recognize user voice input 918. Note that in some examples, public devices (e.g., public device 904) do not store user data and / or do not synchronize user data to a remote device (e.g., server 916). In these examples, user intent module 1106 can only access and utilize user data associated with the user device (e.g., user device 906 and / or user device 910) that is registered to the user who provided the user voice input.

[0344] As described above, aggregate context receiver module 1104 provides context information (e.g., device state change information, context state information, and / or device capability information) and a device identifier associated with the context information to user intent module 1106. In some examples, user intent module 1106 further determines one or more user intents based on the context information (associated with one or more electronic devices) received from aggregate context receiver module 1104.

[0345] In some examples, determining one or more user intents based on contextual information included in at least a portion of the aggregated context further includes disambiguating the user voice input based on the contextual information by the user intent module 1106. For example, if the user voice input 918 is ambiguous with respect to the task requested by the user (e.g., “Hey, Siri, stop.” is ambiguous with respect to what task the user 902 wants the device to perform because it is unclear whether the user 902 wants to stop media playback, stop an alarm, stop a timer, etc.), the user intent module 1106 can use device state change information associated with the public device 904, the user device 906, the public device 908, and / or the user device 910 (e.g., the type of device state change and / or the time of the device state change) to determine what task the user 902 referred to in the user voice input 918 / disambiguate the task. For example, if the device state change information associated with the user device 906 (e.g., data indicating the type of device state change at the user device 906) indicates that a timer event is currently occurring at the user device 906 (e.g., a timer is sounding at the user device 906), the user intent module 1106 may determine that the user 902 wants to stop the timer event at the user device 906. Therefore, in this example, the user intent module 1106 will determine the user intent to stop the timer.

[0346] In some examples, when user voice input is ambiguous with respect to the task requested by the user and two or more events (e.g., timer events, alarm events, media playback, etc.) occur at two or more independent electronic devices in the context sharing group, the user intent module 1106 uses device state change time information (e.g., data indicating the time when each event started) to determine one or more user intents based on the most recent device state change. For example, if in the above example (where user voice input 918 is "Hey, Siri, stop."), the device state change information also indicates that there is an ongoing media playback event at the public device 904 (e.g., the public device 904 is currently playing music while a timer goes off at the user device 906 (e.g., in another room)), the user intent module 1106 can disambiguate the user voice input 918 based on the device state change time information indicating the time when each event started. Specifically, the user intent module 1106 can determine which event started most recently based on the device state change time data because that event is the event that the user 902 is most likely referring to. Thus, if the timer event at the user device 906 started more recently than the media playback event at the public device 904, the user intent module 1106 will determine a user intent to stop the timer rather than a user intent to stop media playback.

[0347] In some examples, when user voice input is ambiguous with respect to the task requested by the user and two or more events (e.g., timer events, alarm events, media playback, etc.) occur at two or more independent electronic devices in a context sharing group, the user intent module 1106 uses device state change type information (e.g., data indicating the type of event) to determine one or more user intents based on the types of events occurring at the two or more independent electronic devices. Specifically, in these examples, the user intent module 1106 determines one or more user intents based on an event priority rule that indicates which event types are prioritized when determining user intent. For example, an event type priority rule may indicate that an alarm event takes precedence over a media playback event. Thus, if in the example above (where the user voice input 918 is “Hey, Siri, stop.”), the device state change information also indicates that there is a media playback event occurring at the public device 904 (e.g., the public device 904 is currently playing music and a timer goes off on the user device 906 (e.g., in another room)), the user intent module 1106 can disambiguate the user voice input 918 based on the event priority rules, thereby determining the user intent to stop the timer rather than the user intent to stop media playback (because the timer event takes precedence over the media playback event).

[0348] Similarly, in yet another example, if user voice input 918 is “Hey, Siri, resume.” and device state change information included in at least a portion of the aggregated context indicates that music previously playing at user device 906 stopped 10 minutes ago, while a movie playing at public device 908 stopped 5 minutes ago (because stopping or pausing media playback is a device state change), user intent module 1106 will determine, based on the device state change time data, that the movie playing at public device 908 stopped or paused more recently. Therefore, user intent module 1106 will determine the user intent to resume the movie rather than the user intent to resume the music.

[0349] As will be referenced below Figure 13 Described in more detail, in some examples, the user intent module 1106 uses one or more digital assistant conversation session histories associated with one or more electronic devices (included in an aggregate context) to disambiguate user voice input and determine one or more user intents corresponding to the user voice input.

[0350] System 1100 includes a task determination module 1108. Task determination module 1108 determines one or more tasks to be performed by one or more electronic devices participating in the context sharing group based on one or more user intents received from user intent module 1106. For example, based on one or more user intents determined by user intent module 1106 based on data corresponding to user voice input 918 received by voice input receiver module 1102 (and, in some examples, also based on context information included in the aggregated context received by aggregated context receiver module 1104), task determination module 1108 determines one or more tasks to be performed by public device 904, user device 906, public device 908, and / or user device 910. After determining one or more tasks, task determination module 1108 provides the one or more tasks and the one or more user intents to device selection module 1110.

[0351] As will be described in more detail below, the one or more tasks are performed by one or more electronic devices participating in the context sharing group to satisfy the one or more user intents. For example, if the user intent module 1106 determines a user intent to stop an alarm (e.g., based on user voice input "Hey, Siri, stop." or "Hey, Siri, stop the alarm."), the task determination module 1108 will determine one or more tasks that, when performed by the electronic device, will cause the electronic device to stop the alarm. In some examples, the one or more tasks determined by the task determination module 1108 are predetermined based on one or more user intents (e.g., the determined user intent corresponds to one or more tasks). Examples of one or more tasks that may be determined by the task determination module 1108 include performing a search, retrieving information / data, opening an application stored on an electronic device, playing media (e.g., songs, videos, movies, etc.), making a purchase, user authentication, displaying retrieved information / data, and the like.

[0352] As will be referenced below Figure 13 Described in more detail, in some examples, the task determination module 1108 uses one or more digital assistant conversation session histories associated with one or more electronic devices to disambiguate user voice input and determine one or more parameters of one or more tasks determined based on user intent corresponding to the user voice input.

[0353] The system 1100 includes a device selection module 1110. The device selection module 1110 selects / identifies one or more electronic devices participating in the context sharing group to perform one or more tasks (received from the task determination module 1108) based at least on the context information included in the aggregated context (received from the aggregated context receiver module 1104). For example, the device selection module 1110 may select one electronic device (e.g., user device 906) participating in the context sharing group 914 to perform the one or more tasks. For another example, as will be described below with reference to FIG. 12A to FIG. 12B Discussed in more detail, the device selection module 1110 may select two or more electronic devices (e.g., the public device 904 and the user device 906) participating in the context sharing group 914 to each perform at least one task (e.g., when the task determination module 1108 determines at least two tasks). In some examples, the device selection module 1110 selects an electronic device (e.g., the public device 904) that provides data corresponding to the user's voice input to the voice input receiver module 1102. In some examples, the device selection module 1110 selects an electronic device (e.g., the user device 906, the public device 908, and / or the user device 910) that does not provide data corresponding to the user's voice input to the voice input receiver module 1102. In some examples, the device selection module 1110 selects a context collector (e.g., the public device 908) for the context sharing group.

[0354] After receiving one or more tasks, one or more user intents, and an aggregated context, the device selection module 1110 determines, based on device state change information included in the aggregated context (e.g., device state change information associated with one or more electronic devices participating in the context sharing group), whether an event corresponding to the user intent in the one or more user intents (e.g., a timer event, an alarm event, media playback, etc.) is currently occurring at one or more electronic devices participating in the context sharing group. For example, if the device selection module 1110 receives a user intent to stop a timer (e.g., based on user voice input "Hey, Siri, stop."), the user intent module 1110 determines, based on the device state change information (e.g., data indicating the type of device state change) (e.g., associated with the device identifiers of the one or more electronic devices included in the aggregated context), whether a timer event is currently occurring at the one or more electronic devices. For another example, if the device selection module 1110 receives a user intent to play the next song (e.g., based on user voice input "Hey, Siri, play the next song"), the device selection module 1110 determines, based on the device state change information associated with the electronic devices, whether a music playback event is currently occurring at the one or more electronic devices.

[0355] If the device selection module 1110 determines that an event corresponding to the user's intention is currently occurring at a single electronic device participating in the context sharing group, the device selection module 1110 selects the single electronic device (at which the event occurs) to perform one or more tasks.

[0356] If the device selection module 1110 determines that an event corresponding to the user intent is currently occurring at two or more electronic devices participating in the context sharing group, the device selection module 1110 determines which event (of the two or more events) started most recently based on data indicating the time of the device state change included in the device state change information associated with the two or more electronic devices. For example, if the device selection module 1110 receives a user intent to stop an alarm (e.g., based on user voice input "Hey, Siri, stop.") and the device selection module 1110 determines that an alarm event is occurring at user device 906 and user device 910 (i.e., a separate alarm is sounding at each device), the device selection module 1110 determines (based on the device state change data indicating the start time of each alarm event) whether the alarm event at user device 906 started more recently than the alarm event at user device 910. Then, after the device selection module 1110 determines which event (of the two or more events) started most recently, the device selection module 1110 selects the electronic device where the event started most recently to perform one or more tasks. Returning to the previous example, if the device selection module 1110 determines that the alarm event at the user device 910 started more recently than the alarm event at the user device 906 (for example, the alarm at the user device 910 started ringing when the alarm at the user device 906 had already sounded), the device selection module 1110 will select the user device 910 (specifically, the device selection module 1110 will select the device identifier corresponding to the user device 910).

[0357] In some examples, if the device selection module 1110 determines that an event corresponding to the user intent is currently occurring at two or more electronic devices participating in the context sharing group, the device selection module 1110 determines which of the two or more electronic devices is physically closest to the electronic device that provided the user voice input data to the voice input receiver module 1102 based on the proximity information included in the aggregated context. The device selection module 1110 then selects the electronic device that is physically closest to the electronic device that provided the user voice input data. For example, if the device selection module 1110 receives a user intent to stop an alarm (e.g., based on the user voice input "Hey, Siri, stop.") and the device selection module 1110 determines that an alarm event is occurring at both user device 906 and user device 910 (i.e., a separate alarm is sounding at each device), the device selection module 1110 determines (based on the proximity information associated with user device 906 and user device 910) whether user device 906 or user device 910 is physically closest to the common device 904. Then, if the device selection module 1110 determines that the user device 906 is physically closest to the public device 904 , the device selection module 1110 will select the user device 906 .

[0358] In some examples, the device selection module 1110 determines, based on device state change information included in the aggregated context (e.g., device state change information associated with one or more electronic devices participating in the context sharing group), whether an event corresponding to the user intent in the one or more user intents previously occurred at one or more electronic devices (participating in the context sharing group) within a predetermined time period (e.g., within the last 5 minutes, 10 minutes, 30 minutes, etc.). For example, if the one or more user intents include a user intent to resume movie playback, and the predetermined time period is 10 minutes, the device selection module 1110 determines whether the movie was paused at one or more electronic devices in the electronic devices participating in the context sharing group 914 within the last 10 minutes (based on the type of device state change and the time of the device state change indicated in the device state change information), because the event of pausing the movie corresponds to the user intent to resume movie playback. In some examples, the device selection module 1110 makes this determination in response to determining that the event corresponding to the user intent in the one or more user intents is not currently occurring at the one or more electronic devices participating in the context sharing group. In some examples, in response to determining that one or more user intents include a user intent to resume media playback (e.g., to resume music playback, movie playback, etc.), the device selection module 1110 determines whether an event corresponding to the user intent in the one or more user intents previously occurred at one or more electronic devices. In some of these examples, in response to determining that one or more user intents include a user intent to resume media playback, the device selection module 1110 determines whether an event corresponding to the user intent in the one or more user intents previously occurred at one or more electronic devices within a predetermined time period, rather than determining whether an event corresponding to the user intent in the one or more user intents is currently occurring at the one or more electronic devices.

[0359] In the above example, if the device selection module 1110 determines that an event corresponding to the user intent in the one or more user intents previously occurred at a single electronic device participating in the context sharing group within a predetermined time period, the device selection module 1110 selects the single electronic device (at which the event previously occurred) to perform one or more tasks. For example, if the user intent is to resume music playback and the device selection module 1110 determines that the public device 904 is the only electronic device participating in the context sharing group 914 that paused music playback within a predetermined time period (e.g., 30 minutes), the device selection module 1110 selects the public device 904.

[0360] Alternatively, if the device selection module 1110 determines that an event corresponding to the user intent in the one or more user intents previously occurred at two or more electronic devices participating in the context sharing group within a predetermined time period, the device selection module 1110 determines which of the two or more electronic devices is physically closest to the electronic device that provided the user voice input data to the voice input receiver module 1102 based on the proximity information included in the aggregated context (e.g., proximity information associated with the one or more electronic devices participating in the context sharing group) (e.g., because the electronic device may be the device closest to the user providing the user voice input). Returning to the previous example, if the device selection module 1110 determines that the user device 906 also paused music playback within the predetermined time period (in addition to the public device 904), the device selection module 1110 will determine whether the user device 906 or the public device 904 is closer to the public device 904 (i.e., the device that provided data corresponding to the user voice input 918 to the voice input receiver module 1102). In this case, the public device 904 is the closest device because the public device 904 itself provided data corresponding to the user voice input 918 to the voice input receiver module 1102. Thus, in this example, the device selection module 1110 will select the public device 904 to perform one or more tasks. Determining which electronic device was most recently located in these examples will prevent the selection (e.g., and subsequent resumption of media playback) of an electronic device that is located in a completely different area (e.g., different from where the user is) of the location associated with the context sharing group.

[0361] In some examples, the proximity information is based on data included in one or more trigger indications included in the aggregated context (e.g., associated with one or more electronic devices participating in the context sharing group). Specifically, as described above, each trigger indication includes data indicating whether the electronic device detects a digital assistant trigger included in the user voice input, such as data indicating an energy level (e.g., a decibel level) of the detected digital assistant trigger (e.g., the energy level of the digital assistant trigger when received by the electronic device). In these examples, determining which of the two or more electronic devices is physically closest to the electronic device that provides the user voice input data to the voice input receiver module 1102 includes: the device selection module 1110 compares the digital assistant trigger energy levels of the two or more electronic devices and determines which electronic device corresponds to the highest energy level. The device selection module then selects the electronic device with the highest digital assistant trigger energy level to perform one or more tasks.

[0362] In some examples, the device selection module 1110 determines which of the two or more electronic devices is physically closest to the electronic device providing the user voice input data to the voice input receiver module 1102 based on contextual state information included in the aggregated context (e.g., instead of or in addition to proximity information). Specifically, in examples where the contextual state information includes the current location of the electronic devices participating in the context sharing group (e.g., based on GPS data from the GPS module 235 and / or from a software application with context sharing group functionality (e.g., ), the device selection module 1110 compares the current locations of the two or more electronic devices and, based on the comparison, determines which electronic device is physically closest to the electronic device that provides voice input data to the voice input receiver module 1102. The device selection module 1110 then selects the closest electronic device to perform one or more tasks.

[0363] In some examples, if the device selection module 1110 determines, based on the proximity information and / or context state information included in the aggregate context, that the two or more electronic devices are physically equally close to the electronic device providing the user voice input data to the voice input receiver module 1102, then the device selection module 1110 selects the two or more electronic devices (rather than selecting a single electronic device). In some examples, if the difference between the corresponding digital assistant trigger energy levels is less than a predetermined threshold (e.g., less than 5 decibels), then the two or more electronic devices are physically equally close to the electronic device providing the user voice input data to the voice input receiver module 1102. For example, if the digital assistant trigger energy levels of the public device 904 and the user device 906 are 40 decibels and 42 decibels, respectively, and the predetermined threshold is 5 decibels, then the device selection module 1110 will determine that the public device 904 and the user device 906 are physically equally close to the public device 904 (i.e., the device providing data corresponding to the user voice input 918). In some examples, if the context state information associated with each of two or more electronic devices indicates that the two or more electronic devices are each currently located within the same area (e.g., the same room, the same office, etc.) of the location associated with the context sharing group, then the two or more electronic devices are physically equally close to the electronic device that provides user voice input data to the voice input receiver module 1102.

[0364] In some examples, in response to determining that an event corresponding to a user intent in one or more user intents previously occurred at two or more electronic devices within a predetermined time period, the device selection module 1110 simply selects the two or more electronic devices, rather than determining which of the two or more electronic devices is physically closest to the electronic device that provides user voice input data to the voice input receiver module 1102.

[0365] As will be described in more detail below, when the device selection module 1110 selects two or more electronic devices in the above example, the device selection module 1110 provides to the command module 1112 (1) device identifiers corresponding to the two or more electronic devices, (2) one or more tasks, and (3) instructions for providing commands that cause the electronic device (e.g., the common device 904) that provides user voice input data to the voice input receiver module 1102 to output a query requesting the user to select an electronic device from the two or more electronic devices to perform the one or more tasks.

[0366] If the device selection modu...

Claims

1. A method for performing one or more tasks in a context sharing group, comprising: At a first electronic device participating in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of the at least two electronic devices sharing context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device and a context collector, wherein at least the first electronic device and the second electronic device provide the context information to be included in an aggregated context to the context collector, and wherein the first electronic device and the second electronic device each provide their respective context information to the context collector in response to experiencing a device state change: Receive user voice input; receiving the aggregated context of the context sharing group from the context collector; After receiving the aggregated context, providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device that is not participating in the context sharing group; receiving, from the remote device, a command to perform one or more tasks and a device identifier corresponding to the second electronic device, wherein the remote device determines the one or more tasks and the device identifier based on the data corresponding to the user voice input and context information included in the at least a portion of the aggregated context; as well as The command is sent to the second electronic device based on the device identifier, wherein the command causes the second electronic device to perform the one or more tasks. 2 . The method of claim 1 , wherein each electronic device participating in the context sharing group is connected to a single wireless network at the first location. The method according to claim 1 , wherein the second electronic device is the context collector. The method according to claim 1 , wherein the context collector is a third electronic device participating in the context sharing group.

5. The method according to any one of claims 1 to 4, further comprising: In response to receiving the user voice input, a request is sent to the context collector for the context collector to send the aggregate context of the context sharing group to the first electronic device, wherein the request causes the context collector to send the aggregate context to the first electronic device. 6 . The method according to claim 1 , wherein the context information includes device state change information corresponding to at least the first electronic device and the second electronic device. 7 . The method according to claim 1 , wherein the context information comprises context state information corresponding to at least the first electronic device and the second electronic device. 8 . The method according to claim 1 , wherein the context information includes device capability information corresponding to at least the first electronic device and the second electronic device.

9. A method according to any one of claims 1 to 4, wherein the command also causes the second electronic device to output a user query after performing the one or more tasks, and wherein the user query inquires whether to send a second command for performing the one or more tasks to a fourth electronic device participating in the context sharing group.

10. A method according to any one of claims 1 to 4, wherein the user voice input is ambiguous with respect to defining the electronic device that will respond to the user voice input, and wherein the remote device disambiguates the user voice input based on the context information included in at least a portion of the aggregate context.

11. A method according to any one of claims 1 to 4, wherein the first electronic device and the second electronic device are both personal electronic devices each registered to a single user, and wherein the remote device eliminates ambiguity of one or more words included in the user voice input based on user data associated with the second electronic device.

12. The method according to any one of claims 1 to 4, wherein the first electronic device and the second electronic device are both personal electronic devices registered to different users, the method further comprising: Before sending the command to the second electronic device: Output a request for user authentication; as well as Authentication data is received from a user of the first electronic device, wherein the first electronic device sends the command in response to determining that the user of the first electronic device is an authorized user of the second electronic device based on the received authentication data.

13. The method according to any one of claims 1 to 4, wherein the context sharing group further includes a fourth electronic device, and wherein the first electronic device, the second electronic device, and the fourth electronic device are all personal electronic devices, and the first electronic device, the second electronic device, and the fourth electronic device are each registered to a single user, the method further comprising: receiving user data associated with the fourth electronic device from the remote device before sending the command to the second electronic device; as well as The user data is sent to the second electronic device along with the command, wherein the command causes the second electronic device to perform the one or more tasks based on the user data.

14. The method of any one of claims 1 to 4, wherein the user voice input comprises a digital assistant trigger, the method further comprising: Prior to sending the at least a portion of the aggregated context to the remote device: sending a request to the second electronic device for the second electronic device to provide an indication to the first electronic device, the indication being whether the second electronic device detects the digital assistant trigger included in the user voice input; as well as After receiving the indication from the second electronic device, incorporating the indication into context information associated with the second electronic device included in the aggregated context, wherein the remote device determines the physical proximity of the second electronic device to the first electronic device based on the indication.

15. A first electronic device, comprising: one or more processors; 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, wherein the one or more programs include instructions for: when the first electronic device participates in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of the at least two electronic devices sharing context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device and a context collector, wherein at least the first electronic device and the second electronic device provide the context information to be included in an aggregated context to the context collector, and wherein the first electronic device and the second electronic device each provide their respective context information to the context collector in response to experiencing a device state change: Receive user voice input; receiving the aggregated context of the context sharing group from the context collector; After receiving the aggregated context, providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device that is not participating in the context sharing group; receiving, from the remote device, a command to perform one or more tasks and a device identifier corresponding to the second electronic device, wherein the remote device determines the one or more tasks and the device identifier based on the data corresponding to the user voice input and context information included in the at least a portion of the aggregated context; as well as The command is sent to the second electronic device based on the device identifier, wherein the command causes the second electronic device to perform the one or more tasks. 16 . The first electronic device of claim 15 , wherein each electronic device participating in the context sharing group is connected to a single wireless network at the first location. The first electronic device according to claim 15 , wherein the second electronic device is the context collector. 18 . The first electronic device of claim 15 , wherein the context collector is a third electronic device participating in the context sharing group.

19. The first electronic device according to any one of claims 15 to 18, wherein the one or more programs include further instructions for: In response to receiving the user voice input, a request is sent to the context collector for the context collector to send the aggregate context of the context sharing group to the first electronic device, wherein the request causes the context collector to send the aggregate context to the first electronic device. 20 . The first electronic device according to claim 15 , wherein the context information includes device state change information corresponding to at least the first electronic device and the second electronic device. 21 . The first electronic device according to claim 15 , wherein the context information comprises context state information corresponding to at least the first electronic device and the second electronic device. 22 . The first electronic device according to claim 15 , wherein the context information includes device capability information corresponding to at least the first electronic device and the second electronic device.

23. A first electronic device according to any one of claims 15 to 18, wherein the command also causes the second electronic device to output a user query after performing the one or more tasks, and wherein the user query inquires whether a second command for performing the one or more tasks is sent to a fourth electronic device participating in the context sharing group.

24. A first electronic device according to any one of claims 15 to 18, wherein the user voice input is ambiguous with respect to defining the electronic device that will respond to the user voice input, and wherein the remote device disambiguates the user voice input based on the context information included in at least a portion of the aggregate context.

25. A first electronic device according to any one of claims 15 to 18, wherein the first electronic device and the second electronic device are both personal electronic devices each registered to a single user, and wherein the remote device eliminates ambiguity of one or more words included in the user voice input based on user data associated with the second electronic device.

26. The first electronic device of any one of claims 15 to 18, wherein the first electronic device and the second electronic device are both personal electronic devices each registered to a different user, and wherein the one or more programs include further instructions for: Before sending the command to the second electronic device: outputting a request for user authentication; and Authentication data is received from a user of the first electronic device, wherein the first electronic device sends the command in response to determining that the user of the first electronic device is an authorized user of the second electronic device based on the received authentication data.

27. The first electronic device of any one of claims 15 to 18, wherein the context sharing group further includes a fourth electronic device, wherein the first electronic device, the second electronic device, and the fourth electronic device are all personal electronic devices, the first electronic device, the second electronic device, and the fourth electronic device are each registered to a single user, and wherein the one or more programs include additional instructions for: receiving user data associated with the fourth electronic device from the remote device before sending the command to the second electronic device; and The user data is sent to the second electronic device along with the command, wherein the command causes the second electronic device to perform the one or more tasks based on the user data.

28. The first electronic device of any one of claims 15 to 18, wherein the user voice input comprises a digital assistant trigger, and wherein the one or more programs comprise further instructions for: Prior to sending the at least a portion of the aggregated context to the remote device: sending a request to the second electronic device for the second electronic device to provide an indication to the first electronic device, the indication being whether the second electronic device detects the digital assistant trigger included in the user voice input; and After receiving the indication from the second electronic device, incorporating the indication into context information associated with the second electronic device included in the aggregated context, wherein the remote device determines the physical proximity of the second electronic device to the first electronic device based on the indication.

29. A computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by one or more processors of a first electronic device, cause the first electronic device to perform the following operations: when the first electronic device participates in a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices, each of the at least two electronic devices sharing context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device and a context collector, wherein at least the first electronic device and the second electronic device provide the context information to be included in an aggregated context to the context collector, and wherein the first electronic device and the second electronic device each provide their respective context information to the context collector in response to experiencing a device state change: Receive user voice input; receiving the aggregated context of the context sharing group from the context collector; After receiving the aggregated context, providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device that is not participating in the context sharing group; receiving, from the remote device, a command to perform one or more tasks and a device identifier corresponding to the second electronic device, wherein the remote device determines the one or more tasks and the device identifier based on the data corresponding to the user voice input and context information included in the at least a portion of the aggregated context; as well as The command is sent to the second electronic device based on the device identifier, wherein the command causes the second electronic device to perform the one or more tasks.

30. The computer-readable storage medium of claim 29, wherein each electronic device participating in the context sharing group is connected to a single wireless network at the first location.

31. The computer-readable storage medium of claim 29, wherein the second electronic device is the context collector.

32. The computer-readable storage medium of claim 29, wherein the context collector is a third electronic device participating in the context sharing group.

33. The computer-readable storage medium of any one of claims 29 to 32, wherein the one or more programs include further instructions that, when executed by one or more processors of the first electronic device, cause the first electronic device to: In response to receiving the user voice input, a request is sent to the context collector for the context collector to send the aggregate context of the context sharing group to the first electronic device, wherein the request causes the context collector to send the aggregate context to the first electronic device.

34. The computer-readable storage medium according to any one of claims 29 to 32, wherein the context information includes device state change information corresponding to at least the first electronic device and the second electronic device.

35. The computer-readable storage medium according to any one of claims 29 to 32, wherein the context information includes context state information corresponding to at least the first electronic device and the second electronic device.

36. The computer-readable storage medium of any one of claims 29 to 32, wherein the context information includes device capability information corresponding to at least the first electronic device and the second electronic device.

37. A computer-readable storage medium according to any one of claims 29 to 32, wherein the command also causes the second electronic device to output a user query after performing the one or more tasks, and wherein the user query inquires whether a second command for performing the one or more tasks is to be sent to a fourth electronic device participating in the context sharing group.

38. A computer-readable storage medium according to any one of claims 29 to 32, wherein the user voice input is ambiguous with respect to defining the electronic device that will respond to the user voice input, and wherein the remote device disambiguates the user voice input based on the context information included in at least a portion of the aggregate context.

39. A computer-readable storage medium according to any one of claims 29 to 32, wherein the first electronic device and the second electronic device are both personal electronic devices each registered to a single user, and wherein the remote device eliminates ambiguity of one or more words included in the user voice input based on user data associated with the second electronic device.

40. The computer-readable storage medium of any one of claims 29 to 32, wherein the first electronic device and the second electronic device are both personal electronic devices, each registered to a different user, and wherein the one or more programs include further instructions that, when executed by one or more processors of the first electronic device, cause the first electronic device to: Before sending the command to the second electronic device: outputting a request for user authentication; and Authentication data is received from a user of the first electronic device, wherein the first electronic device sends the command in response to determining that the user of the first electronic device is an authorized user of the second electronic device based on the received authentication data.

41. The computer-readable storage medium of any one of claims 29 to 32, wherein the context sharing group further includes a fourth electronic device, wherein the first electronic device, the second electronic device, and the fourth electronic device are all personal electronic devices, the first electronic device, the second electronic device, and the fourth electronic device are each registered to a single user, and wherein the one or more programs include additional instructions that, when executed by one or more processors of the first electronic device, cause the first electronic device to: receiving user data associated with the fourth electronic device from the remote device before sending the command to the second electronic device; and The user data is sent to the second electronic device along with the command, wherein the command causes the second electronic device to perform the one or more tasks based on the user data.

42. The computer-readable storage medium of any one of claims 29 to 32, wherein the user voice input comprises a digital assistant trigger, and wherein the one or more programs comprise further instructions that, when executed by one or more processors of the first electronic device, cause the first electronic device to: Prior to sending the at least a portion of the aggregated context to the remote device: sending a request to the second electronic device for the second electronic device to provide an indication to the first electronic device, the indication being whether the second electronic device detects the digital assistant trigger included in the user voice input; and After receiving the indication from the second electronic device, incorporating the indication into context information associated with the second electronic device included in the aggregated context, wherein the remote device determines the physical proximity of the second electronic device to the first electronic device based on the indication.

43. An electronic device comprising: Device for carrying out the method according to any one of claims 1 to 14.

Images