CN112732622A

CN112732622A - Digital assistant hardware abstraction

Info

Publication number: CN112732622A
Application number: CN202011003469.2A
Authority: CN
Inventors: B·汉森; N·戈特比; 桂一枫; X·黄; B·S·菲普斯; E·雷; M·R·尚巴尔; J·泰卡罗; S·瓦特
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2020-05-11
Filing date: 2020-09-21
Publication date: 2021-04-30
Also published as: CN112732623A

Abstract

The present disclosure relates to digital assistant hardware abstraction. The present disclosure relates to intelligent automated assistants, and more particularly, to intelligent context sharing and task execution in 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 a user voice input; receiving an aggregated context for the context-sharing group from a context collector; providing, to a remote device, at least a portion of the aggregated context and data corresponding to the user voice input; receiving, from the remote device, a command to perform one or more tasks and a device identifier corresponding to a second electronic device; and transmitting 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

Digital assistant hardware abstraction

Statement of case division

The application is a digital assistant hardware abstract image with the application date of 9 and 21 months in 2020 and the application number of: 202010998524.X, a divisional application of the chinese invention patent application.

Technical Field

The present disclosure relates generally to intelligent automated assistants, and more particularly to intelligent context sharing and task execution in a set of devices with intelligent automated assistant capabilities.

Background

Intelligent automated assistants (or digital assistants) may provide a beneficial interface between a human user and an electronic device. Such assistants can allow users to interact with a device or system in speech and/or text form using natural language. For example, a user may provide a voice input containing a user request to a digital assistant that is running on an electronic device. The digital assistant can interpret the user intent from the speech input and manipulate the user intent into a task. These tasks may then be performed by executing one or more services of the electronic device, and relevant output responsive to the user request may be returned to the user.

Disclosure of Invention

A location such as a home or office may contain multiple devices with digital assistant capabilities. Thus, it may be desirable for the multiple devices to share context 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 occurring (and most recently occurring) at each device, the location of the user relative to each device, and/or what device capabilities are required for the tasks. In this way, a user-requested task may be performed at one of the plurality of devices even if the user does not directly provide the user request to the digital assistant of the device. This in turn 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.

Example methods are disclosed herein. An exemplary method includes, at a first electronic device: adding a context sharing group associated with a first location, wherein the context sharing group is a set of at least two electronic devices that each share 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, choosing one electronic device of the set of at least two electronic devices as a context collector for the context-sharing group, wherein choosing the context collector comprises: determining a first context collector score corresponding to the first electronic device based at least on a strength of connectivity between the first electronic device and a wireless network of the first location; receiving, from at least the second electronic device, one or more context collector scores corresponding to at least the second electronic device; and determining which of the electronic devices included in the context-sharing group to choose as the context collector of 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 accordance with a determination to choose 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.

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 that each share 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 a user voice input; receiving an aggregated context for 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 speech input to a remote device 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 contextual information included in the at least a portion of the aggregated context; and transmitting 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.

Another exemplary method includes, at one or more servers: receiving, from a first electronic device participating in a context-sharing group associated with a first location, a user speech input and at least a portion of an aggregated context of the context-sharing group, wherein the context-sharing group is a collection of a plurality of electronic devices that each share context information with at least one other electronic device included in the collection; determining a user intent based on the user speech input; determining one or more tasks corresponding to the user intent; identifying a second electronic device of the plurality of 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 aggregated context; and sending a command to a first electronic device to perform the one or more tasks and a device identifier corresponding to the second 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.

Another example 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 a plurality of electronic devices that each share context information with at least one other electronic device included in the set, and wherein the set includes a context collector: receiving a user voice input; receiving an aggregated context for 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 not participating in the context-sharing group, wherein the remote device determines a plurality of tasks based on the data corresponding to the user voice input; receiving, from the remote device: a first command to perform a first set of tasks of the plurality of tasks and a second command to perform a second set of tasks of the plurality of tasks; and a first device identifier corresponding to a second electronic device of the plurality of electronic devices and a second device identifier corresponding to a third electronic device of the plurality of 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 set 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 set of tasks.

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 that each share 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, at the first electronic device, a first digital assistant response based on the first user voice input, wherein the first electronic device sends contextual information comprising a digital assistant dialog session history for 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, at the second electronic device, an updated aggregated context for the context-sharing group from the context collector, wherein the updated aggregated context comprises the digital assistant dialog session history for the first electronic device; and outputting, at the second electronic device, a second digital assistant response based on the second user voice input and the digital assistant dialog history of the first electronic device.

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 collection of at least two electronic devices that each share context information with at least one other electronic device participating in the collection, and wherein the collection includes at least a second electronic device and a context collector: receiving a user voice input, wherein the user voice input comprises a digital assistant trigger; in response to detecting the digital assistant trigger, sending a first trigger advertisement to the context collector, wherein the first trigger advertisement indicates a first time at which the digital assistant trigger ended according to the first electronic device; receiving a second trigger advertisement from the context collector, wherein the second trigger advertisement indicates a second time at which the digital assistant trigger ended according to the second electronic device; determining whether the second time is within a predetermined time range prior to the first time; and in accordance with a determination that the second time is within the predetermined time range prior to the first time, forgoing further processing of the user speech input.

Example non-transitory computer-readable media are disclosed herein. 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: joining a context-sharing group associated with a first location, wherein the context-sharing group is a set of at least two electronic devices that each share 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, choosing one electronic device of the set of at least two electronic devices as a context collector for the context-sharing group, wherein choosing the context collector comprises: determining a first context collector score corresponding to the first electronic device based at least on a strength of connectivity between the first electronic device and a wireless network of the first location; receiving, from at least the second electronic device, one or more context collector scores corresponding to at least the second electronic device; and determining which of the electronic devices included in the context-sharing group to choose as the context collector of 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 in accordance with a determination to choose the first electronic device as the context collector, receive context information from at least the second electronic device in response to at least the second electronic device undergoing a device state change.

Another example non-transitory computer readable storage medium stores one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to: while the first electronic device is 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 that each share 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 a user voice input; receiving an aggregated context for 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 speech input to a remote device 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 contextual information included in the at least a portion of the aggregated context; and transmitting 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.

Another example non-transitory computer readable storage medium stores one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of one or more servers, cause the one or more servers to: receiving, from a first electronic device participating in a context-sharing group associated with a first location, a user speech input and at least a portion of an aggregated context of the context-sharing group, wherein the context-sharing group is a collection of a plurality of electronic devices that each share context information with at least one other electronic device included in the collection; determining a user intent based on the user speech input; determining one or more tasks corresponding to the user intent; identifying a second electronic device of the plurality of 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 aggregated context; and sending a command to a first electronic device to perform the one or more tasks and a device identifier corresponding to the second 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.

Another example non-transitory computer readable storage medium stores one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to: while the first electronic device is participating in a context-sharing group associated with a first location, wherein the context-sharing group is a collection of a plurality of electronic devices that each share context information with at least one other electronic device included in the collection, and wherein the collection includes a context collector: receiving a user voice input; receiving an aggregated context for the context-sharing group from the context collector; after receiving the aggregated upper context, providing at least a portion of the aggregated context and data corresponding to the user speech input to a remote device not participating in the context-sharing group, wherein the remote device determines a plurality of tasks based on the data corresponding to the user speech input; receiving, from the remote device: a first command to perform a first set of tasks of the plurality of tasks and a second command to perform a second set of tasks of the plurality of tasks; and a first device identifier corresponding to a second electronic device of the plurality of electronic devices and a second device identifier corresponding to a third electronic device of the plurality of 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 set of tasks; and transmitting 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 set of tasks.

A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to: 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 that each share 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, at the first electronic device, a first digital assistant response based on the first user voice input, wherein the first electronic device sends contextual information comprising a digital assistant dialog session history for 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, at the second electronic device, an updated aggregated context for the context-sharing group from the context collector, wherein the updated aggregated context comprises the digital assistant conversation session history for the first electronic device; and outputting, at the second electronic device, a second digital assistant response based on the second user voice input and the digital assistant dialog history of the first electronic device.

A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to: while the first electronic device is participating in a context-sharing group associated with a first location, wherein the context-sharing group is a collection of at least two electronic devices that each share context information with at least one other electronic device participating in the collection, and wherein the collection includes at least a second electronic device and a context collector: receiving a user voice input, wherein the user voice input comprises a digital assistant trigger; in response to detecting the digital assistant trigger, sending a first trigger advertisement to the context collector, wherein the first trigger advertisement indicates a first time at which the digital assistant trigger ends according to the first electronic device; receiving a second trigger advertisement from the context collector, wherein the second trigger advertisement indicates a second time at which the digital assistant trigger ended according to the second electronic device; determining whether the second time is within a predetermined time range prior to the first time; and in accordance with a determination that the second time is within the predetermined time range prior to the first time, forgoing further processing of the user speech input.

Example electronic devices and systems are disclosed herein. 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 that each share 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, choosing one electronic device of the set of at least two electronic devices as a context collector of the context-sharing group, wherein choosing the context collector comprises: determining a first context collector score corresponding to the first electronic device based at least on a strength of connectivity between the first electronic device and a wireless network of the first location; receiving, from at least the second electronic device, one or more context collector scores corresponding to at least the second electronic device; and determining which of the electronic devices included in the context-sharing group to choose as the context collector of 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 accordance with a determination to choose 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.

Another example 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: while the first electronic device is 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 that each share 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 a user voice input; receiving an aggregated context for 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 speech input to a remote device 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; and transmitting 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.

An exemplary system comprises one or more processors; a memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: receiving, from a first electronic device participating in a context-sharing group associated with a first location, a user speech input and at least a portion of an aggregated context of the context-sharing group, wherein the context-sharing group is a collection of a plurality of electronic devices that each share context information with at least one other electronic device included in the collection; determining a user intent based on the user speech input; determining one or more tasks corresponding to the user intent; identifying a second electronic device of the plurality of 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 aggregated context; and sending a command to a first electronic device to perform the one or more tasks and a device identifier corresponding to the second 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.

Another example 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: while the first electronic device is participating in a context-sharing group associated with a first location, wherein the context-sharing group is a collection of a plurality of electronic devices that each share context information with at least one other electronic device included in the collection, and wherein the collection includes a context collector: receiving a user voice input; receiving an aggregated context for 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 speech input to a remote device not participating in the context-sharing group, wherein the remote device determines a plurality of tasks based on the data corresponding to the user speech input; receiving, from the remote device: a first command to perform a first set of tasks of the plurality of tasks and a second command to perform a second set of tasks of the plurality of tasks; and a first device identifier corresponding to a second electronic device of the plurality of electronic devices and a second device identifier corresponding to a third electronic device of the plurality of 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 set 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 set of tasks.

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: 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 that each share 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; at the first electronic device, outputting a first digital assistant response based on the first user voice input, wherein the first electronic device sends contextual information including a digital assistant dialog session history for 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, at the second electronic device, an updated aggregated context for the context-sharing group from the context collector, wherein the updated aggregated context comprises the digital assistant conversation session history for the first electronic device; and outputting, at the second electronic device, a second digital assistant response based on the second user voice input and the digital assistant dialog history of the first electronic device.

Another example 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: while the first electronic device is 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 that each share context information with at least one other electronic device that is participating in the set, and wherein the set includes at least a second electronic device and a context collector: receiving a user voice input, wherein the user voice input comprises a digital assistant trigger; in response to detecting the digital assistant trigger, sending a first trigger advertisement to the context collector, wherein the first trigger advertisement indicates a first time at which the digital assistant trigger ended according to the first electronic device; receiving a second trigger advertisement from the context collector, wherein the second trigger advertisement indicates a second time at which the digital assistant trigger ended according to the second electronic device; determining whether the second time is within a predetermined time range prior to the first time; and in accordance with a determination that the second time is within the predetermined time range prior to the first time, forgoing further processing of the user speech input.

An example 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 that each share context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device. Means for, after joining the context-sharing group, choosing one electronic device of the set of at least two electronic devices as a context collector of the context-sharing group, wherein choosing the context collector comprises: determining a first context collector score corresponding to the first electronic device based at least on a strength of connectivity between the first electronic device and a wireless network of the first location; receiving, from at least the second electronic device, one or more context collector scores corresponding to at least the second electronic device; and determining which of the electronic devices included in the context-sharing group to choose as the context collector of 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. Means for, in accordance with the determination, choosing the first electronic device as the context collector for receiving context information from at least the second electronic device in response to at least the second electronic device experiencing a device state change.

Another example first electronic device includes means for: while the first electronic device is 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 that each share 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 a user voice input; means for receiving an aggregated context of the context-sharing group from the context collector; after receiving the aggregated context, means for providing at least a portion of the aggregated context and data corresponding to the user speech input to a remote device not participating in the context-sharing group; means for receiving a command from the remote device 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 contextual information included in the at least a portion of the aggregated context; and means 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.

Another exemplary system includes means for: means for receiving, from a first electronic device participating in a context-sharing group, a user speech input and at least a portion of an aggregated context of the context-sharing group, the context-sharing group associated with a first location, wherein the context-sharing group is a collection of a plurality of electronic devices that each share context information with at least one other electronic device included in the collection; means for determining a user intent based on the user speech input; means for determining one or more tasks corresponding to the user intent; means for identifying a second electronic device of the plurality of 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 aggregated context; and means for sending a command to a first electronic device to perform the one or more tasks and a device identifier corresponding to the second 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.

Another example first electronic device includes means for: while the first electronic device is participating in a context-sharing group associated with a first location, wherein the context-sharing group is a set of a plurality of electronic devices that each share 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; means for receiving an aggregated context of the context-sharing group from the context collector; after receiving the aggregated context, means for providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device not participating in the context-sharing group, wherein the remote device determines a plurality of tasks based on the data corresponding to the user voice input; means for receiving from the remote device: a first command to perform a first set of tasks of the plurality of tasks and a second command to perform a second set of tasks of the plurality of tasks; and a first device identifier corresponding to a second electronic device of the plurality of electronic devices and a second device identifier corresponding to a third electronic device of the plurality of electronic devices; means 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 set of tasks; and means 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 set of tasks.

Another exemplary system includes means for: 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 that each share 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; means for outputting, at the first electronic device, a first digital assistant response based on the first user voice input, wherein the first electronic device sends contextual information comprising a digital assistant dialog session history of the first electronic device to the context collector after outputting the first digital assistant response; means for receiving a second user voice input at the second electronic device; means for receiving, at the second electronic device, an updated aggregated context for the context-sharing group from the context collector, wherein the updated aggregated context comprises the digital assistant dialog session history of the first electronic device; and means for outputting, at the second electronic device, a second digital assistant response based on the second user voice input and the digital assistant dialog history of the first electronic device.

Another example first electronic device includes means for: while the first electronic device is participating in a context-sharing group associated with a first location, wherein the context-sharing group is a collection of at least two electronic devices that each share context information with at least one other electronic device participating in the collection, and wherein the collection includes at least a second electronic device and a context collector: receiving a user voice input, wherein the user voice input comprises a digital assistant trigger; in response to detecting the digital assistant trigger, sending a first trigger advertisement to the context collector, wherein the first trigger advertisement indicates a first time at which the digital assistant trigger ended according to the first electronic device; receiving a second trigger advertisement from the context collector, wherein the second trigger advertisement indicates a second time at which the digital assistant trigger ended according to the second electronic device; determining whether the second time is within a predetermined time range prior to the first time; and in accordance with a determination that the second time is within the predetermined time range prior to the first time, forgoing further processing of the user speech input.

In some examples, determining a first context collector score corresponding to a first electronic device based at least on a strength of connectivity between the first electronic device and a wireless network of a first location, and then determining which of the electronic devices included in the context-sharing group to choose as a 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 may improve a user's digital assistant experience. In particular, determining a 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 to ensure that electronic devices with strong connectivity to the wireless network will be picked as context collectors because the context collector picking 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 with the wireless network and leave the context sharing group. In this way, the collector will be able to consistently receive and send context information to electronic devices participating in the context-sharing group, which will allow the digital assistant of the electronic device to respond to user requests based on the context information provided to and received from the context collector.

In some examples, providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device not participating in the context-sharing group such that the remote device may determine one or more tasks and device identifiers based on the data corresponding to the user voice input and contextual information included in at least a portion of the aggregated context may improve a digital assistant experience for the user. In particular, by performing the above-described operations, the remote device can, 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 context of the remote device user when the user voice input is provided with respect to all devices participating in the context-sharing group, rather than the first electronic device that only received the user voice input. This, in turn, allows the remote device to determine an optimal electronic device for responding to the user based on the one or more tasks corresponding to the determined user intent and the contextual information included in the aggregated context. Thus, even if the first electronic device receives user speech input, the first electronic device may send one or more tasks to another electronic device that is better suited for performing the one or more tasks based on the device identifier provided by the remote device (e.g., located closer to the user, better device capabilities for performing the one or more tasks, etc.). Thus, the first electronic device provides the aggregated context to the remote device, and the first electronic device transmits one or more tasks to the second electronic device based on the received device identifiers, allowing the digital assistants of the electronic devices participating in the context-sharing group to intelligently coordinate the performance of the tasks with one another, 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.

In some examples, identifying a second electronic device of the plurality of electronic devices participating in the context-sharing group to perform the one or more tasks based on the one or more tasks and the context information included in at least a portion of the aggregated context of the context-sharing group may improve a digital assistant experience of the user. In particular, as described above, the electronic device receiving the user's digital assistant request may not be the best device for performing the requested task. For example, an electronic device receiving a user request may be less than an optimal device because the device may have a small display (or no display at all), the request may relate to an event occurring at another electronic device (e.g., alarm clock, timer, media playback, etc.), and/or there may be another electronic device that is more conveniently located with respect to the user. Thus, because the aggregated context includes context information (associated with the plurality of devices participating in the context-sharing group) indicating, for example, device capabilities, device location, and current and/or previous device activities and user interactions, the remote device (e.g., one or more servers) may identify a second, more suitable electronic device for performing one or more tasks based on the context information, rather than simply indicating the electronic device receiving 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 in order to provide the best response to the user's request.

Sending a first command to the second electronic device to perform a first set of tasks of the plurality of tasks and sending a second command to the third electronic device to perform a second set of tasks of the plurality of tasks may improve a digital assistant experience for the user. In particular, when a user's digital assistant requests that multiple tasks need to be performed (such as, for example, the output of digital assistant responses and the display of corresponding data/information), assigning the performance 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). Thus, instead of displaying data/information on a small display (or not displaying data/information at all), the second electronic device may be instructed via the first command to provide an audio digital assistant response while the third electronic device (e.g., having a larger display than the second electronic device) may be instructed to display 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.

In some examples, outputting, at the second electronic device, the second digital assistant response based on the second user speech input and the digital assistant dialog history of the first electronic device may improve the digital assistant experience of the user. In particular, using the digital assistant dialog 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 though the first user input is provided to the first electronic device and not the second electronic device. In this way, the user of the second electronic device may provide the digital assistant request (e.g., in the second user input) in a more natural and conversational manner, and if certain aspects of the request have been introduced in the first user input, those aspects need not be repeated. For example, if the first user voice input includes a user request "how about hey, Siri, pajoram weather? ", then the user of the second electronic device can then" hey, Siri, new york woo? "rather than having to repeat what weather information is desired (e.g.," how about 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.

In some examples, determining whether a second time at which the digital assistant trigger included in the user speech input ended in accordance with the second electronic device is within a predetermined time range before a first time at which the digital assistant trigger ended in accordance with the first electronic device, and forgoing further processing of the user speech input in accordance with determining that the second time is within the predetermined time range before the first time may improve the user's digital assistant experience. In particular, if the digital assistant trigger detection of the electronic device is delayed, the electronic device will begin processing the user speech input even if another electronic device in the vicinity (digital assistant trigger detection without delay) has begun processing the user speech input and/or has provided a response to the user speech 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 user digital assistant experience (e.g., due to user confusion and/or annoyance). Thus, forgoing further processing of the user voice input in the event that the electronic device determines that another electronic device has detected a 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.

Drawings

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

Fig. 2A is a block diagram illustrating a portable multifunction device implementing a client-side portion of a digital assistant, according to various examples.

Fig. 2B is a block diagram illustrating exemplary components for event processing according to various examples.

Fig. 3 illustrates a portable multi-function device implementing a client-side portion of a digital assistant, according to various examples.

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

Fig. 5A illustrates an exemplary user interface of a menu of applications on a portable multifunction device according to various examples.

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

Fig. 6A illustrates a personal electronic device, according to various examples.

Fig. 6B is a block diagram illustrating a personal electronic device, according to various examples.

Fig. 7A is a block diagram illustrating a digital assistant system or server portion thereof according to various examples.

Fig. 7B illustrates functionality of the digital assistant illustrated in fig. 7A according to various examples.

Fig. 7C illustrates a portion of an ontology according to various examples.

Fig. 8 illustrates systems and techniques for selecting a context collector for a context sharing group, according to various examples.

Fig. 9 illustrates systems and techniques for performing one or more tasks in a context sharing group, according to various examples.

Fig. 10 illustrates systems and techniques for suppressing delayed digital assistant trigger detection using a context collector of a context sharing group, according to various examples.

FIG. 11 is a block diagram illustrating a system for task determination and device selection in a context sharing group, according to various examples.

12A-12B illustrate systems and techniques for multimodal task execution in a context sharing group, according to various examples.

Fig. 13 illustrates systems and techniques for conducting a persistent digital assistant session across multiple devices participating in a context-sharing group, according to various examples.

14A-14C illustrate flow diagrams representing processes for selecting a context collector for a context-sharing group, according to various examples.

15A-15B illustrate flow diagrams representing processes for performing one or more tasks in a context-shared group, according to various examples.

Fig. 16A-16E illustrate flow diagrams representing processes for identifying electronic devices participating in a context-sharing group to perform one or more tasks, according to various examples.

17A-17C illustrate flow diagrams representing processes for multimodal task execution in a context sharing group, according to various examples.

18A-18B illustrate flow diagrams of processes representing a continuous digital assistant session across a plurality of electronic devices participating in a context-sharing group, according to various examples.

19A-19B illustrate flow diagrams representing processes for suppressing delayed digital assistant trigger detections using a context collector of a context-sharing group, according to various examples.

Detailed Description

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

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

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

Depending on the context, the term "if" may be interpreted to mean "when …" ("where" or "upon") or "in response to a determination" or "in response to a detection". Similarly, depending on the context, the phrase "if determined …" or "if [ stated condition or event ] is detected" may be interpreted to mean "upon determination …" or "in response to determination …" or "upon detection of [ stated condition or event ] or" in response to detection of [ stated condition or event ] ".

1. System and environment

Fig. 1 illustrates a block diagram of a system 100 according to various examples. In some examples, system 100 implements a digital assistant. The terms "digital assistant," "virtual assistant," "intelligent automated assistant," or "automatic digital assistant" refer to any information processing system that interprets natural language input in spoken and/or textual form to infer user intent and perform actions based on the inferred user intent. For example, to act on the 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, entering specific requirements into the task flow in accordance with the inferred user intent; executing the task flow by calling a program, a method, a service, an API, etc.; and to generate output responses to the user in audible (e.g., voice) and/or visual form.

In particular, the digital assistant is capable of accepting user requests at least partially in the form of natural language commands, requests, statements, narratives and/or inquiries. Typically, a user requests to seek an informational answer or perform a task by the digital assistant. Satisfactory responses to user requests include providing requested informational answers, performing requested tasks, or a combination of both. For example, a user presents a question to a digital assistant, such as "where do i am present? ". Based on the user's current location, the digital assistant answers "you are near the siemens of the central park. "the user also requests to perform a task, such as" please invite my friends to join my girlfriend's birthday party the next week. In response, the digital assistant can acknowledge the request by saying "good, now" and then send an appropriate calendar invitation on behalf of the user to each of the user's friends listed in the user's electronic address book. During the performance of requested tasks, the digital assistant sometimes interacts with the user in a continuous conversation involving multiple exchanges of information over a long 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, the digital assistant also provides responses in other visual or audio forms, such as text, alerts, music, video, animation, and so forth.

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

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

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

iPod

And

an apparatus. Other examples of portable multifunction devices include, but are not limited to, earbuds/headsets, speakers, and laptop or tablet computers. Further, in some examples, user device 104 is a non-portable multifunction device. In particular, the user device 104 is a desktop computer, a game console, a speaker, a television, or a television set-top box. In some examples, the user device 104 includes a touch-sensitive surface (e.g., a touchscreen display and/or a trackpad). Further, the user device 104 optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse, and/or joystick. Various examples of electronic devices, such as multifunction devices, are described in more detail below.

Examples of one or more communication networks 110 include a Local Area Network (LAN) and a Wide Area Network (WAN), 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.

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 employs various virtual devices and/or services of third party service providers (e.g., third party cloud service providers) to provide potential computing resources and/or infrastructure resources of the server system 108.

In some examples, user device 104 communicates with DA server 106 via second user device 122. The second user device 122 is similar to or the same as the user device 104. For example, the second user equipment 122 is similar to the apparatus 200, 400, or 600 described below with reference to fig. 2A, 4, and 6A-6B. 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 area Wi-Fi network). In some examples, second user device 122 is configured to act as a proxy between user device 104 and DA server 106. For example, DA client 102 of user device 104 is configured to transmit information (e.g., a user request received at user device 104) to DA server 106 via second user device 122. DA server 106 processes the information and returns relevant data (e.g., data content in response to the user request) to user device 104 via second user device 122.

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

user devices

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

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

2. Electronic device

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

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

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

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

Memory 202 includes one or more computer-readable storage media. These computer readable storage media are, for example, tangible and non-transitory. The memory 202 comprises 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.

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

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

RF (radio frequency) circuitry 208 receives and transmits RF signals, also referred to as electromagnetic signals. The RF circuitry 208 converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 208 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a Subscriber Identity Module (SIM) card, memory, and so forth. The RF circuitry 208 optionally communicates with networks such as the internet, also known as the World Wide Web (WWW), intranets, and/or wireless networks such as cellular telephone networks, wireless Local Area Networks (LANs), and/or Metropolitan Area Networks (MANs), and other devices via wireless communications. The RF circuitry 208 optionally includes well-known circuitry for detecting Near Field Communication (NFC) fields, such as by a short-range communications radio. The wireless communication optionally uses any of a number of communication standards, protocols, and technologies, including, but not limited to, global system for mobile communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), evolution, pure data (EV-DO), HSPA +, dual cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), wideband code division multiple access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), bluetooth low power consumption (BTLE), wireless fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over internet protocol (VoIP), Wi-MAX, email protocol (e.g., Internet Message Access Protocol (IMAP), and/or Post Office Protocol (POP))), Instant messaging (e.g., extensible messaging and presence protocol (XMPP), session initiation protocol with extensions for instant messaging and presence (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed at the filing date of this document.

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

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

A quick push of the push button disengages the lock on the touch screen 212 or begins the process of Unlocking the Device using a gesture on the touch screen, as described in U.S. patent application No. 11/322,549, entitled "Unlocking a Device by Forming appliances on an Unlock Image," filed on 23.12.2005, which is hereby incorporated by reference in its entirety. Pressing the push button (e.g., 306) longer turns the device 200 on or off. The user can customize the functionality of one or more buttons. The touch screen 212 is used to implement virtual or soft buttons and one or more soft keyboards.

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

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

The touch screen 212 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. Touch screen 212 and display controller 256 detect contact and any movement or breaking thereof using any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, 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 touch screen 212. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that available from Apple Inc. (Cupertino, California)

And iPod

The technique used in (1).

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

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

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

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

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

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

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

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

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

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

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

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

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

(trademark of Apple inc.) 30-pin connection used on equipmentA multi-pin (e.g., 30-pin) connector that is the same or similar to and/or compatible with the connector.

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

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

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

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

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

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

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

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

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

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

In some examples, the digital assistant client module 229 utilizes various sensors, subsystems, and peripherals of the portable multifunction device 200 to gather additional information from the surroundings of the portable multifunction device 200 to establish context associated with the user, current user interaction, and/or 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 the user intent. In some examples, the digital assistant also uses the contextual information to determine how to prepare and communicate the output to the user. The context information is referred to as context data.

In some examples, contextual information accompanying the user input includes sensor information, such as lighting, ambient noise, ambient temperature, images or video of the surrounding environment, and so forth. In some examples, the context information may also include physical states of the device, such as device orientation, device location, device temperature, power level, velocity, acceleration, motion pattern, cellular signal strength, and the like. In some 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 activities, background services, error logs, resource usage, etc., is provided to the DA server 106 as contextual information associated with the user input.

In some examples, digital assistant client module 229 selectively provides information (e.g., user data 231) stored on portable multifunction device 200 in response to requests from 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 at the request of the DA server 106. The digital assistant client module 229 communicates this additional input to the DA server 106 to assist the DA server 106 in intent inference and/or to implement the user intent expressed in the user request.

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

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

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

a phone module 238;

a video conferencing module 239;

an email client module 240;

an Instant Messaging (IM) module 241;

fitness support module 242;

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

an image management module 244;

a video player module;

a music player module;

a browser module 247;

a calendar module 248;

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

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

A search module 251;

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

a notepad module 253;

a map module 254; and/or

Online video module 255.

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

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

In conjunction with the RF circuitry 208, the audio circuitry 210, the speaker 211, the microphone 213, the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, and the text input module 234, the phone module 238 is operable to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in the 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 completed. As described above, wireless communication uses any of a variety of communication standards, protocols, and technologies.

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

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

In conjunction with the RF circuitry 208, the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, and the text input module 234, the instant message module 241 includes executable instructions for: entering a sequence of characters corresponding to an instant message, modifying previously entered characters, transmitting a corresponding instant message (e.g., using a Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocol for a phone-based instant message or using XMPP, SIMPLE, or IMPS for an internet-based instant message), receiving an instant message, and viewing the received instant message. In some embodiments, the transmitted and/or received instant messages 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 message" refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

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

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

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

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

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

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

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

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

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

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

In conjunction with the RF circuitry 208, the touch screen 212, the display controller 256, the contact/motion module 230, the graphics module 232, the text input module 234, the 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 maps (e.g., driving directions, data related to stores and other points of interest at or near a particular location, and other location-based data) according to user instructions.

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

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

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

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

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

The event sorter 270 receives the event information and determines the application 236-1 to which the event information is to be delivered and the application view 291 of the application 236-1. Event sorter 270 includes event monitor 271 and 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, device/global internal state 257 is used by event classifier 270 to determine which application(s) are currently active, and application internal state 292 is used by event classifier 270 to determine the application view 291 to which to deliver event information.

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

The event monitor 271 receives event information from the peripheral interface 218. The event information includes information about a sub-event (e.g., a user touch on the touch-sensitive display 212 as part of a multi-touch gesture). Peripherals interface 218 transfers 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 circuitry 210). Information received by the peripheral interface 218 from the I/O subsystem 206 includes information from the touch-sensitive display 212 or touch-sensitive surface.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When the respective event recognizer 280 determines that the sequence of sub-events does not match any event in the event definition 286, the respective event recognizer 280 enters an event not possible, event failed, or event end state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, the 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.

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

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

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

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

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

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

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

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 buttons are implemented as soft keys in a GUI displayed on touch screen 212.

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

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

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

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

Fig. 5A illustrates an exemplary user interface of an application menu on a portable multifunction device 200 according to some embodiments. A similar user interface is implemented on the device 400. In some embodiments, the user interface 500 includes the following elements, or a subset or superset thereof:

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

time 504;

A bluetooth indicator 505;

a battery status indicator 506;

tray 508 with icons for common applications, such as:

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

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

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

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

icons for other applications, such as:

icon 524 of IM module 241 labeled "message";

icon 526 of calendar module 248 labeled "calendar";

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

icon 530 for camera module 243 labeled "camera";

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

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

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

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

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

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

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

an icon 546 labeled "settings" for setting applications or modules that provides access to the settings of the device 200 and its various applications 236.

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

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

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

contacts

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

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

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

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

In some embodiments, device 600 has one or

more input mechanisms

606 and 608. The input mechanisms 606 and 608 (if included) are in physical form. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 600 has one or more attachment mechanisms. Such attachment mechanisms, if included, may allow device 600 to be attached with, for example, a hat, glasses, earrings, necklace, shirt, jacket, bracelet, watchband, bracelet, pants, belt, shoe, purse, backpack, and the like. These attachment mechanisms allow the user to wear the device 600.

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

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

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 the one or more computer processors 616, cause the computer processors to perform the techniques and processes described above, for example. The computer-executable instructions are also stored and/or transmitted, for instance, within any non-transitory computer-readable storage medium, for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. The personal electronic device 600 is not limited to the components and configuration of fig. 6B, but may include other components or additional components in a variety of configurations.

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

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

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

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

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 that: at which intensity the device will perform the operations typically associated with clicking a button of a physical mouse or touch pad. In some embodiments, the deep press intensity threshold corresponds to an intensity that: at which intensity the device will perform a different operation than that typically associated with clicking a button of a physical mouse or trackpad. In some embodiments, when a contact is detected whose characteristic intensity is below a light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, a contact below the nominal contact detection intensity threshold is no longer detected), the device will move the focus selector in accordance with movement of the contact on the touch-sensitive surface without performing operations associated with the light press intensity threshold or the deep press intensity threshold. Generally, these intensity thresholds are consistent between different sets of user interface drawings, unless otherwise stated.

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

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

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

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

3. Digital assistant system

Fig. 7A illustrates a block diagram of a digital assistant system 700, according to various examples. In some examples, the digital assistant system 700 is implemented on a standalone computer system. In some examples, the digital assistant system 700 is distributed across multiple computers. In some examples, some of the modules and functionality 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, e.g., as shown in fig. 1. In some examples, digital assistant system 700 is a specific implementation of server system 108 (and/or DA server 106) shown in fig. 1. It should be noted that the digital assistant system 700 is only one example of a digital assistant system, and that the digital assistant system 700 has more or fewer components than shown, combines two or more components, or may have a different configuration or layout of components. The various components shown in fig. 7A 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.

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

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

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

In some examples, the network communication interface 708 includes one or more wired communication ports 712 and/or wireless transmission and reception circuitry 714. The one or more wired communication ports receive and transmit communication signals via one or more wired interfaces, such as ethernet, Universal Serial Bus (USB), FIREWIRE, and the like. The wireless circuitry 714 receives and transmits RF and/or optical signals to and from the communication network and other communication devices. The wireless communication uses any of a number of communication standards, protocols, and technologies, such as GSM, EDGE, CDMA, TDMA, Bluetooth, Wi-Fi, VoIP, Wi-MAX, or any other suitable communication protocol. Network communication interface 708 enables communication between digital assistant system 700 and other devices via a network, such as the internet, an intranet, and/or a wireless network, such as a cellular telephone network, a wireless Local Area Network (LAN), and/or a Metropolitan Area Network (MAN).

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

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

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

User interface module 722 receives commands and/or input from a user (e.g., from a keyboard, touch screen, pointing device, controller, and/or microphone) via I/O interface 706 and generates user interface objects on the display. User interface module 722 also prepares and communicates output (e.g., voice, sound, animation, text, icons, vibrations, haptic feedback, lighting, etc.) to the user via I/O interface 706 (e.g., via a display, audio channel, speaker, touch pad, etc.).

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

The memory 702 also stores a digital assistant module 726 (or a server portion of a digital assistant). In some examples, digital assistant module 726 includes the following sub-modules, or a subset or superset thereof: an input/output processing module 728, a Speech To Text (STT) processing module 730, a natural language processing module 732, a 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, or a subset or superset thereof, of the digital assistant module 726: ontology 760, vocabulary index 744, user data 748, task flow model 754, service model 756, and ASR system 758.

In some examples, using the processing modules, data, and models implemented in the digital assistant module 726, the digital assistant can perform at least some of the following: converting the speech input to text; identifying a user intent expressed in a natural language input received from a user; proactively elicit and obtain the information needed to fully infer the user's intent (e.g., by disambiguating words, games, intentions, etc.); determining a task flow for satisfying the inferred intent; and executing the task flow to satisfy the inferred intent.

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

STT processing module 730 includes one or more ASR systems 758. The one or more ASR systems 758 may process speech input received through the I/O processing module 728 to generate recognition results. Each ASR system 758 includes a front-end speech preprocessor. A front-end speech preprocessor extracts representative features from speech input. For example, a front-end speech preprocessor performs a fourier transform on a speech input to extract spectral features characterizing the speech input as a sequence of representative multi-dimensional 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 dynamic time warping based engines and Weighted Finite State Transformer (WFST) based engines. The extracted representative features of the front-end speech preprocessor are processed using one or more speech recognition models and one or more speech recognition engines to produce intermediate recognition results (e.g., phonemes, phoneme strings, and sub-words), and ultimately text recognition results (e.g., words, word strings, or symbol sequences). In some examples, the voice input is processed at least in part by a third party service or on a device of the user (e.g., device 104, device 200, device 400, or device 600) to produce a recognition result. Once STT processing module 730 generates recognition results that include a text string (e.g., a word, or a sequence of words, or a sequence of symbols), the recognition results are communicated to natural language processing module 732 for intent inference. In some examples, STT processing module 730 generates a plurality of candidate text representations of the speech input. Each candidate text representation is a sequence of words or symbols corresponding to the speech input. In some examples, each candidate text representation is associated with a speech recognition confidence score. Based on the speech recognition confidence scores, STT processing module 730 ranks the candidate text representations and provides n-best (e.g., n-highest ranked) candidate text representations to 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 native language processing module 732 for intent inference. As another example, the 5 highest ranked (n ═ 5) candidate textual representations are passed to natural language processing module 732 for intent inference.

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

In some casesIn an example, STT processing module 730 includes a vocabulary of recognizable words and/or accesses the vocabulary via phonetic letter conversion module 731. Each vocabulary word is associated with one or more candidate pronunciations for the word represented in the speech recognition phonetic alphabet. In particular, the vocabulary of recognizable words includes words associated with a plurality of candidate pronunciations. For example, the word includes and-

/and-

The word "tomato" associated with the candidate pronunciation of/. In addition, the vocabulary words are associated with custom candidate pronunciations based on prior speech input from the user. Such custom candidate pronunciations are stored in STT processing module 730 and associated with a particular user via a user profile on the device. In some examples, the candidate pronunciation of the word is determined based on the spelling of the word and one or more linguistic and/or phonetic rules. In some examples, the candidate pronunciation is generated manually, e.g., based on a known standard pronunciation.

In some examples, candidate pronunciations are ranked based on their prevalence. For example, a candidate pronunciation-

Rank greater than ^ greater than

V. because the former is a more common pronunciation (e.g., among all users, for users in a particular geographic area, or for any other suitable subset of users). In some examples, the candidate pronunciations are ranked based on whether the candidate pronunciations are self-defined candidate pronunciations associated with the user. For example, the custom candidate pronunciation is ranked higher than the standard candidate pronunciation. This can be used to identify proper nouns with unique pronunciations that deviate from the canonical pronunciation. In some examples, the candidate pronunciation is associated with one or more speech features such as geographyOrigin, country or species. For example, a candidate pronunciation-

/is associated with the United states and the candidate pronunciation +

Associated with the uk. Further, 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 a user profile that the user is associated with the united states. Candidate vocalization based on a user's association with the United states

/(associated with the United states) may be compared to a candidate pronunciation @

/(associated with the uk) is ranked higher. In some examples, one of the ranked candidate pronunciations may be selected as a predicted pronunciation (e.g., the most likely pronunciation).

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

Then it may then determine that the sequence corresponds to the word "tomato" based on the lexical index 744.

In some examples, STT processing module 730 uses fuzzy matching techniques to determine words in the utterance. Thus, for example, STT processing module 730 determines a phoneme sequence ≧

Corresponding to the word "tomato", even if the particular phoneme sequence is notIs a candidate phoneme sequence for the word.

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

In some examples, the natural language processing module 732 receives context information associated with the user request, for example, from the I/O processing module 728, in addition to the sequence of words or symbols obtained from the STT processing module 730. The natural language processing module 732 optionally uses the context information to clarify, supplement, and/or further define information contained in the candidate text representation received from the STT processing module 730. Contextual information includes, for example, user preferences, hardware and/or software states of the user device, sensor information collected before, during, or shortly after a user request, previous interactions (e.g., conversations) between the digital assistant and the user, and so forth. As described herein, in some examples, the contextual information is dynamic and varies with time, location, content of the conversation, and other factors.

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

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

Further, the attribute nodes "cuisine", "price interval", "phone number", and "location" are child nodes of the attribute node "restaurant", and are all connected to the "restaurant reservation" node (i.e., actionable intent node) through the intermediate attribute node "restaurant". As another example, as shown in FIG. 7C, ontology 760 also includes a "set reminder" node (i.e., another actionable intent node). The attribute nodes "date/time" (for set reminders) and "topic" (for reminders) are both connected to the "set reminders" 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 the ontology 760.

The actionable intent node, along with its linked property nodes, is described as a "domain". In the present discussion, each domain is associated with a respective executable intent and refers to a set of nodes (and relationships between those nodes) associated with a particular executable intent. For example, ontology 760 shown in FIG. 7C includes an example of a restaurant reservation field 762 and an example of a reminder field 764 within ontology 760. The restaurant reservation domain includes the actionable intent node "restaurant reservation," the attribute nodes "restaurant," date/time, "and" party size, "and the child attribute nodes" cuisine, "" price range, "" phone number, "and" location. The reminder field 764 includes the actionable intent node "set reminder" and property nodes "subject" and "date/time". In some examples, ontology 760 is comprised 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 field 762 and reminder field 764, the "date/time" property node is associated with a number of different fields (e.g., a scheduling field, a travel reservation field, a movie tickets field, etc.).

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

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

In some examples, nodes associated with multiple related executables are clustered under a "super domain" in the ontology 760. For example, a "travel" super-domain includes a cluster of attribute nodes and actionable intent nodes related to travel. Executable intent nodes related to travel include "airline reservation," "hotel reservation," "car rental," "route planning," "finding points of interest," and the like. Actionable intent nodes under the same super-domain (e.g., a "travel" super-domain) have multiple attribute nodes in common. For example, executable intent nodes for "airline reservation," hotel reservation, "" car rental, "" get route, "and" find point of interest "share one or more of the attribute nodes" starting location, "" destination, "" departure date/time, "" arrival date/time, "and" party size.

In some examples, each node in ontology 760 is associated with a set of words and/or phrases that are related to the attributes or actionable intents represented by the node. The respective set of words and/or phrases associated with each node is a so-called "vocabulary" associated with the node. A respective set of words and/or phrases associated with each node is stored in the lexical index 744 associated with the attribute or actionable intent represented by the node. For example, returning to FIG. 7B, the vocabulary associated with the node for the "restaurant" attribute includes words such as "food," "drinks," "cuisine," "hunger," "eating," "pizza," "fast food," "meal," and so forth. As another example, the words associated with the node that "place a phone call" actionable intent include words and phrases such as "call," "make phone call," "dial," "make phone call with … …," "call the number," "call to," and the like. The lexical index 744 optionally includes words and phrases in different languages.

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 relate to. In some examples, if a word or phrase in a candidate text representation is found to be associated (via lexical index 744) with one or more nodes in ontology 760, then the word or phrase "triggers" or "activates" those nodes. Based on the number and/or relative importance of the activated nodes, natural language processing module 732 selects one of the actionable intents as the task that the user intends for the digital assistant to perform. In some examples, the domain with the most "triggered" nodes is selected. In some examples, the domain with the highest confidence level (e.g., based on the relative importance of its respective triggered nodes) is selected. In some examples, the domain is selected based on a combination of the number and importance of triggered nodes. In some examples, additional factors are also considered in selecting a node, such as whether the digital assistant has previously correctly interpreted a similar request from the user.

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

It is to be appreciated that in some examples, the natural language processing module 732 is implemented with one or more machine learning mechanisms (e.g., a neural network). In particular, one or more machine learning mechanisms are configured to receive candidate text representations and contextual information associated with the candidate text representations. Based on the candidate text representations and the associated context information, one or more machine learning mechanisms are configured to determine an intent confidence score based on a set of candidate actionable intents. The natural language processing module 732 may select one or more candidate executables from a set of candidate executables based on the determined intent confidence scores. In some examples, an ontology (e.g., ontology 760) is also utilized to select one or more candidate actionable intents from a set of candidate actionable intents.

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

In some examples, once natural language processing module 732 identifies an actionable intent (or domain) based on a user request, natural language processing module 732 generates a structured query to represent the identified actionable intent. In some examples, the structured query includes parameters for one or more nodes within the domain that can execute the intent, and at least some of the parameters are populated with specific information and requirements specified in the user request. For example, the user says "help me reserve a seat at 7 pm in a sushi shop. In this case, the natural language processing module 732 can correctly recognize the executable intent as "restaurant reservation" based on the user input. According to the ontology, the structured query of the "restaurant reservation" domain includes parameters such as { cuisine }, { time }, { date }, { party size }, and the like. In some examples, based on the speech input and text derived from the speech input using STT processing module 730, natural language processing module 732 generates a partially structured query for the restaurant reservation field, where the partially structured query includes parameters { cuisine ═ sushi class "} and { time ═ 7 pm" }. However, in this example, the user utterance contains insufficient information to complete a structured query associated with the domain. Thus, based on the currently available information, other necessary parameters such as { party number } and { date } are not specified in the structured query. In some examples, 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 store that is "nearby," the natural language processing module 732 populates the { location } parameter in the structured query with the GPS coordinates from the user device.

In some examples, natural language processing module 732 identifies a plurality of candidate executable intents for each candidate text representation received from STT processing module 730. Additionally, in some examples, a respective structured query is generated (partially or wholly) for each identified candidate executable intent. The natural language processing module 732 determines an intent confidence score for each candidate actionable intent and ranks the candidate actionable intents based on the intent confidence scores. In some examples, the natural language processing module 732 passes the generated one or more structured queries (including any completed parameters) to a task stream processing module 736 ("task stream processor"). In some examples, the one or more structured queries for the m-best (e.g., m highest ranked) candidate executables are provided to task flow processing module 736, where m is a predetermined integer greater than zero. In some examples, the one or more structured queries for the m best candidate executable intents are provided to task flow processing module 736 along with the corresponding one or more candidate textual representations.

Additional details of Inferring User Intent based on multiple candidate actionable intents determined From multiple candidate textual representations of Speech input are described in U.S. utility model patent application 14/298,725 entitled "System and Method for inducing User Intent From Speech Inputs" filed 6.6.2014, the entire disclosure of which is incorporated herein by reference.

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

As described above, to complete a structured query, the task flow processing module 736 needs to initiate additional dialog with the user in order to obtain additional information and/or clarify potentially ambiguous utterances. When such interaction is necessary, task flow processing module 736 invokes dialog flow processing module 734 to participate in the dialog with the user. In some examples, the dialog flow processor module 734 determines how (and/or when) to request additional information from the user, and receives and processes the user response. The questions are provided to the user and the answers are received from the user through the I/O processing module 728. In some examples, the conversation flow processing module 734 presents the conversation output to the user via audible output and/or visual output and receives input from the user via a spoken or physical (e.g., click) response. Continuing with the above example, when the task flow processing module 736 invokes the conversation flow processing module 734 to determine "party size" and "date" information for a structured query associated with the domain "restaurant reservation," the conversation flow processing module 734 generates a message such as "a few bits in a line? "and" which day to subscribe? "and the like to the user. Upon receiving an answer from the user, the dialog flow processing module 734 may populate the structured query with missing information or pass the information to the task flow processing module 736 to complete the missing information from the structured query.

Once the task flow processing module 736 has completed the structured query for the executable intent, the task flow processing module 736 begins executing the final task associated with the executable intent. Thus, the task flow processing module 736 performs the steps and instructions in the task flow model according to the specific parameters contained in the structured query. For example, a task flow model for the actionable intent "restaurant reservation" includes steps and instructions for contacting a dining room and actually requesting a reservation for a particular party size at a particular time. For example, using structured queries such as: { restaurant reservation, restaurant ABC cafe, date 3/12/2012, time 7pm, party number 5}, task flow processing module 736 may perform the following steps: (1) logging into a server of an ABC cafe or a coffee shop such as

The restaurant reservation system of (1), (2) entering date, time, and party size information in the form of a website, (3) submitting a form, and (4) forming a reservation in the user's calendarA calendar entry.

In some examples, the task flow processing module 736 either completes the task requested in the user input or provides the informational answer requested in the user input with the assistance of the service processing module 738 ("service processing module"). For example, the service processing module 738 initiates a telephone call, sets calendar entries, 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., restaurant reservation portal, social networking site, 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 respective ones of service models 756. The service handling module 738 accesses the appropriate service model for the service and generates a request for the service according to the service model according to the protocols and APIs required by the service.

For example, if a restaurant has enabled an online reservation service, the restaurant submits a service model that specifies the necessary parameters to make the reservation and an API to communicate the values of the necessary parameters to the online reservation service. The service processing module 738, when requested by the task flow processing module 736, can establish a network connection with the online booking service using the Web address stored in the service model and send the necessary parameters for booking (e.g., time, date, party size) to the online booking interface in a format according to the API of the online booking service.

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

In examples where the task flow processing module 736 receives multiple structured queries from the natural language processing module 732, the task flow processing module 736 first processes a first structured query of the received structured queries in an attempt to complete the first structured query and/or to perform one or more tasks or actions represented by the first structured query. In some examples, the first structured query corresponds to a highest ranked executable intent. In other examples, the first structured query is selected from structured queries received based on a combination of a corresponding speech recognition confidence score and a 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 of the received structured queries that corresponds to a lower ranked executable intent. The second structured query is selected, for example, based on the speech recognition confidence score of the corresponding candidate text representation, the intent confidence score of the corresponding candidate actionable intent, the missing necessary parameters in the first structured query, or any combination thereof.

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

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

Additional details regarding digital assistants can be found in U.S. utility model patent application 12/987,982 entitled "Intelligent Automated Assistant" filed on 10.1.2011 and U.S. utility model patent application 13/251,088 entitled "Generation and Processing Task Items Using to Performance" filed on 30.9.2011, the entire disclosures of which are incorporated herein by reference.

4. Systems and techniques for selecting context collectors for context-sharing groups

Fig. 8 illustrates systems and techniques for selecting a context collector for a device circle, according to various examples. System 800 includes user device 802, public device 804, user device 806, and user device 808. User device 802, user device 806, and user device 808 are all client devices (e.g.,

user devices

104, 122, 200, 400, or 600). For example, the user equipment 802 is

User equipment 806 is Apple

The user equipment 808 is

The client device is registered with a single user. For example, user device 802 may be registered with a first user, and user device 806 and user device 808 may be registered with a second user. Public device 804 is a smart speaker with the same or similar digital assistant capabilities as the various user devices. A public device is an electronic device that 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, public device 804 is

Another example of a common device is a smart television (e.g., Apple)

)。

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

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

In some examples, in response to undergoing a "device state change" (the device state change is 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 a context-sharing group. Further, the context collector provides the "aggregated context" of the context-sharing group (which includes the context information received from the one or more electronic devices participating in the context-sharing group) to the one or more electronic devices participating in the context-sharing group (e.g., in response to a request for aggregated context information, e.g., received from the one or more electronic devices). In some examples, the context collector of the context-sharing group is an electronic device (e.g., a user device or a public device) participating in the context-sharing group. 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 may serve as context collectors include one or more servers (e.g., DA server 106), one or more cloud computing systems, one or more local servers, and so forth.

As will be described below with reference to fig. 8, the electronic devices participating in the context-sharing group are first "picked" (i.e., selected) as context collectors before beginning to receive context information from other electronic devices participating in the context-sharing group and aggregate the context information. It is noted that while fig. 8 and the corresponding description below discuss the selection of a single context collector for context-sharing group 814, in some examples, context-sharing group 814 includes more than one context collector (e.g., two or three context collectors).

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

In some examples, the user device 802 must register in the context sharing group 814 in order to join the context sharing group 814. For example, registering the user device 802 in the context sharing group 814 may include the user of the user device 802 via a software application having context sharing group functionality stored on the user device 802 (e.g., via a software application having context sharing group functionality stored on the user device 802)

An application) and/or register the user device 802 with the context sharing group 814 via a website having 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 the context-sharing group 814 and then registering with the context-sharing group 814 after the context-sharing group 814 is created. At one endIn some examples, registering in the context-sharing group 814 includes the user device 802 granting access to/allowing 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., media, contacts, voice profiles, preferences, etc. of the user) 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) that is registered in the context-sharing group 814.

In the example above, 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. The user device 802 then joins the context share group 813 only if it determines that it is registered in the context share group 814. If the user device 802 determines that it is not registered in the context share group 814, the user device 802 relinquishes joining the context share group 814.

After the user device 802 joins the context-sharing group 814 (e.g., immediately after or shortly after (e.g., after a few minutes)), the electronic devices participating in the context-sharing group 814 perform context collector "picking," which is a process used to pick (i.e., select) one of the electronic devices participating in the context-sharing group 814 as the context collector of the context-sharing group. As described above, in some examples, more than one electronic device participating in the context sharing group 814 is elected to be a context collector. In some examples, the user device 802 (and other electronic devices participating in the context-sharing group 814) performs the context collector selection in response to joining the context-sharing group 814 (e.g., immediately after joining). In some examples, the user device 802 (and other electronic devices participating in the context sharing group 814) performs context collector selection in response to the electronic device (e.g., the current context collector) participating in the context sharing group 814 leaving the context sharing group (e.g., disconnecting from the network 810, disconnecting from communication with another electronic device participating in the context sharing group 814, and/or leaving a particular location associated with the context sharing group 814). Note that, as will be discussed below, electronic devices participating in context-sharing group 814 may perform context collector culling even though context-sharing group 814 already includes context collectors, and even though context-sharing group 814 only allows a single context collector.

Context collector selection begins with the user device 802 (and each of the other electronic devices participating in the context sharing group 814) determining a collector score based on the strength of the connectivity between the user device 802 and the network 810 and/or based on the power state of the user device 802 (e.g., wired power connection versus battery level and/or remaining battery level). For example, a stronger connection between the user device 802 and the network 810 will result in a higher context collector score. Similarly, the more stable the power of the user device 802, the higher the context collector score of the user device 802 will be (e.g., the more stable the wired power connection is than the battery power, and the more stable the full battery power is than the low battery power). In some examples, the collector score is also based on the frequency with which the user device 802 moves in and out of the context-sharing group 814 (e.g., the frequency with which the user device 802 connects/disconnects from the network 810 and/or the frequency with which the user device 802 enters and/or leaves a particular location associated with the context-sharing group 814). In some examples, the context collector score is also based on the stability of the user device 802 to keep the context information in its memory. In some examples, the context collector score is also based on the stability of the communication connections between the user device 802 and the other electronic devices participating in the context sharing group 814. In some examples, the context collector score is also based on reachability of the user device 802 to other electronic devices participating in the context-sharing group 814 (e.g., the more devices reachable by the user device 802 over various networks/other communication protocols, the higher the context collector score). The above-described factors considered in determining the context collector score place a premium on the stability of the electronic devices participating in the context sharing group, the ability to communicate with other electronic devices, and/or the ability to store context information, as it is desirable for the context sharing group 814 to have context collectors that are available as frequently as possible to receive, aggregate, store, and/or send context information.

As illustrated by arrow 816, after the user device 802 determines the context collector score, the user device 802 sends the context collector score (e.g., data corresponding to the context collector score) to each of the other electronic devices (i.e., the public device 804, the user device 806, and the user device 808) participating in the context sharing group 814 via the network 810. In some examples, the user device 802 also sends a context collector indication (also referred to as a context collector "flag") indicating whether the user device 802 is currently a context collector. For example, the user device 802 sends the context collector indication at the same time 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 a context collector if (1) the user device 802 was previously picked as a context collector after joining the context sharing group 814 (i.e., after connecting to the network 810 as shown by arrow 812) and/or if (2) the user device 802 was picked as a 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 shown by arrow 812), the context collector indication of the user device 802 will indicate that the user device 802 is a context collector. Otherwise, the context collector indication will indicate that the user device 802 is not a context collector.

As indicated by arrow 818, each of the public device 804, the user device 806, and the user device 808 sends their respective context collector scores (and in some examples their respective context collector indications) to the user device 802 before, at the same time as, or shortly after the user device 802 sends its context collector score (and in some examples its context collector indication), as indicated by arrow 816. Although not shown in fig. 8, common device 804, user device 806, and user device 808 also send their respective context collector scores (and in some examples their respective context collectors indicate) to each other. As such, after arrow 816 and arrow 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.

After receiving the context collector scores, the user device 802 (and the other electronic devices participating in the context sharing group 814) determines which of the electronic devices participating in the context sharing group 814 will pick as a context collector based on the context collector scores. The other electronic devices also make this determination based on the provided context collector scores. Determining which of the electronic devices included in the context sharing group 814 will pick as a context collector includes the user device 802 comparing its own context collector score to the context collector scores received from the common 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 the comparison, the user device 802 (and other electronic devices participating in the context sharing group 814) identifies the highest context collector score and picks the electronic device with the highest context collector score as the context collector.

Since common device 804, user device 806, and user device 808 make the above-described determination based on the same data and information as user device 802, they each also pick the same electronic device as user device 802 as the context collector. Thus, an electronic device participating in the context sharing group 814 will know whether it was chosen as a context collector based on its own context collector score comparison. However, in some examples, each electronic device participating in the context-sharing group 814 sends a pick indication to the other electronic devices, the pick indication indicating the context collector picked by each electronic device.

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 of the electronic devices participating in context sharing group 814 will pick as a context collector further comprises user device 802 (and the other electronic devices participating in context sharing group 814) determining whether context sharing group 814 currently comprises a context collector based on the received context collector indication. In these examples, if the user device 802 determines that the context sharing group 814 already includes a context collector, the user device 802 picks an existing context collector as the context collector of the context sharing group 814 regardless of the context collector score comparison result. If the user device 802 determines that the context sharing group 814 already includes two or more context collectors, the user device 802 picks a context collector based on the determined context collector score (as described above). This in turn improves the stability of the context collectors, as it is ensured that the context collectors of the context-sharing group 814 will not change unless an existing context collector leaves the context-sharing group 814.

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 the other electronic devices participating in the context-sharing group 814) will pick 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 two context collectors are currently participating in the context-sharing group 814, the user device 802 will pick the 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 pick a context collector based on a comparison of the determined context collector scores.

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

As described above, in some examples, electronic devices participating in a context-sharing group automatically share context information with a context collector of the context-sharing group in response to experiencing a "device state change. Examples of device state changes include media playback, activation (e.g., open) of a stored software application, a timer event (e.g., a timer of an electronic device sounds), an alarm event (e.g., an alarm of an electronic device sounds), a change in power state (e.g., an electronic device powers on or off), a change in display visibility (e.g., a display of an electronic device is repositioned from a display-down position to a display-up position (such that the display is 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.), initiating a digital assistant dialog session via pressing or holding a physical button on the device, and ending of the digital assistant dialog session (e.g., after a digital assistant of the electronic device provides/outputs a digital assistant response to the user request).

For example, as shown in FIG. 8, once alarm event 820 begins, user device 808 undergoes a device state change. Thus, the user device 808 sends the context information associated with the user device 808 to the chosen context collector of the context sharing group 814 shortly after the 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 the user device 802 is picked as a context collector, the user device 808 sends context information to the user device 802. Alternatively, as illustrated by arrow 822b, if public device 804 is chosen as the context collector, user device 808 sends context information to public device 804. In addition to sending context information to a 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 a predetermined (e.g., a predetermined serial number, etc.). In some examples, the device identifier is randomly generated (e.g., 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 when joining the context sharing group 814.

In response to receiving the device identifier, the context collector stores an association between the user device 808 and the device identifier. As will be described in more detail below with reference to fig. 9, the stored association between the electronic device and its device identifier is used to send commands to a particular electronic device. In particular, in some examples, the context collector notifies electronic devices participating in the context-sharing group of the stored associations such that each electronic device is able to relay/send commands (e.g., commands received from a remote device) to one or more other electronic devices based on 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 aggregated context of the context sharing group 814, the context collector also associates a device identifier corresponding to the user device 808 with the context information. In this way, the context information included in the aggregated context may be organized based on its associated device identifier. As will be described in more detail below with reference to fig. 9, one or more remote devices (e.g., 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.

The contextual information sent by an electronic device (e.g., user device 808) in response to experiencing a device state change includes various types of contextual information associated with the electronic device. Examples of contextual information that the electronic device transmits in response to experiencing a device state change include device state change information (e.g., type of state change (e.g., timer event, alarm event, end of digital assistant conversation session, etc.), time of state change, etc.), device capability information (e.g., type of device, processing power, memory availability, display information (e.g., whether the device has a display and/or dimensions of a display), speaker information (e.g., whether the device has a speaker and/or loudness of a speaker), etc.), and contextual 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.,

) Information of (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)), the strength of the network connection (e.g., to network 810), battery level, power type (e.g., battery versus wired power), etc.).

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

In some examples, the context collector stores only 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 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. 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 of each electronic device. In some examples, the context collector stores a short event history for each electronic device. In some embodiments, the 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, the context collector removes/deletes the context information of the electronic device when the electronic device leaves the context sharing group 814.

Then, as will be described in more detail below with reference to fig. 9 and 11-13, 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 causes the one or more electronic devices to obtain a digital assistant response to the user request based on the aggregated context (or based on at least a portion of the aggregated context).

5. Systems and techniques for performing tasks in a context-sharing group

Fig. 9 illustrates systems and techniques for performing one or more tasks in a context sharing group, according to various examples. System 900 includes a common device 904, a user device 906, a common 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, the user device 906 is registered with the user 902, while the user device 910 is not registered with the user 902. Public device 904 is a smart speaker with the same or similar digital assistant capabilities as the user device. The common device 908 is a smart television (connected display not shown) with the same or similar digital assistant capabilities as the user device. The public device 908 is a context collector of the context sharing group 914 (e.g., because the public device 908 was previously picked as a context collector). As discussed above with reference to fig. 8, 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, common device 904 is

The public device 910 is an Apple

System 900 also includes network 912 and server 916 (e.g., DA server 106). 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 and the server 916 via the network 912 (and thus are each connected to the network 912). Further, server 916 is a remote device that does not participate in context sharing group 914. In some examples, system 900 includes one or more other remote devices (e.g., local servers, cloud computing systems, etc.) in place of server 916. It should be appreciated that any operations performed by public device 904, user device 906, public device 908, and/or user device 910 may instead be performed by server 916 in these examples. For example, server 916 may perform operations of the respective DA client modules (e.g., DA client modules 229) of public device 904, user device 906, public device 908, user device 806, and/or user device 910.

As shown in FIG. 9, user 902 provides user voice input 918 received by common device 904 (e.g., "hey, Siri, stop timer" or "hey, Siri, play music"). User voice input 918 comprises a digital assistant trigger. A digital assistant trigger is a word or phrase (e.g., "hey, Siri," "Siri," etc.) that initiates a dialog session with a digital assistant of an electronic device. Thus, upon receiving the user speech input 918, the public device 904 detects a digital assistant trigger (e.g., determines that the user speech input 918 comprises a digital assistant trigger), determines that the user speech input 918 represents a digital assistant request (based on the detection of the digital assistant trigger), and begins processing the user speech input 918 to determine and/or obtain a response to the user speech input 918 (e.g., perform one or more tasks and/or output a digital assistant response).

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 user speech input as described above. During this time, 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 received the user voice input and detected a digital assistant trigger included in the user voice input in order to determine which device should process the received user voice input.

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

Fig. 10 illustrates systems and techniques for suppressing delayed digital assistant trigger detection using a context collector of a context sharing group, according to various examples. System 1000 is similar to system 900. In particular, system 1000 includes a common device 1004 (corresponding to common device 904), a user device 1006 (corresponding to user device 906), and a common device 1008 (corresponding to common device 908), all of which participate in a context-sharing group 1012 (corresponding to context-sharing group 914). The system 1000 also includes a network 1010 (corresponding to network 912). For simplicity, the user device corresponding to the user device 910 and the server corresponding to the server 916 are not shown. As with system 900, in the examples described below, public device 1008 is a context collector of context-sharing group 1012 (e.g., because public device 1008 was previously picked as a context collector).

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

As shown in fig. 10, user device 1002 provides user speech input 1014 (e.g., corresponding to user speech input 918 (e.g., "hey, Siri, stop timer" or "hey, Siri, play music.")) that includes a digital assistant trigger. User speech input 1014 is received by public device 1004 and user device 1006 (e.g., because public device 1004 and user device 1006 are located in close proximity to each other (e.g., in the same room)). However, public device 1004 detects a digital assistant trigger prior to user device 1006. Thus, the common device 1004 initiates a digital assistant dialog session while the user device is still determining whether the user speech input 1014 includes a digital assistant trigger. Further, as illustrated by arrow 1016, public device 1004 sends the context information (and the device identifier corresponding to public device 1004) to public device 1008 (since the detection of the digital assistant trigger is a device state change and public device 1008 is a context collector). For example, public device 1004 transmits the context information and the device identifier in response to detecting a digital assistant trigger.

Because the device state change of public device 1004 is the detection of a digital assistant trigger, the context information sent to public device 1008 includes a trigger advertisement (e.g., along with other device state change information). The trigger advertisement includes a digital assistant trigger end time, which is the time when the digital assistant trigger ends according to the common device 1004 (e.g., the time when the common device 1004 stops receiving audio signals corresponding to the digital assistant trigger). In some examples, the trigger advertisement further includes data indicative of an energy level (e.g., decibel level) of the digital assistant trigger (e.g., an energy level of an audio signal corresponding to the digital assistant trigger). In some examples, the first trigger advertisement also includes data indicating a confidence score corresponding to a confidence that the common device 1004 includes a digital assistant trigger with respect to the user speech input 1014.

Upon receiving the context information and trigger advertisement from the common device 1004, the common device 1008 updates the aggregated context of the context sharing group 1012 to include the context information and trigger advertisement. Further, as shown by arrow 1017, in response to receiving the trigger advertisement, the public device 1008 retrieves and sends to the public device 1004 (e.g., the trigger advertisement received within a predetermined period of time (e.g., within the last 30 seconds, within the last minute, within the last 5 minutes, etc.)) the trigger advertisement that has been included in the aggregated context (associated with the one or more other electronic devices participating in the context-sharing group). In some examples, instead of sending only trigger advertisements, common device 1008 sends the aggregated context (including the received trigger advertisements) to common device 1004. As will be described in more detail below with respect to user device 1006, public device 1004 uses trigger advertisements (e.g., data included in the trigger advertisements) received from public device 1008 to determine whether it should suppress its own digital assistant trigger detection (and thus forgo further processing of user voice input 1014).

In this case, however, the public device 1004 does not inhibit detection of the digital assistant trigger (e.g., because the public device 1004 is the first electronic device that detects the digital assistant trigger included in the user speech input 1014) and continues to process the user speech input 1014 (e.g., to determine/obtain a response to the user speech input 1014 (e.g., to perform one or more tasks and/or output a digital assistant response)). Thus, as illustrated with arrow 1018, the common device 1004 sends a request for an aggregated context for the context sharing group 1012 to the common device 1008. As illustrated with 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 where the common device 1008 sends the aggregated context at arrow 1017 instead of just sending the trigger advertisement,

arrows

1018 and 1020 do not occur because the common device has already received the aggregated context. After the public device 1004 receives the aggregated context (as illustrated by arrow 1020, or in some examples, as illustrated by arrow 1017) and determines that it should continue to process the user speech input 1014, the public device 1004 obtains a response to the user speech input 1014 based on the user speech input 1014 and context information included in the aggregated context (as will be described in more detail below with reference to fig. 9).

As shown by arrow 1022, in response to detecting a digital assistant trigger included in user voice input 1014, user device 1006 sends context information (and a device identifier corresponding to user device 1006) to common device 1008 (since the detection of the digital assistant trigger is a device state change and common device 1008 is a context collector). Note that while fig. 10 shows user device 1006 sending context information to public device 1008 after arrow 1020, user device 1006 sends context information at any time after public device 1004 detects a digital assistant trigger and sends context information to public device 1008 (as shown by arrow 1016). For example, user device 1006 can 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 a detection of a digital assistant trigger, the context information sent to common device 1008 includes a trigger advertisement corresponding to the digital assistant trigger detection of user device 1006. The trigger advertisement sent by user device 1006 includes the same types of data and information (e.g., data indicating the time at which the digital assistant trigger ended (e.g., the time at which user device 1006 stopped receiving audio signals corresponding to the digital assistant trigger)) that were included in the trigger advertisement previously sent by common device 1004.

Upon receiving the context information and trigger advertisement from user device 1006, common device 1008 updates the aggregated context of context sharing group 1012 to include the context information and trigger advertisement. Further, as illustrated by arrow 1024, in response to receiving the trigger advertisement from user device 1006, public device 1008 retrieves and sends to user device 1006 (e.g., trigger advertisements received within a predetermined time period (e.g., within the last 30 seconds, within the last minute, within the last 5 minutes, etc.) the trigger advertisement that has been included in the aggregated context (associated with the one or more other electronic devices participating in the context-sharing group including public device 1004). In some examples, instead of sending only the trigger advertisement, common device 1008 sends the aggregated context (including the received trigger advertisement) to user device 1006.

In some examples, in addition to sending the context information and trigger advertisement to the common device 1008 (via the network 1010), the user device 1006 sends the trigger advertisement (e.g., data corresponding to the trigger advertisement) 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 advertisement directly to the public device 1004 via the BTLE connection (e.g., before or shortly after sending the context information and trigger advertisement to the public device 1008). Then, in response to receiving the trigger advertisement from the user device 1006, the one or more electronic devices send their own trigger advertisements to the user device 1006 via their respective short-range communication connections. For example, the one or more electronic devices transmit trigger advertisements corresponding to digital assistant triggers that they detected within a predetermined time period (e.g., within the last 5 seconds, within the last 30 seconds, within the last minute, etc.).

After receiving the trigger advertisement from public device 1008 (and, in some examples, from one or more electronic devices with which user device 1006 shares a short-range communication connection), user device 1006 determines whether it should suppress its own digital assistant trigger detection (and thus forgo further processing of user voice input 1014). In particular, the user device 1006 determines whether each trigger advertisement that it has received (e.g., within the last second) is "reasonable" based on the digital assistant trigger end time included in each trigger advertisement (i.e., the time when the digital assistant trigger ends according to the electronic device). A trigger advertisement is reasonable if the digital assistant trigger end time of the trigger advertisement 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 speech input 1014 ended according to the user device 1006).

If the user device 1006 determines that one or more of the trigger notifications it has received are legitimate (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 foregoes further processing of the user speech input 1014. For example, if user device 1006 determines that a trigger advertisement corresponding to public device 1004 (e.g., a trigger advertisement received from public device 1008 and/or received from public device 1004) is legitimate, the user device foregoes further processing of user voice input 1014 so that public device 1004 will be the only electronic device providing a response to user voice input 1014. However, in some examples, public device 1004 receives one or more reasonable trigger notifications (e.g., from public device 1008 (e.g., as illustrated by arrow 1017)) corresponding to one or more other electronic devices that detected the digital assistant trigger, and thus also foregoes further processing of user voice input 1014 (e.g., rather than sending a request for aggregated context to public device 1008 (e.g., as illustrated by arrow 1018)).

If the user device 1006 determines that none of the trigger advertisements that it has received is reasonable (i.e., none of the trigger advertisements includes 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 speech input 1014 (e.g., by sending a request for an aggregated context to the common device 1008). This situation will occur, for example, under the following conditions: (1) the trigger advertisement of user device 1006 corresponds to a digital assistant trigger detected 30 seconds after common device 1004 detects a digital assistant trigger included in user speech input 1014, and (2) the predetermined time range is 500 milliseconds before a digital assistant trigger end time corresponding to the detection of the digital assistant trigger by user device 1006. In this example, the digital assistant trigger end time of the common device 1004 does not significantly fall within the 500 millisecond time range before the digital assistant trigger end time of the user device 1006. Thus, the user voice input received by user device 1006 represents a separate user request that user device 1006 should continue processing (e.g., separate from the user request for user voice input 1014).

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

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

As illustrated with arrow 922, upon receiving the request for the aggregated context from the public device 904, the public device 908 sends the aggregated context (or, in some examples, at least a portion of the aggregated context) to the public device 904. In some examples, the request for the aggregated context causes the 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 the public device 904. The aggregated context sent to the common device 904 includes context information (e.g., device state change information, context state information, device capability information, etc.) associated with at least the common device 904, the user device 906, and the user device 910 (e.g., because the common device 904, the user device 906, and the user device 910 each recently sent context information to the common device 908 in response to experiencing a device state change (e.g., a timer event)). In particular, the context information is associated with at least the common device 904, the user device 906, and the user device 910 based on a device identifier that the common device 908 receives along with the context information from at least the common device 904, the user device 906, and the user device 910. In some examples, the aggregation context does not include any other type of device identification or identification information other than the device identifier received with the context information included in the aggregation context. This, in turn, helps to ensure the anonymity of electronic devices participating in the context sharing group 914 when the server 916 receives the aggregated context (e.g., as shown by arrow 924).

In other examples, the aggregated context does include (in addition to device identification) other types of device identifications and/or information identifying registered users 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 two or more different users (as 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 aggregated context allows the server 916 to determine whether the user voice input was provided by the registered user. Further, as described below, in some examples, the server 916 uses the additional identifying information to access and/or utilize user data stored on the server 916 and associated with one or more of the electronic devices (e.g., user data previously synchronized/sent to a remote device by the electronic devices participating in the context sharing group 914 (e.g., during automatic and/or periodic user data synchronization)).

After receiving the aggregated context from the public device 908, the public device 904 provides (e.g., transmits) at least a portion of the aggregated context and data corresponding to the user voice input 918 to the server 916, as illustrated with arrow 924.

In some examples, public device 904 provides audio data corresponding to user voice input 918 to server 916. In some examples, the public device 904 (e.g., using STT processing module 730) performs voice-to-text processing of the user voice input 918 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 speech 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.

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

In some examples, prior to sending at least a portion of the aggregated context to the server 916, the public device 904 sends a request to the electronic devices (including the user device 906, the public device 908, and the user device 910) participating in the context sharing group 914 for each device to provide the public device 904 with an indication of whether it detected a digital assistant trigger included in the user voice input 918. In some examples, the public device 904 requests that each electronic device provide an indication to the public device 904 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 transmits the requested indication (also referred to as a trigger indication) along with its corresponding device identifier.

After receiving a trigger indication (indicating whether each of the one or more electronic devices detected a digital assistant trigger included in user voice input 918) from one or more (e.g., all) of the electronic devices participating in context sharing group 914, public device 904 incorporates the trigger indication into the aggregated context based on a device identifier received with the trigger indication. In particular, the common device 904 incorporates the trigger indications received from each electronic device into the context information (in terms of the device identifier of each electronic device) of the electronic devices included in at least a portion of the aggregated context. For example, the common device 904 incorporates the trigger indication received from the user device 906 into context information associated with a device identifier of the user device 906 included in at least a portion of the aggregated context. In some examples, the trigger indication includes data indicative of an 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 a confidence of the electronic device (e.g., user device 906) that the user speech input 918 includes a digital assistant trigger.

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 not a context collector). For example, user device 906 is unaware of user device 910. Thus, in these examples, the user equipment cannot send trigger indication requests or trigger indications directly to other user equipment. Thus, in these examples, the user device sends a trigger indication request to a context collector of the context-sharing group, such that the context collector can send the trigger indication request to all other electronic devices participating in the context-sharing group. The context collector then sends all trigger indications it receives back to the user equipment that sent the trigger indication request to the context collector. For example, to receive a trigger indication from the user device 910, the user device 906 sends a trigger indication request to the public device 908, such that the public device 908 can send the trigger indication request to both the user device 910 and the public device 904. Thus, the common device will receive trigger indications from the common device 904 and the user device 910, and then send those trigger indications (along with its own trigger indications) to the user device 906. In some examples, user device 906 sends the trigger indication request directly to public device 904 (e.g., in addition to sending the request to public device 908) because user device 906 still knows that the public device is participating in context sharing group 914.

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

As will be described in more detail below with reference to fig. 11, upon receiving data corresponding to the user voice input 918, the server 916 (and in particular, one or more modules of the server 916) processes the data corresponding to the user voice input 918 (e.g., based on contextual 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 are to 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 data and aggregated context corresponding to the user voice input 918 to the server 916. In these examples, the public device 904 (and in particular, one or more modules of the public device) processes data corresponding to the user voice input 918 (e.g., based on context information included in the aggregated context) and performs the above-listed determinations (rather than the server 916).

FIG. 11 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 functionality of system 1100 are distributed between one or more remote devices and one or more electronic devices participating in a context-sharing group.

The system 1100 is implemented using hardware, software, or a combination of hardware and software to perform the functions discussed herein. Further, system 1100 is exemplary, and thus system 1100 may have more or fewer components than illustrated, 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 the system 1100, it should be understood that these functions may be performed at other modules of the system 1100, and that these functions may be performed at more than one module of the system 1100.

To illustrate examples discussed herein, system 1100 is described with reference to fig. 9 and various components of system 900. Unless otherwise noted, system 1100 is implemented on server 916 in the examples described below.

The system 1100 includes a speech input receiver module 1102. The speech input receiver module 1102 receives data (e.g., audio data, text data, natural language processing results, etc.) corresponding to a user speech input from an electronic device 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 the user voice input 918 from the public device 904 (e.g., as indicated by arrow 924). In some examples, the voice input receiver module 1102 receives user voice input directly from a user. For example, when the system 1100 or the voice input-only 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 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.

System 1100 includes an aggregated context receiver module 1104. The aggregated context receiver module 1104 receives at least a portion of the aggregated context of the context-sharing group from the electronic devices participating in the context-sharing group (e.g., from the common 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, the aggregated context receiver module 1104 receives at least a portion of the aggregated context of the context sharing group 914 from the common device 904 (e.g., as illustrated by arrow 924). In some examples, the 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 just aggregation context receiver module 1104 is implemented on public device 904, aggregation context receiver module 1104 receives at least a portion of the aggregation context from public device 908 (the context collector of context sharing group 914) (as public device 904 receives at least a portion of the aggregation context from public device 908 (e.g., as illustrated by arrow 922)). Upon 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 the device identifier associated with the context information to the user intent module 1106, the device selection module 1110, and/or the command module 1112.

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

In some examples, determining the one or more user intents includes user intent module 1106 performing speech-to-text processing, natural language processing, and/or the like based on data corresponding to the user speech input. In these examples, the user intent module 1106 includes a speech to text processing module (e.g., STT processing module 730), a natural language processing module (e.g., natural language processing module 732), and so on. 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), determining the one or more user intents includes the user intent module 1106 performing voice-to-text processing based on the audio data. As another example, if the data corresponding to the user speech input 918 is text data (e.g., a textual representation of the user speech input 918), determining that the one or more user intents includes the user intent module 1106 performing natural language processing (but not speech-to-text processing because the user speech input 918 has been recognized (e.g., by the public device 904)) based on the text data.

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

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 user voice input to the voice input receiver module 1102 (e.g., the public device 904). For example, when data corresponding to user voice input 918 is sent to server 916, public device 904 may send the stored user data to server 916 (e.g., the user data may be included in the aggregation context). The user intent module 1106 can 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., 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).

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 a context sharing group and (2) does not provide data corresponding to user voice input to the voice input receiver module 1102. For example, user data used by the user intent module 1106 in performing speech to text processing of data corresponding to the user speech input 918 may include user data previously synchronized/sent by the user device 906 to the server 916. For example, if the user voice input 918 includes a unique name "celenerys Targaryen," the user intent module 1106 can identify 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, user data associated with user device 906 is not stored on public device 904 and is not synchronized/sent by public device 904 to server 916.

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

As described above, 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 the device identifier associated with the context information to the user intent module 1106. In some examples, the user intent module 1106 also determines one or more user intents based on the context information (associated with the one or more electronic devices) received from the aggregated context receiver module 1104.

In some examples, also determining the one or more user intents based on context information included in at least a portion of the aggregated context includes the user intent module 1106 disambiguating the user speech input based on the context information. 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 wishes 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 (e.g., the type of device state change and/or the time of the device state change) associated with the common device 904, the user device 906, the common device 908, and/or the user device 910 to determine what task the user 902 mentions 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 rings at the user device 906), the user intent module 1106 can determine that the user 902 wants to stop the timer event at the user device 906. Thus, in this example, the user intent module 1106 will determine a user intent to stop the timer.

In some examples, when the user speech input is ambiguous with respect to the task requested by the user and two or more events (e.g., timer event, alarm event, media playback, etc.) occur at two or more separate electronic devices in the context sharing group, the user intent module 1106 uses the device state change time information (e.g., data indicating the time at which each event started) to determine one or more user intents based on the most recent device state change. For example, if in the example above (where the user voice input 918 is "hey, Siri, stop."), the device state change information also indicates that there are media playback events occurring at the common device 904 (e.g., the common device 904 is currently playing music while a timer rings 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 at which each event started. In particular, the user intent module 1106 can determine which event started most recently based on the device state change time data, as the event is the most likely event to be mentioned by the user 902. Thus, if the timer event at the user device 906 begins 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.

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

Similarly, in yet another example, if the user speech input 918 is "hey, Siri, resume. "and the device state change information included in at least a portion of the aggregated context indicates that music previously played at the user device 906 stopped before 10 minutes and the movie played at the public device 908 stopped before 5 minutes (since stopping or pausing media playback is a device state change), the user intent module 1106 will determine that the movie playing at the public device 908 was more recently stopped or paused based on the device state change time data. Thus, the user intent module 1106 will determine the user intent to resume the movie rather than the user intent to resume the music.

As will be described in more detail below with reference to fig. 13, in some examples, the user intent module 1106 uses one or more digital assistant dialog session histories (included in the aggregated context) associated with one or more electronic devices to disambiguate the user voice input and determine one or more user intents corresponding to the user voice input.

The 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 the one or more user intents received from user intent module 1106. For example, based on the one or more user intents determined by the user intent module 1106 based on data corresponding to the user speech input 918 received by the speech input receiver module 1102 (and, in some examples, also based on contextual information included in the aggregated context received by the aggregated context receiver module 1104), the task determination module 1108 determines one or more tasks to be performed by the public device 904, the user device 906, the public device 908, and/or the user device 910. After determining the 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.

As will be described in greater 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 user intent module 1106 determines a user intent to stop the alarm (e.g., based on a user voice input of "black out, Siri, stop," or "black out, Siri, stop alarm"), task determination module 1108 will determine one or more tasks that, when executed by the electronic device, will cause the electronic device to stop the alarm. In some examples, the one or more tasks determined by task determination module 1108 are predetermined based on one or more user intents (e.g., the determined user intents correspond to the one or more tasks). Examples of one or more tasks that may be determined by task determination module 1108 include performing a search, retrieving information/data, opening an application stored on the electronic device, playing media (e.g., songs, videos, movies, etc.), making a purchase, authenticating a user, displaying the retrieved information/data, and so forth.

As will be described in more detail below with reference to fig. 13, in some examples, task determination module 1108 uses one or more digital assistant dialog session history associated with one or more electronic devices to disambiguate user speech input and determines one or more parameters of one or more tasks determined based on user intent corresponding to the user speech input.

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 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., the user device 906) participating in the context sharing group 914 to perform the one or more tasks. As another example, as will be discussed in more detail below with reference to fig. 12A-12B, the device selection module 1110 may select two or more electronic devices (e.g., the common 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., public device 904) that provides data corresponding to the user voice input to the voice input receiver module 1102. In some examples, the device selection module 1110 selects an electronic device (e.g., user device 906, public device 908, and/or user device 910) that does not provide data corresponding to the user voice input to the voice input receiver module 1102. In some examples, the device selection module 1110 selects a context collector (e.g., the common device 908) of the context sharing group.

After receiving the one or more tasks, the one or more user intents, and the 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 (e.g., a timer event, an alarm event, media playback, etc.) corresponding to a user intent of the one or more user intents currently occurs 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 a user voice input of "hey, Siri, stop."), the user intent module 1110 will determine whether there is an ongoing timer event at one or more electronic devices based on device state change information (e.g., data indicating the type of device state change) (e.g., associated with device identifiers of one or more electronic devices included in the aggregated context). For another example, if the device selection module 1110 receives a user intent to play the next song (e.g., based on a user voice input of "hey, Siri, play the next song"), the device selection module 1110 will determine whether a music playback event exists at one or more electronic devices based on device state change information associated with the electronic devices.

If the device selection module 1110 determines that an event corresponding to the user's intent 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 occurred) to perform one or more tasks.

If the device selection module 1110 determines that an event corresponding to the user's intention 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) has recently started based on data indicating a time of a device state change included in device state change information associated with the two or more electronic devices. For example, if device selection module 1110 receives a user intent to stop an alarm (e.g., "hey, Siri, stop" based on a user voice input) and 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), device selection module 1110 will determine (based on device state change data indicating the start time of each alarm event) whether the alarm event at user device 906 starts 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) has recently started, the device selection module 1110 selects the electronic device on which the event has recently started 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 is more recent to begin than the alarm event at the user device 906 (e.g., the alarm at the user device 910 does not begin to sound until the alarm at the user device 906 has sounded), the device selection module 1110 will select the user device 910 (in particular, the device selection module 1110 will select the device identifier corresponding to the user device 910).

In some examples, if the device selection module 1110 determines that an event corresponding to the user's 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 providing the user voice input data to the voice input receiver module 1102 based on 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 providing the user voice input data. For example, if device selection module 1110 receives a user intent to stop an alarm (e.g., "hey, Siri, stop" based on user voice input) and 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 sounded at each device), device selection module 1110 will determine (based on proximity information associated with user device 906 and user device 910) whether user device 906 or user device 910 is physically closest to common device 904. Then, if the device selection module 1110 determines that the user device 906 is physically closest to the common device 904, the device selection module 1110 will select the user device 906.

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 a user intent of 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 includes a user intent to resume movie playback and the predetermined time period is 10 minutes, the device selection module 1110 will determine whether to pause the movie in the last 10 minutes at one or more of the electronic devices participating in the context sharing group 914 (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 the determination in response to determining that an event corresponding to a user intent of 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 the one or more user intentions include a user intent to resume media playback (e.g., resume music playback, movie playback, etc.), the device selection module 1110 determines whether an event corresponding to a user intent of the one or more user intentions previously occurred at the one or more electronic devices. In some of these examples, in response to determining that the one or more user intents include a user intent to resume media playback, the device selection module 1110 determines whether an event corresponding to a user intent of the one or more user intents previously occurred at the one or more electronic devices within a predetermined time period, rather than determining whether an event corresponding to a user intent of the one or more user intents currently occurred at the one or more electronic devices.

In the above example, if the device selection module 1110 determines that an event corresponding to a user intent of 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 common device 904 is the only electronic device participating in the context sharing group 914 that paused music playback for a predetermined period of time (e.g., 30 minutes), the device selection module 1110 selects the common device 904.

Alternatively, if the device selection module 1110 determines that an event corresponding to a user intent of 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 providing the user voice input data to the voice input receiver module 1102 (e.g., because the electronic device may be the device closest to the user providing the user voice input) based on 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). Returning to the previous example, if the device selection module 1110 determines that the user device 906 also pauses music playback within a predetermined period of time (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 provides 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 provides 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 common device 904 to perform one or more tasks. Determining which electronic device in these examples will most recently prevent selection of an electronic device (e.g., and subsequent resumption of media playback) that is located in a disparate area of the location associated with the context-sharing group (e.g., other than where the user is located).

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). In particular, as described above, each trigger indication includes data indicative of whether the electronic device detected a digital assistant trigger included in the user speech input, such as data indicative of an 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 these examples, determining 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 comprises: 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 Help trigger energy level to perform one or more tasks.

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 context status information included in the aggregated context (e.g., instead of or in addition to proximity information). In particular, in examples where the context state information includes a current location of the electronic device participating in the context-sharing group (e.g., based on GPS data from GPS module 235 and/or from a software application having context-sharing group functionality (e.g.,

) For example, the device selection module 1110 compares the current locations of the two or more electronic devices and determines which electronic device is physically closest to the electronic device providing voice input data to the voice input receiver module 1102 based on the comparison. The device selection module 1110 then selects the closest electronic device to perform one or more tasks.

In some examples, if the device selection module 1110 determines that the two or more electronic devices are physically close to the electronic device providing the user voice input data to the voice input receiver module 1102 based on the proximity information and/or context state information included in the aggregated context, 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 respective 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 also physically proximate to the electronic device providing the user speech input data to the speech 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, the device selection module 1110 will determine that the public device 904 and the user device 906 are physically close to the public device 904 as well (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 the two or more electronic devices indicates that the two or more electronic devices are currently each located within the same area (e.g., the same room, the same office, etc.) of the location associated with the context-sharing group, the two or more electronic devices are physically proximate to the electronic device that provided the user voice input data to the voice input receiver module 1102 as well.

In some examples, in response to determining that an event corresponding to a user intent of the one or more user intentions 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 providing the user voice input data to the voice input receiver module 1102.

As will be described in more detail below, when the device selection module 1110 selects two or more electronic devices in the above-described examples, the device selection module 1110 provides (1) device identifiers corresponding to the two or more electronic devices, (2) one or more tasks, and (3) instructions for providing a command to the command module 1112 that causes an electronic device (e.g., the public 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 of the two or more electronic devices to perform the one or more tasks.

If the device selection module 1110 determines that an event corresponding to a user intent of the one or more user intents is not currently occurring at the electronic device participating in the context sharing group (and, in some examples, the event corresponding to the user intent has not previously occurred at the electronic device within a predetermined time period), the device selection module 1110 determines that the user intent corresponds to a user request to have a new event occur at the one or more electronic devices participating in the context sharing group. For example, if the user intent is to play music (e.g., based on the user voice input "hey, Siri, play Taylor Swift songs") and the device selection module 1110 determines (based on the device state change information included in the aggregated context) that a music playback event is not occurring at any electronic device participating in the context sharing group 914, then the device selection module 1110 will determine that the user intent corresponds to a user request to cause a new event (in this case, music playback) to occur at one or more electronic devices of the context sharing group 914.

After determining that the user intent corresponds to a user request to cause a new event to occur, device selection module 1110 determines whether one or more electronic devices participating in the context sharing group are available to perform one or more tasks based on device state change information included in the aggregated context (e.g., time of device state change, type of device state change, etc.). In some examples, device selection module 1110 also determines whether one or more electronic devices are available based on contextual state information associated with the electronic devices (e.g., data indicating display visibility of the electronic devices). An electronic device may not be available to perform one or more tasks if device state change information and/or context state information associated with the electronic device indicates that the electronic device is currently being used by a user (e.g., an open/active software application), is currently performing a task, and/or is currently unable to provide audio and/or visual output (e.g., because the electronic device is facing down, muting, playing media, etc.). For example, if the device state change information associated with the public device 908 indicates that the public device 908 is currently playing a movie, the device selection module 1110 will determine that the public device 908 is not available to perform one or more tasks. As another example, if the device state change information associated with the user device 906 indicates that a gaming software application stored on the user device 906 is currently open (e.g., such that the user is interacting with the gaming software application), the device selection module 1110 will determine that the user device 906 is not available to perform one or more tasks.

If the device selection module 1110 determines that one or more electronic devices are available to perform one or more tasks, the device selection module 1110 determines whether each of the one or more available electronic devices is capable of performing the one or more tasks based on device capability information (e.g., type of device, processing power, memory availability, display information (e.g., size of display), speaker information (e.g., loudness of speaker), etc.) included in the aggregated context. For example, if the one or more tasks include a task to display information, images, videos, etc., the electronic device may only perform the one or more tasks if the device has (or is communicatively connected to) a display. As another example, if performing the one or more tasks requires the electronic device to have a minimum amount of processing power and/or memory, and the device capability information associated with the electronic device indicates that the electronic device does not have the minimum amount of processing power and/or memory, the electronic device will not be able to perform the one or more tasks. In some examples, the device selection model also determines whether one or more available electronic devices are capable of performing one or more tasks based on contextual state information (e.g., strength of network connection, battery level, etc.) associated with the one or more available electronic devices. In some examples, the device selection module 1110 determines that the electronic device is a capable electronic device if the electronic device is capable of performing at least one of the one or more tasks.

If the device selection module 1110 determines that only a single electronic device participating in the context-sharing group is available and capable of performing one or more tasks, the device selection module selects the single electronic device to perform the one or more tasks.

If the device selection module 1110 determines that two or more electronic devices participating in the context-sharing group are available and capable of performing one or more tasks, 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 proximity information associated with the two or more available and capable electronic devices. For example, if the device selection module 1110 determines that both the user device 906 and the common device 908 are available and capable of performing one or more tasks, the device selection module 1110 will determine that either the user device 906 or the common device 908 are physically closer to the common device 904. Determining which electronic device is physically closest to the common device 904 ensures that the device selection module 1110 does not select the user device 906 to perform one or more tasks, for example, if the user device 906 is in a different area (e.g., in a different room, on a different floor, etc.) of the location associated with the context-sharing group 914 relative to the common device 904 (and thus relative to the user 902 (e.g., because the user is typically located near the electronic device that provides user voice input data to the voice input receiver module 1102)). This in turn improves the user experience.

As described above, in some examples, the proximity information is based on data included in one or more trigger indications included in the aggregated context. In particular, each trigger indication includes data indicative of whether the electronic device detected a digital assistant trigger included in the user speech input, such as data indicative of an 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 these examples, determining which of the two or more available and capable electronic devices is physically closest to the electronic device providing 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 available and capable 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.

In some examples, letThe alternative selection module 1110 determines which of the two or more available and capable electronic devices is physically closest to the electronic device providing the user voice input data to the voice input receiver module 1102 based on context status information included in the aggregated context (e.g., instead of or in addition to proximity information). In particular, in examples where the context state information includes a current location of the electronic device participating in the context-sharing group (e.g., based on GPS data from GPS module 235 and/or from a software application having context-sharing group functionality (e.g.,

) For example, the device selection module 1110 compares the current locations of the two or more available and capable electronic devices and determines which electronic device is physically closest to the electronic device providing voice input data to the voice input receiver module 1102 based on the comparison. The device selection module 1110 then selects the closest electronic device to perform one or more tasks.

In some examples, if the device selection module 1110 determines that two or more available and capable electronic devices are physically close to the electronic device providing the user voice input data to the voice input receiver module 1102 as well based on the proximity information and/or context state information included in the aggregated context, the device selection module 1110 determines whether a user of the electronic device providing voice input data to the voice input receiver module 1102 (e.g., a user providing voice input for the user) is viewing a display of an electronic device of the two or more available and capable electronic devices based on user attention information included in the aggregated context (e.g., data indicating whether the user is currently viewing the display of the electronic device (e.g., based on information from the optical sensors 264 at the front and/or rear of the electronic device)). As described above, in some examples, if the difference between the respective 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 also physically proximate to the electronic device providing the voice input data to the voice input receiver module 1102 for the user. In some examples, if the context state information associated with each of the two or more electronic devices indicates that the two or more electronic devices are currently each located within the same area (e.g., the same room, the same office, etc.) of the location associated with the context-sharing group, the two or more electronic devices are physically close to the electronic device that provided the user voice input data to the voice input receiver module 1102 as well.

In some examples, if the device selection module 1110 determines, based on user attention information associated with two or more available and capable electronic devices, that a user of the electronic device providing user voice input data to the voice input receiver module 1102 is viewing a single electronic device of the two or more available and capable electronic devices, the device selection module 1110 selects the single electronic device to perform two or more tasks. For example, if both the user device 906 and the user device 910 are (1) available and capable of performing one or more tasks and (2) physically close to the common device 904 as such (e.g., both devices are in the same room), but the user attention information associated with the devices indicates that the user 902 is viewing the user device 906 (rather than the user device 910), the device selection module 1110 will select the user device 906 to perform the one or more tasks. Selecting the electronic device that the user is viewing when two or more available and capable electronic devices are physically close together (as described above) improves the user experience. For example, if one or more tasks include displaying information, images, videos, etc., the user would have viewed the correct display to view the displayed information, images, videos, etc., rather than having to turn his or her attention to the display of another electronic device. This in turn improves the user experience.

In some of the above examples, if the two or more available, capable, and physically proximate electronic devices include an electronic device that provides user voice input data to the voice input receiver module 1102, but the device selection module 1110 determines that the user is only viewing another electronic device of the two or more available and capable electronic devices, the device selection module 1110 selects the electronic device that provides user voice input data to the voice input receiver module 1102. As will be described in greater detail below, in some examples, after making the above-described selection, the device selection module 1110 instructs the command module 1112 to provide a command and/or output (e.g., as an audio output and/or output on a display) to cause the selected electronic device to perform the one or more tasks to switch execution of the one or more tasks to a notification of the electronic device being viewed by the user. In addition to providing the device identifier and one or more tasks corresponding to the selected electronic device to the command module 1112, the device selection module also provides the instructions described above.

In some examples, if the device selection module 1110 determines, based on user attention information associated with two or more available and capable electronic devices, that a user of an electronic device providing user voice input data to the voice input receiver module 1102 is not viewing any of the two or more available and capable electronic devices (e.g., because none of the two or more available and capable electronic devices have a display or a communicatively connected display), the device selection module 1110 determines which of the two or more available and capable electronic devices has the largest display based on data indicative of display size included in device capability information associated with the two or more available and capable electronic devices (including communicatively connected displays (e.g., a display communicatively connected to a smart television). For example, if device selection module 1110 determines that (1) both user device 906 and public device 908 are available and capable of performing one or more tasks, (2) both user device 906 and public device 908 are physically close to public device 904 as well (e.g., both devices are in the same room), and (3) user 902 is not viewing user device 906 or public device 908, device selection module 1110 will determine whether user device 906 or public device 908 has the largest display (or is communicatively connected to the largest display). The device selection module 1110 then selects a single electronic device having the largest display (or communicatively connected to the largest display) of the two or more available and capable electronic devices.

In some examples, if the device selection module 1110 determines, based on user attention information associated with two or more available and capable electronic devices, that a user of an electronic device providing user voice input data to the voice input receiver module 1102 is not viewing any of the two or more available and capable electronic devices, the device selection module 1110 determines which of the two or more available and capable electronic devices has the loudest speaker (or is communicatively connected to the loudest speaker) based on data indicative of speaker loudness (e.g., a maximum decibel level) included in the device capability information associated with the two or more available and capable electronic devices. For example, if the device selection module 1110 determines that (1) both the user device 906 and the public device 908 are available and capable of performing one or more tasks, (2) both the user device 906 and the public device 908 are physically close to the public device 904 as well (e.g., both devices are in the same room), and (3) the user 902 is not viewing the user device 906 or the public device 908, the device selection module 1110 will determine whether the user device 906 or the public device 908 has the largest speaker (or is communicatively connected to the largest speaker). The device selection module 1110 then selects a single one of the two or more available and capable electronic devices having the loudest speaker (or communicatively connected to the loudest speaker).

In some examples, if the device selection module 1110 determines, based on user attention information associated with two or more available and capable electronic devices, that a user of the electronic device providing user voice input data to the voice input receiver module 1102 is not viewing any of the two or more available and capable electronic devices, the device selection module 1110 simply selects the two available and capable electronic devices. As will be described in more detail below, when the device selection module 1110 selects two or more available and capable electronic devices in the above-described examples, the device selection module 1110 provides (1) device identifiers corresponding to the two or more available and capable electronic devices, (2) one or more tasks, and (3) instructions for providing a command to the command module 1112 that causes an electronic device that provides user voice input data to the voice input receiver module 1102 (e.g., the public device 904) to output a query requesting the user to select an electronic device of the two or more electronic devices to perform the one or more tasks.

As will be described in more detail below with reference to fig. 12A-12B, in some examples, if the task determination module 1108 determines a plurality of tasks (e.g., more than one task) and the device selection module 1110 determines that two or more available and capable electronic devices are also physically proximate to the electronic device providing the user voice input data to the voice input receiver module 1102 based on proximity information and/or context state information included in the aggregated context, the device selection module 1110 selects at least two of the two or more electronic devices to each perform at least one of the plurality of tasks. These examples are referred to as "multimodal task execution" because the above selections cause two or more electronic devices to simultaneously execute tasks (of the multiple tasks) to satisfy a user request. For example, if the device selection module 1110 determines that both the user device 906 and the common device 908 are available, capable, and proximate to the common device 904 (e.g., in the same room), the device selection module may select both the user device 906 and the common device 908 to perform at least one task of the plurality of tasks. In these examples, after selecting at least two electronic devices to perform one or more tasks, the device selection module 1110 assigns a set of tasks of the plurality of tasks to each of the selected electronic devices. The set of tasks may include one of the plurality of tasks or a plurality of the plurality of tasks. Returning to the example above, device selection module 1110 can assign a first set of tasks to user device 906 (e.g., to perform a search, retrieve data/information, and provide an audio output (e.g., digital assistant response) including the retrieved data/information), assign a second set of tasks to common device 908 (e.g., to perform a search, retrieve data/information, and provide (e.g., display) a visual output (e.g., textual representation of digital assistant response output by user device 906) including the retrieved data/information). As described in the examples above, in some examples, the device selection module assigns one or more of the same tasks to each of the at least two selected electronic devices. For example, the device selection module 1110 may distribute the tasks of performing a search and retrieving data/information based on the search to all selected electronic devices (e.g., enabling each electronic device to provide an output including the retrieved data/information).

In some examples, rather than determining whether a user is viewing an electronic device of the two or more electronic devices based on user attention information included in the aggregated context, the device selection module 1110 selects at least two of the two or more available, capable, and proximate electronic devices for multimodal task execution. In some examples, the device selection module 1110 selects at least two of the two or more available, capable, and proximate electronic devices for multimodal task execution even if the device selection module 1110 determines that a user of the electronic device providing user voice input data to the voice input receiver module 1102 is viewing a single electronic device of the two or more available, capable, and proximate electronic devices.

In some examples, the device selection module 1110 selects the at least two electronic devices for multimodal task execution based on a plurality of tasks including one or more particular tasks (e.g., if the plurality of tasks include displaying a particular type of information (e.g., images, recipes, etc.), if the plurality of tasks include providing audio output and visual output, if the plurality of tasks include user authentication (e.g., for making a purchase), etc.). In these examples, if device selection module 1110 determines that the plurality of tasks includes one or more particular tasks, device selection module 1110 selects the at least two electronic devices for multi-modal task execution rather than (1) determining whether the user is viewing the electronic devices and/or (2) selecting a single electronic device that the user is viewing. For example, if the device selection module 1110 determines that the plurality of tasks includes a user authentication task, the device selection module 1110 may select the at least two electronic devices for multimodal task execution.

In some examples, the device selection module selects the at least two electronic devices for multimodal task execution based on the determined user intents corresponding to the plurality of tasks. In these examples, the device selection module selects the at least two electronic devices for multimodal task execution, rather than (1) determining whether the user is viewing the electronic devices and/or (2) selecting a single electronic device that the user is viewing. For example, if the plurality of tasks correspond to a user intent to provide a food recipe or a user intent to purchase a movie, the device selection module 1110 will select at least two electronic devices for multi-modal task execution in response to determining that the at least two electronic devices are available, capable, and proximate to the electronic device providing the user voice input data to the voice input receiver module 1102.

As will be described in more detail below, when the device selection module 1110 selects at least two electronic devices for multimodal task execution in the above example, the device selection module 1110 provides instructions to the command module 1112 that (1) device identifiers corresponding to the at least two electronic devices, (2) a set of tasks (of the plurality of tasks) associated with each device identifier, and (3) provide a command to each of the selected electronic devices that causes each electronic device to execute its associated set of tasks.

In some examples, the device selection module 1110 determines that none of the electronic devices participating in the context-sharing group are available. For example, if the context information included in the aggregated context indicates that the user device 906 and the user device 910 are facing downward (and thus do not have a visible display) and if the public device 904 and the public device 908 have performed tasks for the user and/or have software applications open/active (e.g., software applications with which the user is interacting), then all electronic devices in the context-sharing group will not be available. In these examples, the device selection module 1110 selects a single capable and/or proximate electronic device (proximate to the electronic device providing voice input data to the voice input receiver module 1102) as described above. In some examples, the device selection module selects more than one capable and/or proximate electronic device. Then, as will be described in more detail below, the device selection module 1110 provides to the command module 1112 (1) a device identifier corresponding to the selected electronic device, (2) one or more tasks, and (3) instructions for providing a command that causes the selected electronic device to output results of the execution of the one or more tasks within the notification (e.g., data retrieved based on the execution of the one or more tasks, audio and/or textual output data generated based on the execution of the one or more tasks, etc.). In some examples, the notification includes the retrieved data/information. In some examples, the notification provides a link or affordance that, when selected (e.g., pressed) by a user of the electronic device, causes the electronic device to output the digital assistant response as an audio output and/or as text on a display of the electronic device (e.g., a digital assistant response including the retrieved data/information).

As described above, in some examples, the system 1100 can access and utilize user data associated with one or more electronic devices participating in a context-sharing group when such user data is stored, for example, on one or more remote devices (e.g., server 916) implementing the system 1100. For example, the user intent module 1106 can access and utilize user data in determining one or more user intents. Similarly, in some of the above examples, after the device selection module 1110 selects an electronic device to perform one or more tasks (e.g., before the device selection module provides the device identifier, one or more tasks, and/or instructions to the command module 1112), the device selection module 1110 determines whether there is user data (e.g., the user's media, contacts, voice profiles, preferences, etc.) stored on one or more remote devices needed to perform the one or more tasks based on the determined user intent and/or one or more tasks. For example, if the one or more tasks include a task of playing a particular song (e.g., a song by a particular artist (e.g., "play a song by Taylor Swift," based on user voice input)), the device selection module may determine that audio data corresponding to the particular song is needed to perform the one or more tasks.

If the device selection module 1110 determines that there is stored user data needed to perform the one or more tasks, the device selection module determines whether the selected electronic device has access to the stored user data (e.g., if the stored user data is also stored locally on the selected electronic device, such that the selected electronic device may access and utilize the user data in performing the one or more tasks). The device selection module 1110 makes this determination based on the user data associated with the selected electronic device stored on the one or more remote devices (e.g., because the user data stored on the one or more remote devices indicates which user data is stored on the selected electronic device when, for example, the selected electronic device periodically synchronizes/transmits its stored user data to the one or more remote devices). In particular, if the user data required to perform the one or more tasks is not included in the user data associated with the selected electronic device stored on the one or more remote devices (e.g., the user data is included only in the stored user data associated with another electronic device participating in the context sharing group), the device selection module 1110 determines that the selected electronic device does not have access rights to the required user data. Returning to the previous example, if the selected electronic device is user device 906 and device selection module determines (stored on server 916) that the user data associated with user device 906 does not include audio data corresponding to a particular song (e.g., the audio data is only included in the stored user data associated with one or more other electronic devices (e.g., user device 910)), device selection module 1110 will determine that user device 906 does not have access to the audio data.

If the device selection module 1110 determines that the selected electronic device does not have access to user data needed to perform one or more tasks, the device selection module retrieves the stored user data and provides the user data to the command module 1112 (e.g., when the device selection module 1110 provides a device identifier, one or more tasks, and/or instructions to the command module 1112). In particular, the device selection module provides the command module 1112 with (1) a device identifier corresponding to the selected electronic device, (2) one or more tasks associated with the device identifier, (3) the retrieved user data, and (4) instructions to provide the selected electronic device with a command that causes the selected electronic device to perform the one or more tasks based on the retrieved user data. Returning to the previous example, upon determining that the user device 906 does not have access to stored audio data corresponding to a particular song, the device selection module 1110 will retrieve the audio from stored user data associated with another electronic device (e.g., the user device 910) participating in the context-sharing group 914 and then provide the audio data and a device identifier corresponding to the user device 906 to the command module 1112, such that the command module 1112 may generate a command that will cause the user device 906 to play the particular song using the retrieved audio data.

In some examples, another electronic device (e.g., user device 910) associated with the retrieved user data must register with the user providing the user voice input (e.g., user 902) in order for the device selection module 1110 to retrieve the user data for performing the task at the selected electronic device (e.g., user device 906). For example, if the user device 906 and the user device 910 are registered to two separate users, the device selection module 1110 will be unable to retrieve stored user data associated with the user device 910 for performing tasks at the user device 906 (or vice versa). In other examples, device selection module 1110 may retrieve stored user data associated with any electronic device currently participating in the context-sharing group (even if the registered user of the electronic device is different from the registered user providing the user voice input).

In some examples, the device selection module 1110 retrieves stored user data associated with a former electronic device only if an electronic device registered to a user providing user voice input is participating in the same context sharing group as the selected electronic device. For example, if the user 902 is a registered user of another electronic device that is not currently participating in the context-sharing group 914, the device selection module 1110 may not be able to retrieve user data associated with the other electronic device until the other electronic device joins the context-sharing group 914. As another example, if the user device 910 is registered with the user 902, but the user device 910 leaves the context sharing group 914 (e.g., by being disconnected from the network 912) before the device selection module 1110 retrieves the user data from the stored user data associated with the user device 910, the device selection module 1110 will be unable to retrieve the user data from the stored user data associated with the user device 910 or provide the user data to the command module 1112. Note that in some examples, a public device (e.g., public device 904) does not store user data and/or does not synchronize user data to a remote device (e.g., server 916). In these examples, device selection module 1110 may only retrieve and provide user data associated with user devices (e.g., user device 906 and/or user device 910) registered with the user providing the user voice input.

The system 1100 includes a command module 1112. The command module 1112(1) receives the device identifier, task, instruction, and/or user data from the device selection module 1110, (2) generates one or more commands based on the received device identifier, task, instruction, and/or user data, and (3) provides the one or more commands and associated device identifier (and, in some examples, user data) to the electronic device providing the voice input data to the voice input receiver module 1102 (e.g., because this is the only electronic device in communication with the remote device (e.g., server 916) that is participating in the context sharing group). For example, after determining the one or more commands, the command module 1112 sends the one or more commands and a device identifier associated with each command to the common device 904. As described above, the commands generated by the command module 1112 will cause the electronic device to perform various tasks based on the determinations and selections made by the device selection module 1110. In particular, the number of ways in which one or more commands are generated by the command module 1112 can vary based on the device identifier, task, instructions, and/or user data received from the device selection module 1110, each of which is discussed in turn below.

If the command module 1112 receives (1) a single device identifier corresponding to the selected electronic device and (2) one or more tasks, the command module 1112 will generate a command that will cause the selected electronic device to perform the one or more tasks. In some examples, the command further causes the selected electronic device to output an audio and/or visual digital assistant response based on the performance of the one or more tasks (e.g., "i have stopped your alarm," or "play a song of Taylor Swift now"). In some examples, the command module 1112 generates additional commands that will cause an electronic device providing the user voice input data to the voice input receiver module 1102 (e.g., the public device 904) to output an audio and/or visual digital assistant response indicating which electronic device was selected to perform one or more tasks (e.g., "a route description to san jose airport is ready on your phone" or "a photograph is now displayed on your television").

If the command module 1112 receives (1) two or more device identifiers corresponding to two or more electronic devices, (2) one or more tasks, and (3) an instruction to provide a command that causes an electronic device that provides user voice input data to the voice input receiver module 1102 (e.g., the common device 904) to output a query requesting the user to select an electronic device of the two or more electronic devices to perform the one or more tasks, the command module 1112 will generate two commands. The first command will cause the electronic device selected by the user to perform one or more tasks. The second command will cause the electronic device providing the user voice input data to the voice input receiver module 1102 to (1) output a query (e.g., as an audio output and/or as text on a display) requesting the user to select one of the two or more selected electronic devices to perform one or more tasks (e.g., "do you want to see your photo on your iPhone or your iPad?and (2) send the first command to the user-selected electronic device (e.g., after receiving a response from the user to the query (e.g., the response from the user is a second user voice input or a selection of a displayed affordance corresponding to one of the two or more electronic devices)).

In some examples, the first command further causes the user-selected electronic device to output an audio and/or visual digital assistant response based on the performance of the one or more tasks (e.g., "i have stopped your alarm." or "a song of a Taylor Swift is now playing"). In some examples, the second command further causes the electronic device providing the user voice input data to the voice input receiver module 1102 to output an audio and/or visual digital assistant response (e.g., "show a photograph on your iPad now") after receiving a user selection indicating the electronic device selected for performing one or more tasks.

If the command module 1112 receives instructions to (1) the device identifier corresponding to the selected electronic device, (2) one or more tasks, and (3) provide a command that causes the selected electronic device to output results of performing the one or more tasks within a notification, the command module 1112 will generate a command that will cause the selected electronic device to perform the one or more tasks and then provide a notification that includes results of performing the one or more tasks (e.g., appear on a lock screen interface of the selected electronic device, a notification in a notification history interface of the selected electronic device, etc.). In some examples, the command further causes the selected electronic device to output an audio indication when the notification is provided. In some examples, command module 1112 generates additional commands that will cause the electronic device providing the user voice input data to voice input receiver module 1102 (e.g., public device 904) to output an audio and/or visual digital assistant response indicating that none of the electronic devices participating in the context-sharing group are available to perform the one or more tasks and/or that further information related to the user's request can be found on the selected electronic device (e.g., "none of your devices at the moment can display a photo.

If the command module 1112 receives (1) a device identifier corresponding to the selected electronic device, (2) one or more tasks, (3) instructions to provide a command that causes the selected electronic device to output (e.g., as audio output and/or output on a display) a notification to switch execution of the one or more tasks to another electronic device (e.g., the electronic device that the user is viewing), and (4) a second device identifier corresponding to the other electronic device, the command module 1112 will generate a command that will cause the selected electronic device to output a notification to switch execution of the one or more tasks to another electronic device corresponding to the second device identifier (e.g., "do you prefer to view a thousand layers of recipes on your iPad"). In some examples, the command further causes the selected electronic device to perform one or more tasks, and then output a notification that switches the performance of the one or more tasks, along with the results of the performance of the one or more tasks, to another electronic device (e.g., "is here a thousand-level recipe i find.

If the command module receives (1) device identifiers corresponding to two or more selected electronic devices, (2) a set of tasks associated with each device identifier, and (3) instructions to provide each of the two or more selected electronic devices with a command that causes each electronic device to perform its associated set of tasks, the command module 1112 will generate a command for each device identifier. For example, if the command module 1112 receives a device identifier corresponding to the user device 906, a device identifier corresponding to the common device 908, and a set of tasks associated with each device identifier, the command module 1112 will generate a first command that will cause the user device 906 to perform its associated set of tasks and a second command that will cause the common device 908 to perform its associated set of tasks. In some examples, at least one of the two or more commands generated by the command module 1112 further causes the selected electronic device to output an audio and/or visual digital assistant response based on the performance of the one or more tasks (e.g., "there are several star wars movies for you to select, as displayed on your television.

In some examples, the command module 1112 determines whether the set of tasks received from the device selection module 1110 includes a user authentication (e.g., user authentication required to make a purchase) task. In these examples, if the command module 1112 determines that a set of tasks includes a user authentication task, the command module 1112 sends the set of tasks to the electronic device (e.g., the public device 904) that provided the user voice input data to the voice input receiver module 1102 and foregoes sending commands corresponding to the remaining set of tasks. The command module 1112 will forgo sending commands corresponding to the remaining set of tasks until the command module 1112 (or one or more other modules of the system 1100) authenticates the user (e.g., authenticates based on a comparison of stored user authentication data to authentication data provided to an electronic device performing a set of tasks including user authentication tasks), or until the command module 1112 (or one or more other modules of the system 1100) receives an indication from the electronic device providing user voice input data that the user has been authenticated (e.g., when the electronic device performing the set of tasks locally authenticates the user instead of providing authentication data for the command module 1112 to verify the user). After authenticating the user or receiving an indication that the user has been authenticated, the command module sends commands corresponding to the remaining set of tasks to the electronic device providing the user voice input data. An example of this process is described in more detail below with reference to fig. 12B.

If the command module 1112 receives instructions to (1) a device identifier corresponding to the selected electronic device, (2) one or more tasks associated with the device identifier, (3) the retrieved user data, and (4) provide a command to the selected electronic device that causes the selected electronic device to perform the one or more tasks based on the retrieved user data, the command module 1112 will generate a command that will cause the selected electronic device to perform the one or more tasks based on the retrieved user data. In some examples, the command further causes the selected electronic device to output an audio and/or visual digital assistant response based on the performance of the one or more tasks (e.g., "play the song of the Taylor Swift now" or "call the danerys targaryen"). In some examples, the command module 1112 generates additional commands that will cause an electronic device providing the voice input receiver module 1102 with user voice input data (e.g., the public device 904) to output an audio and/or visual digital assistant response indicating which electronic device was selected to perform one or more tasks (e.g., "play the song of Taylor Swift now on your HomePod", or "call danerys targaryen on your iPhone").

It is noted that while the above description describes different types of commands generated by the command module 1112 separately, it should be understood that in some examples, the command module 1112 generates more than one type of command in response to a single user voice input. For example, if the user voice input 918 is "hey, Siri, play a song of a Taylor Swift," the device selection module 1110 can provide to the command module 1112 (1) an instruction to provide a command that causes the common device 904 to output a query requesting the user 902 to select an electronic device to perform one or more tasks, (2) retrieved audio data corresponding to the song of the Taylor Swift, and (3) an instruction to provide the user selected electronic device with a command that causes the user selected electronic device to perform one or more tasks based on the retrieved audio data. In response, the command module 1112 may generate a first command that will cause the user-selected electronic device to perform one or more tasks based on the retrieved audio data, and a second command that will cause the common device 904 to (1) output a query (e.g., as audio output and/or as text output on a display) requesting the user to select an electronic device of the two or more selected electronic devices to perform the one or more tasks based on the retrieved audio data and (2) send the first command to the user-selected electronic device along with the retrieved audio data. Thus, as shown in the above example, the command module 1112 generates a first type of command (e.g., relating to performing one or more tasks based on the retrieved user data) and a second type of command (e.g., relating to the user selecting the electronic device to perform the one or more tasks) in response to a single user voice input.

After generating one or more commands (e.g., as described above), the command module 1112 transmits the one or more commands (and associated device identifiers) to the electronic device that provides the user voice input data to the voice input receiver module 1102. In the above example where the command module 1112 receives user data retrieved by the device selection module 1110, the command module 1112 further sends the user data (and associated device identifier) to the electronic device providing the user voice input data to the voice input receiver module 1102. As will be described in more detail below with reference to fig. 9, after receiving one or more commands (and, in some examples, user data), the electronic device providing the user voice input data to the voice input receiver module 1102 sends the one or more commands to the one or more electronic devices participating in the context-sharing group based on the device identifiers associated with the one or more electronic devices.

Returning to fig. 9, as indicated by arrow 926, the public device 904 receives a command (e.g., a command generated by the command module 1112) for performing one or more tasks and a device identifier (associated with the command) corresponding to the user device 906 from the server 916. In some examples, public device 904 also receives user data stored on server 916 (e.g., when the command is to perform one or more tasks based on the user data). It should be appreciated that although arrow 926 indicates that the common device receives a single command to perform one or more tasks at a single selected electronic device, the common device 904 may alternatively or additionally receive any type of command (or any combination of those command types) described above with reference to the command module 1112.

As illustrated by

arrows

928 and 928a, upon receiving a command to perform one or more tasks and a device identifier corresponding to the user device 906, the public device 904 sends the command to the user device 906 (e.g., based on the stored associations between electronic devices participating in the context sharing group 914 and their device identifiers). After the user device 906 receives the command, the command causes the user device 906 to perform one or more tasks. As described above, in some examples, public device 904 receives an additional command from server 916 that causes public device 904 to output an audio and/or visual digital assistant response that indicates that user device 906 is selected to perform one or more tasks (e.g., "i have stopped an alarm on your iPhone." "show a photo on your iPhone now").

In some examples, prior to sending the command to the electronic device (e.g., as shown by

arrows

928 and 928 a), the public device 904 determines whether a device identifier associated with the command corresponds to a client device (e.g., user device 906 or user device 910). If the public device 904 determines that the device identifier corresponds to a client device, the public device determines whether the user 902 is a registered user of the client device. For example, if the device identifier received by the public device corresponds to the user device 910 (and not the user device 906), the public device 904 may determine whether the user 902 is a registered user of the user device 910. Then, if the public device determines that the user 902 is not an registered user of the user device 910, the public device 904 determines whether the user 902 is an authorized user of the user device 910.

In some examples, the authorized user is a user of the client device that has been granted access to the control by a registered user and/or a user that made a user request on the client device (other than the registered user of the client device). In some examples, an authorized user of a client device may control the client device and/or make a user request on the client device only when the client device is participating in a context sharing group. Authorizing user information by a registered user of a client device via a software application stored on the client device (e.g., via a software application stored on the client device)

An application) and/or via a website having context sharing group functionality (e.g., when a registered user is registering a client device in a context sharing group, or at any time thereafter). Thus, returning to the previous example, the public device 904 determines whether the user 902 is an authorized user of the user device 910 by accessing authorized user information associated with the user device 910 (e.g., via a software application and/or a website). In some examples, determining whether the user 902 is an authorized user of the user device 910 includes the public device outputting a request for user authentication (e.g., voice authentication, password authentication, and/or biometric authentication (e.g., facial and/or fingerprint authentication)). Then, upon receiving the user authentication data from the user 902, the public device compares the user authentication data with user authentication data included in authorized user information associated with the user device 910 to determine whether the user 902 is an authorized user of the user device 910. As illustrated by

arrows

928 and 928b, in response to determining that the user 902 is an authorized user of the user device 910, the public device 904 sends a command to the user device 910.

Note that in some examples, the server 916 (e.g., the device selection module 1110) determines whether the user 902 is a registered user of the user device 910 prior to sending the command and the device identifier (corresponding to the user device 910) to the public device 904 (e.g., as illustrated by arrow 926). For example, the server 916 determines whether the user 902 is a registered user of the user device 910 based on user data associated with the user device 910 (e.g., user voice profile information associated with a registered user of the user device 910) stored on the server 916. In these examples, as illustrated by arrow 925, if the server 916 determines that the user 902 is not a registered user of the user device 910, the server 916 (e.g., the command module 1112) sends a command to the public device 904 that causes the public device 904 to output a request for user authentication, receives user authentication data (from the user 902), and then determines whether the user 902 is an authorized user of the user device 910 based on the received authentication data. Then, as shown by arrow 927, if public device 904 determines that user 902 is an authorized user of user device 910, public device 904 sends an indication that user 902 is an authorized user of user device 910 to server 916. Upon receiving the indication, the server 916 sends the command and the device identifier (corresponding to the user device 910) to the public device 904 (e.g., as illustrated by arrow 926), and the public device 904 sends the command to the user device 910 as illustrated by

arrows

928 and 928 b.

6. Systems and techniques for multi-modal task execution in context-sharing groups

12A-12B illustrate systems and techniques for multimodal task execution in a context sharing group, according to various examples. As shown in fig. 12A-12B, system 1200 includes a public device 1204, a public device 1206, and a user device 1210, all of which participate in a context-sharing group 1214 (which is associated with a particular location (e.g., home, office, etc.). User device 1210 is a client device (e.g.,

user device

104, 122, 200, 400, or 600). For example, the user equipment 1210 is

In the examples described below, the user device 1210 is registered to the user 1202. Public device 1204 is a smart speaker with the same or similar digital assistant capabilities as user device 1210. Public device 1206Is a smart television with the same or similar digital assistant capabilities as the user device. The common device 1206 is communicatively connected to a display 1208 (e.g., a television, monitor, etc.). Further, public device 1206 is a context collector of context-sharing group 1214 (e.g., because public device 1206 was previously picked as a context collector). As discussed above with reference to fig. 8, 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, common device 1204 is

The public device 1206 is Apple

System 1200 also includes a network 1212 and a server 1216 (e.g., DA server 106). The network 1212 is a wireless communication network (e.g., network 110). As shown, public device 1204, public device 1206, and user device 1210 communicate with each other and server 1216 via network 1212 (and thus are each connected to network 1212). Server 1216 is a remote device that does not participate in context-sharing group 1214. In some examples, system 1200 includes one or more other remote devices (e.g., a local server, a cloud computing system, etc.) in place of server 1216. It should be appreciated that any operations performed by public device 1204, public device 1206, and/or user device 1210 may alternatively be performed by server 1216 in these examples. For example, server 1216 may perform operations of public device 1204, public device 1206, and/or respective DA client modules (e.g., DA client modules 229) of user devices 1210.

As shown in fig. 12A, a user 1202 provides a user voice input 1218 that is received by public device 1204 (e.g., "hey, Siri, play me a" star wars "movie" or "hey, Siri, what is star wars").

As illustrated with arrow 1220, in response to receiving user voice input 1218 (or, in some examples, in response to detecting a digital assistant trigger included in user voice input 1218), public device 1204 sends a request (via network 1212) to public device 1206 (i.e., a context collector of context-sharing group 1214) for public device 1206 to send the aggregated context of context-sharing group 1214 to public device 1204.

As illustrated by arrow 1222, upon receiving a request for an aggregated context from the public device 1204, the public device 1206 sends the aggregated context (or, in some examples, at least a portion of the aggregated context) to the public device 1204. In some examples, the request for the aggregated context causes public device 1206 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 1204. The aggregated context sent to the public device 1204 includes context information (e.g., device state change information, context state information, device capability information, proximity information, etc.) associated with at least the public device 1204, the public device 1206, and the user device 1210 (e.g., because the public device 1204, the public device 1206, and the user device 1210 each recently experienced a device state change (e.g., a timer event, detection of a digital assistant trigger, playing a movie, etc.)). In particular, the context information is associated with at least the public device 1204, the public device 1206, and the user device 1210 based on a device identifier received by the public device 1206 along with the context information from at least the public device 1204, the public device 1206, and the user device 1210. In some examples, the aggregation context does not include any other type of device identification or identification information other than the device identifier received with the context information included in the aggregation context.

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

As illustrated by arrow 1224, upon receiving the aggregated context from public device 1206, public device 1204 provides (e.g., transmits) at least a portion of the aggregated context and data corresponding to user voice input 1218 to server 1216.

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

In some examples, public device 1204 provides all aggregated context to server 1216. In some examples, the public device 1204 determines which contextual information included in the aggregated context relates to the user speech input 1218 (e.g., when the public device 1204 performs natural language processing of the user speech input 1218), and only provides the relevant contextual information to the server 1216. In some examples, the public device 1204 determines which contextual information is relevant based on one or more domains of an active ontology (e.g., ontology 760) corresponding to the user voice input 1218 (e.g., by identifying contextual information that is relevant or related to the one or more domains corresponding to the user voice input 1218). In some examples, public device 1204 removes personal information (e.g., email addresses, home addresses, payment information, etc.) and/or user data (e.g., preferences, media, contacts, voice profiles, etc. of the user) included in the aggregated context before providing the aggregated context to server 1216. In some examples, public device 1204 encrypts personal information and/or user data included in the aggregated context (rather than removing the personal information and/or user data) prior to providing the aggregated context to server 1216.

After receiving at least a portion of the data and aggregated context corresponding to the user voice input 1218, the server 1216: (1) determine one or more user intents, (2) determine a plurality of tasks corresponding to the one or more user intents, (3) select two electronic devices to perform the plurality of tasks, and (4) generate two separate commands (based on data corresponding to the user voice input 1218 and contextual information included in at least a portion of the aggregated context), as described above with reference to fig. 11 and modules of system 1100. In particular, the server 1216 (e.g., the device selection module 1110) determines that both the public device 1204 and the public device 1206 are available, capable of performing at least one of the plurality of tasks, and is proximate to the public device 1204 (i.e., the device that provides data corresponding to the user voice input 1218 to the server 1216 (e.g., to the voice input receiver module 1102)). Thus, server 1216 selects common device 1204 and common device 1206 for multimodal task execution, and assigns a set of tasks to each device (where each set of tasks includes at least one task of the plurality of tasks). Thus, the server 1216 (e.g., the command module 1112) generates a first command for performing a first set of tasks and a second command for performing a second set of tasks. The first command is associated with a device identifier corresponding to the public device 1204 and the second command is associated with a device identifier corresponding to the public device 1206. Note that in some examples, one or more tasks in the first set of tasks are the same as one or more tasks in the second set of tasks (e.g., the first and second sets each include a task to perform a search and a task to retrieve data/information based on the search). Further, in some examples, the server 1216 selects more than two electronic devices for multimodal task execution (e.g., three electronic devices, four electronic devices, etc.), and thus assigns a set of tasks to each of the more than two electronic devices and generates independent commands for executing each set of tasks.

The server 1216 sends the first command and the second command, along with their associated device identifiers, to the common device 1204, as illustrated with arrow 1226. In some examples, server 1216 also sends user data stored on server 1216 to public device 1204 (e.g., so that public device 1204 and/or public device 1206 can perform one or more tasks based on the user data).

After receiving the first and second commands and their associated device identifiers, as illustrated by arrow 1228, the public device 1204 sends the second command to the public device 1206 based on the device identifier corresponding to the public device 1206 (e.g., based on the stored association between the electronic devices participating in the context-sharing group 1214 and their device identifiers). Further, based on the device identifier corresponding to the common device 1204 being associated with the first command, the common device 1204 determines that it is to perform the first set of tasks. Thus, after the common device 1206 receives the second command, the common device 1204 performs the first set of tasks, and the common device 1206 performs the second set of tasks. In some examples, common device 1204 and common device 1206 perform their respective set of tasks simultaneously, such that each device outputs the results of the performance of its respective set of tasks simultaneously.

In some examples, execution of the first set of tasks (performed by common device 1204) and the second set of tasks (performed by common device 1206) results in dividing the audio output and the visual output of the results of the execution of the tasks between common device 1204 and common device 1206. For example, if the user voice input 1218 were "hey, Siri, play me a star wars movie," the first and second set of tasks would each include tasks to perform a search of the star wars movie and retrieve data/information (e.g., movie title, year of last show, director, etc.) for the star wars movie. However, the first set of tasks will include tasks that output the retrieved data/information within an audio output (e.g., within a digital assistant response), while the second set of tasks will include tasks that output the retrieved data/information within a visual audio output. Thus, as shown by audio output 1230, after performing the first set of tasks, the public device 1204 will, for example, output (via one or more speakers) an audio digital assistant response that includes at least a portion of the retrieved data/information (e.g., "I found several" Star wars "movies; Star wars: New hope. Star wars: empire. …"). Further, as shown by results interface 1232, after performing the second set of tasks, common device 906 will, for example, display (on display 1208) an interface that includes at least a portion of the retrieved data/information (e.g., a "star wars" movie title with a corresponding image). Although in the above example two separate devices are providing output, the data/information included in the output is the same. As such, the user 1202 will be able to view the data/information included in the interface while hearing the corresponding data/information included in the audio output 1230. Thus, dividing the audio output and the visual output between at least two electronic devices (as described above) improves the user's digital assistant experience, as this ensures that the user is able to view and hear the response to the user request even if the device that initially received the user request does not, for example, have a display.

In some examples, execution of the first set of tasks (performed by common device 1204) and the second set of tasks (performed by common device 1206) causes one device to provide a summary response and the other device to provide a more detailed response. For example, if the user speech input 1218 is "hey, Siri, what is the star wars? "then the first set of tasks and the second set of tasks would each include tasks to perform a search for" star wars "and retrieve data/information associated with" star wars "(e.g., genre information, creator information, mapping information, country of origin, etc.). However, the first set of tasks will include tasks that output a short summary of the retrieved data/information, such as outputting a short list of data/information and/or a high-level overview of the data/information. Thus, as shown by audio output 1230, after performing the first set of tasks, public device 1204 will output, for example (via one or more speakers), an audio digital assistant response that includes a brief summary of the data/information retrieved by public device 1204. In some examples, audio output 1230 further instructs user 1202 to view public device 1206 for a more detailed response (e.g., "more information about star wars" is displayed on your television "). As shown in results interface 1232, after performing the second set of tasks, public device 1206 will, for example, display (on display 1208) an interface including a detailed summary of the retrieved data/information including hyperlinks, images, and/or other information not included in the short summary output by public device 1204 (e.g., a star wars movie title, a star wars page hyperlink, a star wars movie purchase link, etc. with corresponding images). It is noted that while the above examples separate the brief summary and the detailed summary between the audio output and the visual output, in some examples both the brief summary and the detailed summary are provided as visual outputs (e.g., on the displays of two separate devices). Providing a short summary and a detailed summary of the retrieved data/information in response to a user request (as described above) improves the user's digital assistant experience by ensuring that the user is able to view and/or hear a short response to the user request, while having the option of quickly viewing and/or hearing a more detailed response if the user desires more information on the requested subject (e.g., rather than having to provide a subsequent user request or perform a manual search for more detailed information).

Although not shown in FIG. 12A, after public device 1204 provides audio output 1230, public device 1204 sends context information to public device 1206 (e.g., because the provision of audio output 1230 is a device state change (e.g., the end of a digital assistant dialog session)). The contextual information includes a digital assistant dialog session history that includes data (e.g., text data) corresponding to the audio output 1230, as well as data indicative of the data/information retrieved as a result of performing the first set of tasks. Upon receiving the context information from public device 1204, public device 1206 incorporates the context information into the aggregated context. Similarly, after the common device 1206 provides the results interface 1232 (via display 1208), the common device incorporates its own contextual information into the aggregated context (e.g., because the provision of the results interface 1232 is a device state change (e.g., the end of a digital assistant response and/or the opening/activation of a software application)). The contextual information that the common device incorporates into the aggregated context includes data indicative of the data/information displayed in the results interface 1232 (e.g., data indicative of the results of performing the second set of tasks). The aggregated context that includes the new context information associated with public device 1204 and public device 1206 is referred to as an "updated aggregated context" in the following description.

As shown in fig. 12B, after public device 1204 provides audio output 1230 and public device 1206 provides result interface 1232, user 1202 provides user voice input 1234, which is received by public device 1204. In the example below, the user voice input 1234 is a user request to purchase media corresponding to a media item (e.g., a representation of an image, a video, a song, a movie, an e-book, a game software application, etc.) included in the results interface 1232. For example, if the results interface 1232 includes a media item (or a link and/or affordance for purchasing media) corresponding to a movie of the world war, the user voice input 1234 can be "hey, Siri, purchase of the world war: empire fight. "

As illustrated by arrow 1236, in response to receiving user voice input 1234 (or, in some examples, in response to detecting a digital assistant trigger included in user voice input 1234), public device 1204 sends a request (via network 1212) to public device 1206 that public device 1206 send the aggregated context of context sharing group 1214 to public device 1204.

Upon receiving a request for an aggregated context from public device 1204, public device 1206 sends the updated aggregated context to public device 1204, as illustrated with arrow 1238. As described above, the updated aggregated context includes updated context information associated with public device 1204 and updated context information associated with public device 1206.

As indicated by the arrow 1240, the common device 1204 sends at least a portion of the data and updated aggregated context corresponding to the user voice input 1234 to the server 1216 (e.g., to the voice input receiver module 1102 and the aggregated context receiver module 1104). After receiving at least a portion of the aggregated context of data and updates corresponding to the user voice input 1234, the server 1216: (1) determine one or more user intents, (2) determine a plurality of tasks corresponding to the one or more user intents, (3) select two electronic devices to perform the plurality of tasks, and (4) generate two separate commands (based on data corresponding to the user voice input 1234 and contextual information included in at least a portion of the updated aggregated context), as described above with reference to fig. 11 and modules of system 1100. In particular, the server 1216 (e.g., the device selection module 1110) determines that both the public device 1206 and the user device 1210 are available, capable of performing at least one of the plurality of tasks, and proximate to the public device 1204 (i.e., the device that provides data corresponding to the user voice input 1234 to the server 1216). Thus, the server 1216 selects the common device 1206 and the user device 1210 for multimodal task execution, and assigns a set of tasks to each device (where each set of tasks includes at least one task of the plurality of tasks).

Because the user voice input 1234 is a user request to purchase media, the server 1216 allocates a set of tasks (referred to as a third set of tasks) to the user device 1210 that includes one or more tasks for user authentication. In addition, server 1216 assigns a separate set of tasks (referred to as a fourth set of tasks) to public device 1206 that includes one or more tasks for purchasing the requested media. Thus, the server 1216 (e.g., the command module 1112) generates a third command for performing a third set of tasks and a fourth command for performing a fourth set of tasks. The third command is associated with a device identifier corresponding to the user device 1210 and the fourth command is associated with a device identifier corresponding to the common device 1206.

Prior to sending the third command and the fourth command, the server 916 (e.g., the command module 1112) determines that the third set of tasks includes one or more tasks for user authentication. Thus, as illustrated by arrow 1242, server 1216: (1) the third command and the device identifier corresponding to the user device 1210 are sent to the public device 1204, and (2) the fourth command and the device identifier corresponding to the public device 1206 are forgotten to be sent.

Upon receiving the third command and the device identifier corresponding to the user device 1210, the public device 1204 sends the third command to the user device 1210, as illustrated with arrow 1244. The third command then causes the user device 1210 to perform a third set of tasks, including one or more tasks for user authentication. For example, the third set of tasks includes outputting a request for a user (e.g., user 1202) to provide user authentication data (e.g., voice authentication data, password authentication data, and/or biometric authentication data (e.g., data corresponding to facial and/or fingerprint authentication)) to user device 1210. In some examples, the request includes user device 1210 displaying a user authentication interface (e.g., a password entry interface).

In this example, the third set of tasks includes tasks that send the received user authentication data to public device 1204. Thus, after the user device 1210 receives user authentication data from the user, the user device 1210 transmits the user authentication data to the public device 1204, as illustrated by arrow 1246. The public device then sends the user authentication data to the server 1216 as indicated by arrow 1248. Upon receiving the user authentication data, the server 1216 compares the received user authentication data with stored user authentication data associated with the user device 1210 (e.g., included in stored user data associated with the user device 1210 that was previously synchronized to the server 1216).

As illustrated with arrow 1250, if server 1216 determines, based on the comparison, that the user providing the user authentication data is authorized to make the requested purchase (e.g., because server 1216 determines that the received user authentication data matches the stored user authentication data), server 1216 sends a fourth command and a device identifier corresponding to public device 1206 to public device 1204. Alternatively, if server 1216 determines that the user providing the user authentication data is not authorized to make the requested purchase (e.g., because server 1216 determines that the received user authentication data does not match the stored user authentication data or because server 1216 determines that stored restrictions (e.g., household pipe) associated with the user prevent the user from making the requested purchase), server 1216 drops sending the fourth command to public device 1204.

In some examples, the third set of tasks includes tasks to authenticate the user locally based on the received user authentication data, rather than tasks to send the received user authentication data to the common device 1204. Thus, in these examples, after user device 1210 receives user authentication data from a user, user device 1210 compares the received user authentication to user authentication data stored on user device 1210 and determines whether the user providing the user authentication data is authorized to make the requested purchase. If the user device 1210 determines that the user is authorized to make the requested purchase, the user device 1210 sends an indication to the public device 1204 that the user is authorized to make the requested purchase. Public device 1204 then sends the indication to server 1216. In response to receiving the indication, server 1216 sends a fourth command and a device identifier corresponding to public device 1206 to public device 1204.

In some of the examples in which the third set of tasks includes the task of locally authenticating the user based on the received user authentication data rather than sending the received user authentication data to the public device 1204, the server 1216 sends the third command and the fourth command to the public device 1204 at the same time. The public device then sends the third set of tasks to the user device 1210, but foregoes sending the fourth command to the public device 1206 until the public device 1204 receives an indication from the user device 1210 that the user is authorized to make the requested purchase. Thus, if user device 1210 determines that the user is not authorized to make the requested purchase, public device 1204 will not send the fourth command to public device 1206.

Public device 1204 sends a fourth command to public device 1206 as illustrated with arrow 1252. The fourth command causes public device 1206 to perform a fourth set of tasks, which results in public device 1206 purchasing the requested media. In some examples, after purchasing the requested media, public device 1206 outputs the requested media via display 1208, as represented by media output 1254. It is noted that while the above examples relate to purchasing digital media, the above systems and processes are applicable to other types of user-requested purchases, such as purchasing physical objects (e.g., books, groceries, etc.) from a website. Assigning tasks for user authentication and purchase to separate electronic devices (as described above) allows a user to quickly and easily provide user authentication data when, for example, the electronic device to which the user requested purchase is to be made is further away from the user and/or has only less efficient user authentication capabilities (e.g., user authentication is performed only via manual password input).

In general, multimodal task execution improves a user's digital assistant experience because it creates the appearance of a single digital assistant that is aware of the user's context and surroundings and interacts with the user across multiple devices (rather than a separate digital assistant for each device).

7. Systems and techniques for persistent digital assistant sessions in context-sharing groups

Fig. 13 illustrates systems and techniques for conducting a persistent digital assistant session across multiple devices participating in a context-sharing group, according to various examples. As shown in fig. 13, system 1300 includes user device 1304, user device 1306, and public device 1308, all of which participate in context sharing group 1312 (which is associated with a particular location (e.g., home, office, etc.). User equipment 1304 and user equipment 1306 are all client devices (e.g.,

user devices

104, 122, 200, 400, or 600). For example, user equipment 1304 is

User device 1306 is Apple

In the examples described below, user device 1304 and user device 1306 are registered with user 1302. In some examples, only one of user device 1304 and user device 1306 is registered with user 1302. Public device 1308 is a smart speaker with the same or similar digital assistant capabilities as user device 1304 and user device 1306. Further, common device 1308 is a context collector for context sharing group 1312 (e.g., because common device 1308 was previously picked as a context collector). As discussed above with reference to fig. 8, 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, common device 1308 is

System 1300 also includes a network 1310 and a server 1314 (e.g., DA server 106). Network 1310 is a wireless communication network (e.g., network 110). As shown, user device 1304, user device 1306, and public device 1308 are in communication with each other and server 1314 (and thus each is connected to network 1310) via network 1310. The server 1314 is a remote device that does not participate in the context sharing group 1312. In some examples, system 1300 includes one or more other remote devices (e.g., local servers, cloud computing systems, etc.) in place of server 1314. It is to be appreciated that any operations performed by user device 1304, user device 1306, and/or public device 1308 may alternatively be performed by server 1314 in these examples. For example, server 1314 may perform operations for user device 1304, user device 1306, and/or a respective DA client module (e.g., DA client module 229) of public devices 1308.

As shown in fig. 13, a user 1302 provides a user voice input 1316 (e.g., "what is the temperature of Siri, pero"), which is received by the user device 1304.

As illustrated by arrow 1318, in response to receiving user voice input 1316 (or, in some examples, in response to detecting a digital assistant trigger included in user voice input 1316), user device 1304 sends a request (via network 1310) to public device 1308 (i.e., a context collector of context sharing group 1312) for public device 1308 to send the aggregated context of context sharing group 1312 to user device 1304.

As illustrated with arrow 1320, upon receiving a request for an aggregated context from the user device 1304, the common device 1308 sends the aggregated context (or, in some examples, at least a portion of the aggregated context) to the user device 1304. In some examples, the request for the aggregated context causes the common device 1308 to send the aggregated context (e.g., data corresponding to the aggregated context) or at least a portion of the aggregated context to the user device 1304. The aggregated context sent to the user device 1304 includes context information (e.g., device state change information, context state information, device capability information, proximity information, etc.) associated with at least the user device 1304, the user device 1306, and the public device 1308 (e.g., because the user device 1304, the user device 1306, and the public device 1308 each recently experienced a device state change (e.g., a timer event, detection of a digital assistant trigger, playing a movie, etc.)). In particular, the context information is associated with at least user device 1304, user device 1306, and common device 1308 based on a device identifier that common device 1308 receives along with the context information from at least user device 1304, user device 1306, and common device 1308. In some examples, the aggregation context does not include any other type of device identification or identification information other than the device identifier received with the context information included in the aggregation context.

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

After receiving the aggregated context from the public device 1308, the user device 1304 sends data corresponding to the user voice input 1316 and at least a portion of the aggregated context to the server 1314, as illustrated with arrow 1322.

In some examples, the user device 1304 provides audio data corresponding to the user voice input 1316 to the server 1314. In some examples, the user device 1304 performs speech-to-text processing of the user speech input 1316 (e.g., using the STT processing module 730) and provides text data corresponding to the user speech input 1316 (e.g., a textual representation of the user speech input 1316) to the server 1314. In some examples, the user device 1304 also performs natural language processing of the text data corresponding to the user speech input 1316 (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 1314.

In some examples, the user device 1304 provides all aggregated context to the server 1314. In some examples, the user device 1304 determines which contextual information included in the aggregated context relates to the user speech input 1316 (e.g., when the user device 1304 performs natural language processing of the user speech input 1316), and only provides the relevant contextual information to the server 1314. In some examples, the user device 1304 determines which contextual information is relevant based on one or more domains of an active ontology (e.g., ontology 760) corresponding to the user voice input 1316 (e.g., by identifying contextual information that is relevant or related to the one or more domains corresponding to the user voice input 1316). In some examples, the user device 1304 removes personal information (e.g., email addresses, home addresses, payment information, etc.) and/or user data (e.g., preferences, media, contacts, voice profiles, etc. of the user) included in the aggregated context before providing the aggregated context to the server 1314. In some examples, the user device 1304 encrypts personal information and/or user data included in the aggregation context (rather than removing the personal information and/or user data) prior to providing the aggregation context to the server 1314.

The server 1314 transmits, to the user device 1304, a first command to perform one or more tasks and a device identifier corresponding to the user device 1304, as illustrated with arrow 1324. After the user device 1304 receives the first command and determines that it is to perform the one or more tasks based on the associated device identifier corresponding to the user device 1304, the user device 1304 performs the one or more tasks. For example, if the user speech input 1316 is "he, Siri, how much the temperature of the pareto chart? ", the one or more tasks include performing a search for weather data associated with the pareto chart, retrieving the requested weather data (e.g., temperature data), and generating a digital assistant response including the retrieved weather data. The first command also causes the user device 1304 to output a digital assistant response based on the performance of the one or more tasks. Thus, as shown in fig. 13, the user device 1304 outputs the digital assistant response 1326 as an audio output (e.g., via one or more speakers). Returning to the previous example, if the user speech input 1316 is "hey, Siri, how much the temperature of the pareto chart? ", the digital assistant response 1326 may be" panoo current 68 degrees. "

As illustrated with arrow 1327, after the user device 1304 provides the digital assistant response 1326, the user device 1304 sends context information to the public device 1308 (e.g., because the output of the digital assistant response 1326 is a device state change (e.g., the digital assistant dialog session ends)). The contextual information includes a digital assistant dialog session history including data (e.g., textual data) corresponding to the user speech input 1316 and the digital assistant response 1326, as well as data/information retrieved as a result of the execution of the one or more tasks (e.g., weather data associated with a pareto chart). In some examples, the digital assistant dialog session history includes data corresponding to a most recent digital assistant dialog session occurring at the user device 1304 (e.g., speech recognition results, natural language processing results, and/or data retrieved and/or provided during the most recent digital assistant dialog session (e.g., data corresponding to recent user speech inputs and digital assistant responses)). In some examples, the digital assistant dialog session history includes data corresponding to all digital assistant dialog sessions occurring at the user device 1304 within a predetermined period of time (e.g., within a past hour, within a past day, etc.). Upon receiving the contextual information from the user device 1304, the public device 1308 incorporates the contextual information into the aggregated context and thus generates an updated aggregated context that now also includes the digital assistant dialog session history that the user device 1304 included in its contextual information.

As shown in fig. 13, sometimes after the user device 1304 outputs a digital assistant response 1326, the user 1302 moves from a first area (e.g., a living room, an office, etc.) to a second area (e.g., a bedroom, another office, a different floor of the location, etc.) of a location (e.g., the home of the user 1302, the office building in which the user 1302 works, etc.) in which the user device 1304 is located that is associated with the context-sharing group 1312. At a second region of the location, the user 1302 provides user voice input 1328 (e.g., "how long is he, Siri, do i take to drive thereDevice 1306 receives. In this case, user device 1306 is a wearable user device (e.g., Apple)

) And thus also in the second region when it receives user speech input 1328. In some examples, when user device 1306 receives user voice input 1328, user device 1306 is located in a first area of the location (where user device 1304 is located).

As illustrated with arrow 1330, in response to receiving user voice input 1328 (or, in some examples, in response to detecting a digital assistant trigger included in user voice input 1328), user device 1306 sends a request to public device 1308 for public device 1308 to send the aggregated context of context sharing group 1312 to user device 1306.

As illustrated with arrow 1332, upon receiving a request for an aggregated context from user device 1306, common device 1308 sends the updated aggregated context (or, in some examples, at least a portion of the updated aggregated context) to user device 1306. As described above, the updated aggregated context includes the digital assistant conversation session history that the user device 1304 provided to the common device 1308 (e.g., in addition to other contextual information included in the aggregated context associated with one or more electronic devices participating in the context-sharing group 1312).

After receiving the updated aggregated context from public device 1308, user device 1306 sends data corresponding to user voice input 1328 and at least a portion of the updated aggregated context to server 1314 as illustrated with arrow 1334. At least a portion of the updated aggregated context includes a digital assistant dialog session history that the user device 1304 provides to the public device 1308.

After receiving at least a portion of the data and updated aggregated context corresponding to the user voice input 1328, the server 1314: (1) determine one or more user intents, (2) determine one or more tasks corresponding to the one or more user intents, (3) select an electronic device to perform the one or more tasks (in this case, the user device 1306), and (4) generate commands for performing the one or more tasks (based on data corresponding to the user voice input 1328 and contextual information included in at least a portion of the updated aggregated context), as described above with reference to modules of fig. 11 and system 1100. In particular, the server 1314 uses the data corresponding to the user voice input 1316 included in the digital assistant dialog session history (which the public device 1308 added to the updated aggregated context) to disambiguate the user voice input 1328.

In some examples, the server 1314 (e.g., the task determination module 1108) uses the data corresponding to the user voice input 1316 to determine one or more parameters of one or more tasks determined based on the user intent corresponding to the user voice input 1328. For example, if the user speech input 1328 is "hey, Siri, how long did i take to drive there? ", the server 1314 will determine the user's intent to navigate to a location. However, the location parameters of the user speech input 1328 with respect to the navigation task are ambiguous. Thus, the server 1314 determines the location parameter of "perout view" based on the data corresponding to the user voice input 1316, because "perout view" is the location parameter for the user voice input 1316.

In some examples, the server 1314 (e.g., the user intent module 1106) uses the data corresponding to the user voice input 1316 to determine a user intent corresponding to the user voice input 1328. For example, if the user speech input 1328 is "hey, Siri, new york? ", the server 1314 will use the data corresponding to the user speech input 1316 (e.g., text data corresponding to the user speech input 1316, natural language processing results corresponding to the user speech input 1316, etc.) to determine that the user speech input 1328 represents a user request to the digital assistant to perform a task previously performed by the digital assistant of the user device 1304 using the parameters provided in the user speech input 1328 (e.g., the location parameter" new york "). Thus, if the user intent corresponding to the user voice input 1316 is a user intent to obtain weather information (e.g., because the user voice input 1316 is "what is the temperature of Siri, pajoram.

As illustrated by arrow 1336, server 1314 transmits a second command to user device 1306 to perform one or more tasks and a device identifier corresponding to user device 1306. After user device 1306 receives the second command and determines that it is to perform the one or more tasks based on the associated device identifier corresponding to user device 1306, user device 1306 performs the one or more tasks. For example, if the user speech input 1328 is "hey, Siri, ny? ", and the server 1314 determines that the user intent corresponding to the user voice input 1328 is to obtain weather information (as described above), the one or more tasks would include performing a search for weather data associated with new york, retrieving the requested weather data (e.g., temperature data), and generating a digital assistant response including the retrieved weather data. The second command also causes the user device 1306 to output a digital assistant response based on the execution of the one or more tasks. Thus, as shown in fig. 13, user device 1306 outputs digital assistant response 1338 as audio output (e.g., via one or more speakers), and in some examples, as visual output (e.g., text) on a display of user device 1306. Returning to the previous example, if the user speech input 1316 is "hey, Siri, new york woollen? ", the digital assistant response 1338 may be" new york current 45 degrees. "

As illustrated with arrow 1340, after user device 1306 provides digital assistant response 1338, user device 1306 sends context information to public device 1308 (e.g., because the output of digital assistant response 1338 is a device state change (e.g., the end of a digital assistant dialog session)). The contextual information includes a digital assistant dialog session history including data (e.g., text data) corresponding to the user voice input 1328 and the digital assistant response 1338, as well as data/information retrieved as a result of the execution of the one or more tasks (e.g., weather data associated with new york). Upon receiving the contextual information from user device 1306, public device 1308 incorporates the contextual information into the updated aggregated context, and thus generates a second updated aggregated context that now also includes the digital assistant dialog session history that user device 1306 included in its contextual information.

8. Process for providing a digital assistant in a context sharing group comprising at least two electronic devices

14A-14C illustrate flow diagrams representing processes for selecting a context collector for a context-sharing group, according to various examples. Process 1400 is performed, for example, using one or more electronic devices implementing a digital assistant. In some examples, one or more blocks of process 1400 are performed by one or more remote devices (e.g., one or more remote servers (e.g., DA server 106), one or more local servers, a cloud computing system, etc.). For example, the blocks of process 1400 are divided in any manner between one or more servers (e.g., DA server 106) and the client device. In other examples, the blocks of process 1400 are divided between one or more servers and a plurality of client devices (e.g., a mobile phone and a smart watch). Thus, while portions of process 1400 are described herein as being performed by a particular device, it should be understood that process 1400 is not so limited. In other examples, process 1400 is performed using only a client device (e.g., user device 104) or only a plurality of client devices. In process 1400, some blocks are optionally combined, the order of some blocks is optionally changed, and some blocks are optionally omitted. In some examples, additional steps may be performed in connection with process 1400.

In some examples, at block 1402, a first electronic device (e.g., a personal or client electronic device (e.g., a mobile device (e.g.,

) A tablet computer (e.g.,

) Smart watch (e.g., Apple)

) A desktop computer (e.g.,

) Or a laptop computer (e.g.,

) Or a public electronic device (e.g., a smart television (e.g., Apple)

) Or a smart speaker (e.g.,

) For example, user device 802) to a wireless network (e.g., a local Wi-Fi network (e.g., a Wi-Fi network of the user's home, office, etc.) (e.g., as shown by arrow 812 of fig. 8) at a first location.

In some examples, at block 1404, the first electronic device determines whether the first electronic device is registered in a context sharing group associated with the first location. In some examples, in accordance with a determination that the first electronic device is not registered in the context-sharing group, the first electronic device requests registration into the context-sharing group. In some examples, the first electronic device must register in the context-sharing group in order to join the context-sharing group (e.g., previously registered via a software application (e.g., HomeKit) stored on the first electronic device or via a website having context-sharing group functionality).

At block 1406, the first electronic device joins a context-sharing group associated with the first location (e.g., a set of one or more electronic devices (e.g., within a particular location) that automatically share context information (e.g., shared with a context collector) in response to a device state change) (e.g., as shown by context-sharing group 814 of fig. 8). The context-sharing group associated with the first location is a set of at least two electronic devices, each electronic device sharing context information with at least one other electronic device included in the set. The context-sharing group includes at least a second electronic device. In some examples, the first electronic device must connect to the wireless network in order to join the context sharing group at the first location. In some examples, each electronic device participating in the context sharing group is connected to a wireless network. In some examples, a first electronic device joins a context-sharing group by establishing a communication connection with (e.g., contextual information and other data may be wirelessly transmitted via) at least one other electronic device participating in the context-sharing group.

At block 1408, after joining the context-sharing group associated with the first location, the first electronic device chooses (e.g., selects) one of the set of at least two electronic devices as a context collector for the context-sharing group. In some examples, the first electronic device chooses a context collector in response to joining the context-sharing group (e.g., immediately after joining). In some examples, the first electronic device picks a context collector in response to an electronic device participating in the context-sharing group (e.g., the current context collector) leaving the context-sharing group (e.g., disconnecting from the wireless network at the first location).

At block 1410, the first electronic device determines a first context collector score corresponding to the first electronic device based at least on a strength of connectivity between the first electronic device and a wireless network of the first location. In some examples, the first context collector score is also based on a power state of the first electronic device (e.g., wired power connection versus battery power and/or remaining battery power). In some examples, the first context collector score is also based on a frequency with which the first electronic device moves in and out of the context-sharing group (e.g., a frequency of connecting/disconnecting to/from a wireless network at the first location).

In some examples, at block 1412, the first electronic device sends the first context collector score to at least a second electronic device included in the context sharing group (e.g., as illustrated by arrow 816).

At block 1414, the first electronic device receives, from at least the second electronic device, one or more context collector scores corresponding to the at least the second electronic device (e.g., as illustrated by arrow 818 of fig. 8). In some examples, the first electronic device further transmits a context collector indication indicating whether the first electronic device was previously elected as a context collector for the context-sharing group (e.g., when the first electronic device previously participated in the context-sharing group).

At block 1416, the first electronic device determines which of the electronic devices included in the context-sharing group to choose 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 the second electronic device. In some examples, the first electronic device determining which of the electronic devices included in the context-sharing group to choose as the context collector of the context-sharing group includes comparing the first context collector score to one or more context collector scores corresponding to at least the second electronic device, and identifying a highest context collector score based on the comparison, wherein the electronic device with the highest context collector score is chosen as the context collector.

In some examples, at block 1418, the first electronic device receives one or more context collector indications from at least the second electronic device (e.g., as illustrated by arrow 818 of fig. 8). The context collector indication indicates whether the electronic device is currently a context collector.

In some examples, at block 1420, the first electronic device determines whether the context-sharing group currently includes a context collector based on a context collector indication corresponding to the first electronic device and one or more context collector indications received from at least the second electronic device.

In some examples, at block 1422, the first electronic device also determines which of the electronic devices included in the context-sharing group to choose as the context collector for the context-sharing group based on whether the context-sharing group currently includes a context collector.

In some examples, at block 1424, in accordance with a determination that the context-sharing group currently includes a context collector, the first electronic device picks the current context collector as the context collector of the context-sharing group. In some examples, the second electronic device is a context collector of the context sharing group.

In some examples, at block 1426, in accordance with a determination that the context-sharing group includes more than one context collector (e.g., because the first electronic device was previously chosen as the context collector of the context-sharing group when previously participating in the context-sharing group), a determination is made as to which of the electronic devices included in the context-sharing group to choose as the context collector of 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.

At block 1428, in accordance with a determination to choose a first electronic device as a context collector, the first electronic device receives context information (e.g., device state change type), from at least a second electronic device in response to at least the second electronic device experiencing a device state change (media playback, application activation, timer event, alarm event, power state change (e.g., power on/off), display visibility change (e.g., turning the second electronic device from a display-down position to a display-up position (e.g., in the display-up position, the display of the second electronic device is visible to a user of the second electronic device)), digital assistant trigger (e.g., "black, Siri," "Siri," etc.) detection and/or end of a digital assistant dialog session), from at least the second electronic device, Device state change time, etc.), device capability information, context state information (e.g., current location, acceleration, display visibility, user attention, etc.), user-specific information (e.g., corresponding to a registered user of the electronic device), etc. (e.g., as represented by alarm event 820 and arrow 822a of fig. 8).

In some examples, at block 1430, the first electronic device receives a request from the second electronic device for an aggregated context of the context-sharing group (e.g., a stored set of context information received from one or more (e.g., each) electronic devices participating in the context-sharing group (e.g., when the one or more electronic devices undergo a device state change)). In some examples, the second electronic device sends the request to the first electronic device in response to receiving a user voice input from a user of the second electronic device.

In some examples, at block 1432, the first electronic device sends the aggregated context to the second electronic device. In some examples, sending the aggregated context to the second electronic device causes the second electronic device to obtain a digital assistant response to the user speech input based on context information included in the aggregated context. In some examples, obtaining the digital assistant response includes transmitting at least a portion of the user speech input and the aggregated context to a remote device (e.g., one or more servers, local servers, cloud computing systems, etc.) that does not participate in the context-sharing group, such that the remote device determines the digital assistant response or determines one or more tasks for the second electronic device to perform. In an example where the remote device determines the one or more tasks, the second electronic device performs the one or more tasks and determines a digital assistant response based on results of the performance of the one or more tasks.

In some examples, at block 1434, in accordance with the determination to choose the second electronic device as the context collector, the first electronic device sends context information associated with the first electronic device to the second electronic device in response to the first electronic device experiencing a device state change (e.g., as illustrated by alarm event 820 and arrow 822b of fig. 8).

15A-15B illustrate flow diagrams representing processes for performing one or more tasks in a context-shared group, according to various examples. Process 1500 is performed, for example, using one or more electronic devices implementing a digital assistant. In some examples, one or more blocks of process 1500 are performed by one or more remote devices (e.g., one or more remote servers (e.g., DA server 106), one or more local servers, a cloud computing system, etc.). For example, the blocks of process 1500 are divided in any manner between one or more servers (e.g., DA server 106) and the client device. In other examples, the blocks of process 1500 are divided between one or more servers and a plurality of client devices (e.g., a mobile phone and a smart watch). Thus, while portions of process 1500 are described herein as being performed by a particular device, it should be understood that process 1500 is not so limited. In other examples, process 1500 is performed using only a client device (e.g., user device 104) or only a plurality of client devices. In process 1500, some blocks are optionally combined, the order of some blocks is optionally changed, and some blocks are optionally omitted. In some examples, additional steps may be performed in connection with process 1500.

At block 1502, a first electronic device (e.g., public device 904) participating in a context-sharing group associated with a first location receives a user voice input (e.g., "hey, Siri, stop timer", hey, Siri, play music ", etc.) (e.g., as illustrated by user voice input 918 of fig. 9). The context-sharing group is a collection of at least two electronic devices that each share context information with at least one other electronic device included in the collection (e.g., as shown by context-sharing group 914 of fig. 9). The set includes at least a second electronic device (e.g., user device 906, user device 910, or public device 908) and a context collector (e.g., public device 908). In some examples, the second electronic device is a context collector. In some examples, the context collector is a third electronic device participating in the context sharing group. In some examples, each electronic device participating in the context-sharing group is connected to a single wireless network (e.g., a Wi-Fi network) at the first location.

In some examples, at block 1504, in response to receiving the user voice input, the first electronic device sends a request to the context collector to send the aggregated context of the context-sharing group to the first electronic device (e.g., as illustrated by arrow 920). The request causes the context collector to send the aggregated context to the first electronic device (e.g., as illustrated by arrow 922 of fig. 9).

At block 1506, the first electronic device receives aggregated context for the context-sharing group from a context collector (e.g., a set of context information received from one or more (e.g., each) electronic devices participating in the context-sharing group (e.g., device state change information (e.g., type of state change and time of state change), context state information (e.g., device location, display visibility (e.g., display up or display down), user attention information (e.g., whether the user is viewing the device display), strength of network connection, battery level, power type (e.g., battery versus wired power), etc.) and/or device capability information (e.g., device type, processing capability, memory availability, display information, speaker information, etc.)) (e.g., as indicated by arrow 922 in fig. 9). In some examples, the context information included in the aggregated context indicates whether the electronic device is available (e.g., whether the electronic device is currently being used (e.g., an open/active application), is currently performing a task, and/or is currently unable to provide audio and/or visual output (e.g., because the electronic device is facing down)).

In some examples, prior to receiving the aggregated context, at least the first electronic device and the second electronic device provide context information included in the aggregated context to the context collector. In some examples, 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. In some examples, the context information includes device state change information (e.g., data indicating a type of device state change and/or a time of the device state change) corresponding to at least the first electronic device and the second electronic device. In some examples, the context information includes context state information corresponding to at least the first electronic device and the second electronic device (e.g., device location, display visibility (e.g., display up or display down), user attention information (e.g., whether the user is viewing the device display), strength of the network connection, battery level, power type (e.g., battery versus wired power), etc.). In some examples, the context information includes device capability information (e.g., device type, processing capability, memory availability, display information, speaker information, etc.) corresponding to at least the first electronic device and the second electronic device.

In some examples, at block 1508, prior to transmitting at least a portion of the aggregated context to a remote device (e.g., one or more servers) that is not participating in the context sharing group, the first electronic device sends a request to the second electronic device to provide an indication (e.g., a trigger indication) to the first electronic device by the second electronic device, the indication being whether the second electronic device detected (e.g., received or heard) a digital assistant trigger included in the user speech input. The first electronic device sends the request when the user speech input includes a digital assistant trigger (e.g., a word or phrase (e.g., "hey, Siri," "Siri," etc.) that initiates a dialog session with a digital assistant of the electronic device). In some examples, the first electronic device requests the second electronic device to provide an indication (e.g., a trigger indication) to the first electronic device as to whether the second 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 some examples, the first electronic device sends a request for an indication of a trigger to each electronic device participating in the context-sharing group. In these examples, the request is for each electronic device to provide an indication of whether each electronic device detected a digital assistant trigger.

In some examples, at block 1510, after receiving the indication from the second electronic device (e.g., indicating that the second electronic device detected or did not detect a digital assistant trigger), the first electronic device incorporates the indication into contextual information associated with the second electronic device included in the aggregated context (e.g., incorporates the indication as device proximity information). After receiving the contextual information including the indication, the remote device determines a physical proximity of the second electronic device to the first electronic device based on the indication (e.g., based on data included in the indication) (e.g., when determining one or more tasks and/or selecting an electronic device to perform the one or more tasks). In some examples, the indication includes data indicative of an energy level (e.g., decibel level) of the digital assistant trigger (e.g., the energy level of the digital assistant trigger when received by the second electronic device). In some examples, the indication includes a confidence score corresponding to a confidence of the second electronic device that the user speech input includes a digital assistant trigger.

At block 1512, the first electronic device provides (e.g., sends) at least a portion of the aggregated context and data corresponding to the user voice input to a remote device (e.g., one or more servers) that is not participating in the context-sharing group (e.g., as shown by arrow 924 of fig. 9).

In some examples, the first electronic device provides all aggregated context to the remote device. In some examples, the first electronic device determines which contextual information included in the aggregated context relates to the user speech input (e.g., when the first electronic device performs natural language processing of the first user input), and only provides the related contextual information to the remote device. In some examples, the first electronic device determines which contextual information is relevant based on one or more domains of the active ontology corresponding to the user speech input (e.g., by identifying contextual information relevant to the one or more domains). In some examples, the first electronic device removes personal data (e.g., personal information and/or user data) included in the aggregated context prior to providing the aggregated context to the remote device. In some examples, the first electronic device encrypts personal data (e.g., personal information and/or user data) included in the aggregated context prior to providing the aggregated context to the remote device.

In some examples, a first electronic device provides audio data to a remote device. In some examples, the first electronic device performs speech recognition processing of the user speech input (e.g., speech to text processing) and provides text data corresponding to the user speech input (e.g., a text representation of the user speech input) to the remote device. In some examples, the first electronic device performs natural language processing of the user's voice input and provides results of the natural language processing (e.g., one or more user intents) to the remote device.

In some examples, the user speech input is ambiguous with respect to the electronic device defining that the user speech input is to be responded to (e.g., the user speech input such as "hey, Siri, stop" when an event (e.g., a timer event or an alarm event) occurs at two separate electronic devices participating in the context sharing group). In some of these examples, after the remote device (e.g., the speech input receiver module 1102 and the aggregated context receiver module 1104 of fig. 11) receives the data corresponding to the user speech input and at least a portion of the aggregated context from the first electronic device, the remote device (e.g., the user intent module 1106 of fig. 11)) disambiguates the user speech input based on context information included in the at least a portion of the aggregated context (e.g., the remote device determines which event has recently started using data indicating a time of a device state change included in the aggregated context because the event is the most likely event to be mentioned by the user (and thus determines the electronic device that the user is most likely to mention)).

In some examples, both the first electronic device and the second electronic device are personal electronic devices (e.g., client devices) that are each registered to a single user. In some of these examples, after a remote device (e.g., the speech input receiver module 1102 and the aggregated context receiver module 1104 of fig. 11) receives at least a portion of the data and the aggregated context corresponding to the user speech input from the first electronic device, the remote device (e.g., the user intent module 1106 of fig. 11) disambiguates one or more single words included in the user speech input based on user data associated with the second electronic device. In some examples, the user data associated with the second electronic device includes contacts stored on the second electronic device, a user voice profile generated based on user voice input received at the second electronic device, and/or media (e.g., songs, images, etc.) stored on the second electronic device. In some examples, user data associated with the second electronic device is stored on the remote device (e.g., the second electronic device periodically synchronizes the user data to the remote device). In some examples, the remote device disambiguates (e.g., recognizes one or more words included in) the user voice input using the user voice profile data associated with the second electronic device and/or the stored contact information associated with the second electronic device.

At block 1514, the first electronic device receives, from the remote device, a command to perform one or more tasks (e.g., one or more tasks to be performed by the electronic devices of the context-sharing group to satisfy the user intent corresponding to the user voice input) and a device identifier (e.g., data indicative of the second electronic device) corresponding to the second electronic device (e.g., as shown by arrow 926 of fig. 9). In some examples, the electronic device is assigned a device identifier when the electronic device joins the context-sharing group. In some examples, at least a portion of the aggregated context includes a device identifier of each electronic device currently participating in the context-sharing group (e.g., associated with context information for each electronic device). The remote device (e.g., task determination module 1108 and device selection module 1110 of fig. 11) determines the one or more tasks and selects a device identifier based on the data corresponding to the user voice input and contextual information included in at least a portion of the aggregated context.

In some examples, the context-sharing group further includes a fourth electronic device. In some examples, the first electronic device, the second electronic device, and the fourth electronic device are all personal electronic devices (e.g., client devices) that are each registered to a single user. In some of these examples, at block 1516, the first electronic device receives user data associated with the fourth electronic device from the remote device (e.g., the first electronic device receives the user data prior to, concurrently with, or shortly after receiving the command) before sending the command to the second electronic device (based on the device identifier corresponding to the second electronic device). In some examples, the user data associated with the fourth electronic device includes contact information stored on the fourth electronic device and/or media (e.g., songs, images, videos, etc.) stored on the fourth electronic device. In some examples, user data associated with the fourth electronic device is also stored on the remote device (e.g., the fourth electronic device periodically synchronizes the user data to the remote device).

In some examples, both the first electronic device and the second electronic device are personal electronic devices (e.g., client devices) that are each registered to a different user. In some of these examples, at block 1518, the first electronic device outputs a request for user authentication (e.g., voice authentication, password authentication, and/or biometric authentication (e.g., facial and/or fingerprint authentication)) before sending the command to the second electronic device. In some examples, the first electronic device determines that the second electronic device is registered to a different user, and in response to the determination, outputs a request for user authentication. In some examples, the remote device determines that the first electronic device and the second electronic device are each registered to a different user. In these examples, the first electronic device receives the second command and a device identifier corresponding to the first electronic device from the remote device (e.g., as shown by arrow 925 of fig. 9) prior to outputting the request for user authentication. The second command then causes the first electronic device to output a request for authentication. In some examples, the second command is received at the same time the command is received (received at block 1514), and the first electronic device executes the second command before sending the command to the second electronic device.

In some examples, at block 1520, the first electronic device receives authentication data from a user of the first electronic device.

In some examples, at block 1522, after receiving the authentication data, the first electronic device transmits a 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. In some examples, the user previously registered with the second electronic device as an authorized user of the second electronic device. In some examples, the user of the second electronic device registers the user of the first electronic device as an authorized user of the second electronic device. In some examples, a user of the first electronic device is registered as an authorized user of the second electronic device via a software application (e.g., HomeKit) stored on the first electronic device and/or the second electronic device and/or via a website. In some examples, the first electronic device transmits authentication information received from the user to the remote device (e.g., as illustrated by arrow 927 of fig. 9). In these examples, the remote device determines that the user is an authorized user of the second electronic device, and thus instructs the first electronic device to send the command to the second electronic device (e.g., via the second command).

At block 1524, the first electronic device transmits a command to the second electronic device based on the device identifier (e.g., as illustrated by

arrows

928a or 928b of fig. 9). The command causes the second electronic device to perform one or more tasks. In some examples, the command further causes the second electronic device to output the user query (e.g., as an audio output and/or via a display) after performing the one or more tasks. In some examples, the user query asks whether a second command to execute the one or more tasks is sent to a fourth electronic device participating in the context sharing group. In some examples, the command causes the second electronic device to output the user query prior to performing the one or more tasks.

In some examples of the above examples in which the first electronic device receives (at block 1516) user data associated with the fourth electronic device, at block 1526 the first electronic device sends the user data associated with the fourth electronic device to the second electronic device along with a command (e.g., in response to the user voice input "black, Siri, play a song of the Taylor Swift," the server provides data (e.g., audio data) stored on the fourth electronic device to the first electronic device corresponding to the song of the Taylor Swift so that the second electronic device can subsequently play the song of the Taylor Swift despite the song not being stored on the second electronic device). In these examples, the command sent to the second electronic device causes the second electronic device to perform one or more tasks based on the user data.

Fig. 16A-16E illustrate flow diagrams representing processes for identifying electronic devices participating in a context-sharing group to perform one or more tasks, according to various examples. Process 1600 is performed, for example, by one or more servers (e.g., DA server 106). In some examples, process 1600 is performed, for example, by one or more other remote devices or a combination of remote devices (e.g., one or more local servers, cloud computing systems, etc.). In some examples, one or more blocks of process 1600 are performed using one or more electronic devices implementing a digital assistant. For example, the blocks of process 1600 are divided in any manner between one or more servers (e.g., DA server 106) and client devices. In other examples, the blocks of process 1600 are divided between one or more servers and a plurality of client devices (e.g., a mobile phone and a smart watch). Thus, while portions of process 1600 are described herein as being performed by a particular device, it should be understood that process 1600 is not so limited. In other examples, process 1600 is performed using only a client device (e.g., user device 104) or only a plurality of client devices. In process 1600, some blocks are optionally combined, the order of some blocks is optionally changed, and some blocks are optionally omitted. In some examples, additional steps may be performed in connection with process 1600.

At block 1602, one or more servers (e.g., server 916 (e.g., voice input receiver module 1102 and aggregated context receiver module 1104 of fig. 11)) receive, from a first electronic device (e.g., public device 904) participating in a context-sharing group associated with a first location, user voice input and at least a portion of an aggregated context of the context-sharing group (e.g., as illustrated by arrow 924 of fig. 9). The context-sharing group (e.g., context-sharing group 914) is a collection of multiple electronic devices, each of which shares context information with at least one other electronic device included in the collection. In some examples, each electronic device of the plurality of electronic devices is connected to a single wireless network (e.g., a Wi-Fi network) at the first location. In some examples, at least one of the electronic devices participating in the context-sharing group is connected to the single wireless network, and the remaining electronic devices participating in the context-sharing group are connected to the at least one electronic device via one or more wireless communication connections (e.g., short-range communication connections (e.g., bluetooth and/or BTLE)).

An aggregated context is, for example, a set of context information (e.g., device state change information (e.g., type of state change and time of state change), context state information (e.g., device location, display visibility (e.g., display up or display down), user attention information (e.g., whether the user is viewing the device display), strength of network connection, battery level, power type (e.g., battery versus wired power), etc.), and/or device capability information (e.g., device type, processing capability, memory availability, display information, speaker information, etc.)) received from one or more (e.g., each) electronic devices participating in a context sharing group. In some examples, the context information (e.g., device state change information and/or context state information) indicates whether the electronic device is available (e.g., whether the electronic device is currently being used (e.g., whether there are open/active applications, etc.), whether a task is currently being performed, and/or whether audio and/or visual output is currently unavailable (e.g., because the electronic device is facing down, muted, playing media, etc.)). In some examples, the context information included in the aggregated context includes device proximity information indicating a physical proximity of one or more electronic devices participating in the context-sharing group to the first electronic device. In some examples, the device proximity information is based on data (e.g., data included in one or more trigger indications) indicating whether one or more electronic devices participating in the context-sharing group detected (e.g., heard) a digital assistant trigger word or phrase included in the user speech input.

At block 1604, one or more servers (e.g., user intent module 1106 of fig. 11) determine a user intent based on the user speech input. In some examples, determining the user intent includes one or more servers performing speech recognition processing and/or natural language processing of the user speech input. In some examples, the one or more servers also determine the user intent based on context information included in at least a portion of the aggregated context. In some of these examples, the context information includes device state change information associated with the second electronic device participating in the context-sharing group (e.g., context information indicating a time, location, and/or type of device state change of the electronic devices participating in the context-sharing group). In some examples where the device state change information indicates a type of device state change and a time of the device state change of a most recent device state change of the second electronic device, determining the user intent includes disambiguating the user speech input based on the type of device state change and the time of the device state change. For example, if the user speech input is "hey, Siri, stop" and the context information indicates that a timer event is occurring at the device, the one or more servers can determine a user intent to stop the timer based on the timer event indication. In some examples, when two or more events (e.g., timer, alarm, media playback, etc.) occur at two or more separate electronic devices, the one or more servers use the device state change time information to determine user intent based on the most recent device state change (e.g., if the timer event is closer than the media playback event, the one or more servers may "black out, Siri, stop" in response to the user voice input to determine user intent to stop the timer event).

At block 1606, one or more servers (e.g., task determination module 1108 of fig. 11) determine one or more tasks that correspond to the user intent (e.g., one or more tasks to be performed by the electronic device to satisfy the user intent). In some examples, one or more tasks corresponding to the user intent are predetermined based on the determined user intent. In some examples, the one or more tasks include performing a search, retrieving information/data, opening a software application stored on the electronic device, playing media, making a purchase, displaying the retrieved information/data, and so forth.

At block 1608, the one or more servers (e.g., device selection module 1110 of fig. 11) identify (e.g., select) a second electronic device (e.g., a personal electronic device or a public electronic device) of the plurality of electronic devices to perform the one or more tasks based on the one or more tasks and contextual information included in at least a portion of the aggregated context (e.g., contextual information associated with the second electronic device and/or contextual information associated with one or more of the plurality of electronic devices). In some examples, the one or more servers also identify the second electronic device based on the determined user intent. In some examples, the first electronic device is a second electronic device (e.g., when one or more servers identify an electronic device providing user speech input to the one or more servers as the best electronic device to perform one or more tasks). In some examples, the one or more servers identify two or more of the plurality of electronic devices, rather than only one electronic device (e.g., for multimodal task execution).

In some examples, at block 1610, identifying that the second electronic device (at block 1608) includes one or more servers determining, based on device state change information included in the context information (e.g., time of device state change, type of device state change (e.g., timer event, alarm event, media playback, etc.), whether an event (e.g., timer event, alarm event, media playback, etc.) corresponding to a user intent (e.g., user intent to stop timer, stop alarm, stop or update media playback (e.g., pause or change song), etc.) currently occurs at one or more of the plurality of electronic devices.

In some examples, at block 1612, in accordance with a determination that the event corresponding to the user intent is currently occurring only at the second electronic device, the one or more servers identify (e.g., select) the second electronic device.

In some examples, at block 1614, in accordance with a determination that an event corresponding to the user intent is currently occurring at the second electronic device and at least one other electronic device of the plurality of electronic devices, the one or more servers determine which event recently started based on the data indicating the time of the device state change included in the device state change information.

In some examples, at block 1616, in accordance with a determination that the event occurring at the second electronic device recently started, the one or more servers identify (e.g., select) the second electronic device.

In some examples, identifying that the second electronic device (at block 1608) includes the one or more servers determining, based on device state change information (e.g., a time of the device state change, a type of the device state change (e.g., a timer event, an alarm event, media playback, etc.) included in the context information, whether an event (e.g., stopping the timer, pausing the media playback, etc.) corresponding to the user intent (e.g., a user intent to restart the timer, resume the media playback, etc.) previously occurred at one or more of the plurality of electronic devices within a predetermined time period (e.g., within the last 5 minutes, 10 minutes, or 15 minutes), at block 1618.

In some examples, at block 1620, in accordance with a determination that the event corresponding to the user intent previously occurred only at the second electronic device within the predetermined time period, the one or more servers identify (e.g., select) the second electronic device.

In some examples, at block 1622, in accordance with a determination that an event corresponding to the user intent previously occurred at the second electronic device and at least one other electronic device of the plurality of electronic devices within the predetermined time period, the one or more servers determine whether the second electronic device or the at least one other electronic device is physically closer to the first electronic device based on proximity information included in the context information (e.g., proximity information associated with the second electronic device and the at least one other electronic device). In some examples, the one or more servers determine whether the second electronic device or the at least one other electronic device is physically closer to the first electronic device based on context state information (e.g., current locations of the second electronic device and the at least one other electronic device) included in the context information.

In some examples, at block 1624, in accordance with a determination that the second electronic device is physically closer to the first electronic device than the at least one other electronic device, the one or more servers identify (e.g., select) the second electronic device. In some examples, the one or more servers send a command to the first electronic device (e.g., prior to or concurrent with the command to perform the one or more tasks) that causes the first electronic device to request that a user of the first electronic device select an electronic device of the plurality of electronic devices to perform the one or more tasks (e.g., rather than determining which electronic device is closest to the first electronic device, or when the second electronic device and the at least one other electronic device are physically close to the first electronic device as well (or within the same area (e.g., the same room) of the first location).

In some examples, the aforementioned proximity information is based on data indicating whether one or more of the plurality of electronic devices detected a digital assistant trigger included in the user speech input (e.g., data indicating whether the electronic device detected a digital assistant trigger included in context information included in the aggregated context (e.g., included in one or more trigger advertisements included in the aggregated context)). In some examples, the data indicative of whether one or more of the plurality of electronic devices detected a digital assistant trigger included in the user speech input includes data indicative of an energy level (e.g., decibel level) of the digital assistant trigger (e.g., an energy level of a digital assistant trigger word or phrase when received by the electronic device).

In some examples, identifying (at block 1608) the second electronic device includes, at block 1626, the one or more servers determining whether one or more of the plurality of electronic devices are available to perform one or more tasks based on device state change information included in the context information (e.g., a time of the device state change, a type of the device state change (e.g., a timer event, an alarm event, media playback, etc.)). For example, an electronic device may not be available if context information (specifically, device state change information and/or context state information) included in the aggregated context indicates that the electronic device is currently being used (e.g., an open/active application), is currently performing a task, and/or is currently unable to provide audio and/or visual output (e.g., because the electronic device is facing down, muting, playing media, etc.). In some examples, the one or more servers also determine whether the one or more electronic devices are available based on context state information included in the context information (e.g., also based on display visibility of the one or more electronic devices).

In some examples, at block 1628, in accordance with a determination that the second electronic device is available to perform one or more tasks, the one or more servers determine whether the second electronic device is capable of performing the one or more tasks based on device capability information included in the context information, such as device capability information associated with the second electronic device (e.g., device type, processing capability, memory availability, display information, speaker information, etc.). For example, if the one or more tasks include a task that displays information (e.g., results of task execution), the electronic device must have at least a display in order to be able to perform the one or more tasks. In some examples, the one or more servers also determine whether the second electronic device is capable of performing the one or more tasks based on context state information included in the context information (e.g., context state information associated with the second electronic device, such as strength of network connection, battery level, power type (e.g., battery versus wired power), etc.).

In some examples, at block 1630, in accordance with the determination that the second electronic device is capable of performing the one or more tasks, the one or more servers determine whether at least one other electronic device of the plurality of electronic devices is available and capable of performing the one or more tasks.

In some examples, at block 1632, the one or more servers identify (e.g., select) the second electronic device in accordance with a determination that no other electronic devices of the plurality of electronic devices are available and capable of performing the one or more tasks.

In some examples, at block 1634, in accordance with a determination that at least one other electronic device of the plurality of electronic devices is available and capable of performing the one or more tasks, the one or more servers determine whether the second electronic device or the at least one other electronic device is physically closer to the first electronic device based on proximity information included in the context information (e.g., proximity information associated with the second electronic device and the at least one other electronic device). The proximity information is based on data indicative of whether one or more of the plurality of electronic devices detected a digital assistant trigger included in the user voice input (e.g., data included in one or more trigger indications). The data indicative of whether one or more of the plurality of electronic devices detected a digital assistant trigger included in the user speech input includes data indicative of a first energy level according to the digital assistant trigger of the second electronic device and data indicative of a second energy level according to the digital assistant trigger of the at least one other electronic device. In some examples, the one or more servers also determine whether the second electronic device or the at least one other electronic device is physically closer to the first electronic device based on context state information included in the context information (e.g., a current location of the second electronic device and a current location of the at least one other electronic device).

In some examples, at block 1636, determining whether the second electronic device or the at least one other electronic device is physically closer to the first electronic device (at block 1634) includes the one or more servers comparing the first energy level according to the digital assistant trigger of the second electronic device to the second energy level according to the digital assistant trigger of the at least one other electronic device.

In some examples, at block 1638, the one or more servers determine whether a difference between the first energy level and the second energy level is less than a predetermined threshold (e.g., a predetermined decibel level difference (e.g., 2 decibels, 5 decibels, etc.)).

In some examples, at block 1640, in accordance with the determination that the difference is less than the predetermined threshold, the one or more servers determine whether the user of the first electronic device is viewing the display of the second electronic device or the display of the at least one other electronic device based on the user attention information included in the context information.

In some examples, at block 1642, in accordance with a determination that the user is viewing the display of the second electronic device, the one or more servers identify (e.g., select) the second electronic device.

In some examples, at block 1642, in accordance with a determination that the second electronic device is physically closer to the first electronic device than the at least one other electronic device (at block 1634), the one or more servers identify (e.g., select) the second electronic device.

In some examples, at block 1646, the one or more servers identify (e.g., select) a third electronic device of the plurality of electronic devices to perform at least one task of the one or more tasks (e.g., display the retrieved information/data, provide audio output based on the retrieved information/data, etc.) based on the one or more tasks and the contextual information (e.g., perform before, after, or while the second electronic device is performing the remaining tasks).

At block 1648, the one or more servers (e.g., command module 1112) send a command to the first electronic device to perform the one or more tasks and a device identifier corresponding to the second electronic device (e.g., data indicative of the second electronic device) (e.g., as illustrated by arrow 926 of fig. 9). After receiving the command, the first electronic device transmits the command to the second electronic device based on the device identifier. The command then causes the second electronic device to perform one or more tasks. In some examples, the command further causes the second electronic device to provide an audio and/or visual digital assistant response based on the performance of the one or more tasks (e.g., "a song that is currently playing a Taylor Swift" or "resume" the Star wars: empire ").

In some examples, the electronic device is assigned a device identifier when the electronic device joins the context-sharing group. In some examples, at least a portion of the aggregated context includes a device identifier of each electronic device currently participating in the context-sharing group (e.g., associated with context information for each electronic device).

In some examples in which the one or more servers in the above examples identify the third electronic device to perform at least one task of the one or more tasks (at block 1646), at block 1650 the one or more servers send a second command to the first electronic device to perform the at least one task and a device identifier corresponding to the third electronic device. In some examples, the one or more servers send the command and the second command to the first electronic device simultaneously.

17A-17C illustrate flow diagrams representing processes for multimodal task execution in a context sharing group, according to various examples. The process 1700 is performed, for example, using one or more electronic devices implementing a digital assistant. In some examples, one or more blocks of process 1700 are performed by one or more remote devices (e.g., one or more remote servers (e.g., DA server 106), one or more local servers, a cloud computing system, etc.). For example, the blocks of process 1700 are divided between one or more servers (e.g., DA server 106) and client devices in any manner. In other examples, the blocks of process 1700 are divided between one or more servers and a plurality of client devices (e.g., a mobile phone and a smart watch). Thus, while portions of process 1700 are described herein as being performed by a particular device, it should be understood that process 1700 is not so limited. In other examples, process 1700 is performed using only a client device (e.g., user device 104) or only a plurality of client devices. In process 1700, some blocks are optionally combined, the order of some blocks is optionally changed, and some blocks are optionally omitted. In some examples, additional steps may be performed in connection with process 1700.

At block 1702, a first electronic device (e.g., public device 1204) participating in a context-sharing group associated with a first location receives a user voice input (e.g., user voice input 1218). The context sharing group is a collection of a plurality of electronic devices, each electronic device sharing context information with at least one other electronic device included in the collection. The set includes a context collector (e.g., public device 1206).

At block 1704, the first electronic device receives the aggregated context for the context-sharing group from the context collector (e.g., as shown by arrow 1222 of fig. 12A).

At block 1706, after receiving the aggregated context, the first electronic device provides at least a portion of the aggregated context and data corresponding to the user voice input to remote devices that are not participating in the context-sharing group (e.g., as shown by arrow 1224 of fig. 12A). The remote device determines a plurality of tasks (e.g., a plurality of tasks to be performed by one or more electronic devices participating in the context-sharing group to satisfy the user intent corresponding to the user voice input) based on the data corresponding to the user voice input. In some examples, the remote device also determines the plurality of tasks based on context information included in at least a portion of the aggregated context (e.g., also based on device state change information).

At block 1708, the first electronic device receives, from the remote device, a first command to perform a first set of the plurality of tasks and a second command to perform a second set of the plurality of tasks (e.g., as illustrated by arrow 1226 of fig. 12A). In some examples, one or more tasks of the first set of tasks are the same as one or more tasks of the second set of tasks (e.g., performing a search, retrieving information/data based on the search, opening software applications stored on the first electronic device and the second electronic device, etc.).

In some examples, at least a portion of the aggregated context includes context information associated with the second electronic device and context information associated with a third electronic device of the plurality of electronic devices. In some of these examples, the remote device determines the first set of tasks based on device capability information included in context information associated with the second electronic device (e.g., whether the second electronic device has a display and/or dimensions of a display, whether the second electronic device has a speaker and/or loudness of a speaker, device processing power, etc.), and the remote device determines the second set of tasks based on device capability information included in context information associated with the third electronic device (e.g., whether the third electronic device has a display and/or dimensions of a display, whether the third electronic device has a speaker and/or loudness of a speaker, device processing power, etc.). Further, in some of these examples, the remote device determines the first set of tasks and the second set of tasks in response to determining that both the second electronic device and the third electronic device are available (e.g., not currently being used (e.g., an open/active application), not currently performing a task, and/or currently being capable of providing audio and/or visual output (e.g., because the electronic device is facing up)) based on the context information associated with the second electronic device and the context information associated with the third electronic device, being capable of performing at least one of the plurality of tasks, and being proximate to the first electronic device (e.g., located within an area (e.g., the same room) of the same first location as the first electronic device). In some examples, the remote device determines whether the electronic device is located within the same area of the first location as the first electronic device based on proximity information included in the context information (e.g., based on an energy level (e.g., decibel level) of a digital assistant trigger word or phrase according to the second electronic device and the third electronic device, respectively) (e.g., the energy level of the digital assistant trigger word or phrase when received by the second electronic device is compared to the energy level of the digital assistant trigger word or phrase when received by the third electronic device).

At block 1710, the first electronic device receives, from the remote device, a first device identifier (e.g., data indicative of the second electronic device) corresponding to a second electronic device of the plurality of electronic devices and a second device identifier corresponding to a third electronic device of the plurality of electronic devices (e.g., as illustrated by arrow 1226 of fig. 12A). In some examples, the second electronic device or the third electronic device is the first electronic device.

At block 1712, the first electronic device transmits a first command to the second electronic device based on the first device identifier (e.g., as illustrated by arrow 1228 of fig. 12A). The first command causes the second electronic device to perform a first set of tasks. As described above, in some examples, the first electronic device is a second electronic device. In these examples, the first electronic device performs the first set of tasks (rather than sending the first command) in response to receiving the first command from the remote device.

At block 1714, the first electronic device transmits a second command to the third electronic device based on the second device identifier. The second command causes the third electronic device to perform a second set of tasks. As described above, in some examples, the first electronic device is a third electronic device. In these examples, the first electronic device performs the second set of tasks (rather than sending the second command) in response to receiving the second command from the remote device.

In some examples, the second electronic device outputs only audio output based on performance of the first set of tasks (e.g., a digital assistant response saying the titles of all star wars movies), and the third electronic device displays only visual output based on performance of the second set of tasks (e.g., displays the titles of the star wars movies and corresponding movie poster images).

In some examples, in response to performing the first set of tasks, the second electronic device outputs (e.g., on a display of the second electronic device and/or as audio output) a brief summary of the data or information retrieved based on the performance of the first set of tasks (e.g., a brief summary of text, hyperlinks, images, etc., corresponding to the star wars movie titles, calendar history information, actor information, etc.).

In some examples, in response to performing the second set of tasks, the third electronic device outputs (e.g., on a display of the third electronic device and/or as an audio output) a detailed summary of the data or information retrieved based on the performance of the second set of tasks (e.g., a detailed summary of text, hyperlinks, images, etc. corresponding to the star wars movie titles, calendar history information, actor information, etc.). In some examples, the detailed summary includes at least one of hyperlinks, images, audio data, or text data not included in the short summary.

In some examples, at block 1716, the first electronic device receives a second user voice input (e.g., user voice input 1234) representing a user request to make a purchase (e.g., "hey, Siri, purchase of" star wars: empire ").

In some examples, at block 1718, the first electronic device receives the updated aggregated context from the context collector (e.g., as shown by arrow 1238 of fig. 12B). The updated aggregated context includes updated context information associated with the second electronic device and updated context information associated with the third electronic device (e.g., the updated context information of the two devices includes data (e.g., any audio output provided, content currently displayed, etc.) indicating results of execution of the first set of tasks and results of execution of the second set of tasks, respectively). In some examples, the second electronic device sends updated context information associated with the second electronic device to the context collector after performing the first set of tasks, and the third electronic device sends updated context information associated with the third electronic device to the context collector after performing the second set of tasks.

In some examples, at block 1720, the first electronic device transmits at least a portion of the data and updated aggregated context corresponding to the second user voice input to the remote device (e.g., as illustrated by arrow 1240 of fig. 12B). The remote device then determines a second plurality of tasks based on the data corresponding to the second user voice input. In some examples, the remote device also determines the plurality of tasks based on context information included in at least a portion of the updated aggregated context (e.g., also based on device state change information).

In some examples, at block 1722, the first electronic device receives, from the remote device, a third command to perform a third set of tasks of the second plurality of tasks and a third device identifier corresponding to a fourth electronic device of the plurality of electronic devices (e.g., as illustrated by arrow 1242 of fig. 12B). The third set of tasks includes user authentication tasks. In some examples, the fourth electronic device is the second electronic device.

In some examples, at block 1724, the first electronic device sends a third command to the fourth electronic device based on the third device identifier (e.g., as illustrated by arrow 1244 of fig. 12B). The third command causes the fourth electronic device to perform a third set of tasks.

In some examples, after sending the third command to the fourth electronic device (at block 1724), at block 1726, the first electronic device receives user authentication data (e.g., voice authentication data, password authentication data, and/or biometric authentication data (e.g., data corresponding to facial and/or fingerprint authentication)) corresponding to the user of the first electronic device from the fourth electronic device (e.g., as shown by arrow 1246 of fig. 12B).

In some examples, at block 1728, the first electronic device transmits the user authentication data to the remote device (e.g., as illustrated by arrow 1248 of fig. 12B).

In some examples, at block 1730, the first electronic device receives, from the remote device, a fourth command to perform a fourth set of tasks of the second plurality of tasks and a second device identifier corresponding to a third electronic device (e.g., as illustrated by arrow 1250 of fig. 12B). The remote device transmits a fourth command to the first electronic device in response to determining, based on the user authentication data, that the user of the first electronic device is authorized to make the requested purchase. The fourth set of tasks includes tasks to perform the requested purchase. In some examples, the remote device sends the fourth command before, at the same time as, or shortly after the third command. In these examples, the first electronic device will not send the fourth command to the third electronic device until the remote device notifies the first electronic device that the user of the first electronic device is authorized to make the requested purchase.

In some examples, at block 1732, the first electronic device sends a fourth command to the third electronic device based on the second device identifier (e.g., as illustrated by arrow 1252 of fig. 12B). The fourth command causes the third electronic device to perform a fourth set of tasks.

In some examples, after sending the third command to the fourth electronic device (at block 1724), at block 1734, the first electronic device receives an indication from the fourth electronic device that the user of the first electronic device is authorized to make the requested purchase (e.g., the fourth electronic device locally authenticates the user (e.g., based on user authentication data stored on the fourth electronic device) and sends the indication in response to the authentication).

In some examples, at block 1736, the first electronic device sends the indication to the remote device.

In some examples, at block 1738, the first electronic device receives, from the remote device, a fifth command to perform a fifth set of tasks of the second plurality of tasks and a second device identifier corresponding to a third electronic device. In response to receiving an indication that the user of the first electronic device is authorized to make the requested purchase, the remote device transmits a fifth command to the first electronic device. The fifth set of tasks includes tasks to perform the requested purchase.

In some examples, the remote device sends the fifth command before, at the same time as, or shortly after the third command. In these examples, the first electronic device will not send the fifth command to the third electronic device until the first electronic device receives an indication that the user of the first electronic device is authorized to make the requested purchase (so that the server does not participate in the user authentication decision). If the user is not authorized to make the requested purchase, the first electronic device does not send the fifth command to the third electronic device.

In some examples, at block 1740, the first electronic device sends a fifth command to the third electronic device based on the second device identifier. The fifth command causes the third electronic device to perform a fifth set of tasks.

18A-18B illustrate flow diagrams of processes representing a continuous digital assistant session across a plurality of electronic devices participating in a context-sharing group, according to various examples. For example, process 1800 is performed using one or more electronic devices that implement digital assistants. In some examples, one or more blocks of process 1800 are performed by one or more remote devices (e.g., one or more remote servers (e.g., DA server 106), one or more local servers, a cloud computing system, etc.). For example, the blocks of process 1800 are divided in any manner between one or more servers (e.g., DA server 106) and client devices. In other examples, the blocks of process 1800 are divided between one or more servers and multiple client devices (e.g., a mobile phone and a smart watch). Thus, while portions of process 1800 are described herein as being performed by a particular device, it should be understood that process 1800 is not so limited. In other examples, process 1800 is performed using only a client device (e.g., user device 104) or only a plurality of client devices. In process 1800, some blocks are optionally combined, the order of some blocks is optionally changed, and some blocks are optionally omitted. In some examples, additional steps may be performed in connection with process 1800.

At block 1802, a first electronic device (e.g., user device 1304) participating in a context-sharing group associated with a first location receives a first user voice input (e.g., user voice input 1316 of fig. 13 (e.g., "how are temperatures of Siri, pajo?). The context sharing group is a set of at least two electronic devices, each electronic device sharing context information with at least one other electronic device included in the set. The set includes a second electronic device (e.g., user device 1306) and a context collector (e.g., public device 1308). In some examples, the context collector is a third electronic device participating in the context sharing group. In some examples, the context collector is the first electronic device or the second electronic device. In some examples, the first electronic device and the second electronic device are located within two separate areas (e.g., two separate rooms) of the first location.

In some examples, at block 1804, the first electronic device receives the aggregated context for the context-sharing group from the context collector (e.g., as illustrated by arrow 1320 of fig. 13) prior to outputting the first digital assistant response. In these examples, the aggregated context includes context information associated with the first electronic device and context information associated with the second electronic device.

In some examples, at block 1806, the first electronic device transmits at least a portion of the data and aggregated context corresponding to the first user voice input to a remote device (e.g., one or more remote servers, one or more local servers, a cloud computing system, etc.) that does not participate in the context sharing group (e.g., as illustrated by arrow 1322 of fig. 13).

In some examples, at block 1808, the first electronic device receives, from the remote device, a first command to perform one or more tasks and a first device identifier corresponding to the first electronic device (e.g., as illustrated by arrow 1324 of fig. 13). In these examples, the remote device determines the one or more tasks and the device identifier corresponding to the first electronic device based at least on the data corresponding to the first user voice input and contextual information included in the aggregated context (e.g., contextual information associated with the first electronic device and/or contextual information associated with one or more other electronic devices participating in the context-sharing group). The first command causes the first electronic device to perform the one or more tasks and determine a first digital assistant response based on results of the performance of the one or more tasks.

At block 1810, the first electronic device outputs a first digital assistant response (e.g., digital assistant response 1326 (e.g., "panoo current 68 degrees")) based on the first user voice input.

After outputting the first digital assistant response (e.g., immediately after the outputting or a few seconds after the outputting (e.g., after the current conversation session ends (e.g., 1 second or 2 seconds after the first electronic device provides the first digital assistant response without receiving additional user speech input at the first electronic device))), at block 1812 the first electronic device sends context information including the digital assistant conversation session history for the first electronic device to a context collector (e.g., as illustrated by arrow 1327 of fig. 13). In some examples, the digital assistant dialog session history includes data corresponding to the most recent digital assistant dialog session (e.g., ASR results, NLP results, and/or data retrieved and/or provided during the most recent digital assistant dialog session (e.g., data corresponding to recent user speech inputs and digital assistant responses)). For example, the digital assistant dialog session history includes data corresponding to the first user voice input and the first digital assistant response. In some examples, the digital assistant dialog session history includes data corresponding to digital assistant dialog sessions that occurred within a predetermined period of time (e.g., within a past hour, within a past day, etc.).

At block 1814, the second electronic device receives a second user voice input (e.g., user voice input 1328 (e.g., "how long is he, Siri, do i drive there")). In some examples, the first electronic device and the second electronic device receive a first user voice input and a second user voice input from a single user. In other examples, the first electronic device and the second electronic device receive the first user voice input and the second user voice input from different users.

In some examples, at block 1816, the second electronic device sends a request for an updated aggregated context for the context-sharing group to the context collector (e.g., as illustrated by arrow 1330 of fig. 13). In some examples, the second electronic device sends a request for an updated aggregated context in response to receiving the second user voice input.

At block 1818, the second electronic device receives the updated aggregated context for the context-sharing group from the context collector (e.g., as shown by arrow 1332 of fig. 13). The updated aggregated context includes a digital assistant dialog session history for the first electronic device. In some examples, the context collector generates an updated aggregated context (e.g., in response to receiving context information from the first electronic device). In these examples, generating the updated aggregated context includes the context collector updating context information associated with the first electronic device included in the aggregated context of the context-sharing group based at least on the digital assistant conversation session history of the first electronic device.

In some examples, at block 1820, prior to the second electronic device outputting the second digital assistant response, the second electronic device transmits at least a portion of the updated aggregated context and data corresponding to the second user voice input to a remote device (e.g., one or more remote servers, one or more local servers, a cloud computing system, etc.) that is not participating in the context-sharing group (e.g., as shown by arrow 1334 of fig. 13). In these examples, at least a portion of the updated aggregated context includes a digital assistant dialog session history for the first electronic device.

In some examples, at block 1822, the second electronic device receives, from the remote device, a second command to perform the one or more tasks and a second device identifier corresponding to the second electronic device (e.g., the device identifier causes the second electronic device to perform the one or more tasks) (e.g., as shown by arrow 1336 of fig. 13). The remote device (e.g., user intent module 1106 and/or task determination module 1108 of fig. 11) determines the one or more tasks and the device identifier corresponding to the second electronic device based at least on the data corresponding to the second user voice input and the digital assistant dialog session history of the first electronic device. The second command causes the second electronic device to perform the one or more tasks and determine a second digital assistant response based on results of the performance of the one or more tasks.

In some examples, the digital assistant dialog session history of the first electronic device includes data corresponding to the first user voice input. In these examples, determining the one or more tasks based at least on the data corresponding to the second user voice input and the digital assistant dialog session history of the first electronic device includes the remote device disambiguating the second user voice input based on the first user voice input. In some examples, disambiguating the second user voice input based on the first user voice input includes the remote device (e.g., task determination module 1108) determining one or more parameters for the second user voice input based on one or more parameters for the first user voice input (e.g., a location included in the first user voice input, a contact name, a website, an email address, etc.). In some examples, disambiguating the second user voice input (e.g., "hey, Siri, new york.

At block 1824, the second electronic device outputs a second digital assistant response (e.g., digital assistant response 1338 of fig. 13 (e.g., "traffic to pajo is clear, so it takes 15 minutes to estimate route to king avenue to pass.") based on the second user voice input and the digital assistant dialog session history of the first electronic device.

19A-19B illustrate flow diagrams representing processes for suppressing delayed digital assistant trigger detections using a context collector of a context-sharing group, according to various examples. Process 1900 is performed, for example, using one or more electronic devices implementing a digital assistant. In some examples, one or more blocks of process 1900 are performed by one or more remote devices (e.g., one or more remote servers (e.g., DA server 106), one or more local servers, a cloud computing system, etc.). For example, the blocks of process 1900 are divided in any way between one or more servers (e.g., DA server 106) and client devices. In other examples, the blocks of process 1900 are divided between one or more servers and a plurality of client devices (e.g., a mobile phone and a smart watch). Thus, while portions of process 1900 are described herein as being performed by a particular device, it should be understood that process 1900 is not so limited. In other examples, process 1900 is performed using only a client device (e.g., user device 104) or only a plurality of client devices. In process 1900, some blocks are optionally combined, the order of some blocks is optionally changed, and some blocks are optionally omitted. In some examples, additional steps may be performed in connection with process 1900.

At block 1902, a first electronic device (e.g., user device 1006 of fig. 10) participating in a context-sharing group associated with a first location receives a user voice input (e.g., user voice input 1014 of fig. 10). The user speech input includes a digital assistant trigger (e.g., a word or phrase (e.g., "hey, Siri," "Siri," etc.) that initiates a dialog session with a digital assistant of the electronic device). The context sharing group is a collection of at least two electronic devices, each electronic device sharing context information with at least one other electronic device participating in the collection. The set includes at least a second electronic device (e.g., public device 1004) and a context collector (e.g., public device 1008). In some examples, the second electronic device is a context collector. In some examples, the context collector is a third electronic device participating in the context sharing group. In some examples, each electronic device participating in the context-sharing group is connected to a single wireless network at the first location.

At block 1904, in response to detecting the digital assistant trigger (e.g., determining that the user speech input comprises the digital assistant trigger), the first electronic device sends a first trigger announcement (e.g., as illustrated by arrow 1022 of fig. 10) to the context collector (e.g., via a wireless network of the first location). The first trigger advertisement indicates that the digital assistant trigger is based on a first time at the end of the first electronic device. In some examples, the first trigger advertisement includes data indicative of an energy level (e.g., decibel level) of the digital assistant trigger word or phrase (e.g., the energy level of the digital assistant trigger word or phrase when received by the first electronic device). In some examples, the first trigger advertisement includes a confidence score corresponding to a confidence of the first electronic device that the user speech input includes a digital assistant trigger word or phrase.

In some examples, the first electronic device and the second electronic device share a short-range communication connection (e.g., a bluetooth or bluetooth low energy (BTLE) connection). In some of these examples, at block 1906, in response to detecting the digital assistant trigger, the first electronic device transmits a first trigger advertisement to the second electronic device via the short-range communication connection (e.g., the first electronic device transmits the first trigger advertisement via bluetooth or BTLE before, concurrently with, or shortly after transmitting the first trigger advertisement to the context collector).

At block 1908, the first electronic device receives a second trigger advertisement from the context collector (e.g., as illustrated by arrow 1024 of fig. 10). The second trigger advertisement indicates a second time at which the digital assistant trigger ended according to the second electronic device. In some examples, in response to detecting the digital assistant trigger included in the user voice input, the second electronic device sends a second trigger advertisement to the context collector (before the context collector sends the second trigger advertisement to the first electronic device). In some examples, the second electronic device includes a second trigger advertisement (e.g., data corresponding to the second trigger advertisement) in the context information sent by the second electronic device to the context collector after detecting the digital assistant trigger included in the user speech input (e.g., as illustrated by arrow 1016 of fig. 10).

In some of the examples in which the first electronic device and the second electronic device share a short-range communication connection (e.g., as described above with reference to block 1906), at block 1910, the first electronic device receives a third trigger advertisement from the second electronic device via the short-range communication connection. The third trigger advertisement indicates a third time at which the digital assistant trigger ended according to the second electronic device. In some examples, the third time is the same as the second time indicated by the second trigger advertisement. In some examples, in response to receiving the first trigger advertisement from the first electronic device via the short-range communication connection, the second electronic device transmits a third trigger advertisement via the short-range communication connection.

At block 1912, the first electronic device determines whether the second time is within a predetermined time range (e.g., 750 milliseconds, 500 milliseconds, 100 milliseconds, etc.) before the first time (e.g., determines whether the second trigger advertisement is "reasonable").

In some examples in which the first electronic device and the second electronic device share a short-range communication connection (e.g., as described above with reference to blocks 1906 and 1910), at block 1914, after determining whether the second time is within a predetermined time range before the first time, the first electronic device determines whether the third time is within a predetermined time range before the first time (e.g., 750 milliseconds, 500 milliseconds, 100 milliseconds, etc.) (e.g., determines whether the third trigger advertisement is "reasonable").

In accordance with a determination that the second time is within a predetermined time range before the first time (e.g., if the predetermined time range is 500 milliseconds, the second time is within 500 milliseconds before the first time), the first electronic device foregoes further processing of the user voice input at block 1916. In some examples, forgoing further processing the user voice input includes the first electronic device forgoing sending a request to the context collector for an aggregated context of the context-sharing group.

In some of the examples in which the first electronic device and the second electronic device share a short-range communication connection (e.g., as described above with reference to

blocks

1906, 1910, and 1914), at block 1918, in accordance with a determination that the third time is within a predetermined range prior to the first time, the first electronic device foregoes further processing of the user voice input even if the second time is not within the predetermined range prior to the first time.

In some examples, at block 1920, in accordance with a determination that the second time is not within the predetermined time range (e.g., if the predetermined time range is 500 milliseconds, the second time is equal to or more than 500 milliseconds before the first time), the first electronic device continues to process the user voice input. In some examples, continuing to process the user speech input includes the first electronic device sending a request to the context collector for an aggregated context of the context-sharing group.

The operations described above with reference to fig. 14A-14C, 15A-15B, 16A-16E, 17A-17C, 18A-18B, and 19A-19B are optionally implemented by components depicted in fig. 1-4, 6A-6B, and 7A-7C. For example, the operations of process 1400, process 1500, process 1600, process 1700, process 1800, and/or process 1900 may be implemented by system 100. Those of ordinary skill in the art will clearly know how to implement other processes based on the components depicted in fig. 1-4, 6A-6B, and 7A-7C.

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

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

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

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

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

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

As described above, one aspect of the disclosed technology is to collect and use data (e.g., user data, user-specific context information, etc.) available from various sources to assist/improve the determination of digital assistant responses during a video communication session. The present disclosure contemplates that, in some instances, such collected data may include personal information data that uniquely identifies or may be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, twitter IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personal information data in the disclosed technology may be useful to benefit a user. For example, the personal information data may be used to determine one or more parameters of a task to be performed by the digital assistant of the user device and/or the public device in response to a user request. Thus, the use of such personal information data enables the digital assistant of the user device to provide a digital assistant response (based on the performance of the above-described tasks) that is more meaningful and/or useful to the user. In addition, the present disclosure also contemplates other uses for which personal information data is beneficial to the user. For example, health and fitness data may be used to provide insight into the overall health status of a user, or may be used as positive feedback for individuals using technology to pursue health goals.

The present disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and/or privacy practices. In particular, such entities should enforce and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data is collected and/or used. Personal information from the user should be collected for legitimate and legitimate uses by the entity and not shared or sold outside of these legitimate uses. Furthermore, such acquisition/sharing should be performed after receiving user informed consent. Furthermore, such entities should consider taking any necessary steps to defend and secure access to such personal information data, and to ensure that others who have access to the personal information data comply with their privacy policies and procedures. In addition, such entities may subject themselves to third party evaluations to prove compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to the particular type of personal information data collected and/or accessed, and to applicable laws and standards including specific considerations of jurisdiction. For example, in the united states, the collection or acquisition of certain health data may be governed by federal and/or state laws, such as the health insurance association and accountability act (HIPAA); while other countries may have health data subject to other regulations and policies and should be treated accordingly. Therefore, different privacy practices should be maintained for different personal data types in each country.

Regardless of the foregoing, the present disclosure also contemplates embodiments in which a user selectively prevents use or access to personal information data. That is, the present disclosure contemplates that hardware elements and/or software elements may be provided to prevent or block access to such personal information data. For example, to the extent that user data is collected and used to assist/improve the determination of digital assistant responses, the disclosed techniques may be configured to allow a user to opt-in or opt-out of participating in the collection of personal information data during registration service or at any time thereafter. As another example, the user may choose not to provide user data (e.g., the user's media, contacts, voice profiles, preferences, etc.) to assist/improve the determination of the digital assistant's response. As another example, the user may choose to prevent certain types/forms of personal information data (e.g., email address, home address, payment information, etc.) from being collected and used for determining the digital assistant response. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to accessing or using personal information. For example, the user may be notified that their personal information data is to be accessed when the application is downloaded, and then be reminded again just before the personal information data is accessed by the application.

Further, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting data collection and deleting data. In addition, and when applicable, including in certain health-related applications, data de-identification may be used to protect the privacy of the user. Where appropriate, de-identification may be facilitated by removing certain identifiers (e.g., date of birth, etc.), controlling the amount or characteristics of data stored (e.g., collecting location data at the city level rather than the address level), controlling the manner in which data is stored (e.g., aggregating data between users), and/or other methods.

Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may be implemented without access to such personal information data. That is, various embodiments of the disclosed technology do not fail to function properly due to the lack of all or a portion of such personal information data. For example, a digital assistant response may be determined based on non-personal information data/user data or an absolute minimum amount of personal information and/or user data (such as content requested by a device associated with the user, other non-personal information available to the digital assistant, or publicly available information).

Some exemplary aspects of the disclosure are described below.

Aspect 1: a method, comprising:

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 that each share 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, choosing one electronic device of the set of the at least two electronic devices as a context collector of the context-sharing group, wherein choosing the context collector comprises:

determining a first context collector score corresponding to the first electronic device based at least on a strength of connectivity between the first electronic device and a wireless network of the first location;

receiving, from at least the second electronic device, one or more context collector scores corresponding to at least the second electronic device; and

determining which of the electronic devices included in the context-sharing group to choose as the context collector of 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

In accordance with a determination to choose 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.

Aspect 2: the method of aspect 1, wherein the at least two electronic devices of the context-sharing group each automatically share context information with at least one other electronic device participating in the context-sharing group in response to experiencing a device state change.

Aspect 3: the method of any of aspects 1-2, further comprising:

the wireless network connected to the first location, wherein the first electronic device joins the context sharing group in response to the wireless network connected to the first location.

Aspect 4: the method of aspect 3, wherein each electronic device participating in the context-sharing group is connected to the wireless network.

Aspect 5: the method of any of aspects 1-4, further comprising:

determining whether the first electronic device is registered in the context-sharing group associated with the first location, wherein the first electronic device joins the context-sharing group in accordance with the determination that the first electronic device is registered in the context-sharing group.

Aspect 6: the method of any of aspects 1-5, wherein the first electronic device joins the context-sharing group by establishing a communication connection with at least one other electronic device participating in the context-sharing group.

Aspect 7: the method of any of aspects 1-6, wherein the first context collector score is further based on a power state of the first device.

Aspect 8: the method of any of aspects 1-7, wherein the first context collector score is further based on a frequency with which the first electronic device moves into and out of the context-sharing group.

Aspect 9: the method of any of aspects 1-8, further comprising:

sending the first context collector score to at least the second electronic device prior to determining which of the electronic devices included in the context-sharing group to choose as the context collector of the context-sharing group.

Aspect 10: the method of any of aspects 1-9, further comprising:

in accordance with a determination to choose the second electronic device as the context collector, sending context information associated with the first electronic device to the second electronic device in response to the first electronic device experiencing a device state change.

Aspect 11: the method of any of aspects 1-10, wherein choosing the context collector further comprises:

receiving one or more context collector indications from at least the second electronic device, wherein a context collector indication indicates whether an electronic device is currently the context collector; and

determining whether the context-sharing group currently includes a context collector based on a context collector indication corresponding to the first electronic device and the one or more context collector indications received from at least the second electronic device, wherein the first electronic device further determines which of the electronic devices included in the context-sharing group to choose as the context collector of the context-sharing group based on whether the context-sharing group currently includes a context collector.

Aspect 12: the method of aspect 11, further comprising:

in accordance with a determination that the context-sharing group currently includes a context collector, choosing the current context collector as the context collector of the context-sharing group.

Aspect 13: the method of aspect 11, further comprising:

In accordance with a determination that the context-sharing group includes more than one context collector, determining which of the electronic devices included in the context-sharing group to choose as the context collector of 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.

Aspect 14: the method of any of aspects 1-13, wherein the contextual information received from at least the second electronic device comprises at least one of: device state change information associated with at least the second electronic device, device capability information associated with at least the second electronic device, and context state information associated with at least the second electronic device.

Aspect 15: the method of any of aspects 1-14, further comprising:

receiving a request for an aggregated context of the context-sharing group from the second electronic device, wherein the second electronic device sends the request to the first electronic device in response to receiving user voice input from a user of the second electronic device; and

Sending the aggregated context to the second electronic device, wherein sending the aggregated context to the second electronic device causes the second electronic device to obtain a digital assistant response to the user speech input based on context information included in the aggregated context.

Aspect 16: a method, comprising:

at a first electronic device participating in a context-sharing group, the context-sharing group associated with a first location, wherein the context-sharing group is a set of at least two electronic devices that each share 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 a user voice input;

receiving an aggregated context for 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 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 contextual 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.

Aspect 17: the method of aspect 16, wherein each electronic device participating in the context-sharing group is connected to a single wireless network at the first location.

Aspect 18: the method of any of aspects 16-17, wherein the second electronic device is the context collector.

Aspect 19: the method of any of aspects 16-17, wherein the context collector is a third electronic device participating in the context-sharing group.

Aspect 20: the method of any of aspects 16 to 19, further comprising:

in response to receiving the user speech input, sending a request to the context collector to send the aggregated context of the context-sharing group to the first electronic device, wherein the request causes the context collector to send the aggregated context to the first electronic device.

Aspect 21: the method of any of aspects 16-20, wherein prior to receiving the aggregated context, at least the first electronic device and the second electronic device provide the context information included in the 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 undergoing a device state change.

Aspect 22: the method of aspect 21, wherein the context information comprises device state change information corresponding to at least the first electronic device and the second electronic device.

Aspect 23: the method of any of aspects 21-22, wherein the context information comprises context state information corresponding to at least the first electronic device and the second electronic device.

Aspect 24: the method of any of aspects 21-23, wherein the context information comprises device capability information corresponding to at least the first electronic device and the second electronic device.

Aspect 25: the method of any of aspects 16-24, wherein the command further causes the second electronic device to output a user query after performing the one or more tasks, and wherein the user query asks whether to send a second command to perform the one or more tasks to a fourth electronic device participating in the context sharing group.

Aspect 26: the method of any of aspects 16-25, wherein the user speech input is ambiguous with respect to the electronic device defining that the user speech input is to be responded to, and wherein the remote device disambiguates the user speech input based on the context information included in the at least a portion of the aggregated context.

Aspect 27: the method of any of aspects 16-26, wherein the first electronic device and the second electronic device are both personal electronic devices that are each registered to a single user, and wherein the remote device disambiguates one or more words included in the user voice input based on user data associated with the second electronic device.

Aspect 28: the method of any of aspects 16-26, wherein both the first electronic device and the second electronic device are personal electronic devices that are each registered to a different user, the method further comprising:

prior to sending the command to the second electronic device:

outputting a request for user authentication; and

receiving authentication data 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.

Aspect 29: the method of any of aspects 16-26, wherein the context-sharing group further comprises a fourth electronic device, and wherein the first electronic device, the second electronic device, and the fourth electronic device are all personal electronic devices that are each registered to a single user, the method further comprising:

Receiving user data associated with the fourth electronic device from the remote device prior to sending the command to the second electronic device; and

sending the user data 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.

Aspect 30: the method of any of aspects 16-29, wherein the user speech 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 to provide an indication to the first electronic device by the second electronic device, the indication being whether the digital assistant trigger included in the user voice input was detected by the second electronic device; 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 a physical proximity of the second electronic device to the first electronic device based on the indication.

Aspect 31: a method, comprising:

at one or more servers:

receiving, from a first electronic device participating in a context-sharing group associated with a first location, a user speech input and at least a portion of an aggregated context of the context-sharing group, wherein the context-sharing group is a collection of a plurality of electronic devices that each share context information with at least one other electronic device included in the collection;

determining a user intent based on the user speech input;

determining one or more tasks corresponding to the user intent;

identifying a second electronic device of the plurality of 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 aggregated context; and

transmitting a command to the first electronic device to perform the one or more tasks and a device identifier corresponding to the second 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.

Aspect 32: the method of aspect 31, wherein each of the plurality of electronic devices is connected to a single wireless network at the first location.

Aspect 33: the method of any of aspects 31-32, wherein the aggregated context is a set of context information associated with one or more of the plurality of electronic devices participating in the context-sharing group, and wherein the first electronic device receives the aggregated context from a context collector of the context-sharing group after the first electronic device receives a voice input from a user to the user.

Aspect 34: the method of any of aspects 31-33, wherein the aggregating the context information included in the context comprises at least one of: device state change information, context state information, device capability information, and device proximity information associated with the second electronic device.

Aspect 35: the method of any of aspects 31-34, wherein the user intent is determined further based on context information included in the aggregated context.

Aspect 36: the method of aspect 35, wherein the context information includes device state change information associated with the second electronic device, wherein the device state change information indicates a type of device state change and a time of device state change with respect to a most recent device state change of the second electronic device, and wherein determining the user intent includes disambiguating the user speech input based on the type of device state change and the time of the device state change.

Aspect 37: the method of any of aspects 31-36, wherein identifying the second electronic device comprises:

determining whether an event corresponding to the user intent currently occurs at one or more of the plurality of electronic devices based on device state change information included in the context information; and

in accordance with a determination that an event corresponding to the user intent is currently occurring only at the second electronic device, identifying the second electronic device.

Aspect 38: the method of aspect 37, further comprising:

in accordance with a determination that an event corresponding to the user intent is currently occurring at the second electronic device and at least one other electronic device of the plurality of electronic devices:

Determining which event has recently started based on data indicating a time of a device state change included in the device state change information; and

in accordance with a determination that the event occurring at the second electronic device recently started, identifying the second electronic device.

Aspect 39: the method of any of aspects 31-36, wherein identifying the second electronic device comprises:

determining whether an event corresponding to the user intention has previously occurred at one or more of the plurality of electronic devices within a predetermined time period based on device state change information included in the context information; and

in accordance with a determination that an event corresponding to the user intent has previously occurred only at the second electronic device within the predetermined period of time, identifying the second electronic device.

Aspect 40: the method of aspect 39, further comprising:

in accordance with a determination that an event corresponding to the user intent has previously occurred at the second electronic device and at least one other electronic device of the plurality of electronic devices within the predetermined time period:

determining whether the second electronic device or the at least one other electronic device is physically closer to the first electronic device based on proximity information included in the context information; and

In accordance with a determination that the second electronic device is physically closer to the first electronic device than the at least one other electronic device, identifying the second electronic device.

Aspect 41: the method of aspect 40, wherein the proximity information is based on data indicating whether one or more of the plurality of electronic devices detected a digital assistant trigger included in the user voice.

Aspect 42: the method of any of aspects 31-36, wherein identifying the second electronic device includes determining whether one or more of the plurality of electronic devices are available to perform the one or more tasks based on device state change information included in the context information.

Aspect 43: the method of aspect 42, further comprising:

in accordance with a determination that the second electronic device is available to perform the one or more tasks, determining whether the second electronic device is capable of performing the one or more tasks based on device capability information included in the context information.

Aspect 44: the method of aspect 43, further comprising:

in accordance with a determination that the second electronic device is capable of performing the one or more tasks:

Determining whether at least one other electronic device of the plurality of electronic devices is available and capable of performing the one or more tasks; and

identifying the second electronic device based on a determination that no other electronic devices of the plurality of electronic devices are available and capable of performing the one or more tasks.

Aspect 45: the method of aspect 44, further comprising:

in accordance with a determination that at least one other electronic device of the plurality of electronic devices is available and capable of performing the one or more tasks:

in accordance with a determination that the second electronic device is physically closer to the first electronic device than the at least one electronic device, identifying the second electronic device.

Aspect 46: the method of aspect 45, wherein the proximity information is based on data indicative of whether one or more of the plurality of electronic devices detected a digital assistant trigger included in the user voice input, and wherein the data indicative of whether one or more of the plurality of electronic devices detected a digital assistant trigger included in the user voice input comprises:

Data indicative of a first energy level of the digital assistant trigger according to the second electronic device, an

Data indicating a second energy level of the digital assistant trigger according to the at least one other electronic device, wherein determining whether the second electronic device or the at least one other electronic device is physically closer to the first electronic device comprises comparing the first energy level to the second energy level.

Aspect 47: the method of aspect 46, further comprising:

determining whether a difference between the first energy level and the second energy level is less than a predetermined threshold;

in accordance with a determination that the difference is less than the predetermined threshold, determining whether a user of the first electronic device is viewing a display of the second electronic device or viewing a display of the at least one other electronic device based on user attention information included in the context information; and

in accordance with a determination that the user is viewing the display of the second electronic device, identifying the second electronic device.

Aspect 48: the method of any of aspects 31-36, further comprising:

Identifying a third electronic device of the plurality of electronic devices to perform at least one task of the one or more tasks based on the one or more tasks and the contextual information; and

sending a second command to the first electronic device to perform the at least one task and a device identifier corresponding to the third electronic device.

Aspect 49: a method, comprising:

at a first electronic device participating in a context-sharing group, the context-sharing group associated with a first location, wherein the context-sharing group is a set of a plurality of electronic devices that each share context information with at least one other electronic device included in the set, and wherein the set includes a context collector:

receiving a user voice input;

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 not participating in the context-sharing group, wherein the remote device determines a plurality of tasks based on the data corresponding to the user voice input;

Receiving, from the remote device:

a first command to perform a first set of tasks of the plurality of tasks and a second command to perform a second set of tasks of the plurality of tasks; and

a first device identifier corresponding to a second electronic device of the plurality of electronic devices and a second device identifier corresponding to a third electronic device of the plurality of 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 set 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 set of tasks.

Aspect 50: the method of aspect 49, wherein one or more tasks of the first set of tasks are the same as one or more tasks of the second set of tasks.

Aspect 51: the method of any of aspects 49-50, wherein:

the at least a portion of the aggregated context comprises context information associated with the second electronic device and context information associated with the third electronic device,

The remote device determines the first set of tasks based on device capability information included in the context information associated with the second electronic device, and

the remote device determines the second set of tasks based on device capability information included in the context information associated with the third electronic device.

Aspect 52: the method of aspect 51, wherein the remote device determines the first set of tasks and the second set of tasks in response to determining that both the second electronic device and the third electronic device are available, capable of performing at least one task of the plurality of tasks, and proximate to the first electronic device based on the context information associated with the second electronic device and the context information associated with the third electronic device.

Aspect 53: the method of any of aspects 49-52, wherein the second electronic device outputs only audio output based on performance of the first set of tasks, and wherein the third electronic device displays only visual output based on performance of the second set of tasks.

Aspect 54: the method of any of aspects 49-53, wherein in response to executing the first set of tasks, the second electronic device outputs a brief summary of data or information retrieved based on the execution of the first set of tasks.

Aspect 55: the method of aspect 54, wherein in response to performing the second set of tasks, the third electronic device outputs a detailed summary of data or information retrieved based on the performance of the second set of tasks, wherein the detailed summary includes at least one of hyperlinks, images, media items, or text data not included in the brief summary.

Aspect 56: the method of any of aspects 49-55, further comprising:

receiving a second user voice input representing a user request to make a purchase;

receiving an updated aggregated context from the context collector, wherein the updated aggregated context comprises updated context information associated with the second electronic device and updated context information associated with the third electronic device; and

sending, to the remote device, data corresponding to the second user voice input and at least a portion of the updated aggregated context, wherein the remote device determines a second plurality of tasks based on the data corresponding to the second user voice input.

Aspect 57: the method of aspect 56, wherein the second electronic device sends the updated context information associated with the second electronic device after performing the first set of tasks, and wherein the third electronic device sends the updated context information associated with the third electronic device after performing the second set of tasks.

Aspect 58: the method of any of aspects 49-57, further comprising:

receiving, from the remote device, a third command to perform a third set of tasks of the second plurality of tasks and a third device identifier corresponding to a fourth electronic device of the plurality of electronic devices, wherein the third set of tasks includes a user authentication task; and

sending the third command to the fourth electronic device based on the third device identifier, wherein the third command causes the fourth electronic device to perform the third set of tasks.

Aspect 59: the method of aspect 58, further comprising:

receiving, from the fourth electronic device, user authentication data corresponding to a user of the first electronic device;

transmitting the user authentication data to the remote device;

receiving, from the remote device, a fourth command to perform a fourth set of tasks of the second plurality of tasks and the second device identifier corresponding to the third electronic device,

wherein the remote device sends the fourth command to the first electronic device in response to determining, based on the user authentication data, that the user of the first electronic device is authorized to make the requested purchase, and

Wherein the fourth set of tasks includes tasks to perform the requested purchase; and

sending the fourth command to the third electronic device based on the second device identifier, wherein the fourth command causes the third electronic device to perform the fourth set of tasks.

Aspect 60: the method of aspect 58, further comprising:

receiving, from the fourth electronic device, an indication that the user of the first electronic device is authorized to make the requested purchase;

transmitting the indication to the remote device;

receive, from the remote device, a fifth command to perform a fifth set of tasks of the second plurality of tasks and the second device identifier corresponding to the third electronic device,

wherein in response to receiving the indication that the user of the first electronic device is authorized to make the requested purchase, the remote device sends the fifth command to the first electronic device, and

wherein the fifth set of tasks includes tasks to perform the requested purchase; and

sending the fifth command to the third electronic device based on the second device identifier, wherein the fifth command causes the third electronic device to perform the fifth set of tasks.

Aspect 61: a method, comprising:

at a system comprising at least a first electronic device and a second electronic device participating in a context-sharing group, the context-sharing group associated with a first location, wherein the context-sharing group is a set of at least two electronic devices that each share context information with at least one other electronic device included in the set, and wherein the set comprises a context collector:

receiving a first user voice input at the first electronic device;

at the first electronic device, outputting a first digital assistant response based on the first user voice input, wherein the first electronic device sends contextual information comprising a digital assistant dialog 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, at the second electronic device, an updated aggregated context for the context-sharing group from the context collector, wherein the updated aggregated context comprises the digital assistant dialog session history for the first electronic device; and

Outputting, at the second electronic device, a second digital assistant response based on the second user voice input and the digital assistant dialog history of the first electronic device.

Aspect 62: the method of aspect 61, wherein the first electronic device and the second electronic device are located within two separate areas of the first location.

Aspect 63: the method of any of aspects 61-62, wherein the first electronic device and the second electronic device receive the first user voice input and the second user voice input from a single user.

Aspect 64: the method of any of aspects 61-62, wherein the first electronic device and the second electronic device receive the first user voice input and the second user voice input from two different users.

Aspect 65: the method of any of aspects 61-64, further comprising:

prior to outputting the first digital assistant response:

receiving, at the first electronic device, an aggregated context of the context-sharing group from the context collector, wherein the aggregated context comprises context information associated with the first electronic device and context information associated with the second electronic device,

Transmitting, from the first electronic device, data corresponding to the first user voice input and at least a portion of the aggregated context to a remote device that is not participating in the context-sharing group; and

receiving, at the first electronic device, a first command to perform one or more tasks and a first device identifier corresponding to the first electronic device from the remote device,

wherein the remote device determines the one or more tasks and the device identifier corresponding to the first electronic device based at least on the data corresponding to the first user voice input and context information included in the aggregated context, and

wherein the first command causes the first electronic device to perform the one or more tasks and determine the first digital assistant response based on a result of the performance of the one or more tasks.

Aspect 66: the method of any of aspects 61-65, wherein the digital assistant dialog session history comprises data corresponding to the first user voice input and the first digital assistant response.

Aspect 67: the method of any of aspects 61-66, further comprising:

Sending a request for the updated aggregated context from the second electronic device to the context collector prior to receiving the updated aggregated context from the context collector.

Aspect 68: the method of any of aspects 61-67, wherein the context collector generates the updated aggregated context, and wherein generating the updated aggregated context comprises updating contextual information associated with the first electronic device included in an aggregated context of the context-sharing group based at least on the digital assistant conversation session history for the first electronic device.

Aspect 69: the method of any of aspects 61-68, further comprising:

prior to outputting the second digital assistant response:

transmitting data corresponding to the second user voice input and at least a portion of the updated aggregated context from the second electronic device to a remote device not participating in the context-sharing group, wherein the at least a portion of the updated aggregated context comprises the digital assistant dialog session history of the first electronic device; and

receiving, at the second electronic device, a second command to perform one or more tasks and a second 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 corresponding to the second electronic device based at least on the data corresponding to the second user voice input and the digital assistant dialog session history of the first electronic device, and

wherein the second command causes the second electronic device to perform the one or more tasks and determine the second digital assistant response based on a result of the performance of the one or more tasks.

Aspect 70: the method of aspect 69, wherein the digital assistant dialog session history includes data corresponding to the first user voice input, and wherein determining the one or more tasks based at least on the data corresponding to the second user voice input and the digital assistant dialog session history of the first electronic device includes the remote device disambiguating the second user voice input based on the first user voice.

Aspect 71: a method, comprising:

at a first electronic device participating in a context-sharing group, the context-sharing group associated with a first location, wherein the context-sharing group is a set of at least two electronic devices that each share 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 a user voice input, wherein the user voice input comprises a digital assistant trigger;

in response to detecting the digital assistant trigger, sending a first trigger announcement to the context collector, wherein the first trigger announcement indicates a first time at which the digital assistant trigger ends according to the first electronic device;

receiving a second trigger advertisement from the context collector, wherein the second trigger advertisement indicates a second time at which the digital assistant trigger ended according to the second electronic device;

determining whether the second time is within a predetermined time range prior to the first time; and

in accordance with a determination that the second time is within the predetermined time range prior to the first time, forgoing further processing of the user speech input.

Aspect 72: the method of aspect 71, further comprising:

in accordance with a determination that the second time is not within the predetermined time range, continuing to process the user speech input.

Aspect 73: the method of any of aspects 71-72, wherein each electronic device participating in the context sharing group is connected to a single wireless network of the first location.

Aspect 74: the method of aspect 73, wherein the first electronic device sends the first trigger advertisement to the context collector via the single wireless network.

Aspect 75: the method of any of aspects 71-74, wherein the context collector sends the second trigger advertisement to the first electronic device via the single wireless network in response to receiving the first trigger advertisement.

Aspect 76: the method of any of aspects 71-75, wherein the second electronic device sends the second trigger announcement to the context collector in response to detecting the digital assistant trigger included in the user speech input.

Aspect 77: the method of any of aspects 71-76, wherein the first electronic device and the second electronic device share a short-range communication connection, the method further comprising:

in response to detecting the digital assistant trigger, sending the first trigger advertisement to the second electronic device via the short-range communication connection;

receiving a third trigger advertisement from the second electronic device via the short-range communication connection, wherein the third trigger advertisement indicates a third time at which the digital assistant trigger ended according to the second electronic device;

After determining whether the second time is within the predetermined time range before the first time, determining whether the third time is within the predetermined time range before the first time; and

in accordance with a determination that the third time is within the predetermined range prior to the first time, forgoing further processing of the user speech input even though the second time is not within the predetermined range prior to the first time.

Aspect 78: a first electronic device, comprising:

one or more processors;

a memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, wherein the one or more programs include instructions for:

Aspect 79: a first electronic device, comprising:

one or more processors;

a memory; and

when the first electronic device participates in a context sharing group, the context sharing group is associated with a first location, wherein the context sharing group is a set of at least two electronic devices that each share contextual 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 a user voice input;

Aspect 80: a system, comprising:

one or more processors;

a memory; and

determining a user intent based on the user speech input;

determining one or more tasks corresponding to the user intent;

Aspect 81: a first electronic device, comprising:

one or more processors;

a memory; and

when the first electronic device participates in a context sharing group, the context sharing group is associated with a first location, wherein the context sharing group is a set of a plurality of electronic devices that each share context information with at least one other electronic device included in the set, and wherein the set includes a context collector:

receiving a user voice input;

receiving, from the remote device:

Aspect 82: a system, comprising:

One or more processors;

a memory; and

when a first electronic device and a second electronic device participate in a context-sharing group, the context-sharing group is associated with a first location, wherein the context-sharing group is a collection of at least two electronic devices that each share context information with at least one other electronic device included in the collection, and wherein the collection includes a context collector:

receiving a first user voice input at the first electronic device;

receiving a second user voice input at the second electronic device;

Aspect 83: a first electronic device, comprising:

one or more processors;

a memory; and

when the first electronic device participates in a context sharing group, the context sharing group is associated with a first location, wherein the context sharing group is a set of at least two electronic devices that each share 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:

Aspect 84: a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to perform operations comprising:

Aspect 85: a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to perform operations comprising:

receiving a user voice input;

Aspect 86: a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of one or more servers, cause the one or more servers to:

determining a user intent based on the user speech input;

determining one or more tasks corresponding to the user intent;

Aspect 87: a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to perform operations comprising:

receiving a user voice input;

receiving, from the remote device:

Aspect 88: a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to perform operations comprising:

receiving a first user voice input at the first electronic device;

receiving a second user voice input at the second electronic device;

Aspect 89: a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to perform operations comprising:

Aspect 90: a first electronic device, comprising:

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 that each share context information with at least one other electronic device included in the set, and wherein the set includes at least a second electronic device;

means for, after joining the context-sharing group, choosing one electronic device of the set of the at least two electronic devices as a context collector of the context-sharing group, wherein choosing the context collector comprises:

means for selecting, in accordance with the determination, the first electronic device as the context collector for receiving context information from at least the second electronic device in response to at least the second electronic device undergoing a device state change.

Aspect 91: a first electronic device, comprising:

Means for receiving a user voice input;

means for receiving an aggregated context of the context-sharing group from the context collector;

after receiving the aggregated context, means for providing at least a portion of the aggregated context and data corresponding to the user speech input to a remote device not participating in the context-sharing group;

means for receiving a command from the remote device 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 contextual information included in the at least a portion of the aggregated context; and

means 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.

Aspect 92: a system, comprising:

means for receiving, from a first electronic device participating in a context-sharing group associated with a first location, a user speech input and at least a portion of an aggregated context of the context-sharing group, wherein the context-sharing group is a collection of a plurality of electronic devices that each share context information with at least one other electronic device included in the collection;

Means for determining a user intent based on the user speech input;

means for determining one or more tasks corresponding to the user intent;

means for identifying a second electronic device of the plurality of 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 aggregated context; and

means for sending a command to the first electronic device to perform the one or more tasks and a device identifier corresponding to the second electronic device,

Aspect 93: a first electronic device, comprising:

Means for receiving a user voice input;

after receiving the aggregated context, means for providing at least a portion of the aggregated context and data corresponding to the user voice input to a remote device not participating in the context-sharing group, wherein the remote device determines a plurality of tasks based on the data corresponding to the user voice input;

means for receiving from the remote device:

means 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 set of tasks; and

means 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 set of tasks.

Aspect 94: a system, comprising:

means for receiving a first user voice input at the first electronic device;

means for outputting, at the first electronic device, a first digital assistant response based on the first user voice input, wherein the first electronic device sends contextual information comprising a digital assistant dialog session history for the first electronic device to the context collector after outputting the first digital assistant response;

means for receiving a second user voice input at the second electronic device;

means for receiving, at the second electronic device, an updated aggregated context for the context-sharing group from the context collector, wherein the updated aggregated context comprises the digital assistant dialog session history for the first electronic device; and

Means for outputting, at the second electronic device, a second digital assistant response based on the second user voice input and the digital assistant dialog history of the first electronic device.

Aspect 95: a first electronic device, comprising:

means for receiving a user voice input, wherein the user voice input comprises a digital assistant trigger;

in response to detecting the digital assistant trigger, means for sending a first trigger announcement to the context collector, wherein the first trigger announcement indicates a first time at which the digital assistant trigger ends according to the first electronic device;

means for receiving a second trigger advertisement from the context collector, wherein the second trigger advertisement indicates a second time at which the digital assistant trigger ended according to the second electronic device;

Means for determining whether the second time is within a predetermined time range prior to the first time; and

Aspect 96: a first electronic device, comprising:

one or more processors;

a memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and wherein the one or more programs include instructions for performing the method of any of aspects 1-15.

Aspect 97: a first electronic device, comprising:

one or more processors;

a memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and wherein the one or more programs include instructions for performing the method of any of aspects 16-30.

Aspect 98: a system, comprising:

one or more processors;

a memory; and

One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and wherein the one or more programs include instructions for performing the method of any of aspects 31-48.

Aspect 99: a first electronic device, comprising:

one or more processors;

a memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and wherein the one or more programs include instructions for performing the method of any of aspects 49-60.

Aspect 100: a system, comprising:

one or more processors;

a memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and wherein the one or more programs include instructions for performing the method of any of aspects 61-70.

Aspect 101: a first electronic device, comprising:

one or more processors;

A memory; and

one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and wherein the one or more programs include instructions for performing the method of any of aspects 71-77.

Aspect 102: a non-transitory computer readable storage medium storing one or more programs, wherein the one or more programs comprise instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to perform the method of any of aspects 1-15.

Aspect 103: a non-transitory computer readable storage medium storing one or more programs, wherein the one or more programs comprise instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to perform the method of any of aspects 16-30.

Aspect 104: a non-transitory computer readable storage medium storing one or more programs, wherein the one or more programs comprise instructions, which when executed by one or more processors of a system, cause the system to perform the method of any of aspects 31-48.

Aspect 105: a non-transitory computer readable storage medium storing one or more programs, wherein the one or more programs comprise instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to perform the method of any of aspects 49-60.

Aspect 106: a non-transitory computer readable storage medium storing one or more programs, wherein the one or more programs comprise instructions, which when executed by one or more processors of a system, cause the system to perform the method of any of aspects 61-70.

Aspect 107: a non-transitory computer readable storage medium storing one or more programs, wherein the one or more programs comprise instructions, which when executed by one or more processors of a first electronic device, cause the first electronic device to perform the method of any of aspects 71-77.

Aspect 108: a first electronic device, comprising:

apparatus for performing the method of any of aspects 1-15.

Aspect 109: a first electronic device, comprising:

Means for performing the method of any of aspects 16-30.

Aspect 110: a system, comprising:

means for performing the method of any of aspects 31-48.

Aspect 111: a first electronic device, comprising:

means for performing the method of any of aspects 49-60.

Aspect 112: a system, comprising:

means for performing the method of any of aspects 61-70.

Aspect 113: a first electronic device, comprising:

means for performing the method of any of aspects 71-77.

Claims

1. A method, 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 that each share 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 a user voice input;

after receiving the aggregated context, providing at least a portion of the aggregated context and data corresponding to the user speech input to a remote device not participating in the context-sharing group;

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.

3. The method of any of claims 1-2, wherein the second electronic device is the context collector.

4. The method of any of claims 1-2, wherein the context collector is a third electronic device participating in the context-sharing group.

5. The method of any of claims 1 to 4, further comprising:

6. The method of any of claims 1-5, wherein prior to receiving the aggregated context, at least the first electronic device and the second electronic device provide the context information included in the 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 undergoing a device state change.

7. The method of claim 6, wherein the context information comprises device state change information corresponding to at least the first electronic device and the second electronic device.

8. The method of any of claims 6-7, wherein the context information includes context state information corresponding to at least the first electronic device and the second electronic device.

9. The method of any of claims 6-8, wherein the context information includes device capability information corresponding to at least the first electronic device and the second electronic device.

10. The method of any of claims 1-9, wherein the command further causes the second electronic device to output a user query after performing the one or more tasks, and wherein the user query asks whether to send a second command to execute the one or more tasks to a fourth electronic device participating in the context-sharing group.

11. The method of any of claims 1-10, wherein the user speech input is ambiguous with respect to the electronic device defining that the user speech input is to be responded to, and wherein the remote device disambiguates the user speech input based on the context information included in the at least a portion of the aggregated context.

12. The method of any of claims 1-11, wherein both the first electronic device and the second electronic device are personal electronic devices that are each registered to a single user, and wherein the remote device disambiguates one or more words included in the user voice input based on user data associated with the second electronic device.

13. The method of any of claims 1-11, wherein both the first electronic device and the second electronic device are personal electronic devices that are each registered to a different user, the method further comprising:

prior to sending the command to the second electronic device:

outputting a request for user authentication; and

14. The method of any of claims 1-11, wherein the context-sharing group further comprises a fourth electronic device, and 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 each registered to a single user, the method further comprising:

15. The method of any of claims 1-14, wherein the user speech input comprises a digital assistant trigger, the method further comprising:

16. A first electronic device, comprising:

one or more processors;

a memory; and

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 that each share 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 a user voice input;

17. The first electronic device of claim 16, wherein each electronic device participating in the context-sharing group is connected to a single wireless network at the first location.

18. The first electronic device of any of claims 16-17, wherein the second electronic device is the context collector.

19. The first electronic device of any of claims 16-17, wherein the context collector is a third electronic device participating in the context-sharing group.

20. The first electronic device of any of claims 16-19, wherein the one or more programs include further instructions for:

21. The first electronic device of any of claims 16-20, wherein prior to receiving the aggregated context, at least the first electronic device and the second electronic device provide the context information included in the 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 undergoing a device state change.

22. The first electronic device of claim 21, wherein the context information includes device state change information corresponding to at least the first electronic device and the second electronic device.

23. The first electronic device of any of claims 21-22, wherein the context information includes context state information corresponding to at least the first electronic device and the second electronic device.

24. The first electronic device of any of claims 21-23, wherein the context information includes device capability information corresponding to at least the first electronic device and the second electronic device.

25. The first electronic device of any of claims 16-24, wherein the command further causes the second electronic device to output a user query after performing the one or more tasks, and wherein the user query asks whether to send a second command to execute the one or more tasks to a fourth electronic device participating in the context-sharing group.

26. The first electronic device of any of claims 16-25, wherein the user voice input is ambiguous with respect to the electronic device defining that the user voice input is to be responded to, and wherein the remote device disambiguates the user voice input based on the context information included in the at least a portion of the aggregated context.

27. The first electronic device of any of claims 16-26, wherein both the first electronic device and the second electronic device are personal electronic devices that are each registered to a single user, and wherein the remote device disambiguates one or more words included in the user voice input based on user data associated with the second electronic device.

28. The first electronic device of any of claims 16-26, wherein both the first electronic device and the second electronic device are personal electronic devices that are each registered to a different user, and wherein the one or more programs include further instructions for:

prior to sending the command to the second electronic device:

outputting a request for user authentication; and

29. The first electronic device of any of claims 16-26, wherein the context-sharing group further comprises 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 each registered to a single user, and wherein the one or more programs include further instructions for:

30. The first electronic device of any of claims 16-29, wherein the user speech input comprises a digital assistant trigger, and wherein the one or more programs include further instructions to:

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

receiving a user voice input;

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

33. The computer-readable storage medium of any of claims 31-32, wherein the second electronic device is the context collector.

34. The computer-readable storage medium of any of claims 31-32, wherein the context collector is a third electronic device participating in the context-sharing group.

35. The computer readable storage medium of any of claims 31-34, 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:

36. The computer-readable storage medium of any of claims 31-35, wherein prior to receiving the aggregated context, at least the first electronic device and the second electronic device provide the context information included in the 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 undergoing a device state change.

37. The computer-readable storage medium of claim 36, wherein the context information includes device state change information corresponding to at least the first electronic device and the second electronic device.

38. The computer-readable storage medium of any of claims 36-37, wherein the context information includes context state information corresponding to at least the first electronic device and the second electronic device.

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

40. The computer-readable storage medium of any of claims 31-39, wherein the commands further cause the second electronic device to output a user query after performing the one or more tasks, and wherein the user query asks whether to send a second command to execute the one or more tasks to a fourth electronic device participating in the context-sharing group.

41. The computer-readable storage medium of any of claims 31-40, wherein the user speech input is ambiguous with respect to the electronic device defining that the user speech input is to be responded to, and wherein the remote device disambiguates the user speech input based on the context information included in the at least a portion of the aggregated context.

42. The computer-readable storage medium of any of claims 31-41, wherein both the first electronic device and the second electronic device are personal electronic devices that are each registered to a single user, and wherein the remote device disambiguates one or more words included in the user voice input based on user data associated with the second electronic device.

43. The computer-readable storage medium of any of claims 31-41, wherein both the first electronic device and the second electronic device are personal electronic devices that are 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:

prior to sending the command to the second electronic device:

outputting a request for user authentication; and

44. The computer-readable storage medium of any of claims 31-41, wherein the context-sharing group further comprises 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 each registered to a single user, and wherein the one or more programs include further instructions that, when executed by the one or more processors of the first electronic device, cause the first electronic device to:

45. The computer-readable storage medium of any of claims 31-44, wherein the user speech input comprises a digital assistant trigger, 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:

46. An electronic device, comprising:

apparatus for performing the method of any one of claims 1 to 2.