Patent Grant
11835985
This relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that capture, display and/or otherwise manipulate digital content taken or recorded by cameras.
The use of electronic devices for capturing, viewing, editing, and sharing digital content has increased significantly in recent years. Users frequently record digital content (e.g., images and/or videos) with their portable electronic devices (e.g., smart phones, tablets, and dedicated digital cameras); view and edit their digital content in image management applications (e.g., Photos from Apple Inc. of Cupertino, California) and/or digital content management applications (e.g., iTunes from Apple Inc. of Cupertino, California); and share their digital content with others through instant messages, email, social media applications, and other communication applications.
Portable electronic devices typically capture two types of digital content: still images and video. A still image is typically captured by simply pressing a shutter button. The still image freezes an instant in time, but details of the moment surrounding that instant are lost. Videos record extended periods of time, which may include both interesting moments and not-so-interesting moments. Significant editing is typically required to remove the less interesting moments.
Accordingly, there is a need for electronic devices with improved methods and interfaces for capturing and interacting with moments taken or recorded by cameras. Such methods and interfaces optionally complement or replace conventional methods for capturing and interacting with still images and video.
The disclosed devices expand photography beyond the still image by providing new and improved methods for capturing and interacting with moments. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch-screen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, note taking, and/or digital video playing. 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.
In accordance with some embodiments, a method is performed at an electronic device with a display and a camera. The method includes, while in a first media acquisition mode for the camera, displaying a live preview on the display. The method further includes, while displaying the live preview, detecting activation of a shutter button at a first time, and, in response to detecting activation of the shutter button at the first time, grouping a plurality of images acquired by the camera in temporal proximity to the activation of the shutter button at the first time into a first sequence of images. The first sequence of images includes: a plurality of images acquired by the camera prior to detecting activation of the shutter button at the first time; a representative image that represents the first sequence of images and was acquired by the camera after one or more of the other images in the first sequence of images; and a plurality of images acquired by the camera after acquiring the representative image.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method includes displaying a representative image on the display. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images also includes one or more images acquired by the camera before acquiring the representative image. The method includes, while displaying the representative image on the display, detecting a first portion of a first input and, in response to detecting the first portion of the first input, replacing display of the representative image with display, in sequence, of the one or more images acquired by the camera after acquiring the representative image. The method further includes, after detecting the first portion of the first input, detecting a second portion of the first input, and, in response to detecting the second portion of the first input, displaying, in sequence, the one or more images acquired by the camera before acquiring the representative image, the representative image, and the one or more images acquired by the camera after acquiring the representative image.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method includes displaying a representative image on the display. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. The method further includes, while displaying the representative image on the display, detecting a first portion of a first input. The method further includes, in response to detecting the first portion of the first input, transitioning from displaying the representative image to displaying a respective prior image in the sequence of images, where the respective prior image was acquired by the camera before acquiring the representative image. The method further includes, in response to detecting the first portion of the first input, after transitioning from displaying the representative image to displaying the respective prior image, displaying, in sequence starting with the respective prior image, at least some of the one or more images acquired by the camera before acquiring the representative image and at least some of the one or more images acquired by the camera after acquiring the representative image.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface. The method includes displaying a representative image on the display. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The method further includes, while displaying the representative image on the display, detecting a first input that includes detecting an increase in a characteristic intensity of a contact on the touch-sensitive surface to a first intensity that is greater than a first intensity threshold. The method further includes, in response to detecting the increase in the characteristic intensity of the contact, advancing, in a first direction, through the one or more images acquired by the camera after acquiring the representative image at a rate that is determined based at least in part on the first intensity. The method further includes, after advancing through the one or more images acquired by the camera after acquiring the representative image at the rate that is determined based on the first intensity, detecting a decrease in intensity of the contact to a second intensity that is less than the first intensity. The method further includes, in response to detecting the decrease in the characteristic intensity of the contact to the second intensity, in accordance with a determination that the second intensity is above the first intensity threshold, continuing to advance, in the first direction, through the one or more images acquired by the camera after acquiring the representative image at a second rate. The second rate is determined based at least in part on the second intensity and the second rate is slower than the first rate. The method further includes, in response to detecting the decrease in the characteristic intensity of the contact to the second intensity, in accordance with a determination that the second intensity is below the first intensity threshold, moving, in a second direction that is opposite to the first direction, through the one or more images acquired by the camera after acquiring the representative image at a rate that is determined based at least in part on the second intensity.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method includes storing a plurality of sequences of images. A respective sequence of images includes a respective representative image taken by a camera, one or more images acquired by the camera after acquiring the respective representative image, and one or more images acquired by the camera before acquiring the respective representative image. The method further includes displaying a first representative image for a first sequence of images in a movable first area on the display. The method further includes detecting a drag gesture on the touch-sensitive surface. The method further includes, in accordance with a determination that the drag gesture is in a first direction on the touch-sensitive surface: in the moveable first area, replacing display of the first representative image for the first sequence of images with display, in chronological order, of at least some of one or more images for the first sequence of images acquired by the camera after acquiring the first representative image for the first sequence of images. The method further includes moving the first area in the first direction.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method includes storing a plurality of sequences of images. A respective sequence of images includes: a respective representative image taken by a camera, and one or more images acquired by the camera before acquiring the respective representative image. The method further includes displaying a first representative image for a first sequence of images in a movable first area on the display. The method further includes detecting a gesture on the touch-sensitive surface, the gesture including movement by a contact that corresponds to movement in a first direction on the display. The method further includes, in response to detecting the gesture on the touch-sensitive surface: moving the first area in the first direction on the display; moving a movable second area in the first direction on the display; and, in accordance with a determination that sequence-display criteria are met, while moving the second area in the first direction, displaying, in chronological order in the second area, at least some of the one or more images for a second sequence of images acquired by the camera before acquiring a second representative image for the second sequence of images.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method includes storing a plurality of sequences of images. A respective sequence of images includes: a respective representative image taken by a camera, one or more images acquired by the camera after acquiring the respective representative image, and one or more images acquired by the camera before acquiring the respective representative image. The method further includes storing a plurality of images that are distinct from the images in the plurality of sequences of images. A respective image in the plurality of images is not part of a sequence of images in the plurality of sequences of images. The method further includes displaying a first image on the display and, while displaying the first image on the display, detecting a first input. The method further includes, in response to detecting the first input: in accordance with a determination that the first image is an image in a first sequence of images, performing a first operation that includes displaying at least some of the images in the first sequence of images besides the first image. The method further includes, in accordance with a determination that the first image is an image in the plurality of images that are distinct from the images in the plurality of sequences of images, performing a second operation, distinct from the first operation, involving the first image.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method includes displaying a representative image on the display. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. The method further includes, while displaying the representative image on the display, detecting an input to modify the representative image. The method further includes, in response to detecting the input to modify the representative image: in accordance with a determination that the device is in a first editing mode, modifying the representative image, the one or more images acquired by the camera after acquiring the representative image, and the one or more images acquired by the camera before acquiring the representative image; and, in accordance with a determination that the device is in a second editing mode, distinct from the first editing mode, modifying the representative image, without modifying the one or more images acquired by the camera after acquiring the representative image, and without modifying the one or more images acquired by the camera before acquiring the representative image.
In accordance with some embodiments, a method is performed at a first electronic device with a display. The method includes displaying, on the display, a representative image in a user interface of an application that is configured to communicate with other electronic devices. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. The method further includes, while displaying the representative image on the display, detecting an input that corresponds to a request to send the representative image or a request to select the representative image for sending to a second electronic device, remote from the first electronic device, using the application. The method further includes, in response to detecting the input that corresponds to the request to send the representative image or to the request to select the representative image for sending to the second electronic device: in accordance with a determination that the second electronic device is configured to interact with the sequence of images as a group, displaying a first set of options for sending at least a portion of the sequence of images to the second electronic device; and, in accordance with a determination that the second electronic device is not configured to interact with the sequence of images as a group, displaying a second set of options for sending at least a portion of the sequence of images to the second electronic device, wherein the second set of options is different from the first set of options.
In accordance with some embodiments, a method is performed at an electronic device with a display and a camera. The method includes, while in a first media acquisition mode for the camera, displaying a live preview of a scene on the display and performing scene recognition on the scene. The method further includes, while displaying the live preview of the scene, detecting a single activation of a shutter button at a first time. The method further includes, in response to detecting the single activation of the shutter button at the first time, in accordance with a determination that the scene meets action capture criteria, based at least in part on the scene recognition performed on the scene, retaining a plurality of images acquired by the camera in temporal proximity to the activation of the shutter button at the first time and grouping the plurality of images into a first sequence of images. The first sequence of images includes: a plurality of images acquired by the camera prior to detecting activation of the shutter button at the first time; a representative image that represents the first sequence of images and was acquired by the camera after one or more of the other images in the first sequence of images; and a plurality of images acquired by the camera after acquiring the representative image. The method further includes, in response to detecting the single activation of the shutter button at the first time, in accordance with a determination that the scene does not meet the action capture criteria, retaining a single image in temporal proximity to the activation of the shutter button at the first time.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method includes displaying an image on the display. The image is one image in a sequence of images taken by a camera. The sequence of images includes a representative image. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. The method further includes, while displaying the image in the sequence of images on the display, detecting a first input. The method further includes, in response to detecting the first input: displaying a user interface for trimming the sequence of images to a subset, less than all, of the sequence of images. The user interface includes: an area that contains representations of images in the sequence of images; a user-adjustable begin-trim icon that delimits a beginning image in the subset of the sequence of images via a position of the begin-trim icon in the area that contains representations of images in the sequence of images; and a user-adjustable end-trim icon that delimits an ending image in the subset of the sequence of images via a position of the end-trim icon in the area that contains representations of images in the sequence of images. The begin-trim icon is located at a first position, in the area that contains representations of images in the sequence of images, that is automatically selected by the device. The end-trim icon is located at a second position, in the area that contains representations of images in the sequence of images, that is automatically selected by the device. The method further includes, while displaying the user interface for trimming the sequence of images, detecting a second input. The method further includes, in response to detecting a second input, trimming the sequence of images to the subset of the sequence of images in accordance with a current position of the begin-trim icon and a current position of the end-trim icon.
In accordance with some embodiments, an electronic device includes a display unit configured to display a live preview, a camera unit configured to acquire images, and a processing unit coupled with the display unit and the camera unit. The processing unit is configured to, while in a first media acquisition mode for the camera unit, display the live preview on the display unit. The processing unit is further configured to, while displaying the live preview, detect activation of a shutter button at a first time, and, in response to detecting activation of the shutter button at the first time, group a plurality of images acquired by the camera unit in temporal proximity to the activation of the shutter button at the first time into a first sequence of images. The first sequence of images includes: a plurality of images acquired by the camera unit prior to detecting activation of the shutter button at the first time; a representative image that represents the first sequence of images and was acquired by the camera unit after one or more of the other images in the first sequence of images; and a plurality of images acquired by the camera unit after acquiring the representative image.
In accordance with some embodiments, an electronic device includes a display unit configured to display images, a touch-sensitive surface unit configured to detect user inputs, and a processing unit coupled with the display unit and the touch-sensitive surface unit. The processing unit is configured to display a representative image on the display unit. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. The processing unit is further configured to, while displaying the representative image on the display unit, detect a first portion of a first input. The processing unit is further configured to, in response to detecting the first portion of the first input, replace display of the representative image with display, on the display unit, in sequence, of the one or more images acquired by the camera after acquiring the representative image. The processing unit is further configured to, after detecting the first portion of the first input, detect a second portion of the first input. The processing unit is further configured to, in response to detecting the second portion of the first input, display, on the display unit, in sequence, the one or more images acquired by the camera before acquiring the representative image, the representative image, and the one or more images acquired by the camera after acquiring the representative image.
In accordance with some embodiments, an electronic device includes a display unit configured to display images, a touch-sensitive surface unit configured to detect user inputs, and a processing unit coupled with the display unit and the touch-sensitive surface unit. The processing unit is configured to enable display of a representative image on the display unit. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. The processing unit is further configured to, while enabling display of the representative image on the display unit, detect a first portion of a first input. The processing unit is further configured to, in response to detecting the first portion of the first input: transition from displaying the representative image to displaying a respective prior image in the sequence of images, wherein the respective prior image was acquired by the camera before acquiring the representative image; and, after transitioning from displaying the representative image to displaying the respective prior image, enable display of, in sequence starting with the respective prior image, at least some of the one or more images acquired by the camera before acquiring the representative image and at least some of the one or more images acquired by the camera after acquiring the representative image.
In accordance with some embodiments, an electronic device includes a display unit configured to display images, a touch-sensitive surface unit configured to detect user inputs, one or more sensors units configured to detect intensity of contacts with the touch-sensitive surface unit, and a processing unit coupled with the display unit, the touch-sensitive surface unit, and the one or more sensors. The processing unit is configured to enable display of a representative image on the display unit. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The processing unit is further configured to, while enabling display of the representative image on the display unit, detect a first input that includes detecting an increase in a characteristic intensity of a contact on the touch-sensitive surface unit to a first intensity that is greater than a first intensity threshold. The processing unit is further configured to, in response to detecting the increase in the characteristic intensity of the contact, advance, in a first direction, through the one or more images acquired by the camera after acquiring the representative image at a rate that is determined based at least in part on the first intensity. The processing unit is further configured to, after advancing through the one or more images acquired by the camera after acquiring the representative image at the rate that is determined based on the first intensity, detect a decrease in intensity of the contact to a second intensity that is less than the first intensity. The processing unit is further configured to, in response to detecting the decrease in the characteristic intensity of the contact to the second intensity: in accordance with a determination that the second intensity is above the first intensity threshold, continue to advance, in the first direction, through the one or more images acquired by the camera after acquiring the representative image at a second rate. The second rate is determined based at least in part on the second intensity and the second rate is slower than the first rate. The processing unit is further configured to, in response to detecting the decrease in the characteristic intensity of the contact to the second intensity: in accordance with a determination that the second intensity is below the first intensity threshold, move, in a second direction that is opposite to the first direction, through the one or more images acquired by the camera after acquiring the representative image at a rate that is determined based at least in part on the second intensity.
In accordance with some embodiments, an electronic device includes a display unit configured to display images, a touch-sensitive surface unit configured to detect user inputs, a memory unit configured to store images, and a processing unit coupled with the display unit, the memory unit, and the touch-sensitive surface unit. The processing unit is configured to store, in the memory unit, a plurality of sequences of images. A respective sequence of images includes: a respective representative image taken by a camera, one or more images acquired by the camera after acquiring the respective representative image, and one or more images acquired by the camera before acquiring the respective representative image. The processing unit is further configured to display, on the display unit, a first representative image for a first sequence of images in a movable first area on the display unit. The processing unit is further configured to detect a drag gesture on the touch-sensitive surface unit. The processing unit is further configured to, in accordance with a determination that the drag gesture is in a first direction on the touch-sensitive surface unit: in the moveable first area, replace display of the first representative image for the first sequence of images with display, on the display unit, in chronological order, of at least some of one or more images for the first sequence of images acquired by the camera after acquiring the first representative image for the first sequence of images, and move the first area in the first direction on the display unit.
In accordance with some embodiments, an electronic device includes a display unit configured to display images, a touch-sensitive surface unit configured to detect user inputs, and a processing unit coupled with the display unit and the touch-sensitive surface unit. The processing unit is configured to store a plurality of sequences of images. A respective sequence of images includes: a respective representative image taken by a camera, and one or more images acquired by the camera before acquiring the respective representative image. The processing unit is further configured to enable display of a first representative image for a first sequence of images in a movable first area on the display unit. The processing unit is configured to detect a gesture on the touch-sensitive surface unit, the gesture including movement by a contact that corresponds to movement in a first direction on the display unit. The processing unit is configured to, in response to detecting the gesture on the touch-sensitive surface unit: move the first area in the first direction on the display unit; move a movable second area in the first direction on the display unit; and, in accordance with a determination that sequence-display criteria are met, while moving the second area in the first direction, enable display of, in chronological order in the second area, at least some of the one or more images for a second sequence of images acquired by the camera before acquiring a second representative image for the second sequence of images.
In accordance with some embodiments, an electronic device includes a display unit configured to display images, a touch-sensitive surface unit configured to detect user inputs, a memory unit configured to store images, and a processing unit coupled with the display unit, the memory unit, and the touch-sensitive surface unit. The processing unit is configured to store, in the memory unit, a plurality of sequences of images. A respective sequence of images includes a respective representative image taken by a camera, one or more images acquired by the camera after acquiring the respective representative image, and one or more images acquired by the camera before acquiring the respective representative image. The processing unit is further configured to store, in the memory unit, a plurality of images that are distinct from the images in the plurality of sequences of images. A respective image in the plurality of images is not part of a sequence of images in the plurality of sequences of images. The processing unit is further configured to display a first image on the display unit. The processing unit is further configured to, while displaying the first image on the display unit, detect a first input. The processing unit is further configured to, in response to detecting the first input: in accordance with a determination that the first image is an image in a first sequence of images, perform a first operation that includes displaying, on the display unit, at least some of the images in the first sequence of images besides the first image. The processing unit is further configured to, in accordance with a determination that the first image is an image in the plurality of images that are distinct from the images in the plurality of sequences of images, perform a second operation, distinct from the first operation, involving the first image.
In accordance with some embodiments, an electronic device includes a display unit configured to display images, a touch-sensitive surface unit configured to detect user inputs, and a processing unit coupled with the display unit and the touch-sensitive surface unit. The processing unit is configured to enable display of a representative image on the display unit. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. The processing unit is further configured to, while enabling display of the representative image on the display unit, detect an input to modify the representative image. The processing unit is configured to, in response to detecting the input to modify the representative image: in accordance with a determination that the device is in a first editing mode, modify the representative image, the one or more images acquired by the camera after acquiring the representative image, and the one or more images acquired by the camera before acquiring the representative image; and, in accordance with a determination that the device is in a second editing mode, distinct from the first editing mode, modify the representative image, without modifying the one or more images acquired by the camera after acquiring the representative image, and without modifying the one or more images acquired by the camera before acquiring the representative image.
In accordance with some embodiments, an electronic device includes a display unit configured to display images and a processing unit coupled with the display unit. The processing unit is configured to enable display, on the display unit, of a representative image in a user interface of an application that is configured to communicate with other electronic devices. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. The processing unit is further configured to, while enabling display of the representative image on the display unit, detect an input that corresponds to a request to send the representative image or a request to select the representative image for sending to a second electronic device, remote from the electronic device, using the application. The processing unit is further configured to, in response to detecting the input that corresponds to the request to send the representative image or to the request to select the representative image for sending to the second electronic device: in accordance with a determination that the second electronic device is configured to interact with the sequence of images as a group, enable display of a first set of options for sending at least a portion of the sequence of images to the second electronic device; and, in accordance with a determination that the second electronic device is not configured to interact with the sequence of images as a group, enable display of a second set of options for sending at least a portion of the sequence of images to the second electronic device, wherein the second set of options is different from the first set of options.
In accordance with some embodiments, an electronic device includes a display unit configured to display images, a camera unit configured to acquire images, and a processing unit coupled with the display unit and the camera unit. The processing unit is configured to, while in a first media acquisition mode for the camera unit, enable display of a live preview of a scene on the display unit and perform scene recognition on the scene. The processing unit is further configured to, while enabling display of the live preview of the scene, detect a single activation of a shutter button at a first time. The processing unit is further configured to, in response to detecting the single activation of the shutter button at the first time: in accordance with a determination that the scene meets action capture criteria, based at least in part on the scene recognition performed on the scene, retain a plurality of images acquired by the camera unit in temporal proximity to the activation of the shutter button at the first time and group the plurality of images into a first sequence of images. The first sequence of images includes: a plurality of images acquired by the camera unit prior to detecting activation of the shutter button at the first time; a representative image that represents the first sequence of images and was acquired by the camera unit after one or more of the other images in the first sequence of images; and a plurality of images acquired by the camera unit after acquiring the representative image. The processing unit is further configured to, in response to detecting the single activation of the shutter button at the first time: in accordance with a determination that the scene does not meet the action capture criteria, retain a single image in temporal proximity to the activation of the shutter button at the first time.
In accordance with some embodiments, an electronic device includes a display unit configured to display images, a touch-sensitive surface unit configured to detect user inputs, and a processing unit coupled with the display unit and the camera unit. The processing unit is configured to enable display of an image on the display unit. The image is one image in a sequence of images taken by a camera. The sequence of images includes a representative image. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. The processing unit is further configured to, while enabling display of the image in the sequence of images on the display unit, detect a first input. The processing unit is further configured to, in response to detecting the first input, enable display of a user interface for trimming the sequence of images to a subset, less than all, of the sequence of images. The user interface includes: an area that contains representations of images in the sequence of images; a user-adjustable begin-trim icon that delimits a beginning image in the subset of the sequence of images via a position of the begin-trim icon in the area that contains representations of images in the sequence of images; and a user-adjustable end-trim icon that delimits an ending image in the subset of the sequence of images via a position of the end-trim icon in the area that contains representations of images in the sequence of images. The begin-trim icon is located at a first position, in the area that contains representations of images in the sequence of images, that is automatically selected by the device. The end-trim icon is located at a second position, in the area that contains representations of images in the sequence of images, that is automatically selected by the device. The processing unit is further configured to, while enabling display of the user interface for trimming the sequence of images, detect a second input. The processing unit is further configured to, in response to detecting a second input, trim the sequence of images to the subset of the sequence of images in accordance with a current position of the begin-trim icon and a current position of the end-trim icon.
In accordance with some embodiments, an electronic device includes a display, a touch-sensitive surface, one or more optional sensors to detect intensity of contacts with the touch-sensitive surface, one or more processors, memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors and the one or more programs include instructions for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, a computer readable storage medium has stored therein instructions which when executed by an electronic device with a display, a touch-sensitive surface, and one or more optional sensors to detect intensity of contacts with the touch-sensitive surface, cause the device to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a graphical user interface on an electronic device with a display, a touch-sensitive surface, one or more optional sensors to detect intensity of contacts with the touch-sensitive surface, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein, which are updated in response to inputs, as described in any of the methods described herein. In accordance with some embodiments, an electronic device includes: a display, a touch-sensitive surface, and one or more optional sensors to detect intensity of contacts with the touch-sensitive surface; and means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display and a touch-sensitive surface, and one or more optional sensors to detect intensity of contacts with the touch-sensitive surface, includes means for performing or causing performance of the operations of any of the methods described herein.
Thus, electronic devices are provided with improved methods and interfaces for capturing and interacting with moments taken or recorded by cameras. Such methods and interfaces may complement or replace conventional methods for capturing and interacting with still images and video.
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.
As noted above, portable electronic devices typically capture two types of digital content: still images and video. A still image is typically captured by simply pressing a shutter button. The still image freezes an instant in time, but details of the moment surrounding that instant are lost. Videos record extended periods of time, which may include both interesting moments and not-so-interesting moments. Significant editing is typically required to remove the less interesting moments.
Here, new and improved devices and methods for capturing and interacting with moments are described.
In some embodiments, in response to the press of a shutter button, the device groups a sequence of images together that includes a representative image (analogous to the instant captured in a conventional still image), as well as images acquired before the shutter button was pressed and images acquired after the representative image. Thus, the press of a shutter button captures the moment around an instant in time, instead of just the instant. In some embodiments, additional information about the moment, such as sound and metadata, is also captured. From a user perspective, this process makes capturing moments (grouped sequences of images that include a representative image) as easy as capturing instants (a single still image)—the user just needs to press a shutter button. To distinguish from a single still image, the term “enhanced photo” is sometimes used for brevity to refer to a grouped sequence of images.
In some embodiments, while viewing a representative image, an enhanced photo can “come to life” and replay the moment in response to a user input (e.g., a press-and-hold gesture or a deep press gesture on the enhanced photo).
In some embodiments, while navigating between enhanced photos, for a respective enhanced photo, the images taken just before the representative image of the enhanced photo are shown as the enhanced photo comes into view on the display and/or the images taken just after the representative image are shown as the enhanced photo leaves the display, which enhances display of the moment.
In some embodiments, while navigating between enhanced photos and conventional still images, enhanced photos are “replayed” while coming into view and/or leaving the display, while for the conventional still images additional information (e.g., location data) and/or animations within the still image are shown when the still images are displayed.
In some embodiments, a user can modify a representative image in an enhanced photo and have the modifications applied to just the representative image or applied to all of the images in the enhanced photo (e.g., the user can toggle between an apply-to-all mode and a still image editing mode).
In some embodiments, when a respective user sends an enhanced photo to another user, the respective user's device presents different options for sending the enhanced photo depending on whether the other user's device is compatible with enhanced photos (e.g., presents an option for sending the enhanced photo as an enhanced photo when the other user's device is compatible with enhanced photos, and presents an option for sending just the representative image when the other user's device incompatible with enhanced photos).
In some embodiments, a device performs scene recognition (e.g., while in an image capture mode). When the scene is conducive to retaining an enhanced photo (e.g., the scene includes movement or faces), in response to the press of a shutter button, the device retains an enhanced photo. When the scene is not conducive to retaining an enhanced photo (e.g., the scene is a picture of a receipt), in response to the press of a shutter button, the device retains a single still image.
In some embodiments, a user can trim a sequence of images to a subset of the sequence of images. The device provides handles for trimming the sequence at automatically chosen positions in the sequence (e.g., based on scene recognition) The handles can also be used to manually trim the sequence.
Below,
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact, unless the context clearly indicates otherwise.
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.
As used herein, 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 note taking application, 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 “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. Access to memory 102 by other components of device 100, such as CPU(s) 120 and the peripherals interface 118, is, optionally, controlled by memory controller 122.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU(s) 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(s) 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 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 (HSDPA), 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, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), 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-sensitive display system 112 and other input or control devices 116, with peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input or 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 with any (or none) of the following: a keyboard, infrared port, USB port, stylus, and/or a pointer device such as a mouse. The one or more buttons (e.g., 208,
Touch-sensitive display system 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-sensitive display system 112. Touch-sensitive display system 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 corresponds to user interface objects. As used herein, the term “affordance” refers to a user-interactive graphical user interface object (e.g., graphical user interface object that is configured to respond to inputs directed toward the graphical user interface object). Examples of user-interactive graphical user interface objects include, without limitation, a button, slider, icon, selectable menu item, switch, or other user interface control.
Touch-sensitive display system 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-sensitive display system 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-sensitive display system 112 and converts 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-sensitive display system 112. In an exemplary embodiment, a point of contact between touch-sensitive display system 112 and the user corresponds to a finger of the user or a stylus.
Touch-sensitive display system 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-sensitive display system 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-sensitive display system 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, California.
Touch-sensitive display system 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen video resolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally makes contact with touch-sensitive display system 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 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-sensitive display system 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, haptic feedback module (or set of instructions) 133, 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 stores device/global internal state 157, as shown in
Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware 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 in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. In some embodiments, the external port is a Lightning connector that is the same as, or similar to and/or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.
Contact/motion module 130 optionally detects contact with touch-sensitive display system 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 (e.g., by a finger or by a stylus), 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 stylus 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.
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 (lift off) 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 (lift off) event. Similarly, tap, swipe, drag, and other gestures are optionally detected for a stylus by detecting a particular contact pattern for the stylus.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 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 138 for use in location-based dialing, to camera 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-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 includes executable instructions 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 and/or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 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-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing 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-sensitive display system 112, display controller 156, contact 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-sensitive display system 112, display controller 156, contact 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, Apple Push Notification Service (APNs) 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 (e.g., still images), enhanced photos, audio files, video files and/or other attachments as are supported in a 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, APNs, or IMPS).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (in sports devices and smart watches); 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-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact 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, and/or delete a still image or video from memory 102.
In conjunction with touch-sensitive display system 112, display controller 156, contact 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-sensitive display system 112, display system controller 156, contact 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-sensitive display system 112, display system controller 156, contact 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-sensitive display system 112, display system controller 156, contact 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-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 includes executable instructions to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch-sensitive display system 112, display system controller 156, contact 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-sensitive display system 112, display system controller 156, contact 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-sensitive display system 112, or on an external display connected wirelessly or 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-sensitive display system 112, display controller 156, contact 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-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions 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-sensitive display system 112, display system controller 156, contact 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 executable instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen 112, or on an external display connected wirelessly or 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.
Each of the above identified modules and applications correspond 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 (i.e., 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 re-arranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.
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 system 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 system 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 system 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, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or 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 system 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 (i.e., 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, 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 module 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes 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 lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (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 system 112, and lift-off 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 system 112, when a touch is detected on touch-sensitive display system 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 145. 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 touch-pads; 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 includes 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 the touch-screen display.
In some embodiments, device 100 includes the touch-screen display, 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, head set 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 some embodiments, 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-sensitive display system 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 (“UI”) that are, optionally, implemented on portable multifunction device 100.
It should be noted that the icon labels illustrated in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures, etc.), 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 a 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.
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 “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 or a stylus 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 or a sum) 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 readily 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).
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 thresholds 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).
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 may include 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 intensity threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more intensity thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective option 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 may receive a continuous swipe contact transitioning from a start location and reaching an end location (e.g., a drag gesture), at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be 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 may be 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 user interface figures described herein optionally include various intensity diagrams that show the current intensity of the contact on the touch-sensitive surface relative to one or more intensity thresholds (e.g., a contact detection intensity threshold IT0, a light press intensity threshold ITL, a deep press intensity threshold ITD (e.g., that is at least initially higher than IL), and/or one or more other intensity thresholds (e.g., an intensity threshold IH that is lower than IL)). This intensity diagram is typically not part of the displayed user interface, but is provided to aid in the interpretation of the figures. 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 IT0 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.
In some embodiments, the response of the device to inputs detected by the device depends on criteria based on the contact intensity during the input. For example, for some “light press” inputs, the intensity of a contact exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the response of the device to inputs detected by the device depends on criteria that include both the contact intensity during the input and time-based criteria. For example, for some “deep press” inputs, the intensity of a contact exceeding a second intensity threshold during the input, greater than the first intensity threshold for a light press, triggers a second response only if a delay time has elapsed between meeting the first intensity threshold and meeting the second intensity threshold. This delay time is typically less than 200 ms in duration (e.g., 40, 100, or 120 ms, depending on the magnitude of the second intensity threshold, with the delay time increasing as the second intensity threshold increases). This delay time helps to avoid accidental deep press inputs. As another example, for some “deep press” inputs, there is a reduced-sensitivity time period that occurs after the time at which the first intensity threshold is met. During the reduced-sensitivity time period, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to detection of a deep press input does not depend on time-based criteria.
In some embodiments, one or more of the input intensity thresholds and/or the corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application running, rate at which the intensity is applied, number of concurrent inputs, user history, environmental factors (e.g., ambient noise), focus selector position, and the like. Exemplary factors are described in U.S. patent application Ser. Nos. 14/399,606 and 14/624,296, which are incorporated by reference herein in their entireties.
For example,
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold ITL to an intensity between the light press intensity threshold ITL and the deep press intensity threshold ITD 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 ITD to an intensity above the deep press intensity threshold ITD 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 IT0 to an intensity between the contact-detection intensity threshold IT0 and the light press intensity threshold ITL 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 IT0 to an intensity below the contact-detection intensity threshold IT0 is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments IT0 is zero. In some embodiments, IT0 is greater than zero. In some illustrations a shaded circle or oval is used to represent intensity of a contact on the touch-sensitive surface. In some illustrations, a circle or oval without shading is used represent a respective contact on the touch-sensitive surface without specifying the intensity of the respective contact.
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., the respective operation is performed on 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., the respective operation is performed on an “up stroke” of the respective press input).
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., the respective operation is performed on 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 description 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: 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, 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. As described above, in some embodiments, the triggering of these responses also depends on time-based criteria being met (e.g., a delay time has elapsed between a first intensity threshold being met and a second intensity threshold being met).
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device, such as portable multifunction device 100 or device 300, with a display, a touch-sensitive surface, and optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface.
In this example, portable multifunction device 100, while in the live preview, is configured to be in an enhanced media acquisition mode (e.g., in which portable multifunction device 100 is configured to obtain enhanced photos) or another media acquisition mode (e.g., in which portable multifunction device 100 is configure to capture still images, video, burst images, or any other type of image). In some embodiments, media capture user interface 500 includes an affordance 506 for enabling the enhanced media acquisition mode (e.g., turning/toggling enhance media acquisition mode on/off). In some embodiments, media capture user interface 500 includes a visual indication that the enhanced media acquisition mode is off. For example, in
In some embodiments, when the enhanced media acquisition mode is on, portable multifunction device 100 provides a visual indication that the enhanced media acquisition mode is on (e.g., to indicate that image and/or audio data is being captured while media capture user interface 500 is displayed). For example, as shown in
In some embodiments, as shown in
Portable multifunction device 100 captures media (e.g., images and/or audio) when the enhanced media acquisition mode is on. For example, because the enhanced video mode is on in
Media capture user interface 500 includes a shutter button 514 (illustrated as a shutter release icon). As shown in
In some embodiments, the representative image is analogous to a single image captured in the still image mode of a conventional digital camera when its shutter button is activated. In some embodiments, representative image 512-4 corresponds to an image that was acquired at the time shutter button 514 was activated by tap gesture 518. In some embodiments, representative image 512-4 corresponds to an image that was acquired shortly after detecting activation of the shutter button 514, at a time that takes into account shutter lag (the time delay between detecting activation of the shutter button and capturing/storing the representative image). In some embodiments, representative image 512-4 acquired by the camera is used to represent the sequence of images, for example in an image presentation mode (as shown in
As noted above, in some embodiments, the live preview displays images at a first resolution. In some embodiments, the sequence of images 512 includes images, at the first resolution, that were displayed in the live preview, while representative image 512-4 acquired by the camera has a second resolution that is higher than the first resolution. For example, as shown in
As shown in
In some embodiments, upon completion of capturing the sequence of images, portable multifunction device 100 returns to the functionality described with respect to
As shown in
As shown in
In some embodiments, user interface 600 is a user interface in an image management application (e.g., Photos from Apple Inc. of Cupertino, California). To that end, in some embodiments, the camera that took the sequence of images 602 is part of portable multifunction device 100 (e.g., the camera comprises optical sensors 164 conjunction with imaging module 143,
In some embodiments, portable multifunction device 100 stores a plurality of grouped sequences of images, some of which were acquired using portable multifunction device 100 and some of which were transferred to portable multifunction device 100 after being taken with a camera on a different device. For example, in some circumstances, a user may obtain (e.g., take, capture) sequences of images, as described with reference to methods 900/2600, on a plurality of devices (e.g., a tablet, a laptop, and/or a digital camera, all in addition to portable multifunction device 100) and synchronize or otherwise transfer the sequences of images onto portable multifunction device 100.
In some embodiments, user interface 600 is a user interface in a messaging application (e.g., Messages from Apple Inc. of Cupertino, California). In some circumstance, a user may have obtained (e.g., taken, captured) a respective sequence of images on her own portable multifunction device 100 and also have received a different sequence of images from a different user (e.g., in a messaging application). Thus, in some embodiments, the sequence of images 602 is a respective sequence of images in a plurality of sequences of images stored on portable multifunction device 100 that includes at least one sequence of images obtained using a camera on portable multifunction device 100 and at least one sequence of images that was obtained using a camera on a different device, distinct from portable multifunction device 100.
In some embodiments, representative image 602-3 is displayed in user interface 600 when portable multifunction device 100 is in a collection view mode.
User interface 600 optionally includes one more toolbars. For example, as shown, user interface 600 includes an operations toolbar 604 that includes a plurality of affordances 606 (e.g., send affordance 606-1 that allows the user to send the sequence of images 602 to other users using e-mail, messaging, or other applications; edit affordance 606-2 that brings up a user interface for editing the sequence of images 602; a favorites affordance 606-3 through which the user may indicate that the sequence of images 602 is one of her favorites; and delete affordance 606-4 that allows the user to delete sequence of images 602). As another example, user interface 600 includes a navigation toolbar 608 that includes another plurality of affordances (e.g., all photos affordance 610-1 that, when activated, navigates to a user interface for navigating the user's photos; and “done” affordance 610-2 that, when activated, navigates to a different user interface, such as a user interface for obtaining a photo).
The sequence of images 602 shown in
In image 602-5, cat 612 has walked partially out of the field of view and bird 614 remains perched in the tree (e.g., image 602-5 is an image that was taken after respective image 602-4). Thus,
In some embodiments, the one or more images acquired by the camera after acquiring representative image 602-3 are displayed, in response to detecting the first portion 616-1 of first input 616, in sequence at a rate that is based on an intensity of a contact in the first portion 616-1 of first input 616 as shown in intensity diagram 618 (e.g., the rate of display increases as an intensity of a contact in the first portion 616-1 of first input 616 increases, and the rate of display decreases as an intensity of a contact in the first portion 616-1 of first input 616 decreases). In some embodiments, during sequential display of the sequence of images 602 during the first portion 616-1 of first input 616, portable multifunction device 100 dwells on each respective image in the sequence of images 602 for a duration of time proportional (or inversely proportional) to a characteristic intensity of the first input 616 while the respective image is displayed. So, for example, in such embodiments, portable multifunction device 100 dwells on representative image 602-3 (
In some embodiments, after this initial dependence of the display rate on contact intensity in first input 616, subsequent displays of the sequence of images 602 (in response to detecting later portions of first input 616, as described below) occur at fixed display rates, independent of the contact intensity in later portions of first input 616. So, for example, portable multifunction device 100 dwells on image 602-1 (
In some embodiments, as described below with reference to
In some embodiments, the second portion 616-2 of first input 616 is a portion that is continuous with and immediately subsequent to the first portion 616-1 of first input 616. In some embodiments, unless first input 616 is terminated during the second portion 616-2, the second portion 616-2 of first input 616 lasts (e.g., has a duration of) an amount of time it takes to replace, in sequence, all of the images in the sequence of images 602.
In image 602-1 (
In some embodiments, one difference between the sequential display, during the first portion 616-1 of first input 616, of the one or more images acquired by the camera after acquiring representative image 602-3 (as shown in
In some embodiments, the sequence of images 602 is displayed, in response to detecting the second portion 616-2 of first input 616 (e.g., during the first complete playback), in sequence at a fixed rate (e.g., at the same rate at which the images were obtained, also called a “1×” rate). For example, in some embodiments, audio is presented during the first complete playback at 1× rate and the corresponding sequence of images 602 are displayed at a 1× rate, giving the playback a natural look and sound. In some embodiments, a 1× rate means that portable multifunction device 100 dwells upon a respective image for an amount of time substantially the same as the amount of time that elapsed between obtaining the respective image and the next image.
In some embodiments, images in the sequence of images 602 are sequentially displayed at a fixed rate, independent of the intensity of a contact in first input 616. For example, portable multifunction device 100 dwells on image 602-1 (
In some embodiments, as described below with reference to
As noted above,
In some circumstances, a grouped sequence of images is asymmetrical with respect to its representative image, meaning that there are an unequal number of images that occur before and after the representative image. In some embodiments, portable multifunction device 100 determines whether there are fewer images between the currently displayed image and the representative image in the forward- or reverse-chronological order directions. Portable multifunction device 100 then sequentially displays (e.g., traverses) the sequence of images in whichever direction has fewer images between the currently displayed image and the representative image.
In
So, for example, in diagram 650, device 100 initially displays representative image 652. In response to user input 648, device 100 plays three images forward (e.g., or one image or ten images, etc.) to image 660, then replaces display of image 660 with display of initial image 654. Device 100 then plays the sequence of images forward from initial image 654, in accordance with any of the embodiments described above with reference to
As another example, in diagram 656, device 100 initially displays representative image 652. In response to user input 648, device 100 replaces display of representative image 652 with display of initial image 654 (or any other respective prior image). Device 100 then plays the sequence of images forward from initial image 654, in accordance with any of the embodiments described above with reference to
In some embodiments, as shown in diagram 656, transitioning from displaying representative image 652 to displaying initial image 654 (e.g., the respective prior image) does not include displaying any of the one or more images acquired by the camera after acquiring representative image 652 (e.g., the device goes straight back to initial image 654).
In some embodiments, device 100 determines which transition to apply (e.g., the transition shown in diagram 650 or the transition shown in diagram 656) based on characteristics of user input 648 (e.g., a characteristic contact intensity of the first portion of the first input 648). For example, when the first portion of the first input 648 exceeds deep press threshold ITD, as shown in intensity diagram 668-2, device 100 transitions in accordance with diagram 656. When the first portion of the first input 648 does not exceed deep press threshold ITD, as shown in intensity diagram 668-1, device 100 transitions in accordance with diagram 650.
In some embodiments, certain images acquired during acquisition of the sequence of images are dropped or fused in generating a sequence of images. For example, blurry images are dropped (e.g., not included) in the sequence of images and/or one or more dark images are combined to increase the quality of the images in the sequence of images. In some circumstances, dropping and/or fusing images results in a sequence of images that are not evenly spaced temporally. For example, if ten images are acquired by a camera per second, but three images are fused to form a respective single image in the sequence of image, the respective single image represents a greater passage of time than the other images in the sequence of images. Thus, in some embodiments, playback of the sequence of images is re-timed according to removal and/or fusing of images within the sequence of images (e.g., in the example above, when playing the sequence of images at 1× playback, device 100 dwells on the respective single image of 0.3 seconds, or three times as long as it otherwise would).
In accordance with some embodiments,
Portable multifunction device 100 displays, in user interface 640, a representative image 602-1 in a grouped sequence of images 602. In some embodiments, the sequence of images 602 is an enhanced photo that the user has chosen for her lock screen (e.g., chosen in a settings user interface). In the example shown in
In some embodiments, user interface 640 also includes quick access information 642, such as time and date information.
While displaying representative image 602-1 on touch screen 112, device 100 detects an input 644 (e.g., a press-and-hold gesture) for which a characteristic intensity of a contact on touch screen 112 exceeds an intensity threshold. In this example, the intensity threshold is the light press threshold ITL. As shown in intensity diagram 618 (
In response to detecting the increase in the characteristic intensity of the contact, the device advances in chronological order through the one or more images acquired after acquiring representative image 602-1 at a rate that is determined based at least in part on the characteristic intensity of the contact of input 644. So, for example, display of representative image 602-1 (
In
In some embodiments, the rate, indicated in rate diagrams 646 (
In some embodiments, the rate forward or backward is determined in real-time or near-real time, so that the user can speed up or slow down movement through the images (either in the forward or reverse direction) by changing the characteristic intensity of the contact. Thus, in some embodiments, the user can scrub forwards and backwards through sequence of images 602 (e.g., in between the initial and final images in the sequence of images) by increasing and decreasing the contact intensity of user input 644.
In accordance with some embodiments,
As shown in
In this example, device 100 has a maximum rate Vmax (e.g., plus or minus 2×) which is reached when input 644's current contact intensity reaches deep press threshold ITD (or any other upper threshold) and hint threshold ITH (or any other appropriate lower threshold), respectively. The rate of movement through the sequence of images is constrained by a maximum reverse rate while the contact is detected on the touch-sensitive surface
In accordance with some embodiments, certain circumstances optionally result in device 100 deviating from a rate of movement based solely on input 644's current contact intensity. For example, as device 100 nears a final image while advancing forward through sequence of images 602, device 100 slows the rate of movement as compared to what the rate of movement would be if it were based solely on input 644's current contact intensity (e.g., device 100 “brakes” slightly as it reaches the end of the sequence of images). Similarly, in some embodiments, as device 100 nears an initial image while advancing backwards through sequence of images 602, device 100 slows the rate of movement as compared to what the rate of movement would be if it were based solely on input 644's current contact intensity (e.g., device 100 “brakes” slightly as it reaches the beginning of the sequence of images going backwards).
In some embodiments, a swipe gesture triggers playback of sequence of images 602 upon termination (e.g., lift off) of the swipe gesture. In some embodiments, sequence of images 602 does not play back during a drag gesture but instead plays back up termination (e.g., lift off) of a drag gesture. In some embodiments, sequence of images 602 plays back in response to a press-and-hold gesture (e.g., sequence of images 602 in messaging application 680 plays back in accordance with any of the embodiments described with reference to
In some embodiments, sequence of images 602 is displayed (e.g., played back) as the scrollable region of the messaging application is scrolled and the images are, in some circumstances interspersed with text messages 684 or other messages sent and received via the messaging application (e.g., in conversation bubbles). In some circumstance, a user may have obtained (e.g., taken, captured) a respective sequence of images on her own portable multifunction device 100 and also have received a different sequence of images from a different user (e.g., in a messaging application). Thus, in some circumstances, the plurality of sequences of images stored on portable multifunction device 100 includes at least one sequence of images obtained using a camera on portable multifunction device 100 and at least one sequence of images that was obtained using a camera on a different device, distinct from portable multifunction device 100.
Portable multifunction device 100 displays user interface 700. User interface 700 optionally includes one more toolbars. For example, as shown, user interface 700 includes an operations toolbar 704 that includes a plurality of affordances 706 (e.g., send affordance 706-1 that allows the user to send first sequence of images 702 to other users using e-mail, messaging, or other applications; edit affordance 706-2 that brings up a user interface for editing first sequence of images 702; a favorites affordance 706-3 through which the user may indicate that first sequence of images 702 is one of her favorites; and delete affordance 706-4 that allows the user to delete first sequence of images 702). As another example, user interface 700 includes a navigation toolbar 706 that includes another plurality of affordances (e.g., all photos affordance 710-1 that navigates to a user interface for navigating the user's photos; “done” affordance 710-2 that navigates to a different user interface, such as a user interface for obtaining a photo).
First sequence of images 702 depicts a scene in which a cat 712 walks into the field of view, rolls his back on the ground, and gets up and walks away. Meanwhile, a bird 714 lands on a branch. While in reality, such a scene may take several seconds to unfold, in some embodiments, first sequence of images 702 is captured in a short temporal window. For example, in some embodiments, any of the sequences of images described herein may depict the moments surrounding (e.g., within half a second or one second) the moment when its respective representative image was obtained. For example, the user's interest may have been piqued when cat 712 began rolling in the grass, prompting the user to take first representative image 702-3. In some embodiments, first sequence of images 702 includes images just before and just after first representative image 702-3 was obtained, such that first sequence of images 702 comprises an enhanced photo through which the moment can “come to life” when the user performs certain operations with respect to first representative image 702-3, as described herein.
Second grouped sequence of images 724 includes second representative image 724-3 (
Third grouped sequence of images 726 includes third representative image 726-1 and at least one or more images acquired by the camera after acquiring third representative image 726-1 (e.g., image 726-3,
Fourth grouped sequence of images 760 includes fourth representative image 760-3 and at least one or more images acquired by the camera before acquiring fourth representative image 760-1 (e.g., image 760-1,
In some embodiments, the first sequence of images 702 was acquired by the camera before the second sequence of images 724, and the first sequence of images 702 was acquired by the camera after the third sequence of images 726.
In some embodiments, user interface 700 is a user interface in an image management application (e.g., Photos from Apple Inc. of Cupertino, California). To that end, in some embodiments, the camera that took first sequence of images 702 (and/or second sequence of images 724; third sequence of images 726; etc.) is part of portable multifunction device 100 (e.g., the camera comprises optical sensors 164 in conjunction with imaging module 143,
In some embodiments, some of the plurality of sequences of images were acquired using portable multifunction device 100 and some were transferred to portable multifunction device 100 after being taken with a camera on a different device. For example, in some circumstances, a user may obtain (e.g., take, capture) sequences of images, as described with reference to methods 900/2600, on a plurality of devices (e.g., a tablet, a laptop, and/or a digital camera, all in addition to portable multifunction device 100) and synchronize or otherwise transfer the sequences of images onto portable multifunction device 100.
In some embodiments, user interface 700 is a user interface in a messaging application (e.g., Messages from Apple Inc. of Cupertino, California). In some embodiments, first sequence of images 702 is a message in a message conversation displayed in a scrollable region of the messaging application, and first sequence of images 702 is displayed as the scrollable region of the messaging application is scrolled and the images are, in some circumstances interspersed with text messages or other messages sent and received via the messaging application (e.g., in conversation bubbles). In some circumstance, a user may have obtained (e.g., taken, captured) a respective sequence of images on her own portable multifunction device 100 and also have received a different sequence of images from a different user (e.g., in a messaging application). Thus, in some circumstances, the plurality of sequences of images stored on portable multifunction device 100 includes at least one sequence of images obtained using a camera on portable multifunction device 100 and at least one sequence of images that was obtained using a camera on a different device, distinct from portable multifunction device 100.
In some embodiments, representative image 702-3 is displayed in user interface 700 (e.g., displayed in an image management application or messaging application when the user is scrolling through her images or messages).
User interface 700, as shown in
In
In some embodiments, the display, in chronological order in first area 734, of at least some of the one or more images for first sequence of images 702 acquired by the camera after acquiring the first representative image occurs in accordance with the movement of contact in drag gesture 736. Thus, if the movement of drag gesture 736 to the left speeds up, the display of the chronological progression of images in first area 734 speeds up. If the movement of drag gesture 736 to the left slows down, the display of the chronological progression of images in first area 734 slows down. If the movement of drag gesture 736 to the left is paused, the display of the chronological progression of images in first area 734 is paused. And, if the movement of drag gesture 736 reverses direction (e.g., from a leftward drag gesture to a rightward drag gesture), the display of the progression of images in first sequence of images 702 in first area 734 is reversed and the images are shown in reverse chronological order in accordance with the movement of the drag gesture 736 in the reverse direction. More generally, in some embodiments, for a respective sequence of images, the display of a progression of images in the respective sequence of images, in a respective area, occurs in accordance with the movement of a contact in the drag gesture.
In some embodiments, the user triggers the operations shown in
In some embodiments, movement of first area 734 corresponds to movement of drag gesture 736. For example, in some embodiments, the movement of first area 734 between
In some embodiments, as shown in
In some embodiments, the display, in chronological order in second area 738, of at least some of the one or more images for second sequence of images 724 acquired by the camera before acquiring second representative image 724-3 occurs in accordance with the movement of a contact in drag gesture 736 (e.g., in analogous manner to that described above with reference to first sequence of images 702). For example, during drag gesture 736, the images in first area 734 and the images in the second area 738 are both advancing at the same rate, with the rate based on the movement of drag gesture 736. In some embodiments, for example as described below with reference to
In some embodiments, as an alternative to the example shown in
In some embodiments, user interface 700 includes a next icon 750-1 (e.g.,
While the operations occurring in
As illustrated in
As illustrated in
As shown in
Conversely, in some embodiments, when the next-sequence-navigation criteria are not met, portable multifunction device 100 moves second area 738 completely off touch screen 112 (e.g., by moving second area 738 to the right until second area 738 is completely off touch screen 112) and moves first area 734 completely onto touch screen 112 (e.g., by moving first area 734 back to the right until first area 734 is completely on touch screen 112). As a result, portable multifunction device 100 displays first representative image 702-3 again (e.g., returns to the view shown in
In some embodiments, the display, in reverse chronological order in third area 746, of at least some of the one or more images for third sequence of images 726 acquired by the camera after acquiring third representative image 726-1 occurs in accordance with the movement of a contact in drag gesture 744 (e.g., in analogous manner to that described above with reference to first sequence of images 702). For example, during drag gesture 744, the images in first area 734 and the images in the third area 746 are both reversing at the same rate, with the rate based on the movement of drag gesture 744.
In some embodiments, like detecting drag gesture 744 in the second direction, detecting activation of previous icon 750-2 (e.g.,
In some embodiments, as an alternative to the example shown in
While the operations occurring in
As illustrated in
As illustrated in
As shown in
Conversely, in some embodiments, when the previous-sequence-navigation criteria are not met, portable multifunction device 100 moves third area 746 completely off touch screen 112 (e.g., by moving third area 746 to the left until third area 746 is completely off touch screen 112) and moves first area 734 completely onto touch screen 112 (e.g., by moving first area 734 back to the left until first area 734 is completely on touch screen 112). As a result, portable multifunction device 100 displays first representative image 702-3 again (e.g., returns to the view shown in
In this example, first area 734 is over second area 738 (e.g., in a z-layer) so that, as first area 734 touch screen 112 in response to drag gesture 752, second area 738 is progressively revealed. At the beginning of drag gesture 752, second area 738 is partially, but not completely onto touch screen 112 (e.g., half way, or three quarters of the way onto touch screen 112). As the user slides first area 734 rightward off touch screen 112, second area 738 slides the remainder of the way onto touch screen 112, such that completely sliding first area 734 off of touch screen 112 corresponds to completely sliding second area 738 onto touch screen 112. Moving first area 734 off of touch screen 112 at a rate that is different from the rate at which second area 738 is moved onto touch screen 112 provides the user with intuitive visual cues as to a direction that the user is navigating in a hierarchy (e.g., z-layering) of enhanced photos.
In some embodiments, during drag gesture 752, the images in first area 734 and the images in the second area 738 advance at different rates. In some embodiments, the respective rates at which images in first area 734 and the images in the second area 738 advance are both based on the movement of drag gesture 752. In some embodiments, the images in first area 734 advance at a rate that is higher than a rate at which the images in second area 738 advance. In
To that end,
As shown in
As shown in
In some embodiments, the sequence-display criteria include navigation criteria (e.g., criteria that indicate that device 100 should finish transitioning to the next or previous photo even without further user input). For example, device 100 only plays through second sequence of images 724 if the user has flicked quickly enough and/or dragged far enough to transition to the next sequence of images (e.g., second sequence of images 724). Navigation criteria are described in greater detail above with reference to
In some embodiments, as first area 734 slides off the display, device 100 maintains display of first representative image 702-3 (e.g., statically, without replacing display of first representative image 702-3) while playing-back a least a portion of second sequence of images 724 (e.g., first sequence of image 702 does not playback while second sequence of images 724 is playing-back). Thus, representative image 702-3 is displayed in first area 734 in each of
In some embodiments, a rightward swipe/drag gesture results in analogous functionality, except that the previous enhanced photo (e.g., in a camera roll) is slid onto the display instead of the next enhanced photo (e.g., in the camera roll). For example, in
As shown in
Sequence of images 802 depicts a scene in which a cat 812 walks into the field of view, rolls his back on the ground, and gets up and walks away. Meanwhile, a bird 814 lands on a branch. While in reality, such a scene may take several seconds to unfold, in some embodiments, sequence of images 802 is captured in a short temporal window. For example, in some embodiments, any of the sequence of images described herein may depict the moment surrounding (e.g., within 0.5, 1.0, 1.5, 2.0, or 2.5 seconds) the instant when its respective representative image was obtained. For example, the user's interest may have been piqued when cat 812 began rolling in the grass, prompting the user to take representative image 802-3. In some embodiments, sequence of images 802 includes images just before and just after first representative image 802-3 was obtained, such that first sequence of images 802 comprises an enhanced photo through which the moment can “come to life” when the user performs certain operations with respect to representative image 802-3, as described herein.
In the example shown in
In some embodiments, user interface 800 is a user interface in an image management application (e.g., Photos from Apple Inc. of Cupertino, California). To that end, in some embodiments, the camera that took sequence of images 802 is part of portable multifunction device 100 (e.g., the camera comprises optical sensors 164 in conjunction with imaging module 143,
In some embodiments, some of the still images and/or the plurality of sequences of images were acquired using portable multifunction device 100 and some were transferred to portable multifunction device 100 after being taken with a camera on a different device. For example, in some circumstances, a user may obtain (e.g., take, capture) sequences of images, as described with reference to methods 900/2600, on a plurality of devices (e.g., a tablet, a laptop, and/or a digital camera, all in addition to portable multifunction device 100) and synchronize or otherwise transfer the sequences of images onto portable multifunction device 100, which stores additional still images.
In some embodiments, user interface 800 is a user interface in a messaging application (e.g., Messages from Apple Inc. of Cupertino, California). In some embodiments, sequence of images 802 and/or still image 824 are messages in a message conversation displayed in a scrollable region of the messaging application, and sequence of images 802 is displayed as the scrollable region of the messaging application is scrolled. In some circumstance, a user may have obtained (e.g., taken, captured) a respective sequence of images on her own portable multifunction device 100 and also have received a different sequence of images, or different still images, from a different user (e.g., in a messaging application). Thus, in some embodiments, the plurality of sequences of images stored on portable multifunction device 100 includes at least one sequence of images obtained using a camera on portable multifunction device 100 and at least one sequence of images or still image that was obtained using a camera on a different device, distinct from portable multifunction device 100.
As shown in
As a result, portable multifunction device 100 performs a first operation when first input 816 is detected while displaying representative image 802-3 and a second, different, operation when second input 836 is detected while displaying still image 824. In the example shown in
While in a first media acquisition mode for the camera, the device displays (902) (e.g., as shown in
In some embodiments, the first media acquisition mode is (904) configured to be enabled or disabled by a user of the device (e.g., via a settings interface for the camera). In some embodiments, the device includes at least three media acquisition modes: (1) the first media acquisition mode (which may be considered an “enhanced still image” acquisition mode), which groups a sequence of images in response to detecting activation of a shutter button, where the sequence of images includes images acquired before the activation of the shutter button and after the activation of the shutter button and stores them as a group of images; (2) a second media acquisition mode (e.g., a conventional still image acquisition mode), which stores a single image in response to detecting activation of a shutter button, like the still image mode in a conventional digital camera; and (3) a third media acquisition mode (e.g., a video acquisition mode), which stores video acquired after detecting activation of the shutter button, and which keeps recording video until the shutter button is activated again. In some embodiments, the user can select which media acquisition mode is enabled via a settings interface for the camera, mode selection buttons, a mode selection dial, or the like.
In some embodiments, the live preview is (906) displayed as part of a media capture user interface that includes an affordance for enabling the first media acquisition mode (e.g., affordance 506
While displaying the live preview, the device detects (908) activation of a shutter button at a first time (e.g., the device detects pressing of a physical button at the first time or detects a gesture on a virtual shutter button on a touch-sensitive display at the first time, such as a tap gesture on a shutter release icon (as shown in
In response to detecting activation of the shutter button at the first time, the device groups (910) a plurality of images acquired by the camera in temporal proximity to the activation of the shutter button at the first time into a first sequence of images (e.g., as shown in
In some embodiments, the representative image is acquired by the camera at the first time and is analogous to the single image captured in the still image mode of a conventional digital camera when its shutter button is activated. In some embodiments, the representative image acquired by the camera corresponds to an image that was acquired at the first time. In some embodiments, the representative image acquired by the camera corresponds to an image that was acquired shortly after detecting activation of the shutter button at the first time, at a time that takes into account shutter lag (the time delay between detecting activation of the shutter button and capturing/storing the representative image). In some embodiments, the representative image acquired by the camera is used to represent the sequence of images, for example in an image presentation mode.
In some embodiments, the first sequence of images includes a predefined number of images—such as 5, 10, 15, 20, 25, or 30 images—acquired after acquiring the representative image. In some embodiments, the images acquired after acquiring the representative image are images that are within a predefined time after acquiring the representative image, such as within 0.5, 1.0, 1.5, 2.0, or 2.5 seconds after acquiring the representative image. In some embodiments, the first sequence of images includes a predefined number of images—such as 5, 10, 15, 20, 25, or 30 images—acquired after detecting activation of the shutter button at the first time. In some embodiments, the images acquired after detecting activation of the shutter button at the first time are images that are within a predefined time after the first time, such as within 0.5, 1.0, 1.5, 2.0, or 2.5 seconds after the first time. In some embodiments, the plurality of images, in the first sequence of images, that is acquired after acquiring the representative image meet predefined grouping criteria. In some embodiments, the predefined grouping criteria include selecting a predefined number of images after the representative image. In some embodiments, the predefined grouping criteria include selecting images in a predefined range of time immediately after detecting activation of the shutter button. In some embodiments, the predefined grouping criteria include selecting images in a predefined range of time immediately after the time at which the representative image is acquired.
In some embodiments, the first sequence of images are (912) stored as a first distinct set of images in the memory (e.g., stored together in a data structure in non-volatile memory). In some embodiments, the representative image acquired by the camera is used to represent the first distinct set of images, for example in an image presentation mode (e.g., see
In some embodiments, the live preview displays (914) images at a first resolution and the first sequence of images includes images, at the first resolution, that were displayed in the live preview (e.g., the first resolution is a lower resolution than an upper limit of the camera's resolution). In some embodiments, the representative image acquired by the camera has (916) a second resolution that is higher than the first resolution. In some embodiments, the representative image acquired by the camera has a higher resolution than other images in the first sequence of images. For example, the representative image acquired by the camera is a 12, 18, or 24 megapixel image and the other images in the first sequence of images have a lower resolution that corresponds to the resolution displayed in the live preview (e.g., the first resolution). In some embodiments, the representative image acquired by the camera has the same resolution as other images in the first sequence of images.
In some embodiments, parameters for a respective sequence of images grouped in response to detecting a respective activation of the shutter button are (918) configurable by a user of the device. For example, via a settings interface for the camera, a user can select the number of images in a respective sequence, which image serves as a representative image of the sequence (e.g., as shown in
In some embodiments, the plurality of images acquired by the camera prior to detecting activation of the shutter button at the first time are (920) stored in a first form in the memory (e.g., program memory, volatile memory, ring buffer, etc.) prior to detecting activation of the shutter button at the first time and are stored in a second form in the memory (e.g., non-volatile memory/storage) in response to detecting activation of the shutter button at the first time.
In some embodiments, the plurality of images acquired prior to detecting activation of the shutter button at the first time is (922) a predefined number of images (e.g., 5, 10, 15, 20, 25, or 30 images).
In some embodiments, the plurality of images acquired prior to detecting activation of the shutter button at the first time is (924) images that are within a predefined time prior to the first time (e.g., within 0.5, 1.0, 1.5, 2.0, or 2.5 seconds prior to the first time).
In some embodiments, the plurality of images acquired prior to detecting activation of the shutter button at the first time is (926) images that are within a predefined time prior to a time at which the representative image is acquired (e.g., within 0.5, 1.0, 1.5, 2.0, or 2.5 seconds prior to the time at which the representative image is acquired).
In some embodiments, the plurality of images acquired prior to detecting activation of the shutter button at the first time are (928) from a range of time between the first time and a second time that is prior to the first time, and acquiring the plurality of images prior to detecting activation of the shutter button at the first time is independent of detecting an interaction with the shutter button that is temporally proximate to the second time (other than detecting activation of the shutter button at the first time). For example, the plurality of images acquired prior to detecting activation of the shutter button at the first time is not acquired in response to detecting an interaction with the shutter button that is temporally proximate to the second time (other than detecting activation of the shutter button at the first time). For example, the plurality of images acquired prior to detecting activation of the shutter button at the first time is not acquired in response to detecting a partial (or complete) activation of the shutter button at or near the second time.
In some embodiments, the plurality of images, in the first sequence of images, that are acquired prior to detecting activation of the shutter button at the first time meet (930) one or more predefined grouping criteria. In some embodiments, the predefined grouping criteria include selecting (932) a predefined number of images prior to detecting activation of the shutter button. In some embodiments, the predefined grouping criteria include selecting (934) a predefined number of images prior to the representative image. In some embodiments, the predefined grouping criteria include selecting (936) images in a predefined range of time immediately prior to detecting activation of the shutter button. In some embodiments, the predefined grouping criteria include selecting (938) images in a predefined range of time immediately prior to the time at which the representative image is acquired.
In some embodiments, the live preview is (940) displayed as part of a media capture user interface that includes an affordance for enabling the first media acquisition mode and the shutter button is a software button displayed in the media capture user interface (e.g., shutter button 514,
In some embodiments, the device begins (944) acquiring and storing images upon entering the first media acquisition mode (independent of detecting activations of the shutter button). The device deletes (946) (or marks for deletion) images that are not grouped into a respective plurality of images that are in temporal proximity to activation of the shutter button at a respective time while in the first media acquisition mode.
In some embodiments, the device begins (948) acquiring and storing images upon displaying the live preview (independent of detecting activations of the shutter button). The device deletes (950) (or marks for deletion) images that are not grouped into a respective plurality of images that are in temporal proximity to activation of the shutter button at a respective time while in the first media acquisition mode.
In some embodiments, the devices acquire (952) and store images while displaying the live preview, independent of detecting activations of the shutter button. The device deletes (954) (or marks for deletion) acquired and stored images that are not grouped into a respective plurality of images that are in temporal proximity to activation of the shutter button at a respective time while in the first media acquisition mode.
In some embodiments, the user can select a length of time that an image is retained before discarding the image if it is not grouped into a sequence of images. For example, the user can set the device to retain images displayed in the live preview mode for 5, 10, or 20 seconds. Assuming, for example, that the user selects a length of time of 5 seconds, an image displayed in the live preview is retained for 5 seconds after it is displayed in the live preview and then discarded (e.g., deleted, or marked for deletion) if it is not grouped into a sequence of images by activation of the shutter button.
In some embodiments, in response to detecting activation of the shutter button at the first time, the device associates (956), with the first sequence of images, audio that corresponds to the first sequence of images (e.g., including audio that was recorded prior to detecting activation of the shutter button and audio that was recorded after detecting activation of the shutter button). In some embodiments, the device includes a microphone (or is in communication with a microphone) and audio detected when the sequence of images was acquired is stored in the memory and linked to (or otherwise associated with) the stored first sequence of images. For example,
In some embodiments, in response to detecting activation of the shutter button at the first time, the device associates (958), with the first sequence of images, metadata that corresponds to the first sequence of images (e.g.,
In some embodiments, the device automatically excludes (960) (or deletes or forgoes displaying as part of the sequence) blurred images from the first sequence of images.
In some embodiments, after detecting activation of the shutter button at the first time, the device detects (962) a next activation of the shutter button at a second time (without detecting any activations of the shutter button between the first time and the second time). In response to detecting the next activation of the shutter button at the second time: the device groups (964) a plurality of images acquired by the camera in temporal proximity to the activation of the shutter button at the second time into a second sequence of images. The second sequence of images includes: a plurality of images acquired by the camera prior to detecting activation of the shutter button at the second time and a representative image that represents the second sequence of images and was acquired by the camera after one or more of the other images in the second sequence of images. In some embodiments, capturing sequences of images is done in an analogous manner to capturing individual images with a conventional digital camera, which makes it simple and intuitive for even novice users to capture such sequences of images. For a conventional digital camera, each time the shutter button is activated, an individual image is captured. Here, each time the shutter button is activated, a sequence of images is captured. This manner of capturing sequences of images is different from the manner of capturing video with a conventional digital camera. For capturing video with a conventional digital camera, a first activation of a shutter button starts recording the video and the next activation of the shutter button stops recording the video.
In some embodiments, the first frame and/or a last frame in a sequence are changed in accordance with a change of the representative image (e.g., as shown in
In some embodiments, the number of images between the initial image and the representative image and the number of images between the revised initial image and the revised representative image is the same. In some embodiments, the number of images between the representative image and the final image and the number of images between the revised representative image and the revised final image is the same. In some embodiments, the added images are in temporal proximity to the one end of the first sequence of images. For example, if the revised representative image is three images earlier in the first sequence of images, then three images (acquired immediately before the initial image) are added to the beginning of the first sequence (with the earliest of the three images becoming the revised initial image), and three images are deleted from the end of the first sequence.
In some embodiments, the display is (972) a touch-sensitive display. The device receives (974) a request to display the representative image from the first sequence of images. In response to receiving the request to display the representative image, the device displays (976) the representative image on the touch-sensitive display. While displaying the representative image, the device receives (978) a touch input on the touch-sensitive display on the representative image, the touch input including a characteristic that changes with time. For example, an intensity of the touch input changes with time, or a position of a contact in the touch input changes with time (e.g., due to lateral movement of the contact across the touch-sensitive display). In response to receiving the touch input on the touch-sensitive display on the representative image, the device displays (980) (e.g., sequentially) images in the first sequence of images at a rate that is determined based on the change in the characteristic of the touch input over time (for example, as described with reference to the press-and-hold gesture,
It should be understood that the particular order in which the operations in
The device displays (1002) a representative image on the display (e.g., while the device is in an image presentation mode, see
While displaying the representative image on the display, the device detects (1004) a first portion of a first input (e.g., an input on the touch-sensitive surface, see first portion 616-1 of first input 616,
In response to detecting the first portion of the first input, the device replaces (1010) display of the representative image with display, in sequence, of the one or more images acquired by the camera after acquiring the representative image (e.g., as shown in
In some embodiments, replacing display of the representative image with display, in sequence, of the one or more images acquired by the camera after acquiring the representative image includes updating (e.g., replacing) the displayed image multiple times a second (e.g., 10, 20, 30, or 60 times per second), optionally without regard to whether or not the first portion of the first input meets one or more predetermined intensity criteria. In some embodiments, the animation is a fluid animation that is updated as the intensity of the first portion of the first input changes, so as to provide feedback to the user as to the amount of intensity detected by the device (e.g., feedback as to the amount of force applied by the user). In some embodiments the animation is updated smoothly and quickly so as to create the appearance for the user that the user interface is responding in real-time to changes in force applied to the touch-sensitive surface (e.g., the animation is perceptually instantaneous for the user so as to provide immediate feedback to the user and enable the user to better modulate the force that they are applying to the touch-sensitive surface to interact efficiently with user interface objects that are responsive to contacts with different or changing intensity).
In some embodiments, an animation showing the sequence of images being replaced, in sequence, is displayed in a manner that dynamically responds to small changes in the intensity of the first contact (e.g., as shown in
In some embodiments, after detecting the first portion of the first input, the device detects (1014) a second portion of the first input (e.g., continuing to detect sufficient contact and/or intensity in a finger gesture). In some embodiments, the second portion is a continuation of the first input that has the same characteristics as the first portion of the first input (e.g., there is no time dependent change between the first portion and the second portion of the first input). In some embodiments, unless interrupted or discontinued by the user, the first portion of the first input lasts as long as it takes to perform operation 1010, and anything after that is the second portion, or a later portion, of the first input.
In some embodiments, in response to detecting the second portion of the first input, the device displays (1016), in sequence, the one or more images acquired by the camera before acquiring the representative image, the representative image, and the one or more images acquired by the camera after acquiring the representative image (e.g., as shown in
In some embodiments, instead of responding to detecting the first portion of the first input by replacing display of the representative image with display, in sequence, of the one or more images acquired by the camera after acquiring the representative image, the device responds to detecting the first portion of the first input by replacing display of the representative image with display, in sequence, of the initial image of the sequence followed by the remainder of the sequence.
In some embodiments, the sequence of images is displayed (1018), in response to detecting the second portion of the first input, in sequence at a fixed rate. In some embodiments, images in the sequence of images are sequentially displayed at a fixed rate, independent of the intensity of a contact in the first input (e.g., during the second portion of the first input). For example, the sequence of images is sequentially displayed at a 1× video playback rate (e.g., a rate at which the images were obtained) during the second portion of the first input. In some embodiments, the rate at which images in the sequence of images are sequentially displayed during the second portion of the first input depends on the intensity of a contact in the first input. For example, the rate increases as the intensity of the contact increases. In some embodiments, the sequence of images is displayed, in response to detecting the second portion of the first input, in sequence at a rate that is based on an intensity of a contact in the first portion of the input.
In some embodiments, the device cross fades (1020) from displaying, in sequence, the one or more images acquired by the camera after acquiring the representative image to displaying, in sequence, the one or more images acquired by the camera before acquiring the representative image. In some embodiments, a cross fade animation is displayed from the end of the sequence of images (e.g., as shown in
In some embodiments, in response to detecting the second portion of the first input, the device presents (1022) audio that corresponds to the sequence of images. In some embodiments, in response to detecting the second portion of the first input, the entire sequence of images is displayed with corresponding audio that was recorded when the sequence of images was acquired. In some embodiments, audio is not presented in response to detecting the first portion of the first input. In some embodiments, the audio is presented during the first complete playback of the sequence of images (e.g., in response to detecting the second portion of the first input). In some embodiments, if the first input is maintained after the first complete playback of the sequence of images (e.g., in response to detecting the second portion of the first input), the audio is not presented again during subsequent playbacks of the sequence in response to continued detection of the first input. In some embodiments, for a given input, the audio is only presented during the first complete playback of the sequence of images. In some embodiments, for a given input, the audio is only presented during the second complete playback of the sequence of images.
In some embodiments, after detecting the second portion of the first input, the device detects (1024) a third portion of the first input (e.g., continuing to detect sufficient contact and/or intensity in a finger gesture, as shown in
In some embodiments, in response to detecting the third portion of the first input, the device displays (1028) metadata that corresponds to the sequence of images. In some embodiments, if pressure and/or contact in the first input is maintained, the sequence of images is displayed again with concurrent display of metadata for the sequence of images, such as time, date, location (e.g., via GPS), weather, music that was playing when the sequence of images was acquired (e.g., music identified with music identification software in the device, such as Shazam, SoundHound, or Midomi), local event information (such as a sports game that was being played when and where the first sequence of images was acquired), and/or post-event information (such as a final score). For example,
In some embodiments, the device detects (1030) termination of the first input (e.g., detecting liftoff of a contact in the first input or detecting the intensity of a contact in the first input drop below a predetermined threshold intensity value, such as ITL, as shown in
In some embodiments, the device detects (1034) termination of the first input (e.g., detecting liftoff of a contact in the first input or detecting the intensity of a contact in the first input drop below a predetermined threshold intensity value, such as ITL, as shown in
In some embodiments, the sequence of images is (1038) configured to be sequentially displayed in a loop in either a forward direction or a reverse direction. The device detects (1040) termination of the first input (e.g., the device detects liftoff of a contact in the first input or detecting the intensity of a contact in the first input drop below a predetermined threshold intensity value) while displaying a first image in the sequence of images. In response (1042) to detecting termination of the first input while displaying the first image in the sequence of images: in accordance with a determination that there are fewer images between the first image and the representative image when the loop is traversed in the forward direction, the device sequentially displays images from the first image to the representative image in the forward direction, and in accordance with a determination that there are fewer images between the first image and the representative image when the loop is traversed in the reverse direction, the device sequentially displays images from the first image to the representative image in the reverse direction.
In some embodiments, the one or more images acquired by the camera after acquiring the representative image are sequentially displayed (1044) in accordance with respective intensity levels applied by the first input. For example, as shown in
In some embodiments, the first portion of the first input includes (1046) a change in intensity of a contact detected on the touch-sensitive surface (e.g., as shown in
In some embodiments, the respective number of images is based (1048) on the magnitude of the change in intensity of the contact. For example, in
In some embodiments, when the change in intensity of the contact has a first magnitude, the first sequential image is (1050) immediately after the respective image in the sequence of images and the second sequential image is immediately after the first sequential image in the sequence of images. In some embodiments, when the respective change in intensity of the contact has a second magnitude that is greater than the first magnitude, the first sequential image spaced apart from the respective image by a respective number of images in the sequence of images and the second sequential image is spaced apart from the first sequential image by the respective number of images in the sequence of images, wherein the respective number of images is one or more images. For example, in
In some embodiments, the first portion of the first input includes (1052) a change in intensity of a contact detected on the touch-sensitive surface (e.g., as shown in
It should be understood that the particular order in which the operations in
The device displays (10002) a representative image on the display. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. In some embodiments, the sequence of images is analogous to the sequence of images described with reference to operation 1002 of method 1000.
While displaying the representative image on the display, the device detects (10004) a first portion of a first input. In some embodiments, the first input is (10006) a press-and-hold gesture. In some embodiments, the first input is analogous to the first input described with reference to operations 1004-1008 of method 1000.
In response to detecting the first portion of the first input: the device transitions (10008) from displaying the representative image to displaying a respective prior image in the sequence of images, wherein the respective prior image was acquired by the camera before acquiring the representative image; and, after transitioning from displaying the representative image to displaying the respective prior image, the device displays, in sequence starting with the respective prior image, at least some of the one or more images acquired by the camera before acquiring the representative image and at least some of the one or more images acquired by the camera after acquiring the representative image. In some embodiments, after transitioning from displaying the representative image to displaying the respective prior image, the device displays, in sequence starting with the respective prior image, at least some of the one or more images acquired by the camera before acquiring the representative image, the representative image, and at least some of the one or more images acquired by the camera after acquiring the representative image.
In some embodiments, transitioning from displaying the representative image to displaying the respective prior image includes displaying (10010), in sequence, at least some of the one or more images acquired by the camera after acquiring the representative image and then replacing display of a respective subsequent image acquired after acquiring the representative image with the respective prior image (e.g., the device cross fades and/or blurs to switch from displaying the respective subsequent image to displaying the respective prior image, as described with reference to diagram 650,
In some embodiments, transitioning from displaying the representative image to displaying the respective prior image includes replacing (10012) display of the representative image with the respective prior image (e.g., the device cross fades and/or blurs to switch from displaying the representative image to displaying the respective prior image, without displaying one or more images acquired by the camera after acquiring the representative image prior to the switch, as described with reference to diagram 656,
In some embodiments, transitioning from displaying the representative image to displaying the respective prior image includes: in accordance with a determination that the first portion of the first input meets first playback criteria (e.g., detecting a slow increase in intensity of a contact to a playback intensity threshold or detecting an increase in intensity of the contact to a slow playback intensity threshold that is lower than a fast playback intensity threshold), displaying (10014), in sequence, at least some of the one or more images acquired by the camera after acquiring the representative image and then replacing display of a respective subsequent image acquired after acquiring the representative image with the respective prior image (e.g., cross fading and/or blurring to switch from displaying the respective subsequent image to displaying the respective prior image); and, in accordance with a determination that the first portion of the first input meets second playback criteria (e.g., detecting a fast increase in intensity of the contact to the playback intensity threshold or detecting an increase in intensity of the contact to the fast playback intensity threshold), different from the first playback criteria, replacing display of the representative image with the respective prior image (e.g., cross fading and/or blurring to switch from displaying the representative image to displaying the respective prior image, without displaying one or more images acquired by the camera after acquiring the representative image prior to the switch).
In some embodiments, the device includes (10016) one or more sensor units to detect intensity of contacts with the touch-sensitive surface. The first input includes a contact on the touch-sensitive surface. The first playback criteria include a criterion that is met when the contact has a characteristic intensity above a first intensity threshold (e.g., light press threshold ITL,
In some embodiments, the one or more images acquired by the camera before acquiring the representative image and the one or more images acquired by the camera after acquiring the representative image are displayed (10018), in sequence starting with the respective prior image, at a fixed rate (e.g., in an analogous manner to the display of images at a fixed rate described with reference to operation 1018, method 1000).
In some embodiments, the device presents (10020) audio that corresponds to the sequence of images (e.g., analogous to presentation of audio described with reference to operation 1022, method 1000).
In some embodiments, after detecting the first portion of the first input, the device detects (10022) a second portion of the first input. In response to detecting the second portion of the first input, the device displays, in sequence, at least some of the one or more images acquired by the camera before acquiring the representative image and at least some of the one or more images acquired by the camera after acquiring the representative image (e.g., in an analogous manner to operations 1024-1028, method 1000). In some embodiments, in response to detecting the second portion of the first input, the device displays (10024) metadata that corresponds to the sequence of images.
In some embodiments, the device detects (10026) termination (e.g. liftoff) of the first input. In response to detecting termination of the first input, the device displays the representative image. (e.g., in an analogous manner to operations 1030-1032, method 1000).
In some embodiments, the device detects (10028) termination (e.g. liftoff) of the first input while displaying a first image in the sequence of images. In response to detecting termination of the first input while displaying the first image in the sequence of images: in accordance with a determination that the first image occurs before the representative image in the sequence of images, the device sequentially displays, in chronological order, images from the first image to the representative image, and in accordance with a determination that the first image occurs after the representative image in the sequence of images, the device sequentially displays, in reverse-chronological order, images from the first image to the representative image (e.g., in an analogous manner to operations 1034-1036, method 1000).
In some embodiments, the sequence of images is (10030) configured to be sequentially displayed in a loop in either a forward direction or a reverse direction. The device detects termination (e.g., liftoff) of the first input while displaying a first image in the sequence of images. In response to detecting termination of the first input while displaying the first image in the sequence of images: in accordance with a determination that there are fewer images between the first image and the representative image when the loop is traversed in the forward direction, the device sequentially displays images from the first image to the representative image in the forward direction, and in accordance with a determination that there are fewer images between the first image and the representative image when the loop is traversed in the reverse direction, the device sequentially displays images from the first image to the representative image in the reverse direction (e.g., in an analogous manner to operations 1038-1042, method 1000).
It should be understood that the particular order in which the operations in
At an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface: the device displays (10052) a representative image on the display (e.g., representative image 602-1,
The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. In some embodiments, the representative image is an initial image in the sequence of images. In some embodiments, the sequence of images includes (10054) one or more images acquired by the camera before acquiring the representative image (e.g., sequence of images is analogous to the sequence of images described with reference to operation 1002 of method 1000).
While displaying the representative image on the display, the device detects (10056) a first input that includes detecting an increase in a characteristic intensity of a contact on the touch-sensitive surface to a first intensity that is greater than a first intensity threshold (e.g., light press threshold ITL,
In some embodiments, the first input is (10058) a press-and-hold gesture. In some embodiments, the first input is analogous to the first input described with reference to operations 1004-1008 of method 1000.
In response to detecting the increase in the characteristic intensity of the contact, the device advances (10060), in a first direction (e.g., in chronological order), through the one or more images acquired by the camera after acquiring the representative image at a rate that is determined based at least in part on the first intensity (e.g., as described with reference to
After advancing through the one or more images acquired by the camera after acquiring the representative image at the rate that is determined based on the first intensity, the device detects (10062) a decrease in intensity of the contact to a second intensity that is less than the first intensity.
In response to detecting the decrease in the characteristic intensity of the contact to the second intensity: in accordance with a determination that the second intensity is above the first intensity threshold, the device continues (10064) to advance, in the first direction, through the one or more images acquired by the camera after acquiring the representative image at a second rate, wherein: the second rate is determined based at least in part on the second intensity and the second rate is slower than the first rate; and, in accordance with a determination that the second intensity is below the first intensity threshold, the device moves, in a second direction that is opposite to the first direction (e.g., reverse-chronological order), through the one or more images acquired by the camera after acquiring the representative image at a rate that is determined based at least in part on the second intensity (e.g., device 100 moves backwards in the sequence of images 602 from
In some embodiments, images are (10066) displayed, in sequence, at a rate that increases as the characteristic intensity of the contact increases (e.g., the first rate and/or the second rate is proportional to the characteristic intensity of the contact). In some embodiments, in accordance with a determination that the characteristic intensity of the contact is above a first intensity threshold, display of the representative image is replaced with display, in sequence, of at least some of the one or more images acquired by the camera after acquiring the representative image at a rate that increases as the characteristic intensity of the contact increases.
In some embodiments, in accordance with a determination that the characteristic intensity of the contact is below the first intensity threshold, images in the sequence are displayed in reverse-chronological order at a backward rate that increases as the characteristic intensity of the contact decreases (e.g., as shown in rate diagrams 646,
In some embodiments, the rate forward or backward is determined in real-time or near-real time, so that the user can speed up or slow down progress through the images (either in the forward or reverse direction) by changing the characteristic intensity of the contact.
In some embodiments, the images are (10068) displayed, in sequence, at a rate proportional to a difference between the characteristic intensity of the contact and the first intensity threshold (e.g., the first rate and/or the second rate is proportional to the difference between the characteristic intensity of the contact and the first intensity threshold). In some embodiments, in accordance with a determination that the characteristic intensity of the contact is above a first intensity threshold, display of the representative image is replaced with display, in sequence, of at least some of the one or more images acquired by the camera after acquiring the representative image at a rate proportional to a difference between the characteristic intensity of the contact and the first intensity threshold.
In some embodiments, in accordance with a determination that the characteristic intensity of the contact is below the first intensity threshold, images in the sequence are displayed in reverse-chronological order at a backward rate proportional to the difference between the characteristic intensity of the contact and the first intensity threshold.
In some embodiments, the rate forward or backward is determined in real-time or near-real time, so that the user can speed up or slow down progress through the images (either in the forward or reverse direction) by changing the characteristic intensity of the contact.
In some embodiments, the device decreases (10070) a rate at which images in the sequence of images are displayed as a terminus of the sequence of images is approached e.g., independent of the characteristic intensity of the contact).
For example, in some embodiments, the first rate is (10072) determined based in part on a proximity of a currently displayed image to an end of the sequence of images (e.g., as playback nears the end of the sequence, the rate of advancement slows down, so that the playback of the sequence of images slows to a stop at the end of the sequence of images). Thus, the device “brakes” slightly as it reaches the end of the sequence of images.
As another example, in some embodiments, the second rate is (10074) determined based in part on a proximity of a currently displayed image to a beginning of the sequence of images (e.g., as reverse playback nears the beginning of the sequence, the rate of backwards movement slows down, so that the reverse playback of the sequence of images slows to a stop at the beginning of the sequence of images). Thus, the device “brakes” slightly as it reaches the beginning of the sequence of images moving in reverse-chronological order.
In some embodiments, the rate of advancement through the sequence of images is (10076) constrained by a maximum rate while the contact is detected on the touch-sensitive surface (e.g., a maximum rate of 2×, where x is the standard playback speed for the content, e.g., the speed at which playing back for 1 second corresponds to 1 second of time elapsing during the acquisition of the images in the sequence).
In some embodiments, intensity values of the characteristic intensity of the contact proximate to the first intensity threshold are (10078) associated with rate values that are at least a predetermined amount away from a rate of zero images per second (e.g., 0.2× for values above the first intensity threshold and −0.2× for values below the first intensity threshold). Ensuring that the playback rate of the sequence of images does not get close to zero prevents the images from being played back so slowly that inconsistencies between the images become readily apparent, which avoids breaking the illusion of smooth playback through the sequence of images.
In some embodiments, the rate of movement through the sequence of images is (10080) constrained by a maximum reverse rate while the contact is detected on the touch-sensitive surface (e.g., a maximum reverse rate of −2×).
In some embodiments, the representative image is (10082) displayed as a background image on a lock screen of a device, and one or more foreground elements (e.g., a date, a time, one or more notifications, network status information, battery status information, device unlock instructions, and/or other status information) are not changed while the device advances through the one or more images captured after the respective image.
In some embodiments, the device displays (10084) metadata that corresponds to the sequence of images. For example, the device displays metadata such as time, date, location (e.g., via GPS), weather, music that was playing when the sequence of images was acquired (e.g., music identified with music identification software in the device, such as Shazam, SoundHound, or Midomi), local event information (such as a sports game that was being played when and where the first sequence of images was acquired), and/or post-event information (such as a final score).
In some embodiments, the device detects (10086) liftoff of the contact from the touch-sensitive surface. In response to detecting liftoff of the contact, the device moves through the images in the second direction at a rate that is greater than the maximum reverse rate (e.g., a rate of −4×).
In some embodiments, the device detects (10088) termination (e.g., liftoff) of the first input. In response to detecting termination of the first input, the device displays the representative image (e.g., in an analogous manner to operations 1030-1032, method 1000).
In some embodiments, the device detects (10090) termination (e.g., liftoff) of the first input while displaying a first image in the sequence of images. In response to detecting termination of the first input while displaying the first image in the sequence of images: in accordance with a determination that the first image occurs before the representative image in the sequence of images, the device sequentially displays, in chronological order, images from the first image to the representative image, and in accordance with a determination that the first image occurs after the representative image in the sequence of images, the device sequentially displays, in reverse-chronological order, images from the first image to the representative image (e.g., in an analogous manner to operations 1034-1036, method 1000).
It should be understood that the particular order in which the operations in
The device stores (1102) a plurality of sequences of images (e.g., in non-volatile memory and/or program memory). A respective sequence of images includes: a respective representative image taken by a camera, one or more images acquired by the camera after acquiring the respective representative image, and one or more images acquired by the camera before acquiring the respective representative image. In some embodiments, the camera that took the respective sequence of images is part of the electronic device. In some embodiments, the respective sequence of images was taken by a camera that is not part of the electronic device (e.g., the respective sequence of images was transferred to the electronic device after being taken with a camera on another device). In some embodiments, the respective sequence of images was obtained in response to detecting activation of a shutter button at a first time, as described herein with respect to
The device displays (1104) a first representative image for a first sequence of images in a movable first area on the display (e.g., while the device is in an image presentation mode, as shown in
In some embodiments, the first sequence of images is (1106) a message in a message conversation displayed in a scrollable region of a messaging application, and the first sequence of images is displayed as the scrollable region of the messaging application is scrolled (e.g., as the message moves across the display).
The device detects (1108) a drag gesture on the touch-sensitive surface (e.g., drag gesture 736,
In accordance with a determination (1112) that the drag gesture is in a first direction on the touch-sensitive surface (e.g., leftward or upward): in the moveable first area, the device replaces (1114) display of the first representative image for the first sequence of images with display, in chronological order, of at least some of one or more images for the first sequence of images acquired by the camera after acquiring the first representative image for the first sequence of images. The device also moves (1116) the first area in the first direction (e.g., drags the first area with the drag gesture). For example, in response to detecting a leftward drag gesture, as shown
In some embodiments, the movement of the first area in the first direction on the display corresponds to the movement of a contact in the drag gesture in the first direction on the touch-sensitive surface (e.g., movement of the contact appears to directly manipulate the movement of the first area). More generally, in some embodiments, the movement of a respective area that displays images in a respective sequence of images corresponds to the movement of a contact in a drag gesture on the touch-sensitive surface.
In some embodiments, the display, in chronological order in the first area, of at least some of the one or more images for the first sequence of images acquired by the camera after acquiring the first representative image occurs in accordance with the movement of a contact in the drag gesture. Thus, if the movement of the contact in the first direction speeds up, the display of the chronological progression of images in the first area speeds up. If the movement of the contact in the first direction slows down, the display of the chronological progression of images in the first area slows down. If the movement of the contact in the first direction is paused, the display of the chronological progression of images in the first area is paused. And, if the movement of the contact reverses direction (e.g., from a leftward drag gesture to a rightward drag gesture), the display of the progression of images in the first sequence of images in the first area is reversed and the images are shown in reverse chronological order in accordance with the movement of the contact in the reverse direction. More generally, in some embodiments, for a respective sequence of images, the display of a progression of images in the respective sequence of images, in a respective area, occurs in accordance with the movement of a contact in the drag gesture.
In some embodiments, moving the first area in the first direction includes (1118) moving at least part of the first area off of the display in the first direction (e.g., leftward or upward). In some embodiments, as a result of moving the first area in the first direction, only a portion of the first area is displayed on the display. For example, as shown in
In some embodiments, in accordance with the determination that the drag gesture is in the first direction on the touch-sensitive surface (e.g., leftward or upward): the device moves (1120) a movable second area in the first direction. In some embodiments, the movable second area is an area that displays images in the second sequence of images, without displaying images from sequences of images other than the second sequence of images (e.g., movable second area 738,
In some embodiments, the display, in chronological order in the second area, of at least some of the one or more images for the second sequence of images acquired by the camera before acquiring the second representative image occurs in accordance with the movement of a contact in the drag gesture (e.g., in analogous manner to that described above with reference to the first sequence of images). For example, during the drag gesture, the images in the first area and the images in the second area are both advancing at the same rate, with the rate based on the movement of the contact.
In some embodiments, while moving the second area in the first direction, the second area just displays the second representative image for the second sequence of images, without displaying other images in the second sequence of images.
In some embodiments, instead of moving the second area in the first direction, the second area is underneath the first area in a z-layer (front-to-back) order, and the second area is revealed as the first area moves off the display in the first direction.
In some embodiments, like detecting a drag gesture in the first direction, detecting activation of a next icon or button (e.g., next icon 750-1,
In some embodiments, moving the second area in the first direction includes (1124) moving at least part of the second area onto the display in the first direction (e.g., leftward or upward). In some embodiments, as a result of moving the second area in the first direction, only a portion of the second area is displayed on the display, with more of the second area revealed as the second area is dragged in the first direction. For example, as shown in
In some embodiments, in accordance with the determination that the drag gesture is in the first direction on the touch-sensitive surface (e.g., leftward or upward): after moving the second area in the first direction, the device displays (1126) the second representative image for the second sequence of images in the second area. For example,
In some embodiments, while displaying the second representative image for the second sequence of images in the second area, the device detects (1128) a change in intensity of an input corresponding to the second representative image. In response to detecting the change in intensity of the input, the device advances (1130) through the second sequence of images in the second area without moving the second area on the display (e.g., starting with images chronologically after the second representative image and looping back to images chronologically before the second representative image). For example, in some embodiments, the user can pause the drag gesture, thereby converting the drag gesture to a press-and-hold gesture that triggers playback the second sequence of images as described in greater detail with reference to methods 1000/10000/10050,
In some embodiments, the device detects (1132) termination (e.g., lift off) of the drag gesture while moving the first area and the second area. In response to detecting termination (1134) of the drag gesture while moving the first area and the second area: in accordance with a determination that the drag gesture meets next-sequence-navigation criteria (e.g., more than half of the first area has been moved off the display (as shown
In some embodiments, in response to detecting termination of the drag gesture while moving the first area and the second area: in accordance with a determination that the drag gesture does not meet the next-sequence-navigation criteria: the devices moves (1138) the second area completely off the display in a second direction, opposite the first direction; moves the first area completely onto the display; and displays the first representative image for the first sequence of images in the first area. In some embodiments, the display, in chronological order in the first area, of at least some of the one or more images for the first sequence of images acquired by the camera after acquiring the first representative image is reversed as the first area moves completely onto the display until the first representative image is displayed. In some embodiments, the display, in chronological order in the second area, of at least some of the one or more images for the second sequence of images acquired by the camera before acquiring the second representative image is reversed as the second area moves completely off the display.
In some embodiments in accordance with a determination (1140) that the drag gesture is in a second direction on the touch-sensitive surface (e.g., rightward or downward): in the moveable first area, the device replaces (1142) display of the first representative image for the first sequence of images with display, in reverse chronological order, of at least some of one or more images for the first sequence of images acquired by the camera before acquiring the first representative image for the first sequence of images. The device also moves (1144) the first area in the second direction (e.g., rightward or downward).
In some embodiments, the movement of the first area in the second direction on the display corresponds to the movement of a contact in the drag gesture in the second direction on the touch-sensitive surface (e.g., movement of the contact appears to directly manipulate the movement of the first area). More generally, in some embodiments, the movement of a respective area that displays images in a respective sequence of images corresponds to the movement of a contact in a drag gesture on the touch-sensitive surface.
In some embodiments, the display, in reverse chronological order in the first area, of at least some of the one or more images for the first sequence of images acquired by the camera before acquiring the first representative image occurs in accordance with the movement of a contact in the drag gesture. Thus, if the movement of the contact in the second direction speeds up, the display of the reverse chronological progression of images in the first area speeds up. If the movement of the contact in the second direction slows down, the display of the reverse chronological progression of images in the first area slows down. If the movement of the contact in the second direction is paused, the display of the reverse chronological progression of images in the first area is paused. And, if the movement of the contact reverses direction (e.g., from a rightward drag gesture to a leftward drag gesture), the display of the progression of images in the first sequence of images in the first area is reversed and the images are shown in chronological order in accordance with the movement of the contact in the reverse direction. More generally, in some embodiments, for a respective sequence of images, the display of a progression of images in the respective sequence of images, in a respective area, occurs in accordance with the movement of a contact in the drag gesture.
In some embodiments, moving the first area in the second direction includes (1146) moving at least part of the first area off of the display in the second direction (e.g., rightward or downward). For example, in response to detecting rightward drag gesture 744,
In some embodiments, in accordance with the determination that the drag gesture is in the second direction on the touch-sensitive surface (e.g., to the right or downward): the device moves (1148) a third area in the second direction. In some embodiments, the movable third area is an area that displays images in the third sequence of images, without displaying images from sequences of images other than the third sequence of images. In some embodiments, the movable third area is adjacent to the movable first area (e.g., to the left of the movable first area). While moving the third area in the second direction, the device also displays (1150), in reverse chronological order in the third area, at least some of one or more images for a third sequence of images acquired by the camera after acquiring a third representative image for the third sequence of images.
In some embodiments, the display, in reverse chronological order in the third area, of at least some of the one or more images for the third sequence of images acquired by the camera after acquiring the third representative image occurs in accordance with the movement of a contact in the drag gesture (e.g., in analogous manner to that described above with reference to the first sequence of images). For example, during the drag gesture, the images in the first area and the images in the third area are both retreating at the same rate, with the rate based on the movement of the contact.
In some embodiments, while moving the third area in the second direction, the third area just displays the third representative image for the third sequence of images, without displaying other images in the third sequence of images.
In some embodiments, instead of moving the first area in the second direction, the first area is underneath the third area in a z-layer (front-to-back) order, and the first area is covered as the third area moves onto the display in the second direction.
In some embodiments, like detecting a drag gesture in the second direction, detecting activation of a previous icon (e.g., previous icon 750-2,
In some embodiments, moving the third area in the second direction includes (1152) moving at least part of the third area onto the display in the second direction (e.g., rightward or downward). For example, in response to detecting rightward drag gesture 744,
In some embodiments, the first sequence of images was acquired (1154) by the camera before the second sequence of images and the first sequence of images was acquired by the camera after the third sequence of images. For example, the sequences of images are in chronological order from left to right.
In some embodiments, in accordance with the determination that the drag gesture is in the second direction on the touch-sensitive surface (e.g., rightward or downward): after moving the third area in the second direction, the device displays (1156) the third representative image for the third sequence of images in the third area (e.g., as shown in
In some embodiments, the device detects (1158) termination (e.g., lift off) of the drag gesture while moving the first area and the third area (e.g., as shown in
In some embodiments, in accordance with a determination that the drag gesture does not (1164) meet the previous-sequence-navigation criteria: the device moves the third area completely off the display in the first direction (e.g., leftward or upward); moves the first area completely onto the display; and displays the first representative image for the first sequence of images in the first area. In some embodiments, the display, in reverse chronological order in the first area, of at least some of the one or more images for the first sequence of images acquired by the camera before acquiring the first representative image is reversed as the first area moves completely onto the display until the first representative image is displayed. In some embodiments, the display, in reverse chronological order in the third area, of at least some of the one or more images for the third sequence of images acquired by the camera after acquiring the third representative image is reversed as the third area moves completely off the display.
It should be understood that the particular order in which the operations in
The device stores (11002) a plurality of sequences of images. A respective sequence of images includes: a respective representative image taken by a camera, and one or more images acquired by the camera before acquiring the respective representative image. In some embodiments, the camera that took the respective sequence of images is part of the electronic device. In some embodiments, a respective sequence of images includes (11004) one or more images acquired by the camera after acquiring the respective representative image.
In some embodiments, the respective sequence of images was taken by a camera that is not part of the electronic device (e.g., the respective sequence of images was transferred to the electronic device after being taken with a camera on another device). In some embodiments, the respective sequence of images was obtained in response to detecting activation of a shutter button at a first time, as described herein with respect to
The device displays (11006) a first representative image for a first sequence of images in a movable first area on the display (e.g., while the device is in an image presentation mode). In some embodiments, the movable first area is an area that displays images in the first sequence of images, without displaying images from sequences of images other than the first sequence of images (e.g., representative image 702-3,
In some embodiments, the first sequence of images is (11008) a message in a message conversation displayed in a scrollable region of a messaging application, and the first sequence of images is displayed as the scrollable region of the messaging application is scrolled (e.g., as described with reference to operation 1106, method 1100).
The device detects (11010) a gesture on the touch-sensitive surface, the gesture including movement by a contact that corresponds to movement in a first direction on the display (e.g., flick/swipe gesture 740,
In response to detecting the gesture on the touch-sensitive surface, the device: moves (11012) (e.g., with the first representative image) the first area in the first direction on the display; moves a movable second area in the first direction on the display; and, in accordance with a determination that sequence-display criteria are met, while moving the second area in the first direction, displays, in chronological order in the second area, at least some of one or more images for a second sequence of images acquired by the camera before acquiring a second representative image for the second sequence of images (e.g., display of sequence of images 724,
In some embodiments, in response to detecting the gesture on the touch-sensitive surface: in accordance with a determination that the sequence-display criteria are not met, while moving the second area in the first direction, the device displays (11014) the second representative image for the second sequence of images in the movable second area on the display (without displaying other images in the second sequence of images in the moveable second area). In some embodiments, in accordance with a determination that the sequence-display criteria are not met, while moving the second area in the first direction, the device displays an initial image (rather than the second representative image) for the second sequence of images in the movable second area on the display, or another image acquired before the second representative image for the second sequence of images.
In some embodiments, the sequence-display criteria include (11016) a criterion that the contact lifts off prior to displaying, in chronological order in the second area, at least some of one or more images for the second sequence of images acquired by the camera before acquiring the second representative image. In some embodiments, if the contact continues to be detected while the second area is moving in the first direction, then just the representative image (or just the initial image) for the second sequence images is displayed while the second area moves in the first direction. For example, the contact is part of a leftward (or rightward) drag gesture that moves slowly across the touch sensitive surface and slowly drags the second area leftward (or rightward). Conversely, if the contact ceases to be detected while the second area is moved in the first direction, then an animated sequence of images taken prior to the second representative image is displayed in the second area while the second area continues to move in the first direction. For example, the contact is part of a leftward (or rightward) flick gesture that moves quickly across the touch sensitive surface and then lifts off while the second area is still moving leftward (or rightward). For example, the contact is part of a leftward (or rightward) drag gesture that moves across the touch sensitive surface (while displaying just the second representative image, or the initial image, for the second sequence of images in the second area) and then lifts off after at least a predetermined amount (e.g., 25%, 30%, 40%, or 50%) of the second area has moved onto the display. After liftoff, the remainder of the second area moves onto the display and at least some of the images for the second sequence of images acquired by the camera before acquiring the second representative image are displayed in the second area.
In some embodiments, moving the movable second area in the first direction on the display includes (11018) displaying a respective prior image that was acquired prior to acquiring the second representative image in the second region (e.g., the device initially displays the initial image in the sequence of images rather than the representative image).
In some embodiments, the sequence-display criteria include (11020) detecting liftoff of the contact (e.g., as described with reference to
In some embodiments, while moving the moveable first region, the device displays (11022) a simulated parallax effect for an image within the moveable first region such that the image within the moveable first region shifts relative to a frame of the moveable first region (e.g., as though the frame of the moveable first region were separated in a simulated z-direction from the image within the moveable first region).
In some embodiments, while moving the moveable second region while the contact is detected on the touch-sensitive surface (e.g., prior to displaying the images from the second sequence of images), the device displays (11024) a simulated parallax effect for an image within the moveable second region such that the image within the moveable second region shifts relative to a frame of the moveable second region (e.g., as though the frame of the moveable second region were separated in a simulate z-direction from the image within the moveable second region).
In some embodiments, moving the first area in the first direction includes (11026) moving at least part of the first area off of the display in the first direction (e.g., sliding the first area off the display,
In some embodiments, moving the second area in the first direction includes (11028) moving at least part of the second area onto the display in the first direction (e.g., sliding the second area onto the display in conjunction with sliding the first area off the display,
In some embodiments, after moving the second area in the first direction, the device displays (11030) the second representative image for the second sequence of images in the second area (e.g., as shown in
In some embodiments, while displaying the second representative image for the second sequence of images in the second area, the device detects (11032) a change in intensity of an input corresponding to the second representative image. In response to detecting the change in intensity of the input, the device advances through the second sequence of images in the second area without moving the second area on the display (e.g., the device performs any of the operations shown in
In some embodiments, the device detects (11034) termination of the drag gesture while moving the first area and the second area. In response to detecting termination of the drag gesture while moving the first area and the second area: in accordance with a determination that the drag gesture meets next-sequence-navigation criteria, the device: moves the first area completely off the display in the first direction; moves the second area completely onto the display; and displays the second representative image for the second sequence of images in the second area (e.g., as described with reference to operation 1136, method 1100).
In some embodiments, in response to detecting termination of the drag gesture while moving the first area and the second area: in accordance with a determination that the drag gesture does not meet the next-sequence-navigation criteria, the device: moves (11036) the second area completely off the display in a second direction, opposite the first direction; moves the first area completely onto the display; and displays the first representative image for the first sequence of images in the first area (e.g., as described with reference to operation 1138, method 1100).
It should be understood that the particular order in which the operations in
The device stores (1202) a plurality of sequences of images. A respective sequence of images includes: a respective representative image taken by a camera, one or more images acquired by the camera after acquiring the respective representative image, and one or more images acquired by the camera before acquiring the respective representative image. In some embodiments, the camera that took the respective sequence of images is part of the electronic device. In some embodiments, the respective sequence of images was taken by a camera that is not part of the electronic device (e.g., the respective sequence of images was transferred to the electronic device after being taken with a camera on another device). In some embodiments, the respective sequence of images was obtained in response to detecting activation of a shutter button at a first time, as described herein with respect to
The device stores (1204) a plurality of images that are distinct from the images in the plurality of sequences of images. A respective image in the plurality of images is not part of a sequence of images in the plurality of sequences of images.
The device displays (1206) a first image on the display (e.g., as shown in
In some embodiments, the first input is (1216) a press-and-hold gesture, the first operation displays at least a portion of the first sequence of images (e.g., as described herein with respect to
In some embodiments, the first input is (1218) a press-and-hold gesture, the first operation displays at least a portion of the first sequence of images (e.g., as described herein with respect to
In some embodiments, the device includes (1220) one or more sensors to detect intensity of contacts with the touch-sensitive surface, the first input includes a finger contact that satisfies first contact-intensity criteria (e.g., a finger gesture on the first image on a touch-sensitive display, or a finger gesture on a track pad while a cursor or other focus selector is over the first image on a display, wherein a contact in the finger gesture exceeds a light press (or deep press) intensity threshold for at least part of the input), the first operation displays at least a portion of the first sequence of images (e.g., as described herein with respect to
In some embodiments, the device includes (1222) one or more sensors to detect intensity of contacts with the touch-sensitive surface, the first input includes a finger contact that satisfies first contact-intensity criteria (e.g., a finger gesture on the first image on a touch-sensitive display, or a finger gesture on a track pad while a cursor or other focus selector is over the first image on a display, wherein a contact in the finger gesture exceeds a deep press intensity threshold for at least part of the input), the first operation displays at least a portion of the first sequence of images (e.g., as described herein with respect to
In some embodiments, the first input is (1224) a drag gesture, the first operation displays at least some of the images in the first sequence of images while transitioning from displaying the first image to displaying a second image (the second image not being an image in the first sequence of images) (e.g., as described herein with respect to
In some embodiments, when the first image is an image in a first sequence of images, the method further includes detecting a navigational input and navigating to a second image that is an image in the plurality of images that are distinct from the images in the plurality of sequences of images. The method further includes detecting a second input that shares one or more characteristics with the first input (e.g., intensity and/or path inputs). In some embodiments, the first input and the second input need not share a location. The method further includes, in response to detecting the second input, performing the second operation involving the second image.
It should be understood that the particular order in which the operations in
In accordance with some embodiments,
As shown in
The processing unit 1308 is configured to: while in a first media acquisition mode for the camera unit 1304 display (e.g., using the display enabling unit 1310) the live preview on the display unit 1302 (e.g., of images obtained from the camera unit 1304) while displaying the live preview, detect activation of a shutter button at a first time (e.g., using the sensor units 1306). In response to detecting activation of the shutter button at the first time, the processing unit 1308 is configured to group (e.g., with the grouping unit 1312) a plurality of images acquired by the camera unit 1304 in temporal proximity to the activation of the shutter button at the first time into a first sequence of images. The first sequence of images includes: a plurality of images acquired by the camera unit 1304 prior to detecting activation of the shutter button at the first time; a representative image that represents the first sequence of images and was acquired by the camera unit 1304 after one or more of the other images in the first sequence of images; and a plurality of images acquired by the camera unit 1304 after acquiring the representative image.
As shown in
The processing unit 1408 is configured to display a representative image on the display unit 1402 (e.g., with display enabling unit 1410). The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image and the sequence of images includes one or more images acquired by the camera before acquiring the representative image. The processing unit 1408 is further configured to, while displaying the representative image on the display unit 1402, detect a first portion of a first input (e.g., with the detecting unit 1412, which optionally detects inputs on the touch-sensitive surface unit 1404). The processing unit 1408 is configured, in response to detecting the first portion of the first input, replace display (e.g., with the display enabling unit 1410) of the representative image with display, on the display unit 1402, in sequence, of the one or more images acquired by the camera after acquiring the representative image. The processing unit 1408 is configured, after detecting the first portion of the first input, detect a second portion of the first input (e.g., with the detecting unit 1412). The processing unit 1408 is configured, in response to detecting the second portion of the first input, display, on the display unit 1402, in sequence, the one or more images acquired by the camera before acquiring the representative image, the representative image, and the one or more images acquired by the camera after acquiring the representative image.
As shown in
The processing unit 1508 is configured to store, in the memory unit 1516, a plurality of sequences of images. A respective sequence of images includes: a respective representative image taken by a camera, one or more images acquired by the camera after acquiring the respective representative image, and one or more images acquired by the camera before acquiring the respective representative image. The processing unit 1508 is further configured to display (e.g., with the display enabling unit 1510), on the display unit 1502, a first representative image for a first sequence of images in a movable first area on the display unit 1502. The processing unit 1508 is further configured to detect (e.g., with detecting unit 1512) a drag gesture on the touch-sensitive surface unit 1504. In accordance with a determination that the drag gesture is in a first direction on the touch-sensitive surface unit 1504: the processing unit 1508 is configured to replace (e.g., with the display enabling unit 1510), in the moveable first area, display of the first representative image for the first sequence of images with display, on the display unit 1502, in chronological order, of at least some of one or more images for the first sequence of images acquired by the camera after acquiring the first representative image for the first sequence of images. The processing unit 1508 is further configured to move (e.g., with the display enabling unit 1510) the first area in the first direction on the display unit 1502.
As shown in
The processing unit 1608 is configured to store, in the memory unit 1616, a plurality of sequences of images. A respective sequence of images includes: a respective representative image taken by a camera, one or more images acquired by the camera after acquiring the respective representative image, and one or more images acquired by the camera before acquiring the respective representative image. The processing unit 1608 is further configured to store, in the memory unit 1616, a plurality of images that are distinct from the images in the plurality of sequences of images. A respective image in the plurality of images is not part of a sequence of images in the plurality of sequences of images. The processing unit 1608 is further configured to display (e.g., with display enabling unit 1610) a first image on the display unit 1602. The processing unit 1608 is further configured to, while displaying the first image on the display unit 1602, detect (e.g., with detecting unit 1612) a first input. The processing unit 1608 is further configured to, in response to detecting the first input: in accordance with a determination (e.g., with determining unit 1614) that the first image is an image in a first sequence of images, perform a first operation that includes displaying (e.g., with display enabling unit 1610), on the display unit 1602, at least some of the images in the first sequence of images besides the first image; and, in accordance with a determination (e.g., with determining unit 1614) that the first image is an image in the plurality of images that are distinct from the images in the plurality of sequences of images, perform a second operation, distinct from the first operation, involving the first image.
As shown in
The processing unit 1708 is configured to enable display (e.g., with display enabling unit 1710) of a representative image on the display unit 1702. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. The processing unit 1708 is further configured to, while enabling display of the representative image on the display unit 1702, detect (e.g., with detecting unit 1712) a first portion of a first input. The processing unit 1708 is further configured to, in response to detecting the first portion of the first input, transition (e.g., with transitioning unit 1714) from displaying the representative image to displaying a respective prior image in the sequence of images. The respective prior image was acquired by the camera before acquiring the representative image. The processing unit 1708 is further configured to, in response to detecting the first portion of the first input, after transitioning from displaying the representative image to displaying the respective prior image, enable display (e.g., with display enabling unit 1710) of, in sequence starting with the respective prior image, at least some of the one or more images acquired by the camera before acquiring the representative image and at least some of the one or more images acquired by the camera after acquiring the representative image.
As shown in
The processing unit 1808 is configured to enable display (e.g., with display enabling unit 1810) of a representative image on the display unit 1802. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The processing unit 1808 is further configured to, while enabling display of the representative image on the display unit 1802, detect (e.g., with detecting unit 1812) a first input that includes detecting (e.g., with sensor units 1804) an increase in a characteristic intensity of a contact on the touch-sensitive surface unit 1804 to a first intensity that is greater than a first intensity threshold. The processing unit 1808 is further configured to, in response to detecting the increase in the characteristic intensity of the contact, advance (e.g., with moving unit 1814), in a first direction, through the one or more images acquired by the camera after acquiring the representative image at a rate that is determined based at least in part on the first intensity. The processing unit 1808 is further configured to, after advancing through the one or more images acquired by the camera after acquiring the representative image at the rate that is determined based on the first intensity, detect (e.g., with detecting unit 1812) a decrease in intensity of the contact to a second intensity that is less than the first intensity. The processing unit 1808 is further configured to, in response to detecting the decrease in the characteristic intensity of the contact to the second intensity: in accordance with a determination that the second intensity is above the first intensity threshold, continue to advance (e.g., with moving unit 1814), in the first direction, through the one or more images acquired by the camera after acquiring the representative image at a second rate. The second rate is determined based at least in part on the second intensity and the second rate is slower than the first rate. The processing unit 1808 is further configured to, in response to detecting the decrease in the characteristic intensity of the contact to the second intensity: in accordance with a determination that the second intensity is below the first intensity threshold, move (e.g., with moving unit 1814), in a second direction that is opposite to the first direction, through the one or more images acquired by the camera after acquiring the representative image at a rate that is determined based at least in part on the second intensity.
As shown in
The processing unit 1908 is configured to store (e.g., with storing unit 1914) a plurality of sequences of images. A respective sequence of images includes: a respective representative image taken by a camera, and one or more images acquired by the camera before acquiring the respective representative image. The processing unit 1908 is further configured to enable display (e.g., with display enabling unit 1910) of a first representative image for a first sequence of images in a movable first area on the display unit 1902. The processing unit 1908 is further configured to detect (e.g., with detecting unit 1912) a gesture on the touch-sensitive surface unit 1904, the gesture including movement by a contact that corresponds to movement in a first direction on the display unit 1902. The processing unit 1908 is further configured to, in response to detecting the gesture on the touch-sensitive surface unit 1904: move (e.g., with moving unit 1916) the first area in the first direction on the display unit 1902; move (e.g., with moving unit 1916) a movable second area in the first direction on the display unit 1902; and, in accordance with a determination that sequence-display criteria are met, while moving the second area in the first direction, enable display (e.g., with display enabling unit 1910) of, in chronological order in the second area, at least some of the one or more images for a second sequence of images acquired by the camera before acquiring a second representative image for the second sequence of images.
The photo editing user interface also includes an affordance 2006 (e.g., a toggle switch) for toggling between a first editing mode (e.g., an apply-to-all editing mode) and a second editing mode (e.g., a single image editing mode). In
In contrast, in
Returning to the example in which only representative image 2002-3 is modified (e.g., following from
In particular, as shown in
As noted above, in
In some embodiments, rather than replace display of representative image 2002-3 with at least some of the images acquired after representative image 2002-3 (e.g., images 2002-4 and image 2002-5) in any of the examples above, device 100 replaces display of representative image 2002-3 with display of a respective image acquired before representative image 2002-3 (e.g., omits the playback shown in
In some circumstances, modifying the representative image without modifying the additional images would result in a discontinuity when the enhanced photograph is played back. For example, as shown in
To that end, as shown in
In this example, device 100 detects a user input 2116 that is a request to select image 2110-b for sending to the user of the second device. For the purposes of explanation, in this example, image 2110-b is a representative image from a sequence of images (e.g., a representative image from an enhanced photo) that includes images acquired before representative image 2110-b and/or images acquired after representative image 2110-b.
As shown in
In contrast,
Second set of options 2122 includes: an option 2122-a for sending the representative image without sending the images acquired before representative image 2110-b and without sending the images acquired after representative image 2110-b (e.g., sending only representative image 2110-b as a still image); an option 2122-b for converting at least the portion of the sequence of images to an animated image format (e.g., a GIF format); an option 2122-c for converting at least the portion of the sequence of images to a video format (e.g., an MPEG format); and an option 2122-d to cancel. Device 100 also displays an indication 2120 that image 2110-b has been selected for sending to the second electronic device. In some embodiments, second set of options 2122 does not include an option to send the entire sequence of images (e.g., send the enhanced photo) because Robert's device is not configured to interact with the entire sequence of images as a group.
To that end,
As shown in
As shown in
In this example, when conversation user interface 2144 (
As also shown in
As shown in
In contrast,
Some scenes, more than others, are conducive to being captured as a sequence of images (e.g., an enhanced photo). For example, people often use the same portable multifunction device to capture important moments (e.g., a picture of their children smiling at the beach) and to capture more mundane images, such as taking a picture of a receipt for documentation purposes. In accordance with some embodiments,
In
While device 100 is in the media acquisition mode, device 100 performs scene recognition on the scene. For example, in some embodiments, the scene recognition includes detecting text, detecting movement, detecting people's faces, and/or detecting movement of device 100 (e.g., when the user is planning to track a target). In
In contrast,
Device 100 performs scene detection while live preview 2210 is displayed on the display. In this example, the action capture criteria are met when the device detects a threshold amount of movement. So, because the train is moving in the live preview 2210, in response to activation of shutter button 2206 at time 2210-3, device 100 retains a sequence of images 2218 (e.g., an enhance photo) as shown in
As shown in
The photo editing user interface also includes a “done” affordance 2301, which applies the user's modifications to the photo.
In
In
In
In
User interface 2314 includes second area 2322, displayed concurrently with area 2316. The representative image, or a currently selected image, is displayed in second area 2322.
Area 2316 includes a begin handle 2320-a that delimits a beginning image in the subset of the sequence of images. Area 2316 also includes an end handle 2320-b that delimits an ending image in the subset of the sequence of images. Begin handle 2320-a and end handle 2320-b are located at positions in the area 2316 that are automatically selected by the device (e.g., using scene detection). For example, device 100 uses scene detection to determine a period of time during which the best action transpired (e.g., by determining when a face is turned toward the camera, or determining when the images are least blurry). Device 100 sets begin handle 2320-a to a position in area 2316 representing the beginning of the period of time during which the best action transpired and sets end handle 2320-b to a position in area 2316 representing the end of the period of time during which the best action transpired.
User interface 2314 also includes reset affordance 2324. In
In
As shown in
As also shown in
As also shown in
In some embodiments, when the user selects “done” affordance 2301 while in trimming user interface 2314, which applies the user's trimming to the sequence of images, device 100 either deletes (or marks for deletion) the images not included in the subset of images (e.g., whose representations 2318 are not in between begin handle 2320-a and end handle 2320-b), or disables playback of the images not included in the subset of images. For example, when the trimmed sequence of images is played back in accordance with the embodiments described with reference to
Method 2400 provides an intuitive way to modify an enhanced photo. In particular, when the user is modifying a representative image for the enhanced photo (e.g., cropping, making black & white, changing balance and/or contrast), in some embodiments, method 2400 allows a user to specify (e.g., with a toggle switch) whether the modifications should be applied to just the representative image or to all of the images in the enhanced photo. When the modifications are applied to only the representative image, method 2400 provides playback recipes in accordance with a variety of embodiments. For example, in various embodiments, an enhanced photo that includes a sequence of images with a modified representative image is played back with the representative image modified, unmodified, or omitted. When the modifications are applied to the entire sequence of images, the enhanced photo plays back the modified sequence of images.
The device displays (2402) a representative image on the display (e.g., while the device is in an image presentation mode). The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. In some embodiments, the camera that took the sequence of images is part of the electronic device. In some embodiments, the sequence of images was taken by a camera that is not part of the electronic device (e.g., the sequence of images was transferred to the electronic device after being taken with a camera on another device). In some embodiments, the sequence of images was obtained in response to detecting activation of a shutter button at a first time, as described herein with respect to
While displaying the representative image on the display, the device detects (2404) an input to modify the representative image (e.g., an input to crop, filter, adjust the exposure, adjust the color, convert to black & white, or the like). For example, input 2008,
In response to detecting the input to modify the representative image: in accordance with a determination that the device is in a first editing mode (e.g., an affordance, such as toggle switch 2006,
In some embodiments, the device provides the affordance to toggle between the first editing mode and the second editing mode in a photo editing user interface (e.g., toggle switch 2006,
In some embodiments, in response to detecting the input to modify the representative image, the device presents the user with the option of applying the modification to only the representative image or to the representative image as well as the one or more images acquired by the camera after acquiring the representative image, and the one or more images acquired by the camera before acquiring the representative image.
In some circumstances, modifying the representative image without modifying the additional images would result in a discontinuity when the enhanced photograph is played back. For example, when the representative image is cropped or rotated relative to the additional image, playing-back the enhanced photograph would result in a “jump” when the representative image is displayed. Thus, in some embodiments, when making certain modifications to the representative image (e.g., cropping and/or rotating), without modifying the one or more images acquired by the camera after acquiring the representative image, and without modifying the one or more images acquired by the camera before acquiring the representative image, the device automatically turns off playback of the additional images, deletes the additional images, or causes the modified representative image to be saved to a new file as a still image. In some embodiments, the device warns the user that the modification will result in the modified representative image becoming a still image and provides the user with the option to continue the modification or cancel the modification (e.g., warning 2018,
In some embodiments, after modifying the representative image, without modifying the one or more images acquired by the camera after acquiring the representative image, and without modifying the one or more images acquired by the camera before acquiring the representative image: the device displays (2408) the modified representative image on the display. While displaying the modified representative image on the display, the device detects a first portion of a second input. In response to detecting the first portion of the second input, the device replaces display of the modified representative image with display of, in sequence, at least some of the one or more images acquired by the camera after acquiring the representative image. Thus, in some embodiments, in response to detecting the first portion of the second input, the one or more (unmodified) images acquired by the camera after acquiring the representative image are sequentially displayed (e.g., as shown in
After detecting the first portion of the second input, the device detects a second portion of the second input (e.g., continues to detect contact and/or intensity in a finger gesture). In response to detecting the second portion of the second input, the device displays, in sequence, at least some of the one or more images acquired by the camera before acquiring the representative image, the representative image without modification, and at least some of the one or more images acquired by the camera after acquiring the representative image (e.g., as shown in
Thus, in some embodiments, in response to detecting the second portion of the second input, the entire sequence of (unmodified) images is played, from the initial image to the final image in the sequence. For example, the representative image is modified by changing it to a black and white image, while the other images in the sequence remain color images. While the black and white representative image is displayed, a first portion of an input (e.g., a press-and-hold gesture or a deep press gesture) is detected. In response, the display of the black and white representative image is replaced by the display of, in sequence, one or more (unmodified) color images in the sequence of images, which were acquired by the camera after acquiring the representative image. In response to detecting a second portion of the second input, the entire sequence of images is played, from the initial image to the final image in the sequence, with all the images displayed in color.
In some embodiments, after modifying the representative image, without modifying the one or more images acquired by the camera after acquiring the representative image, and without modifying the one or more images acquired by the camera before acquiring the representative image: the device displays (2410) the modified representative image on the display. While displaying the modified representative image on the display, the device detects a second input. In response to detecting the second input, the device displays, in sequence, at least some of the one or more images acquired by the camera before acquiring the representative image, the representative image without modification, and at least some of the one or more images acquired by the camera after acquiring the representative image.
Thus, in some embodiments, in response to detecting the second input, the device plays back the enhanced photo, with none of the images modified, starting from an image acquired before acquiring the representative image (e.g., starting with the initial image in the sequence of images) rather than starting playback by displaying images acquired by the camera after the representative image.
In some embodiments, after modifying the representative image, without modifying the one or more images acquired by the camera after acquiring the representative image, and without modifying the one or more images acquired by the camera before acquiring the representative image: the device displays (2412) the modified representative image on the display. While displaying the modified representative image on the display, the device detects a first portion of a second input. In response to detecting the first portion of the second input, the device replaces display of the modified representative image with display of, in sequence, at least some of the one or more images acquired by the camera after acquiring the representative image. Thus, in some embodiments, in response to detecting the first portion of the second input, the one or more (unmodified) images acquired by the camera after acquiring the representative image are sequentially displayed. In some embodiments, the device displays a cross fade animation between the modified representative image and the one or more (unmodified) images acquired by the camera after acquiring the representative image (e.g., as shown in
After detecting the first portion of the second input, the device detects a second portion of the second input (e.g., continues to detect contact and/or intensity in a finger gesture). In response to detecting the second portion of the second input, the device displays, in sequence, at least some of the one or more images acquired by the camera before acquiring the representative image, the modified representative image, and at least some of the one or more images acquired by the camera after acquiring the representative image (e.g., as shown in
Thus, in some embodiments, in response to detecting the second portion of the second input, the entire sequence of images is played, from the initial image to the final image in the sequence, with just the representative image being modified. For example, the representative image is modified by changing it to a black and white image, while the other images in the sequence remain color images. While the black and white representative image is displayed, a first portion of an input (e.g., a press-and-hold gesture or a deep press gesture) is detected. In response, the display of the black and white representative image is replaced by the display of, in sequence, one or more (unmodified) color images in the sequence of images, which were acquired by the camera after acquiring the representative image. In response to detecting a second portion of the second input, the entire sequence of images is played, from the initial image to the final image in the sequence, with all the images displayed in color except the representative image, which is displayed in black and white.
In some embodiments, after modifying the representative image, without modifying the one or more images acquired by the camera after acquiring the representative image, and without modifying the one or more images acquired by the camera before acquiring the representative image: the device displays (2414) the modified representative image on the display. While displaying the modified representative image on the display, the device detects a second input. In response to detecting the second input, the device displays, in sequence, at least some of the one or more images acquired by the camera before acquiring the representative image, the modified representative image, and at least some of the one or more images acquired by the camera after acquiring the representative image.
Thus, in some embodiments, in response to detecting the second input, the device plays back the enhanced photo, with only the representative image modified, starting from an image acquired before acquiring the representative image (e.g., starting with the initial image in the sequence of images) rather than starting playback by displaying images acquired by the camera after the representative image.
In some embodiments, after modifying the representative image, without modifying the one or more images acquired by the camera after acquiring the representative image, and without modifying the one or more images acquired by the camera before acquiring the representative image: the device displays (2416) the modified representative image on the display. While displaying the modified representative image on the display, the device detects a first portion of a second input. In response to detecting the first portion of the second input, the device replaces display of the modified representative image with display of, in sequence, at least some of the one or more images acquired by the camera after acquiring the representative image. Thus, in some embodiments, in response to detecting the first portion of the second input, the one or more (unmodified) images acquired by the camera after acquiring the representative image are sequentially displayed. In some embodiments, the device displays a cross fade animation between the modified representative image and the one or more (unmodified) images acquired by the camera after acquiring the representative image (e.g., as shown in
After detecting the first portion of the second input, the device detects a second portion of the second input (e.g., continues to detect contact and/or intensity in a finger gesture). In response to detecting the second portion of the second input, the device displays, in sequence, at least some of the one or more images acquired by the camera before acquiring the representative image and at least some of the one or more images acquired by the camera after acquiring the representative image (e.g., as shown in
Thus, in some embodiments, in response to detecting the second portion of the second input, the entire sequence of images is played, from the initial image to the final image in the sequence, except the representative image is not displayed (e.g., the modified representative image is omitted from the first full playback of the enhanced photo). In some embodiments, the device continues to loop through the sequence of images as long as the input is maintained (e.g., a press-and-hold gesture and/or a deep press with an intensity above a predefined threshold).
In some embodiments, after modifying the representative image, without modifying the one or more images acquired by the camera after acquiring the representative image, and without modifying the one or more images acquired by the camera before acquiring the representative image: the device displays (2418) the modified representative image on the display. While displaying the modified representative image on the display, the device detects a second input. In response to detecting the second input, the device displays, in sequence, at least some of the one or more images acquired by the camera before acquiring the representative image and at least some of the one or more images acquired by the camera after acquiring the representative image.
Thus, in some embodiments, in response to detecting the second input, the device plays back the enhanced photo, with the representative image omitted and the remaining images unmodified, starting from an image acquired before acquiring the representative image (e.g., starting with the initial image in the sequence of images) rather than starting playback by displaying images acquired by the camera after the representative image.
In some embodiments, after modifying the representative image, the one or more images acquired by the camera after acquiring the representative image, and the one or more images acquired by the camera before acquiring the representative image: the device displays (2420) the modified representative image on the display. While displaying the modified representative image on the display, the device detects a first portion of a second input. In response to detecting the first portion of the second input, the device replaces display of the modified representative image with display of, in sequence, at least some of the modified one or more images acquired by the camera after acquiring the representative image. Thus, in some embodiments, in response to detecting the first portion of the second input, the modified one or more images acquired by the camera after acquiring the representative image are sequentially displayed (e.g., as shown in
After detecting the first portion of the second input, the device detects a second portion of the second input (e.g., continues to detect contact and/or intensity in a finger gesture). In response to detecting the second portion of the second input, the device displays, in sequence, at least some of the modified one or more images acquired by the camera before acquiring the representative image, the modified representative image, and at least some of the modified one or more images acquired by the camera after acquiring the representative image (e.g., as shown in
Thus, in some embodiments, in response to detecting the second portion of the second input, the entire sequence of modified images is played, from the initial image to the final image in the sequence. For example, the images in the sequence are modified by changing them from color to black and white images. While the black and white representative image is displayed, a first portion of an input (e.g., a press-and-hold gesture or a deep press gesture) is detected. In response, the display of the black and white representative image is replaced by the display of, in sequence, one or more black and white images in the sequence of images, which were acquired by the camera after acquiring the representative image. In response to detecting a second portion of the second input, the entire sequence of images is played, from the initial image to the final image in the sequence, with all the images displayed in black and white.
In some embodiments, after modifying the representative image, the one or more images acquired by the camera after acquiring the representative image, and the one or more images acquired by the camera before acquiring the representative image: the device displays (2422) the modified representative image on the display. While displaying the modified representative image on the display, the device detects a second input. In response to detecting the second input, the device displays, in sequence, at least some of the modified one or more images acquired by the camera before acquiring the representative image, the modified representative image, and at least some of the modified one or more images acquired by the camera after acquiring the representative image.
Thus, in some embodiments, in response to detecting the second input, the device plays back the enhanced photo, with all of the images modified, starting from an image acquired before acquiring the representative image (e.g., starting with the initial image in the sequence of images) rather than starting playback by displaying images acquired by the camera after the representative image.
In some embodiments, the device detects (2424) a second input corresponding to a request to delete the one or more images acquired by the camera before acquiring the representative image and the one or more images acquired by the camera after acquiring the representative image. In response to detecting the second input, the device deletes (or marks for deletion) the one or more images acquired by the camera before acquiring the representative image and the one or more images acquired by the camera after acquiring the representative image (e.g., deletes all of the additional images in the enhanced photo, other than the representative image, without additional user input beyond the second input).
It should be understood that the particular order in which the operations in
In accordance with some embodiments, method 2500 allows a user to share her enhanced photos with other users' devices when the other users' devices are configured to interact (e.g., compatible) with enhanced photos. To that end, method 2500 includes determining if a remote electronic device is configured to interact with enhanced photos and, when the remote electronic device is configured to interact with enhanced photos, method 2500 includes responding to a request to send an enhanced photo by displaying a first set of sharing options (e.g., that includes an option to send the enhanced photo). When the remote electronic device is not configured to interact with enhanced photos, method 2500 includes responding to a request to send an enhanced photo by displaying a second set of sharing options (e.g., that includes sending just a representative image or converting the enhanced photo to a video or GIF format).
The first electronic device displays (2502), on a display, a representative image in a user interface of an application that is configured to communicate with other electronic devices. For example, the representative image is displayed in an input area for a messaging application (e.g., iMessage from Apple Inc. of Cupertino, California), a social networking application (e.g., Twitter or Facebook), an ad hoc network service (e.g., AirDrop from Apple Inc. of Cupertino, California), or an email application (e.g., Mail from Apple Inc. of Cupertino, California).
The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. In some embodiments, the camera that took the sequence of images is part of the first electronic device. In some embodiments, the sequence of images was taken by a camera that is not part of the first electronic device (e.g., the sequence of images was transferred to the first electronic device after being taken with a camera on another device). In some embodiments, the sequence of images was obtained in response to detecting activation of a shutter button at a first time, as described herein with respect to
In some embodiments, the application that is configured to communicate with other electronic devices is displayed (2504) in response to detecting selection of an application icon that corresponds to the application in a sharing user interface (e.g., a sharing menu such as a share sheet in iOS by Apple Inc. of Cupertino, California). In some embodiments, the representative image is displayed in the sharing user interface and the sharing user interface is configured to display interactions with the sequence of images as a group (such as those interactions described with reference to
While displaying the representative image on the display, the first electronic device detects (2506) an input that corresponds to a request to send the representative image or a request to select the representative image for sending (e.g., detecting activation of a “send” icon or a “select photo” icon by a tap gesture on a touch-sensitive surface of the first electronic device or a mouse click) to a second electronic device, remote from the first electronic device, using the application.
In response to detecting the input that corresponds to the request to send the representative image or to the request to select the representative image for sending to the second electronic device: in accordance with a determination that the second electronic device is configured to interact with the sequence of images as a group (e.g., the second electronic device is configured to perform the interactions described with reference to
In some embodiments, the determination that the second electronic device is not configured to interact with the sequence of images as a group includes instances where it cannot be determined that the second electronic device is configured to interact with the sequence of images as a group. In some embodiments, if it cannot be determined that the second electronic device is configured to interact with the sequence of images as a group, it is concluded that the second electronic device is not configured to interact with the sequence of images as a group.
In some embodiments, the determination that the second electronic device is configured to interact with the sequence of images as a group is based at least in part on determining the operating system being used by the second electronic device. In some embodiments, as an alternative to presenting the first set of options, in accordance with a determination that the second electronic device is configured to interact with the sequence of images as a group, the first electronic device automatically sends the sequence of images (e.g., sends the entire sequence of images, to be interacted with as a group, without further user intervention after the user presses the “send” button). In some embodiments, in accordance with a determination that the second electronic device is not configured to interact with the sequence of images as a group, the first electronic device automatically sends the representative image without sending the one or more images acquired by the camera after acquiring the representative image and without sending the one or more images acquired by the camera before acquiring the representative image.
In some embodiments, the first set of options for sending at least a portion of the sequence of images to the second electronic device includes (2510) an option to send the entire sequence of images (e.g., the first set of options includes an option for sending the sequence of images as an enhanced photo).
In some embodiments, the second set of options for sending at least a portion of the sequence of images to the second electronic device includes (2512) an option for converting at least the portion of the sequence of images to a video format (e.g., an MPEG format). In some embodiments, the second set of options for sending at least a portion of the sequence of images to the second electronic device includes an option for converting at least the portion of the sequence of images to a format with which the second electronic device is configured to interact. In some embodiments, the second set of options for sending at least a portion of the sequence of images to the second electronic device includes an option for converting at least the portion of the sequence of images to an animated image format (e.g., a GIF format).
In some embodiments, if the second electronic device is not configured to interact with the sequence of images as a group, instead of sending the representative image without sending other images in the sequence of images, the first electronic device displays a menu (e.g., a pop-up menu) that gives a user the option to convert the sequence of images (and, in some embodiments, audio that corresponds to the sequence of images) into a video clip and/or animated GIF. In response to user selection of a “convert to video” and/or “send as video” option, a video that corresponds to the sequence of images is sent to the second electronic device. In some embodiments, in response to user selection of a “convert to video” and/or “send as video” option, the first electronic device converts the sequence of images into a video and sends the video to the second electronic device. In response to user selection of a “convert to GIF” and/or “send as GIF” option, an animated GIF that corresponds to the sequence of images is sent to the second electronic device. In some embodiments, in response to user selection of a “convert to GIF” and/or “send as GIF” option, the first electronic device converts the sequence of images into an animated GIF and sends the GIF to the second electronic device.
In some embodiments, the first set of options for sending at least a portion of the sequence of images to the second electronic device includes (2514) an option for converting at least the portion of the sequence of images to a video format (e.g., an MPEG format). In some embodiments, the first electronic device displays a menu (e.g., a send options menu) that gives a user the option to convert the sequence of images (and, in some embodiments, audio that corresponds to the sequence of images) into a video clip and/or animated GIF, independent of whether the second electronic device is configured to interact with the sequence of images as a group. Thus, if such an option is selected, a video or animated GIF is sent to the second electronic device, instead of the sequence of images (with or without associated audio and/or metadata), even if the second electronic device is configured to interact with the sequence of images as a group.
In some embodiments, the first electronic device displays a menu (e.g., an export, “send as” or “convert to” menu) that gives a user the option to convert the sequence of images (and, in some embodiments, audio that corresponds to the sequence of images) into a video clip and/or animated GIF. If such an option is selected, the sequence of images (with or without associated audio and/or metadata) is converted to a video or animated GIF in accordance with the option selected.
In some embodiments, in accordance with the determination that the second electronic device is configured to interact with the sequence of images as a group (e.g., the second electronic device is configured to perform the interactions described with respect to
In some embodiments, in accordance with the determination that the second electronic device is configured to interact with the sequence of images as a group (e.g., second electronic device is configured to perform the interactions described with respect to
In some embodiments, the second set of options for sending at least a portion of the sequence of images to the second electronic device includes (2520) an option for sending the representative image without sending the one or more images acquired by the camera after acquiring the representative image and without sending the one or more images acquired by the camera before acquiring the representative image (e.g., sending the representative image as a still image).
In some embodiments, the first electronic device determines (2522) whether the first electronic device is in a first mode that permits sending the sequence of images (e.g., as a group). In accordance with a determination that the first electronic device is not in the first mode that permits sending the sequence of images as a group, the first electronic device modifies the first set of options for sending at least the portion of the sequence of images to the second electronic device. In some embodiments, to send the sequence of images instead of just sending the representative image, in addition to determining that the second electronic device is configured to interact with the sequence of images as a group, the first electronic device also needs to be in a mode that permits sending the sequence of images as a group, rather than in a mode that only permits sending a still image (e.g., the representative image) from the sequence of images. In some embodiments, a user can choose between these two modes using an affordance, such as toggle switch 2006, as shown in
In some embodiments, while displaying the representative image on the display (and one of the set of options), the first electronic device detects (2524) a second input. In response to detecting the second input, the first electronic device replaces display of the representative image with display of, in sequence, at least some of the images in the sequence of images. In some embodiments, the first electronic device is configured to play back the enhanced photo while displaying the sharing options, which may help the user decide how she wants to share the photo (e.g., as an enhanced photo, video, GIF, or still image).
In some embodiments, the first electronic device includes (2526) a touch-sensitive surface and one or more sensors to detect intensity of contacts with the touch-sensitive surface. The second input includes a finger contact that satisfies first contact-intensity criteria. For example, when the set of options is displayed, a deep press over the representative image plays back the enhanced photo.
It should be understood that the particular order in which the operations in
In accordance with some embodiments, the device performs scene recognition while capturing images from the camera. In response to a user activating a shutter, the device determines, based on the scene recognition, whether to retain a sequence of images (e.g., as an enhanced photo) or retain a still image. For example, when the scene includes a lot of movement, the device automatically retains an enhanced photo. As another example, when the scene includes a large amount of text (e.g., the “scene” is merely a receipt or a page from a book), the device retains a still image.
To that end, while in a first media acquisition mode for the camera (e.g., a mode labeled as an auto still/enhanced photo mode): the device displays (2602) a live preview of a scene on the display.
The device performs (2604) scene recognition on the scene. In some embodiments, performing scene recognition includes recognizing faces in the scene, recognizing motion in the scene, recognizing text in the scene, recognizing whether the scene is indoors or outdoors (e.g., recognizing a threshold amount of brightness and/or recognizing the sun), and/or recognizing a depth of field of the scene (e.g., determining if the scene is of a landscape).
While displaying the live preview of the scene, the device detects (2606) a single activation of a shutter button at a first time. In some embodiments, detecting a single activation of a shutter button at a first time includes detecting pressing of a physical button at the first time or detecting a gesture on a virtual shutter button on a touch-sensitive display at the first time, such as a tap gesture on a shutter release icon or a tap gesture on the live preview, where the live preview acts as a virtual shutter button). In some embodiments, the detected activation is a single activation of the shutter button (e.g., analogous to a single activation used in a conventional digital camera to capture a single image in the still image mode of a conventional digital camera). In some embodiments, the single activation of the shutter button does not require that the activation be maintained for any particular amount of time (e.g., any detectable activation of the shutter button will suffice, regardless of the length that the activation is maintained).
In response to detecting (2608) the single activation of the shutter button at the first time: in accordance with a determination that the scene meets action capture criteria (e.g., criteria concerning activity in a scene), based at least in part on the scene recognition performed on the scene, the device retains a plurality of images acquired by the camera in temporal proximity to the activation of the shutter button at the first time and groups the plurality of images into a first sequence of images (e.g., the device retains an enhanced photo of the scene, as shown in
The first sequence of images includes: a plurality of images acquired by the camera prior to detecting activation of the shutter button at the first time; a representative image that represents the first sequence of images and was acquired by the camera after one or more of the other images in the first sequence of images; and a plurality of images acquired by the camera after acquiring the representative image.
In accordance with a determination that the scene does not meet the action capture criteria, the device retains a single image in temporal proximity to the activation of the shutter button at the first time (without grouping a plurality of images acquired by the camera in temporal proximity to the activation of the shutter button at the first time into a first sequence of images, as shown in
In some embodiments, the images acquired prior to detecting activation of the shutter button at the first time are a predefined number of images, such as 5, 10, 15, 20, 25, or 30 images. In some embodiments, the images acquired prior to detecting activation of the shutter button at the first time are images that are within a predefined time prior to the first time, such as within 0.5, 1.0, 1.5, 2.0, or 2.5 seconds prior to the first time. In some embodiments, the plurality of images acquired prior to detecting activation of the shutter button at the first time are from a range of time between a second time (prior to the first time) and the first time, and the plurality of images acquired prior to detecting activation of the shutter button at the first time are independent of interaction with the shutter button that is temporally proximate to the second time. For example, the plurality of images acquired prior to detecting activation of the shutter button at the first time are not acquired in response to detecting an interaction with the shutter button that is temporally proximate to the second time. For example, the plurality of images acquired prior to detecting activation of the shutter button at the first time are not acquired in response to detecting a partial (or complete) activation of the shutter button at or near the second time.
In some embodiments, the device begins acquiring and storing images upon entering the first media acquisition mode.
In some embodiments, the plurality of images, in the first sequence of images, that are acquired prior to detecting activation of the shutter button at the first time meet predefined grouping criteria. In some embodiments, the predefined grouping criteria include selecting a predefined number of images prior to the representative image. In some embodiments, the predefined grouping criteria include selecting images in a predefined range of time immediately prior to detecting activation of the shutter button. In some embodiments, the predefined grouping criteria include selecting images in a predefined range of time immediately prior to the time at which the representative image is acquired. In some embodiments, the predefined grouping criteria include selecting images based on scene recognition and/or movement of the device (e.g., the device discards images that were obtained when the device was moving too much, so as to discard, for example, images taken as the user lifted the device up).
In some embodiments, the representative image is acquired by the camera at the first time and is analogous to the single image captured in the still image mode of a conventional digital camera when its shutter button is activated. In some embodiments, the representative image acquired by the camera corresponds to an image that was acquired at the first time. In some embodiments, the representative image acquired by the camera corresponds to an image that was acquired shortly after detecting activation of the shutter button at the first time, at a time that takes into account shutter lag (the time delay between detecting activation of the shutter button and capturing/storing the representative image). In some embodiments, the representative image acquired by the camera is used to represent the sequence of images, for example in an image presentation mode.
In some embodiments, the first sequence of images includes a predefined number of images—such as 5, 10, 15, 20, 25, or 30 images—acquired after acquiring the representative image. In some embodiments, the images acquired after acquiring the representative image are images that are within a predefined time after acquiring the representative image, such as within 0.5, 1.0, 1.5, 2.0, or 2.5 seconds after acquiring the representative image. In some embodiments, the first sequence of images includes a predefined number of images—such as 5, 10, 15, 20, 25, or 30 images—acquired after detecting activation of the shutter button at the first time. In some embodiments, the images acquired after detecting activation of the shutter button at the first time are images that are within a predefined time after the first time, such as within 0.5, 1.0, 1.5, 2.0, or 2.5 seconds after the first time. In some embodiments, the plurality of images, in the first sequence of images, that are acquired after acquiring the representative image meet predefined grouping criteria. In some embodiments, the predefined grouping criteria include selecting a predefined number of images after the representative image. In some embodiments, the predefined grouping criteria include selecting images in a predefined range of time immediately after detecting activation of the shutter button. In some embodiments, the predefined grouping criteria include selecting images in a predefined range of time immediately after the time at which the representative image is acquired. In some embodiments, the predefined grouping criteria include selecting images based on scene recognition and/or movement of the device.
In some embodiments, the action capture criteria include (2610) recognizing one or more faces in the scene. In some embodiments, when the device recognizes at least one face in the scene, the device retains and groups the plurality of images.
In some embodiments, the device includes (2612) default image capture parameters for acquiring images. The device determines (2614) that the scene contains a single face in portrait orientation, the single face occupying more than a predetermined amount of the display. In response to determining that the scene contains the single face in portrait orientation, the single face occupying more than a predetermined amount of the display: the device acquires (2616) (and/or retains) the plurality of images with image capture parameters that are distinct from the default image capture parameters (e.g., higher frame rate to capture small changes in expression, higher resolution to better capture detail, etc.).
In some embodiments, the action capture criteria include (2618) recognizing motion in the scene (e.g., detecting motion (e.g., in the live preview) above a predetermined threshold value). In some embodiments, when the device recognizes at least a predefined threshold amount of motion in the scene, the device retains and groups the plurality of images.
In some embodiments, performing scene recognition on the scene includes (2620) determining an amount of motion in the scene. Retaining the plurality of images acquired by the camera in temporal proximity to the activation of the shutter button at the first time includes: in accordance with a determination that the amount of motion is a first amount, retaining the plurality of images at a first frame rate; and in accordance with a determination that the amount of motion is a second amount that is greater than the first amount, retaining images at a second frame rate that is higher than the first frame rate.
In some circumstances, the electronic device itself is moving (e.g., panning, and/or translating). In some embodiments, the action capture criteria include (2622) detecting movement of the electronic device above a predetermined threshold value. In some embodiments, certain properties of the movement of the device indicate that the device is being aimed at a moving scene (e.g., the device is panned while remaining substantially level). When the device determines that the device is being aimed, the device retains and groups the plurality of images. For example, in some circumstances, the device is panned to track a subject (e.g., an athlete playing a sport, a car passing by, etc.). In some embodiments, detecting the movement of the electronic device includes detecting acceleration of the device using accelerometers 168 (
In some embodiments, the number of images in the retained plurality of images depends (2624) on detected movement of the device while the plurality of images was acquired. For example, the device recognizes when it is being translated (e.g., attached to a helmet of a mountain biker or skier). When the device is being translated faster (e.g., as indicated by vibrations and or quick changes in acceleration), the device retains and groups the plurality of images at a higher frame rate, and/or for a longer period of time, resulting in a greater number of images retained in the plurality of images.
In some embodiments, performing scene recognition includes recognizing a landscape with activity (e.g., a waterfall, a windmill, trees with leaves blowing in the wind). When the device recognizes that the device is capturing a landscape with activity, the device retains and groups the plurality of images (e.g., as an enhanced photo). In some embodiments, enhanced photos of landscapes playback in a loop so that the landscape scene appears continuous.
Conversely, the device acquires a single image in response to detecting the single activation of the shutter button at the first time (without grouping a plurality of images acquired by the camera in temporal proximity to the activation of the shutter button at the first time into a first sequence of images), in accordance with a determination that no faces are present in the scene, there is no significant movement in the scene, and/or the electronic device itself is not moving (e.g., the device is stationary). In some embodiments, the single image is a still image that merges a plurality of still images, such as a high dynamic range (HDR) still image.
In some embodiments, certain properties of the movement of the device indicate that the device is not being aimed (e.g., is being taken out of the user's pocket and/or is being lifted up to aim at the scene). When the device determines that it is moving without being aimed, the device retains a single image.
In some embodiments, performing scene recognition on the scene includes (2626) recognizing text. The action capture criteria include a criterion that is met when an amount of text in the scene is below a predefined threshold. In some embodiments, the device recognizes when the picture is of a receipt or document. When the picture is of a receipt or document, the device captures a still image rather than an enhanced photo.
It should be understood that the particular order in which the operations in
In accordance with some embodiments, the device provides a user interface for trimming a sequence of image to a subset of the sequence of images (e.g., modifying the beginning and ending image in the sequence of images). When a user requests to trim an enhanced photo, the device provides movable handles that the user can use to modify the beginning and ending images in the sequence of images. The initial location of the handles (e.g., when the user first enters the user interface for trimming the sequence of images) are automatically provided by the device (e.g., based on scene detection). In some embodiments, the user can toggle the locations of the handles between the automatically suggested beginning and ending images and the initial and final images in the sequence of images. As used herein, the terms “initial image” and “final image” refer to the first and last images in the (original) sequence of images, whereas “beginning image” and “ending image” refer to the first and last images in the subset of the sequence of images.
To that end, the device displays (2702) an image on a display (e.g., while the device is in an image editing mode).
The image is one image in a sequence of images taken by a camera. The sequence of images includes a representative image. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. In some embodiments, the camera that took the sequence of images is part of the electronic device. In some embodiments, the sequence of images was taken by a camera that is not part of the electronic device (e.g., the sequence of images was transferred to the electronic device after being taken with a camera on another device). In some embodiments, the sequence of images was obtained in response to detecting activation of a shutter button at a first time, as described herein with respect to
In some embodiments, while displaying the image, the device displays a visual indication that the image is a respective image in a sequence of images (e.g., the device displays an indication that the image is from an enhanced photo). In some embodiments, the visual indication that the image is a respective image in a sequence of images is an affordance (e.g., selectable affordance 2304,
In some embodiments, the displayed image is (2704) the representative image from the sequence of images.
In some embodiments, the displayed image is (2706) a currently selected image from the sequence of images. In some embodiments, the currently selected image is visually distinguished from the other images in the sequence of images. In some embodiments, the currently selected image is concurrently displayed in the second area (described below) with a representation (e.g., a thumbnail) of the currently selected image in the area that contains representations of images in the sequence of images. In some embodiments, selection of a given image replaces the representative image with the given image as a new representative image. In some embodiments, the user can select a new representative image for the sequence of images by tapping on a thumbnail of a given image in the sequence of images to select a new representative image.
While displaying the image in the sequence of images on the display, the device detects (2708) a first input (e.g., detects an input that corresponds to a request to display a user interface for trimming the sequence of images, such as a tap gesture on trim icon 2310-3 in
In response to detecting the first input: the device displays (2710) a user interface for trimming the sequence of images to a subset, less than all, of the sequence of images. In some embodiments, the user interface is part of a trimming mode.
The user interface includes: an area (e.g., a strip, such as strip 2316,
The begin-trim icon is located at a first position, in the area that contains representations of images in the sequence of images, that is automatically selected by the device. The end-trim icon is located at a second position, in the area that contains representations of images in the sequence of images, that is automatically selected by the device. In some embodiments, the beginning image for the subset that is automatically selected by the device (which is shown by the first position of the begin-trim icon) is not the initial image in the sequence of images. In some embodiments, the beginning image for the subset is a later image in the sequence of images than the initial image. In some embodiments, the ending image for the subset that is automatically selected by the device (which is shown by the second position of the end-trim icon) is not the final image in the sequence of images. In some embodiments, the ending image for the subset is an earlier image in the sequence of images than the final image.
In some embodiments, representations of images between the begin-trim icon and the end-trim icon are (2712) visually distinguished from the other representations in the area that contains representations of images in the sequence of images. In some embodiments, both the sequence of images and the subset of the sequence of images include an uninterrupted consecutive set of images acquired by the camera.
In some embodiments, the user interface for trimming the sequence of images includes (2714) a second area that displays the image in the sequence of images. The second area is displayed concurrently with the area that contains representations of images in the sequence of images. In some embodiments, the second region occupies more than half of the display, more than 80% of the display, or more than 90% of the display. In some embodiments, the second region of the display occupies the entire region of the display save optional menu bars at the top and bottom of the display and the area that contains representations of images in the sequence of images.
In some embodiments, automatically selecting the beginning image in the subset and the corresponding first position of the begin-trim icon is (2716) based on one or more characteristics of the images in the sequence of images. Automatically selecting the ending image in the subset and the corresponding second position of the begin-trim icon is based on one or more characteristics of the images in the sequence of images. In some embodiments, the device selects/suggests the beginning image and the ending image in the subset based on scene recognition on the sequence of images.
In some embodiments, the sequence of images includes (2718) an initial image and a final image. The device displays, in the area that contains representations of images in the sequence of images, one or more representations of images, not included in the sequence of images, that were obtained before the initial image in the sequence of images and/or that were obtained after the final image in the sequence of images. In some embodiments, in addition to trimming the original sequence of images, a user is also able to add images obtained just before or just after the original sequence of images.
In some embodiments, prior to detecting the second input, while displaying the user interface for trimming the sequence of images, the device detects (2720) an input on the end-trim icon. In response to detecting the input on the end-trim icon, the device moves the end-trim icon from the second position to a third position in the area that contains representations of images in the sequence of images. In some embodiments, a user is able to manually override the ending image for the subset that was automatically recommended/selected by the device. Similarly, in some embodiments, a user is able to manually override the beginning image for the subset that was automatically recommended/selected by the device, e.g., with a drag gesture that starts on the begin-trim icon and moves the begin-trim icon from the first position to another position in the area that contains representations of images in the sequence of images.
While displaying the user interface for trimming the sequence of images, the device detects (2722) a second input (e.g., detects activation of done icon 2301,
In response to detecting a second input, the device trims (2724) the sequence of images to the subset of the sequence of images in accordance with a current position of the begin-trim icon and a current position of the end-trim icon. In some embodiments, trimming the sequence of images to the subset of the sequence of images includes storing data indicating a position of the beginning image in the subset and the ending image in the subset.
In some embodiments, the device deletes (2726) images, from the sequence of images, which are not included in the subset of the sequence of images. In some embodiments, the device edits the sequence of images to include only those images in the subset (which were automatically selected/suggested by the device and confirmed by the user, or which were manually selected by the user). In some embodiments, the device continues to store the images that are not in the subset, e.g., so that the user can further modify the sequence of images at a later time with all of the original images in the sequence of images available (e.g., as obtained by the camera).
In some embodiments, the sequence of images includes (2728) an initial image and a final image, and the user interface includes a reset affordance (e.g., reset button 2324,
In some embodiments, in response to detecting the input on the reset affordance: the device displays (2730) an automatic selection affordance (e.g., “auto” icon 2332,
In some embodiments, in response to detecting a third input, the device selects (2732) a new representative image for the subset of the sequence of images (e.g., an image at the middle of the subset or an image selected based on scene recognition performed on the subset of the sequence of images).
In some embodiments, after trimming the sequence of images to the subset of the sequence of images in accordance with the current position of the begin-trim icon and the current position of the end-trim icon, the device displays (2734) a representative image of the subset of the sequence of images on the display (e.g., while the device is in an image presentation mode). In some embodiments, the representative image of the subset of the sequence of images is the same as the representative image of the sequence of images. In some embodiments, the representative image of the subset of the sequence of images is different from the representative image of the sequence of images. In some embodiments, the representative image of the subset is displayed in response to an input that corresponds to a request to exit the editing mode. While displaying the representative image on the display, the device detects a third input (e.g., an input that corresponds to a request to playback the subset of the sequence of images, such as a press-and-hold gesture or a gesture that meets contact intensity criteria for playback). In response to detecting the third input, the device replaces display of the representative image with an animated playback of the subset of the sequence of images. In some embodiments, the subset of the sequence of images is played back in an analogous manner to playback of the sequence of images, as described herein with respect to
In some embodiments, in response to detecting a fourth input, the device disables (2736) the animated playback of the subset of the sequence of images while retaining the subset of images.
In some embodiments, in response to detecting a third input that corresponds to a request to edit the representative image, the device provides (2738) a user of the device with options to: continue editing the representative image with the animated playback of the subset of the sequence of images disabled; and cancel editing the representative image.
In some embodiments, the device presents (2740) an affordance for deleting images in the sequence of images other than the representative image. In response to detecting a third input, the device deletes the one or more images acquired by the camera after acquiring the representative image and the one or more images acquired by the camera before acquiring the representative image.
It should be understood that the particular order in which the operations in
In accordance with some embodiments,
As shown in
The processing unit 2808 is configured to enable (e.g., with the display enabling unit 2810) display of a representative image on the display unit 2812. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. The processing unit 2808 is further configured to, while enabling display of the representative image on the display unit 2802, detect (e.g., with the detecting unit 2812, in conjunction with the touch-sensitive surface unit 2804) an input to modify the representative image. The processing unit 2808 is further configured to, in response to detecting the input to modify the representative image: in accordance with a determination that the device is in a first editing mode, modify (e.g., with the modifying unit 2814) the representative image, the one or more images acquired by the camera after acquiring the representative image, and the one or more images acquired by the camera before acquiring the representative image; and, in accordance with a determination that the device is in a second editing mode, distinct from the first editing mode, modify (e.g., with the modifying unit 2814) the representative image, without modifying the one or more images acquired by the camera after acquiring the representative image, and without modifying the one or more images acquired by the camera before acquiring the representative image.
In accordance with some embodiments,
As shown in
The processing unit 2908 is configured to enable (e.g., with display enabling unit 2910) display, on the display unit 2902, of a representative image in a user interface of an application that is configured to communicate with other electronic devices. The representative image is one image in a sequence of images taken by a camera. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image. The processing unit 2908 is further configured to, while enabling display of the representative image on the display unit 2902, detect (e.g., with detecting unit 2912, in conjunction with touch-sensitive surface unit 2904) an input that corresponds to a request to send the representative image or a request to select the representative image for sending to a second electronic device, remote from the electronic device, using the application. The processing unit 2908 is further configured to, in response to detecting the input that corresponds to the request to send the representative image or to the request to select the representative image for sending to the second electronic device: in accordance with a determination that the second electronic device is configured to interact with the sequence of images as a group, enable (e.g., with display enabling unit 2910) display of a first set of options for sending at least a portion of the sequence of images to the second electronic device; and, in accordance with a determination that the second electronic device is not configured to interact with the sequence of images as a group, enable (e.g., with display enabling unit 2910) display of a second set of options for sending at least a portion of the sequence of images to the second electronic device. The second set of options is different from the first set of options.
In accordance with some embodiments,
As shown in
The processing unit 3008 is configured to, while in a first media acquisition mode for the camera unit 3006: enable (e.g., with display enabling unit 3010) display of a live preview of a scene on the display unit 3002 and perform (e.g., with scene recognition performing unit 3014) scene recognition on the scene. The processing unit 3008 is further configured to, while enabling display of the live preview of the scene, detect (e.g., with detecting unit 3012, in conjunction with touch-sensitive surface unit 3004) a single activation of a shutter button at a first time. The processing unit 3008 is further configured to, in response to detecting the single activation of the shutter button at the first time: in accordance with a determination that the scene meets action capture criteria, based at least in part on the scene recognition performed on the scene, retain (e.g., with retaining unit 3016) a plurality of images acquired by the camera unit 3006 in temporal proximity to the activation of the shutter button at the first time and group (e.g., with grouping unit 3018) the plurality of images into a first sequence of images. The first sequence of images includes: a plurality of images acquired by the camera unit 3006 prior to detecting activation of the shutter button at the first time; a representative image that represents the first sequence of images and was acquired by the camera unit 3006 after one or more of the other images in the first sequence of images; and a plurality of images acquired by the camera unit 3006 after acquiring the representative image. The processing unit 3008 is further configured to, in accordance with a determination that the scene does not meet the action capture criteria, retain (e.g., with retaining unit 3016) a single image in temporal proximity to the activation of the shutter button at the first time.
In accordance with some embodiments,
As shown in
The processing unit 3108 is configured to enable display (e.g., with the display enabling unit 3110) of an image on the display unit 3102. The image is one image in a sequence of images taken by a camera. The sequence of images includes a representative image. The sequence of images includes one or more images acquired by the camera after acquiring the representative image. The sequence of images includes one or more images acquired by the camera before acquiring the representative image.
The processing unit 3108 is further configured to, while enabling display of the image in the sequence of images on the display unit 3102, detect (e.g., with detecting unit 3112) a first input. The processing unit 3108 is further configured to, in response to detecting the first input, enable display (e.g., with display enabling unit 3110) of a user interface for trimming the sequence of images to a subset, less than all, of the sequence of images. The user interface includes: an area that contains representations of images in the sequence of images; a user-adjustable begin-trim icon that delimits a beginning image in the subset of the sequence of images via a position of the begin-trim icon in the area that contains representations of images in the sequence of images; and a user-adjustable end-trim icon that delimits an ending image in the subset of the sequence of images via a position of the end-trim icon in the area that contains representations of images in the sequence of images. The begin-trim icon is located at a first position, in the area that contains representations of images in the sequence of images, that is automatically selected by the device. The end-trim icon is located at a second position, in the area that contains representations of images in the sequence of images, that is automatically selected by the device.
The processing unit 3108 is further configured to, while enabling display of the user interface for trimming the sequence of images, detect (e.g., with detecting unit 3112) a second input. The processing unit 3108 is further configured to, in response to detecting a second input, trim (e.g., with trimming unit 3114) the sequence of images to the subset of the sequence of images in accordance with a current position of the begin-trim icon and a current position of the end-trim icon.
The operations in methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to
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. For example, the methods described herein are also applicable in an analogous manner to electronic devices configured for management, playback, and/or streaming (e.g., from an external server) of audio and/or visual content that are in communication with a remote control and a display (e.g., Apple TV from Apple Inc. of Cupertino, California). For such devices, inputs are optionally received that correspond to gestures on a touch-sensitive surface of the remote control, voice inputs to the remote control, and/or activation of buttons on the remote control, rather than having the touch-sensitive surface, audio input device (e.g., a microphone), and/or buttons on the device itself. For such devices, data is optionally provided to the display rather than displayed by the device itself. 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 invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated.
This application is a continuation of U.S. application Ser. No. 17/524,692, filed Nov. 11, 2021, which is a continuation of U.S. application Ser. No. 17/003,869, filed Aug. 26, 2020, now U.S. Pat. No. 11,240,424, which is a continuation of U.S. application Ser. No. 16/534,214, filed Aug. 7, 2019, now U.S. Pat. No. 10,841,484, which is a continuation of U.S. application Ser. No. 16/252,478, filed Jan. 18, 2019, now U.S. Pat. No. 10,455,146, which is a continuation of U.S. application Ser. No. 14/864,529, filed Sep. 24, 2015, now U.S. Pat. No. 10,200,598, which is a continuation of U.S. application Ser. No. 14/863,432, filed Sep. 23, 2015, now U.S. Pat. No. 9,860,451, which claims priority to: (1) U.S. Provisional Application Ser. No. 62/215,689, filed Sep. 8, 2015, entitled “Devices and Methods for Capturing and Interacting with Enhanced Digital Images;” (2) U.S. Provisional Application Ser. No. 62/172,233, filed Jun. 8, 2015, entitled “Devices and Methods for Capturing and Interacting with Enhanced Digital Images;” and (3) U.S. Provisional Application Ser. No. 62/172,223, filed Jun. 7, 2015, entitled “Reduced Size User Interface,” all of which are incorporated by reference herein in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4864520 | Setoguchi et al. | Sep 1989 | A |
| 5184120 | Schultz | Feb 1993 | A |
| 5374787 | Miller et al. | Dec 1994 | A |
| 5428730 | Baker et al. | Jun 1995 | A |
| 5463722 | Venolia | Oct 1995 | A |
| 5510813 | Makinwa et al. | Apr 1996 | A |
| 5555354 | Strasnick et al. | Sep 1996 | A |
| 5559301 | Bryan, Jr. et al. | Sep 1996 | A |
| 5589855 | Blumstein et al. | Dec 1996 | A |
| 5664210 | Fleming et al. | Sep 1997 | A |
| 5710896 | Seidl | Jan 1998 | A |
| 5717438 | Kim et al. | Feb 1998 | A |
| 5793360 | Fleck et al. | Aug 1998 | A |
| 5793377 | Moore | Aug 1998 | A |
| 5801692 | Muzio et al. | Sep 1998 | A |
| 5805144 | Scholder et al. | Sep 1998 | A |
| 5805167 | Van Cruyningen | Sep 1998 | A |
| 5809267 | Moran et al. | Sep 1998 | A |
| 5819293 | Comer et al. | Oct 1998 | A |
| 5825352 | Bisset et al. | Oct 1998 | A |
| 5844560 | Crutcher et al. | Dec 1998 | A |
| 5870683 | Wells et al. | Feb 1999 | A |
| 5872922 | Hogan et al. | Feb 1999 | A |
| 5946647 | Miller et al. | Aug 1999 | A |
| 5956032 | Argiolas | Sep 1999 | A |
| 5973670 | Barber et al. | Oct 1999 | A |
| 6002397 | Kolawa et al. | Dec 1999 | A |
| 6031989 | Cordell | Feb 2000 | A |
| 6088019 | Rosenberg | Jul 2000 | A |
| 6088027 | Konar et al. | Jul 2000 | A |
| 6111575 | Martinez et al. | Aug 2000 | A |
| 6121960 | Carroll et al. | Sep 2000 | A |
| 6208329 | Ballare | Mar 2001 | B1 |
| 6208340 | Amin et al. | Mar 2001 | B1 |
| 6219034 | Elbing et al. | Apr 2001 | B1 |
| 6223188 | Albers et al. | Apr 2001 | B1 |
| 6232891 | Rosenberg | May 2001 | B1 |
| 6243080 | Molne | Jun 2001 | B1 |
| 6252594 | Xia et al. | Jun 2001 | B1 |
| 6292233 | Erba et al. | Sep 2001 | B1 |
| 6300936 | Braun et al. | Oct 2001 | B1 |
| 6313836 | Russell, Jr. et al. | Nov 2001 | B1 |
| 6396523 | Segal et al. | May 2002 | B1 |
| 6429846 | Rosenberg et al. | Aug 2002 | B2 |
| 6448977 | Braun et al. | Sep 2002 | B1 |
| 6459442 | Edwards et al. | Oct 2002 | B1 |
| 6489978 | Gong et al. | Dec 2002 | B1 |
| 6512530 | Rzepkowski et al. | Jan 2003 | B1 |
| 6563487 | Martin et al. | May 2003 | B2 |
| 6567102 | Kung | May 2003 | B2 |
| 6583798 | Hoek et al. | Jun 2003 | B1 |
| 6590568 | Astala et al. | Jul 2003 | B1 |
| 6661438 | Shiraishi et al. | Dec 2003 | B1 |
| 6734882 | Becker | May 2004 | B1 |
| 6735307 | Volckers | May 2004 | B1 |
| 6750890 | Sugimoto | Jun 2004 | B1 |
| 6806893 | Kolawa et al. | Oct 2004 | B1 |
| 6822635 | Shahoian et al. | Nov 2004 | B2 |
| 6906697 | Rosenberg | Jun 2005 | B2 |
| 6919927 | Hyodo | Jul 2005 | B1 |
| 6943778 | Astala et al. | Sep 2005 | B1 |
| 7036088 | Tunney | Apr 2006 | B2 |
| 7138983 | Wakai et al. | Nov 2006 | B2 |
| 7312791 | Hoshino et al. | Dec 2007 | B2 |
| 7411575 | Hill et al. | Aug 2008 | B2 |
| 7434177 | Ording et al. | Oct 2008 | B1 |
| 7453439 | Kushler et al. | Nov 2008 | B1 |
| 7471284 | Bathiche et al. | Dec 2008 | B2 |
| 7479949 | Jobs et al. | Jan 2009 | B2 |
| 7500127 | Fleck et al. | Mar 2009 | B2 |
| 7516404 | Colby et al. | Apr 2009 | B1 |
| 7533352 | Chew et al. | May 2009 | B2 |
| 7552397 | Holecek et al. | Jun 2009 | B2 |
| 7577530 | Vignalou-Marche | Aug 2009 | B2 |
| 7614008 | Ording | Nov 2009 | B2 |
| 7619616 | Rimas Ribikauskas et al. | Nov 2009 | B2 |
| 7629966 | Anson | Dec 2009 | B2 |
| 7656413 | Khan et al. | Feb 2010 | B2 |
| 7683889 | Rimas Ribikauskas et al. | Mar 2010 | B2 |
| 7702733 | Fleck et al. | Apr 2010 | B2 |
| 7743348 | Robbins et al. | Jun 2010 | B2 |
| 7760187 | Kennedy | Jul 2010 | B2 |
| 7787026 | Flory et al. | Aug 2010 | B1 |
| 7797642 | Karam et al. | Sep 2010 | B1 |
| 7801950 | Eisenstadt et al. | Sep 2010 | B2 |
| 7812826 | Ording et al. | Oct 2010 | B2 |
| 7890862 | Kompe et al. | Feb 2011 | B2 |
| 7903090 | Soss et al. | Mar 2011 | B2 |
| 7952566 | Poupyrev et al. | May 2011 | B2 |
| 7956847 | Christie | Jun 2011 | B2 |
| 7973778 | Chen | Jul 2011 | B2 |
| 8000694 | Labidi et al. | Aug 2011 | B2 |
| 8040142 | Bokma et al. | Oct 2011 | B1 |
| 8059104 | Shahoian et al. | Nov 2011 | B2 |
| 8059105 | Rosenberg et al. | Nov 2011 | B2 |
| 8106856 | Matas et al. | Jan 2012 | B2 |
| 8125440 | Guyot-Sionnest et al. | Feb 2012 | B2 |
| 8125492 | Wainwright et al. | Feb 2012 | B1 |
| RE43448 | Kimoto et al. | Jun 2012 | E |
| 8209628 | Davidson | Jun 2012 | B1 |
| 8271900 | Walizaka et al. | Sep 2012 | B2 |
| 8300005 | Tateuchi et al. | Oct 2012 | B2 |
| 8311514 | Bandyopadhyay et al. | Nov 2012 | B2 |
| 8325398 | Satomi et al. | Dec 2012 | B2 |
| 8363020 | Li et al. | Jan 2013 | B2 |
| 8390583 | Forutanpour et al. | Mar 2013 | B2 |
| 8423089 | Song et al. | Apr 2013 | B2 |
| 8446376 | Levy et al. | May 2013 | B2 |
| 8446382 | Goto et al. | May 2013 | B2 |
| 8453057 | Stallings et al. | May 2013 | B2 |
| 8456431 | Victor | Jun 2013 | B2 |
| 8466889 | Tong et al. | Jun 2013 | B2 |
| 8482535 | Pryor | Jul 2013 | B2 |
| 8499243 | Yuki | Jul 2013 | B2 |
| 8504946 | Williamson et al. | Aug 2013 | B2 |
| 8508494 | Moore | Aug 2013 | B2 |
| 8542205 | Keller | Sep 2013 | B1 |
| 8553092 | Tezuka et al. | Oct 2013 | B2 |
| 8570296 | Birnbaum et al. | Oct 2013 | B2 |
| 8581870 | Bokma et al. | Nov 2013 | B2 |
| 8587542 | Moore | Nov 2013 | B2 |
| 8593415 | Han et al. | Nov 2013 | B2 |
| 8593420 | Buuck | Nov 2013 | B1 |
| 8625882 | Backlund et al. | Jan 2014 | B2 |
| 8638311 | Kang et al. | Jan 2014 | B2 |
| 8665227 | Gunawan | Mar 2014 | B2 |
| 8669945 | Coddington | Mar 2014 | B2 |
| 8698765 | Keller | Apr 2014 | B1 |
| 8706172 | Priyantha et al. | Apr 2014 | B2 |
| 8713471 | Rowley et al. | Apr 2014 | B1 |
| 8717305 | Williamson et al. | May 2014 | B2 |
| 8726198 | Rydenhag et al. | May 2014 | B2 |
| 8743069 | Morton et al. | Jun 2014 | B2 |
| 8760425 | Crisan | Jun 2014 | B2 |
| 8769431 | Prasad | Jul 2014 | B1 |
| 8773389 | Freed | Jul 2014 | B1 |
| 8788964 | Shin et al. | Jul 2014 | B2 |
| 8793577 | Schellingerhout et al. | Jul 2014 | B2 |
| 8799816 | Wells et al. | Aug 2014 | B2 |
| 8816989 | Nicholson et al. | Aug 2014 | B2 |
| 8854316 | Shenfield | Oct 2014 | B2 |
| 8872729 | Lyons et al. | Oct 2014 | B2 |
| 8872773 | Mak et al. | Oct 2014 | B2 |
| 8875044 | Ozawa | Oct 2014 | B2 |
| 8881062 | Kim et al. | Nov 2014 | B2 |
| 8914732 | Jun et al. | Dec 2014 | B2 |
| 8932412 | Ferragut, II et al. | Jan 2015 | B2 |
| 8952987 | Momeyer et al. | Feb 2015 | B2 |
| 8954889 | Fujibayashi | Feb 2015 | B2 |
| 8959430 | Spivak et al. | Feb 2015 | B1 |
| 8976128 | Moore | Mar 2015 | B2 |
| 9026932 | Dixon | May 2015 | B1 |
| 9030419 | Freed | May 2015 | B1 |
| 9030436 | Ikeda | May 2015 | B2 |
| 9032321 | Cohen et al. | May 2015 | B1 |
| 9043732 | Nurmi et al. | May 2015 | B2 |
| 9046999 | Teller et al. | Jun 2015 | B1 |
| 9052820 | Jarrett et al. | Jun 2015 | B2 |
| 9052925 | Chaudhri | Jun 2015 | B2 |
| 9063563 | Gray et al. | Jun 2015 | B1 |
| 9063731 | Heo et al. | Jun 2015 | B2 |
| 9069460 | Moore | Jun 2015 | B2 |
| 9078208 | Dutta et al. | Jul 2015 | B1 |
| 9086755 | Cho et al. | Jul 2015 | B2 |
| 9086875 | Harrat et al. | Jul 2015 | B2 |
| 9092058 | Kasahara et al. | Jul 2015 | B2 |
| 9098188 | Kim | Aug 2015 | B2 |
| 9104260 | Marsden et al. | Aug 2015 | B2 |
| 9111076 | Park et al. | Aug 2015 | B2 |
| 9116569 | Stacy et al. | Aug 2015 | B2 |
| 9116571 | Zeliff et al. | Aug 2015 | B2 |
| 9122364 | Kuwabara et al. | Sep 2015 | B2 |
| 9128605 | Nan et al. | Sep 2015 | B2 |
| 9141262 | Nan et al. | Sep 2015 | B2 |
| 9146914 | Dhaundiyal | Sep 2015 | B1 |
| 9164779 | Brakensiek et al. | Oct 2015 | B2 |
| 9170607 | Bose et al. | Oct 2015 | B2 |
| 9170649 | Ronkainen | Oct 2015 | B2 |
| 9178971 | Nemoto | Nov 2015 | B2 |
| 9218105 | Mansson et al. | Dec 2015 | B2 |
| 9244562 | Rosenberg et al. | Jan 2016 | B1 |
| 9244576 | Vadagave et al. | Jan 2016 | B1 |
| 9244601 | Kim et al. | Jan 2016 | B2 |
| 9244606 | Kocienda et al. | Jan 2016 | B2 |
| 9246487 | Casparian et al. | Jan 2016 | B2 |
| 9262002 | Momeyer et al. | Feb 2016 | B2 |
| 9280286 | Commarford et al. | Mar 2016 | B2 |
| 9304668 | Rezende et al. | Apr 2016 | B2 |
| 9307112 | Molgaard et al. | Apr 2016 | B2 |
| 9349552 | Huska et al. | May 2016 | B2 |
| 9361018 | Defazio et al. | Jun 2016 | B2 |
| 9383887 | Khafizov et al. | Jul 2016 | B1 |
| 9389718 | Letourneur | Jul 2016 | B1 |
| 9389722 | Matsuki et al. | Jul 2016 | B2 |
| 9395800 | Liu et al. | Jul 2016 | B2 |
| 9400581 | Bokma et al. | Jul 2016 | B2 |
| 9405367 | Jung et al. | Aug 2016 | B2 |
| 9405428 | Roh et al. | Aug 2016 | B2 |
| 9417754 | Smith | Aug 2016 | B2 |
| 9423938 | Morris | Aug 2016 | B1 |
| 9436344 | Kuwabara et al. | Sep 2016 | B2 |
| 9448694 | Sharma et al. | Sep 2016 | B2 |
| 9451230 | Henderson et al. | Sep 2016 | B1 |
| 9471145 | Langlois et al. | Oct 2016 | B2 |
| 9477393 | Zambetti et al. | Oct 2016 | B2 |
| 9542013 | Dearman et al. | Jan 2017 | B2 |
| 9547436 | Ohki et al. | Jan 2017 | B2 |
| 9569093 | Lipman et al. | Feb 2017 | B2 |
| 9582178 | Grant et al. | Feb 2017 | B2 |
| 9600114 | Milam et al. | Mar 2017 | B2 |
| 9600116 | Tao et al. | Mar 2017 | B2 |
| 9612741 | Brown et al. | Apr 2017 | B2 |
| 9619076 | Bernstein et al. | Apr 2017 | B2 |
| 9619113 | Mark | Apr 2017 | B2 |
| 9625987 | LaPenna et al. | Apr 2017 | B1 |
| 9645722 | Stasior et al. | May 2017 | B1 |
| 9665762 | Thompson et al. | May 2017 | B2 |
| 9671943 | Van Der Velden | Jun 2017 | B2 |
| 9678571 | Robert et al. | Jun 2017 | B1 |
| 9733716 | Shaffer | Aug 2017 | B2 |
| 9740381 | Chaudhri et al. | Aug 2017 | B1 |
| 9753527 | Connell et al. | Sep 2017 | B2 |
| 9760241 | Lewbel | Sep 2017 | B1 |
| 9785305 | Alonso Ruiz et al. | Oct 2017 | B2 |
| 9798443 | Gray | Oct 2017 | B1 |
| 9804665 | DeBates et al. | Oct 2017 | B2 |
| 9829980 | Lisseman et al. | Nov 2017 | B2 |
| 9891747 | Jang et al. | Feb 2018 | B2 |
| 10055066 | Lynn et al. | Aug 2018 | B2 |
| 10057490 | Shin | Aug 2018 | B2 |
| 10095396 | Kudershian et al. | Oct 2018 | B2 |
| 10133388 | Sudou | Nov 2018 | B2 |
| 10133397 | Smith | Nov 2018 | B1 |
| 10180722 | Lu | Jan 2019 | B2 |
| 10222980 | Alonso Ruiz et al. | Mar 2019 | B2 |
| 10235023 | Gustafsson et al. | Mar 2019 | B2 |
| 10275087 | Smith | Apr 2019 | B1 |
| 10331769 | Hill et al. | Jun 2019 | B1 |
| 10386960 | Smith | Aug 2019 | B1 |
| 10469767 | Shikata | Nov 2019 | B2 |
| 10496151 | Kim et al. | Dec 2019 | B2 |
| 10547895 | Morris | Jan 2020 | B1 |
| 10739896 | Kim et al. | Aug 2020 | B2 |
| 10771274 | Reimann et al. | Sep 2020 | B2 |
| 10782871 | Bernstein et al. | Sep 2020 | B2 |
| 20010024195 | Hayakawa et al. | Sep 2001 | A1 |
| 20010045965 | Orbanes et al. | Nov 2001 | A1 |
| 20020006822 | Krintzman | Jan 2002 | A1 |
| 20020008691 | Hanajima et al. | Jan 2002 | A1 |
| 20020015064 | Robotham et al. | Feb 2002 | A1 |
| 20020042925 | Ebisu et al. | Apr 2002 | A1 |
| 20020054011 | Bruneau et al. | May 2002 | A1 |
| 20020057256 | Flack | May 2002 | A1 |
| 20020109668 | Rosenberg et al. | Aug 2002 | A1 |
| 20020109678 | Marmolin et al. | Aug 2002 | A1 |
| 20020128036 | Yach et al. | Sep 2002 | A1 |
| 20020140680 | Lu | Oct 2002 | A1 |
| 20020140740 | Chen | Oct 2002 | A1 |
| 20020163498 | Chang et al. | Nov 2002 | A1 |
| 20020180763 | Kung | Dec 2002 | A1 |
| 20020186257 | Cadiz et al. | Dec 2002 | A1 |
| 20030001869 | Nissen | Jan 2003 | A1 |
| 20030013492 | Bokhari et al. | Jan 2003 | A1 |
| 20030058241 | Hsu | Mar 2003 | A1 |
| 20030068053 | Chu | Apr 2003 | A1 |
| 20030086496 | Zhang et al. | May 2003 | A1 |
| 20030112269 | Lentz et al. | Jun 2003 | A1 |
| 20030117440 | Hellyar et al. | Jun 2003 | A1 |
| 20030122779 | Martin et al. | Jul 2003 | A1 |
| 20030128242 | Gordon | Jul 2003 | A1 |
| 20030151589 | Bensen et al. | Aug 2003 | A1 |
| 20030184574 | Phillips et al. | Oct 2003 | A1 |
| 20030189552 | Chuang et al. | Oct 2003 | A1 |
| 20030189647 | Kang | Oct 2003 | A1 |
| 20030201914 | Fujiwara et al. | Oct 2003 | A1 |
| 20030206169 | Springer et al. | Nov 2003 | A1 |
| 20030222915 | Marion et al. | Dec 2003 | A1 |
| 20040015662 | Cummings | Jan 2004 | A1 |
| 20040021643 | Hoshino et al. | Feb 2004 | A1 |
| 20040056849 | Lohbihler et al. | Mar 2004 | A1 |
| 20040108995 | Hoshino et al. | Jun 2004 | A1 |
| 20040138849 | Schmidt et al. | Jul 2004 | A1 |
| 20040141010 | Fitzmaurice et al. | Jul 2004 | A1 |
| 20040150631 | Fleck et al. | Aug 2004 | A1 |
| 20040150644 | Kincaid et al. | Aug 2004 | A1 |
| 20040155752 | Radke | Aug 2004 | A1 |
| 20040155869 | Robinson et al. | Aug 2004 | A1 |
| 20040168131 | Blumberg | Aug 2004 | A1 |
| 20040174399 | Wu et al. | Sep 2004 | A1 |
| 20040219969 | Casey et al. | Nov 2004 | A1 |
| 20040267877 | Shiparo et al. | Dec 2004 | A1 |
| 20050012723 | Pallakoff | Jan 2005 | A1 |
| 20050039141 | Burke et al. | Feb 2005 | A1 |
| 20050064911 | Chen et al. | Mar 2005 | A1 |
| 20050066207 | Fleck et al. | Mar 2005 | A1 |
| 20050076256 | Fleck et al. | Apr 2005 | A1 |
| 20050078093 | Peterson, Jr. et al. | Apr 2005 | A1 |
| 20050091604 | Davis | Apr 2005 | A1 |
| 20050110769 | DaCosta et al. | May 2005 | A1 |
| 20050114785 | Finnigan et al. | May 2005 | A1 |
| 20050125742 | Grotjohn et al. | Jun 2005 | A1 |
| 20050134578 | Chambers et al. | Jun 2005 | A1 |
| 20050156892 | Grant | Jul 2005 | A1 |
| 20050183017 | Cain | Aug 2005 | A1 |
| 20050190280 | Haas et al. | Sep 2005 | A1 |
| 20050204295 | Voorhees et al. | Sep 2005 | A1 |
| 20050223338 | Partanen | Oct 2005 | A1 |
| 20050229112 | Clay et al. | Oct 2005 | A1 |
| 20050283726 | Lunati | Dec 2005 | A1 |
| 20050289476 | Tokkonen | Dec 2005 | A1 |
| 20060001650 | Robbins et al. | Jan 2006 | A1 |
| 20060001657 | Monney et al. | Jan 2006 | A1 |
| 20060012577 | Kyrola | Jan 2006 | A1 |
| 20060022955 | Kennedy | Feb 2006 | A1 |
| 20060026536 | Hotelling et al. | Feb 2006 | A1 |
| 20060031776 | Glein et al. | Feb 2006 | A1 |
| 20060036945 | Radtke et al. | Feb 2006 | A1 |
| 20060036971 | Mendel et al. | Feb 2006 | A1 |
| 20060059436 | Nurmi | Mar 2006 | A1 |
| 20060067677 | Tokiwa et al. | Mar 2006 | A1 |
| 20060101347 | Runov et al. | May 2006 | A1 |
| 20060101581 | Blanchard et al. | May 2006 | A1 |
| 20060109252 | Kolmykov-Zotov et al. | May 2006 | A1 |
| 20060109256 | Grant et al. | May 2006 | A1 |
| 20060119586 | Grant et al. | Jun 2006 | A1 |
| 20060132455 | Rimas-Ribikauskas et al. | Jun 2006 | A1 |
| 20060132456 | Anson | Jun 2006 | A1 |
| 20060132457 | Rimas-Ribikauskas et al. | Jun 2006 | A1 |
| 20060136834 | Cao et al. | Jun 2006 | A1 |
| 20060136845 | Rimas-Ribikauskas et al. | Jun 2006 | A1 |
| 20060161861 | Holecek et al. | Jul 2006 | A1 |
| 20060161870 | Hotelling et al. | Jul 2006 | A1 |
| 20060190834 | Marcjan | Aug 2006 | A1 |
| 20060195438 | Galuten | Aug 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060210958 | Rimas-Ribikauskas et al. | Sep 2006 | A1 |
| 20060212812 | Simmons et al. | Sep 2006 | A1 |
| 20060213754 | Jarrett et al. | Sep 2006 | A1 |
| 20060224989 | Pettiross et al. | Oct 2006 | A1 |
| 20060233248 | Rynderman et al. | Oct 2006 | A1 |
| 20060236263 | Bathiche et al. | Oct 2006 | A1 |
| 20060274042 | Krah et al. | Dec 2006 | A1 |
| 20060274086 | Forstall et al. | Dec 2006 | A1 |
| 20060277469 | Chaudhri et al. | Dec 2006 | A1 |
| 20060282778 | Barsness et al. | Dec 2006 | A1 |
| 20060284858 | Rekimoto | Dec 2006 | A1 |
| 20060290681 | Ho et al. | Dec 2006 | A1 |
| 20070003134 | Song et al. | Jan 2007 | A1 |
| 20070024595 | Baker et al. | Feb 2007 | A1 |
| 20070024646 | Saarinen et al. | Feb 2007 | A1 |
| 20070036456 | Hooper | Feb 2007 | A1 |
| 20070080953 | Lii | Apr 2007 | A1 |
| 20070113681 | Nishimura et al. | May 2007 | A1 |
| 20070120834 | Boillot | May 2007 | A1 |
| 20070120835 | Sato | May 2007 | A1 |
| 20070124699 | Michaels | May 2007 | A1 |
| 20070152959 | Peters | Jul 2007 | A1 |
| 20070157089 | Van Os et al. | Jul 2007 | A1 |
| 20070157173 | Klein et al. | Jul 2007 | A1 |
| 20070168369 | Bruns | Jul 2007 | A1 |
| 20070168890 | Zhao et al. | Jul 2007 | A1 |
| 20070176904 | Russo | Aug 2007 | A1 |
| 20070182999 | Anthony et al. | Aug 2007 | A1 |
| 20070186178 | Schiller | Aug 2007 | A1 |
| 20070200713 | Weber et al. | Aug 2007 | A1 |
| 20070222768 | Geurts et al. | Sep 2007 | A1 |
| 20070229455 | Martin et al. | Oct 2007 | A1 |
| 20070229464 | Hotelling et al. | Oct 2007 | A1 |
| 20070236450 | Colgate et al. | Oct 2007 | A1 |
| 20070236477 | Ryu et al. | Oct 2007 | A1 |
| 20070245241 | Bertram et al. | Oct 2007 | A1 |
| 20070257821 | Son et al. | Nov 2007 | A1 |
| 20070270182 | Gulliksson et al. | Nov 2007 | A1 |
| 20070271513 | Andren et al. | Nov 2007 | A1 |
| 20070288862 | Ording | Dec 2007 | A1 |
| 20070294295 | Finkelstein et al. | Dec 2007 | A1 |
| 20070299923 | Skelly et al. | Dec 2007 | A1 |
| 20080001924 | de los Reyes et al. | Jan 2008 | A1 |
| 20080010610 | Lim et al. | Jan 2008 | A1 |
| 20080024459 | Poupyrev et al. | Jan 2008 | A1 |
| 20080034306 | Ording | Feb 2008 | A1 |
| 20080034331 | Josephsoon et al. | Feb 2008 | A1 |
| 20080036743 | Westerman et al. | Feb 2008 | A1 |
| 20080051989 | Welsh | Feb 2008 | A1 |
| 20080052945 | Matas et al. | Mar 2008 | A1 |
| 20080066010 | Brodersen et al. | Mar 2008 | A1 |
| 20080094367 | Van De Ven et al. | Apr 2008 | A1 |
| 20080094368 | Ording et al. | Apr 2008 | A1 |
| 20080094398 | Ng et al. | Apr 2008 | A1 |
| 20080106523 | Conrad | May 2008 | A1 |
| 20080109753 | Karstens | May 2008 | A1 |
| 20080136790 | Hio | Jun 2008 | A1 |
| 20080155415 | Yoon et al. | Jun 2008 | A1 |
| 20080163119 | Kim et al. | Jul 2008 | A1 |
| 20080165141 | Christie | Jul 2008 | A1 |
| 20080165160 | Kocienda et al. | Jul 2008 | A1 |
| 20080168379 | Forstall et al. | Jul 2008 | A1 |
| 20080168395 | Ording et al. | Jul 2008 | A1 |
| 20080168403 | Westerman et al. | Jul 2008 | A1 |
| 20080168404 | Ording | Jul 2008 | A1 |
| 20080189605 | Kay et al. | Aug 2008 | A1 |
| 20080202824 | Philipp et al. | Aug 2008 | A1 |
| 20080204427 | Heesemans et al. | Aug 2008 | A1 |
| 20080219493 | Tadmor | Sep 2008 | A1 |
| 20080222569 | Champion et al. | Sep 2008 | A1 |
| 20080225007 | Nakadaira et al. | Sep 2008 | A1 |
| 20080244448 | Goering et al. | Oct 2008 | A1 |
| 20080259046 | Carsanaro | Oct 2008 | A1 |
| 20080263452 | Tomkins | Oct 2008 | A1 |
| 20080284866 | Mizutani | Nov 2008 | A1 |
| 20080294984 | Ramsay et al. | Nov 2008 | A1 |
| 20080297475 | Woolf et al. | Dec 2008 | A1 |
| 20080303795 | Lowles et al. | Dec 2008 | A1 |
| 20080303799 | Schwesig et al. | Dec 2008 | A1 |
| 20080307335 | Chaudhri et al. | Dec 2008 | A1 |
| 20080307359 | Louch et al. | Dec 2008 | A1 |
| 20080307361 | Louch et al. | Dec 2008 | A1 |
| 20080317378 | Steinberg et al. | Dec 2008 | A1 |
| 20080320419 | Matas et al. | Dec 2008 | A1 |
| 20090007017 | Anzures et al. | Jan 2009 | A1 |
| 20090016645 | Sako et al. | Jan 2009 | A1 |
| 20090028359 | Terada et al. | Jan 2009 | A1 |
| 20090046110 | Sadler et al. | Feb 2009 | A1 |
| 20090058828 | Jiang et al. | Mar 2009 | A1 |
| 20090061837 | Chaudhri et al. | Mar 2009 | A1 |
| 20090064031 | Bull et al. | Mar 2009 | A1 |
| 20090066668 | Kim et al. | Mar 2009 | A1 |
| 20090073118 | Yamaji et al. | Mar 2009 | A1 |
| 20090075738 | Pearce | Mar 2009 | A1 |
| 20090083665 | Anttila et al. | Mar 2009 | A1 |
| 20090085878 | Heubel et al. | Apr 2009 | A1 |
| 20090085881 | Keam | Apr 2009 | A1 |
| 20090085886 | Huang et al. | Apr 2009 | A1 |
| 20090089293 | Garritano et al. | Apr 2009 | A1 |
| 20090100343 | Lee et al. | Apr 2009 | A1 |
| 20090102804 | Wong et al. | Apr 2009 | A1 |
| 20090102805 | Meijer et al. | Apr 2009 | A1 |
| 20090140985 | Liu | Jun 2009 | A1 |
| 20090150775 | Miyazaki et al. | Jun 2009 | A1 |
| 20090158198 | Hayter et al. | Jun 2009 | A1 |
| 20090160793 | Rekimoto | Jun 2009 | A1 |
| 20090160814 | Li et al. | Jun 2009 | A1 |
| 20090164905 | Ko | Jun 2009 | A1 |
| 20090167507 | Maenpaa | Jul 2009 | A1 |
| 20090167508 | Fadell et al. | Jul 2009 | A1 |
| 20090167509 | Fadell et al. | Jul 2009 | A1 |
| 20090167704 | Terlizzi et al. | Jul 2009 | A1 |
| 20090169061 | Anderson et al. | Jul 2009 | A1 |
| 20090178008 | Herz et al. | Jul 2009 | A1 |
| 20090187824 | Hinckley et al. | Jul 2009 | A1 |
| 20090189866 | Haffenden et al. | Jul 2009 | A1 |
| 20090195959 | Ladouceur et al. | Aug 2009 | A1 |
| 20090198767 | Jakobson et al. | Aug 2009 | A1 |
| 20090201260 | Lee et al. | Aug 2009 | A1 |
| 20090219294 | Young et al. | Sep 2009 | A1 |
| 20090225037 | Williamson et al. | Sep 2009 | A1 |
| 20090228842 | Westerman et al. | Sep 2009 | A1 |
| 20090231453 | Huang | Sep 2009 | A1 |
| 20090237374 | Li et al. | Sep 2009 | A1 |
| 20090244357 | Huang | Oct 2009 | A1 |
| 20090247112 | Lundy et al. | Oct 2009 | A1 |
| 20090247230 | Lundy et al. | Oct 2009 | A1 |
| 20090251410 | Mori et al. | Oct 2009 | A1 |
| 20090251421 | Bloebaum | Oct 2009 | A1 |
| 20090256947 | Ciurea et al. | Oct 2009 | A1 |
| 20090259975 | Asai et al. | Oct 2009 | A1 |
| 20090267906 | Schroderus | Oct 2009 | A1 |
| 20090276730 | Aybes et al. | Nov 2009 | A1 |
| 20090280860 | Dahlke | Nov 2009 | A1 |
| 20090282360 | Park et al. | Nov 2009 | A1 |
| 20090284478 | De La Torre Baltierra et al. | Nov 2009 | A1 |
| 20090288032 | Chang et al. | Nov 2009 | A1 |
| 20090289779 | Braun et al. | Nov 2009 | A1 |
| 20090293009 | Meserth et al. | Nov 2009 | A1 |
| 20090295713 | Piot et al. | Dec 2009 | A1 |
| 20090295739 | Nagara | Dec 2009 | A1 |
| 20090295943 | Kim et al. | Dec 2009 | A1 |
| 20090298546 | Kim et al. | Dec 2009 | A1 |
| 20090303187 | Pallakoff | Dec 2009 | A1 |
| 20090307583 | Tonisson | Dec 2009 | A1 |
| 20090307633 | Haughay, Jr. et al. | Dec 2009 | A1 |
| 20090322893 | Stallings et al. | Dec 2009 | A1 |
| 20090325566 | Bell et al. | Dec 2009 | A1 |
| 20100005390 | Bong | Jan 2010 | A1 |
| 20100007926 | Imaizumi et al. | Jan 2010 | A1 |
| 20100011304 | Van Os | Jan 2010 | A1 |
| 20100013613 | Weston | Jan 2010 | A1 |
| 20100013777 | Baudisch et al. | Jan 2010 | A1 |
| 20100017710 | Kim et al. | Jan 2010 | A1 |
| 20100020035 | Ryu et al. | Jan 2010 | A1 |
| 20100020221 | Tupman et al. | Jan 2010 | A1 |
| 20100026640 | Kim et al. | Feb 2010 | A1 |
| 20100026647 | Abe et al. | Feb 2010 | A1 |
| 20100039446 | Hillis et al. | Feb 2010 | A1 |
| 20100044121 | Simon et al. | Feb 2010 | A1 |
| 20100045619 | Birnbaum et al. | Feb 2010 | A1 |
| 20100057235 | Wang et al. | Mar 2010 | A1 |
| 20100058231 | Duarte et al. | Mar 2010 | A1 |
| 20100060548 | Choi et al. | Mar 2010 | A1 |
| 20100060605 | Rimas-Ribikauskas et al. | Mar 2010 | A1 |
| 20100061637 | Mochizuki et al. | Mar 2010 | A1 |
| 20100062803 | Yun et al. | Mar 2010 | A1 |
| 20100070908 | Mori et al. | Mar 2010 | A1 |
| 20100073329 | Raman et al. | Mar 2010 | A1 |
| 20100083116 | Akifusa et al. | Apr 2010 | A1 |
| 20100085302 | Fairweather et al. | Apr 2010 | A1 |
| 20100085314 | Kwok | Apr 2010 | A1 |
| 20100085317 | Park et al. | Apr 2010 | A1 |
| 20100088596 | Griffin et al. | Apr 2010 | A1 |
| 20100088654 | Henhoeffer | Apr 2010 | A1 |
| 20100102832 | Bartling et al. | Apr 2010 | A1 |
| 20100110082 | Myrick et al. | May 2010 | A1 |
| 20100111434 | Madden | May 2010 | A1 |
| 20100127983 | Irani et al. | May 2010 | A1 |
| 20100128002 | Stacy et al. | May 2010 | A1 |
| 20100138776 | Korhonen | Jun 2010 | A1 |
| 20100148999 | Casparian et al. | Jun 2010 | A1 |
| 20100149096 | Migos et al. | Jun 2010 | A1 |
| 20100153879 | Rimas-Ribikauskas et al. | Jun 2010 | A1 |
| 20100156807 | Stallings et al. | Jun 2010 | A1 |
| 20100156813 | Duarte et al. | Jun 2010 | A1 |
| 20100156818 | Burrough et al. | Jun 2010 | A1 |
| 20100156823 | Paleczny et al. | Jun 2010 | A1 |
| 20100156825 | Sohn et al. | Jun 2010 | A1 |
| 20100156830 | Homma et al. | Jun 2010 | A1 |
| 20100159995 | Stallings et al. | Jun 2010 | A1 |
| 20100171713 | Kwok et al. | Jul 2010 | A1 |
| 20100175023 | Gatlin et al. | Jul 2010 | A1 |
| 20100180136 | Thompson et al. | Jul 2010 | A1 |
| 20100180225 | Chiba et al. | Jul 2010 | A1 |
| 20100199227 | Xiao et al. | Aug 2010 | A1 |
| 20100211872 | Rolston et al. | Aug 2010 | A1 |
| 20100214135 | Bathiche et al. | Aug 2010 | A1 |
| 20100214239 | Wu | Aug 2010 | A1 |
| 20100218663 | Choi | Sep 2010 | A1 |
| 20100220065 | Ma | Sep 2010 | A1 |
| 20100225456 | Eldering | Sep 2010 | A1 |
| 20100225604 | Homma et al. | Sep 2010 | A1 |
| 20100231533 | Chaudhri | Sep 2010 | A1 |
| 20100231534 | Chaudhri et al. | Sep 2010 | A1 |
| 20100231539 | Cruz-Hernandez et al. | Sep 2010 | A1 |
| 20100235118 | Moore et al. | Sep 2010 | A1 |
| 20100235726 | Ording et al. | Sep 2010 | A1 |
| 20100235733 | Drislane et al. | Sep 2010 | A1 |
| 20100235746 | Anzures | Sep 2010 | A1 |
| 20100240415 | Kim et al. | Sep 2010 | A1 |
| 20100241955 | Price et al. | Sep 2010 | A1 |
| 20100248787 | Smuga et al. | Sep 2010 | A1 |
| 20100251168 | Fujita et al. | Sep 2010 | A1 |
| 20100259500 | Kennedy | Oct 2010 | A1 |
| 20100271312 | Alameh et al. | Oct 2010 | A1 |
| 20100271500 | Park et al. | Oct 2010 | A1 |
| 20100277419 | Ganey et al. | Nov 2010 | A1 |
| 20100277496 | Kawanishi et al. | Nov 2010 | A1 |
| 20100281379 | Meaney et al. | Nov 2010 | A1 |
| 20100281385 | Meaney et al. | Nov 2010 | A1 |
| 20100287486 | Coddington | Nov 2010 | A1 |
| 20100289807 | Yu et al. | Nov 2010 | A1 |
| 20100293460 | Budelli | Nov 2010 | A1 |
| 20100295789 | Shin et al. | Nov 2010 | A1 |
| 20100295805 | Shin et al. | Nov 2010 | A1 |
| 20100302177 | Kim et al. | Dec 2010 | A1 |
| 20100302179 | Ahn et al. | Dec 2010 | A1 |
| 20100306702 | Warner | Dec 2010 | A1 |
| 20100308983 | Conte et al. | Dec 2010 | A1 |
| 20100309147 | Fleizach et al. | Dec 2010 | A1 |
| 20100313050 | Harrat et al. | Dec 2010 | A1 |
| 20100313124 | Privault et al. | Dec 2010 | A1 |
| 20100313146 | Nielsen et al. | Dec 2010 | A1 |
| 20100313156 | Louch et al. | Dec 2010 | A1 |
| 20100313158 | Lee et al. | Dec 2010 | A1 |
| 20100313166 | Nakayama et al. | Dec 2010 | A1 |
| 20100315417 | Cho et al. | Dec 2010 | A1 |
| 20100315438 | Horodezky et al. | Dec 2010 | A1 |
| 20100317410 | Song et al. | Dec 2010 | A1 |
| 20100321301 | Casparian et al. | Dec 2010 | A1 |
| 20100321312 | Han et al. | Dec 2010 | A1 |
| 20100325578 | Mital et al. | Dec 2010 | A1 |
| 20100328229 | Weber et al. | Dec 2010 | A1 |
| 20110010626 | Fino et al. | Jan 2011 | A1 |
| 20110012851 | Ciesla et al. | Jan 2011 | A1 |
| 20110018695 | Bells et al. | Jan 2011 | A1 |
| 20110026099 | Kwon et al. | Feb 2011 | A1 |
| 20110035145 | Yamasaki | Feb 2011 | A1 |
| 20110037706 | Pasquero et al. | Feb 2011 | A1 |
| 20110038552 | Lam | Feb 2011 | A1 |
| 20110039602 | McNamara et al. | Feb 2011 | A1 |
| 20110047368 | Sundaramurthy et al. | Feb 2011 | A1 |
| 20110050576 | Forutanpour et al. | Mar 2011 | A1 |
| 20110050588 | Li et al. | Mar 2011 | A1 |
| 20110050591 | Kim et al. | Mar 2011 | A1 |
| 20110050594 | Kim et al. | Mar 2011 | A1 |
| 20110050628 | Homma et al. | Mar 2011 | A1 |
| 20110050629 | Homma et al. | Mar 2011 | A1 |
| 20110050630 | Ikeda | Mar 2011 | A1 |
| 20110050653 | Miyazawa et al. | Mar 2011 | A1 |
| 20110050687 | Alyshev et al. | Mar 2011 | A1 |
| 20110054837 | Ikeda | Mar 2011 | A1 |
| 20110055135 | Dawson et al. | Mar 2011 | A1 |
| 20110055741 | Jeon et al. | Mar 2011 | A1 |
| 20110057886 | Ng et al. | Mar 2011 | A1 |
| 20110057903 | Yamano et al. | Mar 2011 | A1 |
| 20110061021 | Kang et al. | Mar 2011 | A1 |
| 20110061029 | Yeh et al. | Mar 2011 | A1 |
| 20110063236 | Arai et al. | Mar 2011 | A1 |
| 20110063248 | Yoon | Mar 2011 | A1 |
| 20110069012 | Martensson | Mar 2011 | A1 |
| 20110069016 | Victor | Mar 2011 | A1 |
| 20110074697 | Rapp et al. | Mar 2011 | A1 |
| 20110080349 | Holbein et al. | Apr 2011 | A1 |
| 20110080350 | Almalki et al. | Apr 2011 | A1 |
| 20110080367 | Marchand et al. | Apr 2011 | A1 |
| 20110084910 | Almalki et al. | Apr 2011 | A1 |
| 20110087982 | McCann et al. | Apr 2011 | A1 |
| 20110087983 | Shim | Apr 2011 | A1 |
| 20110093815 | Gobeil | Apr 2011 | A1 |
| 20110093817 | Song et al. | Apr 2011 | A1 |
| 20110102829 | Jourdan | May 2011 | A1 |
| 20110107272 | Aquilar | May 2011 | A1 |
| 20110109617 | Snook et al. | May 2011 | A1 |
| 20110116716 | Kwon et al. | May 2011 | A1 |
| 20110119610 | Hackborn et al. | May 2011 | A1 |
| 20110126139 | Jeong et al. | May 2011 | A1 |
| 20110138295 | Momchilov et al. | Jun 2011 | A1 |
| 20110141031 | McCullough et al. | Jun 2011 | A1 |
| 20110141052 | Bernstein et al. | Jun 2011 | A1 |
| 20110144777 | Firkins et al. | Jun 2011 | A1 |
| 20110145752 | Fagans | Jun 2011 | A1 |
| 20110145753 | Prakash | Jun 2011 | A1 |
| 20110145759 | Leffert et al. | Jun 2011 | A1 |
| 20110145764 | Higuchi et al. | Jun 2011 | A1 |
| 20110149138 | Watkins | Jun 2011 | A1 |
| 20110154199 | Maffitt et al. | Jun 2011 | A1 |
| 20110159469 | Hwang et al. | Jun 2011 | A1 |
| 20110163971 | Wagner et al. | Jul 2011 | A1 |
| 20110163978 | Park et al. | Jul 2011 | A1 |
| 20110169765 | Aono | Jul 2011 | A1 |
| 20110175826 | Moore et al. | Jul 2011 | A1 |
| 20110175832 | Miyazawa et al. | Jul 2011 | A1 |
| 20110181521 | Reid et al. | Jul 2011 | A1 |
| 20110181526 | Shaffer et al. | Jul 2011 | A1 |
| 20110181538 | Aono | Jul 2011 | A1 |
| 20110181751 | Mizumori | Jul 2011 | A1 |
| 20110185299 | Hinckley et al. | Jul 2011 | A1 |
| 20110185300 | Hinckley et al. | Jul 2011 | A1 |
| 20110185316 | Reid et al. | Jul 2011 | A1 |
| 20110191675 | Kauranen | Aug 2011 | A1 |
| 20110193788 | King et al. | Aug 2011 | A1 |
| 20110193809 | Walley et al. | Aug 2011 | A1 |
| 20110193881 | Rydenhag | Aug 2011 | A1 |
| 20110197160 | Kim et al. | Aug 2011 | A1 |
| 20110201387 | Paek et al. | Aug 2011 | A1 |
| 20110202834 | Mandryk et al. | Aug 2011 | A1 |
| 20110202853 | Mujkic | Aug 2011 | A1 |
| 20110202879 | Stovicek et al. | Aug 2011 | A1 |
| 20110205163 | Hinckley et al. | Aug 2011 | A1 |
| 20110209088 | Hinckley et al. | Aug 2011 | A1 |
| 20110209093 | Hinckley et al. | Aug 2011 | A1 |
| 20110209097 | Hinckley et al. | Aug 2011 | A1 |
| 20110209099 | Hinckley et al. | Aug 2011 | A1 |
| 20110209104 | Hinckley et al. | Aug 2011 | A1 |
| 20110210834 | Pasquero et al. | Sep 2011 | A1 |
| 20110210926 | Pasquero et al. | Sep 2011 | A1 |
| 20110210931 | Shai | Sep 2011 | A1 |
| 20110215914 | Edwards | Sep 2011 | A1 |
| 20110221684 | Rydenhag | Sep 2011 | A1 |
| 20110221776 | Shimotani et al. | Sep 2011 | A1 |
| 20110231789 | Bukurak et al. | Sep 2011 | A1 |
| 20110234639 | Shimotani et al. | Sep 2011 | A1 |
| 20110238690 | Arrasvouri et al. | Sep 2011 | A1 |
| 20110239110 | Garrett et al. | Sep 2011 | A1 |
| 20110242029 | Kasahara et al. | Oct 2011 | A1 |
| 20110246801 | Seethaler et al. | Oct 2011 | A1 |
| 20110246877 | Kwak et al. | Oct 2011 | A1 |
| 20110248916 | Griffin et al. | Oct 2011 | A1 |
| 20110248942 | Yana et al. | Oct 2011 | A1 |
| 20110248948 | Griffin et al. | Oct 2011 | A1 |
| 20110252346 | Chaudhri | Oct 2011 | A1 |
| 20110252357 | Chaudhri | Oct 2011 | A1 |
| 20110252362 | Cho et al. | Oct 2011 | A1 |
| 20110252380 | Chaudhri | Oct 2011 | A1 |
| 20110258537 | Rives et al. | Oct 2011 | A1 |
| 20110260994 | Saynac et al. | Oct 2011 | A1 |
| 20110263298 | Park | Oct 2011 | A1 |
| 20110265035 | Lepage et al. | Oct 2011 | A1 |
| 20110265045 | Hsieh | Oct 2011 | A1 |
| 20110267530 | Chun | Nov 2011 | A1 |
| 20110279380 | Weber et al. | Nov 2011 | A1 |
| 20110279381 | Tong et al. | Nov 2011 | A1 |
| 20110279395 | Kuwabara et al. | Nov 2011 | A1 |
| 20110279852 | Oda et al. | Nov 2011 | A1 |
| 20110285656 | Yaksick et al. | Nov 2011 | A1 |
| 20110285659 | Kuwabara et al. | Nov 2011 | A1 |
| 20110291945 | Ewing, Jr. et al. | Dec 2011 | A1 |
| 20110291951 | Tong | Dec 2011 | A1 |
| 20110296334 | Ryu et al. | Dec 2011 | A1 |
| 20110296351 | Ewing, Jr. et al. | Dec 2011 | A1 |
| 20110304559 | Pasquero | Dec 2011 | A1 |
| 20110304577 | Brown et al. | Dec 2011 | A1 |
| 20110310049 | Homma et al. | Dec 2011 | A1 |
| 20110319136 | Labowicz et al. | Dec 2011 | A1 |
| 20120001856 | Davidson | Jan 2012 | A1 |
| 20120005622 | Park et al. | Jan 2012 | A1 |
| 20120007857 | Noda et al. | Jan 2012 | A1 |
| 20120011437 | James et al. | Jan 2012 | A1 |
| 20120013541 | Boka et al. | Jan 2012 | A1 |
| 20120013542 | Shenfield | Jan 2012 | A1 |
| 20120013607 | Lee | Jan 2012 | A1 |
| 20120019448 | Pitkanen et al. | Jan 2012 | A1 |
| 20120023591 | Sahita et al. | Jan 2012 | A1 |
| 20120026110 | Yamano | Feb 2012 | A1 |
| 20120030623 | Hoellwarth | Feb 2012 | A1 |
| 20120032979 | Blow et al. | Feb 2012 | A1 |
| 20120036441 | Basir et al. | Feb 2012 | A1 |
| 20120036556 | LeBeau et al. | Feb 2012 | A1 |
| 20120038580 | Sasaki | Feb 2012 | A1 |
| 20120044153 | Arrasvouri et al. | Feb 2012 | A1 |
| 20120047380 | Nurmi | Feb 2012 | A1 |
| 20120056837 | Park et al. | Mar 2012 | A1 |
| 20120056848 | Yamano et al. | Mar 2012 | A1 |
| 20120057039 | Gardiner et al. | Mar 2012 | A1 |
| 20120060123 | Smith | Mar 2012 | A1 |
| 20120062470 | Chang | Mar 2012 | A1 |
| 20120062564 | Miyashita et al. | Mar 2012 | A1 |
| 20120062604 | Lobo | Mar 2012 | A1 |
| 20120062732 | Marman et al. | Mar 2012 | A1 |
| 20120066630 | Kim et al. | Mar 2012 | A1 |
| 20120066648 | Rolleston et al. | Mar 2012 | A1 |
| 20120081326 | Heubel et al. | Apr 2012 | A1 |
| 20120081375 | Robert et al. | Apr 2012 | A1 |
| 20120084644 | Robert et al. | Apr 2012 | A1 |
| 20120084689 | Ledet et al. | Apr 2012 | A1 |
| 20120084713 | Desai et al. | Apr 2012 | A1 |
| 20120089932 | Kano et al. | Apr 2012 | A1 |
| 20120089942 | Gammon | Apr 2012 | A1 |
| 20120089951 | Cassidy | Apr 2012 | A1 |
| 20120092381 | Hoover et al. | Apr 2012 | A1 |
| 20120096393 | Shim et al. | Apr 2012 | A1 |
| 20120096400 | Cho | Apr 2012 | A1 |
| 20120098780 | Fujisawa et al. | Apr 2012 | A1 |
| 20120102437 | Worley et al. | Apr 2012 | A1 |
| 20120105358 | Momeyer et al. | May 2012 | A1 |
| 20120105367 | Son et al. | May 2012 | A1 |
| 20120106852 | Khawand et al. | May 2012 | A1 |
| 20120113007 | Koch et al. | May 2012 | A1 |
| 20120113023 | Koch et al. | May 2012 | A1 |
| 20120126962 | Ujii et al. | May 2012 | A1 |
| 20120131495 | Goossens et al. | May 2012 | A1 |
| 20120139844 | Ramstein et al. | Jun 2012 | A1 |
| 20120139864 | Sleeman et al. | Jun 2012 | A1 |
| 20120144330 | Flint | Jun 2012 | A1 |
| 20120146945 | Miyazawa et al. | Jun 2012 | A1 |
| 20120147052 | Homma et al. | Jun 2012 | A1 |
| 20120154303 | Lazaridis et al. | Jun 2012 | A1 |
| 20120154328 | Kono | Jun 2012 | A1 |
| 20120158629 | Hinckley et al. | Jun 2012 | A1 |
| 20120159380 | Kocienda et al. | Jun 2012 | A1 |
| 20120162093 | Buxton et al. | Jun 2012 | A1 |
| 20120174042 | Chang | Jun 2012 | A1 |
| 20120169646 | Berkes et al. | Jul 2012 | A1 |
| 20120169716 | Mihara | Jul 2012 | A1 |
| 20120176403 | Cha et al. | Jul 2012 | A1 |
| 20120179967 | Hayes | Jul 2012 | A1 |
| 20120180001 | Griffen et al. | Jul 2012 | A1 |
| 20120182226 | Tuli | Jul 2012 | A1 |
| 20120183271 | Forutanpour et al. | Jul 2012 | A1 |
| 20120192108 | Kolb | Jul 2012 | A1 |
| 20120200528 | Ciesla et al. | Aug 2012 | A1 |
| 20120206393 | Hillis et al. | Aug 2012 | A1 |
| 20120216114 | Privault et al. | Aug 2012 | A1 |
| 20120218203 | Kanki | Aug 2012 | A1 |
| 20120235912 | Laubach | Sep 2012 | A1 |
| 20120236037 | Lessing et al. | Sep 2012 | A1 |
| 20120240044 | Johnson et al. | Sep 2012 | A1 |
| 20120242584 | Tuli | Sep 2012 | A1 |
| 20120242599 | Seo et al. | Sep 2012 | A1 |
| 20120245922 | Koslova et al. | Sep 2012 | A1 |
| 20120249575 | Krolczyk et al. | Oct 2012 | A1 |
| 20120249853 | Krolczyk et al. | Oct 2012 | A1 |
| 20120250598 | Lonnfors et al. | Oct 2012 | A1 |
| 20120256829 | Dodge | Oct 2012 | A1 |
| 20120256846 | Mak | Oct 2012 | A1 |
| 20120256847 | Mak et al. | Oct 2012 | A1 |
| 20120256857 | Mak | Oct 2012 | A1 |
| 20120257071 | Prentice | Oct 2012 | A1 |
| 20120260208 | Jung | Oct 2012 | A1 |
| 20120260219 | Piccolotto | Oct 2012 | A1 |
| 20120260220 | Griffin | Oct 2012 | A1 |
| 20120274578 | Snow et al. | Nov 2012 | A1 |
| 20120274591 | Rimas-Ribikauskas et al. | Nov 2012 | A1 |
| 20120274662 | Kim et al. | Nov 2012 | A1 |
| 20120278744 | Kozitsyn et al. | Nov 2012 | A1 |
| 20120284673 | Lamb et al. | Nov 2012 | A1 |
| 20120293449 | Dietz | Nov 2012 | A1 |
| 20120293551 | Momeyer et al. | Nov 2012 | A1 |
| 20120297041 | Momchilov | Nov 2012 | A1 |
| 20120303548 | Johnson et al. | Nov 2012 | A1 |
| 20120304108 | Jarrett et al. | Nov 2012 | A1 |
| 20120304132 | Sareen et al. | Nov 2012 | A1 |
| 20120304133 | Nan et al. | Nov 2012 | A1 |
| 20120306632 | Fleizach et al. | Dec 2012 | A1 |
| 20120306748 | Fleizach et al. | Dec 2012 | A1 |
| 20120306764 | Kamibeppu | Dec 2012 | A1 |
| 20120306765 | Moore | Dec 2012 | A1 |
| 20120306766 | Moore | Dec 2012 | A1 |
| 20120306772 | Tan et al. | Dec 2012 | A1 |
| 20120306778 | Wheeldreyer et al. | Dec 2012 | A1 |
| 20120306927 | Lee et al. | Dec 2012 | A1 |
| 20120311429 | Decker et al. | Dec 2012 | A1 |
| 20120311437 | Weeldreyer et al. | Dec 2012 | A1 |
| 20120311498 | Kluttz et al. | Dec 2012 | A1 |
| 20120311504 | van Os et al. | Dec 2012 | A1 |
| 20120313847 | Boda et al. | Dec 2012 | A1 |
| 20130002561 | Wakasa | Jan 2013 | A1 |
| 20130014057 | Reinpoldt et al. | Jan 2013 | A1 |
| 20130016042 | Makinen et al. | Jan 2013 | A1 |
| 20130016056 | Shinozaki et al. | Jan 2013 | A1 |
| 20130016122 | Bhatt et al. | Jan 2013 | A1 |
| 20130019158 | Watanabe | Jan 2013 | A1 |
| 20130019174 | Gil et al. | Jan 2013 | A1 |
| 20130031514 | Gabbert | Jan 2013 | A1 |
| 20130036386 | Park et al. | Feb 2013 | A1 |
| 20130042199 | Fong et al. | Feb 2013 | A1 |
| 20130044062 | Bose et al. | Feb 2013 | A1 |
| 20130047100 | Kroeger et al. | Feb 2013 | A1 |
| 20130050131 | Lee et al. | Feb 2013 | A1 |
| 20130050143 | Kim et al. | Feb 2013 | A1 |
| 20130050518 | Takemura et al. | Feb 2013 | A1 |
| 20130061172 | Huang et al. | Mar 2013 | A1 |
| 20130063364 | Moore | Mar 2013 | A1 |
| 20130063389 | Moore | Mar 2013 | A1 |
| 20130067383 | Kataoka et al. | Mar 2013 | A1 |
| 20130067513 | Takami | Mar 2013 | A1 |
| 20130067527 | Ashbook et al. | Mar 2013 | A1 |
| 20130069889 | Pearce et al. | Mar 2013 | A1 |
| 20130069991 | Davidson | Mar 2013 | A1 |
| 20130074003 | Dolenc | Mar 2013 | A1 |
| 20130076649 | Myers et al. | Mar 2013 | A1 |
| 20130076676 | Gan | Mar 2013 | A1 |
| 20130077804 | Glebe et al. | Mar 2013 | A1 |
| 20130082824 | Colley | Apr 2013 | A1 |
| 20130082937 | Liu et al. | Apr 2013 | A1 |
| 20130086056 | Dyor et al. | Apr 2013 | A1 |
| 20130088455 | Jeong | Apr 2013 | A1 |
| 20130093691 | Moosavi | Apr 2013 | A1 |
| 20130093764 | Andersson et al. | Apr 2013 | A1 |
| 20130097520 | Lewin et al. | Apr 2013 | A1 |
| 20130097521 | Lewin et al. | Apr 2013 | A1 |
| 20130097534 | Lewin et al. | Apr 2013 | A1 |
| 20130097539 | Mansson et al. | Apr 2013 | A1 |
| 20130097556 | Louch | Apr 2013 | A1 |
| 20130097562 | Kermoian et al. | Apr 2013 | A1 |
| 20130102366 | Teng et al. | Apr 2013 | A1 |
| 20130111345 | Newman et al. | May 2013 | A1 |
| 20130111378 | Newman et al. | May 2013 | A1 |
| 20130111398 | Lu et al. | May 2013 | A1 |
| 20130111415 | Newman et al. | May 2013 | A1 |
| 20130111579 | Newman et al. | May 2013 | A1 |
| 20130113715 | Grant et al. | May 2013 | A1 |
| 20130113720 | Van Eerd et al. | May 2013 | A1 |
| 20130113760 | Gossweiler, III et al. | May 2013 | A1 |
| 20130120278 | Cantrell | May 2013 | A1 |
| 20130120280 | Kukulski | May 2013 | A1 |
| 20130120295 | Kim et al. | May 2013 | A1 |
| 20130120306 | Furukawa | May 2013 | A1 |
| 20130125039 | Murata | May 2013 | A1 |
| 20130127755 | Lynn et al. | May 2013 | A1 |
| 20130135243 | Hirsch et al. | May 2013 | A1 |
| 20130135288 | King et al. | May 2013 | A1 |
| 20130135499 | Song | May 2013 | A1 |
| 20130141364 | Lynn et al. | Jun 2013 | A1 |
| 20130141396 | Lynn et al. | Jun 2013 | A1 |
| 20130145313 | Roh et al. | Jun 2013 | A1 |
| 20130154948 | Schediwy et al. | Jun 2013 | A1 |
| 20130154959 | Lindsay et al. | Jun 2013 | A1 |
| 20130155018 | Dagdeviren | Jun 2013 | A1 |
| 20130159893 | Lewis et al. | Jun 2013 | A1 |
| 20130159930 | Paretti et al. | Jun 2013 | A1 |
| 20130162603 | Peng et al. | Jun 2013 | A1 |
| 20130162667 | Eskolin et al. | Jun 2013 | A1 |
| 20130169549 | Seymour et al. | Jul 2013 | A1 |
| 20130174049 | Townsend et al. | Jul 2013 | A1 |
| 20130174089 | Ki | Jul 2013 | A1 |
| 20130174094 | Heo et al. | Jul 2013 | A1 |
| 20130174179 | Park et al. | Jul 2013 | A1 |
| 20130179840 | Fisher et al. | Jul 2013 | A1 |
| 20130185642 | Gammons | Jul 2013 | A1 |
| 20130187869 | Rydenhag et al. | Jul 2013 | A1 |
| 20130191791 | Rydenhag et al. | Jul 2013 | A1 |
| 20130194217 | Lee et al. | Aug 2013 | A1 |
| 20130194480 | Fukata et al. | Aug 2013 | A1 |
| 20130198690 | Barsoum et al. | Aug 2013 | A1 |
| 20130201139 | Tanaka | Aug 2013 | A1 |
| 20130212515 | Eleftheriou | Aug 2013 | A1 |
| 20130212541 | Dolenc et al. | Aug 2013 | A1 |
| 20130215079 | Johnson et al. | Aug 2013 | A1 |
| 20130222274 | Mori et al. | Aug 2013 | A1 |
| 20130222323 | McKenzie | Aug 2013 | A1 |
| 20130222333 | Miles et al. | Aug 2013 | A1 |
| 20130222671 | Tseng et al. | Aug 2013 | A1 |
| 20130227413 | Thorsander et al. | Aug 2013 | A1 |
| 20130227419 | Lee et al. | Aug 2013 | A1 |
| 20130227450 | Na et al. | Aug 2013 | A1 |
| 20130228023 | Drasnin et al. | Sep 2013 | A1 |
| 20130232353 | Belesiu et al. | Sep 2013 | A1 |
| 20130232402 | Lu et al. | Sep 2013 | A1 |
| 20130234929 | Libin | Sep 2013 | A1 |
| 20130239057 | Ubillos et al. | Sep 2013 | A1 |
| 20130246954 | Gray et al. | Sep 2013 | A1 |
| 20130249814 | Zeng | Sep 2013 | A1 |
| 20130257793 | Zeliff et al. | Oct 2013 | A1 |
| 20130257817 | Yliaho | Oct 2013 | A1 |
| 20130263252 | Lien et al. | Oct 2013 | A1 |
| 20130265246 | Tae | Oct 2013 | A1 |
| 20130265452 | Shin et al. | Oct 2013 | A1 |
| 20130268875 | Han et al. | Oct 2013 | A1 |
| 20130271395 | Tsai et al. | Oct 2013 | A1 |
| 20130275422 | Silber et al. | Oct 2013 | A1 |
| 20130278520 | Weng et al. | Oct 2013 | A1 |
| 20130293496 | Takamoto | Nov 2013 | A1 |
| 20130305184 | Kim et al. | Nov 2013 | A1 |
| 20130307790 | Konttori et al. | Nov 2013 | A1 |
| 20130307792 | Andres et al. | Nov 2013 | A1 |
| 20130314359 | Sudou | Nov 2013 | A1 |
| 20130314434 | Shetterly et al. | Nov 2013 | A1 |
| 20130321340 | Seo et al. | Dec 2013 | A1 |
| 20130321457 | Bauermeister et al. | Dec 2013 | A1 |
| 20130325342 | Pylappan et al. | Dec 2013 | A1 |
| 20130326420 | Liu et al. | Dec 2013 | A1 |
| 20130326421 | Jo | Dec 2013 | A1 |
| 20130326583 | Freihold et al. | Dec 2013 | A1 |
| 20130328770 | Parham | Dec 2013 | A1 |
| 20130328793 | Chowdhury | Dec 2013 | A1 |
| 20130328796 | Al-Dahle et al. | Dec 2013 | A1 |
| 20130332836 | Cho | Dec 2013 | A1 |
| 20130332892 | Matsuki | Dec 2013 | A1 |
| 20130335373 | Tomiyasu | Dec 2013 | A1 |
| 20130338847 | Lisseman et al. | Dec 2013 | A1 |
| 20130339001 | Craswell et al. | Dec 2013 | A1 |
| 20130339909 | Ha | Dec 2013 | A1 |
| 20140002355 | Lee et al. | Jan 2014 | A1 |
| 20140002374 | Hunt et al. | Jan 2014 | A1 |
| 20140002386 | Rosenberg et al. | Jan 2014 | A1 |
| 20140013271 | Moore et al. | Jan 2014 | A1 |
| 20140015784 | Oonishi | Jan 2014 | A1 |
| 20140019786 | Green et al. | Jan 2014 | A1 |
| 20140024414 | Fuji | Jan 2014 | A1 |
| 20140026098 | Gilman | Jan 2014 | A1 |
| 20140026099 | Andersson Reimer et al. | Jan 2014 | A1 |
| 20140028554 | De Los Reyes et al. | Jan 2014 | A1 |
| 20140028571 | St. Clair | Jan 2014 | A1 |
| 20140028601 | Moore | Jan 2014 | A1 |
| 20140028606 | Giannetta | Jan 2014 | A1 |
| 20140035804 | Dearman | Feb 2014 | A1 |
| 20140035826 | Frazier et al. | Feb 2014 | A1 |
| 20140049491 | Nagar et al. | Feb 2014 | A1 |
| 20140053116 | Smith et al. | Feb 2014 | A1 |
| 20140055367 | Dearman et al. | Feb 2014 | A1 |
| 20140055377 | Kim | Feb 2014 | A1 |
| 20140059460 | Ho | Feb 2014 | A1 |
| 20140059485 | Lehrian et al. | Feb 2014 | A1 |
| 20140063316 | Lee et al. | Mar 2014 | A1 |
| 20140063541 | Yamazaki | Mar 2014 | A1 |
| 20140067293 | Parivar et al. | Mar 2014 | A1 |
| 20140068475 | Li et al. | Mar 2014 | A1 |
| 20140071060 | Santos-Gomez | Mar 2014 | A1 |
| 20140072281 | Cho et al. | Mar 2014 | A1 |
| 20140072283 | Cho et al. | Mar 2014 | A1 |
| 20140078318 | Alameh | Mar 2014 | A1 |
| 20140078343 | Dai et al. | Mar 2014 | A1 |
| 20140082536 | Costa et al. | Mar 2014 | A1 |
| 20140092025 | Pala et al. | Apr 2014 | A1 |
| 20140092030 | Van Der Velden | Apr 2014 | A1 |
| 20140092031 | Schwartz et al. | Apr 2014 | A1 |
| 20140108936 | Khosropour et al. | Apr 2014 | A1 |
| 20140109016 | Ouyang et al. | Apr 2014 | A1 |
| 20140111456 | Kashiwa et al. | Apr 2014 | A1 |
| 20140111480 | Kim et al. | Apr 2014 | A1 |
| 20140111670 | Lord et al. | Apr 2014 | A1 |
| 20140118268 | Kuscher | May 2014 | A1 |
| 20140123080 | Gan | May 2014 | A1 |
| 20140139456 | Wigdor et al. | May 2014 | A1 |
| 20140139471 | Matsuki | May 2014 | A1 |
| 20140145970 | Cho | May 2014 | A1 |
| 20140152581 | Case et al. | Jun 2014 | A1 |
| 20140157203 | Jeon et al. | Jun 2014 | A1 |
| 20140160063 | Yairi et al. | Jun 2014 | A1 |
| 20140160073 | Matsuki | Jun 2014 | A1 |
| 20140160168 | Ogle | Jun 2014 | A1 |
| 20140164955 | Thiruvidam et al. | Jun 2014 | A1 |
| 20140164966 | Kim et al. | Jun 2014 | A1 |
| 20140165006 | Chaudhri et al. | Jun 2014 | A1 |
| 20140168093 | Lawrence | Jun 2014 | A1 |
| 20140168110 | Araki et al. | Jun 2014 | A1 |
| 20140168153 | Deichmann et al. | Jun 2014 | A1 |
| 20140173517 | Chaudhri | Jun 2014 | A1 |
| 20140179377 | Song et al. | Jun 2014 | A1 |
| 20140184526 | Cho | Jul 2014 | A1 |
| 20140201660 | Clausen et al. | Jul 2014 | A1 |
| 20140208271 | Bell et al. | Jul 2014 | A1 |
| 20140210758 | Park et al. | Jul 2014 | A1 |
| 20140210760 | Aberg et al. | Jul 2014 | A1 |
| 20140210798 | Wilson | Jul 2014 | A1 |
| 20140223376 | Tarvainen et al. | Aug 2014 | A1 |
| 20140223381 | Huang et al. | Aug 2014 | A1 |
| 20140237408 | Ohlsson et al. | Aug 2014 | A1 |
| 20140245202 | Yoon et al. | Aug 2014 | A1 |
| 20140245367 | Sasaki et al. | Aug 2014 | A1 |
| 20140253305 | Rosenberg et al. | Sep 2014 | A1 |
| 20140267114 | Lisseman et al. | Sep 2014 | A1 |
| 20140267135 | Chhabra | Sep 2014 | A1 |
| 20140267362 | Kocienda et al. | Sep 2014 | A1 |
| 20140282084 | Murarka et al. | Sep 2014 | A1 |
| 20140282211 | Ady et al. | Sep 2014 | A1 |
| 20140282214 | Shirzadi et al. | Sep 2014 | A1 |
| 20140300569 | Matsuki et al. | Oct 2014 | A1 |
| 20140304599 | Alexandersson | Oct 2014 | A1 |
| 20140304646 | Rossman | Oct 2014 | A1 |
| 20140304651 | Johansson et al. | Oct 2014 | A1 |
| 20140306897 | Cueto | Oct 2014 | A1 |
| 20140306899 | Hicks | Oct 2014 | A1 |
| 20140310638 | Lee et al. | Oct 2014 | A1 |
| 20140313130 | Yamano et al. | Oct 2014 | A1 |
| 20140333551 | Kim et al. | Nov 2014 | A1 |
| 20140333561 | Bull et al. | Nov 2014 | A1 |
| 20140344765 | Hicks et al. | Nov 2014 | A1 |
| 20140351744 | Jeon et al. | Nov 2014 | A1 |
| 20140354845 | Molgaard et al. | Dec 2014 | A1 |
| 20140354850 | Kosaka et al. | Dec 2014 | A1 |
| 20140359438 | Matsuki | Dec 2014 | A1 |
| 20140359528 | Murata | Dec 2014 | A1 |
| 20140361982 | Shaffer | Dec 2014 | A1 |
| 20140365882 | Lemay | Dec 2014 | A1 |
| 20140365945 | Karunamuni et al. | Dec 2014 | A1 |
| 20140365956 | Karunamuni et al. | Dec 2014 | A1 |
| 20140368436 | Abzarian et al. | Dec 2014 | A1 |
| 20140380247 | Tecarro et al. | Dec 2014 | A1 |
| 20150002664 | Eppinger et al. | Jan 2015 | A1 |
| 20150012861 | Loginov | Jan 2015 | A1 |
| 20150015763 | Lee et al. | Jan 2015 | A1 |
| 20150019997 | Kim et al. | Jan 2015 | A1 |
| 20150020032 | Chen | Jan 2015 | A1 |
| 20150020033 | Newham et al. | Jan 2015 | A1 |
| 20150020036 | Kim et al. | Jan 2015 | A1 |
| 20150022482 | Hewitt et al. | Jan 2015 | A1 |
| 20150026584 | Kobayakov et al. | Jan 2015 | A1 |
| 20150026592 | Mohammed et al. | Jan 2015 | A1 |
| 20150026642 | Wilson et al. | Jan 2015 | A1 |
| 20150029149 | Andersson et al. | Jan 2015 | A1 |
| 20150033184 | Kim et al. | Jan 2015 | A1 |
| 20150040065 | Bianco et al. | Feb 2015 | A1 |
| 20150042588 | Park | Feb 2015 | A1 |
| 20150046876 | Goldenberg | Feb 2015 | A1 |
| 20150049033 | Kim et al. | Feb 2015 | A1 |
| 20150052464 | Chen et al. | Feb 2015 | A1 |
| 20150055890 | Lundin et al. | Feb 2015 | A1 |
| 20150058723 | Cieplinski et al. | Feb 2015 | A1 |
| 20150062046 | Cho et al. | Mar 2015 | A1 |
| 20150062052 | Bernstein et al. | Mar 2015 | A1 |
| 20150062068 | Shih et al. | Mar 2015 | A1 |
| 20150066950 | Tobe et al. | Mar 2015 | A1 |
| 20150067495 | Bernstein et al. | Mar 2015 | A1 |
| 20150067496 | Missig et al. | Mar 2015 | A1 |
| 20150067497 | Cieplinski et al. | Mar 2015 | A1 |
| 20150067513 | Zambetti et al. | Mar 2015 | A1 |
| 20150067519 | Missig et al. | Mar 2015 | A1 |
| 20150067534 | Choi et al. | Mar 2015 | A1 |
| 20150067559 | Missig et al. | Mar 2015 | A1 |
| 20150067560 | Cieplinski et al. | Mar 2015 | A1 |
| 20150067563 | Bernstein et al. | Mar 2015 | A1 |
| 20150067596 | Brown et al. | Mar 2015 | A1 |
| 20150067601 | Bernstein et al. | Mar 2015 | A1 |
| 20150067602 | Bernstein et al. | Mar 2015 | A1 |
| 20150067605 | Zambetti et al. | Mar 2015 | A1 |
| 20150071547 | Keating et al. | Mar 2015 | A1 |
| 20150082162 | Cho et al. | Mar 2015 | A1 |
| 20150082238 | Meng | Mar 2015 | A1 |
| 20150116205 | Westerman et al. | Apr 2015 | A1 |
| 20150121218 | Kim et al. | Apr 2015 | A1 |
| 20150121225 | Somasundaram et al. | Apr 2015 | A1 |
| 20150128092 | Lee et al. | May 2015 | A1 |
| 20150135108 | Pope et al. | May 2015 | A1 |
| 20150135109 | Zambetti et al. | May 2015 | A1 |
| 20150135132 | Josephson | May 2015 | A1 |
| 20150138126 | Westerman | May 2015 | A1 |
| 20150138155 | Bernstein et al. | May 2015 | A1 |
| 20150139605 | Wiklof | May 2015 | A1 |
| 20150143273 | Bernstein et al. | May 2015 | A1 |
| 20150143284 | Bennett et al. | May 2015 | A1 |
| 20150143294 | Piccinato et al. | May 2015 | A1 |
| 20150143303 | Sarrazin et al. | May 2015 | A1 |
| 20150149899 | Bernstein et al. | May 2015 | A1 |
| 20150149964 | Bernstein et al. | May 2015 | A1 |
| 20150149967 | Bernstein et al. | May 2015 | A1 |
| 20150153897 | Huang et al. | Jun 2015 | A1 |
| 20150153929 | Bernstein et al. | Jun 2015 | A1 |
| 20150160729 | Nakagawa | Jun 2015 | A1 |
| 20150169059 | Behles et al. | Jun 2015 | A1 |
| 20150185840 | Golyshko et al. | Jul 2015 | A1 |
| 20150193099 | Murphy | Jul 2015 | A1 |
| 20150193951 | Lee et al. | Jul 2015 | A1 |
| 20150205342 | Ooi et al. | Jul 2015 | A1 |
| 20150205495 | Koide et al. | Jul 2015 | A1 |
| 20150205775 | Berdahl et al. | Jul 2015 | A1 |
| 20150234446 | Nathan et al. | Aug 2015 | A1 |
| 20150234493 | Parivar et al. | Aug 2015 | A1 |
| 20150253866 | Amm et al. | Sep 2015 | A1 |
| 20150268786 | Kitada | Sep 2015 | A1 |
| 20150268802 | Kim et al. | Sep 2015 | A1 |
| 20150268813 | Bos | Sep 2015 | A1 |
| 20150309573 | Brombach et al. | Oct 2015 | A1 |
| 20150321607 | Cho et al. | Nov 2015 | A1 |
| 20150332107 | Paniaras | Nov 2015 | A1 |
| 20150332607 | Gardner, Jr. et al. | Nov 2015 | A1 |
| 20150378519 | Brown et al. | Dec 2015 | A1 |
| 20150378982 | McKenzie et al. | Dec 2015 | A1 |
| 20150381931 | Uhma et al. | Dec 2015 | A1 |
| 20160004373 | Huang | Jan 2016 | A1 |
| 20160004393 | Faaborg et al. | Jan 2016 | A1 |
| 20160004427 | Zambetti et al. | Jan 2016 | A1 |
| 20160004428 | Bernstein et al. | Jan 2016 | A1 |
| 20160004430 | Missig et al. | Jan 2016 | A1 |
| 20160004431 | Bernstein et al. | Jan 2016 | A1 |
| 20160004432 | Bernstein et al. | Jan 2016 | A1 |
| 20160011725 | D'Argenio et al. | Jan 2016 | A1 |
| 20160011771 | Cieplinski | Jan 2016 | A1 |
| 20160019718 | Mukkamala et al. | Jan 2016 | A1 |
| 20160021511 | Jin et al. | Jan 2016 | A1 |
| 20160041750 | Cieplinski et al. | Feb 2016 | A1 |
| 20160048326 | Kim et al. | Feb 2016 | A1 |
| 20160062466 | Moussette et al. | Mar 2016 | A1 |
| 20160062619 | Reeve et al. | Mar 2016 | A1 |
| 20160070401 | Kim et al. | Mar 2016 | A1 |
| 20160077721 | Laubach et al. | Mar 2016 | A1 |
| 20160085385 | Gao et al. | Mar 2016 | A1 |
| 20160092071 | Lawson et al. | Mar 2016 | A1 |
| 20160124924 | Greenberg et al. | May 2016 | A1 |
| 20160125234 | Ota | May 2016 | A1 |
| 20160132139 | Du et al. | May 2016 | A1 |
| 20160188181 | Smith | Jun 2016 | A1 |
| 20160188186 | Yea | Jun 2016 | A1 |
| 20160196028 | Kenney et al. | Jul 2016 | A1 |
| 20160210025 | Bernstein et al. | Jul 2016 | A1 |
| 20160246478 | Davis et al. | Aug 2016 | A1 |
| 20160259412 | Flint et al. | Sep 2016 | A1 |
| 20160259413 | Anzures et al. | Sep 2016 | A1 |
| 20160259495 | Butcher et al. | Sep 2016 | A1 |
| 20160259496 | Butcher et al. | Sep 2016 | A1 |
| 20160259498 | Foss et al. | Sep 2016 | A1 |
| 20160259499 | Kocienda et al. | Sep 2016 | A1 |
| 20160259516 | Kudurshian et al. | Sep 2016 | A1 |
| 20160259517 | Butcher et al. | Sep 2016 | A1 |
| 20160259518 | King et al. | Sep 2016 | A1 |
| 20160259519 | Foss et al. | Sep 2016 | A1 |
| 20160259527 | Kocienda et al. | Sep 2016 | A1 |
| 20160259528 | Foss et al. | Sep 2016 | A1 |
| 20160259536 | Kudurshian et al. | Sep 2016 | A1 |
| 20160259548 | Ma | Sep 2016 | A1 |
| 20160274686 | Ruiz et al. | Sep 2016 | A1 |
| 20160274728 | Luo et al. | Sep 2016 | A1 |
| 20160274761 | Ruiz et al. | Sep 2016 | A1 |
| 20160283054 | Suzuki | Sep 2016 | A1 |
| 20160306507 | Defazio et al. | Oct 2016 | A1 |
| 20160320906 | Bokma et al. | Nov 2016 | A1 |
| 20160357368 | Federighi et al. | Dec 2016 | A1 |
| 20160357389 | Dakin et al. | Dec 2016 | A1 |
| 20160357390 | Federighi et al. | Dec 2016 | A1 |
| 20160357404 | Alonso Ruiz et al. | Dec 2016 | A1 |
| 20160360116 | Penha et al. | Dec 2016 | A1 |
| 20170045981 | Karunamuni et al. | Feb 2017 | A1 |
| 20170046039 | Karunamuni et al. | Feb 2017 | A1 |
| 20170046058 | Karunamuni et al. | Feb 2017 | A1 |
| 20170046059 | Karunamuni et al. | Feb 2017 | A1 |
| 20170046060 | Karunamuni et al. | Feb 2017 | A1 |
| 20170075520 | Bauer et al. | Mar 2017 | A1 |
| 20170075562 | Bauer et al. | Mar 2017 | A1 |
| 20170075563 | Bauer et al. | Mar 2017 | A1 |
| 20170090617 | Jang et al. | Mar 2017 | A1 |
| 20170090699 | Pennington et al. | Mar 2017 | A1 |
| 20170091153 | Thimbleby | Mar 2017 | A1 |
| 20170109011 | Jiang | Apr 2017 | A1 |
| 20170115867 | Bargmann | Apr 2017 | A1 |
| 20170123497 | Yonezawa | May 2017 | A1 |
| 20170124699 | Lane | May 2017 | A1 |
| 20170139565 | Choi | May 2017 | A1 |
| 20170315694 | Alonso Ruiz et al. | Nov 2017 | A1 |
| 20170357403 | Geary et al. | Dec 2017 | A1 |
| 20180024681 | Bernstein et al. | Jan 2018 | A1 |
| 20180059866 | Drake et al. | Mar 2018 | A1 |
| 20180082522 | Bartosik | Mar 2018 | A1 |
| 20180188920 | Bernstein et al. | Jul 2018 | A1 |
| 20180342103 | Schwartz et al. | Nov 2018 | A1 |
| 20180349362 | Sharp et al. | Dec 2018 | A1 |
| 20180364898 | Chen | Dec 2018 | A1 |
| 20190012059 | Kwon et al. | Jan 2019 | A1 |
| 20190018562 | Bernstein et al. | Jan 2019 | A1 |
| 20190042075 | Bernstein et al. | Feb 2019 | A1 |
| 20190042078 | Bernstein et al. | Feb 2019 | A1 |
| 20190065043 | Zambetti et al. | Feb 2019 | A1 |
| 20190121493 | Bernstein et al. | Apr 2019 | A1 |
| 20190121520 | Cieplinski et al. | Apr 2019 | A1 |
| 20190138101 | Bernstein | May 2019 | A1 |
| 20190138102 | Missig | May 2019 | A1 |
| 20190138189 | Missig | May 2019 | A1 |
| 20190146643 | Foss et al. | May 2019 | A1 |
| 20190155503 | Alonso Ruiz et al. | May 2019 | A1 |
| 20190158727 | Penha et al. | May 2019 | A1 |
| 20190163358 | Dascola et al. | May 2019 | A1 |
| 20190171353 | Missig et al. | Jun 2019 | A1 |
| 20190171354 | Dascola et al. | Jun 2019 | A1 |
| 20190212896 | Karunamuni et al. | Jul 2019 | A1 |
| 20190332257 | Kudurshian et al. | Oct 2019 | A1 |
| 20190364194 | Penha et al. | Nov 2019 | A1 |
| 20190391658 | Missig et al. | Dec 2019 | A1 |
| 20200081614 | Zambetti | Mar 2020 | A1 |
| 20200142548 | Karunamuni et al. | May 2020 | A1 |
| 20200201472 | Bernstein et al. | Jun 2020 | A1 |
| 20200210059 | Hu et al. | Jul 2020 | A1 |
| 20200218445 | Alonso Ruiz et al. | Jul 2020 | A1 |
| 20200301556 | Alonso Ruiz et al. | Sep 2020 | A1 |
| 20200333936 | Khoe et al. | Oct 2020 | A1 |
| 20200371683 | Zambetti et al. | Nov 2020 | A1 |
| 20200394413 | Bhanu | Dec 2020 | A1 |
| 20200396375 | Penha et al. | Dec 2020 | A1 |
| 20210081082 | Dascola et al. | Mar 2021 | A1 |
| 20210117054 | Karunamuni et al. | Apr 2021 | A1 |
| 20210191602 | Brown et al. | Jun 2021 | A1 |
| 20210191975 | Lu | Jun 2021 | A1 |
| 20210311598 | Bernstein et al. | Oct 2021 | A1 |
| 20210326039 | Alonso Ruiz et al. | Oct 2021 | A1 |
| 20210382613 | Kudurshian et al. | Dec 2021 | A1 |
| 20220011932 | Khoe et al. | Jan 2022 | A1 |
| 20220070359 | Clarke et al. | Mar 2022 | A1 |
| 20220129076 | Bernstein et al. | Apr 2022 | A1 |
| 20220187985 | Dascola et al. | Jun 2022 | A1 |
| 20220261131 | Bernstein et al. | Aug 2022 | A1 |
| 20220365671 | Bernstein et al. | Nov 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 2780765 | May 2011 | CA |
| 1356493 | Jul 2002 | CN |
| 1534991 | Jun 2004 | CN |
| 1620327 | May 2005 | CN |
| 1808362 | Jul 2006 | CN |
| 101068310 | Jul 2007 | CN |
| 101118469 | Feb 2008 | CN |
| 101192097 | Jun 2008 | CN |
| 101202866 | Jun 2008 | CN |
| 101222704 | Jul 2008 | CN |
| 101227764 | Jul 2008 | CN |
| 101241397 | Aug 2008 | CN |
| 101320303 | Dec 2008 | CN |
| 101356493 | Jan 2009 | CN |
| 101384977 | Mar 2009 | CN |
| 101390039 | Mar 2009 | CN |
| 101421707 | Apr 2009 | CN |
| 101464777 | Jun 2009 | CN |
| 101798979 | Aug 2009 | CN |
| 101526876 | Sep 2009 | CN |
| 101527745 | Sep 2009 | CN |
| 101562703 | Oct 2009 | CN |
| 101593077 | Dec 2009 | CN |
| 101609380 | Dec 2009 | CN |
| 101620507 | Jan 2010 | CN |
| 101627359 | Jan 2010 | CN |
| 101630230 | Jan 2010 | CN |
| 101685370 | Mar 2010 | CN |
| 101692194 | Apr 2010 | CN |
| 101727179 | Jun 2010 | CN |
| 101739206 | Jun 2010 | CN |
| 101763193 | Jun 2010 | CN |
| 101784981 | Jul 2010 | CN |
| 101809526 | Aug 2010 | CN |
| 101896962 | Nov 2010 | CN |
| 101937304 | Jan 2011 | CN |
| 101945212 | Jan 2011 | CN |
| 101971603 | Feb 2011 | CN |
| 101998052 | Mar 2011 | CN |
| 102004575 | Apr 2011 | CN |
| 102004576 | Apr 2011 | CN |
| 102004577 | Apr 2011 | CN |
| 102004593 | Apr 2011 | CN |
| 102004602 | Apr 2011 | CN |
| 102004604 | Apr 2011 | CN |
| 102016777 | Apr 2011 | CN |
| 102053790 | May 2011 | CN |
| 102067068 | May 2011 | CN |
| 102112946 | Jun 2011 | CN |
| 102150018 | Aug 2011 | CN |
| 102160021 | Aug 2011 | CN |
| 102171629 | Aug 2011 | CN |
| 102195514 | Sep 2011 | CN |
| 102203702 | Sep 2011 | CN |
| 102214038 | Oct 2011 | CN |
| 102223476 | Oct 2011 | CN |
| 102243662 | Nov 2011 | CN |
| 102257460 | Nov 2011 | CN |
| 102301322 | Dec 2011 | CN |
| 102349038 | Feb 2012 | CN |
| 102349040 | Feb 2012 | CN |
| 102354269 | Feb 2012 | CN |
| 102365666 | Feb 2012 | CN |
| 102375605 | Mar 2012 | CN |
| 102385478 | Mar 2012 | CN |
| 102388351 | Mar 2012 | CN |
| 102438092 | May 2012 | CN |
| 102483666 | May 2012 | CN |
| 102483677 | May 2012 | CN |
| 102546925 | Jul 2012 | CN |
| 102566908 | Jul 2012 | CN |
| 102576251 | Jul 2012 | CN |
| 102576282 | Jul 2012 | CN |
| 102625931 | Aug 2012 | CN |
| 102646013 | Aug 2012 | CN |
| 102662571 | Sep 2012 | CN |
| 102662573 | Sep 2012 | CN |
| 102722312 | Oct 2012 | CN |
| 102752441 | Oct 2012 | CN |
| 102792255 | Nov 2012 | CN |
| 102819331 | Dec 2012 | CN |
| 102819401 | Dec 2012 | CN |
| 102841677 | Dec 2012 | CN |
| 102880417 | Jan 2013 | CN |
| 103019586 | Apr 2013 | CN |
| 103092386 | May 2013 | CN |
| 103092406 | May 2013 | CN |
| 103097992 | May 2013 | CN |
| 103139473 | Jun 2013 | CN |
| 103186345 | Jul 2013 | CN |
| 103201714 | Jul 2013 | CN |
| 103268184 | Aug 2013 | CN |
| 103279295 | Sep 2013 | CN |
| 103390017 | Nov 2013 | CN |
| 103518176 | Jan 2014 | CN |
| 103562841 | Feb 2014 | CN |
| 103581544 | Feb 2014 | CN |
| 103620531 | Mar 2014 | CN |
| 103649885 | Mar 2014 | CN |
| 103699292 | Apr 2014 | CN |
| 103699295 | Apr 2014 | CN |
| 103777850 | May 2014 | CN |
| 103777886 | May 2014 | CN |
| 103793134 | May 2014 | CN |
| 103838465 | Jun 2014 | CN |
| 103870190 | Jun 2014 | CN |
| 103888661 | Jun 2014 | CN |
| 103970474 | Aug 2014 | CN |
| 103984501 | Aug 2014 | CN |
| 104011637 | Aug 2014 | CN |
| 104020868 | Sep 2014 | CN |
| 104020955 | Sep 2014 | CN |
| 104021021 | Sep 2014 | CN |
| 104024985 | Sep 2014 | CN |
| 104038838 | Sep 2014 | CN |
| 104077014 | Oct 2014 | CN |
| 104090979 | Oct 2014 | CN |
| 104142798 | Nov 2014 | CN |
| 104160362 | Nov 2014 | CN |
| 104205098 | Dec 2014 | CN |
| 104238904 | Dec 2014 | CN |
| 104267902 | Jan 2015 | CN |
| 104270565 | Jan 2015 | CN |
| 104331239 | Feb 2015 | CN |
| 104349124 | Feb 2015 | CN |
| 104392292 | Mar 2015 | CN |
| 104412201 | Mar 2015 | CN |
| 104471521 | Mar 2015 | CN |
| 104487928 | Apr 2015 | CN |
| 104487929 | Apr 2015 | CN |
| 104487930 | Apr 2015 | CN |
| 105264476 | Jan 2016 | CN |
| 100 59 906 | Jun 2002 | DE |
| 0 364178 | Apr 1990 | EP |
| 0 859 307 | Mar 1998 | EP |
| 0 880 090 | Nov 1998 | EP |
| 1 028 583 | Aug 2000 | EP |
| 1 406 150 | Apr 2004 | EP |
| 1 674 977 | Jun 2006 | EP |
| 1 882 902 | Jan 2008 | EP |
| 2 000 896 | Dec 2008 | EP |
| 2 017 701 | Jan 2009 | EP |
| 2 028 583 | Feb 2009 | EP |
| 2 112 586 | Oct 2009 | EP |
| 2 141 574 | Jan 2010 | EP |
| 2 175 357 | Apr 2010 | EP |
| 2 196 893 | Jun 2010 | EP |
| 2 214 087 | Aug 2010 | EP |
| 2 226 715 | Sep 2010 | EP |
| 2 284 675 | Feb 2011 | EP |
| 2 299 351 | Mar 2011 | EP |
| 2 302 496 | Mar 2011 | EP |
| 2 363 790 | Sep 2011 | EP |
| 2 375 309 | Oct 2011 | EP |
| 2 375 314 | Oct 2011 | EP |
| 2 386 935 | Nov 2011 | EP |
| 2 407 868 | Jan 2012 | EP |
| 2 420 924 | Feb 2012 | EP |
| 2 426 580 | Mar 2012 | EP |
| 2 445 182 | Apr 2012 | EP |
| 2 447 818 | May 2012 | EP |
| 2 527 966 | Nov 2012 | EP |
| 2 530 677 | Dec 2012 | EP |
| 2 541 376 | Jan 2013 | EP |
| 2 555 500 | Feb 2013 | EP |
| 2 615 535 | Jul 2013 | EP |
| 2 631 737 | Aug 2013 | EP |
| 2 674 834 | Dec 2013 | EP |
| 2 674 846 | Dec 2013 | EP |
| 2 708985 | Mar 2014 | EP |
| 2 733 578 | May 2014 | EP |
| 2 808 764 | Dec 2014 | EP |
| 2 809 058 | Dec 2014 | EP |
| 2 813 938 | Dec 2014 | EP |
| 3 664 092 | Jun 2020 | EP |
| 2 402 105 | Dec 2004 | GB |
| 58-182746 | Oct 1983 | JP |
| H06-161647 | Jun 1994 | JP |
| H07-098769 | Apr 1995 | JP |
| H07-104915 | Apr 1995 | JP |
| H07-151512 | Jun 1995 | JP |
| H08-227341 | Sep 1996 | JP |
| H09-269883 | Oct 1997 | JP |
| H09-330175 | Dec 1997 | JP |
| H11-203044 | Jul 1999 | JP |
| 2001-078137 | Mar 2001 | JP |
| 2001-202192 | Jul 2001 | JP |
| 2001-222355 | Aug 2001 | JP |
| 2001-306207 | Nov 2001 | JP |
| 2002-044536 | Feb 2002 | JP |
| 2002-149312 | May 2002 | JP |
| 3085481 | May 2002 | JP |
| 2002-182855 | Jun 2002 | JP |
| 2003-157131 | May 2003 | JP |
| 2003-186597 | Jul 2003 | JP |
| 2004-054861 | Feb 2004 | JP |
| 2004-062648 | Feb 2004 | JP |
| 2004-070492 | Mar 2004 | JP |
| 2004-078957 | Mar 2004 | JP |
| 2004-086733 | Mar 2004 | JP |
| 2004-120576 | Apr 2004 | JP |
| 2004-152217 | May 2004 | JP |
| 2004-288208 | Oct 2004 | JP |
| 2005-031786 | Feb 2005 | JP |
| 2005-092386 | Apr 2005 | JP |
| 2005-102106 | Apr 2005 | JP |
| 2005-135106 | May 2005 | JP |
| 2005-157842 | Jun 2005 | JP |
| 2005-196810 | Jul 2005 | JP |
| 2005-317041 | Nov 2005 | JP |
| 2005-352927 | Dec 2005 | JP |
| 2006-059238 | Mar 2006 | JP |
| 2006-185443 | Jul 2006 | JP |
| 2007-116384 | May 2007 | JP |
| 2007-148104 | Jun 2007 | JP |
| 2007-264808 | Oct 2007 | JP |
| 2008-009759 | Jan 2008 | JP |
| 2008-015890 | Jan 2008 | JP |
| 2008-033739 | Feb 2008 | JP |
| 2008-516348 | May 2008 | JP |
| 2008-146453 | Jun 2008 | JP |
| 2008-191086 | Aug 2008 | JP |
| 2008-537615 | Sep 2008 | JP |
| 2008-305174 | Dec 2008 | JP |
| 2009-500761 | Jan 2009 | JP |
| 2009-110243 | May 2009 | JP |
| 2009-129171 | Jun 2009 | JP |
| 2009-129443 | Jun 2009 | JP |
| 2009-169452 | Jul 2009 | JP |
| 2009-211704 | Sep 2009 | JP |
| 2009-217543 | Sep 2009 | JP |
| 2009-294688 | Dec 2009 | JP |
| 2009-545805 | Dec 2009 | JP |
| 2010-009321 | Jan 2010 | JP |
| 2010-503126 | Jan 2010 | JP |
| 2010-503130 | Jan 2010 | JP |
| 2010-055274 | Mar 2010 | JP |
| 2010-097353 | Apr 2010 | JP |
| 2010-146507 | Jul 2010 | JP |
| 2010-152716 | Jul 2010 | JP |
| 2010-176174 | Aug 2010 | JP |
| 2010-176337 | Aug 2010 | JP |
| 2010-181934 | Aug 2010 | JP |
| 2010-181940 | Aug 2010 | JP |
| 2010-198385 | Sep 2010 | JP |
| 2010-536077 | Nov 2010 | JP |
| 2010-541071 | Dec 2010 | JP |
| 2011-501307 | Jan 2011 | JP |
| 2011-028635 | Feb 2011 | JP |
| 2011-048023 | Mar 2011 | JP |
| 2011-048666 | Mar 2011 | JP |
| 2011-048686 | Mar 2011 | JP |
| 2011-048762 | Mar 2011 | JP |
| 2011-048832 | Mar 2011 | JP |
| 2011-053831 | Mar 2011 | JP |
| 2011-053972 | Mar 2011 | JP |
| 2011-053973 | Mar 2011 | JP |
| 2011-053974 | Mar 2011 | JP |
| 2011-054196 | Mar 2011 | JP |
| 2011-059821 | Mar 2011 | JP |
| 2011-070342 | Apr 2011 | JP |
| 2011-100290 | May 2011 | JP |
| 2011-107823 | Jun 2011 | JP |
| 2011-123773 | Jun 2011 | JP |
| 2011-141868 | Jul 2011 | JP |
| 2011-170538 | Sep 2011 | JP |
| 2011-192179 | Sep 2011 | JP |
| 2011-192215 | Sep 2011 | JP |
| 2011-197848 | Oct 2011 | JP |
| 2011-221640 | Nov 2011 | JP |
| 2011-232947 | Nov 2011 | JP |
| 2011-242386 | Dec 2011 | JP |
| 2011-250004 | Dec 2011 | JP |
| 2011-253556 | Dec 2011 | JP |
| 2011-257941 | Dec 2011 | JP |
| 2011-530101 | Dec 2011 | JP |
| 2012-027940 | Feb 2012 | JP |
| 2012-033061 | Feb 2012 | JP |
| 2012-043266 | Mar 2012 | JP |
| 2012-043267 | Mar 2012 | JP |
| 2012-053687 | Mar 2012 | JP |
| 2012-053754 | Mar 2012 | JP |
| 2012-053926 | Mar 2012 | JP |
| 2012-073785 | Apr 2012 | JP |
| 2012-073873 | Apr 2012 | JP |
| 2012-509605 | Apr 2012 | JP |
| 2012-093820 | May 2012 | JP |
| 2012-118825 | Jun 2012 | JP |
| 2012-118993 | Jun 2012 | JP |
| 2012-123564 | Jun 2012 | JP |
| 2012-128825 | Jul 2012 | JP |
| 2012-168620 | Sep 2012 | JP |
| 2012-212473 | Nov 2012 | JP |
| 2012-527685 | Nov 2012 | JP |
| 2013-025357 | Feb 2013 | JP |
| 2013-030050 | Feb 2013 | JP |
| 2013-058149 | Mar 2013 | JP |
| 2013-077270 | Apr 2013 | JP |
| 2013-080521 | May 2013 | JP |
| 2013-093020 | May 2013 | JP |
| 2013-098826 | May 2013 | JP |
| 2013-101465 | May 2013 | JP |
| 2013-105410 | May 2013 | JP |
| 2013-520727 | Jun 2013 | JP |
| 2013-131185 | Jul 2013 | JP |
| 2013-529339 | Jul 2013 | JP |
| 2013-200879 | Oct 2013 | JP |
| 2013-236298 | Nov 2013 | JP |
| 2013-542488 | Nov 2013 | JP |
| 2013-250602 | Dec 2013 | JP |
| 2014-504419 | Feb 2014 | JP |
| 2014-052852 | Mar 2014 | JP |
| 2014-130567 | Jul 2014 | JP |
| 2014-140112 | Jul 2014 | JP |
| 2014-149833 | Aug 2014 | JP |
| 2014-519109 | Aug 2014 | JP |
| 2014-529137 | Oct 2014 | JP |
| 2014-232347 | Dec 2014 | JP |
| 2015-099555 | May 2015 | JP |
| 2015-521315 | Jul 2015 | JP |
| 2015-153420 | Aug 2015 | JP |
| 2015-185161 | Oct 2015 | JP |
| 20020041828 | Jun 2002 | KR |
| 2006-0071353 | Jun 2006 | KR |
| 2006-0117870 | Nov 2006 | KR |
| 100807738 | Feb 2008 | KR |
| 20080026138 | Mar 2008 | KR |
| 2008-0045143 | Apr 2008 | KR |
| 100823871 | Apr 2008 | KR |
| 2008-0054346 | Jun 2008 | KR |
| 2009-0066319 | Jun 2009 | KR |
| 2009-0108065 | Oct 2009 | KR |
| 2010-0010860 | Feb 2010 | KR |
| 2010-0014095 | Feb 2010 | KR |
| 2010 0133246 | Dec 2010 | KR |
| 2011 0026176 | Mar 2011 | KR |
| 2011 0086501 | Jul 2011 | KR |
| 20120130972 | Jan 2012 | KR |
| 2012 0103670 | Sep 2012 | KR |
| 20120135488 | Dec 2012 | KR |
| 20120135723 | Dec 2012 | KR |
| 20130027017 | Mar 2013 | KR |
| 20130076397 | Jul 2013 | KR |
| 2013 0099647 | Sep 2013 | KR |
| 2014 0016495 | Feb 2014 | KR |
| 2014 0029720 | Mar 2014 | KR |
| 2014 0043760 | Apr 2014 | KR |
| 2014 0067965 | Jun 2014 | KR |
| 2014 0079110 | Jun 2014 | KR |
| 2014 0122000 | Oct 2014 | KR |
| 20150013263 | Feb 2015 | KR |
| 20150021977 | Mar 2015 | KR |
| 2007145218 | Jul 2009 | RU |
| 25036989 | Jan 2014 | RU |
| 201447740 | Dec 2014 | TW |
| WO 2005106637 | Nov 2005 | WO |
| WO 2006013485 | Feb 2006 | WO |
| WO 2006042309 | Apr 2006 | WO |
| WO 2006094308 | Sep 2006 | WO |
| WO 2007121557 | Nov 2007 | WO |
| WO 2008030976 | Mar 2008 | WO |
| WO 2008064142 | May 2008 | WO |
| WO 2009155981 | Dec 2009 | WO |
| WO 2009158549 | Dec 2009 | WO |
| WO 2010013876 | Feb 2010 | WO |
| WO 2010032598 | Mar 2010 | WO |
| WO 2010090010 | Aug 2010 | WO |
| WO 2010122813 | Oct 2010 | WO |
| WO 2010134729 | Nov 2010 | WO |
| WO 2011024389 | Mar 2011 | WO |
| WO 2011024465 | Mar 2011 | WO |
| WO 2011024521 | Mar 2011 | WO |
| WO 2011093045 | Aug 2011 | WO |
| WO 2011105009 | Sep 2011 | WO |
| WO 2011108190 | Sep 2011 | WO |
| WO 2011115187 | Sep 2011 | WO |
| WO 2011121375 | Oct 2011 | WO |
| WO 2012021417 | Feb 2012 | WO |
| WO 2012037664 | Mar 2012 | WO |
| WO 2012096804 | Jul 2012 | WO |
| WO 2012108213 | Aug 2012 | WO |
| WO 2012114760 | Aug 2012 | WO |
| WO 2012137946 | Oct 2012 | WO |
| WO 2012150540 | Nov 2012 | WO |
| WO 2012153555 | Nov 2012 | WO |
| WO 2013022486 | Feb 2013 | WO |
| WO 2013035725 | Mar 2013 | WO |
| WO 2013112453 | Aug 2013 | WO |
| WO 2013127055 | Sep 2013 | WO |
| WO 2013169302 | Nov 2013 | WO |
| WO 2013169845 | Nov 2013 | WO |
| WO 2013169846 | Nov 2013 | WO |
| WO 2013169849 | Nov 2013 | WO |
| WO 2013169851 | Nov 2013 | WO |
| WO 2013169853 | Nov 2013 | WO |
| WO 2013169854 | Nov 2013 | WO |
| WO 2013169870 | Nov 2013 | WO |
| WO 2013169875 | Nov 2013 | WO |
| WO 2013169877 | Nov 2013 | WO |
| WO 2013169882 | Nov 2013 | WO |
| WO 2013173838 | Nov 2013 | WO |
| WO 2014034706 | Mar 2014 | WO |
| WO 2014105275 | Jul 2014 | WO |
| WO 2014105276 | Jul 2014 | WO |
| WO 2014105277 | Jul 2014 | WO |
| WO 2014105278 | Jul 2014 | WO |
| WO 2014105279 | Jul 2014 | WO |
| WO 2014129655 | Aug 2014 | WO |
| WO 2014149473 | Sep 2014 | WO |
| WO 2014152601 | Sep 2014 | WO |
| WO 2014200733 | Dec 2014 | WO |
| WO 2013145804 | Dec 2015 | WO |
| WO 2016200584 | Dec 2016 | WO |
| Entry |
|---|
| Office Action, dated Mar. 2, 2023, received in Chinese Patent Application No. 202010281684.2, which corresponds with U.S. Appl. No. 14/864,601, 4 pages. |
| Office Action, dated Mar. 7, 2023, received in Brazilian Patent Application No. 11201701119-9, which corresponds with U.S. Appl. No. 14/871,236, 4 pages. |
| Office Action, dated Mar. 2, 2023, received in Indian Patent Application No. 202118003907, which corresponds with U.S. Appl. No. 16/243,834, 11 pages. |
| Final Office Action, dated Feb. 24, 2023, received in U.S. Appl. No. 16/896,141, 23 pages. |
| Office Action, dated Feb. 22, 2023, received in Chinese Patent Application No. 202010290361.X, hich corresponds with U.S. Appl. No. 17/003,869, 4 pages. |
| Notice of Allowance, dated Mar. 16, 2023, received in U.S. Appl. No. 17/351,035, 23 pages. |
| Notice of Allowance, dated Mar. 6, 2023, received in U.S. Appl. No. 17/524,692, 14 pages. |
| Office Action, dated Feb. 16, 2023, received in U.S. Appl. No. 17/728,909, 12 pages. |
| Agarwal, “How to Copy and Paste Text on Windows Phone 8,” Guiding Tech, http://web.archive.org/web20130709204246/http://www.guidingtech.com/20280/copy-paste-text-windows-phone-8/, Jul. 9, 2013, 10 pages. |
| Angelov, “Sponsor Flip Wall with Jquery & CSS”, Tutorialzine. N.p., Mar. 24, 2010. Web. http://tutorialzine.com/2010/03/sponsor-wall-slip-jquery-css/, Mar. 24, 2010, 8 pages. |
| Anonymous, “1-Click Installer for Windows Media Taskbar Mini-Player for Windows 7, 8, 8.1 10”, http://metadataconsulting.blogspot.de/2014/05/installer-for-windows-media-taskbar.htm, May 5, 2014, 6 pages. |
| Anonymous, “Acer Liquid Z5 Duo User's Manual”, https://global-download.acer.com, Feb. 21, 2014, 65 pages. |
| Anonymous, “Android—What Should Status Bar Toggle Button Behavior Be?”, https://ux.stackechange.com/questions/34814, Jan. 15, 2015, 2 pages. |
| Anonymous, “Google Android 5.0 Release Date, Specs and Editors Hands On Review—CNET”, http://www.cnet.com/products/google-an-android-5-0-lollipop/, Mar. 12, 2015, 10 pages. |
| Anonymous, “How Do I Add Contextual Menu to My Apple Watch App?”, http://www.tech-recipes.com/rx/52578/how-do-i-add-contextual-menu-to-my-apple-watch-app, Jan. 13, 2015, 3 pages. |
| Anonymous, “[new] WMP12 with Taskbar Toolbar for Windows 7—Windows Customization—WinMatrix”, http://www.winmatrix.com/forums/index/php?/topic/25528-new-wmp12-with-taskbar-toolbar-for-windows-7, Jan. 27, 2013, 6 pages. |
| Anonymous, “Nokia 808 PureView screenshots”, retrieved from Internet; no URL, Nov. 12, 2012, 8 pages. |
| Anonymous, “Nokia 808 PureView User Guide,” http://download-fds.webapps.microsoft.com/supportFiles/phones/files/pdf_guides/devices/808/Nokia_808_UG_en_APAC.pdf, Jan. 1, 2012, 144 pages. |
| Anonymous, “Notifications, Android 4.4 and Lower”, Android Developers, https://developer.android.com/design/patterns/notifications_k.html, May 24, 2015, 9 pages. |
| Anonymous, RX-V3800AV Receiver Owner's Manual, Yamaha Music Manuals, www.Manualslib.com, Dec. 31, 2007, 169 pages. |
| Anonymous, “Taskbar Extensions”, https://web.archive.org/web/20141228124434/http://msdn.microsoft.com:80/en-us/library/windows/desktop/dd378460(v=vs.85).aspx, Dec. 28, 2014, 8 pages. |
| Apple, “Final Cut Express 4 User Manual”, https://wsi.li.dl/mBGZWEQ8fh556f/, Jan. 1, 2007, 1,152 pages. |
| Apple, “Apple—September Event 2014”, https://www.youtube.com/watch?v=38lqQpqwPe7s, Sep. 10, 2014, 5 pages. |
| Azundris, “A Fire in the Pie,” http://web.archive.org/web/20140722062639/http://blog.azundrix.com/archives/168-A-fire-in-the-sky.html, Jul. 22, 2014, 8 pages. |
| Billibi, “Android 5.0 Lollipop”, https://www.bilibili.comvideo/av1636046?from=search&seid=3128140235778895126, Oct. 19, 2014, 6 pages. |
| B-log—betriebsraum weblog, “Extremely Efficient Menu Selection: Marking Menus for the Flash Platform,” http://www.betriebsraum.de/blog/2009/12/11/extremely-efficient-menu-selection-marking-for-the-flash-platform, Dec. 11, 2009, 9 pages. |
| Bognot, “Microsoft Windows 7 Aero Shake, Snap, and Peek”, https://www.outube.com/watch?v=vgD7wGrsQg4, Apr. 3, 2012, 4 pages. |
| Bolluyt, “5 Apple Watch Revelations from Apple's New WatchKit”, http://www.cheatsheet.com/tecnology/5-apple-watch-revelations-from-apples-new-watchkit.html/?a=viewall, Nov. 22, 2014, 3 pages. |
| Boring, “The Fat Thumb: Using the Thumb's Contact Size for Single-Handed Mobile Interaction”, https://www.youtube.com/watch?v=E9vGU5R8nsc&feature=youtu.be, Jun. 14, 2012, 2 pages. |
| Borowska, “6 Types of Digital Affordance that Impact Your Ux”, https://www.webdesignerdepot.com/2015/04/6-types-of-digital-affordance-that-implact-your-ux, Apr. 7, 2015, 6 pages. |
| Brewster, “The Design and Evaluation of a Vibrotactile Progress Bar”, Glasgow Interactive Systems Group, University of Glasgow, Glasgow, G12 8QQ, UK, 2005, 2 pages. |
| Brownlee, “Android 5.0 Lollipop Feature Review!”, https//www.youtube.com/watch?v=pEDQ1z1-PvU, Oct. 27, 2014, 5 pages. |
| Cheng, “iPhone 5: a little bit taller, a little bit baller”,https://arstechnica.com/gadgets/2012/09/iphone-5-a-little-bit-taller-a little-bit-baller, Oct. 14, 2021, 22 pages. |
| Clark, “Global Moxie, Touch Means a Renaissance for Radial Menus,” http://globalmoxie.com/blog/radial-menus-for-touch-ui˜print.shtml, Jul. 17, 2012, 7 pages. |
| Cohen, Cinemagraphs are Animated Gifs for Adults, http://www.tubefilter.com/2011/07/10/cinemagraph, Jul. 10, 2011, 3 pages. |
| CrackBerry Forums, Windows 8 Bezel Control and Gestures, http://wwwforums.crackberry.com/blackberry-playbook-f222/windows-8-bezel-control-gestures-705129/, Mar. 1, 2012, 8 pages. |
| Crook, “Microsoft Patenting Multi-Screen, Milti-Touch Gestures,” http://techcrunch.com/2011/08/25/microsoft-awarded-patents-for-multi-screen-multi-touch-gestures/, Aug. 25, 2011, 8 pages. |
| Cvil.ly—a design blog, Interesting Touch Interactions on Windows 8, http://cvil.ly/2011/06/04/interesting-touch-interactions-on-windows-8/, Jun. 4, 2011, 3 pages. |
| Davidson, et al., “Extending 2D Object Arrangement with Pressure-Sensitive Layering Cues”, Proceedings of the 21st Annual ACM Symposium on User Interface Software and Technology, Oct. 19, 2008, 4 pages. |
| Dinwiddie, et al., “Combined-User Interface for Computers, Television, Video Recorders, and Telephone, Etc”, IP.COM Journal, Aug. 1, 1990, 3 Pages. |
| Drinkwater, “Glossary: Pre/Post Alarm Image Buffer,” http://www.networkwebcams.com/ip-camera-learning-center/2008/07/17/glossary-prepost-alarm-image-buffer/, Jul. 17, 2008, 1 page. |
| Dzyre, “10 Android Notification Features You Can Fiddle With”, http://www.hongkiat.com/blog/android-notification-features, Mar. 10, 2014, 10 pages. |
| Easton-Ellett, “Three Free Cydia Utilities To Remove iOS Notification Badges”, http://www.ijailbreak.com/cydia/three-free-cydia-utilies-to-remove-ios-notification-badges, Apr. 14, 2012, 2 pages. |
| Elliot, “Mac System 7”, YouTube. Web. Mar. 8, 2017, http://www.youtube.com/watch?v=XLv22hfuuik, Aug. 3, 2011, 1 page. |
| Farshad, “SageThumbs-Preview And Convert Pictures From Windows Context Menu”, https://web.addictivetips.com/windows-tips/sagethumbs-preview-and-convert-photos-from-windows-context-menu, Aug. 8, 2011, 5 pages. |
| Fenlon, “The Case for Bezel Touch Gestures on Apple's iPad,” http://www.tested.com/tech/tablets/3104-the case-for-bezel-touch-gestures-on-apples-ipad/, Nov. 2, 2011, 6 pages. |
| Flaherty, “Is Apple Watch's Pressure-Sensitive Screen A Bigger Deal Than The Gadget Itself?”, http://www.wired.com/2014/09/apple-watchs-pressure-sensitive-screen-bigger-deal-gadget, Sep. 15, 2014, 3 pages. |
| Flixel, “Cinemagraph Pro For Mac”, https://flixel.com/products/mac/cinemagraph-pro, 2014, 7 pages. |
| Flowplayer, “Slowmotion: Flowplayer,” https://web.archive.org/web/20150226191526/http://flash.flowplayer.org/plugins/stre aming/slowmotion.html, Feb. 26, 2015, 4 pages. |
| Garcia-Hernandez et al., “Orientation Discrimination of Patterned Surfaces through an Actuated and Non-Actuated Tactile Display”, 2011 IEEE World Haptics Conference, Istanbul, Jun. 21-24, 2011, 3 pages. |
| Forlines, et al., “Glimpse: a Novel Input Model for Multi-level Devices”, Chi '05 Extended Abstracts on Human Factors in Computing Systems, Apr. 2, 2005, 4 pages. |
| Gardner, “Recenz—Recent Apps In One Tap”, You Tube, https://www.youtube.com/watch?v-qailSHRgsTo, May 15, 2015, 1 page. |
| Geisler, “Enriched Links: A Framework For Improving Web Navigation Using Pop-Up Views”, Journal of the American Society for Information Science, Chapel Hill, NC, Jan. 1, 2000, 13 pages. |
| Gonzalo et al., “Zliding: Fluid Zooming and Sliding for High Precision Parameter Manipulation”, Department of Computer Science, University of Toronto, Seattle, Washington, Oct. 23, 2005, 10 pages. |
| Google-Chrome, “Android 5.0 Lollipop”, http://androidlover.net/android-os/android-5-0-lollipop/android-5-0-lollipop-recent-apps-card-google-search.html, Oct. 19, 2014, 10 pages. |
| Grant, “Android's Notification Center”, https://www.objc.io/issues/11-android/android-notifications, Apr. 30, 2014, 26 pages. |
| Gurman, “Force Touch on iPhone 6S Revealed: Expect Shortcuts, Faster Actions, iOS”, 9To5Mac Aug. 10, 2015, 31 pages. |
| Henderson et al., “Opportunistic User Interfaces for Augmented Reality”, Department of Computer Science, New York, NY, Jan. 2010, 13 pages. |
| IBM et al., “Pressure-Sensitive Icons”, IBM Technical Disclosure Bulletin, vol. 33, No. 1B, Jun. 1, 1990, 3 pages. |
| ICIMS Recruiting Software, “Blackberry Playbook Review,” http://www.tested.com/tech.tablets/5749-blackberry-playbook-review/, 2015, 11 pages. |
| IPhonehacksTV, “Confero allows you to easily manage your Badge notifications—iPhone Hacks”, youtube, https://wwwyoutube.com/watch?v=JCk61pnL4SU, Dec. 26, 2014, 3 pages. |
| IPhoneOperator, “Wasser Liveeffekt fur Homescreen & Lockscreen—Aquaboard (Cydia)”, http://www.youtube.com/watch?v=fG9YMF-mBOQ, Sep. 22, 2012, 3 pages. |
| IPodHacks 142: “Water Ripple Effects On The Home and Lock Screen: AquaBoard Cydia Tweak Review”, YouTube, https://www.youtube.comwatch?v-Auu_uRaYHJs, Sep. 24, 2012, 3 pages. |
| Jauregui, “Design and Evaluation of 3D Cursors and Motion Parallax for the Exploration of Desktop Virtual Environments”, IEEE Symposium on 3D User Interfaces 2012, Mar. 4, 2012, 8 pages. |
| Jones, “Touch Screen with Feeling”, IEEE Spectrum, ,spectrum.ieee.org/commuting/hardware/touch-screens-with-feeling, May 1, 2009, 2 pages. |
| Kaaresoja, “Snap-Crackle-Pop: Tactile Feedback for Mobile Touch Screens,” Nokia Research Center, Helsinki, Finland, Proceedings of Eurohaptics vol. 2006, Jul. 3, 2006, 2 pages. |
| Kiener, “Force Touch on iPhone”, https://www.youtube.com/watch?v=CEMmnsU5fC8, Aug. 4, 2015, 4 pages. |
| Kleinman, “iPhone 6s Said to Sport Force Touch Display, 2GB of RAM”, https://www.technobuffalo.com/2015/01/15/iphone-6s-said-to-sport-force-touch-display-2gb-of-ram, Jan. 15, 2015, 2 pages. |
| Kost, “LR3-Deselect All Images But One”, Julieanne Kost's Blog, blogs.adobe.com/jkost/2011/12/lr3-deselect-all-images-but-one.html, Dec. 22, 2011, 1 page. |
| Kronfli, “HTC Zoe Comes To Google Play, Here's Everything You Need To Know,” Know Your Mobile, http://www.knowyourmobile.com/htc/htc-one/19550/what-htc-zoe, Aug. 14, 2014, 5 pages. |
| Kumar, “How to Enable Ripple Effect on Lock Screen of Galaxy S2”, YouTube, http, http://www.youtube.com/watch?v+B9-4M5abLXA, Feb. 12, 2013, 3 pages. |
| Kurdi, “XnView Shell Extension: A Powerful Image Utility Inside The Context Menu”, http://www.freewaregenius.com/xnview-shell-extension-a-powerful-image-utility-inside-the-context-menu, Jul. 30, 2008, 4 pages. |
| Laurie, “The Power of the Right Click,” http://vlaurie.com/right-click/customize-context-menu.html, 2002-2016, 3 pages. |
| MacKenzie et al., “The Tactile Touchpad”, Chi '97 Extended Abstracts on Human Factors in Computing Systems Looking to the Future, Chi '97, Mar. 22, 1997, 5 pages. |
| Mahdi, Confero now available in Cydia, brings a new way to manage Notification badges [Jailbreak Tweak], http://www.iphonehacks.com/2015/01/confero/tweak-manage-notification-badges.html, Jan. 1, 2015, 2 pages. |
| Matthew, “How to Preview Photos and Images From Right-Click Context Menue in Windows [Tip]”, http://www.dottech.org/159009/add-image-preview-in-windows-context-menu-tip, Jul. 4, 2014, 5 pages. |
| McGarry, “Everything You Can Do With Force Touch on Apple Watch”, Macworld, www.macworld.com, May 6, 2015, 4 pages. |
| McRitchie, “Internet Explorer Right-Click Menus,” http://web.archive.org/web-201405020/http:/dmcritchie.mvps.org/ie/rightie6.htm, May 2, 2014, 10 pages. |
| Microsoft, “Lumia—How to Personalize Your Start Screen”, https://www.youtube.com/watch?v=6GI5Z3TrSEs, Nov. 11, 2014, 3 pages. |
| Microsoft, “Use Radial Menus to Display Commands in OneNote for Windows 8,” https://support.office.com/en-us/article/Use-radial-menues-to-display-OneNote-commands-Od75f03f-cde7-493a-a8a0b2ed6f99fbe2, 2016, 5 pages. |
| Microsoft, “Windows 7 Aero Shake, Snap, and Peek”, hr.msu.edu.techtipshrsds/window 7 snappeekandshake.pdf, Apr. 4, 2012, 6 pages. |
| Minsky, “Computational Haptics The Sandpaper System for Synthesizing Texture for a Force-Feedback Display,” Massachusetts Institute of Technology, Jun. 1978, 217 pages. |
| Mitroff, “Google Android 5.0 Lollipop,” http://www.cnet.com/products/google-android-5-0-lollipop, Mar. 12, 2015, 5 pages. |
| Mohr, “Do Not Disturb—The iPhone Feature You Should Be Using”, http.www.wonderoftech.com/do-not-disturb-iphone, Jul. 14, 2014, 30 pages. |
| Nacca, “NiLS Lock Screen Notifications / Floating Panel—Review”, https://www.youtube.com/watch?v=McT4QnS9TDY, Feb. 3, 2014, 4 pages. |
| Neuburg, “Detailed Explanation iOS SDK”, Oreilly Japan, Dec. 22, 2014, vol. 4, P175-186, 15 pages. |
| Nickinson, How to Use Do Not Disturb on the HTC One M8, https://www.androidcentral.com/how-to-use-do-not-disturb-htc-one-m8, Apr. 7, 2014, 9 pages. |
| Nickinson, “Inside Android 4.2: Notifications and Quick Settings”, https://www.andrloidcentral.com/inside-android-42-notifications-and-quick-settings, Nov. 3, 2012, 3 pages. |
| Nikon, “Scene Recognition System and Advanced SRS,” http://www.nikonusa.com/en.Learn-And-Explore/Article/ftlzi4rr/Scene-Recognition-System.html, Jul. 22, 2015, 2 pages. |
| Nishino, “A Touch Screen Interface Design with Tactile Feedback”, Computer Science, 2011 International Conference on Complex, Intelligent, and Software Intensive Systems, 2011, 4 pages. |
| Ogino, “iOS 7 Design Standard”, Japan, Impress Japan Corporation, 1st edition, Nov. 21, 2013, 2 pages. |
| Oh, et al., “Moving Objects with 2D Input Devices in CAD Systems and Desktop Virtual Environments”, Proceedings of Graphics Interface 2005, 8 pages, May 2005. |
| O'Hara, et al., “Pressure-Sensitive Icons”, IP.COM Journal, IP.COM Inc., West Henrietta, NY, US, Jun. 1, 1990, 2 Pages. |
| Pallenberg, “Wow, the new iPad had gestures.” https://plus.google.com/+SaschaPallenberg/posts/aaJtJogu8ac, Mar. 7, 2012, 2 pages. |
| Phonebuff, “How To Pair Bluetooth On The iPhone”, https://www.youtube.com/watch?v=LudNwEar9A8, Feb. 8, 2012, 3 pages. |
| Plaisant et al., “Touchscreen Toggle Design”, Proceedings of CHI '92, pp. 667-668, May 3-7, 1992, 2 pages. |
| PoliceOne.com, “COBAN Technologies Pre-Event Buffer & Fail Safe Feature,” http://www.policeone.com/police-products/police-technology/mobile-computures/videos/5955587-COBAN-Technologies-Pre-Event, Nov. 11, 2010, 2 pages. |
| Pradeep, “Android App Development—Microsoft Awarded With Patents On Gestures Supported On Windows 8,” http://mspoweruser.com/microsoft-awarded-with-patents-on-gestures-supported-on-windows-8/, Aug. 25, 2011, 16 pages. |
| “Quickly Preview Songs in Windows Media Player 12 in Windows 7,” Quickly Preview Songs in Windows Media Player 12 in Windows 7. How-to Geek, Apr. 28, 2010, Web. May 8, 2010, http://web.archive.org/web/20100502013134/http://www.howtogeek.com/howto/16157/quickly-preview-songs-in-windows-media-center-12-in-windows-7>, 6 pages. |
| Quinn, et al., “Zoofing! Faster List Selections with Pressure-Zoom-Flick-Scrolling”, Proceedings of the 21st Annual Conference of the Australian Computer-Human Interaction Special Interest Group on Design, Nov. 23, 2009, ACM Press, vol. 411, 8 pages. |
| Rekimoto, et al., “PreSense: Interaction Techniques for Finger Sensing Input Devices”, Proceedings of the 16th Annual ACM Symposium on User Interface Software and Technology, Nov. 30, 2003, 10 pages. |
| Rekimoto, et al., “PreSensell: Bi-directional Touch and Pressure Sensing Interactions with Tactile Feedback”, Conference on Human Factors in Computing Systems Archive, ACM, Apr. 22, 2006, 6 pages. |
| Rekimoto, et al., “SmartPad: A Finger-Sensing Keypad for Mobile Interaction”, CHI 2003, Ft. Lauderdale, Florida, ACM 1-58113-637-Apr. 5-10, 2003, 2 pages. |
| Ritchie, “How to see all the unread message notifications on your iPhone, all at once, all in the same place | iMore”, https://www.imore.com/how-see-all-unread-message-notifications-your-iphone-all-once-all-same-place, Feb. 22, 2014, 2 pages. |
| Roth et al., “Bezel Swipe: Conflict-Free Scrolling and Miltiple Selection on Mobile Touch Screen Devices,” Chi 2009, Boston, Massachusetts, USA, Apr. 4-9, 2009, 4 pages. |
| Rubino et al., “How to Enable 'Living Images' on your Nokia Lumia with Windows Phone 8.1”, https://www.youtube.com/watch?v=RX7vpoFy1Dg, Jun. 6, 2014, 5 pages. |
| Sleepfreaks, “How to Easily Play/Loop an Event Range in Cubase”, https://sleepfreaks-dtm.com/for-advance-cubase/position-3/>, Apr. 4, 2011, 14 pages. |
| Sony, “Intelligent Scene Recognition,” https://www.sony-asia.com/article/252999/section/product/product/dsc-t77, downloaded on May 20, 2016, 5 pages. |
| Sood, “MultitaskingGestures”, http://cydia.saurik.com/package/org.thebigboxx.multitaskinggestures/, Mar. 3, 2014, 2 pages. |
| Stewart, et al., “Characteristics of Pressure-Based Input for Mobile Devices”, Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 2010, 10 pages. |
| Stross, “Wearing A Badge, and a Video Camera,” The New York Times, http://www.nytimes.com/2013/04/07/business/wearable-video-cameras-for-police-offers.html? R=0, Apr. 6, 2013, 4 pages. |
| Taser, “Taser Axon Body Camera User Manual,” https://www.taser.com/images/support/downloads/product-resourses/axon body_product_manual.pdf, Oct. 1, 2013, 24 pages. |
| Tidwell, “Designing Interfaces,” O'Reilly Media, Inc., USA, Nov. 2005, 348 pages. |
| Tweak, “QuickCenter—Add 3D-Touch Shortcuts to Control Center”, https://www.youtube.com/watch?v=8rHOFpGvZFM, Mar. 22, 2016, 2 pages. |
| Tweak, “iOS 10 Tweak on iOS 9.0.2 Jailbread & 9.2.1-9.3 Support: QuickCenter 3D, Touch Cydia Tweak!” https://wwwyoutube.com/watch?v=opOBr30_Fkl, Mar. 6, 2016, 3 pages. |
| UpDown-G, “Using Multiple Selection Mode in Android 4.0 / Getting Started”, https://techbooster.org/android/13946, Mar. 7, 2012, 7 pages. |
| VGJFeliz, “How to Master Android Lollipop Notifications in Four Minutes!”, https://www.youtube.com/watch?v=S-zBRG7GJgs, Feb. 8, 2015, 5 pages. |
| VisioGuy, “Getting a Handle on Selecting and Subselecting Visio Shapes”, http://www.visguy.com/2009/10/13/getting-a-handle-on-selecting-and-subselecting-visio-shapes/, Oct. 13, 2009, 18 pages. |
| Viticci, “Apple Watch: Our Complete Overview—MacStories”, https://www.macstories.net, Sep. 10, 2014, 21 pages. |
| Wikipedia, “AirDrop,”, Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/AirDrop, May 17, 2016, 5 pages. |
| Wikipedia, “Cinemagraph,” Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/Cinemagraph, Last Modified Mar. 16, 2016, 2 pages. |
| Wikipedia, “Context Menu,” Wikipedia, the free encyclopedia https://en.wikipedia.org/wiki/Context menu, Last Modified May 15, 2016, 4 pages. |
| Wikipedia, “HTC One (M7),” Wikipedia, the free encyclopedia, https://en.wikipedia.org/wiki/HTC_One_(M7), Mar. 2013, 20 pages. |
| Wikipedia, “Mobile Ad Hoc Network,” Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/Mobile_ad hoc_network, May 20, 2016, 4 pages. |
| Wikipedia, “Pie Menu,” Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/Pie_menu, Last Modified Jun. 4, 2016, 3 pages. |
| Wikipedia, “Quick Look,” from Wikipedia, the free encyclopedia, https;//en.wikipedia.org/wiki/Quick_Look, Last Modified Jan. 15, 2016, 3 pages. |
| Wikipedia, “Sony Xperia Z1”, Wikipedia, the free encyclopedia, https://enwikipedia.org/wiki/Sony_Experia_Z1, Sep. 2013, 10 pages. |
| Wilson, et al., “Augmenting Tactile Interaction with Pressure-Based Input”, School of Computing Science, Glasgow, UK, Nov. 15-17, 2011, 2 pages. |
| Yang, et al., “Affordance Application on Visual Interface Design of Desk-Top Virtual Experiments”, 2014 International Conference on Information Science, Electronics and Electrical Engineering, IEEE, vol. 1, Apr. 26, 2014, 5 pages. |
| Yatani, et al., SemFeel: A User Interface with Semantic Tactile Feedback for Mobile Touch-Screen Devices, Proceedings of the 22nd annual ACM symposium on user interface software and technology (UIST '09), Oct. 2009, 10 pages. |
| Youtube, “Android Lollipop Lock-Screen Notification Tips”, https://www.youtube.com/watch?v=LZTxHBOwzIU, Nov. 13, 2014, 3 pages. |
| Youtube, “Blackberry Playbook bezel interaction,” https://www.youtube.com/watch?v=YGkzFqnOwXI, Jan. 10, 2011, 2 pages. |
| Youtube, “How to Master Android Lollipop Notifications in Four Minutes!”, Video Gadgets Journal (VGJFelix), https://www.youtube.com/watch?v=S-zBRG7GGJgs, Feb. 8, 2015, 4 pages. |
| Youtube, “HTC One Favorite Camera Features”, http://www.youtube.com/watch?v=sUYHfcjl4RU, Apr. 28, 2013, 3 pages. |
| Youtube, “Multitasking Gestures: Zephyr Like Gestures on iOS”, https://www.youtube.com/watch?v=Jcod-f7Lw0I, Jan. 27, 2014, 3 pages. |
| Youtube, “Recentz—Recent Apps in A Tap”, https://www.youtube.com/watch?v=qailSHRgsTo, May 15, 2015, 1 page. |
| Zylom, “House Secrets”, http://game.zylom.com/servlet/Entry?g=38&s=19521&nocache=1438641323066, Aug. 3, 2015, 1 page. |
| Office Action, dated Mar. 15, 2017, received in U.S. Appl. No. 14/535,671, 13 pages. |
| Office Action, dated Nov. 30, 2017, received in U.S. Appl. No. 14/535,671, 21 pages. |
| Notice of Allowance, dated Sep. 5, 2018, received in U.S. Appl. No. 14/535,671, 5 pages. |
| Office Action, dated Jun. 29, 2017, received in U.S. Appl. No. 14/608,895, 30 pages. |
| Final Office Action, dated Feb. 22, 2018, received in U.S. Appl. No. 14/608,895, 20 pages. |
| Notice of Allowance, dated Jun. 26, 2018, received in U.S. Appl. No. 14/608,895, 9 pages. |
| Office Action, dated Dec. 18, 2015, received in Australian Patent Application No. 2013368440, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Oct. 18, 2016, received in Australian Patent Application No. 2013368440, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Notice of Allowance, dated Dec. 20, 2016, received in Australian Patent Application No. 2013368440, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Certificate of Grant, dated Apr. 29, 2017, received in Australian Patent Application No. 2013368440, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Nov. 6, 2017, received in Chinese Patent Application No. 201380068493.6, which corresponds with U.S. Appl. No. 14/608,895, 5 pages. |
| Office Action, dated Oct. 9, 2018, received in Chinese U.S. Appl. No. 201380068493.6, which corresponds with U.S. Appl. No. 14/608,895, 3 pages. |
| Patent, dated Dec. 25, 2018, received in Chinese Patent Application No. 201380068493.6, which corresponds with U.S. Appl. No. 14/608,895, 4 pages. |
| Office Action, dated Jul. 21, 2016, received in European Patent Application No. 13795391.5, which corresponds with U.S. Appl. No. 14/536,426, 9 pages. |
| Office Action, dated Mar. 9, 2018, received in European Patent Application No. 13795391.5, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Intention to Grant, dated Jul. 6, 2018, received in European Patent Application No. 13795391.5, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Certificate of Grant, dated Dec. 26, 2018, received in European Patent Application No. 13795391.5, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Office Action, dated Sep. 13, 2016, received in Japanese Patent Application No. 2015-547948, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Patent, dated May 12, 2017, received in Japanese Patent Application No. 2015-547948, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Apr. 5, 2016, received in Korean Patent Application No. 10-2015-7018851, which corresponds with U.S. Appl. No. 14/536,426, 7 pages. |
| Office Action, dated Feb. 24, 2017, received in Korean Patent Application No. 10-2015-7018851, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Patent, dated May 26, 2017, received in Korean Patent Application No. 2015-7018851, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Oct. 5, 2018, received in Korean Patent Application No. 2018-7028236, which corresponds with U.S. Appl. No. 14/608,895, 6 pages. |
| Notice of Allowance, dated May 24, 2019, received in Korean Patent Application No. 2018-7028236, which corresponds with U.S. Appl. No. 14/608,895, 4 pages. |
| Patent, dated Jul. 9, 2019, received in Korean Patent Application No. 2018-7028236, which corresponds with U.S. Appl. No. 14/608,895, 4 pages. |
| Office Action, dated Jul. 26, 2017, received in U.S. Appl. No. 14/536,235, 14 pages. |
| Final Office Action, dated Feb. 26, 2018, received in U.S. Appl. No. 14/536,235, 13 pages. |
| Notice of Allowance, dated Aug. 15, 2018, received in U.S. Appl. No. 14/536,235, 5 pages. |
| Office Action, dated Apr. 5, 2017, received in U.S. Appl. No. 14/536,367, 16 pages. |
| Notice of Allowance, dated Nov. 30, 2017, received in U.S. Appl. No. 14/536,367, 9 pages. |
| Notice of Allowance, dated May 16, 2018, received in U.S. Appl. No. 14/536,367, 5 pages. |
| Office Action, dated Dec. 17, 2015, received in U.S. Appl. No. 14/536,426, 28 pages. |
| Final Office Action, dated May 6, 2016, received in U.S. Appl. No. 14/536,426, 23 pages. |
| Office action, dated Aug. 3, 2017, received in U.S. Appl. No. 14/536,426, 10 pages. |
| Office Action, dated Jul. 15, 2015, received in Australian Patent Application No. 2013259606, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Notice of Allowance, dated May 23, 2016, received in Australian Patent Application No. 2013259606, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Certificate of Grant, dated Sep. 15, 2016, received in Australian Patent Australian No. 2013259606, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
| Office Action, dated Nov. 18, 2015, received in Australian Patent Application No. 2015101231, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated May 15, 2017, received in Australian Patent Application No. 2016216580, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated May 8, 2018, received in Australian Patent Application No. 2016216580, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Notice of Allowance, dated May 17, 2018, received in Australian Patent Application No. 2016216580, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Certificate of Grant, dated Sep. 13, 2018, received in Australian Patent Application No. 2016216580, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
| Office Action, dated Apr. 12, 2019, received in Australian Patent Application No. 2018223021, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Nov. 18, 2019, received in Australian Patent Application No. 2018223021, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Feb. 18, 2020, received in Australian Patent Application No. 2018223021, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Notice of Allowance, dated Mar. 27, 2020, received in Australian Patent Application No. 2018223021, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Certificate of Grant, dated Jul. 23, 2020, received in Australian Patent Application No. 2018223021, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Office Action, dated Sep. 19, 2017, received in Chinese Patent Application No. 201380035982.1, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Notice of Allowance, dated May 10, 2018, received in Chinese Patent Application No. 201380035982.1, which corresponds with U.S. Appl. No. 14/536,426, 2 pages. |
| Patent, dated Aug. 17, 2018, received in Chinese Patent Application No. 201380035982.1, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Office Action, dated Sep. 20, 2017, received in Chinese Patent Application No. 201510566550.4, which corresponds with U.S. Appl. No. 14/536,426, 11 pages. |
| Notice of Allowance, dated Aug. 8, 2018, received in Chinese Patent Application No. 201510566550.4, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Patent, dated Oct. 23, 2018, received in Chinese Patent Application No. 201510566550.4, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Office Action, dated Jan. 4, 2021, received in Chinese Patent Application No. 201810826224.6, which corresponds with U.S. Appl. No. 14/536,426, 6 pages. |
| Office Action, dated Jun. 24, 2021, received in Chinese Patent Application No. 201810826224.6, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Notice of Allowance, dated Oct. 11, 2021, received in Chinese Patent Application No. 201810826224.6, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
| Patent, dated Nov. 12, 2021, received in Chinese Patent Application No. 201810826224.6, which corresponds with U.S. Appl. No. 14/536,426, 7 pages. |
| Decision to Grant, dated Jul. 14, 2016, received in European Patent Application No. 13724100.6, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
| Letters Patent, dated Aug. 10, 2016, received in European Patent Application No. 13724100.6, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
| Office Action, dated Jan. 20, 2017, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Office Action, dated Aug. 21, 2017, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Intention to Grant, dated Mar. 9, 2018, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Intention to Grant, dated Aug. 14, 2018, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Decision to Grant, dated Jan. 10, 2019, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Patent, dated Feb. 6, 2019, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 4 pages. |
| Office Action, dated Sep. 6, 2019, received in European Patent Application No. 18180503.7, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Certificate of Grant, dated Nov. 10, 2017, received in Hong Kong Patent Application No. 15107535.0, which corresponds with U.S. Appl. No. 14/536,426, 2 pages. |
| Certificate of Grant, dated Jul. 5, 2019, received in Hong Kong Patent Application No. 15108892.5, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Patent, dated Nov. 22, 2019, received in Hong Kong Patent Application No. 16107033.6, which corresponds with U.S. Appl. No. 14/536,426, 6 pages. |
| Office Action, dated Mar. 4, 2016, received in Japanese Patent Application No. 2015-511644, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Feb. 6, 2017, received in Japanese Patent Application No. 2015-511644, which corresponds with U.S. Appl. No. 14/536,426, 6 pages. |
| Notice of Allowance, dated Dec. 8, 2017, received in Japanese Patent Application No. 2015-511644, which corresponds with U.S. Appl. No. 14/536,426, 6 pages. |
| Patent, dated Jan. 12, 2018, received in Japanese Patent Application No. 2015-511644, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
| Office Action, dated Nov. 6, 2018, received in Japanese Patent Application No. 2018-000753 (5842JP01), which corresponds with U.S. Appl. No. 14/536,426, 8 pages. |
| Office Action, dated Oct. 7, 2019, received in Japanese Patent Application No. 2018-000753, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
| Office Action, dated Feb. 8, 2021, received in Japanese Patent Application No. 2018-000753, which corresponds with U.S. Appl. No. 14/536,426, 2 pages. |
| Office Action, dated Mar. 9, 2017, received in U.S. Appl. No. 14/536,464, 21 pages. |
| Final Office Action, dated Aug. 25, 2017, received in U.S. Appl. No. 14/536,464, 30 pages. |
| Office Action, dated Feb. 12, 2018, received in U.S. Appl. No. 14/536,464, 33 pages. |
| Final Office Action, dated Jun. 22, 2018, received in U.S. Appl. No. 14/536,464, 32 pages. |
| Notice of Allowance, dated Jan. 25, 2021, received in U.S. Appl. No. 14/536,464, 5 pages. |
| Notice of Allowance, dated Feb. 23, 2021, received in U.S. Appl. No. 14/536,464, 5 pages. |
| Office Action, dated Sep. 25, 2017, received in U.S. Appl. No. 14/536,644, 29 pages. |
| Final Office Action, dated May 3, 2018, received in U.S. Appl. No. 14/536,644, 28 pages. |
| Office Action, dated Nov. 2, 2018, received in U.S. Appl. No. 14/536,644, 24 pages. |
| Notice of Allowance, dated Jul. 2, 2019, received in U.S. Appl. No. 14/536,644, 5 pages. |
| Office Action, dated Oct. 19, 2017, received in U.S. Appl. No. 14/608,926, 14 pages. |
| Final Office Action, dated Jun. 6, 2018, received in U.S. Appl. No. 14/608,926, 19 pages. |
| Notice of Allowance, dated Apr. 10, 2019, received in U.S. Appl. No. 14/608,926, 16 pages. |
| Notice of Allowance, dated May 21, 2019, received in U.S. Appl. No. 14/608,926, 5 pages. |
| Office Action, dated Feb. 1, 2016, received in Australian Patent Application No. 2013368441, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Notice of Allowance, dated Mar. 30, 2016, received in Australian Patent Application No. 2013368441, which corresponds with U.S. Appl. No. 14/608,926, 1 page. |
| Certificate of Grant, dated Jul. 29, 2016, received in Australian Patent Application No. 2013368441, which corresponds with U.S. Appl. No. 14/608,926, 1 page. |
| Office Action, dated Jan. 3, 2017, received in Australian Patent Application No. 2016201451, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Notice of Acceptance, dated Dec. 20, 2017, received in Australian Patent Application No. 2016201451, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Certificate of Grant, dated May 3, 2018, received in Australian Patent Application No. 2016201451, which corresponds with U.S. Appl. No. 14/608,926, 1 page. |
| Office Action, dated May 4, 2017, received in Chinese Patent Application No. 201380068414.4, which corresponds with U.S. Appl. No. 14/608,926, 5 pages. |
| Notice of Allowance, dated Feb. 8, 2018, received in Chinese Patent Application No. 201380068414.1, which corresponds with U.S. Appl. No. 14/608,926, 2 pages. |
| Patent, dated May 4, 2018, received in Chinese Patent Application No. 201380068414.4, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Office Action, dated Dec. 1, 2020, received in Chinese Patent Application No. 201810369259.1, which corresponds with U.S. Appl. No. 14/608,926, 14 pages. |
| Office Action, dated Jul. 14, 2021, received in Chinese Patent Application No. 201810369259.1, which corresponds with U.S. Appl. No. 14/608,926, 5 pages. |
| Office Action, dated Jan. 10, 2022, received in Chinese Patent Application No. 201810369259.1, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Office Action, dated Apr. 21, 2016, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 6 pages. |
| Office Action, dated May 6, 2016, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 6 pages. |
| Office Action, dated Nov. 11, 2016, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 6 pages. |
| Office Action, dated Jul. 4, 2017, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Oral Summons, dated Feb. 13, 2017, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 11 pages. |
| Intent to Grant, dated May 11, 2022, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 7 pages. |
| Decision to Grant, dated Jun. 17, 2022, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 7 pages. |
| Patent, dated Jul. 13, 2022, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Office Action, dated Mar. 14, 2016, received in Japanese Patent Application No. 2015-549392, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Notice of Allowance, dated Jan. 17, 2017, received in Japanese Patent Application No. 2015-549392, which corresponds with U.S. Appl. No. 14/608,926, 2 pages. |
| Patent, dated Feb. 17, 2017, received in Japanese Patent Application No. 2015-549392, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Patent, dated Apr. 27, 2018, received in Japanese Patent Application No. 2017-024234, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Office Action, dated Feb. 22, 2019, received in Japanese Patent Application No. 2018-079290, which corresponds with U.S. Appl. No. 14/608,926, 7 pages. |
| Office Action, dated Sep. 30, 2019, received in Japanese Patent Application No. 2018-079290, which corresponds with U.S. Appl. No. 14/608,926, 5 pages. |
| Notice of Allowance, dated Apr. 3, 2020, received in Japanese Patent Application No. 2018-079290, which corresponds with U.S. Appl. No. 14/608,926, 5 pages. |
| Patent, dated Apr. 14, 2020, received in Japanese Patent Application No. 2018-079290, which corresponds with U.S. Appl. No. 14/608,926, 5 pages. |
| Office Action, dated May 12, 2016, received in Korean Patent Application No. 10-2015-7018853, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Notice of Allowance, dated Mar. 31, 2017, received in Korean Patent Application No. 2015-7018853, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
| Patent, dated Jun. 30, 2017, received in Korean Patent Application No. 2015-7018853, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Office Action, dated Aug. 22, 2017, received in Korean Patent Application No. 2017-7018250, which corresponds with U.S. Appl. No. 14/608,926, 2 pages. |
| Notice of Allowance, dated Dec. 29, 2017, received in Korean Patent Application No. 2017-7018250, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
| Office Action, dated Oct. 19, 2017, received in U.S. Appl. No. 14/536,646, 21 pages. |
| Notice of Allowance, dated Aug. 9, 2018, received in U.S. Appl. No. 14/536,646, 5 pages. |
| Office Action, dated Jul. 17, 2015, received in Australian Patent Application No. 2013259613, which corresponds with U.S. Appl. No. 14/536,646, 5 pages. |
| Office Action, dated May 31, 2016, received in Australian Patent Application No. 2013259613, which corresponds with U.S. Appl. No. 14/536,646, 4 pages. |
| Notice of Allowance, dated Jul. 5, 2016, received in Australian Patent Application No. 2013259613, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
| Office Action, dated Jun. 6, 2019, received in Australian Patent Application No. 2018256626, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
| Notice of Acceptance, dated Aug. 1, 2019, received in Australian Patent Application No. 2018256626, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
| Certificate of Grant, dated Dec. 5, 2019, received in Australian Patent Application No. 2018256626, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
| Office Action, dated Dec. 1, 2016, received in Chinese Patent Application No. 2013800362059, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
| Notice of Allowance, dated Oct. 9, 2017, received in Chinese Patent Application No. 2013800362059, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
| Office Action, dated Jul. 3, 2020, received in Chinese Patent Application No. 201711425148.X, which corresponds with U.S. Appl. No. 14/536,646, 13 pages. |
| Office Action, dated Jun. 10, 2021, received in Chinese Patent Application No. 201711425148.X, which corresponds with U.S. Appl. No. 14/536,646, 2 pages. |
| Notice of Allowance, dated Oct. 9, 2021, received in Chinese Patent Application No. 201711425148.X, which corresponds with U.S. Appl. No. 14/536,646, 2 pages. |
| Office Action, dated Oct. 26, 2020, received in Chinese Patent Application No. 201711422092.2, which corresponds with U.S. Appl. No. 14/536,646, 20 pages. |
| Notice of Allowance, dated Mar. 22, 2021, received in Chinese Patent Application No. 201711422092.2, which corresponds with U.S. Appl. No. 14/536,646, 2 pages. |
| Certificate of Grant, dated Apr. 13, 2021, received in Chinese Patent Application No. 201711422092.2, which corresponds with U.S. Appl. No. 14/536,646, 8 pages. |
| Office Action, dated Nov. 12, 2015, received in European Patent Application No. 13724102.2, which corresponds with U.S. Appl. No. 14/536,646, 6 pages. |
| Office Action, dated May 31, 2016, received in European Patent Application No. 13724102.2, which corresponds with U.S. Appl. No. 14/536,646, 5 pages. |
| Notice of Allowance, dated Jan. 4, 2017, received in European Patent Application No. 13724102.2, which corresponds with U.S. Appl. No. 14/536,646, 5 pages. |
| Patent, dated May 26, 2017, received in European Patent Application No. 13724102.2, which corresponds with U.S. Appl. No. 14/536,646, 1 page. |
| Office Action, dated Feb. 29, 2016, received in Japanese Patent Application No. 2015-511645, which corresponds with U.S. Appl. No. 14/536,646, 5 pages. |
| Notice of Allowance, dated Dec. 22, 2016, received in Japanese Patent Application No. 2015-511645, which corresponds with U.S. Appl. No. 14/536,646, 2 pages. |
| Certificate of Grant, dated Jan. 25, 2019, received in Hong Kong Patent Application No. 2015-511645, which corresponds with U.S. Appl. No. 14/536,646, 4 pages. |
| Office Action, dated Apr. 3, 2017, received in U.S. Appl. No. 14/536,141, 11 pages. |
| Notice of Allowance, dated Sep. 20, 2017, received in U.S. Appl. No. 14/536,141, 10 pages. |
| Office Action, dated Aug. 27, 2015, received in Australian Patent Application No. 2013259614, which corresponds with U.S. Appl. No. 14/536,141, 4 pages. |
| Notice of Allowance, dated Aug. 15, 2016, received in Australian Patent Application No. 2013259614, which corresponds with U.S. Appl. No. 14/536,141, 1 page. |
| Office Action, dated Jul. 21, 2017, received in Australian Patent Application No. 2016262773, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Notice of Acceptance, dated Jul. 19, 2018, received in Australian Patent Application No. 2016262773, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Office Action, dated Jun. 5, 2019, received in Australian Patent Application No. 2018256616, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Notice of Acceptance, dated Jan. 22, 2020, received in Australian Patent Application No. 2018256616, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Certificate of Grant, dated May 21, 2020, received in Australian Patent Application No. 2018256616, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Office Action, dated Mar. 3, 2017, received in Chinese Patent Application No. 201380035893.7, which corresponds with U.S. Appl. No. 14/536,141, 8 pages. |
| Office Action, dated Feb. 2, 2018, received in Chinese Patent Application No. 201380035893.7, which corresponds with U.S. Appl. No. 14/536,141, 5 pages. |
| Notice of Allowance, dated Aug. 31, 2018, received in Chinese Patent Application No. 201380035893.7, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Office Action, dated Mar. 10, 2021, received in Chinese Patent Application No. 201811142423.1, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Office Action, dated Aug. 12, 2021, received in Chinese Patent Application No. 201811142423.1, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Notice of Allowance, dated Oct. 26, 2021, received in Chinese Patent Application No. 201811142423.1, which corresponds with U.S. Appl. No. 14/536,141, 2 pages. |
| Patent, dated Dec. 31, 2021, received in Chinese Patent Application No. 201811142423.1, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Patent, dated Oct. 23, 2018, received in Chinese Patent Application No. 201380035893.7, which corresponds with U.S. Appl. No. 14/536,141, 4 pages. |
| Office Action, dated Jan. 7, 2016, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 10 pages. |
| Office Action, dated Aug. 31, 2016, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 10 pages. |
| Office Action, dated Apr. 9, 2018, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 9 pages. |
| Office Action, dated Mar. 7, 2019, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 5 pages. |
| Intention to Grant, dated Sep. 6, 2019, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 7 pages. |
| Decision to Grant, dated Jan. 23, 2020, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 1 page. |
| Patent, dated Feb. 19, 2020, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 4 page. |
| Office Action, dated Feb. 29, 2016, received in Japanese Patent Application No. 2015-511646, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Office Action, dated Oct. 25, 2016, received in Japanese Patent Application No. 2015-511646, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Notice of Allowance, dated Jun. 30, 2017, received in Japanese Patent Application No. 2015-511646, which corresponds with U.S. Appl. No. 14/536,141, 5 pages. |
| Patent, dated Jul. 28, 2017, received in Japanese Patent Application No. 2015-511646, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
| Office Action, dated Aug. 10, 2018, received in Japanese Patent Application No. 2017-141953, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Office Action, dated Jul. 5, 2019, received in Japanese Patent Application No. 2017-141953, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
| Office Action, dated Dec. 8, 2016, received in U.S. Appl. No. 14/608,942, 9 pages. |
| Notice of Allowance, dated May 12, 2017, received in U.S. Appl. No. 14/608,942, 10 pages. |
| Office Action, dated Jan. 29, 2016, received in Australian Patent Application No. 2013368443, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Notice of Allowance, dated Mar. 11, 2016, received in Australian Patent Application No. 2013368443, which corresponds with U.S. Appl. No. 14/608,942, 2 pages. |
| Certificate of Grant, dated Jul. 7, 2016, received in Australian Patent Application No. 2013368443, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Office Action, dated Mar. 29, 2017, received in Australian patent Application No. 2016201303, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Notice of Acceptance, dated Mar. 7, 2018, received in Australian patent Application No. 2016201303, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Certificate of Grant, dated Jul. 5, 2018, received in Australian patent Application No. 2016201303, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Office Action, dated Jun. 16, 2017, received in Chinese Patent Application No. 201380068295.X, which corresponds with U.S. Appl. No. 14/608,942, 6 pages. |
| Office Action, dated Mar. 28, 2018, received in Chinese Patent Application No. 201380068295.X, which corresponds with U.S. Appl. No. 14/608,942, 5 pages. |
| Office Action, dated Oct. 8, 2018, received in Chinese Patent Application No. 201380068295.X, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Notice of Allowance, dated May 7, 2019, received in Chinese Patent Application No. 201380068295.X, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Patent, dated Jul. 5, 2019, received in Chinese Patent Application No. 201380068295.X, which corresponds with U.S. Appl. No. 14/608,942, 8 pages. |
| Office Action, dated Oct. 7, 2016, received in European Patent Application No. 13798464.7, which corresponds with U.S. Appl. No. 14/608,942, 7 pages. |
| Decision to Grant, dated Sep. 13, 2018, received in European Patent Application No. 13798464.7, which corresponds with U.S. Appl. No. 14/608,942, 2 pages. |
| Intention to Grant, dated Nov. 8, 2019, received in European Patent Application No. 18194127.9, which corresponds with U.S. Appl. No. 14/608,942, 7 pages. |
| Decision to Grant, dated Aug. 20, 2020, received in European Patent Application No. 18194127.9, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Patent, dated Sep. 16, 2020, received in European Patent Application No. 18194127.9, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Certificate of Grant, dated Jul. 26, 2019, received in Hong Kong, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Office Action, dated Jul. 4, 2016, received in Japanese Patent Application No. 2015-549393, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Notice of Allowance, dated May 12, 2017, received in Japanese Patent Application No. 2015-549393, which corresponds with U.S. Appl. No. 14/608,942, 5 pages. |
| Patent, dated Jun. 16, 2017, received in Japanese Patent Application No. 2015-549393, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
| Office Action, dated Apr. 5, 2016, received in Korean Patent Application No. 2015-7018448, which corresponds with U.S. Appl. No. 14/608,942, 6 pages. |
| Office Action, dated Feb. 24, 2017, received in Korean Patent Application No. 2015-7018448, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Notice of Allowance, dated Jan. 15, 2019, received in Korean Patent Application No. 2015-7018448, which corresponds with U.S. Appl. No. 14/608,942, 5 pages. |
| Patent, dated Mar. 8, 2019, received in Korean Patent Application No. 2015-7018448, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
| Office Action, dated Jul. 17, 2017, received in U.S. Appl. No. 14/536,166, 19 pages. |
| Notice of Allowance, dated Feb. 28, 2018, received in U.S. Appl. No. 14/536,166, 5 pages. |
| Office Action, dated Aug. 1, 2016, received in U.S. Appl. No. 14/536,203, 14 pages. |
| Notice of Allowance, dated Feb. 1, 2017, received in U.S. Appl. No. 14/536,203, 9 pages. |
| Office Action, dated Jul. 9, 2015, received in Australian Patent Application No. 2013259630, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Notice of Allowance, dated Jun. 15, 2016, received in Australian Patent Application No. 2013259630, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Certificate of Grant, dated Oct. 21, 2016, received in Australian Patent Application No. 2013259630, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Office Action, dated Jul. 4, 2017, received in Australian Patent Application No. 2016238917, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Notice of Acceptance, dated Jul. 19, 2018, received in Australian Patent Application No. 2016238917, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Certificate of Grant, dated Nov. 1, 2018, received in Australian Patent Application No. 2016238917, which corresponds with U.S. Appl. No. 14/536,203, 1 page. |
| Office Action, dated Aug. 20, 2018, received in Australian Patent Application No. 2018250481, which corresponds with U.S. Appl. No. 14/536,203, 2 pages. |
| Notice of Allowance, dated Apr. 29, 2020, received in Australian Patent Application No. 2018250481, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Certificate of Grant, dated Sep. 3, 2020, received in Australian Patent Application No. 2018250481, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Office Action, dated Oct. 25, 2017, received in Chinese Patent Application No. 201380035977.0, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Notice of Allowance, dated Apr. 4, 2018, received in Chinese Patent Application No. 201380035977.0, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Patent, dated Jul. 6, 2018, received in Chinese Patent Application No. 201380035977.0, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Office Action, dated Jan. 26, 2021, received in Chinese Patent Application No. 201810632507.7, 5 pages. |
| Notice of Allowance, dated Aug. 11, 2021, received in Chinese Patent Application No. 201810632507.7, which corresponds with U.S. Appl. No. 14/536,203, 1 page. |
| Patent, dated Oct. 22, 2021, received in Chinese Patent Application No. 201810632507.7, which corresponds with U.S. Appl. No. 14/536,203, 7 pages. |
| Office Action, dated Nov. 11, 2015, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Office Action, dated May 31, 2016, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Office Action, dated Dec. 6, 2017, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 9 pages. |
| Decision to Grant, dated Oct. 24, 2018, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Intention to Grant, dated Mar. 18, 2019, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 9 pages. |
| Decision to Grant, dated Aug. 8, 2019, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 1 page. |
| Certificate of Grant, dated Sep. 4, 2019, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Patent, dated Sep. 27, 2019, received in Hong Kong Patent Application No. 15108904.1, which corresponds with U.S. Appl. No. 14/536,203, 6 pages. |
| Office Action, dated Feb. 15, 2016, received in Japanese Patent Application No. 2015-511650, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Notice of Allowance, dated Aug. 5, 2016, received in Japanese Patent Application No. 2015-511650, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Certificate of Patent, dated Sep. 9, 2016, received in Japanese Patent Application No. 2015-511650, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Office Action, dated Jun. 23, 2017, received in Japanese Patent Application No. 2016173113, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Notice of Allowance, dated Jan. 12, 2018, received in Japanese Patent Application No. 2016173113, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Patent, dated Feb. 16, 2018, received in Japanese Patent Application No. 2016173113, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Office Action, dated Oct. 19, 2018, received in Japanese Patent Application No. 2018-022394, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Office Action, dated Sep. 30, 2019, received in Japanese Patent Application No. 2018-022394, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Office Action, dated Jan. 22, 2021, received in Japanese Patent Application No. 2018-022394, which corresponds with U.S. Appl. No. 14/536,203, 2 pages. |
| Notice of Allowance, dated Dec. 3, 2021, received in Japanese Patent Application No. 2018-022394, which corresponds with U.S. Appl. No. 14/536,203, 2 pages. |
| Patent, dated Dec. 13, 2021, received in Japanese Patent Application No. 2018-022394, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
| Office Action, dated Dec. 4, 2015, received in Korean Patent Application No. 2014-7034520, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Notice of Allowance, dated Sep. 1, 2016, received in Korean Patent Application No. 2014-7034520, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Office Action, dated Feb. 6, 2017, received in Korean Patent Application No. 2016-7033834, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Notice of Allowance, dated Oct. 30, 2017, received in Korean Patent Application No. 2016-7033834, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
| Patent, dated Jan. 23, 2018, received in Korean Patent Application No. 2016-7033834, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
| Office Action, dated Oct. 20, 2017, received in U.S. Appl. No. 14/608,965, 14 pages. |
| Office Action, dated Jul. 2, 2018, received in U.S. Appl. No. 14/608,965, 16 pages. |
| Final Office Action, dated Jan. 10, 2019, received in U.S. Appl. No. 14/608,965, 17 pages. |
| Notice of Allowance dated Nov. 7, 2019, received in U.S. Appl. No. 14/608,965, 17 pages. |
| Notice of Allowance dated Jan. 2, 2020, received in U.S. Appl. No. 14/608,965, 5 pages. |
| Office action, dated Oct. 11, 2017, received in Chinese Patent Application No. 201380074060.1, which corresponds with U.S. Appl. No. 14/608,965, 5 pages. |
| Office action, dated Aug. 1, 2018, received in Chinese Patent Application No. 201380074060.1, which corresponds with U.S. Appl. No. 14/608,965, 5 pages. |
| Office action, dated Nov. 1, 2018, received in Chinese Patent Application No. 201380074060.1, which corresponds with U.S. Appl. No. 14/608,965, 3 pages. |
| Office action, dated Apr. 3, 2019, received in Chinese Patent Application No. 201380074060.1, which corresponds with U.S. Appl. No. 14/608,965, 3 pages. |
| Patent, dated May 17, 2019, received in Chinese Patent Application No. 201380074060.1, which corresponds with U.S. Appl. No. 14/608,965, 6 pages. |
| Office Action, dated Jul. 22, 2016, received in European Office Action No. 13798465.4, which corresponds with U.S. Appl. No. 14/608,965, 3 pages. |
| Oral Proceedings, dated Mar. 7, 2018, received in European Office Action No. 13798465.4, which corresponds with U.S. Appl. No. 14/608,965, 5 pages. |
| Decision to Grant, dated Sep. 6, 2018, received in European Office Action No. 13798465.4, which corresponds with U.S. Appl. No. 14/608,965, 2 pages. |
| Office Action, dated Oct. 20, 2016, received in U.S. Appl. No. 14/536,247, 10 pages. |
| Final Office Action, dated Mar. 24, 2017, received in U.S. Appl. No. 14/536,247, 14 pages. |
| Notice of Allowance, dated Nov. 22, 2017, received in U.S. Appl. No. 14/536,247, 6 pages. |
| Office Action, dated Mar. 24, 2017, received in U.S. Appl. No. 14/536,267, 12 pages. |
| Notice of Allowance, dated Nov. 9, 2017, received in U.S. Appl. No. 14/536,267, 8 pages. |
| Notice of Allowance, dated Jun. 1, 2018, received in U.S. Appl. No. 14/536,267, 5 pages. |
| Office Action, dated Aug. 10, 2015, received in Australian Patent Application No. 2013259637, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Notice of Allowance, dated Jun. 28, 2016, received in Australian Patent Application No. 2013259637, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Certificate of Grant, dated Oct. 21, 2016, received in Australian Patent Application No. 2013259637, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Office Action, dated Mar. 24, 2017, received in Australian Patent Application No. 2016204411, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Notice of Acceptance, dated Feb. 27, 2018, received in Australian Patent Application No. 2016204411, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Certificate of Grant, dated Jun. 28, 2018, received in Australian Patent Application No. 2016204411, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Office Action, dated Mar. 15, 2019, received in Australian Patent Application No. 2018204236, which corresponds with U.S. Appl. No. 14/5326,267, 5 pages. |
| Notice of Acceptance, dated Apr. 29, 2019, received in Australian Patent Application No. 2018204236, which corresponds with U.S. Appl. No. 14/5326,267, 3 pages. |
| Certificate of Grant, dated Aug. 28, 2019, received in Australian Patent Application No. 2018204236, which corresponds with U.S. Appl. No. 14/5326,267, 4 pages. |
| Office Action, dated Dec. 9, 2016, received in Chinese Patent Application No. 2016120601564130, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Notice of Allowance, dated Jan. 29, 2018, received in Chinese Patent Application No. 201380035968.1, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Patent, dated Apr. 20, 2018, received in Chinese Patent Application No. 201380035968.1, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Office Action, dated Nov. 28, 2018, received in Chinese Patent Application No. 201610537334.1, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Office Action, dated Jul. 11, 2019, received in Chinese Patent Application No. 201610537334.1, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Office Action, dated Sep. 30, 2019, received in Chinese Patent Application No. 201610537334.1, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Office Action, dated Dec. 20, 2019, received in Chinese Patent Application No. 201610537334.1, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Office Action, dated Apr. 20, 2020, received in Chinese Patent Application No. 201610537334.1, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Patent, dated Sep. 29, 2020, received in Chinese Patent Application No. 201610537334.1, which corresponds with U.S. Appl. No. 14/536,267, 7 pages. |
| Office Action, dated Jun. 13, 2018, received in Chinese Patent Application No. 201810332044.2, which corresponds with U.S. Appl. No. 14/536,267, 2 pages. |
| Office Action, dated Jan. 20, 2021, received in Chinese Patent Application No. 201810332044.2, which corresponds with U.S. Appl. No. 14/536,267, 15 pages. |
| Patent, dated May 27, 2022, received in Chinese Patent Application No. 201810332044.2, which corresponds with U.S. Appl. No. 14/536,267, 6 pages. |
| Office Action, dated Jul. 19, 2021, received in Chinese Patent Application No. 201810332044.2, which corresponds with U.S. Appl. No. 14/536,267, 1 page. |
| Office Action, dated Nov. 23, 2021, received in Chinese Patent Application No. 201810332044.2, which corresponds with U.S. Appl. No. 14/536,267, 2 page. |
| Notice of Allowance, dated Mar. 21, 2022, received in Chinese Patent Application No. 201810332044.2, which corresponds with U.S. Appl. No. 14/536,267, 1 page. |
| Office Action, dated Jan. 25, 2018, received in European Patent Application No. 13724106.3, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Intention to Grant, dated Jun. 27, 2018, received in European Patent Application No. 13724106.3, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Decision to Grant, dated Oct. 18, 2018, received in European Patent Application No. 13724106.3, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Grant Certificate, dated Nov. 14, 2018, received in European Patent Application No. 13724106.3, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. 4 pages. |
| Office Action, dated Sep. 13, 2017, received in European Patent Application No. 16177863.4, which corresponds with U.S. Appl. No. 14/536,267, 6 pages. |
| Decision to Grant, dated Nov. 29, 2018, received in European Patent Application No. 16177863.4, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Patent, dated Dec. 26, 2018, received in European Patent Application No. 16177863.4, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Office Action, dated Aug. 29, 2019, received in European Patent Application No. 18183789.9, which corresponds with U.S. Appl. No. 16/262,800, 9 pages. |
| Office Action, dated Aug. 21, 2020, received in European Patent Application No. 18183789.9, which corresponds with U.S. Appl. No. 16/262,800, 9 pages. |
| Intent to Grant, dated Mar. 16, 2022, received in European Patent Application No. 18183789.9, which corresponds with U.S. Appl. No. 16/262,800, 7 pages. |
| Decision to Grant, dated Jul. 21, 2022, received in European Patent Application No. 18183789.9, which corresponds with U.S. Appl. No. 16/262,800, 3 pages. |
| Patent, dated Aug. 17, 2022, received in European Patent Application No. 18183789.9, which corresponds with U.S. Appl. No. 16/262,800, 4 pages. |
| Patent, dated Aug. 30, 2019, received in Hong Kong Patent Application No. 15107537.8, which corresponds with U.S. Appl. No. 14/536,267, 9 pages. |
| Patent, dated Nov. 8, 2019, received in Hong Kong Patent Application No. 15108890.7, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Office Action, dated Jan. 29, 2016, received in Japanese Patent Application No. 2015-511652, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Notice of Allowance, dated Sep. 26, 2016, received in Japanese Patent Application No. 2015-511652, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Office Action, dated Mar. 3, 2017, received in Japanese Patent Application No. 2016-125839, which corresponds with U.S. Appl. No. 14/536,267, 6 pages. |
| Notice of Allowance, dated Nov. 17, 2017, received in Japanese Patent Application No. 2016-125839, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Office Action, dated Feb. 4, 2019, received in Japanese Patent Application No. 2017-237035, which corresponds with U.S. Appl. No. 14/536,267, 7 pages. |
| Notice of Allowance, dated Sep. 9, 2019, received in Japanese Patent Application No. 2017-237035, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Patent, dated Sep. 27, 2019, received in Japanese Patent Application No. 2017-237035, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Office Action, dated Dec. 4, 2015, received in Korean Patent Application No. 2014-7034530, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Notice of Allowance, dated Sep. 1, 2016, received in Korean Patent Application No. 2014-7034530, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
| Office Action, dated Jan. 5, 2017, received in Korean Patent Application No. 2016-7029533, which corresponds with U.S. Appl. No. 14/536,267, 2 pages. |
| Notice of Allowance, dated Sep. 1, 2017, received in Korean Patent Application No. 2016-7029533, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Patent, dated Dec. 1, 2017, received in Korean Patent Application No. 2016-7029533, which corresponds with U.S. Appl. No. 14/536,267, 2 pages. |
| Office Action, dated Jan. 29, 2018, received in Korean Patent Application No. 2017-7034838, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Notice of Allowance, dated Dec. 3, 2018, received in Korean Patent Application No. 2017-7034838, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
| Patent, dated Mar. 4, 2019, received in Korean Patent Application No. 2017-7034838, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
| Office Action, dated Apr. 7, 2017, received in U.S. Appl. No. 14/536,291, 11 pages. |
| Notice of Allowance, dated Dec. 1, 2017, received in U.S. Appl. No. 14/536,291, 19 pages. |
| Notice of Allowance, dated Mar. 20, 2018, received in U.S. Appl. No. 14/536,291, 5 pages. |
| Office Action, dated Aug. 18, 2015, received in Australian Patent Application No. 2013259642, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Office Action, dated Jul. 25, 2016, received in Australian Patent Application No. 2013259642, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Office Action, dated Aug. 10, 2016, received in Australian Patent Application No. 2013259642, which corresponds with U.S. Appl. No. 14/536,291, 4 pages. |
| Office Action, dated Jul. 21, 2017, received in Australian Patent Application No. 2016216658, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Notice of Acceptance, dated Jul. 19, 2018, received in Australian Patent Application No. 2016216658, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Patent, dated Nov. 30, 2018, received in Australian Patent Application No. 2016216658, which corresponds with U.S. Appl. No. 14/536,291, 4 pages. |
| Innovation Patent, dated Sep. 1, 2016, received in Australian Patent Application No. 2016101481, which corresponds with U.S. Appl. No. 14/536,291, 1 page. |
| Office Action, dated Sep. 29, 2016, received in Australian Patent Application No. 2016101481, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Office Action, dated Oct. 23, 2017, received in Chinese Patent Application No. 201380035986.X, which corresponds with U.S. Appl. No. 14/536,291, 9 pages. |
| Notice of Allowance, dated Jun. 24, 2020, received in Chinese Patent Application No. 201710781246.0, which corresponds with U.S. Appl. No. 14/536,291, 5 pages. |
| Patent, dated Jul. 31, 2020, received in Chinese Patent Application No. 201710781246.0, which corresponds with U.S. Appl. No. 14/536,291, 6 pages. |
| Office Action, dated Jul. 17, 2020, received in Chinese Patent Application No. 2018100116175.X, which corresponds with U.S. Appl. No. 14/536,291, 15 pages. |
| Office Action, dated Nov. 17, 2020, received in Chinese Patent Application No. 2018100116175.X, which corresponds with U.S. Appl. No. 14/536,291, 16 pages. |
| Notice of Allowance, dated Mar. 29, 2021, received in Chinese Patent Application No. 2018100116175.X, which corresponds with U.S. Appl. No. 14/536,291, 1 page. |
| Patent, dated Apr. 27, 2021, received in Chinese Patent Application No. 2018100116175.X, which corresponds with U.S. Appl. No. 14/536,291, 6 pages. |
| Office Action, dated Jan. 7, 2016, received in European Patent Application No. 13724107.1, which corresponds with U.S. Appl. No. 14/536,291, 11 pages. |
| Office Action, dated Aug. 22, 2016, received in European Patent Application No. 13724107.1, which corresponds with U.S. Appl. No. 14/536,291, 7 pages. |
| Office Action, dated Mar. 23, 2017, received in European Patent Application No. 13724107.1, which corresponds with U.S. Appl. No. 14/536,291, 8 pages. |
| Intention to Grant, dated Jan. 8, 2019, received in European Patent Application No. 17186744.3, which corresponds with U.S. Appl. No. 14/536,291, 7 pages. |
| Decision to Grant, dated Oct. 31, 2019, received in European Patent Application No. 17186744.3, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Patent, dated Nov. 27, 2019, received in European Patent Application No. 17186744.3, which corresponds with U.S. Appl. No. 14/536,291, 4 pages. |
| Office Action, dated Mar. 8, 2016, received in Japanese Patent Application No. 2015-511655, which corresponds with U.S. Appl. No. 14/536,291, 4 pages. |
| Final Office Action, dated Dec. 22, 2016, received in Japanese Patent Application No. 2015-511655, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Office Action, dated Jun. 29, 2018, received in Japanese Patent Application No. 2017-083027, which corresponds with U.S. Appl. No. 14/536,291, 5 pages. |
| Patent, dated Feb. 22, 2019, received in Japanese Patent Application No. 2017-083027, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
| Notice of Allowance, dated Jan. 15, 2019, received in Japanese Patent Application No. 2017-083027, which corresponds with U.S. Appl. No. 14/536,291, 5 pages. |
| Office Action, dated Oct. 19, 2017, received in U.S. Appl. No. 14/608,985, 13 pages. |
| Notice of Allowance, dated Apr. 20, 2018, received in U.S. Appl. No. 14/608,985, 5 pages. |
| Office Action, dated Jan. 15, 2016, received in Australian Patent Application No. 2013368445, which corresponds with U.S. Appl. No. 14/608,985, 3 pages. |
| Notice of Allowance, dated Jan. 18, 2017, received in Australian Patent Application No. 2013368445, which corresponds with U.S. Appl. No. 14/608,985, 3 pages. |
| Patent, dated May 18, 2017, received in Australian Patent Application No. 2013368445, which corresponds with U.S. Appl. No. 14/608,985, 1 page. |
| Office Action, dated May 19, 2017, received in Chinese Patent Application No. 201380068399.0, which corresponds with U.S. Appl. No. 14/608,985, 5 pages. |
| Notice of Allowance, dated Sep. 19, 2017, received in Chinese Patent Application No. 201380068399.0, which corresponds with U.S. Appl. No. 14/608,985, 3 pages. |
| Patent, dated Dec. 8, 2017, received in Chinese Patent Application No. 201380068399.0, which corresponds with U.S. Appl. No. 14/608,985, 4 pages. |
| Office Action, dated Jul. 25, 2016, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 8 pages. |
| Office Action, dated Feb. 27, 2017, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 6 pages. |
| Summons, dated Oct. 6, 2017, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 6 pages. |
| Intention to Grant, dated Jan. 16, 2019, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 9 pages. |
| Decision to Grant, dated Aug. 1, 2019, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 2 pages. |
| Certificate of Grant, dated Aug. 28, 2019, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 4 pages. |
| Certificate of Grant, dated Jun. 29, 2018, received in Hong Kong Patent Application No. 15112851.6, which corresponds with U.S. Appl. No. 14/608,985, 2 pages. |
| Office Action, dated Apr. 25, 2016, received in Japanese Patent Application No. 2015-550384, which corresponds with U.S. Appl. No. 14/608,985, 4 pages. |
| Notice of Allowance, dated Jan. 24, 2017, received in Japanese Patent Application No. 2015-550384, which corresponds with U.S. Appl. No. 14/608,985, 5 pages. |
| Patent, dated Feb. 24, 2017, received in Japanese Patent Application No. 2015-550384, which corresponds with U.S. Appl. No. 14/608,985, 2 pages. |
| Office Action, dated Nov. 4, 2016, received in Korean Patent Application No. 2015-7019984, which corresponds with U.S. Appl. No. 14/608,985, 8 pages. |
| Notice of Allowance, dated Sep. 19, 2017, received in Korean Patent Application No. 2015-7019984, which corresponds with U.S. Appl. No. 14/608,985, 4 pages. |
| Patent, dated Dec. 19, 2017, received in Korean Patent Application No. 2015-7019984, which corresponds with U.S. Appl. No. 14/608,985, 3 pages. |
| Office Action, dated Mar. 24, 2017, received in U.S. Appl. No. 14/609,006, 13 pages. |
| Final Office Action, dated Sep. 21, 2017, received in U.S. Appl. No. 14/609,006, 17 pages. |
| Office Action, dated Mar. 20, 2018, received in U.S. Appl. No. 14/609,006, 13 pages. |
| Office Action, dated Oct. 11, 2018, received in U.S. Appl. No. 14/609,006, 12 pages. |
| Final Office Action, dated May 23, 2019, received in U.S. Appl. No. 14/609,006, 14 pages. |
| Office Action, dated Jan. 7, 2020, received in U.S. Appl. No. 14/609,006, 17 pages. |
| Final Office Action, dated Jun. 15, 2020, received in U.S. Appl. No. 14/609,006, 19 pages. |
| Decision on Appeal, dated Jun. 9, 2022, received in U.S. Appl. No. 14/609,006, 11 pages. |
| Office Action, dated Apr. 19, 2017, received in U.S. Appl. No. 14/536,296, 12 pages. |
| Final Office Action, dated Nov. 2, 2017, received in U.S. Appl. No. 14/536,296, 13 pages. |
| Notice of Allowance, dated Mar. 14, 2018, received in U.S. Appl. No. 14/536,296, 8 pages. |
| Office Action, dated Nov. 1, 2017, received in U.S. Appl. No. 14/536,648, 22 pages. |
| Final Office Action, dated Aug. 7, 2018, received in U.S. Appl. No. 14/536,648, 14 pages. |
| Office Action, dated Jan. 2, 2019, received in U.S. Appl. No. 14/536,648 12 pages. |
| Notice of Allowance, dated Jul. 2, 2019, received in U.S. Appl. No. 14/536,648, 5 pages. |
| Office Action, dated Jul. 21, 2017, received in Australian Patent Application No. 2016247194, which corresponds with U.S. Appl. No. 14/536,648, 3 pages. |
| Notice of Acceptance, dated Jul. 19, 2018, received in Australian Patent Application No. 2016247194, which corresponds with U.S. Appl. No. 14/536,648, 3 pages. |
| Office Action, dated Jul. 24, 2020, received in Chinese Patent Application No. 201711422121.5, which corresponds with U.S. Appl. No. 14/536,648, 10 pages. |
| Notice of Allowance, dated Feb. 2, 2021, received in Chinese Patent Application No. 201711422121.5, which corresponds with U.S. Appl. No. 14/536,648, 1 page. |
| Patent, dated Mar. 9, 2021, received in Chinese Patent Application No. 201711422121.5, which corresponds with U.S. Appl. No. 14/536,648, 7 pages. |
| Intention to Grant, dated Apr. 1, 2019, received in European Patent Application No. 17153418.3, which corresponds with U.S. Appl. No. 14/536,648, 7 pages. |
| Decision to Grant, dated Aug. 16, 2019, received in European Patent Application No. 17153418.3, which corresponds with U.S. Appl. No. 14/536,648, 3 pages. |
| Grant Certificate, dated Sep. 11, 2019, received in European Patent Application No. 17153418.3, which corresponds with U.S. Appl. No. 14/536,648, 3 pages. |
| Office Action, dated Apr. 27, 2018, received in Japanese Patent Application No. 2017-008764, which corresponds with U.S. Appl. No. 14/536,648, 5 pages. |
| Notice of Allowance, dated Feb. 4, 2019, received in Japanese Patent Application No. 2017-008764, which corresponds with U.S. Appl. No. 14/536,648, 5 pages. |
| Patent, dated Mar. 1, 2019, received in Japanese Patent Application No. 2017-008764, which corresponds with U.S. Appl. No. 14/536,648, 3 pages. |
| Office Action, dated Jan. 19, 2017, received in U.S. Appl. No. 14/609,042, 12 pages. |
| Notice of Allowance, dated Jul. 10, 2017, received in U.S. Appl. No. 14/609,042, 8 pages. |
| Office Action, dated Aug. 24, 2018, received in Japanese Patent Application No. 2017-113598, which corresponds with U.S. Appl. No. 14/609,042, 6 pages. |
| Notice of Allowance, dated Apr. 9, 2019, received in Japanese Patent Application No. 2017-113598, which corresponds with U.S. Appl. No. 14/609,042, 5 pages. |
| Patent, dated Apr. 19, 2019, received in Japanese Patent Application No. 2017-113598, which corresponds with U.S. Appl. No. 14/609,042, 2 pages. |
| Notice of Allowance, dated Dec. 17, 2018, received in Korean Patent Application No. 2017-7008614, which corresponds with U.S. Appl. No. 14/609,042, 5 pages. |
| Patent, dated Mar. 8, 2019, received in Korean Patent Application No. 2017-7008614, which corresponds with U.S. Appl. No. 14/609,042, 4 pages. |
| Office Action, dated Mar. 31, 2016, received in U.S. Appl. No. 14/864,737, 17 pages. |
| Notice of Allowance, dated Feb. 27, 2017, received in U.S. Appl. No. 14/864,737, 9 pages. |
| Notice of Allowance, dated Jun. 19, 2017, received in U.S. Appl. No. 14/864,737, 8 pages. |
| Office Action, dated Apr. 16, 2018, received in Australian Patent Application No. 2016233792, which corresponds with U.S. Appl. No. 14/864,737, 2 pages. |
| Notice of Acceptance, dated Mar. 12, 2019, received in Australian Patent Application No. 2016233792, which corresponds with U.S. Appl. No. 14/864,737, 5 pages. |
| Certificate of Grant, dated Jul. 4, 2019, received in Australian Patent Application No. 2016233792, which corresponds with U.S. Appl. No. 14/864,737, 1 page. |
| Office Action, dated Sep. 11, 2018, received in Chinese Patent Application No. 201610159295.6, which corresponds with U.S. Appl. No. 14/864,737, 6 pages. |
| Notice of Allowance, dated Apr. 17, 2019, received in Chinese Patent Application No. 201610159295.6, which corresponds with U.S. Appl. No. 14/864,737, 3 pages. |
| Patent, dated May 31, 2019, received in Chinese Patent Application No. 201610159295.6, which corresponds with U.S. Appl. No. 14/864,737, 7 pages. |
| Notice of Allowance, dated Jul. 1, 2016, received in Chinese Patent Application No. 201620214376.7, which corresponds with U.S. Appl. No. 14/864,737, 3 pages. |
| Patent, dated Aug. 3, 2016, received in Chinese Patent Application No. 201620214376.7, which corresponds with U.S. Appl. No. 14/864,737, 5 pages. |
| Certificate of Registration, dated Jun. 20, 2016, received in German Patent Application No. 202016001845.1, which corresponds with U.S. Appl. No. 14/864,737, 3 pages. |
| Office Action, dated Apr. 5, 2016, received in Danish Patent Application No. 201500577, which corresponds with U.S. Appl. No. 14/864,737, 7 pages. |
| Intention to Grant, dated Aug. 2, 2016, received in Danish Patent Application No. 201500577, which corresponds with U.S. Appl. No. 14/864,737, 2 pages. |
| Decision to grant, dated Mar. 29, 2018, received in European Patent Application No. 16710871.1, which corresponds with U.S. Appl. No. 14/864,737, 2 pages. |
| Grant Certificate, dated Apr. 25, 2018, received in European Patent Application No. 16710871.1, which corresponds with U.S. Appl. No. 14/864,737, 2 pages. |
| Office Action, dated May 15, 2017, received in Japanese Patent Application No. 2016-558331, which corresponds with U.S. Appl. No. 14/864,737, 5 pages. |
| Notice of Allowance, dated Jun. 23, 2017, received in Japanese Patent Application No. 2016-558331, which corresponds with U.S. Appl. No. 14/864,737, 5 pages. |
| Patent, dated Jul. 28, 2017, received in Japanese Patent Application No. 2016- 558331, which corresponds with U.S. Appl. No. 14/864,737, 3 pages. |
| Office Action, dated Feb. 14, 2018, received in Korean Patent Application No. 2017-7030129, which corresponds with U.S. Appl. No. 14/864,737, 17 pages. |
| Patent, dated Dec. 26, 2018, received in Korean Patent Application No. 2017-7030129, which corresponds with U.S. Appl. No. 14/864,737, 4 pages. |
| Patent, dated Jul. 12, 2017, received in Dutch Patent Application No. 2016452, which corresponds with U.S. Appl. No. 14/864,737, 2 pages. |
| Office Action, dated Jun. 27, 2016, received in U.S. Appl. No. 14/866,981, 22 pages. |
| Notice of Allowance, dated Oct. 24, 2016, received in U.S. Appl. No. 14/866,981, 7 pages. |
| Notice of Allowance, dated Feb. 10, 2017, received in U.S. Appl. No. 14/866,981, 5 pages. |
| Office Action, dated May 10, 2016, received in Australian Patent Application No. 2016100254, which corresponds with U.S. Appl. No. 14/866,981, 6 pages. |
| Patent, dated Nov. 2, 2016, received in Australian Patent Application No. 2016100254, which corresponds with U.S. Appl. No. 14/866,981, 1 page. |
| Office Action, dated Nov. 5, 2018, received in Chinese Patent Application No. 201610131415.1, which corresponds with U.S. Appl. No. 14/866,981, 6 pages. |
| Office Action, dated Jul. 16, 2019, received in Chinese Patent Application No. 201610131415.1, which corresponds with U.S. Appl. No. 14/866,981, 4 pages. |
| Office Action, dated Mar. 16, 2020, received in Chinese Patent Application No. 201610131415.1, which corresponds with U.S. Appl. No. 14/866,981, 3 pages. |
| Notice of Allowance, dated Dec. 4, 2020, received in Chinese Patent Application No. 201610131415.1, which corresponds with U.S. Appl. No. 14/866,981, 3 pages. |
| Patent, dated Jan. 22, 2021, received in Chinese Patent Application No. 201610131415.1, which corresponds with U.S. Appl. No. 14/866,981, 6 pages. |
| Notice of Allowance, dated Jul. 27, 2016, received in Chinese Patent Application No. 201620176169.7, which corresponds with U.S. Appl. No. 14/866,981, 3 pages. |
| Patent, dated Sep. 28, 2016, received in Chinese Patent Application No. 201620176169.7, which corresponds with U.S. Appl. No. 14/866,981, 4 pages. |
| Certificate of Registration, dated Jun. 20, 2016, received in German Patent Application No. 202016001514.2, which corresponds with U.S. Appl. No. 14/864,737, 3 pages. |
| Office Action, dated Mar. 18, 2016, received in Danish Patent Application No. 201500575, which corresponds with U.S. Appl. No. 14/866,981, 9 pages. |
| Office Action, dated Dec. 5, 2016, received in Danish Patent Application No. 201500575, which corresponds with U.S. Appl. No. 14/866,981, 3 pages. |
| Office Action, dated Jul. 7, 2017, received in Danish Patent Application No. 201500575, 4 pages. |
| Patent, Nov. 16, 2017, received in Dutch Patent Application No. 2016375, which corresponds with U.S. Appl. No. 14/866,981, 2 pages. |
| Office Action, dated Dec. 15, 2017, received in U.S. Appl. No. 14/866,159, 35 pages. |
| Notice of Allowance, dated May 18, 2018, received in U.S. Appl. No. 14/866,159, 8 pages. |
| Office Action, dated May 19, 2016, received in Australian Patent Application No. 2016100251, which corresponds with U.S. Appl. No. 14/866,159, 5 pages. |
| Office Action, dated Jun. 5, 2018, received in Chinese Patent Application No. 201610137839.9, which corresponds with U.S. Appl. No. 14/866,159, 11 pages. |
| Notice of Allowance, dated Dec. 6, 2018, received in Chinese Patent Application No. 201610137839.9, which corresponds with U.S. Appl. No. 14/866,159, 3 pages. |
| Patent, dated Feb. 19, 2019, received in Chinese Patent Application No. 201610137839.9, which corresponds with U.S. Appl. No. 14/866,159, 6 pages. |
| Office Action, dated Jul. 5, 2016, received in Chinese Patent Application No. 201620186008.6, which corresponds with U.S. Appl. No. 14/866,159, 3 pages. |
| Certificate of Registration, dated Jun. 16, 2016, received in German Patent No. 202016001483.9, which corresponds with U.S. Appl. No. 14,866,159, 3 pages. |
| Office Action, dated Mar. 9, 2016, received in Danish Patent Application No. 14/866,159, which corresponds with U.S. Appl. No. 14/866,159, 11 pages. |
| Office Action, dated Sep. 27, 2016, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 4 pages. |
| Office Action, dated Mar. 14, 2017, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 5 pages. |
| Office Action, dated Jul. 6, 2017, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 3 pages. |
| Office Action, dated Jan. 10, 2018, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 2 pages. |
| Notice of Allowance, dated Mar. 21, 2018, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 2 pages. |
| Patent, dated May 22, 2018, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 2 pages. |
| Intention to Grant, dated Oct. 28, 2019, received in European Patent Application No. 16707356.8, which corresponds with U.S. Appl. No. 14/866,159, 7 pages. |
| Decision to Grant, dated Mar. 5, 2020, received in European Patent Application No. 16707356.8, which corresponds with U.S. Appl. No. 14/866,159, 2 pages. |
| Patent, dated Apr. 1, 2020, received in European Patent Application No. 16707356.8, which corresponds with U.S. Appl. No. 14/866,159, 3 pages. |
| Patent, dated Sep. 7, 2017, received in Dutch Patent Application No. 2016377, which corresponds with U.S. Appl. No. 14/866,159, 4 pages. |
| Office Action, dated Oct. 6, 2017, received in U.S. Appl. No. 14/868,078, 40 pages. |
| Notice of Allowance, dated May 24, 2018, received in U.S. Appl. No. 14/868,078, 6 pages. |
| Innovation Patent, dated Aug. 4, 2016, received in Australian Patent Application No. 2016101201, which corresponds with U.S. Appl. No. 14/868,078, 1 page. |
| Office Action, dated Oct. 12, 2016, received in Australian Patent Application No. 2016101201, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Notice of Allowance, dated Sep. 1, 2017, received in Australian Patent Application No. 2016229421, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Certificate of Grant, dated Jan. 3, 2018, received in Australian Patent Applicaiton No. 2016229421, which corresponds with U.S. Appl. No. 14/868,078, 1 page. |
| Office Action, dated Feb. 7, 2019, received in Australian Patent Application No. 2017258967, which corresponds with U.S. Appl. No. 14/868,078, 3 page. |
| Notice of Acceptance, dated Jun. 21, 2019, received in Australian Patent Application No. 2017258967, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Certificate of Grant, dated Oct. 17, 2019, received in Australian Patent Application No. 2017258967, which corresponds with U.S. Appl. No. 14/868,078, 4 page. |
| Office Action, dated Aug. 20, 2018, received in Chinese Patent Application No. 01610130348.1, which corresponds with U.S. Appl. No. 14/868,078, 6 pages. |
| Office Action, dated Feb. 26, 2019, received in Chinese Patent Application No. 01610130348.1, which corresponds with U.S. Appl. No. 14/868,078, 4 pages. |
| Notice of Allowance, dated May 6, 2019, received in Chinese Patent Application No. 01610130348.1, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Patent, dated Jul. 5, 2019, received in Chinese Patent Application No. 201610130348.1, which corresponds with U.S. Appl. No. 14/868,078, 6 pages. |
| Notice of Allowance, dated Oct. 1, 2016, received in Chinese Patent Application No. 201620175847.8, which corresponds with U.S. Appl. No. 14/868,078, 1 page. |
| Office Action, dated Nov. 21, 2019, received in Chinese Patent Application No. 201680011338.4, which corresponds with U.S. Appl. No. 14/868,078, 8 pages. |
| Office Action, dated May 19, 2020, received in Chinese Patent Application No. 201680011338.4, which corresponds with U.S. Appl. No. 14/868,078, 4 pages. |
| Office Action, dated Jun. 30, 2020, received in Chinese Patent Application No. 201680011338.4, which correspondence with U.S. Appl. No. 14/868,078, 4 pages. |
| Patent, dated Dec. 11, 2020, received in Chinese Patent Application No. 201680011338.4, which correspondence with U.S. Appl. No. 14/868,078, 3 pages. |
| Certificate of Registration, dated Jun. 30, 2016, received in German Patent Application No. 20201600156.9, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Office Action, dated Mar. 30, 2016, received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 9 pages. |
| Office Action, dated Sep. 2, 2016, received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 4 pages. |
| Notice of Allowance, dated Jan. 30, 2017, received in received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 2 pages. |
| Notice of Allowance, dated May 2, 2017, received in received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 2 pages. |
| Patent, dated Sep. 11, 2017, received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 5 pages. |
| Office Action, dated Apr. 25, 2018, received in European Patent Application No. 16708916.8, which corresponds with U.S. Appl. No. 14/868,078, 6 pages. |
| Intention to Grant, dated May 10, 2019, received in European Patent Application No. 16708916.8, which corresponds with U.S. Appl. No. 14/868,078, 5 pages. |
| Decision to Grant, dated Sep. 12, 2019, received in European Patent Application No. 16708916.8, which corresponds with U.S. Appl. No. 14/868,078, 2 pages. |
| Patent, dated Oct. 9, 2019, received in European Patent Application No. 16708916.8, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Office Action, dated Oct. 25, 2018, received in European Patent Application No. 17184437.6, which corresponds with U.S. Appl. No. 14/868,078, 6 pages. |
| Intention to Grant, dated May 22, 2019, received in European Patent Application No. 17184437.6, which corresponds with U.S. Appl. No. 14/868,078, 7 pages. |
| Decision to Grant, dated Sep. 19, 2019, received in European Patent Application No. 17184437.6, which corresponds with U.S. Appl. No. 14/868,078, 2 pages. |
| Patent, dated Oct. 16, 2019, received in European Patent Application No. 17184437.6, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
| Patent, dated Jul. 12, 2017, received in Dutch Patent Application No. 2016376, which corresponds with U.S. Appl. No. 14/868,078, 2 pages. |
| Office Action, dated May 9, 2016, received in U.S. Appl. No. 14/863,432, 26 pages. |
| Notice of Allowance, dated Nov. 14, 2016, received in U.S. Appl. No. 14/863,432, 7 pages. |
| Notice of Allowance, dated Apr. 27, 2017, received in U.S. Appl. No. 14/863,432, 7 pages. |
| Notice of Allowance, dated Sep. 18, 2017, received in U.S. Appl. No. 14/863,432, 8 pages. |
| Office Action, dated Aug. 19, 2016, received in Australian Patent Application No. 2016100647, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
| Office Action, dated Dec. 4, 2018, received in Chinese Patent Application No. 201610342313.4, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
| Office Action, dated Jun. 17, 2019, received in Chinese Patent Application No. 201610342313.4, which corresponds with U.S. Appl. No. 14/863,432, 4 pages. |
| Office Action, dated Nov. 5, 2019, received in Chinese Patent Application No. 201610342313.4, which corresponds with U.S. Appl. No. 14/863,432, 4 pages. |
| Notice of Allowance, dated Mar. 20, 2020, received in Chinese Patent Application No. 201610342313.4, which corresponds with U.S. Appl. No. 14/863,432, 6 pages. |
| Patent, dated May 12, 2020, received in Chinese Patent Application No. 201610342313.4, which corresponds with U.S. Appl. No. 14/863,432, 7 pages. |
| Notice of Allowance, dated Jan. 12, 2017, received in Chinese Patent Application No. 201620470063.8, which corresponds with U.S. Appl. No. 14/863,432, 1 page. |
| Patent, dated Feb. 8, 2017, received in Chinese Patent Application No. 201620470063.8, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
| Office Action, dated Apr. 4, 2016, received in Danish Patent Application No. 201500582, which corresponds with U.S. Appl. No. 14/863,432, 10 pages. |
| Office Action, dated Oct. 7, 2016, received in Danish Patent Application No. 201500582, which corresponds with U.S. Appl. No. 14/863,432, 6 pages. |
| Office Action, dated Jun. 12, 2017, received in Danish Patent Application No. 201500582, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
| Office Action, dated Jan. 10, 2020, received in Japanese Patent Application No. 2018-243773, which corresponds with U.S. Appl. No. 14/863,432, 6 pages. |
| Office Action, dated Jul. 17, 2020, received in Japanese Patent Application No. 2018-243773, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
| Notice of Allowance, dated Dec. 4, 2020, received in Japanese Patent Application No. 2018-243773, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
| Patent, dated Jan. 5, 2021, received in Japanese Patent Application No. 2018-243773, which corresponds with U.S. Appl. No. 14/863,432, 4 pages. |
| Notice of Allowance, dated Jul. 13, 2020, received in Korean Patent Application No. 2020-7015964, which corresponds with U.S. Appl. No. 14/863,432, 6 pages. |
| Patent, dated Oct. 12, 2020, received in Korean Patent Application No. 2020-7015964, which corresponds with U.S. Appl. No. 14/863,432, 8 pages. |
| Grant, dated Jul. 21, 2017, received in Dutch Patent Application No. 2016801, which corresponds with U.S. Appl. No. 14/871,227, 8 pages. |
| Office Action, dated Oct. 13, 2016, received in U.S. Appl. No. 14/866,511, 27 pages. |
| Final Office Action, dated Jan. 27, 2017, received in U.S. Appl. No. 14/866,511, 26 pages. |
| Notice of Allowance, dated Oct. 4, 2017, received in U.S. Appl. No. 14/866,511, 37 pages. |
| Office Action, dated Aug. 19, 2016, received in U.S. Appl. No. 14/291,880—to be referenced in 7294 per Robby), 19 pages. |
| Notice of Allowance, dated Jan. 10, 2017, received in U.S. Appl. No. 14/291,880—to be referenced in 7294 per Robby), 8 pages. |
| Patent, dated Aug. 8, 2016, received in Australian Patent Application No. 2016100653, corresponds with U.S. Appl. No. 14/866,511, 1 page. |
| Office Action, dated Dec. 5, 2018, received in Chinese Patent Application No. 201610342264.4, which corresponds with U.S. Appl. No. 14/866,511, 4 pages. |
| Office Action, dated Jul. 11, 2019, received in Chinese Patent Application No. 14/866,511.4, which corresponds with U.S. Appl. No. 14/866,511, 4 pages. |
| Office Action, dated Sep. 17, 2019, received in Chinese Patent Application No. 201610342264.4, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
| Notice of Allowance, dated Nov. 28, 2019, received in Chinese Patent Application No. 201610342264.4, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
| Patent, dated Feb. 7, 2020, received in Chinese Patent Application No. 201610342264.4, which corresponds with U.S. Appl. No. 14/866,511, 7 pages. |
| Notice of Allowance, dated Jan. 12, 2017, received in Chinese Patent Application No. 201620470281.1, which corresponds with U.S. Appl. No. 14/866,511, 1 page. |
| Office Action, dated Mar. 22, 2016, received in Danish Patent Application No. 201500576, which corresponds with U.S. Appl. No. 14/866,511, 10 pages. |
| Intention to Grant, dated Jun. 8, 2016, received in Danish Patent Application No. 201500576, which corresponds with U.S. Appl. No. 14/866,511, 2 pages. |
| Grant, dated Aug. 26, 2016, received in Danish Patent Application No. 201500576, which corresponds with U.S. Appl. No. 14/866,511, 2 pages. |
| Patent, dated Jan. 23, 2017, received in Danish Patent Application No. 201500576, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
| Office Action, dated Nov. 24, 2017, received in European Patent Application No. 16727900.9, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
| Office Action, dated May 24, 2018, received in European Patent Application No. 16727900.9, which corresponds with U.S. Appl. No. 14/866,511, 7 pages. |
| Office Action, dated Jan. 2, 2019, received in European Patent Application No. 16727900.9, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
| Intention to Grant, dated Jul. 5, 2019, received in European Patent Application No. 16727900.9, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
| Decision to Grant, dated Dec. 5, 2019, received in European Patent Application No. 16727900.9, which corresponds with U.S. Appl. No. 14/866,511, 2 pages. |
| Patent, dated Jan. 1, 2020, received in European Patent Application No. 16727900.9, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
| Office Action, dated Jun. 9, 2017, received in Japanese Patent Application No. 2016558214, which corresponds with U.S. Appl. No. 14/866,511, 6 pages. |
| Notice of Allowance, dated Jul. 14, 2017, received in Japanese Patent Application No. 2016558214, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
| Patent, dated Aug. 18, 2017, received in Japanese Patent Application No. 2016558214, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
| Office Action, dated Apr. 24, 2020, received in Korean Patent Application No. 2020-7003065, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
| Notice of Allowance, dated Jul. 29, 2020, received in Korean Patent Application No. 2020-7003065, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
| Patent, dated Oct. 29, 2020, received in Korean Patent Application No. 2020-7003065, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
| Office Action, dated Jul. 29, 2022, received in Indian U.S. Appl. No. 14/866,511, which corresponds with U.S. Appl. No. 14/866,511, 9 pages. |
| Office Action, dated May 10, 2016, received in U.S. Appl. No. 14/866,489, 15 pages. |
| Final Office Action, dated Sep. 16, 2016, received in U.S. Appl. No. 14/866,489, 24 pages. |
| Notice of Allowance, dated Apr. 27, 2017, received in U.S. Appl. No. 14/866,489, 27 pages. |
| Notice of Allowance, dated Jul. 6, 2017, received in U.S. Appl. No. 14/866,489, 12 pages. |
| Office Action, dated Mar. 28, 2016, received in U.S. Appl. No. 14/869,899, 17 pages. |
| Office Action, dated Jun. 28, 2016, received in U.S. Appl. No. 14/869,899, 5 pages. |
| Final Office Action, dated Sep. 2, 2016, received in U.S. Appl. No. 14/869,899, 22 pages. |
| Notice of Allowance, dated Feb. 28, 2017, received in U.S. Appl. No. 14/869,899, 9 pages. |
| Innovation Patent, dated Aug. 25, 2016, received in Australian Patent Application No. 2016101428, which corresponds with U.S. Appl. No. 14/869,899, 1 page. |
| Certificate of Examination, dated Oct. 11, 2016, received in Australian Patent Application No. 2016101438, which corresponds with U.S. Appl. No. 14/869,899, 1 page. |
| Notice of Acceptance, dated Aug. 23, 2018, received in Australian Patent Application No. 2018204611, which corresponds with U.S. Appl. No. 14/869,899, 3 pages. |
| Office Action, dated Nov. 6, 2020, received in Chinese Patent Application No. 201610871595.7, which corresponds with U.S. Appl. No. 14/869,899, 15 pages. |
| Notice of Allowance, dated Mar. 30, 2021, received in Chinese Patent Application No. 201610871595.7, which corresponds with U.S. Appl. No. 14/869,899, 1 page. |
| Patent, dated Jun. 4, 2021, received in Chinese Patent Application No. 201610871595.7, which corresponds with U.S. Appl. No. 14/869,899, 7 pages. |
| Office Action, dated Feb. 3, 2016, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 9 pages. |
| Office Action, dated Oct. 7, 2016, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 6 pages. |
| Office Action, dated Jul. 3, 2017, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 5 pages. |
| Office Action, dated Jan. 29, 2018, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 2 pages. |
| Notice of Allowance, dated Apr. 24, 2018, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 2 pages. |
| Patent, dated May 28, 2018, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 2 pages. |
| Office Action, dated Nov. 22, 2016, received in Danish Patent Application No. 201670594, which corresponds with U.S. Appl. No. 14/869,899, 9 pages. |
| Office Action, dated Dec. 14, 2017, received in Danish Patent Application No. 201670594, which corresponds with U.S. Appl. No. 14/869,899, 3 pages. |
| Office Action, dated May 1, 2018, received in Danish Patent Application No. 201670594, which corresponds with U.S. Appl. No. 14/869,899, 2 pages. |
| Office Action, dated Oct. 9, 2018, received in Danish Patent Application No. 201670594, which corresponds with U.S. Appl. No. 14/869,899, 2 pages. |
| Patent, dated Feb. 26, 2019, received in Danish Patent Application No. 201670594, which corresponds with U.S. Appl. No. 14/869,899, 3 pages. |
| Office Action, dated May 8, 2019, received in European Patent Application No. 18168939.9, which corresponds with U.S. Appl. No. 14/869,899, 10 pages. |
| Intention to Grant, dated Oct. 25, 2019, received in European Patent Application No. 18168939.9, which corresponds with U.S. Appl. No. 14/869,899, 8 pages. |
| Decision to Grant, dated Mar. 26, 2020, received in European Patent Application No. 18168939.9, which corresponds with U.S. Appl. No. 14/869,899, 3 pages. |
| Patent, dated Apr. 22, 2020, received in European Patent Application No. 18168939.9, which corresponds with U.S. Appl. No. 14/869,899, 3 pages. |
| Office Action, dated May 23, 2019, received in European Patent Application No. 18175195.9, which corresponds with U.S. Appl. No. 14/869,899, 10 pages. |
| Oral Summons, dated Dec. 6, 2019, received in European Patent Application No. 18175195.9, which corresponds with U.S. Appl. No. 14/869,899, 9 pages. |
| Office Action, dated Sep. 21, 2018, received in Japanese Patent Application No. 2018-100827, which corresponds with U.S. Appl. No. 14/869,899, 4 pages. |
| Notice of Allowance, dated Mar. 1, 2019, received in Japanese Patent Application No. 2018-100827, which corresponds with U.S. Appl. No. 14/869,899, 5 pages. |
| Patent, dated Apr. 5, 2019, received in Japanese Patent Application No. 2018-100827, which corresponds with U.S. Appl. No. 14/869,899, 5 pages. |
| Office Action, dated Oct. 5, 2018, received in Korean Patent Application No. 2018-7017213, which corresponds with U.S. Appl. No. 14/869,899, 3 pages. |
| Office Action, dated Mar. 22, 2019, received in Korean Patent Application No. 2018-7017213, which corresponds with U.S. Appl. No. 14/869,899, 6 pages. |
| Patent, dated May 10, 2019, received in Korean Patent Application No. 2018-7017213, which corresponds with U.S. Appl. No. 14/869,899, 8 pages. |
| Office Action, dated Mar. 4, 2016, received in U.S. Appl. No. 14/866,992, 30 pages. |
| Final Office Action, dated Jul. 29, 2016, received in U.S. Appl. No. 14/866,992, 35 pages. |
| Office Action, dated Apr. 13, 2017, received in U.S. Appl. No. 14/866,992, 34 pages. |
| Final Office Action, dated Oct. 3, 2017, received in U.S. Appl. No. 14/866,992, 37 pages. |
| Office Action, dated Jan. 29, 2018, received in U.S. Appl. No. 14/866,992, 44 pages. |
| Final Office Action, dated Aug. 28, 2018, received in U.S. Appl. No. 14/866,992, 52 pages. |
| Examiner's Answer, dated May 9, 2019, received in U.S. Appl. No. 14/866,992, 26 pages. |
| Innovation Patent, dated Sep. 22, 2016, received in Australian Patent Application No. 2016101418, which corresponds with U.S. Appl. No. 14/866,992, 1 page. |
| Office Action, dated Nov. 22, 2016, received in Australian Patent Application No. 2016101418, which corresponds with U.S. Appl. No. 14/866,992, 7 pages. |
| Office Action, dated Feb. 7, 2017, received in Australian Patent Application No. 2016101418, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
| Office Action, dated Mar. 26, 2018, received in Australian Patent Application No. 2016304890, which corresponds with U.S. Appl. No. 14/866,992, 3 pages. |
| Notice of Acceptance, dated Mar. 12, 2019, received in Australian Patent Application No. 2016304890, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
| Certificate of Grant, dated Jul. 4, 2019, received in Australian Patent Application No. 2016304890, which corresponds with U.S. Appl. No. 14/866,992, 1 page. |
| Office Action, dated Jan. 19, 2018, received in Australian Patent Application No. 201761478, which corresponds with U.S. Appl. No. 14/866,992, 6 pages. |
| Certificate of Grant, dated May 9, 2019, received in Australian Patent Application No. 201761478, which corresponds with U.S. Appl. No. 14/866,992, 3 pages. |
| Office Action, dated Sep. 12, 2019, received in Chinese Patent Application No. 201610658351.8, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
| Office Action, dated Jan. 13, 2020, received in Chinese Patent Application No. 201610658351.8, which corresponds with U.S. Appl. No. 14/866,992, 3 pages. |
| Office Action, dated Jun. 30, 2020, received in Chinese Patent Application No. 201610658351.8, which corresponds with U.S. Appl. No. 14/866,992, 11 pages. |
| Office Action, dated Nov. 25, 2020, received in Chinese Patent Application No. 201610658351.8, which corresponds with U.S. Appl. No. 14/866,992, 9 pages. |
| Office Action, dated Jul. 24, 2020, received in Chinese Patent Application No. 201680041559.6, which corresponds with U.S. Appl. No. 14/866,992, 13 pages. |
| Notice of Allowance, dated Apr. 26, 2021, received in Chinese Patent Application No. 201680041559.6, which corresponds with U.S. Appl. No. 14/866,992, 1 page. |
| Patent, dated May 28, 2021, received in Chinese Patent Application No. 201680041559.6, which corresponds with U.S. Appl. No. 14/866,992, 7 pages. |
| Office Action, dated Mar. 18, 2016, received in Danish Patent Application No. 201500593, which corresponds with U.S. Appl. No. 14/866,992, 10 pages. |
| Office Action, dated Jun. 27, 2016, received in Danish Patent Application No. 201500593, which corresponds with U.S. Appl. No. 14/866,992, 7 pages. |
| Office Action, dated Feb. 6, 2017, received in Danish Patent Application No. 201500593, which corresponds with U.S. Appl. No. 14/866,992, 4 pages. |
| Office Action, dated Sep. 5, 2017, received in Danish Patent Application No. 201500593, which corresponds with U.S. Appl. No. 14/866,992, 6 pages. |
| Office Action, dated Oct. 12, 2018, received in European Patent Application No. 16758008.3, which corresponds with U.S. Appl. No. 14/866,992, 11 pages. |
| Summons, dated May 8, 2019, received in European Patent Application No. 16758008.3, which corresponds with U.S. Appl. No. 14/866,992, 14 pages. |
| Office Action, dated Jan. 11, 2019, received in Japanese Patent Application No. 2018-506425, which corresponds with U.S. Appl. No. 14/866,992, 6 pages. |
| Notice of Allowance, dated Jun. 18, 2019, received in Japanese Patent Application No. 2018-506425, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
| Patent, dated Jul. 26, 2019, received in Japanese Patent Application No. 2018-506425, which corresponds with U.S. Appl. No. 14/866,992, 3 pages. |
| Notice of Allowance, dated Sep. 10, 2019, received in Korean Patent Application No. 2018-7003890, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
| Patent, dated Oct. 11, 2019, received in Korean Patent Application No. 2018-7003890, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
| Office Action, dated Feb. 12, 2018, received in U.S. Appl. No. 15/009,661, 36 pages. |
| Final Office Action, dated Sep. 19, 2018, received in U.S. Appl. No. 15/009,661, 28 pages. |
| Office Action, dated Jun. 28, 2019, received in U.S. Appl. No. 15/009,661, 33 pages. |
| Final Office Action, dated Dec. 30, 2019, received in U.S. Appl. No. 15/009,661, 33 pages. |
| Office Action, dated Sep. 16, 2020, received in U.S. Appl. No. 15/009,661, 37 pages. |
| Final Office Action, dated Feb. 26, 2021, received in U.S. Appl. No. 15/009,661, 46 pages. |
| Office Action, dated Jul. 1, 2021 received in U.S. Appl. No. 15/009,661, 52 pages. |
| Office Action, dated Jan. 18, 2018, received in U.S. Appl. No. 15/009,676, 21 Pages. |
| Notice of Allowance, dated Aug. 3, 2018, received in U.S. Appl. No. 15/009,676, 6 pages. |
| Notice of Allowance, dated Nov. 15, 2018, received in U.S. Appl. No. 15/009,676, 6 pages. |
| Office Action, dated Jul. 15, 2020, received in Chinese Patent Application No. 201680047125.7, which corresponds with U.S. Appl. No. 15/009,676, 11 pages. |
| Office Action, dated Nov. 30, 2020, received in Chinese Patent Application No. 201680047125.7, which corresponds with U.S. Appl. No. 15/009,676, 11 pages. |
| Notice of Allowance, dated Feb. 24, 2021, received in Chinese Patent Application No. 201680047125.7, which corresponds with U.S. Appl. No. 15/009,676, 1 page. |
| Patent, dated Apr. 27, 2021, received in Chinese Patent Application No. 201680047125.7, which corresponds with U.S. Appl. No. 15/009,676, 8 pages. |
| Intention to Grant, dated Apr. 7, 2020, received in European Patent Application No. 16756866.6, which corresponds with U.S. Appl. No. 15/009,676, 8 pages. |
| Decision to Grant, dated Aug. 27, 2020, received in European Patent Application No. 16756866.6, which corresponds with U.S. Appl. No. 15/009,676, 4 pages. |
| Patent, dated Sep. 23, 2020, received in European Patent Application No. 16756866.6, which corresponds with U.S. Appl. No. 15/009,676, 4 pages. |
| Office Action, dated Mar. 13, 2018, received in U.S. Appl. No. 15/009,688, 10 pages. |
| Notice of Allowance, dated Nov. 6, 2018, received in U.S. Appl. No. 15/009,688, 10 pages. |
| Office Action, dated Jun. 29, 2020, received in Chinese Patent Application No. 201680047164.7, which corresponds with U.S. Appl. No. 15/009,688, 7 pages. |
| Notice of Allowance, dated Oct. 9, 2020, received in Chinese Patent Application No. 201680047164.7, which corresponds with U.S. Appl. No. 15/009,688, 5 pages. |
| Patent, dated Nov. 10, 2020, received in Chinese Patent Application No. 201680047164.7, which corresponds with U.S. Appl. No. 15/009,688, 6 pages. |
| Intention to Grant, dated Mar. 16, 2020, received in European Patent Application No. 16753796.8, which corresponds with U.S. Appl. No. 15/009,688, 6 pages. |
| Decision to Grant, dated Sep. 24, 2020, received in European Patent Application No. 16753796.8, which corresponds with U.S. Appl. No. 15/009,688, 4 pages. |
| Certificate of Grant, dated Oct. 21, 2020, received in European Patent Application No. 16753796.8, which corresponds with U.S. Appl. No. 15/009,688, 4 pages. |
| Office Action, dated Nov. 30, 2015, received in U.S. Appl. No. 14/845,217, 24 pages. |
| Final Office Action, dated Apr. 22, 2016, received in U.S. Appl. No. 14/845,217, 36 pages. |
| Notice of Allowance, dated Aug. 26, 2016, received in U.S. Appl. No. 14/845,217, 5 pages. |
| Notice of Allowance, dated Jan. 4, 2017, received in U.S. Appl. No. 14/845,217, 5 pages. |
| Office Action, dated Feb. 3, 2016, received in U.S. Appl. No. 14/856,517, 36 pages. |
| Final Office Action, dated Jul. 13, 2016, received in U.S. Appl. No. 14/856,517, 30 pages. |
| Office Action, dated May 2, 2017, received in U.S. Appl. No. 14/856,517, 34 pages. |
| Final Office Action, dated Oct. 4, 2017, received in U.S. Appl. No. 14/856,517, 33 pages. |
| Notice of Allowance, dated Jun. 29, 2018, received in U.S. Appl. No. 14/856,517, 11 pages. |
| Office Action, dated Feb. 11, 2016, received in U.S. Appl. No. 14/856,519, 34 pages. |
| Final Office Action, dated Jul. 15, 2016, received in U.S. Appl. No. 14/856,519, 31 pages. |
| Office Action, dated May 18, 2017, received in U.S. Appl. No. 14/856,519, 35 pages. |
| Final Office Action, dated Nov. 15, 2017, received in U.S. Appl. No. 14/856,519, 31 pages. |
| Notice of Allowance, dated Jan. 31, 2018, received in U.S. Appl. No. 14/856,519, 9 pages. |
| Notice of Allowance, dated May 2, 2018, received in U.S. Appl. No. 14/856,519, 10 pages. |
| Office Action, dated Jun. 9, 2017, received in U.S. Appl. No. 14/856,520, 36 pages. |
| Final Office Action, dated Nov. 16, 2017, received in U.S. Appl. No. 14/856,520, 41 pages. |
| Office Action, dated Nov. 20, 2018, received in U.S. Appl. No. 14/856,520, 36 pages. |
| Final Office Action, dated Apr. 17, 2019, received in U.S. Appl. No. 14/856,520, 38 pages. |
| Notice of Allowance, dated Jan. 6, 2020, received in U.S. Appl. No. 14/856,520, 5 pages. |
| Notice of Allowance, dated Mar. 4, 2020, received in U.S. Appl. No. 14/856,520, 6 pages. |
| Notice of Allowance, dated Oct. 1, 2020, received in U.S. Appl. No. 14/856,520, 5 pages. |
| Office Action, dated Jun. 30, 2017, received in U.S. Appl. No. 14/856,522, 22 pages. |
| Notice of Allowance, dated Feb. 9, 2018, received in U.S. Appl. No. 14/856,522, 9 pages. |
| Office Action, dated Feb. 1, 2016, received in U.S. Appl. No. 14/857,645, 15 pages. |
| Final Office Action, dated Jun. 16, 2016, received in U.S. Appl. No. 14/857,645, 12 pages. |
| Notice of Allowance, dated Oct. 24, 2016, received in U.S. Appl. No. 14/857,645, 6 pages. |
| Notice of Allowance, dated Jun. 16, 2017, received in in U.S. Appl. No. 14/857,645, 5 pages. |
| Office Action, dated Nov. 30, 2017, received in U.S. Appl. No. 14/857,636, 19 pages. |
| Notice of Allowance, dated Aug. 16, 2018, received in U.S. Appl. No. 14/857,636, 5 pages. |
| Office Action, dated Jan. 17, 2018, received in Australian Patent Application No. 20172202816, which corresponds with U.S. Appl. No. 14/857,636, 3 pages. |
| Notice of Allowance, dated Jan. 15, 2019, received in Australian Patent Application No. 2017202816, which corresponds with U.S. Appl. No. 14/857,636, 3 pages. |
| Certificate of Grant, dated May 16, 2019, received in Australian Patent Application No. 2017202816, which corresponds with U.S. Appl. No. 14/857,636, 4 pages. |
| Office Action, dated Jul. 1, 2020, received in Chinese Patent Application No. 201711262953.5, which corresponds with U.S. Appl. No. 14/857,636, 13 pages. |
| Patent, dated Nov. 27, 2020, received in Chinese Patent Application No. 201711262953.5, which corresponds with U.S. Appl. No. 14/857,636, 6 pages. |
| Office Action, dated Sep. 22, 2017, received in Japanese Patent Application No. 2017-029201, which corresponds with U.S. Appl. No. 14/857,636, 8 pages. |
| Office Action, dated Jun. 25, 2018, received in Japanese Patent Application No. 2017-029201, which corresponds with U.S. Appl. No. 14/857,636, 4 pages. |
| Office Action, dated Jan. 20, 2020, received in Japanese Patent Application No. 2017-029201, which corresponds with U.S. Appl. No. 14/857,636, 21 pages. |
| Notice of Allowance, dated Oct. 16, 2020, received in Japanese Patent Application No. 2017-029201, which corresponds with U.S. Appl. No. 14/857,636, 4 pages. |
| Patent, dated Nov. 12, 2020, received in Japanese Patent Application No. 2017-029201, which corresponds with U.S. Appl. No. 14/857,636, 3 pages. |
| Office Action, dated Nov. 28, 2018, received in Korean Patent Application No. 20177036645, which corresponds with U.S. Appl. No. 14/857,636, 6 pages. |
| Notice of Allowance, dated May 10, 2019, received in Korean Patent Application No. 20177036645, which corresponds with U.S. Appl. No. 14/857,636, 4 pages. |
| Patent, dated Jul. 11, 2019, received in Korean Patent Application No. 20177036645, which corresponds with U.S. Appl. No. 14/857,636, 8 pages. |
| Office Action, dated Dec. 1, 2017, received in U.S. Appl. No. 14/857,663, 15 pages. |
| Notice of Allowance, dated Aug. 16, 2018, received in U.S. Appl. No. 14/857,663, 5 pages. |
| Office Action, dated Jul. 14, 2020, received in Chinese Patent Application No. 201711261143.8, which corresponds with U.S. Appl. No. 14/857,663, 12 pages. |
| Notice of Allowance, dated Dec. 2, 2020, received in Chinese Patent Application No. 201711261143.8, which corresponds with U.S. Appl. No. 14/857,663, 3 pages. |
| Patent, dated Jan. 22, 2021, received in Chinese Patent Application No. 201711261143.8, which corresponds with U.S. Appl. No. 14/857,663, 6 pages. |
| Office Action, dated Nov. 11, 2019, received in Japanese Patent Application No. 2018-201076, which corresponds with U.S. Appl. No. 14/857,663, 7 pages. |
| Notice of Allowance, dated Sep. 18, 2020, received in Japanese Patent Application No. 2018-201076, which corresponds with U.S. Appl. No. 14/857,663, 5 pages. |
| Patent, dated Oct. 19, 2020, received in Japanese Patent Application No. 2018-201076, which corresponds with U.S. Appl. No. 14/857,663, 4 pages. |
| Office Action, dated Mar. 31, 2017, received in U.S. Appl. No. 14/857,700, 14 pages. |
| Final Office Action, dated Oct. 11, 2017, received in U.S. Appl. No. 14/857,700, 13 pages. |
| Notice of Allowance, dated Feb. 12, 2018, received in U.S. Appl. No. 14/857,700, 13 pages. |
| Notice of Allowance, dated Apr. 9, 2018, received in U.S. Appl. No. 14/857,700, 7 pages. |
| Notice of Allowance, dated Apr. 19, 2018, received in U.S. Appl. No. 14/864,529, 11 pages. |
| Notice of Allowance, dated Oct. 9, 2018, received in U.S. Appl. No. 14/864,529, 11 pages. |
| Office Action, dated Dec. 21, 2020, received in Korean Patent Application No. 2020-7029178, which corresponds with U.S. Appl. No. 14/870,882, 2 pages. |
| Notice of allowance, dated Jun. 28, 2021, received in Korean Patent Application No. 2020-7029178, which corresponds with U.S. Appl. No. 14/870,882, 2 pages. |
| Patent, dated Sep. 28, 2021, received in Korean Patent Application No. 2020-7029178, which corresponds with U.S. Appl. No. 14/870,882, 3 pages. |
| Grant of Patent, dated Apr. 16, 2018, received in Dutch Patent Application No. 2019215, 2 pages. |
| Office Action, dated Jan. 25, 2016, received in U.S. Appl. No. 14,864,580, 29 pages. |
| Notice of Allowance, dated May 23, 2016, received in U.S. Appl. No. 14/864,580, 9 pages. |
| Notice of Allowance, dated Aug. 4, 2016, received in U.S. Appl. No. 14/864,580, 9 pages. |
| Notice of Allowance, dated Dec. 28, 2016, received in U.S. Appl. No. 14/864,580, 8 pages. |
| Office Action, dated Aug. 19, 2016, received in Australian Patent Application No. 2016100648, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
| Office Action, dated Jul. 1, 2019, received in Australian Patent Application No. 2019200872, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
| Notice of Acceptance, dated Sep. 19, 2019, received in Australian Patent Application No. 2019200872, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Certificate of Grant, dated Jan. 23, 2020, received in Australian Patent Application No. 2019200872, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Office Action, dated Nov. 7, 2018, received in Chinese Patent Application No. 201610342151.4, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Notice of Allowance, dated Jun. 14, 2019, received in Chinese Patent Application No. 201610342151.4, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Patent, dated Jul. 30, 2019, received in Chinese Patent Application No. 201610342151.4, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
| Notice of Allowance, dated Nov. 8, 2016, received in Chinese Patent Application No. 201620470247.4, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Certificate of Registration, dated Oct. 14, 2016, received in German Patent Application No. 20201600003234.9, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Office Action, dated Apr. 8, 2016, received in Danish Patent Application No. 201500584, which corresponds with U.S. Appl. No. 14/864,580, 9 pages. |
| Office Action, dated Oct. 7, 2016, received in Danish Patent Application No. 201500584, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Office Action, dated May 5, 2017, received in Danish Patent Application No. 201500584, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Office Action, dated Dec. 15, 2017, received in Danish Patent Application No. 201500584, which corresponds with U.S. Appl. No. 14/864,580, 4 pages. |
| Office Action, dated Jun. 17, 2021, received in European Patent Application No. 19194418.0, which corresponds with U.S. Appl. No. 14/864,580, 7 pages. |
| Office Action, dated Aug. 23, 2022, received in European Patent Application No. 19194418.0, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
| Notice of Allowance, dated Feb. 4, 2022, received in Japanese Patent Application No. 2020-185336, which corresponds with U.S. Appl. No. 14/864,580, 2 pages. |
| Patent, dated Mar. 3, 2022, received in Japanese Patent Application No. 2020-185336, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
| Notice of Allowance, dated Aug. 14, 2019, received in Korean Patent Application No. 2019-7018317, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
| Patent, dated Nov. 12, 2019, received in Korean Patent Application No. 2019-7018317, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
| Notice of Allowance, dated Nov. 23, 2016, received in U.S. Appl. No. 14/864,601, 12 pages. |
| Notice of Allowance, dated Apr. 20, 2017, received in U.S. Appl. No. 14/864,601, 13 pages. |
| Office Action, dated Aug. 31, 2018, received in Australian Patent Application No. 2016276030, which corresponds with U.S. Appl. No. 14/864,601, 3 pages. |
| Certificate of Grant, dated Feb. 21, 2019, received in Australian Patent Application No. 14/864,601, which corresponds with U.S. Appl. No. 14/864,601, 4 pages. |
| Office Action, dated Feb. 4, 2019, received in European Patent Application No. 14/864,601, which corresponds with U.S. Appl. No. 14/864,601, 10 pages. |
| Intention to Grant, dated Jul. 18, 2019, received in European Patent Application No. 16730554.9, which corresponds with U.S. Appl. No. 14/864,601, 5 pages. |
| Decision to Grant, dated Sep. 12, 2019, received in European Patent Application No. 14/864,601, which corresponds with U.S. Appl. No. 14/864,601, 2 pages. |
| Patent, dated Oct. 9, 2019, received in European Patent Application No. 16730554.9, which corresponds with U.S. Appl. No. 14/864,601, 3 pages. |
| Notice of Allowance, dated Dec. 10, 2018, received in Japanese Patent Application No. 2017-561375, which corresponds with U.S. Appl. No. 14/864,601, 5 pages. |
| Patent, dated Jan. 11, 2019, received in Japanese Patent Application No. 2017- 561375, which corresponds with U.S. Appl. No. 14/864,601, 3 pages. |
| Office Action, dated Jan. 25, 2019, received in Korean Patent Application No. 2017-7033756, which corresponds with U.S. Appl. No. 14/864,601, 8 pages. |
| Notice of Allowance, dated May 29, 2019, received in Korean Patent Application No. 2017-7033756, which corresponds with U.S. Appl. No. 14/864,601, 6 pages. |
| Patent, dated Jun. 25, 2019, received in Korean Patent Application No. 2017-7033756, which corresponds with U.S. Appl. No. 14/864,601, 6 pages. |
| Office Action, dated Apr. 19, 2016, received in U.S. Appl. No. 14/864,627, 9 pages. |
| Notice of Allowance, dated Jan. 31, 2017, received in U.S. Appl. No. 14/864,627, 7 pages. |
| Office Action, dated Apr. 8, 2016, received in Danish Patent Application No. 201500585, which corresponds with U.S. Appl. No. 14/864,627, 9 pages. |
| Office Action, dated Oct. 7, 2016, received in Danish Patent Application No. 201500585, which corresponds with U.S. Appl. No. 14/864,627, 3 pages. |
| Office Action, dated May 5, 2017, received in Danish Patent Application No. 201500585, which corresponds with U.S. Appl. No. 14/864,627, 4 pages. |
| Office Action, dated Dec. 15, 2017, received in Danish Patent Application No. 201500585, which corresponds with U.S. Appl. No. 14/864,627, 5 pages. |
| Office Action, dated Mar. 29, 2016, received in U.S. Appl. No. 14/866,361, 22 pages. |
| Notice of Allowance, dated Jul. 19, 2016, received in U.S. Appl. No. 14/866,361, 8 pages. |
| Office Action, dated Jun. 10, 2016, received in Australian Patent Application No. 2016100292, which corresponds with U.S. Appl. No. 14/866,361, 4 pages. |
| Certificate of Examination, dated Dec. 8, 2016, received in Australian Patent Application No. 2016100292, which corresponds with U.S. Appl. No. 14/866,361, 1 page. |
| Office Action, dated Oct. 19, 2018, received in Chinese Patent Application No. 201610189298.4, which corresponds with U.S. Appl. No. 14/866,361, 6 pages. |
| Notice of Allowance, dated May 23, 2019, received in Chinese Patent Application No. 201610189298.4, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
| Patent, dated Jul. 23, 2019, received in Chinese Patent Application No. 201610189298.4, which corresponds with U.S. Appl. No. 14/866,361, 7 pages. |
| Notice of Allowance/Grant, dated Jul. 1, 2016, received in Chinese Patent Application No. 201620251706.X, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
| Letters Patent, dated Aug. 3, 2016, received in Chinese Patent Application No. 201620251706.X, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
| Certificate of Registration, dated Jun. 24, 2016, received in German Patent Application No. 202016001819.2, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
| Office Action, dated Apr. 7, 2016, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 10 pages. |
| Office Action, dated Oct. 28, 2016, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
| Office Action, dated Jun. 15, 2017, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 2 pages. |
| Office Action, dated Jan. 4, 2018, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 2 pages. |
| Notice of Allowance, dated Mar. 16, 2018, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 2 pages. |
| Patent, dated May 22, 2018, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 2 pages. |
| Office Action, dated Jun. 11, 2018, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 10 pages. |
| Office Action, dated Jan. 30, 2019, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 13 pages. |
| Office Action, dated Oct. 8, 2019, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 6 pages. |
| Intention to Grant, dated Apr. 14, 2020, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 7 pages. |
| Intention to Grant, dated Feb. 3, 2021, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 7 pages. |
| Patent, dated May 26, 2021, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
| Office Action, dated Oct. 12, 2018, received in Japanese Patent Application No. 2017-141962, which corresponds with U.S. Appl. No. 14/866,361, 6 pages. |
| Office Action, dated Jun. 10, 2019, received in Japanese Patent Application No. 2017-141962, which corresponds with U.S. Appl. No. 14/866,361, 6 pages. |
| Notice of Allowance, dated Oct. 7, 2019, received in Japanese Patent Application No. 2017-141962, which corresponds with U.S. Appl. No. 14/866,361, 5 pages. |
| Patent, dated Nov. 8, 2019, received in Japanese Patent Application No. 2017-141962, which corresponds with U.S. Appl. No. 14/866,361, 4 pages. |
| Office Action, dated Sep. 14, 2018, received in Korean Patent Application No. 2018-7013039, which corresponds with U.S. Appl. No. 14/866,361, 2 pages. |
| Notice of Allowance, dated Jan. 30, 2019, received in Korean Patent Application No. 2018-7013039, which corresponds with U.S. Appl. No. 14/866,361, 5 pages. |
| Patent, dated Apr. 3, 2019, received in Korean Patent Application No. 2018- 7013039, which corresponds with U.S. Appl. No. 14/866,361, 4 pages. |
| Office Action, dated Jan. 22, 2018, received in U.S. Appl. No. 14/866,987, 22 pages. |
| Final Office Action, dated Oct. 11, 2018, received in U.S. Appl. No. 14/866,987, 20 pages. |
| Notice of Allowance, dated Apr. 4, 2019, received in U.S. Appl. No. 14/866,987, 5 pages. |
| Patent, dated Aug. 8, 2016, received in Australian Patent Application No. 2016100649, which corresponds with U.S. Appl. No. 14/866,987, 1 page. |
| Office Action, dated Dec. 4, 2018, received in Chinese Patent Application No. 201610342336.5, which corresponds with U.S. Appl. No. 14/866,987, 5 pages. |
| Rejection Decision, dated Apr. 28, 2019, received in Chinese Patent Application No. 201610342336.5, which corresponds with U.S. Appl. No. 14/866,987, 4 pages. |
| Office Action, dated Aug. 15, 2019, received in Chinese Patent Application No. 201610342336.5, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Notice of Allowance, dated Dec. 3, 2019, received in Chinese Patent Application No. 201610342336.5, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Patent, dated Jan. 31, 2020, received in Chinese Patent Application No. 201610342336.5, which corresponds with U.S. Appl. No. 14/866,987, 7 pages. |
| Office Action, dated Oct. 19, 2016, received in Chinese Patent Application No. 2016201470246.X, which corresponds with U.S. Appl. No. 14/866,987, 4 pages. |
| Patent, dated May 3, 2017, received in Chinese Patent Application No. 2016201470246.X, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
| Patent, dated Sep. 19, 2016, received in German Patent Application No. 202016002908.9, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Office Action, dated Mar. 22, 2016, received in Danish Patent Application No. 201500587, which corresponds with U.S. Appl. No. 14/866,987, 8 pages. |
| Intention to Grant, dated Jun. 10, 2016, received in Danish Patent Application No. 201500587, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
| Notice of Allowance, dated Nov. 1, 2016, received in Danish Patent Application No. 201500587, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
| Office Action, dated Sep. 9, 2016, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 7 pages. |
| Notice of Allowance, dated Jan. 31, 2017, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Office Action, dated Apr. 19, 2017, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Notice of Allowance, dated Sep. 29, 2017, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
| Patent, dated Nov. 6, 2017, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 6 pages. |
| Office Action, dated May 7, 2018, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 5 pages. |
| Office Action, dated Dec. 11, 2018, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 6 pages. |
| Intention to Grant, dated Jun. 14, 2019, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 7 pages. |
| Intention to Grant, dated Oct. 25, 2019, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 7 pages. |
| Decision to Grant, dated Nov. 14, 2019, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
| Patent, dated Dec. 11, 2019, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Office Action, dated Feb. 3, 2020, received in European Patent Application No. 17163309.2, which corresponds with U.S. Appl. No. 14/866,987, 6 pages. |
| Office Action, dated Dec. 22, 2021, received in European Patent Application No. 17163309.2, which corresponds with U.S. Appl. No. 14/866,987, 4 pages. |
| Patent, dated Feb. 5, 2021, received in Hong Kong Patent Application No. 1235878, which corresponds with U.S. Appl. No. 14/866,987, 6 pages. |
| Patent, dated Jan. 8, 2021, received in Hong Kong Patent Application No. 18100151.5, which corresponds with U.S. Appl. No. 14/866,987, 6 pages. |
| Office Action, dated Aug. 26, 2020, received in Indian Application No. 201617032291, which corresponds with U.S. Appl. No. 14/866,987, 9 pages. |
| Notice of Allowance, dated Sep. 22, 2017, received in Japanese Patent Application No. 2016-233449, which corresponds with U.S. Appl. No. 14/866,987, 5 pages. |
| Patent, dated Oct. 27, 2017, received in Japanese Patent Application No. 2016-233449, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Office Action, dated Jul. 31, 2017, received in Japanese Patent Application No. 2017126445, which corresponds with U.S. Appl. No. 14/866,987, 6 pages. |
| Notice of Allowance, dated Mar. 6, 2018, received in Japanese Patent Application No. 2017-126445, which corresponds with U.S. Appl. No. 14/866,987, 5 pages. |
| Patent, dated Apr. 6, 2018, received in Japanese Patent Application No. 2017-126445, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
| Office Action, dated Nov. 29, 2017, received in U.S. Appl. No. 14/866,989, 31 pages. |
| Final Office Action, dated Jul. 3, 2018, received in U.S. Appl. No. 14/866,989, 17 pages. |
| Notice of Allowance, dated Jan. 17, 2019, received in U.S. Appl. No. 14/866,989, 8 pages. |
| Certificate of Exam, dated Jul. 21, 2016, received in Australian Patent Application No. 2016100652, which corresponds with U.S. Appl. No. 14/866,989, 1 page. |
| Office Action, dated Feb. 26, 2018, received in Australian Patent Application No. 2017201079, which corresponds with U.S. Appl. No. 14/866,989, 6 pages. |
| Notice of Acceptance, dated Feb. 14, 2019, received in Australian Patent Application No. 217201079, which corresponds with U.S. Appl. No. 14/866,989, 3 pages. |
| Certificate of Grant, dated Jun. 13, 2019, received in Australian Patent Application No. 2017201079, which corresponds with U.S. Appl. No. 14/866,989, 1 page. |
| Office Action, dated Sep. 19, 2018, received in Chinese Patent Application No. 201610342314.9, which corresponds with U.S. Appl. No. 14/866,989, 6 pages. |
| Office Action, dated Feb. 25, 2019, received in Chinese Patent Application No. 201610342314.9, which corresponds with U.S. Appl. No. 14/866,989, 3 pages. |
| Rejection Decision, dated Apr. 24, 2019, received in Chinese Patent Application No. 201610342314.9, which corresponds with U.S. Appl. No. 14/866,989, 3 pages. |
| Office Action, dated Jun. 16, 2017, received in Japanese Patent Application No. 2016-233450, which corresponds with U.S. Appl. No. 14/866,989, 6 pages. |
| Patent, dated Mar. 9, 2018, received in Japanese Patent Application No. 2016-233450, which corresponds with U.S. Appl. No. 14/866,989, 4 pages. |
| Office Action, dated Apr. 1, 2016, received in Danish Patent Application No. 201500589, which corresponds with U.S. Appl. No. 14/866,989, 8 pages. |
| Intention to Grant, dated Jun. 10, 2016, received in Danish Patent Application No. 201500589, which corresponds with U.S. Appl. No. 14/866,989, 2 pages. |
| Notice of Allowance, dated Nov. 1, 2016, received in Danish Patent Application No. 201500589, which corresponds with U.S. Appl. No. 14/866,989, 2 pages. |
| Office Action, dated Feb. 3, 2020, received in European Patent Application No. 16189425.8, which corresponds with U.S. Appl. No. 14/866,989, 6 pages. |
| Intention to Grant, dated Dec. 3, 2020, received in European Patent Application No. 16189425.8, which corresponds with U.S. Appl. No. 14/866,989, 7 pages. |
| Decision to Grant, dated Feb. 25, 2021, received in European Patent Application No. 16189425.8, which corresponds with U.S. Appl. No. 14/866,989, 1 page. |
| Notice of Allowance, dated Feb. 5, 2018, received in Japanese Patent Application No. 2016-233450, which corresponds with U.S. Appl. No. 14/866,989, 5 pages. |
| Office Action, dated Apr. 11, 2016, received in U.S. Appl. No. 14/871,236, 23 pages. |
| Office Action, dated Jun. 28, 2016, received in U.S. Appl. No. 14/871,236, 21 pages. |
| Final Office Action, dated Nov. 4, 2016, received in U.S. Appl. No. 14/871,236, 24 pages. |
| Notice of Allowance, dated Feb. 28, 2017, received in U.S. Appl. No. 14/871,236, 9 pages. |
| Innovation Patent, dated Aug. 25, 2016, received in Australian Patent Application No. 2016101433, which corresponds with U.S. Appl. No. 14/871,236, 1 page. |
| Office Action, dated Oct. 14, 2016, received in Australian Patent Application No. 2016101433, which corresponds with U.S. Appl. No. 14/871,236, 3 pages. |
| Office Action, dated Jun. 23, 2020, received in Brazilian Patent Application No. 11201701119-9, which corresponds with U.S. Appl. No. 14/871,236, 9 pages. |
| Office Action, dated Sep. 30, 2019, received in Chinese Patent Application No. 201610871466.8, which corresponds with U.S. Appl. No. 14/871,236, 4 pages. |
| Notice of Allowance, dated Mar. 24, 2020, received in Chinese Patent Application No. 201610871466.8, which corresponds with U.S. Appl. No. 14/871,236, 3 pages. |
| Patent, dated May 19, 2020, received in Chinese Patent Application No. 201610871466.8, which corresponds with U.S. Appl. No. 14/871,236, 8 pages. |
| Office Action, dated Apr. 8, 2016, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 12 pages. |
| Office Action, dated May 26, 2016, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 14 pages. |
| Office Action, dated Sep. 30, 2016, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 10 pages. |
| Office Action, dated Jun. 15, 2017, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 4 pages. |
| Office Action, dated Jan. 29, 2018, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 2 pages. |
| Notice of Allowance, dated Apr. 26, 2018, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 2 pages. |
| Patent, dated Jun. 18, 2018, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 3 pages. |
| Intention to Grant, dated Dec. 4, 2019, received in European Patent Application No. 18168941.5, which corresponds with U.S. Appl. No. 14/871,236, 8 pages. |
| Intention to Grant, dated Oct. 5, 2020, received in European Patent Application No. 18168941.5, which corresponds with U.S. Appl. No. 14/871,236, 8 pages. |
| Decision to Grant, dated Mar. 25, 2021, received in European Patent Application No. 18168941.5, which corresponds with U.S. Appl. No. 14/871,236, 2 pages. |
| Patent, dated Apr. 21, 2021, received in European Patent Application No. 18168941.5, which corresponds with U.S. Appl. No. 14/871,236, 3 pages. |
| Office Action, dated Mar. 17, 2020, received in Mx/a/2017/011610, which corresponds with U.S. Appl. No. 14/871,236, 4 pages. |
| Notice of Allowance, dated Sep. 7, 2020, received in Mx/a/2017/011610, which corresponds with U.S. Appl. No. 14/871,236, 12 pages. |
| Patent, dated Dec. 2, 2020, received in Mx/a/2017/011610 (7337MX), which corresponds with U.S. Appl. No. 14/871,236, 4 pages. |
| Office Action, dated Jul. 19, 2018, received in Russian Patent Application No. 2017131408, which corresponds with U.S. Appl. No. 14/871,236, 8 pages. |
| Patent, dated Feb. 15, 2019, received in Russian Patent Application No. 2017131408, which corresponds with U.S. Appl. No. 14/871,236, 2 pages. |
| Office Action, dated Sep. 1, 2017, received in U.S. Appl. No. 14/870,754, 22 pages. |
| Final Office Action, dated Mar. 9, 2018, received in U.S. Appl. No. 14/870,754, 19 pages. |
| Notice of Allowance, dated Jul. 2, 2018, received in U.S. Appl. No. 14/870,754, 9 pages. |
| Notice of Allowance, dated Dec. 3, 2018, received in U.S. Appl. No. 14/870,754, 8 pages. |
| Office Action, dated Nov. 14, 2017, received in U.S. Appl. No. 14/870,882, 25 pages. |
| Final Office Action, dated Apr. 20, 2018, received in U.S. Appl. No. 14/870,882, 7 pages. |
| Notice of Allowance, dated Jul. 12, 2018, received in U.S. Appl. No. 14/870,882, 5 pages. |
| Notice of Allowance, dated Dec. 5, 2018, received in U.S. Appl. No. 14/870,882, 8 pages. |
| Innovation Patent, dated Aug. 25, 2016, received in Australian Patent Application No. 2016101436, which corresponds with U.S. Appl. No. 14/871,236, 1 page. |
| Office Action, dated Oct. 31, 2016, received in Australian Patent Application No. 2016101438, which corresponds with U.S. Appl. No. 14/871,236, 6 pages. |
| Office Action, dated Nov. 28, 2019, received in Chinese Patent Application No. 201610870912.3, which corresponds with U.S. Appl. No. 14/870,882, 10 pages. |
| Office Action, dated Aug. 3, 2020, received in Chinese Patent Application No. 201610870912.3, which corresponds with U.S. Appl. No. 14/870,882, 4 pages. |
| Office Action, dated Dec. 21, 2020, received in Chinese Patent Application No. 201610870912.3, which corresponds with U.S. Appl. No. 14/870,882, 5 pages. |
| Notice of Allowance, dated Mar. 22, 2021, received in Chinese Patent Application No. 201610870912.3, which corresponds with U.S. Appl. No. 14/870,882, 1 page. |
| Patent, dated May 25, 2021, received in Chinese Patent Application No. 201610870912.3, which corresponds with U.S. Appl. No. 14/870,882, 8 pages. |
| Office Action, dated Apr. 6, 2016, received in Danish Patent Application No. 201500596, which corresponds with U.S. Appl. No. 14/870,882, 7 pages. |
| Office Action, dated Jun. 9, 2016, received in Danish Patent Application No. 201500596, which corresponds with U.S. Appl. No. 14/870,882, 9 pages. |
| Notice of Allowance, dated Oct. 31, 2017, received in Danish Patent Application No. 201500596, which corresponds with U.S. Appl. No. 14/870,882, 2 pages. |
| Patent, dated Jan. 29, 2018, received in Danish Patent Application No. 201500596, which corresponds with U.S. Appl. No. 14/870,882, 4 pages. |
| Office Action, dated Feb. 11, 2019, received in European Patent Application No. 17171972.7, which corresponds with U.S. Appl. No. 14/870,882, 7 pages. |
| Office Action, dated Sep. 1, 2017, received in U.S. Appl. No. 14/870,988, 14 pages. |
| Final Office Action, dated Feb. 16, 2018, received in U.S. Appl. No. 14/870,988, 18 pages. |
| Notice of Allowance, dated Aug. 27, 2018, received in U.S. Appl. No. 14/870,988, 11 pages. |
| Office Action, dated Nov. 22, 2017, received in U.S. Appl. No. 14/871,227, 24 pages. |
| Notice of Allowance, dated Jun. 11, 2018, received in U.S. Appl. No. 14/871,227, 11 pages. |
| Office Action, dated Oct. 17, 2016, received in Australian Patent Application No. 2016203040, which corresponds with U.S. Appl. No. 14/871,227, 7 pages. |
| Office Action, dated Oct. 16, 2017, received in Australian Patent Application No. 2016203040, which corresponds with U.S. Appl. No. 14/871,227, 5 pages. |
| Notice of Acceptance, dated Oct. 30, 2018, received in Australian Patent Application No. 2016203040, which corresponds with U.S. Appl. No. 14/871,227, 4 pages. |
| Certificate of Grant, dated Feb. 28, 2019, received in Australian Patent Application No. 2016203040, which corresponds with U.S. Appl. No. 14/871,227, 1 page. |
| Office Action, dated Oct. 18, 2016, received in Australian Patent Application No. 2016101431, which corresponds with U.S. Appl. No. 14/871,227, 3 pages. |
| Office Action, dated Apr. 13, 2017, received in Australian Patent Application No. 2016101431, which corresponds with U.S. Appl. No. 14/871,227, 4 pages. |
| Office Action, dated Oct. 11, 2018, received in Australian Patent Application No. 2017245442, which corresponds with U.S. Appl. No. 14/871,227, 4 pages. |
| Office Action, dated Nov. 16, 2018, received in Chinese Patent Application No. 201680000466.9, which corresponds with U.S. Appl. No. 14/871,227, 5 pages. |
| Notice of Allowance, dated Jun. 5, 2019, received in Chinese Patent Application No. 201680000466.9, which corresponds with U.S. Appl. No. 14/871,227, 5 pages. |
| Patent, dated Aug. 9, 2019, received in Chinese Patent Application No. 201680000466.9, which corresponds with U.S. Appl. No. 14/871,227, 8 pages. |
| Intention to Grant, dated Apr. 7, 2016, received in Danish Patent Application No. 201500597, which corresponds with U.S. Appl. No. 14/871,227, 7 pages. |
| Grant, dated Jun. 21, 2016, received in Danish Patent Application No. 201500597, which corresponds with U.S. Appl. No. 14/871,227, 2 pages. |
| Patent, dated Sep. 26, 2016, received in Danish Patent Application No. 201500597, which corresponds with U.S. Appl. No. 14/871,227, 7 pages. |
| Intent to Grant, dated Sep. 17, 2018, received in European Patent No. 16711743.1, which corresponds with U.S. Appl. No. 14/871,227, 5 pages. |
| Patent, dated Nov. 28, 2018, received in European Patent No. 16711743.1, which corresponds with U.S. Appl. No. 14/871,227, 1 page. |
| Office Action, dated Jul. 20, 2020, received in Indian Patent Application No. 201617032293, which corresponds with U.S. Appl. No. 14/871,227, 9 pages. |
| Office Action, dated Mar. 24, 2017, received in Japanese Patent Application No. 2016-533201, which corresponds with U.S. Appl. No. 14/871,227, 6 pages. |
| Office Action, dated Aug. 4, 2017, received in Japanese Patent Application No. 2016-533201, which corresponds with U.S. Appl. No. 14/871,227, 6 pages. |
| Notice of Allowance, dated Jan. 4, 2018, received in Japanese Patent Application No. 2016-533201, which corresponds with U.S. Appl. No. 14/871,227, 4 pages. |
| Patent, dated Feb. 9, 2018, received in Japanese Patent Application No. 2016-533201, which corresponds with U.S. Appl. No. 14/871,227, 4 pages. |
| Office Action, dated Feb. 20, 2018, received in Korean Patent Application No. 2016-7019816, which corresponds with U.S. Appl. No. 14/871,227, 8 pages. |
| Notice of Allowance, dated Oct. 1, 2018, received in Korean Patent Application No. 2016-7019816, which corresponds with U.S. Appl. No. 14/871,227, 6 pages. |
| Patent, dated Dec. 28, 2018, received in Korean Patent Application No. 2016- 7019816, which corresponds with U.S. Appl. No. 14/871,227, 8 pages. |
| Office Action, dated Oct. 26, 2017, received in U.S. Appl. No. 14/871,336, 22 pages. |
| Final Office Action, dated Mar. 15, 2018, received in U.S. Appl. No. 14/871,336, 23 pages. |
| Office Action, dated Nov. 5, 2018, received in U.S. Appl. No. 14/871,336, 24 pages. |
| Notice of Allowance, dated Feb. 5, 2019, received in U.S. Appl. No. 14/871,336, 10 pages. |
| Office Action, dated Oct. 14, 2016, received in Australian Patent Application No. 2016101437, which corresponds with U.S. Appl. No. 14/871,336, 2 pages. |
| Office Action, dated Apr. 11, 2017, received in Australian Patent Application No. 2016101437, which corresponds with U.S. Appl. No. 14/871,336, 4 pages. |
| Office Action, dated Nov. 4, 2019, received in Chinese Patent Application No. 201610871323.7, which corresponds with U.S. Appl. No. 14/871,336, 12 pages. |
| Office Action, dated Aug. 4, 2020, received in Chinese Patent Application No. 201610871323.7, which corresponds with U.S. Appl. No. 14/871,336, 18 pages. |
| Office Action, dated Feb. 9, 2021, received in Chinese Patent Application No. 201610871323.7, which corresponds with U.S. Appl. No. 14/871,336, 1 page. |
| Office Action, dated Jun. 1, 2021, received in Chinese Patent Application No. 201610871323.7, which corresponds with U.S. Appl. No. 14/871,336, 1 page. |
| Office Action, dated Apr. 18, 2016, received in Danish Patent Application No. 201500601, which corresponds with U.S. Appl. No. 14/871,336, 8 pages. |
| Office Action, dated Oct. 18, 2016, received in Danish Patent Application No. 201500601, which corresponds with U.S. Appl. No. 14/871,336, 3 pages. |
| Notice of Allowance, dated Mar. 23, 2017, received in Danish Patent Application No. 201500601, which corresponds with U.S. Appl. No. 14/871,336, 2 pages. |
| Patent, dated Oct. 30, 2017, Danish Patent Application No. 201500601, which corresponds with U.S. Appl. No. 14/871,336, 5 pages. |
| Office Action, dated Feb. 12, 2019, received in European Patent Application No. 17172266.3, which corresponds with U.S. Appl. No. 14/871,336, 6 pages. |
| Office Action, dated Apr. 2, 2018, received in Japanese Patent Application No. 2018-020324, which corresponds with U.S. Appl. No. 14/871,336, 4 pages. |
| Notice of Allowance, dated Oct. 12, 2018, received in Japanese Patent Application No. 2018-020324, which corresponds with U.S. Appl. No. 14/871,336, 5 pages. |
| Patent, dated Nov. 16, 2018, received in Japanese Patent Application No. 2018-020324, which corresponds with U.S. Appl. No. 14/871,336, 4 pages. |
| Office Action, dated Oct. 16, 2017, received in U.S. Appl. No. 14/871,462, 26 pages. |
| Innovation Patent, dated Aug. 25, 2016, received in Australian Patent Application No. 2016101435, which corresponds with U.S. Appl. No. 14/871,462, 1 page. |
| Office Action, dated Oct. 4, 2016, received in Australian Patent Application No. 2016101435, which corresponds with U.S. Appl. No. 14/871,462, 3 pages. |
| Office Action, dated Oct. 4, 2016, received in Australian Patent Application No. 2016231505, which corresponds with U.S. Appl. No. 14/871,462, 3 pages. |
| Office Action, dated Sep. 29, 2017, received in Australian Patent Application No. 2016231505, which corresponds with U.S. Appl. No. 14/871,462, 5 pages. |
| Innovation Patent, dated Oct. 11, 2017, received in Australian Patent Application No. 14/871,462, which corresponds with U.S. Appl. No. 14/871,462, 1 page. |
| Office Action, dated Oct. 9, 2021, received in Chinese Patent Application No. 201610869950.7, which corresponds with U.S. Appl. No. 14/871,462, 5 pages. |
| Notice of Allowance, dated Feb. 9, 2022, received in Chinese Patent Application No. 201610869950.7, which corresponds with U.S. Appl. No. 14/871,462, 1 page. |
| Patent, dated Mar. 8, 2022, received in Chinese Patent Application No. 201610869950.7, which corresponds with U.S. Appl. No. 14/871,462, 7 pages. |
| Office Action, dated Apr. 20, 2017, received in Chinese Patent Application No. 201621044346.2, which corresponds with U.S. Appl. No. 14/871,462, 3 pages. |
| Intention to Grant, dated Apr. 18, 2016, received in Danish Patent Application No. 201500600, which corresponds with U.S. Appl. No. 14/871,462, 7 pages. |
| Grant, dated Aug. 30, 2016, received in Danish Patent Application No. 201500600, which corresponds with U.S. Appl. No. 14/871,462, 2 pages. |
| Office Action, dated Mar. 13, 2017, received in Japanese Patent Application No. 2016-183289, which corresponds with U.S. Appl. No. 14/871,462, 5 pages. |
| Office Action, dated Nov. 13, 2017, received in Japanese Patent Application No. 2016-183289, which corresponds with U.S. Appl. No. 14/871,462, 5 pages. |
| Office Action, dated Apr. 29, 2016, received in U.S. Appl. No. 14/867,823, 28 pages. |
| Final Office Action, dated Sep. 28, 2016, received in U.S. Appl. No. 14/867,823, 31 pages. |
| Office Action, dated May 11, 2017, received in U.S. Appl. No. 14/867,823, 42 pages. |
| Final Office Action, dated Nov. 29, 2017, received in U.S. Appl. No. 14/867,823, 47 pages. |
| Notice of Allowance, dated Apr. 18, 2018, received in U.S. Appl. No. 14/867,823, 10 pages. |
| Notice of Allowance, dated Aug. 7, 2018, received in U.S. Appl. No. 14/867,823, 8 pages. |
| Office Action, dated Mar. 18, 2016, received in Danish Patent Application No. 201500594, which corresponds with U.S. Appl. No. 14/867,823, 10 pages. |
| Office Action, dated Sep. 7, 2016, received in Danish Patent Application No. 201500594, which corresponds with U.S. Appl. No. 14/867,823, 4 pages. |
| Office Action, dated May 15, 2017, received in Danish Patent Application No. 201500594, which corresponds with U.S. Appl. No. 14/867,823, 4 pages. |
| Office Action, dated Jan. 23, 2018, received in Danish Patent Application No. 201500594, which corresponds with U.S. Appl. No. 14/867,823, 8 pages. |
| Office Action, dated May 10, 2016, received in U.S. Appl. No. 14/867,892, 28 pages. |
| Final Office Action, dated Nov. 2, 2016, received in U.S. Appl. No. 14/867,892, 48 pages. |
| Office Action, dated Jul. 6, 2017, received in U.S. Appl. No. 14/867,892, 55 pages. |
| Final Office Action, dated Dec. 14, 2017, received in U.S. Appl. No. 14/867,892, 53 pages. |
| Office Action, dated Apr. 24, 2018, received in U.S. Appl. No. 14/867,892, 63 pages. |
| Final Office Action, dated Oct. 17, 2018, received in U.S. Appl. No. 14/867,892, 48 pages. |
| Examiner's Answer, dated Jul. 18, 2019, received in U.S. Appl. No. 14/867,892, 17 pages. |
| Notice of Allowance, dated May 26, 2021, received in U.S. Appl. No. 14/867,892, 7 pages. |
| Notice of Allowance, dated Jul. 13, 2021, received in U.S. Appl. No. 14/867,892, 8 pages. |
| Office Action, dated Mar. 21, 2016, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 9 pages. |
| Office Action, dated Sep. 14, 2016, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 4 pages. |
| Office Action, dated May 4, 2017, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 4 pages. |
| Office Action, dated Oct. 31, 2017, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 2 pages. |
| Notice of Allowance, dated Jan. 26, 2018, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 2 pages. |
| Office Action, dated Feb. 28, 2018, received in U.S. Appl. No. 14/869,361, 26 pages. |
| Final Office Action, dated Oct. 4, 2018, received in U.S. Appl. No. 14/869,361, 28 pages. |
| Office Action, dated Feb. 27. 2019, received in U.S. Appl. No. 14/869,361, 28 pages. |
| Office Action, dated Mar. 1, 2017, received in U.S. Appl. No. 14/869,855, 14 pages. |
| Final Office Action, dated Oct. 10, 2017, received in U.S. Appl. No. 14/869,855, 16 pages. |
| Office Action, dated Jan. 23, 2018, received in U.S. Appl. No. 14/869,855, 24 pages. |
| Notice of Allowance, dated May 31, 2018, received in U.S. Appl. No. 14/869,855, 10 pages. |
| Office Action, dated Feb. 9, 2017, received in U.S. Appl. No. 14/869,873, 17 pages. |
| Final Office Action, dated Aug. 18, 2017, received in U.S. Appl. No. 14/869,873, 20 pages. |
| Office Action, dated Jan. 18, 2018, received in U.S. Appl. No. 14/869,873, 25 pages. |
| Final Office Action, dated May 23, 2018, received in U.S. Appl. No. 14/869,873, 18 pages. |
| Notice of Allowance, dated Jul. 30, 2018, received in U.S. Appl. No. 14/869,873, 8 pages. |
| Office Action, dated Jan. 11, 2018, received in U.S. Appl. No. 14/869,997, 17 pages. |
| Office Action, dated Sep. 7, 2018, received in U.S. Appl. No. 14/869,997, 23 pages. |
| Notice of Allowance, dated Apr. 4, 2019, received in U.S. Appl. No. 14/869,997, 9 pages. |
| Notice of Allowance, dated Jan. 17, 2018, received in U.S. Appl. No. 14/867,990, 12 pages. |
| Notice of Allowance, dated Mar. 30, 3018, received in U.S. Appl. No. 14/867,990, 5 pages. |
| Office Action, dated May 23, 2016, received in Australian Patent Application No. 2016100253, which corresponds with U.S. Appl. No. 14/867,990, 5 pages. |
| Notice of Allowance, dated May 21, 2019, received in Chinese Patent Application No. 201610131507.X, which corresponds with U.S. Appl. No. 14/867,990, 3 pages. |
| Patent, dated Jul. 19, 2019, received in Chinese Patent Application No. 201610131507.X, which corresponds with U.S. Appl. No. 14/867,990, 6 pages. |
| Office Action, dated Jul. 5, 2016, received in Chinese Patent Application No. 201620176221.9, which corresponds with U.S. Appl. No. 14/867,990, 4 pages. |
| Office Action, dated Oct. 25, 2016, received in Chinese Patent Application No. 201620176221.9, which corresponds with U.S. Appl. No. 14/867,990, 7 pages. |
| Certificate of Registration, dated Jun. 16, 2016, received in German Patent No. 202016001489.8, which corresponds with U.S. Appl. No. 14/867,990, 3 pages. |
| Office Action, dated Mar. 18, 2016, received in Danish Patent Application No. 201500581, which corresponds with U.S. Appl. No. 14/867,990, 9 pages. |
| Office Action, dated Sep. 26, 2016, received in Danish Patent Application No. 201500581, which corresponds with U.S. Appl. No. 14/867,990, 5 pages. |
| Office Action, dated May 3, 2017, received in Danish Patent Application No. 201500581, which corresponds with U.S. Appl. No. 14/867,990, 5 pages. |
| Office Action, dated Feb. 19, 2018, received in Danish Patent Application No. 201500581, which corresponds with U.S. Appl. No. 14/867,990, 4 pages. |
| Office Action, dated Feb. 21, 2020, received in European Patent Application No. 16711725.8, which corresponds with U.S. Appl. No. 14/867,990, 13 pages. |
| Office Action, dated May 14, 2021, received in European Patent Application No. 16711725.8, which corresponds with U.S. Appl. No. 14/867,990, 7 pages. |
| Intent to Grant, dated Jan. 9, 2023, received in European Patent Application No. 16711725.8, which corresponds with U.S. Appl. No. 14/867,990, 7 pages. |
| Office Action, dated Apr. 19, 2018, received in U.S. Appl. No. 14/869,703, 19 pages. |
| Final Office Action, dated Oct. 26, 2018, received in U.S. Appl. No. 14/869,703, 19 pages. |
| Notice of Allowance, dated Mar. 12, 2019, received in U.S. Appl. No. 14/869,703, 6 pages. |
| Office Action, dated Dec. 12, 2017, received in U.S. Appl. No. 15/009,668, 32 pages. |
| Final Office Action, dated Jul. 3, 2018, received in U.S. Appl. No. 15/009,668, 19 pages. |
| Office Action, dated Jan. 10, 2019, received in U.S. Appl. No. 15/009,668, 17 pages. |
| Notice of Allowance, dated May 1, 2019, received in U.S. Appl. No. 15/009,668, 12 pages. |
| Office Action, dated Aug. 20, 2020, received in Chinese Patent Application No. 201680046985.9, which corresponds with U.S. Appl. No. 15/009,668, 15 pages. |
| Notice of Allowance, dated Apr. 20, 2021, received in Chinese Patent Application No. 201680046985.9, which corresponds with U.S. Appl. No. 15/009,668, 1 page. |
| Office Action, dated Jan. 31, 2020, received in European Patent Application No. 16753795.0, which corresponds with U.S. Appl. No. 15/009,668, 9 pages. |
| Office Action, dated Mar. 19, 2021, received in European Patent Application No. 16753795.0, which corresponds with U.S. Appl. No. 15/009,668, 5 pages. |
| Intention to Grant, dated Sep. 26, 2022, received in European Patent Application No. 16753795.0, which corresponds with U.S. Appl. No. 15/009,668, 7 pages. |
| Decision to Grant, dated Nov. 24, 2022, received in European Patent Application No. 16753795.0, which corresponds with U.S. Appl. No. 15/009,668, 4 pages. |
| Patent, dated Dec. 21, 2023, received in European Patent Application No. 16753795.0, which corresponds with U.S. Appl. No. 15/009,668, 4 pages. |
| Office Action, dated Nov. 25, 2016, received in U.S. Appl. No. 15/081,771, 17 pages. |
| Final Office Action, dated Jun. 2, 2017, received in U.S. Appl. No. 15/081,771, 17 pages. |
| Notice of Allowance, dated Dec. 4, 2017, received in U.S. Appl. No. 15/081,771, 10 pages. |
| Office Action, dated Feb. 1, 2018, received in Australian Patent Application No. 2017202058, which corresponds with U.S. Appl. No. 15/081,771, 4 pages. |
| Notice of Acceptance, dated Jan. 24, 2019, received in Australian Patent Application No. 2017202058, which corresponds with U.S. Appl. No. 15/081,771, 3 pages. |
| Certificate of Grant, dated May 23, 2019, received in Australian Patent Application No. 2017202058, which corresponds with U.S. Appl. No. 15/081,771, 1 page. |
| Office Action, dated Mar. 2, 2022, received in Chinese Patent Application No. 201811561188.1, which corresponds with U.S. Appl. No. 15/081,771, 1 page. |
| Office Action, dated Jan. 24, 2020, received in European Patent Application No. 18205283.7, which corresponds with U.S. Appl. No. 15/081,771, 4 pages. |
| Intention to Grant, dated Apr. 30, 2020, received in European Patent Application No. 18205283.7, which corresponds with U.S. Appl. No. 15/081,771, 7 pages. |
| Decision to Grant, dated Aug. 27, 2020, received in European Patent Application No. 18205283.7, which corresponds with U.S. Appl. No. 15/081,771, 4 pages. |
| Patent, dated Sep. 23, 2020, received in European Patent Application No. 18205283.7, which corresponds with U.S. Appl. No. 15/081,771, 4 pages. |
| Office Action, dated Jan. 26, 2018, received in Japanese Patent Application No. 2017-086460, which corresponds with U.S. Appl. No. 15/081,771, 6 pages. |
| Notice of Allowance, dated Oct. 12, 2018, received in Japanese Patent Application No. 2017-086460, which corresponds with U.S. Appl. No. 15/081,771, 5 pages. |
| Office Action, dated Aug. 29, 2017, received in Korean Patent Application No. 2017-7014536, which corresponds with U.S. Appl. No. 15/081,771, 5 pages. |
| Notice of Allowance, dated Jun. 28, 2018, received in Korean Patent Application No. 2017-7014536, which corresponds with U.S. Appl. No. 15/081,771, 4 pages. |
| Patent, dated Sep. 28, 2018, received in Korean Patent Application No. 2017-7014536, which corresponds with U.S. Appl. No. 15/081,771, 3 pages. |
| Final Office Action, dated May 1, 2017, received in U.S. Appl. No. 15/136,782, 18 pages. |
| Notice of Allowance, dated Oct. 20, 2017, received in U.S. Appl. No. 15/136,782, 9 pages. |
| Office Action, dated May 4, 2018, received in Australian Patent Application No. 2018202855, which corresponds with U.S. Appl. No. 15/136,782, 3 pages. |
| Notice of Acceptance, dated Sep. 10, 2018, received in Australian Patent Application No. 2018202855, which corresponds with U.S. Appl. No. 15/136,782, 3 pages. |
| Certificate of Grant, dated Jan. 17. 2019, received in Australian Patent Application No. 2018202855, which corresponds with U.S. Appl. No. 15/136,782, 4 pages. |
| Office Action, dated Sep. 27, 2019, received in Chinese Patent Application No. 201810119007.3, which corresponds with U.S. Appl. No. 15/136,782, 6 pages. |
| Notice of Allowance, dated Feb. 26, 2020, received in Chinese Patent Application No. 201810119007.3, which corresponds with U.S. Appl. No. 15/136,782, 3 pages. |
| Patent, dated Apr. 7, 2020, received in Chinese Patent Application No. 201810119007.3, which corresponds with U.S. Appl. No. 15/136,782, 7 pages. |
| Office Action, dated May 23, 2017, received in Danish Patent Application No. 201770190, which corresponds with U.S. Appl. No. 15/136,782, 7 pages. |
| Office Action, dated Jan. 8, 2018, received in Danish Patent Application No. 201770190, which corresponds with U.S. Appl. No. 15/136,782, 2 pages. |
| Notice of Allowance, dated Mar. 19, 2018, received in Danish Patent Application No. 201770190, which corresponds with U.S. Appl. No. 15/136,782, 2 pages. |
| Patent, dated May 22, 2018, received in Danish Patent Application No. 201770190, which corresponds with U.S. Appl. No. 15/136,782, 2 pages. |
| Office Action, dated Apr. 17, 2019, received in European Patent Application No. 18171453.6, which corresponds with U.S. Appl. No. 15/136,782, 4 pages. |
| Office Action, dated Oct. 2, 2019, received in European Patent Application No. 18171453.6, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Office Action, dated May 12, 2020, received in European Patent Application No. 18171453.6, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Patent, dated Feb. 5, 2021, received in Hong Kong Patent Application No. 1257553, which corresponds with U.S. Appl. No. 15/136,782, 14 pages. |
| Office Action, dated Jun. 1, 2018, received in Japanese Patent Application No. 2018-062161, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Office Action, dated Nov. 12, 2018, received in Japanese Patent Application No. 2018-062161, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Notice of Allowance, dated Feb. 18, 2019, received in Japanese Patent Application No. 2018-062161, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Patent, dated Mar. 22, 2019, received in Japanese Patent Application No. 2018- 062161, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Office Action, dated Oct. 31, 2018, received in Korean Patent Application No. 2018-7020659, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Notice of Allowance, dated Feb. 25, 2019, received in Korean Patent Application No. 2018-7020659, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Patent, dated Apr. 3, 2019, received in Korean Patent Application No. 2018- 7020659, which corresponds with U.S. Appl. No. 15/136,782, 5 pages. |
| Office Action, dated Jan. 20, 2017, received in U.S. Appl. No. 15/231,745, 21 pages. |
| Notice of Allowance, dated Jul. 6, 2017, received in U.S. Appl. No. 15/231,745, 18 pages. |
| Office Action, dated Oct. 17, 2016, received in Danish Patent Application No. 201670587, which corresponds with U.S. Appl. No. 15/231,745, 9 pages. |
| Office Action, dated Jun. 29, 2017, received in Danish Patent Application No. 201670587, which corresponds with U.S. Appl. No. 15/231,745, 4 pages. |
| Office Action, dated Feb. 22, 2018, received in Danish Patent Application No. 201670587, which corresponds with U.S. Appl. No. 15/231,745, 4 pages. |
| Office Action, dated Dec. 18, 2018, received in Danish Patent Application No. 201670587, which corresponds with U.S. Appl. No. 15/231,745, 4 pages. |
| Office Action, dated Dec. 14, 2016, received in Danish Patent Application No. 201670590, which corresponds with U.S. Appl. No. 15/231,745, 9 pages. |
| Office Action, dated Jul. 6, 2017, received in Danish Patent Application No. 201670590, which corresponds with U.S. Appl. No. 15/231,745, 3 pages. |
| Office Action, dated Jan. 10, 2018, received in Danish Patent Application No. 201670590, which corresponds with U.S. Appl. No. 15/231,745, 2 pages. |
| Patent, dated May 28, 2018, received in Danish Patent Application No. 201670590, which corresponds with U.S. Appl. No. 15/231,745, 2 pages. |
| Office Action, dated Nov. 10, 2016, received in Danish Patent Application No. 201670591, which corresponds with U.S. Appl. No. 15/231,745, 12 pages. |
| Office Action, dated Apr. 11, 2018, received in Danish Patent Application No. 201670591, which corresponds with U.S. Appl. No. 15/231,745, 3 pages. |
| Office Action, dated Nov. 23, 2018, received in Danish Patent Application No. 201670591, which corresponds with U.S. Appl. No. 15/231,745, 7 pages. |
| Office Action, dated Oct. 26, 2016, received in Danish Patent Application No. 201670592, which corresponds with U.S. Appl. No. 15/231,745, 8 pages. |
| Office Action, dated Jan. 5, 2017, received in Danish Patent Application No. 201670592, which corresponds with U.S. Appl. No. 15/231,745, 3 pages. |
| Office Action, dated Jan. 30, 2018, received in Danish Patent Application No. 201670592, which corresponds with U.S. Appl. No. 15/231,745, 2 pages. |
| Notice of Allowance, dated Mar. 27, 2018, received in Danish Patent Application No. 201670592, which corresponds with U.S. Appl. No. 15/231,745, 2 pages. |
| Patent, dated May 28, 2018, received in Danish Patent Application No. 201670592, which corresponds with U.S. Appl. No. 15/231,745, 2 pages. |
| Office Action, dated Oct. 12, 2016, received in Danish Patent Application No. 201670593, which corresponds with U.S. Appl. No. 15/231,745, 7 pages. |
| Patent, dated Oct. 30, 2017, received in Danish Patent Application No. 201670593, which corresponds with U.S. Appl. No. 15/231,745, 3 pages. |
| Notice of Allowance, dated Nov. 1, 2019, received in Japanese Patent Application No. 2018-158502, which corresponds with U.S. Appl. No. 15/231,745, 5 pages. |
| Patent, dated Nov. 29, 2019, received in Japanese Patent Application No. 2018-158502, which corresponds with U.S. Appl. No. 15/231,745, 3 pages. |
| Notice of Allowance, dated Oct. 4, 2018, received in U.S. Appl. No. 15/272,327, 46 pages. |
| Notice of Acceptance, dated Mar. 2, 2018, received in Australian Patent Application No. 2018200705, which corresponds with U.S. Appl. No. 15/272,327, 3 pages. |
| Certificate of Grant, dated Jun. 28, 2018, received in Australian Patent Application No. 20182200705, which corresponds with U.S. Appl. No. 15/272,327, 4 pages. |
| Office Action, dated Mar. 22, 2019, received in Australian Patent Application No. 2018204234, which corresponds with U.S. Appl. No. 15/272,327, 7 pages. |
| Notice of Acceptance, dated Dec. 10, 2019, received in Australian Patent Application No. 2018204234, which corresponds with U.S. Appl. No. 15/272,327, 3 pages. |
| Certificate of Grant, dated Apr. 2, 2020, received in Australian Patent Application No. 2018204234, which corresponds with U.S. Appl. No. 15/272,327, 1 page. |
| Office Action, dated Aug. 31, 2020, received in Chinese Patent Application No. 201810151593.X, which corresponds with U.S. Appl. No. 15/272,327, 10 pages. |
| Notice of Allowance, dated Jan. 27, 2021, received in Chinese Patent Application No. 201810151593.X, which corresponds with U.S. Appl. No. 15/272,327, 3 pages. |
| Patent, dated Mar. 19, 2021, received in Chinese Patent Application No. 201810151593.X, which corresponds with U.S. Appl. No. 15/272,327, 6 pages. |
| Office Action, dated Sep. 14, 2018, received in European Patent Application No. 15155939.4, which corresponds with U.S. Appl. No. 15/272,327, 5 pages. |
| Intention to Grant, dated Mar. 19, 2019, received in European Patent Application No. 15155939.4, which corresponds with U.S. Appl. No. 15/272,327, 6 pages. |
| Decision to Grant, dated Apr. 26, 2019, received in European Patent Application No. 15155939.4, which corresponds with U.S. Appl. No. 15/272,327, 2 pages. |
| Patent, dated May 22, 2019, received in European Patent Application No. 15155939.4, which corresponds with U.S. Appl. No. 15/272,327, 1 page. |
| Notice of Allowance, dated Jul. 30, 2018, received in Japanese Patent Application No. 2018-506989, which corresponds with U.S. Appl. No. 15/272,327, 4 pages. |
| Patent, dated Aug. 31, 2018, received in Japanese Patent Application No. 2018-506989, which corresponds with U.S. Appl. No. 15/272,327, 3 pages. |
| Notice of Allowance, dated Oct. 14, 2022, received in Japanese Patent Application No. 2021-157204, which corresponds with U.S. Appl. No. 15/272,327, 2 pages. |
| Office Action, dated Oct. 26, 2018, received in U.S. Appl. No. 15/272,341, 22 pages. |
| Final Office Action, dated Mar. 25, 2019, received in U.S. Appl. No. 15/272,341, 25 pages. |
| Notice of Allowance, dated Feb. 20, 2020, received in U.S. Appl. No. 15/272,341, 12 pages. |
| Office Action, dated Jul. 27, 2017, received in Australian Patent Application No. 2017100535, which corresponds with U.S. Appl. No. 15/272,341, 4 pages. |
| Notice of Allowance, dated Sep. 20, 2018, received in U.S. Appl. No. 15/272,343, 44 pages. |
| Office Action, dated Jun. 5, 2019, received in Chinese Patent Application No. 201810071627.4, which corresponds with U.S. Appl. No. 15/272,343, 6 pages. |
| Notice of Allowance, dated Dec. 11, 2019, received in Chinese Patent Application No. 201810071627.4, which corresponds with U.S. Appl. No. 15/272,343, 4 pages. |
| Patent, dated Mar. 3, 2020, received in Chinese Patent Application No. 201810071627.4, which corresponds with U.S. Appl. No. 15/272,343, 7 pages. |
| Office Action, dated Jan. 8, 2019, received in European Patent Application No. 17206374.5, which corresponds with U.S. Appl. No. 15/272,343, 5 pages. |
| Intention to Grant, dated May 13, 2019, received in European Patent Application No. 17206374.5, which corresponds with U.S. Appl. No. 15/272,343, 7 pages. |
| Decision to Grant, dated Sep. 12, 2019, received in European Patent Application No. 17206374.5, which corresponds with U.S. Appl. No. 15/272,343, 3 pages. |
| Patent, Oct. 9, 2019, received in European Patent Application No. 17206374.5, which corresponds with U.S. Appl. No. 15/272,343, 3 pages. |
| Office Action, dated Oct. 15, 2018, received in U.S. Appl. No. 15/272,345. 31 pages. |
| Final Office Action, dated Apr. 2, 2019, received in U.S. Appl. No. 15/272,345, 28 pages. |
| Notice of Allowance, dated Apr. 22, 2020, received in U.S. Appl. No. 15/272,345, 12 pages. |
| Notice of Acceptance, dated Mar. 2, 2018, received in Australian Patent Application No. 2016304832, which corresponds with U.S. Appl. No. 15/272,345, 3 pages. |
| Certificate of Grant, dated Jun. 28, 2018, received in Australian Patent Application No. 2016304832, which corresponds with U.S. Appl. No. 15/272,345, 4 pages. |
| Office Action, dated Oct. 22, 2019, received in Chinese Patent Application No. 201680022696.5, which corresponds with U.S. Appl. No. 15/272,345, 7 pages. |
| Notice of Allowance, dated Jul. 6, 2020, received in Chinese Patent Application No. 201680022696.5, which corresponds with U.S. Appl. No. 15/272,345, 5 pages. |
| Patent, dated Sep. 18, 2020, received in Chinese Patent Application No. 201680022696.5, which corresponds with U.S. Appl. No. 15/272,345, 6 pages. |
| Office Action, dated Apr. 20, 2018, received in European Patent Application No. 16756862.5, which corresponds with U.S. Appl. No. 15/272,345, 15 pages. |
| Office Action, dated Nov. 13, 2018, received in European Patent Application No. 16756862.5, which corresponds with U.S. Appl. No. 15/272,345, 5 pages. |
| Decision to Grant, dated Jan. 31, 2019, received in European Patent Application No. 16756862.5, which corresponds with U.S. Appl. No. 15/272,345, 5 pages. |
| Patent, dated Feb. 27, 2019, received in European Patent Application No. 16756862.5, which corresponds with U.S. Appl. No. 15/272,345, 3 pages. |
| Patent, dated Feb. 7, 2020, received in Hong Kong Patent Application No. 18101477.0, which corresponds with U.S. Appl. No. 15/272,345, 6 pages. |
| Office Action, dated Dec. 4, 2020, received in Japanese Patent Application No. 2019-212493, which corresponds with U.S. Appl. No. 15/272,345, 5 pages. |
| Notice of Allowance, dated Aug. 27, 2021, received in Japanese Patent Application No. 2019-212493, which corresponds with U.S. Appl. No. 15/272,345, 2 pages. |
| Patent, dated Sep. 29, 2021, received in Japanese Patent Application No. 2019-212493, which corresponds with U.S. Appl. No. 15/272,345, 4 pages. |
| Office Action, dated Mar. 7, 2018, received in U.S. Appl. No. 15/482,618, 7 pages. |
| Notice of Allowance, dated Aug. 15, 2018, received in U.S. Appl. No. 15/482,618, 7 pages. |
| Office Action, dated Apr. 23, 2018, received in U.S. Appl. No. 15/499,691, 29 pages. |
| Notice of Allowance, dated Oct. 12, 2018, received in U.S. Appl. No. 15/499,693, 8 pages. |
| Office Action, dated May 11, 2020, received in Australian Patent Application No. 2019203776, which corresponds with U.S. Appl. No. 15/499,693, 4 pages. |
| Notice of Acceptance, dated Jul. 22, 2020, received in Australian Patent Application No. 2019203776, which corresponds with U.S. Appl. No. 15/499,693, 3 pages. |
| Certificate of Grant, dated Nov. 26, 2020, received in Australian Patent Application No. 2019203776, which corresponds with U.S. Appl. No. 15/499,693, 3 pages. |
| Office Action, dated Jun. 7, 2022, received in European Patent Application No. 20188553.0, which corresponds with U.S. Appl. No. 15/499,693, 7 pages. |
| Office action, dated Nov. 20, 2020, received in Japanese Patent Application No. 2019-200174, which corresponds with U.S. Appl. No. 15/499,693, 6 pages. |
| Notice of Allowance, dated Jul. 16, 2021, received in Japanese Patent Application No. 2019-200174, which corresponds with U.S. Appl. No. 15/499,693, 2 pages. |
| Patent, dated Aug. 18, 2021, received in Japanese Patent Application No. 2019-200174, which corresponds with U.S. Appl. No. 15/499,693, 3 pages. |
| Office Action, dated Aug. 2, 2019, received in Korean Patent Application No. 2019-7009439, which corresponds with U.S. Appl. No. 15/499,693, 3 pages. |
| Notice of Allowance, dated Dec. 27, 2019, received in Korean Patent Application No. 2019-7009439, which corresponds with U.S. Appl. No. 15/499,693, 5 pages. |
| Patent, dated Mar. 27, 2020, received in Korean Patent Application No. 2019-7009439, which corresponds with U.S. Appl. No. 15/499,693, 4 pages. |
| Office Action, dated Aug. 30, 2017, received in U.S. Appl. No. 15/655,749, 22 pages. |
| Final Office Action, dated May 10, 2018, received in U.S. Appl. No. 15/655,749, 19 pages. |
| Office Action, dated Jan. 24, 2019, received in U.S. Appl. No. 15/655,749, 25 pages. |
| Final Office Action, dated Jul. 1, 2019, received in U.S. Appl. No. 15/655,749, 24 pages. |
| Notice of Allowance, dated Feb. 20, 2020, received in U.S. Appl. No. 15/655,749, 10 pages. |
| Office Action, dated Feb. 3, 2020, received in Chinese Patent Application No. 201710331254.5, which corresponds with U.S. Appl. No. 15/655,749, 8 pages. |
| Office Action, dated Mar. 22, 2021, received in Chinese Patent Application No. 201710331254.5, which corresponds with U.S. Appl. No. 15/655,749, 4 pages. |
| Notice of Allowance, dated May 27, 2021, received in Chinese Patent Application No. 201710331254.5, which corresponds with U.S. Appl. No. 15/655,749, 1 page. |
| Patent, dated Jun. 25, 2021, received in Chinese Patent Application No. 201710331254.5, which corresponds with U.S. Appl. No. 15/655,749, 7 pages. |
| Notice of Allowance, dated Apr. 18, 2019, received in Korean Patent Application No. 2017-7034248, which corresponds with U.S. Appl. No. 15/655,749, 5 pages. |
| Patent, dated Jul. 3, 2019, received in Korean Patent Application No. 2017-7034248, which corresponds with U.S. Appl. No. 15/655,749, 5 pages. |
| Office Action, dated Aug. 1, 2019, received in U.S. Appl. No. 15/785,372, 22 pages. |
| Final Office Action, dated Feb. 5, 2020, received in U.S. Appl. No. 15/785,372, 26 pages. |
| Office Action, dated Jul. 23, 2020, received in U.S. Appl. No. 15/785,372, 23 pages. |
| Final Office Action, dated Nov. 18, 2020, received in U.S. Appl. No. 15/785,372, 27 pages. |
| Notice of Allowance, dated Jul. 14, 2021, received in U.S. Appl. No. 15/785,372, 11 pages. |
| Notice of Allowance, dated Oct. 22, 2021, received in U.S. Appl. No. 15/785,372, 11 pages. |
| Office Action, dated Oct. 31, 2017, received in U.S. Appl. No. 15/723,069, 7 pages. |
| Notice of Allowance, dated Dec. 21, 2017, received in U.S. Appl. No. 15/723,069, 7 pages. |
| Office Action, dated Apr. 11, 2019, received in U.S. Appl. No. 15/889,115, 9 pages. |
| Final Office Action, dated Oct. 28, 2019, received in U.S. Appl. No. 15/889,115, 12 pages. |
| Notice of Allowance, dated May 19, 2020, received in U.S. Appl. No. 15/889,115, 9 pages. |
| Office Action, dated Jul. 25, 2019, received in U.S. Appl. No. 15/979,347, 14 pages. |
| Final Office Action, dated Feb. 27, 2020, received in U.S. Appl. No. 15/979,347, 19 pages. |
| Office Action, dated Jul. 14, 2020, received in U.S. Appl. No. 15/979,347, 10 pages. |
| Final Office Action, dated Jan. 25, 2021, received in U.S. Appl. No. 15/979,347, 12 pages. |
| Office Action, dated Sep. 25, 2020, received in U.S. Appl. No. 15/994,843, 5 pages. |
| Notice of Allowance, dated Jan. 22, 2021, received in U.S. Appl. No. 15/994,843, 8 pages. |
| Office Action, dated Nov. 25, 2019, received in U.S. Appl. No. 16/049,725, 9 pages. |
| Notice of Allowance, dated May 14, 2020, received in U.S. Appl. No. 16/049,725, 9 pages. |
| Office Action, dated May 31, 2019, received in Australian Patent Application No. 2018253539, which corresponds with U.S. Appl. No. 16/049,725, 3 pages. |
| Notice of Acceptance, dated Apr. 2, 2020, received in Australian Patent Application No. 2018253539, which corresponds with U.S. Appl. No. 16/049,725, 3 pages. |
| Certificate of Grant, dated Aug. 13, 2020, received in Australian Patent Application No. 2018253539, which corresponds with U.S. Appl. No. 16/049,725, 3 pages. |
| Notice of Allowance, dated Oct. 10, 2019, received in U.S. Appl. No. 16/102,409, 9 pages. |
| Office Action, dated Nov. 29, 2019, received in U.S. Appl. No. 16/136,163, 9 pages. |
| Final Office Action, dated Jun. 9, 2020, received in U.S. Appl. No. 16/136,163, 10 pages. |
| Office Action, dated Sep. 17, 2020, received in U.S. Appl. No. 16/136,163, 13 pages. |
| Final Office Action, dated May 20, 2021, received in U.S. Appl. No. 16/136,163, 13 pages. |
| Office Action, dated Nov. 23, 2021, received in U.S. Appl. No. 16/136,163, 27 pages. |
| Office Action, dated Mar. 9, 2020, received in U.S. Appl. No. 16/145,954, 15 pages. |
| Office Action, dated Dec. 10, 2020, received in U.S. Appl. No. 16/145,954, 5 pages. |
| Office Action, dated Mar. 6, 2020, received in U.S. Appl. No. 16/154,591, 16 pages. |
| Final Office Action, dated Oct. 1, 2020, received in U.S. Appl. No. 16/154,591, 19 pages. |
| Office Action, dated Mar. 4, 2021, received in U.S. Appl. No. 16/154,591, 20 pages. |
| Office Action, dated May 4, 2020, received in Australian Patent Application No. 2019203175, which corresponds with U.S. Appl. No. 16/154,591, 4 pages. |
| Office Action, dated Oct. 13, 2020, received in Australian Patent Application No. 2019203175, which corresponds with U.S. Appl. No. 16/154,591, 5 pages. |
| Office Action, dated Dec. 2, 2019, received in Japanese Patent Application No. 2018-202048, which corresponds with U.S. Appl. No. 16/154,591, 6 pages. |
| Notice of Allowance, dated Jun. 1, 2020, received in Japanese Patent Application No. 2018-202048, which corresponds with U.S. Appl. No. 16/154,591, 3 pages. |
| Patent, dated Jun. 25, 2020, received in Japanese Patent Application No. 2018-202048, which corresponds with U.S. Appl. No. 16/154,591, 4 pages. |
| Office Action, dated Aug. 20, 2019, received in Korean Patent Application No. 2019-7019946, which corresponds with U.S. Appl. No. 16/154,591, 6 pages. |
| Office Action, dated Feb. 27, 2020, received in Korean Patent Application No. 2019-7019946, which corresponds with U.S. Appl. No. 16/154,591, 5 pages. |
| Office Action, dated Mar. 29, 2021, received in Korean Patent Application No. 2019-7019946, which corresponds with U.S. Appl. No. 16/154,591, 6 pages. |
| Notice of Allowance, dated Aug. 26, 2021, received in Korean Patent Application No. 2019-7019946, which corresponds with U.S. Appl. No. 16/154,591, 2 pages. |
| Patent, dated Sep. 7, 2021, received in Korean Patent Application No. 2019-7019946, which corresponds with U.S. Appl. No. 16/154,591, 4 pages. |
| Office Action, dated Nov. 25, 2019, received in U.S. Appl. No. 16/174,170, 31 pages. |
| Final Office Action, dated Mar. 19, 2020, received in U.S. Appl. No. 16/174,170, 25 pages. |
| Notice of Allowance, dated Jun. 18, 2020, received in U.S. Appl. No. 16/174,170, 19 pages. |
| Notice of Allowance, dated Aug. 26, 2020, received in U.S. Appl. No. 16/240,669, 18 pages. |
| Office Action, dated Oct. 30, 2020, received in U.S. Appl. No. 16/230,707, 20 pages. |
| Notice of Allowance, dated Feb. 18, 2021, received in U.S. Appl. No. 16/230,707, 9 pages. |
| Office Action, dated Aug. 10, 2020, received in U.S. Appl. No. 16/240,672, 13 pages. |
| Final Office Action, dated Nov. 27, 2020, received in U.S. Appl. No. 16/240,672, 12 pages. |
| Office Action, dated May 17, 2021, received in U.S. Appl. No. 16/240,672, 14 pages. |
| Notice of Allowance, dated Sep. 2, 2021, received in U.S. Appl. No. 16/240,672, 13 pages. |
| Office Action, dated Sep. 24, 2020, received in Australian Patent Application No. 2019268116, which corresponds with U.S. Appl. No. 16/240,672, 4 pages. |
| Office Action, dated Jan. 28, 2021, received in Australian Patent Application No. 2019268116, which corresponds with U.S. Appl. No. 16/240,672, 4 pages. |
| Notice of Allowance, dated Sep. 20, 2021, received in Australian Patent Application No. 2019268116, which corresponds with U.S. Appl. No. 16/240,672, 3 pages. |
| Patent, dated Jan. 27, 2022, received in Australian Patent Application No. 2019268116, which corresponds with U.S. Appl. No. 16/240,672, 3 pages. |
| Office Action, dated Apr. 21, 2021, received in European Patent Application No. 19195414.8, which corresponds with U.S. Appl. No. 16/240,672, 7 pages. |
| Notice of Allowance, dated May 22, 2020, received in Japanese Patent Application No. 2019-027634, which corresponds with U.S. Appl. No. 16/240,672, 5 pages. |
| Patent, dated Jun. 23, 2020, received in Japanese Patent Application No. 2019-027634, which corresponds with U.S. Appl. No. 16/240,672, 4 pages. |
| Office Action, dated May 22, 2019, received in U.S. Appl. No. 16/230,743, 7 pages. |
| Notice of Allowance, dated Sep. 11, 2019, received in U.S. Appl. No. 16/230,743, 5 pages. |
| Office Action, dated Mar. 6, 2020, received in U.S. Appl. No. 16/243,834, 19 pages. |
| Notice of Allowance, dated Sep. 24, 2020, received in U.S. Appl. No. 16/243,834, 10 pages. |
| Office Action, dated Dec. 18, 2019, received in Australian Patent Application No. 2018282409, which corresponds with U.S. Appl. No. 16/243,834, 3 pages. |
| Office Action, dated Sep. 18, 2020, received in Australian Patent Application No. 2018282409, which corresponds with U.S. Appl. No. 16/243,834, 3 pages. |
| Notice of Acceptance, dated Oct. 21, 2020, received in Australian Patent Application No. 2018282409, which corresponds with U.S. Appl. No. 16/243,834, 3 pages. |
| Certificate of Grant, dated Feb. 18, 2021, received in Australian Patent Application No. 2018282409, which corresponds with U.S. Appl. No. 16/243,834, 3 pages. |
| Office Action, dated Aug. 7, 2020, received in Japanese Patent Application No. 2019-058800, which corresponds with U.S. Appl. No. 16/243,834, 8 pages. |
| Office Action, dated Feb. 12, 2021, received in Japanese Patent Application No. 2019-058800, which corresponds with U.S. Appl. No. 16/243,834, 2 pages. |
| Office Action, dated Apr. 11, 2022, received in Japanese Patent Application No. 2019-058800, which corresponds with U.S. Appl. No. 16/243,834, 4 pages. |
| Notice of Allowance, dated Jan. 20, 2023, reveived in Japanese Patent Application No. 2019-058800, which corresponds with U.S. Appl. No. 16/243,834, 2 pages. |
| Office Action, dated Jul. 25, 2022, received in Japanese Patent Application No. 2021-099049, which corresponds with U.S. Appl. No. 16/243,834, 2 pages. |
| Office Action, dated Jul. 5, 2019, received in Korean Patent Application No. 2018-7037896, which corresponds with U.S. Appl. No. 16/243,834, 2 pages. |
| Notice of Allowance, dated Dec. 23, 2019, received in Korean Patent Application No. 2018-7037896, which corresponds with U.S. Appl. No. 16/243,834, 6 pages. |
| Patent, dated Mar. 13, 2020, received in Korean Patent Application No. 2018-7037896, which corresponds with U.S. Appl. No. 16/243,834, 7 pages. |
| Office Action, dated Jul. 18, 2022, received in Mexican Patent Application No. MX/a/2020/011482, which corresponds with U.S. Appl. No. 16/243,834, 4 pages. |
| Office Action, dated Jan. 5, 2023, received in Mexican Patent Application No. MX/a/2020/011482, which corresponds with U.S. Appl. No. 16/243,834, 5 pages. |
| Office Action, dated Nov. 30, 2021, received in Russian Patent Application No. 2018146112, which corresponds with U.S. Appl. No. 16/243,834, 15 pages. |
| Notice of Allowance, dated Apr. 14, 2022, received in Russian Patent Application No. 2018146112, which corresponds with U.S. Appl. No. 16/243,834, 2 pages. |
| Notice of Allowance, dated Nov. 20, 2020, received in U.S. Appl. No. 16/262,784, 8 pages. |
| Office action, dated Feb. 25, 2021, received in Australian Patent Application No. 2020201648, which corresponds with U.S. Appl. No. 16/262,784, 3 pages. |
| Notice of Allowance, dated Dec. 14, 2021, received in Australian Patent Application No. 2020201648, which corresponds with U.S. Appl. No. 16/262,784, 3 pages. |
| Certificate of Grant, dated Apr. 21, 2022, received in Australian Patent Application No. 2020201648, which corresponds with U.S. Appl. No. 16/262,784, 3 pages. |
| Office Action, dated Feb. 5, 2021, received in U.S. Appl. No. 16/262,800, 53 pages. |
| Final Office Action, dated Jun. 4, 2021, received in U.S. Appl. No. 16/262,800, 65 pages. |
| Notice of Allowance, dated Jan. 24, 2022, received in U.S. Appl. No. 16/262,800, 26 pages. |
| Office Action, dated Sep. 15, 2020, received in European Patent Application No. 19194439.6, which corresponds with U.S. Appl. No. 16/262,800, 6 pages. |
| Office Action, dated Mar. 25, 2021, received in European Patent Application No. 19194439.6, which corresponds with U.S. Appl. No. 16/262,800, 5 pages. |
| Notice of Allowance, dated Apr. 19, 2019, received in U.S. Appl. No. 16/252,478, 11 pages. |
| Office Action, dated Jun. 11, 2020, received in Australian Patent Application No. 2019257437, which corresponds with U.S. Appl. No. 16/252,478, 3 pages. |
| Notice of Allowance, dated Sep. 15, 2020, received in Australian Patent Application No. 2019257437, which corresponds with U.S. Appl. No. 16/252,478, 3 pages. |
| Notice of Allowance, dated Dec. 13, 2019, received in Korean Patent Application No. 2019-7033444, which corresponds with U.S. Appl. No. 16/252,478, 6 pages. |
| Patent, dated Mar. 12, 2020, received in Korean Patent Application No. 2019-7033444, which corresponds with U.S. Appl. No. 16/252,478, 6 pages. |
| Office action, dated Aug. 27, 2020, received in U.S. Appl. No. 16/241,883, 11 pages. |
| Notice of Allowance, dated Sep. 28, 2020, received in U.S. Appl. No. 16/241,883, 10 pages. |
| Office Action, dated Aug. 10, 2021, received in European Patent Application No. 19181042.3, which corresponds with U.S. Appl. No. 16/241,883, 7 pages. |
| Office Action, dated Oct. 1, 2021, received in Japanese Patent Applicat No. 2020-174097, which corresponds with U.S. Appl. No. 16/241,883, 2 pages. |
| Patent, dated Jun. 14, 2022, received in Japanese Patent Application No. 2020-174097, which corresponds with U.S. Appl. No. 16/241,883, 3 pages. |
| Office Action, dated Jul. 15, 2019, received in U.S. Appl. No. 16/258,394, 8 pages. |
| Notice of Allowance, dated Nov. 6, 2019, received in U.S. Appl. No. 16/258,394, 8 pages. |
| Office Action, dated Oct. 21, 2021, received in Australian Patent Application No. 2020267298, which corresponds with U.S. Appl. No. 16/258,394, 2 pages. |
| Notice of Allowance, dated Jan. 14, 2022, received in Australian Patent Application No. 2020267298, which corresponds with U.S. Appl. No. 16/258,394, 3 pages. |
| Patent, dated May 19, 2022, received in Australian Patent Application No. 2020267298, which corresponds with U.S. Appl. No. 16/258,394, 4 pages. |
| Office Action, dated Oct. 3, 2022, received in Japanese Patent Application No. 2021-132350, which corresponds with U.S. Appl. No. 16/258,394, 2 pages. |
| Office Action, dated May 14, 2020, received in U.S. Appl. No. 16/354,035, 16 pages. |
| Notice of Allowance, dated Aug. 25, 2020, received in U.S. Appl. No. 16/354,035, 14 pages. |
| Office Action, dated Jun. 9, 2021, received in U.S. Appl. No. 16/896,141, 21 pages. |
| Final Office Action, dated Dec. 13, 2021, received in U.S. Appl. No. 16/896,141, 29 pages. |
| Office Action, dated Oct. 11, 2019, received in Australian Patent Application No. 2019202417, which corresponds with U.S. Appl. No. 16/896,141, 4 pages. |
| Notice of Allowance, dated Jul. 6, 2020, received in Australian Patent Application No. 2019202417, which corresponds with U.S. Appl. No. 16/896,141, 3 pages. |
| Certificate of Grant, dated Nov. 5, 2020, received in Australian Patent Application No. 2019202417, which corresponds with U.S. Appl. No. 16/896,141, 4 pages. |
| Office Action, dated Aug. 21, 2020, received in Japanese Patent Application No. 2019-047319, which corresponds with U.S. Appl. No. 16/896,141, 6 pages. |
| Office Action, dated Apr. 9, 2021, received in Japanese Patent Application No. 2019-047319, which corresponds with U.S. Appl. No. 16/896,141, 2 pages. |
| Final Office Action, dated Mar. 4, 2022, received in Japanese Patent Application No. 2019-047319, which corresponds with U.S. Appl. No. 16/896,141, 2 pages. |
| Final Office Action, dated Sep. 16, 2022, received in Japanese Patent Application No. 2019-047319, which corresponds with U.S. Appl. No. 16/896,141, 2 pages. |
| Office Action, dated Aug. 30, 2019, received in Korean Patent Application No. 2019-7019100, 2 pages. |
| Notice of Allowance, dated Nov. 1, 2019, received in Korean Patent Application No. 2019-7019100, 5 pages. |
| Patent, dated Jan. 31, 2020, received in Korean Patent Application No. 2019-7019100, 5 pages. |
| Office Action, dated May 14, 2020, received in U.S. Appl. No. 16/509,438, 16 pages. |
| Notice of Allowance, dated Jan. 6, 2021, received in U.S. Appl. No. 16/509,438, 5 pages. |
| Notice of Allowance, dated Apr. 29, 2021, received in U.S. Appl. No. 16/509,438, 9 pages. |
| Notice of Allowance, dated Sep. 20, 2022, received in Chinese Patent Application No. 201910610331.X, 1 page. |
| Patent, dated Nov. 25, 2022, received in Chinese Patent Application No. 201910610331.X, 7 pages. |
| Office Action, dated Sep. 6, 2021, received in Chinese Patent Application No. 201910718931.8, 6 pages. |
| Office Action, dated Mar. 17, 2022, received in Chinese Patent Application No. 201910718931.8, 1 page. |
| Office Action, dated Jul. 18, 2022, received in Chinese Patent Application No. 201910718931.8, 2 pages. |
| Notice of Allowance, dated Jan. 5, 2023, received in Chinese Patent Application No. 201910718931.8, 4 pages. |
| Notice of Allowance, dated May 20, 2020, received in U.S. Appl. No. 16/534,214, 16 pages. |
| Office Action, dated Oct. 7, 2020, received in U.S. Appl. No. 16/563,505, 20 pages. |
| Final Office Action, dated May 12, 2021, received in U.S. Appl. No. 16/563,505, 19 pages. |
| Office Action, dated Oct. 5, 2021, received in U.S. Appl. No. 16/563,505, 19 pages. |
| Office Action, dated Oct. 19, 2020, received in U.S. Appl. No. 16/685,773, 15 pages. |
| Final Office Action, dated Feb. 2, 2021, received in U.S. Appl. No. 16/685,773, 20 pages. |
| Office Action, dated Dec. 14, 2021, received in U.S. Appl. No. 16/685,773, 20 pages. |
| Final Office Action, dated Jul. 18, 2022, received in U.S. Appl. No. 16/685,773, 20 pages. |
| Office Action, dated Oct. 30, 2020, received in U.S. Appl. No. 16/824,490, 15 pages. |
| Notice of Allowance, dated Feb. 24, 2021, received in U.S. Appl. No. 16/824,490, 8 pages. |
| Office Action, dated Dec. 16, 2022, received in Australian Patent Application No. 2022200212, 3 pages. |
| Office Action, dated May 17, 2022, received in Korean Patent Application No. 2020-7008888, 2 pages. |
| Notice of Allowance, dated Nov. 23, 2022, received in Korean Patent Application No. 2020-7008888, 2 pages. |
| Office Action, dated Sep. 21, 2020, received in U.S. Appl. No. 16/803,904, 5 pages. |
| Notice of Allowance, dated Jan. 6, 2021, received in U.S. Appl. No. 16/803,904, 9 pages. |
| Notice of Allowance, dated Oct. 25, 2021, received in U.S. Appl. No. 17/003,869, 21 pages. |
| Office Action, dated Aug. 30, 2021, received in Australian Patent Application No. 2020244406, which corresponds with U.S. Appl. No. 17/003,869, 4 pages. |
| Notice of Allowance, dated Jan. 14, 2022, received in Australian Patent Application No. 2020244406, which corresponds with U.S. Appl. No. 17/003,869, 3 pages. |
| Patent, dated May 19, 2022, received in Australian Patent Appliction No. 2020244406, which corresponds with U.S. Appl. No. 17/003,869, 3 pages. |
| Office Action, dated Jan. 5, 2023, received in Japanese Patent Application No. 2022-031194, which corresponds with U.S. Appl. No. 17/003,869, 6 pages. |
| Notice of Allowance, dated May 4, 2020, received in Korean Patent Application No. 2019-7033444, which corresponds with U.S. Appl. No. 17/003,869, 5 pages. |
| Patent, dated Jun. 3, 2020, received in Korean Patent Application No. 2019-7033444, which corresponds with U.S. Appl. No. 17/003,869, 7 pages. |
| Notice of Allowance, dated Dec. 21, 2021, received in U.S. Appl. No. 16/921,083, 25 pages. |
| Office Action, dated Sep. 8, 2021, received in Japanese Patent Application No. 2020-106360, 2 pages. |
| Office Action, dated May 26, 2021, received in U.S. Appl. No. 16/988,509, 25 pages. |
| Final Office Action, dated Sep. 16, 2021, received in U.S. Appl. No. 16/988,509, 38 pages. |
| Notice of Allowance, dated Feb. 7, 2022, received in U.S. Appl. No. 16/988,509, 16 pages. |
| Office Action, dated Apr. 27, 2022, received in Australian Patent Application No. 2020257134, 3 pages. |
| Notice of Allowance, dated Aug. 23, 2022, received in Australian Patent Application No. 2020257134, 2 pages. |
| Patent, dated Dec. 22, 2022, received in Australian Patent Application No. 2020257134, 3 pages. |
| Office Action, dated Feb. 23, 2021, received in Korean Patent Application No. 2020-7031330, 3 pages. |
| Office Action, dated Aug. 27, 2021, received in Korean Patent Application No. 2020-7031330, 6 pages. |
| Office Action, dated Dec. 23, 2021, received in Korean Patent Application No. 2020-7031330, 8 pages. |
| Office Action, dated Apr. 28, 2022, received in Korean Patent Application No. 2022-7005994, 5 pages. |
| Notice of Allowance, dated Oct. 18, 2022, received in Korean Patent Application No. 2022-7005994, 5 pages. |
| Office Action, dated Oct. 26, 2021, received in U.S. Appl. No. 17/103,899 21 pages. |
| Final Office Action, dated May 2, 2022, received in U.S. Appl. No. 17/103,899 21 pages. |
| Office Action, date Aug. 19, 2022, received in U.S. Appl. No. 17/103,899 24 pages. |
| Final Office Action, dated Jan. 24, 2023, received in U.S. Appl. No. 17/103,899 27 pages. |
| Office Action, dated Nov. 11, 2021, received in Australian Patent Application No. 2021200655, which corresponds with U.S. Appl. No. 17/103,899, 4 pages. |
| Notice of Acceptance, dated Nov. 10, 2022, received in Australian Patent Application No. 2021200655, which corresponds with U.S. Appl. No. 17/103,899, 4 pages. |
| Office Action, dated Mar. 16, 2022, received in U.S. Appl. No. 17/138,676, 22 pages. |
| Office Action, dated Nov. 8, 2022, received in U.S. Appl. No. 17/333,810, 9 pages. |
| Office Action, dated Jun. 10, 2022, received in U.S. Appl. No. 17/362,852, 12 pages. |
| Notice of Allowance, dated Aug. 24, 2022, received in U.S. Appl. No. 17/362,852, 9 pages. |
| Office Action, dated Nov. 9, 2022, received in U.S. Appl. No. 17/409,573, 20 pages. |
| Notice of Allowance, dated Sep. 22, 2022, received in U.S. Appl. No. 17/524,692, 22 pages. |
| Office Action, dated Jan. 11, 2023, received in Australian Patent Application No. 2022202892, which corresponds with U.S. Appl. No. 15/113,779, 3 pages. |
| Office Action, dated Oct. 29, 2021, received in Korean Patent Application No. 2021-7031223, 2 pages. |
| Patent, dated Jan. 27, 2022, received in Korean Patent Application No. 2021-7031223, 5 pages. |
| Office Action, dated Nov. 28, 2022, received in U.S. Appl. No. 17/560,013, 13 pages. |
| Notice of Allowance, dated Feb. 21, 2022, received in Korean Patent Application No. 2022-7003345, 2 pages. |
| Patent, dated May 10, 2022, received in Korean Patent Application No. 2022-7003345, 8 pages. |
| Office Action, dated May 23, 2022, received in Korean Patent Application No. 2022-7015718, 2 pages. |
| Patent, dated Aug. 10, 2022, received in Korean Patent Application No. 2022-7015718, 6 pages. |
| International Search Report and Written Opinion dated May 26, 2014, received in International Application No. PCT/US2013/040053, which corresponds to U.S. Appl. No. 14/535,671, 32 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040053, which corresponds to U.S. Appl. No. 14/535,671, 26 pages. |
| International Search Report and Written Opinion dated Apr. 7, 2014, received in International Application No. PCT/US2013/069472, which corresponds to U.S. Appl. No. 14/608,895, 24 pages. |
| International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069472, which corresponds with U.S. Appl. No. 14/608,895, 18 pages. |
| International Search Report and Written Opinion dated Aug. 7, 2013, received in International Application No. PCT/US2013/040054, which corresponds to U.S. Appl. No. 14/536,235, 12 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040054, which corresponds to U.S. Appl. No. 14/536,235, 11 pages. |
| International Search Report and Written Opinion dated Aug. 7, 2013, received in International Application No. PCT/US2013/040056, which corresponds to U.S. Appl. No. 14/536,367, 12 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040056, which corresponds to U.S. Appl. No. 14/536,367, 11 pages. |
| Extended European Search Report, dated Nov. 6, 2015, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 7 pages. |
| Extended European Search Report, dated Jul. 30, 2018, received in European Patent Application No. 18180503.7, which corresponds with U.S. Appl. No. 14/536,426, 7 pages. |
| International Search Report and Written Opinion dated Aug. 6, 2013, received in International Application No. PCT/US2013/040058, which corresponds to U.S. Appl. No. 14/536,426, 12 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040058, which corresponds to U.S. Appl. No. 14/536,426, 11 pages. |
| International Search Report and Written Opinion dated Feb. 5, 2014, received in International Application No. PCT/US2013/040061, which corresponds to U.S. Appl. No. 14/536,464, 30 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040061, which corresponds to U.S. Appl. No. 14/536,464, 26 pages. |
| International Search Report and Written Opinion dated May 8, 2014, received in International Application No. PCT/US2013/040067, which corresponds to U.S. Appl. No. 14/536,644, 45 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040067, which corresponds to U.S. Appl. No. 14/536,644, 36 pages. |
| International Search Report and Written Opinion dated Mar. 12, 2014, received in International Application No. PCT/US2013/069479, which corresponds with U.S. Appl. No. 14/608,926, 14 pages. |
| International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069479, which corresponds with U.S. Appl. No. 14/608,926, 11 pages. |
| International Search Report and Written Opinion dated Aug. 7, 2013, received in International Application No. PCT/US2013/040070, which corresponds to U.S. Appl. No. 14/535,646, 12 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040070, which corresponds to U.S. Appl. No. 14/535,646, 10 pages. |
| International Search Report and Written Opinion dated Apr. 7, 2014, received in International Application No. PCT/US2013/040072, which corresponds to U.S. Appl. No. 14/536,141, 38 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040072, which corresponds to U.S. Appl. No. 14/536,141, 32 pages. |
| Extended European Search Report, dated Dec. 5, 2018, received in European Patent Application No. 18194127.9, which corresponds with U.S. Appl. No. 14/608,942, 8 pages. |
| International Search Report and Written Opinion dated Apr. 7, 2014, received in International Application No. PCT/US2013/069483, which corresponds with U.S. Appl. No. 14/608,942, 18 pages. |
| International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Application No. PCT/2013/069483, which corresponds to U.S. Appl. No. 14/608,942, 13 pages. |
| International Search Report and Written Opinion dated Mar. 3, 2014, received in International Application No. PCT/US2013/040087, which corresponds to U.S. Appl. No. 14/536,166, 35 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013/040087, which corresponds to U.S. Appl. No. 14/536,166, 29 pages. |
| International Search Report and Written Opinion dated Aug. 7, 2013, received in International Application No. PCT/US2013/040093, which corresponds to U.S. Appl. No. 14/536,203, 11 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013040093, which corresponds to U.S. Appl. No. 14,536,203, 9 pages. |
| International Search Report and Written Opinion dated Jul. 9, 2014, received in International Application No. PCT/US2013/069484, which corresponds with U.S. Appl. No. 14/608,965, 17 pages. |
| International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069484, which corresponds with U.S. Appl. No. 14/608,965, 12 pages. |
| International Search Report and Written Opinion dated Feb. 5, 2014, received in International Application No. PCT/US2013/040098, which corresponds to U.S. Appl. No. 14/536,247, 35 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013/040098, which corresponds to U.S. Appl. No. 14/536,247, 27 pages. |
| Extended European Search Report, dated Oct. 7, 2016, received in European Patent Application No. 16177863.4, which corresponds with U.S. Appl. No. 14/536,267, 12 pages. |
| Extended European Search Report, dated Oct. 30, 2018, received in European Patent Application No. 18183789.9, which corresponds with U.S. Appl. No. 14/536,267, 11 pages. |
| International Search Report and Written Opinion dated Jan. 27, 2014, received in International Application No. PCT/US2013/040101, which corresponds to U.S. Appl. No. 14/536,267, 30 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013/040101, which corresponds to U.S. Appl. No. 14/536,267, 24 pages. |
| Extended European Search Report, dated Nov. 24, 2017, received in European Patent Application No. 17186744.3, which corresponds with U.S. Appl. No. 14/536,291, 10 pages. |
| International Search Report and Written Opinion dated Jan. 8, 2014, received in International Application No. PCT/US2013/040108, which corresponds to U.S. Appl. No. 14/536,291, 30 pages. |
| International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013/040108, which corresponds to U.S. Appl. No. 14/536,291, 25 pages. |
| International Search Report and Written Opinion dated Jun. 2, 2014, received in International Application No. PCT/US2013/069486, which corresponds with U.S. Appl. No. 14/608,985, 7 pages. |
| International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069486, which corresponds with U.S. Appl. No. 14/608,985, 19 pages. |
| International Search Report and Written Opinion dated Mar. 6, 2014, received in International Application No. PCT/US2013/069489, which corresponds with U.S. Appl. No. 14/609,006, 12 pages. |
| International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069489, which corresponds with U.S. Appl. No. 14/609,006, 10 pages. |
| Extended European Search Report, dated Mar. 15, 2017, received in European Patent Application No. 17153418.3, which corresponds with U.S. Appl. No. 14/536,648, 7 pages. |
| Search Report, dated Apr. 13, 2017, received in Dutch Patent Application No. 2016452, which corresponds with U.S. Appl. No. 14/864,737, 22 pages. |
| Search Report, dated Jun. 22, 2017, received in Dutch Patent Application No. 2016375, which corresponds with U.S. Appl. No. 14/866,981, 17 pages. |
| International Search Report and Written Opinion, dated Oct. 14, 2016, received in International Patent Application No. PCT/US2016/020697, which corresponds with U.S. Appl. No. 14/866,981, 21 pages. |
| Search Report, dated Jun. 19, 2017, received in Dutch Patent Application No. 2016377, which corresponds with U.S. Appl. No. 14/866,159, 13 pages. |
| International Search Report and Written Opinion, dated Apr. 25, 2016, received in International Patent Application No. PCT/US2016/018758, which corresponds with U.S. Appl. No. 14/866,159, 15 pages. |
| Extended European Search Report, dated Oct. 17, 2017, received in European Patent Application No. 14/868,078, Which corresponds with U.S. Appl. No. 14/868,078, 8 pages. |
| Search Report, dated Apr. 13, 2017, received in Dutch Patent Application No. 2016376, which corresponds with U.S. Appl. No. 14/868,078, 15 pages. |
| International Search Report and Written Opinion, dated Jul. 21, 2016, received in International Patent Application No. PCT/US2016/019913, which corresponds with U.S. Appl. No. 14/868,078, 16 pages. |
| Search Report, dated Apr. 18, 2017, received in Dutch Patent Application No. 2016801, which corresponds with U.S. Appl. No. 14/863,432, 34 pages. |
| International Search Report and Written Opinion, dated Oct. 31, 2016, received in International Patent Application No. PCT/US2016/033578, which corresponds with U.S. Appl. No. 14/863,432, 36 pages. |
| International Search Report and Written Opinion, dated Nov. 14, 2016, received in International Patent Application No. PCT/US2016/033541, which corresponds with U.S. Appl. No. 14/866,511, 29 pages. |
| Extended European Search Report, dated Aug. 17, 2018, received in European Patent Application No. 18175195.9, which corresponds with U.S. Appl. No. 14/869,899, 13 pages. |
| International Search Report and Written Opinion, dated Aug. 29, 2016, received in International Patent Application No. PCT/US2016/021400, which corresponds with U.S. Appl. No. 14/869,899, 48 pages. |
| International Preliminary Report on Patentability, dated Sep. 12, 2017, received in International Patent Application No. PCT/US2016/021400, which corresponds with U.S. Appl. No. 14/869,899, 39 pages. |
| International Search Report and Written Opinion, dated Jan. 12, 2017, received in International Patent No. PCT/US2016/046419, which corresponds with U.S. Appl. No. 14/866,992, 23 pages. |
| International Search Report and Written Opinion, dated Dec. 15, 2016, received in International Patent Application No. PCT/US2016/046403, which corresponds with U.S. Appl. No. 15/009,661, 17 pages. |
| International Search Report and Written Opinion, dated Feb. 27, 2017, received in International Patent Application No. PCT/US2016/046407, which corresponds with U.S. Appl. No. 15/009,688, 30 pages. |
| International Preliminary Report on Patentability, dated Feb. 13, 2018, received in International Patent Application No. PCT/US2016/046407, which corresponds with U.S. Appl. No. 15/009,688, 20 pages. |
| Search Report, dated Feb. 15, 2018, received in Dutch Patent Application No. 2019215, which corresponds with U.S. Appl. No. 14/864,529, 13 pages. |
| Extended European Search Report, dated Nov. 14, 2019, received in European Patent Application No. 19194418.0, which corresponds with U.S. Appl. No. 14/864,580, 8 pages. |
| Search Report, dated Feb. 15, 2018, received in Dutch Patent Application No. 2019214, which corresponds with U.S. Appl. No. 14/864,601, 12 pages. |
| Extended European Search Report, dated Oct. 10, 2017, received in European Patent Application No. 17188507.2, which corresponds with U.S. Appl. No. 14/866,361, 9 pages. |
| Extended European Search Report, dated Jun. 22, 2017, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 7 pages. |
| Extended European Search Report, dated Sep. 11, 2017, received in European Patent Application No. 17163309.2, which corresponds with U.S. Appl. No. 14/866,987, 8 pages. |
| Extended European Search Report, dated Jun. 8, 2017, received in European Patent Application No. 16189425.8, which corresponds with U.S. Appl. No. 14/866,989, 8 pages. |
| Extended European Search Report, dated Aug. 2, 2018, received in European Patent Application No. 18168941.5, which corresponds with U.S. Appl. No. 14/871,236, 11 pages. |
| Extended European Search Report, dated Jul. 25, 2017, received in European Patent Application No. 17171972.7, which corresponds with U.S. Appl. No. 14/870,882, 12 pages. |
| Extended European Search Report, dated Jul. 25, 2017, received in European Patent Application No. 171722696.3, which corresponds with U.S. Appl. No. 14/871,336, 9 pages. |
| Extended European Search Report, dated Dec. 21, 2016, received in European Patent Application No. 16189790.5, which corresponds with U.S. Appl. No. 14/871,462, 8 pages. |
| Extended European Search Report, dated Mar. 8, 2019, received in European Patent Application No. 18205283.7, which corresponds with U.S. Appl. No. 15/081,771, 15 pages. |
| Extended European Search Report, dated Aug. 24, 2018, received in European Patent Application No. 18171453.6, which corresponds with U.S. Appl. No. 15/136,782, 9 pages. |
| International Search Report and Written Opinion, dated Jan. 3, 2017, received in International Patent Application No. PCT/US2016/046214, which corresponds with U.S. Appl. No. 15/231,745, 25 pages. |
| Extended European Search Report, dated May 30, 2018, received in European Patent Application No. 18155939.4, which corresponds with U.S. Appl. No. 15/272,327, 8 pages. |
| Extended European Search Report, dated Mar. 2, 2018, received in European Patent Application No. 17206374.5, which corresponds with U.S. Appl. No. 15/272,343, 11 pages. |
| Extended European Search Report, dated Oct. 6, 2020, received in European Patent Application No. 20188553.0, which corresponds with U.S. Appl. No. 15/499,693, 11 pages. |
| Extended European Search Report, dated Oct. 28, 2019, received in European Patent Application No. 19195414.8, which corresponds with U.S. Appl. No. 16/240,672, 6 pages. |
| Extended European Search Report, dated Nov. 13, 2019, received in European Patent Application No. 19194439.6, which corresponds with U.S. Appl. No. 16/262,800, 12 pages. |
| Extended European Search Report, dated Oct. 9, 2019, received in European Patent Application No. 19181042.3, which corresponds with U.S. Appl. No. 15/272,343, 10 pages. |
| International Search Report and Written Opinion, dated Jan. 11, 2022, received in International Application No. PCT/US2021/042402, which corresponds with U.S. Appl. No. 17/031,637, 50 pages. |
| Intent to Grant, dated Jun. 1, 2023, received in European Patent Application No. 16711725.8, which corresponds with U.S. Appl. No. 14/867,990, 8 pages. |
| Notice of Allowance, dated May 19, 2023, received in Japanese Patent Application No. 2021-099049, which corresponds with U.S. Appl. No. 16/243,834, 2 pages. |
| Patent, dated Jun. 19, 2023, received in Japanese Patent Application No. 2021-099049, which corresponds with U.S. Appl. No. 16/243,834, 4 pages. |
| Final Office Action, dated Jul. 14, 2023, received in Japanese Patent Application No. 2021-132350, which corresponds with U.S. Appl. No. 16/258,394, 2 pages. |
| Final Office Action, dated Jul. 14, 2023, received in Japanese Patent Application No. 2019-047319, which corresponds with U.S. Appl. No. 16/896,141, 2 pages. |
| Notice of Allowance, dated Jun. 13, 2023, received in Australian Patent Application No. 2022202892, which corresponds with U.S. Appl. No. 15/113,779, 3 pages. |
| Office Action, dated Jun. 28, 2023, received in Australian Patent Application No. 2021254568, which corresponds with U.S. Appl. No. 17/560,013, 3 pages. |
| Final Office Action, dated May 31, 2023, received in U.S. Appl. No. 17/409,573, 22 pages. |
| Office Action, dated Mar. 12, 2023, received in Chinese Patent Application No. 202010281127.0, which corresponds with U.S. Appl. No. 16/252,478, 4 pages. |
| Patent, dated Mar. 17, 2023, received in Chinese Patent Application No. 201910718931.8, 7 pages. |
| Patent, dated Mar. 16, 2023, received in Australian Patent Application No. 2021200655, which corresponds with U.S. Appl. No. 17/103,899, 3 pages. |
| Final Office Action, dated Apr. 24, 2023, received in U.S. Appl. No. 17/333,810, 12 pages. |
| Office Action, dated Sep. 20, 2022, received in Australian Patent Application No. 2021254568, which corresponds with U.S. Appl. No. 17/560,013, 4 pages. |
| Notice of Allowance, dated Mar. 24, 2023, received in U.S. Appl. No. 17/666,495, 28 pages. |
| Office Action, dated Mar. 30, 2023, received in U.S. Appl. No. 17/875,307, 15 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230133870 A1 | May 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62215689 | Sep 2015 | US | |
| 62172233 | Jun 2015 | US | |
| 62172223 | Jun 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17524692 | Nov 2021 | US |
| Child | 18089397 | US | |
| Parent | 17003869 | Aug 2020 | US |
| Child | 17524692 | US | |
| Parent | 16534214 | Aug 2019 | US |
| Child | 17003869 | US | |
| Parent | 16252478 | Jan 2019 | US |
| Child | 16534214 | US | |
| Parent | 14864529 | Sep 2015 | US |
| Child | 16252478 | US | |
| Parent | 14863432 | Sep 2015 | US |
| Child | 14864529 | US |
