Patent Grant
12107985
The present disclosure relates generally to computer user interfaces, and more specifically to techniques for managing media playback devices.
The number of electronic devices, and particularly smart devices, in users' homes continues to increase. These devices are increasingly being interconnected with each other, are increasingly more capable, and are performing more complex tasks. As such, these devices are increasingly expected to have thoughtfully-designed user interfaces.
Some techniques for managing media playback devices using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for managing media playback devices. Such methods and interfaces optionally complement or replace other methods for managing media playback devices. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges. Such methods and interfaces can reduce the number of unnecessary, extraneous, or repetitive user inputs. Further, such methods and interfaces can reduce the battery usage by a display or speaker of an electronic device.
In accordance with some embodiments, a method is performed at a device with a display. The method comprises: receiving a user input; and in response to receiving the user input, displaying, on the display, a multi-device interface that includes: one or more indicators associated with a plurality of available playback devices that are connected to the device and available to initiate playback of media from the device, and a media playback status of the plurality of available playback devices.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: receiving a user input; and in response to receiving the user input, displaying, on the display, a multi-device interface that includes: one or more indicators associated with a plurality of available playback devices that are connected to the device and available to initiate playback of media from the device, and a media playback status of the plurality of available playback devices.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a user input; and in response to receiving the user input, displaying, on the display, a multi-device interface that includes: one or more indicators associated with a plurality of available playback devices that are connected to the device and available to initiate playback of media from the device, and a media playback status of the plurality of available playback devices.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; means for receiving a user input; and means for, responsive to receiving the user input, displaying, on the display, a multi-device interface that includes: one or more indicators associated with a plurality of available playback devices that are connected to the device and available to initiate playback of media from the device, and a media playback status of the plurality of available playback devices.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: receiving a user input; and in response to receiving the user input, displaying, on the display, a multi-device interface that includes: one or more indicators associated with a plurality of available playback devices that are connected to the device and available to initiate playback of media from the device, and a media playback status of the plurality of available playback devices.
In accordance with some embodiments, a method is performed at a device with a display. The method comprises: displaying, on the display, a first current media interface for the device, wherein the first current media interface includes: a representation of a first media item available for playback on the device, and a playback device selection affordance; receiving a first user input representing selection of the playback device selection affordance; in response to receiving the first user input, displaying, on the display, one or more affordances associated with a plurality of available playback devices connected to the device; receiving a second user input representing selection of the one or more affordances associated with the plurality of available playback devices; and in response to receiving the second user input, configuring the device to initiate playback on the plurality of available playback devices.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: displaying, on the display, a first current media interface for the device, wherein the first current media interface includes: a representation of a first media item available for playback on the device, and a playback device selection affordance; receiving a first user input representing selection of the playback device selection affordance; in response to receiving the first user input, displaying, on the display, one or more affordances associated with a plurality of available playback devices connected to the device; receiving a second user input representing selection of the one or more affordances associated with the plurality of available playback devices; and in response to receiving the second user input, configuring the device to initiate playback on the plurality of available playback devices.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, on the display, a first current media interface for the device, wherein the first current media interface includes: a representation of a first media item available for playback on the device, and a playback device selection affordance; receiving a first user input representing selection of the playback device selection affordance; in response to receiving the first user input, displaying, on the display, one or more affordances associated with a plurality of available playback devices connected to the device; receiving a second user input representing selection of the one or more affordances associated with the plurality of available playback devices; and in response to receiving the second user input, configuring the device to initiate playback on the plurality of available playback devices.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; means for displaying, on the display, a first current media interface for the device, wherein the first current media interface includes: a representation of a first media item available for playback on the device, and a playback device selection affordance; means for receiving a first user input representing selection of the playback device selection affordance; means for, responsive to receiving the first user input, displaying, on the display, one or more affordances associated with a plurality of available playback devices connected to the device; means for receiving a second user input representing selection of the one or more affordances associated with the plurality of available playback devices; and means for, responsive to receiving the second user input, configuring the device to initiate playback on the plurality of available playback devices.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: displaying, on the display, a first current media interface for the device, wherein the first current media interface includes: a representation of a first media item available for playback on the device, and a playback device selection affordance; receiving a first user input representing selection of the playback device selection affordance; in response to receiving the first user input, displaying, on the display, one or more affordances associated with a plurality of available playback devices connected to the device; receiving a second user input representing selection of the one or more affordances associated with the plurality of available playback devices; and in response to receiving the second user input, configuring the device to initiate playback on the plurality of available playback devices.
In accordance with some embodiments, a method is performed at a first device. The method comprises: detecting an indication that a physical proximity between the first device and a second device satisfies a proximity condition, wherein the first device is connected to the second device via a communication link; in accordance with detecting the indication, audibly outputting an audio tone signal, wherein the audio tone signal is out-of-band to the communication link; subsequent to outputting the audio tone signal, determining whether a response audio tone signal from the second device has been received; in accordance with a determination that the response audio tone signal from the second device has been received, proceeding to a next step in a configuration process; and in accordance with a determination that the response audio tone signal from the second device has not been received, forgoing proceeding to the next step in the configuration process.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs including instructions for: detecting an indication that a physical proximity between the first device and a second device satisfies a proximity condition, wherein the first device is connected to the second device via a communication link; in accordance with detecting the indication, audibly outputting an audio tone signal, wherein the audio tone signal is out-of-band to the communication link; subsequent to outputting the audio tone signal, determining whether a response audio tone signal from the second device has been received; in accordance with a determination that the response audio tone signal from the second device has been received, proceeding to a next step in a configuration process; and in accordance with a determination that the response audio tone signal from the second device has not been received, forgoing proceeding to the next step in the configuration process.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: detecting an indication that a physical proximity between the first device and a second device satisfies a proximity condition, wherein the first device is connected to the second device via a communication link; in accordance with detecting the indication, audibly outputting an audio tone signal, wherein the audio tone signal is out-of-band to the communication link; subsequent to outputting the audio tone signal, determining whether a response audio tone signal from the second device has been received; in accordance with a determination that the response audio tone signal from the second device has been received, proceeding to a next step in a configuration process; and in accordance with a determination that the response audio tone signal from the second device has not been received, forgoing proceeding to the next step in the configuration process.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: means for detecting an indication that a physical proximity between the first device and a second device satisfies a proximity condition, wherein the first device is connected to the second device via a communication link; means for, in accordance with detecting the indication, audibly outputting an audio tone signal, wherein the audio tone signal is out-of-band to the communication link; means for, subsequent to outputting the audio tone signal, determining whether a response audio tone signal from the second device has been received; means for, in accordance with a determination that the response audio tone signal from the second device has been received, proceeding to a next step in a configuration process; and means for, in accordance with a determination that the response audio tone signal from the second device has not been received, forgoing proceeding to the next step in the configuration process.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs including instructions for: detecting an indication that a physical proximity between the first device and a second device satisfies a proximity condition, wherein the first device is connected to the second device via a communication link; in accordance with detecting the indication, audibly outputting an audio tone signal, wherein the audio tone signal is out-of-band to the communication link; subsequent to outputting the audio tone signal, determining whether a response audio tone signal from the second device has been received; in accordance with a determination that the response audio tone signal from the second device has been received, proceeding to a next step in a configuration process; and in accordance with a determination that the response audio tone signal from the second device has not been received, forgoing proceeding to the next step in the configuration process.
In accordance with some embodiments, a method is performed at a first device with a display. The method comprises: detecting, while connected to a second device, an indication that a physical proximity between the first device and the second device satisfies a proximity condition; and in accordance with detecting that the physical proximity satisfies the proximity condition, displaying, on the display, a media information interface.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, wherein the electronic device is a first device, the one or more programs including instructions for: detecting, while connected to a second device, an indication that a physical proximity between the first device and the second device satisfies a proximity condition; and in accordance with detecting that the physical proximity satisfies the proximity condition, displaying, on the display, a media information interface.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: detecting, while connected to a second device, an indication that a physical proximity between the electronic device and the second device satisfies a proximity condition; and in accordance with detecting that the physical proximity satisfies the proximity condition, displaying, on the display, a media information interface.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; means for detecting, while connected to a second device, an indication that a physical proximity between the electronic device and the second device satisfies a proximity condition; and means for in accordance with detecting that the physical proximity satisfies the proximity condition, displaying, on the display, a media information interface.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, wherein the electronic device is a first device, the one or more programs including instructions for: detecting, while connected to a second device, an indication that a physical proximity between the first device and the second device satisfies a proximity condition; and in accordance with detecting that the physical proximity satisfies the proximity condition, displaying, on the display, a media information interface.
In accordance with some embodiments, a method is performed at a device with a touch-sensitive surface. The method comprises: detecting a touch on the touch-sensitive surface; in response to detecting the touch on the touch-sensitive surface, determining whether the device is currently playing media; in accordance with a determination that the device is currently playing media: determining whether a location of the touch is within a first area of the touch-sensitive surface or within a second area of the touch-sensitive surface, wherein the first area and the second area are non-overlapping; in accordance with a determination that the location of the touch is within the first area of the touch-sensitive surface, ceasing playing media; and in accordance with a determination that the location of the touch is within the second area of the touch-sensitive surface, adjusting a volume of the currently playing media; and in accordance with a determination that the device is not currently playing media, initiating playback of media.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a touch-sensitive surface, the one or more programs including instructions for: detecting a touch on the touch-sensitive surface; in response to detecting the touch on the touch-sensitive surface, determining whether the device is currently playing media; in accordance with a determination that the device is currently playing media: determining whether a location of the touch is within a first area of the touch-sensitive surface or within a second area of the touch-sensitive surface, wherein the first area and the second area are non-overlapping; in accordance with a determination that the location of the touch is within the first area of the touch-sensitive surface, ceasing playing media; and in accordance with a determination that the location of the touch is within the second area of the touch-sensitive surface, adjusting a volume of the currently playing media; and in accordance with a determination that the device is not currently playing media, initiating playback of media.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a touch-sensitive surface; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: detecting a touch on the touch-sensitive surface; in response to detecting the touch on the touch-sensitive surface, determining whether the device is currently playing media; in accordance with a determination that the device is currently playing media: determining whether a location of the touch is within a first area of the touch-sensitive surface or within a second area of the touch-sensitive surface, wherein the first area and the second area are non-overlapping; in accordance with a determination that the location of the touch is within the first area of the touch-sensitive surface, ceasing playing media; and in accordance with a determination that the location of the touch is within the second area of the touch-sensitive surface, adjusting a volume of the currently playing media; and in accordance with a determination that the device is not currently playing media, initiating playback of media.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a touch-sensitive surface; means for detecting a touch on the touch-sensitive surface; means for, responsive to detecting the touch on the touch-sensitive surface, determining whether the device is currently playing media; means for, in accordance with a determination that the device is currently playing media: determining whether a location of the touch is within a first area of the touch-sensitive surface or within a second area of the touch-sensitive surface, wherein the first area and the second area are non-overlapping; in accordance with a determination that the location of the touch is within the first area of the touch-sensitive surface, ceasing playing media; and in accordance with a determination that the location of the touch is within the second area of the touch-sensitive surface, adjusting a volume of the currently playing media; and means for, in accordance with a determination that the device is not currently playing media, initiating playback of media.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a touch-sensitive surface, the one or more programs including instructions for: detecting a touch on the touch-sensitive surface; in response to detecting the touch on the touch-sensitive surface, determining whether the device is currently playing media; in accordance with a determination that the device is currently playing media: determining whether a location of the touch is within a first area of the touch-sensitive surface or within a second area of the touch-sensitive surface, wherein the first area and the second area are non-overlapping; in accordance with a determination that the location of the touch is within the first area of the touch-sensitive surface, ceasing playing media; and in accordance with a determination that the location of the touch is within the second area of the touch-sensitive surface, adjusting a volume of the currently playing media; and in accordance with a determination that the device is not currently playing media, initiating playback of media.
In accordance with some embodiments, a method is performed at a first device. The method comprises: receiving a first request to queue a first media item for playback on a set of devices, wherein the set of devices includes the first device; adding the first media item to a playback queue; receiving a second request to queue a second media item for playback on the set of devices; adding the second media item to the playback queue; accessing the first media item from a first media streaming service; initiating playback of the first media item on the set of devices; accessing the second media item from a second media streaming service different than the first media streaming service; and initiating playback of the second media item on the set of devices.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device, the one or more programs including instructions for: receiving a first request to queue a first media item for playback on a set of devices, wherein the set of devices includes the first device; adding the first media item to a playback queue; receiving a second request to queue a second media item for playback on the set of devices; adding the second media item to the playback queue; accessing the first media item from a first media streaming service; initiating playback of the first media item on the set of devices; accessing the second media item from a second media streaming service different than the first media streaming service; and initiating playback of the second media item on the set of devices.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a first request to queue a first media item for playback on a set of devices, wherein the set of devices includes the electronic device; adding the first media item to a playback queue; receiving a second request to queue a second media item for playback on the set of devices; adding the second media item to the playback queue; accessing the first media item from a first media streaming service; initiating playback of the first media item on the set of devices; accessing the second media item from a second media streaming service different than the first media streaming service; and initiating playback of the second media item on the set of devices.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: means for receiving a first request to queue a first media item for playback on a set of devices, wherein the set of devices includes the electronic device; means for adding the first media item to a playback queue; means for receiving a second request to queue a second media item for playback on the set of devices; means for adding the second media item to the playback queue; means for accessing the first media item from a first media streaming service; means for initiating playback of the first media item on the set of devices; means for accessing the second media item from a second media streaming service different than the first media streaming service; and means for initiating playback of the second media item on the set of devices.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device, the one or more programs including instructions for: receiving a first request to queue a first media item for playback on a set of devices, wherein the set of devices includes the first device; adding the first media item to a playback queue; receiving a second request to queue a second media item for playback on the set of devices; adding the second media item to the playback queue; accessing the first media item from a first media streaming service; initiating playback of the first media item on the set of devices; accessing the second media item from a second media streaming service different than the first media streaming service; and initiating playback of the second media item on the set of devices.
In accordance with some embodiments, a method is performed at a first device. The method comprises: receiving, from a second device associated with a first user, a first request to queue a first media item for playback on a set of devices, wherein the set of devices includes the first device; adding the first media item to a playback queue; receiving, from a third device associated with a second user, a second request to queue a second media item for playback on the set of devices, wherein the second user is different than the first; adding the second media item to the playback queue; initiating playback of the first media item on the set of devices; and initiating playback of the second media item on the set of devices.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device, the one or more programs including instructions for: receiving, from a second device associated with a first user, a first request to queue a first media item for playback on a set of devices, wherein the set of devices includes the first device; adding the first media item to a playback queue; receiving, from a third device associated with a second user, a second request to queue a second media item for playback on the set of devices, wherein the second user is different than the first; adding the second media item to the playback queue; initiating playback of the first media item on the set of devices; and initiating playback of the second media item on the set of devices.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving, from a second device associated with a first user, a first request to queue a first media item for playback on a set of devices, wherein the set of devices includes the electronic device; adding the first media item to a playback queue; receiving, from a third device associated with a second user, a second request to queue a second media item for playback on the set of devices, wherein the second user is different than the first; adding the second media item to the playback queue; initiating playback of the first media item on the set of devices; and initiating playback of the second media item on the set of devices.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: means for receiving, from a second device associated with a first user, a first request to queue a first media item for playback on a set of devices, wherein the set of devices includes the electronic device; means for adding the first media item to a playback queue; means for receiving, from a third device associated with a second user, a second request to queue a second media item for playback on the set of devices, wherein the second user is different than the first; means for adding the second media item to the playback queue; means for initiating playback of the first media item on the set of devices; and means for initiating playback of the second media item on the set of devices.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device, the one or more programs including instructions for: receiving, from a second device associated with a first user, a first request to queue a first media item for playback on a set of devices, wherein the set of devices includes the first device; adding the first media item to a playback queue; receiving, from a third device associated with a second user, a second request to queue a second media item for playback on the set of devices, wherein the second user is different than the first; adding the second media item to the playback queue; initiating playback of the first media item on the set of devices; and initiating playback of the second media item on the set of devices.
In accordance with some embodiments, a method is performed at a first device with a display. The method comprises: detecting an audio tone signal indicative of a pairing handshake with a second device, wherein the first device is connected to the second device via a communication link, and wherein the audio tone signal is out-of-band to the communication link; in accordance with detecting the audio tone signal, initiating, on the first device, a configuration process for configuring the second device; during the configuration process, displaying, on the display, a configuration user interface that includes a prompt to select a location; receiving user input selection of a location; and in response to receiving the user input, configuring the second device to be associated with the location.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, wherein the electronic device is a first device, the one or more programs including instructions for: detecting an audio tone signal indicative of a pairing handshake with a second device, wherein the first device is connected to the second device via a communication link, and wherein the audio tone signal is out-of-band to the communication link; in accordance with detecting the audio tone signal, initiating, on the first device, a configuration process for configuring the second device; during the configuration process, displaying, on the display, a configuration user interface that includes a prompt to select a location; receiving user input selection of a location; and in response to receiving the user input, configuring the second device to be associated with the location.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: detecting an audio tone signal indicative of a pairing handshake with a second device, wherein the electronic device is connected to the second device via a communication link, and wherein the audio tone signal is out-of-band to the communication link; in accordance with detecting the audio tone signal, initiating, on the electronic device, a configuration process for configuring the second device; during the configuration process, displaying, on the display, a configuration user interface that includes a prompt to select a location; receiving user input selection of a location; and in response to receiving the user input, configuring the second device to be associated with the location.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; means for detecting an audio tone signal indicative of a pairing handshake with a second device, wherein the electronic device is connected to the second device via a communication link, and wherein the audio tone signal is out-of-band to the communication link; means for, in accordance with detecting the audio tone signal, initiating, on the electronic device, a configuration process for configuring the second device; means for, during the configuration process, displaying, on the display, a configuration user interface that includes a prompt to select a location; means for receiving user input selection of a location; and means for, responsive to receiving the user input, configuring the second device to be associated with the location.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, wherein the electronic device is a first device, the one or more programs including instructions for: detecting an audio tone signal indicative of a pairing handshake with a second device, wherein the first device is connected to the second device via a communication link, and wherein the audio tone signal is out-of-band to the communication link; in accordance with detecting the audio tone signal, initiating, on the first device, a configuration process for configuring the second device; during the configuration process, displaying, on the display, a configuration user interface that includes a prompt to select a location; receiving user input selection of a location; and in response to receiving the user input, configuring the second device to be associated with the location.
In accordance with some embodiments, a method is performed at a device. The method comprises: while outputting an audible signal from the device, detecting a user input voice command from a voice command source; in response to detecting the user input voice command, determining a spatial position of the voice command source relative to the device; and while continuing to output the audible signal, adjusting the output of the audible signal based on the spatial position of the voice command source.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs including instructions for: while outputting an audible signal from the device, detecting a user input voice command from a voice command source; in response to detecting the user input voice command, determining a spatial position of the voice command source relative to the device; and while continuing to output the audible signal, adjusting the output of the audible signal based on the spatial position of the voice command source.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: while outputting an audible signal from the device, detecting a user input voice command from a voice command source; in response to detecting the user input voice command, determining a spatial position of the voice command source relative to the device; and while continuing to output the audible signal, adjusting the output of the audible signal based on the spatial position of the voice command source.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: means for, while outputting an audible signal from the device, detecting a user input voice command from a voice command source; means for, responsive to detecting the user input voice command, determining a spatial position of the voice command source relative to the device; and means for, while continuing to output the audible signal, adjusting the output of the audible signal based on the spatial position of the voice command source.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs including instructions for: while outputting an audible signal from the device, detecting a user input voice command from a voice command source; in response to detecting the user input voice command, determining a spatial position of the voice command source relative to the device; and while continuing to output the audible signal, adjusting the output of the audible signal based on the spatial position of the voice command source.
In accordance with some embodiments, a method is performed at a first device associated with a first user account. The method comprises: detecting that a second device associated with a second user account is connected to the first device, wherein the first user account is associated with a first media preference profile; wherein the second user account is associated with a second media preference profile different than the first media preference profile; and initiating playback of media based on the first media preference profile and the second media preference profile.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device associated with a first user account, wherein the first user account is associated with a first media preference profile, the one or more programs including instructions for: detecting that a second device associated with a second user account is connected to the first device, wherein the second user account is associated with a second media preference profile different than the first media preference profile; and initiating playback of media based on the first media preference profile and the second media preference profile.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: detecting that a second device associated with a second user account is connected to the electronic device, wherein the electronic device is associated with a first user account, wherein the first user account is associated with a first media preference profile: wherein the second user account is associated with a second media preference profile different than the first media preference profile; and initiating playback of media based on the first media preference profile and the second media preference profile.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: means for detecting that a second device associated with a second user account is connected to the electronic device, wherein the electronic device is associated with a first user account, wherein the first user account is associated with a first media preference profile: wherein the second user account is associated with a second media preference profile different than the first media preference profile; and means for initiating playback of media based on the first media preference profile and the second media preference profile.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device associated with a first user account, wherein the first user account is associated with a first media preference profile, the one or more programs including instructions for: detecting that a second device associated with a second user account is connected to the first device, wherein the second user account is associated with a second media preference profile different than the first media preference profile; and initiating playback of media based on the first media preference profile and the second media preference profile.
In accordance with some embodiments, a method is performed at a first device. The method comprises: receiving a request, from a third device, to initiate media playback on at least one device of a set of devices, wherein the set of devices comprises the first device and a second device, wherein the third device is not a member of the set of devices, and wherein the third device is connected to the first device; in response to receiving the request: in accordance with a determination that the third device has permission to initiate media playback on the at least one device of set of devices, initiating media playback on the set of devices; and in accordance with a determination that the third device does not have permission to initiate media playback on the at least one device of set of devices: transmitting a request for permission to the second device; and in response to receiving permission from the second device, initiating media playback on the at least one device of the set of devices.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device, the one or more programs including instructions for: receiving a request, from a third device, to initiate media playback on at least one device of a set of devices, wherein the set of devices comprises the first device and a second device, wherein the third device is not a member of the set of devices, and wherein the third device is connected to the first device; in response to receiving the request: in accordance with a determination that the third device has permission to initiate media playback on the at least one device of set of devices, initiating media playback on the set of devices; and in accordance with a determination that the third device does not have permission to initiate media playback on the at least one device of set of devices: transmitting a request for permission to the second device; and in response to receiving permission from the second device, initiating media playback on the at least one device of the set of devices.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a request, from a third device, to initiate media playback on at least one device of a set of devices, wherein the set of devices comprises the electronic device and a second device, wherein the third device is not a member of the set of devices, and wherein the third device is connected to the electronic device; in response to receiving the request: in accordance with a determination that the third device has permission to initiate media playback on the at least one device of set of devices, initiating media playback on the set of devices; and in accordance with a determination that the third device does not have permission to initiate media playback on the at least one device of set of devices: transmitting a request for permission to the second device; and in response to receiving permission from the second device, initiating media playback on the at least one device of the set of devices.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: means for receiving a request, from a third device, to initiate media playback on at least one device of a set of devices, wherein the set of devices comprises the electronic device and a second device, wherein the third device is not a member of the set of devices, and wherein the third device is connected to the electronic device; means for, responsive to receiving the request: in accordance with a determination that the third device has permission to initiate media playback on the at least one device of set of devices, initiating media playback on the set of devices; and in accordance with a determination that the third device does not have permission to initiate media playback on the at least one device of set of devices: transmitting a request for permission to the second device; and in response to receiving permission from the second device, initiating media playback on the at least one device of the set of devices.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device, the one or more programs including instructions for: receiving a request, from a third device, to initiate media playback on at least one device of a set of devices, wherein the set of devices comprises the first device and a second device, wherein the third device is not a member of the set of devices, and wherein the third device is connected to the first device; in response to receiving the request: in accordance with a determination that the third device has permission to initiate media playback on the at least one device of set of devices, initiating media playback on the set of devices; and in accordance with a determination that the third device does not have permission to initiate media playback on the at least one device of set of devices: transmitting a request for permission to the second device; and in response to receiving permission from the second device, initiating media playback on the at least one device of the set of devices.
In accordance with some embodiments, a method is performed at a first device associated with a user account. The method comprises: receiving user input representing a request to access data from the user account; in response to receiving the user input, determining whether a physical positioning of the first device and a second device associated with the user account satisfies a permissive condition; in accordance with a determination that the physical positioning satisfies the permissive condition, providing the data from the user account through the first device; and in accordance with a determination that the physical positioning does not satisfy the permissive condition, forgoing providing the data from the user account through the first device.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first electronic device associated with a user account, the one or more programs including instructions for: receiving user input representing a request to access data from the user account; in response to receiving the user input, determining whether a physical positioning of the electronic device and a second device associated with the user account satisfies a permissive condition; in accordance with a determination that the physical positioning satisfies the permissive condition, providing the data from the user account through the electronic device; and in accordance with a determination that the physical positioning does not satisfy the permissive condition, forgoing providing the data from the user account through the electronic device.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving user input representing a request to access data from a user account, wherein the electronic device is associated with the user account; in response to receiving the user input, determining whether a physical positioning of the electronic device and a second device associated with the user account satisfies a permissive condition; in accordance with a determination that the physical positioning satisfies the permissive condition, providing the data from the user account through the electronic device; and in accordance with a determination that the physical positioning does not satisfy the permissive condition, forgoing providing the data from the user account through the electronic device.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: means for receiving user input representing a request to access data from a user account, wherein the electronic device is associated with the user account; means for, responsive to receiving the user input, determining whether a physical positioning of the electronic device and a second device associated with the user account satisfies a permissive condition; means for, in accordance with a determination that the physical positioning satisfies the permissive condition, providing the data from the user account through the electronic device; and means for, in accordance with a determination that the physical positioning does not satisfy the permissive condition, forgoing providing the data from the user account through the electronic device.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first electronic device associated with a user account, the one or more programs including instructions for: receiving user input representing a request to access data from the user account; in response to receiving the user input, determining whether a physical positioning of the electronic device and a second device associated with the user account satisfies a permissive condition; in accordance with a determination that the physical positioning satisfies the permissive condition, providing the data from the user account through the electronic device; and in accordance with a determination that the physical positioning does not satisfy the permissive condition, forgoing providing the data from the user account through the electronic device.
In accordance with some embodiments, a method is performed at a first device. The method comprises: receiving a command to initiate playback of media on a set of devices comprising the first device and a second device; in response to receiving the command, initiating synchronized playback of the media on the set of devices, wherein the second device is designated as a primary device configured to coordinate the playback of the media on the set of devices, and wherein the first device is configured to be a designated heir to the primary device.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device, the one or more programs including instructions for: receiving a command to initiate playback of media on a set of devices comprising the first device and a second device; in response to receiving the command, initiating synchronized playback of the media on the set of devices, wherein the second device is designated as a primary device configured to coordinate the playback of the media on the set of devices, and wherein the first device is configured to be a designated heir to the primary device.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a command to initiate playback of media on a set of devices comprising the electronic device and a second device; in response to receiving the command, initiating synchronized playback of the media on the set of devices, wherein the second device is designated as a primary device configured to coordinate the playback of the media on the set of devices, and wherein the electronic device is configured to be a designated heir to the primary device.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: means for receiving a command to initiate playback of media on a set of devices comprising the electronic device and a second device; means for, responsive to receiving the command, initiating synchronized playback of the media on the set of devices, wherein the second device is designated as a primary device configured to coordinate the playback of the media on the set of devices, and wherein the electronic device is configured to be a designated heir to the primary device.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device, the one or more programs including instructions for: receiving a command to initiate playback of media on a set of devices comprising the first device and a second device; in response to receiving the command, initiating synchronized playback of the media on the set of devices, wherein the second device is designated as a primary device configured to coordinate the playback of the media on the set of devices, and wherein the first device is configured to be a designated heir to the primary device.
In accordance with some embodiments, a method is performed at a first device of a set of devices associated with a first user account. The method comprises: receiving an audible output trigger event; determining that a first user, associated with the first user account, is located within an audible output range of a device of the set of devices; in accordance with a determination that the first user is within the audible output range of the first device, and in accordance with an occurrence of the audible output trigger event, outputting an audible output; and in accordance with a determination that the first user is within the audible output range of a second device, and in accordance with an occurrence of the audible output trigger event, forgoing outputting the audible output.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device of a set of devices associated with a first user account, the one or more programs including instructions for: receiving an audible output trigger event; determining that a first user, associated with the first user account, is located within an audible output range of a device of the set of devices; in accordance with a determination that the first user is within the audible output range of the first device, and in accordance with an occurrence of the audible output trigger event, outputting an audible output; and in accordance with a determination that the first user is within the audible output range of a second device, and in accordance with an occurrence of the audible output trigger event, forgoing outputting the audible output.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving an audible output trigger event; determining that a first user, associated with a first user account, is located within an audible output range of a device of a set of devices associated with the first user account, wherein the electronic device is a first device of the set of devices; in accordance with a determination that the first user is within the audible output range of the first device, and in accordance with an occurrence of the audible output trigger event, outputting an audible output; and in accordance with a determination that the first user is within the audible output range of a second device, and in accordance with an occurrence of the audible output trigger event, forgoing outputting the audible output.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: means for receiving an audible output trigger event; means for determining that a first user, associated with a first user account, is located within an audible output range of a device of a set of devices associated with the first user account, wherein the electronic device is a first device of the set of devices; means for, in accordance with a determination that the first user is within the audible output range of the first device, and in accordance with an occurrence of the audible output trigger event, outputting an audible output; and means for, in accordance with a determination that the first user is within the audible output range of a second device, and in accordance with an occurrence of the audible output trigger event, forgoing outputting the audible output.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device of a set of devices associated with a first user account, the one or more programs including instructions for: receiving an audible output trigger event; determining that a first user, associated with the first user account, is located within an audible output range of a device of the set of devices; in accordance with a determination that the first user is within the audible output range of the first device, and in accordance with an occurrence of the audible output trigger event, outputting an audible output; and in accordance with a determination that the first user is within the audible output range of a second device, and in accordance with an occurrence of the audible output trigger event, forgoing outputting the audible output.
In accordance with some embodiments, a method is performed at a first device. The method comprises: receiving a user input voice command representing a request to output a signal representative of media currently being played back by a second device that is connected to the first device; in response to receiving the user input, transmitting a request for information regarding the media currently being played back by the second device; receiving the information regarding the media currently being played back by the second device; and in accordance with receiving the information regarding the media currently being played back by the second device, and while the second device continues playback of at least one component of the media, initiating output of at least one component of the signal representative of the media currently being played back by the second device.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device, the one or more programs including instructions for: receiving a user input voice command representing a request to output a signal representative of media currently being played back by a second device that is connected to the first device; in response to receiving the user input, transmitting a request for information regarding the media currently being played back by the second device; receiving the information regarding the media currently being played back by the second device; and in accordance with receiving the information regarding the media currently being played back by the second device, and while the second device continues playback of at least one component of the media, initiating output of at least one component of the signal representative of the media currently being played back by the second device.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a user input voice command representing a request to output a signal representative of media currently being played back by a second device that is connected to the electronic device; in response to receiving the user input, transmitting a request for information regarding the media currently being played back by the second device; receiving the information regarding the media currently being played back by the second device; and in accordance with receiving the information regarding the media currently being played back by the second device, and while the second device continues playback of at least one component of the media, initiating output of at least one component of the signal representative of the media currently being played back by the second device.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: means for receiving a user input voice command representing a request to output a signal representative of media currently being played back by a second device that is connected to the electronic device; means for, responsive to receiving the user input, transmitting a request for information regarding the media currently being played back by the second device; means for receiving the information regarding the media currently being played back by the second device; and means for, in accordance with receiving the information regarding the media currently being played back by the second device, and while the second device continues playback of at least one component of the media, initiating output of at least one component of the signal representative of the media currently being played back by the second device.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device, the one or more programs including instructions for: receiving a user input voice command representing a request to output a signal representative of media currently being played back by a second device that is connected to the first device; in response to receiving the user input, transmitting a request for information regarding the media currently being played back by the second device; receiving the information regarding the media currently being played back by the second device; and in accordance with receiving the information regarding the media currently being played back by the second device, and while the second device continues playback of at least one component of the media, initiating output of at least one component of the signal representative of the media currently being played back by the second device.
In accordance with some embodiments, a method is performed at a first device. The method comprises: receiving a request to initiate media playback on a set of devices that does not include the first device; in response to receiving the request, and while the first device is coordinating media playback, determining whether the set of devices includes a device configured to coordinate media playback; in accordance with a determination that the set of devices includes a device configured to coordinate media playback, transferring a media playback coordination task from the first device to the device configured to coordinate media playback; and in accordance with a determination that the set of devices does not include a device configured to coordinate media playback, forgoing transferring the media playback coordination task.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device, the one or more programs including instructions for: receiving a request to initiate media playback on a set of devices that does not include the first device; in response to receiving the request, and while the first device is coordinating media playback, determining whether the set of devices includes a device configured to coordinate media playback; in accordance with a determination that the set of devices includes a device configured to coordinate media playback, transferring a media playback coordination task from the first device to the device configured to coordinate media playback; and in accordance with a determination that the set of devices does not include a device configured to coordinate media playback, forgoing transferring the media playback coordination task.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a request to initiate media playback on a set of devices that does not include the electronic device; in response to receiving the request, and while the electronic device is coordinating media playback, determining whether the set of devices includes a device configured to coordinate media playback; in accordance with a determination that the set of devices includes a device configured to coordinate media playback, transferring a media playback coordination task from the electronic device to the device configured to coordinate media playback; and in accordance with a determination that the set of devices does not include a device configured to coordinate media playback, forgoing transferring the media playback coordination task.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: means for receiving a request to initiate media playback on a set of devices that does not include the electronic device; means for, responsive to receiving the request, and while the electronic device is coordinating media playback, determining whether the set of devices includes a device configured to coordinate media playback; means for, in accordance with a determination that the set of devices includes a device configured to coordinate media playback, transferring a media playback coordination task from the electronic device to the device configured to coordinate media playback; and means for, in accordance with a determination that the set of devices does not include a device configured to coordinate media playback, forgoing transferring the media playback coordination task.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, wherein the electronic device is a first device, the one or more programs including instructions for: receiving a request to initiate media playback on a set of devices that does not include the first device; in response to receiving the request, and while the first device is coordinating media playback, determining whether the set of devices includes a device configured to coordinate media playback; in accordance with a determination that the set of devices includes a device configured to coordinate media playback, transferring a media playback coordination task from the first device to the device configured to coordinate media playback; and in accordance with a determination that the set of devices does not include a device configured to coordinate media playback, forgoing transferring the media playback coordination task.
In accordance with some embodiments, a method is performed at a device. The method comprises: receiving a request to initiate media playback on a set of devices connected to the device; in response to receiving the request, and while the device is coordinating media playback, determining, for each device of a plurality of devices configured to coordinate media playback and connected to the set of devices, one or more device characteristics; selecting, based at least in part on the one or more characteristics of each device of the plurality of devices configured to coordinate media playback, a primary device from among the plurality of devices configured to coordinate media playback; and transferring a media playback coordination task from the device to the primary device configured to coordinate media playback.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs including instructions for: receiving a request to initiate media playback on a set of devices connected to the device; in response to receiving the request, and while the device is coordinating media playback, determining, for each device of a plurality of devices configured to coordinate media playback and connected to the set of devices, one or more device characteristics; selecting, based at least in part on the one or more characteristics of each device of the plurality of devices configured to coordinate media playback, a primary device from among the plurality of devices configured to coordinate media playback; and transferring a media playback coordination task from the device to the primary device configured to coordinate media playback.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving a request to initiate media playback on a set of devices connected to the device; in response to receiving the request, and while the device is coordinating media playback, determining, for each device of a plurality of devices configured to coordinate media playback and connected to the set of devices, one or more device characteristics; selecting, based at least in part on the one or more characteristics of each device of the plurality of devices configured to coordinate media playback, a primary device from among the plurality of devices configured to coordinate media playback; and transferring a media playback coordination task from the device to the primary device configured to coordinate media playback.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: means for receiving a request to initiate media playback on a set of devices connected to the device; means for, responsive to receiving the request, and while the device is coordinating media playback, determining, for each device of a plurality of devices configured to coordinate media playback and connected to the set of devices, one or more device characteristics; means for selecting, based at least in part on the one or more characteristics of each device of the plurality of devices configured to coordinate media playback, a primary device from among the plurality of devices configured to coordinate media playback; and means for transferring a media playback coordination task from the device to the primary device configured to coordinate media playback.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs including instructions for: receiving a request to initiate media playback on a set of devices connected to the device; in response to receiving the request, and while the device is coordinating media playback, determining, for each device of a plurality of devices configured to coordinate media playback and connected to the set of devices, one or more device characteristics; selecting, based at least in part on the one or more characteristics of each device of the plurality of devices configured to coordinate media playback, a primary device from among the plurality of devices configured to coordinate media playback; and transferring a media playback coordination task from the device to the primary device configured to coordinate media playback.
In accordance with some embodiments, a method is performed at a first device with a display. The method comprises: establishing a communication link with a second device; subsequent to establishing the communication link with the second device, initiating a configuration process for configuring the second device; during the configuration process: displaying, on the display, a configuration user interface that includes a prompt to select a location; receiving user input selection of a location; and in response to receiving the user input, configuring the second device to be associated with the location; detecting an audio tone signal indicative of a pairing handshake with the second device, wherein the audio tone signal is out-of-band to the communication link; and in accordance with detecting the audio tone signal, proceeding to a next step in the configuration process for configuring the second device.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, wherein the electronic device is a first device, the one or more programs including instructions for: establishing a communication link with a second device; subsequent to establishing the communication link with the second device, initiating a configuration process for configuring the second device; during the configuration process: displaying, on the display, a configuration user interface that includes a prompt to select a location; receiving user input selection of a location; and in response to receiving the user input, configuring the second device to be associated with the location; detecting an audio tone signal indicative of a pairing handshake with the second device, wherein the audio tone signal is out-of-band to the communication link; and in accordance with detecting the audio tone signal, proceeding to a next step in the configuration process for configuring the second device.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: establishing a communication link with a second device; subsequent to establishing the communication link with the second device, initiating a configuration process for configuring the second device; during the configuration process: displaying, on the display, a configuration user interface that includes a prompt to select a location; receiving user input selection of a location; and in response to receiving the user input, configuring the second device to be associated with the location; detecting an audio tone signal indicative of a pairing handshake with the second device, wherein the audio tone signal is out-of-band to the communication link; and in accordance with detecting the audio tone signal, proceeding to a next step in the configuration process for configuring the second device.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; means for establishing a communication link with a second device; subsequent to establishing the communication link with the second device, means for initiating a configuration process for configuring the second device; during the configuration process: means for displaying, on the display, a configuration user interface that includes a prompt to select a location; means for receiving user input selection of a location; and means for, responsive to receiving the user input, configuring the second device to be associated with the location; means for detecting an audio tone signal indicative of a pairing handshake with the second device, wherein the audio tone signal is out-of-band to the communication link; and in accordance with detecting the audio tone signal, means for proceeding to a next step in the configuration process for configuring the second device.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: establishing a communication link with a second device; subsequent to establishing the communication link with the second device, initiating a configuration process for configuring the second device; during the configuration process: displaying, on the display, a configuration user interface that includes a prompt to select a location; receiving user input selection of a location; and in response to receiving the user input, configuring the second device to be associated with the location; detecting an audio tone signal indicative of a pairing handshake with the second device, wherein the audio tone signal is out-of-band to the communication link; and in accordance with detecting the audio tone signal, proceeding to a next step in the configuration process for configuring the second device.
Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
Thus, devices are provided with faster, more efficient methods and interfaces for managing media playback devices, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for managing media playback devices.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
There is a need for electronic devices that provide efficient methods and interfaces for managing media playback devices. For example, methods and techniques for transferring playback between devices are described below. Such techniques can reduce the cognitive burden on a user who accesses event notifications, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
Below,
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the 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 (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are 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., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size 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 a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally 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 122 optionally controls access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), 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), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality 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 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a 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 actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone module 138 for use in location-based dialing; to camera module 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with 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 RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the 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, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this 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 are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include 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 (also called device attitude) of the device.
Event comparator 184 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 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700, 900, 1100, 1300, 1500, 1700, 1800, 2000, 2200, 2400, 2600, 2800, 3000, 3200, 3400, 3600, and 3800 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or 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 an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the 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 the 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 display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed in proximity of application icon 572B, as shown in
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to 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 hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
Electronic device 580 includes speaker 586 for outputting audio. Device 580 can include audio circuitry (e.g., in I/O section 594) that receives audio data, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 586. Speaker 586 converts the electrical signal to human-audible sound waves. The audio circuitry (e.g., in I/O section 594) also receives electrical signals converted by a microphone (e.g., input mechanism 588) from sound waves. The audio circuitry (e.g., in I/O section 594) converts the electrical signal to audio data. Audio data is, optionally, retrieved from and/or transmitted to memory 598 and/or RF circuitry (e.g., in communication unit 590) by I/O section 594.
Memory 598 of personal electronic device 580 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 596, for example, can cause the computer processors to perform the techniques described below, including processes 700, 900, 1100, 1300, 1500, 1700, 1800, 2000, 2200, 2400, 2600, 2800, 3000, 3200, 3400, 3600, and 3800 (
As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
As used herein, the terms “open application” or “executing application” refer to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application is, optionally, any one of the following types of applications:
As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
As shown in
As shown in
In this example, the set of devices named Living Room and represented by indicator 610F are currently playing back the media item titled “Heart Wave” by the artist “MKTS”, which are indicated inside of indicator 610F. In some embodiments, a media item is one or more of a song, a video, a podcast, an audio stream, a video stream, an audio file, a video file, an e-book (e.g., also referred to as an electronic book), a text document, a webpage, a phone call, a video call, or the like. Indicator 610G corresponds to the set of devices named or included in the set named “Bedroom”, which are currently playing back the song titled “Vibes” by artist “John Appleseed”. In some embodiments, an indicator for a set of devices (e.g., indicator 610F and 610G) is displayed (e.g., in a multi-device interface) even when the corresponding set of devices is not currently playing back media. In some embodiments, an indicator for a set of devices (e.g., indicator 610F and 610G) is displayed (e.g., in a multi-device interface) even when fewer than all devices in the corresponding set of devices are currently playing back media. For example, if the set of Living Room devices includes three devices (e.g., three smart speaker devices, such as device 580), and only one of the devices is currently playing a media item (e.g., “Heart Wave” by “MKTS”), the corresponding indicator in the multi-device interface still includes an identification of currently playing back media (e.g., “Heart Wave” by “MKTS” is displayed inside of indicator 610F for the device set “Living Room”).
In some embodiments, if individual devices of the set of devices are concurrently playing back different media items, the multi-device interface displays an indication that multiple media items are playing on the devices of a set of devices. For example, the multi-device interface can include a single indicator for the set (e.g., 610F) and an identification that multiple media items are being played back on those devices (e.g., “1 movie, 1 song”). For example, the multi-device interface can include two indicators (e.g., 610F) for the set and an identification of each respective media item being played back (e.g., an indicator like 610F for each media item, both identified as “Living Room”, or identified as “Living Room—Device 1” and “Living Room—Device 2”).
A set of devices can also be referred to as a set of “available playback devices”. In some embodiments, available playback devices include one or more (e.g., remote, external) devices on which a current device (e.g., device 600) can control or affect playback (e.g., using a multi-device interface such as 610). For example, as shown in
In some embodiments, one or more devices automatically detect another device. In some embodiments, the devices then form a network between themselves. For example, two devices (e.g., 580) can detect each other after booting up for the first time (e.g., straight out of the box, without configuration by a user), establish a connection link between themselves (e.g., and between device 600), and appear in a multi-device interface (e.g., with a name such as “Speaker 1”, and/or a location such as “No Location”). In some embodiments, the device (e.g., 580) is configured to part of a user's home (e.g., the home devices). One of skill in the art will appreciate that a variety of techniques can be used to interconnect and/or transmit information between devices (e.g., 580, 600), which are all intended to be within the scope of this disclosure, and thus additional details are not included here.
In
As shown in
As shown in
As shown in
In some embodiments, an indicator associated with a set of devices or an individual device includes an identification of a user who initiated playback of media on, respectively, the set of devices or the individual device. For example, with reference to
The multi-device interface 610 of
In some embodiments, in response to user input 616, the device 600 updates the display of the multi-device interface to “focus” (also referred to as “target”) the second media session. For example,
Switching between media sessions can be referred to as “retargeting”, “targeting”, “refocusing”, “focusing”, or the like. Thus, the selection of indicator 610F can be referred to as “focusing” the current device 600 or “focusing” the multi-device interface 610 on a set of devices or a media session.
As shown above with respect to
In
At
At
As shown in as shown in
As shown in as shown in
A user may desire to view the media status of the plurality of devices within their home at any time, even while viewing an interface for a non-media related application on their device. Thus, a technique for accessing a multi-device interface easily and quickly from any application executing on a device is described herein.
Turning to the figures,
In response to receiving the user input 652, device 600 displays message interface 654 in
In
As described above with respect to multi-device interface 610, multi-device interface 670 includes individual indicators representing available playback devices (e.g., devices in the user's home). Indicator 670D identifies the current device (named “Living Room Apple TV”) and includes the selection indicator 670K. In this example, selection indicator 670K includes a checkmark, which indicates that the device 670D is currently playing back the media of indicator 670B (e.g., is included in the currently-targeted media session). Indicator 670E identifies the set of devices named “Kitchen” and includes indicator 670L, which does not include a checkmark (e.g., the Kitchen set of devices is not currently playing back the media track “Heart Wave” by “MKTS”). Indicator 670E also includes an indication that the Kitchen set of devices are currently playing back other media. For example, in
While multi-device interface 670 is displayed, device 662 receives user input 672, as shown in
In response to a user input (e.g., swipe gesture), in some examples, the device updates multi-device interface 670A to focus on a different media session. As shown in
As shown in
In some examples, in response to user input 678 on a selected indicator corresponding to one or more devices, a volume control affordance is displayed. As shown in
As shown in
In some embodiments, a device (e.g., device 600) is configured to receive playback coordination responsibility from another device (e.g., device 580). For example, a device that is configured to receive or perform playback coordination responsibility (also referred to as a “hero device”) is a device that is configured to perform one or more of the following tasks: issue commands to one or more external devices to synchronize and/or control playback of media on the external devices; store a media item or a playback queue for playback; access a content stream from a remote location (e.g., an internet location); provide a content stream (e.g., of media) to one or more external devices for playback; and process playback control instructions for a media session (e.g., receive, process (e.g., de-duplicate redundant requests), and forward instructions to appropriate devices). In some embodiments, device 600 coordinates playback on a set of device. In some embodiments, the set of devices excludes the device 600. For example, if the set of devices does not include a device configured to be hero device, device 600 retains playback coordination responsibility. In some embodiments, device 600 transfers playback coordination responsibility to a device configured to be a hero device. For example, if the set of devices includes a device configured to be hero device, device 600 transfers playback coordination responsibility to that device (e.g., such as a device 580). Playback coordination responsibility is described in more detail below.
As described below, method 700 provides an intuitive way for accessing media playback status of a plurality of available playback devices. The method reduces the cognitive burden on a user when accessing media playback status of a plurality of available playback devices, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to access media playback status of a plurality of available playback devices faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 600) receives (702) a user input. For example, the device receives user input (e.g., 608A of
In response to receiving the user input, the electronic device (e.g., 600) displays (704), on the display, a multi-device interface (e.g., 610) that includes: one or more indicators (e.g., 610A, 610F, 610G) (706) associated with a plurality of available playback devices that are connected to the device (e.g., 600) and available to initiate playback of media from the device (e.g., 600), and a media playback status (e.g., as indicated by 610F and 610G) (708) of the plurality of available playback devices. In some examples, a media playback status includes one or more of: an indication of what is currently being played on the plurality of available playback devices. In some examples, the devices in the plurality of available playback devices are associated with a user, a user account, or a plurality of devices associated with a user. For example, the devices may be a collection of devices belonging to the user or designated as residing inside of a user's home. In some embodiments, an indicator of the one or more indicators can be associated with more than one available playback device. For example, devices that are currently playing the same content can be grouped and displayed as a single indicator (e.g., 610A of FIG. AB).
Displaying a multi-device interface that includes one or more indicators associated with a plurality of available playback devices that are connected to the device and available to initiate playback of media from the device, along with a media playback status of the plurality of available playback devices, provides the user with visual feedback about the state of a plurality of devices that are available for media playback. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
Additionally, displaying such a multi-device interface allows the user to collectively view a plurality of states for a plurality of available devices in one optimized interface. Providing an optimized interface to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, one or more devices are “connected” when data can be exchanged between the devices. For example, devices can be connected to a common Local Area Network (“LAN”) that enables data exchange between the devices. In some embodiments, one or more connected devices are connected directly. In some examples, a direct connection between two devices does not rely on an intermediate device between two directly connected devices. For example, a direct connection can be formed between a device that creates a Wi-Fi connection directly to a second device, without requiring an intermediate wireless access point (“WAP”) to facilitate the connection.
In some embodiments, one or more devices are connected indirectly. In some examples, an indirect connection between two devices includes (e.g., is routed through) an intermediate device between two connected devices. For example, an indirect connection can be formed between a device that is connected to a common wireless (e.g., Wi-Fi) connection through an intermediate WAP.
In some embodiments, one or more devices are “connected” by virtue of each being logged into (or otherwise associated with) the same user account. For example, a user may have two personal devices that are both logged into an account for a cloud-based service and thus are connected. For instance, the user's phone (e.g., an iPhone) and their tablet computer (e.g., an iPad) can both be logged into the user's iCloud account. In this example, the iPhone and the iPad can exchange data through the cloud-based service (e.g., a cloud server). In some embodiments, the device is connected to the available playback devices such that the device can initiate playback of media on one or more of the available playback devices. For example, an available playback device can begin playback of an media file (or stream), transfer playback (currently playing on the device) to the available device, or add the available device to concurrently play back of media a currently playing on the device).
In some embodiments, the user input (e.g., 608A of
In some embodiments, the user input (e.g., 608A of
In some embodiments, while the electronic device (e.g., 600) is playing back a first media item (e.g., represented by 610A of
In some embodiments, the browsing interface (e.g., 620) includes an affordance associated with a third media item (e.g., 620B), and the electronic device receives a sixth user input (e.g., 622) associated with the affordance associated with the third media item. In accordance with receiving the sixth user input, the electronic device displays, on the display, the multi-device interface. For example, after receiving a deep press on a media item (e.g., a song), the device displays the multi-device interface (e.g., 610 of
In some embodiments, the sixth user input (e.g., 622) is a press and hold. In some embodiments, in response to the sixth user input, the electronic device displays a menu (e.g., 624) with an affordance (e.g., 624A), selection of which causes the multi-device interface (e.g., 610) to be displayed.
In some embodiments, the sixth user input (e.g., 622) has a characteristic intensity. In accordance with a determination that the characteristic intensity of the sixth user input meets the intensity-dependent criteria, and subsequent to receiving the sixth user input, the electronic device (e.g., 600) displays, on the display (e.g., 602), the multi-device interface (e.g., 610). In some embodiments, in response to the sixth user input, the electronic device displays a menu (e.g., 624) with an affordance (e.g., 624A), selection of which causes the multi-device interface (e.g., 610) to be displayed. In accordance with a determination that the characteristic intensity of the sixth user input does not meet the intensity-dependent criteria, and subsequent to receiving the sixth user input: the electronic device forgoes displaying, on the display, the multi-device interface; and transmits an instruction to initiate playback of the third media item (e.g., 620B) on the set of playback devices that does not include the device (e.g., Living Room+Kitchen, as shown in
In some embodiments, to display the multi-device interface (e.g., 610), the electronic device (e.g., 600) concurrently displays, on the display (e.g., 602): a first region (e.g., 611A of
In some embodiments, the first region (e.g., 6611A) is visually overlaid on the second region (e.g., 611B, as shown in
In some embodiments, the electronic device (e.g., 600) receives selection (e.g., user input 634) of an indicator (e.g., 6610F of
In some embodiments, the user input (e.g., 608A or 608B) is a first user input, and prior to receiving the user input, the electronic device (e.g., 600) receives a seventh user input (e.g., 604 or 642). In response to receiving the seventh user input, the electronic device displays, on the display (e.g., 602), a playback control interface (e.g., 606A of
In some embodiments, the electronic device receives the first user input (e.g., 608A or 608B), and the first user input has an input characteristic. In some embodiments, an input characteristic is a characteristic intensity of an input. In some embodiments, an input characteristic is a length of time associated with an input. In some examples, a length of time associated with an input is a length of time that a touch input was continuously detected on a touch-sensitive surface (e.g., of device 600).
The electronic device (e.g., 600) determines whether the input characteristic meets an input characteristic-dependent criteria. In some embodiments, to determine whether the input characteristic meets an input characteristic-dependent criteria, the electronic determines whether the characteristic intensity meets an intensity-dependent criteria. For example, whether the characteristic input of the input is above a threshold intensity. In some embodiments, to determine whether the input characteristic meets an input characteristic-dependent criteria, electronic device determines whether the user input meets a time-based criteria. For example, whether the touch is detected (e.g., on a touch-sensitive surface associated with the electronic device) for a predetermined amount of time. Input characteristics and input characteristic dependent criteria other than those based on intensity or time can be used. In accordance with a determination that the input characteristic meets the input characteristic-dependent criteria, the device displays, on the display, the multi-device interface. In accordance with a determination that the input characteristic intensity does not meet the input characteristic-dependent criteria, the electronic device forgoes displaying, on the display, the multi-device interface. In some embodiments, further in accordance with a determination that the input characteristic intensity does not meet the input characteristic-dependent criteria, the electronic device determines a location associated with the first user input. In accordance with a determination that the location is associated with a playback control affordance (e.g., 606M of
In some embodiments, the seventh user input (e.g., 642) is received while displaying a user interface of an application executing on the device (e.g., 640 of
In some embodiments, the multi-device interface (e.g., 610 of
In some embodiments, the multi-device interface includes a plurality of individual volume control affordances (e.g., 610S, 610T, and 610U of
In some embodiments, the one or more indicators associated with the plurality of available playback devices includes (728): a first indicator (e.g., 670B of
In some embodiments, the electronic device (e.g., 660) displays (734) an indication (e.g., 670K) of whether each device of the plurality of available playback devices is currently playing back a media item associated with an indicator displayed in the first region.
In some embodiments, the electronic device (e.g., 660) receives an eleventh user input (e.g., 678) associated with an individual indicator (e.g., 670E of
In some embodiments, the electronic device (e.g., 600, 660) receives a twelfth user input representing a request to initiate media playback on the plurality of available devices. In response to receiving the twelfth user input: in accordance with a determination that the plurality of available devices includes at least one device configured to receive playback coordination responsibility, the electronic device transfers playback coordination responsibility to the at least one device of the plurality of devices. In accordance with a determination that the plurality of available devices does not include at least one device configured to receive playback coordination responsibility, the electronic device (e.g., 600, 660) coordinates the media playback on the plurality of devices.
In some embodiments, while the electronic device (e.g., 600 or 660) is coordinating the media playback on the plurality of devices, the electronic device receives a thirteenth user input representing a request to initiate a phone call on the device. For example, the device receives user input representing a request to answer a phone call or to place a phone call. In response to receiving the thirteenth user input representing the request to initiate the phone call, the electronic device: initiates the phone call; and continues coordinating the media playback on the plurality of devices during the phone call.
In some embodiments, further in response to receiving the twelfth user input, the electronic device (e.g., 600, 660) transmits data representing a playback queue to each of the devices in the plurality of devices.
In some embodiments, the electronic device (e.g., 600 or 660) receives a fourteenth user input representing a request to initiate media playback on the plurality of available devices, wherein the fourteenth user input is associated with a first user. In some examples, the electronic device determines that a user input is associated with the first user based on detected voice input, based on a device that sent the request, or the like. In response to receiving the fourteenth user input, in accordance with a determination that the first user is subject to a playback restriction, the electronic device (e.g., 600, 660) prevents the electronic device (e.g., 600, 660) from initiating media playback on the plurality of available devices in response to the eleventh user input. In accordance with a determination that the first user is not subject to the playback restriction, the electronic device allows the device to initiate media playback on the plurality of available devices in response to the eleventh user input.
In some embodiments, the electronic device (e.g., 600 or 660) receives (736) a fifteenth user input (e.g., 652 of
Note that details of the processes described above with respect to method 700 (e.g.,
In particular,
In response to receiving user input 812, device 800 displays an expanded version of indicator 810J, as shown in
At
At
In some examples, a notification prompt for taking over playback is displayed in response to user input 830. For example, in response to a user selecting an indicator for Kitchen device in
As described below, method 900 provides an intuitive way for configuring an electronic device to initiate playback on a plurality of available playback devices. The method reduces the cognitive burden on a user for configuring an electronic device to initiate playback on a plurality of available playback devices, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to configure an electronic device to initiate playback on a plurality of available playback devices faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 800) displays (902), on the display (e.g., 802), a first current media interface (e.g., 804 of
In some embodiments, the electronic device (e.g., 800) is currently playing the first media item. For example, the first current media interface is a “Now Playing” interface. In some embodiments, the representation of the first media item available for playback on the device is selectable (e.g., is an affordance), and can be selected to initiate playback of the first media item on the electronic device. For example, the first current media interface is a browsing interface that allows browsing of one or more media items (e.g., the first media item) while a media application on the electronic device (e.g., or the electronic device itself) is targeting the electronic device. In some embodiments, selection of a media item (e.g., the first media item) while the music application is targeted to a device causes playback of the media item to initiate on the targeted device in response.
In some embodiments, selection of a playback device selection affordance (e.g., 804E) allows one or more available playback devices to be selected. In some embodiments, the available playback devices include the electronic device. Selection of one or more available playback devices may be referred to as “targeting”, “retargeting”, “focusing”, “refocusing” a media application or the electronic device, as described above. For example, a media application or device can be targeted to three discrete devices: the electronic device and two external speakers connected to the device via a wireless connection. In this example, while targeted to the three discrete devices in this example, a media item is selected for playback, and playback is initiated on the three discrete devices.
The electronic device (e.g., 800) receives (908) a first user input (e.g., 806 of
In response to receiving the first user input (e.g., 806), the electronic device (e.g., 800) displays (910), on the display (e.g., 802), one or more affordances (e.g., affordances 804B-804K) associated with a plurality of available playback devices (e.g., the device sets iPhone, Bedroom, Kitchen, and/or Living Room of
Displaying one or more affordances associated with a plurality of available playback devices connected to the device provides the user with visual feedback about the state of a plurality of devices that are available for media playback. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
Displaying one or more affordances associated with a plurality of available playback devices connected to the device allows the user to collectively view a plurality of states for a plurality of available devices in one optimized interface. Providing an optimized interface to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
The electronic device (e.g., 800) receives (912) a second user input (e.g., 812 of
In response to receiving the second user input (e.g., 812), the electronic device (e.g., 800) configures (914) the device to initiate playback on the plurality of available playback devices (e.g., the devices in the set “Kitchen+Living Room” represented by affordance 810J of
Configuring a device to initiate playback on the plurality of available playback devices allows the user to collectively control a plurality of available devices in one optimized interface. Providing an optimized interface to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, configuring the device to initiate playback on the plurality of available playback devices comprises transmitting (916) an instruction to the available playback devices to initiate playback (e.g., the devices in the set “Kitchen+Living Room” represented by affordance 810J of
In some embodiments, while the electronic device (e.g., 800) is configured to initiate playback on the plurality of available playback devices (e.g., devices represented by affordances 804D and 804E of
In some embodiments, the first current media interface (e.g., 804 of
In some embodiments, the one or more affordances (e.g., 810J of
In some embodiments, the information identifying the media currently being played back by the plurality of available playback devices includes one or more of: a song title, an artist, a movie title, an episode name, and a URL (e.g., “Heart Wave” by “MKTS” as indicated by indicator 810J of
In some embodiments, while the electronic device (e.g., 800) is configured to initiate playback on the plurality of available playback devices (e.g., the device set “Kitchen+Living Room” represented by indicator 810J of
In some embodiments, the electronic device (e.g., 800) determines (926) that the plurality of available playback devices (e.g., the device set Kitchen and the device set Living Room respectively corresponding to indicators 810D and 810E of
In some embodiments, further in response to receiving the second user input (936) (e.g., 812 of
In some embodiments, a media item includes (938) one or more of audio data, video data, or both.
Note that details of the processes described above with respect to method 900 (e.g.,
As shown in
In some embodiments, the first device repeats the audio tone signal until it receives a confirmation that the second device detected the audio tone signal. For example, device 1000 can repeat output of audio tone signal 1014 until receiving confirmation that device 1010 detected the signal 1014. For example, the confirmation can be a response tone (e.g., second audio tone signal 1016; “out-of-band”) or a communication over the communication link (e.g., Bluetooth, Wi-Fi, or the like; “in-band”) between the two devices.
In some embodiments, the first device repeats the audio tone signal for a predetermined number of times. In some embodiments, the first device repeats the audio tone signal for a predetermined number of times or until a confirmation that the second device detected the audio tone signal is received, whichever comes first. For example, device 1000 can repeat the audio tone signal 1014 three times before it ceases repeating the tone, if no confirmation is received (e.g., response tone signal 1016).
In some embodiments, the first device outputs a dictated audio passcode. As shown in
In some embodiments, device 1000 outputs encoded data visually. For example, LED indicators (e.g., 1006A-1006B) can be used to output a pattern or sequence of light emission that is detectable by another device (e.g., 1010) and that includes or otherwise represents data information. The other device can, for example, capture or record the light pattern and decode the data, or transmit the captured data back to the device to verify that the other device observed the light pattern.
In some embodiments, during a configuration process, configuration data is received and stored by device 1000. Examples of configuration data include, but are not limited to, one or more of: whether a device (e.g., 1000 or 1010) is a member of a group of devices (e.g., home devices, or a stereo pair), a name or identifier of the device, a user associated with the device, a location (e.g., a room name) of the device, user account credentials (e.g., for network or cloud-based services such as iCloud, iTunes, Apple Music, Spotify, or the like). Configuration data for device 1000 can also be added or edited in a home control application (e.g., as shown in
In some embodiments, the first device is configured to be included in a group of devices.
In some embodiments, a group of devices (e.g., as shown in
In some embodiments, a group of devices (e.g., as shown in
In some embodiments, device 1000 receives a configuration setting of a permission level that sets a permission condition that another device (e.g., 1010) must meet in order to control the first device. For example, the condition can be that the other device must be connected to the same network (e.g., Wi-Fi network). For further example, the condition can be that the other device is in close proximity. In some examples, the condition is satisfied by either one of these example conditions. In some embodiments, the user can change the configuration setting of a permission level. In some embodiments, the user can remove the configuration setting of a permission level (e.g., any device within a communication range can control device 1000).
In some embodiments, synchronized audio tone signals are harmonics. Thus, in some examples, the synchronized audio tone signals are the same audio frequency. For example, audio tone signal 1042 has a frequency of 2000 Hertz, while audio tone signal 1044 has a frequency of 2000 Hertz. In some examples, audio frequency of one of the synchronized audio tone signals is an integer multiple of the audio frequency of the other frequency. For example, audio tone signal 1042 has a frequency of 1000 Hertz, while audio tone signal 1044 has a frequency of 2000 Hertz.
In some embodiments, synchronized audio tone signals are each a different frequency of a musical chord or a musical scale. Thus, for example, the synchronized tones sound (e.g., to a user) like they are in harmony.
In some embodiments, subsequent synchronized audio tone signals have a different audio frequency. For example, to indicate that the configuration process is progressing, the synchronized audio tone signals can increase (e.g., step up) in frequency at each subsequent step in a configuration process. In the example shown in
Turning now to
As described below, method 1100 provides an intuitive way for configuring a first device using a second device. The method reduces the cognitive burden on a user for configuring a first device using a second device, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to configure a first device using a second device faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 1000) detects (1102) an indication that a physical proximity between the electronic device (e.g., 1000 of
In accordance with detecting the indication, the electronic device audibly outputs (1104) an audio tone signal (e.g., 1014), wherein the audio tone signal is out-of-band to the communication link (e.g., 1039). For example, the device is a speaker that plays a tone. In some examples the tone is a proximity handshake tone at the beginning of a configuration process. In some examples the tone is played by the speaker during the configuration process (e.g., after it begins). In some embodiments, being out-of-band to a communication link means that a signal (e.g., an audio tone signal) is not communicated using the same data exchange technique.
Using a detection of physical proximity allows the user to efficiently move through a configuration process for a device with fewer required user inputs. Providing an optimized configuration process to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
Subsequent to outputting the audio tone signal (e.g., 1014), the electronic device (e.g., 1000) determines (1106) whether a response audio tone signal (e.g., 1016) from the second device (e.g., 1010) has been received.
In accordance with a determination that the response audio tone signal (e.g., 1016) from the second device (e.g., 1010) has been received, the electronic device (e.g., 1000) proceeds (1108) to a next step in a configuration process. In some embodiments, a configuration process includes receiving one or more configuration settings for the electronic device. In some examples, configuration settings include one or more of: a location (e.g., room name) of the electronic device, a device identifier (e.g., a name), whether the electronic device is a member of a group of devices (e.g., a left or right channel of a stereo pair of speakers), user account credentials (e.g., allowing the electronic device to log into a cloud-based service), audio output preferences (e.g., language, volume), content restrictions (e.g., parental controls), or the like.
Proceeding to a next step in a configuration process in accordance with a determination that a response audio tone signal has been received allows the user to efficiently move through a configuration process for a device with fewer required user inputs. Providing an optimized configuration process to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In accordance with a determination that the response audio tone signal from the second device has not been received, the electronic device (e.g., 1000) forgoes (1110) proceeding to the next step in the configuration process. For example, if the device does not detect a response audio tone signal (e.g., 1016) within a threshold amount of time after outputting an audio tone signal, the device can timeout (e.g., stop listening for a response audio tone signal), can repeat the tone, or dictate an audio passcode aloud.
In some embodiments, the response audio tone signal (e.g., 1016) represents (1112) an indication that the audio tone signal (e.g., 1014) was detected by the second device (e.g., 1010).
In some embodiments, at least one of the audio tone signal (e.g., 1014) and the response audio tone signal (e.g., 1016) comprises (1114) encoded data. In some embodiments, the encoded data comprises an indication of the outputting device's identity. For example, the encoded data can include an audible representation of data sent from one device to the other. Audibly outputting the data from one device such that the other device can detect it (e.g., using a microphone) can provide sufficient indication that the second device and the electronic device are within a relative close physical proximity to each other. In some embodiments, the encoded data includes user account credentials. For example, the encoded data can include data representing user account information for a cloud-based service (e.g., iCloud login information), a media streaming service (e.g., Apple Music), or data for confirming that the electronic device (e.g., 1000) should be provided access to the user's account or personal data.
In some embodiments, the response audio tone signal (e.g., 1016) comprises encoded data, and further in accordance with a determination that the response audio tone signal from the second device (e.g., 1010) has been received (1116), the electronic device (e.g., 1000) converts (1118) the encoded data, of the response audio tone signal, into decoded data. In some embodiments, the electronic device (e.g., 1000) uses (1120) at least a portion of the decoded data to log in to a user account of a cloud-based service. For example, if the encoded data includes login credentials for a cloud-based service (e.g., iCloud) the electronic device decodes the encoded data into an account user name and/or password, and logs into the cloud-based service.
In some embodiments, the response audio tone signal (e.g., 1016) comprises data that confirms the identity of the second device (e.g., 1010). For example, the data that is encoded can be data that was transmitted to the second device that is played back as a tone, or can be a unique identifier associated with the second device.
In some embodiments, the electronic device (e.g., 1000) includes a memory, and the electronic device receives (1122) one or more configuration settings from the second device (e.g., 1010). In response to receiving the one or more configuration settings, the electronic device stores (1124) the configuration settings in the memory of the electronic device. In some examples, configuration settings include one or more of the settings as described above.
In some embodiments, the one or more configuration settings includes a location identifier representing a physical location of the electronic device (e.g., 1000). For example, a location identifier can include a room identifier such as “Living Room”, “Bedroom”, “Bedroom 2”, “Kitchen”, “Tim's Room”, or the like. In some embodiments, the location identifier is associated with the electronic device (e.g., 1000) and communicated to other devices (e.g., 1010). For example, the identifier can be used in a multi-device interface (e.g., 610 of
In some embodiments, the one or more configuration settings includes (1126) an indication that the electronic device (e.g., 1000) is included in a device group (e.g., a group comprised of device 1000 and 1020 of
In some embodiments, the first device (e.g., 1000) and the second device (e.g., 1010) are connected (1128) to a local area network via an access point (e.g., 1030). In some embodiments, the electronic device (e.g., 1000) establishes a communication link (e.g., 1032) to the third device (e.g., 1020 of
In some embodiments, to audibly output the audio tone signal (1132), the electronic device (e.g., 1000) audibly outputs (1134) the audio tone signal (e.g., 1014), and determines (1136) whether the second device (e.g., 1010) detected the audio tone signal. In some embodiments, determining whether the second device detected the audio tone signal includes determining whether data is received over the communication link (e.g., 1038) representing confirmation that the second device (e.g., 1010) detected the audio tone signal (e.g., 1014). In some embodiments, the electronic device receives (e.g., detects) a response audio tone signal (e.g., 1016) from the second device (e.g., 1010) representing confirmation that the second device detected the audio tone signal (e.g., 1014). In accordance with a determination that the second device (e.g., 1010) did not detect the audio tone signal (e.g., 1014), the electronic device (e.g., 1000) repeats (1138) audibly outputting the audio tone signal (e.g., 1014). For example, the electronic device plays the tone (e.g., 1014) a second time (or an nth time). In accordance with a determination that the second device detected the audio tone signal, the electronic device forgoes (1140) repeating audibly outputting the audio tone signal.
In some embodiments, further in accordance with a determination that the second device (e.g., 1010) did not detect the audio tone signal (e.g., 1014), the electronic device (e.g., 1000) determines (1142) whether the audio tone signal has been audibly outputted a threshold number of times. In accordance with a determination that the audio tone signal has been audibly outputted a threshold number of times, the electronic device (e.g., 1000) audibly outputs (1144) a dictated passcode (e.g., 1018 of
In some embodiments, the audio tone signal (e.g., 1014) is a first audio tone signal, and in response to progressing from a first step in the configuration process to a second step in the configuration process, the electronic device (e.g., 1000) outputs a second audio tone signal (e.g., 1042 of
In some embodiments, in response to progressing from the second step in the configuration process to a third step in the configuration process, the electronic device (e.g., 1000) outputs a fourth audio tone signal (e.g., 1046 of
In some embodiments, subsequent to proceeding to the next step in the configuration process, the electronic device (e.g., 1000 or 1906) outputs an audible voice prompt by a voice assistant prompting a user to provide user voice input invoking one or more functions of the voice assistant (e.g., as shown in
Outputting an audible voice prompt by a voice assistant prompting a user to provide user voice input invoking one or more functions of the voice assistant provides the user with information regarding the capabilities and state of a device. Providing such information to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the audible voice prompt is a prompt to provide a command for performing the first function (e.g., a music function) of the voice assistant, and the user voice input is a command to perform the first function of the voice assistant (e.g., “Hey, play some music”). For example, the prompt relates to the same function as the received command.
In some embodiments, the audible voice prompt is a prompt to provide a command for performing a second function (e.g., a weather function) of the voice assistant, and the user voice input is a command to perform the first function (e.g., a music function) of the voice assistant, different than the second function. For example, the prompt relates to a different function as the received command, but the device 1000 performs the respective action anyway. Thus, device 1000 can output the voice prompt “Now you try, say ‘Hey, tell me the news,’” but perform a music function if the user responds with the voice command “Hey, play some music.”
In some embodiments, in accordance with performing the first function, the electronic device (e.g., 1000 or 1906) transmits data related to the first function to the second device (e.g., device 1010 or 1900).
In some embodiments, the electronic device (e.g., 1000 or 1906) receives, from the second device, a configuration setting of a permission level that sets a permission condition that another device must meet in order to control the first device. In some embodiments, the permission condition is that the other device and the first device must be connected to the same local area network. In some embodiments, the permission condition is that the other device and the first device are within a threshold physical proximity.
In some embodiments, prior to establishing the communication link connecting the first device (e.g., 1000 or 1906) and the second device (e.g., 1010 or 1900) the electronic device (e.g., 1000 or 1906) detects an indication that a physical proximity between the first device and the second device satisfies a proximity condition. In response to detecting the indication that the physical proximity between the first device and the second device satisfies the proximity condition, the electronic device (e.g., 1000 or 1906) outputs an audio tone signal. In some embodiments, both the first and second devices (e.g., 1000 and 1010) play tones in response to satisfying the proximity condition.
Using an indication that the physical proximity between the first device and the second device satisfies the proximity condition in order to output an audio tone signal provides the user with auditory feedback regarding the state of the first device. For example, when there are other potential devices in proximity that are configurable, the audio tone signal can indicate which device will be configured. Providing improved feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
Note that details of the processes described above with respect to method 1100 (e.g.,
As described above (e.g., with respect to
In some examples, the satisfaction of a proximity condition between two devices can be used as an indication that a user (e.g., of one of the devices, a mobile device) would like to transfer media playback to or from one device (e.g., the mobile device) to the other device (e.g., a stationary smart speaker). Exemplary techniques are described below.
It is noted that
In the example shown in
At
At
In some examples, current media interface is displayed on lock screen of device 1200. For example, the proximity card 1208 can be displayed while the device 1200 was locked and, while remaining locked, the device receives user input that causes the device to initiate playback of media and update the lock screen (e.g., to display interface 1212).
In the example shown in
As shown in
In some embodiments, a proximity card is displayed concurrently with a current media interface. In some embodiments, display of a proximity card replaces display of a portion of a current media interface. For example,
At
Proximity card 1230 includes an identifier 1230A that indicates the current focus of the proximity card (e.g., Kitchen Speaker), a media identifier 1230B identifying a media item currently being played back by the targeted device (e.g., the song “Same Thing” by “Jambug”), and playback control affordances 1230C for controlling playback of the current media session.
At
At
In some examples, media information interface 1236 is displayed in response to device 1200 being placed (e.g., briefly or continuously) in close proximity with device 1202. Thus, because media information interface 1236 displayed in response to the device being placed in close proximity, it is also referred to as a “proximity card” or specifically a “media proximity card”.
In the example shown in
In some examples, device 1200 requires that the proximity card 1236 be held at the push position for a threshold amount of time before performing an action in response. In some examples, device 1200 provides a visual indication of the progress toward satisfying the threshold amount of time. For example,
In response to the user input 1238, device 1200 performs an action in response. In some embodiments, the device 1200 “pushes” media playback onto the device 1202. In some examples, device 1200 initiates playback of the media item represented by proximity card 1236 on device 1202 (e.g., transmits an instruction to device 1202 in response to user input 1238). In some examples, playback on device 1200 ceases in response to user input 1238.
In accordance with some embodiments, media content is automatically transferred from a first device to a second device if the devices are in close proximity for a length of time greater than a threshold length of time. For example, if device 1200 is placed in close proximity to device 1202 for longer than a threshold length of time (e.g., 5 seconds), device 1200 can automatically (e.g., without further user input) transfer playback of media to device 1202. This can be referred to as “automatic push” or “auto-push”. In accordance with some embodiments, media content is automatically transferred from a second device to a first device if the devices are in close proximity for a length of time greater than a threshold length of time. For example, if device 1200 is placed in close proximity to device 1202 for longer than a threshold length of time (e.g., 5 seconds), device 1202 can automatically (e.g., without further user input) transfer playback of media to device 1200. This can be referred to as “automatic pull” or “auto-pull”. When a user places a device in close proximity to another device for an extended period of time, this can be a strong indication that the user wishes playback to transfer between the devices. For example, a user can place their smartphone next to their smart speaker (e.g., 580) after entering their home and have what they were listening to on headphones begin playing on their home sound system, without further input at any device. Thus, by automatically pushing or pulling content from a personal electronic device, the number of user inputs for transferring media playback is reduced.
In the example shown in
In some examples, device 1200 requires that the proximity card 1242 be held at the pull position for a threshold amount of time before performing an action in response. In some examples, device 1200 provides a visual indication of the progress toward satisfying the threshold amount of time. For example, at
In response to the user input 1242, device 1200 performs an action in response. In some embodiments, the device 1200 “pulls” media playback onto the device 1200. In some embodiments, pulling playback includes initiating playback on the current device (e.g., 1200) and ceasing playback on the external device (e.g., 1202). In some embodiments, pulling playback includes initiating playback on the current device (e.g., 1200) and continuing playback on the external device (e.g., 1202).
In some examples, device 1200 initiates playback of the media item represented by proximity card 1242. In some examples, playback on device 1202 ceases in response to user input 1242 or in response to device 1200 initiating playback.
In some examples, if device 1200 is associated with a personal listening device (e.g., headphones), device 1200 automatically pulls the media playback from device 1202 and initiates the playback on the personal listening device. For example, as shown in the current media interface 1246 of
For example,
Further, in the example depicted in
One of skill in the art would appreciate the numerous possible combinations of devices (e.g., two or more) that can be used to create an integrated media playback experience as described herein (e.g., with respect to
For example,
As one of skill in the art would appreciate, a phone call involves both audio output and audio input (e.g., using a microphone). In some embodiments, transferring a media item (e.g., a phone call or a video call) from one device to another device comprises transferring media output (e.g., audio or video output), but not transferring a media input function (e.g., audio or video input). For example, in the example depicted in
It should be apparent to one of skill in the art that the various interfaces and techniques described herein (e.g., with respect to
In certain situations, the owner of a device may not desire to allow any user that has physical access to a device to be able to control the device. For example, it may not be desirable to allow guests (e.g., via the guests' devices) to control playback on the owner's home device.
Proximity card 1266 includes the title 1266A “Kitchen Speaker”, visually indicating the name of the device (e.g., device 1202) that is the target of the proximity card (e.g., whose media playback information is presented on the card). Additionally, proximity card 1266 includes a media affordance 1266B representing media content (e.g., one or more media items). In this example, media affordance 1266B includes album art for the track titled “How Many Times” by the artist “Jambug” (e.g., that is currently playing on device 1202). In some examples, media affordance 1266B includes other types of visual indications of one or more media items (e.g., text, images, or other appropriate visual representations). In this example, the media content represented (e.g., by affordance 1266B) by the proximity card 1266 is content that is currently playing on the device 1202 (e.g., the Kitchen Speaker). Proximity card 1266 also includes a textual identification 1266C of the currently playing media. Thus, proximity card 1266 provides an informational interface that allows a guest to view information about media playback on a device in close proximity, without being able to affect the playback. For example, a swipe on proximity card 1266 will not push or pull media playback to device 1200.
As described below, method 1300 provides an intuitive way for displaying a media information interface. The method reduces the cognitive burden on a user for displaying a media information interface, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to display a media information interface faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 1200) detects (1302), while connected to a second device (e.g., 1202), an indication that a physical proximity between the first device and the second device satisfies a proximity condition. For example, the devices are connected when the second device is in Bluetooth range of the first device, or is connected to the same Wi-Fi network as the first device. In some examples, the proximity condition is satisfied when a physical proximity of the electronic device (e.g., 1200) is within a proximity zone of the second device (e.g., such as proximity zone 1204 of
In accordance with detecting that the physical proximity satisfies the proximity condition (e.g., the electronic device is within the proximity zone 1204 of
Using a detection of physical proximity for displaying a media information interface allows the user to efficiently invoke a device-specific user interface with fewer required user inputs. Performing an operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the indication is detected while the first device (e.g., 1200) is not playing media content and while the second device (e.g., 1202) is not playing media content. In some embodiments, displaying the media information interface (e.g., 1208) comprises displaying (1306), on the display (e.g., 1206), a first affordance (e.g., 1208A) representing a first media item that was recently played on the second device. In some embodiments, the electronic device (e.g., 1200) receives (1308) a first user input (e.g., 1210) representing selection of the first affordance. In response to receiving the first user input (e.g., 1210), the electronic device (e.g., 1200) transmits (1310) an instruction to the second device (e.g., 1202) to initiate playback of the first media item.
In some embodiments, the electronic device (e.g., 1200) receives (1312) a second user input (e.g., 1214 of
In some embodiments, the indication is detected while the first device (e.g., 1200) is playing a third media item (e.g., 1220A of
In some embodiments, further in response to receiving the third user input (e.g., 1226), the electronic device (e.g., 1200) ceases playing (1322) the third media item (e.g., 1220A) on the first device (e.g., 1200).
In some embodiments, further in response to receiving the third user input (e.g., 1226), the electronic device (e.g., 1200) displays (1324), on the display, playback control affordances (e.g., 1228B of
In some embodiments, the indication is detected while the first device (e.g., 1200) is playing a fifth media item (e.g., 1220A of
In some embodiments, the first device (e.g., 1200) ceases playback of the fifth media item at a playback time (e.g., as illustrated by 1220D of
In some embodiments, displaying the media information interface comprises displaying, on the display (e.g., 1206), a fifth affordance (e.g., 1220C of
In some embodiments, the indication is detected while the first device (e.g., 1200) is not playing media content and while the second device (e.g., 1202) is playing a sixth media item (e.g., represented by 1242B of
In some embodiments, the electronic device (e.g., 1200) determines (1362) whether the fifth user input (e.g., 1248 of
In some embodiments, the second device (e.g., 1202) ceases playback of the sixth media item (e.g., represented by 1246A of
In some embodiments, initiating playback, on the first device (e.g., 1200), of the sixth media item (e.g., represented by 1246A of
In some embodiments, the first device (e.g., 1200) is connected to a plurality of devices, wherein the plurality of devices includes the second device (e.g., 1202), and wherein the displayed media information interface (e.g., 1208, 1224, 1236, or 1242) corresponds to the second device (e.g., 1202).
In some embodiments, the first device (e.g., 1200) is connected to the second device (e.g., 1202) via a wireless communication link.
In some embodiments, the media information interface (e.g., 1236, or 1242) comprises an indication (e.g., 1236B, 1236D, 1242C, and/or 1242D) that the media content playing back on the first device (e.g., 1200) or the second device (e.g., 1202) can be transferred to the other device not playing back the media content. For example, proximity cards can include an indication (e.g., text, an arrow) that the media content can be “pushed” to the second device (e.g., an up arrow) or “pulled” from the second device (e.g., down arrow).
In some embodiments, a media item is selected from the group consisting of an audio file, an audio stream, a video file, a video stream, a phone call, and a video call.
In some embodiments, the first device (e.g., 1200) is associated with a first user account (e.g., user 602A of
In some embodiments, in accordance with a determination (e.g., by device 1200 or 1202) that the physical proximity between the first device (e.g., 1200) and the second device (e.g., 1202) has satisfied the proximity condition continuously for a threshold amount of time, the first device automatically transfers (1372) playback of a media item between the first device and the second device. In some embodiments, automatically transferring comprises transferring without further user input and/or without requiring an additional condition be met. In some embodiments, in accordance with a determination that the physical proximity between the first device and the second device has not satisfied the proximity condition continuously for a threshold amount of time, the electronic device (e.g., 1200) forgoes automatically transferring (1374) playback of a media item between the first device and the second device.
Note that details of the processes described above with respect to method 1300 (e.g.,
At
In some embodiments, the “+” and “−” indicators 1406A and 1406B cease to be displayed in response to device 1400 performing a voice assistant function. For example, in response to detecting voice user input (e.g., “Hey Siri”), the device can cease displaying one or more of the icons within indicator 1406A and 1406B. In some examples, the illumination of one or more of indicators 1404, 1406A, and 1406B changes during a voice assistant function. For example, indicators 1404, 1406A, and 1406B can turn off, be illuminated, change color, or the like in response to a voice assistant function being performed on device 1400.
In response to receiving user input 1410, device 1400 adjusts a volume of device 1400. For example, as illustrated by the volume level meter 1412 in
At
In some embodiments, further in response to receiving user input 1416 on an indicator 1406A, device 1400 temporarily expands the touch-sensitive region 1414A to form an expanded touch-sensitive region (also referred to as an “expanded region”). An exemplary expanded region 1418 is shown in
In some embodiments, the device ceases to maintain the expanded touch-sensitive region after a predetermined amount of time. In some embodiments, the device ceases to maintain the expanded touch-sensitive region after a predetermined amount of time since the last user input within the expanded region. For example, subsequent user inputs (e.g., taps) within the expanded region would cause a measure (e.g., a timer) of the amount of time since the last user input to be reset after each detect touch input. In this example, the expanded region returns to its normal size (e.g., 1414A) after the amount of time reaches the predetermined amount of time after the final user input with the expanded region.
At
In some examples, in accordance with a determination that the second user input (e.g., 1420) was not received during the predetermined amount of time after detecting the first touch, device 1400 ceases playing media. For example, if user input 1420 was received after a predetermined amount of time after a touch that caused the region 1414A to expand (or a subsequent touch within the expanded region 1418), and was not within the region 1414A, then the volume is not increased because the temporary expansion (e.g., increase in responsive area on a touch-sensitive surface) ended before the user input 1420 was received. In some examples, device 1400 ceases playback in response to user input 1420, when it is received after the predetermined amount of time, and is outside of the second region. For instance, in the example shown in
In some embodiments, device 1400 includes a plurality of volume levels. For example, device 1400 can maintain e.g., store in memory) a volume level for a media playback function, and maintain a volume level for a voice assistant function. In some examples, the plurality of volume levels are each different. For example, device 1400 can adjust a first volume level (e.g., of media playback) to 0% of maximum (e.g., muted, no sound is produced by a speaker of device 1400) while a second volume level is set to a non-zero value of 50% of maximum (e.g., a maximum output level of the speaker, or a maximum level of a volume level meter).
For example,
In some embodiments, a second volume level is a derivative of a first volume level. For example, the volume level of a voice assistant (e.g., represented by volume meter 1432) can be mathematically derived from the volume level of media playback volume. For example, Volume (voice assistant)=(Volume (media)÷1.5). Thus, the second volume level (e.g., of the voice assistant) is derived from a first volume level (e.g., of media playback), and adjustment of the first results in an adjustment of the second.
In some embodiments, a second volume level is non-zero when a first volume level is zero. For example, as shown in
In some embodiments, user input on touch-sensitive surface 1402 causes device 1400 to change playback of currently playing media. For example, user input on touch-sensitive surface 1402 can cause device 1400 to skip to next media item (e.g., on a playlist), to go back to a previous media item (e.g., on a playlist), pause playback, or the like. In some embodiments, device 1400 concurrently plays back a plurality of media items. In some embodiments, in response to user input on touch-sensitive-surface 1402, device 1400 adjusts the output of each of the plurality of concurrently playing media items. In some embodiments, each of the plurality of media items are adjusted differently. For example, if device 1400 is concurrently playing back first media representing a news program (e.g., an audio stream) and second media representing music (e.g., an audio stream), a user input (e.g., a swipe gesture, a rotational swipe, a multi-contact swipe, or the like) on surface 1402 causes device 1400 to adjust an output level of the first and second media. In some embodiments, the adjustment is relative. For example, an output level of the first media is adjusted higher while an output level of the second media is adjusted lower. For example, an output level of the first media is adjusted lower while an output level of the second media is adjusted higher. For example, if the user desires to increase the volume of the news program and lower the music volume, a counter-clockwise rotational swipe gesture on surface 1402 causes device 1400 to adjust the volume of each media item accordingly. Conversely, in this example, a clockwise rotational swipe gesture on surface 1402 causes device 1400 to increase the volume of the music and lower the volume of the news program. Thus, device 1400 receives user input to control a crossfade between a plurality of currently playing media signals.
In some embodiments, device 1400 includes one or more microphones. In some examples, device 1400 detects, with the one or more microphones, a voice command user input from a voice command source. In some embodiments, the voice command source is moving. For example, the voice command source is a user that is speaking to the device, and the user may move (e.g., walk around a room) relative to the device (e.g., stationary in the room). In some embodiments, while continuing to detect the voice command user input: device 1400 determines a plurality of spatial positions of the moving voice command source, and illuminates light-emitting elements (e.g., indicators 1404) based on the plurality of spatial positions of the moving voice command source. Thus, for example, device 1400 can use (e.g., selectively illuminate) indicators 1404 based on the direction of a voice command source (e.g., a user speaking to device 1400 to invoke a voice assistant function using device 1400). For instance, when a user stands at a first position relative to device 1400 (e.g., and speaks a command to the device), indicators 1404 include one or more illuminated LEDs that visually appear to align with or indicate (e.g., “point in”) the direction of the first position. Likewise, when a user stands at a second position relative to device 1400 (e.g., and speaks a command to the device), different than the first position, indicators 1404 include one or more illuminated LEDs that visually appear to align with or indicate (e.g., “point in”) the direction of the second position.
In some embodiments, device 1400 detects a plurality of voice sources. In some embodiments, the device determines that one voice source, of the plurality of voice sources, represents a voice command user input. In some embodiments, device 1400 illuminates light-emitting elements (e.g., indicators 1404) based on the one voice source, of the plurality of voice sources. For example, if device 1400 is placed in a room with a plurality of speaking users and one user (or more than one) utters a voice command, the device 1400 uses indicators 1404 to visually indicate the direction of the user whose voice is currently being used to generate and/or process a voice command.
In
In
In some examples, other appropriate types of visual patterns can be used to indicate direction of a voice command source, and the examples above are not intended to limit the scope of this disclosure.
In some examples, the color elements in indicator 1404, as described above with respect to patterns 1454J-1454L, are used to provide visual indication that the device 1400 is performing a first function (e.g., a voice assistant function), in contrast to a second function (e.g., media playback). For example, monochromatic light can be output by indicator 1404 when device 1400 is only playback media (e.g., a song), but transition to color when the device (e.g., even while continuing media playback) begins performing a voice assistant-related function (e.g., detects voice input of a token phrase, such as “Hey Siri”).
As described below, method 1500 provides an intuitive way for controlling media playback. The method reduces the cognitive burden on a user for controlling media playback, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to control media playback faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 1400) detects (1502) a touch (e.g., 1408 or 1410) on the touch-sensitive surface (e.g., 1402). In response to detecting the touch on the touch-sensitive surface, the electronic device (e.g., 1400) determines (1504) whether the electronic device (e.g., 1400) is currently playing media (e.g., represented by 1410 of
In accordance with a determination that the device (e.g., 1400) is currently playing media (1506): the electronic device (e.g., 1400) determines (1508) whether a location of the touch (e.g., 1408 or 1410) is within a first area (e.g., 1414C of the touch-sensitive surface (e.g., 1402) or within a second area (e.g., 1414A) of the touch-sensitive surface, wherein the first area and the second area are non-overlapping.
In accordance with a determination that the location of the touch is within the first area (e.g., 1414C) of the touch-sensitive surface, the electronic device (e.g., 1400) ceases playing media (1510).
In accordance with a determination that the location of the touch is within the second area (e.g., 1414A) of the touch-sensitive surface, the electronic device (e.g., 1400) adjusts (1512) a volume of the currently playing media (e.g., adjust up or down).
In accordance with a determination that the device is not currently playing media, the electronic device (e.g., 1400) initiates playback of media (1514).
Using a device state as well as a location of an area of a touch on a touch-sensitive surface to determine how a device responds to touch user input provides the user with a simplified interface that provides contextually relevant controls. Providing additional control of the device without cluttering the UI with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the second area is comprised of a plurality of non-contiguous and non-overlapping areas (e.g., 1414A and 1414B of
In some embodiments, the second area is comprised of a first sub-area (e.g., 1414A) and a second sub-area (e.g., 1414B), and wherein adjusting the volume of the currently playing media comprises: lowering the volume of the currently playing media if the location of the touch is within the first sub-area (e.g., 1414B); and raising the volume of the currently playing media if the location of the touch is within the second sub-area (e.g., 1414A).
In some embodiments, the touch is a first touch (e.g., 1416), and, subsequent to adjusting the volume of the currently playing media in accordance a determination that the location of the touch (e.g., 1416) is within the second area (e.g., 1414A): the electronic device (e.g., 1400) temporarily expands (1516) the second area to create an expanded second area (e.g., 1418 of
In some embodiments, the touch-sensitive surface includes a display (e.g., 1404A and 1404B). In some embodiments, the display is an LED array (e.g., 1406). In some embodiments, further in accordance with a determination that the device is currently playing media, the electronic device (e.g., 1400) displays (1526), on the display, an indicator (e.g., + icon in 1406A of
In some embodiments, to adjust the volume of the currently playing media comprises (1530): the electronic device (e.g., 1400) adjusts (1532) a media playback volume (e.g., 1430 of
In some embodiments, the virtual assistant volume is non-zero when the media playback volume is zero.
In some embodiments, a maximum value of the virtual assistant volume (e.g., 1432) is lower than a maximum value of the media playback volume (e.g., 1430).
Note that details of the processes described above with respect to method 1500 (e.g.,
At
In this example, playlist interface 1610 is displayed on device 1602. However, because the playback queue represented by playlist interface 1610 is a shared queue, it can be accessed by multiple users and/or multiple devices. In some embodiments, device 1604 displays playlist interface 1610. In some embodiments, device 1602 and device 1604 display (e.g., concurrently) playlist interface 1610. Referring back to the scenario in
While reference is made to a playlist of songs in this example, an exemplary playback queue is not limited to songs. In some embodiments, a playback queue is any data representing one or more media items and information usable to access the media items (e.g., for playback). In some embodiments, a playback queue includes data associated with the one or more media items. For example, the playback can include information regarding one or more of: when the media was added to the queue, when the media expires from the queue, a source of the media (e.g., file location, a URL, an identification of a streaming service, a source device (e.g., the device that stores the media item)), credentials for accessing media (e.g., login credentials or a token granting access to a media streaming service), an identifier of a user that added the media to the queue, an identifier of a device that added the media to the queue, or the like. In some embodiments, a playback queue includes, but is not limited to, one or more of the following types of media items: an audio file, a video file, an audio stream, a video stream, or the like.
Turning back to the figures,
At
At
In response to user input 1618, device 1602 displays playlist interface 1610, which has been updated to include media item 1610C (
At
In response to input 1620, device 1604 displays playlist interface 1610, which has been updated to include media item 1610D (
In some embodiments, users can remove media items from a shared queue.
In response to input 1621, device 1604 displays media menu 1622, which includes an affordance 1622A for deleting a media item from the playlist (e.g., that includes the text “Delete from Tim's Birthday”) (
At
In some embodiments, a user or device requires permission to add a media item to a playback queue. For example, if a user lacks permission to add a media item to a shared queue, a message box similar to 1624 can be displayed that reads “You do not have permission to add tracks to Tim's Birthday Playlist”. In some embodiments, permission to add media items are subject to the same conditions or approval states and levels described above with respect to permission to remove media items, and thus are not repeated.
Notably, a fourth device 1630 displays playback interface 1610 of
In some embodiments, a device is associated with a media preference profile (also referred to as a “taste preference profile”). For example, device 1600 can be associated with (e.g., logged into) a user account associated with a third user (e.g., not the users of devices 1602 and 1604). The third user, in some examples, may not want the media that is added to the shared playback queue on their device (e.g., 1600) to affect their media preference profile. For example, the media preference profile can include data representing one or more of: particular media items associated the third user's account, media item playback history, media recommendations based on history or taste preferences, or the like. Thus, in some embodiments, media added to the playback queue on the first device (e.g., 1600) does not affect a media preference profile of a user account associated with the first device (e.g., 1600). In some examples, if the user of device 1602 is the same as the third user (e.g., whose account is associated with device 1600), device 1600 updates the media preference profile of third user based on media added by device 1602, but not based on media added by device 1604 (e.g., associated with a different user than the third user). Thus, the owner of a device can allow others to add music to a playback queue on a device associated with the owner's user account, without affect the device owner's taste preference profile.
As described below, method 1700 provides an intuitive way for playing back media from a plurality of media streaming services. The method reduces the cognitive burden on a user for playing back media from a plurality of media streaming services, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to play back media from a plurality of media streaming services faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 1600) receives (1702) a first request (e.g., represented by user input 1618 of
The electronic device (e.g., 1600) adds (1704) the first media item (e.g., 1610C as shown in
The electronic device (e.g., 1600) receives (1706) a second request (e.g., represented by user input 1620 of
The electronic device (e.g., 1600) adds (1708) the second media item (e.g., 1610D as shown in
The electronic device (e.g., 1600) accesses (1710) the first media item (e.g., 1610C) from a first media streaming service (e.g., represented by 1610E of
The electronic device (e.g., 1600) initiates playback (1712) of the first media item (e.g., 1610C) on the set of devices (e.g., 1600);
The electronic device (e.g., 1600) accesses (1714) the second media (e.g., 1610D) item from a second media streaming service (e.g., represented by 1610F of
The electronic device (e.g., 1600) initiates playback (1716) of the second media item (e.g., 1610D) on the set of devices (e.g., 1600).
Allowing a first media item from a first media streaming service and a second media item from a second media streaming service, different than the first media streaming service, to be added to a common playback queue, accessed, and played back allows the user to efficiently queue and manage playback of media from different sources using a single interface, thus requiring fewer user inputs to do so. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first request is received from a first requester (e.g., 1602). In some embodiments, a requester is a device (e.g., 1602). In some embodiments, a requester is a user account (e.g., a user account associated with identifier 1610G of
In some embodiments, the second request is received from a second requester (e.g., 1604) different than the first requester (e.g., 1602). In some embodiments, the second request includes identification of the second requester (e.g., represented by 1610H of
In some embodiments, the first requester is a second device (e.g., 1602) associated with a first user account (e.g., a user account associated with identifier 1610G). In some embodiments, the second requester is a third device (e.g., 1604) associated with a second user account (e.g., a user account associated with identifier 1610H).
In some embodiments, further in response to receiving the first request, the electronic device (e.g., 1600) determines whether the first requester (e.g., 1602) has permission to add a media item (e.g., 1610C) to the playback queue (e.g., 1610). In accordance with a determination that the first requester has permission to add a media item to the playback queue (e.g., 1610), the electronic device (e.g., 1600) adds the first media item to the playback queue (e.g., 1610 as shown in
In some embodiments, to determine whether the first requester has permission to add a media item to the playback queue, the electronic device (e.g., 1600) determines whether a user account (e.g., a user account associated with identifier 1610G) associated with the first requester (e.g., 1602) has permission to add a media item (e.g., 1610C) to the playback queue (e.g., 1610). In accordance with a determination that the user account associated with the first requester has permission to add a media item to the playback queue, the electronic device (e.g., 1600) adds the first media item (e.g., 1610C) to the playback queue (e.g., 1610 as shown in
In some embodiments, the electronic device (e.g., 1600) receives, from the second requester (e.g., 1604), a third request (e.g., 1623) to remove the first media item (e.g., 1610C) from the playback queue (e.g., 1610). The electronic device (e.g., 1600) determines whether the second requester has permission to remove the first media item from the playback queue. In accordance with a determination that the second requester has permission to remove the first media item from the playback queue, the electronic device (e.g., 1600) removes the first media item from the playback queue (e.g., 1610 as shown in
In some embodiments, to determine whether the second requester (e.g., 1604) has permission to remove the first media item from the playback queue, the electronic device (e.g., 1600) determines whether the second requester (e.g., 1604) is a member of a predefined set of requesters (e.g., the set of users represented by 603A-603C of
In some embodiments, the electronic device (e.g., 1600) transmits (1718), to a fourth device (e.g., 1630 of
In some embodiments, subsequent to adding the first media item to the playback queue: the electronic device (e.g., 1600) determines (1728) whether a queue removal condition (e.g., illustrated by 1632 of
In some embodiments, the first device (e.g., 1600) is not included (1734) in the set of devices.
Note that details of the processes described above with respect to method 1700 (e.g.,
As described below, method 1800 provides an intuitive way for playing back media requested by a plurality of devices. The method reduces the cognitive burden on a user for playing back media requested by a plurality of devices, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to play back media requested by a plurality of devices faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 1600) receives (1802), from a second device (e.g., 1602) associated with a first user (e.g., a first user account), a first request (e.g., represented by user input 1618 of
The electronic device (e.g., 1600) adds (1804) the first media item (e.g., 1610C of
The electronic device (e.g., 1600) receives (1806), from a third device (e.g., 1604) associated with a second user (e.g., a second user account), a second request (represented by user input 1620 of
The electronic device (e.g., 1600) adds (1808) the second media item (e.g., 1610D of
The electronic device (e.g., 1600) initiates playback (1810) of the first media item (e.g., 1610C of
The electronic device (e.g., 1600) initiates playback (1812) of the second media item (e.g., 1610D of
Allowing a first media item from a first device associated with a first user and a second media item from a second device associated with a second user, different than the first user, to be added to a queue for playback on a common set of devices allows a plurality of users to efficiently share and manage a common playback queue from any of a plurality of devices, thus requiring fewer user inputs to do so. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first request includes (1814) a first identifier (e.g., 1610G of
In some embodiments, the second request includes (1814) a second identifier (e.g., 1610H of
In some embodiments, the second device (e.g., 1602) is associated with a first user account that is associated with the first user. In some embodiments, the first user account is a user account on a media streaming service. For example, exemplary media streaming services include Apple Music, Spotify, or the like. In some embodiments, the first user account is a cloud-based service user account. For example, exemplary media streaming services include Apple iCloud, or the like.
In some embodiments, the third device (e.g., 1604) is associated with a second user account that is associated with the second user.
In some embodiments, the electronic device transmits, to a fourth device (e.g., 1630 of
In some embodiments, further in response to receiving the second request, and in accordance with a determination that the third device (e.g., 1604) has permission to add a media item to the playback queue, the electronic device (e.g., 1600) adds the second media (e.g., 1610D of
In some embodiments, further in response to receiving the second request (1818): in accordance with a determination that the second user (e.g., 1610H of
In some embodiments, the electronic device (e.g., 1600) receives (1824), from the third device (e.g., 1604), a third request (e.g., 1623 of
In some embodiments, in response to receiving the third request (e.g., 1623 of
In some embodiments, subsequent to adding the first media item to the playback queue, and in accordance with a determination that a queue removal condition (e.g., illustrated by 1632 of
In some embodiments, the first device (e.g., 1600) is not included (1816) in the set of devices.
In some embodiments, the first device (e.g., 1600) is associated with a media preference profile, wherein the media preference profile is associated with the first user. In some embodiments, further in response to receiving, from the second device (e.g., 1602) associated with the first user, the request (e.g., 1618) to queue the first media item (e.g., 1610C) for playback, the electronic device (e.g., 1600) updates (1832) the media preference profile based on the first media item. In some embodiments, further in response to receiving, from the third device associated with the second user, the request to queue the second media item for playback, the electronic device (e.g., 1600) forgoes updating (1834) the media preference profile based on the second media item. For example, if the request to queue the first media item is received from a device or user that is not associated with an owner of device 1600 (e.g., a home member), then a request to queue the media item will not affect the owner's taste preferences (e.g., which can be based on history of media played back on device 1000, or other home devices).
Note that details of the processes described above with respect to method 1800 (e.g.,
In some embodiments, an audio tone signal is only output by one device (e.g., to be configured, such as device 1906) that is in close proximity to device 1900, other than device 1900. For example, in some situations, device 1900 is placed in close proximity to multiple other devices that can be configured using device 1900. For example, a user may have purchased two speakers (e.g., such as device 1906) and wishes to configure one of them. In such case, it is useful to the user to be aware of which speaker device 1900 has connected to and that will be configured, for example, according to the techniques described below. Thus, even though device 1900 is brought into close proximity to two configurable devices, only the configurable device (e.g., device 1906) that will be configured during the configuration process will output an audio tone in response to an indication that device 1900 is in close proximity.
Setup card 1910 includes an identification of the device to be configured, which is the device (e.g., 1906) that device 1900 was placed in close proximity to. As shown, setup card 1910 includes the title “Speaker” (e.g., device 1906 is a smart speaker), as well as an image depicting the device (e.g., in the shape of device 1906 as shown in
At
At
At
At
In some embodiments, device 1900 displays a message (not illustrated) indicating that the tone was not detected by device 1900. For example, device 1900 can update message 1916A to read “Your device is listening but cannot detect a tone, please move your phone closer”.
In some embodiments, setup card 1918 includes one or more fields for entering a passcode (not illustrated). In some embodiments, device 1900 displays setup card 1972 (
At
As described previously, a device (e.g., device 1906) can be configured to be part of a device group (e.g., a stereo pair).
At
In some embodiments, device 1900 displays setup card 1926 of
In some embodiments, a location identifier is a name associated with the device. For instance, in some examples, a location identifier does not include reference to any particular location (e.g., “Speaker 1”). Thus, the location identifier can simply be used as a name by which to identify a configured device (e.g., at a multi-device interface as described above).
In some examples, the configuration process requires that device 1900 logs into a user account in order to proceed with the configuration process.
At
In some embodiments, device 1906 outputs an audible voice prompt prompting the user to provide one or more of the voice commands shown in setup card 1948 of
While the examples shown in setup card 1948 of
At
Additionally,
The configuration process can require that certain features be enabled on the device being configured (e.g., device 1906), even if such features are disabled on the device doing the configuring (e.g., device 1900).
In some embodiments, a setting of device 1900 that is compatible with device 1906 is automatically adopted in the configuration settings of device 1906. For example, if device 1900 has English (U.S.) set as their default language on device 1900, and device 1906 is only compatible with English (U.S.), English (U.K.) and English (Australian), then device 1900 would not display setup card 1960 during the configuration process. Rather, the configuration settings of device 1906 would be automatically include English (U.S.) as the language (e.g., for a voice assistant feature).
In some embodiments, a setting of device 1900 that is not compatible with device 1906 causes device 1900 to display an interface for selecting a compatible setting. For example, if device 1900 has Latin set as their default language on device 1900, and device 1906 is only compatible with English (U.S.), English (U.K.) and English (Australian), then device 1900 would display setup card 1960 during the configuration process, prompting user to select a compatible language setting.
As described below, method 2000 provides an intuitive way for configuring a second device. The method reduces the cognitive burden on a user for configuring a second device, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to configure a second device faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 1900) (also referred to as a “first device”) detects (2002) an audio tone signal (e.g., 1904) indicative of a pairing handshake with a second device (e.g., 1906). In some embodiments, the audio tone signal is an initial tone. For example the tone is played in response to the devices being place in close proximity. In some embodiments, the audio tone signal is played during a configuration process. In some embodiments, the audio tone signal represents a response to another audio tone signal played by the electronic device.
In some embodiments, the first device (e.g., 1900) is connected (2004) to the second device via a communication link (e.g., 1039 of
In some embodiments, the audio tone signal (e.g., 1904) is out-of-band to the communication link (2006). For example, the audio tone signal is not transmitted using the communication link. For example, the first and second devices are connected and exchange data communications over a Bluetooth wireless connection (e.g., a communication link). In this example, while the devices continue to be connected via the Bluetooth connection (e.g., while the devices are paired), an audio tone signal (e.g., an audible tone that includes or represents a communication between the devices) is out-of-band with the Bluetooth communication link. In some embodiments, being out-of-band to a communication link means that a signal (e.g., an audio tone signal) is not communicated using the same data exchange technique.
Using an audio tone signal that is out-of-band with a communication link between two devices allows the user to efficiently move through a configuration process for a device with fewer required user inputs, while ensuring that the devices are in relatively close proximity and that the user has physical access to both devices. Providing an optimized configuration process to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In accordance with detecting the audio tone signal, the first device (e.g., 1900) initiates (2008), on the first device (e.g., 1900), a configuration process for configuring the second device (e.g., 1906).
Using a detection of an audio tone signal allows the user to efficiently move through a configuration process for a device with fewer required user inputs. Providing an optimized configuration process to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
During the configuration process, the first device (e.g., 1900) displays (2010), on the display (e.g., 1902), a configuration user interface (e.g., 1912) that includes a prompt to select a location (e.g., “Where is this speaker?” as shown in
The first device (e.g., 1900) receives (2012) user input selection (e.g., 1913) of a location (e.g., the location “John's Room” shown in 1912A of
In response to receiving the user input, the first device (e.g., 1900) configures (2014) the second device (e.g., 1906) to be associated with the location. In some embodiments, configuring the second device to be associated with the location includes transmitting configuration data that includes the location. In some embodiments, the data is transmitted to the second device (e.g., a smart speaker). In some embodiments, the data is transmitted to a third device (e.g., an Apple TV).
In some embodiments, the audio tone signal (e.g., 1904) is generated by the second device (e.g., 1906 as shown in
In some embodiments, the audio tone signal includes an audio passcode. In some embodiments, the audio passcode is dictated (e.g., as shown in
In some embodiments, the audio tone signal (e.g., 1904) is received while the first device (e.g., 1900) is physically positioned within a threshold physical proximity (e.g., 1908 of
In some embodiments, the audio tone signal is a first audio tone signal, and during the configuration process (e.g., while displaying setup card 1918 of
In some embodiments, further in response to receiving the user input selection (e.g., 1913) of the location (e.g., “John's Room” as shown in
In some embodiments, the first device (e.g., 1900) receives user input (e.g., 1923) representing an affirmative request create the device group. In some embodiments, in response to the user input representing an affirmative request create the device group, the first device (e.g., 1900) displays, on the display, a configuration user interface (e.g., 1924 of
In some embodiments, the prompt to select a location includes a plurality of predetermined location identifiers (e.g., Kitchen, Bedroom, Patio, Dining Room, as shown in
In some embodiments, the plurality of predetermined location identifiers includes a user-defined location identifier (e.g., John's Room, as shown in
In some embodiments, the prompt to select a location includes a field (e.g., “Create New Room” option as shown in
In some embodiments, during the configuration process (2032): the first device (e.g., 1900) displays (2034), on the display (e.g., 1902), a configuration user interface (e.g., setup card 1914 of
In some embodiments, prior to transmitting the user account information to the second device, and in accordance with a determination that the first device (e.g., 1900) is not currently logged into a user account associated with the user account information (e.g., is not currently logged into an iCloud account), the first device (e.g., 1900) displays, on the display (e.g., 1902), a prompt to log in to the user account (e.g., setup card 1932 that includes the text “Please login to your iCloud account to continue” as shown in
In some embodiments, in response to progressing from a first step (e.g., setup card 1912) in the configuration process to a second step (e.g., setup card 1914) in the configuration process, the first device (e.g., 1900) outputs a third audio tone signal (e.g., 1044 of
In some embodiments, in response to progressing from the second step (e.g., setup card 1914) in the configuration process to a third step (e.g., setup card 1916) in the configuration process, the first device (e.g., 1900) outputs a fifth audio tone signal (e.g., 1048 of
In some embodiments, subsequent to initiating the configuration process, the first device (e.g., 1900) receives data regarding an output of an operation being performed by the second device (e.g., 1906). For example, the output can be audio output (e.g., dictation by a voice assistant) by device 1906 of media (e.g., music), weather information, news, calendar appointments, or the like. In response to receiving the data regarding the output of the operation being performed by the second device (e.g., 1906), the first device (e.g., 1900) displays a user interface (e.g., interface 1950 of
Displaying a user interface that includes a representation of the output of the operation being performed by the second device, provides the user with visual feedback about the state of a state of the second device. Providing improved visual feedback to the user enhances the operability of the second device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the operation being performed by the second device (e.g., 1906) includes audibly outputting information (e.g., playing the song identified in interface 1950). In some embodiments, receiving the data regarding the output of the operation being performed includes receiving data representing the information (e.g., song title, elapsed play time, weather forecast data, news stories). In some embodiments, displaying the user interface (e.g., interface 1950 which includes information about the song being played), that includes the representation of the output of the operation being performed by the second device, includes displaying at least a portion of the data representing the information (e.g., displaying less than all of the data, such as a song title but not an album name, or displaying one news story where there are three current news stories in the data received by device 1900).
Displaying data representing information corresponding to information being audibly outputted by the second device provides the user with visual feedback about the state of the second device, in addition to the audio feedback being provided directly by the second device. Providing improved (e.g., supplemental or additional) visual feedback to the user enhances the operability of the second device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the information includes a media item (e.g., a song), and the operation being performed by the second device (e.g., 1906) includes audibly outputting the media item. In some embodiments, displaying the data representing the information includes displaying one or more of: an artist, a media item name, an album name, album art, and a media playback progress indicator (e.g., as shown in interface 1950 of
Displaying additional data (e.g., one or more of artist, a media item name, an album name, album art, and a media playback progress indicator) that corresponds to a media item being audibly outputted by the second device provides the user with visual feedback about the state of the second device. Providing improved (e.g., supplemental or additional) visual feedback to the user enhances the operability of the second device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the user interface that includes the representation of the output of the operation being performed by the second device includes displaying one or more of news information or weather information.
In some embodiments, during the configuration process: in accordance with a first configuration setting of the first device being compatible with the second device (e.g., 1906), the first device (e.g., 1900) configures the second device (e.g., 1906) to include the first configuration setting. For example, a configuration setting can be a language setting for a voice assistant, and a first configuration setting can be “English (U.S.)” In this example, English (U.S.) is compatible with (e.g., supported by) a voice assistant on device 1906. In some embodiments, the configuration is done automatically, without requiring user input or confirmation, if the setting is compatible. In accordance with the first configuration setting of the first device not being compatible with the second device (e.g., 1906), the first device (e.g., 1900) displays an indication that the first configuration setting is not compatible with the second device (e.g., displays a message). In some embodiments, the indication that the first setting is not compatible with the second device is the display of a setup card for selecting a different/compatible setting (e.g., setup card 1960 of
Using a first configuration setting of the first device that is compatible with the second device allows the user to efficiently move through a configuration process for a device with fewer required user inputs, providing an optimized configuration process. Providing an optimized configuration process to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, further in accordance with the first configuration setting of the first device being compatible with the second device (e.g., 1906), the first device (e.g., 1900) displays a configuration user interface that includes a prompt requesting acceptance of the first configuration setting for the second device. In response to receiving user input accepting the first configuration setting for the second device (e.g., 1906), the first device (e.g., 1900) configures the second device to include the first configuration setting.
Displaying a configuration user interface that includes a prompt requesting acceptance of the first configuration setting for the second device, provides the user with visual feedback about the state of the second device (e.g., that it is compatible with the first configuration setting). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first configuration setting is a setting disabling a device feature (e.g., a voice assistant), and wherein a second configuration setting is a setting enabling the device feature (e.g., a voice assistant). In accordance with a determination that the configuration process requires enabling the device feature on the second device (e.g., 1906): the first device (e.g., 1900) displays an indication that the device feature will be enabled on the second device (e.g., setup card 1958 of
Displaying an indication that the device feature will be enabled on the second device (e.g., even when it is disabled on the first device) provides the user with visual feedback about the state of the second device (e.g., that the feature is required on the second device). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the indication that the device feature will be enabled on the second device (e.g., 1906) includes displaying an indication that the device feature will remain disabled on the first device.
Displaying an indication that the feature will remain disabled on the first device provides the user with visual feedback about the nature of the operation and the state of the first device (e.g., that enabling the feature on the second device will not alter the state of the first device, as to the feature). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, further in accordance with the first configuration setting of the first device not being compatible with the second device (e.g., 1906), the first device (e.g., 1900) displays a configuration user interface (e.g., 1960 of
Displaying a configuration user interface that includes a prompt requesting selection of a third configuration setting compatible with the second device reduces the number of inputs needed to configure the second device by surfacing compatible options to the user and provides an optimized configuration process. Providing an optimized configuration process to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, prior to establishing the communication link connecting the first device and the second device (e.g., 1906), the first device (e.g., 1900) detects an indication that a physical proximity between the first device and the second device satisfies a proximity condition (e.g., as shown in
Using an indication that the physical proximity between the first device and the second device satisfies the proximity condition in order to output an audio tone signal provides the user with auditory feedback regarding the state of the first device. For example, when there are other potential devices in proximity that are configurable, the audio tone signal can indicate which device will be configured. Providing improved feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, subsequent to transmitting the user account information to the second device (e.g., 1906), the first device (e.g., 1900) displays a configuration user interface (e.g., 1948 of
Displaying a configuration user interface associated with a voice assistant that includes a prompt to provide user voice input invoking one or more functions of the voice assistant provides the user with information regarding the capabilities and state of a device. Providing such information to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, in accordance with a determination that user voice input invoking one or more of the features of the voice assistant has been received by either the first device or the second device (e.g., 1906), the first device (e.g., 1900) maintains display of the configuration user interface (e.g., 1948) associated with the voice assistant. In response to receiving user input selection of an affordance (e.g., affordance labeled “Done” in setup card 1948) included in the configuration user interface associated with the voice assistant, the first device (e.g., 1900) ceases display of the configuration user interface associated with the voice assistant (e.g., setup card 1948 slides off the display, as shown in
Note that details of the processes described above with respect to method 2000 (e.g.,
In some embodiments, in response to detecting the user input voice command (e.g., 2108 by user 2106), device 2100 adjusts the output of an audible signal (e.g., 2104). In some embodiments, device 2100 adjusts the output of the audible signal based on a spatial position of the voice command source (e.g., the position of user 2106) while continuing to output the audible signal (e.g., 2104). For example, device 2100 applies spatial domain audio processing to project the sound away from the user 2106, to filter the sound with low pass, and/or band pass, and/or high pass filters, or to lower the volume (e.g., to zero) of one or more of its speakers (e.g., where device 2100 includes an array of a plurality of speakers). For example, device 2100 can lower the volume of a speaker (e.g. of an array of speakers of device 2100) that is outputting the audible signal and that is nearest the spatial position of user 2106.
In some embodiments, in response to detecting the user input voice command (e.g., 2108), device 2100 determines a spatial position of a voice command source (e.g., user 2106).
In some embodiments, a plurality of devices (e.g., 2100 and 2110) are used to determine a spatial position of a voice command source (e.g., user 2106). For example, both devices 2100 and 2110, as shown in
In some embodiments, device 2100 adjusts the output of the audible signal based on the spatial position of the voice command source (e.g., user 2106).
In some embodiments, device 2100 adjusts the output of the audible signal based on the second device (e.g., 2110).
In some embodiments, a first device performs an audio processing technique. For example, device 2100 can perform an audio processing technique to project the audio output so that it is perceived by a user to be in a direction away from the user. For example, device 2100 performs a spatial audio processing technique on one or more signals representing the audio output. The spatial audio processing technique, in some examples, is used to transform the one or more signals representing the audio output, when outputted by the device, is perceived by a listener to emanate from a selected spatial position. One of skill in the art would recognize that various appropriate techniques can be used for performing such audio processing, all of which are intended to be within the scope of this disclosure.
In some embodiments, device 2100 adjusts audio output such that it will be perceived by a voice command source (e.g., user 2106) to emanate from a point in a direction away from them (e.g., relative to device 2100). For example, in response to detecting voice user input 2108, the device can adjust the output of 2104 (e.g., playback of music as shown in
In some embodiments, device 2100 adjusts audio output such that it will be perceived by a voice command source (e.g., user 2106) to emanate from a point in a direction toward them (e.g., relative to device 2100). For example, as shown in
As described below, method 2200 provides an intuitive way for adjusting audible output. The method reduces the cognitive burden on a user for adjusting audible output, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to adjust audible output faster and more efficiently conserves power and increases the time between battery charges.
While outputting an audible signal (e.g., 2104) from the electronic device (e.g., 2100), the electronic device (e.g., 2100) detects a (2202) user input voice command (e.g., 2108) from a voice command source (e.g., 2106).
In response to detecting the user input voice command, the electronic device (e.g., 2100) determines (2204) a spatial position (e.g., angle 2122 and/or distance 2124 of
While continuing to output the audible signal (e.g., 2104), the electronic device (e.g., 2100) adjusts (2206) the output (e.g., volume, frequency, and/or direction) of the audible signal based on the spatial position of the voice command source (e.g., as shown in
Adjusting the output of an audible signal, while continuing to output it, based on a spatial position determined in response to a user input voice command provides the user with feedback that their voice command is being detected. Providing improved audible feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the device is a first device, and the audible signal is a first audible signal. In some embodiments, the electronic device (e.g., 2100) determines (2208) that a second device (e.g., 2110) is currently outputting a second audible signal (e.g., 2112). For example, the first and second device are currently playing the same content (e.g., are a device group), or the first device detects (e.g., via one or more microphones) that the second device is outputting audio (e.g., which can be a different audio signal).
In some embodiments, adjusting, by the first device (e.g., 2100), the output of the first audible signal is further based on (2210) a known influence that audio output by the first device has on the second device (e.g., 2110). For example, the second device may be closer to the voice command source (e.g., 2106), and thus may be the most appropriate device to listen to the user input voice command (e.g., 2108). In some embodiments, the audio output of the first device is adjusted so as to reduce interference with the second device's ability to detect and/or process the user input voice command. For example, the second device includes a microphone for detecting voice input and the first device adjusts its output so as to reduce interference with the second devices use of its microphone to detect voice user input. In some embodiments, the known influence is determined (e.g., by device 2100) based on the spatial position of the second device (e.g., relative to the position of the first device). In some embodiments, the known influence is based on data received from the second device (e.g., the second device transmits quantitative data regarding how the output of audible signals by the first device affects the audio detection circuitry (e.g., microphone) of the second device).
In some embodiments, the first device (e.g., 2100) adjusts the output (e.g., volume, frequency, and/or direction) of the audible signal based on the spatial position of second device (e.g., 2110) (e.g., as shown in
In some embodiments, the device (e.g., 2100) includes a speaker array (e.g., two or more speakers, such as speakers 2102A-2102C of
In some embodiments, the audio processing technique includes transforming the audio output into the spatial domain and applying one or more filters (e.g., head-related transfer functions (HRTFs). For example, the filter can create a three-dimensional audio effect at a position that is laterally located in the opposite direction of the voice command source (e.g., point 2132 as shown in
In some embodiments, the spatial position is a first spatial position (e.g., 2130 of
In some embodiments, subsequent to adjusting the output of the audible signal: the electronic device (e.g., 2100) detects that the user input voice command (e.g., 2108) from the voice command source (e.g., 2106) has ended. In response to detecting that the user input voice command from the voice command source has ended, the electronic device (e.g., 2100) ceases adjusting the output the audible signal. For example, the adjusted audio output (shown in
In some embodiments, determining the spatial position of the voice command source relative to the device comprises: determining a distance (e.g., 2124) of the voice command source relative (e.g., 2106) to the electronic device (e.g., 2100), and determining an angular position (e.g., a lateral or vertical angle) (e.g., 2122) of the voice command source relative to the device.
In some embodiments, the audible signal (e.g., 2104) is a first audible signal, and while adjusting the output of the audible signal (e.g., 2104 as shown in
In some embodiments, the spatial position (e.g., position of user 2106 in
In some embodiments, the first audible signal represents playback of a media item (e.g., a song, video audio), and wherein the second audible signal represents a virtual assistant output (e.g., a voice assistant output 2140, as shown in
In some embodiments, the electronic device (e.g., 2100) includes a plurality of microphones (e.g., a microphone array).
Note that details of the processes described above with respect to method 2200 (e.g.,
In some embodiments, a device (e.g., 2300) populates (e.g., adds media items to) an existing media playback queue in response to detecting a device associated with a taste profile. Thus, in some examples, device 2300 dynamically updates a queue based user taste profiles as more users are detected.
In some embodiments, a device (e.g., 2300) removes media items from a playback queue in response to no longer detecting a device associated with a taste profile. For example, device 2300 updates a queue to cater to the users that remain connected. For instance, in response to device 2302 no longer being detected by device 2300, device 2300 can remove media items 2314D and 2314E from playlist 2312. Thus, media playback can be tailored to users who remain present in a location (e.g., connected to device 2300) even as users come and go, without requiring excessive user inputs to do so.
In some embodiments, a device (e.g., 2300) creates a playback queue based on a plurality of taste profiles in response to user input.
In response to user input 2320A, device 2310 displays playlist creation interface 2324 (
In some embodiments, a device (e.g., 2310) displays a prompt to create a queue based on a plurality of taste profiles of detected devices in response to receiving user input (e.g., 2326). As shown in
As described above, a device can automatically generate a playback queue based on a plurality of taste profiles. In some embodiments, a device (e.g., 2300, 2310) generates the queue based on a plurality of taste profile in response to user input activating (e.g., opening) a media application. For example,
As described below, method 2400 provides an intuitive way for maintaining a queue based on multiple user taste profiles. The method reduces the cognitive burden on a user for maintaining a queue based on multiple user taste profiles, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to maintain a queue based on multiple user taste profiles faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 2300 or 2302), which is a first device, detects (2402) that a second device (e.g., 2310) associated with a second user account (e.g., an iCloud account) is connected to the first device (e.g., 2300 or 2302). For example, the second device is connected to the same Wi-Fi network, within Bluetooth range of the first device, or the like. The first device is associated (2404) with a first user account (e.g., an iCloud account). The first user account is associated (2406) with a first media preference profile (e.g., 2316A or 2318A). In some embodiments, a media preference profile includes data representing media items or information for identifying media items that represents the preferences of the owner of the first user account. In some embodiments, a preference profile includes one or more media items. For example, the profile includes identifiers for media (e.g., songs, videos) that the first user account has saved, liked, listened to (e.g., a plurality of times), or otherwise indicates that the owner of the first user account likes a media item. In some embodiments, the preference profile includes generalized information for identifying media items. For example, generalized information can include a genre (e.g., type of music), an artist, an album (e.g., comprised of a plurality of media items). Such generalized information can be used to identify media items by matching, for example, metadata associated with media items to the generalized information. The second user account is associated (2408) with a second media preference profile (e.g., 2316B or 2318B) different than the first media preference profile.
The first device (e.g., 2300 or 2302) initiates (2410) playback of media based on the first media preference profile and the second media preference profile.
Initiating playback of media based on first and second media profiles associated with first and second devices that are connected provides users with an improved media playback feature for creating playback queues according to the tastes of multiple users whose devices are connected while reducing redundant user inputs at each device. Providing improved media playback features to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first device (e.g., 2300 or 2302) determines (2412) a combined preference profile (e.g., 2316C or 2318C) based on the first media preference profile (e.g., 2316A or 2318A) and the second media preference profile (e.g., 2316B or 2318B).
In some embodiments, determining a combined preference profile based on the first media preference profile and the second media preference profile comprises: determining (2414) a media preference that is related to both the first media preference profile and the second media preference profile. In some embodiments, a media preference includes one or more of a genre of media (e.g., music), an artist, a media item (e.g., a song), or the like. In some embodiments, a media preference that is related to both is a media preference that is common to both profiles (e.g., 2316C). In some embodiments, a media preference that is related to both is a media preference that is a subset or superset of both profiles. For example, rock and roll music is a superset of rock and roll music from the year 1987.
In some embodiments, while continuing to detect that the second device (e.g., 2310) is connected to the first device (2416): the first device (e.g., 2300 or 2302) adds (2418) a plurality of media items (e.g., 2314D and 2314E of
In some embodiments, the first device (e.g., 2300 or 2302) receives a request (e.g., selection of affordance 2314F) to initiate playback on the first device, and in response to receiving the request, initiates the playback of media based on the first media preference profile and the second media preference profile.
In some embodiments, the request (e.g., selection of 2314F) is received from the second device (e.g., 2310). For example, a guest device (e.g., not associated with the device or the home set of devices) initiates playback of a playback queue that includes a media items pertaining to a blended taste profile.
In some embodiments, the first device includes a display (e.g., 2302), and wherein the method further comprises: displaying, on the display, an affordance (e.g., a “play now” affordance (e.g., 2314F), a media item in a playlist (e.g., 2314D), a “shuffle all” affordance, or the like), and wherein receiving the request to initiate playback on the first device comprises receiving user input selection of the affordance (e.g., 2314F). In response to receiving user input selection of the affordance, the first device (e.g., 2300 or 2302) initiates the playback of media based on the first media preference profile and the second media preference profile.
In some embodiments, initiating playback of media based on the first media preference profile and the second media preference profile comprises: transmitting an instruction to a third device (e.g., 2300) to initiate playback.
In some embodiments, the first device (e.g., 2300 or 2302) receives (2422) a media item (e.g., an identifier of a media item, a link to the media item, or a copy of the media item). In response to receiving the media item (2424): in accordance with a determination that the media item was received from the first device, the first device (e.g., 2300 or 2302) updates (2426) the first media preference profile based on the media item (e.g., 2316A or 2318A); and in accordance with a determination that the media item was received from the second device (e.g., 2310), the first device (e.g., 2300 or 2302) forgoes updating (2428) the first media preference profile based on the media item. For example, if the media item was added to a blended taste profile queue by a device not associated with a user account of the device managing or storing the queue (e.g., the owner's device), the owner's taste profile is not updated based on the addition of that media item to the queue.
Note that details of the processes described above with respect to method 2400 (e.g.,
In response to user input 2508, device 2502 displays exemplary multi-device interface 2510 (
In response to receiving selection of the device named “Tim's Living Room” (e.g., user input 2512), device 2502 displays message 2514 (
At
In some embodiments, a permission interface allows selection of a plurality of different permission levels. In some embodiments, a permission level grants conditional permission. For example, permission request interface 2518 (
In some embodiments, playback of media by guests (e.g., by device 2502) on a device of the home set of devices does not affect a preference profile and/or playback history of a user associated with the set of devices. For example,
As described below, method 2600 provides an intuitive way for allowing a guest device to initiate playback. The method reduces the cognitive burden on a user for allowing a guest device to initiate playback, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to allowing a guest device to initiate playback faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 2500), which is a first device, receives a request (2602), from a third device (e.g., 2502), to initiate media playback on at least one device of a set of devices (e.g., a set that includes devices 2500 and 2504).
In some embodiments, the set of devices comprises (2604) the first device (e.g., 2500) and a second device (e.g., 2504). In some embodiments, the set of devices is a home set of devices (e.g., configured using a home control application as described with respect to
In some embodiments, the third device is not a (2606) member of the set of devices. For example, the third device belongs to a guest or visitor to the home that includes the set of devices. For example, the third device can be associated with a user account that is not a member of the set of user accounts that comprise the set of users making up the household), and
In some embodiments, the third device (e.g., 2502) is connected to (2608) the first device (e.g., 2500). In some examples, the devices are connected via Wi-Fi, Bluetooth, or the like.
In some embodiments, in response to receiving the request (2610): in accordance with a determination that the third device (e.g., 2502) has permission (e.g., previously granted by member of the home) to initiate media playback on the at least one device (e.g., 2500) of set of devices, the electronic device (e.g., 2500) initiates (2612) media playback on the set of devices (e.g., 2500). In some embodiments, a set of devices includes one or more devices.
In accordance with a determination (2614) that the third device does not have permission to initiate media playback on the at least one device of set of devices: the electronic device (e.g., 2500) transmits (2616) a request for permission (e.g., represented by 2516 of
Requesting permission, by a first device, from a second device to initiate playback based on a request from a third device in response to the request provides users with the ability to quickly and dynamically request permission for media playback while reducing the number of user inputs required to navigate permissions menus or resend a request to initiate playback after being granted permission. Providing improved media playback permissions features to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In response to receiving permission from the second device, the electronic device (e.g., 2500) initiates (2618) media playback on the at least one device (e.g., 2500) of the set of devices. In some embodiments, initiating playback includes transmitting an instruction (e.g., to another device in the set of devices) to initiate playback.
In some embodiments, in accordance with a determination that a first user account associated with the third device has permission to initiate media playback on the set of devices, the electronic device (e.g., 2500) determines (2620) that the third device (e.g., 2502) has permission (e.g., device 2502 has permission by virtue being associated with a user (e.g., user account) that has permission), wherein the first user account is not associated with any device of the set of devices (e.g., is an account (e.g., iCloud) of a guest user that is not associated with any device in the home of the home set of devices). In accordance with a determination that the first user account associated with the third device does not have permission to initiate media playback on the set of devices, the electronic device (e.g., 2500) forgoes determining (2622) that the third device has permission. For example, if the user account associated with the third device does not have permission, playback does not initiate in response to a request from the third device.
In some embodiments, further in accordance with a determination that the third device does not have permission, the electronic device (e.g., 2500) transmits (2624) the request for permission to a plurality of devices (e.g., 2504 and another device (e.g., a personal device with a display), both associated with the home owner) that includes the second device (e.g., 2504). For example, the plurality of devices are devices that are associated with the first device. In some embodiments, the first device and the plurality of devices are each associated with one or more user accounts that are not associated with the third device. For example, the plurality of devices can be other devices associated with an owner (e.g., their user account) of the first device (e.g., logged into a common account belonging to the owner, or logged in to accounts associated with a predefined group of users such as a family of the owner), but the third device is associated with a guest (e.g., with the guest's user account) to the owner's home. Thus, the third device is not included in the group of users in the owner's household.
In some embodiments, initiating media playback on the at least one device of the set of devices comprises: initiating playback on the first device (e.g., 2500); and forgoing initiating playback on the second device (e.g., 2504). Thus, in some examples, the device that initiates playback is not the device that granted permission.
In some embodiments, subsequent to receiving permission from the second device (e.g., 2504): the electronic device (e.g., 2500) receives a request, from the third device (e.g., 2502), to initiate playback on a fourth device (e.g., another smart speaker device that is not device 2500), wherein the set of devices comprises the fourth device, and wherein the fourth device is not included in the at least one device of the set of devices (e.g., the original request (by device 2502) to initiate playback on device 2500 did not include a request to initiate playback on the fourth device). In response to receiving the request to initiate playback on a fourth device, (by device 2502) initiates playback on the fourth device. In some embodiments, initiating playback includes transmitting an instruction (e.g., to another device) to initiate playback. For example, if the guest user subsequently selects additional devices (e.g., at a multi-device interface) in the home owner's home (e.g., after being granted permission to initiate playback on the first device 2500), the permission extends to other devices (e.g., all devices) associated with the home set of devices.
In some embodiments, subsequent to receiving permission from the second device: receiving a request, from the third device, to remove a media item (e.g., as shown in
In some embodiments, the first device is associated with a media preference profile (e.g., 2316A as shown in
Note that details of the processes described above with respect to method 2600 (e.g.,
As illustrated above, a permissive condition can be based on device proximity. In some embodiments, a permissive condition is based on (or further based on) an orientation of a device (e.g., 2702).
As described below, method 2800 provides an intuitive way for providing data based on a physical position. The method reduces the cognitive burden on a user for providing data based on a physical position, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to provide data based on a physical position faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 2700), which is at a first device associated with a user account (e.g., logged into user's iCloud) receives (2802) user input (e.g., a user input voice command) representing a request to access data from the user account. In some embodiments, data from a user account can include one or more of: calendar data (e.g., meetings, events, or the like), messages (e.g., text messages, iMessages, emails, voice messages, or the like), notes, reminders (e.g., audio or text reminders), or the like.
In response to receiving (2804) the user input (e.g., user input voice command), the first device (e.g., 2700) determines (2806) whether a physical positioning of the first device (e.g., 2700) and a second device (e.g., 2702) associated with the user account satisfies a permissive condition. In some embodiments, a permissive condition is satisfied when the second device is in close proximity to the first device (e.g., as shown in
In accordance with a determination that the physical positioning satisfies the permissive condition, the first device (e.g., 2700) provides (2808) the data from the user account through the first device (e.g., dictates the data, as shown in
In accordance with a determination that the physical positioning does not satisfy the permissive condition, the first device (e.g., 2700) forgoes (2810) providing the data from the user account through the first device (e.g., requests that the second device is placed in close proximity, as shown in
Using a determination of whether the physical positioning of device satisfies a permissive condition provides the user with an easy technique for granting permission without extraneous user inputs. Performing an operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, providing the data from the user account through the first device comprises: outputting (2812) an audio signal (e.g., 2706 or 2712) representative of the data from the user account.
In some embodiments, outputting an audio signal representative of the data from the user account comprises: causing audible output (2814) of a dictation (e.g., 2706 or 2712) representative of the data from the user account using a text-to-speech algorithm In some embodiments, the dictation is in a natural language (e.g., a spoken language such as English, Spanish, French, or the like). For example, the dictation comprises data being read aloud (e.g., using a text-to-speech algorithm) through a speaker of the first device.
In some embodiments, the data from the user account comprises data from one or more of: a calendar entry (e.g., a meeting, an appointment), a notification (e.g., of an incoming text message), an email, a text message, a stored text document (e.g., a note), stored contact information, phone call audio, video call audio or video (e.g., FaceTime, Skype), a voice message, an address (e.g., user's home), and a media item (e.g., music, video).
In some embodiments, determining whether the physical positioning of the first device and second device satisfies the permissive condition comprises: determining (2816) whether a physical proximity between the first device and the second device satisfies a proximity condition (e.g., the first and second device are in close proximity to each other).
In some embodiments, determining whether the physical positioning of the first device and second device satisfies the permissive condition comprises: determining whether (2818) a physical orientation of the first device satisfies an orientation condition. In some embodiments, the physical orientation can be detected via sensors on the second device (e.g., and communicated to the first device), such as one or more of: accelerometer, ambient light sensor, camera, or the like. In some embodiments, an orientation condition is satisfied when the second device is positioned such that a main display is not covered. For example, a device that is resting face up (e.g., with its display visible, in contrast to face down) satisfies the orientation condition.
In some embodiments, further in accordance with a determination that the physical positioning does not satisfy the permissive condition, the first device (e.g., 2700) outputs (2820) an indication (e.g., 2708 or 2710) that the permissive condition is not satisfied (e.g., the devices are not in close proximity).
In some embodiments, outputting the indication that the permissive condition is not satisfied comprises: outputting (2822) an audible indication (e.g., 2708 or 2710) of a user action required to satisfy the permissive condition (e.g., a dictated output of: “Please unlock your device” or “Please bring your phone closer”, or the like).
In some embodiments, the user input representing a request to access data from the user account is a first user input, the method further comprising, subsequent to providing the data from the user account through the first device (e.g., as shown in
Note that details of the processes described above with respect to method 2800 (e.g.,
At
In some embodiments, a set of devices that is concurrently playing back media (e.g., as part the same media session) synchronizes playback of the media. In some embodiments, one device coordinates playback synchronization (e.g., also referred to as a “primary device” or “hero device”). Coordinating playback synchronization can include one or more of: processing playback control commands (e.g., pause, next track), streaming media to the other devices in the set of devices, storing and/or maintaining a playback queue, detecting whether the other devices are outputting the media in synchronization with each other (e.g., via use of a clock signal), or the like.
In some embodiments, a set of devices (e.g., for a media session) includes an heir device (also referred to as a “designated heir” or a “backup primary device”). In some embodiments, the designated heir is configured to take over responsibility of the primary device in response to the primary device no longer being able to playback media (e.g., for the media session) and/or coordinate playback synchronization. In some embodiments, several “generations” of heirs are designated (e.g., a designated heir, a designated heir to the designated heir, and so forth).
In some embodiments, primary device responsibility (e.g., playback coordination) includes processing playback control commands. For example, because the devices in a set of devices are interconnected with each other (and potentially connected with other devices), a playback control command can be received by any device of the set of devices (or by the other devices). In some embodiments, the playback control command is forwarded to the primary device if it is a device that is not the primary device for a media session. In some embodiments, the primary device processes the playback control command, and then transmits instructions to the (e.g., remaining) devices in the set of devices (e.g., for enacting the playback control command).
For example,
As described below, method 3000 provides an intuitive way for managing playback coordination. The method reduces the cognitive burden on a user for managing playback coordination, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manage playback coordination faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 2910), which is a first device, receives (3002) a command to initiate playback of media on a set of devices comprising the first device (e.g., 2910) and a second device (e.g., 2912). In some embodiments, the first and second devices are both configured to be capable of receiving playback coordination responsibility for the set of devices.
In response to receiving the command, the first device (e.g., 2910) initiates (3004) synchronized playback of the media on the set of devices (e.g., 2910 and 2912), wherein the second device is designated (3006) as a primary device (e.g., as shown in
Initiating synchronized playback and automatically managing the coordination of media playback without requiring further user input reduces the burden on the user when playing back media on a plurality of devices. Performing an operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the set of devices further comprises a third device (e.g., 2914 as shown in
In some embodiments, coordinating the playback of the media on the third device comprises one or more of (3020): providing a link to the media (e.g., a URL); providing a stream of the media (e.g., a real time or buffered stream of data representing the media); and providing a copy of the media (e.g., a media file).
In some embodiments, the first device (e.g., 2910) receives (3022) a command to cease playback of media on the first device. In response to receiving the command to cease playback of media on the first device (3024): the first device (e.g., 2910) ceases playback (3026) of media on the first device (e.g., as shown in
In some embodiments, the set of devices further comprises a third device (e.g., 2914), and during playback on the set of devices (e.g., 2910, 2912, and 2914), the first device (e.g., 2910) detects that the second device (e.g., 2912) is no longer available for playback of the media (e.g., as shown in
In some embodiments, the first device (e.g., 2910) receives, from a fourth device (e.g., 2916), a command to initiate playback of media on the set of devices. The first device (e.g., 2910) receives, from the fourth device, a designation that the first device is the designated heir. For example, the device that transmits the command to initiate playback and that designates the designated heir is a device different than the designated heir and the designated primary device.
In some embodiments, the fourth device is not a member of the set of devices. For example, the fourth device is a device in the home set of devices that initially coordinates playback on device(s) regardless of whether playback includes the fourth device. In some embodiments, initially coordinating playback includes designating a designated heir and/or a primary device for the playback session on the set of devices.
In some embodiments, initiating synchronized playback of the media on the set of devices comprises transmitting a copy of a playback queue to each device in the set of devices.
In some embodiments, during synchronized playback, the first device (e.g., 2910) receives, at the first device, a playback control command (e.g., 2920, such as pause, next track, seek, or the like). In response to receiving the playback control command: in accordance with the first device being designated the primary device, the first device (e.g., 2910) transmits an instruction to each of the devices in the set of devices based on the playback control command (e.g., as shown in
Note that details of the processes described above with respect to method 3000 (e.g.,
As described above, devices such as devices 3100, 3102, and 3104 (e.g., smart speaker devices), in accordance with some embodiments, can determine a spatial position of a user for targeting audio content to a voice command source and/or act as an extension (e.g., for notifications output) of another device (e.g., a personal device). Similarly, a device (or a set of devices) (e.g., such as devices 3100, 3102, and 3104) can be configured to automatically and selectively output audible output based on whether a user is within a range of the device (e.g., physically present near the device).
In some embodiments, a device (e.g., 3100) has an audible output range (e.g., a designated, predetermined, or dynamic range). In some embodiments, if a device (e.g., 3100) determines that a user is located outside of the audible output range of the device, it forgoes outputting the audible output when the trigger event occurs. For example, as shown in
In some embodiments, determining whether a user is located within an audible output range is based on one or more of: a detected physical proximity of the device (e.g., 3100) to the user (e.g., 3108), a detected presence of the user (e.g., 3108) in the same room as the device (e.g., 3100), and the output characteristics (e.g., audio output power) of the device (e.g., 3100). In some embodiments, determining whether a user is located within an audible output range is based on detection of a device associated with the user.
An audible output range can be determined in a variety of manners. In some embodiments, the audible output range (e.g., of each device) is fixed. For example,
In some embodiments, a user can be within the audible output range of a plurality of devices. For example, as shown in
In some embodiments, an audible output range of a device is the room in which a device is located. For example, as shown in
In some embodiments, each device in a set of devices (e.g., 3100, 3102, and 3104) receives the audible output trigger event. As shown in
In some embodiments, the audible output range of a device (e.g., 3100) is relative to one or more other devices (e.g., 3102), or is otherwise affected by other devices in a set of devices or nearby. For instance,
In some embodiments, a device (e.g., 3100) of the set of devices (e.g., 3100, 3102, and 3104) detects a user voice to determine whether the user is located within the device's audible output range. For example, in
In some embodiments, a device (e.g., 3106) that is not one of the set of devices (e.g., 3100, 3102, and 3104) is connected to the set of devices. In this example, device 3106 is a car that connected to a personal device of user 3106 when the user entered the car. In some embodiments, the devices of the set of devices forgo outputting audible outputs in response to determining that the user is within an audible output range (e.g., while the car is powered on) of the device (e.g., 3106) that is not one of the set of devices. For example, as shown in
In some examples, the devices of a set of devices are used as intelligent end-to-end communication tools. In some embodiments, a first device (e.g., 3100) of a set of devices (e.g., 3100, 3102, and 3104) receives a user input request (e.g., 3118) to deliver a message (e.g., 3120) to a user (e.g., 3116) that is within audible output range of at least one device of the set of devices. In some embodiments, the first device (e.g., 3100) transmits the message to a second device (e.g., 3104) (e.g., that the user 3116 is within audible output range of) of the set of devices (e.g., 3100, 3102, and 3104). For example, as shown in
In some embodiments, the audible output range of a device (e.g., 3100) is based on one or more of: other detectable indicia of a user presence or location, including footsteps (e.g., determining and detecting a footstep pattern associated with a user, tracking the location of a set of footsteps as they move around (e.g., which are presumed to be the user), determining and detecting a breathing pattern of the user, using a visual detection mechanism (e.g., a motion sensor, a camera), or the like.
As described below, method 3200 provides an intuitive way for outputting an audible output based on user location. The method reduces the cognitive burden on a user for outputting an audible output based on user location, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to outputting an audible output based on user location faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 3100), which is a first device of a set of devices (e.g., 3100, 3102, and 3104) associated with a first user account: receives (3202) an audible output trigger event. In some embodiments, an audible output trigger event is any data configured to cause a device to output an audible output in response to a trigger event. In some embodiments, an audible output trigger events is one or more of: a notification (e.g., alarm/timer/reminder) for a particular time (e.g., 5:00 PM) or some length of time in the future (e.g., in 30 minutes). In some embodiments, an audible output trigger event is a device notifications setting.
The first device (e.g., 3100) determines (3204) that a first user (e.g., 3108), associated with the first user account, is located within an audible output range (e.g., 3100A, 3102A, and/or 3104A) of a device of the set of devices. In some embodiments, an audible output range is independent for each device (or is not affected by whether there are other devices in the set of devices). For example, each device has an “fixed” proximity range, so a user (e.g., 3108) can be out of range of each device in a set of devices. In some embodiments, the audible output range of a device is relative or otherwise affected by other devices in the set of devices. For example, the user may always be within the audible output range of the closest (most proximate) device of the set (e.g., closest device responds, even if it is in the next room or 100 meters away; a shown in
In accordance with a determination that the first user (e.g., 3108) is within the audible output range of the first device (e.g., 3100), and in accordance with an occurrence of the audible output trigger event, the first device (e.g., 3100) outputs (3206) an audible output (e.g., 3110 as shown in
Using a determination of whether the physical position of a user is within an audible output range of a device provides the user with an easy technique for receiving output from appropriately positioned devices without extraneous user inputs. Performing an operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In accordance with a determination that the first user is within the audible output range of a second device (e.g., 3102 as shown in
In some embodiments, the device (e.g., 3102) of the set of devices is a second device, and wherein outputting the audible output comprises transmitting (3210) an instruction to the second device (e.g., 3102) to output the audible output (e.g., 3110 as shown in
In some embodiments, outputting the audible output includes playing (3212) an audible tone (e.g., a sound, or voice dictation). In some embodiments, the device also outputs a visual output (e.g., using an LED or a display).
In some embodiments, receiving the audible output trigger event comprises receiving (3214) user input representing configuration of the audible output trigger event (e.g., setting a timer, an alarm, or reminder; or setting up notification or phone call output settings).
In some embodiments, receiving the audible output trigger event comprises receiving (3216) data representing audible output settings associated with the first user account (e.g., whether to push one or more of: phone calls, text message notifications, email notifications, etc., to the first device (e.g., for audible output)).
In some embodiments, the audible output range of the first device is based on one or more of (3218): a detected physical proximity (e.g., distance) of the first device to the first user; a detected presence of the first user in the same room as the first device; and the output characteristics of the first device (e.g., speaker output power).
In some embodiments, determining that the first user is located within the audible output range of the device of the set of devices comprises one or more of the following (3220): detecting (3222), at the device (e.g., 3100), a voice associated with the first user (e.g., 3112 or 3114) (e.g., within a threshold time before the notification trigger event, indirectly (e.g., overhearing user), or directly (e.g., user interacts with device with a voice command)); detecting (3224), at the device, a third device (e.g., a personal device) associated with the user, wherein the third device is not a member of the set of devices (e.g., the device is the user's personal phone, and is not part of a group of stationary devices (e.g., devices 3100, 3102, and 3104)); and receiving a signal (3226), from an external sensor (e.g., a sensor on an external device, or a sensor on the device), representative of the first user being physically near the device (e.g., motion sensor, camera).
In some embodiments, subsequent to outputting the audible output (3228): in accordance with a determination that the first user (e.g., 3108) is within an audible output range of a fourth device (e.g., 3106) that is not a member of the set of devices (e.g., 3100, 3102, and 3104), and in accordance with an occurrence of the audible output trigger event, the first device (e.g., 3100) forgoes outputting (3228) the audible output. For example, the user has entered their car in the garage (e.g., which is connected to the set of devices), and the set of devices forgoes outputting the audible output even though the user is still be within range of a device of the set of devices.
In some embodiments, the first device (e.g., 3100) plays back media content. Further in accordance with a determination that the first user is within the audible output range of the fourth device (e.g., 3106) that is not a member of the set of devices, ceasing playback of the media content.
Note that details of the processes described above with respect to method 3200 (e.g.,
As described above with respect to
A user may desire to listen to the media content, currently being played back by the living room devices, on a device (e.g., 3300) in the kitchen. In some embodiments, user input (e.g., voice input 3314) is received at a device (e.g., 3300) connected to the set of devices (e.g., 3302, 3304, 3306, and 3308) playing back media content (e.g., the movie “Super Heroes”). In some embodiments, in response to the user input, a new device (e.g., 3300) that is not currently part of the media session initiates output of a signal representative of the media. For example, user input received at any device that is connected to the living room devices (or is part of the living room set of devices) can be used to add the kitchen device 3300 to the “Super Heroes” media session that includes the living room devices. In some examples, the user input is voice user input. For instance,
In some embodiments, a signal representative of media includes a video component and/or an audio component. In some embodiments, a device initiates output of one or more of the video component and the audio component. For example, as described above, the audio portion of a media session was forwarded to a new device (e.g., 3300) in response to a user request. In some examples, a video portion of the media can be forwarded to a device in response to a user request (e.g., “Hey Siri, let me watch the movie on the display in the kitchen”). Likewise, in some examples, both the audio and video portions can be forward to a device (e.g., “Hey Siri, let me watch the movie in the home theater room.”)
In some embodiments, a device (e.g., 3300), that is not a member of the set of devices (e.g., 3302, 3304, 3306, and 3308) currently playback back media, initiates output of a component of the media in response to a user input (e.g., 3314), and the set of devices ceases to output that portion. For example,
As described below, method 3400 provides an intuitive way for controlling media playback. The method reduces the cognitive burden on a user for controlling media playback, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to control media playback faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 3300) (also referred to as a “first device”) receives (3402) a user input voice command (e.g., represented by voice input 3314) representing a request to output a signal (e.g., audio output 3312 of
In response to receiving the user input, the first device (e.g., 3300) transmits (3404) a request for information regarding the media currently being played back by the second device (e.g., 3302 or 3304). In some embodiments, the request is transmitted to the second device. In some embodiments, the request is transmitted to a device different than the second device. For instance, in some examples, the first device transmits the request to a primary device for the media session currently playing back on the second device. In some embodiments, the request is a request for one or more of: a media stream of the media, a location where the first device can stream the media from (e.g., a URL, a media service usable to access the media, login credentials for the media service, or the like), or an identification that the first device can use to locate a source of the media (e.g., identifying information of the media, such as a title, a unique number, or the like).
The first device (e.g., 3300) receives (3406) the information regarding the media currently being played back by the second device. For example, the second device (e.g., or a primary device for the media session that includes the second device) received the request, and in response, transmitted the information regarding the media to the first device.
In accordance with receiving the information regarding the media currently being played back by the second device, and while the second device continues playback of at least one component of the media, the first device (e.g., 3300) initiates (3408) output of at least one component (e.g., audio component and/or video component) of the signal representative of the media currently being played back by the second device (e.g., as shown in
Using a voice command to cause a device to initiate playback of a component representative of media currently playing back on another device, wherein the other device continues playing back a component representative of the media, provides the user an efficient user interface to manage the devices that are included in a media playback session that requires fewer user inputs. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the signal representative of the media currently being played back by the second device includes (3410) one or more of: an audio signal, a video signal, or both.
In some embodiments, the media currently being played back by the second device (e.g., 3302 or 3304) includes a video component and an audio component, and initiating output of the at least one component of the signal representative of the media currently being played back by the second device comprises initiating output (3412) of the audio component without initiating output of the video component (e.g., as shown in
In some embodiments, the second device (e.g., 3302 or 3304) continues playback of both the video component and the audio component subsequent to the first device initiating output of the at least one component of the signal (e.g., as shown in
In some embodiments, the second device (e.g., 3302 or 3304) continues playback of the video component and ceases playback of the audio component subsequent to the first device initiating output of the at least one component of the signal (e.g., as shown in
In some embodiments, initiating output of at least one component of the signal representative of the media currently being played back by the second device comprises playing back (3414), by the first device (e.g., 3300), the at least one component of the signal representative of the media currently being played back by the second device (e.g., 3302 or 3304). For example, the first device 3300 receives the user input voice command 3314 and, in response, begins output of the audio component of the media session.
In some embodiments, initiating output of the at least one component of the signal representative of the media currently being played back by the second device comprises transmitting an instruction (3416), to a third device (e.g., connected to the first device), to initiate output of the at least one component of the signal representative of the media currently being played back by the second device. For example, the first device 3300 receives the user input voice command 3314 and, in response, causes a third device to output the audio component of the media session. For instance, the third device can be one or more personal listening device, such as headphones. In some examples, the third device does not include the ability to process the user input (e.g., the third device does not include a microphone) but the user requests that output begin on the third device—thus, the first device receives the user input, but causes output on (e.g., provides a media stream to) the third device. In some embodiments, the first and third devices are connected via a wired or wireless connection (e.g., Bluetooth, or the like).
In some embodiments, the media currently being played back by the second device is being played back in a first natural language (e.g., English), and transmitting the instruction, to the third device, to initiate output of the at least one component of the signal representative of the media currently being played back by the second device comprises transmitting an instruction to initiate output of the at least one component of the signal being played back by the second device in a second natural language (e.g., Spanish) different than the first natural language. For example, the first device causes the third device (e.g., headphones) to output audio (e.g., movie dialogue) in a different language. Thus, for example, when one or more users are watching a movie in a first language, another user can concurrently watch the same movie and while listening to audio in another language using headphones.
In some embodiments, the user input voice command (e.g., 3314) is a first user input, and the first device (e.g., 3300) receives a second user input representing a playback control command. For example, as described above, a playback control command is a command for controlling media playback such as pause, next track, seek, or the like. In response to receiving the second user input, the first device (e.g., 3300) transmits the playback control command to the second device (e.g., 3304). For example, if the first device is not a primary device for the media session and the second device (e.g., 3302 or 3304) is the primary device, the first device forwards the playback control command to the primary device for processing. In some embodiments, the first device forgoes performing the playback control command. In some embodiments, the first device subsequently receives an instruction from the second device to perform the playback command. For example, the second device processes the playback control command and transmits an instruction to the first device to alter playback in accordance with the command. In some examples, relying on the primary device for processing of a command helps maintain synchronization between the devices in the media session when the first device is independently streaming the content (e.g., synchronizing whether to perform a responsive action, the timing of a responsive action, etc.). That is, when the second device is not providing a media stream to the first device, the first and second devices must coordinate their action responsive to the playback control command—otherwise, media playback on each device my become unsynchronized, which is undesirable for users.
In some embodiments, receiving the information regarding the media currently being played back by the second device comprises receiving one or more of: an identifier of the media (e.g., so the first device can determine if it has access to the media), a location where the signal representative of the media is accessible (e.g., a location or media streaming service, a URL, or the like), and a media stream of the signal representative of the media (e.g., the second device provides media stream to the first device). In some embodiments, the first device receives the information (e.g., an audio stream) from the second device. In some embodiments, the first device receives the information from a fourth device, different than the second device).
In some embodiments, receiving the information regarding the media currently being played back by the second device comprises the first device (e.g., 3300) receiving, from a fourth device (e.g., 3308), a media stream of the at least one component of the signal representative of the media the media currently being played back by the second device. For example, a fourth device (e.g., a primary device to the second device, or a device close to the first device that is part of the media session), can provide an audio stream to the first device of the media currently playing back on the second device. In some embodiments, the first device receives the information regarding the media from the fourth device.
Note that details of the processes described above with respect to method 3400 (e.g.,
In some embodiments, a device (e.g., 3500) receives user input (e.g., 3512) requesting playback on a set of devices (e.g., 3502, 3504, 3506, and 3508) that does not include the device. As shown in
In some embodiments, a device (e.g., 3500) performs a voice assistant function while concurrently providing a media stream to a set of devices (e.g., 3502, 3504, 3506, and 3508). In some embodiments, a device (e.g., 3500) performs a phone call function while concurrently providing a media stream to a set of devices (e.g., 3502, 3504, 3506, and 3508).
In some embodiments, a device (e.g., 3500) provides a plurality of different media streams concurrently.
In some embodiments, another device (e.g., 3516) adds a new device (e.g., 3518) to the set of devices (e.g., 3502, 3504, 3506, and 3508).
As described below, method 3600 provides an intuitive way for managing playback of media on a set of devices. The method reduces the cognitive burden on a user for managing playback of media on a set of devices, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manage playback of media on a set of devices faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 3500) (also referred to as a “first device”) receives (3602) a request (e.g., user input 3512) to initiate media playback on a set of devices (e.g., 3502, 3504, 3506, and 3508) that does not include the first device. In some embodiments, the set of devices includes one or more devices. For example, device 3500 receives user input at a multi-device interface 3510 to initiate playback of media on the “Bedroom”, “Kitchen”, and “Living Room” devices (e.g., 3502, 3504, 3506, and 3508) that are connected to the first device.
In response to receiving the request, and while the first device is coordinating media playback, the first device (e.g., 3500) determines (3604) whether the set of devices includes a device configured to coordinate media playback. For example, device 3500 determines whether any device in the set of devices 3502, 3504, 3506, and 3508 include a device that is capable of becoming a primary device (e.g., as described above with respect to
In accordance with a determination that the set of devices includes a device configured to coordinate media playback (e.g., is a smart group), the first device (e.g., 3500) transfers (3606) a media playback coordination task from the first device to the device (e.g., 3504 as shown
Transferring a media playback coordination task, for media playback that does not include the first device, from a first device to another device configured to coordinate media playback, subsequent to the first device receiving user input, allows the first device to free up device resources and provide an improved response to further user input requests, without requiring further user input to do so. Performing an operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In accordance with a determination that the set of devices does not include a device configured to coordinate media playback, the first device (e.g., 3500) forgoes (3608) transferring the media playback coordination task (e.g., as shown in
In some embodiments, the media playback coordination task is selected from the group consisting of: storing a media playback queue, providing a media stream to one or more devices in the set of devices during media playback, transmitting data indicating that the media stream is available (e.g., advertise to other devices that it is the primary device), synchronizing playback between devices of the set of devices, and a combination thereof. In some embodiments, the media playback coordination task includes other playback coordination tasks. Additional examples of playback coordination tasks are described above (e.g., with respect to
In some embodiments, further in accordance with a determination that the set of devices does not include a device configured to coordinate media playback (3610), the first device (e.g., 3500) detects (3612) a second device (e.g., 3514), connected to the first device and the set of devices, and not included in the set of devices, that is configured to coordinate media playback. In accordance with detecting the second device, the first device (e.g., 3500) transfers (3614) the media playback coordination task from the first device to the second device. For example, device 3500 hands off primary device responsibility to a home media hub device (e.g., such as device 3514 of
In some embodiments, further in accordance with a determination that the set of devices does not include a device configured to coordinate media playback, the first device (e.g., 3500) performs (3616) the media playback coordination task. For example, device 3500 retains primary device responsibility (e.g., as shown in 35E), and thus performs a media playback coordination task as part of its role as primary device for the media session on the set of devices.
In some embodiments, performing the media playback coordination task comprises providing a media stream to one or more devices in the set of devices during media playback, and while providing the media stream to one or more devices in the set of devices during media playback, the first device (e.g., 3500) receives (3618) a request to perform a voice assistant function or a phone call function. In response to the request (3620) to perform a voice assistant function or a phone call function the first device (e.g., 3500): performs (3622) the voice assistant function or the phone call function, and continues (3624) to provide the media stream to one or more devices in the set of devices during media playback while performing the voice assistant function or the phone call function. In some embodiments, a request to perform a voice assistant function is a user input. For example, device 3500 receives voice user input, such as “Hey Siri”, which invokes a personal digital assistant. In some embodiments, request to perform a phone call function is a user input. For example, device 3500 can receive user input representing a request to begin a phone call (e.g., a request to answer an incoming call, or a request to place an outgoing call). In some embodiments, a phone call this includes one or more of a telephone call, a voice over internet protocol (“VoIP”) call, a video call (e.g., video chat, FaceTime, Skype, or the like), an internet-based call (e.g., a “Wi-Fi Calling” call), or the like. Thus, in accordance with some embodiments, the first device can perform other functions such as making a telephone call or using a voice assistant, without interrupting the media stream.
In some embodiments, performing the media playback coordination task comprises providing a media stream to one or more devices in the set of devices during media playback, wherein the media stream is a first media stream, and wherein the set of devices is a first set of devices. While providing the first media stream, the first device (e.g., 3500) concurrently provides (3626) a second media stream, different than the first media stream to a second set of devices different than the first set of devices (e.g., as shown in
In some embodiments, performing the media playback coordination task comprises providing a media stream to one or more devices in the set of devices during media playback, and while providing the media stream to one or more devices in the set of devices during media playback, the first device (e.g., 3500) receives (3628) an indication that a third device (e.g., 3516) added a new device (e.g., 3518 as shown in
In some embodiments, further in accordance with a determination that the set of devices does not include a device configured to coordinate media playback, the first device (e.g., 3500) receives a playback control command. In response to receiving the playback control command, the first device (e.g., 3500) transmits an instruction to the set devices in accordance with the playback control command. For instance, in some examples, the first device has media playback coordination responsibility (e.g., is a primary device) for the set of devices, and thus processes the playback control command and issues instructions to one or more devices in the set of devices to perform the appropriate corresponding action.
In some embodiments, receiving the playback control command comprises receiving user input, at the first device, representing the playback control command. For example, the first device receives the playback control command via user input.
In some embodiments, receiving the playback control command comprises receiving, from a device other than the first device, data representing the playback control command. For example, the first device receives the playback control command from another device that received input on a proximity card or other interface for controlling media playback.
In some embodiments, further in accordance with a determination that the set of devices includes a device configured to coordinate media playback, the first device (e.g., 3500) receives a playback control command, and in response to receiving the playback control command, the first device (e.g., 3500) forwards the playback control command to the device (e.g., 3504 of
In some embodiments, further in accordance with a determination that the set of devices includes a device configured to coordinate media playback, the first device (e.g., 3500) transmits a playback queue to the device configured to coordinate media playback. For example, if the request to initiate playback received at the first device is a request to play a playlist (e.g., a plurality of songs), the playlist is forwarded to the primary device of the set of devices.
In some embodiments, the request to initiate media playback is a request to initiate playback of first media (e.g., a song, playlist, movie, or the like). Further in accordance with a determination that the set of devices includes a device configured to coordinate media playback (3632), and in accordance with a determination that the device configured to coordinate media playback has access to the first media, the first device (e.g., 3500) transfers (3634) the media playback coordination task from the first device to the device (e.g., 3504 of
In some embodiments, the set of devices includes a plurality of devices configured to coordinate media playback, and further in accordance with a determination that the set of devices includes a device configured to coordinate media playback, the first device (e.g., 3500) selects a primary device from the plurality of devices configured to coordinate media playback, and transmits the media playback coordination task from the first device to the selected primary device. For example, when the set of devices includes multiple potential primary devices (e.g., that are configured to coordinate media playback), the first device selects one of the devices to act as the primary device for the media session.
In some embodiments, the first device (e.g., 3500) selects a designated heir (e.g., 3502 of
In some embodiments, the set of devices includes a plurality of devices configured to coordinate media playback, and further in accordance with a determination that the set of devices includes a device configured to coordinate media playback, the first device (e.g., 3500) receives, from a fourth device (e.g., 3514), selection of a primary device from the plurality of devices configured to coordinate media playback, and the first device (e.g., 3500) transmits the media playback coordination task from the first device to the primary device (e.g., 3504 of
In some embodiments, the first device (e.g., 3500) transmits an instruction to the set of devices to initiate media playback. For example, the first device transmits an instruction to initiate playback, of the requested media, to the set of devices.
In some embodiments, the first device (e.g., 3500) transmits a copy of a media playback queue to at least two devices of the set of devices. For example, the first device transmits a playback queue to non-primary devices of the set of devices. In some examples, a copy of a media playback queue is stored on multiple devices of the set of devices during the media session that includes the set of devices.
Note that details of the processes described above with respect to method 3600 (e.g.,
In some embodiments, a device (e.g., 3700) receives user input (e.g., 3712) requesting playback on a set of devices that does not include the device. As shown, device 3700 received user input 3712, which is request to initiate playback on devices 3702, 3704, 3706, and 3708 (shown in
In this example, each set of characteristics includes a “Power Source” characteristic, which identifies a power source of the device—for example, whether the respective device is operating on battery power or is plugged in (e.g., is operating on wall power or is otherwise charging). For example, the power source of the respective device can be a characteristic that is considered when selecting a primary device to perform playback coordination tasks, which can require an increase in power consumption by a device (e.g., due to increased data transmission activity that results from providing a media stream to the set of devices).
In this example, each set of characteristics also includes a “Network Performance” characteristic, which can include one or more indications of the quality of a respective device's connection to a network (e.g., a local area network that connects each device in the set of devices, a connection to a wide area network, or the like). For example, the network performance of the device can be a characteristic that is considered when selecting a primary device to perform playback coordination tasks, which can require an increased demand on network activity by a device (e.g., due to increased data transmission activity that results from providing a media stream to the set of devices).
In this example, each set of characteristics also includes an indication of the quality of connection between the respective device and each device in the set of devices included in the requested media session. These are identified variously as “Connection to Kitchen Device” (e.g., device 3702), “Connection to Living Room Device 1” (e.g., device 3704), “Connection to Living Room Device 2” (e.g., device 3706), and “Connection to Bedroom Device” (e.g., device 3708). For example, the quality of connection between a respective device and each device in the set of devices can be a characteristic that is considered when selecting a primary device to perform playback coordination tasks, which can require the selected primary device to transmit data to each device in the set of devices (e.g., to provide a media stream).
In some embodiments, a device (e.g., 3700) selects, based at least in part on the one or more characteristics of each device of the plurality of devices (e.g., 3702, 3704, and 3706) configured to coordinate media playback, a primary device from among the plurality of devices configured to coordinate media playback on a set of devices (e.g., 3702, 3704, 3706, and 3708). As shown in
In some embodiments, the plurality of devices (e.g., 3702, 3704, 3706, and 3716) includes one or more devices (e.g., 3716) not included in the set of devices (e.g., 3702, 3704, 3706, and 3708).
As described below, method 3800 provides an intuitive way for managing playback of media on a set of devices. The method reduces the cognitive burden on a user for managing playback of media on a set of devices, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to manage playback of media on a set of devices faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 3700) receives (3802) a request (e.g., user input 3712) to initiate media playback on a set of devices (e.g., 3702, 3704, 3706, and 3708 of
In response to receiving the request, and while the device is coordinating media playback, the electronic device (e.g., 3700) determines (3804), for each device of a plurality of devices (e.g., 3702, 3704, and 3706) configured to coordinate media playback and connected to the set of devices (e.g., 3702, 3704, 3706, and 3708), one or more device characteristics For example, the set of devices includes multiple devices capable of becoming a primary device (e.g., multiple smart devices). In some embodiments, the plurality of devices includes the device (e.g., 3700). In some embodiments, the plurality of devices includes one or more devices that are not the device and that are not included in the set of devices (e.g., 3716 of
The electronic device (e.g., 3700) selects (3806), based at least in part on the one or more characteristics (e.g., as shown in
The electronic device (e.g., 3700) transfers (3808) a media playback coordination task from the device to the primary device (e.g., 3704 of
Transferring a media playback coordination task from a device to another device configured to coordinate media playback based on one or more device characteristics, subsequent to the device receiving user input, allows the device to free up device resources and provides an optimized delegation of a media playback coordination task, without requiring further user input to do so. Performing an operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the selected primary device (e.g., 3716, as shown in
In some embodiments, the selected primary device (e.g., 3704 of
In some embodiments, the one or more characteristics is selected from the group consisting of (3814): whether the respective device is operating on battery power, a network performance characteristic (e.g., signal strength, bandwidth, throughput, error rate of a network connection) of the respective device, a quality of connection of the respective device to the each device in the set of devices, and a combination thereof. In some embodiments, a quality of connection of the respective e device is based on a measure of proximity to a device in the set of devices. In some examples, other characteristics are used to select a primary device.
In some embodiments, the electronic device (e.g., 3700) selects (3816) a designated heir to the primary device from the plurality of devices configured to coordinate media playback.
In some embodiments, the electronic device (e.g., 3700) transmits an instruction to initiate media playback to the set of devices.
In some embodiments, the electronic device (e.g., 3700) transmits (3818) a copy of a media playback queue to the selected primary device. In some embodiments, the electronic device (e.g., 3700) transmits a copy of the media playback queue to two or more devices (e.g., including at least one non-primary device) in the set of devices.
In some embodiments, the request to initiate media playback is a request to initiate playback of first media (e.g., a song, playlist, movie, or the like), and wherein transferring the media playback coordination task from the device to the selected primary device is further in accordance with a determination that the selected primary device has access to the first media (3820). For example, the device forgoes handoff of primary device responsibility to a selected primary device if such device does not have access to the first media.
In some embodiments, the electronic device (e.g., 3700) receives a playback control command, and in response to receiving the playback control command, forwards the playback control command to the selected primary device. For example, a device that is not the primary device forwards the playback control command to the primary device for processing. In some embodiments, the playback control command is received via user input at the device. In some embodiments, the playback control command is received from another device.
In some embodiments, the media playback coordination task is selected from the group consisting of (3822): storing a media playback queue, providing a media stream to one or more devices in the set of devices during media playback, transmitting data indicating that the media stream is available (e.g., advertise to other devices (e.g., in the set of devices) that it is the primary device), synchronizing playback between devices of the set of devices, and a combination thereof. In some embodiments, the device transfers all or fewer than all playback coordination tasks that would otherwise be performed by a primary device.
Note that details of the processes described above with respect to method 3800 (e.g.,
As described below, method 3900 provides an intuitive way for configuring a second device. The method reduces the cognitive burden on a user for configuring a second device, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to configure a second device faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 1900) (also referred to as a “first device”) establishes (3902) a communication link with a second device (e.g., 1906). Subsequent to establishing the communication link with the second device, the first device (e.g., 1900) initiates (3904) a configuration process (e.g., as shown in
In some embodiments, during the configuration process (3906): the first device (e.g., 1900) displays (3908), on the display, a configuration user interface that includes a prompt to select a location (e.g., “Where is this speaker?” as shown in
In some embodiments, during the configuration process (3906): the first device (e.g., 1900) detects (3914) an audio tone signal (e.g., 1014 of
In some embodiments, the first device (e.g., 1900) detects an indication that a physical proximity between the first device and the second device the first device (e.g., 1906) satisfies a proximity condition; and in response to detecting the indication that the physical proximity between the first device and the second device satisfies the proximity condition, establishes the communication link with the second device.
Using an audio tone to establish a communication link between two devices allows the user to efficiently move through a configuration process for a device with fewer required user inputs, while ensuring that the devices are in relatively close proximity and that the user has physical access to both devices. Providing an optimized configuration process to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. In some embodiments, the audio tone signal is a first audio tone signal, the method further comprising: further in response to detecting the indication that the physical proximity between the first device and the second device satisfies the proximity condition, outputting a second audio tone signal.
In some embodiments, proceeding to the next step of the configuration process includes completing the configuration process (e.g., proceeding to display setup card 1942 of
In some embodiments, the audio tone signal (e.g., 1904) is generated by the second device (e.g., 1906 as shown in
In some embodiments, the audio tone signal includes an audio passcode. In some embodiments, the audio passcode is dictated (e.g., as shown in
In some embodiments, the audio tone signal (e.g., 1904) is received while the first device (e.g., 1900) is physically positioned within a threshold physical proximity (e.g., 1908 of
In some embodiments, the audio tone signal is a first audio tone signal, and during the configuration process (e.g., while displaying setup card 1918 of
In some embodiments, further in response to receiving the user input selection (e.g., 1913) of the location (e.g., “John's Room” as shown in
In some embodiments, the first device (e.g., 1900) receives user input (e.g., 1923) representing an affirmative request create the device group. In some embodiments, in response to the user input representing an affirmative request create the device group, the first device (e.g., 1900) displays, on the display, a configuration user interface (e.g., 1924 of
In some embodiments, the prompt to select a location includes a plurality of predetermined location identifiers (e.g., Kitchen, Bedroom, Patio, Dining Room, as shown in
In some embodiments, the plurality of predetermined location identifiers includes a user-defined location identifier (e.g., John's Room, as shown in
In some embodiments, the prompt to select a location includes a field (e.g., “Create New Room” option as shown in
In some embodiments, during the configuration process (3932): the first device (e.g., 1900) displays (3934), on the display (e.g., 1902), a configuration user interface (e.g., setup card 1914 of
In some embodiments, prior to transmitting the user account information to the second device, and in accordance with a determination that the first device (e.g., 1900) is not currently logged into a user account associated with the user account information (e.g., is not currently logged into an iCloud account), the first device (e.g., 1900) displays, on the display (e.g., 1902), a prompt to log in to the user account (e.g., setup card 1932 that includes the text “Please login to your iCloud account to continue” as shown in
In some embodiments, in response to progressing from a first step (e.g., setup card 1912) in the configuration process to a second step (e.g., setup card 1914) in the configuration process, the first device (e.g., 1900) outputs a fourth audio tone signal (e.g., 1044 of
In some embodiments, in response to progressing from the second step (e.g., setup card 1914) in the configuration process to a third step (e.g., setup card 1916) in the configuration process, the first device (e.g., 1900) outputs a sixth audio tone signal (e.g., 1048 of
In some embodiments, subsequent to initiating the configuration process, the first device (e.g., 1900) receives data regarding an output of an operation being performed by the second device (e.g., 1906). For example, the output can be audio output (e.g., dictation by a voice assistant) by device 1906 of media (e.g., music), weather information, news, calendar appointments, or the like. In response to receiving the data regarding the output of the operation being performed by the second device (e.g., 1906), the first device (e.g., 1900) displays a user interface (e.g., interface 1950 of
Displaying a user interface that includes a representation of the output of the operation being performed by the second device, provides the user with visual feedback about the state of a state of the second device. Providing improved visual feedback to the user enhances the operability of the second device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the operation being performed by the second device (e.g., 1906) includes audibly outputting information (e.g., playing the song identified in interface 1950), wherein receiving the data regarding the output of the operation being performed includes receiving data representing the information (e.g., song title, elapsed play time, weather forecast data, news stories), and wherein displaying the user interface, that includes the representation of the output of the operation being performed by the second device, includes displaying (e.g., interface 1950) at least a portion of the data representing the information.
Displaying data representing information corresponding to information being audibly outputted by the second device provides the user with visual feedback about the state of the second device, in addition to the audio feedback being provided directly by the second device. Providing improved (e.g., supplemental or additional) visual feedback to the user enhances the operability of the second device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the information includes a media item (e.g., a song), and the operation being performed by the second device (e.g., 1906) includes audibly outputting the media item. In some embodiments, displaying the data representing the information includes displaying one or more of: an artist, a media item name, an album name, album art, and a media playback progress indicator (e.g., as shown in interface 1950 of
Displaying additional data (e.g., one or more of artist, a media item name, an album name, album art, and a media playback progress indicator) that corresponds to a media item being audibly outputted by the second device provides the user with visual feedback about the state of the second device. Providing improved (e.g., supplemental or additional) visual feedback to the user enhances the operability of the second device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the user interface that includes the representation of the output of the operation being performed by the second device includes displaying one or more of news information or weather information.
In some embodiments, during the configuration process: in accordance with a first configuration setting of the first device being compatible with the second device (e.g., 1906), the first device (e.g., 1900) configures the second device (e.g., 1906) to include the first configuration setting. For example, a configuration setting can be a language setting for a voice assistant, and a first configuration setting can be “English (U.S.)” In this example, English (U.S.) is compatible with (e.g., supported by) a voice assistant on device 1906. In some embodiments, the configuration is done automatically, without requiring user input or confirmation. In accordance with the first configuration setting of the first device not being compatible with the second device (e.g., 1906), the first device (e.g., 1900) displays an indication that the first configuration setting is not compatible with the second device (e.g., displays a message). In some embodiments, the indication that the first setting is not compatible with the second device is the display of a setup card for selecting a different/compatible setting (e.g., setup card 1960 of
Using a first configuration setting of the first device that is compatible with the second device allows the user to efficiently move through a configuration process for a device with fewer required user inputs, providing an optimized configuration process. Providing an optimized configuration process to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, further in accordance with the first configuration setting of the first device being compatible with the second device (e.g., 1906), the first device (e.g., 1900) displays a configuration user interface that includes a prompt requesting acceptance of the first configuration setting for the second device. In response to receiving user input accepting the first configuration setting for the second device (e.g., 1906), the first device (e.g., 1900) configures the second device to include the first configuration setting.
Displaying a configuration user interface that includes a prompt requesting acceptance of the first configuration setting for the second device, provides the user with visual feedback about the state of the second device (e.g., that it is compatible with the first configuration setting). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first configuration setting is a setting disabling a device feature (e.g., a voice assistant), and wherein a second configuration setting is a setting enabling the device feature (e.g., a voice assistant). In accordance with a determination that the configuration process requires enabling the device feature on the second device (e.g., 1906): the first device (e.g., 1900) displays an indication that the device feature will be enabled on the second device (e.g., setup card 1958 of
Displaying an indication that the device feature will be enabled on the second device (e.g., even when it is disabled on the first device) provides the user with visual feedback about the state of the second device (e.g., that the feature is required on the second device). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the indication that the device feature will be enabled on the second device (e.g., 1906) includes displaying an indication that the device feature will remain disabled on the first device.
Displaying an indication that the feature will remain disabled on the first device provides the user with visual feedback about the nature of the operation and the state of the first device (e.g., that enabling the feature on the second device will not alter the state of the first device, as to the feature). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, further in accordance with the first configuration setting of the first device not being compatible with the second device (e.g., 1906), the first device (e.g., 1900) displays a configuration user interface (e.g., 1960 of
Displaying a configuration user interface that includes a prompt requesting selection of a third configuration setting compatible with the second device reduces the number of inputs needed to configure the second device by surfacing compatible options to the user and provides an optimized configuration process. Providing an optimized configuration process to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, prior to establishing the communication link connecting the first device and the second device (e.g., 1906), the first device (e.g., 1900) detects an indication that a physical proximity between the first device and the second device satisfies a proximity condition (e.g., as shown in
Using an indication that the physical proximity between the first device and the second device satisfies the proximity condition in order to output an audio tone signal provides the user with auditory feedback regarding the state of the first device. For example, when there are other potential devices in proximity that are configurable, the audio tone signal can indicate which device will be configured. Providing improved feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, subsequent to transmitting the user account information to the second device (e.g., 1906), the first device (e.g., 1900) displays a configuration user interface (e.g., 1948 of
Displaying a configuration user interface associated with a voice assistant that includes a prompt to provide user voice input invoking one or more functions of the voice assistant provides the user with information regarding the capabilities and state of a device. Providing such information to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, in accordance with a determination that user voice input invoking one or more of the features of the voice assistant has been received by either the first device or the second device (e.g., 1906), the first device (e.g., 1900) maintains display of the configuration user interface (e.g., 1948) associated with the voice assistant. In response to receiving user input selection of an affordance (e.g., affordance labeled “Done” in setup card 1948) included in the configuration user interface associated with the voice assistant, the first device (e.g., 1900) ceases display of the configuration user interface associated with the voice assistant (e.g., setup card 1948 slides off the display, as shown in
Note that details of the processes described above with respect to method 3900 (e.g.,
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the 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. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery to users of invitational content or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information.
The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.
The present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select to not provide precise location information, but permit the transfer of location zone information.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publicly available information.
This application is a continuation of U.S. patent application Ser. No. 17/835,110, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL,” filed on Jun. 8, 2022, which is a continuation of U.S. patent application Ser. No. 17/461,103, entitled “METHODS AND INTERFACES FOR INITIATING MEDIA PLAYBACK,” filed on Aug. 30, 2021, which is a continuation of U.S. patent application Ser. No. 17/031,833, entitled “METHODS AND INTERFACES FOR ADJUSTING THE VOLUME OF MEDIA,” filed on Sep. 24, 2020, which is a continuation of U.S. patent application Ser. No. 16/807,604, entitled “METHODS AND INTERFACES FOR CONFIGURING A DEVICE IN ACCORDANCE WITH AN AUDIO TONE SIGNAL,” filed on Mar. 3, 2020, which is a continuation of U.S. patent application Ser. No. 16/702,968, entitled “METHODS AND INTERFACES FOR ADJUSTING AN AUDIBLE SIGNAL BASED ON A SPATIAL POSITION OF A VOICE COMMAND SOURCE,” filed on Dec. 4, 2019, which is a continuation of U.S. patent application Ser. No. 15/910,263, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL,” filed on Mar. 2, 2018, which claims priority to U.S. provisional patent application 62/507,202, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL,” filed on May 16, 2017, U.S. provisional patent application 62/507,208, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL,” filed on May 16, 2017, U.S. provisional patent application 62/514,932, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL,” filed on Jun. 4, 2017, and U.S. provisional patent application 62/622,122, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL,” filed on Jan. 25, 2018. The contents of each of which are hereby incorporated by reference in their entirety. This application also relates to Denmark Patent Application No. PA 2017 70392, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL”, filed on May 29, 2017, Denmark Patent Application No. PA 2017 70401, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL”, filed on May 29, 2017, Denmark Patent Application No. PA 2017 70402, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL”, filed on May 29, 2017, Denmark Patent Application No. PA 2017 70403, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL”, filed on May 29, 2017, Denmark Patent Application No. PA 2017 70404, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL”, filed on May 29, 2017, Denmark Patent Application No. PA 2017 70406, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL”, filed on May 29, 2017, Denmark Patent Application No. PA 2017 70408, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL”, filed on May 29, 2017, Denmark Patent Application No. PA 2017 70409, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL”, filed on May 29, 2017, and Denmark Patent Application No. PA 2017 70410, entitled “METHODS AND INTERFACES FOR HOME MEDIA CONTROL”, filed on May 29, 2017, the contents of each of which are hereby incorporated by reference in their entirety. This application also relates to the U.S. patent application Ser. No. 14/300,120 entitled “MULTI-CHANNEL LOUDSPEAKER MATCHING VARIABLE DIRECTIVITY,” filed on Jun. 9, 2014, the content of which is hereby incorporated by reference in its entirety, and included in the Appendix. This application also relates to the U.S. patent application Ser. No. 14/732,711 entitled “MULTI-MICROPHONE SPEECH RECOGNITION SYSTEMS AND RELATED TECHNIQUES,” filed on Jun. 6, 2015, the content of which is hereby incorporated by reference in its entirety, and included in the Appendix. This application also relates to the U.S. patent application Ser. No. 14/732,715 entitled “MULTI-MICROPHONE SPEECH RECOGNITION TECHNIQUES AND RELATED SYSTEMS,” filed on Jun. 6, 2015. This application also relates to the U.S. patent application Ser. No. 14/869,760 entitled “MODAL BASED ARCHITECTURE FOR CONTROLLING THE DIRECTIVITY OF LOUDSPEAKER ARRAYS,” filed on Sep. 29, 2015, the content of which is hereby incorporated by reference in its entirety, and included in the Appendix. This application also relates to the U.S. patent application Ser. No. 15/266,956 entitled “INTELLIGENT AUTOMATED ASSISTANT FOR MEDIA EXPLORATION,” filed on Sep. 15, 2016. This application also relates to the U.S. patent application Ser. No. 15/268,338 entitled “INTELLIGENT DEVICE ARBITRATION AND CONTROL,” filed on Sep. 16, 2016, the content of which is hereby incorporated by reference in its entirety, and included in the Appendix. This application also relates to the U.S. patent application Ser. No. 15/272,214 entitled “INTELLIGENT LIST READING,” filed on Sep. 21, 2016. This application also relates to the U.S. patent application Ser. No. 15/275,077 entitled “PRESSURE GRADIENT MICROPHONE FOR MEASURING AN ACOUSTIC CHARACTERISTIC OF A LOUDSPEAKER,” filed on Sep. 23, 2016. This application also relates to the U.S. patent application Ser. No. 15/385,606 entitled “INTELLIGENT AUTOMATED ASSISTANT,” filed on Dec. 20, 2016, the content of which is hereby incorporated by reference in its entirety, and included in the Appendix. This application also relates to the U.S. patent application Ser. No. 15/504,312 entitled “A ROTATIONALLY SYMMETRIC SPEAKER ARRAY,” filed on Aug. 18, 2014. This application also relates to the U.S. patent application Ser. No. 15/514,455 entitled “METHOD TO DETERMINE LOUDSPEAKER CHANGE OF PLACEMENT,” filed on Sep. 25, 2015. This application also relates to the U.S. patent application Ser. No. 15/583,949 entitled “A ROTATIONALLY SYMMETRIC SPEAKER ARRAY,” filed on May 1, 2017. This application also relates to the U.S. patent application Ser. No. 15/593,887 entitled “SPATIAL AUDIO RENDERING FOR BEAMFORMING LOUDSPEAKER ARRAY,” filed on May 12, 2017, the content of which is hereby incorporated by reference in its entirety, and included in the Appendix. This application also relates to the U.S. Patent Application No. 62/004,111 entitled “MULTI-CHANNEL LOUDSPEAKER MATCHING USING VARIABLE DIRECTIVITY,” filed on May 28, 2014. This application also relates to the U.S. Patent Application No. 62/057,989 entitled “MODAL BASED ARCHITECTURE FOR CONTROLLING THE DIRECTIVITY OF LOUDSPEAKER ARRAYS,” filed on Sep. 30, 2014. This application also relates to the U.S. Patent Application No. 62/057,999 entitled “METHOD TO DETERMINE LOUDSPEAKER CHANGE OF PLACEMENT,” filed on Sep. 30, 2014. This application also relates to the U.S. Patent Application No. 62/346,236 entitled “INTELLIGENT LIST READING,” filed on Jun. 6, 2016. This application also relates to the U.S. Patent Application No. 62/347,480 entitled “INTELLIGENT AUTOMATED ASSISTANT FOR MEDIA EXPLORATION,” filed on Jun. 8, 2016. This application also relates to the U.S. Patent Application No. 62/348,896 entitled “INTELLIGENT DEVICE ARBITRATION AND CONTROL,” filed on Jun. 11, 2016. This application also relates to the U.S. Patent Application No. 62/399,165 entitled “AUDIO DRIVER AND POWER SUPPLY UNIT ARCHITECTURE,” filed on Sep. 23, 2016. This application also relates to the U.S. Patent Application No. 62/399,229 entitled “MULTI-LOBE MAGNET FOR SUBWOOFER,” filed on Sep. 23, 2016. This application also relates to the U.S. Patent Application No. 62/399,232 entitled “INTELLIGENT AUTOMATED ASSISTANT,” filed on Sep. 23, 2016. This application also relates to the U.S. Patent Application No. 62/399,262 entitled “FORWARD BACK VOLUME OF AIR FOR AUDIO DRIVER,” filed on Sep. 23, 2016. This application also relates to the U.S. Patent Application No. 62/399,288 entitled “UPPER HOUSING COMPONENT ARCHITECTURE,” filed on Sep. 23, 2016. This application also relates to the U.S. Patent Application No. 62/399,293 entitled “AUDIO DRIVER EXIT GEOMETRY,” filed on Sep. 23, 2016. This application also relates to the U.S. Patent Application No. 62/402,836 entitled “SPATIAL AUDIO RENDERING STRATEGIES FOR BEAMFORMING LOUD SPEAKER ARRAY,” filed on Sep. 30, 2016. This application also relates to the U.S. Patent Application No. 62/506,912 entitled “MANAGING MEDIA COLLECTIONS USING DIRECTED ACYCLIC GRAPHS,” filed on May 16, 2017. This application also relates to the U.S. Patent Application No. 62/507,007 entitled “SPEAKER,” filed on May 16, 2017. This application also relates to the U.S. Patent Application No. 62/507,100 entitled “TRANSFERRING PLAYBACK QUEUES BETWEEN DEVICES,” filed on May 16, 2017. This application also relates to the U.S. Patent Application No. 62/507,151 entitled “FAR-FIELD EXTENSION FOR DIGITAL ASSISTANT SERVICES,” filed on May 16, 2017, the content of which is hereby incorporated by reference in its entirety, and included in the Appendix. This application also relates to the U.S. Patent Application No. 62/507,056 entitled “PROVIDING AN AUDITORY-BASED INTERFACE OF A DIGITAL ASSISTANT,” filed on May 16, 2017. This application also relates to the U.S. Patent Application No. 62/506,871 entitled “METHODS AND SYSTEMS FOR PHONETIC MATCHING IN DIGITAL ASSISTANT SERVICE,” filed on May 16, 2017. This application also relates to the U.S. Patent Application No. 62/507,042 entitled “DETECTING A TRIGGER OF A DIGITAL ASSISTANT,” filed on May 16, 2017. This application also relates to the U.S. Patent Application No. 62/506,981 entitled “INTELLIGENT AUTOMATED ASSISTANT FOR MEDIA EXPLORATION,” filed on May 16, 2017. This application also relates to the U.S. patent application Ser. No. 15/967,089 entitled “SPATIALLY DUCKING AUDIO PRODUCED THROUGH A BEAMFORMING LOUDSPEAKER ARRAY,” filed on Apr. 30, 2018. This application also relates to the U.S. patent application Ser. No. 15/613,127 entitled “MULTI-CHANNEL SPEECH SIGNAL ENHANCEMENT FOR ROBUST VOICE TRIGGER DETECTION AND AUTOMATIC SPEECH RECOGNITION,” filed on Jun. 2, 2017. This application also relates to the U.S. patent application Ser. No. 15/613,040 entitled “LOUDSPEAKER ORIENTATION SYSTEMS,” filed on Jun. 2, 2017. This application also relates to the U.S. patent application Ser. No. 15/619,058 entitled “AUDIO SYSTEMS WITH SMOOTH DIRECTIVITY TRANSITIONS,” filed on Jun. 9, 2017. This application also relates to the U.S. patent application Ser. No. 15/613,198 entitled “AUDIO SYSTEMS WITH ACTIVE FEEDBACK ACOUSTIC ECHO CANCELLATION,” filed on Jun. 3, 2017. This application also relates to the U.S. Patent Application No. 62/507,150 entitled “TECHNIQUES FOR VERIFYING USER INTENT AND SECURELY CONFIGURING COMPUTER DEVICES,” filed on May 16, 2017. This application also relates to the U.S. Patent Application No. 62/507,187 entitled “TECHNIQUES FOR REPAIRING AN INOPERABLE AUXILIARY DEVICE USING ANOTHER DEVICE,” filed on May 16, 2017. The content of each of the above-listed related applications are hereby incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5202961 | Mills et al. | Apr 1993 | A |
| 5305435 | Bronson | Apr 1994 | A |
| 5333266 | Boaz et al. | Jul 1994 | A |
| 5347628 | Welch et al. | Sep 1994 | A |
| 5404316 | Klingler et al. | Apr 1995 | A |
| 5463725 | Henckel et al. | Oct 1995 | A |
| 5495566 | Kwatinetz | Feb 1996 | A |
| 5513342 | Leong et al. | Apr 1996 | A |
| 5519828 | Rayner | May 1996 | A |
| 5521841 | Arman et al. | May 1996 | A |
| 5557724 | Sampat et al. | Sep 1996 | A |
| 5568603 | Chen et al. | Oct 1996 | A |
| 5611060 | Belfiore et al. | Mar 1997 | A |
| 5614940 | Cobbley et al. | Mar 1997 | A |
| 5682326 | Klingler et al. | Oct 1997 | A |
| 5684970 | Asuma et al. | Nov 1997 | A |
| 5692213 | Harrison et al. | Nov 1997 | A |
| 5726687 | Belfiore et al. | Mar 1998 | A |
| 5732184 | Chao et al. | Mar 1998 | A |
| 5745096 | Ludolph et al. | Apr 1998 | A |
| 5751260 | Nappi et al. | May 1998 | A |
| 5754174 | Carpenter et al. | May 1998 | A |
| 5758180 | Duffy et al. | May 1998 | A |
| 5760767 | Shore et al. | Jun 1998 | A |
| 5760772 | Austin | Jun 1998 | A |
| 5778053 | Skarbo et al. | Jul 1998 | A |
| 5793366 | Mano et al. | Aug 1998 | A |
| 5841971 | Longginou et al. | Nov 1998 | A |
| 5864868 | Contois | Jan 1999 | A |
| 5872566 | Bates et al. | Feb 1999 | A |
| 5872922 | Hogan et al. | Feb 1999 | A |
| 5874958 | Ludolph | Feb 1999 | A |
| 5880725 | Southgate | Mar 1999 | A |
| 5880733 | Horvitz et al. | Mar 1999 | A |
| 5892507 | Moorby | Apr 1999 | A |
| 5936623 | Amro | Aug 1999 | A |
| 5999173 | Ubillos | Dec 1999 | A |
| 6011537 | Slotznick | Jan 2000 | A |
| 6016248 | Anzai et al. | Jan 2000 | A |
| 6023275 | Horvitz et al. | Feb 2000 | A |
| 6026389 | Nakajima et al. | Feb 2000 | A |
| 6031529 | Migos et al. | Feb 2000 | A |
| 6061062 | Venolia | May 2000 | A |
| 6072503 | Tani et al. | Jun 2000 | A |
| 6081256 | Martin et al. | Jun 2000 | A |
| 6094197 | Buxton et al. | Jul 2000 | A |
| 6115037 | Sumiyoshi et al. | Sep 2000 | A |
| 6118450 | Proehl et al. | Sep 2000 | A |
| 6140987 | Stein et al. | Oct 2000 | A |
| 6166736 | Hugh | Dec 2000 | A |
| 6204840 | Petelycky et al. | Mar 2001 | B1 |
| 6208342 | Mugura et al. | Mar 2001 | B1 |
| 6236400 | Guerrero | May 2001 | B1 |
| 6262724 | Crow et al. | Jul 2001 | B1 |
| 6308187 | Destefano | Oct 2001 | B1 |
| 6310613 | Tanaka et al. | Oct 2001 | B1 |
| 6317784 | Mackintosh et al. | Nov 2001 | B1 |
| 6323846 | Westerman et al. | Nov 2001 | B1 |
| 6332147 | Moran et al. | Dec 2001 | B1 |
| 6351765 | Pietropaolo et al. | Feb 2002 | B1 |
| 6362837 | Ginn | Mar 2002 | B1 |
| 6363395 | Tanaka et al. | Mar 2002 | B1 |
| 6366296 | Boreczky et al. | Apr 2002 | B1 |
| 6369835 | Lin | Apr 2002 | B1 |
| 6393430 | Van et al. | May 2002 | B1 |
| 6393462 | Mullen-schultz | May 2002 | B1 |
| 6446080 | Van Ryzin et al. | Sep 2002 | B1 |
| 6452609 | Katinsky et al. | Sep 2002 | B1 |
| 6456305 | Qureshi et al. | Sep 2002 | B1 |
| 6477117 | Narayanaswami et al. | Nov 2002 | B1 |
| 6489951 | Wong et al. | Dec 2002 | B1 |
| 6504934 | Kasai et al. | Jan 2003 | B1 |
| 6515681 | Knight | Feb 2003 | B1 |
| 6515988 | Eldridge et al. | Feb 2003 | B1 |
| 6538665 | Crow et al. | Mar 2003 | B2 |
| 6544295 | Bodnar et al. | Apr 2003 | B1 |
| 6556222 | Narayanaswami | Apr 2003 | B1 |
| 6570557 | Westerman et al. | May 2003 | B1 |
| 6577330 | Tsuda et al. | Jun 2003 | B1 |
| 6584479 | Chang et al. | Jun 2003 | B2 |
| 6587127 | Stojakovic et al. | Jul 2003 | B1 |
| 6600936 | Kärkkäinen et al. | Jul 2003 | B1 |
| 6611297 | Akashi et al. | Aug 2003 | B1 |
| 6674452 | Kraft et al. | Jan 2004 | B1 |
| 6677932 | Westerman | Jan 2004 | B1 |
| 6677965 | Ullmann et al. | Jan 2004 | B1 |
| 6725427 | Freeman et al. | Apr 2004 | B2 |
| 6833848 | Wolff et al. | Dec 2004 | B1 |
| 6834371 | Jensen et al. | Dec 2004 | B1 |
| 6850256 | Crow et al. | Feb 2005 | B2 |
| 6922147 | Viksnins et al. | Jul 2005 | B1 |
| 6975306 | Hinckley et al. | Dec 2005 | B2 |
| 7081905 | Raghunath | Jul 2006 | B1 |
| 7091964 | Wong et al. | Aug 2006 | B2 |
| 7111240 | Crow et al. | Sep 2006 | B2 |
| 7191411 | Moehrle | Mar 2007 | B2 |
| 7240297 | Anderson et al. | Jul 2007 | B1 |
| 7315984 | Crow et al. | Jan 2008 | B2 |
| 7318196 | Crow et al. | Jan 2008 | B2 |
| 7370244 | Breitling et al. | May 2008 | B2 |
| 7415720 | Jung | Aug 2008 | B2 |
| 7441207 | Filner | Oct 2008 | B2 |
| 7454192 | Zhu | Nov 2008 | B1 |
| 7458025 | Crow et al. | Nov 2008 | B2 |
| 7479949 | Jobs et al. | Jan 2009 | B2 |
| 7492350 | Fabre et al. | Feb 2009 | B2 |
| 7526728 | Apparao et al. | Apr 2009 | B2 |
| 7546470 | Schultz | Jun 2009 | B2 |
| 7571014 | Lambourne et al. | Aug 2009 | B1 |
| 7581186 | Dowdy et al. | Aug 2009 | B2 |
| 7593749 | Vallstrom et al. | Sep 2009 | B2 |
| 7596761 | Lemay et al. | Sep 2009 | B2 |
| 7656393 | King et al. | Feb 2010 | B2 |
| 7710393 | Tsuk et al. | May 2010 | B2 |
| 7730223 | Bavor et al. | Jun 2010 | B1 |
| 7750893 | Hashimoto et al. | Jul 2010 | B2 |
| 7831054 | Ball et al. | Nov 2010 | B2 |
| 7860936 | Newstadt et al. | Dec 2010 | B1 |
| 7996792 | Anzures et al. | Aug 2011 | B2 |
| 8028323 | Weel | Sep 2011 | B2 |
| 8042157 | Bennett et al. | Oct 2011 | B2 |
| 8046804 | Kelts | Oct 2011 | B2 |
| 8060571 | Rao | Nov 2011 | B2 |
| 8060825 | Chaudhri et al. | Nov 2011 | B2 |
| 8077157 | Sengupta et al. | Dec 2011 | B2 |
| 8116807 | Matas | Feb 2012 | B2 |
| 8146019 | Kim et al. | Mar 2012 | B2 |
| 8171137 | Parks et al. | May 2012 | B1 |
| 8196043 | Crow et al. | Jun 2012 | B2 |
| 8217906 | Sinclair | Jul 2012 | B2 |
| 8224894 | Parks et al. | Jul 2012 | B1 |
| 8225191 | Kalman | Jul 2012 | B1 |
| 8234395 | Millington | Jul 2012 | B2 |
| 8260879 | Chan | Sep 2012 | B2 |
| 8264465 | Grant et al. | Sep 2012 | B2 |
| 8280539 | Jehan et al. | Oct 2012 | B2 |
| 8290603 | Lambourne | Oct 2012 | B1 |
| 8305356 | Jang | Nov 2012 | B1 |
| 8386563 | Parks et al. | Feb 2013 | B2 |
| 8392259 | Macgillivray et al. | Mar 2013 | B2 |
| 8392617 | Weber et al. | Mar 2013 | B1 |
| 8427303 | Brady et al. | Apr 2013 | B1 |
| 8434133 | Kulkarni et al. | Apr 2013 | B2 |
| 8458780 | Takkallapally et al. | Jun 2013 | B1 |
| 8462961 | Bywaters et al. | Jun 2013 | B1 |
| 8467766 | Rackley, III et al. | Jun 2013 | B2 |
| 8478363 | Levien et al. | Jul 2013 | B2 |
| 8478816 | Parks et al. | Jul 2013 | B2 |
| 8531427 | Jang | Sep 2013 | B2 |
| 8564543 | Chaudhri | Oct 2013 | B2 |
| 8572513 | Chaudhri et al. | Oct 2013 | B2 |
| 8587528 | Chaudhri | Nov 2013 | B2 |
| 8589823 | Lemay et al. | Nov 2013 | B2 |
| 8613070 | Borzycki et al. | Dec 2013 | B1 |
| 8624836 | Miller et al. | Jan 2014 | B1 |
| 8682722 | Des Jardins et al. | Mar 2014 | B1 |
| 8689128 | Chaudhri et al. | Apr 2014 | B2 |
| 8698762 | Wagner et al. | Apr 2014 | B2 |
| 8718556 | Lee et al. | May 2014 | B2 |
| 8736557 | Chaudhri et al. | May 2014 | B2 |
| 8769624 | Cotterill | Jul 2014 | B2 |
| 8811951 | Faaborg et al. | Aug 2014 | B1 |
| 8812601 | Hsieh et al. | Aug 2014 | B2 |
| 8826415 | Last | Sep 2014 | B2 |
| 8830181 | Clark et al. | Sep 2014 | B1 |
| 8860674 | Lee et al. | Oct 2014 | B2 |
| 8875046 | Jitkoff | Oct 2014 | B2 |
| 8884874 | Kim et al. | Nov 2014 | B1 |
| 8886710 | Evans et al. | Nov 2014 | B2 |
| 8914752 | Spiegel | Dec 2014 | B1 |
| 8914840 | Reisman | Dec 2014 | B2 |
| 8943410 | Ubillos | Jan 2015 | B2 |
| 8984431 | Newman et al. | Mar 2015 | B2 |
| 9002322 | Cotterill | Apr 2015 | B2 |
| 9042556 | Kallai et al. | May 2015 | B2 |
| 9084003 | Sanio et al. | Jul 2015 | B1 |
| 9095779 | Chan et al. | Aug 2015 | B2 |
| 9100944 | Sauhta et al. | Aug 2015 | B2 |
| 9112849 | Werkelin Ahlin et al. | Aug 2015 | B1 |
| 9134902 | Kang et al. | Sep 2015 | B2 |
| 9185062 | Yang et al. | Nov 2015 | B1 |
| 9191988 | Newham | Nov 2015 | B2 |
| 9195219 | Hong et al. | Nov 2015 | B2 |
| 9202509 | Kallai et al. | Dec 2015 | B2 |
| 9244584 | Fino | Jan 2016 | B2 |
| 9247363 | Triplett et al. | Jan 2016 | B2 |
| 9251787 | Hart et al. | Feb 2016 | B1 |
| 9269083 | Jarajapu et al. | Feb 2016 | B1 |
| 9294476 | Lurey et al. | Mar 2016 | B1 |
| 9294853 | Dhaundiyal | Mar 2016 | B1 |
| 9319782 | Crump et al. | Apr 2016 | B1 |
| 9374607 | Bates et al. | Jun 2016 | B2 |
| 9395905 | Wherry | Jul 2016 | B2 |
| 9400489 | Kim et al. | Jul 2016 | B2 |
| D765118 | Bachman et al. | Aug 2016 | S |
| 9431021 | Scalise et al. | Aug 2016 | B1 |
| 9450812 | Lee et al. | Sep 2016 | B2 |
| 9477208 | Park et al. | Oct 2016 | B2 |
| 9489106 | Chaudhri et al. | Nov 2016 | B2 |
| D773510 | Foss et al. | Dec 2016 | S |
| 9519413 | Bates | Dec 2016 | B2 |
| 9549323 | Lee et al. | Jan 2017 | B2 |
| 9582178 | Grant et al. | Feb 2017 | B2 |
| 9588661 | Jauhal et al. | Mar 2017 | B1 |
| 9628414 | Umapathy et al. | Apr 2017 | B1 |
| D789381 | Okumura et al. | Jun 2017 | S |
| 9680927 | Miller et al. | Jun 2017 | B2 |
| 9680982 | Fiedler | Jun 2017 | B2 |
| 9710639 | Saini | Jul 2017 | B1 |
| 9727749 | Tzeng et al. | Aug 2017 | B2 |
| 9779613 | Bates | Oct 2017 | B2 |
| 9794720 | Kadri | Oct 2017 | B1 |
| 9798443 | Gray | Oct 2017 | B1 |
| 9820323 | Young et al. | Nov 2017 | B1 |
| 9846564 | Toksoz et al. | Dec 2017 | B1 |
| 9846685 | Li | Dec 2017 | B2 |
| 9847999 | Van Os et al. | Dec 2017 | B2 |
| 9898250 | Williams et al. | Feb 2018 | B1 |
| 9922317 | Bak et al. | Mar 2018 | B2 |
| 9954989 | Zhou | Apr 2018 | B2 |
| 9967401 | Coffman et al. | May 2018 | B2 |
| 10027775 | Mierau et al. | Jul 2018 | B1 |
| 10055094 | Li et al. | Aug 2018 | B2 |
| 10089607 | Ziat et al. | Oct 2018 | B2 |
| 10096015 | Bak et al. | Oct 2018 | B2 |
| 10104089 | Kim et al. | Oct 2018 | B2 |
| 10129044 | Kangshang et al. | Nov 2018 | B2 |
| 10142122 | Hill et al. | Nov 2018 | B1 |
| 10157040 | Ballinger et al. | Dec 2018 | B2 |
| 10178234 | Coffman et al. | Jan 2019 | B2 |
| 10182138 | Motika et al. | Jan 2019 | B2 |
| 10198563 | Wang et al. | Feb 2019 | B2 |
| 10200468 | Leban et al. | Feb 2019 | B2 |
| 10225711 | Parks et al. | Mar 2019 | B2 |
| 10237141 | Sasaki et al. | Mar 2019 | B2 |
| 10248779 | Song et al. | Apr 2019 | B2 |
| 10284980 | Woo et al. | May 2019 | B1 |
| 10299300 | Young | May 2019 | B1 |
| 10300394 | Evans et al. | May 2019 | B1 |
| 10303422 | Woo et al. | May 2019 | B1 |
| 10310725 | Smith et al. | Jun 2019 | B2 |
| 10334054 | Van Os et al. | Jun 2019 | B2 |
| 10339769 | Mixter et al. | Jul 2019 | B2 |
| 10374804 | Lee et al. | Aug 2019 | B2 |
| 10417037 | Gruber et al. | Sep 2019 | B2 |
| 10436977 | Bergman et al. | Oct 2019 | B2 |
| 10454781 | Sasaki et al. | Oct 2019 | B2 |
| 10511456 | Smith et al. | Dec 2019 | B2 |
| 10523625 | Allen et al. | Dec 2019 | B1 |
| 10524300 | Ueda et al. | Dec 2019 | B2 |
| 10701067 | Ziraknejad et al. | Jun 2020 | B1 |
| 10705701 | Pisula et al. | Jul 2020 | B2 |
| 10713699 | Lien et al. | Jul 2020 | B1 |
| 10732819 | Wang et al. | Aug 2020 | B2 |
| 10742645 | Hevizi et al. | Aug 2020 | B2 |
| 10742648 | Magyar et al. | Aug 2020 | B2 |
| 10749967 | Van Os et al. | Aug 2020 | B2 |
| 10779085 | Carrigan | Sep 2020 | B1 |
| 10783883 | Mixter et al. | Sep 2020 | B2 |
| 10824299 | Bai | Nov 2020 | B2 |
| 10833887 | Wu | Nov 2020 | B2 |
| 10924446 | Paul | Feb 2021 | B1 |
| 10929099 | Querze et al. | Feb 2021 | B2 |
| 10963145 | Voss et al. | Mar 2021 | B1 |
| 11079913 | Kim et al. | Aug 2021 | B1 |
| 11164580 | Kraker | Nov 2021 | B2 |
| 11281711 | Sanders et al. | Mar 2022 | B2 |
| 11283916 | Coffman et al. | Mar 2022 | B2 |
| 11316709 | Brown et al. | Apr 2022 | B2 |
| 11343370 | Gordon et al. | May 2022 | B1 |
| 11343613 | Gordon et al. | May 2022 | B2 |
| 11431834 | Gordon et al. | Aug 2022 | B1 |
| 11463576 | Gordon et al. | Oct 2022 | B1 |
| 11523166 | Tu et al. | Dec 2022 | B1 |
| 20010030597 | Inoue et al. | Oct 2001 | A1 |
| 20010031622 | Kivela et al. | Oct 2001 | A1 |
| 20010039497 | Hubbard | Nov 2001 | A1 |
| 20010043514 | Kita et al. | Nov 2001 | A1 |
| 20010049627 | Simpson | Dec 2001 | A1 |
| 20010050687 | Iida et al. | Dec 2001 | A1 |
| 20020002039 | Qureshey et al. | Jan 2002 | A1 |
| 20020015024 | Westerman et al. | Feb 2002 | A1 |
| 20020026442 | Lipscomb et al. | Feb 2002 | A1 |
| 20020048224 | Dygert et al. | Apr 2002 | A1 |
| 20020054158 | Asami | May 2002 | A1 |
| 20020054164 | Uemura | May 2002 | A1 |
| 20020057262 | Patrick et al. | May 2002 | A1 |
| 20020059295 | Ludtke et al. | May 2002 | A1 |
| 20020068600 | Chihara et al. | Jun 2002 | A1 |
| 20020080151 | Venolia | Jun 2002 | A1 |
| 20020115478 | Fujisawa et al. | Aug 2002 | A1 |
| 20020116276 | Ottley | Aug 2002 | A1 |
| 20020122066 | Bates et al. | Sep 2002 | A1 |
| 20020137565 | Blanco | Sep 2002 | A1 |
| 20020142734 | Wickstead | Oct 2002 | A1 |
| 20020154173 | Etgen et al. | Oct 2002 | A1 |
| 20020168938 | Chang | Nov 2002 | A1 |
| 20020191028 | Senechalle et al. | Dec 2002 | A1 |
| 20020198909 | Huynh et al. | Dec 2002 | A1 |
| 20030028382 | Chambers et al. | Feb 2003 | A1 |
| 20030028639 | Yamamoto et al. | Feb 2003 | A1 |
| 20030030673 | Ho | Feb 2003 | A1 |
| 20030052901 | Fukuchi | Mar 2003 | A1 |
| 20030055977 | Miller | Mar 2003 | A1 |
| 20030067908 | Mattaway et al. | Apr 2003 | A1 |
| 20030076298 | Rosenberg | Apr 2003 | A1 |
| 20030076301 | Tsuk et al. | Apr 2003 | A1 |
| 20030079057 | Ruskin et al. | Apr 2003 | A1 |
| 20030081506 | Karhu et al. | May 2003 | A1 |
| 20030097358 | Mendez et al. | May 2003 | A1 |
| 20030097413 | Vishik et al. | May 2003 | A1 |
| 20030112938 | Kanakubo et al. | Jun 2003 | A1 |
| 20030122787 | Zimmerman et al. | Jul 2003 | A1 |
| 20030128192 | Van Os | Jul 2003 | A1 |
| 20030160861 | Barlow et al. | Aug 2003 | A1 |
| 20030182139 | Harris et al. | Sep 2003 | A1 |
| 20030188183 | Lee et al. | Oct 2003 | A1 |
| 20030229900 | Reisman | Dec 2003 | A1 |
| 20040019640 | Bartram et al. | Jan 2004 | A1 |
| 20040027371 | Jaeger | Feb 2004 | A1 |
| 20040032955 | Hashimoto et al. | Feb 2004 | A1 |
| 20040046638 | Kawasaki | Mar 2004 | A1 |
| 20040055446 | Robbin et al. | Mar 2004 | A1 |
| 20040056837 | Koga et al. | Mar 2004 | A1 |
| 20040073432 | Stone | Apr 2004 | A1 |
| 20040100479 | Nakano et al. | May 2004 | A1 |
| 20040104896 | Suraqui | Jun 2004 | A1 |
| 20040122683 | Grossman et al. | Jun 2004 | A1 |
| 20040125088 | Zimmerman et al. | Jul 2004 | A1 |
| 20040130581 | Howard et al. | Jul 2004 | A1 |
| 20040139398 | Testa et al. | Jul 2004 | A1 |
| 20040140956 | Kushler et al. | Jul 2004 | A1 |
| 20040155907 | Yamaguchi et al. | Aug 2004 | A1 |
| 20040168118 | Wong et al. | Aug 2004 | A1 |
| 20040181695 | Walker et al. | Sep 2004 | A1 |
| 20040189714 | Fox et al. | Sep 2004 | A1 |
| 20040235520 | Cadiz et al. | Nov 2004 | A1 |
| 20040237048 | Tojo et al. | Nov 2004 | A1 |
| 20040242200 | Maeoka et al. | Dec 2004 | A1 |
| 20040250217 | Tojo et al. | Dec 2004 | A1 |
| 20040261010 | Matsuishi | Dec 2004 | A1 |
| 20040264916 | Van et al. | Dec 2004 | A1 |
| 20040268400 | Barde et al. | Dec 2004 | A1 |
| 20050012723 | Pallakoff | Jan 2005 | A1 |
| 20050021418 | Marcus et al. | Jan 2005 | A1 |
| 20050024341 | Gillespie et al. | Feb 2005 | A1 |
| 20050052458 | Lambert | Mar 2005 | A1 |
| 20050071188 | Thuerk | Mar 2005 | A1 |
| 20050093868 | Hinckley | May 2005 | A1 |
| 20050096009 | Ackley | May 2005 | A1 |
| 20050097135 | Epperson et al. | May 2005 | A1 |
| 20050117752 | Iima et al. | Jun 2005 | A1 |
| 20050144247 | Christensen et al. | Jun 2005 | A1 |
| 20050144452 | Lynch et al. | Jun 2005 | A1 |
| 20050144568 | Gruen et al. | Jun 2005 | A1 |
| 20050146534 | Fong et al. | Jul 2005 | A1 |
| 20050160372 | Gruen et al. | Jul 2005 | A1 |
| 20050162402 | Watanachote | Jul 2005 | A1 |
| 20050177445 | Church | Aug 2005 | A1 |
| 20050181774 | Miyata | Aug 2005 | A1 |
| 20050192924 | Drucker et al. | Sep 2005 | A1 |
| 20050210412 | Matthews et al. | Sep 2005 | A1 |
| 20050216839 | Salvucci | Sep 2005 | A1 |
| 20050220304 | Lenoir et al. | Oct 2005 | A1 |
| 20050229112 | Clay et al. | Oct 2005 | A1 |
| 20050233780 | Jani et al. | Oct 2005 | A1 |
| 20050239512 | Hasegawa et al. | Oct 2005 | A1 |
| 20050240756 | Mayer | Oct 2005 | A1 |
| 20050251566 | Weel | Nov 2005 | A1 |
| 20050275628 | Balakrishnan et al. | Dec 2005 | A1 |
| 20050278587 | Breitling et al. | Dec 2005 | A1 |
| 20060001645 | Drucker et al. | Jan 2006 | A1 |
| 20060002523 | Bettis et al. | Jan 2006 | A1 |
| 20060019649 | Feinleib et al. | Jan 2006 | A1 |
| 20060020637 | Kedem | Jan 2006 | A1 |
| 20060020904 | Aaltonen et al. | Jan 2006 | A1 |
| 20060026535 | Hotelling et al. | Feb 2006 | A1 |
| 20060026536 | Hotelling et al. | Feb 2006 | A1 |
| 20060038796 | Hinckley et al. | Feb 2006 | A1 |
| 20060050054 | Liang et al. | Mar 2006 | A1 |
| 20060085751 | O'brien et al. | Apr 2006 | A1 |
| 20060085766 | Dominowska et al. | Apr 2006 | A1 |
| 20060125799 | Hillis et al. | Jun 2006 | A1 |
| 20060132456 | Anson | Jun 2006 | A1 |
| 20060132460 | Kolmykov-zotov et al. | Jun 2006 | A1 |
| 20060132469 | Lai et al. | Jun 2006 | A1 |
| 20060146074 | Harrison | Jul 2006 | A1 |
| 20060148455 | Kim | Jul 2006 | A1 |
| 20060156239 | Jobs et al. | Jul 2006 | A1 |
| 20060160090 | Macina et al. | Jul 2006 | A1 |
| 20060161621 | Rosenberg | Jul 2006 | A1 |
| 20060161870 | Hotelling et al. | Jul 2006 | A1 |
| 20060161871 | Hotelling et al. | Jul 2006 | A1 |
| 20060176278 | Mathews et al. | Aug 2006 | A1 |
| 20060178110 | Nurminen et al. | Aug 2006 | A1 |
| 20060185005 | Graves et al. | Aug 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060206709 | Labrou et al. | Sep 2006 | A1 |
| 20060210092 | Navid | Sep 2006 | A1 |
| 20060217104 | Cho | Sep 2006 | A1 |
| 20060224882 | Chin | Oct 2006 | A1 |
| 20060227106 | Hashimoto et al. | Oct 2006 | A1 |
| 20060236847 | Withop | Oct 2006 | A1 |
| 20060246874 | Sullivan | Nov 2006 | A1 |
| 20060250578 | Pohl et al. | Nov 2006 | A1 |
| 20060256090 | Huppi | Nov 2006 | A1 |
| 20060258289 | Dua | Nov 2006 | A1 |
| 20060268020 | Han | Nov 2006 | A1 |
| 20060271425 | Goodman et al. | Nov 2006 | A1 |
| 20060271864 | Satterfield et al. | Nov 2006 | A1 |
| 20060271867 | Wang et al. | Nov 2006 | A1 |
| 20060279541 | Kim et al. | Dec 2006 | A1 |
| 20060281449 | Kun et al. | Dec 2006 | A1 |
| 20060286971 | Maly et al. | Dec 2006 | A1 |
| 20060288226 | Kowal | Dec 2006 | A1 |
| 20070011614 | Crow et al. | Jan 2007 | A1 |
| 20070013671 | Zadesky et al. | Jan 2007 | A1 |
| 20070015519 | Casey | Jan 2007 | A1 |
| 20070027682 | Bennett | Feb 2007 | A1 |
| 20070033295 | Marriott | Feb 2007 | A1 |
| 20070048714 | Plastina et al. | Mar 2007 | A1 |
| 20070053268 | Crandall et al. | Mar 2007 | A1 |
| 20070070045 | Sung et al. | Mar 2007 | A1 |
| 20070070066 | Bakhash | Mar 2007 | A1 |
| 20070073649 | Kikkoji et al. | Mar 2007 | A1 |
| 20070085841 | Tsuk et al. | Apr 2007 | A1 |
| 20070097090 | Battles | May 2007 | A1 |
| 20070097093 | Ohshita et al. | May 2007 | A1 |
| 20070113294 | Field et al. | May 2007 | A1 |
| 20070115933 | Muhamed et al. | May 2007 | A1 |
| 20070124680 | Robbin et al. | May 2007 | A1 |
| 20070126715 | Funamoto | Jun 2007 | A1 |
| 20070136679 | Yang | Jun 2007 | A1 |
| 20070136778 | Birger et al. | Jun 2007 | A1 |
| 20070143495 | Porat | Jun 2007 | A1 |
| 20070150842 | Chaudhri et al. | Jun 2007 | A1 |
| 20070152979 | Jobs et al. | Jul 2007 | A1 |
| 20070157089 | Van Os et al. | Jul 2007 | A1 |
| 20070157094 | Lemay et al. | Jul 2007 | A1 |
| 20070157103 | Arneson et al. | Jul 2007 | A1 |
| 20070162963 | Penet et al. | Jul 2007 | A1 |
| 20070168369 | Bruns | Jul 2007 | A1 |
| 20070168413 | Barletta et al. | Jul 2007 | A1 |
| 20070180492 | Hassan et al. | Aug 2007 | A1 |
| 20070186106 | Ting et al. | Aug 2007 | A1 |
| 20070186235 | Jarman et al. | Aug 2007 | A1 |
| 20070191008 | Bucher et al. | Aug 2007 | A1 |
| 20070192744 | Reponen | Aug 2007 | A1 |
| 20070198111 | Oetzel et al. | Aug 2007 | A1 |
| 20070226645 | Kongqiao et al. | Sep 2007 | A1 |
| 20070226778 | Pietruszka | Sep 2007 | A1 |
| 20070229221 | Saotome | Oct 2007 | A1 |
| 20070260547 | Little | Nov 2007 | A1 |
| 20070283011 | Rakowski et al. | Dec 2007 | A1 |
| 20070294182 | Hammad | Dec 2007 | A1 |
| 20080010387 | Curtis et al. | Jan 2008 | A1 |
| 20080011827 | Little et al. | Jan 2008 | A1 |
| 20080016368 | Adams | Jan 2008 | A1 |
| 20080016468 | Chambers et al. | Jan 2008 | A1 |
| 20080016537 | Little et al. | Jan 2008 | A1 |
| 20080017721 | Zehnacker | Jan 2008 | A1 |
| 20080027947 | Pritchett et al. | Jan 2008 | A1 |
| 20080034011 | Cisler et al. | Feb 2008 | A1 |
| 20080034289 | Doepke et al. | Feb 2008 | A1 |
| 20080036743 | Westerman et al. | Feb 2008 | A1 |
| 20080037951 | Cho et al. | Feb 2008 | A1 |
| 20080040786 | Chang et al. | Feb 2008 | A1 |
| 20080042866 | Morse et al. | Feb 2008 | A1 |
| 20080055263 | Lemay et al. | Mar 2008 | A1 |
| 20080055264 | Anzures et al. | Mar 2008 | A1 |
| 20080057926 | Forstall et al. | Mar 2008 | A1 |
| 20080062141 | Chaudhri | Mar 2008 | A1 |
| 20080065505 | Plastina et al. | Mar 2008 | A1 |
| 20080066016 | Dowdy et al. | Mar 2008 | A1 |
| 20080075368 | Kuzmin | Mar 2008 | A1 |
| 20080081558 | Dunko et al. | Apr 2008 | A1 |
| 20080082939 | Nash et al. | Apr 2008 | A1 |
| 20080084400 | Rosenberg | Apr 2008 | A1 |
| 20080091717 | Garbow et al. | Apr 2008 | A1 |
| 20080094367 | Van De Ven et al. | Apr 2008 | A1 |
| 20080094370 | Ording et al. | Apr 2008 | A1 |
| 20080100693 | Jobs et al. | May 2008 | A1 |
| 20080109764 | Linnamaki | May 2008 | A1 |
| 20080114678 | Bennett et al. | May 2008 | A1 |
| 20080114980 | Sridhar | May 2008 | A1 |
| 20080122794 | Koiso et al. | May 2008 | A1 |
| 20080122796 | Jobs et al. | May 2008 | A1 |
| 20080126935 | Blomgren | May 2008 | A1 |
| 20080147735 | Sloo | Jun 2008 | A1 |
| 20080155413 | Ubillos et al. | Jun 2008 | A1 |
| 20080155417 | Vallone et al. | Jun 2008 | A1 |
| 20080155474 | Duhig et al. | Jun 2008 | A1 |
| 20080158170 | Herz et al. | Jul 2008 | A1 |
| 20080160974 | Vartiainen et al. | Jul 2008 | A1 |
| 20080163127 | Newell et al. | Jul 2008 | A1 |
| 20080165141 | Christie | Jul 2008 | A1 |
| 20080165152 | Forstall et al. | Jul 2008 | A1 |
| 20080165153 | Platzer et al. | Jul 2008 | A1 |
| 20080168185 | Robbin et al. | Jul 2008 | A1 |
| 20080168384 | Platzer et al. | Jul 2008 | A1 |
| 20080168395 | Ording et al. | Jul 2008 | A1 |
| 20080168403 | Westerman et al. | Jul 2008 | A1 |
| 20080190266 | Kim et al. | Aug 2008 | A1 |
| 20080201454 | Soffer | Aug 2008 | A1 |
| 20080208762 | Arthur et al. | Aug 2008 | A1 |
| 20080209468 | Milosevski | Aug 2008 | A1 |
| 20080214163 | Onyon et al. | Sep 2008 | A1 |
| 20080222546 | Mudd et al. | Sep 2008 | A1 |
| 20080225007 | Nakadaira et al. | Sep 2008 | A1 |
| 20080225013 | Muylkens et al. | Sep 2008 | A1 |
| 20080229409 | Miller et al. | Sep 2008 | A1 |
| 20080250319 | Lee et al. | Oct 2008 | A1 |
| 20080259829 | Rosenblatt | Oct 2008 | A1 |
| 20080273712 | Eichfeld et al. | Nov 2008 | A1 |
| 20080273713 | Hartung et al. | Nov 2008 | A1 |
| 20080282202 | Sunday | Nov 2008 | A1 |
| 20080285772 | Haulick et al. | Nov 2008 | A1 |
| 20080292074 | Boni et al. | Nov 2008 | A1 |
| 20080305742 | Basir | Dec 2008 | A1 |
| 20080313257 | Allen et al. | Dec 2008 | A1 |
| 20080320391 | Lemay et al. | Dec 2008 | A1 |
| 20090002335 | Chaudhri | Jan 2009 | A1 |
| 20090002396 | Andrews et al. | Jan 2009 | A1 |
| 20090006846 | Rosenblatt | Jan 2009 | A1 |
| 20090006958 | Pohjola et al. | Jan 2009 | A1 |
| 20090007188 | Omernick | Jan 2009 | A1 |
| 20090031375 | Sullivan et al. | Jan 2009 | A1 |
| 20090051649 | Rondel | Feb 2009 | A1 |
| 20090054044 | Ikemori et al. | Feb 2009 | A1 |
| 20090055377 | Hedge et al. | Feb 2009 | A1 |
| 20090058822 | Chaudhri | Mar 2009 | A1 |
| 20090060170 | Coughlan et al. | Mar 2009 | A1 |
| 20090061837 | Chaudhri et al. | Mar 2009 | A1 |
| 20090063851 | Nijdam | Mar 2009 | A1 |
| 20090066648 | Kerr et al. | Mar 2009 | A1 |
| 20090075694 | Kim et al. | Mar 2009 | A1 |
| 20090077491 | Kim | Mar 2009 | A1 |
| 20090094681 | Sadler et al. | Apr 2009 | A1 |
| 20090100383 | Sunday et al. | Apr 2009 | A1 |
| 20090119754 | Schubert | May 2009 | A1 |
| 20090122149 | Ishii | May 2009 | A1 |
| 20090125571 | Kiilerich et al. | May 2009 | A1 |
| 20090128500 | Sinclair | May 2009 | A1 |
| 20090135678 | Godat | May 2009 | A1 |
| 20090140960 | Mahowald et al. | Jun 2009 | A1 |
| 20090140991 | Takasaki et al. | Jun 2009 | A1 |
| 20090144391 | Jung et al. | Jun 2009 | A1 |
| 20090144451 | Cabezas et al. | Jun 2009 | A1 |
| 20090144623 | Jung | Jun 2009 | A1 |
| 20090153289 | Hope et al. | Jun 2009 | A1 |
| 20090153466 | Tilley | Jun 2009 | A1 |
| 20090158390 | Guan | Jun 2009 | A1 |
| 20090164581 | Bove et al. | Jun 2009 | A1 |
| 20090165107 | Tojo et al. | Jun 2009 | A1 |
| 20090174677 | Gehani et al. | Jul 2009 | A1 |
| 20090174680 | Anzures et al. | Jul 2009 | A1 |
| 20090174763 | Bengtsson et al. | Jul 2009 | A1 |
| 20090177966 | Chaudhri | Jul 2009 | A1 |
| 20090187423 | Kim | Jul 2009 | A1 |
| 20090187981 | Pan et al. | Jul 2009 | A1 |
| 20090193514 | Adams et al. | Jul 2009 | A1 |
| 20090195497 | Fitzgerald et al. | Aug 2009 | A1 |
| 20090198359 | Chaudhri | Aug 2009 | A1 |
| 20090199119 | Park et al. | Aug 2009 | A1 |
| 20090199130 | Tsern et al. | Aug 2009 | A1 |
| 20090199188 | Fujimaki | Aug 2009 | A1 |
| 20090204920 | Beverley et al. | Aug 2009 | A1 |
| 20090204929 | Baurmann et al. | Aug 2009 | A1 |
| 20090228938 | White et al. | Sep 2009 | A1 |
| 20090231960 | Hutcheson | Sep 2009 | A1 |
| 20090241169 | Dhand et al. | Sep 2009 | A1 |
| 20090244015 | Sengupta et al. | Oct 2009 | A1 |
| 20090248737 | Shukla et al. | Oct 2009 | A1 |
| 20090249244 | Robinson et al. | Oct 2009 | A1 |
| 20090265417 | Svendsen et al. | Oct 2009 | A1 |
| 20090271744 | Anders | Oct 2009 | A1 |
| 20090304205 | Hardacker et al. | Dec 2009 | A1 |
| 20090307633 | Haughay et al. | Dec 2009 | A1 |
| 20090311993 | Horodezky | Dec 2009 | A1 |
| 20090322695 | Cho et al. | Dec 2009 | A1 |
| 20090327449 | Silverman et al. | Dec 2009 | A1 |
| 20100001967 | Yoo | Jan 2010 | A1 |
| 20100004031 | Kim | Jan 2010 | A1 |
| 20100005421 | Yoshioka | Jan 2010 | A1 |
| 20100017474 | Kandekar et al. | Jan 2010 | A1 |
| 20100023449 | Skowronek et al. | Jan 2010 | A1 |
| 20100042654 | Heller et al. | Feb 2010 | A1 |
| 20100042835 | Lee et al. | Feb 2010 | A1 |
| 20100050086 | Sherrard et al. | Feb 2010 | A1 |
| 20100054497 | Bull et al. | Mar 2010 | A1 |
| 20100058228 | Park | Mar 2010 | A1 |
| 20100058253 | Son | Mar 2010 | A1 |
| 20100070490 | Amidon et al. | Mar 2010 | A1 |
| 20100075656 | Howarter et al. | Mar 2010 | A1 |
| 20100082481 | Lin et al. | Apr 2010 | A1 |
| 20100085379 | Hishikawa et al. | Apr 2010 | A1 |
| 20100088634 | Tsuruta et al. | Apr 2010 | A1 |
| 20100088639 | Yach et al. | Apr 2010 | A1 |
| 20100094834 | Svendsen | Apr 2010 | A1 |
| 20100106647 | Raman | Apr 2010 | A1 |
| 20100107229 | Najafi et al. | Apr 2010 | A1 |
| 20100121636 | Burke et al. | May 2010 | A1 |
| 20100122195 | Hwang | May 2010 | A1 |
| 20100125785 | Moore et al. | May 2010 | A1 |
| 20100131978 | Friedlander et al. | May 2010 | A1 |
| 20100138780 | Marano et al. | Jun 2010 | A1 |
| 20100146463 | Cho et al. | Jun 2010 | A1 |
| 20100159995 | Stallings et al. | Jun 2010 | A1 |
| 20100174644 | Rosano et al. | Jul 2010 | A1 |
| 20100174993 | Pennington et al. | Jul 2010 | A1 |
| 20100178873 | Lee et al. | Jul 2010 | A1 |
| 20100190478 | Brewer et al. | Jul 2010 | A1 |
| 20100205563 | Haapsaari et al. | Aug 2010 | A1 |
| 20100223542 | Vuong et al. | Sep 2010 | A1 |
| 20100229094 | Nakajima et al. | Sep 2010 | A1 |
| 20100231534 | Chaudhri et al. | Sep 2010 | A1 |
| 20100231535 | Chaudhri et al. | Sep 2010 | A1 |
| 20100231536 | Chaudhri et al. | Sep 2010 | A1 |
| 20100231537 | Pisula et al. | Sep 2010 | A1 |
| 20100235729 | Kocienda et al. | Sep 2010 | A1 |
| 20100235746 | Anzures et al. | Sep 2010 | A1 |
| 20100248823 | Smith | Sep 2010 | A1 |
| 20100250376 | Nandiraju | Sep 2010 | A1 |
| 20100251304 | Donoghue et al. | Sep 2010 | A1 |
| 20100257466 | Wroblewski et al. | Oct 2010 | A1 |
| 20100257484 | Nakamura et al. | Oct 2010 | A1 |
| 20100259482 | Ball | Oct 2010 | A1 |
| 20100269156 | Hohlfeld et al. | Oct 2010 | A1 |
| 20100272250 | Yap et al. | Oct 2010 | A1 |
| 20100283743 | Coddington | Nov 2010 | A1 |
| 20100284389 | Ramsay et al. | Nov 2010 | A1 |
| 20100293598 | Collart et al. | Nov 2010 | A1 |
| 20100295803 | Kim et al. | Nov 2010 | A1 |
| 20100296678 | Kuhn-rahloff et al. | Nov 2010 | A1 |
| 20100299436 | Khalid et al. | Nov 2010 | A1 |
| 20100299639 | Ramsay et al. | Nov 2010 | A1 |
| 20100302172 | Wilairat et al. | Dec 2010 | A1 |
| 20100304729 | Sabotta et al. | Dec 2010 | A1 |
| 20100306657 | Derbyshire et al. | Dec 2010 | A1 |
| 20100318908 | Neuman et al. | Dec 2010 | A1 |
| 20100318917 | Holladay et al. | Dec 2010 | A1 |
| 20100318928 | Neuman et al. | Dec 2010 | A1 |
| 20100318939 | Moon | Dec 2010 | A1 |
| 20100321201 | Huang et al. | Dec 2010 | A1 |
| 20100325239 | Khedouri et al. | Dec 2010 | A1 |
| 20110003587 | Belz et al. | Jan 2011 | A1 |
| 20110010470 | Hulbert et al. | Jan 2011 | A1 |
| 20110016089 | Freedman et al. | Jan 2011 | A1 |
| 20110029750 | Jang et al. | Feb 2011 | A1 |
| 20110029891 | Kim et al. | Feb 2011 | A1 |
| 20110035799 | Handler | Feb 2011 | A1 |
| 20110041102 | Kim | Feb 2011 | A1 |
| 20110054268 | Fidacaro et al. | Mar 2011 | A1 |
| 20110059769 | Brunolli | Mar 2011 | A1 |
| 20110065384 | Cader et al. | Mar 2011 | A1 |
| 20110071656 | Mckiel, Jr. | Mar 2011 | A1 |
| 20110081923 | Bednar et al. | Apr 2011 | A1 |
| 20110082902 | Rottler et al. | Apr 2011 | A1 |
| 20110087431 | Gupta et al. | Apr 2011 | A1 |
| 20110088086 | Swink et al. | Apr 2011 | A1 |
| 20110106671 | Minnis et al. | May 2011 | A1 |
| 20110126148 | Krishnaraj et al. | May 2011 | A1 |
| 20110130168 | Vendrow et al. | Jun 2011 | A1 |
| 20110131537 | Cho et al. | Jun 2011 | A1 |
| 20110138166 | Peszek et al. | Jun 2011 | A1 |
| 20110138284 | Wigdor et al. | Jun 2011 | A1 |
| 20110138295 | Momchilov et al. | Jun 2011 | A1 |
| 20110142234 | Rogers | Jun 2011 | A1 |
| 20110149874 | Reif | Jun 2011 | A1 |
| 20110157046 | Lee et al. | Jun 2011 | A1 |
| 20110159469 | Hwang et al. | Jun 2011 | A1 |
| 20110159927 | Choi | Jun 2011 | A1 |
| 20110163971 | Wagner et al. | Jul 2011 | A1 |
| 20110164042 | Chaudhri | Jul 2011 | A1 |
| 20110164269 | Kamishiro | Jul 2011 | A1 |
| 20110178811 | Sheridan | Jul 2011 | A1 |
| 20110179386 | Shaffer et al. | Jul 2011 | A1 |
| 20110183650 | Mckee | Jul 2011 | A1 |
| 20110187497 | Chin | Aug 2011 | A1 |
| 20110191695 | Dinka et al. | Aug 2011 | A1 |
| 20110209099 | Hinckley et al. | Aug 2011 | A1 |
| 20110214158 | Pasquero et al. | Sep 2011 | A1 |
| 20110215921 | Ben et al. | Sep 2011 | A1 |
| 20110225426 | Agarwal et al. | Sep 2011 | A1 |
| 20110231914 | Hung | Sep 2011 | A1 |
| 20110242002 | Kaplan et al. | Oct 2011 | A1 |
| 20110246942 | Misawa | Oct 2011 | A1 |
| 20110250895 | Wohlert et al. | Oct 2011 | A1 |
| 20110254683 | Soldan et al. | Oct 2011 | A1 |
| 20110273526 | Mehin et al. | Nov 2011 | A1 |
| 20110275358 | Faenger | Nov 2011 | A1 |
| 20110279852 | Oda et al. | Nov 2011 | A1 |
| 20110281568 | Le | Nov 2011 | A1 |
| 20110283334 | Choi et al. | Nov 2011 | A1 |
| 20110291971 | Masaki et al. | Dec 2011 | A1 |
| 20110302493 | Runstedler et al. | Dec 2011 | A1 |
| 20110306393 | Goldman et al. | Dec 2011 | A1 |
| 20110314398 | Yano et al. | Dec 2011 | A1 |
| 20110319056 | Toy et al. | Dec 2011 | A1 |
| 20110320450 | Liu et al. | Dec 2011 | A1 |
| 20120004920 | Kelly et al. | Jan 2012 | A1 |
| 20120005708 | Kelts | Jan 2012 | A1 |
| 20120011437 | James et al. | Jan 2012 | A1 |
| 20120016678 | Gruber et al. | Jan 2012 | A1 |
| 20120019610 | Hornyak et al. | Jan 2012 | A1 |
| 20120024947 | Naelon et al. | Feb 2012 | A1 |
| 20120033028 | Murphy et al. | Feb 2012 | A1 |
| 20120036556 | Lebeau et al. | Feb 2012 | A1 |
| 20120040719 | Lee et al. | Feb 2012 | A1 |
| 20120044062 | Jersa et al. | Feb 2012 | A1 |
| 20120050185 | Davydov et al. | Mar 2012 | A1 |
| 20120051560 | Sanders | Mar 2012 | A1 |
| 20120054278 | Taleb et al. | Mar 2012 | A1 |
| 20120059813 | Sejnoha et al. | Mar 2012 | A1 |
| 20120066632 | Sundermeyer et al. | Mar 2012 | A1 |
| 20120066731 | Vasquez et al. | Mar 2012 | A1 |
| 20120079126 | Evans et al. | Mar 2012 | A1 |
| 20120084697 | Reeves | Apr 2012 | A1 |
| 20120088477 | Cassidy et al. | Apr 2012 | A1 |
| 20120089951 | Cassidy | Apr 2012 | A1 |
| 20120096069 | Chan | Apr 2012 | A1 |
| 20120096076 | Chan et al. | Apr 2012 | A1 |
| 20120096386 | Baumann et al. | Apr 2012 | A1 |
| 20120105358 | Momeyer et al. | May 2012 | A1 |
| 20120110455 | Sharma et al. | May 2012 | A1 |
| 20120115608 | Pfeifer et al. | May 2012 | A1 |
| 20120129496 | Park et al. | May 2012 | A1 |
| 20120131459 | Ilama-vaquero et al. | May 2012 | A1 |
| 20120136998 | Hough et al. | May 2012 | A1 |
| 20120143694 | Zargahi et al. | Jun 2012 | A1 |
| 20120178431 | Gold | Jul 2012 | A1 |
| 20120197419 | Dhruv et al. | Aug 2012 | A1 |
| 20120210226 | Mccoy et al. | Aug 2012 | A1 |
| 20120214458 | Levien et al. | Aug 2012 | A1 |
| 20120215684 | Kidron | Aug 2012 | A1 |
| 20120218177 | Pang et al. | Aug 2012 | A1 |
| 20120222092 | Rabii | Aug 2012 | A1 |
| 20120223890 | Borovsky et al. | Sep 2012 | A1 |
| 20120223959 | Lengeling et al. | Sep 2012 | A1 |
| 20120260169 | Schwartz et al. | Oct 2012 | A1 |
| 20120269361 | Bhow et al. | Oct 2012 | A1 |
| 20120272145 | Ryan et al. | Oct 2012 | A1 |
| 20120272230 | Lee | Oct 2012 | A1 |
| 20120284185 | Mettler et al. | Nov 2012 | A1 |
| 20120284297 | Aguera-arcas et al. | Nov 2012 | A1 |
| 20120284673 | Lamb et al. | Nov 2012 | A1 |
| 20120290657 | Parks et al. | Nov 2012 | A1 |
| 20120290943 | Toney et al. | Nov 2012 | A1 |
| 20120294118 | Haulick et al. | Nov 2012 | A1 |
| 20120297017 | Livshits et al. | Nov 2012 | A1 |
| 20120304111 | Queru et al. | Nov 2012 | A1 |
| 20120311444 | Chaudhri | Dec 2012 | A1 |
| 20120322508 | Forstall et al. | Dec 2012 | A1 |
| 20120323868 | Robbin et al. | Dec 2012 | A1 |
| 20120324390 | Tao et al. | Dec 2012 | A1 |
| 20130002589 | Jang | Jan 2013 | A1 |
| 20130005487 | Frazzini et al. | Jan 2013 | A1 |
| 20130007203 | Szu | Jan 2013 | A1 |
| 20130007617 | Mackenzie et al. | Jan 2013 | A1 |
| 20130016818 | Cohn | Jan 2013 | A1 |
| 20130017846 | Schoppe | Jan 2013 | A1 |
| 20130022221 | Kallai et al. | Jan 2013 | A1 |
| 20130024932 | Toebes et al. | Jan 2013 | A1 |
| 20130026293 | Schneider et al. | Jan 2013 | A1 |
| 20130027289 | Choi et al. | Jan 2013 | A1 |
| 20130027341 | Mastandrea | Jan 2013 | A1 |
| 20130031217 | Rajapakse | Jan 2013 | A1 |
| 20130041790 | Murugesan et al. | Feb 2013 | A1 |
| 20130046893 | Hauser et al. | Feb 2013 | A1 |
| 20130047084 | Sanders et al. | Feb 2013 | A1 |
| 20130047233 | Fisk et al. | Feb 2013 | A1 |
| 20130051755 | Brown et al. | Feb 2013 | A1 |
| 20130053107 | Kang et al. | Feb 2013 | A1 |
| 20130054697 | Cha et al. | Feb 2013 | A1 |
| 20130055082 | Fino et al. | Feb 2013 | A1 |
| 20130055150 | Galor | Feb 2013 | A1 |
| 20130060687 | Bak et al. | Mar 2013 | A1 |
| 20130061155 | Hon | Mar 2013 | A1 |
| 20130063364 | Moore | Mar 2013 | A1 |
| 20130073286 | Bastea-forte et al. | Mar 2013 | A1 |
| 20130073584 | Kuper et al. | Mar 2013 | A1 |
| 20130074194 | White et al. | Mar 2013 | A1 |
| 20130080177 | Chen | Mar 2013 | A1 |
| 20130080516 | Bologh | Mar 2013 | A1 |
| 20130080525 | Aoki et al. | Mar 2013 | A1 |
| 20130080955 | Reimann et al. | Mar 2013 | A1 |
| 20130082819 | Cotterill | Apr 2013 | A1 |
| 20130086637 | Cotterill et al. | Apr 2013 | A1 |
| 20130091205 | Kotler et al. | Apr 2013 | A1 |
| 20130094666 | Haaff et al. | Apr 2013 | A1 |
| 20130094770 | Lee et al. | Apr 2013 | A1 |
| 20130102281 | Kanda et al. | Apr 2013 | A1 |
| 20130102298 | Goodman et al. | Apr 2013 | A1 |
| 20130103797 | Park et al. | Apr 2013 | A1 |
| 20130111407 | Mullen | May 2013 | A1 |
| 20130113822 | Putrevu et al. | May 2013 | A1 |
| 20130115932 | Williams et al. | May 2013 | A1 |
| 20130117693 | Anderson et al. | May 2013 | A1 |
| 20130120106 | Cauwels et al. | May 2013 | A1 |
| 20130120254 | Mun et al. | May 2013 | A1 |
| 20130124207 | Sarin et al. | May 2013 | A1 |
| 20130132865 | Li | May 2013 | A1 |
| 20130138272 | Louise-babando et al. | May 2013 | A1 |
| 20130141378 | Yumiki et al. | Jun 2013 | A1 |
| 20130141514 | Chao et al. | Jun 2013 | A1 |
| 20130145303 | Prakash et al. | Jun 2013 | A1 |
| 20130148020 | Cook | Jun 2013 | A1 |
| 20130159858 | Joffray et al. | Jun 2013 | A1 |
| 20130162411 | Moses et al. | Jun 2013 | A1 |
| 20130166332 | Hammad | Jun 2013 | A1 |
| 20130173699 | Parks et al. | Jul 2013 | A1 |
| 20130173794 | Agerbak et al. | Jul 2013 | A1 |
| 20130174044 | Hill | Jul 2013 | A1 |
| 20130189963 | Epp et al. | Jul 2013 | A1 |
| 20130191220 | Dent et al. | Jul 2013 | A1 |
| 20130191454 | Oliver et al. | Jul 2013 | A1 |
| 20130191911 | Dellinger et al. | Jul 2013 | A1 |
| 20130194476 | Shimosato | Aug 2013 | A1 |
| 20130205375 | Woxblom et al. | Aug 2013 | A1 |
| 20130212212 | Addepalli et al. | Aug 2013 | A1 |
| 20130222270 | Winkler et al. | Aug 2013 | A1 |
| 20130223821 | Issa et al. | Aug 2013 | A1 |
| 20130231127 | Kildal et al. | Sep 2013 | A1 |
| 20130234924 | Janefalkar et al. | Sep 2013 | A1 |
| 20130239202 | Adams et al. | Sep 2013 | A1 |
| 20130243924 | Bhandari et al. | Sep 2013 | A1 |
| 20130244615 | Miller | Sep 2013 | A1 |
| 20130244633 | Jacobs et al. | Sep 2013 | A1 |
| 20130246522 | Bilinski et al. | Sep 2013 | A1 |
| 20130246916 | Reimann et al. | Sep 2013 | A1 |
| 20130254574 | Zacchio et al. | Sep 2013 | A1 |
| 20130256403 | Mackinnon Keith | Oct 2013 | A1 |
| 20130262298 | Morley et al. | Oct 2013 | A1 |
| 20130262857 | Neuman et al. | Oct 2013 | A1 |
| 20130268593 | Parekh | Oct 2013 | A1 |
| 20130275881 | Hahm | Oct 2013 | A1 |
| 20130282180 | Layton | Oct 2013 | A1 |
| 20130283161 | Reimann et al. | Oct 2013 | A1 |
| 20130283199 | Selig et al. | Oct 2013 | A1 |
| 20130298024 | Rhee et al. | Nov 2013 | A1 |
| 20130304758 | Gruber et al. | Nov 2013 | A1 |
| 20130305354 | King et al. | Nov 2013 | A1 |
| 20130311597 | Arrouye et al. | Nov 2013 | A1 |
| 20130311986 | Arrouye et al. | Nov 2013 | A1 |
| 20130311997 | Gruber et al. | Nov 2013 | A1 |
| 20130314302 | Jeung et al. | Nov 2013 | A1 |
| 20130318158 | Teng et al. | Nov 2013 | A1 |
| 20130318249 | Mcdonough et al. | Nov 2013 | A1 |
| 20130322634 | Bennett et al. | Dec 2013 | A1 |
| 20130324081 | Gargi et al. | Dec 2013 | A1 |
| 20130325967 | Parks et al. | Dec 2013 | A1 |
| 20130329924 | Fleizach et al. | Dec 2013 | A1 |
| 20130332162 | Keen | Dec 2013 | A1 |
| 20130332560 | Knight et al. | Dec 2013 | A1 |
| 20130333006 | Tapling et al. | Dec 2013 | A1 |
| 20130339343 | Hierons et al. | Dec 2013 | A1 |
| 20130346068 | Solem et al. | Dec 2013 | A1 |
| 20130346859 | Bates et al. | Dec 2013 | A1 |
| 20130347022 | Bates et al. | Dec 2013 | A1 |
| 20140003597 | Lazaridis et al. | Jan 2014 | A1 |
| 20140006562 | Handa et al. | Jan 2014 | A1 |
| 20140026188 | Gubler | Jan 2014 | A1 |
| 20140032706 | Kuscher et al. | Jan 2014 | A1 |
| 20140033035 | Crow et al. | Jan 2014 | A1 |
| 20140037107 | Marino et al. | Feb 2014 | A1 |
| 20140040742 | Park et al. | Feb 2014 | A1 |
| 20140043424 | Gava et al. | Feb 2014 | A1 |
| 20140045463 | Hsieh et al. | Feb 2014 | A1 |
| 20140046464 | Reimann | Feb 2014 | A1 |
| 20140047020 | Matus et al. | Feb 2014 | A1 |
| 20140047382 | Kim et al. | Feb 2014 | A1 |
| 20140049447 | Choi | Feb 2014 | A1 |
| 20140058860 | Roh et al. | Feb 2014 | A1 |
| 20140058941 | Moon et al. | Feb 2014 | A1 |
| 20140064155 | Evans et al. | Mar 2014 | A1 |
| 20140068751 | Last | Mar 2014 | A1 |
| 20140072282 | Cho | Mar 2014 | A1 |
| 20140073256 | Newham et al. | Mar 2014 | A1 |
| 20140075130 | Bansal et al. | Mar 2014 | A1 |
| 20140075311 | Boettcher et al. | Mar 2014 | A1 |
| 20140080416 | Seo et al. | Mar 2014 | A1 |
| 20140082136 | Garcia Puga et al. | Mar 2014 | A1 |
| 20140082715 | Grajek et al. | Mar 2014 | A1 |
| 20140089196 | Paya et al. | Mar 2014 | A1 |
| 20140095965 | Li | Apr 2014 | A1 |
| 20140104178 | Jo | Apr 2014 | A1 |
| 20140114966 | Bilinski et al. | Apr 2014 | A1 |
| 20140122730 | Burch et al. | May 2014 | A1 |
| 20140136481 | Quan et al. | May 2014 | A1 |
| 20140136986 | Martin et al. | May 2014 | A1 |
| 20140139422 | Mistry et al. | May 2014 | A1 |
| 20140139637 | Mistry et al. | May 2014 | A1 |
| 20140143737 | Mistry et al. | May 2014 | A1 |
| 20140149884 | Flynn et al. | May 2014 | A1 |
| 20140155031 | Lee et al. | Jun 2014 | A1 |
| 20140155123 | Lee et al. | Jun 2014 | A1 |
| 20140157160 | Cudak et al. | Jun 2014 | A1 |
| 20140165012 | Shen et al. | Jun 2014 | A1 |
| 20140168696 | Matsuhara et al. | Jun 2014 | A1 |
| 20140171064 | Das | Jun 2014 | A1 |
| 20140171156 | Pattikonda et al. | Jun 2014 | A1 |
| 20140173447 | Das et al. | Jun 2014 | A1 |
| 20140176298 | Kumar et al. | Jun 2014 | A1 |
| 20140181183 | Yamamoto et al. | Jun 2014 | A1 |
| 20140181202 | Gossain | Jun 2014 | A1 |
| 20140181654 | Kumar et al. | Jun 2014 | A1 |
| 20140189589 | Kim et al. | Jul 2014 | A1 |
| 20140207707 | Na et al. | Jul 2014 | A1 |
| 20140215413 | Calkins et al. | Jul 2014 | A1 |
| 20140223490 | Pan et al. | Aug 2014 | A1 |
| 20140229835 | Ravine | Aug 2014 | A1 |
| 20140236325 | Sasaki et al. | Aug 2014 | A1 |
| 20140237361 | Martin et al. | Aug 2014 | A1 |
| 20140247229 | Cho et al. | Sep 2014 | A1 |
| 20140258292 | Thramann et al. | Sep 2014 | A1 |
| 20140267002 | Luna | Sep 2014 | A1 |
| 20140267911 | Grant et al. | Sep 2014 | A1 |
| 20140270183 | Luna | Sep 2014 | A1 |
| 20140282103 | Jerry | Sep 2014 | A1 |
| 20140282240 | Flynn et al. | Sep 2014 | A1 |
| 20140283018 | Dadu et al. | Sep 2014 | A1 |
| 20140298432 | Brown | Oct 2014 | A1 |
| 20140310348 | Keskitalo et al. | Oct 2014 | A1 |
| 20140320387 | Eriksson et al. | Oct 2014 | A1 |
| 20140320425 | Jeong et al. | Oct 2014 | A1 |
| 20140325447 | Jin et al. | Oct 2014 | A1 |
| 20140334644 | Selig et al. | Nov 2014 | A1 |
| 20140335789 | Cohen et al. | Nov 2014 | A1 |
| 20140337791 | Agnetta et al. | Nov 2014 | A1 |
| 20140337931 | Cotterill | Nov 2014 | A1 |
| 20140344904 | Venkataramani et al. | Nov 2014 | A1 |
| 20140354759 | Cranfill et al. | Dec 2014 | A1 |
| 20140359140 | Shankarraman | Dec 2014 | A1 |
| 20140359454 | Lee et al. | Dec 2014 | A1 |
| 20140359637 | Yan | Dec 2014 | A1 |
| 20140359709 | Nassar et al. | Dec 2014 | A1 |
| 20140362293 | Bakar et al. | Dec 2014 | A1 |
| 20140363024 | Apodaca | Dec 2014 | A1 |
| 20140364056 | Belk et al. | Dec 2014 | A1 |
| 20140365904 | Kim et al. | Dec 2014 | A1 |
| 20140372309 | Bullard et al. | Dec 2014 | A1 |
| 20140375577 | Yeh et al. | Dec 2014 | A1 |
| 20140380187 | Gardenfors et al. | Dec 2014 | A1 |
| 20140380234 | Shim et al. | Dec 2014 | A1 |
| 20150012435 | Wright et al. | Jan 2015 | A1 |
| 20150019944 | Kalgi | Jan 2015 | A1 |
| 20150020081 | Cho et al. | Jan 2015 | A1 |
| 20150032812 | Dudley | Jan 2015 | A1 |
| 20150033361 | Choi et al. | Jan 2015 | A1 |
| 20150039494 | Sinton et al. | Feb 2015 | A1 |
| 20150040012 | Faaborg et al. | Feb 2015 | A1 |
| 20150046828 | Desai et al. | Feb 2015 | A1 |
| 20150049591 | Adams et al. | Feb 2015 | A1 |
| 20150051913 | Choi | Feb 2015 | A1 |
| 20150052222 | Farrell et al. | Feb 2015 | A1 |
| 20150058744 | Dhingra et al. | Feb 2015 | A1 |
| 20150067803 | Alduaiji | Mar 2015 | A1 |
| 20150081072 | Kallai et al. | Mar 2015 | A1 |
| 20150085057 | Ouyang et al. | Mar 2015 | A1 |
| 20150089359 | Brisebois | Mar 2015 | A1 |
| 20150095175 | Dua | Apr 2015 | A1 |
| 20150095804 | Grossman et al. | Apr 2015 | A1 |
| 20150098309 | Adams et al. | Apr 2015 | A1 |
| 20150100623 | Gudell et al. | Apr 2015 | A1 |
| 20150111559 | Leaver et al. | Apr 2015 | A1 |
| 20150113407 | Hoffert et al. | Apr 2015 | A1 |
| 20150120545 | Fiore et al. | Apr 2015 | A1 |
| 20150130737 | Im et al. | May 2015 | A1 |
| 20150135049 | Murphy | May 2015 | A1 |
| 20150135282 | Kong et al. | May 2015 | A1 |
| 20150138101 | Park et al. | May 2015 | A1 |
| 20150143419 | Bhagwat et al. | May 2015 | A1 |
| 20150148927 | Georges et al. | May 2015 | A1 |
| 20150149599 | Caunter et al. | May 2015 | A1 |
| 20150154589 | Li | Jun 2015 | A1 |
| 20150154676 | Matousek et al. | Jun 2015 | A1 |
| 20150160856 | Jang et al. | Jun 2015 | A1 |
| 20150163188 | Faaborg et al. | Jun 2015 | A1 |
| 20150177914 | Coyner et al. | Jun 2015 | A1 |
| 20150179008 | Sung et al. | Jun 2015 | A1 |
| 20150186892 | Zhang et al. | Jul 2015 | A1 |
| 20150189426 | Pang | Jul 2015 | A1 |
| 20150193069 | Di Censo et al. | Jul 2015 | A1 |
| 20150193127 | Chai et al. | Jul 2015 | A1 |
| 20150193130 | Cho et al. | Jul 2015 | A1 |
| 20150193196 | Lin et al. | Jul 2015 | A1 |
| 20150193392 | Greenblatt et al. | Jul 2015 | A1 |
| 20150195133 | Sheets et al. | Jul 2015 | A1 |
| 20150199967 | Reddy et al. | Jul 2015 | A1 |
| 20150200715 | Oiwa et al. | Jul 2015 | A1 |
| 20150205353 | Feng et al. | Jul 2015 | A1 |
| 20150205511 | Vinna et al. | Jul 2015 | A1 |
| 20150205971 | Sanio et al. | Jul 2015 | A1 |
| 20150206529 | Kwon et al. | Jul 2015 | A1 |
| 20150208158 | Sanders | Jul 2015 | A1 |
| 20150212681 | Shinozaki et al. | Jul 2015 | A1 |
| 20150212705 | Sasaki et al. | Jul 2015 | A1 |
| 20150213542 | Wallaja | Jul 2015 | A1 |
| 20150215128 | Pal | Jul 2015 | A1 |
| 20150215382 | Arora et al. | Jul 2015 | A1 |
| 20150215398 | Murphy et al. | Jul 2015 | A1 |
| 20150222615 | Allain et al. | Aug 2015 | A1 |
| 20150222680 | Grover | Aug 2015 | A1 |
| 20150223005 | Hardman et al. | Aug 2015 | A1 |
| 20150229650 | Grigg et al. | Aug 2015 | A1 |
| 20150229750 | Zhou et al. | Aug 2015 | A1 |
| 20150229782 | Zuidema et al. | Aug 2015 | A1 |
| 20150242065 | Ko et al. | Aug 2015 | A1 |
| 20150242073 | Munoz et al. | Aug 2015 | A1 |
| 20150242597 | Danciu | Aug 2015 | A1 |
| 20150242611 | Cotterill | Aug 2015 | A1 |
| 20150242837 | Yarbrough et al. | Aug 2015 | A1 |
| 20150243163 | Shoemake | Aug 2015 | A1 |
| 20150248200 | Cho et al. | Sep 2015 | A1 |
| 20150248268 | Kumar et al. | Sep 2015 | A1 |
| 20150249540 | Khalil et al. | Sep 2015 | A1 |
| 20150253960 | Lin et al. | Sep 2015 | A1 |
| 20150254661 | Lanc | Sep 2015 | A1 |
| 20150256957 | Kim et al. | Sep 2015 | A1 |
| 20150261493 | Lemmon et al. | Sep 2015 | A1 |
| 20150262183 | Gervais et al. | Sep 2015 | A1 |
| 20150264304 | Chastney et al. | Sep 2015 | A1 |
| 20150271120 | Langholz | Sep 2015 | A1 |
| 20150278799 | Palanisamy | Oct 2015 | A1 |
| 20150286360 | Wachter | Oct 2015 | A1 |
| 20150286694 | Kaplinger et al. | Oct 2015 | A1 |
| 20150286813 | Jakobsson | Oct 2015 | A1 |
| 20150295921 | Cao | Oct 2015 | A1 |
| 20150302856 | Kim et al. | Oct 2015 | A1 |
| 20150304330 | Soamboonsrup et al. | Oct 2015 | A1 |
| 20150309768 | Van Der Heide | Oct 2015 | A1 |
| 20150312299 | Chen | Oct 2015 | A1 |
| 20150319006 | Plummer et al. | Nov 2015 | A1 |
| 20150319046 | Plummer et al. | Nov 2015 | A1 |
| 20150324552 | Beckhardt | Nov 2015 | A1 |
| 20150339466 | Gao et al. | Nov 2015 | A1 |
| 20150347010 | Yang et al. | Dec 2015 | A1 |
| 20150347738 | Ulrich et al. | Dec 2015 | A1 |
| 20150348002 | Van et al. | Dec 2015 | A1 |
| 20150348014 | Van Os et al. | Dec 2015 | A1 |
| 20150350031 | Burks et al. | Dec 2015 | A1 |
| 20150350296 | Yang et al. | Dec 2015 | A1 |
| 20150350297 | Yang et al. | Dec 2015 | A1 |
| 20150350448 | Coffman et al. | Dec 2015 | A1 |
| 20150355816 | Shim | Dec 2015 | A1 |
| 20150355818 | Corbin | Dec 2015 | A1 |
| 20150355879 | Beckhardt et al. | Dec 2015 | A1 |
| 20150356278 | Britt et al. | Dec 2015 | A1 |
| 20150358043 | Jeong et al. | Dec 2015 | A1 |
| 20150358304 | Beckhardt et al. | Dec 2015 | A1 |
| 20150365400 | Cox | Dec 2015 | A1 |
| 20150370426 | Carrigan et al. | Dec 2015 | A1 |
| 20150370455 | Van Os et al. | Dec 2015 | A1 |
| 20150373172 | Boesen | Dec 2015 | A1 |
| 20150373178 | Felt et al. | Dec 2015 | A1 |
| 20150378522 | Butts | Dec 2015 | A1 |
| 20160004393 | Faaborg et al. | Jan 2016 | A1 |
| 20160004417 | Bates | Jan 2016 | A1 |
| 20160004499 | Kim et al. | Jan 2016 | A1 |
| 20160005024 | Harrell | Jan 2016 | A1 |
| 20160005189 | Gray et al. | Jan 2016 | A1 |
| 20160006745 | Furuichi et al. | Jan 2016 | A1 |
| 20160011850 | Sheen et al. | Jan 2016 | A1 |
| 20160012417 | Mizon | Jan 2016 | A1 |
| 20160014266 | Bhatt | Jan 2016 | A1 |
| 20160026429 | Triplett | Jan 2016 | A1 |
| 20160026779 | Grigg et al. | Jan 2016 | A1 |
| 20160028869 | Bhatt | Jan 2016 | A1 |
| 20160029146 | Tembey et al. | Jan 2016 | A1 |
| 20160034887 | Lee | Feb 2016 | A1 |
| 20160036996 | Midholt et al. | Feb 2016 | A1 |
| 20160037345 | Margadoudakis | Feb 2016 | A1 |
| 20160043962 | Kim et al. | Feb 2016 | A1 |
| 20160048705 | Yang | Feb 2016 | A1 |
| 20160050199 | Ganesan | Feb 2016 | A1 |
| 20160050476 | Patil | Feb 2016 | A1 |
| 20160054710 | Jo et al. | Feb 2016 | A1 |
| 20160062487 | Foss et al. | Mar 2016 | A1 |
| 20160062567 | Yang et al. | Mar 2016 | A1 |
| 20160062589 | Wan et al. | Mar 2016 | A1 |
| 20160062606 | Vega et al. | Mar 2016 | A1 |
| 20160062719 | Romano et al. | Mar 2016 | A1 |
| 20160065707 | Yang et al. | Mar 2016 | A1 |
| 20160065708 | Yang et al. | Mar 2016 | A1 |
| 20160066277 | Yang et al. | Mar 2016 | A1 |
| 20160070244 | Cipollo et al. | Mar 2016 | A1 |
| 20160073197 | Hammer et al. | Mar 2016 | A1 |
| 20160073482 | Fok et al. | Mar 2016 | A1 |
| 20160077734 | Buxton et al. | Mar 2016 | A1 |
| 20160086176 | Henrique et al. | Mar 2016 | A1 |
| 20160088039 | Millington et al. | Mar 2016 | A1 |
| 20160092072 | So et al. | Mar 2016 | A1 |
| 20160092665 | Cowan et al. | Mar 2016 | A1 |
| 20160097651 | Jung et al. | Apr 2016 | A1 |
| 20160099901 | Allen et al. | Apr 2016 | A1 |
| 20160127799 | Alsina et al. | May 2016 | A1 |
| 20160132132 | Li | May 2016 | A1 |
| 20160132864 | Shah et al. | May 2016 | A1 |
| 20160134488 | Straub et al. | May 2016 | A1 |
| 20160134942 | Lo | May 2016 | A1 |
| 20160139752 | Shim et al. | May 2016 | A1 |
| 20160142763 | Kim et al. | May 2016 | A1 |
| 20160150624 | Meerbeek et al. | May 2016 | A1 |
| 20160155443 | Khan et al. | Jun 2016 | A1 |
| 20160156687 | Leung | Jun 2016 | A1 |
| 20160156957 | Yun | Jun 2016 | A1 |
| 20160156992 | Kuper | Jun 2016 | A1 |
| 20160162252 | Di Censo et al. | Jun 2016 | A1 |
| 20160171482 | Muncey et al. | Jun 2016 | A1 |
| 20160173318 | Ha et al. | Jun 2016 | A1 |
| 20160173617 | Allinson | Jun 2016 | A1 |
| 20160183046 | Kwon | Jun 2016 | A1 |
| 20160189451 | Yoo et al. | Jun 2016 | A1 |
| 20160196042 | Laute et al. | Jul 2016 | A1 |
| 20160196106 | Hammer et al. | Jul 2016 | A1 |
| 20160202866 | Zambetti | Jul 2016 | A1 |
| 20160209939 | Zambetti et al. | Jul 2016 | A1 |
| 20160210602 | Siddique et al. | Jul 2016 | A1 |
| 20160210983 | Amada et al. | Jul 2016 | A1 |
| 20160224966 | Van Os et al. | Aug 2016 | A1 |
| 20160231902 | Sirpal et al. | Aug 2016 | A1 |
| 20160239167 | Reimann et al. | Aug 2016 | A1 |
| 20160241543 | Jung et al. | Aug 2016 | A1 |
| 20160241983 | Lambourne et al. | Aug 2016 | A1 |
| 20160246566 | Fullerton et al. | Aug 2016 | A1 |
| 20160253145 | Lee et al. | Sep 2016 | A1 |
| 20160259656 | Sumner et al. | Sep 2016 | A1 |
| 20160259936 | Mukherjee et al. | Sep 2016 | A1 |
| 20160267319 | Murillo et al. | Sep 2016 | A1 |
| 20160267779 | Kuang | Sep 2016 | A1 |
| 20160277708 | Rintel et al. | Sep 2016 | A1 |
| 20160277903 | Poosala et al. | Sep 2016 | A1 |
| 20160291824 | Grossman et al. | Oct 2016 | A1 |
| 20160291924 | Bierbower et al. | Oct 2016 | A1 |
| 20160295340 | Baker et al. | Oct 2016 | A1 |
| 20160299669 | Bates | Oct 2016 | A1 |
| 20160299736 | Bates et al. | Oct 2016 | A1 |
| 20160314451 | Martin | Oct 2016 | A1 |
| 20160320849 | Koo | Nov 2016 | A1 |
| 20160335041 | Wachter et al. | Nov 2016 | A1 |
| 20160336531 | Yokoyama | Nov 2016 | A1 |
| 20160342141 | Koumaiha et al. | Nov 2016 | A1 |
| 20160342386 | Kallai et al. | Nov 2016 | A1 |
| 20160345039 | Billmeyer | Nov 2016 | A1 |
| 20160345172 | Cotterill | Nov 2016 | A1 |
| 20160350839 | Avidor et al. | Dec 2016 | A1 |
| 20160351191 | Vilermo et al. | Dec 2016 | A1 |
| 20160352661 | Yang et al. | Dec 2016 | A1 |
| 20160357507 | Decker et al. | Dec 2016 | A1 |
| 20160360344 | Shim et al. | Dec 2016 | A1 |
| 20160364600 | Shah et al. | Dec 2016 | A1 |
| 20160366481 | Lim et al. | Dec 2016 | A1 |
| 20160366531 | Popova | Dec 2016 | A1 |
| 20160372113 | David et al. | Dec 2016 | A1 |
| 20160373884 | Peterson et al. | Dec 2016 | A1 |
| 20160378424 | Kanda et al. | Dec 2016 | A1 |
| 20160378961 | Park | Dec 2016 | A1 |
| 20160379205 | Margadoudakis | Dec 2016 | A1 |
| 20160381476 | Gossain et al. | Dec 2016 | A1 |
| 20170003931 | Dvortsov et al. | Jan 2017 | A1 |
| 20170010782 | Chaudhri et al. | Jan 2017 | A1 |
| 20170010794 | Cho et al. | Jan 2017 | A1 |
| 20170013562 | Lim et al. | Jan 2017 | A1 |
| 20170017531 | Choi et al. | Jan 2017 | A1 |
| 20170019517 | Wilder et al. | Jan 2017 | A1 |
| 20170025124 | Mixter et al. | Jan 2017 | A1 |
| 20170026686 | Glazier et al. | Jan 2017 | A1 |
| 20170031552 | Lin | Feb 2017 | A1 |
| 20170031648 | So et al. | Feb 2017 | A1 |
| 20170041727 | Reimann | Feb 2017 | A1 |
| 20170046025 | Dascola et al. | Feb 2017 | A1 |
| 20170054731 | Cotterill | Feb 2017 | A1 |
| 20170068402 | Lochhead et al. | Mar 2017 | A1 |
| 20170068507 | Kim et al. | Mar 2017 | A1 |
| 20170070346 | Lombardi et al. | Mar 2017 | A1 |
| 20170078294 | Medvinsky | Mar 2017 | A1 |
| 20170083285 | Meyers et al. | Mar 2017 | A1 |
| 20170083494 | Kim et al. | Mar 2017 | A1 |
| 20170092085 | Agarwal | Mar 2017 | A1 |
| 20170092270 | Newendorp et al. | Mar 2017 | A1 |
| 20170093846 | Lopez Lecube et al. | Mar 2017 | A1 |
| 20170097621 | Ackmann et al. | Apr 2017 | A1 |
| 20170099270 | Anson | Apr 2017 | A1 |
| 20170115940 | Byeon | Apr 2017 | A1 |
| 20170127145 | Rajapakse | May 2017 | A1 |
| 20170134553 | Jeon et al. | May 2017 | A1 |
| 20170134567 | Jeon et al. | May 2017 | A1 |
| 20170134872 | Silva et al. | May 2017 | A1 |
| 20170140372 | Wang et al. | May 2017 | A1 |
| 20170142087 | Maninder et al. | May 2017 | A1 |
| 20170142584 | Oh et al. | May 2017 | A1 |
| 20170148010 | Bak et al. | May 2017 | A1 |
| 20170180843 | Perianu et al. | Jun 2017 | A1 |
| 20170185373 | Kim et al. | Jun 2017 | A1 |
| 20170192730 | Yang et al. | Jul 2017 | A1 |
| 20170193813 | Carroll et al. | Jul 2017 | A1 |
| 20170195772 | Han et al. | Jul 2017 | A1 |
| 20170206779 | Lee et al. | Jul 2017 | A1 |
| 20170212667 | Miyazaki | Jul 2017 | A1 |
| 20170227935 | Su et al. | Aug 2017 | A1 |
| 20170230705 | Pardue et al. | Aug 2017 | A1 |
| 20170235545 | Millington et al. | Aug 2017 | A1 |
| 20170235926 | Fyke et al. | Aug 2017 | A1 |
| 20170235935 | Song et al. | Aug 2017 | A1 |
| 20170242653 | Lang et al. | Aug 2017 | A1 |
| 20170251314 | Pye et al. | Aug 2017 | A1 |
| 20170269556 | Zhou | Sep 2017 | A1 |
| 20170270507 | Wang et al. | Sep 2017 | A1 |
| 20170285788 | Park et al. | Oct 2017 | A1 |
| 20170289249 | Knight et al. | Oct 2017 | A1 |
| 20170322713 | Hwang et al. | Nov 2017 | A1 |
| 20170339151 | Van Os et al. | Nov 2017 | A1 |
| 20170357420 | Dye et al. | Dec 2017 | A1 |
| 20170357421 | Dye et al. | Dec 2017 | A1 |
| 20170357425 | Smith et al. | Dec 2017 | A1 |
| 20170357434 | Coffman et al. | Dec 2017 | A1 |
| 20170357439 | Lemay et al. | Dec 2017 | A1 |
| 20170357477 | Im et al. | Dec 2017 | A1 |
| 20170357973 | Van Os et al. | Dec 2017 | A1 |
| 20170359189 | Smith et al. | Dec 2017 | A1 |
| 20170359191 | Smith et al. | Dec 2017 | A1 |
| 20170363436 | Eronen et al. | Dec 2017 | A1 |
| 20180039916 | Ravindra | Feb 2018 | A1 |
| 20180040324 | Wilberding | Feb 2018 | A1 |
| 20180067712 | Behzadi et al. | Mar 2018 | A1 |
| 20180067904 | Li | Mar 2018 | A1 |
| 20180069957 | Mushikabe et al. | Mar 2018 | A1 |
| 20180070187 | Drinkwater et al. | Mar 2018 | A1 |
| 20180075439 | Bak et al. | Mar 2018 | A1 |
| 20180091381 | Mclaughlin et al. | Mar 2018 | A1 |
| 20180096064 | Lennon | Apr 2018 | A1 |
| 20180101297 | Yang et al. | Apr 2018 | A1 |
| 20180109629 | Van Os et al. | Apr 2018 | A1 |
| 20180124128 | Faulkner et al. | May 2018 | A1 |
| 20180131732 | Aronoff et al. | May 2018 | A1 |
| 20180139292 | Koren et al. | May 2018 | A1 |
| 20180190279 | Anderson et al. | Jul 2018 | A1 |
| 20180199137 | Mate et al. | Jul 2018 | A1 |
| 20180205797 | Faulkner | Jul 2018 | A1 |
| 20180217709 | Hotelling | Aug 2018 | A1 |
| 20180227341 | Rizzi | Aug 2018 | A1 |
| 20180228003 | O'driscoll et al. | Aug 2018 | A1 |
| 20180234549 | Coffman et al. | Aug 2018 | A1 |
| 20180267773 | Kim et al. | Sep 2018 | A1 |
| 20180286395 | Li et al. | Oct 2018 | A1 |
| 20180302790 | Cotterill | Oct 2018 | A1 |
| 20180308480 | Jang et al. | Oct 2018 | A1 |
| 20180329585 | Carrigan et al. | Nov 2018 | A1 |
| 20180329586 | Sundstrom et al. | Nov 2018 | A1 |
| 20180332559 | Gudivada et al. | Nov 2018 | A1 |
| 20180335903 | Coffman et al. | Nov 2018 | A1 |
| 20180337924 | Graham et al. | Nov 2018 | A1 |
| 20180338038 | Ly et al. | Nov 2018 | A1 |
| 20180341448 | Behzadi et al. | Nov 2018 | A1 |
| 20180351762 | Iyengar et al. | Dec 2018 | A1 |
| 20180357631 | Bak et al. | Dec 2018 | A1 |
| 20180364665 | Clymer et al. | Dec 2018 | A1 |
| 20180375676 | Bader-natal et al. | Dec 2018 | A1 |
| 20190012069 | Bates | Jan 2019 | A1 |
| 20190012073 | Hwang | Jan 2019 | A1 |
| 20190012966 | Shi | Jan 2019 | A1 |
| 20190025943 | Jobs et al. | Jan 2019 | A1 |
| 20190028419 | Sullivan | Jan 2019 | A1 |
| 20190056854 | Azzolin et al. | Feb 2019 | A1 |
| 20190056907 | So et al. | Feb 2019 | A1 |
| 20190058777 | Chen | Feb 2019 | A1 |
| 20190076084 | Kanegae et al. | Mar 2019 | A1 |
| 20190102145 | Wilberding et al. | Apr 2019 | A1 |
| 20190124203 | Coffman et al. | Apr 2019 | A1 |
| 20190124510 | Cotterill | Apr 2019 | A1 |
| 20190124745 | Mason et al. | Apr 2019 | A1 |
| 20190129661 | Hirota et al. | May 2019 | A1 |
| 20190138951 | Brownhill et al. | May 2019 | A1 |
| 20190149972 | Parks et al. | May 2019 | A1 |
| 20190158645 | Yang et al. | May 2019 | A1 |
| 20190163329 | Yang et al. | May 2019 | A1 |
| 20190199963 | Ahn et al. | Jun 2019 | A1 |
| 20190222775 | Ahn | Jul 2019 | A1 |
| 20190278900 | Yang et al. | Sep 2019 | A1 |
| 20190279634 | Tak et al. | Sep 2019 | A1 |
| 20190289079 | Van Os et al. | Sep 2019 | A1 |
| 20190294406 | Bierbower et al. | Sep 2019 | A1 |
| 20190297439 | Maeda | Sep 2019 | A1 |
| 20190306607 | Clayton et al. | Oct 2019 | A1 |
| 20190332400 | Spoor et al. | Oct 2019 | A1 |
| 20190339769 | Cox et al. | Nov 2019 | A1 |
| 20190342519 | Van Os et al. | Nov 2019 | A1 |
| 20190354252 | Badr | Nov 2019 | A1 |
| 20190361575 | Ni et al. | Nov 2019 | A1 |
| 20190361729 | Gruber et al. | Nov 2019 | A1 |
| 20200050426 | Jung et al. | Feb 2020 | A1 |
| 20200050502 | Ghafourifar et al. | Feb 2020 | A1 |
| 20200104018 | Coffman et al. | Apr 2020 | A1 |
| 20200120503 | Cotterill | Apr 2020 | A1 |
| 20200135191 | Nourbakhsh | Apr 2020 | A1 |
| 20200152186 | Koh et al. | May 2020 | A1 |
| 20200154583 | Lee et al. | May 2020 | A1 |
| 20200186378 | Six et al. | Jun 2020 | A1 |
| 20200192627 | Jang et al. | Jun 2020 | A1 |
| 20200201491 | Coffman et al. | Jun 2020 | A1 |
| 20200201495 | Coffman et al. | Jun 2020 | A1 |
| 20200213437 | Bhatt | Jul 2020 | A1 |
| 20200213530 | Ahn | Jul 2020 | A1 |
| 20200218486 | Behzadi et al. | Jul 2020 | A1 |
| 20200220914 | Carrigan et al. | Jul 2020 | A1 |
| 20200225817 | Coffman et al. | Jul 2020 | A1 |
| 20200302913 | Marcinkiewicz | Sep 2020 | A1 |
| 20200335187 | Lefkofsky et al. | Oct 2020 | A1 |
| 20200348830 | Bates | Nov 2020 | A1 |
| 20200366742 | Van Os et al. | Nov 2020 | A1 |
| 20200367816 | Panneer Selvam | Nov 2020 | A1 |
| 20200379711 | Graham et al. | Dec 2020 | A1 |
| 20200379712 | Carrigan | Dec 2020 | A1 |
| 20200379713 | Carrigan | Dec 2020 | A1 |
| 20200379714 | Graham et al. | Dec 2020 | A1 |
| 20200379716 | Carrigan et al. | Dec 2020 | A1 |
| 20200379729 | Graham et al. | Dec 2020 | A1 |
| 20200379730 | Graham et al. | Dec 2020 | A1 |
| 20200382332 | Carrigan et al. | Dec 2020 | A1 |
| 20200383157 | Lee et al. | Dec 2020 | A1 |
| 20200395012 | Kim et al. | Dec 2020 | A1 |
| 20200413197 | Carrigan et al. | Dec 2020 | A1 |
| 20210011588 | Coffman et al. | Jan 2021 | A1 |
| 20210011613 | Pisula et al. | Jan 2021 | A1 |
| 20210014610 | Carrigan et al. | Jan 2021 | A1 |
| 20210043189 | Pyun | Feb 2021 | A1 |
| 20210064317 | Juenger et al. | Mar 2021 | A1 |
| 20210065134 | Chhabra et al. | Mar 2021 | A1 |
| 20210099829 | Soto et al. | Apr 2021 | A1 |
| 20210152685 | Li | May 2021 | A1 |
| 20210158830 | Boehlke | May 2021 | A1 |
| 20210173431 | Yang et al. | Jun 2021 | A1 |
| 20210181903 | Carrigan et al. | Jun 2021 | A1 |
| 20210203765 | Yang et al. | Jul 2021 | A1 |
| 20210255816 | Behzadi et al. | Aug 2021 | A1 |
| 20210255819 | Graham et al. | Aug 2021 | A1 |
| 20210263702 | Carrigan | Aug 2021 | A1 |
| 20210266274 | Liu et al. | Aug 2021 | A1 |
| 20210272118 | Van Os et al. | Sep 2021 | A1 |
| 20210321197 | Annamraju | Oct 2021 | A1 |
| 20210323406 | So et al. | Oct 2021 | A1 |
| 20210349680 | Kim et al. | Nov 2021 | A1 |
| 20210352172 | Kim et al. | Nov 2021 | A1 |
| 20210392223 | Coffman et al. | Dec 2021 | A1 |
| 20210407507 | Zhou et al. | Dec 2021 | A1 |
| 20220004356 | Kim et al. | Jan 2022 | A1 |
| 20220043626 | Carrigan | Feb 2022 | A1 |
| 20220058257 | Cotterill | Feb 2022 | A1 |
| 20220100367 | Carrigan et al. | Mar 2022 | A1 |
| 20220100841 | Yang et al. | Mar 2022 | A1 |
| 20220137759 | Yang et al. | May 2022 | A1 |
| 20220163996 | Yang et al. | May 2022 | A1 |
| 20220277037 | Sanders et al. | Sep 2022 | A1 |
| 20220279063 | Coffman et al. | Sep 2022 | A1 |
| 20220286549 | Coffman et al. | Sep 2022 | A1 |
| 20220291832 | Bi | Sep 2022 | A1 |
| 20220303383 | Coffman et al. | Sep 2022 | A1 |
| 20220326817 | Carrigan et al. | Oct 2022 | A1 |
| 20220350482 | Carrigan et al. | Nov 2022 | A1 |
| 20220391166 | Sanders | Dec 2022 | A1 |
| 20230041125 | Kim et al. | Feb 2023 | A1 |
| 20230084551 | Coffman et al. | Mar 2023 | A1 |
| 20230098814 | Carrigan et al. | Mar 2023 | A1 |
| 20230104819 | Coffman et al. | Apr 2023 | A1 |
| 20230106600 | Coffman et al. | Apr 2023 | A1 |
| 20230106761 | Coffman et al. | Apr 2023 | A1 |
| 20230168797 | Chaudhri et al. | Jun 2023 | A1 |
| 20230179700 | Bhatt | Jun 2023 | A1 |
| 20230246857 | Boucheron et al. | Aug 2023 | A1 |
| 20230266866 | Bates et al. | Aug 2023 | A1 |
| 20230291824 | Yang et al. | Sep 2023 | A1 |
| 20230319413 | Manzari et al. | Oct 2023 | A1 |
| 20230370507 | Chang et al. | Nov 2023 | A1 |
| 20230376268 | Carrigan et al. | Nov 2023 | A1 |
| 20230393714 | Giuliani | Dec 2023 | A1 |
| 20230393809 | Carrigan et al. | Dec 2023 | A1 |
| 20230403509 | Carrigan et al. | Dec 2023 | A1 |
| 20230409191 | Carrigan et al. | Dec 2023 | A1 |
| 20240053953 | Sanders | Feb 2024 | A1 |
| 20240077991 | Von Hagen | Mar 2024 | A1 |
| 20240080642 | Carrigan et al. | Mar 2024 | A1 |
| 20240111333 | Yang et al. | Apr 2024 | A1 |
| 20240126804 | Sanders et al. | Apr 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 060465 | Jun 2008 | AR |
| 2007100826 | Sep 2007 | AU |
| 2008100011 | Feb 2008 | AU |
| 2014100584 | Jul 2014 | AU |
| 2532145 | Jul 1995 | CA |
| 2798093 | Nov 2011 | CA |
| 2876587 | Feb 2014 | CA |
| 1263425 | Aug 2000 | CN |
| 1274439 | Nov 2000 | CN |
| 1341889 | Mar 2002 | CN |
| 1452739 | Oct 2003 | CN |
| 1525723 | Sep 2004 | CN |
| 1558690 | Dec 2004 | CN |
| 1620677 | May 2005 | CN |
| 1663174 | Aug 2005 | CN |
| 1741104 | Mar 2006 | CN |
| 1797295 | Jul 2006 | CN |
| 1813240 | Aug 2006 | CN |
| 1828599 | Sep 2006 | CN |
| 1846221 | Oct 2006 | CN |
| 1863281 | Nov 2006 | CN |
| 1908981 | Feb 2007 | CN |
| 101002167 | Jul 2007 | CN |
| 101022395 | Aug 2007 | CN |
| 101047521 | Oct 2007 | CN |
| 101107668 | Jan 2008 | CN |
| 101188506 | May 2008 | CN |
| 101243426 | Aug 2008 | CN |
| 101268470 | Sep 2008 | CN |
| 101299694 | Nov 2008 | CN |
| 101309311 | Nov 2008 | CN |
| 101321156 | Dec 2008 | CN |
| 101340274 | Jan 2009 | CN |
| 101341718 | Jan 2009 | CN |
| 101341727 | Jan 2009 | CN |
| 101350938 | Jan 2009 | CN |
| 101359291 | Feb 2009 | CN |
| 101409743 | Apr 2009 | CN |
| 101485128 | Jul 2009 | CN |
| 101488138 | Jul 2009 | CN |
| 100530059 | Aug 2009 | CN |
| 101501657 | Aug 2009 | CN |
| 101517563 | Aug 2009 | CN |
| 101567858 | Oct 2009 | CN |
| 101610155 | Dec 2009 | CN |
| 101625620 | Jan 2010 | CN |
| 101673207 | Mar 2010 | CN |
| 101673298 | Mar 2010 | CN |
| 101854278 | Oct 2010 | CN |
| 101861562 | Oct 2010 | CN |
| 101873386 | Oct 2010 | CN |
| 101877748 | Nov 2010 | CN |
| 101882409 | Nov 2010 | CN |
| 101931655 | Dec 2010 | CN |
| 101976171 | Feb 2011 | CN |
| 102065148 | May 2011 | CN |
| 102077191 | May 2011 | CN |
| 102164213 | Aug 2011 | CN |
| 201928419 | Aug 2011 | CN |
| 102202192 | Sep 2011 | CN |
| 102209321 | Oct 2011 | CN |
| 102262506 | Nov 2011 | CN |
| 102281294 | Dec 2011 | CN |
| 102301323 | Dec 2011 | CN |
| 102396205 | Mar 2012 | CN |
| 102414755 | Apr 2012 | CN |
| 102450040 | May 2012 | CN |
| 102508707 | Jun 2012 | CN |
| 102695302 | Sep 2012 | CN |
| 102707994 | Oct 2012 | CN |
| 102737313 | Oct 2012 | CN |
| 102740146 | Oct 2012 | CN |
| 102750066 | Oct 2012 | CN |
| 102750086 | Oct 2012 | CN |
| 102754071 | Oct 2012 | CN |
| 102769705 | Nov 2012 | CN |
| 102859480 | Jan 2013 | CN |
| 102866828 | Jan 2013 | CN |
| 102902453 | Jan 2013 | CN |
| 102905181 | Jan 2013 | CN |
| 102968267 | Mar 2013 | CN |
| 102982401 | Mar 2013 | CN |
| 103067625 | Apr 2013 | CN |
| 103069378 | Apr 2013 | CN |
| 103139370 | Jun 2013 | CN |
| 103250138 | Aug 2013 | CN |
| 103260079 | Aug 2013 | CN |
| 203311163 | Nov 2013 | CN |
| 103425451 | Dec 2013 | CN |
| 103458215 | Dec 2013 | CN |
| 103558916 | Feb 2014 | CN |
| 103576902 | Feb 2014 | CN |
| 103582873 | Feb 2014 | CN |
| 103593154 | Feb 2014 | CN |
| 103604272 | Feb 2014 | CN |
| 103765385 | Apr 2014 | CN |
| 103793075 | May 2014 | CN |
| 103793138 | May 2014 | CN |
| 103853328 | Jun 2014 | CN |
| 103853493 | Jun 2014 | CN |
| 103870255 | Jun 2014 | CN |
| 103914238 | Jul 2014 | CN |
| 104106036 | Oct 2014 | CN |
| 104166458 | Nov 2014 | CN |
| 203942537 | Nov 2014 | CN |
| 104205785 | Dec 2014 | CN |
| 104331796 | Feb 2015 | CN |
| 104335234 | Feb 2015 | CN |
| 104392352 | Mar 2015 | CN |
| 104574054 | Apr 2015 | CN |
| 104867004 | Aug 2015 | CN |
| 104956276 | Sep 2015 | CN |
| 104994106 | Oct 2015 | CN |
| 105208511 | Dec 2015 | CN |
| 105373920 | Mar 2016 | CN |
| 105374192 | Mar 2016 | CN |
| 105388998 | Mar 2016 | CN |
| 105431855 | Mar 2016 | CN |
| 105474580 | Apr 2016 | CN |
| 105549947 | May 2016 | CN |
| 105654286 | Jun 2016 | CN |
| 105654287 | Jun 2016 | CN |
| 105657465 | Jun 2016 | CN |
| 205267230 | Jun 2016 | CN |
| 105745863 | Jul 2016 | CN |
| 105794231 | Jul 2016 | CN |
| 105900376 | Aug 2016 | CN |
| 105940678 | Sep 2016 | CN |
| 106030700 | Oct 2016 | CN |
| 106062810 | Oct 2016 | CN |
| 106134209 | Nov 2016 | CN |
| 106170783 | Nov 2016 | CN |
| 103914238 | Feb 2017 | CN |
| 106383645 | Feb 2017 | CN |
| 106416142 | Feb 2017 | CN |
| 106797415 | May 2017 | CN |
| 107077288 | Aug 2017 | CN |
| 107250949 | Oct 2017 | CN |
| 107533368 | Jan 2018 | CN |
| 107637073 | Jan 2018 | CN |
| 107683470 | Feb 2018 | CN |
| 107819928 | Mar 2018 | CN |
| 107949879 | Apr 2018 | CN |
| 104012150 | May 2018 | CN |
| 108289239 | Jul 2018 | CN |
| 108292203 | Jul 2018 | CN |
| 108683798 | Oct 2018 | CN |
| 108958608 | Dec 2018 | CN |
| 109117078 | Jan 2019 | CN |
| 109196825 | Jan 2019 | CN |
| 109287140 | Jan 2019 | CN |
| 109302531 | Feb 2019 | CN |
| 109314795 | Feb 2019 | CN |
| 109347581 | Feb 2019 | CN |
| 109348052 | Feb 2019 | CN |
| 109461462 | Mar 2019 | CN |
| 109584879 | Apr 2019 | CN |
| 109688441 | Apr 2019 | CN |
| 109688442 | Apr 2019 | CN |
| 108683798 | Apr 2021 | CN |
| 109584879 | Jul 2021 | CN |
| 113835583 | Dec 2021 | CN |
| 108958608 | Jul 2022 | CN |
| 459174 | Dec 1991 | EP |
| 0564247 | Oct 1993 | EP |
| 684543 | Nov 1995 | EP |
| 0844555 | May 1998 | EP |
| 0871177 | Oct 1998 | EP |
| 0880091 | Nov 1998 | EP |
| 0881563 | Dec 1998 | EP |
| 1079371 | Feb 2001 | EP |
| 1133119 | Sep 2001 | EP |
| 1186987 | Mar 2002 | EP |
| 1215575 | Jun 2002 | EP |
| 1357458 | Oct 2003 | EP |
| 1469374 | Oct 2004 | EP |
| 1615109 | Jan 2006 | EP |
| 1705883 | Sep 2006 | EP |
| 1760584 | Mar 2007 | EP |
| 1885109 | Feb 2008 | EP |
| 1942401 | Jul 2008 | EP |
| 2018032 | Jan 2009 | EP |
| 2180665 | Apr 2010 | EP |
| 2194698 | Jun 2010 | EP |
| 2247087 | Nov 2010 | EP |
| 2409214 | Jan 2012 | EP |
| 2420925 | Feb 2012 | EP |
| 2523109 | Nov 2012 | EP |
| 2568693 | Mar 2013 | EP |
| 2600584 | Jun 2013 | EP |
| 2629291 | Aug 2013 | EP |
| 2632193 | Aug 2013 | EP |
| 2674889 | Dec 2013 | EP |
| 2725473 | Apr 2014 | EP |
| 2733579 | May 2014 | EP |
| 2741190 | Jun 2014 | EP |
| 2750062 | Jul 2014 | EP |
| 2770673 | Aug 2014 | EP |
| 2770708 | Aug 2014 | EP |
| 2891049 | Jul 2015 | EP |
| 2892240 | Jul 2015 | EP |
| 2993909 | Mar 2016 | EP |
| 2998822 | Mar 2016 | EP |
| 3032537 | Jun 2016 | EP |
| 3038427 | Jun 2016 | EP |
| 2568693 | Jul 2016 | EP |
| 3057342 | Aug 2016 | EP |
| 3073703 | Sep 2016 | EP |
| 3138300 | Mar 2017 | EP |
| 3163495 | May 2017 | EP |
| 3276905 | Jan 2018 | EP |
| 3379853 | Sep 2018 | EP |
| 2632193 | Oct 2018 | EP |
| 3420441 | Jan 2019 | EP |
| 3445058 | Feb 2019 | EP |
| 2568693 | Dec 2019 | EP |
| 3038427 | Dec 2019 | EP |
| 3633963 | Apr 2020 | EP |
| 3751405 | Dec 2020 | EP |
| 3069679 | Feb 2019 | FR |
| 2341698 | Mar 2000 | GB |
| 0412212 | Jul 2004 | GB |
| 2402105 | Dec 2004 | GB |
| 2466038 | Jun 2010 | GB |
| 2505476 | Mar 2014 | GB |
| 1038MUM2005 | Jun 2007 | IN |
| 5-266169 | Oct 1993 | JP |
| 8-147138 | Jun 1996 | JP |
| 8-166783 | Jun 1996 | JP |
| 9-97154 | Apr 1997 | JP |
| 9-258947 | Oct 1997 | JP |
| 10-198517 | Jul 1998 | JP |
| 10-232757 | Sep 1998 | JP |
| 11-272391 | Oct 1999 | JP |
| 2000-101879 | Apr 2000 | JP |
| 2000-105772 | Apr 2000 | JP |
| 2000-122957 | Apr 2000 | JP |
| 2000-163193 | Jun 2000 | JP |
| 2000-200092 | Jul 2000 | JP |
| 2000-231371 | Aug 2000 | JP |
| 2000-259477 | Sep 2000 | JP |
| 2000-283772 | Oct 2000 | JP |
| 2000-284879 | Oct 2000 | JP |
| 2000-347921 | Dec 2000 | JP |
| 2001-67099 | Mar 2001 | JP |
| 2001-202176 | Jul 2001 | JP |
| 2001-306375 | Nov 2001 | JP |
| 2001-331758 | Nov 2001 | JP |
| 2002-58082 | Feb 2002 | JP |
| 2002-82745 | Mar 2002 | JP |
| 2002-288125 | Oct 2002 | JP |
| 2002-288690 | Oct 2002 | JP |
| 2002-342356 | Nov 2002 | JP |
| 2002-351768 | Dec 2002 | JP |
| 2003-30245 | Jan 2003 | JP |
| 2003-43978 | Feb 2003 | JP |
| 2003-52019 | Feb 2003 | JP |
| 2003-62975 | Mar 2003 | JP |
| 2003-264621 | Sep 2003 | JP |
| 2003-330586 | Nov 2003 | JP |
| 2003-330613 | Nov 2003 | JP |
| 2004-38895 | Feb 2004 | JP |
| 2004-96397 | Mar 2004 | JP |
| 2004-104813 | Apr 2004 | JP |
| 2004-192573 | Jul 2004 | JP |
| 2004-348601 | Dec 2004 | JP |
| 2004-356816 | Dec 2004 | JP |
| 2005-44036 | Feb 2005 | JP |
| 2005-507112 | Mar 2005 | JP |
| 2005-190108 | Jul 2005 | JP |
| 2005-332368 | Dec 2005 | JP |
| 2006-166248 | Jun 2006 | JP |
| 2006-185154 | Jul 2006 | JP |
| 2006-295753 | Oct 2006 | JP |
| 2007-41976 | Feb 2007 | JP |
| 2007-304854 | Nov 2007 | JP |
| 2007-534009 | Nov 2007 | JP |
| 2008-26439 | Feb 2008 | JP |
| 2008-99330 | Apr 2008 | JP |
| 2009-17486 | Jan 2009 | JP |
| 2009-93206 | Apr 2009 | JP |
| 2009-239867 | Oct 2009 | JP |
| 2009-296577 | Dec 2009 | JP |
| 2009-543166 | Dec 2009 | JP |
| 2009-543228 | Dec 2009 | JP |
| 2010-503082 | Jan 2010 | JP |
| 2010-503922 | Feb 2010 | JP |
| 2010-109789 | May 2010 | JP |
| 3162246 | Aug 2010 | JP |
| 2010-198341 | Sep 2010 | JP |
| 2010-245940 | Oct 2010 | JP |
| 2010-257118 | Nov 2010 | JP |
| 2010-271779 | Dec 2010 | JP |
| 2011-60281 | Mar 2011 | JP |
| 2011-65590 | Mar 2011 | JP |
| 2011-118662 | Jun 2011 | JP |
| 2011-209786 | Oct 2011 | JP |
| 2011-237857 | Nov 2011 | JP |
| 2012-168966 | Sep 2012 | JP |
| 2012-215938 | Nov 2012 | JP |
| 2013-25357 | Feb 2013 | JP |
| 2013-506225 | Feb 2013 | JP |
| 2013-74499 | Apr 2013 | JP |
| 2013-93699 | May 2013 | JP |
| 2013-98613 | May 2013 | JP |
| 2013-105468 | May 2013 | JP |
| 2013-530433 | Jul 2013 | JP |
| 2013-530458 | Jul 2013 | JP |
| 2013-175188 | Sep 2013 | JP |
| 2013-191065 | Sep 2013 | JP |
| 2013-200879 | Oct 2013 | JP |
| 2014-503861 | Feb 2014 | JP |
| 2014-44724 | Mar 2014 | JP |
| 2014-71835 | Apr 2014 | JP |
| 2014-87126 | May 2014 | JP |
| 2014-512044 | May 2014 | JP |
| 2014-110638 | Jun 2014 | JP |
| 2014-131359 | Jul 2014 | JP |
| 2014-170982 | Sep 2014 | JP |
| 2015-8001 | Jan 2015 | JP |
| 2015-14923 | Jan 2015 | JP |
| 2015-501022 | Jan 2015 | JP |
| 2015-61318 | Mar 2015 | JP |
| 2015-520456 | Jul 2015 | JP |
| 2015-524974 | Aug 2015 | JP |
| 2015-526776 | Sep 2015 | JP |
| 2015-533441 | Nov 2015 | JP |
| 2016-38615 | Mar 2016 | JP |
| 2016-157292 | Sep 2016 | JP |
| 6023162 | Nov 2016 | JP |
| 2017-34563 | Feb 2017 | JP |
| 2017-41008 | Feb 2017 | JP |
| 2017-143357 | Aug 2017 | JP |
| 2018-7158 | Jan 2018 | JP |
| 2018-147265 | Sep 2018 | JP |
| 2018-200624 | Dec 2018 | JP |
| 10-2003-0030384 | Apr 2003 | KR |
| 10-2005-0072071 | Jul 2005 | KR |
| 10-2007-0101893 | Oct 2007 | KR |
| 10-2007-0120125 | Dec 2007 | KR |
| 10-0805341 | Feb 2008 | KR |
| 20-2008-0004775 | Oct 2008 | KR |
| 10-2009-0089472 | Aug 2009 | KR |
| 10-2009-0125377 | Dec 2009 | KR |
| 10-2010-0036351 | Apr 2010 | KR |
| 10-2012-0003323 | Jan 2012 | KR |
| 10-2012-0088746 | Aug 2012 | KR |
| 10-2012-0100433 | Sep 2012 | KR |
| 10-1253392 | Apr 2013 | KR |
| 10-2013-0063019 | Jun 2013 | KR |
| 10-2013-0075783 | Jul 2013 | KR |
| 10-2013-0082190 | Jul 2013 | KR |
| 10-2013-0108563 | Oct 2013 | KR |
| 10-2013-0141688 | Dec 2013 | KR |
| 101342208 | Dec 2013 | KR |
| 10-2014-0016244 | Feb 2014 | KR |
| 10-2014-0026263 | Mar 2014 | KR |
| 10-2014-0031283 | Mar 2014 | KR |
| 10-2014-0043370 | Apr 2014 | KR |
| 10-2014-0137400 | Dec 2014 | KR |
| 10-2014-0148289 | Dec 2014 | KR |
| 10-2015-0031010 | Mar 2015 | KR |
| 10-2015-0121177 | Oct 2015 | KR |
| 10-2016-0012008 | Feb 2016 | KR |
| 10-2016-0045633 | Apr 2016 | KR |
| 10-2016-0092363 | Aug 2016 | KR |
| 10-2016-0141847 | Dec 2016 | KR |
| 10-2017-0008601 | Jan 2017 | KR |
| 10-2017-0027435 | Mar 2017 | KR |
| 10-2017-0027999 | Mar 2017 | KR |
| 10-2017-0082022 | Jul 2017 | KR |
| 10-2017-0100358 | Sep 2017 | KR |
| 10-2017-0124954 | Nov 2017 | KR |
| 10-1820573 | Jan 2018 | KR |
| 10-2018-0034637 | Apr 2018 | KR |
| 10-2018-0085931 | Jul 2018 | KR |
| 10-2019-0002658 | Jan 2019 | KR |
| 10-2019-0014495 | Feb 2019 | KR |
| 10-2019-0022883 | Mar 2019 | KR |
| 10-2019-0057414 | May 2019 | KR |
| 10-2011177 | Aug 2019 | KR |
| 10-2020-0039030 | Apr 2020 | KR |
| 336834 | Feb 2016 | MX |
| 201403363 | Jan 2014 | TV |
| 201131471 | Sep 2011 | TW |
| 201137722 | Nov 2011 | TW |
| 201316247 | Apr 2013 | TW |
| 201324310 | Jun 2013 | TW |
| 201409345 | Mar 2014 | TW |
| 201415345 | Apr 2014 | TW |
| 201416959 | May 2014 | TW |
| 199944114 | Sep 1999 | WO |
| 200201864 | Jan 2002 | WO |
| 0211022 | Feb 2002 | WO |
| 2003036457 | May 2003 | WO |
| 2003054832 | Jul 2003 | WO |
| 2003062975 | Jul 2003 | WO |
| 2003062976 | Jul 2003 | WO |
| 2004095414 | Nov 2004 | WO |
| 2004104813 | Dec 2004 | WO |
| 2005031608 | Apr 2005 | WO |
| 2005053225 | Jun 2005 | WO |
| 2005109829 | Nov 2005 | WO |
| 2006011139 | Feb 2006 | WO |
| 2006020304 | Feb 2006 | WO |
| 2006020305 | Feb 2006 | WO |
| 2006113834 | Oct 2006 | WO |
| 2006130234 | Dec 2006 | WO |
| 2007073422 | Jun 2007 | WO |
| 2007102110 | Sep 2007 | WO |
| 2007142703 | Dec 2007 | WO |
| 2007149731 | Dec 2007 | WO |
| 2008027924 | Mar 2008 | WO |
| 2008030779 | Mar 2008 | WO |
| 2008030976 | Mar 2008 | WO |
| 2008033853 | Mar 2008 | WO |
| 2008085742 | Jul 2008 | WO |
| 2008103853 | Aug 2008 | WO |
| 2008151229 | Dec 2008 | WO |
| 2009005563 | Jan 2009 | WO |
| 2009010827 | Jan 2009 | WO |
| 2009067670 | May 2009 | WO |
| 2009086599 | Jul 2009 | WO |
| 2009097592 | Aug 2009 | WO |
| 2010087988 | Aug 2010 | WO |
| 2010107661 | Sep 2010 | WO |
| 2010120972 | Oct 2010 | WO |
| 2010128442 | Nov 2010 | WO |
| 2011027964 | Mar 2011 | WO |
| 2011041427 | Apr 2011 | WO |
| 2011084857 | Jul 2011 | WO |
| 2011126502 | Oct 2011 | WO |
| 2011149231 | Dec 2011 | WO |
| 2012004288 | Jan 2012 | WO |
| 2012006494 | Jan 2012 | WO |
| 2012028773 | Mar 2012 | WO |
| 2012050927 | Apr 2012 | WO |
| 2012051052 | Apr 2012 | WO |
| 2012079530 | Jun 2012 | WO |
| 2012104288 | Aug 2012 | WO |
| 2012126078 | Sep 2012 | WO |
| 2012154748 | Nov 2012 | WO |
| 2012166352 | Dec 2012 | WO |
| 2012170446 | Dec 2012 | WO |
| 2013000150 | Jan 2013 | WO |
| 2013026023 | Feb 2013 | WO |
| 2013048880 | Apr 2013 | WO |
| 2013049346 | Apr 2013 | WO |
| 2013097882 | Jul 2013 | WO |
| 2013097895 | Jul 2013 | WO |
| 2013097896 | Jul 2013 | WO |
| 2013111239 | Aug 2013 | WO |
| 2013132144 | Sep 2013 | WO |
| 2013135270 | Sep 2013 | WO |
| 2013137503 | Sep 2013 | WO |
| 2013153405 | Oct 2013 | WO |
| 2013169842 | Nov 2013 | WO |
| 2013169846 | Nov 2013 | WO |
| 2013169875 | Nov 2013 | WO |
| 2013173504 | Nov 2013 | WO |
| 2013173838 | Nov 2013 | WO |
| 2013176847 | Nov 2013 | WO |
| 2014021967 | Feb 2014 | WO |
| 2014030320 | Feb 2014 | WO |
| 2014032461 | Mar 2014 | WO |
| 2014057795 | Apr 2014 | WO |
| 2014078965 | May 2014 | WO |
| 2014105274 | Jul 2014 | WO |
| 2014105276 | Jul 2014 | WO |
| 2014107469 | Jul 2014 | WO |
| 2014115605 | Jul 2014 | WO |
| 2014128800 | Aug 2014 | WO |
| 2014143776 | Sep 2014 | WO |
| 2014147297 | Sep 2014 | WO |
| 2014151089 | Sep 2014 | WO |
| 2013173504 | Dec 2014 | WO |
| 2014197279 | Dec 2014 | WO |
| 2015008409 | Jan 2015 | WO |
| 2015062410 | May 2015 | WO |
| 2015076930 | May 2015 | WO |
| 2015102572 | Jul 2015 | WO |
| 2015114690 | Aug 2015 | WO |
| 2015124831 | Aug 2015 | WO |
| 2015134692 | Sep 2015 | WO |
| 2015185123 | Dec 2015 | WO |
| 2016033400 | Mar 2016 | WO |
| 2016036472 | Mar 2016 | WO |
| 2016036541 | Mar 2016 | WO |
| 2016040405 | Mar 2016 | WO |
| 2016057117 | Apr 2016 | WO |
| 2016200603 | Dec 2016 | WO |
| 2016204186 | Dec 2016 | WO |
| 2017027526 | Feb 2017 | WO |
| 2017058293 | Apr 2017 | WO |
| 2017058442 | Apr 2017 | WO |
| 2017112003 | Jun 2017 | WO |
| 2017147081 | Aug 2017 | WO |
| 2017218143 | Dec 2017 | WO |
| 2017218192 | Dec 2017 | WO |
| 2017218199 | Dec 2017 | WO |
| 2018048510 | Mar 2018 | WO |
| 2018084802 | May 2018 | WO |
| 2018098136 | May 2018 | WO |
| 2018144339 | Aug 2018 | WO |
| 2018213401 | Nov 2018 | WO |
| 2018213415 | Nov 2018 | WO |
| 2018213844 | Nov 2018 | WO |
| 2018232333 | Dec 2018 | WO |
| 2020063762 | Apr 2020 | WO |
| 2020243691 | Dec 2020 | WO |
| 2021010993 | Jan 2021 | WO |
| 2021231412 | Nov 2021 | WO |
| Entry |
|---|
| Notice of Allowance received for Chinese Patent Application No. 201911288715.0, mailed on Jul. 12, 2023, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/306,354, mailed on Jul. 24, 2023, 7 pages. |
| Intention to Grant received for European Patent Application No. 15714698.6, mailed on Dec. 8, 2023, 9 pages. |
| Intention to Grant received for European Patent Application No. 21728781.2, mailed on Dec. 12, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/666,971, mailed on Dec. 15, 2023, 8 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/476,404, mailed on Oct. 31, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/479,974, mailed on Nov. 1, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/088,309, mailed on Oct. 27, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/102,025, mailed on Nov. 15, 2023, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/320,900, mailed on Nov. 6, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/102,025, mailed on Nov. 3, 2023, 9 pages. |
| Office Action received for Japanese Patent Application No. 2022-149476, mailed on Nov. 2, 2023, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-0053111, mailed on Oct. 23, 2023, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/922,675, mailed on Nov. 15, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/181,089, mailed on Nov. 22, 2022, 3 pages. |
| Decision to Grant received for Danish Patent Application No. PA202170320, mailed on Nov. 10, 2022, 2 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/031760, mailed on Nov. 24, 2022, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/917,659, mailed on Dec. 1, 2022, 11 pages. |
| Office Action received for Australian Patent Application No. 2021261941, mailed on Nov. 3, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2022200515, mailed on Nov. 2, 2022, 2 pages. |
| Office Action received for Australian Patent Application No. 2022241590, mailed on Nov. 18, 2022, 8 pages. |
| 13 questions and answers about using Apple Pay online, online available at: http://www.it528.com/apple/1356.html, Feb. 18, 2016, 5 pages. |
| Advisory Action received for U.S. Appl. No. 10/308,315, mailed on Jul. 10, 2006., 3 pages. |
| Advisory Action received for U.S. Appl. No. 12/395,537, mailed on Apr. 26, 2012, 4 pages. |
| Advisory Action received for U.S. Appl. No. 12/566,673, mailed on Jun. 12, 2013, 3 pages. |
| Advisory Action received for U.S. Appl. No. 13/038,217, mailed on Dec. 8, 2014, 3 pages. |
| Advisory Action received for U.S. Appl. No. 13/587,850, mailed on May 15, 2015, 2 pages. |
| Advisory Action received for U.S. Appl. No. 14/863,099, mailed on Sep. 8, 2016, 3 pages. |
| Advisory Action received for U.S. Appl. No. 15/730,610, mailed on Oct. 24, 2019, 5 pages. |
| Advisory Action received for U.S. Appl. No. 16/422,736, mailed on Mar. 12, 2021, 3 pages. |
| Advisory Action received for U.S. Appl. No. 16/583,989, mailed on Sep. 22, 2020, 5 pages. |
| Advisory Action received for U.S. Appl. No. 15/250,152, mailed on Mar. 25, 2019, 5 pages. |
| Akhgari Ehsan, “Don't Leave a Trace: Private Browsing in Firefox”, available online at “http://ehsanakhgari.org/blog/2008-11-04/dont-leave-trace-private-browsing-firefox”, Nov. 4, 2008, 71 pages. |
| Akshay, “Control your SmartThings compatible devices on the Gear S2 and S3 with the Smarter Things app”, Online available at: https://iotgadgets.com/2017/09/control-smartthings-compatible-devices-gear-s2-s3-smarter-things-app/, Sep. 7, 2017, 4 pages. |
| Alba Davey, “Samsung Shape: for $400, Your Music Can Follow You Around the House”, Online available at: https://www.popularmechanics.com/technology/audio/a9536/samsung-shape-for-400-your-music-can-follow-you-aroundnd-15997831/, Oct. 3, 2013, 5 pages. |
| Androidcentral, “How do respond to group messages from notification bar?”, Available online at: https://forums.androidcentral .com/ask-question/952030-how-do-i-respond-group-messages-notification-bar.html, Mar. 25, 2019, 3 pages. |
| Appeal Brief received for U.S. Appl. No. 11/522,167 mailed on Nov. 2010., 65 pages. |
| Apple, “Iphone User's Guide”, iPhone first generation, Available at: <http://pocketpccentral.net/iphone/products/1 g_iphone.htm>, Jun. 29, 2007, 124 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/641,304, mailed on Dec. 2, 2019, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/641,304, mailed on Jul. 28, 2020, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/433,320, mailed on Feb. 11, 2020, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/583,989, mailed on Aug. 3, 2020, 6 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/583,989, mailed on Mar. 25, 2020, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/583,994, mailed on Apr. 3, 2020, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/584,490, mailed Jul. 28, 2020, 4 pages. |
| Applicant Initiated Inverview Summary received for U.S. Appl. No. 16/702,968, mailed on Jul. 1, 2020, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/917,659, mailed on Jan. 28, 2022, 2 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 17/176,908, mailed on Jun. 14, 2022, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/433,320, mailed on Nov. 25, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/730,610, mailed on Aug. 25, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/910,263, mailed on Nov. 18, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/263,280, mailed on Apr. 26, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/263,280, mailed on Nov. 25, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/422,736, mailed on Feb. 24, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/422,736, mailed on Sep. 28, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/583,981, mailed on Mar. 9, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/583,981, mailed on Sep. 14, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/583,994, mailed on May 28, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/583,994, mailed on Nov. 24, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,490, mailed on Jan. 31, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,743, mailed on May 1, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,002, mailed on Apr. 28, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/670,949, mailed on Apr. 6, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/679,967, mailed on Feb. 10, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/679,967, mailed on Jun. 1, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/679,967, mailed on Oct. 25, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/702,968, mailed on Sep. 28, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/723,583, mailed on Dec. 28, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/803,849, mailed on Aug. 21, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/803,849, mailed on Dec. 21, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/803,849, mailed on Feb. 28, 2022, 9 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/803,849, mailed on Oct. 12, 2021, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/807,604, mailed on Dec. 21, 2020, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/807,604, mailed on Jul. 24, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/836,571, mailed on Jul. 7, 2021, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/922,675, mailed on Dec. 16, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/922,675, mailed on Nov. 2, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/922,675, mailed on Sep. 3, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/026,818, mailed on Dec. 15, 2020, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/026,818, mailed on Mar. 8, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,833, mailed on Dec. 21, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,833, mailed on May 24, 2021, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/168,069, mailed on Nov. 17, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/181,089, mailed on Oct. 7, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/223,794, mailed on Sep. 7, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/314,948, mailed on Oct. 21, 2022, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/461,103, mailed on Jan. 26, 2022, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/476,404, mailed on Jul. 27, 2022, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/476,404, mailed on Mar. 18, 2022, 2 pages. |
| Beard Chris, “Mozilla Labs Introducing Weave”, available online at <https://blog.mozilla.org/labs/2007/12/introducing-weave/>, Dec. 21, 2007, 57 pages. |
| Bell Killian, “Twitter Notifications, iCloud Tabs & Location-Based Reminders Appear In Latest Os X 10.8 Beta”, available online at “http://www.cultofmac.com/154522/twitter-notifications-icloud-tabs-location-based-reminders-appear-in-latest-os-x-10-8-beta/”, Mar. 19, 2012, 10 pages. |
| Benjamin Jeff, “iOS 10: How to use the new Home app to control HomeKit devices [Video]”, Available online at: https://9to5mac.com/2016/09/23/ios-10-how-to-use-new-home-app-control-homekit-devices-video, Sep. 23, 2016, 36 pages. |
| Bennett Stephen, “ES2: Logic's Most Sophisticated Virtual Analogue Synth”, Logic Notes & Techniques, Jun. 2007, 6 pages. |
| Decision received for Chinese Patent Application No. 201510288981.9, mailed on May 6, 2021, 31 pages. |
| Decision received for Chinese Patent Application No. 201580043701.6, mailed on Aug. 19, 2021, 2 pages. |
| Decision received for Chinese Patent Application No. 201580046339.8, mailed on Jun. 22, 2021, 12 pages. |
| Decision received for Chinese Patent Application No. 201810338826.7, mailed on May 30, 2022, 20 pages. |
| Decision received for Chinese Patent Application No. 201811367893.8, mailed on Aug. 25, 2022, 2 pages. |
| Board Opinion received for Chinese Patent Application No. 201510288981.9, mailed on Jan. 4, 2021, 21 pages. |
| Board Opinion received for Chinese Patent Application No. 201580046339.8, mailed on Mar. 19, 2021, 11 pages. |
| Board Opinion received for Chinese Patent Application No. 201810338826.7, mailed on Jan. 19, 2022, 18 pages. |
| Board Opinion received for Chinese Patent Application No. 201910164962.3, mailed on Sep. 16, 2021, 16 pages. |
| Bove Tony, “iPod & iTunes for Dummies”, Wiley Publishing, Inc., 6th Edition, 2008, pp. 143-182. |
| Boxer David, “Change the permissions of the Google Drive file or folder or Share the file or folder”, Blake School Website, Online Available at: https://support.blakeschool.org/hc/en-us/articles/231790648-Change-the-permissions-of-the-Google-Drive-file-or-folder-or-Share-the-file-or-folder, Oct. 31, 2016, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 17799904.2, mailed on Sep. 13, 2022, 1 page. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 17813737.8, mailed on Sep. 19, 2022, 1 page. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 18197583.0, mailed on Feb. 18, 2021, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 19150528.8, mailed on Sep. 5, 2022, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 19169980.0, mailed on Jun. 17, 2021, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20158824.1, mailed on May 30, 2022, 1 page. |
| Brumberg et al., “The Unlock Project: A Python-based framework for practical brain- computer interface communication “app” development”, Conf Proc IEEE Eng Med Biol Soc. 2012, doi: 10.1109/EMBC.2012.6346473, Institute of Electrical and Electronics Engineers, 2012, 11 pages. |
| Butler Travis, “Portable MP3: The Nomad Jukebox”, available at <http://tidbits.com/article/6261>, Jan. 8, 2001, 4 pages. |
| Call Me, “Samsung R3 speaker gives you a delicious 360-degree sound experience—with WiFi and Bluetooth | Call me”, 0:24 / 3:22, Available Online at: <https://www.youtube.com/watch?v=4Uv_sOhrlro>, Sep. 22, 2016, 3 pages. |
| Certificate of Examination received for Australian Patent Application No. 2017100553, mailed on Jan. 17, 2018, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2018101014, mailed on Mar. 20, 2019, 2 pages. |
| Chan Christine, “Handoff Your Browser to Your iPhone or iPad! Plus a Chance to Win a Copy!”, Apr. 12, 2011, 2 pages. |
| Cipriani Jason, ““How to use Spotify's Offline mode on iPhone””, XP055533907, Available online at: https://www.cnet.com/how-to/how-to-use-spotifys-offline-mode-on-iphone/, Aug. 1, 2011, 5 pages. |
| ComputerAdv, “Sonos App Navigation & Menu on iPhone”, Available online at: https://www.youtube.com/watch?v=Jhz9XvWQ204, Aug. 4, 2015, 1 page. |
| Corrected Notice of Allowance received for U.S. Appl. No. 13/587,850, mailed on Apr. 1, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 13/587,850, mailed on Mar. 23, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/641,298, mailed on Dec. 9, 2021, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/719,217, mailed on Apr. 22, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/719,217, mailed on Mar. 20, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/830,629, mailed on Feb. 13, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/269,801, mailed on Oct. 3, 2017, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/730,610, mailed on Nov. 27, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/845,794, mailed on Feb. 25, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/910,263, mailed on Feb. 10, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/910,263, mailed on Mar. 17, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/910,263, mailed on Mar. 18, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/952,736, mailed on Nov. 19, 2018, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/229,959, mailed on Mar. 3, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/263,280, mailed on Aug. 5, 2021, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/422,736, mailed on Jul. 9, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/434,865, mailed on Apr. 28, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/434,865, mailed on Jun. 4, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/583,981, mailed on Apr. 6, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/583,981, mailed on May 17, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/583,994, mailed on Jul. 6, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/584,743, mailed on Dec. 30, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/670,949, mailed on Sep. 8, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/702,968, mailed on Jun. 8, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/702,968, mailed on Jun. 16, 2021, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/702,968, mailed on Jun. 28, 2021, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/702,968, mailed on May 26, 2021, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/702,968, mailed on May 28, 2021, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/803,849, mailed on Jul. 7, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/803,849, mailed on Jun. 8, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/807,604, mailed on Jul. 26, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/807,604, mailed on Jun. 28, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/807,604, mailed on May 28, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/807,604, mailed on Oct. 4, 2021, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/807,604, mailed on Oct. 14, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/807,604, mailed on Oct. 22, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/836,571, mailed on Dec. 6, 2021, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/836,571, mailed on Mar. 25, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/836,571, mailed on Nov. 4, 2021, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/836,571, mailed on Nov. 18, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/836,571, mailed on Oct. 12, 2021, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/921,551, mailed on Feb. 9, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/921,551, mailed on Jan. 26, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/922,675, mailed on Mar. 4, 2022, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/987,003, mailed on Sep. 1, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/027,373, mailed on Jul 12, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/027,373, mailed on Oct. 26, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/031,833, mailed on Aug. 2, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/168,069, mailed on Feb. 9, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/461,103, mailed on Apr. 14, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/461,103, mailed on Aug. 3, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/461,103, mailed on May 10, 2022, 2 pages. |
| Crutnacker, “Amazon Echo Tips and Tricks: Playing Music Demonstration”, Available Online at: https://www.youtube.com/watch?v=W_bqq2ynUll, Nov. 4, 2015, 1 page. |
| Customize Notifications and Content on Your Galaxy Phone's Lock Screen, Online Available at: https://www.samsung.com/us/support/answer/ANS00062636, Oct. 4, 2017, 5 pages. |
| Decision on Appeal received for U.S. Appl. No. 12/566,673, mailed on Dec. 18, 2019, 10 pages. |
| Decision on Appeal received for U.S. Appl. No. 13/587,850, mailed on Aug. 28, 2019, 21 pages. |
| Decision on Appeal received for U.S. Appl. No. 13/587,850, mailed on Oct. 21, 2019, 3 pages. |
| Decision on Appeal received for U.S. Appl. No. 14/641,298, mailed on Nov. 1, 2021, 9 pages. |
| Decision on Appeal received for U.S. Appl. No. 14/774,664, mailed on Sep. 12, 2019, 8 pages. |
| Decision on Appeal received for U.S. Appl. No. 14/863,099, mailed on Aug. 22, 2019, 9 pages. |
| Decision on Appeal received for U.S. Appl. No. 15/128,952, mailed on Dec. 28, 2020, 23 pages. |
| Decision to Grant received for Danish Patent Application No. PA201670628, mailed on Nov. 20, 2017, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770392, mailed on Oct. 24, 2018, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770401, mailed on Oct. 24, 2018, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770403, mailed on Oct. 24, 2018, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770404, mailed on Nov. 11, 2019, 3 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770406, mailed on May 15, 2020, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770782, mailed on Oct. 25, 2019, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA202070560, mailed on Oct. 21, 2021, 2 pages. |
| Decision to Grant received for European Patent Application No. 10712824.1, mailed on May 17, 2018, 3 pages. |
| Decision to Grant received for European Patent Application No. 12181537.7, mailed on Mar. 3, 2016, 2 pages. |
| Decision to Grant received for European Patent Application No. 12773460.6, mailed on Jun. 27, 2019, 2 pages. |
| Decision to Grant received for European Patent Application No. 13171047.7, mailed on Jun. 27, 2019, 2 pages. |
| Decision to Grant received for European Patent Application No. 15711969.4, mailed on Sep. 26, 2019, 2 pages. |
| Decision to Grant received for European Patent Application No. 15713062.6, mailed on Apr. 11, 2019, 2 pages. |
| Decision to Grant received for European Patent Application No. 15719347.5, mailed on Jun. 24, 2021, 2 pages. |
| Decision to Grant received for European Patent Application No. 15724160.5, mailed on Jun. 14, 2018, 2 pages. |
| Decision to Grant received for European Patent Application No. 16710590.7, mailed on Oct. 28, 2021, 2 pages. |
| Decision to Grant received for European Patent Application No. 18197583.0, mailed on Feb. 3, 2022, 3 pages. |
| Decision to Grant received for European Patent Application No. 18197589.7, mailed on Jun. 10, 2021, 2 pages. |
| Decision to Grant received for European Patent Application No. 19207753.5, mailed on Jun. 2, 2022, 3 pages. |
| Decision to Grant received for German Patent Application No. 102015208532.5, mailed on Sep. 22, 2020, 10 pages. |
| Decision to Grant received for Japanese Patent Application No. 2014-017726, mailed on Dec. 7, 2015, 6 pages. |
| Decision to Grant received for Japanese Patent Application No. 2017-075031, mailed on Jul. 1, 2019, 3 pages. |
| Decision to Grant received for Japanese Patent Application No. 2019-124728, mailed on Apr. 2, 2021, 4 pages. |
| Decision to Refuse received for European Patent Application No. 07842262.3, mailed on Dec. 21, 2018, 8 pages. |
| Decision to Refuse received for European Patent Application No. 10177096.4, mailed on Feb. 13, 2019, 4 pages. |
| Decision to Refuse received for European Patent Application No. 12753631.6, mailed on Feb. 20, 2019, 20 pages. |
| Decision to Refuse received for European Patent Application No. 12770400.5, mailed on Nov. 8, 2018, 12 pages. |
| Decision to Refuse received for European Patent Application No. 17799904.2, mailed on Sep. 19, 2022, 4 pages. |
| Decision to Refuse received for European Patent Application No. 17813737.8, mailed on Sep. 30, 2022, 5 pages. |
| Decision to Refuse received for European Patent Application No. 19150528.8, mailed on Sep. 9, 2022, 4 pages. |
| Decision to Refuse received for European Patent Application No. 19169980.0, mailed on Jul. 15, 2021, 4 pages. |
| Detroitborg, ““Apple Music: Walkthrough””, YouTube Video, online available at: “https://www.youtube.com/watch?v=NLgjodiAtbQ”, Jun. 30, 2015, 1 page. |
| Dharmasena Anusha, “iMessage-send as text message Option”, YouTube, Available online at: <https://www.youtube.com/watch?v=hXG-MdIW6FA>, Feb. 18, 2013, 1 page. |
| Digital Video Editor, IBM Technical Disclosure Bulletin, vol. 35, No. 2, IP.com Journal, IP.com Inc., West Henrietta XP013097273, Jul. 1, 1992, 6 pages. |
| Dybwad Barb, “Google Chrome Gets Bookmark Syncing”, available online at “http://mashable.com/2009/11/02/chrome-bookmark-sync/”,, Nov. 3, 2009, 6 pages. |
| Enright Andrewc. , “Meet Cover Flow”, Available online at <http://web.archive.org/web/20060111073239/thetreehouseandthecave.blogspot.com/2005/08/meet-coverflow.html>, retrieved on Feb. 19, 2008, Aug. 13, 2005, 2 pages. |
| Enright Andrewc. , “Visual Browsing on an iBook Ds”, Available online at <http://web.archive.org/web/20060111175609/thetreehouseandthecave.blogspot.com/2004/12/visual-browsing-on-i book-ds.html>,, Dec. 29, 2004, 2 page. |
| Enright Andrewc., “Dissatisfaction Sows Innovation”, Available at <http://web.archive.org/web/20051225123312/http://thetreehouseandthecave.blogspot.com/2004/12/dissatisfaction-sows-innovation.html>,, retrieved on Feb. 19, 2008, Dec. 29, 2004, 6 pages. |
| Evaluation Report for Utility Model Patent received for Chinese Patent Application No. 201620051290.7, completed on Sep. 19, 2016, 11 pages. |
| Examiner Allowance Proposal received for U.S. Appl. No. 16/807,604, mailed on Apr. 12, 2021, 3 pages. |
| Examiner Proposed Amendment received for U.S. Appl. No. 16/803,849, mailed on Apr. 22, 2021, 4 pages. |
| Examiner-Initiated Interview Summary received for U.S. Appl. No. 17/027,373, mailed on Mar. 31, 2022, 4 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 11/522,167 mailed on Feb. 15, 2011., 13 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 12/566,673, mailed on Nov. 17, 2017, 10 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/641,298, mailed on Mar. 22, 2021, 19 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/774,664, mailed on May 31, 2018, 28 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/863,099, mailed on Jul. 28, 2017, 31 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 15/128,952, mailed on Jan. 8, 2020, 9 pages. |
| Examiner's Initiated Interview Summary received for U.S. Appl. No. 14/641,298, mailed on Mar. 10, 2020, 4 pages. |
| Examiner's Pre-Review Report received for Japanese Patent Application No. 2018-080122, mailed on Feb. 25, 2020, 6 pages. |
| Extended European Search Report includes (Partial European Search Report and European Search Opinion) received for European Patent Application No. 12181537.7, mailed on Mar. 27, 2014, 7 pages. |
| Extended European Search Report (includes Partial European Search Report and European Search Opinion) received for European Patent Application No. 13184872.3, mailed on Dec. 5, 2013, 9 pages. |
| Extended European Search Report for European Application No. 10177099.8, mailed on Oct. 18, 2010, 7 pages. |
| Extended European Search Report for European Application No. 17813737.8, mailed on Nov. 22, 2019, 9 pages. |
| Extended European Search Report received for European Patent Application No. 10177096.4, mailed on Oct. 18, 2010., 9 pages. |
| Extended European Search Report received for European Patent Application No. 13171047.7, mailed on Oct. 29, 2014, 8 pages. |
| Extended European Search Report received for European Patent Application No. 17799904.2, mailed on Jul. 30, 2018, 7 pages. |
| Extended European Search Report received for European Patent Application No. 18178147.7, mailed on Oct. 4, 2018, 8 pages. |
| Extended European Search Report received for European Patent Application No. 18197583.0, mailed on Jun. 4, 2019, 20 pages. |
| Extended European Search Report received for European Patent Application No. 18197589.7, mailed on Jan. 7, 2019, 9 pages. |
| Extended European Search Report received for European Patent Application No. 18208881.5, mailed on Jan. 8, 2019, 7 pages. |
| Extended European Search Report received for European Patent Application No. 19150528.8, mailed on May 15, 2019, 9 pages. |
| Extended European Search Report received for European Patent Application No. 19169980.0, mailed on Jul. 2, 2019, 8 pages. |
| Extended European Search Report received for European Patent Application No. 19186538.5, mailed on Oct. 9, 2019, 10 pages. |
| Extended European Search Report received for European Patent Application No. 19203942.8, mailed on Apr. 1, 2020, 10 pages. |
| Extended European Search Report received for European Patent Application No. 19207753.5, mailed on Dec. 18, 2019, 9 pages. |
| Extended European Search Report received for European Patent Application No. 20158824.1, mailed on Aug. 10, 2020, 13 pages. |
| Extended European Search Report received for European Patent Application No. 21160991.2, mailed on Jul. 16, 2021, 14 pages. |
| Extended European Search Report received for European Patent Application No. 21166718.3, mailed on Jul. 6, 2021, 11 pages. |
| Extended European Search Report received for European Patent Application No. 21197457.1, mailed on Nov. 15, 2021, 8 pages. |
| Extended European Search Report received for European Patent Application No. 21207736.6, mailed on Feb. 22, 2022, 11 pages. |
| Extended European Search Report received for European Patent Application No. 22188377.0, mailed on Oct. 27, 2022, 8 pages. |
| FarmboyReef, “Apple watch controlling your tv”, Available online at: https://www.youtube.com/watch?v=xaJPG0Wm3Tg, Jun. 23, 2015, 3 pages. |
| Feng Lipeng, “Bound for computer lovers”, Dec. 31, 2009, 2 pages. |
| Final Office Action received for U.S. Appl. No. 09/293,507, mailed on Apr. 24, 2002, 12 pages. |
| Final Office Action received for U.S. Appl. No. 09/293,507, mailed on Feb. 14, 2001, 10 pages. |
| Final Office Action received for U.S. Appl. No. 10/308,315, mailed on Apr. 6, 2005., 10 pages. |
| Final Office Action received for U.S. Appl. No. 10/308,315, mailed on Mar. 9, 2006., 10 pages. |
| Final Office Action received for U.S. Appl. No. 10/308,315, mailed on Mar. 23, 2007., 12 pages. |
| Final Office Action received for U.S. Appl. No. 11/459,591, mailed on Jan. 13, 2009, 11 pages. |
| Final Office Action received for U.S. Appl. No. 11/522,167, mailed on Aug. 5, 2009., 9 pages. |
| Final Office Action received for U.S. Appl. No. 11/522,167, mailed on Jul. 23, 2010., 11 pages. |
| Final Office Action received for U.S. Appl. No. 11/522,167, mailed on Jun. 3, 2013., 18 pages. |
| Final Office Action received for U.S. Appl. No. 11/522,167, mailed on Oct. 15, 2008., 10 pages. |
| Final Office Action received for U.S. Appl. No. 11/767,409, mailed on Jul. 17, 2012, 24 pages. |
| Final Office Action received for U.S. Appl. No. 11/767,409, mailed on Mar. 16, 2011, 16 pages. |
| Final Office Action received for U.S. Appl. No. 11/960,674, mailed on May 12, 2011, 10 pages. |
| Final Office Action received for U.S. Appl. No. 11/983,059, mailed on Jun. 6, 2011., 11 pages. |
| Final Office Action received for U.S. Appl. No. 12/215,651, mailed on Jul. 6, 2012, 27 pages. |
| Final Office Action received for U.S. Appl. No. 12/395,537, mailed on Feb. 3, 2012, 15 pages. |
| Final Office Action received for U.S. Appl. No. 12/395,537, mailed on Jun. 29, 2015, 17 pages. |
| Final Office Action received for U.S. Appl. No. 12/395,537, mailed on Nov. 14, 2013, 22 pages. |
| Final Office Action received for U.S. Appl. No. 12/395,541, mailed on Dec. 28, 2011, 16 pages. |
| Final Office Action received for U.S. Appl. No. 12/566,669, mailed on Nov. 23, 2012, 29 pages. |
| Final Office Action received for U.S. Appl. No. 12/566,671, mailed on Dec. 20, 2012, 20 pages. |
| Final Office Action received for U.S. Appl. No. 12/566,673, mailed on Aug. 12, 2016, 28 pages. |
| Final Office Action received for U.S. Appl. No. 12/566,673, mailed on Jan. 17, 2013, 22 pages. |
| Final Office Action received for U.S. Appl. No. 12/566,673, mailed on Mar. 25, 2014, 19 pages. |
| Final Office Action received for U.S. Appl. No. 13/038,217, mailed on May 6, 2014, 11 pages. |
| Final Office Action received for U.S. Appl. No. 13/248,882, mailed on Dec. 4, 2013, 22 pages. |
| Final Office Action received for U.S. Appl. No. 13/333,890, mailed on Feb. 13, 2014, 19 pages. |
| Final Office Action received for U.S. Appl. No. 13/333,890, mailed on Oct. 2, 2015, 21 pages. |
| Final Office Action received for U.S. Appl. No. 13/333,900, mailed on Dec. 19, 2014, 15 pages. |
| Final Office Action received for U.S. Appl. No. 13/333,900, mailed on Nov. 7, 2013, 14 pages. |
| Final Office Action received for U.S. Appl. No. 13/489,245, mailed on Mar. 28, 2014, 23 pages. |
| Final Office Action received for U.S. Appl. No. 13/489,245, mailed on Oct. 16, 2019, 25 pages. |
| Final Office Action received for U.S. Appl. No. 13/489,245, mailed on Sep. 27, 2018, 25 pages. |
| Final Office Action received for U.S. Appl. No. 13/492,057, mailed on Apr. 8, 2016, 29 pages. |
| Final Office Action received for U.S. Appl. No. 13/492,057, mailed on Mar. 30, 2015, 18 pages. |
| Final Office Action received for U.S. Appl. No. 13/587,850, mailed on May 3, 2016, 31 pages. |
| Final Office Action received for U.S. Appl. No. 13/587,850, mailed on Nov. 28, 2014, 22 pages. |
| Final Office Action received for U.S. Appl. No. 14/045,544, mailed on May 6, 2016., 26 pages. |
| Final Office Action received for U.S. Appl. No. 14/285,378, mailed on Jul. 23, 2015, 19 pages. |
| Final Office Action received for U.S. Appl. No. 14/503,327, mailed on May 18, 2017, 10 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,289, mailed on Jul. 1, 2016., 32 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,298, mailed on Jun. 26, 2020, 50 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,298, mailed on May 16, 2019, 50 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,298, mailed on Oct. 4, 2017, 30 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,304, mailed on Jul. 24, 2018, 19 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,304, mailed on Oct. 15, 2019, 21 pages. |
| Final Office Action received for U.S. Appl. No. 14/719,217, mailed on Feb. 23, 2017., 37 pages. |
| Final Office Action received for U.S. Appl. No. 14/774,664, mailed on Aug. 25, 2017, 23 pages. |
| Final Office Action received for U.S. Appl. No. 14/830,629, mailed on Apr. 16, 2018, 27 pages. |
| Final Office Action received for U.S. Appl. No. 14/841,455, mailed on Nov. 6, 2018, 14 pages. |
| Final Office Action received for U.S. Appl. No. 14/863,099, mailed on Apr. 21, 2016, 20 pages. |
| Final Office Action received for U.S. Appl. No. 15/128,952, mailed on Jul. 18, 2018, 19 pages. |
| Final Office Action received for U.S. Appl. No. 15/433,320, mailed on Dec. 31, 2019, 30 pages. |
| Final Office Action received for U.S. Appl. No. 15/730,610, mailed on Aug. 6, 2019, 28 pages. |
| Final Office Action received for U.S. Appl. No. 15/910,263, mailed on Aug. 28, 2019, 32 pages. |
| Final Office Action received for U.S. Appl. No. 16/263,280, mailed on Mar. 4, 2021, 13 pages. |
| Final Office Action received for U.S. Appl. No. 16/422,736, mailed on Jan. 11, 2021, 39 pages. |
| Final Office Action received for U.S. Appl. No. 16/583,981, mailed on Apr. 16, 2020, 19 pages. |
| Final Office Action received for U.S. Appl. No. 16/583,989, mailed on Jul. 10, 2020, 23 pages. |
| Final Office Action received for U.S. Appl. No. 16/583,994, mailed on Jul. 23, 2020, 16 pages. |
| Final Office Action received for U.S. Appl. No. 16/584,490, mailed on May 1, 2020, 48 pages. |
| Final Office Action received for U.S. Appl. No. 16/679,967, mailed on Nov. 10, 2021, 14 pages. |
| Final Office Action received for U.S. Appl. No. 16/702,968, mailed on Jul. 27, 2020, 21 pages. |
| Final Office Action received for U.S. Appl. No. 16/723,583, mailed on Feb. 5, 2021, 15 pages. |
| Final Office Action received for U.S. Appl. No. 16/803,849, mailed on Nov. 2, 2021, 37 pages. |
| Final Office Action received for U.S. Appl. No. 16/803,849, mailed on Sep. 24, 2020, 29 pages. |
| Final Office Action received for U.S. Appl. No. 16/807,604, mailed on Aug. 19, 2020, 35 pages. |
| Final Office Action received for U.S. Appl. No. 16/922,675, mailed on Dec. 3, 2020, 21 pages. |
| Final Office Action received for U.S. Appl. No. 16/922,675, mailed on Nov. 30, 2020, 12 pages. |
| Final Office Action received for U.S. Appl. No. 17/026,818, mailed on Jan. 29, 2021, 21 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,833, mailed on Jan. 26, 2021, 17 pages. |
| Final Office Action received for U.S. Appl. No. 17/181,089, mailed on Oct. 21, 2022, 15 pages. |
| Final Office Action received for U.S. Appl. No. 17/476,404, mailed on May 5, 2022, 30 pages. |
| Final Office Action received for U.S. Appl. No. 15/250, 152, mailed on Aug. 23, 2017, 24 pages. |
| Final Office Action received for U.S. Appl. No. 15/250, 152, mailed on Nov. 16, 2018, 30 pages. |
| Final Office Action received in U.S. Appl. No. 12/547,401, mailed on Jun. 28, 2010, 19 pages. |
| Finkelstein Ellen, “Temporarily Override Object Snap Settings”, AutoCAD Tips Blog, Apr. 9, 2007, 4 pages. |
| Firefox Sync—Take Your Bookmarks, Tabs and Personal Information with You, available online at https://web.archive.org/web/20120601020556/http://support.mozilla.org/en-US/kb/firefox-sync-take-your-bookmarks-and-tabs-with-you?redirectlocale=en-US&redirectslug=what-firefox-sync, Jun. 1, 2012, 3 pages. |
| Frakes Dan, “How to Get Started with Airplay”, available at: https://www.macworld.com/article/2039770/how-to-get-started-with-airplay.html, Macworld, May 27, 2013, 8 pages. |
| Free Virtual Classic Analogue Mono Synth, Samsara Cycle Audio Releases DEISK-O, Jan. 2, 2011, 3 pages. |
| G Pad, LG's latest UIs that shine even more on the G-Pad, Online available at : http://bungq.com/1014., Nov. 19, 2013, 49 pages. |
| Gil Lory, “How to control Apple TV with your Apple Watch”, Available online at: https://www.imore.com/how-control-your-apple-tv-remote-app%ADapple-watch], Jun. 6, 2016, 24 pages. |
| Google Labs, “Google Browser Sync”, available online at “https://web.archive.org/web/20120518050142/http://www.google.com/tools/firefox/browsersync/faq.html”, May 18, 2012, 5 pages. |
| Google, “Google Home Help, Listen to music”, Datasheet [online], Available Online at: <https://web.archive.org/web/20170326051235/https:/support.google.com/googlehome/answer/7030379?hl=en&ref_topic=7030084>, Mar. 26, 2017, 3 pages. |
| Gookin Dan, “Lock Screen Settings on Your Android Phone”, Online Available at: https://www.dummies.com/consumer-electronics/smartphones/droid/lock-screen-settings-on-your-android-phone/, Sep. 23, 2015, 6 pages. |
| Han Hailing, “Research on Testing Method on Computer Interlocking Software”, “Electronic World” vol. 2012 No. 17, Key Laboratory of Optoelectronic Technology and Intelligent Control of Ministry of Education, Lanzhou Jiaotong University, Sep. 2012, 2 pages. |
| Hein Buster, “iOS 5 Allows Users to Delete Music Directly From iPhone/iPad”, Online available at: https://www.cultofmac.com/99990/ios-5-allows-users-to-delete-music-directly-from-iphoneipad/, Jun. 9, 2011, 7 pages. |
| HobbyistSoftwareLTD, “VLC Remote”, Online available at: https://watchaware.com/watch-apps/297244048, 2016, 7 pages. |
| Hoffberger Chase, “Spotify's Collaborative Playlists Let Friends Listen Together”, Evolver.fm, available online at http://www.evolver.fm/2011/08/22/spotify-collaborative-playlists/, Aug. 22, 2011, 4 pages. |
| Howcast, “How to Create and Edit Playlists on iPhone”, Youtube, Available online at: https://www.youtube.com/watch?v=YPOnKUvcso4, Mar. 13, 2014, 3 pages. |
| How-To: iTunes in the Cloud, available at <http://y2kemo.com/2011/06/how-to-itunes-in-the-cloud/>, XP55040711, Jun. 9, 2011, 4 pages. |
| Hughes Neil, “Apple Explores Merging Cloud Content with Locally Stored Media Library”, Available at <http://appleinsider.com/articles/11/02/10/apple_explores_merging_cloud_content_with_locally_stored_media_library.html>, XP55040717, Feb. 10, 2011, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201670628, mailed on Aug. 28, 2017., 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770392, mailed on Aug. 31, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770392, mailed on Jul. 2, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770401, mailed on Jun. 14, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770401, mailed on Sep. 17, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770403, mailed on May 7, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770403, mailed on Oct. 3, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770404, mailed on Sep. 23, 2019, 3 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770406, mailed on Feb. 6, 2020, 3 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770408, mailed on Nov. 30, 2018, 3 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770782, mailed on Aug. 8, 2019, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA202070560, mailed on Apr. 26, 2021, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA202070617, mailed on Nov. 15, 2021, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA202170320, mailed on Jul. 27, 2022, 2 pages. |
| Intention to Grant received for European Patent Application No. 10712824.1, mailed on Jan. 5, 2018, 9 pages. |
| Intention to Grant Received for European Patent Application No. 12181537.7, mailed on Sep. 22, 2015, 7 pages. |
| Intention to Grant received for European Patent Application No. 12773460.6, mailed on Feb. 4, 2019, 8 pages. |
| Intention to Grant received for European Patent Application No. 12773460.6, mailed on Jun. 17, 2019, 4 pages. |
| Intention to Grant received for European Patent Application No. 13171047.7, mailed on Jan. 23, 2019, 8 pages. |
| Intention to Grant received for European Patent Application No. 13184872.3, mailed on Feb. 11, 2019, 7 pages. |
| Intention to Grant received for European Patent Application No. 15711969.4, mailed on May 29, 2019, 11 pages. |
| Intention to Grant received for European Patent Application No. 15713062.6, mailed on Mar. 25, 2019, 7 pages. |
| Intention to Grant received for European Patent Application No. 15713062.6, mailed on Oct. 8, 2018, 8 pages. |
| Intention to Grant received for European Patent Application No. 15719347.5, mailed on Dec. 8, 2020, 7 pages. |
| Intention to Grant received for European Patent Application No. 15719347.5, mailed on Jun. 8, 2021, 7 pages. |
| Intention to Grant received for European Patent Application No. 15719347.5, mailed on May 11, 2021, 8 pages. |
| Intention to Grant received for European Patent Application No. 15724160.5, mailed on Mar. 7, 2018, 8 pages. |
| Intention to Grant received for European Patent Application No. 16710590.7, mailed on Jun. 14, 2021, 8 pages. |
| Intention to Grant received for European Patent Application No. 18197583.0, mailed on Jan. 17, 2022, 9 pages. |
| Intention to Grant received for European Patent Application No. 18197583.0, mailed on Jul. 23, 2021, 9 pages. |
| Intention to Grant received for European Patent Application No. 18197589.7, mailed on Jan. 21, 2021, 8 pages. |
| Intention to Grant received for European Patent Application No. 19207753.5, mailed on Jan. 28, 2022, 8 pages. |
| Intention to Grant received for European Patent Application No. 19207753.5, mailed on Sep. 3, 2021, 8 pages. |
| Intention to Grant received for European Patent Application No. 20158824.1, mailed on Aug. 11, 2022, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US00/010441, mailed on Feb. 14, 2001, 3 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2006/062714, issued on Jul. 8, 2008, 6 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2007/078180, issued on Mar. 17, 2009, 6 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2007/088914, issued on Jul. 7, 2009, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2010/027088, mailed on Sep. 29, 2011, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2012/025314, mailed on Sep. 12, 2013, Sep. 12, 2013, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2012/051432, mailed on Feb. 27, 2014, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2012/057319, mailed on Apr. 10, 2014, 6 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2012/057656, mailed on Apr. 10, 2014, 6 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2013/044710, mailed on Dec. 18, 2014, 11 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/027882, mailed on Sep. 24, 2015, 8 pages. |
| International Preliminary Report on Patentability Received for PCT Patent Application No. PCT/US2015/019306, mailed on Dec. 15, 2016, 10 pages. |
| International Preliminary Report on Patentability Received for PCT Patent Application No. PCT/US2015/019309, mailed on Dec. 15, 2016, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/019317, mailed on Dec. 15, 2016, 18 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/025188, mailed on Mar. 2, 2017, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/030199, mailed on Dec. 15, 2016, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/045965, mailed on Dec. 27, 2016, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/021012, mailed on Sep. 21, 2017, 11 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/031086, mailed on Dec. 27, 2018, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/032240, mailed on Nov. 29, 2018, 29 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2018/032158, mailed on Nov. 21, 2019, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2018/032904, mailed on Nov. 28, 2019, 14 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/024390, mailed on Dec. 9, 2021, 20 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/026044, mailed on Dec. 9, 2021, 18 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/035446, mailed on Dec. 9, 2021, 14 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/035488, mailed on Dec. 9, 2021, 16 pages. |
| International Search Report and Written Opinion received for PCT Application No. PCT/US2015/019309, mailed on Jun. 25, 2015, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US00/10441, mailed on Jul. 11, 2000, 2 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US17/31086, mailed on Sep. 8, 2017, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/078180, mailed on Mar. 3, 2008, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/088914, mailed on Jun. 23, 2008, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2010/027088, mailed on Jun. 18, 2010, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2012/025314, mailed on May 14, 2012, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2012/051432, mailed on Oct. 29, 2012, Oct. 29, 2012, 12 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2012/057319, mailed on Feb. 25, 2013, 7 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2012/057656, mailed on Feb. 25, 2013, 7 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2013/032498, mailed on Feb. 10, 2014, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2013/044710, mailed on Aug. 15, 2013, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2014/027882, mailed on Oct. 10, 2014, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/019306, mailed on Jun. 17, 2015, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/019317, mailed on Aug. 25, 2015, 24 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/025188, mailed on Jun. 23, 2015, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/030199, mailed on Aug. 14, 2015, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/045965, mailed on Feb. 1, 2016, 20 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/021012, mailed on Jun. 2, 2016, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/032240, mailed on Sep. 21, 2017, 33 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2018/032158, mailed on Nov. 2, 2018, 19 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2018/032904, mailed on Oct. 1, 2018, 21 pages. |
| International Search Report and written Opinion received for PCT Patent Application No. PCT/US2020/024390, mailed on Aug. 17, 2020, 22 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/024390, mailed on Oct. 23, 2020, 26 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/026044, mailed on Sep. 9, 2020, 26 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035446, mailed on Nov. 10, 2020, 20 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/035488, mailed on Nov. 17, 2020, 21 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/031760, mailed on Sep. 16, 2021, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/048358, mailed on Feb. 24, 2022, 21 pages. |
| Invitation to Pay Addition Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2018/032904, mailed on Jul. 31, 2018, 18 pages. |
| Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US17/31086, mailed on Jul. 14, 2017., 2 pages. |
| Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US17/32240, mailed on Jul. 12, 2017., 2 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/024390, mailed on Jun. 26, 2020, 15 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2014/027882, mailed on Aug. 5, 2014, 2 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/019317, mailed on May 22, 2015, 7 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2018/032158, mailed on Sep. 10, 2018, 16 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/026044, mailed on Jun. 25, 2020, 12 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/035446, mailed on Sep. 11, 2020, 12 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/035488, mailed on Sep. 23, 2020, 15 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2021/048358, mailed on Dec. 23, 2021, 14 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 18728002.9, mailed on Sep. 2, 2020, 8 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 18733381.0, mailed on Jun. 30, 2021, 4 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 20719301.2, mailed on Dec. 17, 2020, 5 pages. |
| ITJungles, “iPhone 6: How to Pair with Another Bluetooth Device”, Available Online at: https://www.youtube.com/watch?v=9setanYtHAk, Aug. 5, 2015, 3 pages. |
| Jarvie, “Alexa plays me music”, Available online at: https://www.youtube.com/watch?v=bR2ZC8Sy8YQ, Feb. 23, 2015, 1 page. |
| Kanter David, “Start Download Automatically Sync Your (New) Music, Apps, and iBooks Across Your iDevices with iCloud”, Available online at: https://appadvice.com/appnn/2011/06/automatically-sync-music-apps-ibooks-idevices-icloud, Jun. 8, 2011, 6 pages. |
| Kim et al., “An Energy Efficient Transmission Scheme for Real-Time Data in Wireless Sensor Networks”, Sensors, vol. 15, in Sensors 2015, May 20, 2015, 25 pages. |
| Kimura Ryoji, “Keynote presentation practice guide for iPad & iPhone”, K.K. Rutles, first edition, Feb. 29, 2012, 4 pages. |
| Kinect Gesture Commands—Kinect Voice Commands, Xbox Wire, Available Online at: <https://hwcdn.libsyn.com/p/4/4/c/44c89c7f273167b4/Xbox_One_Kinect_Voice_Gesture.pdf?c_id=6458139&cs_id=6458139&expiration=1555411736&hwt=fe78eb09654ea677c9fbf836ad2ed82b >, 2013, 2 pages. |
| Klein Matt, “How to Add, Remove, and Rearrange Apps on the Apple Watch's Dock”, Available online at: https://www.howtogeek.com/279796/how-to-add-remove-and-rearrange-apps-on-the-apple-watch%E2%80%99s-dock/, Nov. 18, 2016, 10 pages. |
| LG G Pad 8.3 Tablet Q Remote User, Available at:—https://mushroomprincess.tistory.com/1320, Dec. 26, 2013, 37 pages. |
| Locklear Mallory, “Samsung to bring SmartThings control to its Gear smartwatches”, Online available at: https://www.engadget.com/2018-01-08-samsung-smartthings-app-gear-smartwatches.html, Jan. 8, 2018, 12 pages. |
| Low Cherlynn, “So you bought a smartwatch. Now what?”, Online available at: https://www.engadget.com/2018-02-06-how-to-set-up-your-smartwatch.html, Feb. 6, 2018, 19 pages. |
| Mac Fan, “Chapter 4: The True Character of Apple's Genuine Cloud—Your Personal Data Always Exist in There, Regardless of Your Location”, Mainichi Communications Inc., vol. 19, No. 8, Aug. 1, 2011, 8 pages. |
| Mackie Simon, “Emulate Safari's Reader Mode in Other Browsers with Readability”, available online at “https://gigaom.com/2010/06/21/emulate-safaris-reader-mode-in-other-browsers-with-readability/”, Jun. 21, 2010, 5 pages. |
| Mcelhearn Kirk, “iTunes 10.3 Offers Automatic Downloads and Access to Purchases”, Available at <http://web.archive.org/web/20110613084837/http://www.tidbits.com/article/12235>, Jun. 8, 2011, 5 pages. |
| Minutes of Oral Hearing received for German Patent Application No. 102015208532.5, mailed on Dec. 13, 2019, 21 pages. |
| Minutes of the Oral Proceedings received for European Application No. 12770400.5, mailed on Nov. 6, 2018, 7 pages. |
| Minutes of the Oral Proceedings received for European Application No. 15711969.4, mailed on May 16, 2019, 7 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 00923491.5, mailed on May 11, 2011., 69 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 12753631.6, mailed on Feb. 20, 2019, 3 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 18197583.0, mailed on Mar. 9, 2021, 6 pages. |
| Miser Brad, “Sams Teach Yourself iTunes® 10 in 10 Minutes”, SAMS Publishing, Dec. 30, 2010, pp. 65 and 67-69. |
| Mozilla Services, “Firefox Sync Terms of Service (for versions prior to Firefox 29)”, available online at <https://services.mozilla.com/tos/>, Aug. 19, 2010, 4 pages. |
| NBC News, “NBC News—YouTube Democratic Debate (full)”, Online available at:—https://www.youtube.com/watch?v=ti2Nokoq1J4, Jan. 17, 2016, 1 page. |
| Nikolov Anton, “Design principle: Consistency”, Available online at: https://uxdesign.cc/design-principle-consistency-6b0cf7e7339f, Apr. 8, 2017, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/395,537, mailed on Dec. 14, 2015, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/952,736, mailed on Jun. 1, 2018, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/492,057, mailed on Dec. 17, 2015, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,327, mailed on Sep. 12, 2016, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/679,967, mailed on Sep. 2, 2021, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 09/293,507, mailed on Aug. 1, 2001, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 09/293,507, mailed on Jun. 22, 2000, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 09/293,508, mailed on Jun. 30, 2000, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/308,315, mailed on Aug. 8, 2005., 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/374,013, mailed on Feb. 1, 2007., 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/459,591, mailed on Jul. 29, 2008, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/521,740, mailed on Dec. 27, 2007., 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/522,167, mailed on Dec. 6, 2012., 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/522,167, mailed on Feb. 5, 2009., 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/522,167, mailed on Jan. 20, 2010., 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/522,167, mailed on May 2, 2007., 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/522,167, mailed on Oct. 19, 2007., 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/767,409, mailed on Aug. 29, 2011, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/767,409, mailed on Feb. 9, 2012, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/767,409, mailed on Nov. 23, 2010, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/960,674, mailed on Oct. 27, 2010, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/983,059, mailed on Dec. 30, 2010., 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/215,651, mailed on Aug. 15, 2013, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/215,651, mailed on Feb. 2, 2012, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/395,537, mailed on Aug. 15, 2011, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/395,537, mailed on Jan. 5, 2015, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/395,537, mailed on Jul. 8, 2013, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/395,541, mailed on Jul. 26, 2011, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/395,541, mailed on Mar. 14, 2013, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/566,669, mailed on Apr. 17, 2014, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/566,669, mailed on Jun. 19, 2012, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/566,671, mailed on May 23, 2012, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/566,672, mailed on Nov. 8, 2012, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/566,673, mailed on Jun. 7, 2012, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/566,673, mailed on Mar. 26, 2015, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/566,673, mailed on Sep. 13, 2013, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/038,217, mailed on Sep. 13, 2013, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/248,872, mailed on May 19, 2014, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/248,882, mailed on Jul. 10, 2013, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/333,890, mailed on Aug. 30, 2013, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/333,890, mailed on Jun. 5, 2015, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/333,890, mailed on May 1, 2013, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/333,900, mailed on Mar. 19, 2013, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/333,900, mailed on May 23, 2014, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/489,245, mailed on Apr. 8, 2019, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/489,245, mailed on Dec. 27, 2017, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/489,245, mailed on Nov. 20, 2013, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/492,057, mailed on Jul. 8, 2014, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/587,850, mailed on Apr. 7, 2014, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/587,850, mailed on Oct. 8, 2015, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/045,544, mailed on Oct. 6, 2015., 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/285,378, mailed on Dec. 21, 2015, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/285,378, mailed on Jan. 21, 2015, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,289, mailed on Jul. 16, 2015, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,289, mailed on Mar. 11, 2016, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,298, mailed on Mar. 6, 2017, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,298, mailed on Nov. 29, 2019, 47 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,298, mailed on Sep. 19, 2018, 41 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,304, mailed on Feb. 27, 2019, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,304, mailed on Mar. 4, 2020, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,304, mailed on Sep. 11, 2017, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/642,366, mailed on Aug. 24, 2015, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/719,217, mailed on Jul. 26, 2018, 40 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/719,217, mailed on Jul. 28, 2016, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/774,664, mailed on Mar. 7, 2017, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/830,629, mailed on Dec. 1, 2016, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/830,629, mailed on Jun. 15, 2017., 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,455, mailed on Apr. 25, 2018, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/863,099, mailed on Dec. 2, 2015, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/128,952, mailed on Apr. 1, 2019, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/128,952, mailed on Dec. 29, 2017, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/134,638, mailed on Sep. 20, 2016, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/269,801, mailed on Dec. 30, 2016, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/274,963, mailed on Mar. 13, 2018, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/433,320, mailed on Jul. 31, 2020, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/620,666, mailed on Mar. 28, 2018, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/730,610, mailed on Apr. 15, 2020, 36 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/730,610, mailed on Feb. 1, 2019, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/845,794, mailed on Oct. 15, 2018, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/910,263, mailed on Jun. 15, 2020, 38 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/910,263, mailed on Mar. 4, 2019, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/229,959, mailed on Oct. 31, 2019, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/263,280, mailed on Jul. 27, 2020, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/422,736, mailed on Jun. 23, 2020, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/434,865, mailed on Jan. 16, 2020, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/583,981, mailed on Dec. 6, 2019, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/583,989, mailed on Jan. 24, 2020, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/583,994, mailed on Dec. 23, 2020, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/583,994, mailed on Dec. 30, 2019, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,490, mailed on Dec. 10, 2019, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,743, mailed on Feb. 6, 2020, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/586,002, mailed on Feb. 20, 2020, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/670,949, mailed on Dec. 9, 2020, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/679,967, mailed on Apr. 19, 2022, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/702,968, mailed on Apr. 8, 2020, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/723,583, mailed on Aug. 13, 2020, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/803,849, mailed on Jul. 13, 2020, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/803,849, mailed on May 14, 2021, 34 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/807,604, mailed on Jun. 2, 2020, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/836,571, mailed on Mar. 25, 2021, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/917,659, mailed on Jan. 14, 2022, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/921,551, mailed on Sep. 8, 2021, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/922,675, mailed on Aug. 13, 2020, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/922,675, mailed on Jun. 8, 2022, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/922,675, mailed on May 4, 2021, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/987,003, mailed on May 10, 2021, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/026,818, mailed on Nov. 25, 2020, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/027,373, mailed on Feb. 2, 2022, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,833, mailed on Dec. 7, 2020, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/168,069, mailed on Jul. 21, 2021, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/176,908, mailed on Feb. 24, 2022, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/181,089, mailed on May 13, 2022, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/223,794, mailed on Jun. 16, 2021, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/314,948, mailed on Aug. 1, 2022, 33 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/461,103, mailed on Nov. 22, 2021, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/476,404, mailed on Feb. 8, 2022, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/476,404, mailed on Sep. 14, 2022, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/308,315, mailed on Jul. 28, 2004., 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,455, mailed on Apr. 11, 2019, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/250,152, mailed on Apr. 6, 2018, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/250,152, mailed on Mar. 2, 2017, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/433,320, mailed on May 2, 2019, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/945,610, mailed on Sep. 20, 2018, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/566,673, mailed on Dec. 16, 2015, 23 pages. |
| Non-Final Office Action received in U.S. Appl. No. 12/547,401, mailed on Feb. 11, 2013, 13 pages. |
| Non-Final Office Action received in U.S. Appl. No. 12/547,401, mailed on Jan. 8, 2010, 12 pages. |
| Noriega Josh, “How to Store and Listen to Music Directly from Your Android Wear Smartwatch”, Guiding Tech, Available online at: https://www.guidingtech.com/55254/listen-music-android-wear-smartwatch, Jan. 15, 2016, 16 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015201884, mailed on Oct. 4, 2016, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015267671, mailed on Apr. 4, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2016201454, mailed on Mar. 1, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2016230001, mailed on May 25, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017266867, mailed on Mar. 6, 2019, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017284013, mailed on Aug. 26, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018202751, mailed on Sep. 4, 2019, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018220115, mailed on Jun. 29, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018223051, mailed on Oct. 30, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018229544, mailed on May 4, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018236872, mailed on Jul. 9, 2019, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019203473, mailed on Nov. 7, 2019, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019268111, mailed on Feb. 18, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020207785, mailed on May 4, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020239711, mailed on Dec. 16, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020257092, mailed on Aug. 27, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020273355, mailed on Jan. 17, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020282362, mailed on Jan. 4, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020285524, mailed on Dec. 17, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021201403, mailed on Oct. 22, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021203669, mailed on May 25, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021204454, mailed on Feb. 25, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022201369, mailed on Mar. 17, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022202458, mailed on May 6, 2022, 3 pages. |
| Notice of Allowance and Search Report received for Taiwanese Patent Application No. 104128687, mailed on Jun. 7, 2016, 4 pages. |
| Notice of Allowance received for Brazilian Patent Application No. BR112014003009-0, mailed on Jun. 15, 2021, 3 pages. |
| Notice of Allowance Received for Canadian Patent Application No. 2,661,200, mailed on Aug. 20, 2014, 1 page |
| Notice of Allowance received for Canadian Patent Application No. 2,882,403, mailed on Oct. 31, 2018., 1 page. |
| Notice of Allowance received for Chinese Patent Application No. 201210308569.5, mailed on May 31, 2016, 4 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201280040169.9, mailed on Sep. 4, 2018, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201280047459.6, mailed on Jan. 31, 2018, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201410449822.8, mailed on Mar. 5, 2019, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201580028491.3, mailed on Mar. 29, 2019, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201580028505.1, mailed on Sep. 19, 2019, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201580043701.6, mailed on Jan. 26, 2022, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201620051290.7, mailed on Jun. 22, 2016, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201680011682.3, mailed on Aug. 5, 2020, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201780002398.4, mailed on Jun. 17, 2019, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201780033899.9, mailed on Feb. 8, 2022, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201810338038.8, mailed on Jun. 30, 2020, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201810338040.5, mailed on Mar. 30, 2022, 6 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201810339290.0, mailed on Mar. 9, 2022, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201811367893.8, mailed on Sep. 2, 2022, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201811460172.1, mailed on Jan. 11, 2021, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201811539260.0, mailed on Mar. 15, 2021, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201880001436.9, mailed on May 8, 2020, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201910475434.X, mailed on Mar. 10, 2021, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202010125114.4, mailed on Nov. 24, 2021, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202011450203.2, mailed on Sep. 30, 2022, 4 pages. |
| Notice of Allowance received for Chinese Patent Application No.201520364847.8, mailed on Nov. 5, 2015, 9 pages. |
| Notice of Allowance received for Danish Patent Application No. PA201770408, mailed on Feb. 8, 2019, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2012-500842, mailed on Jun. 20, 2014, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2014-148065, mailed on Jan. 12, 2016, 6 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2014-526255, mailed on Jan. 7, 2016, 6 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2015-095183, mailed on Apr. 21, 2017., 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-001259, mailed on Jul. 27, 2018, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-017400, mailed on Dec. 16, 2016, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-022175, mailed on Jan. 12, 2018, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-569669, mailed on Mar. 19, 2018, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-101107, mailed on Jun. 3, 2019, 5 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-507413, mailed on Jul. 22, 2019, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-543762, mailed on Mar. 30, 2020, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-080122, mailed on May 7, 2021, 28 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-560107, mailed on Dec. 6, 2019, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-116580, mailed on Oct. 2, 2020, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-238894, mailed on Oct. 5, 2020, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-159840, mailed on Jul. 8, 2022, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-183773, mailed on Dec. 23, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-558885, mailed on Jul. 26, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2021-026630, mailed on Jan. 7, 2022, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2021-074395, mailed on Jun. 27, 2022, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2021-563716, mailed on Mar. 14, 2022, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2021-571464, mailed on May 30, 2022, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-079682, mailed on Jul. 15, 2022, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-102840, mailed on Aug. 19, 2022, 4 pages. |
| Notice of allowance received for Korean Patent Application No. 10-2013-7028489, issued on Jan. 25, 2016, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2014-7006538, mailed on May 19, 2016, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2015-0072162, mailed on Dec. 27, 2017, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 1020167025395, issued on Oct. 26, 2016, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7032902, mailed on Sep. 7, 2018, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7035555, mailed on Sep. 23, 2019, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2017-7012145, mailed on Oct. 30, 2019, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2017-7022905, mailed on Jul. 31, 2019, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2017-7035057, mailed on May 31, 2018, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-0035949, mailed on Nov. 28, 2019, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7033301, mailed on Feb. 20, 2019, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7035747, mailed on Dec. 9, 2020, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7014494, mailed on Mar. 19, 2020, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0024632, mailed on Jul. 26, 2021, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0123805, mailed on Jun. 19, 2022, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7002929, mailed on Nov. 26, 2020, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7017803, mailed on Nov. 5, 2020, 6 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7031319, mailed on Apr. 6, 2021, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-0143923, mailed on Jan. 27, 2022, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7005691, mailed on Mar. 29, 2021, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7020549, mailed on Jul. 13, 2021, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7021047, mailed on Dec. 6, 2021, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7032984, mailed on Jun. 29, 2022, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7035472, mailed on Nov. 23, 2021, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7039234, mailed on Dec. 20, 2021, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2022-0091730, mailed on Oct. 4, 2022, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7008567, mailed on Jul. 4, 2022, 9 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2014-7008348, mailed on Feb. 21, 2019, 5 pages. |
| Notice of Allowance received for Mexican Patent Application No. MX/a/2014/001761, mailed on Sep. 11, 2015, 3 pages. |
| Notice of Allowance received for Mexican Patent Application No. MX/a/2016/001209, mailed on Mar. 26, 2018, 3 pages. |
| Notice of Allowance received for Taiwanese Patent Application No. 102120412, mailed on Oct. 28, 2015, 5 pages. |
| Notice of Allowance received for Taiwanese Patent Application No. 104108223, mailed on Jan. 10, 2017, 3 pages. |
| Notice of Allowance received for Taiwanese Patent Application No. 104114953, mailed on Oct. 17, 2017, 3 pages. |
| Notice of Allowance Received for Taiwanese Patent Application No. 104117041, mailed on Feb. 24, 2017., 3 pages. |
| Notice of Allowance received for Taiwanese Pate nt Application No. 106144804, mailed on Jun. 27, 2018, 6 pages. |
| Notice of Allowance received for Taiwanese Patent Application No. 104117042, mailed on Nov. 17, 2017, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/702,968, mailed on Apr. 21, 2021, 20 pages. |
| Notice of Allowance received for U.S. Appl. No. 09/293,507, mailed on Jul. 25, 2002, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 09/293,508, mailed on Feb. 13, 2001, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 10/308,315, mailed on Aug. 27, 2007., 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 10/374,013, mailed on Aug. 27, 2007., 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 10/374,445, mailed on May 5, 2006., 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 10/374,831, mailed on Sep. 10, 2004, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/459,591, mailed on May 21, 2009, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/521,740, mailed on Jul. 24, 2008., 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/767,409, mailed on Jun. 12, 2013, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/960,674, mailed on Sep. 2, 2011, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/983,059, mailed on Feb. 10, 2012., 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/215,651, mailed on Feb. 6, 2014, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/395,537 mailed on Jun. 29, 2016, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/395,541, mailed on Aug. 22, 2013, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/395,541, mailed on Sep. 12, 2013, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/547,401, mailed on Jul. 22, 2013, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/566,669, mailed on Nov. 6, 2014, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/566,671, mailed on Apr. 12, 2013, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/566,671, mailed on Dec. 18, 2013, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/566,672, mailed on Jun. 24, 2013, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/566,672, mailed on Mar. 1, 2013, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/566,673, mailed on Feb. 26, 2020, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/248,872, mailed on Dec. 4, 2014, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/248,882, mailed on Mar. 13, 2014, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/333,900, mailed on Apr. 13, 2015, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/333,900, mailed on Dec. 1, 2015, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/333,900, mailed on Sep. 15, 2015, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/492,057, mailed on Jan. 3, 2017, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/492,057, mailed on May 18, 2017, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/587,850, mailed on Feb. 27, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/587,850, mailed on Nov. 8, 2019, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/285,378, mailed May 19, 2016, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,327, mailed on Mar. 22, 2018, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,327, mailed on Nov. 30, 2017, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,289, mailed on Aug. 24, 2017., 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,289, mailed on Dec. 12, 2017, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,298, mailed on Nov. 29, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,304, mailed on Sep. 9, 2020, 15 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/642,366, mailed on Jan. 14, 2016, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/719,217, mailed on Feb. 13, 2019, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/830,629, mailed on Oct. 17, 2018, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/134,638, mailed on Apr. 10, 2018, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/134,638, mailed on Jul. 27, 2018, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/250,152, mailed on May 1, 2019, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/269,801, mailed on May 3, 2017, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/269,801, mailed on Sep. 7, 2017, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/274,963, mailed on Jul. 6, 2018, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/433,320, mailed on Apr. 1, 2021, 19 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/730,610, mailed on Oct. 21, 2020, 29 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/845,794, mailed on Feb. 14, 2019, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/910,263, mailed on Feb. 18, 2021, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/910,263, mailed on Jan. 22, 2021, 33 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/945,610, mailed on May 20, 2019, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/952,736, mailed on Sep. 11, 2018, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/131,767, mailed on Sep. 6, 2019, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/229,959, mailed on Dec. 4, 2019, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/263,280, mailed on Jun. 8, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/263,280, mailed on Sep. 17, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/422,736, mailed on Apr. 20, 2021, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/422,736, mailed on Jun. 15, 2021, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/434,865, mailed on Apr. 7, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/583,981, mailed on Mar. 26, 2021, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/583,989, mailed on Apr. 1, 2021, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/583,989, mailed on Dec. 24, 2020, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/583,994, mailed on Jun. 24, 2021, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,490, mailed on Aug. 27, 2020, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,490, mailed on Mar. 26, 2021, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,743, mailed on Aug. 7, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,743, mailed on Nov. 16, 2020, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/586,002, mailed on Jun. 9, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/670,949, mailed on May 27, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/670,949, mailed on Sep. 14, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/679,967, mailed on Jun. 15, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/679,967, mailed on Nov. 2, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/803,849, mailed on May 17, 2022, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/807,604, mailed on Apr. 30, 2021, 25 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/836,571, mailed on Feb. 14, 2022, 31 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/836,571, mailed on Sep. 8, 2021, 25 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/888,775, mailed on Jan. 12, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/888,775, mailed on Jul. 26, 2021, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/888,775, mailed on Jun. 3, 2021, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/888,775, mailed on Oct. 19, 2022, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/917,659, mailed on Jul. 8, 2022, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/921,551, mailed on Jan. 13, 2022, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/922,675, mailed on Feb. 10, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/922,675, mailed on Jan. 21, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/922,675, mailed on Sep. 27, 2021, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/987,003, mailed on Aug. 18, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/026,818, mailed on May 13, 2021, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/027,373, mailed on Aug. 2, 2022, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/027,373, mailed on Jun. 3, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/027,373, mailed on Oct. 3, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,833, mailed on Jun. 25, 2021, 15 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,833, mailed on Sep. 20, 2021, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/168,069, mailed on Jan. 19, 2022, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/168,069, mailed on Mar. 22, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/461,103, mailed on Jun. 20, 2022, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/461,103, mailed on Mar. 17, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/841,455, mailed on Oct. 22, 2019, 10 pages. |
| Notice of Grant received for Chinese Patent Application No. 200780033722.5, mailed on Jun. 19, 2014, 4 pages. |
| Notice of Hearing received for Indian Patent Application No. 717/CHENP/2014, mailed on May 5, 2021, 3 pages. |
| Notice of Non-Compliant Amendment received for U.S. Appl. No. 11/522,167 mailed on May 14, 2008, 4 pages. |
| Office Action received for Australian Patent Application No 2015201884, mailed on Oct. 12, 2015, 4 pages. |
| Office Action received for Australian Patent Application No. 2012296381, issued on Jan. 21, 2016, 5 pages. |
| Office Action received for Australian Patent Application No. 2012296381, issued on Mar. 4, 2016, 4 pages. |
| Office Action received for Australian Patent Application No. 2012296381, mailed on Mar. 6, 2015, 4 pages. |
| Office Action received for Australian Patent Application No. 2015100490, issued on Jun. 9, 2015, 6 pages. |
| Office Action received for Australian Patent Application No. 2015100490, mailed on Dec. 15, 2016, 2 pages. |
| Office Action received for Australian Patent Application No. 2015267671, mailed on Apr. 5, 2017., 2 pages. |
| Office Action received for Australian Patent Application No. 2015302298, mailed on Apr. 4, 2018, 3 pages. |
| Office Action received for Australian Patent Application No. 2015302298, mailed on Jul. 20, 2018, 3 pages. |
| Office Action received for Australian Patent Application No. 2015302298, mailed on Sep. 14, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2015302298, mailed on Sep. 4, 2018, 5 pages. |
| Office Action received for Australian Patent Application No. 2016201454, mailed on Mar. 29, 2017., 3 pages. |
| Office Action received for Australian Patent Application No. 2016230001, mailed on Feb. 7, 2018, 3 pages. |
| Office Action received for Australian Patent Application No. 2016266010, mailed on Aug. 23, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2016266010, mailed on May 4, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2016266010, mailed on Nov. 28, 2018, 5 pages. |
| Office Action received for Australian Patent Application No. 2016266010, mailed on Nov. 30, 2017., 5 pages. |
| Office Action received for Australian Patent Application No. 2017100553, mailed on Aug. 4, 2017, 5 pages. |
| Office Action received for Australian Patent Application No. 2017101563, mailed on Jan. 22, 2018, 2 pages. |
| Office Action received for Australian Patent Application No. 2017101563, mailed on Jun. 26, 2018, 3 pages. |
| Office Action received for Australian Patent Application No. 2017266867, mailed on Dec. 6, 2018, 3 pages. |
| Office Action received for Australian Patent Application No. 2017284013, mailed on Mar. 19, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2018101014, mailed on Jan. 18, 2019, 5 pages. |
| Office Action received for Australian Patent Application No. 2018101014, mailed on Sep. 19, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2018202751, mailed on Apr. 2, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2018203624, mailed on Feb. 5, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2018203624, mailed on Mar. 11, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2018203624, mailed on Mar. 15, 2019, 6 pages. |
| Office Action received for Australian Patent Application No. 2018203624, mailed on Oct. 30, 2019, 5 pages. |
| Office Action received for Australian Patent Application No. 2018220115, mailed on Apr. 21, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2018220115, mailed on Oct. 4, 2019, 3 pages. |
| Office Action received for Australian Patent Application No. 2018229544, mailed on Nov. 15, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2018236870, mailed on Jul. 29, 2019, 7 pages. |
| Office Action received for Australian Patent Application No. 2018236870, mailed on Nov. 21, 2018, 10 pages. |
| Office Action received for Australian Patent Application No. 2018236870, mailed on Oct. 31, 2019, 8 pages. |
| Office Action received for Australian Patent Application No. 2018236872, mailed on Nov. 23, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2018271366, mailed on Feb. 25, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2018271366, mailed on Jan. 19, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2018271366, mailed on May 17, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2018271366, mailed on Oct. 26, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2019203473, mailed on Oct. 25, 2019, 2 pages. |
| Office Action received for Australian Patent Application No. 2019268111, mailed on Oct. 27, 2020, 7 pages. |
| Office Action received for Australian Patent Application No. 2020207785, mailed on Dec. 14, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2020207785, mailed on Jul. 13, 2021, 3 pages. |
| Office Action received for Australian Patent Application No. 2020239711, mailed on Sep. 13, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2020257092, mailed on Mar. 3, 2021, 7 pages. |
| Office Action received for Australian Patent Application No. 2020257092, mailed on Nov. 30, 2020, 6 pages. |
| Office Action received for Australian Patent Application No. 2020273355, mailed on Jul. 6, 2021, 3 pages. |
| Office Action received for Australian Patent Application No. 2020273355, mailed on Nov. 23, 2021, 6 pages. |
| Office Action received for Australian Patent Application No. 2020282362, mailed on Nov. 25, 2021, 3 pages. |
| Office Action received for Australian Patent Application No. 2021201243, mailed on Feb. 17, 2022, 4 pages. |
| Office Action received for Australian Patent Application No. 2021201243, mailed on Jun. 1, 2022, 5 pages. |
| Office Action received for Australian Patent Application No. 2021201403, mailed on Mar. 16, 2021, 3 pages. |
| Office Action received for Australian Patent Application No. 2021203669, mailed on Apr. 5, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2021204454, mailed on Aug. 9, 2021, 7 pages. |
| Office Action received for Brazilian Patent Application No. BR112014003009-0, mailed on Oct. 29, 2019, 6 pages. |
| Office Action Received for Canadian Patent Application No. 2,661,200, mailed on Jan. 3, 2013, 5 pages. |
| Office Action received for Canadian Patent Application No. 2,661,200, mailed on Jun. 9, 2010., 3 pages. |
| Office Action Received for Canadian Patent Application No. 2,661,200, mailed on Nov. 1, 2011., 4 pages. |
| Office Action received for Canadian Patent Application No. 2,661,200, mailed on Nov. 14, 2013, 2 pages. |
| Office Action received for Canadian Patent Application No. 2,882,403, mailed on Apr. 2, 2015, 5 pages. |
| Office Action received for Canadian Patent Application No. 2,882,403, mailed on Sep. 15, 2017., 5 pages. |
| Office Action received for Chinese Patent Application No. 201210308569.5, mailed on Feb. 5, 2016, 3 pages. |
| Office Action received for Chinese Patent Application No. 201210308569.5, mailed on Nov. 19, 2014, 24 pages. |
| Office Action received for Chinese Patent Application No. 201210308569.5, mailed on Sep. 1, 2015, 39 pages. |
| Office Action received for Chinese Patent Application No. 201280040169.9, mailed on Jun. 1, 2016, 10 pages. |
| Office Action received for Chinese Patent Application No. 201280040169.9, mailed on Mar. 31, 2017., 13 pages. |
| Office Action received for Chinese Patent Application No. 201280040169.9, mailed on May 14, 2018., 6 pages. |
| Office Action received for Chinese Patent Application No. 201280040169.9, mailed on Sep. 20, 2017., 14 pages. |
| Office Action received for Chinese Patent Application No. 201410449822.8, mailed on Dec. 2, 2016, 9 pages. |
| Office Action received for Chinese Patent Application No. 201410449822.8, mailed on May 4, 2018, 12 pages. |
| Office Action received for Chinese Patent Application No. 201410449822.8, mailed on Nov. 20, 2018, 11 pages. |
| Office Action received for Chinese Patent Application No. 201410449822.8, mailed on Sep. 30, 2017, 20 pages. |
| Office Action received for Chinese Patent Application No. 201510288981.9, mailed on Jul. 1, 2019, 16 pages. |
| Office Action received for Chinese Patent Application No. 201510288981.9, mailed on Jul. 3, 2018, 19 pages. |
| Office Action received for Chinese Patent Application No. 201510288981.9, mailed on Mar. 6, 2019, 20 pages. |
| Office Action received for Chinese Patent Application No. 201580028491.3, mailed on Oct. 8, 2018, 9 pages. |
| Office Action received for Chinese Patent Application No. 201580028505.1, mailed on Jan. 16, 2019, 15 pages. |
| Office Action received for Chinese Patent Application No. 201580028505.1, mailed on Jun. 20, 2019, 7 pages. |
| Office Action received for Chinese Patent Application No. 201580043701.6, mailed on Dec. 24, 2018, 20 pages. |
| Office Action received for Chinese Patent Application No. 201580043701.6, mailed on May 8, 2021, 10 pages. |
| Office Action received for Chinese Patent Application No. 201580043701.6, mailed on Nov. 4, 2019, 20 pages. |
| Office Action received for Chinese Patent Application No. 201580043701.6, mailed on Oct. 12, 2020, 22 pages. |
| Office Action received for Chinese Patent Application No. 201580043701.6, mailed on Sep. 10, 2021, 10 pages. |
| Office Action received for Chinese Patent Application No. 201580046339.8, mailed on Feb. 26, 2019, 18 pages. |
| Office Action received for Chinese Patent Application No. 201580046339.8, mailed on Jun. 3, 2020, 19 pages. |
| Office Action received for Chinese Patent Application No. 201580046339.8, mailed on Oct. 19, 2020, 12 pages. |
| Office Action received for Chinese Patent Application No. 201580046339.8, mailed on Oct. 31, 2019, 9 pages. |
| Office Action received for Chinese Patent Application No. 201680011682.3, mailed on Dec. 2, 2019, 14 pages. |
| Office Action received for Chinese Patent Application No. 201711292804.3, mailed on Aug. 5, 2020, 26 pages. |
| Office Action received for Chinese Patent Application No. 201711292804.3, mailed on Feb. 23, 2021, 17 pages. |
| Office Action received for Chinese Patent Application No. 201711292804.3, mailed on Sep. 10, 2021, 19 pages. |
| Office Action received for Chinese Patent Application No. 201780002398.4, mailed on Feb. 27, 2019, 6 pages. |
| Office Action received for Chinese Patent Application No. 201780002398.4, mailed on Sep. 12, 2018, 17 pages. |
| Office Action received for Chinese Patent Application No. 201780033899.9, mailed on Sep. 3, 2021, 12 pages. |
| Office Action received for Chinese Patent Application No. 201810338038.8, mailed on Jan. 21, 2020, 26 pages. |
| Office Action received for Chinese Patent Application No. 201810338038.8, mailed on May 14, 2019, 26 pages. |
| Office Action received for Chinese Patent Application No. 201810338040.5, mailed on Jun. 3, 2021, 25 pages. |
| Office Action received for Chinese Patent Application No. 201810338040.5, mailed on Oct. 25, 2021, 22 pages. |
| Office Action received for Chinese Patent Application No. 201810338826.7, mailed on Apr. 3, 2019, 21 pages. |
| Office Action received for Chinese Patent Application No. 201810338826.7, mailed on Jan. 16, 2020, 16 pages. |
| Office Action received for Chinese Patent Application No. 201810338826.7, mailed on Oct. 21, 2019, 19 pages. |
| Office Action received for Chinese Patent Application No. 201810339290.0, mailed on Jun. 4, 2021, 20 pages. |
| Office Action received for Chinese Patent Application No. 201810339290.0, mailed on Oct. 18, 2021, 20 pages. |
| Office Action received for Chinese Patent Application No. 201811367893.8, mailed on Apr. 27, 2022, 11 pages. |
| Office Action received for Chinese Patent Application No. 201811367893.8, mailed on Feb. 15, 2022, 14 pages. |
| Office Action received for Chinese Patent Application No. 201811367893.8, mailed on Jun. 21, 2021, 18 pages. |
| Office Action received for Chinese Patent Application No. 201811367893.8, mailed on Nov. 29, 2021, 6 pages. |
| Office Action received for Chinese Patent Application No. 201811460172.1, mailed on Jan. 21, 2020, 17 pages. |
| Office Action received for Chinese Patent Application No. 201811460172.1, mailed on Oct. 14, 2020, 7 pages. |
| Office Action received for Chinese Patent Application No. 201811539259.8, mailed on Apr. 3, 2020, 10 pages. |
| Office Action received for Chinese Patent Application No. 201811539259.8, mailed on Sep. 3, 2020, 10 pages. |
| Office Action received for Chinese Patent Application No. 201811539259.8, mailed on Sep. 18, 2019, 12 pages. |
| Office Action received for Chinese Patent Application No. 201811539260.0, mailed on Jun. 3, 2020, 8 pages. |
| Office Action received for Chinese Patent Application No. 201811539260.0, mailed on Nov. 4, 2020, 9 pages. |
| Office Action received for Chinese Patent Application No. 201811539260.0, mailed on Oct. 8, 2019, 14 pages. |
| Office Action received for Chinese Patent Application No. 201880001436.9, mailed on Apr. 28, 2019, 19 pages. |
| Office Action received for Chinese Patent Application No. 201880001436.9, mailed on Nov. 6, 2019, 24 pages. |
| Office Action received for Chinese Patent Application No. 201910164962.3, mailed on Apr. 8, 2020, 25 pages. |
| Office Action received for Chinese Patent Application No. 201910164962.3, mailed on Jan. 12, 2021, 14 pages. |
| Office Action received for Chinese Patent Application No. 201910164962.3, mailed on Sep. 18, 2020, 19 pages. |
| Office Action received for Chinese Patent Application No. 201910475434.X, mailed on Dec. 4, 2019, 14 pages. |
| Office Action received for Chinese Patent Application No. 201910475434.X, mailed on Jun. 3, 2020, 9 pages. |
| Office Action received for Chinese Patent Application No. 201910475434.X, mailed on Oct. 30, 2020, 9 pages. |
| Office Action received for Chinese Patent Application No. 201911128105.4, mailed on Apr. 8, 2021, 10 pages. |
| Office Action received for Chinese Patent Application No. 201911128105.4, mailed on Jan. 4, 2021, 14 pages. |
| Office Action received for Chinese Patent Application No. 201911128105.4, mailed on Jul. 3, 2020, 18 pages. |
| Office Action received for Chinese Patent Application No. 202010125114.4, mailed on Aug. 21, 2020, 16 pages. |
| Office Action received for Chinese Patent Application No. 202010125114.4, mailed on Jun. 7, 2021, 7 pages. |
| Office Action received for Chinese Patent Application No. 202010125114.4, mailed on Mar. 1, 2021, 15 pages. |
| Office Action received for Chinese Patent Application No. 202011450203.2, mailed on Apr. 20, 2022, 9 pages. |
| Office Action received for Chinese Patent Application No. 202011450203.2, mailed on Sep. 1, 2021, 12 pages. |
| Office Action received for Chinese Patent Application No. 202080039642.6, mailed on Sep. 5, 2022, 12 pages. |
| Office Action received for Chinese Patent Application No. 202110235995.X, mailed on Mar. 22, 2022, 17 pages. |
| Office Action received for Chinese Patent Application No. 202110235995.X, mailed on Sep. 30, 2022, 13 pages. |
| Office Action received for Chinese Patent Application No. 202111612841.4, mailed on Jul. 22, 2022, 13 pages. |
| Office Action received for Chinese Patent Application No. 202111652452.4, mailed on Aug. 29, 2022, 23 pages. |
| Office Action received for Danish Patent Application No. PA201570256, mailed on Jul. 7, 2015, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570256, mailed on Mar. 17, 2016, 5 pages. |
| Office Action received for Danish Patent Application No. PA201570256, mailed on May 23, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201570256, mailed on Oct. 10, 2016, 3 pages. |
| Office Action Received for Danish Patent Application No. PA201670622, mailed on Aug. 17, 2018, 4 pages. |
| Office Action Received for Danish Patent Application No. PA201670622, mailed on May 30, 2017, 4 pages. |
| Office Action received for Danish Patent Application No. PA201670622, mailed on Nov. 1, 2017, 5 pages. |
| Office Action Received for Danish Patent Application No. PA201670622, mailed on Oct. 31, 2016, 11 pages. |
| Office Action received for Danish Patent Application No. PA201670628, mailed on Jun. 6, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670628, mailed on Oct. 26, 2016, 7 pages. |
| Office Action received for Danish Patent Application No. PA201770392, mailed on Apr. 17, 2018, 2 pages. |
| Office Action received for Danish Patent Application No. PA201770392, mailed on Dec. 8, 2017, 4 pages. |
| Office Action received for Danish Patent Application No. PA201770392, mailed on Jun. 20, 2017, 11 pages. |
| Office Action received for Danish Patent Application No. PA201770401, mailed on Jan. 31, 2018, 3 pages. |
| Office Action received for Danish Patent Application No. PA201770401, mailed on May 17, 2018, 3 pages. |
| Office Action received for Danish Patent Application No. PA201770402, mailed on Apr. 16, 2018, 5 pages. |
| Office Action received for Danish Patent Application No. PA201770402, mailed on Dec. 18, 2017, 6 pages. |
| Office Action received for Danish Patent Application No. PA201770402, mailed on Jun. 19, 2017, 11 pages. |
| Office Action received for Danish Patent Application No. PA201770403, mailed on Dec. 12, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201770403, mailed on Jun. 16, 2017, 8 pages. |
| Office Action received for Danish Patent Application No. PA201770404, mailed on Aug. 8, 2018, 4 pages. |
| Office Action received for Danish Patent Application No. PA201770404, mailed on Dec. 1, 2017, 5 pages. |
| Office Action received for Danish Patent Application No. PA201770404, mailed on Feb. 21, 2019, 2 pages. |
| Office Action received for Danish Patent Application No. PA201770404, mailed on May 1, 2019, 2 pages. |
| Office Action received for Danish Patent Application No. PA201770406, mailed on Feb. 27, 2018, 7 pages. |
| Office Action received for Danish Patent Application No. PA201770406, mailed on Jan. 25, 2019, 8 pages. |
| Office Action received for Danish Patent Application No. PA201770406, mailed on Jun. 22, 2017, 11 pages. |
| Office Action received for Danish Patent Application No. PA201770406, mailed on Mar. 26, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201770406, mailed on Nov. 11, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201770408, mailed on Dec. 21, 2017., 6 pages. |
| Office Action received for Danish Patent Application No. PA201770408, mailed on Jun. 20, 2017, 9 pages. |
| Office Action received for Danish Patent Application No. PA201770408, mailed on May 3, 2018, 7 pages. |
| Office Action received for Danish Patent Application No. PA201770410, mailed on Apr. 9, 2018, 5 pages. |
| Office Action received for Danish Patent Application No. PA201770410, mailed on Jun. 23, 2017, 9 pages. |
| Office Action received for Danish Patent Application No. PA201770410, mailed on Nov. 22, 2018, 5 pages. |
| Office Action received for Danish Patent Application No. PA201770782, mailed on Jan. 26, 2018, 8 pages. |
| Office Action received for Danish Patent Application No. PA201770782, mailed on Nov. 22, 2018, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870060, mailed on Jan. 15, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870060, mailed on Jul. 25, 2019, 2 pages. |
| Office Action received for Danish Patent Application No. PA201870419, mailed on Feb. 27, 2020, 8 pages. |
| Office Action received for Danish Patent Application No. PA201870419, mailed on Sep. 30, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870598, mailed on May 1, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870598, mailed on Nov. 8, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201970533, mailed on Apr. 20, 2021, 2 pages. |
| Office Action received for Danish Patent Application No. PA201970533, mailed on Jul. 17, 2020, 6 pages. |
| Office Action received for Danish Patent Application No. PA202070560, mailed on Dec. 11, 2020, 7 pages. |
| Office Action received for Danish Patent Application No. PA202070560, mailed on Mar. 10, 2021, 7 pages. |
| Office Action received for Danish Patent Application No. PA202070617, mailed on Sep. 24, 2021, 4 pages. |
| Office Action received for Danish Patent Application No. PA202170320, mailed on May 3, 2022, 3 pages. |
| Office Action received for Danish Patent Application No. PA202270464, mailed on Oct. 25, 2022, 9 pages. |
| Office Action received for European Patent Application No. 00923491.5, mailed on Jan. 11, 2010., 6 pages. |
| Office Action received for European Patent Application No. 00923491.5, mailed on Mar. 12, 2007., 9 pages. |
| Office Action received for European Patent Application No. 00923491.5, mailed on Sep. 11, 2007., 5 pages. |
| Office Action received for European Patent Application No. 07842262.3, mailed on Feb. 16, 2017., 6 pages. |
| Office Action received for European Patent Application No. 07842262.3, mailed on Sep. 8, 2011, 5 pages. |
| Office Action received for European Patent Application No. 10177096.4, mailed on Feb. 20, 2012., 6 pages. |
| Office Action received for European Patent Application No. 10177096.4, mailed on Jul. 26, 2017, 8 pages. |
| Office Action received for European Patent Application No. 10177096.4, mailed on Jun. 7, 2018, 14 pages. |
| Office Action received for European Patent Application No. 10177096.4, mailed on Mar. 21, 2013., 9 pages. |
| Office Action received for European Patent Application No. 10177099.8, mailed on Feb. 20, 2012., 5 pages. |
| Office Action received for European Patent Application No. 10712824.1, mailed on Jun. 23, 2014, 7 pages. |
| Office Action received for European Patent Application No. 12753631.6, mailed on Jul. 10, 2017, 6 pages. |
| Office Action received for European Patent Application No. 12770400.5, mailed on Mar. 10, 2015, 5 pages. |
| Office Action received for European Patent Application No. 12773460.6, mailed on Feb. 19, 2018, 6 pages. |
| Office Action received for European Patent Application No. 13171047.7, mailed on May 24, 2017, 7 pages. |
| Office Action received for European Patent Application No. 13184872.3, mailed on May 18, 2018, 8 pages. |
| Office Action received for European Patent Application No. 15711969.4, mailed on Nov. 17, 2017, 9 pages. |
| Office Action received for European Patent Application No. 15713062.6, mailed on Dec. 6, 2017, 7 pages. |
| Office Action received for European Patent Application No. 15714698.6, mailed on Oct. 13, 2021, 2 pages. |
| Office Action received for European Patent Application No. 15719347.5, mailed on Apr. 9, 2020, 4 pages. |
| Office Action received for European Patent Application No. 15719347.5, mailed on Jun. 17, 2019, 4 pages. |
| Office Action received for European Patent Application No. 16710590.7, mailed on Mar. 15, 2019, 10 pages. |
| Office Action received for European Patent Application No. 17799904.2, mailed on Oct. 21, 2020, 6 pages. |
| Office Action received for European Patent Application No. 17813737.8, mailed on Apr. 16, 2021, 7 pages. |
| Office Action received for European Patent Application No. 18178147.7, mailed on Mar. 20, 2020, 4 pages. |
| Office Action received for European Patent Application No. 18197583.0, mailed on Feb. 28, 2020, 8 pages. |
| Office Action received for European Patent Application No. 18197589.7, mailed on Oct. 1, 2019, 5 pages. |
| Office Action received for European Patent Application No. 18208881.5, mailed on Jun. 11, 2019, 5 pages. |
| Office Action received for European Patent Application No. 18208881.5, mailed on May 7, 2021, 6 pages. |
| Office Action received for European Patent Application No. 18728002.9, mailed on Dec. 14, 2020, 15 pages. |
| Office Action received for European Patent Application No. 18733381.0, mailed on Oct. 29, 2021, 9 pages. |
| Office Action received for European Patent Application No. 19150528.8, mailed on Jul. 1, 2020, 6 pages. |
| Office Action received for European Patent Application No. 19169980.0, mailed on Mar. 4, 2020, 6 pages. |
| Office Action received for European Patent Application No. 19186538.5, mailed on Oct. 12, 2020, 7 pages. |
| Office Action received for European Patent Application No. 19186538.5, mailed on Oct. 22, 2021, 7 pages. |
| Office Action received for European Patent Application No. 19203942.8, mailed on Oct. 29, 2021, 6 pages. |
| Office Action received for European Patent Application No. 19207753.5, mailed on May 10, 2021, 4 pages. |
| Office Action received for European Patent Application No. 19207753.5, mailed on Nov. 12, 2020, 5 pages. |
| Office Action received for European Patent Application No. 20158824.1, mailed on Jun. 13, 2022, 5 pages. |
| Office Action received for European Patent Application No. 20158824.1, mailed on May 18, 2021, 10 pages. |
| Office Action received for European Patent Application No. 20719301.2, mailed on Feb. 21, 2022, 9 pages. |
| Office Action received for European Patent Application No. 20719301.2, mailed on Jan. 28, 2021, 15 pages. |
| Office Action received for European Patent Application No. 20720310.0, mailed on Oct. 4, 2022, 9 pages. |
| Office Action received for European Patent Application No. 21160991.2, mailed on Mar. 24, 2022, 11 pages. |
| Office Action received for European Patent Application No. 21197457.1, mailed on Sep. 2, 2022, 8 pages. |
| Office Action received for European Patent Application No. 10712824.1, mailed on Mar. 1, 2016, 11 pages. |
| Office Action received for German Patent Application No. 102015208532.5, mailed on Apr. 1, 2019, 20 pages. |
| Office Action received for German Patent Application No. 102015208532.5, mailed on Apr. 21, 2020, 3 pages. |
| Office Action received for German Patent Application No. 102015208532.5, mailed on Aug. 21, 2019, 15 pages. |
| Office Action received for Hong Kong Patent Application No. 151051633, mailed on Jun. 5, 2015, 11 pages. |
| Office Action received for Indian Patent Application No. 202014041529, mailed on Dec. 6, 2021, 6 pages. |
| Office Action Received for Indian Patent Application No. 717/CHENP/2014, mailed on Feb. 7, 2019, 5 pages. |
| Office Action Received for Japanese Patent Application No. 2012500842, mailed on Jan. 31, 2014, 5 pages. |
| Office Action received for Japanese Patent Application No. 2014-148065, mailed on Sep. 7, 2015, 5 pages. |
| Office Action received for Japanese Patent Application No. 2014-17726, mailed on Feb. 9, 2015, 4 pages. |
| Office Action received for Japanese Patent Application No. 2014-526255, mailed on Jun. 12, 2015, 5 pages. |
| Office Action received for Japanese Patent Application No. 2015-095183, mailed on Jun. 3, 2016, 13 pages. |
| Office Action received for Japanese Patent Application No. 2016-001259, mailed on Feb. 23, 2018, 11 pages. |
| Office Action received for Japanese Patent Application No. 2016-001259, mailed on Jan. 6, 2017, 6 pages. |
| Office Action received for Japanese Patent Application No. 2016-001259, mailed on Nov. 13, 2017, 10 pages. |
| Office Action received for Japanese Patent Application No. 2016-022175, mailed on Apr. 10, 2017, 11 pages. |
| Office Action received for Japanese Patent Application No. 2017-075031, mailed on Jul. 30, 2018, 16 pages. |
| Office Action received for Japanese Patent Application No. 2017-101107, mailed on Sep. 7, 2018, 14 pages. |
| Office Action received for Japanese Patent Application No. 2017-507413, mailed on Feb. 22, 2019, 11 pages. |
| Office Action received for Japanese Patent Application No. 2017-507413, mailed on May 25, 2018, 14 pages. |
| Office Action received for Japanese Patent Application No. 2017-543762, mailed on Apr. 8, 2019, 5 pages. |
| Office Action received for Japanese Patent Application No. 2017-543762, mailed on Jul. 9, 2018, 8 pages. |
| Office Action received for Japanese Patent Application No. 2018-080122, mailed on Aug. 9, 2019, 5 pages. |
| Office Action received for Japanese Patent Application No. 2018-080122, mailed on Jan. 28, 2019, 11 pages. |
| Office Action received for Japanese Patent Application No. 2018-080122, mailed on Nov. 27, 2020, 16 pages. |
| Office Action received for Japanese Patent Application No. 2018-119170, mailed on May 10, 2019, 8 pages. |
| Office Action received for Japanese Patent Application No. 2018-560107, mailed on Jun. 14, 2019, 26 pages. |
| Office Action received for Japanese Patent Application No. 2019-124728, mailed on Dec. 14, 2020, 4 pages. |
| Office Action received for Japanese Patent Application No. 2019-124728, mailed on Sep. 18, 2020, 6 pages. |
| Office Action received for Japanese Patent Application No. 2019-238894, mailed on Mar. 6, 2020, 7 pages. |
| Office Action received for Japanese Patent Application No. 2020-159840, mailed on Dec. 10, 2021, 13 pages. |
| Office Action received for Japanese Patent Application No. 2020-159840, mailed on Mar. 28, 2022, 6 pages. |
| Office Action received for Japanese Patent Application No. 2020-184605, mailed on Feb. 14, 2022, 24 pages. |
| Office Action received for Japanese Patent Application No. 2021-026630, mailed on Aug. 20, 2021, 7 pages. |
| Office Action received for Korean Patent Application No. 10-2013-7028487, mailed on Feb. 18, 2016, 8 pages. |
| Office Action Received for Korean Patent Application No. 10-2013-7028487, mailed on Jun. 5, 2015, 9 pages. |
| Office Action received for Korean Patent Application No. 10-2013-7028487, mailed on Jun. 13, 2016, 6 pages. |
| Office Action received for Korean Patent Application No. 10-2013-7028489, mailed on Jun. 4, 2015, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2014-7006538, mailed on Jul. 31, 2015, 8 pages. |
| Office Action received for Korean Patent Application No. 10-2014-7008348, mailed on Jan. 22, 2019, 16 pages. |
| Office Action received for Korean Patent Application No. 10-2015-0072162, mailed on Apr. 20, 2016, 11 pages. |
| Office Action received for Korean Patent Application No. 10-2015-0072162, mailed on Feb. 27, 2017., 12 pages. |
| Office Action received for Korean Patent Application No. 10-2016-7022902, mailed on Sep. 4, 2017., 3 pages. |
| Office Action received for Korean Patent Application No. 10-2016-7035555, mailed on Dec. 26, 2017, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2016-7035555, mailed on Jul. 18, 2019, 9 pages. |
| Office Action received for Korean Patent Application No. 10-2016-7035555, mailed on Sep. 18, 2018, 9 pages. |
| Office Action received for Korean Patent Application No. 10-2017-7012145, mailed on Jul. 18, 2019, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2017-7012145, mailed on Sep. 13, 2018, 6 pages. |
| Office Action received for Korean Patent Application No. 10-2017-7022905, mailed on Oct. 22, 2018, 9 pages. |
| Office Action received for Korean Patent Application No. 10-2017-7035057, mailed on Mar. 21, 2018, 10 pages. |
| Office Action received for Korean Patent Application No. 10-2018-0035949, mailed on Apr. 24, 2019, 9 pages. |
| Office Action received for Korean Patent Application No. 10-2018-0035949, mailed on Dec. 24, 2018, 7 pages. |
| Office Action received for Korean Patent Application No. 10-2018-0035949, mailed on Jun. 20, 2018, 9 pages. |
| Office Action received for Korean Patent Application No. 10-2018-7033301, mailed on Dec. 14, 2018, 6 pages. |
| Office Action received for Korean Patent Application No. 10-2018-7035747, mailed on Apr. 9, 2020, 11 pages. |
| Office Action received for Korean Patent Application No. 10-2018-7035747, mailed on Oct. 14, 2020, 6 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7014494, mailed on Jun. 14, 2019, 11 pages. |
| Office Action received for Korean Patent Application No. 10-2020-0024632, mailed on Dec. 29, 2020, 11 pages. |
| Office Action received for Korean Patent Application No. 10-2020-0024632, mailed on May 18, 2020, 11 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7002929, mailed on Mar. 22, 2020, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7031319, mailed on Dec. 8, 2020, 14 pages. |
| Office Action received for Korean Patent Application No. 10-2021-7021047, mailed on Aug. 13, 2021, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2021-7032984, mailed on Feb. 22, 2022, 8 pages. |
| Office Action received for Korean Patent Application No. 10-2022-7006175, mailed on May 27, 2022, 7 pages. |
| Office Action received for Korean Patent Application No. 10-2022-7008567, mailed on Mar. 28, 2022, 5 pages. |
| Office Action received for Mexican Patent Application No. MX/a/2016/001209, mailed on Apr. 20, 2017, 5 pages. |
| Office Action received for Mexican Patent Application No. MX/a/2016/001209, mailed on Aug. 25, 2016, 4 pages. |
| Office Action received for Mexican Patent Application No. MX/a/2016/001209, mailed on Sep. 13, 2017, 5 pages. |
| Office Action received for Taiwanese Patent Application No. 102120412, mailed on Feb. 25, 2015, 15 pages. |
| Office Action received for Taiwanese Patent Application No. 104108223, mailed on Apr. 25, 2016, 10 pages. |
| Office Action received for Taiwanese Patent Application No. 104114953, issued on Feb. 18, 2017, 9 pages. |
| Office Action received for Taiwanese Patent Application No. 104114953, mailed on Jun. 8, 2016, 11 pages. |
| Office Action Received for Taiwanese Patent Application No. 104117041, mailed on Aug. 22, 2016, 6 pages. |
| Office Action received for Taiwanese Patent Application No. 104117042, mailed on Apr. 20, 2017, 18 pages. |
| Ojeda-Zapata Julio, “Five Apps That Play Podcasts Directly from Your Apple Watch”, Available online at: https://tidbits.com/2018/04/09/five-apps-that-play-podcasts-directly-from-your-apple-watch/, Apr. 9, 2018, 12 pages. |
| On-Line Definition for “Playback”, American Heritage Dictionary of the English Language, 4th Edition, 2000, 1 page. |
| Pairing Your Apple Watch with Your AppleTV, Available online at: https://www.youtube.com/watch?v=C4t8YFSJ-UY, Apr. 27, 2015, 3 pages. |
| Partial European Search Report received for European Patent Application No. 20158824.1, mailed on May 8, 2020, 14 pages. |
| Partial European Search Report received for European Patent Application No. 18197583.0, mailed on Jan. 14, 2019, 18 pages. |
| PartyShare—turn your Xperia into a jukebox, Available at: https://forum.xda-developers.com/crossdevice-dev/sony/app-partyshare-xperia-jukebox-t2877807, Sep. 15, 2014, 5 pages. |
| Petternitter, “User Restricted Collaborative Playlists—The Spotify Community”, Downloaded from: https://community.spotify.com/t5/Archived-Ideas/User-restricted-collaborative-playlists/idi-p/70721, May 28, 2012, 4 pages. |
| Plaisant et al., “Touchscreen Toggle Switches: Push or slide? Design Issues and Usability Study”, Technical Report CAR-TR-521, CS-TR-2557, Nov. 1990, pp. 1-10. |
| Planet Quark, ““See Everything Your Mac Printed””, XP055533938, retrieved from the Internet: URL: https://www.planetquark.com/2011/05/19/see-everything-your-mac-printed/#.XjkfQsgzZGM, May 19, 2011, 7 pages. |
| Pu Fang, “Research on Location-aware Service in Pervasive Computing”, Issue No. 7, Information Technology Series, China Doctoral Dissertations, Jul. 15, 2008, 140 pages. |
| Punchkick Interactive, “Punchkick hands-on review: Fitbit Surge”, URL: https://www.youtube.com/watch?v=K2G7aebUYcA, Mar. 25, 2015, 3 pages. |
| Q Pair, When I connected to LG G Pad 8.3 Q pair G Flex . . . —G Pad 8.3 review, Posting of a blog, Online Available at: <http://www.leaderyou.co.kr/2595>, Dec. 7, 2013, 28 pages. |
| Qiye Wang, “Design and Implementation of SAN Device Access Control in Unified Storage Platform”, Master's Theses, Huazhong University of Science & Technology, Wuhan, Jun. 2008, 63 pages. |
| QPair, online available at : http://mongri.net/entry/G-Pad-83-Qpair, Retrieved on Mar. 6, 2017, Dec. 20, 2013, 22 pages. |
| Quick Time Movie Player Ver. 2.1.2.59, Current Time Indicator Dragging Operation, Ver. 2.1.2.59, 1996, 1 page. |
| RealOne Player Version 2.0 Screen Dumps, 2002, 4 pages. |
| Record of Oral Hearing received for U.S. Appl. No. 14/641,298, mailed on Oct. 8, 2021, 17 pages. |
| Restriction Requirement received for U.S. Appl. No. 10/374,013, mailed on Oct. 6, 2006., 4 pages. |
| Restriction Requirement received for U.S. Appl. No. 11/767,409, mailed on Sep. 21, 2010., 8 pages. |
| Restriction Requirement received for U.S. Appl. No. 12/215,651, mailed on Sep. 28, 2011, 11 pages. |
| Restriction Requirement received for U.S. Appl. No. 12/395,537, mailed on May 9, 2011, 6 pages. |
| Restriction Requirement received for U.S. Appl. No. 12/395,541, mailed on May 27, 2011, 6 pages. |
| Result of Consultation received for European Patent Application No. 16710590.7, mailed on Dec. 7, 2020, 4 pages. |
| Result of Consultation received for European Patent Application No. 18197583.0, mailed on Feb. 24, 2021, 3 pages. |
| Result of Consultation received for European Patent Application No. 18197589.7, mailed on Dec. 1, 2020, 9 pages. |
| Result of Consultation received for European Patent Application No. 18197589.7, mailed on Dec. 17, 2020, 6 pages. |
| Result of Consultation received for European Patent Application No. 20158824.1, mailed on May 17, 2022, 7 pages. |
| Rev. Some Culture, “It's super easy for middle-aged and elderly people to learn compute”, Jul. 31, 2013, 2 pages. |
| Review: Samsung Radiant R3 Wireless Speakers, Available Online at: <https://www.youtube.com/watch?v=ZBICVE1WdKE>, Jan. 19, 2016, 3 pages. |
| Richards, “TN Audio Mixer and Master Volume Control with Automatic Configuration”, Technical Disclosure Bulletin, vol. 37, No. 01, Jan. 1, 1994, pp. 485-486. |
| Ricker Thomas, “iTunes (in the Cloud) 10.3 beta available for download, we go hands-on”, retrieved from the internet: https://www.engadget.com/2011/06/07/itunes-in-the-cloud-10-3-beta-available-for-download-we-go-ha/, 2011, 12 pages. |
| Rossignol Joe, “iOS 10 Concept Simplifies Lock Screen With Collapsed Notifications”, Available online at: https://www.macrumors.com/2016/06/16/ios-10-collapsed-notifications-concept/, Jun. 16, 2016, 10 pages. |
| Samsung, “Control an individual smart device on your watch”, Online Available at: https://www.samsung.com/us/support/troubleshooting/TSG01003208/, Nov. 9, 2018, 1 page. |
| Samsung, “Problems with SmartThings on your Samsung Smartwatch”, Online Available at: https://www.samsung.com/us/support/troubleshooting/TSG01003169/#smartthings-error-on-samsung-smartwatch, Nov. 9, 2018, 10 pages. |
| Samsung, “Samsung—User manual—Galaxy Watch”, Online available at: https://content.abt.com/documents/90234/SM-R810NZDAXAR-use.pdf, Aug. 24, 2018, 102 pages. |
| Samsung, “Samsung R3 Wireless 360° Smart Speaker (Black)”, User Manual ver. 1.0 (English), User manual [online], Available Online at: <https://www.samsung.com/uk/support/model/WAM3500/XU/>, Dec. 16, 2016, 3 pages. |
| Sandrahoutz, “How Do I Delete a Playlist from a Synced Ipod but Not Remove it From the Library in itunes”, Apple Communities Website, Available online at: https://discussions.apple.com/thread/7503609, Mar. 23, 2016, 2 pages. |
| Sawyer Brian, “Get with the CoverFlow”, Available online at <https://briansawyer.net/2005/12/08/get-with-the-coverflow/>, Dec. 9, 2005, pp. 1-2. |
| Search Report and Opinion received for Danish Patent Application No. PA201770401, mailed on Jun. 19, 2017, 6 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870060 mailed on Apr. 30, 2018, 7 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870419, mailed on Aug. 27, 2018, 7 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870419, mailed on Sep. 10, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870598, mailed on Dec. 5, 2018, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970533, mailed on Oct. 25, 2019, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070617, mailed on Dec. 23, 2020, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202170320, mailed on Oct. 6, 2021, 9 pages. |
| Search Report received for Danish Patent Application No. PA201770404, mailed on Jun. 20, 2017., 8 pages. |
| Search Report received for Danish Patent Application No. PA201770409, mailed on Jun. 20, 2017., 9 pages. |
| Search Report received for European Patent Application No. 00923491.5, Mailed on Jun. 2, 2006, 6 pages. |
| Search Report received for European Patent Application No. 00923491.5, mailed on Mar. 6, 2006., 4 pages. |
| Search Report received for Netherlands Patent Application No. 2014737, mailed on Oct. 29, 2015, 9 pages. |
| Seifert Dan, “Google Home review: Home is where the smart is”, The Verge, Available Online at: <https://www.theverge.com/2016/11/3/13504658/google-home-review-speaker-assistant-amazon-echo-competitor>, Nov. 3, 2016, 11 pages. |
| Seifi Joe, “Pianist Pro Review”, available at <http://www.appsafari.com/productivity/11529/pianist-pro/>, Apr. 24, 2010, 9 pages. |
| Senicar et al., “User-Centred Design and Development of an Intelligent Light Switch for Sensor Systems”, Technical Gazette, vol. 26, No. 2, available online at: https://hrcak.srce.hr/file/320403, 2019, pp. 339-345. |
| Shankland Stephen, “Chrome OS Gets ‘OK Google’ Voice Search Control”, available online at <http://www.cnet.com/news/chrome-os-gets-ok-google-voice-search-control/>, May 21, 2014, 4 pages. |
| Sharepoint at Rackspace, “Sharepoint 2013: How to Edit a List or Library Using Quick Edit”, Available online at: https://www.youtube.com/watch?v=foZXcFC1k80, Oct. 10, 2014, 1 page. |
| Singh Ajit, “MYTUNZ: Free Iphone Media Player App With Sleep Timer, Gesture Control”, Available online at: https://www.ilovefreesoftware.com/01/iphone/mytunz-free-iphone-media-player-app.html, Jul. 1, 2014, 6 pages. |
| Smart Home App—What is the Widget, Online Available at: https://support.vivint.com/s/article/Vivint-Smart-Home-App-What-is-the-Widget, Jan. 26, 2019, 4 pages. |
| SmartTricks, “Top 3 Music Player for Android”, Available online at: <https://www.youtube.com/watch?v=He7RTn4CL34>, Feb. 22, 2017, 4 pages. |
| Smith Eddie, “The expert's guide to Instapaper”, available online at “http://www.macworld.com/article/1166898/the_experts_guide_to_instapaper.html”, May 23, 2012, 8 pages. |
| Sonos, “Sonos Controller App for iPad Product Guide”, Available online at:—https://www.sonos.com/documents/productguides/en/iPadGuide_EN.pdf, Nov. 2014, 47 pages. |
| Stroud Forrest, “Screen Lock Meaning & Definition”, Online Available at: https://www.webopedia.com/definitions/screen-lock, Jan. 30, 2014, 3 pages. |
| Summon to Attend Oral Proceeding received for European Patent Application No. 10177099.8 mailed on Mar. 20, 2013, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application 20158824.1, mailed on Dec. 7, 2021, 6 pages. |
| Summons to attend oral proceedings received for European Patent Application No. 00923491.5, mailed on Jan. 27, 2011., 10 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 07842262.3, mailed on Jun. 25, 2018, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 12753631.6, mailed on Jul. 6, 2018, 5 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 12753631.6, mailed on May 8, 2018, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 12770400.5, mailed on Mar. 19, 2018, 10 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 13171047.7, mailed on Jul. 9, 2018, 12 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15711969.4, mailed on Oct. 22, 2018, 12 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17799904.2, mailed on Dec. 20, 2021, 8 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17813737.8, mailed on Jan. 4, 2022, 12 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 18178147.7, mailed on Jun. 28, 2021, 8 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 18197583.0, mailed on Aug. 14, 2020, 12 pages. |
| Summons to attend Oral proceedings received for European Patent Application No. 18197589.7, mailed on Apr. 9, 2020, 7 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 18208881.5, mailed on Jun. 29, 2022, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 18728002.9, mailed on Jun. 3, 2022, 15 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19150528.8, mailed on Mar. 15, 2022, 7 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19169980.0, mailed on Dec. 3, 2020, 8 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 21160991.2, mailed on Oct. 19, 2022, 10 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 10177096.4, mailed on Sep. 21, 2018, 12 pages. |
| Summons to Oral Proceedings received for German Patent Application No. 112007002143.8 mailed on Nov. 28, 2018, 13 pages. |
| SupertuneTV, “Ipod Nano 6G—Sync Selected Playlist iTunes”, Youtube, Available online at: https://www.youtube.com/watch?v=xU 3rYRabt_I, Sep. 10, 2012, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/584,490, mailed on Apr. 13, 2021, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/584,743, mailed on Nov. 25, 2020, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/168,069, mailed on Apr. 20, 2022, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/168,069, mailed on Feb. 2, 2022, 2 pages. |
| Tedeschi Bob, “Stoking a Music Fan's Fancy With Apps That Rock”, available at <http://www.nytimes.com/2010/05/20/technology/personaltech/20smart.html>, May 19, 2010, 3 pages. |
| The Single Keyboard Piano, available at <http://moocowmusic.com/PianistPro/Manual/ManualSingleKeyboardPiano.html>, Sep. 26, 2010, 4 pages. |
| Vanhemert Kyle, “Why Siri Could Be the Killer App for Smartwatches”, XP002798416, Retrieved from the Internet: URL: https://www.wired.com/2013/12/what-can-a-smartwatch-really-do/, Dec. 19, 2013, 14 pages. |
| Whitehouse Ben, “Coverflow: Better Digital Music Navigation”, Whitehouse&Company, Online Available at <http://wandco.com/2005/08/coverflow-better-digital-music-navigation/>, Aug. 15, 2005, pp. 1-3. |
| Whitney Lance, “How to Listen to Music on Your Apple Watch”, Available Online at: https://medium.com/pcmag-access/how-to-listen-to-music-on-your-apple-watch-f48a6c20dd52#:˜:text=On%20your%20iPhone%2C%20go%20to,.%E2%80%9D%20Tap%20on%20Add%20Music., Mar. 2, 2018, 13 pages. |
| Whitwam Ryan, “How to Sync and Play Music on Your Android Wear Watch”, Available online at: https://www .greenbot.com/article/2997520/how-to-sync-and-play-music-on-your-android-wear-watch.html, Nov. 2, 2015, 4 pages. |
| Wikipedia, “QR code”, Available online at: https://en.wikipedia.org/w/index.php?title=OR_code&oldid=452939488, Sep. 28, 2011, pp. 1-9. |
| Windows Media Player for Windows XP version 8.0, 2001, 2 pages. |
| Woolsey Amanda, “Apple Watch Tips—How to Add and Play Music”, Available online at: <https://www.youtube.com/watch?v=E0QEuqMaoi8>, Apr. 26, 2015, 3 pages. |
| WZ Science Alliance, “Very simple geriatrics computer and Internet bestselling upgrade”, Sep. 30, 2013, 3 pages. |
| Yamaguchi Yuu, “Useful Freeware and Shareware Information”, Pick Up Onlineware, 23th, MdN, vol. 146, MdN Corporation, Jun. 6, 2006, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/181,089, mailed on Sep. 18, 2023, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/320,900, mailed on Sep. 18, 2023, 5 pages. |
| Extended European Search Report received for European patent Application No. 23191379.9, mailed on Sep. 18, 2023, 8 pages. |
| Final Office Action received for U.S. Appl. No. 17/476,404, mailed on Sep. 12, 2023, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/506,197, mailed on Sep. 14, 2023, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/088,309, mailed on Sep. 21, 2023, 11 pages. |
| Office Action received for European Patent Application No. 20746429.8, mailed on Sep. 20, 2023, 10 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/181,089, mailed on Apr. 7, 2023, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/479,974, mailed on Apr. 4, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/077,905, mailed on Apr. 10, 2023, 2 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/048358, mailed on Apr. 6, 2023, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/043733, mailed on Jan. 3, 2023, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/476,404, mailed on Mar. 30, 2023, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/835,110, mailed on Apr. 3, 2023, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/077,971, mailed on Apr. 3, 2023, 24 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018271366, mailed on Mar. 31, 2023, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/509,356, mailed on Apr. 7, 2023, 11 pages. |
| Office Action received for Chinese Patent Application No. 201811539259.8, mailed on Mar. 13, 2023, 16 pages (8 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Indian Patent Application No. 202215025360, mailed on Mar. 29, 2023, 6 pages. |
| Office Action received for Indian Patent Application No. 202215025363, mailed on Mar. 29, 2023, 6 pages. |
| Office Action received for Indian Patent Application No. 202215025364, mailed on Mar. 29, 2023, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/320,900, mailed on Apr. 17, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/752,582, mailed on Apr. 17, 2023, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/922,675, mailed on Apr. 14, 2023, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/077,905, mailed on Apr. 19, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/077,905, mailed on Apr. 26, 2023, 3 pages. |
| Extended European Search Report received for European Patent Application No. 23157906.1, mailed on Apr. 6, 2023, 10 pages. |
| Final Office Action received for U.S. Appl. No. 17/181,089, mailed on Apr. 19, 2023, 13 pages. |
| Intention to Grant received for European Patent Application No. 18728002.9, mailed on Apr. 12, 2023, 9 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202080039642.6, mailed on Apr. 17, 2023, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2022-007217, mailed on Apr. 10, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for European Patent Application No. 15714698.6, mailed on Apr. 18, 2023, 14 pages. |
| Office Action received for European Patent Application No. 20720310.0, mailed on Apr. 11, 2023, 8 pages. |
| Office Action received for Indian Patent Application No. 202215025361, mailed on Mar. 29, 2023, 6 pages. |
| Advisory Action received for U.S. Appl. No. 17/747,804, mailed on Jun. 23, 2023, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/306,354, mailed on Jun. 28, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/824,510, mailed on Jun. 16, 2023, 4 pages. |
| Final Office Action received for U.S. Appl. No. 17/479,974, mailed on Jun. 28, 2023, 32 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/519,025, mailed on Jun. 22, 2023, 7 pages. |
| Office Action received for Australian Patent Application No. 2022235591, mailed on Jun. 6, 2023, 3 pages. |
| Office Action received for Australian Patent Application No. 2022241590, mailed on Jun. 7, 2023, 7 pages. |
| Office Action received for Chinese Patent Application No. 201811379281.0, mailed on May 16, 2023, 16 pages (6 pages of English Translation and 10 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202111652452.4, mailed on May 19, 2023, 15 pages (8 pages of English Translation and 7 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/666,971, mailed on Jan. 16, 2024, 2 pages. |
| Final Office Action received for U.S. Appl. No. 17/479,974, mailed on Jan. 19, 2024, 16 pages. |
| Office Action received for Australian Patent Application No. 2023204396, mailed on Jan. 8, 2024, 5 pages. |
| Office Action received for Chinese Patent Application No. 202110902807.4, mailed on Dec. 15, 2023, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/067,350, mailed on Sep. 11, 2023, 4 pages. |
| Decision to Grant received for European Patent Application No. 19203942.8, mailed on Nov. 16, 2023, 2 pages. |
| Extended European Search Report received for European Patent Application No. 23172038.4, mailed on Oct. 11, 2023, 10 pages. |
| Extended European Search Report received for European Patent Application No. 23190753.6, mailed on Nov. 22, 2023, 13 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2023/020569, mailed on Sep. 21, 2023, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/067,350, mailed on Aug. 3, 2023, 41 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022241590, mailed on Nov. 14, 2023, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/699,492, mailed on Nov. 29, 2023, 5 pages. |
| Office Action received for Japanese Patent Application No. 2022-129377, mailed on Nov. 10, 2023, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2023-0001668, mailed on Nov. 3, 2023, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 21197457.1, mailed on Nov. 23. 2023, 12 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/922,675, mailed on Jan. 9, 2023, 3 pages. |
| Extended European Search Report received for European Patent Application No. 22195584.2, mailed on Jan. 5, 2023, 13 pages. |
| Extended European Search Report received for European Patent Application No. 22201007.6, mailed on Jan. 12, 2023, 7 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 20760624.5, mailed on Jan. 2, 2023, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202111612841.4, mailed on Jan. 5, 2023, 3 pages (2 pages of English Translation & 1 page of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7001521, mailed on Dec. 26, 2022, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 17/181,089, mailed on Dec. 8, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/181,089, mailed on Nov. 28, 2023, 3 pages. |
| Final Office Action received for U.S. Appl. No. 18/067,350, mailed on Dec. 13, 2023, 44 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/020569, mailed on Nov. 13, 2023, 23 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/024279, mailed on Nov. 17, 2023, 20 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2023/024279, mailed on Sep. 26, 2023, 12 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7033655, mailed on Nov. 29, 2023, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2023-7008877, mailed on Nov. 29, 2023, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 21207736.6, mailed on Nov. 23, 2023, 5 pages. |
| Final Office Action received for U.S. Appl. No. 17/314,948, mailed on Mar. 7, 2023, 31 pages. |
| Intention to Grant received for Danish Patent Application No. PA202270464, mailed on Feb. 20, 2023, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/752,582, mailed on Mar. 6, 2023, 17 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022200901, mailed on Mar. 9, 2023, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/519,025, mailed on Mar. 2, 2023, 8 pages. |
| Office Action received for Chinese Patent Application No. 202111652452.4, mailed on Feb. 11, 2023, 28 pages (13 pages of English Translation and 15 pages of Official Copy). |
| Office Action received for European Patent Application No. 20760624.5, mailed on Mar. 7, 2023, 13 pages. |
| Office Action received for European Patent Application No. 21728781.2, mailed on Mar. 1, 2023, 13 pages. |
| Philips Support Website, “How to switch to preferred audio language in Philips TV from a broadcast with multiple languages audio stream?”, Available Online at: https://www.usa.philips.com/c-f/XC000010105/how-to-switch-to-preferred-audio-language-in-philips-tv-from-a-broadcast-with-multiple-languages-audio-stream, Dec. 29, 2016, 5 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021261941, mailed on Mar. 15, 2023, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/077,905, mailed on Mar. 24, 2023, 18 pages. |
| Office Action received for Australian Patent Application No. 2022241590, mailed on Mar. 17, 2023, 5 pages. |
| Final Office Action received for U.S. Appl. No. 18/088,309, mailed on Jan. 9, 2024, 13 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/031252, mailed on Dec. 21, 2023, 13 pages. |
| Office Action received for Australian Patent Application No. 2022218517, mailed on Dec. 21, 2023, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2022-7001521, mailed on Dec. 19, 2023, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20720310.0, mailed on Jan. 3, 2024, 12 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/019,845, mailed on Aug. 7, 2023, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/848,845, mailed on Aug. 9, 2023, 4 pages. |
| Extended European Search Report received for European Patent Application No. 23168537.1, mailed on Jul. 25, 2023, 13 pages. |
| Intention to Grant received for European Patent Application No. 19203942.8, mailed on Aug. 1, 2023, 8 pages. |
| Intention to Grant received for European Patent Application No. 21728781.2, mailed on Jul. 28, 2023, 9 pages. |
| Non Final Office Action received for U.S. Appl. No. 17/699,492, mailed on Jul. 27, 2023, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/181,089, mailed on Aug. 4, 2023, 15 pages. |
| Office Action received for Australian Patent Application No. 2022218517, mailed on Jul. 24, 2023, 6 pages. |
| Office Action received for European Patent Application No. 20720310.0, mailed on Jul. 25, 2023, 11 pages. |
| Office Action received for Korean Patent Application No. 10-2022-7033655, mailed on Jul. 27, 2023, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 18733381.0, mailed on Jul. 25, 2023, 7 pages. |
| Advisory Action received for U.S. Appl. No. 17/181,089, mailed on Dec. 20, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/476,404, mailed on Dec. 20, 2022, 2 pages. |
| Decision to Grant received for European Patent Application No. 20158824.1, mailed on Dec. 15, 2022, 3 pages. |
| Decision to Refuse received for European Patent Application No. 18208881.5, mailed on Dec. 23, 2022, 12 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 15714698.6, mailed on Dec. 16, 2022, 4 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 18208881.5, mailed on Dec. 22, 2022, 4 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 18728002.9, mailed on Dec. 22, 2022, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/320,900, mailed on Dec. 22, 2022, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/509,356, mailed on Dec. 22, 2022, 16 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022200515, mailed on Dec. 21, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2022200901, mailed on Dec. 19, 2022, 4 pages. |
| Office Action received for Australian Patent Application No. 2022201532, mailed on Dec. 19, 2022, 5 pages. |
| Office Action received for Danish Patent Application No. PA202270464, mailed on Dec. 20, 2022, 3 pages. |
| Office Action received for Japanese Patent Application No. 2020-184605, mailed on Dec. 12, 2022, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-0053111, mailed on Dec. 12, 2022, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/917,659, mailed on Dec. 21, 2022, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/747,804, mailed on Mar. 17, 2023, 4 pages. |
| Decision on Opposition received for Australian Patent Application No. 2018271366, mailed on Mar. 3, 2023, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/922,675, mailed on Mar. 22, 2023, 8 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/666,971, mailed on Jun. 9, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/476,404, mailed on Jun. 2, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/509,356, mailed on Jun. 13, 2023, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/306,354, mailed on Jun. 2, 2023, 21 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/019,845, mailed on Jun. 5, 2023, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/752,582, mailed on Jun. 13, 2023, 18 pages. |
| Office Action received for Chinese Patent Application No. 201811539259.8, mailed on May 24, 2023, 22 pages (2 pages of English Translation and 20 pages of Official Copy). |
| Office Action received for European Patent Application No. 21197457.1, mailed on May 30, 2023, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/666,971, mailed on Aug. 16, 2023, 8 pages. |
| Office Action received for Australian Patent Application No. 2022218540, mailed on Aug. 3, 2023, 5 pages. |
| Office Action received for Australian Patent Application No. 2022241590, mailed on Aug. 15, 2023, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/077,905, mailed on May 4, 2023, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA202270464, mailed on May 9, 2023, 1 page. |
| Final Office Action received for U.S. Appl. No. 17/666,971, mailed on May 12, 2023, 29 pages. |
| Final Office Action received for U.S. Appl. No. 17/747,804, mailed on Apr. 28, 2023, 17 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022204555, mailed on May 11, 2023, 3 pages. |
| Office Action received for Australian Patent Application No. 2022218517, mailed on Apr. 27, 2023, 7 pages. |
| Office Action received for Chinese Patent Application No. 201911099970.0, mailed on Feb. 23, 2023, 15 pages (05 pages of English Translation and 10 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/479,974, mailed on Jul. 21, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/752,582, mailed on Jul. 17, 2023, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201911099970.0, mailed on Jun. 25, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/922,675, mailed on Jul. 19, 2023, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/824,510, mailed on Jul. 19, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/867,317, mailed on Jul. 6, 2023, 11 pages. |
| Office Action received for Australian Patent Application No. 2022235591, mailed on Jun. 28, 2023, 3 pages. |
| Office Action received for Chinese Patent Application No. 201811377642.8, mailed on Jun. 10, 2023, 13 pages (4 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-184605, mailed on Jul. 3, 2023, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-0053111, mailed on Jun. 29, 2023, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7001521, mailed on Jun. 21, 2023, 10 pages (5 page of English Translation and 5 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/506,197, mailed on Oct. 25, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/699,492, mailed on Oct. 25, 2023, 3 pages. |
| Final Office Action received for U.S. Appl. No. 17/181,089, mailed on Oct. 13, 2023, 15 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022218540, mailed on Oct. 16, 2023, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202111483033.2, mailed on Oct. 7, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2020-184605, mailed on Oct. 10, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 18/077,891, mailed on Oct. 19, 2023, 18 pages. |
| Office Action received for European Patent Application No. 20719301.2, mailed on Oct. 20, 2023, 11 pages. |
| Office Action received for European Patent Application No. 22201007.6, mailed on Oct. 9, 2023, 5 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 18728002.9, mailed on Dec. 7, 2022, 1 page. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 18728002.9, mailed on Nov. 28, 2022, 7 pages. |
| Cohn Emily, “Sonos Just Fixed the Most Annoying Thing About Its iPhone App”, online available at: <https://www.businessinsider.com/sonos-mobile-app-works-on-lock-screen-2016-6>, Jun. 27, 2016, 2 pages. |
| Extended European Search Report received for European Patent Application No. 22198071.7, mailed on Dec. 5, 2022, 8 pages. |
| Fingas Jon, “Sonos Puts Speaker Controls On Your iPhone's Lock Screen”, online available at: <https://www.engadget.com/2016-06-21-sonos-ios-lock-screen-controls.html>, Jun. 21, 2016, 3 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/031252, mailed on Oct. 7, 2022, 18 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 21728781.2, mailed on Dec. 2, 2022, 3 pages. |
| Kazmucha Allyson, “Sonos Controller App for iPhone and i Pad Review”, online available at https://www.imore.com/sonos-controller-app-iphone-and-ipad-review, Mar. 1, 2018, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/666,971, mailed on Dec. 8, 2022, 26 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/922,675, mailed on Dec. 8, 2022, 9 pages. |
| Office Action received for Australian Patent Application No. 2021201243, mailed on Dec. 12, 2022, 3 pages. |
| Office Action received for Chinese Patent Application No. 201811377642.8, mailed on Oct. 27, 2022, 20 pages (08 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201811379281.0, mailed on Oct. 27, 2022, 21 pages (8 pages of English Translation and 13 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 18208881.5, mailed on Dec. 6, 2022, 10 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/848,845, mailed on Aug. 28, 2023, 3 pages. |
| Decision to Grant received for European Patent Application No. 18728002.9, mailed on Aug. 31, 2023, 4 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022235591, mailed on Aug. 18, 2023, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/320,900, mailed on Aug. 29, 2023, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/867,317, mailed on Aug. 30, 2023, 6 pages. |
| Office Action received for Chinese Patent Application No. 202110902807.4, mailed on Jul. 4, 2023, 15 pages (6 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2022-116534, mailed on Aug. 28, 2023, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/509,356, mailed on Feb. 3, 2023, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/922,675, mailed on Jan. 20, 2023, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-014389, mailed on Jan. 27, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2022-125792, mailed on Jan. 27, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7006175, mailed on Jan. 12, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for European Patent Application No. 20719301.2, mailed on Jan. 24, 2023, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/181,089, mailed on Feb. 17, 2023, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/479,974, mailed on Feb. 22, 2023, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/747,804, mailed on Mar. 1, 2023, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/867,317, mailed on Feb. 28, 2023, 18 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021201243, mailed on Feb. 23, 2023, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/888,775, mailed on Feb. 21, 2023, 5 pages. |
| Office Action received for Australian Patent Application No. 2022204555, mailed on Feb. 17, 2023, 5 pages. |
| Office Action received for Chinese Patent Application No. 201911288715.0, mailed on Jan. 20, 2023, 23 pages (11 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for European Patent Application No. 21166718.3, mailed on Feb. 20, 2023, 7 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/888,775, mailed on Mar. 1, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/181,089, mailed on May 16, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/747,804, mailed on May 31, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/867,317, mailed on May 30, 2023, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/509,356, mailed on May 24, 2023, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/824,510, mailed on May 22, 2023, 15 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022201532, mailed on May 22, 2023, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/848,845, mailed on May 24, 2023, 26 pages. |
| Mitroff Sarah, “8 things you should know about Apple Music for Android”, CNET website, downloaded from https://www.cnet.com/tech/services-and-software/apple-music-for-android-what-to-know/, Nov. 11, 2015, 4 pages. |
| Ochs Susie, “Getting Started with Apple Music: 12 Things to Do First”, Macworld 9. website, downloaded from https://www.macworld.com/article/225812/getting-started-with-apple-music-12-things-to-do-first.html, Jun. 30, 2015, 12 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/666,971, mailed on Sep. 29, 2023, 2 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/017280, mailed on Jun. 26, 2023, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/479,974, mailed on Oct. 10, 2023, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/102,025, mailed on Oct. 10, 2023, 12 pages. |
| Office Action received for Chinese Patent Application No. 201811379281.0, mailed on Aug. 17, 2023, 16 pages (5 pages of English Translation and 11 pages of Official Copy). |
| Decision to Grant received for European Patent Application No. 21728781.2, mailed on Feb. 8, 2024, 3 pages. |
| Office Action received for Chinese Patent Application No. 202211558100.7, mailed on Jan. 8, 2024, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for European Patent Application No. 22198071.7, mailed on Feb. 13, 2024, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/506,197, mailed on Feb. 7, 2024, 4 pages. |
| Decision to Refuse received for Japanese Patent Application No. 2022-116534, mailed on Jan. 29, 2024, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Extended European Search Report received for European Patent Application No. 23203414.0, mailed on Jan. 26, 2024, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/506,197, mailed on Jan. 29, 2024, 8 pages. |
| Office Action received for Australian Patent Application No. 2023201057, mailed on Jan. 25, 2024, 6 pages. |
| Office Action received for Indian Patent Application No. 202117048581, mailed on Feb. 1, 2024, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/259,954, mailed on Mar. 23, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/013,778, mailed on Feb. 28, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/088,309, mailed on Feb. 28, 2024, 2 pages. |
| Board Decision received for Chinese Patent Application No. 201580046788.2, mailed on Jun. 6, 2022, 17 pages (1 page of English Translation and 16 pages of Official Copy). |
| Board Opinion received for Chinese Patent Application No. 201580046788.2, mailed on Dec. 29, 2021, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 15760008.1, mailed on Sep. 13, 2021, 8 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/841,614, mailed on Jan. 8, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/013,778, mailed on Mar. 7, 2023, 5 pages. |
| Decision to Grant received for European Patent Application No. 15760008.1, mailed on Aug. 11, 2022, 2 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 17/013,778, mailed on Dec. 20, 2022, 9 pages. |
| Extended European Search Report received for European Patent Application No. 22169639.6, mailed on Jul. 19, 2022, 14 pages. |
| Extended European Search Report received for European Patent Application No. 23158566.2, mailed on Jun. 14, 2023, 10 pages. |
| Final Office Action received for U.S. Appl. No. 14/841,614, mailed on May 10, 2018, 13 pages. |
| Final Office Action received for U.S. Appl. No. 14/841,623, mailed on Sep. 5, 2017, 16 pages. |
| Final Office Action received for U.S. Appl. No. 17/013,778, mailed on Apr. 1, 2022, 11 pages. |
| Intention to Grant received for European Patent Application No. 15760008.1, mailed on Apr. 6, 2022, 11 pages. |
| Intention to Grant received for European Patent Application No. 15760008.1, mailed on Oct. 5, 2021, 11 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/046787, mailed on Mar. 16, 2017, 19 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/046787, mailed on Apr. 1, 2016, 26 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/046787, mailed on Dec. 15, 2015, 8 pages. |
| IPhone, “User Guide for iOS 7.1 Software”, Mar. 2014, 162 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 15760008.1, mailed on Sep. 21, 2021, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/013,778, mailed on Aug. 20, 2021, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,608, mailed on Apr. 12, 2017, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,614, mailed on Jul. 27, 2017, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,623, mailed on Feb. 2, 2017, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/259,954, mailed on Feb. 5, 2020, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/013,778, mailed on Dec. 9, 2021, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/200,480, mailed on Feb. 29, 2024, 16 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2023-7008877, mailed on Feb. 20, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 104128519, mailed on Nov. 20, 2017, 5 pages (2 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 14/841,608, mailed on Nov. 14, 2017, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/841,614, mailed on Oct. 24, 2018, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/841,623, mailed on Feb. 23, 2018, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/259,954, mailed on May 7, 2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/013,778, mailed on Feb. 23, 2023, 8 pages. |
| Office Action received for Australian Patent Application No. 2023203357, mailed on Feb. 14, 2024, 3 pages. |
| Office Action received for Chinese Patent Application No. 201580046788.2, mailed on Apr. 15, 2019, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201580046788.2, mailed on Feb. 25, 2020, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201580046788.2, mailed on Mar. 25, 2021, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201580046788.2, mailed on Sep. 22, 2020, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201880031407.7, mailed on Jan. 12, 2024, 15 pages (7 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202011083486.1, mailed on Jan. 16, 2024, 21 pages (7 pages of English Translation and 14 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202211081603.X, mailed on Jan. 10, 2024, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202211081603.X, mailed on Oct. 20, 2023, 15 pages (7 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202211096369.8, mailed on Sep. 29, 2023, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202211110081.1, mailed on Jan. 8, 2024, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202211110081.1, mailed on Oct. 13, 2023, 16 pages (7 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for European Patent Application No. 15760008.1, mailed on Jul. 16, 2019, 9 pages. |
| Office Action received for Japanese Patent Application No. 2023-022576, mailed on Feb. 26, 2024, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104128519, mailed on Mar. 29, 2017, 16 pages (7 pages of English Translation and 9 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 15760008.1, mailed on Sep. 9, 2021, 7 pages. |
| Samsung, “SM-G900F User Manual”, English (EU). Rev.1.0, Mar. 2014, 249 pages. |
| Sony, “Sony Smartwatch 3 SWR50”, User Guide, Jul. 2014, 31 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15760008.1, mailed on Feb. 5, 2021, 11 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/841,608, mailed on Jan. 25, 2018, 2 pages. |
| Advisory Action received for U.S. Appl. No. 17/479,974, mailed on May 6, 2024, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/941,961, mailed on May 6, 2024, 4 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2023204396, mailed on Apr. 15, 2024, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-129377, mailed on Apr. 26, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2022218517, mailed on Apr. 24, 2024, 4 pages. |
| Office Action received for Chinese Patent Application No. 202010728844.3, mailed on Jan. 27, 2024, 16 pages (8 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for European Patent Application No. 22201007.6, mailed on Mar. 13, 2024, 4 pages. |
| Advisory Action received for U.S. Appl. No. 17/479,974, mailed on Apr. 25, 2024, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/479,974, mailed on Mar. 14, 2024, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/067,350, mailed on Mar. 13, 2024, 4 pages. |
| Decision to Grant received for European Patent Application No. 15714698.6, mailed on Apr. 5, 2024, 2 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 17/181,089, mailed on Apr. 15, 2024, 11 pages. |
| Intention to Grant received for European Patent Application No. 21166718.3, mailed on Mar. 25, 2024, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/043733, mailed on Apr. 4, 2024, 9 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/031749, mailed on Dec. 6, 2023, 23 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/032084, mailed on Nov. 27, 2023, 10 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 21789897.2, mailed on Mar. 14, 2024, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/941,961, mailed on Apr. 10, 2024, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/970,417, mailed on Apr. 10, 2024, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/088,309, mailed on Apr. 9, 2024, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/200,480, mailed on Mar. 6, 2024, 17 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202211558100.7, mailed on Mar. 29, 2024, 3 pages (2 pages of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7001521, mailed on Mar. 22, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202080039832.8, mailed on Mar. 23, 2024, 22 pages (12 pages of English Translation and 10 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110902807.4, mailed on Mar. 28, 2024, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202311321231.8, mailed on Mar. 10, 2024, 15 pages (9 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for European Patent Application No. 22188377.0, mailed on Mar. 7, 2024, 7 pages. |
| Office Action received for European Patent Application No. 23158566.2, mailed on Apr. 9, 2024, 7 pages. |
| Office Action received for Indian Patent Application No. 202118049678, mailed on Apr. 18, 2024, 8 pages. |
| Office Action received for Japanese Patent Application No. 2022-149476, mailed on Apr. 22, 2024, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2023-028786, mailed on Mar. 22, 2024, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7032414, mailed on Mar. 26, 2024, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 20720310.0, mailed on Apr. 17, 2024, 9 pages. |
| A Small Revolution in Touch Screens—Evaluation and Testing of LGKF600, China Academic Journal Electronic Publishing House., Feb. 1, 2008, pp. 60-62 (Official Copy Only) {See Communication Under Rule 37 CFR § 1.98(a) (3)}. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/088,309, mailed on Jun. 7, 2024, 2 pages. |
| Extended European Search Report received for European Patent Application No. 24164409.5, mailed on Jun. 14, 2024, 5 pages. |
| Final Office Action received for U.S. Appl. No. 18/200,480, mailed on Jun. 17, 2024, 19 pages. |
| Intention to Grant received for European Patent Application No. 20720310.0, mailed on Jun. 13, 2024, 13 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 20720310.0, mailed on Jun. 7, 2024, 7 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202110902807.4, mailed on May 21, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-0001668, mailed on May 22, 2024, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202011083486.1, mailed on May 22, 2024, 15 pages (5 pages of English Translation and 10 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 20720310.0, mailed on Jun. 4, 2024, 3 pages. |
| Final Office Action received for U.S. Appl. No. 17/941,961, mailed on Jul. 5, 2024, 21 pages. |
| Intention to Grant received for European Patent Application No. 20719301.2, mailed on Jul. 2, 2024, 9 pages. |
| Intention to Grant received for European Patent Application No. 21197457.1, mailed on Jul. 9, 2024, 12 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 21197457.1, mailed on Jul. 3, 2024, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/228,597, mailed on Jul. 8, 2024, 17 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202010728711.6, mailed on Jul. 1, 2024, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-0053111, mailed on Jun. 25, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2023204647, mailed on Jul. 5, 2024, 3 pages. |
| Office Action received for Chinese Patent Application No. 202311305998.1, mailed on May 29, 2024, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 21197457.1. mailed on May 23. 2024, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/747,804, mailed on Jun. 4, 2024, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/067,350, mailed on May 28, 2024, 43 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/200,480, mailed on May 20, 2024, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/229,989, mailed on May 31, 2024, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/395,167, mailed on May 21, 2024, 11 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2023203357, mailed on May 16, 2024, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201911128105.4, mailed on May 24, 2024, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for Chinese Patent Application No. 202211081603.X, mailed on Apr. 29, 2024, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202211110081.1, mailed on Apr. 28, 2024, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for European Patent Application No. 21207736.6, mailed on May 31, 2024, 4 pages. |
| Office Action received for European Patent Application No. 21789897.2, mailed on May 23, 2024. 12 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/970,417, mailed on Jun. 26, 2024, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/229,989, mailed on Jun. 28, 2024, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/395,167, mailed on Jun. 28, 2024, 4 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 21197457.1, mailed on Jun. 19, 2024, 1 page. |
| Create Confirmation Dialog Box—Matlab Ulconfirm, Online available at: https://www.mathworks.com/help/matlab/ref/uiconfirm.html, 2017, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/234,613, mailed on Jul. 1, 2024, 19 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-116534, mailed on Jun. 24, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 18/235,291, mailed on Jul. 3, 2024, 18 pages. |
| Office Action received for Australian Patent Application No. 2023201057, mailed on Jun. 19, 2024, 5 pages. |
| Office Action received for Chinese Patent Application No. 202210384721.1, mailed on May 23, 2024, 26 pages (14 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for European Patent Application No. 23190753.6, mailed on Jun. 25, 2024, 10 pages. |
| Window confirm( ), Online available at: https://www.w3schools.com/jsref/met_win_confirm.asp, 2014, 5 pages. |
| weifeng.com, “Install and use Apple Pay on your Apple Watch”, Available online at: https://www.mpaypass.com.cn/news/201504/28093555.html, Apr. 28, 2015, 3 pages (Official Copy Only). {See Communication Under Rule 37 CFR § 1.98(a) (3)}. |
| Xiaokai, “Apple senior executive”, Apple Watch mobile payment is convenient and fast, Available online at: https://it.hebei.com.cn/system/2015/03/09/015101153.shtml, Mar. 9, 2015, 2 pages (Official Copy Only). {See Communication Under Rule 37 CFR § 1.98(a) (3)}. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/067,350, mailed on Jul. 29, 2024, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/235,291, mailed on Jul. 18, 2024, 3 pages. |
| Intention to Grant received for European Patent Application No. 23168537.1, mailed on Jul. 25, 2024, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/204,888, mailed on Jul. 18, 2024, 21 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202211110081.1, mailed on Jul. 24, 2024, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 18/229,989, mailed on Jul. 24, 2024, 5 pages. |
| Office Action received for Chinese Patent Application No. 202110894284.3, mailed on Jun. 27, 2024, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for European Patent Application No. 22201007.6, mailed on Jul. 18, 2024, 4 pages. |
| Office Action received for Japanese Patent Application No. 2023-077990, mailed on Jul. 12, 2024, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201911128105.4, mailed on Mar. 16, 2024, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201911128105.4, mailed on Mar. 19, 2024, 16 pages (8 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202010728711.6, mailed on Feb. 1, 2024, 30 pages (18 pages of English Translation and 12 pages of Official Copy). |
| Number | Date | Country | |
|---|---|---|---|
| 20230073844 A1 | Mar 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62622122 | Jan 2018 | US | |
| 62514932 | Jun 2017 | US | |
| 62507202 | May 2017 | US | |
| 62507208 | May 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17835110 | Jun 2022 | US |
| Child | 17978930 | US | |
| Parent | 17461103 | Aug 2021 | US |
| Child | 17835110 | US | |
| Parent | 17031833 | Sep 2020 | US |
| Child | 17461103 | US | |
| Parent | 16807604 | Mar 2020 | US |
| Child | 17031833 | US | |
| Parent | 16702968 | Dec 2019 | US |
| Child | 16807604 | US | |
| Parent | 15910263 | Mar 2018 | US |
| Child | 16702968 | US |
