Patent Grant
12265696
The present disclosure relates generally to computer user interfaces, and more specifically to techniques for managing audio messages.
Users send instant messages to communicate with other users using alphanumeric text. Such messaging techniques typically require the user to enter text using a keyboard or for a device to transcribe audio into text to be subsequently sent. Users interact with external devices using mobile devices. Such interactions often are cumbersome and require the user to interact with multiple external devices individually.
Current techniques for managing audio messages using electronic devices 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 audio messages. Such methods and interfaces optionally complement or replace other methods for managing messages. 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 enable messages to be transmitted that include the tone of the message (e.g., importance, seriousness, sarcastic, sad, cheerful), rather than just the words of the message, and enable the recipient to recognize the speaker of the message by the speaker's own voice. Such methods and interfaces also reduce or eliminate the need to provide input using a keyboard or to correct a transcription using input.
Current techniques for managing statuses of external devices at a mobile device 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 external devices. Such methods and interfaces optionally complement or replace other methods for managing external devices, such as allowing a user to manage external devices individual or managing external devices at the same time via a single input. 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.
In accordance with some embodiments, a method is described. The method is performed at a computer system that is in communication with a display generation component. The method comprises: displaying, via the display generation component, a first user interface that includes: a first selectable user interface object, wherein selection of the first selectable user interface object initiates a process for recording and sending a first audio message to a set of external devices, wherein the set of external devices includes a first set of one or more external devices and a second set of one or more external devices; and a first accessory control user interface object corresponding to a first external accessory device, wherein selection of the first accessory control user interface object initiates a process to transmit an instruction to change a state of the first external accessory device; while displaying the first user interface, receiving an input that corresponds to a request to display a second user interface; and in response to receiving the request to display the second user interface, displaying the second user interface, wherein the second user interface includes: a second selectable user interface object, wherein selection of the second selectable user interface object initiates a process for recording and sending a second audio message to the second set of one or more external devices without sending the second audio message to the first set of one or more external devices; and a second accessory control user interface object corresponding to a second external accessory device, wherein selection of the second accessory control user interface object initiates a process to transmit an instruction to change a state of the second external accessory 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 a computer system in communication with a display generation component, the one or more programs including instructions for: displaying, via the display generation component, a first user interface that includes: a first selectable user interface object, wherein selection of the first selectable user interface object initiates a process for recording and sending a first audio message to a set of external devices, wherein the set of external devices includes a first set of one or more external devices and a second set of one or more external devices; and a first accessory control user interface object corresponding to a first external accessory device, wherein selection of the first accessory control user interface object initiates a process to transmit an instruction to change a state of the first external accessory device; while displaying the first user interface, receiving an input that corresponds to a request to display a second user interface; and in response to receiving the request to display the second user interface, displaying the second user interface, wherein the second user interface includes: a second selectable user interface object, wherein selection of the second selectable user interface object initiates a process for recording and sending a second audio message to the second set of one or more external devices without sending the second audio message to the first set of one or more external devices; and a second accessory control user interface object corresponding to a second external accessory device, wherein selection of the second accessory control user interface object initiates a process to transmit an instruction to change a state of the second external accessory 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 a computer system in communication with a display generation component, the one or more programs including instructions for: displaying, via the display generation component, a first user interface that includes: a first selectable user interface object, wherein selection of the first selectable user interface object initiates a process for recording and sending a first audio message to a set of external devices, wherein the set of external devices includes a first set of one or more external devices and a second set of one or more external devices; and a first accessory control user interface object corresponding to a first external accessory device, wherein selection of the first accessory control user interface object initiates a process to transmit an instruction to change a state of the first external accessory device; while displaying the first user interface, receiving an input that corresponds to a request to display a second user interface; and in response to receiving the request to display the second user interface, displaying the second user interface, wherein the second user interface includes: a second selectable user interface object, wherein selection of the second selectable user interface object initiates a process for recording and sending a second audio message to the second set of one or more external devices without sending the second audio message to the first set of one or more external devices; and a second accessory control user interface object corresponding to a second external accessory device, wherein selection of the second accessory control user interface object initiates a process to transmit an instruction to change a state of the second external accessory device.
In accordance with some embodiments, a computer system is described. The computer system comprises: one or more processors, wherein the computer system is in communication with a display generation component; 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, via the display generation component, a first user interface that includes: a first selectable user interface object, wherein selection of the first selectable user interface object initiates a process for recording and sending a first audio message to a set of external devices, wherein the set of external devices includes a first set of one or more external devices and a second set of one or more external devices; and a first accessory control user interface object corresponding to a first external accessory device, wherein selection of the first accessory control user interface object initiates a process to transmit an instruction to change a state of the first external accessory device; while displaying the first user interface, receiving an input that corresponds to a request to display a second user interface; and in response to receiving the request to display the second user interface, displaying the second user interface, wherein the second user interface includes: a second selectable user interface object, wherein selection of the second selectable user interface object initiates a process for recording and sending a second audio message to the second set of one or more external devices without sending the second audio message to the first set of one or more external devices; and a second accessory control user interface object corresponding to a second external accessory device, wherein selection of the second accessory control user interface object initiates a process to transmit an instruction to change a state of the second external accessory device.
In accordance with some embodiments, a computer system is described. The computer system comprising: means for displaying, via a display generation component that is in communication with the computer system, a first user interface that includes: a first selectable user interface object, wherein selection of the first selectable user interface object initiates a process for recording and sending a first audio message to a set of external devices, wherein the set of external devices includes a first set of one or more external devices and a second set of one or more external devices; and a first accessory control user interface object corresponding to a first external accessory device, wherein selection of the first accessory control user interface object initiates a process to transmit an instruction to change a state of the first external accessory device; means, while displaying the first user interface, for receiving an input that corresponds to a request to display a second user interface; and means, responsive to receiving the request to display the second user interface, for displaying the second user interface, wherein the second user interface includes: a second selectable user interface object, wherein selection of the second selectable user interface object initiates a process for recording and sending a second audio message to the second set of one or more external devices without sending the second audio message to the first set of one or more external devices; and a second accessory control user interface object corresponding to a second external accessory device, wherein selection of the second accessory control user interface object initiates a process to transmit an instruction to change a state of the second external accessory device.
In accordance with some embodiments, a method is described. The method is performed at a computer system in communication with a display generation component. The method comprises: receiving first data corresponding to first media; displaying, via the display generation component, until an end of a first time period, a first notification with an indication of the first media; after receiving the first data, receiving second data corresponding to second media, wherein the second media is different from the first media; and in accordance with a determination that the second media meets a set of one or more criteria and in accordance with a determination based on (1) a time that the second data was received and (2) a time that the first data was received, displaying, via the display generation component, until an end of a second time period, a second notification with an indication of the first media, wherein an end of the first time period is different from an end of the second time period.
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 a computer system in communication with a display generation component, the one or more programs including instructions for: receiving first data corresponding to first media; displaying, via the display generation component, until an end of a first time period, a first notification with an indication of the first media; after receiving the first data, receiving second data corresponding to second media, wherein the second media is different from the first media; and in accordance with a determination that the second media meets a set of one or more criteria and in accordance with a determination based on (1) a time that the second data was received and (2) a time that the first data was received, displaying, via the display generation component, until an end of a second time period, a second notification with an indication of the first media, wherein an end of the first time period is different from an end of the second time period.
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 a computer system in communication with a display generation component, the one or more programs including instructions for: receiving first data corresponding to first media; displaying, via the display generation component, until an end of a first time period, a first notification with an indication of the first media; after receiving the first data, receiving second data corresponding to second media, wherein the second media is different from the first media; and in accordance with a determination that the second media meets a set of one or more criteria and in accordance with a determination based on (1) a time that the second data was received and (2) a time that the first data was received, displaying, via the display generation component, until an end of a second time period, a second notification with an indication of the first media, wherein an end of the first time period is different from an end of the second time period.
In accordance with some embodiments, a computer system is described. The computer system comprises: one or more processors, wherein the computer system is in communication with a display generation component; 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 first data corresponding to first media; displaying, via the display generation component, until an end of a first time period, a first notification with an indication of the first media; after receiving the first data, receiving second data corresponding to second media, wherein the second media is different from the first media; and in accordance with a determination that the second media meets a set of one or more criteria and in accordance with a determination based on (1) a time that the second data was received and (2) a time that the first data was received, displaying, via the display generation component, until an end of a second time period, a second notification with an indication of the first media, wherein an end of the first time period is different from an end of the second time period.
In accordance with some embodiments, a computer system is described. The computer system comprises: means for receiving first data corresponding to first media; means for displaying, via a generation component that is in communication with the computer system, until an end of a first time period, a first notification with an indication of the first media; means, after receiving the first data, for receiving second data corresponding to second media, wherein the second media is different from the first media; and means, in accordance with a determination that the second media meets a set of one or more criteria and in accordance with a determination based on (1) a time that the second data was received and (2) a time that the first data was received, for displaying, via the display generation component, until an end of a second time period, a second notification with an indication of the first media, wherein an end of the first time period is different from an end of the second time period.
In accordance with some embodiments, a method is described. The method is performed at an electronic device having one or more microphones, one or more speakers, and one or more display devices. The method comprises: receiving voice input via the one or more microphones; and displaying a visual indication of the voice input, wherein: in accordance with a determination that a portion of the voice input corresponds to voice input that is to be transmitted to one or more devices displaying, via the one or more display devices, the visual indication includes displaying the visual indication with a first set of one or more colors; and in accordance with a determination that the voice input does not include an instruction to transmit any portion of the voice input to other devices, displaying, via the one or more display devices, the visual indication includes displaying the visual indication with a second set of one or more colors that is different from the first set of one or more colors.
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 having one or more microphones, one or more speakers, and one or more display devices, the one or more programs including instructions for: receiving voice input via the one or more microphones; and displaying a visual indication of the voice input, wherein: in accordance with a determination that a portion of the voice input corresponds to voice input that is to be transmitted to one or more devices displaying, via the one or more display devices, the visual indication includes displaying the visual indication with a first set of one or more colors; and in accordance with a determination that the voice input does not include an instruction to transmit any portion of the voice input to other devices, displaying, via the one or more display devices, the visual indication includes displaying the visual indication with a second set of one or more colors that is different from the first set of one or more colors.
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 having one or more microphones, one or more speakers, and one or more display devices, the one or more programs including instructions for: receiving voice input via the one or more microphones; and displaying a visual indication of the voice input, wherein: in accordance with a determination that a portion of the voice input corresponds to voice input that is to be transmitted to one or more devices displaying, via the one or more display devices, the visual indication includes displaying the visual indication with a first set of one or more colors; and in accordance with a determination that the voice input does not include an instruction to transmit any portion of the voice input to other devices, displaying, via the one or more display devices, the visual indication includes displaying the visual indication with a second set of one or more colors that is different from the first set of one or more colors.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more microphones; one or more speakers; one or more display devices; 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 voice input via the one or more microphones; and displaying a visual indication of the voice input, wherein: in accordance with a determination that a portion of the voice input corresponds to voice input that is to be transmitted to one or more devices displaying, via the one or more display devices, the visual indication includes displaying the visual indication with a first set of one or more colors; and in accordance with a determination that the voice input does not include an instruction to transmit any portion of the voice input to other devices, displaying, via the one or more display devices, the visual indication includes displaying the visual indication with a second set of one or more colors that is different from the first set of one or more colors.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: one or more microphones; one or more speakers; one or more display devices; means for receiving voice input via the one or more microphones; and means displaying a visual indication of the voice input, wherein: in accordance with a determination that a portion of the voice input corresponds to voice input that is to be transmitted to one or more devices displaying, via the one or more display devices, the visual indication includes displaying the visual indication with a first set of one or more colors; and in accordance with a determination that the voice input does not include an instruction to transmit any portion of the voice input to other devices, displaying, via the one or more display devices, the visual indication includes displaying the visual indication with a second set of one or more colors that is different from the first set of one or more colors.
In accordance with some embodiments, a method is described. The method is performed at a computer system, wherein the computer system is in communication with a display generation component and one or more input devices. The method comprises: displaying, via the display generation component, a first status that indicates that a plurality of accessory devices of a first accessory type are in a first state, wherein the plurality of accessory devices of the first accessory type includes: a first accessory device that is the first accessory type and is in the first state; and a second accessory device that is the first accessory type and is in the first state, wherein the second accessory device is different from the first accessory device; while displaying the first status indicator, detecting a gesture; and in response to detecting the gesture: in accordance with a determination that the gesture is a first type of gesture and is directed to the first status indicator, causing the first accessory device and the second accessory device to change to a second state that is different from the first state; and in accordance with a determination that the gesture is a second type of gesture that is different from the first type of gesture and is directed to the first status indicator, displaying, via the display generation component, a first accessory control user interface object corresponding to the first accessory device, wherein selection of the first accessory control user interface object causes the first accessory device to change to the second state without causing the second accessory device to change to the second state.
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 a computer system, wherein the computer system is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: displaying, via the display generation component, a first status that indicates that a plurality of accessory devices of a first accessory type are in a first state, wherein the plurality of accessory devices of the first accessory type includes: a first accessory device that is the first accessory type and is in the first state; and a second accessory device that is the first accessory type and is in the first state, wherein the second accessory device is different from the first accessory device; while displaying the first status indicator, detecting a gesture; and in response to detecting the gesture: in accordance with a determination that the gesture is a first type of gesture and is directed to the first status indicator, causing the first accessory device and the second accessory device to change to a second state that is different from the first state; and in accordance with a determination that the gesture is a second type of gesture that is different from the first type of gesture and is directed to the first status indicator, displaying, via the display generation component, a first accessory control user interface object corresponding to the first accessory device, wherein selection of the first accessory control user interface object causes the first accessory device to change to the second state without causing the second accessory device to change to the second state.
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 a computer system, wherein the computer system is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: displaying, via the display generation component, a first status that indicates that a plurality of accessory devices of a first accessory type are in a first state, wherein the plurality of accessory devices of the first accessory type includes: a first accessory device that is the first accessory type and is in the first state; and a second accessory device that is the first accessory type and is in the first state, wherein the second accessory device is different from the first accessory device; while displaying the first status indicator, detecting a gesture; and in response to detecting the gesture: in accordance with a determination that the gesture is a first type of gesture and is directed to the first status indicator, causing the first accessory device and the second accessory device to change to a second state that is different from the first state; and in accordance with a determination that the gesture is a second type of gesture that is different from the first type of gesture and is directed to the first status indicator, displaying, via the display generation component, a first accessory control user interface object corresponding to the first accessory device, wherein selection of the first accessory control user interface object causes the first accessory device to change to the second state without causing the second accessory device to change to the second state.
In accordance with some embodiments, a computer system is described. The computer system comprises: one or more processors, wherein the computer system is in communication with a display generation component and one or more input devices; 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, via the display generation component, a first status that indicates that a plurality of accessory devices of a first accessory type are in a first state, wherein the plurality of accessory devices of the first accessory type includes: a first accessory device that is the first accessory type and is in the first state; and a second accessory device that is the first accessory type and is in the first state, wherein the second accessory device is different from the first accessory device; while displaying the first status indicator, detecting a gesture; and in response to detecting the gesture: in accordance with a determination that the gesture is a first type of gesture and is directed to the first status indicator, causing the first accessory device and the second accessory device to change to a second state that is different from the first state; and in accordance with a determination that the gesture is a second type of gesture that is different from the first type of gesture and is directed to the first status indicator, displaying, via the display generation component, a first accessory control user interface object corresponding to the first accessory device, wherein selection of the first accessory control user interface object causes the first accessory device to change to the second state without causing the second accessory device to change to the second state.
In accordance with some embodiments, a computer system is described. The computer system comprising: means for, displaying, via the display generation component, a first status that indicates that a plurality of accessory devices of a first accessory type are in a first state, wherein the plurality of accessory devices of the first accessory type includes: a first accessory device that is the first accessory type and is in the first state; and a second accessory device that is the first accessory type and is in the first state, wherein the second accessory device is different from the first accessory device; means, while displaying the first status indicator, for detecting a gesture; and means, responsive to detecting the gesture, for: in accordance with a determination that the gesture is a first type of gesture and is directed to the first status indicator, causing the first accessory device and the second accessory device to change to a second state that is different from the first state; and in accordance with a determination that the gesture is a second type of gesture that is different from the first type of gesture and is directed to the first status indicator, displaying, via the display generation component, a first accessory control user interface object corresponding to the first accessory device, wherein selection of the first accessory control user interface object causes the first accessory device to change to the second state without causing the second accessory device to change to the second state
In accordance with some embodiments, a method is described. The method is performed at a computer system that is in communication with a display generation component and one or more inputs devices. The method comprises: displaying, via the display generation component, a media user interface that includes: at a first location, a first representation of a first media message, and at a second location different from the first location, a second representation of a second media message; in response to displaying the media user interface and not based on user input corresponding to the media user interface, playing the first media message; and in response to detecting completion of playing through the first media message: displaying, the second representation of the second media message without displaying, via the display generation component, a representation corresponding to the first media message.
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 a computer system, wherein the computer system is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: displaying, via the display generation component, a media user interface that includes: at a first location, a first representation of a first media message, and at a second location different from the first location, a second representation of a second media message; in response to displaying the media user interface and not based on user input corresponding to the media user interface, playing the first media message; and in response to detecting completion of playing through the first media message: displaying, the second representation of the second media message without displaying, via the display generation component, a representation corresponding to the first media message.
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 a computer system, wherein the computer system is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: displaying, via the display generation component, a media user interface that includes: at a first location, a first representation of a first media message, and at a second location different from the first location, a second representation of a second media message; in response to displaying the media user interface and not based on user input corresponding to the media user interface, playing the first media message; and in response to detecting completion of playing through the first media message: displaying, the second representation of the second media message without displaying, via the display generation component, a representation corresponding to the first media message.
In accordance with some embodiments, a computer system is described. The computer system comprises: one or more processors, wherein the computer system is in communication with a display generation component and one or more input devices; 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, via the display generation component, a media user interface that includes: at a first location, a first representation of a first media message, and at a second location different from the first location, a second representation of a second media message; in response to displaying the media user interface and not based on user input corresponding to the media user interface, playing the first media message; and in response to detecting completion of playing through the first media message: displaying, the second representation of the second media message without displaying, via the display generation component, a representation corresponding to the first media message.
In accordance with some embodiments, a computer system is described. The computer system is in communication with a display generation component and one or more inputs devices. The computer system comprises: means for displaying, via the display generation component, a media user interface that includes: at a first location, a first representation of a first media message, and at a second location different from the first location, a second representation of a second media message; means, responsive to displaying the media user interface and not based on user input corresponding to the media user interface, for playing the first media message; and means, responsive to detecting completion of playing through the first media message, for: displaying, the second representation of the second media message without displaying, via the display generation component, a representation corresponding to the first media message.
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 audio messages, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for managing audio messages.
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 audio messages. The techniques for managing audio messages increase the efficiency of the devices (e.g., reduce unnecessary display), increase information provided about external devices (e.g., displaying the source of audio messages), and increase privacy (by providing visual feedback to the user of the state of the device about audio input received). Such techniques can reduce the cognitive burden on a user who uses audio messages, 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, depth camera controller 169, 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 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 depth camera sensors 175.
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 module 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 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 800 (
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 800 (
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.
Diagram 600 includes home 602 and a set of devices (e.g., device 646, device 604, etc.). Home 602 includes multiple rooms, such as kitchen 602a, dining room 602b, bedroom 602c, living room 602d, and sunroom 602e. Kitchen 602a is in the upper left portion of home 602 and dining room 602b is between kitchen 602a and bedroom 602c, where bedroom 602c is to the right of dining room 602b. Kitchen 602a and dining room 602b do not have a wall between them while dining room 602b and bedroom 602c have a wall between them. Living room 602d is in the bottom left portion of home 602 and sunroom 602e is in the bottom right portion of home 602. In some embodiments, home 602 includes other rooms than those depicted in
As illustrated in
As illustrated in
As illustrated in
In this example, the speakers (e.g., dining room speaker 616, bedroom speaker 636, living room speaker 646, living room speaker 648, sunroom speaker 656, and sunroom speaker 658), lights (e.g., bedroom light 632 and living room lamp 642), and personal devices (e.g., John's phone 604, tablet 634, computer device 674, and Jane's phone 684) shown in
In addition, each individual speaker and light are also assigned to (e.g., mapped to a group that corresponds to) a room in which it is positioned. For example, dining room speaker 616 is assigned to (e.g., programmatically mapped to a group that corresponds to) dining room 602b; bedroom speaker 636 and bedroom light 632 are assigned to bedroom 602c; living room lamp 642, living room speaker 646, and living room speaker 648 are assigned to living room 602d; and sunroom speaker 656 and sunroom speaker 658 assigned to sunroom 602e. In some embodiments, each group that corresponds to each room is also assigned to home 602. Thus, devices that are mapped to a room of home 602 are also concurrently mapped to home 602.
An external device cannot be assigned to two different groups of devices that correspond to different rooms. For example, dining room speaker 616 cannot be assigned to kitchen 602a (e.g., a group corresponding to kitchen 602a) and dining room 602b at the same time. However, two groups of devices that are each assigned to respective rooms can be mapped to a (same) zone. In this example, entertainment zone 660 is assigned to living room 602d in
In this example, the personal devices (e.g., John's phone 604, tablet 634, and Jane's phone 684) are not programmatically mapped to a group that corresponds to a room and only are mapped to a group that corresponds to a home.
In some embodiments, the speakers, lights, and personal devices (e.g., John's phone 604, tablet 634, Jane's phone 684) shown in
While this description often refers to messages as multicast messages (or audio multicast messages), it should be recognized that such messages are optionally sent using (1) a multicast communication, (2) a broadcast communication, (3) a unicast communication, (4) or any combination thereof (e.g., (1) a first device (e.g., a controller) sends a unicast communication to a second device (e.g., a hub in a home) and (2) the second device sends either a multicast or a broadcast communication (e.g., including content from the unicast communication) to one or more third devices (e.g., one or more accessory devices within the home and/or one or more personal devices). In some embodiments, a multicast communication is a communication sent to multiple receipts. In some embodiments, a broadcast communication is a communication transmitted to devices on a channel or network. In some embodiments, a broadcast communication is a communication transmitted to all devices on a channel or network. In some embodiments, a unicast communication is a communication transmitted to a single recipient. In such embodiments, multiple unicast communications are sent when content needs to be sent to multiple devices.
In some embodiments, a broadcast communication is a communication transmitted to all devices on a channel or network. In such embodiments, multiple unicast communications are sent when content needs to be sent to multiple devices.
As illustrated in
As illustrated in
Home location identifier 712 is a name that corresponds to home 602. In this example, the location identifier is part of the address (e.g., “123 Main Street”) of home 602. In some embodiments, the location identifier is an alias, such as an alias assigned to the home. In some embodiments, the alias is a system-created alias. In some embodiments, the alias is a user-created alias. In some embodiments, the location identifier is set by a user of device 700 or an external device. In some embodiments, the location identifier is a graphical user interface object, such as an image.
Status information 714 includes information concerning the current status of some of the devices assigned to home 602. Here, status information 714 indicates that at least one light is on in the home 602. In some embodiments, status information 714 includes information concerning the status of multiple devices (e.g., “bedroom fan on”).
As illustrated in
Additionally, in
Each of external device controls 718, when selected, control at least one device assigned to home 602. For example, dining room speaker control 718a, when selected, causes dining room speaker 616 to play or pause music. In some embodiments, when dining room speaker control 718a is selected, the status information on dining room speaker control 718a changes to show that dining room speaker 616 has paused the playback of media (e.g., as shown by bedroom speaker control 718e) or stopped the playback of media. Some of external device controls 718 control multiple devices when selected. For example, sunroom speakers control 718d, when selected, causes sunroom speakers 656 and 658 to play or pause the playback of media and the status information displayed on sunroom speakers control 718d changes accordingly. Some of external device controls 718 are not speaker device controls. For example, external device controls 718 includes living room lamp control 718b that, when selected, causes living room lamp 642 to turn on/off and the status information displayed on living room lamp control 718b changes accordingly.
In some embodiments, external device controls 718 are selected from a group of other external controls that are also assigned to home 602. For example, the six controls that are shown in
At the bottom of user interface 710 are navigation controls 722. Navigation controls 722 include home navigation control 722a, room navigation control 722b, and automation navigation control 722c. Each of navigation controls 722, when selected, causes device 700 to display a different user interface for the home application.
As illustrated in
In response to detecting tap gesture 750b, device 700 initiates a process for sending an audio multicast message to one or more devices assigned to home 602. In some embodiments, the process includes displaying user interfaces depicted in
As illustrated in
As illustrated in
Additionally, at
As illustrated in
As illustrated in
As illustrated in
As an alternative to the flow described in
In some embodiments, audio is recorded using user interface 710 of
As illustrated in
In
Table 706 in
As illustrated in
In some embodiments, in response to detecting tap gesture 750f1 at a location that corresponds to living room lamp control 718b, device 700 will send instructions that causes living room lamp 642 to turn on (or off if current state was on). In some embodiments, in response to detecting tap gesture 750f2 at a location that corresponds to living room speaker control 718c, device 700 will send instructions that cause living room speakers 646 and 648 (or at least one of them) to initiate playback of media (e.g., or pause playback of media if current state was playing). At
As illustrated in
Notably, the user interfaces (e.g., user interfaces 710 and 760) in the home application are laid out in a hierarchy. For example, user interface 710 is the top node of the hierarchy and includes controls for a group of external devices that are assigned to home 602. And, while displaying user interface 710, input (e.g., a single input (e.g., tap gesture 750f)) can be detected that causes device 700 to display user interface 760, which is a lower node in the hierarchy and includes controls for a group of external devices that are assigned to a respective room in home 602 (e.g., living room 602d) (and not other rooms).
As illustrated in
When compared to external device controls 718 displayed in
Additionally, while external device controls 718 were designated as being a favorite set of controls for home 602 in
As illustrated in
In response to detecting tap gesture 750g3, device 700 initiates a process for sending an audio multicast message to one or more devices assigned to living room 602d. In some embodiments, the process includes displaying user interface 780a, as depicted in
As illustrated in
Turning to
Turning back to
As illustrated in
As illustrated in
In some embodiments, device 700 displays user interface 790 in response to detecting tap gesture 750j (or a tap gesture (e.g., similar to tap gesture 750c1) on a user interface that is similar to user interface 741 of FIG. 7C1 as described above), as illustrated in
In some embodiments, one or more of user interface 730, 740, 750, 780a, 780b, 784, 786, and 790 include an affordance to swap the intended target of the recorded audio multicast message (e.g., change the destination identifier). For example, after initiating a process for sending an audio multicast message to a first group of device (e.g., devices assigned to home 602) (such as while showing
In some embodiments, audio is recorded and sent from a user interface similar to user interface 741 of FIG. 7C1 that is displayed in response to detecting tap gesture 750g. In some embodiments, audio is recorded from user interface 760 in
As illustrated in Table 706 of
At
At
As shown by table 706 in
As illustrated in
As illustrated in
As illustrated in
As illustrated in
At
At
As shown by table 706 in
At
At
As shown by table 706 in
As illustrated in
At
At
As shown by table 706 in
As illustrated in
At
At
As shown by table 706 in
Further, as shown by table 706 in
At some time after displaying user interface 794 in
As illustrated in
As illustrated in
As described below, method 800 provides an intuitive way for sending an audio message, in accordance with some embodiments. The method reduces the cognitive burden on a user for sending an audio message, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to send audio messages faster and more efficiently conserves power and increases the time between battery charges.
The computer system displays (802), via the display generation component, a first user interface (e.g., 730) (e.g., a user interface for controlling a set of external devices). The first user interface includes (e.g., includes display): a first selectable user interface object (e.g., 726), where selection of the first selectable user interface object initiates a process (e.g., user interfaces 730, 740, and 750) for recording (e.g., at the computer system via a microphone) and sending a first audio message to a set of external devices (e.g., 706 in
The first user interface includes a first accessory control user interface object (e.g., one of 718) (e.g., a selectable user interface object) corresponding to a first external accessory device, where selection (e.g., 750f1, 750f2) of the first accessory control user interface object initiates a process to transmit an instruction (e.g., selection causes transmission of the instruction) to change a state of the first external accessory device (e.g., causes the door to lock or unlock, causes the light to turn on or off). In some embodiments, in response to receiving an input, the computer system initiates a process to transmit an instruction (e.g., selection causes transmission of the instruction) to change a state of the first external accessory device and the visual appearance of the first accessory control user interface object changes from a first visual appearance to a second visual appearance that is different from the first visual appearance (e.g., pressed to depressed state (or vice-versa), a first color to a second color, one or more difference characters (e.g., “on to “off” (or vice-versa))).
The computer system, while displaying the first user interface (e.g., and the first user interface), receives (804) an input (e.g., 750f3) (e.g., a single user input (e.g., a tap input on a selectable user interface object or icon that will navigate to the user interface for controlling the second set of one or more external device) or multiple user inputs that are received while the first selectable user interface object are displayed) that corresponds to a request to display a second user interface (e.g., 760) (e.g., a user interface for controlling the second set of one or more external devices (e.g., without controlling the first set of one or more external devices)). In some embodiments, the computer system receives the request to display the second user interface when the computer system receives selection of a selectable user interface object for displaying the second user interface.
In response to receiving the request to display the second user interface, the computer system displays (806) the second user interface (e.g., 760). The second user interface includes (e.g., includes displaying) a second selectable user interface object (812) (e.g., 776), where selection of the second selectable user interface object initiates a process (e.g., user interfaces 780a, 784, and 786a) for recording and sending a second audio message to the second set of one or more external devices (e.g., 646, 648) without sending the second audio message to the first set of one or more external devices (e.g., 706 in
In some embodiments, the first external accessory device (e.g., 718b) is different from the second external accessory device (e.g., 768c). In some embodiments, the first external accessory device is an external device that is grouped under the “Home” group, but is not part of the “Dining Room” category (e.g., a light located in a bedroom) and the second external accessory device is an external device that is grouped under both the “Home” group the “Dining Room” category (e.g., a light located in the dining room). In contrast, in some embodiments, the first external accessory device is the same device as the second external accessory device (e.g., they are the same light located in the dining room, or they are the same smart speaker located in the dining room).
In some embodiments, the first selectable user interface object (e.g., 726) (e.g., while displayed as part of the first user interface) is displayed at a first location (e.g., location of 726 and 776) via the display generation component (e.g., on the display generation component) and the second selectable user interface object (e.g. 776) (e.g., while displayed as part of the second user interface) is displayed at the first location (e.g., location of 726 and 776) via the display generation component (e.g., on the display generation component). In some embodiments, the input received while displaying the first user interface causes the second selectable user interface object to replace display of the first selectable user interface object. Providing the first selectable user interface or the second selectable user interface objects at the same location when prescribed conditions are met allows the user to quickly locate a selectable user interface object for multicasting without having to identify any different operational characteristics (e.g., what particular set of devices will selectable the particular selectable user interface object send a record audio message to) of the selectable user interface object. Providing improved visual feedback to the user enhances the operability of the computer system and makes the user-system 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 computer system by enabling the user to use the computer system more quickly and efficiently.
In some embodiments, the first external accessory device (e.g., 646, 648) (e.g., a smart speaker, wherein playback of music can be configured using the first accessory control user interface object) is included in the set of external devices (e.g., the first external accessory device can be configured from the first user interface and audio (recorded at the computer system) is sent to the first external accessory device using the first selectable user interface object). In some embodiments, the first user interface includes a third accessory control user interface object (e.g., 718b) (e.g., a selectable user interface object) corresponding to a third external accessory device (e.g., 642). In some embodiments, selection of the third accessory control user interface object initiates a process to transmit an instruction (e.g., selection causes transmission of the instruction) to change a state of the third external accessory device (e.g., causes the door to lock or unlock, causes the light to turn on or off). In some embodiments, the third external accessory device (e.g., 642) is not included in the set of external devices and selection of the first selectable user interface object (e.g., 776) does not initiate a process for sending (and/or recording) the first audio message to the third external accessory device (e.g., 706 in 7F). In some embodiments, the first user interface includes accessory control user interface objects for some external accessory devices that can be controlled (e.g., turned on/off), but that are not sent the first audio message (e.g., because the external accessory devices do not have a speaker for playback of the audio message) and the first user interface includes accessory control user interface objects for some external accessory devices that can be controlled (e.g., turned on/off) and that are sent the first audio message (e.g., because the external accessory devices have speakers for playback of the audio message). In some embodiments, the second user interface includes accessory control user interface objects for some external accessory devices that can be controlled (e.g., turned on/off), but that are not sent the second audio message (e.g., because the external accessory devices do not have a speaker for playback of the audio message) and the second user interface includes accessory control user interface objects for some external accessory devices that can be controlled (e.g., turned on/off) and that are sent the second audio message (e.g., because the external accessory devices have speakers for playback of the audio message). In some embodiments, the first set of one or more external devices (e.g., the device in the bedroom group to which the audio message is sent) does not include the first external accessory device (e.g., a light in the bedroom group to which the audio message is not sent) and the second set of external devices (e.g., the device in the dining room group to which the audio message is sent) does not include the second external accessory device (e.g., a light in the dining room group to which the audio message is not sent). Thus, in some embodiments, the audio message is not transmitted to all devices that can be controlled using the accessory control user interface objects which, when selected, cause a respective accessory device to perform one or more functions and/or change a state of the respective accessory device. In some embodiments, an external device that can be controlled (to perform one or more functions and/or change a state of the respective accessory device) using a respective accessory control user interface object is included in the set of external devices (e.g., the first or second set of external devices) and, thus, an audio message can be transmitted to that external device and that external device can be separately controlled.
In some embodiments, the first user interface corresponds to a top-level location (e.g., 602) (e.g., a structure, a home) and the second user interface corresponds to a first sub-location (e.g., 602d) of a first type (e.g., 602a-602e) (e.g., a room of the structure, a dining room in the home). In some embodiments, the second set of one or more external devices (e.g., 646, 648) correspond to the first sub-location (e.g., 602d) (e.g., the second set of one or more external devices have been assigned to the sub-location of the first type). In some embodiments, (e.g., any of) the second set of one or more external devices (e.g., 646, 648) cannot be made to correspond to a second sub-location (e.g., 602a, 602b, 602c, or 602e) (e.g., any sub-location (other than the first sub-location) of the first type (e.g., any other room of the structure) based on the second set of one or more external devices corresponding to the first sub-location (e.g., 602a-602e). In some embodiments, the first user interface corresponds to a top-level location and the second user interface corresponds to a sub-location (e.g., a room of the home) of the top-level location. In some embodiments, the first room and a second room are part of a zone (e.g., a collection of rooms grouped together). In some embodiments, the second set of one or more external devices are devices identified (e.g., by a user) of being located in the room to which the second user interface corresponds.
In some embodiments, the first user interface corresponds to a top-level location (e.g., a structure, a home) and the second user interface corresponds to a third sub-location of a second type (e.g., entertainment zone (e.g., 602d and 602e)) (e.g., a first zone, main floor) that corresponds to a plurality (e.g., 602a-602e) of sub-locations of a first type (e.g., 602a-602e) (e.g., a plurality of rooms). In some embodiments, the second set of one or more external devices corresponds to the third sub-location based on the second set of one or more external devices being included in the plurality of sub-locations of the first type (e.g., 602a-602e) (e.g., a plurality of rooms of the structure, including a first room (e.g., a dining room in the home) and a second room (e.g., a bedroom in the home)). In some embodiments, the first user interface corresponds to a top-level location and the second user interface corresponds to a sub-location (e.g., multiple rooms of the home) of the top-level location. In some embodiments, the second set of one or more external devices includes at least one device assigned to the first room and at least one device assigned to the second room. In some embodiments, the top-level location corresponds to at least one device to which the third sub-location does not correspond (e.g., the home includes some devices that are not included in the third sub-location).
In some embodiments, the second external accessory device is associated with (e.g., corresponds to) the third sub-location (e.g., entertainment zone (e.g., 602d and 602e)) (e.g., the first zone) of the second type. In some embodiments, the second external accessory device (e.g., 646, 648) is also associated with (e.g., corresponds to) a fourth sub-location (e.g., second zone) of the second type (e.g., entertainment zone (e.g., 602d and 602e)) that is different from the third sub-location. In some embodiments, the second zone is a sub-location (e.g., multiple rooms of the home). In some embodiments, the second zone is associated with an external accessory device that is not associated with the first zone. In some embodiments, the computer system can initiate processes for recording and sending messages to various zones. A first zone and a second zone can correspond to different sets of devices, some of which correspond to both the first zone and the second zone and some of which corresponds to only one of the first zone or the second zone.
In some embodiments, the second set of one or more external devices (e.g., 646, 648) is associated with a first location (e.g., 602d) (e.g., a room, a sub-location, a zone) and wherein the process for recording and sending the second audio message to the second set of one or more external devices without sending the second audio message to the first set of one or more external devices includes displaying an indication (e.g., textual indication, graphical indication) of the first location (e.g., 782) (e.g., text specifying the name of the room or zone that the audio message will be transmitted to). In some embodiments, processes for recording and sending audio messages include displaying an indication of the location that corresponds to the external devices to which the respective audio message will be sent. In some embodiments, the first user interface corresponds to a top-level location (e.g., a structure, such as a home) and the second user interface corresponds to a sub-location (e.g., a room of the home, a zone of the home) of the top-level location. In some embodiments, displaying the second user interface, the computer system detects selection of (e.g., tap on, press and hold on) the second selectable user interface object. In some embodiments, in response to detecting selection of the second selectable user interface object, the computer system displays a recording user interface (e.g., by replacing all or part of the second user interface) that concurrently includes: a record user interface object (e.g., a selectable record button), wherein selection of (e.g., tap on, press and hold on) the record user interface object causes recording of an audio message by recording audio detected by the computer system; and an indication (e.g., textual indication, graphical indication) of the sub-location (e.g., text specifying the name of the room or zone that the audio message will be transmitted to). In some embodiments, the second user interface includes the indication of the sub-location. Displaying an indication of a location that is associated with a group of devices to which an audio message is intended to be multicast provide the user with visual feedback concerning the state of the process for recording and sending the audio message. Providing improved visual feedback to the user enhances the operability of the computer system and makes the user-system 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 computer system by enabling the user to use the computer system more quickly and efficiently.
In some embodiments, as a part of initiating a process for recording and sending an audio message to external devices, the computer system initiates, automatically (e.g., without intervening user input that corresponds to a request to initiate recording of the audio), the recording of a new audio message and displays a recording user interface (e.g., 741) that includes a dynamic indication (e.g., 744a) of the audio being recording.
In some embodiments, the computer system detects selection of (e.g., tap on, press and hold on) the record user interface object. In response to detecting selection of the record user interface object, the computer system records an audio message. Subsequent to recording the audio message (and prior to transmitting the audio message), the computer system provides an option to change the external devices to which the message will be transmitted. In some embodiments, the computer system receives activation of a drop-down affordance and, in response, displays one or more sub-locations (each of which correspond to a respective set of external devices). The computer system receives selection of one of the one or more sub-locations and a confirmation to transmit the audio message. In response, the computer system transmits the audio message to the respective set of external devices corresponding to the selected sub-location, rather than to the second set of one or more external devices corresponding to the second user interface.
In some embodiments, the set of external devices includes a personal mobile electronic device (e.g., 604, 634, 684) (e.g., a smart phone, a cell phone, a watch). In some embodiments, the personal mobile electronic device is not included in the first set of or more devices and is not included in the second set of one or more external devices. In some embodiments, the personal mobile electronic device is not assigned to any sub-location of the top-level location, but is a member of the top-level location. Thus, in some embodiments, selecting the first selectable user interface object initiates a process to record and send an audio message to the set of external devices, including the personal mobile electronic device (and any other personal mobile electronic devices that are members of the top-level location).
In some embodiments, the second set of one or more external devices does not include a personal mobile electronic device (e.g., 604, 634, 684) (e.g., a smart phone, a cell phone, a watch). In some embodiments, the personal mobile electronic device is not included in the first set of or more devices and is not included in the second set of one or more devices. In some embodiments, the set of external devices includes the personal mobile electronic device and, therefore, audio messages sent from the first user interface are transmitted to the personal mobile electronic device (and, optionally, other mobile devices that are part of the home). In some embodiments, audio messages sent from the second user interface (or any user interface corresponding to a sub-location) are not transmitted to the personal mobile electronic device (and, optionally, are also not transmitted to other mobile devices that are part of the home). In some embodiments, the computer system disallows assigning personal mobile electronic devices to any sub-location of the top-level location, but permits assigning personal mobile electronic devices to the top-level location. Thus, in some embodiments, selecting the second selectable user interface object initiates a process to record and send an audio message to the second set of one or more devices, which does not include the personal mobile electronic device (or any other personal mobile electronic devices that are members of the top-level location).
In some embodiments, the computer system, subsequent to displaying the second user interface, receives input (e.g., 750q) (e.g., user input; an input on a settings user interface) to disable sending audio messages to the second set of one or more external devices (e.g., 638). In some embodiments, in response to receiving the input to disable sending audio messages to the second set of one or more external devices, the computer system disables (e.g., 768a) sending of audio messages to the second set of one or more external devices via selection of the first selectable user interface object (e.g., 726) (e.g., without disabling sending of audio messages to the first set of one or more external devices via selection of the first selectable user interface object) and via selection of the second selectable user interface object (e.g., 776). In some embodiments, after disabling sending of audio messages to the second set of one or more external devices, navigating back to the first user interface and receiving selection of the first selectable user interface object initiates a process for recording and sending an audio message to the first set of one or more external devices without sending the audio message to the second set of one or more external devices. In some embodiments, in response to receiving the input to disable sending audio messages to the second set of one or more external devices, the computer system removes the second set of one or more external devices from the set of external devices. In some embodiments, after disabling sending of audio messages to the second set of one or more external devices, navigating back to the second user interface and receiving selection of the second selectable user interface object does not initiate a process for recording and sending an audio message to any devices. In some embodiments, after disabling sending of audio messages to the second set of one or more external devices, the second user interface does not include the second selectable user interface object (or includes a non-selectable/disabled version of the user interface object) such that the process for recording and sending an audio message to the second set of one or more external devices cannot be initiated.
In some embodiments, the first user interface corresponds to a top-level location (e.g., 602) (e.g., a structure, such as a home) and the second user interface corresponds to a sub-location (e.g., 602a-602d) (e.g., a room of the home, a zone of the home) of the top-level location (e.g., 602). In some embodiments, the computer system receives (808) (e.g., while not displaying the first user interface and not displaying the second user interface), at a microphone that is in communication with the computer system (e.g., a microphone of the computer system), audio input (e.g., 792a-792e) including a natural language request for a digital assistance, the audio input including: an instruction to initiate a process to transmit an audio message (e.g., including the term “multicast”), a location identifier (e.g., the top-level location, a sub-location), and an audio message (e.g., received subsequent to the instruction to initiate a process to transmit an audio message and/or received subsequent to the identifier of the location). In some embodiments, in accordance with a determination that the location identifier corresponds to the top-level location (e.g., 782a), the computer system transmits (810) (e.g., multicasting) the audio message, without establishing a two-way audio communication channel (e.g., without establishing a full-duplex audio communication channel) with any devices of the set of external devices, for playback at the set of external devices, including the first set of one or more external devices and the second set of one or more external devices. In some embodiments, in accordance with a determination that the location identifier corresponds to the sub-location (e.g., 792b, 792c): the computer system transmits (812) (e.g., multicasting) the audio message, without establishing a two-way audio communication channel with any devices of the set of external devices, for playback at the second set of one or more external devices and not for playback at the first set of one or more external devices. In some embodiments, the computer system transmits the location identifier along with the audio message such that a remote device (e.g., a service, an external device of the set of external devices) can distribute the audio message to the external devices corresponding to the respective external devices.
In some embodiments, as a part of initiating a process for recording and sending an audio message to external devices includes, the computer displays a recording user interface (e.g., 730, 740, 750) (e.g., by replacing all or part of the second user interface) that concurrently includes: a record user interface object (e.g., 736) (e.g., a selectable record button), wherein selection (e.g., 750c) of (e.g., tap on and then press end when audio message is complete, press and hold on while speaking audio message, tap on and allow the computer system to identify the end of the audio message) the record user interface object causes recording of an audio message by recording audio detected by the computer system; and a send user interface object (e.g., 756) (e.g., a selectable send button), wherein selection (e.g., 750e) of (e.g., tap on) the second user interface object causes the computer system to send the audio message to the external devices. In some embodiments, the recording user interface also concurrently includes an indication (e.g., textual indication, graphical indication) of the location (e.g., top-level location, sub-location; text specifying the name of the room or zone that the audio message will be transmitted to) corresponding to the external devices to which the audio message will be sent.
In some embodiments, the computer system is in communication with one or more input devices including a microphone. In some embodiments, as a part of the process (e.g., user interfaces 730, 740, 750) for recording and sending the first audio message to the set of external devices, the computer system receives, via the microphone, a second audio input. In some embodiments, the computer system transmits the first audio message to the set of external devices, wherein the first audio message is based on (e.g., includes a recording of) the second audio input.
Note that details of the processes described above with respect to method 800 (e.g.,
The phrases “multicast message” and/or “audio multicast message” are used generally herein with respect to
As illustrated in
For example, in
As illustrated in
At 10:02 AM, device 700 receives data indicating that a new audio multicast message has been sent (e.g., directed to devices that include electronic device 700) to home 602 (“home target group”). In some embodiments, the data includes a target group identifier (e.g., “Home”) as the receiver for the new audio multicast message.
As illustrated in
Application indication 904a indicates an application that is providing the notification. Here, application indication 904a includes a graphical representation icon that is assigned to a home application and is similar to home icon 704a in
Notification type indication 904b indicates the notification type of the notification. Here, the notification type is a multicast notification.
Sender indication 904c indicates the sender of the audio multicast message. Here, the sender is a person, John, who is registered with the device (e.g., a device that is in the home target group) that has initiated the process for sending the audio multicast message. In some embodiments, when the sender is a person, an identity of the sender is established by one or more devices analyzing voice input corresponding to the audio multicast messages, using one or more voice identification algorithms. In some embodiments, when the identity of the sender cannot be established as a person, sender indication 904c indicates that the sender is a device (e.g., “Living Speaker”), such as the device that sent the audio multicast message. In some embodiments, the sender is not established as a person, for example, a person is not established at the sender device when a person is not registered with the sender device that initiated the process for sending the audio multicast message and/or multiple people are registered with the device that initiated the process for sending the audio multicast message.
Target indication 904d indicates a target group of devices to which an audio multicast message corresponds. Here, target indication 904d is the home target group (e.g., “From Home”). In some embodiments, the target group (that corresponds to the audio multicast message) is the group identified by the sender of the audio multicast message, as described above in relation to
Time of receipt indication 904e indicates when the notification was displayed (or, in some embodiments, when data that corresponds to the notification was received). Here, time of receipt indication 904e shows that the notification was displayed “NOW” or at 10:02 AM.
As illustrated in
As illustrated in
At 10:10, device 700 receives three different sets of data. The first set of data indicates that a new audio multicast message corresponding to the home target group has been received. The second set of data indicates that a new audio multicast message corresponding to a group of devices assigned to bedroom 602c (“bedroom target group”) has been received. The third set of data indicates that a new audio multicast message corresponding to a group of devices assigned to the entertainment zone (“the entertainment zone target group”) (e.g., a combination of a group of devices assigned to living room 602d and sunroom 602e) has been received.
In some embodiments, the first set of data represents an initial audio multicast message or a reply audio multicast message (e.g., a reply to an initial audio multicast message that device 700 sent) corresponding to the home target group. In some embodiments, the second set of data and the third set of data represent reply audio multicast messages, that is, audio multicast messages that are received in response to initial audio multicast messages that were separately sent to each respective target group. In some embodiments, the second set of data and the third set of data are not initial messages that are received from their respective target group because device 700 is not assigned to zone or room target groups and cannot receive initial messages sent from those target groups, as discussed above (e.g., in relation to
As illustrated in
As illustrated in
At 10:11 AM, device 700 receives data indicating that a new audio multicast message corresponding to the home target group has been received.
As illustrated in
Multicast notification 906b is an updated version of multicast notification 906a, which device 700 has ceased to display in
As illustrated in
As illustrated in
At 10:12 AM, device 700 receives data indicating that a new audio multicast message corresponding to the bedroom target group has been received.
As illustrated in
Multicast notification 908b is an updated version of multicast notification 908a, which device 700 has ceased to display in
As illustrated in
As illustrated in
As illustrated in
As illustrated in
As illustrated in
As illustrated in
In
As illustrated in
As illustrated in
As illustrated in
As illustrated in
As described below, method 1000 provides an intuitive way for displaying notifications. The method reduces the cognitive burden on a user for view notifications, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to access notifications faster and more efficiently conserves power and increases the time between battery charges.
The computer system receives (1002) first data corresponding to first media.
The computer system displays (1004) (e.g., in response to receiving the first data), via the display generation component, until an end of a first time period (e.g., a predetermined first time period), a first notification (e.g., 906a, 908a, 910) with an indication of the first media (e.g., 904b, 904c) (e.g., a notification corresponding to the first data) (e.g., a notification selectable to initiate a process to play the first media).
The computer system, after receiving the first data (e.g., after the start of display of the first notification), receives (1006) second data corresponding to second media, wherein the second media (e.g., 932 in 9J) is different from the first media (e.g., 932 in 9K).
The computer system, in accordance with a determination that the second media meets a set of one or more criteria (and, in some embodiments, the one or more criteria includes a criterion that is met when the second media is directed to the same target group as the first media) and in accordance with a determination based on (1) a time that the second data was received and (2) a time that the first data was received (e.g., a determination that the second data was received within a predefined amount of time after the first data was received), displays (1008) (e.g., in response to receiving the second data), via the display generation component, until an end of a second time period. In some embodiments, the second time period is based on receipt of the second data. In some embodiments, the second time period is not based on receipt of the first data. In some embodiments, the second time period is a predetermined second time period), a second notification (e.g., 906b, 908b, 908c) with an indication (e.g., indication in 906b (e.g., “John”), 908b (e.g., “2”)) of the first media (e.g., 932 in 9K) (e.g., a notification corresponding to at least the first data) (e.g., a notification selectable to initiate a process to play at least the first media) (e.g., a notification indicating receipt of at least the first data), where an end of the first time period is different from an end of the second time period. In some embodiments, the second notification is the first notification. In some embodiments, the second notification is different from the first notification (e.g., the second notification is a notification combining (1) information corresponding to the first media and (2) information corresponding to the second media). In some embodiments, the second notification is displayed (e.g., initially displayed) after the first time period. In some embodiments, when receipt of the second media is within a predetermined time of receipt of the first media, a length of time is extended for which information corresponding to the first media is displayed. In some embodiments, the second time period is determined based on a difference between the when the first data was received and when the second data was received. In some embodiments, the media (e.g., first media, second media) is an audio message that was recorded at another device and transmitted to a group of devices, including the computer system receiving the first data and the second data. In some embodiments, the set of one or more criteria includes a criterion that is met when the second media is received prior to an end of a display period (e.g., a duration during which the notification is valid, a duration during which the notification will be displayed in a collection of notifications) of the first media. In some embodiments, the set of one or more criteria includes a criterion that is met when the second media is received prior ceasing to display the first notification (e.g., via activation of the first notification, via receiving user input clearing the first notification). Dynamically displaying a second notification that includes an indication that is included in a first notification that was related to the second notification when certain criteria are met provides the user with feedback about the relationship between the second notification and the first notification while also allowing the indication that is included in the first notification to continue to be displayed even if the first notification has ceased to displayed. Providing improved visual feedback to the user enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.
In some embodiments, the first notification (e.g., 906a) is being displayed at the time the second data is received (e.g., in accordance with the determination that the second media meets the set of one or more criteria). In some embodiments, as a part of displaying the second notification (e.g., 906b), the computer system ceases to display the first notification (e.g., in
In some embodiments, the first media is a first audio message (e.g., 932 in 9K) (e.g., an audio message recorded (using a microphone) at an external device and transmitted by the external device to a group of devices, an audio message that was directed to (e.g., transmitted to) a plurality of external devices that includes the computer system). In some embodiments, the second audio message is a second audio message that was directed (or transmitted) to a second plurality of external devices (e.g., same as the plurality of external devices, different from the plurality of external devices). Displaying a notification that is associated with audio messages that have been multicast provides the user with visual feedback concerning the type of notification, which cause the user to identify that the notification will decay and needs to be responded to in a predetermined period of time. Providing improved visual feedback to the user enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.
In some embodiments, the first notification (e.g., 904) includes an indication (e.g., 904d) of a group of a plurality of external devices to which the first media (e.g., 932 in 9K) was directed (e.g., to which the first data corresponding to the media was transmitted). In some embodiments, the first data identifies the group of the plurality of external devices to which the first media was directed. In some embodiments, the plurality of external devices includes the computer system. Displaying a notification that includes an indication of the group of devices in which the first media is directed provides the user with feedback about the devices that sent and/or will receive a replay message. Providing improved visual feedback to the user enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.
In some embodiments, in response to receiving the first data, the computer system adds the first notification (e.g., 906a) to a collection of notifications (e.g., notifications displayed in
In some embodiments, the first data identifies a target group of a plurality of external devices to which the first media was directed (e.g., transmitted to). In some embodiments, while displaying a notification (e.g., 906a, 908a, 910) (e.g., the first notification) corresponding to the first media (e.g., and which, when the notification is activated, initiates a process for playing the first media (e.g., first audio message)), the computer system receives (1010) third data corresponding to third media. In some embodiments, in response to (1012) receiving the third data corresponding to the third media and in accordance with a determination that the third media meets the set of one or more criteria (wherein, in some embodiments, the one or more criteria includes a criterion that is met when the media is directed to the same target group of devices as the first media), the computer system extends (1014) the duration during which the notification (e.g., the first notification, the second notification) corresponding to the first media (e.g., and which, when the notification is activated, initiates a process for playing the first media (e.g., first audio message)) is displayed (e.g., 906b in
In some embodiments, in accordance with the determination that the second media meets the set of one or more criteria, the second notification (e.g., that meets the set of one or more criteria) includes an indicator (e.g., a number) that is based on (e.g., that indicates) a number (e.g., in 908a and 908b) of media, including the first media, (e.g., the number of audio messages) represented by the second notification. In some embodiments, each subsequent notification after the first notification in a chain of notifications includes an indication of the number of media (e.g., number of audio messages) represented by the notification being displayed. For example, if a notification is the 5th notification in the chain, the notification indicates that the notification corresponds to 5 received media (e.g., 5 audio messages). In some embodiments, in accordance with a determination that the second media does not meet the set of one or more criteria, the second notification (e.g., that meets the set of one or more criteria) does not include an indicator (e.g., a number) that is based on (e.g., that indicates) a number of media, including the first media, (e.g., the number of audio messages) represented by the second notification. Updating an indication of the number of media items (audio multicast message (e.g., an audio message that is multicast to one or more devices)) that has been received from a target group of devices provides the user with feedback about the current state the number of media items that have been received for the respected target group of devices. Providing improved visual feedback to the user enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.
In some embodiments, the second notification includes the indication of the first media. In some embodiments, while displaying the second notification (e.g., 602b), the computer system receives input (e.g., 950h) directed to the second notification. In some embodiments, in response to receiving the input directed to the second notification (e.g., and in accordance with a determination that the second media meets the set of one or more criteria), the computer system initiates a process (e.g., 920, 922 in
In some embodiments, the second media meets the set of one or more criteria (e.g., the second media is directed to the same external devices as the first media). In some embodiments, while displaying the second notification (e.g., 908c), the computer system receives input (e.g., 950l) directed to the second notification. In some embodiments, in response to receiving the input directed to the second notification (e.g., and in accordance with a determination that the second media meets the set of one or more criteria), the computer system displays a user interface (e.g., 960) for playing back the first media (e.g., as part of initiating a process for playing back the first media and the second media), wherein the user interface for playing back the first media includes a record user interface object (e.g., a selectable record button). In some embodiments, selection (e.g., 950p) of the record (e.g., 736) user interface object causes, in accordance with a determination that the first data identifies a first group (e.g., bedroom devices) of a plurality of external devices to which the first media was directed (e.g., transmitted), the computer system to initiate a process (e.g., 730, 740, 750) for transmitting an audio message to the first group of plurality of external devices (e.g., and not the second group). In some embodiments, selection (e.g., 950p) of the record (e.g., 736) user interface object causes, in accordance with a determination that the first data identifies a second group (e.g., home devices) of a plurality of external devices to which the first media was directed (e.g., transmitted), different from the first group, the computer system to initiate a process (e.g., 780a, 784, 786a) for transmitting an audio message to the second group of plurality of external devices (e.g., and not the first group). In some embodiments, the computer system detects selection of (e.g., tap on, press and hold on) the record user interface object, and in response to detecting selection of the record user interface object initiates the corresponding operation, as noted above. In some embodiments, the set of external devices is associated with a top-level location (or destination) (e.g., a location of a first type) (e.g., a home location, business, an office (e.g., a location that is a top-level location (e.g., a location that defines one or more locations (e.g., sub-locations) and/or one or more regions (or zones) that are within an area and/or perimeter that is defined by the location of the top-level location, a location that is at the top level of a hierarchy of locations, a location that is linked (e.g., programmatically) to one or more locations (e.g., sub-locations) and/or one or more regions (or zones)))). In some embodiments, initiating a process for transmitting an audio message includes recording an audio message by recording audio detected by the computer system. In some embodiments, the user interface for playing back the first media includes an indication (e.g., textual indication, graphical indication) of the group (e.g., a top-level location, sub-location) (e.g., text specifying the name of the room or zone that the audio message will be transmitted to).
In some embodiments, while displaying a user interface (e.g., 960) for playing back the first media (e.g., as part of initiating a process for playing back the first media and the second media), the computer system receives user input (e.g., 950i, 950m2, 950n) (e.g., via one or more input devices, using a touch-sensitive surface). In some embodiments, in response to receiving the user input and in accordance with a determination that the user input (e.g., 950i) is directed to selection of a play user interface object (e.g., a tap on a play button displayed as part of the user interface for playing back the first media), the computer system plays back the first media (and, optionally, automatically subsequently playing back the second media and switching to the user interface for playing back the second media). In some embodiments, in response to receiving the user input and in accordance with a determination that the user input is a swipe gesture (e.g., 950m2, 950n) directed to the user interface for playing back the first media (e.g., a left swipe gesture on the user interface for playing back the first media), the computer system replaces display of the user interface for playing back the first media with display of a user interface for playing back the second media (e.g., which includes a play button for playing the second media without playing the first media). In some embodiments, in response to receiving the user input and in accordance with a determination that the user input (e.g., 950i) is directed to selection of a play user interface object (e.g., a tap on a play button displayed as part of the user interface for playing back the first media), the computer system plays back the second media (e.g., the most recently received media corresponding to the notification) and subsequently plays back the first media.
In some embodiments, while displaying a user interface (e.g., 720 of
In some embodiments, the computer system displays a user interface for configuring whether to include the computer system in a group of plurality of external devices that receive data corresponding to media (e.g., device that receive audio messages directed to external devices of the home) directed to a location (e.g., a top-level location (a home), a sub-location (a room of the home), wherein the user interface for configuring whether to include the computer system in a group includes: a first option (e.g., 799c) to (e.g., always) include the computer system in the group of plurality of external devices that receive data corresponding to media (e.g., device that receive audio messages directed to external devices of the home) directed to the location, regardless of a current physical location of the computer system (e.g., as determined by a location sensor of the computer system); and a second option (e.g., 799a) to (e.g., never) not include the computer system in the group of plurality of external devices that receive data corresponding to media (e.g., device that receive audio messages directed to external devices of the home) directed to the location, regardless of the current physical location of the computer system (e.g., as determined by a location sensor of the computer system). In some embodiments, the user can configure the computer system to register/unregister to receive data corresponding to the media or to enabled/disable display of notifications based on received data corresponding to the media.
In some embodiments, the computer system displays a user interface for configuring whether to include the computer system in a group of plurality of external devices that receive data corresponding to media (e.g., device that receive audio messages directed to external devices of the home) directed to a location (e.g., a top-level location (a home), a sub-location (a room of the home), wherein the user interface for configuring whether to include the computer system in a group includes a third option (e.g., 77b) to include the computer system (e.g., 700) in the group of plurality of external devices that receive data corresponding to media (e.g., device that receive audio messages directed to external devices of the home) directed to the location when the computer system (e.g., 700) is currently at a physical location (e.g., within a geo-fenced perimeter of the home, within a particular room of the home, as determined by a location sensor of the computer system) corresponding to the location and not include the computer system (e.g., 700) in the group of plurality of external devices that receive data corresponding to media (e.g., device that receive audio messages directed to external devices of the home) directed to the location when the computer system (e.g., 700) is not currently at the physical location (e.g., within a geo-fenced perimeter of the home, within a particular room of the home, as determined by a location sensor of the computer system) corresponding to the location. In some embodiments, the user can provide input to configure the computer system to only receive data corresponding to media (and/or to only display notifications) directed to a group of devices of a location when the computer system is at that location (e.g., only get messages directed to the home when the computer system is in the home, only get messages directed to a room when the computer system is in that room).
Note that details of the processes described above with respect to method 1000 (e.g.,
As illustrated in
At
As illustrated in
At
As illustrated in
At
As illustrated in
Notably, when compared to
At
As illustrated in
At
As illustrated in
At
As illustrated in
As illustrated in
As illustrated in
As illustrated in
As illustrated in
At
As illustrated in
As illustrated in
At
At
At
In
As illustrated in
As illustrated in
As illustrated in
As described below, method 1200 provides an intuitive way for displaying visual indications. The method reduces the cognitive burden on a user for determining a type of command given to a device, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to recognize the type of command faster and more efficiently conserves power and increases the time between battery charges.
The electronic device receives (1202) voice input (e.g., 1150a-1150r) via the one or more microphones.
The electronic device displays (1204) a visual indication (e.g., lights displayed via 1102) of the voice input, where: in accordance with a determination that a portion of the voice input (e.g., 1150b-1150f, 1150r) corresponds to voice input that is to be transmitted to one or more devices (e.g., and/or transmitted (e.g., multicast) to a plurality of devices) (e.g., and, in some embodiments, another portion (e.g., a portion of the voice input that is not transmitted) of the voice input corresponds to a first type of command (e.g., command that initiates a process for transmitting at least some of the voice input to a plurality of external devices (e.g., personal device (e.g., cellular phone), external accessory devices (e.g., smart home accessory device (e.g., a smart (e.g., intelligent) light bulbs, thermostat, door lock, door opener (e.g., garage door opener), speaker, television, electric outlet, power strip, camera, appliance (e.g., a refrigerator, stove))))), displays (1206), via the one or more display devices, the visual indication (e.g., 1102 in 11B-11F, 11K) includes displaying the visual indication with a first set of one or more colors; and in accordance with a determination that the voice input (e.g., 1150m-1150o, 1150r) does not include an instruction to transmit (e.g., an instruction to multicast) any portion of the voice input to other devices (e.g., to output a part of the voice input, such as by speakers of the other devices (e.g. a plurality of other devices)) (e.g., another portion of the voice input is a second type of command), displays (1210), via the one or more display devices, the visual indication (e.g., 1102 in
In some embodiments, voice input (e.g., 1150m-1150o) requesting for the electronic device to retrieve information (e.g., retrieve information, such as the weather, answers to one or more queries) or change one or more states (e.g., change one or more of an audio state (e.g., answering/placing a phone call, adjusting a volume), a state of media playback (e.g., pausing, playing, fast-forwarding, rewinding, skipping, shuffling media), an on/off state) of the electronic device is the voice input that does not include an instruction to transmit any portion of the voice input to other devices.
In some embodiments, the voice input that corresponds (e.g., 1150b-1150f, 1150k) to voice input that is to be transmitted to the one or more devices includes (1208) an identifier (e.g., a location, a sub-location, a location that corresponds to a group (“home”) or category (e.g., “dining room,” “living room,” “sunroom” within the group) for a group of devices. In some embodiments, the voice input includes the identifier for the group of devices and an audio message that will be transmitted to the group of devices. In some embodiments, the voice input (e.g., 1150m-1150o, 1150r) that does not include an instruction to transmit any portion of the voice input to other devices does not include (1212) the identifier for the group of devices. In some embodiments, the voice input does not include an identifier for a group of devices and an audio message is not transmitted to the group of devices.
In some embodiments, the first set of one or more colors (e.g., 1102 in
In some embodiments, as a part of displaying the visual indication (e.g., 1102 in
In some embodiments, as a part of displaying the animation (e.g., 1102 in
In some embodiments, the electronic receives data corresponding to a plurality of audio messages for playback. In some embodiments, the data corresponding to the plurality of audio messages for playback includes an identifier (e.g., a location that corresponds to a group (“home”) or category (e.g., “dining room,” “living room,” “sunroom” within the group) for a group of devices. In some embodiments, the plurality of audio messages are for a plurality of identifiers, where each identifier corresponds to a different group or category. In some embodiments, in response to receiving the data corresponding to the plurality of audio message for playback, the electronic device outputs an introductory tone (e.g., 1154i) (e.g., a dinging or ringing sound, the introductory tone or chime for all audio messages) before (e.g., and before outputting an identifier for the group of devices) outputting each respective audio message of the plurality of audio messages. In some embodiments, the identifier is output before a group of audio messages that corresponds to the identifier (e.g., that identifies a target group of devices) are output. Outputting same introductory tone before outputting different audio messages that have been multicast alerts recipients that the audio message is a multicast type of audio message. Providing improved audio feedback 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 electronic device receives data corresponding to an audio message (e.g., an audio multicast message) for playback. In some embodiments, the data corresponding to the audio message for playback includes an identifier (e.g., a location that corresponds to a group (“home”) or category (e.g., “dining room,” “living room,” “sunroom” within the group) associated with a group of devices. In some embodiments, in response to receiving the data, the electronic device, automatically, without user input, outputs (e.g., 1154j) (e.g., via a speaker of the electronic device) the audio message. In some embodiments, outputting the audio message includes outputting an identifier (e.g., a location that corresponds to a group (“home”) or category (e.g., “dining room,” “living room,” “sunroom” within the group) for a group of devices.
In some embodiments, before outputting the audio message, displaying a second visual indication (e.g., 1102 in 11I) in response to receiving the data. In some embodiments, the second visual indication has a first visual appearance (e.g., color, size, brightness) when the audio message is an audio message transmitted to multiple devices (e.g., a group of devices). In some embodiments, the second visual indication has a second visual appearance that is different from the first visual appearance when the audio message is an audio message transmitted to the electronic device and not to other devices.
In some embodiments, the electron device receives data corresponding to an audio message (e.g., an audio multicast message) for playback. In some embodiments, the data corresponding to the audio message for playback includes an identifier (e.g., a location that corresponds to a group (“home”) or category (e.g., “dining room,” “living room,” “sunroom” within the group) associated with a group of devices. In some embodiments, outputs the audio message (e.g., automatically, in response to a user request). In some embodiments, while outputting the audio message, the electronic device concurrently displays a visual indication (e.g., 1102 in
In some embodiments, the audio message is output (e.g., 1154j) based on the volume level (e.g., a system-level audio level) (e.g., a current volume level) of the electronic device. In some embodiments, the electronic device is not displaying visual content (e.g., 1102 in
In some embodiments, the electronic device ceases (1214) to display the visual indication (e.g., 1102 in
In some embodiments, the visual indication (e.g., 1102 in
In some embodiments, the visual indication (e.g., 1102 in
Note that details of the processes described above with respect to method 1200 (e.g.,
User interface 710 also includes status indicators 1314. Each of the status indicators includes information concerning the current status of some of the devices currently assigned to home 602 (e.g., some of which have been described above in relation to
Each status indicator contains a name (e.g., “carbon monoxide) associated with the status indicator (e.g., carbon monoxide status indicator 1314a) and can be displayed with at least one particular visual characteristic (e.g., a color (e.g., red, greyed-out, etc.), a pattern, a shape, etc.). In some embodiments, one or more of the status indicators include a representation of a number of devices of a certain type (e.g., carbon monoxide detector or sensor) that are in the state (e.g., active, alerting, or needing attention) that is represented by the status indicators. Each status indicator may also include a quick visual representation of the status indicator's state.
In
In some embodiments, when a determination is made that a new status indicator will need to be displayed, device 700 will display the new status indicator after (or before or among) the status indicators in the same status indicator category as the new status indicator. For example, when a determination is made that a new status indicator should be displayed and the new status indicator is in the second status indicator category, device 700 displays the new status indicator between update available status indicator 1314d and timer status indicator 1314e (e.g., instead of appending the new status indicator at the beginning and/or end of all of the displayed status indicators 1314). Thus, the new status indicator is displayed on device 700 at a position that is relevant to the urgency of the status indicator to allow the user to identify and/or interact with the new status indicator based on the new status indicator's relevant urgency as compared to the relevant urgency of the other displayed status indicators. At
At
As illustrated in
In
At
At
A status indicator in the fourth status indicator category indicates that a number of external devices of a certain type are in a certain state. For example, as illustrated in
At
As illustrated in
Notably, as illustrated in
At
As illustrated in
At
At
As illustrated in
As illustrated in
As illustrated in
As illustrated in
Notably, at
As described below, method 1400 provides an intuitive way for managing external devices. The method reduces the cognitive burden on a user for managing external devices, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to recognize device status faster and more efficiently conserves power and increases the time between battery charges.
The computer system displays (e.g., 1402), via the display generation component, a first status indicator (e.g., 1314g, 1314h, 1314i) (e.g., as a part of displaying a first user interface (e.g., a user interface for controlling a set of accessory devices) that includes (e.g., includes displaying)) that indicates (e.g., a graphical representation and corresponding text (e.g., 2 light bulbs are on)) that a plurality of accessory devices of a first accessory type (e.g., light bulbs, windows, switches, outlets, locks (e.g., door locks, window locks), televisions) are in a first state (e.g., on, off, open, closed, locked, unlocked). The plurality of accessory devices of the first accessory type includes a first accessory device (1404) that is the first accessory type and is in the first state and a second accessory device (1406) that is the first accessory type and is in the first state, where the second accessory device is different from the first accessory device. In some embodiments, the first status indicator does not indicate that an accessory device of the first accessory type that is not in the first state (e.g., in a second state) (e.g., the first status indicator does not indicate or control (e.g., when selected) one or more devices of the first accessory type that are not in the first state (e.g., in the second state)). In some embodiments, the first status indicator does not indicate an accessory device of an accessory type that is not the first accessory type, irrespective of the current state of the accessory device of the accessory type that is not the first accessory type.
The computer system, while displaying the first status indicator, the computer system detects (1408) a gesture (e.g., 1350a-1350c, 1350f) (e.g., via one or more input devices).
In response to (1410) detecting the gesture and in accordance with a determination that the gesture is a first type of gesture (e.g., 1350f) (e.g., a tap gesture) and is directed to (e.g., on, at a location corresponding to) the first status indicator (e.g., 1350h), the computer system causes (1412) (e.g., via initiating a process (and, in some embodiments, the process includes transmitting one or more instructions to one or more devices (e.g., a server, a hub device that is in communication with a plurality of devices that includes the first accessory device and the second accessory device, first accessory device, second accessory device))) the first accessory device (e.g., to perform an action that changes the state of first accessory device) and the second accessory device (e.g., to perform an action that changes the state of the second accessory device) to change to a second state that is different (e.g., an opposite of (e.g., on/off, locked/unlocked, open/closed)) from the first state. In some embodiments, as a part of causing the first accessory device and the second accessory device to be in the second state, the computer system does not cause one or more accessory devices that are in the second state (or any state that is different from the first state) (e.g., before the gesture was detected) to perform any actions and/or to change state.
In response to (1410) detecting the gesture and in accordance with a determination that the gesture is a second type of gesture (e.g., 1350c) (e.g., a long press gesture) that is different from the first type of gesture and is directed to the first status indicator (e.g., 1314h), the computer system displays (1414), via the display generation component, a first accessory control user interface object (e.g., 718b, 718f-718j) (e.g., as a part of displaying a second user interface) corresponding to the first accessory device, where selection (e.g., 1350d) (e.g., via a gesture that is the first type of gesture (e.g., a tap gesture)) of the first accessory control user interface object causes (e.g., via initiating a process (and, in some embodiments, the process includes transmitting an instruction to one or more devices (e.g., a server, a hub device that is in communication with a plurality of accessory devices (e.g., that includes the first and second accessory devices)), first accessory device (not the second accessory device)) the first accessory device (e.g., to perform the action that changes a state of the first accessory device) to change to the second state without causing the second accessory device to change to the second state (e.g., the second accessory device continues to be in the first state after causing the first accessory device to be in the first state is completed). In some embodiments, while displaying the first accessory control user interface object corresponding to the first accessory device, the computer system detects a gesture (e.g., a gesture of the first type directed to the first accessory control user interface object) directed to the first accessory control user interface object; and, in response to detecting the gesture directed to the first accessory control user interface object, the computer system causes the first accessory device (e.g., to perform the action that changes the first accessory device) to be in the second state without causing the second accessory device to be in the second state (e.g., the second accessory device continues to be in the first state after the causing the first accessory device to be in the first state is completed). In some embodiments, in response to detecting the gesture directed to the first status indicator and in accordance with the determination that the gesture is the second gesture (e.g., a long press gesture) that is different from the first gesture, the computer system displays, via the display generation component, a third accessory control user interface object corresponding to a third accessory device, where the third accessory device is the first accessory device type and is not in the first state (e.g., is in the second state); and in response to detecting a gesture directed to the third accessory control user interface object, the computer system causes the third accessory device to be in the first state (e.g., to perform the action that changes the third accessory device) without changing the state of the first accessory device and the second accessory device (e.g., without causing the first accessory device and the second accessory device to be in the second state). In some embodiments, the second user interface does not include an (e.g., or any) accessory control user interface object corresponding to an accessory device that is not of the first type (e.g., of a second accessory type that is different from the first accessory type). In some embodiments, in response to detecting the gesture directed to the first status indicator and in accordance with the determination that the gesture is the second gesture (e.g., a long press gesture) that is different from the first gesture, the computer system does not display accessory control user interface objects that are of an accessory type that is different from the first accessory type are displayed via the second user interface). In some embodiments, in response to detecting the gesture directed to the first status indicator and in accordance with the determination that the gesture is the second gesture (e.g., a long press gesture) that is different from the first gesture, the computer system ceases to display the first status indicator. Performing different operations, when a gesture is directed to the first status indicator, based on the type of gesture detected provides the user with more control options without cluttering the user interface. Providing additional control of the system without cluttering the UI with additional displayed controls enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently. Causing the first accessory device and the second accessory device to change to a second state that is different from the first state provides the user with one control that causes multiple devices to change state, which reduces the number of inputs needed to cause the multiple devices to change state. Reducing the number of inputs needed to perform an operation enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.
In some embodiments, in accordance with the determination that the gesture is the second type of gesture (e.g., 1350c) that is different from the first type of gesture and is directed to the first status indicator (e.g., 1314h), the computer system displays, via the display generation component and concurrently with the first accessory control user interface object (e.g., 718b, 718f-718j), a second accessory control user interface object (e.g., 718b, 718f-718j) corresponding to the second accessory device. In some embodiments, selection (e.g., via a gesture that is the first type of gesture (e.g., a tap gesture)) of the second accessory control user interface object causes (e.g., via a process (and, in some embodiments, the process includes transmitting an instruction to one or more devices (e.g., a server, a hub device that is in communication with a plurality of accessory devices (e.g., that includes the first and second accessory devices)), second accessory device (not the first accessory device)) the second accessory device to change to the second state without causing the first accessory device to change to the second state. In some embodiments, while displaying the second accessory control user interface object corresponding to the second accessory device, the computer system detects a gesture (e.g., a gesture of the first type directed to the first accessory control user interface object) directed to the first accessory control user interface object; and, in response to detecting the gesture directed to the second accessory control user interface object, the computer system causes the second accessory device (e.g., to perform the action that changes the second accessory device) to be in the second state without causing the first accessory device to be in the second state (e.g., the first accessory device continues to be in the first state after the causing the second accessory device to be in the first state is completed). In some embodiments, in response to detecting the gesture directed to the second accessory control user interface object, the second accessory control user interface object is modified from having a first visual appearance (e.g., text, size, color, pressed state (e.g., depressed, pressed)) to a second visual appearance (e.g., text, size, color, pressed state (e.g., depressed, pressed)) that is different from the first visual appearance. Displaying a second accessory control user interface object corresponding to the second accessory device concurrently with the first accessory control corresponding to the first accessory device (e.g., in accordance with the determination that the gesture is the second type of gesture that is different from the first type of gesture and is directed to the first status indicator) provides the user with more control options to control individual accessory devices without cluttering the user interface. Providing additional control of the system without cluttering the UI with additional displayed controls enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.
In some embodiments, the gesture is detected while concurrently displaying, with the first status indicator, a second status indicator (e.g., 1314g, 1314i) that indicates that a plurality of accessory devices of a second accessory type, different from the first accessory type, is in a third state, the plurality of accessory devices of the second accessory type including a third accessory device that is the second accessory type and is in the third state (e.g., a different state than the first state and the second state) and a fourth accessory device that is the second accessory type and is in the third state. In some embodiments, the third accessory device that is the second accessory type and is in the second state and the fourth accessory device that is the second accessory type and is in the second state is different from the first accessory device and the second accessory device. In some embodiments, in accordance with a determination that the gesture is the first type of gesture (e.g., similar to 1350f) (e.g., a tap gesture) and is directed to (e.g., on, at a location corresponding to) the second status indicator (e.g., 1314g, 1314i), the computer system causes (e.g., via a process initiating a process (and, in some embodiments, the process includes transmitting one or more instructions to one or more devices (e.g., a server, a hub device that is in communication with a plurality of devices that includes the first accessory device, the second accessory device, the third accessory device, and the fourth accessory device))) the third accessory device and the fourth accessory device to change to a fourth state that is different from the third state (e.g., without causing the first accessory device and the second accessory device to change to a different state (e.g., the second state that is different (e.g., an opposite of (e.g., on/off, locked/unlocked, open/closed)) from the first state). In some embodiments, in accordance with a determination that the gesture is the second type of gesture (e.g., similar to 1350c) (e.g., a press-and-hold gesture) and is directed to (e.g., on, at a location corresponding to) the second status indicator (e.g., 1314g, 1314i), the computer system displays, via the display generation component, a third accessory control user interface object (e.g., as a part of displaying a second user interface) corresponding to the third accessory device. In some embodiments, selection (e.g., via a gesture that is the first type of gesture (e.g., a tap gesture)) of the third accessory control user interface object causes (e.g., via a process (and, in some embodiments, the process includes transmitting an instruction to one or more devices (e.g., a server, a hub device that is in communication with a plurality of accessory devices (e.g., that includes the first, second, third, and fourth accessory devices)), third accessory device (not the fourth accessory device)) the third accessory device (e.g., to perform the action that changes a state of the first accessory device) to change to the fourth state without causing the fourth accessory device to change to the fourth state (and, in some embodiments, without displaying, via the display generation component, the first accessory control user interface object (e.g., as a part of displaying the second user interface) corresponding to the first accessory device and/or the second accessory control user interface object) (e.g., the fourth accessory device continues to be in the third state after causing the third accessory device has been caused to be in the fourth state). In some embodiments, in accordance with a determination that the gesture is the second type of gesture (e.g., a press-and-hold gesture) and is directed to (e.g., on, at a location corresponding to) the second status indicator, the computer system displays a fourth accessory control user interface object concurrently with the third accessory control user interface object. In some embodiments, when the fourth accessory control user interface object is selected, the computer system causes (e.g., via a process (and, in some embodiments, the process includes transmitting an instruction to one or more devices (e.g., a server, a hub device that is in communication with a plurality of accessory devices (e.g., that includes the first, second, third, fourth accessory devices)), fourth accessory device (not the third accessory device)) the fourth accessory device to change to the fourth state without causing the third accessory device to change to the fourth state. Performing different operations based on the status indicator to which the gesture is directed and the type of gesture detected provides the user with more control options to control different accessory device types without cluttering the user interface. Providing additional control of the system without cluttering the UI with additional displayed controls enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently. Causing the third accessory device and the fourth accessory device to change to a fourth state provides the user with one control that causes multiple devices to change state and reduces the number of inputs needed to cause the multiple devices to change state. Reducing the number of inputs needed to perform an operation enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.
In some embodiments, in accordance with a determination that a fifth accessory device (e.g., device represented by 718b in
In some embodiments, the first type of gesture is a tap gesture (e.g., 1350f) (e.g., a gesture that is detected (e.g., via the one or more input devices) for less than a predetermined period of time). In some embodiments, the second type of gesture is a press-and-hold gesture (e.g., 1350c) (e.g., a gesture that is detected (e.g., via the one or more input devices) for more than a predetermined period of time).
In some embodiments, in response to detecting the gesture and in accordance with a determination that the gesture is a third type of gesture (e.g., 1350a) (e.g., a swipe gesture, a gesture that moves in a direction (e.g., a lateral direction)) (e.g., and is directed to the first status indicator), the computer system displays (e.g., by scrolling the status indicators) a status indicator (e.g., 1314f in
In some embodiments, as a part of causing the first accessory device and the second accessory device to change to the second state, the computer system causes the first accessory device and the second accessory device to perform a type of action (e.g., turn off lights, unlock door locks, open blinds a certain percentage, turn off ac/heat) that is based on the first accessory type (e.g., lights, door locks, blinds, temperature controls). Causing the first accessory device and the second accessory device to perform a type of action that is based on the first accessory type allows the computer system to cause a particular action to be performed that is based on certain prescribed conditions. Performing an operation when a set of conditions has been met without requiring further user input enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently.
In some embodiments, before detecting the gesture, the computer system displays a third status indicator (e.g., 1314b) (e.g., that indicates that a plurality of accessory devices of a second accessory type (e.g., that is different from the first accessory type) are in a third state) adjacent to the first status indicator and a fourth status indicator (e.g., 1314c) (e.g., that indicates that a plurality of accessory devices of a third accessory type (e.g., that is different from the second accessory type and the first accessory type) are in a fourth state) adjacent to the third status indicator (e.g., 1314e). In some embodiments, the first status indicator, the third status indicator, and fourth status indicator are displayed in an order based on a respective status indicator category (e.g., alarms (e.g., co, co2, smoke, leak, alarm), action required (e.g., accessories not responding, account error, low battery, updated available), significant status (things that are important: home temperature, open doors or windows), quick actions (e.g., categories that will flip the state of accessory, doors unlocked, windows open, 5 lights on, 2 fans on), sensors (e.g., humidity level, light level “34 lux”, etc.)) that corresponds to each respective status indicator (e.g., a respective status indicator category that each respective status indicator is in). In some embodiments, while displaying the first status indicator, the third status indicator, and the fourth status indicator in the order, the computer system receives an indication that a fifth status indicator should be displayed (e.g., the state of one or more of a different accessory device type (e.g., than the accessory device types that are indicated by the first status indicator, the second status indicator, and the third status indicator) has changed); and in response to receiving the indicator that the indication that the fifth status indicator should be displayed: (1) in accordance with a determination that the fifth status indicator is in a first status indicator category (e.g., same status indicator category as the first status indicator), the computer system displays the fifth status indicator at a first location (e.g., a location that is adjacent to the first status indicator); (2) in accordance with a determination that the fifth status indicator is in a second status indicator category (e.g., different status indicator category from the first status indicator category) (e.g., same status indicator category as the third status indicator), displaying the fifth status indicator at a second location (e.g., a location that is adjacent to the third status indicator) that is different from the first location; and (3) in accordance with a determination that the fifth status indicator is in a third status indicator category (e.g., different status indicator category from the first status indicator category and the third status indicator category) (e.g., same status indicator category as the fourth status indicator), displaying the fifth status indicator at the third location (e.g., a location that is adjacent to the fourth status indicator) that is different from the first location and the second location). Displaying status indicators in an order based on their respective categories provides the user with enhanced feedback concerning the importance or the category of a particular status indicator and allows a user to quickly recognize the category to which a particular status indicator corresponds. Providing improved visual feedback to the user enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.
In some embodiments, the computer system detects a change in a state of a respective accessory device of the first accessory type. In some embodiments, in response to detecting the change in the state of the respective accessory device of the first accessory type and in accordance with a determination that a state of a respective accessory device has changed to a first state, the computer system adds the respective accessory device to the plurality of accessory devices of the first accessory type (e.g., light bulbs, windows, switches, outlets, locks (e.g., door locks, window locks), televisions) that are in the first state. In some embodiments, in response to detecting the change in the state of the respective accessory device of the first accessory type and in accordance with a determination that the state of the respective accessory device has changed to the second state (or, alternatively, has changed to not be the first state), the computer system removes the respective accessory device from the plurality of accessory devices of the first accessory type (e.g., light bulbs, windows, switches, outlets, locks (e.g., door locks, window locks), televisions) that are in the first state. Thus, as additional accessories of a respective type are detected to be in the respective state, the additional accessories are added to the respective status indicator, such that the additional accessories are controlled by activating the status indictor; as some accessories of a respective type are detected to no longer be in the respective state, the accessories are removed from the respective status indicator, such that the removed accessories are not controlled by activating the status indicator. Updating the plurality of accessory devices based on the status of accessories allows the system to enable the user to quickly change the status of the accessories of the same type and state, and to individually access the accessories (e.g., via a press-and-hold). Providing additional control of the system without cluttering the UI with additional displayed controls enhances the operability of the system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the system) which, additionally, reduces power usage and improves battery life of the system by enabling the user to use the system more quickly and efficiently
In some embodiments, the first status indicator includes an indication of a number of accessory devices that are displayed (or updated) based on a current number of accessory devices of the first accessory type that are in the first state. In some embodiments, before detecting the gesture, the first status indicator includes an indication of a first number of accessory devices (e.g., that are the first accessory type and are in the first state). In some embodiments, in accordance with a determination that a tenth accessory device that is the first accessory device type and has changed to be in the first state, the computer system updates the first status indicator to include an indication of a second number of accessory devices (e.g., that are the second accessory type and are in the second state) that is different from the indication of the first number of accessory devices. In some embodiments, in accordance with a determination that the second accessory has changed to not be in the first state, the computer system updates the first status indicator to include an indication of a third number of accessory devices that is different from the indication of the first number of accessory devices and the indication of the second number of accessory devices. In some embodiments, the second number of accessory devices is greater than the first number of accessory devices, and the third number of accessory devices is less than the first number of accessory devices. Displaying a status indicator that includes an indication that is based on the current number of accessory devices allows the user to quickly recognize the number of devices to which the status indicated by the status indicator corresponds and provides the user with enhanced feedback concerning how many devices that input on the status indicator could potentially impact. Providing improved visual feedback to the user enhances the operability of the computer system and makes the user-system interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the computer system) which, additionally, reduces power usage and improves battery life of the computer system by enabling the user to use the computer system more quickly and efficiently.
In some embodiments, in accordance with a determination that the gesture is the first type of gesture (e.g., 1350f) and is directed to the first status indicator (e.g., 1350h), the computer system ceases to display the first status indicator (e.g., 1350h in
In some embodiments, the first status indicator (e.g., 1314h) is displayed at a first location when the gesture is detected. In some embodiments, in accordance with a determination that the gesture is the first type of gesture (e.g., 1350f) and is directed to the first status indicator (e.g., 1314h), the computer system ceases to display the first status indicator (e.g., 1314h) at the first location and displays a sixth status indicator (e.g., 1314i in
In some embodiments, in accordance with the determination that the gesture is the first type of gesture (e.g., 1350i) and is directed to the first status indicator (e.g., 1314h), the computer system visually updates the first status indicator (e.g., 1314h in
In some embodiments, the first status indicator (e.g., 1314h) is displayed on a first user interface (e.g., 710). In some embodiments, the computer system receives (e.g., while displaying the first status indicator on the first user interface) a request (e.g., 1350h) to display a second user interface (e.g., 1360) that is different from the first user interface (e.g., 710). In some embodiments, in response to receiving the request (e.g., 1350h) to display the second user interface, the computer system displays the second user interface (e.g., 1360) that includes a status indicator (e.g., 1350i in
In some embodiments, before detecting the gesture (e.g., 1350a-1350c and 1350f), an eighth status indicator that indicates that one or more accessory devices of a third accessory type are in a seventh state (e.g., on/off, open, closed) is displayed. In some embodiments, the one or more accessory devices include an eighth accessory device of the third accessory type. In some embodiments, in accordance with a determination that the gesture (e.g., 1350f, 1350i) is the second type of gesture (e.g., a press-and-hold gesture) and is directed to (e.g., on, at a location corresponding to) the eighth status indicator (e.g., 1314h) and in accordance with a determination that the eighth status indicator (e.g., 1314h in
In some embodiments, in accordance with a respective status indicator (e.g., the eighth status indicator) corresponding to a single accessory device, the respective status indicator includes a name (e.g., alphanumeric text) of the accessory device. In accordance with the respective status indicator (e.g., the eighth status indicator) corresponding to a plurality of accessory devices, the respective status indicator includes an indication (e.g., a numeric representation) of the number of accessory devices represented.
In some embodiments, the computer system detects a tap on another type of status indicator (e.g., 1314a-1314f and 1314j-13141) (e.g., climate control, sensors (e.g., different types of sensors may be combined in a single status indicator)) and, in response to detecting the tap, displays a user interface (e.g., 1382, 1384, 1386) for controlling the plurality of a type of devices related to the other type of status indicator. In some embodiments, device 700 does not ceases to display the other type of control after detecting the tap on it.
Note that details of the processes described above with respect to method 1400 (e.g.,
As illustrated in
As illustrated in
Looking back at
Graphical indications 1524a-1524c correspond to different multicast messages that were sent by different users (or devices), which are illustrated by graphical indications 1524a-1524c depicting different representations. Graphical indication 1524a includes a visual representation of a sender (e.g., “John”) (e.g., a determined sender) of the first audio multicast message. Graphical indication 1524b includes a visual representation of a device (e.g., a speaker) that recorded the second audio multicast message. Graphical indication 1524c includes a visual representation of text that corresponds to a sender (e.g., “EA,” which stands for “Emma Appleseed,” who is a person associated with home 602 as indicated in
As illustrated in
In response to determining that the first audio multicast message will end within a predetermined period of time (or has ended) (e.g., without user input, based on a tap gesture on skip affordance 1534), device 700 rotates graphical indications 1524b-1524c counter-clockwise and ceases to display graphical indication 1524a. As illustrated in
As shown in
As illustrated in
In response to determining that the second audio multicast message will end within a predetermined period of time (or has ended), device 700 rotates graphical indications 1524c-1524d counter-clockwise and ceases to display graphical indication 1524b. As illustrated in
As shown in
In response to determining that the third audio multicast message will end within a predetermined period of time (or has ended), device 700 moves (e.g., changes the position of) and enlarges graphical indication 1524d counter-clockwise and ceases to display graphical indication 1524c. As illustrated in
As illustrated in
As described below, method 1600 provides an intuitive way for playing media content. The method reduces the cognitive burden on a user for playing media messages, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to play media content faster and more efficiently conserves power and increases the time between battery charges.
The computer system (e.g., 700) displays (1602), via the display generation component, a media user interface (e.g., 1520) that includes: at a first location, a first representation (1604) (e.g., 1524a in
In response to displaying the media user interface and not based on user input corresponding to the media user interface (e.g., 1520), the computer system (e.g., 700) plays (1608) the first media message (e.g., outputting audio and/or video of the first media message).
In response to detecting completion of playing through the first media message (e.g., reaching an end of the first media message by playing through to the end of the first media message), the computer system (e.g., 700) displays (1610), the second representation (e.g., 1524b) of the second media message (e.g., as in
Displaying representations of various media message at different locations provides the user with feedback about the order of the media message and, for example, which media message is currently playing and which media message will play next. 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 representations of the plurality of (e.g., some of, not all of, three of) media message are displayed with varying sizes based on the order of the ordered set. In some embodiments, the earlier the media message is in the ordered set the larger the representation of the corresponding media message (e.g., a representation of a currently playing media message is the largest, a representation of a media message to be played next is the next largest, etc). Thus, the order of the media message is reflected in the comparative sizes of their corresponding displayed representations.
In accordance with some embodiments, displaying, the first representation (e.g., 1524a in
Displaying representations of various media message at different sizes provides the user with feedback about the order of the media message (e.g., bigger size is earlier in the ordered set) and, for example, which media message is currently playing and which media message will play next. 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 accordance with some embodiments, the computer system (e.g., 700) displays, via the display generation component, concurrently with the first representation of the first media message at the first location and with the second representation of the second media message at the second location: at a third size (e.g., the same as the second size, smaller than the second size) different from the first size (and, optionally, different from the second size) and at a third location different from the first location and second location, a third representation (e.g., 1524c) of a third media message. In response to detecting completion of playing through the first media message (e.g., reaching an end of the first media message by playing through to the end of the first media message): the computer system (e.g., 700) displays, at the first size and at the first location, the second representation (e.g., 1524b) of the second media message (e.g., as in
Displaying representations of various media message at different locations and at different sizes provides the user with feedback about the order of the media message to be played. 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 accordance with some embodiments, the computer system (e.g., 700) receives (e.g., via a wireless network) data (e.g., first, second, third, and fourth data) corresponding to media message (e.g., the group of media, the first, second, third, and fourth media message) including the first media message that is a first (e.g., audio) message (e.g., directed to a target group of devices (e.g., a plurality of devices of a home (e.g., a home automation system)), including the computer system) from a first remote user and the second media message that is a second (e.g., audio) message (e.g., directed to the target group of devices (e.g., the plurality of devices of the home (e.g., a home automation system)), including the computer system) from a second remote user that is different from the first remote user. The computer system (e.g., 700) displays (e.g., in response to receiving the data, until an end of a time period (as described in further detail above)), via the display generation component, a notification (e.g., 1502) corresponding to the media message. While displaying the notification (e.g., 1502), the computer system (e.g., 700) receives, via the one or more input devices, selection (e.g., 1550a) of the notification (e.g., activation of the notification displayed on a lock screen, the notification corresponding to the group of media, the group of media being in an ordered set). In some embodiments, displaying the media user interface occurs in response to receiving selection (e.g., 1550a) of the notification (e.g., 1502). In some embodiments, playing the first media message occurs in response to receiving selection (e.g., 1550a) of the notification (e.g., 1502).
Displaying the media user interface and automatically playing the first media message in response to a selection of a notification enables the computer system to perform two functions (display and playback) in response to the same input, thereby reducing the need for the computer system to receive additional inputs to start the playback. 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 representation (e.g., 1524a), the second representation (e.g., 1524b), and the third representation (e.g., 1524c) are not displayed in a line (e.g., the first, second, and third locations are not all on a line). In some embodiments, the representations of media that are displayed (e.g., as representations removed and new representations are add) are not displayed in a line.
In accordance with some embodiments, the first size is larger than the second size. In some embodiments, the second size is larger than the third size. In some embodiments, the second size and the third size are the same size. In some embodiments, the representation (e.g., 1524a in
Displaying representations of various media message at increasingly larger sizes provides the user with feedback about the order of the media message. For example, the larger the representation the earlier the corresponding media message is in the ordered set of media message, with (for example) the largest representation being the currently playing media item. 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 accordance with some embodiments, in response to detecting completion of playing through the first media message (e.g., reaching an end of the first media message by playing through to the end of the first media message), playing the second media message (e.g., outputting audio and/or video of the second media) without receiving (or requiring) further user input. In some embodiments, the second media message is played in conjunction with displaying, at the first size and at the first location, the second representation of the second media message.
Automatically playing the second media message in response completion of the first media message eliminates the need for the computer system to receive additional inputs to start the playback of the second media message. 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, in response to detecting completion of playing the second media message (e.g., reaching an end of the second media message; skipping the remainder of the first media), the computer system plays the third media message (e.g., outputting audio and/or video of the third media message) without receiving (or requiring) further user input. In some embodiments, the third media message is played in conjunction with displaying, at the first size and at the first location, the third representation of the third media message. In some embodiments, a fifth representation of a fifth media is not displayed after detecting completion of playing the second media message.
In accordance with some embodiments, prior to detecting completion of playing through the first media message, a fourth representation (e.g., 1524d) of a fourth media message (e.g., audio media; visual media; audiovisual media) is not concurrently displayed with the first representation of the first media (e.g., in the media user interface, as shown in
Displaying representations of a first predetermined number of media message of the group of media message without displaying representations of additional media message in the group of media until media message is played and the representation of the played media message is removed provides the user with feedback that additional media message are available for playback without cluttering the user interface. 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, when the media user interface is initially displayed (e.g., in response to selection of a displayed notification), the media user interface includes the first representation, the second representation, and the third representation without including the fourth representation.
In some embodiments, in response to detecting completion of playing the third media message (e.g., reaching an end of the third media message; skipping the remainder of the third media message), displaying, at a size different from (e.g., larger than) the first size and at a location different from the first location, the fourth representation (e.g., 1524d) of the fourth media message and playing the fourth media message without receiving (or requiring) user input (e.g., as shown in
In accordance with some embodiments, while playing the second media message, the computer system (e.g., 700) displays a next media user interface object (e.g., 1534) in the media user interface (e.g., 1520) that, when activated (e.g., detecting a tap on), causes completion of playing of the second media message (e.g., ceasing playing the currently playing media message; forgoing playing the remainder of the second media message; skipping past the remainder of the second media message) (and, optionally, begins playing the third media message). While playing the second media message, the computer system (e.g., 700) receives, via the one or more input devices, activation of (e.g., a tap on) the next media user interface object (e.g., 1534). In response to receiving activation of the next media user interface object (e.g., 1534), the computer system (e.g., 700) displays, via the display generation component, the third representation of the third media message at the first location (and, optionally, at the first size) without displaying, via the display generation component, the second representation of the second media message. In some embodiments, the third media message plays in conjunction with displaying the third representation of the third media message at the first location at the first size. In some embodiments, the next media user interface object, when activated, causes completion of the currently playing media message. In some embodiments, detecting completion of the currently playing media message causes (e.g., except when the currently playing media message is the final media message of the group of media) the technique to proceed to playing the next media message in the ordered set. In some embodiments, in response to receiving activation of the next media user interface object (e.g., 1534), the computer system ceases playing the second media message (e.g., without playing through to the end of the second media message) and plays the third media message.
Displaying a next media user interface object enables the computer system to receive user input to skip to playing the next media message without spending additional time playing the remainder of the currently playing media message. Providing the user with this additional control 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 computer system does not display the previous media user interface object (e.g., concurrently with playing the second media) (e.g., in the media user interface) that, when activated (e.g., detecting a tap on), causes completion of playing the (e.g., second) media message and begins playing a previous (e.g., first) media message. In some embodiments, the computer system forgoes displaying the next media user interface object when a last (e.g., the fourth) media message (e.g., of the group of media) is playing (e.g., as in
In some embodiments, the first media message, the second media message, and the third media message are part of a group of media. In accordance with some embodiments, subsequent to (e.g., in response to detection of completion of) playing a final media message (e.g., after playing or skipping through all media message of the group of media), the computer system (e.g., 700) displays, via the display generation component, a replay user interface object (e.g., 926, at the first location, at the location at which the fourth representation of the fourth media message was displayed) in the media user interface that, when activated (e.g., 1550f1, detecting a tap on), plays the first media message (e.g., outputting audio and/or video of the first media message) before proceeding to playing subsequent media message (e.g., the second, third, and fourth media message). In some embodiments, activation of the replay user interface object restarts the process again to replay the media message of the group of media. In some embodiments, subsequent to playing the final media message (e.g., of the group of media), the computer system deletes (e.g., after a predefined duration of time has passed) the first, second, and third media message (and, optionally the fourth media message) from the computer system (or makes the media message otherwise inaccessible to the user).
Displaying a replay user interface object (e.g., a replay button) to replay the media message of the group of media message allows the user to replay (and re-listen to, re-watch) the media message without needing to individually select each media message to play back. Providing additional control options 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 accordance with some embodiments, the first media message, the second media message, and the third media message (and, optionally, the fourth media message) were directed to a target group of devices (e.g., a plurality of devices of a home (e.g., a home automation system)), including the computer system. In accordance with some embodiments, the computer system (e.g., 700) displays, via the display generation component, a multicast affordance (e.g., 736) in the media user interface that, when activated (e.g., 1550f2, detecting a tap on), initiates a process for sending an audio multicast message to the target group of devices. In some embodiments, the process for sending the audio multicast message includes displaying the user interface of FIG. 7C1 and is described with respect to FIG. 7C1. In some embodiments, the one or more devices are electronic devices that are part of a group of electronic device to which the first, second, and third media message were directed.
Displaying a multicast affordance to initiate a process for sending an audio multicast message to one or more devices provides the user with the ability to respond to the media message that include messages without the need to individually select which users/devices will receive the message, thereby reducing the number of inputs the user needs to provide to respond. 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 process for sending the audio multicast message includes recording, at the computer system, an audio message. In some embodiments, the audio message is made available for playback at the computer system (e.g., as part of the group of media). In some embodiments, the computer system deletes the first, second, and third media message (and, optionally the fourth media message) from the computer system (or makes the media message otherwise inaccessible to the user) in conjunction with sending the audio multicast message.
In accordance with some embodiments, while playing a respective media message (e.g., the first media message, the second media message), the computer system (e.g., 700) displays, via the display generation component and in the media user interface, a name of a respective user (e.g., 1524a, 1524b. 1524c. 1524d) from which the respective media message was received. In some embodiments, as the media message that is playing changes, the name of the respective user is replaced (e.g., the previous name, the current name, the next name are displayed at the same location).
Displaying a name of a respective user from which the currently playing media was received provides the user with feedback about the source from which the computer system received the currently playing media message. 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 accordance with some embodiments, a representation of a currently playing media message (e.g., 1524a in
In accordance with some embodiments, the media message are audio messages (e.g., multicast audio messages). In some embodiments, the audio message (e.g., first media message) is an audio message recorded (using a microphone) at an external device and transmitted by the external device to a group of devices and/or an audio message that was directed to (e.g., transmitted to) a plurality of external devices that includes the computer system). In some embodiments, the second media message is a second audio message that was directed (or transmitted) to a second plurality of external devices (e.g., same as the plurality of external devices, different from the plurality of external devices).
Automatically playing back multiple audio messages of a conversation (e.g., in order) enables the computer system to output a conversation (e.g., an audio conversation among multiple participants) without requiring the user to individually select particular audio messages to play back, thereby reducing the number of required 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, a total count (e.g., “4” in “1 of 4” of 930 in
In some embodiments, a media message (e.g., the first media message) corresponds to a multi-user device (e.g., a device that is configured for multiple users, a device that is not configured for a particular user). In some embodiments, a media message (e.g., the second media message) corresponds to a single-user device (e.g., a device that is configured for a single user). In some embodiments, a visual indicator (e.g., 1522a, 1524a, 1522c, 1524c) of a corresponding user of a media message is displayed concurrent with playing the media message corresponding to the user. In some embodiments, a visual indictor (e.g., 1522b, 1524b) that indicates a multi-user device is displayed while playing the media message corresponding to the multi-user device.
Note that details of the processes described above with respect to method 1600 (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 visual content (e.g., visual indications) or any other content that provides the user with information concerning whether voice input will be sent as an audio messages to one or more devices. 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.
The present disclosure recognizes that the use of 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 improve the display of an indication so that a respective user can determine whether voice input will be transmitted as an audio message. Accordingly, use of such personal information data enables users to have calculated control over sending audio messages. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.
The present disclosure 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. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. 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/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking 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. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.
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 receiving voice input from a user, 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 or anytime thereafter. In another example, users can choose not to provide voice input to be sent as an audio message based on the indication that is displayed. In yet another example, users can select to limit the content of the audio message that corresponds to the voice input based on the indication that is displayed. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.
Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.
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, the visual indication can be displayed to users 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 audio message transmitting services, or publicly available information.
This application is a continuation of to U.S. patent application Ser. No. 17/027,373, filed on Sep. 21, 2020, titled “USER INTERFACE FOR AUDIO MESSAGE,” which claims priority to U.S. Provisional Patent Application Ser. No. 63/041,979, filed on Jun. 21, 2020, titled “USER INTERFACE FOR AUDIO MESSAGE,” and U.S. Provisional Patent Application Ser. No. 63/023,225, filed on May 11, 2020, titled “USER INTERFACE FOR AUDIO MESSAGE,” the contents of which are hereby incorporated by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 102663 | Dillen | May 1870 | A |
| 4975694 | Mclaughlin et al. | Dec 1990 | A |
| 5086385 | Launey et al. | Feb 1992 | A |
| 5146217 | Holmes et al. | Sep 1992 | A |
| 5202961 | Mills et al. | Apr 1993 | A |
| 5418528 | Hosack et al. | May 1995 | A |
| 5483595 | Owen | Jan 1996 | A |
| 5617526 | Oran et al. | Apr 1997 | A |
| 5687216 | Svensson | Nov 1997 | A |
| 5793366 | Mano et al. | Aug 1998 | A |
| 5801700 | Ferguson | Sep 1998 | A |
| 5835084 | Bailey et al. | Nov 1998 | A |
| 5872521 | Lopatukin et al. | Feb 1999 | A |
| 5875403 | Christal | Feb 1999 | A |
| 5923327 | Smith et al. | Jul 1999 | A |
| 5974235 | Nunally et al. | Oct 1999 | A |
| 6002402 | Schacher | Dec 1999 | A |
| 6014429 | Laporta et al. | Jan 2000 | A |
| 6016248 | Anzai et al. | Jan 2000 | A |
| 6025871 | Kantor et al. | Feb 2000 | A |
| 6084529 | Lee et al. | Jul 2000 | A |
| 6094197 | Buxton et al. | Jul 2000 | A |
| 6124947 | Seo | Sep 2000 | A |
| 6140987 | Stein et al. | Oct 2000 | A |
| 6169911 | Wagner et al. | Jan 2001 | B1 |
| 6191807 | Hamada et al. | Feb 2001 | B1 |
| 6216008 | Lee | Apr 2001 | B1 |
| 6230019 | Lee | May 2001 | B1 |
| 6256663 | Davis | Jul 2001 | B1 |
| 6292473 | Duske et al. | Sep 2001 | B1 |
| 6333973 | Smith et al. | Dec 2001 | B1 |
| 6346962 | Goodridge | Feb 2002 | B1 |
| 6362842 | Tahara et al. | Mar 2002 | B1 |
| 6393464 | Dieterman | May 2002 | B1 |
| 6456306 | Chin et al. | Sep 2002 | B1 |
| 6456841 | Tomimori | Sep 2002 | B1 |
| 6457122 | Ramezani | Sep 2002 | B1 |
| 6483986 | Krapf | Nov 2002 | B1 |
| 6504934 | Kasai et al. | Jan 2003 | B1 |
| 6662023 | Helle | Dec 2003 | B1 |
| 6674452 | Kraft et al. | Jan 2004 | B1 |
| 6714965 | Kakuta et al. | Mar 2004 | B2 |
| 6720863 | Hull et al. | Apr 2004 | B2 |
| 6721784 | Leonard et al. | Apr 2004 | B1 |
| 6726094 | Rantze et al. | Apr 2004 | B1 |
| 6728784 | Mattaway | Apr 2004 | B1 |
| 6731308 | Tang et al. | May 2004 | B1 |
| 6741232 | Siedlikowski et al. | May 2004 | B1 |
| 6778642 | Schmidt et al. | Aug 2004 | B1 |
| 6792448 | Smith | Sep 2004 | B1 |
| 6833848 | Wolff et al. | Dec 2004 | B1 |
| 6850781 | Goto | Feb 2005 | B2 |
| 6901439 | Bonasia et al. | May 2005 | B1 |
| 6912429 | Bilger | Jun 2005 | B1 |
| 6931594 | Jun | Aug 2005 | B1 |
| 6934738 | Furusawa et al. | Aug 2005 | B1 |
| 6937707 | Kim et al. | Aug 2005 | B2 |
| 7092768 | Labuda | Aug 2006 | B1 |
| 7102663 | Crook | Sep 2006 | B2 |
| 7120455 | Chen et al. | Oct 2006 | B1 |
| 7124164 | Chemtob | Oct 2006 | B1 |
| 7148911 | Mitsui et al. | Dec 2006 | B1 |
| 7149893 | Leonard et al. | Dec 2006 | B1 |
| 7185054 | Ludwig et al. | Feb 2007 | B1 |
| 7197122 | Vuori | Mar 2007 | B2 |
| 7250955 | Beeman et al. | Jul 2007 | B1 |
| 7293280 | Gupta et al. | Nov 2007 | B1 |
| 7365736 | Marvit et al. | Apr 2008 | B2 |
| 7401351 | Boreczky et al. | Jul 2008 | B2 |
| 7433920 | Blagsvedt et al. | Oct 2008 | B2 |
| 7478129 | Chemtob | Jan 2009 | B1 |
| 7496385 | Gruen et al. | Feb 2009 | B2 |
| 7571014 | Lambourne et al. | Aug 2009 | B1 |
| 7603379 | Kang et al. | Oct 2009 | B2 |
| 7636578 | Cope et al. | Dec 2009 | B1 |
| 7650361 | Wong et al. | Jan 2010 | B1 |
| 7656393 | King et al. | Feb 2010 | B2 |
| 7665031 | Matthews et al. | Feb 2010 | B2 |
| 7680895 | Perlow et al. | Mar 2010 | B2 |
| 7685530 | Sherrard et al. | Mar 2010 | B2 |
| 7716593 | Durazo et al. | May 2010 | B2 |
| 7730223 | Bavor et al. | Jun 2010 | B1 |
| 7789225 | Whiteis | Sep 2010 | B2 |
| 7797390 | Hagale et al. | Sep 2010 | B2 |
| 7801971 | Amidon et al. | Sep 2010 | B1 |
| 7831054 | Ball et al. | Nov 2010 | B2 |
| 7834861 | Lee | Nov 2010 | B2 |
| 7859571 | Brown et al. | Dec 2010 | B1 |
| 7870199 | Galli et al. | Jan 2011 | B2 |
| 7876996 | Herz | Jan 2011 | B1 |
| 7899474 | Neil et al. | Mar 2011 | B2 |
| 7903171 | Takabatake et al. | Mar 2011 | B2 |
| 7904814 | Errico et al. | Mar 2011 | B2 |
| 7908219 | Abanami et al. | Mar 2011 | B2 |
| 7912904 | Buchheit et al. | Mar 2011 | B2 |
| 7921166 | Karn | Apr 2011 | B2 |
| 7982762 | Chatting et al. | Jul 2011 | B2 |
| 8019822 | Martino et al. | Sep 2011 | B2 |
| 8024758 | Byun et al. | Sep 2011 | B2 |
| 8028323 | Weel | Sep 2011 | B2 |
| 8031230 | Takada | Oct 2011 | B2 |
| 8036901 | Mozer | Oct 2011 | B2 |
| 8037139 | Fish et al. | Oct 2011 | B1 |
| 8037141 | Daniell | Oct 2011 | B2 |
| 8060621 | Lee et al. | Nov 2011 | B2 |
| 8116807 | Matas | Feb 2012 | B2 |
| 8121586 | Araradian et al. | Feb 2012 | B2 |
| 8139573 | Kim | Mar 2012 | B2 |
| 8150930 | Satterfield et al. | Apr 2012 | B2 |
| 8169463 | Enstad et al. | May 2012 | B2 |
| 8180382 | Graefen | May 2012 | B1 |
| RE43462 | Washino et al. | Jun 2012 | E |
| 8196043 | Crow et al. | Jun 2012 | B2 |
| 8209384 | Tom et al. | Jun 2012 | B2 |
| 8209634 | Klassen et al. | Jun 2012 | B2 |
| 8214494 | Slavin | Jul 2012 | B1 |
| 8234395 | Millington | Jul 2012 | B2 |
| 8253704 | Jang | Aug 2012 | B2 |
| 8255830 | Ording et al. | Aug 2012 | B2 |
| 8274544 | Kurtz et al. | Sep 2012 | B2 |
| 8280539 | Jehan et al. | Oct 2012 | B2 |
| 8290603 | Lambourne | Oct 2012 | B1 |
| 8311562 | Klassen | Nov 2012 | B2 |
| 8370448 | Galchev | Feb 2013 | B2 |
| 8458780 | Takkallapally et al. | Jun 2013 | B1 |
| 8462961 | Bywaters et al. | Jun 2013 | B1 |
| 8479122 | Hotelling et al. | Jul 2013 | B2 |
| 8488752 | Wiesen | Jul 2013 | B1 |
| 8502856 | Jeong et al. | Aug 2013 | B2 |
| 8516374 | Fleischman et al. | Aug 2013 | B2 |
| 8527345 | Rothschild et al. | Sep 2013 | B2 |
| 8572493 | Qureshi | Oct 2013 | B2 |
| 8607334 | Brown et al. | Dec 2013 | B2 |
| 8611873 | Onyon et al. | Dec 2013 | B2 |
| 8624952 | Currivan et al. | Jan 2014 | B2 |
| 8648799 | Lloyd | Feb 2014 | B1 |
| 8650652 | Adams | Feb 2014 | B2 |
| 8676901 | Nicolaou et al. | Mar 2014 | B1 |
| 8689147 | Griffin et al. | Apr 2014 | B2 |
| 8706818 | Krzyzanowski et al. | Apr 2014 | B2 |
| 8725880 | Santamaria et al. | May 2014 | B2 |
| 8745500 | Kostello et al. | Jun 2014 | B1 |
| 8751594 | Aceves | Jun 2014 | B2 |
| 8762844 | Kim et al. | Jun 2014 | B2 |
| 8830181 | Clark et al. | Sep 2014 | B1 |
| 8848932 | Poulsen et al. | Sep 2014 | B2 |
| 8849928 | Yuyama | Sep 2014 | B2 |
| 8856105 | Gargi | Oct 2014 | B2 |
| 8914752 | Spiegel | Dec 2014 | B1 |
| 8918128 | Merrett | Dec 2014 | B2 |
| 8922485 | Lloyd | Dec 2014 | B1 |
| 8924866 | Shin et al. | Dec 2014 | B2 |
| 8954889 | Fujibayashi | Feb 2015 | B2 |
| 8984444 | O | Mar 2015 | B2 |
| 8990861 | Nishikawa et al. | Mar 2015 | B2 |
| 9021526 | Baron et al. | Apr 2015 | B1 |
| 9042556 | Kallai et al. | May 2015 | B2 |
| 9080736 | Salzinger | Jul 2015 | B1 |
| 9082018 | Laska et al. | Jul 2015 | B1 |
| 9084003 | Sanio et al. | Jul 2015 | B1 |
| 9112849 | Werkelin Ahlin et al. | Aug 2015 | B1 |
| 9112984 | Sejnoha et al. | Aug 2015 | B2 |
| 9134902 | Kang et al. | Sep 2015 | B2 |
| 9158974 | Laska et al. | Oct 2015 | B1 |
| 9170707 | Laska et al. | Oct 2015 | B1 |
| 9185062 | Yang et al. | Nov 2015 | B1 |
| 9202509 | Kallai et al. | Dec 2015 | B2 |
| 9207835 | Yang et al. | Dec 2015 | B1 |
| 9247363 | Triplett et al. | Jan 2016 | B2 |
| 9247380 | Vincent | Jan 2016 | B1 |
| 9251787 | Hart et al. | Feb 2016 | B1 |
| 9253531 | Relyea et al. | Feb 2016 | B2 |
| 9294853 | Dhaundiyal | Mar 2016 | B1 |
| 9313160 | Shamis et al. | Apr 2016 | B1 |
| 9313556 | Borel et al. | Apr 2016 | B1 |
| 9319782 | Crump et al. | Apr 2016 | B1 |
| 9329831 | Fullerton et al. | May 2016 | B1 |
| 9361011 | Burns et al. | Jun 2016 | B1 |
| 9361521 | McLean et al. | Jun 2016 | B1 |
| 9374607 | Bates et al. | Jun 2016 | B2 |
| 9380264 | Vakalapudi | Jun 2016 | B1 |
| D765118 | Bachman et al. | Aug 2016 | S |
| 9413606 | Roberts | Aug 2016 | B1 |
| 9431021 | Scalise et al. | Aug 2016 | B1 |
| 9433032 | Ghadge et al. | Aug 2016 | B1 |
| 9444898 | Cheng et al. | Sep 2016 | B1 |
| 9445048 | Nariyawala et al. | Sep 2016 | B1 |
| 9450812 | Lee et al. | Sep 2016 | B2 |
| 9454336 | Rudradevan et al. | Sep 2016 | B1 |
| 9462017 | Siracusano, Jr. | Oct 2016 | B1 |
| 9483529 | Pasoi et al. | Nov 2016 | B1 |
| D773510 | Foss et al. | Dec 2016 | S |
| 9519413 | Bates | Dec 2016 | B2 |
| 9578160 | Kim et al. | Feb 2017 | B2 |
| 9582178 | Grant et al. | Feb 2017 | B2 |
| 9588661 | Jauhal et al. | Mar 2017 | B1 |
| 9628414 | Umapathy et al. | Apr 2017 | B1 |
| 9635314 | Barkley et al. | Apr 2017 | B2 |
| 9653067 | Brooks et al. | May 2017 | B2 |
| 9665242 | Kim et al. | May 2017 | B2 |
| D789381 | Okumura et al. | Jun 2017 | S |
| 9680982 | Fiedler | Jun 2017 | B2 |
| 9710639 | Saini | Jul 2017 | B1 |
| 9727346 | Shao | Aug 2017 | B2 |
| 9727749 | Tzeng et al. | Aug 2017 | B2 |
| 9728230 | Cudak et al. | Aug 2017 | B2 |
| 9750116 | Witzgall | Aug 2017 | B2 |
| 9759917 | Osterhout et al. | Sep 2017 | B2 |
| 9784417 | Springer | Oct 2017 | B1 |
| 9787938 | Cranfill et al. | Oct 2017 | B2 |
| 9794720 | Kadri | Oct 2017 | B1 |
| 9800951 | Carlson et al. | Oct 2017 | B1 |
| 9819877 | Faulkner et al. | Nov 2017 | B1 |
| 9820323 | Young et al. | Nov 2017 | B1 |
| 9858739 | Johnson et al. | Jan 2018 | B1 |
| 9886953 | Lemay et al. | Feb 2018 | B2 |
| 9898175 | Fiedler | Feb 2018 | B2 |
| 9898250 | Williams et al. | Feb 2018 | B1 |
| 9954989 | Zhou | Apr 2018 | B2 |
| 9992450 | Yuan et al. | Jun 2018 | B1 |
| 10027775 | Mierau et al. | Jul 2018 | B1 |
| 10055094 | Li et al. | Aug 2018 | B2 |
| 10068364 | Cui | Sep 2018 | B2 |
| 10091017 | Landow et al. | Oct 2018 | B2 |
| 10104089 | Kim et al. | Oct 2018 | B2 |
| 10110530 | Sachtjen | Oct 2018 | B2 |
| 10120536 | Cha et al. | Nov 2018 | B2 |
| 10129044 | Kangshang et al. | Nov 2018 | B2 |
| 10142122 | Hill et al. | Nov 2018 | B1 |
| 10157040 | Ballinger | Dec 2018 | B2 |
| 10182138 | Motika et al. | Jan 2019 | B2 |
| 10194189 | Goetz et al. | Jan 2019 | B1 |
| 10198563 | Wang et al. | Feb 2019 | B2 |
| 10200468 | Leban et al. | Feb 2019 | B2 |
| 10219026 | Eim et al. | Feb 2019 | B2 |
| 10237141 | Sasaki et al. | Mar 2019 | B2 |
| 10270983 | Van Os et al. | Apr 2019 | B1 |
| 10282068 | Dubin et al. | May 2019 | B2 |
| 10284812 | Van Os et al. | May 2019 | B1 |
| 10284980 | Woo et al. | May 2019 | B1 |
| 10296128 | Nold et al. | May 2019 | B1 |
| 10298643 | Toal et al. | May 2019 | B1 |
| 10299300 | Young | May 2019 | B1 |
| 10300394 | Evans | May 2019 | B1 |
| 10303422 | Woo et al. | May 2019 | B1 |
| 10306049 | Bauer et al. | May 2019 | B1 |
| 10310725 | Smith et al. | Jun 2019 | B2 |
| 10339769 | Mixter | Jul 2019 | B2 |
| 10353532 | Holz et al. | Jul 2019 | B1 |
| 10362272 | Van Os et al. | Jul 2019 | B1 |
| 10374804 | Lee et al. | Aug 2019 | B2 |
| 10386994 | Singal et al. | Aug 2019 | B2 |
| 10389977 | Van Os et al. | Aug 2019 | B1 |
| 10409239 | Reeder et al. | Sep 2019 | B2 |
| 10410426 | Kamini et al. | Sep 2019 | B2 |
| 10416844 | Yang et al. | Sep 2019 | B2 |
| 10436977 | Bergman et al. | Oct 2019 | B2 |
| 10454781 | Sasaki et al. | Oct 2019 | B2 |
| 10474349 | Jang et al. | Nov 2019 | B2 |
| 10511456 | Smith et al. | Dec 2019 | B2 |
| 10511559 | Stovicek et al. | Dec 2019 | B2 |
| 10515623 | Grizzel | Dec 2019 | B1 |
| 10523625 | Allen et al. | Dec 2019 | B1 |
| 10523976 | Hemmati et al. | Dec 2019 | B2 |
| 10524300 | Ueda et al. | Dec 2019 | B2 |
| 10630795 | Aoki et al. | Apr 2020 | B2 |
| 10631123 | O'keeffe | Apr 2020 | B2 |
| 10645294 | Manzari et al. | May 2020 | B1 |
| 10708653 | Stinson et al. | Jul 2020 | B1 |
| 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 |
| 10757366 | Kwatra et al. | Aug 2020 | B1 |
| 10771740 | Reynolds et al. | Sep 2020 | B1 |
| 10771741 | Reynolds et al. | Sep 2020 | B1 |
| 10779085 | Carrigan | Sep 2020 | B1 |
| 10783883 | Mixter | Sep 2020 | B2 |
| 10824299 | Bai | Nov 2020 | B2 |
| 10833887 | Wu | Nov 2020 | B2 |
| 10909586 | Avedissian et al. | Feb 2021 | B2 |
| 10924446 | Paul | Feb 2021 | B1 |
| 10929099 | Querze | Feb 2021 | B2 |
| 10963145 | Voss et al. | Mar 2021 | B1 |
| 10972655 | Ostap et al. | Apr 2021 | B1 |
| 11012575 | Leblang et al. | May 2021 | B1 |
| 11024303 | Devaraj | Jun 2021 | B1 |
| 11064256 | Voss et al. | Jul 2021 | B1 |
| 11079913 | Kim et al. | Aug 2021 | B1 |
| 11133008 | Piernot et al. | Sep 2021 | B2 |
| 11144885 | Rosenberg | Oct 2021 | B2 |
| 11157143 | Yang et al. | Oct 2021 | B2 |
| 11164113 | Howard | Nov 2021 | B2 |
| 11164580 | Kraker | Nov 2021 | B2 |
| 11176940 | Zhong | Nov 2021 | B1 |
| 11212449 | Manzari et al. | Dec 2021 | B1 |
| 11258619 | Libin | Feb 2022 | B2 |
| 11283916 | Coffman | Mar 2022 | B2 |
| 11290687 | Becchetti | Mar 2022 | B1 |
| 11316709 | Brown | Apr 2022 | B2 |
| 11343370 | Gordon et al. | May 2022 | B1 |
| 11343613 | Gordon | May 2022 | B2 |
| 11360634 | Chang et al. | Jun 2022 | B1 |
| 11431834 | Gordon et al. | Aug 2022 | B1 |
| 11449188 | Chang et al. | Sep 2022 | B1 |
| 11463576 | Gordon et al. | Oct 2022 | B1 |
| 11523166 | Tu | Dec 2022 | B1 |
| 11671697 | O'leary et al. | Jun 2023 | B2 |
| 11726647 | Kim | Aug 2023 | B2 |
| 11770600 | O'leary et al. | Sep 2023 | B2 |
| 12014118 | Gruber | Jun 2024 | B2 |
| 12085421 | Yedid | Sep 2024 | B2 |
| 20010030597 | Inoue et al. | Oct 2001 | A1 |
| 20010033298 | Slotznick | Oct 2001 | A1 |
| 20010041007 | Aoki | Nov 2001 | A1 |
| 20020002039 | Qureshey et al. | Jan 2002 | A1 |
| 20020012526 | Sai et al. | Jan 2002 | A1 |
| 20020057262 | Patrick et al. | May 2002 | A1 |
| 20020057284 | Dalby et al. | May 2002 | A1 |
| 20020060701 | Naughton et al. | May 2002 | A1 |
| 20020063737 | Feig et al. | May 2002 | A1 |
| 20020093531 | Barile | Jul 2002 | A1 |
| 20020093536 | Hong | Jul 2002 | A1 |
| 20020101446 | Tang et al. | Aug 2002 | A1 |
| 20020120869 | Engstrom | Aug 2002 | A1 |
| 20020126135 | Ball et al. | Sep 2002 | A1 |
| 20020152220 | Kang et al. | Oct 2002 | A1 |
| 20020154888 | Allen et al. | Oct 2002 | A1 |
| 20020167488 | Hinckley et al. | Nov 2002 | A1 |
| 20020168938 | Chang | Nov 2002 | A1 |
| 20020180774 | Errico et al. | Dec 2002 | A1 |
| 20030003897 | Hyon | Jan 2003 | A1 |
| 20030023684 | Brown et al. | Jan 2003 | A1 |
| 20030028382 | Chambers et al. | Feb 2003 | A1 |
| 20030040813 | Gonzales et al. | Feb 2003 | A1 |
| 20030063130 | Barbieri et al. | Apr 2003 | A1 |
| 20030073496 | D'amico et al. | Apr 2003 | A1 |
| 20030078833 | Suzuki et al. | Apr 2003 | A1 |
| 20030093790 | Logan et al. | May 2003 | A1 |
| 20030110511 | Schutte et al. | Jun 2003 | A1 |
| 20030112938 | Kanakubo et al. | Jun 2003 | A1 |
| 20030120957 | Pathiyal | Jun 2003 | A1 |
| 20030158886 | Walls et al. | Aug 2003 | A1 |
| 20030160861 | Barlow et al. | Aug 2003 | A1 |
| 20030162554 | Kim | Aug 2003 | A1 |
| 20030225836 | Lee et al. | Dec 2003 | A1 |
| 20030229722 | Beyda | Dec 2003 | A1 |
| 20040003040 | Beavers et al. | Jan 2004 | A1 |
| 20040003051 | Krzyzanowski et al. | Jan 2004 | A1 |
| 20040015548 | Lee et al. | Jan 2004 | A1 |
| 20040015553 | Griffin et al. | Jan 2004 | A1 |
| 20040032955 | Hashimoto et al. | Feb 2004 | A1 |
| 20040048601 | Lee et al. | Mar 2004 | A1 |
| 20040048612 | Virtanen et al. | Mar 2004 | A1 |
| 20040070511 | Kim | Apr 2004 | A1 |
| 20040078444 | Malik et al. | Apr 2004 | A1 |
| 20040078446 | Daniell et al. | Apr 2004 | A1 |
| 20040095377 | Salandro | May 2004 | A1 |
| 20040102225 | Furuta et al. | May 2004 | A1 |
| 20040119740 | Chang et al. | Jun 2004 | A1 |
| 20040131254 | Liang et al. | Jul 2004 | A1 |
| 20040172455 | Green et al. | Sep 2004 | A1 |
| 20040202117 | Wilson et al. | Oct 2004 | A1 |
| 20040208301 | Urban et al. | Oct 2004 | A1 |
| 20040218035 | Crook | Nov 2004 | A1 |
| 20040225502 | Bear et al. | Nov 2004 | A1 |
| 20040239692 | Balle et al. | Dec 2004 | A1 |
| 20040239763 | Notea et al. | Dec 2004 | A1 |
| 20040248598 | Ding et al. | Dec 2004 | A1 |
| 20040261010 | Matsuishi | Dec 2004 | A1 |
| 20040264916 | Van et al. | Dec 2004 | A1 |
| 20050004990 | Durazo et al. | Jan 2005 | A1 |
| 20050015286 | Rudnik et al. | Jan 2005 | A1 |
| 20050041793 | Fulton et al. | Feb 2005 | A1 |
| 20050052458 | Lambert | Mar 2005 | A1 |
| 20050055412 | Kaminsky et al. | Mar 2005 | A1 |
| 20050055472 | Krzyzanowski et al. | Mar 2005 | A1 |
| 20050086605 | Ferrer et al. | Apr 2005 | A1 |
| 20050091314 | Blagsvedt et al. | Apr 2005 | A1 |
| 20050094610 | De et al. | May 2005 | A1 |
| 20050099492 | Orr | May 2005 | A1 |
| 20050114753 | Kumar et al. | May 2005 | A1 |
| 20050120306 | Klassen et al. | Jun 2005 | A1 |
| 20050124365 | Balasuriya et al. | Jun 2005 | A1 |
| 20050130631 | Maguire et al. | Jun 2005 | A1 |
| 20050138552 | Venolia | Jun 2005 | A1 |
| 20050143104 | Kim | Jun 2005 | A1 |
| 20050144247 | Christensen et al. | Jun 2005 | A1 |
| 20050144568 | Gruen et al. | Jun 2005 | A1 |
| 20050163345 | Van et al. | Jul 2005 | A1 |
| 20050169503 | Howell et al. | Aug 2005 | A1 |
| 20050181821 | Elomaa et al. | Aug 2005 | A1 |
| 20050188320 | Bocking | Aug 2005 | A1 |
| 20050191996 | Cha | Sep 2005 | A1 |
| 20050193345 | Klassen et al. | Sep 2005 | A1 |
| 20050198128 | Anderson et al. | Sep 2005 | A1 |
| 20050216568 | Walkush et al. | Sep 2005 | A1 |
| 20050223058 | Buchheit et al. | Oct 2005 | A1 |
| 20050223066 | Buchheit et al. | Oct 2005 | A1 |
| 20050223075 | Swearingen et al. | Oct 2005 | A1 |
| 20050233780 | Jani et al. | Oct 2005 | A1 |
| 20050233784 | You et al. | Oct 2005 | A1 |
| 20050262199 | Chen et al. | Nov 2005 | A1 |
| 20050266884 | Marriott et al. | Dec 2005 | A1 |
| 20050275626 | Mueller et al. | Dec 2005 | A1 |
| 20060002315 | Theurer et al. | Jan 2006 | A1 |
| 20060002523 | Bettis et al. | Jan 2006 | A1 |
| 20060005156 | Korpipää et al. | Jan 2006 | A1 |
| 20060009243 | Dahan et al. | Jan 2006 | A1 |
| 20060013554 | Poslinski et al. | Jan 2006 | A1 |
| 20060019639 | Adams et al. | Jan 2006 | A1 |
| 20060031775 | Sattler et al. | Feb 2006 | A1 |
| 20060034586 | Millar et al. | Feb 2006 | A1 |
| 20060044283 | Eri et al. | Mar 2006 | A1 |
| 20060053194 | Schneider et al. | Mar 2006 | A1 |
| 20060056837 | Vapaakoski | Mar 2006 | A1 |
| 20060075027 | Zager et al. | Apr 2006 | A1 |
| 20060084450 | Dam et al. | Apr 2006 | A1 |
| 20060085505 | Gillum et al. | Apr 2006 | A1 |
| 20060085515 | Kurtz et al. | Apr 2006 | A1 |
| 20060094416 | Endo et al. | May 2006 | A1 |
| 20060098085 | Nichols et al. | May 2006 | A1 |
| 20060098634 | Umemoto et al. | May 2006 | A1 |
| 20060123353 | Matthews et al. | Jun 2006 | A1 |
| 20060128404 | Klassen et al. | Jun 2006 | A1 |
| 20060132455 | Rimas-ribikauskas et al. | Jun 2006 | A1 |
| 20060135136 | Kim et al. | Jun 2006 | A1 |
| 20060149399 | Norhammar et al. | Jul 2006 | A1 |
| 20060158730 | Kira | Jul 2006 | A1 |
| 20060161621 | Rosenberg | Jul 2006 | A1 |
| 20060161629 | Cohen et al. | Jul 2006 | A1 |
| 20060161870 | Hotelling et al. | Jul 2006 | A1 |
| 20060161871 | Hotelling et al. | Jul 2006 | A1 |
| 20060171453 | Rohlfing et al. | Aug 2006 | A1 |
| 20060174035 | Tufail | Aug 2006 | A1 |
| 20060187897 | Dabbs et al. | Aug 2006 | A1 |
| 20060195787 | Topiwala et al. | Aug 2006 | A1 |
| 20060221184 | Vallone et al. | Oct 2006 | A1 |
| 20060256188 | Mock et al. | Nov 2006 | A1 |
| 20060258289 | Dua | Nov 2006 | A1 |
| 20060279628 | Fleming | Dec 2006 | A1 |
| 20060280186 | Carlton et al. | Dec 2006 | A1 |
| 20060286968 | Klassen et al. | Dec 2006 | A1 |
| 20070004389 | Wallace et al. | Jan 2007 | A1 |
| 20070004461 | Bathina et al. | Jan 2007 | A1 |
| 20070027682 | Bennett | Feb 2007 | A1 |
| 20070033632 | Baynger et al. | Feb 2007 | A1 |
| 20070037605 | Logan et al. | Feb 2007 | A1 |
| 20070040898 | Lee et al. | Feb 2007 | A1 |
| 20070050452 | Raju et al. | Mar 2007 | A1 |
| 20070053337 | Aoyama | Mar 2007 | A1 |
| 20070061020 | Bovee et al. | Mar 2007 | A1 |
| 20070064112 | Chatting et al. | Mar 2007 | A1 |
| 20070073823 | Cohen | Mar 2007 | A1 |
| 20070083623 | Nishimura et al. | Apr 2007 | A1 |
| 20070085157 | Fadell et al. | Apr 2007 | A1 |
| 20070093256 | Cha | Apr 2007 | A1 |
| 20070097083 | Seok et al. | May 2007 | A1 |
| 20070113294 | Field et al. | May 2007 | A1 |
| 20070115349 | Currivan et al. | May 2007 | A1 |
| 20070117549 | Arnos | May 2007 | A1 |
| 20070124403 | Umezawa et al. | May 2007 | A1 |
| 20070124783 | Ahiska et al. | May 2007 | A1 |
| 20070143415 | Daigle | Jun 2007 | A1 |
| 20070150834 | Muller et al. | Jun 2007 | A1 |
| 20070150836 | Deggelmann et al. | Jun 2007 | A1 |
| 20070157097 | Peters et al. | Jul 2007 | A1 |
| 20070157106 | Bishop | Jul 2007 | A1 |
| 20070162762 | Huh et al. | Jul 2007 | A1 |
| 20070173233 | Vander Veen et al. | Jul 2007 | A1 |
| 20070173267 | Klassen et al. | Jul 2007 | A1 |
| 20070174774 | Lerman et al. | Jul 2007 | A1 |
| 20070177025 | Kopet et al. | Aug 2007 | A1 |
| 20070191008 | Bucher et al. | Aug 2007 | A1 |
| 20070192486 | Wilson et al. | Aug 2007 | A1 |
| 20070198111 | Oetzel et al. | Aug 2007 | A1 |
| 20070198645 | Chen et al. | Aug 2007 | A1 |
| 20070203991 | Fisher et al. | Aug 2007 | A1 |
| 20070213099 | Bast | Sep 2007 | A1 |
| 20070216659 | Amineh | Sep 2007 | A1 |
| 20070224979 | Oneal et al. | Sep 2007 | A1 |
| 20070236475 | Wherry | Oct 2007 | A1 |
| 20070241945 | Moorer et al. | Oct 2007 | A1 |
| 20070243889 | Choi et al. | Oct 2007 | A1 |
| 20070264977 | Zinn et al. | Nov 2007 | A1 |
| 20070271527 | Paas et al. | Nov 2007 | A1 |
| 20070279482 | Oswald et al. | Dec 2007 | A1 |
| 20070291736 | Furlong et al. | Dec 2007 | A1 |
| 20070300140 | Makela et al. | Dec 2007 | A1 |
| 20080014989 | Sandegard et al. | Jan 2008 | A1 |
| 20080030496 | Lee et al. | Feb 2008 | A1 |
| 20080032704 | Oneil et al. | Feb 2008 | A1 |
| 20080036743 | Westerman et al. | Feb 2008 | A1 |
| 20080036849 | Oh et al. | Feb 2008 | A1 |
| 20080037722 | Klassen | Feb 2008 | A1 |
| 20080051065 | Hong | Feb 2008 | A1 |
| 20080052945 | Matas et al. | Mar 2008 | A1 |
| 20080055264 | Anzures et al. | Mar 2008 | A1 |
| 20080063389 | Fang et al. | Mar 2008 | A1 |
| 20080068447 | Mattila et al. | Mar 2008 | A1 |
| 20080070593 | Altman et al. | Mar 2008 | A1 |
| 20080074049 | Kitai et al. | Mar 2008 | A1 |
| 20080074550 | Park | Mar 2008 | A1 |
| 20080081558 | Dunko et al. | Apr 2008 | A1 |
| 20080084400 | Rosenberg | Apr 2008 | A1 |
| 20080084482 | Hansson et al. | Apr 2008 | A1 |
| 20080091717 | Garbow et al. | Apr 2008 | A1 |
| 20080094370 | Ording et al. | Apr 2008 | A1 |
| 20080114849 | Yuyama | May 2008 | A1 |
| 20080117876 | Hidaka et al. | May 2008 | A1 |
| 20080120427 | Ramanathan et al. | May 2008 | A1 |
| 20080122794 | Koiso et al. | May 2008 | A1 |
| 20080122796 | Jobs et al. | May 2008 | A1 |
| 20080126935 | Blomgren | May 2008 | A1 |
| 20080129816 | Mattila et al. | Jun 2008 | A1 |
| 20080129844 | Cusack et al. | Jun 2008 | A1 |
| 20080133336 | Altman et al. | Jun 2008 | A1 |
| 20080146289 | Korneluk et al. | Jun 2008 | A1 |
| 20080153459 | Kansal et al. | Jun 2008 | A1 |
| 20080155474 | Duhig et al. | Jun 2008 | A1 |
| 20080162649 | Lee et al. | Jul 2008 | A1 |
| 20080163127 | Newell et al. | Jul 2008 | A1 |
| 20080165136 | Christie et al. | Jul 2008 | A1 |
| 20080165160 | Kocienda et al. | Jul 2008 | A1 |
| 20080165388 | Serlet | Jul 2008 | A1 |
| 20080168185 | Robbin et al. | Jul 2008 | A1 |
| 20080171535 | Carmody et al. | Jul 2008 | A1 |
| 20080178175 | Woundy et al. | Jul 2008 | A1 |
| 20080215698 | Baratakke et al. | Sep 2008 | A1 |
| 20080216022 | Lorch et al. | Sep 2008 | A1 |
| 20080246778 | Ham et al. | Oct 2008 | A1 |
| 20080250319 | Lee et al. | Oct 2008 | A1 |
| 20080256190 | Ryan et al. | Oct 2008 | A1 |
| 20080261569 | Britt et al. | Oct 2008 | A1 |
| 20080262715 | Geelen et al. | Oct 2008 | A1 |
| 20080268901 | Miramontes et al. | Oct 2008 | A1 |
| 20080270560 | Tysowski et al. | Oct 2008 | A1 |
| 20080273712 | Eichfeld et al. | Nov 2008 | A1 |
| 20080273713 | Hartung et al. | Nov 2008 | A1 |
| 20080285772 | Haulick et al. | Nov 2008 | A1 |
| 20080307305 | Klassen et al. | Dec 2008 | A1 |
| 20080310602 | Bhupati | Dec 2008 | A1 |
| 20080313278 | Hochberg | Dec 2008 | A1 |
| 20080316295 | King et al. | Dec 2008 | A1 |
| 20080319782 | Good | Dec 2008 | A1 |
| 20090002335 | Chaudhri | Jan 2009 | A1 |
| 20090003552 | Goldman et al. | Jan 2009 | A1 |
| 20090003620 | Mckillop et al. | Jan 2009 | A1 |
| 20090005011 | Christie et al. | Jan 2009 | A1 |
| 20090005089 | Paik et al. | Jan 2009 | A1 |
| 20090007017 | Anzures et al. | Jan 2009 | A1 |
| 20090007188 | Omernick | Jan 2009 | A1 |
| 20090031245 | Brezina et al. | Jan 2009 | A1 |
| 20090037536 | Braam | Feb 2009 | A1 |
| 20090042607 | Adachi et al. | Feb 2009 | A1 |
| 20090046075 | Kim et al. | Feb 2009 | A1 |
| 20090049446 | Merten et al. | Feb 2009 | A1 |
| 20090049502 | Levien et al. | Feb 2009 | A1 |
| 20090051648 | Shamaie et al. | Feb 2009 | A1 |
| 20090055377 | Hedge et al. | Feb 2009 | A1 |
| 20090055383 | Zalewski | Feb 2009 | A1 |
| 20090059922 | Appelman et al. | Mar 2009 | A1 |
| 20090061837 | Chaudhri et al. | Mar 2009 | A1 |
| 20090066648 | Kerr et al. | Mar 2009 | A1 |
| 20090082043 | Lazaridis | Mar 2009 | A1 |
| 20090088204 | Culbert et al. | Apr 2009 | A1 |
| 20090093273 | Dietrich | Apr 2009 | A1 |
| 20090106376 | Tom et al. | Apr 2009 | A1 |
| 20090109276 | Kim | Apr 2009 | A1 |
| 20090117936 | Maeng | May 2009 | A1 |
| 20090125571 | Kiilerich et al. | May 2009 | A1 |
| 20090133070 | Hamano et al. | May 2009 | A1 |
| 20090138828 | Schultz et al. | May 2009 | A1 |
| 20090144391 | Jung et al. | Jun 2009 | A1 |
| 20090153289 | Hope et al. | Jun 2009 | A1 |
| 20090164219 | Yeung et al. | Jun 2009 | A1 |
| 20090164322 | Khan et al. | Jun 2009 | A1 |
| 20090164587 | Gavita et al. | Jun 2009 | A1 |
| 20090174763 | Bengtsson et al. | Jul 2009 | A1 |
| 20090175425 | Lee | Jul 2009 | A1 |
| 20090176517 | Christie et al. | Jul 2009 | A1 |
| 20090183125 | Magal et al. | Jul 2009 | A1 |
| 20090187842 | Collins et al. | Jul 2009 | A1 |
| 20090199119 | Park et al. | Aug 2009 | A1 |
| 20090199130 | Tsern et al. | Aug 2009 | A1 |
| 20090209293 | Louch | Aug 2009 | A1 |
| 20090220206 | Kisliakov | Sep 2009 | A1 |
| 20090228820 | Kim et al. | Sep 2009 | A1 |
| 20090228825 | Van Os et al. | Sep 2009 | A1 |
| 20090228938 | White et al. | Sep 2009 | A1 |
| 20090232028 | Baalbergen et al. | Sep 2009 | A1 |
| 20090232129 | Wong et al. | Sep 2009 | A1 |
| 20090248751 | Myman et al. | Oct 2009 | A1 |
| 20090249244 | Robinson et al. | Oct 2009 | A1 |
| 20090256780 | Small et al. | Oct 2009 | A1 |
| 20090262200 | Takabatake et al. | Oct 2009 | A1 |
| 20090262206 | Park | Oct 2009 | A1 |
| 20090265643 | Jachner et al. | Oct 2009 | A1 |
| 20090282362 | Matsumoto | Nov 2009 | A1 |
| 20090287790 | Upton et al. | Nov 2009 | A1 |
| 20090299810 | Jardine et al. | Dec 2009 | A1 |
| 20090304205 | Hardacker et al. | Dec 2009 | A1 |
| 20090305679 | Kim | Dec 2009 | A1 |
| 20090309897 | Morita et al. | Dec 2009 | A1 |
| 20090313582 | Rupsingh et al. | Dec 2009 | A1 |
| 20100004031 | Kim | Jan 2010 | A1 |
| 20100009719 | Oh et al. | Jan 2010 | A1 |
| 20100011065 | Scherpa et al. | Jan 2010 | A1 |
| 20100017474 | Kandekar et al. | Jan 2010 | A1 |
| 20100039498 | Liu et al. | Feb 2010 | A1 |
| 20100040292 | Clarkson | Feb 2010 | A1 |
| 20100053212 | Kang et al. | Mar 2010 | A1 |
| 20100054497 | Bull et al. | Mar 2010 | A1 |
| 20100058253 | Son | Mar 2010 | A1 |
| 20100069104 | Neil et al. | Mar 2010 | A1 |
| 20100070490 | Amidon et al. | Mar 2010 | A1 |
| 20100073454 | Lovhaugen et al. | Mar 2010 | A1 |
| 20100073455 | Iwabuchi et al. | Mar 2010 | A1 |
| 20100081375 | Rosenblatt et al. | Apr 2010 | A1 |
| 20100085416 | Hegde et al. | Apr 2010 | A1 |
| 20100087230 | Peh et al. | Apr 2010 | A1 |
| 20100094809 | Consul et al. | Apr 2010 | A1 |
| 20100097438 | Ujii | Apr 2010 | A1 |
| 20100106647 | Raman | Apr 2010 | A1 |
| 20100121636 | Burke et al. | May 2010 | A1 |
| 20100124906 | Hautala | May 2010 | A1 |
| 20100138007 | Clark et al. | Jun 2010 | A1 |
| 20100145485 | Duchene et al. | Jun 2010 | A1 |
| 20100162138 | Pascal et al. | Jun 2010 | A1 |
| 20100162171 | Felt et al. | Jun 2010 | A1 |
| 20100169435 | Osullivan et al. | Jul 2010 | A1 |
| 20100177156 | Kim et al. | Jul 2010 | A1 |
| 20100178873 | Lee et al. | Jul 2010 | A1 |
| 20100189096 | Flynn et al. | Jul 2010 | A1 |
| 20100191575 | Raleigh | Jul 2010 | A1 |
| 20100191833 | Hofrichter et al. | Jul 2010 | A1 |
| 20100201815 | Anderson et al. | Aug 2010 | A1 |
| 20100205563 | Haapsaari et al. | Aug 2010 | A1 |
| 20100235729 | Kocienda et al. | Sep 2010 | A1 |
| 20100235746 | Anzures et al. | Sep 2010 | A1 |
| 20100247077 | Yamamoto et al. | Sep 2010 | A1 |
| 20100251119 | Geppert et al. | Sep 2010 | A1 |
| 20100251158 | Geppert et al. | Sep 2010 | A1 |
| 20100251304 | Donoghue et al. | Sep 2010 | A1 |
| 20100259482 | Ball | Oct 2010 | A1 |
| 20100262714 | Hile | Oct 2010 | A1 |
| 20100267370 | Lee | Oct 2010 | A1 |
| 20100273456 | Wolovitz et al. | Oct 2010 | A1 |
| 20100277579 | Cho et al. | Nov 2010 | A1 |
| 20100279663 | Wang et al. | Nov 2010 | A1 |
| 20100280983 | Cho et al. | Nov 2010 | A1 |
| 20100284389 | Ramsay et al. | Nov 2010 | A1 |
| 20100287249 | Mgang et al. | Nov 2010 | A1 |
| 20100293598 | Collart et al. | Nov 2010 | A1 |
| 20100296678 | Kuhn-rahloff et al. | Nov 2010 | A1 |
| 20100299639 | Ramsay et al. | Nov 2010 | A1 |
| 20100309284 | Samadani 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 |
| 20100332518 | Song et al. | Dec 2010 | A1 |
| 20110030324 | Higgins | Feb 2011 | A1 |
| 20110032324 | George et al. | Feb 2011 | A1 |
| 20110040754 | Peto et al. | Feb 2011 | A1 |
| 20110040760 | Fleischman et al. | Feb 2011 | A1 |
| 20110054830 | Logan | Mar 2011 | A1 |
| 20110071656 | Mckiel, Jr. | Mar 2011 | A1 |
| 20110080356 | Kang et al. | Apr 2011 | A1 |
| 20110085017 | Robinson et al. | Apr 2011 | A1 |
| 20110092190 | Willey et al. | Apr 2011 | A1 |
| 20110106279 | Cho et al. | May 2011 | A1 |
| 20110107216 | Bi | May 2011 | A1 |
| 20110115875 | Sadwick et al. | May 2011 | A1 |
| 20110117898 | Pereira et al. | May 2011 | A1 |
| 20110126148 | Krishnaraj et al. | May 2011 | A1 |
| 20110138284 | Wigdor et al. | Jun 2011 | A1 |
| 20110145745 | Hyeon et al. | Jun 2011 | A1 |
| 20110159469 | Hwang et al. | Jun 2011 | A1 |
| 20110159927 | Choi | Jun 2011 | A1 |
| 20110161836 | Mu et al. | Jun 2011 | A1 |
| 20110164032 | Shadmi | Jul 2011 | A1 |
| 20110164058 | Lemay | Jul 2011 | A1 |
| 20110173545 | Meola et al. | Jul 2011 | A1 |
| 20110193995 | Goh et al. | Aug 2011 | A1 |
| 20110205333 | Wu et al. | Aug 2011 | A1 |
| 20110228084 | Colciago | Sep 2011 | A1 |
| 20110234746 | Saleh et al. | Sep 2011 | A1 |
| 20110235549 | Ahlers et al. | Sep 2011 | A1 |
| 20110242002 | Kaplan et al. | Oct 2011 | A1 |
| 20110242356 | Aleksic et al. | Oct 2011 | A1 |
| 20110246942 | Misawa | Oct 2011 | A1 |
| 20110249073 | Cranfill et al. | Oct 2011 | A1 |
| 20110249074 | Cranfill et al. | Oct 2011 | A1 |
| 20110249086 | Guo et al. | Oct 2011 | A1 |
| 20110249861 | Tokutake | Oct 2011 | A1 |
| 20110252146 | Santamaria et al. | Oct 2011 | A1 |
| 20110252357 | Chaudhri | Oct 2011 | A1 |
| 20110254683 | Soldan et al. | Oct 2011 | A1 |
| 20110273526 | Mehin et al. | Nov 2011 | A1 |
| 20110276901 | Zambetti et al. | Nov 2011 | A1 |
| 20110283334 | Choi et al. | Nov 2011 | A1 |
| 20110291971 | Masaki et al. | Dec 2011 | A1 |
| 20110296163 | Abernethy et al. | Dec 2011 | A1 |
| 20110304648 | Kim et al. | Dec 2011 | A1 |
| 20110316769 | Boettcher et al. | Dec 2011 | A1 |
| 20120002001 | Prentice | Jan 2012 | A1 |
| 20120004920 | Kelly et al. | Jan 2012 | A1 |
| 20120019610 | Hornyak et al. | Jan 2012 | A1 |
| 20120022872 | Gruber et al. | Jan 2012 | A1 |
| 20120033028 | Murphy et al. | Feb 2012 | A1 |
| 20120038546 | Cromer et al. | Feb 2012 | A1 |
| 20120050185 | Davydov et al. | Mar 2012 | A1 |
| 20120051560 | Sanders | Mar 2012 | A1 |
| 20120054278 | Taleb et al. | Mar 2012 | A1 |
| 20120054655 | Kang et al. | Mar 2012 | A1 |
| 20120060077 | Mate et al. | Mar 2012 | A1 |
| 20120062784 | Van et al. | Mar 2012 | A1 |
| 20120066632 | Sundermeyer et al. | Mar 2012 | A1 |
| 20120070129 | Lin et al. | Mar 2012 | A1 |
| 20120092436 | Pahud et al. | Apr 2012 | A1 |
| 20120098854 | Ohnishi | Apr 2012 | A1 |
| 20120110455 | Sharma et al. | May 2012 | A1 |
| 20120114108 | Katis et al. | May 2012 | A1 |
| 20120115608 | Pfeifer et al. | May 2012 | A1 |
| 20120131458 | Hayes et al. | May 2012 | A1 |
| 20120143361 | Kurabayashi et al. | Jun 2012 | A1 |
| 20120144416 | Wetzer et al. | Jun 2012 | A1 |
| 20120149405 | Bhat | Jun 2012 | A1 |
| 20120157114 | Alameh et al. | Jun 2012 | A1 |
| 20120169583 | Rippel et al. | Jul 2012 | A1 |
| 20120173383 | Badawiyeh et al. | Jul 2012 | A1 |
| 20120173767 | Kim et al. | Jul 2012 | A1 |
| 20120177339 | Chang et al. | Jul 2012 | A1 |
| 20120178431 | Gold | Jul 2012 | A1 |
| 20120182381 | Abate et al. | Jul 2012 | A1 |
| 20120185355 | Kilroy | Jul 2012 | A1 |
| 20120185547 | Hugg et al. | Jul 2012 | A1 |
| 20120188394 | Park et al. | Jul 2012 | A1 |
| 20120197419 | Dhruv et al. | Aug 2012 | A1 |
| 20120198017 | Levasseur et al. | Aug 2012 | A1 |
| 20120201479 | Zhang et al. | Aug 2012 | A1 |
| 20120210226 | Mccoy et al. | 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 |
| 20120229591 | Lee | Sep 2012 | A1 |
| 20120233571 | Wever et al. | Sep 2012 | A1 |
| 20120254324 | Majeti et al. | Oct 2012 | A1 |
| 20120254325 | Majeti et al. | Oct 2012 | A1 |
| 20120260169 | Schwartz et al. | Oct 2012 | A1 |
| 20120266199 | Noonan et al. | Oct 2012 | A1 |
| 20120269361 | Bhow et al. | Oct 2012 | A1 |
| 20120272230 | Lee | Oct 2012 | A1 |
| 20120282974 | Green et al. | Nov 2012 | A1 |
| 20120293605 | Seferian et al. | Nov 2012 | A1 |
| 20120294118 | Haulick et al. | Nov 2012 | A1 |
| 20120296972 | Backer | Nov 2012 | A1 |
| 20120304079 | Rideout et al. | Nov 2012 | A1 |
| 20120306770 | Moore et al. | Dec 2012 | A1 |
| 20120311444 | Chaudhri | Dec 2012 | A1 |
| 20120311499 | Dellinger et al. | Dec 2012 | A1 |
| 20120313847 | Boda et al. | Dec 2012 | A1 |
| 20120320141 | Bowen et al. | Dec 2012 | A1 |
| 20130007617 | Mackenzie et al. | Jan 2013 | A1 |
| 20130022221 | Kallai et al. | Jan 2013 | A1 |
| 20130026293 | Schneider et al. | Jan 2013 | A1 |
| 20130027289 | Choi et al. | Jan 2013 | A1 |
| 20130035942 | Kim et al. | Feb 2013 | A1 |
| 20130047084 | Sanders et al. | Feb 2013 | A1 |
| 20130051755 | Brown et al. | Feb 2013 | A1 |
| 20130053007 | Cosman et al. | Feb 2013 | A1 |
| 20130053107 | Kang et al. | Feb 2013 | A1 |
| 20130055113 | Chazin et al. | Feb 2013 | A1 |
| 20130055150 | Galor | Feb 2013 | A1 |
| 20130060352 | Kouda et al. | Mar 2013 | A1 |
| 20130061155 | Hon | Mar 2013 | A1 |
| 20130067027 | Song et al. | Mar 2013 | A1 |
| 20130070046 | Wolf et al. | Mar 2013 | A1 |
| 20130073584 | Kuper et al. | Mar 2013 | A1 |
| 20130080516 | Bologh | Mar 2013 | A1 |
| 20130080955 | Reimann et al. | Mar 2013 | A1 |
| 20130088413 | Raffle et al. | Apr 2013 | A1 |
| 20130091298 | Ozzie et al. | Apr 2013 | A1 |
| 20130091443 | Park et al. | Apr 2013 | A1 |
| 20130093833 | Al-asaaed et al. | Apr 2013 | A1 |
| 20130094666 | Haaff et al. | Apr 2013 | A1 |
| 20130094770 | Lee et al. | Apr 2013 | A1 |
| 20130099672 | Lin et al. | Apr 2013 | A1 |
| 20130111603 | Sakai et al. | May 2013 | A1 |
| 20130113822 | Putrevu et al. | May 2013 | A1 |
| 20130117693 | Anderson et al. | May 2013 | A1 |
| 20130124207 | Sarin | May 2013 | A1 |
| 20130124997 | Speir et al. | May 2013 | A1 |
| 20130132865 | Li | May 2013 | A1 |
| 20130138272 | Louise-babando et al. | May 2013 | A1 |
| 20130141223 | Brandsma et al. | Jun 2013 | A1 |
| 20130141378 | Yumiki et al. | Jun 2013 | A1 |
| 20130151623 | Weiser et al. | Jun 2013 | A1 |
| 20130159858 | Joffray et al. | Jun 2013 | A1 |
| 20130162411 | Moses et al. | Jun 2013 | A1 |
| 20130162781 | Hubner et al. | Jun 2013 | A1 |
| 20130166580 | Maharajh et al. | Jun 2013 | A1 |
| 20130169742 | Wu et al. | Jul 2013 | A1 |
| 20130173794 | Agerbak et al. | Jul 2013 | A1 |
| 20130191454 | Oliver et al. | Jul 2013 | A1 |
| 20130194476 | Shimosato | Aug 2013 | A1 |
| 20130205375 | Woxblom et al. | Aug 2013 | A1 |
| 20130212470 | Karunamuni et al. | Aug 2013 | A1 |
| 20130216206 | Dubin et al. | Aug 2013 | A1 |
| 20130219276 | Shan | Aug 2013 | A1 |
| 20130222230 | Choi et al. | Aug 2013 | A1 |
| 20130225140 | Greisson | Aug 2013 | A1 |
| 20130225152 | Matthews et al. | Aug 2013 | A1 |
| 20130227414 | Hwang et al. | Aug 2013 | A1 |
| 20130234924 | Janefalkar et al. | Sep 2013 | A1 |
| 20130243924 | Bhandari et al. | Sep 2013 | A1 |
| 20130246522 | Bilinski et al. | Sep 2013 | A1 |
| 20130246916 | Reimann et al. | Sep 2013 | A1 |
| 20130254714 | Shin et al. | Sep 2013 | A1 |
| 20130259247 | Kim | Oct 2013 | A1 |
| 20130262298 | Morley et al. | Oct 2013 | A1 |
| 20130268593 | Parekh | Oct 2013 | A1 |
| 20130275881 | Hahm et al. | Oct 2013 | A1 |
| 20130282180 | Layton | Oct 2013 | A1 |
| 20130282844 | Logan et al. | Oct 2013 | A1 |
| 20130283161 | Reimann et al. | Oct 2013 | A1 |
| 20130298021 | Park et al. | Nov 2013 | A1 |
| 20130301482 | Katis et al. | Nov 2013 | A1 |
| 20130305354 | King et al. | Nov 2013 | A1 |
| 20130310089 | Gianoukos et al. | Nov 2013 | A1 |
| 20130322634 | Bennett et al. | Dec 2013 | A1 |
| 20130324081 | Gargi et al. | Dec 2013 | A1 |
| 20130325949 | Virani et al. | Dec 2013 | A1 |
| 20130328770 | Parham | Dec 2013 | A1 |
| 20130329924 | Fleizach et al. | Dec 2013 | A1 |
| 20130331083 | Oslund | Dec 2013 | A1 |
| 20130332856 | Sanders et al. | Dec 2013 | A1 |
| 20130346859 | Bates et al. | Dec 2013 | A1 |
| 20130347022 | Bates et al. | Dec 2013 | A1 |
| 20140012927 | Gertzfield et al. | Jan 2014 | A1 |
| 20140013243 | Flynn et al. | Jan 2014 | A1 |
| 20140018053 | Cho et al. | Jan 2014 | A1 |
| 20140024340 | Raleigh | Jan 2014 | A1 |
| 20140025798 | Apte et al. | Jan 2014 | A1 |
| 20140026074 | Cortes et al. | Jan 2014 | A1 |
| 20140032682 | Prado et al. | Jan 2014 | A1 |
| 20140037107 | Marino 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 |
| 20140049447 | Choi | Feb 2014 | A1 |
| 20140053281 | Benoit et al. | Feb 2014 | A1 |
| 20140055552 | Song et al. | Feb 2014 | A1 |
| 20140059448 | Lee | Feb 2014 | A1 |
| 20140063176 | Modai et al. | Mar 2014 | A1 |
| 20140068439 | Lacaze et al. | Mar 2014 | A1 |
| 20140068486 | Sellers et al. | Mar 2014 | A1 |
| 20140070959 | Bhargava et al. | Mar 2014 | A1 |
| 20140075311 | Boettcher et al. | Mar 2014 | A1 |
| 20140075321 | Masera | Mar 2014 | A1 |
| 20140080416 | Seo et al. | Mar 2014 | A1 |
| 20140082501 | Bae et al. | Mar 2014 | A1 |
| 20140085487 | Park et al. | Mar 2014 | A1 |
| 20140092292 | Kuznetsov et al. | Apr 2014 | A1 |
| 20140099004 | Dibona et al. | Apr 2014 | A1 |
| 20140105372 | Nowack et al. | Apr 2014 | A1 |
| 20140108084 | Bargetzi et al. | Apr 2014 | A1 |
| 20140108568 | Lee | Apr 2014 | A1 |
| 20140114966 | Bilinski et al. | Apr 2014 | A1 |
| 20140136989 | Choi | May 2014 | A1 |
| 20140136990 | Gonnen et al. | May 2014 | A1 |
| 20140143737 | Mistry et al. | May 2014 | A1 |
| 20140150029 | Avedissian et al. | May 2014 | A1 |
| 20140155123 | Lee et al. | Jun 2014 | A1 |
| 20140171156 | Pattikonda et al. | Jun 2014 | A1 |
| 20140173082 | Shin | Jun 2014 | A1 |
| 20140176298 | Kumar et al. | Jun 2014 | A1 |
| 20140181202 | Gossain | Jun 2014 | A1 |
| 20140181654 | Kumar et al. | Jun 2014 | A1 |
| 20140181658 | Kumar et al. | Jun 2014 | A1 |
| 20140201126 | Zadeh et al. | Jul 2014 | A1 |
| 20140201632 | Kunigita et al. | Jul 2014 | A1 |
| 20140207707 | Na et al. | Jul 2014 | A1 |
| 20140215356 | Brander et al. | Jul 2014 | A1 |
| 20140215365 | Hiraga et al. | Jul 2014 | A1 |
| 20140215404 | Kong et al. | Jul 2014 | A1 |
| 20140218371 | Du et al. | Aug 2014 | A1 |
| 20140218461 | Deland | Aug 2014 | A1 |
| 20140218517 | Kim | Aug 2014 | A1 |
| 20140222933 | Stovicek et al. | Aug 2014 | A1 |
| 20140229835 | Ravine | Aug 2014 | A1 |
| 20140232273 | Sasaki et al. | Aug 2014 | A1 |
| 20140236325 | Sasaki et al. | Aug 2014 | A1 |
| 20140237361 | Martin et al. | Aug 2014 | A1 |
| 20140237419 | Ryu | Aug 2014 | A1 |
| 20140240122 | Roberts et al. | Aug 2014 | A1 |
| 20140247368 | Chinn | Sep 2014 | A1 |
| 20140257532 | Kim et al. | Sep 2014 | A1 |
| 20140258854 | Li | Sep 2014 | A1 |
| 20140267002 | Luna | Sep 2014 | A1 |
| 20140267068 | Smith et al. | Sep 2014 | A1 |
| 20140267549 | Pinter et al. | Sep 2014 | A1 |
| 20140267911 | Grant et al. | Sep 2014 | A1 |
| 20140270183 | Luna | Sep 2014 | A1 |
| 20140274211 | Sejnoha et al. | Sep 2014 | A1 |
| 20140278435 | Ganong, III et al. | Sep 2014 | A1 |
| 20140280812 | Bealkowski et al. | Sep 2014 | A1 |
| 20140285017 | Noguchi et al. | Sep 2014 | A1 |
| 20140293046 | Ni | Oct 2014 | A1 |
| 20140313032 | Sager et al. | Oct 2014 | A1 |
| 20140331149 | Labey | Nov 2014 | A1 |
| 20140334644 | Selig et al. | Nov 2014 | A1 |
| 20140335789 | Cohen et al. | Nov 2014 | A1 |
| 20140337791 | Agnetta et al. | Nov 2014 | A1 |
| 20140344687 | Durham et al. | Nov 2014 | A1 |
| 20140344711 | Hallerstrom Sjostedt et al. | Nov 2014 | A1 |
| 20140349754 | Kaneoka et al. | Nov 2014 | A1 |
| 20140354527 | Chen et al. | Dec 2014 | A1 |
| 20140354759 | Cranfill et al. | Dec 2014 | A1 |
| 20140359524 | Sasaki et al. | Dec 2014 | A1 |
| 20140362293 | Bakar et al. | Dec 2014 | A1 |
| 20140363024 | Apodaca | Dec 2014 | A1 |
| 20140364056 | Belk et al. | Dec 2014 | A1 |
| 20140365226 | Sinha | Dec 2014 | A1 |
| 20140365904 | Kim et al. | Dec 2014 | A1 |
| 20140365980 | Morrison et al. | Dec 2014 | A1 |
| 20140368547 | Elings | Dec 2014 | A1 |
| 20140368719 | Kaneko et al. | Dec 2014 | A1 |
| 20140373081 | Dodson et al. | Dec 2014 | A1 |
| 20140375747 | Martinez et al. | Dec 2014 | A1 |
| 20140375819 | Larsen et al. | Dec 2014 | A1 |
| 20140380234 | Shim et al. | Dec 2014 | A1 |
| 20150008845 | Kim et al. | Jan 2015 | A1 |
| 20150010167 | Arling et al. | Jan 2015 | A1 |
| 20150032457 | Koo et al. | Jan 2015 | A1 |
| 20150032812 | Dudley | Jan 2015 | A1 |
| 20150033149 | Kuchoor | Jan 2015 | A1 |
| 20150033361 | Choi et al. | Jan 2015 | A1 |
| 20150040012 | Faaborg | Feb 2015 | A1 |
| 20150040029 | Koum et al. | Feb 2015 | A1 |
| 20150042576 | Wang | Feb 2015 | A1 |
| 20150042852 | Lee et al. | Feb 2015 | A1 |
| 20150052222 | Farrell et al. | Feb 2015 | A1 |
| 20150058413 | Ge | Feb 2015 | A1 |
| 20150058780 | Malik et al. | Feb 2015 | A1 |
| 20150062158 | Hildreth et al. | Mar 2015 | A1 |
| 20150067541 | Owens et al. | Mar 2015 | A1 |
| 20150067803 | Alduaiji | Mar 2015 | A1 |
| 20150070272 | Kim et al. | Mar 2015 | A1 |
| 20150071601 | Dabous et al. | Mar 2015 | A1 |
| 20150078680 | Shakib et al. | Mar 2015 | A1 |
| 20150081072 | Kallai et al. | Mar 2015 | A1 |
| 20150082225 | Shearer | Mar 2015 | A1 |
| 20150085057 | Ouyang et al. | Mar 2015 | A1 |
| 20150089359 | Brisebois | Mar 2015 | A1 |
| 20150092009 | Deluca et al. | Apr 2015 | A1 |
| 20150092520 | Robison et al. | Apr 2015 | A1 |
| 20150095804 | Grossman et al. | Apr 2015 | A1 |
| 20150095937 | Tobin | Apr 2015 | A1 |
| 20150100623 | Gudell et al. | Apr 2015 | A1 |
| 20150106720 | Backer | Apr 2015 | A1 |
| 20150106721 | Cha et al. | Apr 2015 | A1 |
| 20150113407 | Hoffert et al. | Apr 2015 | A1 |
| 20150113418 | Sasaki et al. | Apr 2015 | A1 |
| 20150116353 | Miura et al. | Apr 2015 | A1 |
| 20150116363 | Monte et al. | Apr 2015 | A1 |
| 20150120768 | Wellen et al. | Apr 2015 | A1 |
| 20150130737 | Im et al. | May 2015 | A1 |
| 20150135049 | Murphy | May 2015 | A1 |
| 20150135068 | Chiu | May 2015 | A1 |
| 20150135098 | Geppert et al. | May 2015 | A1 |
| 20150138101 | Park et al. | May 2015 | A1 |
| 20150142587 | Salgar et al. | May 2015 | A1 |
| 20150145435 | Ogawa | May 2015 | A1 |
| 20150146945 | Han | May 2015 | A1 |
| 20150147067 | Ryan et al. | May 2015 | A1 |
| 20150149599 | Caunter et al. | May 2015 | A1 |
| 20150159895 | Quam et al. | Jun 2015 | A1 |
| 20150160797 | Shearer et al. | Jun 2015 | A1 |
| 20150169893 | Desai | Jun 2015 | A1 |
| 20150172393 | Oplinger et al. | Jun 2015 | A1 |
| 20150172584 | Park et al. | Jun 2015 | A1 |
| 20150177914 | Coyner et al. | Jun 2015 | A1 |
| 20150180922 | Draznin et al. | Jun 2015 | A1 |
| 20150188724 | Kim et al. | Jul 2015 | A1 |
| 20150188869 | Smilak et al. | Jul 2015 | A1 |
| 20150189426 | Pang | Jul 2015 | A1 |
| 20150193127 | Chai et al. | Jul 2015 | A1 |
| 20150193130 | Cho et al. | Jul 2015 | A1 |
| 20150193196 | Lin et al. | Jul 2015 | A1 |
| 20150198938 | Steele et al. | Jul 2015 | A1 |
| 20150200715 | Oiwa et al. | Jul 2015 | A1 |
| 20150201062 | Shih et al. | Jul 2015 | A1 |
| 20150201480 | Ogawa | Jul 2015 | A1 |
| 20150205511 | Vinna et al. | Jul 2015 | A1 |
| 20150205971 | Sanio et al. | Jul 2015 | A1 |
| 20150206529 | Kwon | Jul 2015 | A1 |
| 20150207849 | Bingzhou et al. | Jul 2015 | A1 |
| 20150212705 | Sasaki et al. | Jul 2015 | A1 |
| 20150215382 | Arora 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 |
| 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 |
| 20150244539 | Ickman et al. | Aug 2015 | A1 |
| 20150248167 | Turbell et al. | Sep 2015 | A1 |
| 20150248268 | Kumar et al. | Sep 2015 | A1 |
| 20150253960 | Lin et al. | Sep 2015 | A1 |
| 20150256796 | Ma | Sep 2015 | A1 |
| 20150256957 | Kim et al. | Sep 2015 | A1 |
| 20150261493 | Lemmon et al. | Sep 2015 | A1 |
| 20150264004 | Khoo | Sep 2015 | A1 |
| 20150264303 | Chastney et al. | Sep 2015 | A1 |
| 20150264304 | Chastney et al. | Sep 2015 | A1 |
| 20150271120 | Langholz | Sep 2015 | A1 |
| 20150286360 | Wachter | Oct 2015 | A1 |
| 20150288868 | Slavin et al. | Oct 2015 | A1 |
| 20150296077 | Wakeyama et al. | Oct 2015 | A1 |
| 20150301338 | Van Heugten | Oct 2015 | A1 |
| 20150304366 | Bader-Natal et al. | Oct 2015 | A1 |
| 20150304413 | Park | Oct 2015 | A1 |
| 20150309768 | Van Der Heide | Oct 2015 | A1 |
| 20150312184 | Langholz et al. | Oct 2015 | A1 |
| 20150312185 | Langholz et al. | Oct 2015 | A1 |
| 20150312299 | Chen | Oct 2015 | A1 |
| 20150319006 | Plummer et al. | Nov 2015 | A1 |
| 20150319046 | Plummer et al. | Nov 2015 | A1 |
| 20150319144 | Barton et al. | Nov 2015 | A1 |
| 20150324552 | Beckhardt | Nov 2015 | A1 |
| 20150326510 | Tomlinson et al. | Nov 2015 | A1 |
| 20150331881 | Myles | Nov 2015 | A1 |
| 20150332586 | Hamm et al. | Nov 2015 | A1 |
| 20150334140 | Singh et al. | Nov 2015 | A1 |
| 20150341227 | Tatzel et al. | Nov 2015 | A1 |
| 20150347086 | Liedholm et al. | Dec 2015 | A1 |
| 20150347738 | Ulrich et al. | Dec 2015 | A1 |
| 20150348493 | Chae et al. | Dec 2015 | A1 |
| 20150348548 | Piernot et al. | Dec 2015 | A1 |
| 20150350031 | Burks et al. | Dec 2015 | A1 |
| 20150350141 | Yang et al. | Dec 2015 | A1 |
| 20150350143 | Lemay et al. | Dec 2015 | A1 |
| 20150350533 | Harris 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 |
| 20150358484 | Permude | Dec 2015 | A1 |
| 20150358584 | Mattson | Dec 2015 | A1 |
| 20150365306 | Chaudhri et al. | Dec 2015 | A1 |
| 20150370230 | Duchene et al. | Dec 2015 | A1 |
| 20150370426 | Carrigan et al. | Dec 2015 | A1 |
| 20150370455 | Van Os et al. | Dec 2015 | A1 |
| 20150373065 | Holmquist 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 |
| 20160005280 | Laska et al. | Jan 2016 | A1 |
| 20160005281 | Laska et al. | Jan 2016 | A1 |
| 20160011850 | Sheen et al. | Jan 2016 | A1 |
| 20160014059 | Rathod | Jan 2016 | A1 |
| 20160014477 | Siders | Jan 2016 | A1 |
| 20160018872 | Tu et al. | Jan 2016 | A1 |
| 20160018899 | Tu et al. | Jan 2016 | A1 |
| 20160018900 | Tu et al. | Jan 2016 | A1 |
| 20160021155 | Sawato | Jan 2016 | A1 |
| 20160021603 | Mueck et al. | Jan 2016 | A1 |
| 20160026429 | Triplett | Jan 2016 | A1 |
| 20160029004 | Campbell et al. | Jan 2016 | A1 |
| 20160029146 | Tembey et al. | Jan 2016 | A1 |
| 20160033985 | Gulli' et al. | Feb 2016 | A1 |
| 20160036996 | Midholt et al. | Feb 2016 | A1 |
| 20160037140 | Lindsey et al. | Feb 2016 | A1 |
| 20160037436 | Spencer et al. | Feb 2016 | A1 |
| 20160041597 | Graham et al. | Feb 2016 | A1 |
| 20160043905 | Fiedler | Feb 2016 | A1 |
| 20160043962 | Kim et al. | Feb 2016 | A1 |
| 20160048705 | Yang | Feb 2016 | A1 |
| 20160050476 | Patil | Feb 2016 | A1 |
| 20160054841 | Yang et al. | Feb 2016 | A1 |
| 20160057173 | Singman 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 |
| 20160065832 | Kim et al. | Mar 2016 | A1 |
| 20160066277 | Yang et al. | Mar 2016 | A1 |
| 20160070244 | Cipollo et al. | Mar 2016 | A1 |
| 20160072861 | Woolsey et al. | Mar 2016 | A1 |
| 20160073185 | Kannappan et al. | Mar 2016 | A1 |
| 20160073197 | Hammer et al. | Mar 2016 | A1 |
| 20160073439 | Palin et al. | Mar 2016 | A1 |
| 20160073482 | Fok et al. | Mar 2016 | A1 |
| 20160077734 | Buxton et al. | Mar 2016 | A1 |
| 20160077794 | Kim et al. | Mar 2016 | A1 |
| 20160080552 | Keating et al. | Mar 2016 | A1 |
| 20160085412 | Meganathan et al. | Mar 2016 | A1 |
| 20160088039 | Millington et al. | Mar 2016 | A1 |
| 20160088146 | Mng et al. | Mar 2016 | A1 |
| 20160088438 | Okeeffe | Mar 2016 | A1 |
| 20160092072 | So et al. | Mar 2016 | A1 |
| 20160093180 | Fitzgibbon et al. | Mar 2016 | A1 |
| 20160093338 | Laska et al. | Mar 2016 | A1 |
| 20160099901 | Allen et al. | Apr 2016 | A1 |
| 20160099987 | Shamma | Apr 2016 | A1 |
| 20160103830 | Cheong et al. | Apr 2016 | A1 |
| 20160117402 | Gowel | Apr 2016 | A1 |
| 20160120009 | Aliakseyeu et al. | Apr 2016 | A1 |
| 20160127636 | Ito et al. | May 2016 | A1 |
| 20160127799 | Alsina et al. | May 2016 | A1 |
| 20160133297 | Thornton et al. | May 2016 | A1 |
| 20160134942 | Lo | May 2016 | A1 |
| 20160139752 | Shim et al. | May 2016 | A1 |
| 20160139785 | Griffin et al. | May 2016 | A1 |
| 20160142450 | Paul et al. | May 2016 | A1 |
| 20160142763 | Kim et al. | May 2016 | A1 |
| 20160150135 | Chen | 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 |
| 20160165390 | Hartzell et al. | Jun 2016 | A1 |
| 20160165600 | Choi et al. | Jun 2016 | A1 |
| 20160173318 | Ha et al. | Jun 2016 | A1 |
| 20160179068 | Qian et al. | Jun 2016 | A1 |
| 20160180259 | Marianko et al. | Jun 2016 | A1 |
| 20160183046 | Kwon | Jun 2016 | A1 |
| 20160187995 | Rosewall | Jun 2016 | A1 |
| 20160191992 | Kwon | 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 |
| 20160212374 | Usbergo et al. | Jul 2016 | A1 |
| 20160224233 | Phang et al. | Aug 2016 | A1 |
| 20160227095 | Yoshizawa et al. | Aug 2016 | A1 |
| 20160231902 | Sirpal et al. | Aug 2016 | A1 |
| 20160239167 | Reimann 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 |
| 20160255706 | Kim et al. | Sep 2016 | A1 |
| 20160259459 | Yang et al. | Sep 2016 | A1 |
| 20160259528 | Foss et al. | Sep 2016 | A1 |
| 20160260436 | Lemay et al. | Sep 2016 | A1 |
| 20160261653 | Kim | Sep 2016 | A1 |
| 20160261790 | Lee et al. | Sep 2016 | A1 |
| 20160267319 | Murillo et al. | Sep 2016 | A1 |
| 20160277708 | Rintel et al. | Sep 2016 | A1 |
| 20160277885 | Shan et al. | Sep 2016 | A1 |
| 20160277903 | Poosala et al. | Sep 2016 | A1 |
| 20160283194 | Patil et al. | Sep 2016 | A1 |
| 20160286630 | Witzgall | Sep 2016 | A1 |
| 20160291824 | Grossman et al. | Oct 2016 | A1 |
| 20160291924 | Bierbower et al. | Oct 2016 | A1 |
| 20160294958 | Zhang et al. | Oct 2016 | A1 |
| 20160295340 | Baker et al. | Oct 2016 | A1 |
| 20160299669 | Bates | Oct 2016 | A1 |
| 20160299736 | Bates et al. | Oct 2016 | A1 |
| 20160301566 | Ramasubramani et al. | Oct 2016 | A1 |
| 20160306422 | Parham et al. | Oct 2016 | A1 |
| 20160306504 | Brunsch et al. | Oct 2016 | A1 |
| 20160308920 | Brunsch et al. | Oct 2016 | A1 |
| 20160316038 | Jolfaei | Oct 2016 | A1 |
| 20160320849 | Koo | Nov 2016 | A1 |
| 20160335041 | Wachter et al. | Nov 2016 | A1 |
| 20160336531 | Yokoyama | Nov 2016 | A1 |
| 20160342386 | Kallai et al. | Nov 2016 | A1 |
| 20160345039 | Billmeyer | 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 |
| 20160364106 | Koum et al. | Dec 2016 | A1 |
| 20160364114 | Von Dehsen et al. | Dec 2016 | A1 |
| 20160364123 | Burns et al. | Dec 2016 | A1 |
| 20160364129 | Mclean 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 |
| 20160379633 | Lehman et al. | Dec 2016 | A1 |
| 20160380780 | Stephenson et al. | Dec 2016 | A1 |
| 20160381476 | Gossain et al. | Dec 2016 | A1 |
| 20170003931 | Dvortsov et al. | Jan 2017 | A1 |
| 20170006162 | Bargetzi 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 |
| 20170024100 | Pieper et al. | Jan 2017 | A1 |
| 20170025124 | Mixter et al. | Jan 2017 | A1 |
| 20170026686 | Glazier et al. | Jan 2017 | A1 |
| 20170031552 | Lin | Feb 2017 | A1 |
| 20170031557 | Xiangli et al. | Feb 2017 | A1 |
| 20170031648 | So et al. | Feb 2017 | A1 |
| 20170034583 | Long et al. | Feb 2017 | A1 |
| 20170041727 | Reimann | Feb 2017 | A1 |
| 20170046025 | Dascola et al. | Feb 2017 | A1 |
| 20170048817 | Yang et al. | Feb 2017 | A1 |
| 20170053008 | Frenkel et al. | Feb 2017 | A1 |
| 20170064184 | Tsai | Mar 2017 | A1 |
| 20170068402 | Lochhead et al. | Mar 2017 | A1 |
| 20170068507 | Kim et al. | Mar 2017 | A1 |
| 20170070346 | Lombardi et al. | Mar 2017 | A1 |
| 20170070775 | Taxier et al. | Mar 2017 | A1 |
| 20170078294 | Medvinsky | Mar 2017 | A1 |
| 20170078767 | Borel et al. | Mar 2017 | A1 |
| 20170083189 | Yang et al. | Mar 2017 | A1 |
| 20170083202 | Yang et al. | Mar 2017 | A1 |
| 20170083285 | Meyers et al. | Mar 2017 | A1 |
| 20170083494 | Kim et al. | Mar 2017 | A1 |
| 20170084135 | Yu | Mar 2017 | A1 |
| 20170091551 | Zhang et al. | Mar 2017 | A1 |
| 20170092085 | Agarwal | Mar 2017 | A1 |
| 20170092270 | Newendorp et al. | Mar 2017 | A1 |
| 20170094019 | Ahmed et al. | Mar 2017 | A1 |
| 20170097621 | Ackmann et al. | Apr 2017 | A1 |
| 20170099270 | Anson | Apr 2017 | A1 |
| 20170111587 | Herbst et al. | Apr 2017 | A1 |
| 20170111595 | Soni et al. | Apr 2017 | A1 |
| 20170115940 | Byeon | Apr 2017 | A1 |
| 20170126592 | El | May 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 |
| 20170142087 | Maninder et al. | May 2017 | A1 |
| 20170150904 | Park et al. | Jun 2017 | A1 |
| 20170176035 | Reeder et al. | Jun 2017 | A1 |
| 20170180843 | Perianu et al. | Jun 2017 | A1 |
| 20170185277 | Sundermeyer et al. | Jun 2017 | A1 |
| 20170185373 | Kim et al. | Jun 2017 | A1 |
| 20170193813 | Carroll et al. | Jul 2017 | A1 |
| 20170195130 | Landow et al. | Jul 2017 | A1 |
| 20170195772 | Han et al. | Jul 2017 | A1 |
| 20170206779 | Lee et al. | Jul 2017 | A1 |
| 20170220212 | Yang et al. | Aug 2017 | A1 |
| 20170230585 | Nash et al. | Aug 2017 | A1 |
| 20170230705 | Pardue | Aug 2017 | A1 |
| 20170235545 | Millington et al. | Aug 2017 | A1 |
| 20170242653 | Lang et al. | Aug 2017 | A1 |
| 20170244932 | Pistilli et al. | Aug 2017 | A1 |
| 20170251314 | Pye et al. | Aug 2017 | A1 |
| 20170280494 | Jung et al. | Sep 2017 | A1 |
| 20170285788 | Park et al. | Oct 2017 | A1 |
| 20170302779 | Zhao et al. | Oct 2017 | A1 |
| 20170309174 | Gonzales et al. | Oct 2017 | A1 |
| 20170322713 | Hwang et al. | Nov 2017 | A1 |
| 20170324784 | Taine et al. | Nov 2017 | A1 |
| 20170336960 | Chaudhri et al. | Nov 2017 | A1 |
| 20170337791 | Gordon-carroll | Nov 2017 | A1 |
| 20170344253 | Zhang | Nov 2017 | A1 |
| 20170345420 | Barnett, Jr. | Nov 2017 | A1 |
| 20170352380 | Doumbouya et al. | Dec 2017 | A1 |
| 20170353508 | Yoakum | Dec 2017 | A1 |
| 20170357382 | Miura et al. | Dec 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 |
| 20170357479 | Shenoy et al. | Dec 2017 | A1 |
| 20170357917 | Holmes et al. | Dec 2017 | A1 |
| 20170359189 | Smith et al. | Dec 2017 | A1 |
| 20170359191 | Smith et al. | Dec 2017 | A1 |
| 20170359285 | Weinig et al. | Dec 2017 | A1 |
| 20170359311 | Chen | Dec 2017 | A1 |
| 20170359555 | Irani et al. | Dec 2017 | A1 |
| 20170363436 | Eronen et al. | Dec 2017 | A1 |
| 20170367484 | Salvoni et al. | Dec 2017 | A1 |
| 20170371496 | Denoue et al. | Dec 2017 | A1 |
| 20170373868 | Deets, Jr. | Dec 2017 | A1 |
| 20180012596 | Piernot et al. | Jan 2018 | A1 |
| 20180013799 | Davies | Jan 2018 | A1 |
| 20180013815 | Gold | Jan 2018 | A1 |
| 20180014043 | Zhang et al. | Jan 2018 | A1 |
| 20180014077 | Hou et al. | Jan 2018 | A1 |
| 20180018081 | Dattilo-green et al. | Jan 2018 | A1 |
| 20180019889 | Burns et al. | Jan 2018 | A1 |
| 20180020530 | Scordato | Jan 2018 | A1 |
| 20180039916 | Ravindra | Feb 2018 | A1 |
| 20180040324 | Wilberding | Feb 2018 | A1 |
| 20180047200 | O'hara et al. | Feb 2018 | A1 |
| 20180048820 | Hinkel et al. | Feb 2018 | A1 |
| 20180061158 | Greene | Mar 2018 | A1 |
| 20180062691 | Barnett, Jr. | Mar 2018 | A1 |
| 20180067712 | Behzadi et al. | Mar 2018 | A1 |
| 20180069957 | Mushikabe et al. | Mar 2018 | A1 |
| 20180070144 | Tang et al. | Mar 2018 | A1 |
| 20180070187 | Drinkwater et al. | Mar 2018 | A1 |
| 20180081522 | Greenberg et al. | Mar 2018 | A1 |
| 20180088795 | Van Os et al. | Mar 2018 | A1 |
| 20180091732 | Wilson et al. | Mar 2018 | A1 |
| 20180095616 | Valdivia et al. | Apr 2018 | A1 |
| 20180096064 | Lennon et al. | Apr 2018 | A1 |
| 20180101297 | Yang et al. | Apr 2018 | A1 |
| 20180103074 | Rosenberg | Apr 2018 | A1 |
| 20180109754 | Kwon | Apr 2018 | A1 |
| 20180113577 | Burns et al. | Apr 2018 | A1 |
| 20180115788 | Burns et al. | Apr 2018 | A1 |
| 20180122378 | Mixter | May 2018 | A1 |
| 20180123986 | Faulkner et al. | May 2018 | A1 |
| 20180124128 | Faulkner et al. | May 2018 | A1 |
| 20180124359 | Faulkner | May 2018 | A1 |
| 20180131732 | Aronoff et al. | May 2018 | A1 |
| 20180139292 | Koren et al. | May 2018 | A1 |
| 20180139374 | Yu | May 2018 | A1 |
| 20180150433 | Sowden et al. | May 2018 | A1 |
| 20180157455 | Troy et al. | Jun 2018 | A1 |
| 20180159810 | Buchheit et al. | Jun 2018 | A1 |
| 20180160072 | Cranfill et al. | Jun 2018 | A1 |
| 20180181185 | Graham et al. | Jun 2018 | A1 |
| 20180190279 | Anderson et al. | Jul 2018 | A1 |
| 20180191965 | Faulkner et al. | Jul 2018 | A1 |
| 20180199080 | Jackson et al. | Jul 2018 | A1 |
| 20180199137 | Mate et al. | Jul 2018 | A1 |
| 20180199164 | Bargetzi et al. | Jul 2018 | A1 |
| 20180203577 | Astavans et al. | Jul 2018 | A1 |
| 20180204111 | Zadeh et al. | Jul 2018 | A1 |
| 20180205797 | Faulkner | Jul 2018 | A1 |
| 20180213144 | Kim et al. | Jul 2018 | A1 |
| 20180213396 | Segal | Jul 2018 | A1 |
| 20180217709 | Hotelling | Aug 2018 | A1 |
| 20180227341 | Rizzi | Aug 2018 | A1 |
| 20180228003 | O'driscoll et al. | Aug 2018 | A1 |
| 20180228006 | Baker | Aug 2018 | A1 |
| 20180232592 | Stewart et al. | Aug 2018 | A1 |
| 20180232705 | Baker et al. | Aug 2018 | A1 |
| 20180246639 | Han et al. | Aug 2018 | A1 |
| 20180249047 | Marlatt | Aug 2018 | A1 |
| 20180249113 | Faulkner | Aug 2018 | A1 |
| 20180253152 | Forsblom et al. | Sep 2018 | A1 |
| 20180267773 | Kim et al. | Sep 2018 | A1 |
| 20180267774 | Williams | Sep 2018 | A1 |
| 20180286395 | Li | Oct 2018 | A1 |
| 20180288104 | Padilla | Oct 2018 | A1 |
| 20180293959 | Monga et al. | Oct 2018 | A1 |
| 20180295079 | Longo | Oct 2018 | A1 |
| 20180308480 | Jang et al. | Oct 2018 | A1 |
| 20180309801 | Rathod | Oct 2018 | A1 |
| 20180329585 | Carrigan et al. | Nov 2018 | A1 |
| 20180329586 | Sundstrom et al. | Nov 2018 | A1 |
| 20180329672 | Sadak 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 | Nov 2018 | A1 |
| 20180341448 | Behzadi et al. | Nov 2018 | A1 |
| 20180348764 | Zhang et al. | Dec 2018 | A1 |
| 20180351762 | Iyengar et al. | Dec 2018 | A1 |
| 20180352072 | Christie et al. | Dec 2018 | A1 |
| 20180359293 | Faulkner et al. | Dec 2018 | A1 |
| 20180364665 | Clymer et al. | Dec 2018 | A1 |
| 20180367483 | Rodriguez et al. | Dec 2018 | A1 |
| 20180367484 | Rodriguez et al. | Dec 2018 | A1 |
| 20180367578 | Verma et al. | Dec 2018 | A1 |
| 20180375676 | Bader-Natal et al. | Dec 2018 | A1 |
| 20190005419 | Howard | Jan 2019 | A1 |
| 20190012069 | Bates | Jan 2019 | A1 |
| 20190012073 | Hwang | Jan 2019 | A1 |
| 20190012966 | Shi | Jan 2019 | A1 |
| 20190013018 | Rekstad | Jan 2019 | A1 |
| 20190025943 | Jobs et al. | Jan 2019 | A1 |
| 20190026021 | Coffman et al. | Jan 2019 | A1 |
| 20190028419 | Sullivan | Jan 2019 | A1 |
| 20190034849 | Romaine et al. | Jan 2019 | A1 |
| 20190056854 | Azzolin et al. | Feb 2019 | A1 |
| 20190056907 | So et al. | Feb 2019 | A1 |
| 20190058777 | Chen | Feb 2019 | A1 |
| 20190068670 | Adam et al. | Feb 2019 | A1 |
| 20190089934 | Goulden et al. | Mar 2019 | A1 |
| 20190102049 | Anzures et al. | Apr 2019 | A1 |
| 20190102145 | Wilberding et al. | Apr 2019 | A1 |
| 20190110087 | Parasseeri et al. | Apr 2019 | A1 |
| 20190124021 | Demattei | Apr 2019 | A1 |
| 20190129661 | Hirota et al. | May 2019 | A1 |
| 20190130185 | Delaney et al. | May 2019 | A1 |
| 20190138951 | Brownhill et al. | May 2019 | A1 |
| 20190149768 | Mcardle | May 2019 | A1 |
| 20190149887 | Williams et al. | May 2019 | A1 |
| 20190158645 | Yang et al. | May 2019 | A1 |
| 20190173939 | Lewis et al. | Jun 2019 | A1 |
| 20190187787 | White et al. | Jun 2019 | A1 |
| 20190199963 | Ahn et al. | Jun 2019 | A1 |
| 20190199993 | Babu J D et al. | Jun 2019 | A1 |
| 20190205861 | Bace | Jul 2019 | A1 |
| 20190208282 | Singh et al. | Jul 2019 | A1 |
| 20190222775 | Ahn | Jul 2019 | A1 |
| 20190228495 | Tremblay et al. | Jul 2019 | A1 |
| 20190236142 | Balakrishnan et al. | Aug 2019 | A1 |
| 20190265946 | Bae et al. | Aug 2019 | A1 |
| 20190273664 | Fujita et al. | Sep 2019 | A1 |
| 20190279634 | Tak | Sep 2019 | A1 |
| 20190286651 | Lee et al. | Sep 2019 | A1 |
| 20190294406 | Bierbower et al. | Sep 2019 | A1 |
| 20190295393 | Lee et al. | Sep 2019 | A1 |
| 20190297039 | Rodriguez et al. | Sep 2019 | A1 |
| 20190297439 | Maeda | Sep 2019 | A1 |
| 20190303861 | Mathias et al. | Oct 2019 | A1 |
| 20190306607 | Clayton et al. | Oct 2019 | A1 |
| 20190332400 | Spoor | Oct 2019 | A1 |
| 20190339769 | Cox | Nov 2019 | A1 |
| 20190339784 | Lemay et al. | Nov 2019 | A1 |
| 20190339825 | Anzures et al. | Nov 2019 | A1 |
| 20190342507 | Dye et al. | Nov 2019 | A1 |
| 20190342519 | Van Os et al. | Nov 2019 | A1 |
| 20190342621 | Carrigan et al. | Nov 2019 | A1 |
| 20190342622 | Carrigan et al. | Nov 2019 | A1 |
| 20190347181 | Cranfill et al. | Nov 2019 | A1 |
| 20190354252 | Badr | Nov 2019 | A1 |
| 20190361575 | Ni | Nov 2019 | A1 |
| 20190361694 | Gordon et al. | Nov 2019 | A1 |
| 20190362555 | Chen et al. | Nov 2019 | A1 |
| 20190370805 | Van Os et al. | Dec 2019 | A1 |
| 20200005539 | Hwang et al. | Jan 2020 | A1 |
| 20200034033 | Chaudhri et al. | Jan 2020 | A1 |
| 20200050426 | Jung et al. | Feb 2020 | A1 |
| 20200050502 | Ghafourifar et al. | Feb 2020 | A1 |
| 20200055515 | Herman et al. | Feb 2020 | A1 |
| 20200059628 | Cranfill et al. | Feb 2020 | A1 |
| 20200098362 | Piernot et al. | Mar 2020 | A1 |
| 20200098368 | Lemay et al. | Mar 2020 | A1 |
| 20200104018 | Coffman et al. | Apr 2020 | A1 |
| 20200106952 | Missig et al. | Apr 2020 | A1 |
| 20200106965 | Malia et al. | Apr 2020 | A1 |
| 20200112690 | Harrison et al. | Apr 2020 | A1 |
| 20200127988 | Bradley | Apr 2020 | A1 |
| 20200135191 | Nourbakhsh | Apr 2020 | A1 |
| 20200142667 | Querze | May 2020 | A1 |
| 20200143593 | Rudman et al. | May 2020 | A1 |
| 20200152186 | Koh et al. | May 2020 | A1 |
| 20200154583 | Lee et al. | May 2020 | A1 |
| 20200183548 | Anzures et al. | Jun 2020 | A1 |
| 20200186378 | Six et al. | Jun 2020 | A1 |
| 20200186576 | Gopal et al. | Jun 2020 | A1 |
| 20200193997 | Piernot et al. | Jun 2020 | A1 |
| 20200195887 | Van Os et al. | Jun 2020 | A1 |
| 20200201491 | Coffman et al. | Jun 2020 | A1 |
| 20200201495 | Coffman et al. | Jun 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 |
| 20200225841 | Coffman et al. | Jul 2020 | A1 |
| 20200226896 | Robertson et al. | Jul 2020 | A1 |
| 20200242788 | Jacobs et al. | Jul 2020 | A1 |
| 20200274726 | Setteboun et al. | Aug 2020 | A1 |
| 20200279279 | Chaudhuri | Sep 2020 | A1 |
| 20200296329 | Tang et al. | Sep 2020 | A1 |
| 20200302913 | Marcinkiewicz | Sep 2020 | A1 |
| 20200312318 | Olson | Oct 2020 | A1 |
| 20200335187 | Lefkofsky | Oct 2020 | A1 |
| 20200348807 | Garcia et al. | Nov 2020 | A1 |
| 20200371577 | Graham et al. | 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 |
| 20200382559 | Kramar et al. | Dec 2020 | A1 |
| 20200383157 | Lee et al. | Dec 2020 | A1 |
| 20200385116 | Sabripour et al. | Dec 2020 | A1 |
| 20200395012 | Kim et al. | Dec 2020 | A1 |
| 20200400957 | Van Heugten | Dec 2020 | A1 |
| 20200413197 | Carrigan et al. | Dec 2020 | A1 |
| 20210011588 | Coffman et al. | Jan 2021 | A1 |
| 20210043189 | Pyun | Feb 2021 | A1 |
| 20210064317 | Juenger et al. | Mar 2021 | A1 |
| 20210065134 | Chhabra et al. | Mar 2021 | A1 |
| 20210092491 | Carrigan et al. | Mar 2021 | A1 |
| 20210096703 | Anzures et al. | Apr 2021 | A1 |
| 20210097768 | Malia et al. | Apr 2021 | A1 |
| 20210099829 | Soto et al. | Apr 2021 | A1 |
| 20210136129 | Ponnusamy et al. | May 2021 | A1 |
| 20210141437 | Graham et al. | May 2021 | A1 |
| 20210144336 | Van Os et al. | May 2021 | A1 |
| 20210152503 | Rodriguez et al. | May 2021 | A1 |
| 20210152685 | Li | May 2021 | A1 |
| 20210158622 | Leelaphattarakij et al. | May 2021 | A1 |
| 20210158830 | Boehlke | May 2021 | A1 |
| 20210176204 | Geppert et al. | Jun 2021 | A1 |
| 20210181903 | Carrigan et al. | Jun 2021 | A1 |
| 20210182169 | Mardente et al. | Jun 2021 | A1 |
| 20210195084 | Olajos et al. | Jun 2021 | A1 |
| 20210203878 | Lee et al. | Jul 2021 | A1 |
| 20210217106 | Hauser et al. | Jul 2021 | A1 |
| 20210255816 | Behzadi et al. | Aug 2021 | A1 |
| 20210255819 | Graham et al. | Aug 2021 | A1 |
| 20210263702 | Carrigan | Aug 2021 | A1 |
| 20210265032 | Burgess et al. | Aug 2021 | A1 |
| 20210266274 | Liu et al. | Aug 2021 | A1 |
| 20210306288 | Boyd et al. | Sep 2021 | A1 |
| 20210321197 | Annamraju | Oct 2021 | A1 |
| 20210323406 | So et al. | Oct 2021 | A1 |
| 20210333864 | Harvey et al. | Oct 2021 | A1 |
| 20210349680 | Kim et al. | Nov 2021 | A1 |
| 20210352172 | Kim et al. | Nov 2021 | A1 |
| 20210360192 | Cranfill et al. | Nov 2021 | A1 |
| 20210360199 | Oz et al. | Nov 2021 | A1 |
| 20210366480 | Lemay et al. | Nov 2021 | A1 |
| 20210373672 | Schwarz et al. | Dec 2021 | A1 |
| 20210390955 | Piernot et al. | Dec 2021 | A1 |
| 20210392223 | Coffman et al. | Dec 2021 | A1 |
| 20210407507 | Zhou et al. | Dec 2021 | A1 |
| 20210409359 | Eirinberg et al. | Dec 2021 | A1 |
| 20220004356 | Kim et al. | Jan 2022 | A1 |
| 20220006946 | Missig et al. | Jan 2022 | A1 |
| 20220019292 | Lemay et al. | Jan 2022 | A1 |
| 20220021680 | Roedel et al. | Jan 2022 | A1 |
| 20220043626 | Carrigan | Feb 2022 | A1 |
| 20220046186 | Fayad et al. | Feb 2022 | A1 |
| 20220046222 | Meier | Feb 2022 | A1 |
| 20220050578 | Waldman et al. | Feb 2022 | A1 |
| 20220053142 | Manzari et al. | Feb 2022 | A1 |
| 20220100362 | Kim | Mar 2022 | A1 |
| 20220100367 | Carrigan et al. | Mar 2022 | A1 |
| 20220103784 | Pollefeys | Mar 2022 | A1 |
| 20220122089 | Bonilla Kuhlmann et al. | Apr 2022 | A1 |
| 20220141329 | Christie et al. | May 2022 | A1 |
| 20220147135 | Graham et al. | May 2022 | A1 |
| 20220180862 | Sharifi | Jun 2022 | A1 |
| 20220244836 | O'leary et al. | Aug 2022 | A1 |
| 20220247587 | Rolin et al. | Aug 2022 | A1 |
| 20220247918 | O'leary et al. | Aug 2022 | A1 |
| 20220247919 | O'leary et al. | Aug 2022 | A1 |
| 20220253136 | Holder et al. | Aug 2022 | A1 |
| 20220254074 | Berliner et al. | Aug 2022 | A1 |
| 20220269882 | Proschowsky et al. | Aug 2022 | A1 |
| 20220278992 | Baker et al. | Sep 2022 | A1 |
| 20220279022 | Kramar et al. | Sep 2022 | A1 |
| 20220279063 | Coffman et al. | Sep 2022 | A1 |
| 20220286314 | Meyer et al. | Sep 2022 | A1 |
| 20220286549 | Coffman et al. | Sep 2022 | A1 |
| 20220303150 | Jensen et al. | Sep 2022 | A1 |
| 20220303383 | Coffman et al. | Sep 2022 | A1 |
| 20220326817 | Carrigan et al. | Oct 2022 | A1 |
| 20220343569 | Karri et al. | Oct 2022 | A1 |
| 20220350482 | Carrigan et al. | Nov 2022 | A1 |
| 20220365643 | Triverio et al. | Nov 2022 | A1 |
| 20220365667 | Carrigan et al. | Nov 2022 | A1 |
| 20220365739 | Chang et al. | Nov 2022 | A1 |
| 20220365740 | Chang et al. | Nov 2022 | A1 |
| 20220368548 | Chang et al. | Nov 2022 | A1 |
| 20220368659 | Chang et al. | Nov 2022 | A1 |
| 20220368742 | Chang et al. | Nov 2022 | A1 |
| 20220374136 | Chang et al. | Nov 2022 | A1 |
| 20230004264 | Anzures et al. | Jan 2023 | A1 |
| 20230035941 | Herman et al. | Feb 2023 | A1 |
| 20230040703 | Lemay et al. | Feb 2023 | A1 |
| 20230057851 | Ansari et al. | Feb 2023 | A1 |
| 20230073844 | Coffman et al. | Mar 2023 | A1 |
| 20230079965 | Garcia et al. | Mar 2023 | A1 |
| 20230082492 | Coffman et al. | Mar 2023 | A1 |
| 20230084551 | Coffman et al. | Mar 2023 | A1 |
| 20230094453 | O'Leary et al. | Mar 2023 | A1 |
| 20230098395 | O'Leary 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 |
| 20230109787 | O'leary et al. | Apr 2023 | A1 |
| 20230143275 | Opara et al. | May 2023 | A1 |
| 20230188674 | Van Os et al. | Jun 2023 | A1 |
| 20230213764 | Arngren et al. | Jul 2023 | A1 |
| 20230246857 | Boucheron et al. | Aug 2023 | A1 |
| 20230262196 | Cranfill et al. | Aug 2023 | A1 |
| 20230262317 | O'Leary et al. | Aug 2023 | A1 |
| 20230266866 | Bates et al. | Aug 2023 | A1 |
| 20230319413 | Manzari et al. | Oct 2023 | A1 |
| 20230370507 | Chang et al. | Nov 2023 | A1 |
| 20230376268 | Carrigan et al. | Nov 2023 | A1 |
| 20230393705 | Krenn | Dec 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 |
| 20240036804 | Chang et al. | Feb 2024 | A1 |
| 20240040198 | Carrigan et al. | Feb 2024 | A1 |
| 20240056521 | Christie et al. | Feb 2024 | A1 |
| 20240064270 | Van Os et al. | Feb 2024 | A1 |
| 20240064395 | O'Leary et al. | Feb 2024 | A1 |
| 20240069711 | Carrigan et al. | Feb 2024 | A1 |
| 20240080642 | Carrigan et al. | Mar 2024 | A1 |
| 20240103677 | Mckenzie et al. | Mar 2024 | A1 |
| 20240104819 | Chand et al. | Mar 2024 | A1 |
| 20240118793 | Triverio et al. | Apr 2024 | A1 |
| 20240176441 | Yang et al. | May 2024 | A1 |
| 20240259638 | Carrigan et al. | Aug 2024 | A1 |
| 20240259669 | Missig et al. | Aug 2024 | A1 |
| 20240377922 | Rajam et al. | Nov 2024 | A1 |
| 20240406632 | Carrigan et al. | Dec 2024 | A1 |
| 20240419322 | Carrigan et al. | Dec 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 2007100826 | Sep 2007 | AU |
| 2008100011 | Feb 2008 | AU |
| 2015100713 | Jun 2015 | AU |
| 2022201622 | Mar 2022 | AU |
| 2532145 | Jul 1995 | CA |
| 2845537 | Sep 2014 | CA |
| 1473430 | Feb 2004 | CN |
| 1641589 | Jul 2005 | CN |
| 1679019 | Oct 2005 | CN |
| 1689327 | Oct 2005 | CN |
| 1801926 | Jul 2006 | CN |
| 1863281 | Nov 2006 | CN |
| 1890996 | Jan 2007 | CN |
| 1985319 | Jun 2007 | CN |
| 101046721 | Oct 2007 | CN |
| 101075173 | Nov 2007 | CN |
| 101107668 | Jan 2008 | CN |
| 101276255 | Oct 2008 | CN |
| 101296356 | Oct 2008 | CN |
| 101374090 | Feb 2009 | CN |
| 101431564 | May 2009 | CN |
| 101517557 | Aug 2009 | CN |
| 101535940 | Sep 2009 | CN |
| 101566866 | Oct 2009 | CN |
| 101567858 | Oct 2009 | CN |
| 101627361 | Jan 2010 | CN |
| 101682622 | Mar 2010 | CN |
| 101853132 | Oct 2010 | CN |
| 101854247 | Oct 2010 | CN |
| 101854261 | Oct 2010 | CN |
| 101861562 | Oct 2010 | CN |
| 101917529 | Dec 2010 | CN |
| 101989072 | Mar 2011 | CN |
| 102063253 | May 2011 | CN |
| 102202192 | Sep 2011 | CN |
| 102215217 | Oct 2011 | CN |
| 102215374 | Oct 2011 | CN |
| 102281294 | Dec 2011 | CN |
| 102301323 | Dec 2011 | CN |
| 102414755 | Apr 2012 | CN |
| 102572369 | Jul 2012 | CN |
| 102651731 | Aug 2012 | CN |
| 102740146 | Oct 2012 | CN |
| 102915630 | Feb 2013 | CN |
| 102932216 | Feb 2013 | CN |
| 102968267 | Mar 2013 | CN |
| 103039064 | Apr 2013 | CN |
| 103119968 | May 2013 | CN |
| 103136497 | Jun 2013 | CN |
| 103207674 | Jul 2013 | CN |
| 103222247 | Jul 2013 | CN |
| 103237191 | Aug 2013 | CN |
| 103260079 | Aug 2013 | CN |
| 103309606 | Sep 2013 | CN |
| 103347116 | Oct 2013 | CN |
| 103384235 | Nov 2013 | CN |
| 103399703 | Nov 2013 | CN |
| 103440247 | Dec 2013 | CN |
| 103442774 | Dec 2013 | CN |
| 103458215 | Dec 2013 | CN |
| 103473004 | Dec 2013 | CN |
| 103581544 | Feb 2014 | CN |
| 103583031 | Feb 2014 | CN |
| 103593154 | Feb 2014 | CN |
| 103649985 | Mar 2014 | CN |
| 103677711 | Mar 2014 | CN |
| 103685729 | Mar 2014 | CN |
| 103718152 | Apr 2014 | CN |
| 103748610 | Apr 2014 | CN |
| 103809905 | May 2014 | CN |
| 103914238 | Jul 2014 | CN |
| 103959751 | Jul 2014 | CN |
| 104010158 | Aug 2014 | CN |
| 104076757 | Oct 2014 | CN |
| 104081335 | Oct 2014 | CN |
| 104106036 | Oct 2014 | CN |
| 104155938 | Nov 2014 | CN |
| 104205785 | Dec 2014 | CN |
| 104247449 | Dec 2014 | CN |
| 104270597 | Jan 2015 | CN |
| 104284477 | Jan 2015 | CN |
| 104298188 | Jan 2015 | CN |
| 204155434 | Feb 2015 | CN |
| 104427288 | Mar 2015 | CN |
| 104429094 | Mar 2015 | CN |
| 104469143 | Mar 2015 | CN |
| 104469512 | Mar 2015 | CN |
| 104581043 | Apr 2015 | CN |
| 104602133 | May 2015 | CN |
| 104618672 | May 2015 | CN |
| 104684207 | Jun 2015 | CN |
| 104766021 | Jul 2015 | CN |
| 104780654 | Jul 2015 | CN |
| 104820631 | Aug 2015 | CN |
| 104869046 | Aug 2015 | CN |
| 104898603 | Sep 2015 | CN |
| 104956276 | Sep 2015 | CN |
| 104956417 | Sep 2015 | CN |
| 104980578 | Oct 2015 | CN |
| 105069118 | Nov 2015 | CN |
| 105094957 | Nov 2015 | CN |
| 105141498 | Dec 2015 | CN |
| 105159107 | Dec 2015 | CN |
| 105204742 | Dec 2015 | CN |
| 105204846 | Dec 2015 | CN |
| 105208511 | Dec 2015 | CN |
| 105263114 | Jan 2016 | CN |
| 105264473 | Jan 2016 | CN |
| 105278681 | Jan 2016 | CN |
| 105283840 | Jan 2016 | CN |
| 103583031 | Feb 2016 | CN |
| 105308634 | Feb 2016 | CN |
| 105359199 | Feb 2016 | CN |
| 105373165 | Mar 2016 | CN |
| 105374192 | Mar 2016 | CN |
| 105388773 | Mar 2016 | CN |
| 105388998 | Mar 2016 | CN |
| 105389173 | Mar 2016 | CN |
| 105391778 | Mar 2016 | CN |
| 105474580 | Apr 2016 | CN |
| 105531671 | Apr 2016 | CN |
| 105549947 | May 2016 | CN |
| 105553796 | May 2016 | CN |
| 105554429 | May 2016 | CN |
| 105554516 | May 2016 | CN |
| 105578111 | May 2016 | CN |
| 205263700 | May 2016 | CN |
| 105657465 | Jun 2016 | CN |
| 105745863 | Jul 2016 | CN |
| 105794231 | Jul 2016 | CN |
| 105847746 | Aug 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 |
| 106210855 | Dec 2016 | CN |
| 106303648 | Jan 2017 | CN |
| 103914238 | Feb 2017 | CN |
| 106383645 | Feb 2017 | CN |
| 106416142 | Feb 2017 | CN |
| 106471793 | Mar 2017 | CN |
| 106537991 | Mar 2017 | CN |
| 106572326 | Apr 2017 | CN |
| 106713946 | May 2017 | CN |
| 106797415 | May 2017 | CN |
| 106843626 | Jun 2017 | CN |
| 107066523 | Aug 2017 | CN |
| 107077288 | Aug 2017 | CN |
| 107122049 | Sep 2017 | CN |
| 107197441 | Sep 2017 | CN |
| 107250949 | Oct 2017 | CN |
| 107491257 | Dec 2017 | CN |
| 107533368 | Jan 2018 | CN |
| 107533417 | Jan 2018 | CN |
| 107534656 | Jan 2018 | CN |
| 107613235 | Jan 2018 | CN |
| 107637073 | Jan 2018 | CN |
| 107683470 | Feb 2018 | CN |
| 107704177 | Feb 2018 | CN |
| 107728876 | Feb 2018 | CN |
| 107819928 | Mar 2018 | CN |
| 104025538 | Apr 2018 | CN |
| 107949879 | Apr 2018 | CN |
| 104012150 | May 2018 | CN |
| 107992248 | May 2018 | CN |
| 108289239 | Jul 2018 | CN |
| 108292203 | Jul 2018 | CN |
| 108933965 | Dec 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 |
| 110456971 | Nov 2019 | CN |
| 111108740 | May 2020 | CN |
| 111601065 | Aug 2020 | CN |
| 112088530 | Dec 2020 | CN |
| 112214275 | Jan 2021 | CN |
| 112261338 | Jan 2021 | CN |
| 105900376 | Feb 2021 | CN |
| 112416223 | Feb 2021 | CN |
| 109584879 | Jul 2021 | CN |
| 113835583 | Dec 2021 | CN |
| 108958608 | Jul 2022 | CN |
| 1133119 | Sep 2001 | EP |
| 1881649 | Jan 2008 | EP |
| 1903791 | Mar 2008 | EP |
| 1986431 | Oct 2008 | EP |
| 2018032 | Jan 2009 | EP |
| 2056568 | May 2009 | EP |
| 2237536 | Oct 2010 | EP |
| 2490432 | Aug 2012 | EP |
| 2582120 | Apr 2013 | EP |
| 2600584 | Jun 2013 | EP |
| 2629291 | Aug 2013 | EP |
| 2675195 | Dec 2013 | EP |
| 2750062 | Jul 2014 | EP |
| 2770673 | Aug 2014 | EP |
| 2784611 | Oct 2014 | EP |
| 2797391 | Oct 2014 | EP |
| 2879470 | Jun 2015 | EP |
| 2892240 | Jul 2015 | EP |
| 2894948 | Jul 2015 | EP |
| 2446619 | Oct 2015 | EP |
| 2933953 | Oct 2015 | EP |
| 2981093 | Feb 2016 | EP |
| 2993909 | Mar 2016 | EP |
| 3032537 | Jun 2016 | EP |
| 3038427 | Jun 2016 | EP |
| 3041229 | Jul 2016 | EP |
| 3057342 | Aug 2016 | EP |
| 3073703 | Sep 2016 | EP |
| 2761582 | Mar 2017 | EP |
| 3138300 | Mar 2017 | EP |
| 3163495 | May 2017 | EP |
| 3227771 | Oct 2017 | EP |
| 3276905 | Jan 2018 | EP |
| 2258103 | May 2018 | EP |
| 3379853 | Sep 2018 | EP |
| 3420441 | Jan 2019 | EP |
| 3445058 | Feb 2019 | EP |
| 3460770 | Mar 2019 | EP |
| 3038427 | Dec 2019 | EP |
| 3579093 | Dec 2019 | EP |
| 3163866 | May 2020 | EP |
| 3751405 | Dec 2020 | EP |
| 4109891 | Dec 2022 | EP |
| 4134799 | Feb 2023 | EP |
| 3069679 | Feb 2019 | FR |
| 2341698 | Mar 2000 | GB |
| 0412212 | Jul 2004 | GB |
| 2402105 | Dec 2004 | GB |
| 2499123 | Aug 2013 | GB |
| 2512821 | Oct 2014 | GB |
| 2533101 | Jun 2016 | GB |
| 1038MUM2005 | Jun 2007 | IN |
| 4-175921 | Jun 1992 | JP |
| 6-113297 | Apr 1994 | JP |
| 6-178356 | Jun 1994 | JP |
| 6-276335 | Sep 1994 | JP |
| 6-276515 | Sep 1994 | JP |
| 7-135594 | May 1995 | JP |
| 9-182046 | Jul 1997 | JP |
| 9-233384 | Sep 1997 | JP |
| 9-247655 | Sep 1997 | JP |
| 9-265457 | Oct 1997 | JP |
| 11-98249 | Apr 1999 | JP |
| 2001-67099 | Mar 2001 | JP |
| 2001-169166 | Jun 2001 | JP |
| 2002-58082 | Feb 2002 | JP |
| 2002-153678 | May 2002 | JP |
| 2002-163217 | Jun 2002 | JP |
| 2002-251365 | Sep 2002 | JP |
| 2002-320140 | Oct 2002 | JP |
| 2002-351802 | Dec 2002 | JP |
| 2003-101981 | Apr 2003 | JP |
| 2003-134382 | May 2003 | JP |
| 2003-141050 | May 2003 | JP |
| 2003-189168 | Jul 2003 | JP |
| 2003-228780 | Aug 2003 | JP |
| 2003-274376 | Sep 2003 | JP |
| 2003-299050 | Oct 2003 | JP |
| 2003-348444 | Dec 2003 | JP |
| 2004-96397 | Mar 2004 | JP |
| 2004-110559 | Apr 2004 | JP |
| 2004-187273 | Jul 2004 | JP |
| 2004-193860 | Jul 2004 | JP |
| 2004-221738 | Aug 2004 | JP |
| 2005-94696 | Apr 2005 | JP |
| 2005-159567 | Jun 2005 | JP |
| 2005-260289 | Sep 2005 | JP |
| 2005-286445 | Oct 2005 | JP |
| 2005-303736 | Oct 2005 | JP |
| 2005-333294 | Dec 2005 | JP |
| 2006-72489 | Mar 2006 | JP |
| 2006-135495 | May 2006 | JP |
| 2006-135667 | May 2006 | JP |
| 2006-166414 | Jun 2006 | JP |
| 2006-185154 | Jul 2006 | JP |
| 2006-222822 | Aug 2006 | JP |
| 2006-245732 | Sep 2006 | JP |
| 2006-246019 | Sep 2006 | JP |
| 2006-254350 | Sep 2006 | JP |
| 2006-319742 | Nov 2006 | JP |
| 2006-350819 | Dec 2006 | JP |
| 2007-58663 | Mar 2007 | JP |
| 2007-88630 | Apr 2007 | JP |
| 2007-140060 | Jun 2007 | JP |
| 2007-150877 | Jun 2007 | JP |
| 2007-150921 | Jun 2007 | JP |
| 2007-200329 | Aug 2007 | JP |
| 2007-201727 | Aug 2007 | JP |
| 2007-274034 | Oct 2007 | JP |
| 2007-282263 | Oct 2007 | JP |
| 2007-300452 | Nov 2007 | JP |
| 2008-28586 | Feb 2008 | JP |
| 2008-99330 | Apr 2008 | JP |
| 2008-125105 | May 2008 | JP |
| 2008-136119 | Jun 2008 | JP |
| 2008-526156 | Jul 2008 | JP |
| 2008-533838 | Aug 2008 | JP |
| 2008-289014 | Nov 2008 | JP |
| 2008-546069 | Dec 2008 | JP |
| 2009-502048 | Jan 2009 | JP |
| 2009-159253 | Jul 2009 | JP |
| 2009-188975 | Aug 2009 | JP |
| 2009-201127 | Sep 2009 | JP |
| 2009-232290 | Oct 2009 | JP |
| 2009-265692 | Nov 2009 | JP |
| 2009-296583 | Dec 2009 | JP |
| 2010-15239 | Jan 2010 | JP |
| 2010-503126 | Jan 2010 | JP |
| 2010-503332 | Jan 2010 | JP |
| 2010-541398 | Dec 2010 | JP |
| 2011-60281 | Mar 2011 | JP |
| 2011-65654 | Mar 2011 | JP |
| 2011-107823 | Jun 2011 | JP |
| 2011-124665 | Jun 2011 | JP |
| 2012-73839 | Apr 2012 | JP |
| 2012-508530 | Apr 2012 | JP |
| 2012-123460 | Jun 2012 | JP |
| 2012-244340 | Dec 2012 | JP |
| 2013-37688 | Feb 2013 | JP |
| 2013-98613 | May 2013 | JP |
| 2013-524683 | Jun 2013 | JP |
| 2013-200879 | Oct 2013 | JP |
| 2013-542522 | Nov 2013 | JP |
| 2014-71835 | Apr 2014 | JP |
| 2014-87126 | May 2014 | JP |
| 2014-135000 | Jul 2014 | JP |
| 2014-160461 | Sep 2014 | JP |
| 2014-170982 | Sep 2014 | JP |
| 2014-186961 | Oct 2014 | JP |
| 5628461 | Nov 2014 | JP |
| 2015-11507 | Jan 2015 | JP |
| 2015-61318 | Mar 2015 | JP |
| 2015-70327 | Apr 2015 | JP |
| 2015-125671 | Jul 2015 | JP |
| 2015-128043 | Jul 2015 | JP |
| 2015-128326 | Jul 2015 | JP |
| 2015-149710 | Aug 2015 | JP |
| 2015-154253 | Aug 2015 | JP |
| 2015-170234 | Sep 2015 | JP |
| 2015-195222 | Nov 2015 | JP |
| 2015-201087 | Nov 2015 | JP |
| 2015-211035 | Nov 2015 | JP |
| 2015-533441 | Nov 2015 | JP |
| 2016-1446 | Jan 2016 | JP |
| 2016-24557 | Feb 2016 | JP |
| 2016-38615 | Mar 2016 | JP |
| 2016-51661 | Apr 2016 | JP |
| 2016-53929 | Apr 2016 | JP |
| 2016-63531 | Apr 2016 | JP |
| 2016-72953 | May 2016 | JP |
| 2016-100791 | May 2016 | JP |
| 2016-119600 | Jun 2016 | JP |
| 2016-525732 | Aug 2016 | JP |
| 2016-157292 | Sep 2016 | JP |
| 2016-167806 | Sep 2016 | JP |
| 2016-174282 | Sep 2016 | JP |
| 2017-34563 | Feb 2017 | JP |
| 2017-41008 | Feb 2017 | JP |
| 2017-508195 | Mar 2017 | JP |
| 2017-84253 | May 2017 | JP |
| 2017-143357 | Aug 2017 | JP |
| 2017-158202 | Sep 2017 | JP |
| 2017-173998 | Sep 2017 | JP |
| 2017-212096 | Nov 2017 | JP |
| 2017-532645 | Nov 2017 | JP |
| 2017-228843 | Dec 2017 | JP |
| 2017-229060 | Dec 2017 | JP |
| 2017-537361 | Dec 2017 | JP |
| 2018-7158 | Jan 2018 | JP |
| 2016-63520 | Apr 2018 | JP |
| 2018-56719 | Apr 2018 | JP |
| 2018-63826 | Apr 2018 | JP |
| 2018-136828 | Aug 2018 | JP |
| 2018-147265 | Sep 2018 | JP |
| 2018-200624 | Dec 2018 | JP |
| 2019-114282 | Jul 2019 | JP |
| 2019-526095 | Sep 2019 | JP |
| 2020-510929 | Apr 2020 | JP |
| 2021-40300 | Mar 2021 | JP |
| 1997-0031883 | Jun 1997 | KR |
| 1999-0044201 | Jun 1999 | KR |
| 10-2001-0091156 | Oct 2001 | KR |
| 10-2004-0016688 | Feb 2004 | KR |
| 10-2004-0045338 | Jun 2004 | KR |
| 10-2004-0089329 | Oct 2004 | KR |
| 10-2005-0054684 | Jun 2005 | KR |
| 10-2006-0031959 | Apr 2006 | KR |
| 10-2006-0064326 | Jun 2006 | KR |
| 10-2006-0116902 | Nov 2006 | KR |
| 10-2007-0111270 | Nov 2007 | KR |
| 10-2008-0096042 | Oct 2008 | KR |
| 10-2009-0002641 | Jan 2009 | KR |
| 10-2009-0004176 | Jan 2009 | KR |
| 10-2009-0017901 | Feb 2009 | KR |
| 10-2009-0017906 | Feb 2009 | KR |
| 10-2009-0036226 | Apr 2009 | KR |
| 110-2009-0042499 | Apr 2009 | KR |
| 110-0891449 | Apr 2009 | KR |
| 10-2009-0122805 | Dec 2009 | KR |
| 10-2009-0126516 | Dec 2009 | KR |
| 10-2010-0036351 | Apr 2010 | KR |
| 10-2011-0022980 | Mar 2011 | KR |
| 10-2011-0075136 | Jul 2011 | KR |
| 10-2011-0093040 | Aug 2011 | KR |
| 10-2012-0059860 | Jun 2012 | KR |
| 10-2012-0079208 | Jul 2012 | KR |
| 10-2013-0115611 | Oct 2013 | KR |
| 10-2014-0148289 | Dec 2014 | KR |
| 10-2015-0005134 | Jan 2015 | KR |
| 10-2015-0031010 | Mar 2015 | KR |
| 10-2015-0043146 | Apr 2015 | KR |
| 10-1522311 | May 2015 | KR |
| 10-2015-0121177 | Oct 2015 | KR |
| 10-2015-0136440 | Dec 2015 | KR |
| 10-2016-0012008 | Feb 2016 | KR |
| 10-2016-0092363 | Aug 2016 | KR |
| 10-2016-0092820 | 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-0107058 | Sep 2017 | KR |
| 10-2017-0124954 | Nov 2017 | KR |
| 10-2017-0128498 | Nov 2017 | 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-0033082 | Mar 2019 | KR |
| 10-2019-0057414 | May 2019 | KR |
| 10-1989433 | Jun 2019 | KR |
| 10-2011177 | Aug 2019 | KR |
| 10-2020-0039030 | Apr 2020 | KR |
| 1321955 | Mar 2010 | TW |
| 201547326 | Dec 2015 | TW |
| 201629750 | Aug 2016 | TW |
| 0039964 | Jul 2000 | WO |
| 200118665 | Mar 2001 | WO |
| 0237848 | May 2002 | WO |
| 2003077553 | Sep 2003 | WO |
| 2004032507 | Apr 2004 | WO |
| 2005055521 | Jun 2005 | WO |
| 2005060501 | Jul 2005 | WO |
| 2005086159 | Sep 2005 | WO |
| 2006063343 | Jun 2006 | WO |
| 2007008321 | Jan 2007 | WO |
| 2007063922 | Jun 2007 | WO |
| 2008027924 | Mar 2008 | WO |
| 2008030972 | Mar 2008 | WO |
| 2008030976 | Mar 2008 | WO |
| 2008040566 | Apr 2008 | WO |
| 2009005563 | Jan 2009 | WO |
| 2009005914 | Jan 2009 | WO |
| 2009010827 | Jan 2009 | WO |
| 2009042579 | Apr 2009 | WO |
| 2009067670 | May 2009 | WO |
| 2009071112 | Jun 2009 | WO |
| 2009086599 | Jul 2009 | WO |
| 2010001672 | Jan 2010 | WO |
| 2010054373 | May 2010 | WO |
| 2010087988 | Aug 2010 | WO |
| 2010137513 | Dec 2010 | WO |
| 2011011224 | Jan 2011 | WO |
| 2011027964 | Mar 2011 | WO |
| 2011126502 | Oct 2011 | WO |
| 2011126505 | Oct 2011 | WO |
| 2011127457 | Oct 2011 | WO |
| 2011146605 | Nov 2011 | WO |
| 2011146839 | Nov 2011 | WO |
| 2011161145 | Dec 2011 | WO |
| 2011163350 | Dec 2011 | WO |
| 2012004288 | Jan 2012 | WO |
| 2012037170 | Mar 2012 | WO |
| 2012085794 | Jun 2012 | WO |
| 2012104288 | Aug 2012 | WO |
| 2012166277 | Dec 2012 | WO |
| 2012166352 | Dec 2012 | WO |
| 2012170118 | Dec 2012 | WO |
| 2013021385 | Feb 2013 | WO |
| 2013048880 | Apr 2013 | WO |
| 2013049346 | Apr 2013 | WO |
| 2013114821 | Aug 2013 | WO |
| 2013153405 | Oct 2013 | WO |
| 2013169875 | Nov 2013 | WO |
| 2014030320 | Feb 2014 | WO |
| 2014030540 | Feb 2014 | WO |
| 2014046475 | Mar 2014 | WO |
| 2014052871 | Apr 2014 | WO |
| 2014058937 | Apr 2014 | WO |
| 2014077987 | May 2014 | WO |
| 2014107469 | Jul 2014 | WO |
| 2014128800 | Aug 2014 | WO |
| 2014143776 | Sep 2014 | WO |
| 2014151089 | Sep 2014 | WO |
| 2014155429 | Oct 2014 | WO |
| 2014159581 | Oct 2014 | WO |
| 2014168616 | Oct 2014 | WO |
| 2014197339 | Dec 2014 | WO |
| 2014200730 | Dec 2014 | WO |
| 2014208057 | Dec 2014 | WO |
| 2014210304 | Dec 2014 | WO |
| 2015008409 | Jan 2015 | WO |
| 2015039000 | Mar 2015 | WO |
| 2015076930 | May 2015 | WO |
| 2015102572 | Jul 2015 | WO |
| 2015105763 | Jul 2015 | WO |
| 2015114690 | Aug 2015 | WO |
| 2015124831 | Aug 2015 | WO |
| 2015134692 | Sep 2015 | WO |
| 2015179031 | Nov 2015 | WO |
| 2015183755 | Dec 2015 | WO |
| 2015185123 | Dec 2015 | WO |
| 2016033400 | Mar 2016 | WO |
| 2016036472 | Mar 2016 | WO |
| 2016036541 | Mar 2016 | WO |
| 2016039992 | Mar 2016 | WO |
| 2016040405 | Mar 2016 | WO |
| 2016052888 | Apr 2016 | WO |
| 2016057117 | Apr 2016 | WO |
| 2016079889 | May 2016 | WO |
| 2016144983 | Sep 2016 | WO |
| 2016168154 | Oct 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 |
| 2017173155 | Oct 2017 | WO |
| 2017205657 | Nov 2017 | WO |
| 2017218143 | Dec 2017 | WO |
| 2017218153 | Dec 2017 | WO |
| 2017218192 | Dec 2017 | WO |
| 2017218199 | Dec 2017 | WO |
| 2018048510 | Mar 2018 | WO |
| 2018057272 | 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 |
| 2019067131 | Apr 2019 | WO |
| 2019090653 | May 2019 | WO |
| 2019217009 | Nov 2019 | WO |
| 2019217341 | Nov 2019 | WO |
| 2019217477 | Nov 2019 | WO |
| 2020063762 | Apr 2020 | WO |
| 2021112983 | Jun 2021 | WO |
| 2021231412 | Nov 2021 | WO |
| Entry |
|---|
| Corrected Notice of Allowance received for U.S. Appl. No. 17/752,582, mailed on Jul. 17, 2023, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/992,229, mailed on Jul. 13, 2023, 14 pages. |
| Notice of Allowance received for Australian Patent Application No. 2022228207, mailed on Jul. 3, 2023, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202110328601.5, mailed on Jul. 5, 2023, 5 pages (1 page of English Translation and 4 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/483,564, mailed on Jul. 17, 2023, 46 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/867,317, mailed on Jul. 6, 2023, 11 pages. |
| 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). |
| Garrison Dr., “An Analysis and Evaluation of Audio Teleconferencing to Facilitate Education at a Distance”, Online Available at: https://doi.org/10.1080/08923649009526713, American journal of distance education, Jol. 4, No. 3, Sep. 24, 2009, 14 pages. |
| Shangmeng Li, “The Design and Implementation of Mobile Terminal System of Multimedia Conference Based on Symbian Operating System”, China Academic Journal Electronic Publishing House, online available at: http://www.cnki.net, 2011, 66 pages (Official Copy only) See Communication under 37 CFR § 1.98(a) (3). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/467,700, mailed on Mar. 28, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/747,804, mailed on Mar. 17, 2023, 4 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. 16/922,675, mailed on Mar. 22, 2023, 8 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. |
| Office Action received for Indian Patent Application No. 202015013360, mailed on Mar. 17, 2023, 7 pages. |
| Advisory Action received for U.S. Appl. No. 16/830,838, mailed on Oct. 10, 2023, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/684,843, mailed on Oct. 5, 2023, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/950,922, mailed on Oct. 2, 2023, 3 pages. |
| Final Office Action received for U.S. Appl. No. 17/742,273, mailed on Oct. 12, 2023, 58 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-016138, mailed on Sep. 25, 2023, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/479,897, mailed on Oct. 3, 2023, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/732,204, mailed on Oct. 12, 2023, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/740,104, mailed on Oct. 4, 2023, 5 pages. |
| Office Action received for Japanese Patent Application No. 2022-104306, mailed on Sep. 19, 2023, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| “6. Voice chat with friends through QQ”, Online available at: https://v.qq.com/x/page/a0166p7xrt0.html, Sep. 22, 2015, 1 page (Official Copy Only). {See Communication under 37 CFR § 1.98(a) (3)}. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,564, mailed on Apr. 21, 2023, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/752,582, mailed on Apr. 17, 2023, 3 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20205496.1, mailed on Apr. 19, 2023, 1 page. |
| 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. 17/467,700, mailed on Apr. 17, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/482,977, mailed on Apr. 24, 2023, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/950,900, mailed on Apr. 14, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/950,922, mailed on Apr. 14, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/077,905, mailed on Apr. 19, 2023, 2 pages. |
| Intention to Grant received for European Patent Application No. 18728002.9, mailed on Apr. 12, 2023, 9 pages. |
| Jiutian Technology, “Windows 8 Chinese version from entry to proficiency”, Jan. 1, 2014, 5 pages (Official Copy Only). {See Communication under 37 CFR § 1.98(a) (3)}. |
| Non-Final Office Action received for U.S. Appl. No. 17/479,897, mailed on Apr. 25, 2023, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/903,946, mailed on Apr. 14, 2023, 17 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). |
| Office Action received for Chinese Patent Application No. 202110327012.5, mailed on Mar. 16, 2023, 12 pages (7 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110328601.5, mailed on Mar. 24, 2023, 25 pages (15 pages of English Translation and 10 pages of Official Copy). |
| Office Action received for European Patent Application No. 20720310.0, mailed on Apr. 11, 2023, 8 pages. |
| Result of Consultation received for European Patent Application No. 20205496.1, mailed on Apr. 18, 2023, 3 pages. |
| Song Jianhua, “Guidelines for Network”, Feb. 29, 2008, 11 pages (Official Copy Only). {See Communication under 37 CFR § 1.98(a) (3)}. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, mailed on Aug. 18, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/479,897, mailed on Aug. 17, 2023, 2 pages. |
| Ex-Parte Quayle Action received for U.S. Appl. No. 17/903,946, mailed on Aug. 4, 2023, 4 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/014271, mailed on Aug. 10, 2023, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/684,843, mailed on Aug. 11, 2023, 23 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,542, mailed on Aug. 11, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/872,736, mailed on Aug. 21, 2023, 6 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. |
| Office Action received for European Patent Application No. 20746426.4, mailed on Aug. 17, 2023, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/922,675, mailed on Jan. 9, 2023, 3 pages. |
| Examiner's Pre-Review Report received for Japanese Patent Application No. 2020-047952, mailed on Dec. 13, 2022, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Extended European Search Report received for European Patent Application No. 22195584.2, mailed on Jan. 5, 2023, 13 pages. |
| Final Office Action received for U.S. Appl. No. 17/116,938, mailed on Dec. 29, 2022, 42 pages. |
| Final Office Action received for U.S. Appl. No. 17/479,897, mailed on Jan. 10, 2023, 15 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. 202110819254.6, mailed on Dec. 27, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110328602.X, mailed on Dec. 1, 2022, 28 pages (17 pages of English Translation 11 pages 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). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,542, mailed on May 22, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, mailed on May 19, 2023, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/509,356, mailed on May 24, 2023, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA202270464, mailed on May 9, 2023, 1 page. |
| Decision to Refuse received for European Patent Application No. 20205496.1, mailed on May 12, 2023, 16 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 20205496.1, mailed on May 9, 2023, 7 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. |
| Non-Final Office Action received for U.S. Appl. No. 17/872,736, mailed on May 11, 2023, 17 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022204555, mailed on May 11, 2023, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2021-206121, mailed on May 15, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/848,845, mailed on May 24, 2023, 26 pages. |
| Ochs Susie, “Getting Started with Apple Music: 12 Things to Do First”, Macworld 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. |
| Office Action received for Australian Patent Application No. 2022228207, mailed on Apr. 28, 2023, 3 pages. |
| Office Action received for Japanese Patent Application No. 2022-016138, mailed on Apr. 24, 2023, 9 pages (5 pages of English Translation and 4 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/740,104, mailed on Jan. 2, 2024, 2 pages. |
| Decision to Grant received for Japanese Patent Application No. 2022-104306, mailed on Jan. 4, 2024, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Intention to Grant received for European Patent Application No. 20746426.4, mailed on Jan. 5, 2024, 9 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). |
| Office Action received for Korean Patent Application No. 10-2023-7011715, mailed on Dec. 20, 2023, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20720310.0, mailed on Jan. 3, 2024, 12 pages. |
| Advisory Action received for U.S. Appl. No. 17/483,679, mailed on Sep. 20, 2022, 8 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/830,838, mailed on Sep. 21, 2022, 2 pages. |
| 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/116,938, mailed on Oct. 13, 2022, 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/479,897, mailed on Oct. 31, 2022, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,542, mailed on Nov. 23, 2022, 4 pages. |
| Communication of the Board of Appeal received for European Patent Application No. 15728307.8, mailed on Sep. 14, 2022, 9 pages. |
| Communication of the Board of Appeal received for European Patent Application No. 15729286.3, mailed on Oct. 6, 2022, 8 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/936,164, mailed on Oct. 13, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/936,164, mailed on Oct. 28, 2022, 3 pages. |
| Decision to Grant received for Danish Patent Application No. PA202170320, mailed on Nov. 10, 2022, 2 pages. |
| Extended European Search Report received for European Patent Application No. 22191264.5, mailed on Nov. 11, 2022, 8 pages. |
| Final Office Action received for U.S. Appl. No. 16/830,838, mailed on Oct. 14, 2022, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/029261, mailed on Oct. 20, 2022, 18 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/029261, mailed on Aug. 29, 2022, 16 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 15728307.8, mailed on Nov. 11, 2022, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/482,977, mailed on Oct. 13, 2022, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,542, mailed on Sep. 22, 2022, 18 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201910400179.2, mailed on Oct. 9, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 202011450203.2, mailed on Sep. 30, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-0091730, mailed on Oct. 4, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| 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/936,164, mailed on Sep. 21, 2022, 9 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 Chinese Patent Application No. 202080039642.6, mailed on Sep. 5, 2022, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110235995.X, mailed on Sep. 30, 2022, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110328597.2, mailed on Oct. 10, 2022, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110819254.6, mailed on Sep. 15, 2022, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202111652452.4, mailed on Aug. 29, 2022, 23 pages (12 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA202270464, mailed on Oct. 25, 2022, 9 pages. |
| Office Action received for European Patent Application No. 20720310.0, mailed on Oct. 4, 2022, 9 pages. |
| Office Action received for Korean Patent Application No. 10-2021-7029861, mailed on Nov. 1, 2022, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 21160991.2, mailed on Oct. 19, 2022, 10 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/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 Danish Patent Application No. PA202270464, mailed on Dec. 20, 2022, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/830,838, mailed on Jun. 1, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/476,404, mailed on Jun. 2, 2023, 2 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. |
| Final Office Action received for U.S. Appl. No. 17/483,564, mailed on May 25, 2023, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/306,354, mailed on Jun. 2, 2023, 21 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/019,845, mailed on Jun. 5, 2023, 10 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 Chinese Patent Application No. 202110328597.2, mailed on May 15, 2023, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for European Patent Application No. 21197457.1, mailed on May 30, 2023, 8 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/077,905, mailed on Apr. 26, 2023, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/077,905, mailed on May 4, 2023, 2 pages. |
| Final Office Action received for U.S. Appl. No. 17/747,804, mailed on Apr. 28, 2023, 17 pages. |
| Office Action received for Korean Patent Application No. 10-2022-7001332, mailed on Apr. 20, 2023, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/830,838, mailed on Sep. 22, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/742,273, mailed on Sep. 27, 2023, 4 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/992,229, mailed on Sep. 25, 2023, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,679, mailed on Sep. 13, 2023, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/742,273, mailed on Sep. 13, 2023, 58 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/950,922, mailed on Sep. 20, 2023, 6 pages. |
| Notice of Hearing received for Indian Patent Application No. 201814036860, mailed on Sep. 8, 2023, 2 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/476,404, mailed on Oct. 31, 2023, 4 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 17/116,938, mailed on Oct. 31, 2023, 55 pages. |
| Office Action received for Australian Patent Application No. 2022291522, mailed on Oct. 11, 2023, 2 pages. |
| Office Action received for Australian Patent Application No. 2023248185, mailed on Oct. 20, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/482,977, mailed on Dec. 5, 2022, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 18728002.9, mailed on Nov. 28, 2022, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/031760, mailed on Nov. 24, 2022, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/029273, mailed on Oct. 27, 2022, 19 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/029282, mailed on Nov. 9, 2022, 22 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/029580, mailed on Nov. 7, 2022, 20 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/029282, mailed on Sep. 15, 2022, 15 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/029580, mailed on Sep. 5, 2022, 13 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2022/029273, mailed on Sep. 2, 2022, 13 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 21728781.2, mailed on Dec. 2, 2022, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,564, mailed on Nov. 28, 2022, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/742,273, mailed on Dec. 7, 2022, 47 pages. |
| Office Action received for Australian Patent Application No. 2022241590, mailed on Nov. 18, 2022, 8 pages. |
| Office Action received for Chinese Patent Application No. 202110328601.5, mailed on Nov. 2, 2022, 32 pages (19 pages of English Translation and 13 pages of Official Copy). |
| QQ, “Method of QQ voice chat”, Online Available at: https://www.taodocs.com/p-47909082.html, May 25, 2016, 3 pages (Official Copy only) See Communication Under 37 CFR § 1.98(a) (3). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, mailed on Dec. 18, 2023, 2 pages. |
| Final Office Action received for U.S. Appl. No. 18/067,350, mailed on Dec. 13, 2023, 44 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/483,542, mailed on Dec. 20, 2023, 6 pages. |
| Office Action received for Chinese Patent Application No. 202110817799.3, mailed on Oct. 26, 2023, 22 pages (13 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2022-155232, mailed on Dec. 15, 2023, 9 pages (4 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. |
| Dolan, Tim, “How To Make a Laptop Webcam into a Document Camera—IPEVO Mirror-Cam Review”, Retrieved from the internet: https://www.youtube.com/watch?v=-K8jyZ1hbbg, Aug. 29, 2020, 1 page. |
| Larson, Tom, “How to Turn your Webcam into a Document Camera”, Retrieved from the Internet: https://www.youtube.com/watchv=UlaW22FxRZM, Nov. 7, 2020, 1 page. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,542, mailed on Jan. 31, 2023, 14 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). |
| Notice of Allowance received for U.S. Appl. No. 17/482,977, mailed on Jan. 24, 2023, 10 pages. |
| Office Action received for European Patent Application No. 20719301.2, mailed on Jan. 24, 2023, 9 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/684,843, mailed on Mar. 4, 2024, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-155232, mailed on Feb. 26, 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-7008877, mailed on Feb. 20, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-7039382, mailed on Feb. 13, 2024, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2024-7000870, mailed on Feb. 13, 2024, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 18/375,457, mailed on Feb. 23, 2024, 16 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. 201880031407.7, mailed on Jan. 12, 2024, 15 pages (7 pages of English Translation and 8 pages of Official Copy). |
| 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 Korean Patent Application No. 10-2022-7044372, mailed on Feb. 13, 2024, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 17/742,273, mailed on Feb. 15, 2023, 56 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/467,700, mailed on Feb. 21, 2023, 11 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 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). |
| 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/992,229, mailed on Nov. 30, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/067,350, mailed on Sep. 11, 2023, 4 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. |
| Office Action received for Australian Patent Application No. 2023248185, mailed on Nov. 22, 2023, 2 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. 17/732,204, mailed on Nov. 16, 2023, 6 pages. |
| Final Office Action received for U.S. Appl. No. 17/484,899, mailed on Nov. 6, 2023, 39 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7001332, mailed on Oct. 25, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for European Patent Application No. 20166552.8, mailed on Nov. 3, 2023, 3 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). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,899, mailed on Feb. 14, 2024, 8 pages. |
| Decision to Grant received for European Patent Application No. 21728781.2, mailed on Feb. 8, 2024, 3 pages. |
| Extended European Search Report received for European Patent Application No. 23203433.0, mailed on Feb. 7, 2024, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/978,930, mailed on Feb. 12, 2024, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/992,229, mailed on Feb. 15, 2024, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/237,341, mailed on Feb. 14, 2024, 13 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022291522, mailed on Jan. 31, 2024, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/684,843, mailed on Feb. 14, 2024, 8 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). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/479,897, mailed on Jun. 12, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,564, mailed on Jun. 21, 2023, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/509,356, mailed on Jun. 13, 2023, 2 pages. |
| Final Office Action received for U.S. Appl. No. 17/483,679, mailed on Jun. 13, 2023, 33 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/484,899, mailed on Jun. 14, 2023, 41 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2021-166451, mailed on Jun. 5, 2023, 4 pages (1 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/752,582, mailed on Jun. 13, 2023, 18 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/950,900, mailed on Jun. 16, 2023, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/989,086, mailed on Jun. 9, 2023, 8 pages. |
| Office Action received for Australian Patent Application No. 2022204466, mailed on Jun. 7, 2023, 4 pages. |
| Office Action received for Australian Patent Application No. 2022241590, mailed on Jun. 7, 2023, 7 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/732,204, mailed on Jan. 18, 2024, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/830,838, mailed on Jan. 22, 2024, 17 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. 202210463449.6, mailed on Dec. 19, 2023, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/742,273, mailed on Jan. 18, 2023, 4 pages. |
| Extended European Search Report received for European Patent Application No. 22196865.4, mailed on Jan. 13, 2023, 7 pages. |
| Extended European Search Report received for European Patent Application No. 22201007.6, mailed on Jan. 12, 2023, 7 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). |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7029861, mailed on Jan. 4, 2023, 7 pages (2 pages of English Translation & 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2021-166451, mailed on Jan. 5, 2023, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| “How to use popular SNS confidence (wechat) in China 2 _ voice message, press together, shake function etc.”, Available at “http://seechina365.com/2014/04/05/wechat02/”, Apr. 5, 2014, 27 pages. |
| “WhatsApp” users over 400 million people! I tried to investigate the most used messaging application in the world, Available at “http://www.appps.jp/2128786/”, Jan. 24, 2014, 10 pages. |
| Abdulezer et al., “Skype For Dummies”, Available Online at: https://ixn.es/Skype%20For%20Dummies.pdf, 2007, 361 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. 15/730,610, mailed on Oct. 24, 2019, 5 pages. |
| Advisory Action received for U.S. Appl. No. 16/404,605, mailed on Apr. 15, 2020, 10 pages. |
| Advisory Action received for U.S. Appl. No. 16/583,989, mailed on Sep. 22, 2020, 5 pages. |
| Akshay, “Control your SmartThings compatible devices on the Gear S2 and S3 with the Smarter Things app”, Online available at: 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. |
| Ambrogi Robert, “Send Secure, Self-Destructing Messages with Wickr”, Lawsites Blog, Available online at: Lawsites Blog, Available online at: https://www.lawsitesblog.com/2013/11/send-secure-self-destructing-messages-wickr.html, Nov. 5, 2013, 3 pages. |
| Androidcentral, “How do i 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. |
| 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. 15/488,093, mailed on Jan. 14, 2020, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/404,605, mailed on Nov. 13, 2019, 3 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 on Jul. 28, 2020, 4 pages. |
| Applicant Initiated Interview 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/790,619, mailed on Jul. 28, 2020, 3 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/817,328, mailed on Dec. 21, 2021, 3 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/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. 15/960,330, mailed on Aug. 11, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/960,330, mailed on Jan. 21, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/528,941, mailed on Jun. 19, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/528,941, mailed on Nov. 10, 2020, 2 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/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/799,481, mailed on Jul. 24, 2020, 3 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/830,838, mailed on Apr. 6, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/830,838, mailed on May 24, 2021, 3 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. 16/936,164, mailed on Aug. 23, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/936,164, mailed on Mar. 22, 2022, 4 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/116,938, mailed on Dec. 13, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/116,938, mailed on Jun. 14, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/121,610, mailed on Oct. 29, 2021, 2 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/223,794, mailed on Sep. 7, 2021, 3 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. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/482,987, mailed on Apr. 11, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,564, mailed on Jul. 21, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,564, mailed on Mar. 14, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, mailed on Apr. 29, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, mailed on Aug. 23, 2022, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,899, mailed on Apr. 27, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,899, mailed on Sep. 1, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,907, mailed on Jan. 10, 2022, 2 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. |
| Board Decision received for Chinese Patent Application No. 201580029071.7, mailed on Jul. 13, 2021, 2 pages. |
| 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. 17167629.9, mailed on Nov. 12, 2020, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 17813777.4, mailed on Nov. 23, 2020, 6 pages. |
| 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. 19182037.2, mailed on Apr. 15, 2021, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 19728558.8, mailed on Jul. 5, 2022, 1 page. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20158824.1, mailed on May 30, 2022, 1 page. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20187610.9, mailed on May 31, 2022, 1 page. |
| 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. 2019100487, mailed on Jan. 7, 2020, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2019100499, mailed on Aug. 15, 2019, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2019101062, mailed on Jun. 2, 2020, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2020100303, mailed on Apr. 17, 2020, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2020100886, mailed on Dec. 22, 2020, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2020101324, mailed on Sep. 7, 2020, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2021100721, mailed on Dec. 16, 2021, 2 pages. |
| Certification of Examination received for Australian Patent Application No. 2017100666, mailed on Jan. 29, 2018, 2 pages. |
| Computeradv,“Sonos App Navigation & Menu on iPhone”, Available online at: https://www.youtube.com/watch?v=Jhz9XvWQ204, Aug. 4, 2015, 1 page. |
| Corrected International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/035293, mailed on Dec. 8, 2017, 21 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 12/163,908, mailed on Feb. 22, 2018, 8 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/928,865, mailed on Aug. 5, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/928,865, mailed on May 16, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/366,763, mailed on Jan. 2, 2020, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/366,890, mailed on Feb. 12, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/427,516, mailed on Apr. 29, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/427,516, mailed on May 8, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/488,093, mailed on Jun. 15, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/488,093, mailed on Jun. 30, 2020, 2 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/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. 16/109,552, mailed on Jun. 13, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,379, mailed on Dec. 18, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,379, mailed on Feb. 14, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,379, mailed on Mar. 3, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,379, mailed on Mar. 12, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/144,572, mailed on Mar. 21, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/147,432, mailed on Jan. 18, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/147,432, mailed on Jul. 16, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/404,605, mailed on Dec. 23, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/511,578, mailed on Feb. 13, 2020, 3 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/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/790,619, mailed on Oct. 13, 2020, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/799,481, mailed on Oct. 27, 2020, 3 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, 5pages. |
| 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/922,675, mailed on Mar. 4, 2022, 6 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/121,610, mailed on Jun. 7, 2022, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/121,610, mailed on Mar. 31, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/121,610, mailed on May 20, 2022, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/157,166, mailed on Apr. 13, 2022, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/157,166, mailed on Apr. 25, 2022, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/157,166, mailed on Dec. 9, 2021, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/157,166, mailed on Dec. 15, 2021, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/157,166, mailed on Jan. 5, 2022, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/157,166, mailed on Jun. 29, 2022, 4 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. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/483,549, mailed on Aug. 24, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/483,582, mailed on Feb. 15, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/484,907, mailed on Aug. 26, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/484,907, mailed on Jun. 15, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/484,907, mailed on Mar. 18, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,379, mailed on Aug. 15, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,379, mailed on Nov. 12, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,379, mailed on Oct. 16, 2019, 2 pages. |
| Corrected Search Report and Opinion received for Danish Patent Application No. PA201870364, mailed on Sep. 5, 2018, 13 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. |
| David Chanceg., “Unpublished U.S. Appl. No. 16/583,989, filed Sep. 26, 2019, titled User Interfaces for Audio Media Control”. |
| Decision on Appeal received for U.S. Appl. No. 14/503,355, mailed on Aug. 25, 2020, 10 pages. |
| Decision to Grant received for Danish Patent Application No. PA201670601, mailed on Jun. 21, 2019, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201670602, mailed on Nov. 30, 2018, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201670604, mailed on Aug. 22, 2018, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201670605, mailed on Nov. 29, 2018, 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. PA201870293, mailed on Dec. 3, 2018, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870362, mailed on May 15, 2020, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870435, mailed on Oct. 20, 2020, 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. 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. 19182037.2, mailed on Sep. 16, 2021, 3 pages. |
| Decision to Grant received for European Patent Application No. 19207753.5, mailed on Jun. 2, 2022, 3 pages. |
| Decision to Grant received for European Patent Application No. 19729395.4, mailed on Dec. 9, 2021, 2 pages. |
| Decision to Grant received for Japanese Patent Application No. 2021-051415, mailed on Jan. 6, 2022, 3 pages. |
| Decision to Refuse received for European Patent Application No. 15728307.8, mailed on Dec. 18, 2019, 14 pages. |
| Decision to Refuse received for European Patent Application No. 15729286.3, mailed on Dec. 18, 2019, 13 pages. |
| Decision to Refuse received for European Patent Application No. 17167629.9, mailed on Nov. 24, 2020, 2 pages. |
| Decision to Refuse received for European Patent Application No. 20187610.9, mailed on Jul. 19, 2022, 13 pages. |
| Detroitborg, “Apple Music: Walkthrough”, YouTube Video, online available at: “https://www.youtube.com/watch?v=NLgjodiAtbQ”, Jun. 30, 2015, 1 page. |
| Ex Partee Quayle Action received for U.S. Appl. No. 17/121,610, mailed on Dec. 9, 2021, 7 pages. |
| Initiated-Interview Summary received for U.S. Appl. No. 16/528,941, mailed on Dec. 1, 2020, 2 pages. |
| Examiner-Initiated Interview Summary received for U.S. Appl. No. 17/027,373, mailed on Mar. 31, 2022, 4 pages. |
| Answer to Appeal Brief received for U.S. Appl. No. 14/503,355, mailed on Apr. 17, 2020, 17 pages. |
| Extended European Search Report (includes Supplementary European Search Report and Search Opinion) received for European Patent Application No. 17813777.4, mailed on Mar. 25, 2019, 8 pages. |
| Extended European Search Report Received for European Patent Application No. 17167629.9, mailed on Jun. 2, 2017, 7 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. 19182037.2, mailed on Oct. 31, 2019, 8 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. 20166552.8, mailed on Jun. 12, 2020, 9 pages. |
| Extended European Search Report received for European Patent Application No. 20187610.9, mailed on Nov. 16, 2020, 7 pages. |
| Extended European Search Report received for European Patent Application No. 20205496.1, mailed on Mar. 11, 2021, 11 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. 21197457.1, mailed on Nov. 15, 2021, 8 pages. |
| Extended Search Report received for European Patent Application No. 21161005.0, mailed on Jun. 14, 2021, 12 pages. |
| Farmboyreef, “Apple watch controlling your tv”, Available online at: https://www.youtube.com/watch?v=xaJPG0Wm3Tg, Jun. 23, 2015, 3 pages. |
| Final Office Action received for U.S. Appl. No. 12/163,908, mailed on Nov. 7, 2012, 15 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/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. 14/503,355, mailed on May 20, 2019, 27 pages. |
| Final Office Action received for U.S. Appl. No. 14/503,355, mailed on Sep. 8, 2017, 25 pages. |
| Final Office Action received for U.S. Appl. No. 14/928,865, mailed on Dec. 5, 2018, 15 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. 15/960,330, mailed on Nov. 10, 2020, 19 pages. |
| Final Office Action received for U.S. Appl. No. 16/404,605, mailed on Feb. 10, 2020, 21 pages. |
| Final Office Action received for U.S. Appl. No. 16/528,941, mailed on Jul. 13, 2020, 15 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/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/830,838, mailed on Dec. 9, 2021, 16 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. 16/936,164, mailed on Jul. 6, 2022, 21 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/116,938, mailed on Mar. 1, 2022, 27 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. 17/483,564, mailed on Apr. 18, 2022, 23 pages. |
| Final Office Action received for U.S. Appl. No. 17/483,679, mailed on May 24, 2022, 21 pages. |
| Final Office Action received for U.S. Appl. No. 17/484,899, mailed on May 12, 2022, 29 pages. |
| Finkelstein Ellen, “Temporarily Override Object Snap Settings”, AutoCAD Tips Blog, Apr. 9, 2007, 4 pages. |
| Free Virtual Classic Analogue Mono Synth, Samsara Cycle Audio Releases DEISK-O, Jan. 2, 2011, 3 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, “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. |
| Graham et al., “Unpublished U.S. Appl. No. 16/584,490, filed Sep. 26, 2019, titled User Interfaces for Audio Media Control”. |
| 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. |
| HuddleCamHD SimplTrack2 Auto Tracking Camera Installation & Operation Manual, Available Online at: https://huddlecamhd.com/wp-content/uploads/2021/01/SimplTrack2-User-Manual-v1_2-6-20.pdf, Jun. 2020, 41 pages. |
| IDB,“HomeCam is the Best Way to View Multiple HomeKit Cameras on iPhone & Apple TV”, Available online at: https://www.youtube.com/watch?v=6x2oCHgSVUU, Feb. 20, 2018, 3 pages. |
| Intention to Grant received for Danish Patent Application No. PA201670601, mailed on Apr. 10, 2019, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201670602, mailed on Aug. 1, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201670604, mailed on Jun. 14, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201670604, mailed on Mar. 15, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201670605, mailed on Aug. 1, 2018, 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. PA201870293, mailed on Aug. 31, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870362, mailed on Feb. 14, 2020, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870435, mailed on Jul. 1, 2020, 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. 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. 19182037.2, mailed on May 4, 2021, 9 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. 19729395.4, mailed on Jul. 23, 2021, 10 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/US2012/025314, mailed on Sep. 12, 2013, Sep. 12, 2013, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/032305, mailed on Dec. 15, 2016, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/032309, mailed on Dec. 15, 2016, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/035293, mailed on Dec. 27, 2018, 16 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/US2018/048151, mailed on Apr. 9, 2020, 14 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/030963, mailed on Nov. 19, 2020, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/031202, mailed on Nov. 19, 2020, 13 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/035426, mailed on Dec. 9, 2021, 10 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 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/US2015/032305, mailed on Sep. 10, 2015, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/032309, mailed on Sep. 2, 2015, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/035293, mailed on Oct. 10, 2017, 25 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/US2018/048151, mailed on Jan. 10, 2019, 23 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/030963, mailed on Oct. 17, 2019, 21 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/031202, mailed on Oct. 4, 2019, 19 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/035426, mailed on Sep. 11, 2020, 12 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. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/014271, mailed on Jul. 4, 2022, 23 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 Addition Fees received for PCT Patent Application No. PCT/US2017/035293, mailed on Aug. 17, 2017, 3 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/014271, mailed on May 12, 2022, 20 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/US2018/032158, mailed on Sep. 10, 2018, 16 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2018/048151, mailed on Nov. 6, 2018, 18 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/030963, mailed on Aug. 22, 2019, 12 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/031202, mailed on Aug. 8, 2019, 12 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. 19728558.8, mailed on Apr. 20, 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. |
| 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. |
| 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. |
| 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. |
| Minutes of Oral Proceedings received for European Patent Application No. 15728307.8, mailed on Dec. 13, 2019, 4 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 15729286.3, mailed on Dec. 13, 2019, 4 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 18197583.0, mailed on Mar. 9, 2021, 6 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 19729395.4, mailed on Jul. 21, 2021, 6 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 20187610.9, mailed on Jun. 7, 2022, 6 pages. |
| Mobile How To, “How to Send A Picture Message/MMS—Samsung Galaxy Note 3”, Online Available at: https://www.youtube.com/watch?v=-3d0z8-KeDw, Published on Nov. 3, 2013, 1 page. |
| 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. 16/035,422, mailed on Nov. 30, 2018, 13 Pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/157,166, mailed on Jul. 9, 2021, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/163,908, mailed on Apr. 7, 2017, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/163,908, mailed on Jun. 13, 2012, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/038,217, mailed on Sep. 13, 2013, Sep. 13, 2013, 16 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 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. 14/503,355, mailed on Dec. 30, 2016, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,355, mailed on Sep. 4, 2018, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,376, mailed on Dec. 22, 2014, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,386, mailed on Jan. 7, 2015, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/928,865, mailed on Mar. 27, 2018, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/366,763, mailed on Mar. 8, 2019, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/366,890, mailed on May 8, 2019, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/427,516, mailed on Aug. 28, 2018, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/488,093, mailed on Oct. 4, 2019, 18 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/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. 15/960,330, mailed on Apr. 28, 2020, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/109,552, mailed on Oct. 17, 2018, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,379, mailed on Mar. 14, 2019, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,572, mailed on Nov. 30, 2018, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/383,403, mailed on Aug. 23, 2019, 10 pages. |
| Non-Final Office Action for U.S. Appl. No. 16/404,605, mailed on Aug. 1, 2019, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/404,605, mailed on Jun. 24, 2020, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/404,612, mailed on Feb. 28, 2020, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/528,941, mailed on Dec. 7, 2020, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/528,941, mailed on Jan. 30, 2020, 14 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/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/790,619, mailed on May 4, 2020, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/799,481, mailed on May 1, 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/830,838, mailed on Oct. 29, 2021, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/830,838, mailed on Apr. 1, 2021, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/830,838, mailed on Jun. 9, 2022, 17 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/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/936,164, mailed on Jan. 18, 2022, 18 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/116,938, mailed on Aug. 1, 2022, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/116,938, mailed on Jul. 30, 2021, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/121,610, mailed on May 13, 2021, 17 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/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. 17/479,897, mailed on Aug. 30, 2022, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/482,987, mailed on Jan. 18, 2022, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,549, mailed on Jan. 11, 2022, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,564, mailed on Jan. 6, 2022, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,679, mailed on Feb. 1, 2022, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/484,899, mailed on Jan. 24, 2022, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/484,907, mailed on Nov. 19, 2021, 24 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. |
| Norman Don, “Affordances and Design”, Jng.org, Available at <http://jnd.org/dn.mss/affordances_and.html>, Jan. 14, 2006, 5 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015267259, mailed on Jan. 30, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015267260, mailed on Jan. 30, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018203215, mailed on Nov. 20, 2019, 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. 2018236872, mailed on Jul. 9, 2019, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019266225, mailed on Dec. 23, 2020, 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. 2020201575, mailed on Mar. 15, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020217458, mailed on Sep. 7, 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. 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. 2021200789, mailed on Feb. 26, 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. 2021202815, mailed on Jun. 16, 2022, 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. 2021203903, 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 received for Australian Patent Application No. 2017286129, mailed on Dec. 10, 2018, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201510290133.1, mailed on Jan. 9, 2019, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201510291012.9, mailed on Jan. 9, 2019, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201520365358.4, mailed on Nov. 20, 2015, 4 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201520365843.1, issued on Feb. 15, 2016, 5 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201580029071.7, mailed on Aug. 19, 2021, 5 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201710267617.3, mailed on May 8, 2021, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201710493025.3, mailed on May 7, 2021, 6 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201810730279.7, mailed on Nov. 5, 2020, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201811151702.4, mailed on Jul. 6, 2020, 6 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201811152097.2, mailed on Oct. 28, 2019, 6 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. 201880056514.5, mailed on Jan. 11, 2021, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201910400180.5, mailed on Nov. 5, 2020, 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. 202010742019.9, mailed on Jul. 6, 2021, 7 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202011243876.0, mailed on Sep. 8, 2021, 4 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202011336156.9, mailed on Jan. 6, 2022, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202110248576.X, mailed on Mar. 21, 2022, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202110818370.6, mailed on Sep. 2, 2022, 7 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. 2017-514992, mailed on Feb. 15, 2019, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-514993, mailed on Jan. 12, 2018, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-018497, mailed on Jun. 21, 2019, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-183504, mailed on Sep. 27, 2019, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-562659, mailed on Jul. 30, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-050138, mailed on Jun. 15, 2020, 5 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-194597, mailed on Nov. 19, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-118723, mailed on Oct. 16, 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-187397, mailed on Sep. 10, 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. 2020-560927, mailed on May 30, 2022, 3 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-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-2018-7034909, mailed on Sep. 30, 2019, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7038093, mailed on Aug. 10, 2020, 5 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-7031319, mailed on Apr. 6, 2021, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7031700, mailed on Apr. 21, 2021, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7032110, mailed on Mar. 8, 2021, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7032488, mailed on Jun. 16, 2021, 4 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-7022610, mailed on Oct. 13, 2021, 3 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-7008567, mailed on Jul. 4, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/035,422, mailed on Apr. 10, 2019, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/528,941, mailed on Aug. 10, 2021, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/528,941, mailed on May 19, 2021, 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. 17/157,166, mailed on Nov. 16, 2021, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/163,908, mailed on Nov. 30, 2017, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,376, mailed on Jul. 29, 2015, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,376, mailed on Sep. 2, 2015, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,376, mailed on Sep. 24, 2015, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,386, mailed on Jul. 30, 2015, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,386, mailed on Sep. 24, 2015, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/928,865, mailed on Apr. 3, 2019, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/928,865, mailed on Jul. 22, 2019, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/366,763, mailed on Oct. 8, 2019, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/366,890, mailed on Nov. 14, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/427,516, mailed on Mar. 4, 2019, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/488,093, mailed on Apr. 22, 2020, 8 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/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/960,330, mailed on Apr. 30, 2021, 18 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/109,552, mailed on Mar. 13, 2019, 25 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/109,552, mailed on May 13, 2019, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,379, mailed on Jan. 29, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,572, mailed on Feb. 28, 2019, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/147,432, mailed on Dec. 18, 2018, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/147,432, mailed on May 20, 2019, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/383,403, mailed on Jan. 10, 2020, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/404,605, mailed on Sep. 18, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/404,612, mailed on Jul. 13, 2020, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/404,612. mailed on Aug. 7, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/511,578, mailed on Nov. 18, 2019, 12 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 June. 9, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/790,619, mailed on Sep. 8, 2020, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/799,481, mailed on Sep. 8, 2020, 6 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/817,328, mailed on Apr. 18, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/817,328, mailed on Feb. 16, 2022, 9 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/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. 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/121,610, mailed on Jul. 7, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/121,610, mailed on Jul. 13, 2022, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/121,610, mailed on Mar. 11, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/157,166, mailed on Mar. 30, 2022, 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. 17/482,987, mailed on Jun. 23, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/482,987, mailed on May 11, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,549, mailed on Apr. 15, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,582, mailed on Apr. 19, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,582, mailed on Jan. 20, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/484,907, mailed on Jul. 25, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/484,907, mailed on Mar. 2, 2022, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/484,907, mailed on May 20, 2022, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,379, mailed on Jun. 26, 2019, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,379, mailed on Sep. 25, 2019, 5 pages. |
| Office Action received for Australian Patent Application No. 2015100711, issued on Jul. 27, 2015, 7 pages. |
| Office Action Received for Australian Patent Application No. 2015100711, mailed on Nov. 19, 2015, 6 pages. |
| Office Action received for Australian Patent Application No. 2015267259, mailed on Jun. 2, 2017, 2 pages. |
| Office Action received for Australian Patent Application No. 2015267260, mailed on Jun. 2, 2017, 2 pages. |
| Office Action received for Australian Patent Application No. 2016102028, mailed on Feb. 13, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2016102029, mailed on Feb. 22, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2017100666, mailed on Jul. 27, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2017286129, mailed on Oct. 18, 2018, 3 pages. |
| Office Action received for Australian Patent Application No. 2018203215, mailed on Mar. 29, 2019, 3 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. 2019100487, mailed on Aug. 16, 2019, 5 pages. |
| Office Action received for Australian Patent Application No. 2019100499, mailed on Jun. 28, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2019100523, mailed on Jan. 23, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2019100523, mailed on Mar. 2, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2019100523, mailed on Sep. 2, 2019, 3 pages. |
| Office Action received for Australian Patent Application No. 2019101062, mailed on Apr. 22, 2020, 2 pages. |
| Office Action received for Australian Patent Application No. 2019101062, mailed on Dec. 5, 2019, 3 pages. |
| Office Action received for Australian Patent Application No. 2019201853, mailed on Apr. 23, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2019201853, mailed on Aug. 10, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2019201853, mailed on Aug. 16, 2019, 5 pages. |
| Office Action received for Australian Patent Application No. 2019201853, mailed on Dec. 9, 2019, 5 pages. |
| Office Action received for Australian Patent Application No. 2019266225, mailed on Nov. 23, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2019267527, mailed on Dec. 2, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2019267527, mailed on Jun. 15, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2019267527, mailed on Jun. 24, 2021, 8 pages. |
| Office Action received for Australian Patent Application No. 2019267527, mailed on Mar. 3, 2022, 3 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. 2020100886, mailed on Aug. 5, 2020, 6 pages. |
| Office Action received for Australian Patent Application No. 2020201575, mailed on Dec. 22, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2020217458, mailed on Aug. 2, 2022, 4 pages. |
| Office Action received for Australian Patent Application No. 2020217458, mailed on May 10, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2020217458, mailed on Sep. 2, 2021, 6 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. 2020282362, mailed on Nov. 25, 2021, 3 pages. |
| Office Action received for Australian Patent Application No. 2021100721, mailed on Jun. 4, 2021, 7 pages. |
| Office Action received for Australian Patent Application No. 2021100721, mailed on Oct. 18, 2021, 4 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. 2021202815, mailed on Apr. 11, 2022, 2 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. 2021203903, mailed on Feb. 24, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2021204454, mailed on Aug. 9, 2021, 7 pages. |
| Office Action received for Chinese Patent Application No. 201510290133.1, mailed on Feb. 9, 2018, 10 pages. |
| Office Action Received for Chinese Patent Application No. 201510291012.9, mailed on Feb. 8, 2018, 10 pages. |
| Office Action received for Chinese Patent Application No. 201520365358.4, mailed on Aug. 11, 2015, 4 pages. |
| Office Action received for Chinese Patent Application No. 201520365843.1, mailed on Aug. 25, 2015, 4 pages. |
| Office Action Received for Chinese Patent Application No. 201520365843.1, mailed on Nov. 16, 2015, 3 pages. |
| Office Action received for Chinese Patent Application No. 201580029071.7, mailed on Apr. 2, 2021, 19 pages. |
| Office Action received for Chinese Patent Application No. 201580029071.7, mailed on Apr. 9, 2020, 33 pages. |
| Office Action received for Chinese Patent Application No. 201580029071.7, mailed on Jul. 2, 2019, 29 pages. |
| Office Action received for Chinese Patent Application No. 201580029071.7, mailed on Oct. 29, 2020, 20 pages. |
| Office Action received for Chinese Patent Application No. 201620393549.6, mailed on Aug. 18, 2016, 2 pages. |
| Office Action received for Chinese Patent Application No. 201620393549.6, mailed on Jan. 13, 2017, 2 pages. |
| Office Action received for Chinese Patent Application No. 201620393748.7, mailed on Aug. 18, 2016, 2 pages. |
| Office Action received for Chinese Patent Application No. 201620393748.7, mailed on Jan. 13, 2017, 2 pages. |
| Office Action received for Chinese Patent Application No. 201710267617.3, mailed on Apr. 17, 2020, 23 pages. |
| Office Action received for Chinese Patent Application No. 201710267617.3, mailed on Jul. 10, 2019, 18 pages. |
| Office Action received for Chinese Patent Application No. 201710267617.3, mailed on Nov. 2, 2020, 6 pages. |
| Office Action received for Chinese Patent Application No. 201710493025.3, mailed on Dec. 6, 2019, 11 pages. |
| Office Action received for Chinese Patent Application No. 201710493025.3, mailed on Jan. 6, 2021, 17 pages. |
| Office Action received for Chinese Patent Application No. 201710493025.3, mailed on Jul. 10, 2020, 17 pages. |
| Office Action received for Chinese Patent Application No. 201710493025.3, mailed on Sep. 19, 2017, 2 pages. |
| Office Action received for Chinese Patent Application No. 201810730279.7, mailed on Jul. 6, 2020, 7 pages. |
| Office Action received for Chinese Patent Application No. 201810730279.7, mailed on Mar. 4, 2020, 14 pages. |
| Office Action received for Chinese Patent Application No. 201810730279.7, mailed on May 7, 2019, 15 pages. |
| Office Action received for Chinese Patent Application No. 201810730279.7, mailed on Nov. 5, 2019, 14 pages. |
| Office Action received for Chinese Patent Application No. 201811151702.4, mailed on Mar. 4, 2020, 13 pages. |
| Office Action received for Chinese Patent Application No. 201811151702.4, mailed on May 7, 2019, 16 pages. |
| Office Action received for Chinese Patent Application No. 201811151702.4, mailed on Oct. 9, 2019, 11 pages. |
| Office Action received for Chinese Patent Application No. 201811152097.2, mailed on May 7, 2019, 18 pages. |
| Office Action received for Chinese Patent Application No. 201811152726.1, mailed on Apr. 22, 2019, 15 pages. |
| Office Action received for Chinese Patent Application No. 201811152726.1, mailed on Apr. 28, 2021, 14 pages. |
| Office Action received for Chinese Patent Application No. 201811152726.1, mailed on Jan. 28, 2021, 13 pages. |
| Office Action received for Chinese Patent Application No. 201811152726.1, mailed on Mar. 18, 2020, 12 pages. |
| Office Action received for Chinese Patent Application No. 201811152726.1, mailed on Oct. 24, 2019, 14 pages. |
| Office Action received for Chinese Patent Application No. 201811152726.1, mailed on Oct. 29, 2020, 12 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. 201880056514.5, mailed on Sep. 2, 2020, 7 pages. |
| Office Action received for Chinese Patent Application No. 201910400179.2, mailed on Dec. 27, 2021, 32 pages. |
| Office Action received for Chinese Patent Application No. 201910400180.5, mailed on Jun. 1, 2020, 11 pages. |
| Office Action received for Chinese Patent Application No. 201910704856.X, mailed on Apr. 6, 2021, 13 pages. |
| Office Action received for Chinese Patent Application No. 201910704856.X, mailed on Dec. 9, 2020, 23 pages. |
| Office Action received for Chinese Patent Application No. 201910704856.X, mailed on May 27, 2020, 26 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. 202010126661.4, mailed on Feb. 3, 2021, 16 pages. |
| Office Action received for Chinese Patent Application No. 202010126661.4, mailed on Jun. 2, 2022, 11 pages. |
| Office Action received for Chinese Patent Application No. 202010126661.4, mailed on Mar. 4, 2022, 13 pages. |
| Office Action received for Chinese Patent Application No. 202010742019.9, mailed on Feb. 3, 2021, 17 pages. |
| Office Action received for Chinese Patent Application No. 202011243876.0, mailed on Apr. 6, 2021, 11 pages. |
| Office Action received for Chinese Patent Application No. 202011336156.9, mailed on May 20, 2021, 13 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. 202110235995.X, mailed on Mar. 22, 2022, 17 pages. |
| Office Action received for Chinese Patent Application No. 202110248576.X, mailed on Sep. 15, 2021, 28 pages. |
| Office Action received for Chinese Patent Application No. 202110327012.5, mailed on Apr. 29, 2022, 17 pages. |
| Office Action received for Chinese Patent Application No. 202110328597.2, mailed on Apr. 15, 2022, 18 pages. |
| Office Action received for Chinese Patent Application No. 202110328601.5, mailed on Apr. 27, 2022, 25 pages. |
| Office Action received for Chinese Patent Application No. 202110328602.X, mailed on Mar. 24, 2022, 6 pages. |
| Office Action received for Chinese Patent Application No. 202110818370.6, mailed on Jun. 22, 2022, 7 pages. |
| Office Action received for Chinese Patent Application No. 202110818370.6, mailed on Mar. 2, 2022, 13 pages. |
| Office Action received for Chinese Patent Application No. 202110819254.6, mailed on May 16, 2022, 16 pages. |
| Office Action received for Chinese Patent Application No. 202111612841.4, mailed on Jul. 22, 2022, 13 pages. |
| Office Action Received for Danish Patent Application No. PA201670601, mailed on Apr. 10, 2018, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670601, mailed on Aug. 9, 2018, 2 pages. |
| Office Action Received for Danish Patent Application No. PA201670601, mailed on Dec. 11, 2018, 3 pages. |
| Office Action Received for Danish Patent Application No. PA201670601, mailed on Feb. 6, 2017, 5 pages. |
| Office Action Received for Danish Patent Application No. PA201670601, mailed on Oct. 21, 2016, 9 pages. |
| Office Action Received for Danish Patent Application No. PA201670601, mailed on Sep. 26, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670602, mailed on Apr. 16, 2018, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670602, mailed on Feb. 9, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670602, mailed on Oct. 25, 2016, 9 pages. |
| Office Action received for Danish Patent Application No. PA201670602, mailed on Sep. 26, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670603, mailed on Nov. 1, 2016, 9 pages. |
| Office Action received for Danish Patent Application No. PA201670604, mailed on Feb. 19, 2018, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670604, mailed on Jun. 9, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670604, mailed on Nov. 8, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201670605, mailed on Apr. 9, 2018, 2 pages. |
| Office Action received for Danish Patent Application No. PA201670605, mailed on Feb. 19, 2018, 2 pages. |
| Office Action received for Danish Patent Application No. PA201670605, mailed on Jun. 13, 2017, 4 pages. |
| Office Action received for Danish Patent Application No. PA201670605, mailed on Nov. 14, 2016, 8 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. 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. PA201870293, mailed on Jul. 17, 2018, 2 pages. |
| Office Action received for Danish Patent Application No. PA201870293, mailed on Jun. 19, 2018, 8 pages. |
| Office Action received for Danish Patent Application No. PA201870362, mailed on Aug. 22, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870362, mailed on Dec. 18, 2018, 2 pages. |
| Office Action received for Danish Patent Application No. PA201870363, mailed on Mar. 26, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870364, mailed on Jan. 28, 2019, 8 pages. |
| Office Action received for Danish Patent Application No. PA201870364, mailed on Jun. 11, 2019, 11 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. PA201870435, mailed on Feb. 6, 2020, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870435, mailed on May 2, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870435, mailed on May 25, 2020, 3 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 European Patent Application No. 15729286.3, mailed on Feb. 7, 2018, 7 pages. |
| Office Action received for European Patent Application No. 15728307.8, mailed on Feb. 8, 2018, 7 pages. |
| Office Action received for European Patent Application No. 17167629.9, mailed on Jan. 25, 2019, 7 pages. |
| Office Action received for European Patent Application No. 17813777.4, mailed on Jan. 3, 2020, 5 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. 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. 18779093.6, mailed on Dec. 11, 2020, 4 pages. |
| Office Action received for European Patent Application No. 18779093.6, mailed on Mar. 17, 2022, 4 pages. |
| Office Action received for European Patent Application No. 19182037.2, mailed on Jun. 16, 2020, 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. 19728558.8, mailed on Jun. 21, 2021, 9 pages. |
| Office Action received for European Patent Application No. 19729395.4, mailed on Jul. 15, 2020, 4 pages. |
| Office Action received for European Patent Application No. 19729395.4, mailed on Sep. 29, 2020, 10 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. 20166552.8, mailed on Mar. 24, 2021, 8 pages. |
| Office Action received for European Patent Application No. 20187610.9, mailed on May 21, 2021, 7 pages. |
| Office Action received for European Patent Application No. 20205496.1, mailed on Nov. 10, 2021, 5 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. 21160991.2, mailed on Mar. 24, 2022, 11 pages. |
| Office Action received for European Patent Application No. 21161005.0, mailed on Apr. 22, 2022, 11 pages. |
| Office Action received for European Patent Application No. 21197457.1, mailed on Sep. 2, 2022, 8 pages. |
| Office Action received for Indian Patent Application No. 201814036860, mailed on Jul. 29, 2021, 8 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. 202118046028, mailed on Apr. 6, 2022, 6 pages. |
| Office Action received for Japanese Patent Application No. 2017-514992, mailed on Apr. 6, 2018, 11 pages. |
| Office Action received for Japanese Patent Application No. 2018-018497, mailed on Dec. 10, 2018, 8 pages. |
| Office Action received for Japanese Patent Application No. 2018-562659, mailed on Dec. 6, 2019, 7 pages. |
| Office Action received for Japanese Patent Application No. 2018-562659, mailed on Jul. 26, 2019, 9 pages. |
| Office Action received for Japanese Patent Application No. 2018-562659, mailed on Mar. 12, 2021, 79 pages. |
| Office Action received for Japanese Patent Application No. 2018-562659, mailed on May 28, 2020, 5 pages. |
| Office Action received for Japanese Patent Application No. 2019-050138, mailed on Jan. 27, 2020, 9 pages. |
| Office Action received for Japanese Patent Application No. 2019-194597, mailed on Jan. 18, 2021, 10 pages. |
| Office Action received for Japanese Patent Application No. 2020-047952, mailed on Aug. 27, 2021, 13 pages. |
| Office Action received for Japanese Patent Application No. 2020-047952, mailed on Feb. 8, 2021, 6 pages. |
| Office Action received for Japanese Patent Application No. 2020-047952, mailed on Jul. 1, 2022, 8 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-187397, mailed on Mar. 12, 2021, 8 pages. |
| Office Action received for Japanese Patent Application No. 2020-560927, mailed on Dec. 1, 2021, 3 pages. |
| Office Action received for Japanese Patent Application No. 2020-560927, mailed on Jun. 10, 2021, 5 pages. |
| Office Action received for Japanese Patent Application No. 2021-026630, mailed on Aug. 20, 2021, 7 pages. |
| Office Action received for Japanese Patent Application No. 2021-051415, mailed on Jul. 19, 2021, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7038093, mailed on Feb. 13, 2020, 11 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-2020-7031700, mailed on Dec. 15, 2020, 6 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7032110, mailed on Dec. 15, 2020, 6 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7032488, mailed on Feb. 9, 2021, 11 pages. |
| Office Action received for Korean Patent Application No. 10-2021-7017731, mailed on May 30, 2022, 5 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-7029861, mailed on Jan. 25, 2022, 11 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. |
| 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. |
| Olson Parmy, “Delete by Default: Why More Snapchat-Like Messaging Is On Its Way”, Forbes.com, Available Online at https://www.forbes.com/sites/parmyolson/2013/11/22/delete-by-default-why-more-snapchat-like-messaging-is-on-its-way, Nov. 22, 2013, 6 pages. |
| 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. |
| Party Share—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. |
| Result of Consultation received for European Patent Application No. 15728307.8, mailed on Nov. 21, 2019, 7 pages. |
| Result of Consultation received for European Patent Application No. 15729286.3, mailed on Nov. 21, 2019, 6 pages. |
| Result of Consultation received for European Patent Application No. 17167629.9, mailed on Nov. 10, 2020, 3 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. 19182037.2, mailed on Mar. 22, 2021, 5 pages. |
| Result of Consultation received for European Patent Application No. 19728558.8, mailed on Jun. 28, 2022, 4 pages. |
| Result of Consultation received for European Patent Application No. 19729395.4, mailed on Jun. 22, 2021, 3 pages. |
| Result of Consultation received for European Patent Application No. 19729395.4, mailed on Jun. 23, 2021, 3 pages. |
| Result of Consultation received for European Patent Application No. 20158824.1, mailed on May 17, 2022, 7 pages. |
| Result of Consultation received for European Patent Application No. 20187610.9, mailed on Jun. 1, 2022, 3 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. |
| 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. |
| 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. PA201870362, mailed on Sep. 7, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870363, mailed on Sep. 11, 2018, 12 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870364, mailed on Sep. 4, 2018, 12 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. PA201870435, mailed on Oct. 26, 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. |
| 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. |
| 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. |
| Softonic, “Beginners Guide to WhatsApp”, Retrieved from the Internet: https://www.youtube.com/watch?v=1YN36KYDgrk, Apr. 29, 2013, 2 pages. |
| SolarWinds Network Configuration Manager Administrator Guide, Available online at:—https://web.archive.org/web/20141031133207/http://www.solarwinds.com/documentation/orionNCM/docs/OrionNCMAdministratorGuide.pdf, Oct. 31, 2014, 466 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. |
| 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. 15728307.8, mailed on Jun. 28, 2019, 10 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15728307.8, mailed on Mar. 7, 2022, 4 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15729286.3, mailed on Jun. 27, 2019, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15729286.3, mailed on Mar. 10, 2022, 3 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17167629.9, mailed on Jun. 3, 2020, 11 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17813777.4, mailed on Jun. 18, 2020, 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. 18728002.9, mailed on Jun. 3, 2022, 15 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19182037.2, mailed on Nov. 24, 2020, 12 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19728558.8, mailed on Jan. 18, 2022, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19729395.4, mailed on Mar. 11, 2021, 7 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19729395.4, mailed on Mar. 19, 2021, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20187610.9, mailed on Dec. 16, 2021, 12 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20187610.9, mailed on Jan. 27, 2022, 2 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20205496.1, mailed on Sep. 8, 2022, 9 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. |
| Techniqued, “How to Send Voice Messages in WhatsApp”, Published on YouTube.com, Available at: https://www.youtube.com/watch?v=mkJqYO984v0, Aug. 12, 2013, 1 page. |
| 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. |
| Wechat Philippines, “WeChat TVC—Hold to Talk”, available at <https://www.youtube.com/watch?v=E_UxteOWVSo>, May 11, 2013, 1 page. |
| WeChat Wiki, available on <http://web.archive.org/web/20130514131044/http://wechat.wikia.com/wiki/WeChat_Wiki >, May 14, 2013, 12 pages. |
| 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. |
| 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. |
| You can use Line perfectly if you just read this!! , How to use & set up Line, Line convenience book for 50 million people, Japan, El Publishing Co., Ltd., Mar. 10, 2014, pp. 16-55. |
| Yundanfengqingdeqing,“A light cloud and light breeze; How to upload multiple pictures on Sina Weibo”, Baidu Experience, Available Online at: <https://jingyan.baidu.com/article/6181c3e074ad0d152ff15353.html>, Jan. 13, 2014, 12 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/483,542, mailed on Feb. 5, 2024, 3 pages. |
| Extended European Search Report received for European Patent Application No. 23203414.0, mailed on Jan. 26, 2024, 10 pages. |
| Final Office Action received for U.S. Appl. No. 17/483,679, mailed on Feb. 6, 2024, 45 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2023248185, mailed on Jan. 23, 2024, 3 pages. |
| Office Action received for Australian Patent Application No. 2022291522, mailed on Jan. 19, 2024, 2 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. 17/872,736, mailed on Jul. 25, 2023, 2 pages. |
| 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. |
| Notice of Allowance received for U.S. Appl. No. 17/479,897, mailed on Jul. 26, 2023, 7 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/872,736, mailed on Oct. 13, 2023, 4 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/017280, mailed on Jun. 26, 2023, 20 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 Korean Patent Application No. 10-2023-7024157, mailed on Sep. 19, 2023, 7 pages (2 pages of English Translation and 5 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. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/732,204, mailed on Dec. 4, 2023, 5 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/029261, mailed on Nov. 30, 2023, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/029273, mailed on Nov. 30, 2023, 14 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/029282, mailed on Nov. 30, 2023, 17 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/029580, mailed on Nov. 30, 2023, 14 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. |
| 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). |
| 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 Korean Patent Application No. 10-2021-7017731, mailed on Feb. 28, 2023, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| 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. |
| Office Action received for Japanese Patent Application No. 2021-206121, mailed on Feb. 20, 2023, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| 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. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/830,838, mailed on Dec. 16, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/476,404, mailed on Dec. 20, 2022, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 18728002.9, mailed on Dec. 7, 2022, 1 page. |
| 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. |
| Decision of Board of Appeal received for European Patent Application No. 15728307.8, mailed on Dec. 8, 2022, 17 pages. |
| Decision to Grant received for European Patent Application No. 20158824.1, mailed on Dec. 15, 2022, 3 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. |
| Kazmucha, Allyson, “Sonos Controller App for iPhone and iPad Review”, online available at https://www.imore.com/sonos-controller-app-iphone-and-ipad-review, Mar. 1, 2018, 4 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 15729286.3, mailed on Dec. 6, 2022, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/483,679, mailed on Dec. 9, 2022, 31 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. 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 Chinese Patent Application No. 202110327012.5, mailed on Nov. 28, 2022, 16 pages (10 pages of English Translation and 6 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 21161005.0, mailed on Dec. 13, 2022, 9 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. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/989,086, mailed on Aug. 7, 2023, 2 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. 20166552.8, mailed on Jun. 29, 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/732,204, mailed on Aug. 4, 2023, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/740,104, mailed on Aug. 2, 2023, 15 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022204466, mailed on Jul. 25, 2023, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/746,789, mailed on Aug. 9, 2023, 7 pages. |
| Office Action received for Australian Patent Application No. 2022291522, mailed on Jul. 20, 2023, 3 pages. |
| Office Action received for Chinese Patent Application No. 202110328597.2, mailed on Jul. 18, 2023, 21 pages (6 pages of English Translation and 15 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110328602.X, mailed on Jun. 29, 2023, 27 pages (18 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for European Patent Application No. 20720310.0, mailed on Jul. 25, 2023, 11 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 18733381.0, mailed on Jul. 25, 2023, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/742,273, mailed on Mar. 30, 2023, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/950,900, mailed on Jan. 26, 2023, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/077,905, mailed on Apr. 10, 2023, 2 pages. |
| Decision to Refuse received for European Patent Application No. 22209306.4, mailed on Mar. 20, 2023, 2 pages. |
| Final Office Action received for U.S. Appl. No. 17/950,900, mailed on Jan. 23, 2023, 14 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/044592, mailed on Mar. 14, 2023, 22 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2022/044592, mailed on Jan. 16, 2023, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/830,838, mailed on Mar. 30, 2023, 16 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. 17/950,900, mailed on Dec. 1, 2022, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/989,086, mailed on Apr. 12, 2023, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/077,971, mailed on Apr. 3, 2023, 24 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/467,700, mailed on Apr. 7, 2023, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/509,356, mailed on Apr. 7, 2023, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/950,900, mailed on Mar. 7, 2023, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/950,922, mailed on Apr. 5, 2023, 10 pages. |
| Notice of Reasons for Refusal received for Japanese Patent Application No. 2020-047952, mailed on Apr. 3, 2023, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| 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. 202215025361, 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/484,899, mailed on Sep. 12, 2023, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/992,229, mailed on Aug. 28, 2023, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/483,542, mailed on Aug. 25, 2023, 3 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. |
| Final Office Action received for U.S. Appl. No. 17/476,404, mailed on Sep. 12, 2023, 30 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/867,317, mailed on Aug. 30, 2023, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/872,736, mailed on Aug. 30, 2023, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2022-7044372, mailed on Aug. 21, 2023, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/067,350, mailed on Jul. 29, 2024, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/204,888, mailed on Aug. 5, 2024, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/235,291, mailed on Aug. 7, 2024, 2 pages. |
| Decision to Refuse received for Japanese Patent Application No. 2023-022576, mailed on Jul. 26, 2024, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Extended European Search Report received for European Patent Application No. 24159026.4, mailed on Jul. 10, 2024, 9 pages. |
| Intention to Grant received for European Patent Application No. 23168537.1, mailed on Jul. 25, 2024, 8 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2024/017017, mailed on May 15, 2024, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202110744381.4, mailed on Jul. 15, 2024, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2023-097196, mailed on Jul. 29, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2023-571161, mailed on Jul. 30, 2024, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2023-571312, mailed on Jul. 16, 2024, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2024-7019962, mailed on Jul. 16, 2024, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 18/229,989, mailed on Aug. 7, 2024, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/903,946, mailed on Sep. 3, 2024, 2 pages. |
| Final Office Action received for U.S. Appl. No. 17/950,868, mailed on Aug. 29, 2024, 13 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2024/017017, mailed on Aug. 2, 2024, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/389,655, mailed on Aug. 23, 2024, 23 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/484,899, mailed on Aug. 26, 2024, 21 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/903,946, mailed on Aug. 27, 2024, 5 pages. |
| Office Action received for Chinese Patent Application No. 202311321231.8, mailed on Jul. 28, 2024, 9 pages (5 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2023-028786, mailed on Aug. 23, 2024, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 22201007.6, mailed on Aug. 20, 2024, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/830,838, mailed on Mar. 11, 2024, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/978,930, mailed on Mar. 13, 2024, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/992,229, mailed on Mar. 11, 2024, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/067,350, mailed on Mar. 13, 2024, 4 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/032084, mailed on Nov. 27, 2023, 10 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202210463449.6, mailed on Mar. 9, 2024, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for Chinese Patent Application No. 201910704856.X, mailed on Mar. 8, 2024, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| 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 Chinese Patent Application No. 202110817799.3, mailed on Feb. 22, 2024, 24 pages (15 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for European Patent Application No. 22201007.6, mailed on Mar. 13, 2024, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2023-7018775, mailed on Feb. 28, 2024, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/950,868, mailed on Jul. 19, 2024, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/235,291, mailed on Jul. 18, 2024, 3 pages. |
| Extended European Search Report received for European Patent Application No. 24165156.1, mailed on Jul. 16, 2024, 7 pages. |
| Intention to Grant received for European Patent Application No. 21197457.1, mailed on Jul. 9, 2024, 12 pages,. |
| Non-Final Office Action received for U.S. Appl. No. 18/204,888, mailed on Jul. 18, 2024, 21 pages. |
| Non-Final Office Action received for U.S. Patent Application No. 18/380, 116, mailed on Jul. 18, 2024, 16 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 Chinese Patent Application No. 202110744146.7, mailed on Jul. 9, 2024, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-7040599, mailed on Jun. 26, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/830,838, mailed on Jul. 15, 2024, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/229,989, mailed on Jul. 24, 2024, 5 pages. |
| Office Action received for Australian Patent Application No. 2023204647, mailed on Jul. 5, 2024, 3 pages. |
| Office Action received for Chinese Patent Application No. 201910704856.X, mailed on Jun. 23, 2024, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202311185909.4, mailed on Jun. 12, 2024, 18 pages (10 pages of English Translation and 8 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 European Patent Application No. 23203433.0, mailed on Jul. 9, 2024, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/237,341, mailed on Mar. 22, 2024, 4 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/032792, mailed on Jan. 19, 2024, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/032911, mailed on Jan. 4, 2024, 18 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/484,899, mailed on Mar. 21, 2024, 42 pages. |
| Office Action received for Chinese Patent Application No. 201911128105.4, mailed on Mar. 19, 2024, 9 pages (1 page of English Translation and 8 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-2023-7040599, mailed on Mar. 12, 2024, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/830,838, mailed on Jun. 17, 2024, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,899, mailed on Jun. 24, 2024, 4 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 21197457.1, mailed on Jun. 19, 2024, 1 page. |
| Decision on Appeal received for U.S. Appl. No. 17/116,938, mailed on Jun. 14, 2024, 12 pages. |
| Intention to Grant received for European Patent Application No. 20720310.0, mailed on Jun. 13, 2024, 13 pages. |
| 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. 201910704856.X, mailed on Jun. 11, 2024, 33 pages (1 page of English Translation and 32 pages of Official Copy). |
| Avery et al., “Kinect”, Wikipedia, Feb. 26, 2015, 14 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 21197457.1, mailed on May 23, 2024, 5 pages. |
| Extended European Search Report received for European Patent Application No. 24160234.1, mailed on May 28, 2024, 6 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 20720310.0, mailed on Jun. 7, 2024, 7 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/229,989, mailed on May 31, 2024, 18 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2024202768, mailed on Jun. 4, 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). |
| Notice of Allowance received for Korean Patent Application No. 10-2024-7001084, mailed on May 22, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/684,843, mailed on Jun. 5, 2024, 5 pages. |
| Office Action received for European Patent Application No. 22705232.1, mailed on May 27, 2024, 7 pages. |
| Office Action received for Japanese Patent Application No. 2023-571161, mailed on May 28, 2024, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Record of Oral Hearing received for U.S. Appl. No. 17/116,938, mailed on May 29, 2024, 13 pages. |
| Result of Consultation received for European Patent Application No. 20720310.0, mailed on Jun. 4, 2024, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/067,350, mailed on May 28, 2024, 43 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. 202311042451.7, mailed on May 15, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110744381.4, mailed on Mar. 25, 2024, 17 pages (6 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for European Patent Application No. 21789897.2, mailed on May 23, 2024, 12 pages. |
| Decision to Grant received for European Patent Application No. 20746426.4, mailed on May 10, 2024, 2 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). |
| Notice of Allowance received for U.S. Appl. No. 18/375,457, mailed on May 16, 2024, 15 pages. |
| Office Action received for Chinese Patent Application No. 202110744146.7, mailed on Apr. 1, 2024, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Anonymous, “Split Your Screen with IPEVO Visualizer Software”, On IPEVO, Available online at: https://medium.com/ipevo/split-your-screen-with-ipevo-visualizer-software-e9641024d24f, Feb. 24, 2020, 10 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/229,989, mailed on Jun. 28, 2024, 2 pages. |
| Cosmic Mook,“Line laboratory, New function Exhaustive Coverage! LINE 120% Application Guide, Inc.”, Jan. 24, 2018, 7 pages (Official Copy Only). {See Communication Under Rule 37 CFR § 1.98(a) (3)}. |
| Create Confirmation Dialog Box—Matlab Ulconfirm, Online available at: https://www.mathworks.com/help/matlab/ref/uiconfirm.html, 2017, 19 pages. |
| Examiner-Initiated Interview Summary received for U.S. Appl. No. 17/950,868, mailed on Jul. 5, 2024, 2 pages. |
| Intention to Grant received for European Patent Application No. 20719301.2, mailed on Jul. 2, 2024, 9 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 21197457.1, mailed on Jul. 3, 2024, 9 pages. |
| Myoko Mori, “Line Perfect Guidebook [Revised Version]”, Sotec Co. Ltd., Dec. 31, 2013, 5 pages (Official Copy Only). {See Communication Under Rule 37 CFR § 1.98(a) (3)}. |
| Non-Final Office Action received for U.S. Appl. No. 18/228,597, mailed on Jul. 8, 2024, 17 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 U.S. Appl. No. 18/235,291, mailed on Jul. 3, 2024, 18 pages. |
| Octoba, “Enjoy free calls with Line! Part 2”, retrieved from: https://web.archive.org/web/20170923013859/https://octoba.net/archives/line-call2.html, Sep. 23, 2017, 13 pages (Official Copy Only). {See Communication Under Rule 37 CFR § 1.98(a) (3)}. |
| 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). |
| Office Action received for European Patent Application No. 22792995.7, mailed on Jun. 24, 2024, 6 pages. |
| Office Action received for European Patent Application No. 23190753.6, mailed on Jun. 25, 2024, 10 pages. |
| Office Action received for Japanese Patent Application No. 2023-097196, mailed on Jun. 7, 2024, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2024-003876, mailed on Jul. 2, 2024, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Window confirm (), Online available at: https://www.w3schools.com/jsref/met_win_confirm.asp, 2014, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/375,457, mailed on Apr. 11, 2024, 2 pages. |
| Final Office Action received for U.S. Appl. No. 16/830,838, mailed on Apr. 11, 2024, 17 pages. |
| Final Office Action received for U.S. Appl. No. 17/978,930, mailed on Apr. 5, 2024, 28 pages. |
| Intention to Grant received for European Patent Application No. 20746426.4, mailed on Apr. 12, 2024, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/044592, mailed on Apr. 4, 2024, 21 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). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-7044044, mailed on Mar. 14, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/903,946, mailed on Apr. 10, 2024, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/992,229, mailed on Apr. 17, 2024, 9 pages. |
| 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. 202010728711.6, mailed on Feb. 1, 2024, 30 pages (18 pages of English Translation and 12 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 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). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/978,930, mailed on Apr. 26, 2024, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/903,946, mailed on Apr. 22, 2024, 2 pages. |
| Final Office Action received for U.S. Appl. No. 18/237,341, mailed on Apr. 23, 2024, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/950,868, mailed on Apr. 24, 2024, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/138,348, mailed on Apr. 30, 2024, 16 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2023204396, mailed on Apr. 15, 2024, 3 pages. |
| 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 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). |
| Result of Consultation received for European Patent Application No. 20720310.0. mailed on Apr. 17, 2024, 9 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/228,597, mailed on Aug. 8, 2024, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/375,457, mailed on Aug. 16, 2024, 2 pages. |
| Examiner-Initiated Interview Summary received for U.S. Appl. No. 18/234,613, mailed on Aug. 9, 2024, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-149476, mailed on Aug. 2, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7044372, mailed on Jul. 30, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-7011715, mailed on Jul. 25, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 17/978,930, mailed on Aug. 19, 2024, 9 pages. |
| Office Action received for Australian Patent Application No. 2023251497, mailed on Aug. 9, 2024, 2 pages. |
| That Guy who Loves Metv, “Kinect Party Gameplay”, Available online at: https://youtu.be/bkbOlzfyLzc?si=QAAKh_V4aqY0iegL, Oct. 20, 2021, 2 pages. |
| Xbox, “Kinect Tips, Part 3: Gesture Controls”, Available online at: https://youtu.be/VXhhE-I96qQ?si=gLmHbp9jOm-w0fNW, May 7, 2014, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/234,613, mailed on Jan. 10, 2025, 5 pages. |
| Decision to Grant received for European Patent Application No. 21197457.1, mailed on Jan. 7, 2025, 4 pages. |
| Decision to Grant received for European Patent Application No. 22734711.9, mailed on Jan. 7, 2025, 2 pages. |
| Final Office Action received for U.S. Appl. No. 18/228,597, mailed on Jan. 8, 2025, 19 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202311305998.1, mailed on Jan. 2, 2025, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 202311312328.2, mailed on Jan. 3, 2025, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2023-022576, mailed on Dec. 24, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Hearing received for Indian Patent Application No. 202015013360, mailed on Dec. 26, 2024, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2023-028786, mailed on Dec. 2, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2024-0112016, mailed on Dec. 2, 2024, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 14/263,889, mailed on May 26, 2016, 4 pages. |
| Advisory Action received for U.S. Appl. No. 15/725,868, mailed on Dec. 10, 2018, 5 pages. |
| Advisory Action received for U.S. Appl. No. 16/666,073, mailed on Jul. 7, 2020, 5 pages. |
| Advisory Action received for U.S. Appl. No. 17/950,868, mailed on Sep. 24, 2024, 3 pages. |
| Advisory Action received for U.S. Appl. No. 18/204,888, mailed on Dec. 13, 2024, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 14/263,889, mailed on Apr. 15, 2016, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/725,868, mailed on Jul. 25. 2018, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/725,868, mailed on May 13, 2019, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/725,868, mailed on Nov. 20, 2018, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/950,868, mailed on Sep. 10, 2024, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/991,708, mailed on Dec. 16, 2024, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/067,350, mailed on Nov. 26, 2024, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/140,449, mailed on Aug. 27, 2024, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/140,449, mailed on Nov. 26, 2024, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/204,888, mailed on Nov. 27, 2024, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/237,364, mailed on Dec. 17, 2024, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/237,364, mailed on Nov. 8, 2024, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/389,655, mailed on Sep. 20, 2024, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/504,001, mailed on Oct. 29, 2024, 4 pages. |
| Baudisch et al., “Back-of-device interaction allows creating very small touch devices”, Chi 2009—Digital Life, New World:Conference Proceedings And Extended Abstracts; The 27th Annual Chi Conference On Human Factors In Computing Systems. Available online at <http://dx.doi.org/10.1145/1518701.1518995>, Apr. 9, 2009, pp. 1923-1932. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/725,868, mailed on Aug. 23, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/725,868, mailed on Sep. 30, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/666,073, mailed on Apr. 6, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/666,073, mailed on Apr. 26, 2021, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/666,073, mailed on Feb. 22, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/666,073, mailed on Mar. 11, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/684,843, mailed on Oct. 7, 2024, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/745,680, mailed on Nov. 20, 2024, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/848,845, mailed on Dec. 11, 2024, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/950,868, mailed on Nov. 27, 2024, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/992,229, mailed on Oct. 31, 2024, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/138,348, mailed on Nov. 27, 2024, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/234,613, mailed on Nov. 20, 2024, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/234,613, mailed on Oct. 28, 2024, 2 pages. |
| Decision on Appeal received for Korean Patent Application No. 10-2020-7034959, mailed on Jul. 25, 2022, 28 pages (5 pages of English Translation and 23 pages of Official Copy). |
| Decision to Grant received for European Patent Application No. 10763539.3, mailed on Jul. 19, 2018, 3 pages. |
| Decision to Grant received for European Patent Application No. 18188433.9, mailed on Aug. 13, 2020, 3 pages. |
| Decision to Grant received for European Patent Application No. 20719301.2, mailed on Nov. 7, 2024, 3 pages. |
| Decision to Grant received for European Patent Application No. 20720310.0, mailed on Dec. 5, 2024, 2 pages. |
| Decision to Grant received for Japanese Patent Application No. 2023-571312, mailed on Aug. 29, 2024, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Decision to Grant received for Japanese Patent Application No. 2024-003876, mailed on Sep. 2, 2024, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Decision to Refuse received for Japanese Patent Application No. 2013-503731, mailed on Jun. 23, 2014, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Examiner's Pre-Review Report received for Japanese Patent Application No. 2014-212867, mailed on Nov. 4, 2016, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Extended European Search Report received for European Patent Application No. 18188433.9, mailed on Oct. 29, 2018, 8 pages. |
| Extended European Search Report received for European Patent Application No. 24211972.5, mailed on Jan. 2, 2025, 7 pages. |
| Final Office Action received for U.S. Appl. No. 12/794,766, mailed on Nov. 26, 2012, 23 pages. |
| Final Office Action received for U.S. Appl. No. 14/263,889, mailed on Jan. 4, 2016, 9 pages. |
| Final Office Action received for U.S. Appl. No. 15/725,868, mailed on Sep. 27, 2018, 25 pages. |
| Final Office Action received for U.S. Appl. No. 16/666,073, mailed on Apr. 17, 2020, 18 pages. |
| Final Office Action received for U.S. Appl. No. 17/332,829, mailed on Feb. 6, 2023, 19 pages. |
| Final Office Action received for U.S. Appl. No. 17/991,708, mailed on Dec. 30, 2024, 22 pages. |
| Final Office Action received for U.S. Appl. No. 18/067,350, mailed on Oct. 31, 2024, 44 pages. |
| Final Office Action received for U.S. Appl. No. 18/138,348, mailed on Oct. 18, 2024, 10 pages. |
| Final Office Action received for U.S. Appl. No. 18/140,449, mailed on Oct. 18, 2024, 11 pages. |
| Final Office Action received for U.S. Appl. No. 18/204,888, mailed on Nov. 18, 2024, 21 pages. |
| Final Office Action received for U.S. Appl. No. 18/237,364, mailed on Nov. 27, 2024, 13 pages. |
| Grothaus, Michael, “WhatsApp Introduces Major New Audio Features”, Engadget, Available at <http://www.engadget.com/2013/08/07/whatsapp-introduces-major-new-audio-features/>, Aug. 7, 2013, 4 pages. |
| Intention to Grant received for European Patent Application No. 10763539.3, mailed on Mar. 15, 2018, 6 pages. |
| Intention to Grant received for European Patent Application No. 18188433.9, mailed on Apr. 6, 2020, 9 pages. |
| Intention to Grant received for European Patent Application No. 20720310.0, mailed on Oct. 7, 2024, 14 pages. |
| Intention to Grant received for European Patent Application No. 21197457.1, mailed on Nov. 21, 2024, 12 pages. |
| Intention to Grant received for European Patent Application No. 21197457.1, mailed on Oct. 24, 2024, 12 pages. |
| Intention to Grant received for European Patent Application No. 21789897.2, mailed on Nov. 12, 2024, 9 pages. |
| Intention to Grant received for European Patent Application No. 22734711.9, mailed on Sep. 13, 2024, 7 pages. |
| Intention to Grant received for European Patent Application No. 23168537.1, mailed on Dec. 2, 2024, 8 pages. |
| Intention to Grant received for European Patent Application No. 24160234.1, mailed on Nov. 4, 2024, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2010/050311, mailed on Oct. 18, 2012, 11 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2023/017280, mailed on Oct. 17, 2024, 15 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2023/020569, mailed on Nov. 21, 2024, 16 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2023/024279, mailed on Dec. 12, 2024, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2010/050311, mailed on Aug. 24, 2011, 15 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2024/023231. mailed on Oct. 23, 2024, 24 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2010/050311, mailed on Dec. 21, 2010, 6 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2024/023231, mailed on Aug. 29, 2024, 17 pages. |
| Koyama, Kaori, “Mac Fan Macintosh Master Book Mac OS X v10.4 “Tiger” & iLife”, '06 version, Mainichi Communications Inc. Nobuyuki Nakagawa, Jul. 9, 2007, 4 pages (Official) Copy Only).{See Communication Under Rule 37 CFR § 1.98(a) (3)}. |
| Non-Final Office Action received for U.S. Appl. No. 12/794,766, mailed on Aug. 5, 2013, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/794,766, mailed on Jun. 25, 2012, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 12/794,768. mailed on Oct. 10, 2012, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/263,889, mailed on Jul. 2, 2015, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/263,889, mailed on Jul. 26, 2016, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/725,868. mailed on Apr. 27, 2018, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/725,868, mailed on Feb. 12, 2019, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/666,073, mailed on Dec. 10, 2019, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/332,829, mailed on Aug. 1, 2022, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/991,708, mailed on Oct. 22, 2024, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/140,449, mailed on May 24, 2024, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/237,364, mailed on Sep. 25, 2024, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/504,001, mailed on Oct. 9, 2024, 28 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2010350749, mailed on Jan. 13, 2015. 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015201127, mailed on Feb. 14, 2017, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2023204647, mailed on Oct. 28, 2024, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2023251497, mailed on Sep. 19, 2024, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2023266353, mailed on Oct. 1, 2024, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2024200283, mailed on Nov. 13, 2024, 3 pages. |
| Notice of Allowance received for Brazilian Patent Application No. BR112012025746-3, mailed on Jul. 6, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201010602653.9, mailed on Nov. 15, 2014, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 2010106600623.4, mailed on Aug. 11, 2014, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201410575145.4, mailed on May 10, 2018, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201910704856.X, mailed on Sep. 30, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 202010728844.3, mailed on Sep. 29, 2024, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 202080032669.2, mailed on Nov. 11, 2024, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 202110817799.3, mailed on Dec. 1, 2024, 3 pages (2 pages of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2014-212867, mailed on Mar. 30, 2018, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2016-151497, mailed on Jun. 4, 2018, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2019-182484, mailed on Aug. 30. 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-154573, mailed on Nov. 11, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2022-197327, mailed on May 31, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2012-7028535, mailed on Jul. 16, 2014, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2014-7005164, mailed on Dec. 21, 2014, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2014-7029838, mailed on Jul. 28, 2015, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2015-7007050, mailed on Feb. 26, 2016, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7014580, mailed on Dec. 17, 2019, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7036975, mailed on Sep. 18, 2019, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7002845, mailed on Sep. 24. 2020, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7032414, mailed on Nov. 27, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-7005442, mailed on Jan. 22, 2024, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-7018775, mailed on Sep. 30, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-7040599, mailed on Oct. 18, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2024-7028393, mailed on Nov. 29, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Mexican Patent Application No. MX/a/2012/011623, mailed on Jan. 16, 2014, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Mexican Patent Application No. MX/a/2014/004295, mailed on May 21, 2015, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Mexican Patent Application No. MX/a/2015/010523, mailed on May 25, 2016, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Mexican Patent Application No. MX/a/2016/012174, mailed on Jan. 17, 2020, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Mexican Patent Application No. MX/a/2020/003290, mailed on Feb. 9, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 099132253, mailed on Apr. 27, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 099132254, mailed on Feb. 18, 2014, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 12/794,766, mailed on Jan. 17, 2014, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/794,768, mailed on Mar. 22, 2013, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/263,889, mailed on Feb. 1, 2017, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/263,889, mailed on Jun. 16, 2017, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/725,868, mailed on Jun. 12, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/666,073, mailed on Jan. 21, 2021, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/116,938, mailed on Sep. 18, 2024, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/483,679, mailed on Nov. 21, 2024, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/684,843, mailed on Sep. 17, 2024, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/745,680, mailed on Dec. 12, 2024, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/745,680, malled on Nov. 12, 2024, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/848,845, mailed on Oct. 11, 2024, 26 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/950,868, mailed on Oct. 23, 2024, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/992,229, mailed on Oct. 22, 2024, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/077,891, mailed on Dec. 10, 2024, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/138,348, mailed on Nov. 13, 2024, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/234,613, mailed on Dec. 12, 2024, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/234,613, mailed on Oct. 11, 2024, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/389,655, mailed on Nov. 27, 2024, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/627,363, mailed on Dec. 20, 2024, 14 pages. |
| Office Action received for Australian Patent Application No. 2010350749, mailed on Oct. 16, 2013, 3 pages. |
| Office Action received for Australian Patent Application No. 2015201127, mailed on Mar. 21, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2023204647, mailed on Sep. 19, 2024, 2 pages. |
| Office Action received for Australian Patent Application No. 2023266353, mailed on Sep. 19, 2024, 2 pages. |
| Office Action received for Australian Patent Application No. 2024200283, mailed on Oct. 8, 2024, 2 pages. |
| Office Action received for Brazilian Patent Application No. BR112012025746-3, mailed on Jun. 2, 2020, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201010602653.9, mailed on Apr. 1, 2013, 21 pages (13 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201010602653.9, mailed on Dec. 9, 2013, 10 pages (6 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201010602653.9, mailed on May 15, 2014, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 2010106600623.4, mailed on Apr. 28, 2014, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 2010106600623.4, mailed on Jan. 24, 2014, 7 pages (4 pages of English Translation and 3 pages of Official Copy). . |
| Office Action received for Chinese Patent Application No. 2010106600623.4, mailed on May 2, 2013, 27 pages (15 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201410575145.4, mailed on Feb. 13, 2017, 18 pages (11 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201410575145.4, mailed on Nov. 30, 2017, 17 pages (11 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202080032669.2, mailed on Sep. 20, 2024, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202110817799.3, mailed on Sep. 4, 2024, 23 pages (15 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202310794146.7, mailed on Aug. 30, 2024, 18 pages (11 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202310794146.7, mailed on Nov. 13, 2024, 17 pages (11 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202311305998.1, mailed on Oct. 19, 2024, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202311753064.4, mailed on Aug. 23. 2024, 18 pages (11 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202311831154.0, mailed on Aug. 30, 2024, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202311835200.4, mailed on Aug. 29, 2024, 16 pages (7 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202410030102.1, mailed on Jul. 23, 2024, 18 pages (9 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202410229610.2, malled on Dec. 2, 2024, 14 pages (8 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202410229610.2, mailed on Sep. 3, 2024, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for European Patent Application No. 10763539.3, mailed on Jun. 13, 2016, 5 pages. |
| Office Action received for European Patent Application No. 22196865.4, mailed on Oct. 18, 2024, 6 pages. |
| Office Action received for European Patent Application No. 22705232.1, mailed on Sep. 26, 2024, 8 pages. |
| Office Action received for European Patent Application No. 22733778.9, mailed on Oct. 22, 2024, 6 pages. |
| Office Action received for European Patent Application No. 22792995.7, mailed on Oct. 15, 2024, 8 pages. |
| Office Action received for Japanese Patent Application No. 2013-503731, mailed on Mar. 3, 2014, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2013-503731, mailed on Sep. 24, 2013, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2014-212867, mailed on Aug. 18, 2017, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2014-212867, mailed on Jun. 29, 2015, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-151497, mailed on Sep. 25, 2017, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-127760, mailed on Feb. 22, 2019, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-127760, mailed on Jul. 5, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2019-182484, mailed on Dec. 4, 2020, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2022-197327, mailed on Mar. 1, 2024, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2023-572748, mailed on Jul. 29, 2024, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2024-146741, mailed on Nov. 24, 2024, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2012-7028535, mailed on Nov. 26, 2013, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2014-7005164, mailed on May 23, 2014, 15 pages (6 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2014-7029838, mailed on Dec. 20, 2014, 13 pages (5 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2015-7007050, mailed on Apr. 16, 2015, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2015-7007050, mailed on Oct. 23, 2015, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014580, mailed on Jan. 30, 2018, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014580, mailed on Jul. 30, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014580, mailed on Jun. 29, 2017, 7 pages (1 page of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014580, mailed on Sep. 19, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014580, mailed on Sep. 27, 2016, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7002774. mailed on Apr. 18, 2017, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7002774, mailed on Jul. 30, 2018, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7002774, mailed on Sep. 20, 2018, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7036975, mailed on Mar. 22, 2019, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7002845, mailed on Feb. 17, 2020, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7034959, mailed on Jan. 27, 2022, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7034959, mailed on Mar. 2, 2021. 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7034959, mailed on Oct. 27, 2021, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7006973. mailed on May 19, 2022, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7006973, mailed on Nov. 24, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2023-7005442. mailed on Jul. 25, 2023, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2024-7019962, mailed on Sep. 25, 2024, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2024-7028393, mailed on Sep. 24, 2024, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2014/004295, mailed on Aug. 21, 2014, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2014/004295, mailed on Jan. 20, 2015, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2015/010523. mailed on Jan. 26, 2016, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2016/012174, mailed on Apr. 10, 2019, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2016/012174, mailed on Aug. 8, 2019, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2020/003290, mailed on Nov. 11, 2022, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2020/003290, mailed on Oct. 26, 2022, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2023/005388, mailed on Dec. 15, 2023, 18 pages (9 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Mexican Patent Application No. MX/a/2023/005388, mailed on Jun. 2, 2023. 24 pages (12 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 099132253, mailed on Jun. 24, 2013, 16 pages (8 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 099132253, mailed on Mar. 27, 2014, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 099132254, mailed on May 27, 2013, 24 pages (12 pages of English Translation and 12 pages of Official Copy). |
| Prabeesh RK., “Android Studio Tutorial-17—Highlight selected item in a ListView”, Available Online at: https://www.youtube.com/watch?v=W6bBYmXP0HY, Feb. 24, 2015, 5 pages. |
| Samsung, “SM-G900F User Manual”, English (EU). Rev.1.0, Mar. 2014, 249 pages. |
| Sharf et al., “SnapPaste:an interactive technique for easy mesh composition”, The Visual Computer; International Journal Of Computer Graphics, Springer, Berlin, DE, vol. 22, No. 9-11. Available Online at <http://dx.doi.org/10.1007/s00371-006-0068-5>, Aug. 25, 2006, pp. 835-844. |
| Sony Ericsson Mobile Comm., “User guide SmartWatch MN2”, Available online at: https://manualzz.com/doc/23127468/sony-smartwatch-mn2-user-guide, Dec. 2011, 19 pages. |
| Sony, “Sony Smartwatch 3 SWR50”, User Guide, Jul. 2014, 31 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/484,899, mailed on Oct. 29, 2024, 5 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/484,899, mailed on Sep. 30, 2024, 5 pages. |
| Szogyenyi, Zina, “Improving the usability of multi-selecting from a long list”, Available online at: https://medium.com/tripaneer-techblog/improving-the-usability-of-multi-selecting-from-a-long-list-63e1a67aab35, Jun. 13, 2018, 12 pages. |
| “User Manual”, Available online at<http://www.manualslib.com/download/754923/Samsung-Gear-2.html>, Apr. 9, 2014, 97 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. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/950,900, mailed on Jun. 30, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/989,086, mailed on Jun. 22, 2023, 2 pages. |
| Examiner Interview Summary received for U.S. Appl. No. 17/903,946, mailed on Jun. 28, 2023, 2 pages. |
| Final Office Action received for U.S. Appl. No. 16/830,838, mailed on Jun. 26, 2023, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/746,789, mailed on Jun. 22, 2023, 8 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-047952, mailed on Jun. 26, 2023, 25 pages (1 page of English Translation and 24 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). |
| Office Action received for European Patent Application No. 18779093.6, mailed on Jun. 28, 2023, 4 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230041125 A1 | Feb 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 63041979 | Jun 2020 | US | |
| 63023225 | May 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17027373 | Sep 2020 | US |
| Child | 17970417 | US |
