Capturing and displaying images with multiple focal planes

Information

  • Patent Grant
  • 11895391
  • Patent Number
    11,895,391
  • Date Filed
    Monday, September 20, 2021
    2 years ago
  • Date Issued
    Tuesday, February 6, 2024
    3 months ago
  • CPC
  • Field of Search
    • CPC
    • H04N5/23216
    • H04N7/141
    • H04N5/232945
    • H04N5/232935
    • H04N5/232127
    • H04N5/232133
    • H04N7/147
  • International Classifications
    • H04N23/62
    • H04N7/14
Abstract
The present disclosure generally relates to capturing and displaying video with multiple focal planes. The video includes a subject with a predefined portion of the subject identified in a first focal region. When a set of one or more conditions is met, the video is displayed with a focal plane of the video selected to be outside of the first focal region. When the set of one or more conditions is met is no longer met; and the video is displayed with the focal plane of the video selected to be inside of the first focal region.
Description
FIELD

The present disclosure relates generally to user interfaces, and more specifically to techniques for capturing and displaying images with multiple focal planes.


BACKGROUND

Users are increasingly using electronic devices to capture images and virtually communicate with others for personal and business reasons. Most electronic devices are capable of capturing images for live communication between users. As an example, some electronic devices provide interactive interfaces to display and control the live communication.


BRIEF SUMMARY

Some techniques for capturing and displaying images, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface to capture or display images with different focal planes, which may include multiple key presses or other physical inputs. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.


Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for capturing and displaying images with multiple focal planes. Such methods and interfaces optionally complement or replace other methods for capturing and displaying images. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.


In some embodiments, a method is performed at an electronic device with a display. The method includes: displaying video for a live communication session, wherein the video includes a subject of the live communication session with a predefined portion of the subject identified in a first focal region, including, in accordance with a determination that a set of one or more conditions is met, displaying the video with a focal plane of the video selected to be outside of the first focal region; and while displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region, determining that the set of one or more conditions is no longer met; and in response to the determination that the set of one or more conditions is no longer met, displaying the video for the live communication session with the focal plane of the video selected to be inside of the first focal region.


In some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs include instructions for: displaying video for a live communication session, wherein the video includes a subject of the live communication session with a predefined portion of the subject identified in a first focal region, including, in accordance with a determination that a set of one or more conditions is met, displaying the video with a focal plane of the video selected to be outside of the first focal region; and while displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region, determining that the set of one or more conditions is no longer met; and in response to the determination that the set of one or more conditions is no longer met, displaying the video for the live communication session with the focal plane of the video selected to be inside of the first focal region.


In some embodiments, a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs include instructions for: displaying video for a live communication session, wherein the video includes a subject of the live communication session with a predefined portion of the subject identified in a first focal region, including, in accordance with a determination that a set of one or more conditions is met, displaying the video with a focal plane of the video selected to be outside of the first focal region; and while displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region, determining that the set of one or more conditions is no longer met; and in response to the determination that the set of one or more conditions is no longer met, displaying the video for the live communication session with the focal plane of the video selected to be inside of the first focal region.


In some embodiments, an electronic device includes a display, one or more processors, and memory. The memory stores one or more programs configured to be executed by the one or more processors. The one or more programs including instructions for: displaying video for a live communication session, wherein the video includes a subject of the live communication session with a predefined portion of the subject identified in a first focal region, including, in accordance with a determination that a set of one or more conditions is met, displaying the video with a focal plane of the video selected to be outside of the first focal region; and while displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region, determining that the set of one or more conditions is no longer met; and in response to the determination that the set of one or more conditions is no longer met, displaying the video for the live communication session with the focal plane of the video selected to be inside of the first focal region.


In some embodiments, an electronic device includes: a display; means for displaying video for a live communication session, wherein the video includes a subject of the live communication session with a predefined portion of the subject identified in a first focal region, including, means for, in accordance with a determination that a set of one or more conditions is met, displaying the video with a focal plane of the video selected to be outside of the first focal region; and means for, while displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region, determining that the set of one or more conditions is no longer met; and means for, in response to the determination that the set of one or more conditions is no longer met, displaying the video for the live communication session with the focal plane of the video selected to be inside of the first focal region.


In some embodiments, a method is performed at an electronic device with a camera. The method includes: detecting activation of a shutter button that is associated with capturing still images; and in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: capturing first image data with the camera focused at a first focal plane; and after capturing the first image data with the camera focused at the first focal plane, capturing second image data with the camera focused at a second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data.


In some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a camera. The one or more programs include instructions for: detecting activation of a shutter button that is associated with capturing still images; and in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: capturing first image data with the camera focused at a first focal plane; and after capturing the first image data with the camera focused at the first focal plane, capturing second image data with the camera focused at a second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data.


In some embodiments, a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a camera. The one or more programs include instructions for: detecting activation of a shutter button that is associated with capturing still images; and in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: capturing first image data with the camera focused at a first focal plane; and after capturing the first image data with the camera focused at the first focal plane, capturing second image data with the camera focused at a second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data.


In some embodiments, an electronic device includes a camera, one or more processors, and memory. The memory stores one or more programs configured to be executed by the one or more processors. The one or more programs including instructions for: detecting activation of a shutter button that is associated with capturing still images; and in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: capturing first image data with the camera focused at a first focal plane; and after capturing the first image data with the camera focused at the first focal plane, capturing second image data with the camera focused at a second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data.


In some embodiments, an electronic device includes: a camera; means for detecting activation of a shutter button that is associated with capturing still images; and means for, in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: means for capturing first image data with the camera focused at a first focal plane; and means for after capturing the first image data with the camera focused at the first focal plane, capturing second image data with the camera focused at a second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data.


Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.


Thus, devices are provided with faster, more efficient methods and interfaces for capturing and displaying images with multiple focal planes, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for capturing and displaying images.





DESCRIPTION OF THE FIGURES

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.



FIG. 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.



FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.



FIG. 2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.



FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.



FIG. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.



FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.



FIG. 5A illustrates a personal electronic device in accordance with some embodiments.



FIG. 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.



FIGS. 5C-5D illustrate exemplary components of a personal electronic device having a touch-sensitive display and intensity sensors in accordance with some embodiments.



FIGS. 5E-5H illustrate exemplary components and user interfaces of a personal electronic device in accordance with some embodiments.



FIGS. 6A-6H illustrate exemplary user interfaces displaying video for a live communication session with multiple focal planes, in accordance with some embodiments.



FIGS. 7A-7B are a flow diagram illustrating a method for displaying video for a live communication session with different focal planes, in accordance with some embodiments.



FIGS. 8A-8E illustrate exemplary user interfaces for capturing images with multiple focal planes, in accordance with some embodiments.



FIG. 9 is a flow diagram illustrating a method for displaying capturing a plurality of still images with a plurality of different focal planes, in accordance with some embodiments.





DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.


There is a need for electronic devices that provide efficient methods and interfaces for capturing and displaying images with multiple focal planes. Such techniques can reduce the cognitive burden on a user who participates in live communication sessions or edits images, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.


Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description of exemplary devices for performing the techniques for capturing and displaying images with multiple focal planes. FIGS. 6A-6H illustrate exemplary user interfaces for displaying video for a live communication session with multiple focal planes. FIGS. 7A-7B are a flow diagram illustrating methods of displaying the video for the live communication session in accordance with some embodiments. The user interfaces in FIGS. 6A-6H are used to illustrate the processes described below, including the processes in FIGS. 7A-7B. FIGS. 8A-8E illustrate exemplary user interfaces for capturing images with multiple focal planes. FIG. 9 is a flow diagram illustrating methods of capturing the images in accordance with some embodiments. The user interfaces in FIGS. 8A-8E are used to illustrate the processes described below, including the processes in FIG. 9.


Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.


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


The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.


Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).


In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.


The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.


The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.


Attention is now directed toward embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device 100 includes memory 102 (which optionally includes one or more computer-readable storage mediums), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.


As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).


As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.


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


Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.


Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.


RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.


Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212, FIG. 2). The headset jack provides an interface between audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone).


I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) optionally include an up/down button for volume control of speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206, FIG. 2).


A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.


Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.


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


Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.


A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.


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


Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.


In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.


Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.


Device 100 optionally also includes one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106. Optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor 164 receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user's image is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor 164 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 164 is used along with the touch screen display for both video conferencing and still and/or video image acquisition.


Device 100 optionally also includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I/O subsystem 106. Depth camera sensor 175 receives data from the environment to create a three dimensional model of an object (e.g., a face) within a scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also called a camera module), depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by the imaging module 143. In some embodiments, a depth camera sensor is located on the front of device 100 so that the user's image with depth information is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display and to capture selfies with depth map data. In some embodiments, the depth camera sensor 175 is located on the back of device, or on the back and the front of the device 100. In some embodiments, the position of depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a depth camera sensor 175 is used along with the touch screen display for both video conferencing and still and/or video image acquisition.


In some embodiments, a depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene from a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint's Z-axis where its corresponding two-dimensional pixel is located. In some embodiments, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0-255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor) in the “three dimensional” scene. In other embodiments, a depth map represents the distance between an object in a scene and the plane of the viewpoint. In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user's face). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction.


Device 100 optionally also includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I/O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.


Device 100 optionally also includes one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternately, proximity sensor 166 is, optionally, coupled to input controller 160 in I/O subsystem 106. Proximity sensor 166 optionally performs as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “Proximity Detector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and Ser. No. 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).


Device 100 optionally also includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I/O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that are capable of being sensed by a user of device 100. In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device 100) or laterally (e.g., back and forth in the same plane as a surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.


Device 100 optionally also includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternately, accelerometer 168 is, optionally, coupled to an input controller 160 in I/O subsystem 106. Accelerometer 168 optionally performs as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100.


In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) stores device/global internal state 157, as shown in FIGS. 1A and 3. Device/global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and location information concerning the device's location and/or attitude.


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


Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.


Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.


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


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


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


In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.


Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.


Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).


GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 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:

    • Contacts module 137 (sometimes called an address book or contact list);
    • Telephone module 138;
    • Video conference module 139;
    • E-mail client module 140;
    • Instant messaging (IM) module 141;
    • Workout support module 142;
    • Camera module 143 for still and/or video images;
    • Image management module 144;
    • Video player module;
    • Music player module;
    • Browser module 147;
    • Calendar module 148;
    • Widget modules 149, which optionally include one or more of: weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;
    • Widget creator module 150 for making user-created widgets 149-6;
    • Search module 151;
    • Video and music player module 152, which merges video player module and music player module;
    • Notes module 153;
    • Map module 154; and/or
    • Online video module 155.


Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.


In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.


In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.


In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.


In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.


In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).


In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.


In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.


In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.


In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.


In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.


In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).


In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).


In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.


In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).


In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.


In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.


In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.


Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152, FIG. 1A). 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.



FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).


Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.


In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.


Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.


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


In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.


Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.


Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.


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


Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.


Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.


In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.


In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.


A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).


Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.


Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.


In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.


In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.


When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.


In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.


In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.


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


In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.


In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.


It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.



FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.


Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.


In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.



FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes input/output (I/O) interface 330 comprising display 340, which is typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A), sensors 359 (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.


Each of the above-identified elements in FIG. 3 is, optionally, stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.


Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.



FIG. 4A illustrates an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

    • Signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals;
    • Time 404;
    • Bluetooth indicator 405;
    • Battery status indicator 406;
    • Tray 408 with icons for frequently used applications, such as:
      • Icon 416 for telephone module 138, labeled “Phone,” which optionally includes an indicator 414 of the number of missed calls or voicemail messages;
      • Icon 418 for e-mail client module 140, labeled “Mail,” which optionally includes an indicator 410 of the number of unread e-mails;
      • Icon 420 for browser module 147, labeled “Browser;” and
      • Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled “iPod;” and
    • Icons for other applications, such as:
      • Icon 424 for IM module 141, labeled “Messages;”
      • Icon 426 for calendar module 148, labeled “Calendar;”
      • Icon 428 for image management module 144, labeled “Photos;”
      • Icon 430 for camera module 143, labeled “Camera;”
      • Icon 432 for online video module 155, labeled “Online Video;”
      • Icon 434 for stocks widget 149-2, labeled “Stocks;”
      • Icon 436 for map module 154, labeled “Maps;”
      • Icon 438 for weather widget 149-1, labeled “Weather;”
      • Icon 440 for alarm clock widget 149-4, labeled “Clock;”
      • Icon 442 for workout support module 142, labeled “Workout Support;”
      • Icon 444 for notes module 153, labeled “Notes;” and
      • Icon 446 for a settings application or module, labeled “Settings,” which provides access to settings for device 100 and its various applications 136.


It should be noted that the icon labels illustrated in FIG. 4A are merely exemplary. For example, icon 422 for video and music player module 152 is labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.



FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3) that is separate from the display 450 (e.g., touch screen display 112). Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.


Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (e.g., contacts 460 and 462, and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) are used by the device to manipulate the user interface on the display (e.g., 450 in FIG. 4B) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein.


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



FIG. 5A illustrates exemplary personal electronic device 500. Device 500 includes body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitive display screen 504, hereafter touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or the touch-sensitive surface) optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device 500.


Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.


In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.



FIG. 5B depicts exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512 that operatively couples I/O section 514 with one or more computer processors 516 and memory 518. I/O section 514 can be connected to display 504, which can have touch-sensitive component 522 and, optionally, intensity sensor 524 (e.g., contact intensity sensor). In addition, I/O section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device 500 can include input mechanisms 506 and/or 508. Input mechanism 506 is, optionally, a rotatable input device or a depressible and rotatable input device, for example. Input mechanism 508 is, optionally, a button, in some examples.


Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.


Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700 and 900 (FIGS. 7A-7B and 9). A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B, but can include other or additional components in multiple configurations.


As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) each optionally constitute an affordance.


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 FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user's intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).


As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.



FIG. 5C illustrates detecting a plurality of contacts 552A-552E on touch-sensitive display screen 504 with a plurality of intensity sensors 524A-524D. FIG. 5C additionally includes intensity diagrams that show the current intensity measurements of the intensity sensors 524A-524D relative to units of intensity. In this example, the intensity measurements of intensity sensors 524A and 524D are each 9 units of intensity, and the intensity measurements of intensity sensors 524B and 524C are each 7 units of intensity. In some implementations, an aggregate intensity is the sum of the intensity measurements of the plurality of intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity that is a portion of the aggregate intensity. FIG. 5D illustrates assigning the aggregate intensity to contacts 552A-552E based on their distance from the center of force 554. In this example, each of contacts 552A, 552B, and 552E are assigned an intensity of contact of 8 intensity units of the aggregate intensity, and each of contacts 552C and 552D are assigned an intensity of contact of 4 intensity units of the aggregate intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij that is a portion of the aggregate intensity, A, in accordance with a predefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is the distance of the respective contact j to the center of force, and ΣDi is the sum of the distances of all the respective contacts (e.g., i=1 to last) to the center of force. The operations described with reference to FIGS. 5C-5D can be performed using an electronic device similar or identical to device 100, 300, or 500. In some embodiments, a characteristic intensity of a contact is based on one or more intensities of the contact. In some embodiments, the intensity sensors are used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity diagrams are not part of a displayed user interface, but are included in FIGS. 5C-5D to aid the reader.


In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.


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


An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.


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



FIGS. 5E-5H illustrate detection of a gesture that includes a press input that corresponds to an increase in intensity of a contact 562 from an intensity below a light press intensity threshold (e.g., “ITL”) in FIG. 5E, to an intensity above a deep press intensity threshold (e.g., “ITS”) in FIG. 5H. The gesture performed with contact 562 is detected on touch-sensitive surface 560 while cursor 576 is displayed over application icon 572B corresponding to App 2, on a displayed user interface 570 that includes application icons 572A-572D displayed in predefined region 574. In some embodiments, the gesture is detected on touch-sensitive display 504. The intensity sensors detect the intensity of contacts on touch-sensitive surface 560. The device determines that the intensity of contact 562 peaked above the deep press intensity threshold (e.g., “ITD”). Contact 562 is maintained on touch-sensitive surface 560. In response to the detection of the gesture, and in accordance with contact 562 having an intensity that goes above the deep press intensity threshold (e.g., “ITD”) during the gesture, reduced-scale representations 578A-578C (e.g., thumbnails) of recently opened documents for App 2 are displayed, as shown in FIGS. 5F-5H. In some embodiments, the intensity, which is compared to the one or more intensity thresholds, is the characteristic intensity of a contact. It should be noted that the intensity diagram for contact 562 is not part of a displayed user interface, but is included in FIGS. 5E-5H to aid the reader.


In some embodiments, the display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed in proximity of application icon 572B, as shown in FIG. 5F. As the animation proceeds, representation 578A moves upward and representation 578B is displayed in proximity of application icon 572B, as shown in FIG. 5G. Then, representations 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed in proximity of application icon 572B, as shown in FIG. 5H. Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses in accordance with an intensity of contact 562, as shown in FIGS. 5F-5G, where the representations 578A-578C appear and move upwards as the intensity of contact 562 increases toward the deep press intensity threshold (e.g., “ITD”). In some embodiments, the intensity, on which the progress of the animation is based, is the characteristic intensity of the contact. The operations described with reference to FIGS. 5E-5H can be performed using an electronic device similar or identical to device 100, 300, or 500.


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


For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.


Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.



FIGS. 6A-6H illustrate exemplary user interfaces displaying video for a live communication session with multiple focal planes, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 7A-7B.



FIG. 6A illustrates a first device 600a with first touch-sensitive display 602a. In some embodiments, first device 600a includes one or more features of devices 100, 300, and 500. First device 600a also includes first camera 603a, which, at a minimum, includes an image sensor that is capable of capturing data representing a portion of the light spectrum (e.g., visible light, infrared light, or ultraviolet light). First camera 603a includes at least one focal lens capable of being adjusted to focus first camera 603a on different focal planes (e.g., distances from first camera 603a at which the sharpest focus is attained). In some embodiments, first camera 603a includes a single focal lens for adjusting the focal plane. In some embodiments, the focal plane is adjusted by modifying the shape of the single focal lens. First camera 603a is capable of being adjusted to focus on different focal planes and capture images at different focal planes within a brief amount of time (e.g., less than 0.5 ms, 1 ms, 5 ms, 10 ms, 15 ms, or 20 ms). The images are captured at each of the different focal planes at a speed such that the multiple images with different focal planes can be associated with a single frame of video (e.g., the images are captured within a time period less than the time period of a frame of video). The content of the images associated with a frame of video appears substantially the same except for the difference in focal planes between the images. In some embodiments, one or more photographic properties of first camera 603a other than the focal plane (e.g., exposure, zoom level, white balance, contrast, ISO value) are kept constant during the capture of the multiple images.


In some embodiments, first camera 603a includes multiple image sensors and/or other types of sensors. In addition to capturing data representing sensed light, in some embodiments, first camera 603a is capable of capturing other types of data, such as depth data. For example, in some embodiments, first camera 603a also captures depth data using techniques based on speckle, time-of-flight, parallax, or focus. Image data that first device 600a captures using first camera 603a includes data corresponding to a portion of the light spectrum for a scene within the field of view of the camera. Additionally, in some embodiments, the captured image data also includes depth data for the light data. In some other embodiments, the captured image data contains data sufficient to determine or generate depth data for the data for the portion of the light spectrum.


In some examples, first device 600a includes a depth camera (e.g., as part of first camera 603a), such as an infrared camera, a thermographic camera, or a combination thereof. In some examples, first device 600a further includes a light-emitting device (e.g., light projector), such as an IR flood light, a structured light projector, or a combination thereof. The light-emitting device is, optionally, used to illuminate the subject during capture of the image by a visible light camera and a depth camera (e.g., an IR camera) and the information from the depth camera and the visible light camera are used to determine a depth map of different portions of a subject captured by the visible light camera. In some embodiments, a depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene from a viewpoint (e.g., a camera). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint's Z-axis where its corresponding two-dimensional pixel is located. In some examples, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0-255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., camera) in the “three dimensional” scene. In other examples, a depth map represents the distance between an object in a scene and the plane of the viewpoint.) In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user's face). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction.


As illustrated in FIG. 6A, first device 600a displays outgoing notification 604 of a live communication application (e.g., a video chat application). The outgoing notification 604 is displayed in response to sending a request to a second device (e.g., second device 600b described in reference to FIG. 6B) to join a live communication session (e.g., a video chat). Outgoing notification 604 includes cancel affordance 606 for canceling the request to join the live communication session (e.g., to immediately end the live communication session). In some embodiments, outgoing notification 604 also includes a name 608 of a second participant being requested to join the live communication session and/or an avatar 610 for the second participant. Outgoing notification 604 also includes an image 612 (e.g., a frame of video) of the first participant sending the request (e.g., a user of first device 600a) (e.g., as a preview of video being sent to second device 600b, as described in reference to FIG. 6B). Image 612 is captured via first camera 603a and corresponds to an environment within the field-of-view of first camera 603a. In this example, the environment within the field-of-view of first camera 603a includes the first participant sending the request.


In some embodiments, first device 600a captures image 612 such that the first participant appears out-of-focus (as illustrated by the dashed lines shown in FIG. 6A). In some embodiments, first device 600a identifies a first focal region where a predefined portion of the first participant (e.g., the first participant's face) would be captured with a sharp focus, and sets a focal plane of first camera 603a to be outside of that first focal region (e.g., the focal plane of first camera 603a is set such that the first participant's face is captured out-of-focus). In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to be outside of the first focal region (e.g., the first participant's face is captured out-of-focus in at least one of the images). In some embodiments, one or more of the images captured by first camera 603a are transmitted to the second device with the request to join the live communication session.



FIG. 6B illustrates a second device 600b with second touch-sensitive display 602b. In some embodiments, second device 600b includes one or more features of devices 100, 300, 500, and 600a. In some embodiments, second device 600b also includes second camera 603b. In some embodiments, second camera 603b includes one or more features of first camera 600a (e.g., at least one focal lens capable of being adjusted to focus second camera 603b on different focal planes).


As illustrated in FIG. 6B, second device 600b displays incoming notification 614 of a live communication application (e.g., a video chat application, such as a video chat application that is the same as, or compatible with, the video chat application generating notification outgoing notification 604 on device 600a). Incoming notification 614 is displayed in response to receiving a request to join a live communication session (e.g., a video chat) from first device 600a. Incoming notification 614 includes answer affordance 616 for joining the live communication session (e.g., to immediately join the live communication session or display a menu with options for joining the live communication session). In some embodiments, incoming notification 614 also includes a name 618 of the first participant sending the request and/or an avatar 620 for the first participant. Incoming notification 614 also includes an image 622 (e.g., a frame of video) of the first participant (e.g., the user of first device 600a).


While the request to join the live communication session is pending (e.g., before answer affordance 616 is selected), image 622 is displayed such that the first participant sending the request appears out-of-focus (e.g., blurry). In some embodiments, the first participant is displayed out-of-focus as a result of first device 600a setting the focal plane of first camera 603a to a focal region where the first participant is out-of-focus. In some embodiments, the participant is displayed out-of-focus as a result of second device 600b sending a request to first device 600a to set the focal plane of first camera 603a to a focal region where the first participant is out-of-focus. In some embodiments, the video data being sent by first device 600a to second device 600b includes image data of the first participant at multiple focal planes. Second device 600b then selects image data with a focal plane where the first participant is out-of-focus for display as image 622 in the incoming notification 614.


As illustrated in FIG. 6C, while the request to join the live communication session continues to be pending, image 622 is displayed by second device 600b such that the first participant continues to appear out-of-focus after the distance of the first participant from first camera 600a changes (e.g., the first participant moves closer to or further away from first camera 600a capturing image 622). In some embodiments, as first device 600a detects that the distance of the first participant from first camera 600a is changing, first device 600a modifies the focal plane of first camera 603a such that the first participant remains out-of-focus. In some embodiments, second device 600b detects that the distance of the first participant from the first camera 603a is changing, and sends a request to first device 600a to modify the focal plane of first camera 603a to keep the first participant out-of-focus. In some embodiments, the video data being sent by first device 600a to second device 600b includes image data of the first participant at multiple focal planes. Second device 600b then selects image data with a focal plane where the first participant is out-of-focus for display as the participant moves closer to or further away from first camera 603a.


In some embodiments, the live communication session is accepted in response to an input 617 (e.g., a contact on second touch-sensitive display 602b) on answer affordance 616. In response to second device 600b accepting the request to join the live communication session, image 622 changes to display the first participant in-focus (e.g., the first participant's face appears sharp), as shown in FIG. 6D.



FIG. 6D illustrates second device 600b displaying live communication interface 624 on second touch-sensitive display 602b. Live communication interface 624 is displayed in response to an acceptance (e.g., input 617) of the request to join the live communication session sent by first device 600a. In response to second device 600b joining the live communication session, image 622 changes to display the first participant in-focus (e.g., the first participant's face appears sharp, as illustrated by the solid lines in FIG. 6D). Live communication interface 624 further includes a preview image 626 of the second participant.


In some embodiments, in response to second device 600b accepting the request to join the live communication session, first device 600a sets the focal plane of first camera 603a such that the first participant is captured in-focus. In some embodiments, first device 600a sets the focal plane in response to a request from second device 600b. Video data with the first participant captured in-focus is then transmitted to second device 600b for display as image 622 in live communication interface 624. In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to capture the first participant in-focus. The images of the first participant captured at different focal planes are transmitted to second device 600b, and second device 600b selects image 622 where the first participant is captured in-focus for display in the live communication interface 624.


As illustrated in FIG. 6E, after the request to join the live communication session has been accepted, image 622 is displayed by second device 600b such that the first participant continues to appear in-focus after the distance of the first participant from first camera 600a changes (e.g., the first participant moves closer or further away from first camera 600a capturing image 622). In some embodiments, as first device 600a detects that the distance of the first participant from first camera 600a is changing, first device 600a modifies the focal plane of first camera 603a such that the first participant remains in-focus. In some embodiments, second device 600b detects that the distance of the first participant from the first camera 603a is changing, and sends a request to first device 600a to modify the focal plane of first camera 603a to keep the first participant in-focus. In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to capture the first participant in-focus at the changed distance from first camera 603a. The images of the first participant captured at different focal planes are transmitted to second device 600b, and second device 600b selects image 622 where the first participant is captured in-focus at the changed distance from first camera 603a for display in the live communication interface 624.


As illustrated in FIG. 6F, after the request to join the live communication session has been accepted, the first participant partially exits the frame of first camera 603a (as shown in FIG. 6A). When the first participant partially exits the camera frame (e.g., at least a portion of the first participant's face is out of view of first camera 603a), a lack of attention is detected. In response to detecting the lack of attention, image 622 is displayed by second device 600b such that the first participant appears out-of-focus. In some embodiments, the lack of attention is detected by first device 600a, and then first device 600a modifies the focal plane of first camera 603a such that the first participant appears out-of-focus. In some embodiments, the lack of attention is detected by second device 600b, and then second device 600b sends a request to first device 600a to modify the focal plane of first camera 603a to capture the first participant out-of-focus. In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to capture the first participant out-of-focus. The images of the first participant captured at different focal planes are transmitted to second device 600b, and second device 600b selects image 622 where the first participant is captured out-of-focus for display in the live communication interface 624 when the lack of attention is detected.


When the first participant returns to the camera frame (e.g., the first participant's face is fully in view of first camera 603a), a return of attention is detected. In response to the return of attention, image 622 is displayed by second device 600b such that the first participant appears in-focus again, as shown in FIG. 6D. In some embodiments, the return of attention is detected by first device 600a, and then first device 600a modifies the focal plane of first camera 603a such that the first participant appears in-focus. In some embodiments, the return of attention is detected by second device 600b, and then second device 600b sends a request to first device 600a to modify the focal plane of first camera 603a to capture the first participant in-focus. In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to capture the first participant in-focus. The images of the first participant captured at different focal planes are transmitted to second device 600b, and second device 600b selects image 622 where the first participant is captured in-focus for display in the live communication interface 624 when the return of attention is detected.


As illustrated in FIG. 6G, after the request to join the live communication session has been accepted, the first participant looks away from first device 600a (as shown in FIG. 6A) (e.g., the first participant turns their head away from first device 600a or the first participant's eyes gaze in a direction other than toward first device 600a). When the first participant looks away from first device 600a, a lack of attention is detected. In response to detecting the lack of attention, image 622 is displayed by second device 600b such that the first participant appears out-of-focus. In some embodiments, the lack of attention is detected by first device 600a, and then first device 600a modifies the focal plane of first camera 603a such that the first participant appears out-of-focus. In some embodiments, the lack of attention is detected by second device 600b, and then second device 600b sends a request to first device 600a to modify the focal plane of first camera 603a to capture the first participant out-of-focus. In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to capture the first participant out-of-focus. The images of the first participant captured at different focal planes are transmitted to second device 600b, and second device 600b selects image 622 where the first participant is captured out-of-focus for display in the live communication interface 624 when the lack of attention is detected.


When the first participant looks back toward first device 600a (e.g., the first participant turns their head toward first device 600a or the first participant's eyes gaze in a direction toward first device 600a), a return of attention is detected. In response to the return of attention, image 622 is displayed by second device 600b such that the first participant appears in-focus again, as shown in FIG. 6D. In some embodiments, the return of attention is detected by first device 600a, and then first device 600a modifies the focal plane of first camera 603a such that the first participant appears in-focus. In some embodiments, the return of attention is detected by second device 600b, and then second device 600b sends a request to first device 600a to modify the focal plane of first camera 603a to capture the first participant in-focus. In some embodiments, first device 600a captures multiple images of the first participant, where each image is captured with the first camera 603a set to a different focal plane, and where at least one of the images is captured with the focal plane of first camera 603a set to capture the first participant in-focus. The images of the first participant captured at different focal planes are transmitted to second device 600b, and second device 600b selects image 622 where the first participant is captured in-focus for display in the live communication interface 624 when the return of attention is detected.


As illustrated in FIG. 6H, in response to an input 628 (e.g., a contact on second touch-sensitive display 602b), the focal plane of image 622 is modified. In some embodiments, in response to input 628, non-visual feedback (e.g., audio/tactile) is provided in conjunction with (e.g., at the same time or near the same time as) modifying the focal plane of image 622.


In some embodiments, the focal plane of image 622 is modified in response to input 628 being on a location of image 622 having a different depth (e.g., the location of an object in the background of image 622). In response to input 628, second device 600b displays image 622 such that a portion of the image at the location selected with input 628 is displayed in-focus (e.g., the focal plane is changed to correspond to the background object). In some examples, as a result of changing the focal plane, first participant is displayed out-of-focus in image 622. In some embodiments, second device 600b sends a request to first device 600a to modify the focal plane of first camera 603a to capture the portion of the image at the location selected with input 628 in-focus. In some embodiments, first device 600a captures multiple images with different focal planes. The multiple images are transmitted to second device 600b, and second device 600b selects image 622 where the portion of the image at the location selected with input 628 is captured in-focus for display in the live communication interface 624.


In some embodiments, the focal plane of image 622 is modified based on a characteristic intensity of input 628 (e.g., a contact on second touch-sensitive display 602b having a characteristic intensity). For example, an input 628 having a characteristic intensity at or below the light press intensity threshold changes the focal plane of image 622 to correspond to a minimum focal plane of first camera 603a (e.g., a shallow focal plane where objects near first camera 603a are displayed in-focus). As the characteristic intensity of input 628 increases, the focal plane of image 622 is changed to correspond to deeper focal planes of first camera 603a (e.g., the focal planes shift further away from first camera 603a as the characteristic intensity of input 628 increases). In this way, a user can vary the focal plane of image 622 by changing the characteristic intensity of input 628.


In some embodiments, the focal plane of image 622 is modified based on a duration of input 628 (e.g., the length of time a contact is held on second touch-sensitive display 602b). For example, when input 628 is initially detected on second touch-sensitive display 602b, the focal plane of image 622 is changed to correspond to a minimum focal plane of first camera 603a (e.g., a shallow focal plane where objects near first camera 603a are displayed in-focus). As the duration of input 628 increases, the focal plane of image 622 is changed to correspond to deeper focal planes of first camera 603a (e.g., the focal planes gradually shift further away from first camera 603a as the duration of the contact increases). When input 628 ceases to be detected, the focal plane of image 622 is maintained at the last focal plane displayed for image 622. In this way, a user can vary the focal plane of image 622 by changing the duration of input 628.



FIGS. 7A-7B are a flow diagram illustrating a method for displaying video for a live communication session with different focal planes, in accordance with some embodiments. Method 700 is performed at a device (e.g., 100, 300, 500, 600b) with a display. Some operations in method 700 are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.


As described below, method 700 provides, among other things, an intuitive way for displaying video for a live communication session. The method reduces the cognitive burden on a user viewing the live communication session, thereby creating a more efficient human-machine interface.


The device (e.g., second device 600b) displays (702) video for a live communication session (e.g., an audio/video communication session with a live data stream transmitted by a capture device (e.g. first device 600a)). The video includes a subject of the live communication session with a predefined portion of the subject identified in a first focal region (e.g., a focal region where the head or face of a participant of the live communication session is in focus). In some embodiments, the video for the live communication session includes first image data corresponding to a focal plane outside of the first focal region and second image data corresponding to a focal plane inside the first focal region (e.g., video data stream from first device 600a includes data for multiple focal depths). In some embodiments, the first image data and second image data are transmitted/received at different periods of time in the video data, or at the same (e.g., approximately the same) period of time (e.g. the video data includes two discrete channels/streams of data for the same time period, having different focal planes). In some embodiments, the device (e.g., second device 600b) selects the image data with the focal plane outside the first focal region (e.g., to display the subject out-of-focus).


In accordance with a determination that a set of one or more conditions is met, the device displays (704) the video with a focal plane of the video selected to be outside of the first focal region (e.g., the head/face of a participant of the live communication session is out of focus in the video). In some embodiments, the video is captured by a capture device (e.g., first device 600a) with a lens set outside the first focal region. In some embodiments, the video includes video data at multiple focal depths and the device (e.g., second device 600b) selects the video data with a focal plane outside the first focal region for display. Displaying video for a live communication session with the focal plane of the video selected to be at different focal regions based on whether one or more conditions are met improves visual feedback by enabling a user to quickly and easily recognize the status of the live communication session (e.g., whether the live communication session has been joined and/or whether another participant is engaged in the live communication session). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


In some embodiments, the video for the live communication session is captured by a camera of a capture device (e.g., first device 600a with first camera 603a), and in accordance with the determination that the set of one or more conditions is met, the focal plane of the camera has been set (e.g. mechanically set/adjusted, set/adjusted via software) outside of the first focal region. In some embodiments, the device (e.g., second device 600b) sends a request to the capture device (e.g., first device 600a) to set the focal plane of the camera (e.g., first camera 603a) of the capture device outside of the first focal region.


Optionally, while (710) displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region and while the set of one or more conditions is met, the device (e.g., second device 600b) detects (712) a change in position of the predefined portion of the subject (e.g., the head/face of the participant moves forward or backward). The device then modifies (714) the first focal region based on the change in position of the predefined portion of the subject. The device then displays (716) the video for the live communication session with the focal plane of the video adjusted to continue being outside of the first focal region (e.g., the focal plane is changed to keep the head/face of the participant out-of-focus). Continually changing the focal plane for the live communication session to be outside of a focal region of the subject as the subject changes position improves visual feedback by enabling a user to quickly and easily recognize the status of the live communication session as the subject moves. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


While displaying the video for the live communication session with the focal plane of the video selected to be outside of the first focal region, the device determines (706) that the set of one or more conditions is no longer met.


In response to the determination that the set of one or more conditions is no longer met, the device displays (708) the video for the live communication session with the focal plane of the video selected to be inside of the first focal region (e.g., a focal region where the head/face of the participant of the live communication session is no longer out of focus in the video). In some embodiments, the video is captured by another device (e.g., first device 600a) with a camera lens set at a focal plane inside the first focal region. In some embodiments, the video includes video data at multiple focal depths and the device (e.g., second device 600b) selects the video data with a focal plane inside the first focal region for display.


Optionally, while (718) the set of one or more conditions is no longer met and while displaying the video for the live communication session with the focal plane of the video selected to be inside of the first focal region, the device (e.g., second device 600b) detects (720) a change in position of the predefined portion of the subject (e.g., the head/face of the participant moves forward or backward). The device then modifies (722) the first focal region based on the change in position of the predefined portion of the subject. The device then displays (724) the video for the live communication session with the focal plane of the video adjusted to continue being inside the first focal region (e.g., the focal plane is changed to keep the head/face of the participant in-focus). Continually changing the focal plane for the live communication session to be inside of a focal region of the subject as the subject changes position improves visual feedback by enabling a user to quickly and easily recognize the status of the live communication session as the subject moves. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


In some embodiments, the device (e.g., second device 600b) receives a request to participate in the live communication session, and the set of one or more conditions includes a condition that is met while the request is pending (e.g., when receiving an incoming video call, video of the participant initiating the call is displayed with the participant's head/face out-of-focus). In some embodiments, the request is pending when the request remains unaccepted (e.g., the device receiving the request is not transmitting video back to the requesting device). In some embodiments, in response to detecting an acceptance (e.g., 617) of the request to participate in the live communication session (e.g., an input (e.g., a finger contact) on an acceptance affordance (e.g., 616) displayed on a touch-sensitive display), the device determines that the set of one or more conditions is no longer met (e.g., the subject is displayed out-of-focus until the live communication session is accepted, and then the subject is displayed in-focus). Displaying video for a live communication session with the focal plane of the video selected to be at different focal regions based on whether a request to join the live communication session is pending improves visual feedback by enabling a user to quickly and easily recognize the status of the live communication session. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


In some embodiments, the set of one or more conditions includes a condition that is met when a lack of attention from the subject of the live communication session has been detected (e.g., subject of video call appears out-of-focus when they are not paying attention to the video call) (e.g. detected via face and/or gaze detection techniques that are, optionally, based on analysis of the video data (e.g., analysis performed at second device 600b, or analysis performed by first device 600a providing the video data along with attention detection data, to the second device 600b)). In some embodiments, the lack of attention is detected based at least in part on the predefined portion of the subject (e.g., the subject's head/face) at least partially exiting an image boundary of the live communication session (e.g., the camera frame of the capture device) for a predetermined amount of time. In some embodiments, in response to a detection that the predefined portion of the subject (e.g., the subject's head/face) reenters the image boundary of the live communication session (e.g., the camera frame of the capture device), the device determines that the set of one or more conditions is no longer met (e.g., the subject is displayed out-of-focus if their head/face partially moves out of the camera frame, and then the subject is displayed in-focus when their head/face returns to the camera frame). Displaying video for a live communication session with the focal plane of the video selected to be at different focal regions based on whether a lack of attention is detected improves visual feedback by enabling a user to quickly and easily recognize the status of the live communication session. Displaying video for the live communication session with the focal plane of the video selected to be at different focal regions based on whether a lack of attention is detected also improves privacy by obfuscating the identity and/or activities of a participant when they are not paying attention to the live communication session. Providing improved visual feedback and privacy to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. Furthermore, user inputs are not required to change the focal plane of the video for the live communication, which allows the live communication session to quickly and easily continue when a return of attention is detected. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


In some embodiments, the lack of attention is detected based at least in part on an eye gaze of the subject being directed in a direction other than toward a capture device (e.g., first device 600a) capturing the live communication session for a predetermined amount of time (e.g., the subject is displayed out-of-focus while they look away from the first camera 603a). In some embodiments, the subject's head/face remains in the camera frame at the same focal plane while they look away from the capture device. In some embodiments, in response to a detection that the eye gaze of the subject is directed toward the capture device (e.g., first device 600a) capturing the live communication session, the device (e.g., second device 600b) determines that the set of one or more conditions is no longer met (e.g., the subject is displayed out-of-focus while they look away from first camera 603a, and then the subject is displayed in-focus when their gaze returns to first camera 603a). Displaying video for a live communication session with the focal plane of the video selected to be at different focal regions based on a participant's eye gaze improves visual feedback by enabling a user to quickly and easily recognize the status of the live communication session. Displaying video for the live communication session with the focal plane of the video selected to be at different focal regions based on a participant's eye gaze also improves privacy by obfuscating the identity and/or activities of a participant when they are not paying attention to the live communication session. Providing improved visual feedback and privacy to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently. Furthermore, user inputs are not required to change the focal plane of the video for the live communication, which allows the live communication session to quickly and easily continue when a return of attention is detected. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


Optionally, while displaying the video for the live communication session on a touch-sensitive display, the device (e.g., second device 600b) detects (726) an input (e.g., 628) (e.g., a finger contact) on the touch-sensitive display. The device then displays (728) the video for the live communication session with the focal plane of the video selected based on one or properties of the input (e.g., location, duration, and/or pressure of the finger contact).


In some embodiments, the device (e.g., second device 600b) sends a request to the capture device (e.g., first device 600a) to set the focal plane of the camera (e.g., first camera 603a) based on the one or more properties of the input (e.g., first device 600a is instructed to capture images having the desired focus, and to send video data including the images to second device 600b). In some embodiments, the video for the live communication session includes image data for two or more focal planes (e.g., video stream from the first device 600a includes data for multiple focal depths (e.g., for the same time period (e.g., providing two channels of video data, having different focal planes)), and the device (e.g., second device 600b) selects image data having a respective focal plane of the two or more focal planes for display based on the one or more properties of the input. In some embodiments, the one or more properties of the input includes a characteristic intensity of the input. In some embodiments, the one or more properties of the input includes a duration of the input (e.g., long press). In some embodiments, the one or more properties of the input includes a location of the input on the touch-sensitive display (e.g., if input location corresponds to a location of an object in the live communication session, focal plane changes to a focal region of the object). In some embodiments, the device (e.g., second device 600b) provides non-visual feedback (e.g., audio/tactile) in conjunction with (e.g., at the same time or near the same time as) the video for the live communication session is displayed with the focal plane of the video selected based on the one or properties of the input (e.g., non-visual feedback occurs when the focal plane of the video changes in response to the input).


Note that details of the processes described above with respect to method 700 (e.g., FIGS. 7A-7B) are also applicable in an analogous manner to the methods described below. For example, method 700 optionally includes one or more of the characteristics of the various methods described below with reference to method 900. For example, a plurality of still images with a plurality of different focal planes as described below with respect to method 900 can used in a live communication session described above with respect to method 700. For brevity, these details are not repeated below.



FIGS. 8A-8E illustrate exemplary user interfaces for capturing images with multiple focal planes, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 9.



FIG. 8A illustrates a front-view 800a and a rear-view 800b of device 800 with touch-sensitive display 802. In some embodiments, device 800 includes one or more features of devices 100, 300, and 500. Device 800 also includes an input device 804 (e.g., a mechanical input button, a press-able input button) and a camera 808. Camera 808, at a minimum, includes an image sensor that is capable of capturing data representing a portion of the light spectrum (e.g., visible light, infrared light, or ultraviolet light). Camera 808 includes at least one focal lens capable of being adjusted to focus camera 808 on different focal planes (e.g., distances from camera 808 at which the sharpest focus is attained). In some embodiments, camera 808 includes a single focal lens for adjusting the focal plane. In some embodiments, the focal plane is adjusted by modifying the shape of the single focal lens. Camera 808 is capable of being adjusted to focus on different focal planes and capture images at each of the different focal planes within a brief amount of time (e.g., less than 0.5 ms, 1 ms, 5 ms, 10 ms, 15 ms, or 20 ms). The images are captured at each of the different focal planes at a speed such that the multiple images with different focal planes can be associated with approximately the same moment in time. The content of the images appear substantially the same except for the difference in focal planes between the images. In some embodiments, one or more photographic properties of camera 808 other than the focal plane (e.g., exposure, zoom level, white balance, contrast, ISO value) are kept constant during the capture of the multiple images.


In some embodiments, camera 808 includes multiple image sensors and/or other types of sensors. In addition to capturing data representing sensed light, in some embodiments, camera 808 is capable of capturing other types of data, such as depth data. For example, in some embodiments, camera 808 also captures depth data using techniques based on speckle, time-of-flight, parallax, or focus. Image data that device 800 captures using camera 808 includes data corresponding to a portion of the light spectrum for a scene within the field of view of the camera. Additionally, in some embodiments, the captured image data also includes depth data for the light data. In some other embodiments, the captured image data contains data sufficient to determine or generate depth data for the data for the portion of the light spectrum.


In some examples, device 800 includes a depth camera (e.g., as part of camera 808), such as an infrared camera, a thermographic camera, or a combination thereof. In some examples, camera 808 further includes a light-emitting device (e.g., light projector), such as an IR flood light, a structured light projector, or a combination thereof. The light-emitting device is, optionally, used to illuminate the subject during capture of the image by a visible light camera and a depth camera (e.g., an IR camera) and the information from the depth camera and the visible light camera are used to determine a depth map of different portions of a subject captured by the visible light camera. In some embodiments, a depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene from a viewpoint (e.g., a camera). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint's Z-axis where its corresponding two-dimensional pixel is located. In some examples, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0-255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., camera) in the “three dimensional” scene. In other examples, a depth map represents the distance between an object in a scene and the plane of the viewpoint.) In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user's face). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction.


In FIG. 8A, electronic device 800 displays, on touch-sensitive display 802, a user interface 806 (e.g., a lock-screen user interface) that includes an affordance 812 for launching an image capture application (e.g., a camera application, an image/photo capturing and editing application). While displaying user interface 806, device 800 detects (e.g., via touch-sensitive display 802) an activation 801 of affordance 812 (e.g., a tap gesture on affordance 812).


In FIG. 8B, in response to detecting activation 801 (or in response to other image capture requests), device 800 displays, on touch-sensitive display 802, a user interface 814 of the image capture application. In this example, image capture application is in a photo mode. While displaying user interface 814 of the image capture application, device 800 receives, via camera 808, image data corresponding to the environment within the field-of-view of camera 808.


Device 800 displays a preview image 818 corresponding to the image data received via camera 808 in the user interface 814 of the image capture application. In this example, preview image 818 includes multiple objects, including a foreground object 820a (e.g., a dog), a middleground object (e.g., a person), and a background object 820c (e.g., a plant). As illustrated in FIG. 8B, the focal plane of camera 808 is set such that middlegound object 820b and background object 820c are displayed out-of-focus (as illustrated by dashed lines) while foreground object 820a is displayed in-focus (as illustrated by solid lines) in preview image 818.


User interface 814 of the image capture application also includes a shutter affordance 822 (e.g., a virtual shutter button). While displaying preview image 818 in user interface 814, device 800 detects an activation 805 of shutter affordance 822 (e.g., a single tap gesture on shutter affordance 822). In response to detecting activation 805, device 800 captures multiple still images corresponding to the environment currently in the field-of-view of camera 808 (e.g., multiple still images of objects 820a-820c included in preview image 818). The still images are captured with multiple different focal planes in response to the activation 805. The multiple different focal planes are selected without reference to changes in objects in the field of view of the camera during the capture of the multiple still images (e.g., the different focal planes are predefined or are selected at the same time and do not change based on movement of the camera or movement of objects toward or away from the camera during the capture of the multiple still images).


In some embodiments, the multiple still images are captured in response to an activation of input device 804 (e.g., a single press of a physical input button). In some embodiments, after capturing the multiple still images with multiple different focal planes, the preview image 818 continues to be displayed. In some embodiments, after capturing the multiple still images with multiple different focal planes, one of the captured still images corresponding to the preview image 818 is displayed (e.g., image 826 shown in FIG. 8D).


In some embodiments, device 800 detects an input 807 (e.g., a contact on touch-sensitive display 802) at a location in preview image 818 corresponding to middleground object 820b. In response to detecting input 807, device 800 captures multiple still images with different focal planes and then displays one of the captured still images (e.g., image 824 shown in FIG. 8C) having a focal plane corresponding to middleground object 820b, as shown in FIG. 8C (e.g., tapping on an object in the preview image 818 causes multiple images with different focal planes to be captured, and an image with that object in-focus to be displayed).


As illustrated in FIG. 8C, image 824 is displayed in user interface 814. Image 824 includes middleground object 820b displayed in-focus, and foreground object 820a and background object 820c displayed out-of-focus. Image 824 is displayed in response to input 807 on the location in preview image 818 corresponding to middleground object 820b, as described in reference to FIG. 8B. While displaying image 824, device 800 detects input 809. In some embodiments, input 809 is at a location in image 824 corresponding to foreground object 820a. In response to input 809 at the location corresponding to foreground object 820a, device 800 displays an image (e.g., image 826 shown in FIG. 8D) having a focal plane corresponding to foreground object 820a, as shown in FIG. 8D (e.g., tapping on an object in image 824 causes an image to be displayed with that object in-focus, without capturing additional images).


In some embodiments, input 809 has a corresponding characteristic intensity. Based on the characteristic intensity of input 809, device 800 displays an image (e.g., image 826 shown in FIG. 8D) having a different focal plane (e.g., a light press causes an image with a shallow focal plane to be displayed, while a deep press causes an image with a deep focal plane to be displayed, without capturing additional images). In some embodiments, device 800 maintains display of image 824 unless input 809 has a corresponding characteristic intensity greater than a threshold intensity. In some embodiments, the threshold intensity is based at least in part on a focal plane of an object captured in the multiple still images (e.g., the characteristic intensity of input 809 pushes the focal plane deeper into image 824 until the focal plane is at a depth corresponding to an object in the image). When the characteristic intensity of input 809 is greater than the threshold intensity, device 800 provides feedback indicating the threshold intensity has been exceeded (e.g., audio/tactile/visual feedback occurs when focal plane is pushed to a depth corresponding to an object in the image).


In some embodiments, input 809 has a corresponding duration (e.g., a long or short press). Based on the duration of input 809, device 800 displays an image (e.g., image 826 shown in FIG. 8D) having a different focal plane (e.g., a short press causes an image with a shallow focal plane to be displayed, while a long press causes an image with a deep focal plane to be displayed, without capturing additional images).


As illustrated in FIG. 8D, image 826 is displayed in user interface 814. Image 826 includes foreground object 820a displayed in-focus, and middleground object 820b and background object 820c displayed out-of-focus. Image 826 is displayed in response to input 809, as described in reference to FIG. 8C. In some embodiments, image 826 is displayed in response to activation 805 of shutter affordance 822 or activation of input device 804, as described in reference to FIG. 8B.


Image 826 is one of the multiple still images captured as described in reference to FIG. 8B. While displaying image 826, device 800 detects input 811 at a location in image 826 corresponding to background object 820c. In response to input 811, device 800 displays an image (e.g., image 828 shown in FIG. 8E) with background object 820c displayed in-focus while foreground object 820a continues to be displayed in-focus, as shown in FIG. 8E (e.g., tapping on another object in the image causes an image to be displayed with that object in-focus and the previously selected object also in-focus, without capturing additional images).


As illustrated in FIG. 8E, image 828 is displayed in user interface 814. Image 828 includes foreground object 820a and background object 820c displayed in-focus, and middleground object 820b displayed out-of-focus. Image 828 is displayed in response to input 811 on the location in image 824 corresponding to background object 820c, as described in reference to FIG. 8C. Input 811 is detected after another input 809 selected foreground object 820a to be displayed in-focus. Image 828 is a composite of a first image captured with foreground object 820a in-focus and a second image captured with background object 820c in-focus. Both the first image and second image were captured in response to input 807 described in reference to FIG. 8B. The composite image 828 includes at least the foreground object 820a from the first image and the background object 820c from the second image. Other portions of the composite image 828 (e.g., middleground object 820b) can be from the first image, the second image, or from other captured still images, such that the other portions of image 828 are displayed out-of-focus.


In some embodiments, device 800 receives a request to display an animation including two or more of the captured still images. For example, the animation includes displaying a first image (e.g., image 824 shown in FIG. 8C) with a first focal plane for a predetermined amount of time, followed by a second image (e.g., image 826 shown in FIG. 8D) with a different focal plane for a predetermined amount of time. In some embodiments, the animation continues indefinitely, cycling between the first image and the second image, until a cancellation input is received. In some embodiments, the animation continues cycling between the first image and the second image as long as an input is maintained (e.g., as long as contact is detected on the touch-sensitive display).


In some embodiments, device 800 determines depth information of the scene being captured in the multiple still images based on image data of the still images. For example, device identifies objects in the scene, and based on the focal planes of the objects, determines the depth of the object in the scene. In some embodiments, an operation is performed on at least one of the still images using the depth information, such as applying a simulated depth effect (e.g., a visual effect having a depth component), inserting an object into the scene, making a measurement, etc. In some embodiments, applying the simulated depth effect includes adjusting areas of the image that correspond to a selected depth to have different degrees of blurriness/sharpness, sizes, degrees of brightness, degrees of saturation, and/or degrees of shape-distortion in order to simulate the depth effect, such as a bokeh effect. In some embodiments, the simulated depth effect is “simulated” in that the effect is (artificially) generated based on a manipulation of the underlying image data for the area of the image to create and apply the effect to the image (e.g., as opposed to being a “natural” effect that is based on underlying data as originally captured via one or more cameras based on the optical properties of light passing through one or more lenses to reach the image sensor of the camera).



FIG. 9 is a flow diagram illustrating a method for displaying capturing a plurality of still images with a plurality of different focal planes, in accordance with some embodiments. Method 900 is performed at a device (e.g., 100, 300, 500, 800) with a camera (e.g., 808). In some embodiments, the camera includes a single lens for adjusting the focal length of the camera. In some embodiments, the focal length changes by modifying the shape of the lens. Some operations in method 900 are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.


As described below, method 900 provides, among other things, an intuitive way for capturing images of an environment with different focal planes. The method reduces the cognitive burden on a user capturing an image of the environment, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to capture images with different focal planes faster and more efficiently conserves power and increases the time between battery charges.


The device (e.g., 800) detects (902) activation (e.g., 805, 807) of a shutter button (e.g., 804, 822, preview image 818) (e.g., a physical or virtual shutter button) that is associated with capturing still images.


In response to the activation of the shutter button, the device captures (904) a plurality of still images with a plurality of different focal planes. In some embodiments, at least one photographic property of the camera (e.g., exposure, zoom level, white balance, contrast, ISO value) other than the focal plane is maintained during the capture of the plurality of still images.


Capturing the plurality of still images includes capturing (906) first image data with the camera focused at a first focal plane (e.g., the image is captured with a lens of the camera set at a first focal length).


After capturing the first image data with the camera focused at the first focal plane, the device captures (908) second image data with the camera focused at a second focal plane. The second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data (e.g., the first focal plane and the second focal plane are predefined or are selected at the same time in response to the activation of the shutter button and do not change based on movement of the camera or movement of objects toward or away from the camera between the capture of the first image data and the capture of the second image data). In some embodiments, the lens is changed to the second focal plane by modifying the shape of the lens. In some embodiments, the second image data is captured at a second time, later than a first time at which the first image data is captured. In some embodiments, the first image data and the second image data are consolidated into a single data file. Capturing a plurality of still images with a plurality of different focal planes in response to a single activation of a shutter button allows the still images to be captured more efficiently. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


In some embodiments, detecting the activation of the shutter button includes detecting an input (e.g., 807) on a touch-sensitive display. In response to detecting the input, the device selects a respective image of the plurality of still images based on one or more properties of the input and displays the respective image of the plurality of still images (e.g., a single finger contact triggers capture of the plurality of still images and selects the focal plane for an image to be displayed). In some embodiments, the one or properties of the input include a characteristic intensity of the input. In some embodiments, the one or more properties of the input (e.g., 807) includes a location (e.g., on middleground object 820b) of the input on the touch-sensitive display. In some embodiments, if the input location corresponds to a location of an object being captured in the plurality of still images (e.g., on middleground object 820b), the focal plane of the image being displayed corresponds to the focal plane of the object). Capturing a plurality of still images with a plurality of different focal planes and then displaying one of the still images in response to a single input allows the still images to be captured and displayed more efficiently. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


Optionally, after capturing the plurality of still images, the device displays (910) on a touch-sensitive display (e.g., 802), a first image (e.g., 824) of the plurality of still images corresponding to the first image data. The device then detects (912) a first input (e.g., 809) (e.g., a finger contact) at a location (e.g., 820a) on the touch-sensitive display corresponding to the first image. In response to the first input, the device displays (914) a second image (e.g., 826) of the plurality of still images corresponding to the second image data. Selecting a second image with a different focal plane for display based on a single input on a touch-sensitive display allows the second image to be displayed more efficiently. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.


In some embodiments, displaying the second image (e.g., 826) includes selecting the second image from the plurality of still images based on one or properties of the first input, the one or more properties including a characteristic intensity of the first input. In some embodiments, in accordance with a determination that the characteristic intensity of the first input is greater than a threshold intensity, the device maintains display of the second image after the first input ceases to be detected by the device, and in accordance with a determination that the characteristic intensity of the first input is less than the threshold intensity, the device displays the first image after the first input ceases to be detected by the device. In some embodiments, the threshold intensity is based at least in part on a focal plane of an object being captured in the plurality of still images (e.g., the characteristic intensity of input 809 pushes the focal plane deeper into image 824 until the focal plane is at a depth corresponding to an object in the image). In some embodiments, after changing to the focal plane of the object, focus is maintained on the object for subsequent activations of the shutter button. In some embodiments, in accordance with the determination that the characteristic intensity of the first input is greater than the threshold intensity, the device provides feedback indicating the threshold intensity is exceeded (e.g., audio/tactile/visual feedback occurs when the characteristic intensity of the first input exceeds the threshold).


In some embodiments, the one or properties of the first input include a duration of the input (e.g., long press, short press).


In some embodiments, the one or more properties of the first input includes the location (e.g., on foreground object 820a) of the first input on the touch-sensitive display. The device identifies an object in the first image corresponding to the location of the first input, where the object is associated with a respective focal plane. The device then displays an image (e.g., 826) of the plurality of still images captured with the respective focal plane (e.g., when the input location corresponds to a location of an object being captured in the plurality of still images, the focal plane changes to the respective focal plane of the object). In some embodiments, after the object is selected with the first input, focus is maintained on the object for subsequent activations of the shutter button.


In some embodiments, while displaying the second image (e.g., 826) of the plurality of still images, the device detects a second input (e.g., 811) (e.g., a finger contact) at a location (e.g., on background object 820c) on the touch-sensitive display corresponding to the second image. In response to the second input, the device displays a composite image (e.g., 828) on the touch-sensitive display. The composite image includes a portion of the second image associated with the first input (e.g., a portion of the image selected to be displayed in focus by the first input) and a portion of the second image associated with the second input (e.g., a portion of the image selected to be displayed in focus by the second input, such that multiple planes (e.g., foreground and background) are displayed in-focus, while other planes (e.g., a middleground) are displayed out-of-focus).


In some embodiments, after capturing the plurality of still images, the device receives a request (e.g., a single request, a single input) to display two or more images of the plurality of still images. In response to receiving the request, the device displays a first image of the plurality of still images and displays a second image of the plurality of still images a predetermined time after displaying the first image, where the first image and the second image were captured with different focal planes. In some embodiments, additional images having different focal depths are also displayed. In some embodiments, the sequence of images with different focal planes are automatically played through in a loop or back and forth (e.g., “boomerang”) animation. In some embodiments, the sequence of images is displayed in response to a user input, and continues to be displayed either while the user's input is maintained or until a cancellation input is received.


In some embodiments, the device determines depth information of a scene captured in the plurality of still images with the plurality of different focal planes. The depth information is determined based on image data of the plurality of still images. In some embodiments, an operation is performed on at least one of the plurality of still images using the depth information, such as applying a simulated depth effect (e.g., a visual effect having a depth component), inserting an object into the scene, making a measurement, etc. In some embodiments, applying the simulated depth effect includes adjusting areas of the image that correspond to a selected depth to have different degrees of blurriness/sharpness, sizes, degrees of brightness, degrees of saturation, and/or degrees of shape-distortion in order to simulate the depth effect, such as a bokeh effect. In some embodiments, the simulated depth effect is “simulated” in that the effect is (artificially) generated based on a manipulation of the underlying image data for the area of the image to create and apply the effect to the image (e.g., as opposed to being a “natural” effect that is based on underlying data as originally captured via one or more cameras based on the optical properties of light passing through one or more lenses to reach the image sensor of the camera).


Note that details of the processes described above with respect to method 900 (e.g., FIG. 9) are also applicable in an analogous manner to the methods described above. For example, method 900 optionally includes one or more of the characteristics of the various methods described above with reference to method 700. For example, a plurality of still images with a plurality of different focal planes as described above with respect to method 900 can used in a live communication session described above with respect to method 700. For brevity, these details are not repeated below.


The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.


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


As described above, one aspect of the present technology is the gathering and use of data available from various sources to change the focal plane of stored images or a live video communication. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.


The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to can be used to recognize a person or subject within a captured image or video. Accordingly, use of such personal information data enables users to more easily recognize the content of a captured image or live video communication. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user's general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.


The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.


Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of detection and recognition of a person or subject within an image or live video communication, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.


Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.


Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, images or live video communications can be displayed based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the device, or publicly available information.

Claims
  • 1. An electronic device, comprising: a camera;a touch-sensitive display;one or more processors; andmemory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: detecting activation of a shutter button that is associated with capturing still images;in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: capturing first image data with the camera focused at a first object in a first focal plane; andafter capturing the first image data with the camera focused at the first object in the first focal plane, adjusting a camera focus from the first focal plane to a second focal plane and capturing second image data with the camera focused at a second object in the second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data;after capturing the plurality of still images, displaying, via the touch-sensitive display, a first image of the plurality of still images corresponding to the first image data, wherein the first image includes the first object in-focus and the second object out-of-focus;while displaying the first image of the plurality of still images, detecting a first input at a location on the touch-sensitive display corresponding to the location of the second object; andin response to detecting the first input, displaying, via the touch-sensitive display, a second image, wherein the second image includes the first object in-focus and the second object in-focus.
  • 2. The electronic device of claim 1, the one or more programs include instructions for: while displaying the first image of the plurality of still images, detecting a second input at a location on the touch-sensitive display corresponding to the first image; andin response to detecting the second input, displaying, via the touch-sensitive display, a third image of the plurality of still images corresponding to the second image data.
  • 3. The electronic device of claim 2, wherein displaying the third image includes selecting the third image from the plurality of still images based on one or more properties of the second input, and wherein the one or more properties include a characteristic intensity of the second input.
  • 4. The electronic device of claim 3, the one or more programs including instructions for: in accordance with a determination that the characteristic intensity of the second input is greater than a threshold intensity, maintaining display of the third image after the second input ceases to be detected by the device; andin accordance with a determination that the characteristic intensity of the second input is less than the threshold intensity, displaying the first image after the second input ceases to be detected by the device.
  • 5. The electronic device of claim 4, wherein the threshold intensity is based at least in part on a focal plane of an object being captured in the plurality of still images.
  • 6. The electronic device of claim 4, the one or more programs including instructions for: in accordance with the determination that the characteristic intensity of the second input is greater than the threshold intensity, providing feedback indicating the threshold intensity is exceeded.
  • 7. The electronic device of claim 2, wherein the one or more properties of the second input include a duration of the second input.
  • 8. The electronic device of claim 2, wherein the one or more properties of the second input includes the location of the second input on the touch-sensitive display, and wherein the one or more programs include instructions for: identifying a respective object in the first image corresponding to the location of the second input, wherein the respective object is associated with a respective focal plane; anddisplaying an image of the plurality of still images captured with the respective focal plane.
  • 9. The electronic device of claim 1, wherein the second image is a composite image that includes a portion of the first image data and a portion of the second image data.
  • 10. The electronic device of claim 1, wherein at least one photographic property of the camera other than the focal plane is maintained during the capture of the plurality of still images.
  • 11. The electronic device of claim 1, wherein detecting the activation of the shutter button includes detecting an input corresponding to activation of the shutter button on the touch-sensitive display, and wherein the one or more programs include instructions for: in response to detecting the input corresponding to activation of the shutter button: selecting a respective image of the plurality of still images based on one or more properties of the input corresponding to activation of the shutter button; anddisplaying, via the touch-sensitive display, the respective image of the plurality of still images.
  • 12. The electronic device of claim 11, wherein the one or more properties of the input corresponding to activation of the shutter button include a characteristic intensity of the input.
  • 13. The electronic device of claim 11, wherein the one or more properties of the input corresponding to activation of the shutter button includes a location of the input on the touch-sensitive display.
  • 14. The electronic device of claim 1, wherein the one or more programs include instructions for: after displaying the first image of the plurality of still images, displaying another image of the plurality of still images a predetermined time after displaying the first image, wherein the first image and the another image were captured with different focal planes.
  • 15. The electronic device of claim 1, the one or more programs including instructions for: determining depth information of a scene captured in the plurality of still images with the plurality of different focal planes, wherein the depth information is determined based on image data of the plurality of still images.
  • 16. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a camera and a touch-sensitive display, the one or more programs including instructions for: detecting activation of a shutter button that is associated with capturing still images;in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: capturing first image data with the camera focused at a first object in a first focal plane; andafter capturing the first image data with the camera focused at the first object in the first focal plane, adjusting a camera focus from the first focal plane to a second focal plane and capturing second image data with the camera focused at a second object in the second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data;after capturing the plurality of still images, displaying, via the touch-sensitive display, a first image of the plurality of still images corresponding to the first image data, wherein the first image includes the first object in-focus and the second object out-of-focus;while displaying the first image of the plurality of still images, detecting a first input at a location on the touch-sensitive display corresponding to the location of the second object; andin response to detecting the first input, displaying, via the touch-sensitive display, a second image, wherein the second image includes the first object in-focus and the second object in-focus.
  • 17. A method comprising: at an electronic device with a camera and a touch-sensitive display: detecting activation of a shutter button that is associated with capturing still images;in response to the activation of the shutter button, capturing a plurality of still images with a plurality of different focal planes, including: capturing first image data with the camera focused at a first object in a first focal plane; andafter capturing the first image data with the camera focused at the first object in the first focal plane, adjusting a camera focus from the first focal plane to a second focal plane and capturing second image data with the camera focused at a second object in the second focal plane, wherein the second focal plane is selected without reference to changes in objects in the field of view of the camera between the capture of the first image data and the capture of the second image data;after capturing the plurality of still images, displaying, via the touch-sensitive display, a first image of the plurality of still images corresponding to the first image data, wherein the first image includes the first object in-focus and the second object out-of-focus;while displaying the first image of the plurality of still images, detecting a first input at a location on the touch-sensitive display corresponding to the location of the second object; andin response to detecting the first input, displaying, via the touch-sensitive display, a second image, wherein the second image includes the first object in-focus and the second object in-focus.
  • 18. The electronic device of claim 1, the one or more programs include instructions for: after capturing the plurality of still images, displaying, via the touch-sensitive display, the first image of the plurality of still images corresponding to the first image data without displaying other images of the plurality of still images.
  • 19. The electronic device of claim 1, the one or more programs including instructions for: in response to detecting the first input, displaying, via the touch-sensitive display, the second image without displaying other images of the plurality of still images.
  • 20. The non-transitory computer-readable storage medium of claim 16, the one or more programs include instructions for: while displaying the first image of the plurality of still images, detecting a second input at a location on the touch-sensitive display corresponding to the first image; andin response to detecting the second input, displaying, via the touch-sensitive display, a third image of the plurality of still images corresponding to the second image data.
  • 21. The non-transitory computer-readable storage medium of claim 20, wherein displaying the third image includes selecting the third image from the plurality of still images based on one or more properties of the second input, and wherein the one or more properties include a characteristic intensity of the second input.
  • 22. The non-transitory computer-readable storage medium of claim 21, the one or more programs including instructions for: in accordance with a determination that the characteristic intensity of the second input is greater than a threshold intensity, maintaining display of the third image after the second input ceases to be detected by the device; andin accordance with a determination that the characteristic intensity of the second input is less than the threshold intensity, displaying the first image after the second input ceases to be detected by the device.
  • 23. The non-transitory computer-readable storage medium of claim 22, wherein the threshold intensity is based at least in part on a focal plane of an object being captured in the plurality of still images.
  • 24. The non-transitory computer-readable storage medium of claim 22, the one or more programs including instructions for: in accordance with the determination that the characteristic intensity of the second input is greater than the threshold intensity, providing feedback indicating the threshold intensity is exceeded.
  • 25. The non-transitory computer-readable storage medium of claim 20, wherein the one or more properties of the second input include a duration of the second input.
  • 26. The non-transitory computer-readable storage medium of claim 20, wherein the one or more properties of the second input includes the location of the second input on the touch-sensitive display, and wherein the one or more programs include instructions for: identifying a respective object in the first image corresponding to the location of the second input, wherein the respective object is associated with a respective focal plane; anddisplaying an image of the plurality of still images captured with the respective focal plane.
  • 27. The non-transitory computer-readable storage medium of claim 16, wherein the second image is a composite image that includes a portion of the first image data and a portion of the second image data.
  • 28. The non-transitory computer-readable storage medium of claim 16, wherein at least one photographic property of the camera other than the focal plane is maintained during the capture of the plurality of still images.
  • 29. The non-transitory computer-readable storage medium of claim 16, wherein detecting the activation of the shutter button includes detecting an input corresponding to activation of the shutter button on the touch-sensitive display, and wherein the one or more programs include instructions for: in response to detecting the input corresponding to activation of the shutter button: selecting a respective image of the plurality of still images based on one or more properties of the input corresponding to activation of the shutter button; anddisplaying, via the touch-sensitive display, the respective image of the plurality of still images.
  • 30. The non-transitory computer-readable storage medium of claim 29, wherein the one or more properties of the input corresponding to activation of the shutter button include a characteristic intensity of the input.
  • 31. The non-transitory computer-readable storage medium of claim 29, wherein the one or more properties of the input corresponding to activation of the shutter button includes a location of the input on the touch-sensitive display.
  • 32. The non-transitory computer-readable storage medium of claim 16, wherein the one or more programs include instructions for: after displaying the first image of the plurality of still images, displaying another image of the plurality of still images a predetermined time after displaying the first image, wherein the first image and the another image were captured with different focal planes.
  • 33. The non-transitory computer-readable storage medium of claim 16, the one or more programs including instructions for: determining depth information of a scene captured in the plurality of still images with the plurality of different focal planes, wherein the depth information is determined based on image data of the plurality of still images.
  • 34. The non-transitory computer-readable storage medium of claim 16, the one or more programs include instructions for: after capturing the plurality of still images, displaying, via the touch-sensitive display, the first image of the plurality of still images corresponding to the first image data without displaying other images of the plurality of still images.
  • 35. The non-transitory computer-readable storage medium of claim 16, the one or more programs including instructions for: in response to detecting the first input, displaying, via the touch-sensitive display, the second image without displaying other images of the plurality of still images.
  • 36. The method of claim 17, wherein the method further comprises: while displaying the first image of the plurality of still images, detecting a second input at a location on the touch-sensitive display corresponding to the first image; andin response to detecting the second input, displaying, via the touch-sensitive display, a third image of the plurality of still images corresponding to the second image data.
  • 37. The method of claim 36, wherein displaying the third image includes selecting the third image from the plurality of still images based on one or more properties of the second input, and wherein the one or more properties include a characteristic intensity of the second input.
  • 38. The method of claim 37, further comprising: in accordance with a determination that the characteristic intensity of the second input is greater than a threshold intensity, maintaining display of the third image after the second input ceases to be detected by the device; andin accordance with a determination that the characteristic intensity of the second input is less than the threshold intensity, displaying the first image after the second input ceases to be detected by the device.
  • 39. The method of claim 38, wherein the threshold intensity is based at least in part on a focal plane of an object being captured in the plurality of still images.
  • 40. The method of claim 38, further comprising: in accordance with the determination that the characteristic intensity of the second input is greater than the threshold intensity, providing feedback indicating the threshold intensity is exceeded.
  • 41. The method of claim 36, wherein the one or more properties of the second input include a duration of the second input.
  • 42. The method of claim 36, wherein the one or more properties of the second input includes the location of the second input on the touch-sensitive display, and wherein the method further comprises: identifying a respective object in the first image corresponding to the location of the second input, wherein the respective object is associated with a respective focal plane; anddisplaying an image of the plurality of still images captured with the respective focal plane.
  • 43. The method of claim 36, wherein the second image is a composite image that includes a portion of the first image data and a portion of the second image data.
  • 44. The method of claim 17, wherein at least one photographic property of the camera other than the focal plane is maintained during the capture of the plurality of still images.
  • 45. The method of claim 17, wherein detecting the activation of the shutter button includes detecting an input corresponding to activation of the shutter button on the touch-sensitive display, and wherein the method further comprises: in response to detecting the input corresponding to activation of the shutter button: selecting a respective image of the plurality of still images based on one or more properties of the input corresponding to activation of the shutter button; anddisplaying, via the touch-sensitive display, the respective image of the plurality of still images.
  • 46. The method of claim 45, wherein the one or more properties of the input corresponding to activation of the shutter button include a characteristic intensity of the input.
  • 47. The method of claim 45, wherein the one or more properties of the input corresponding to activation of the shutter button includes a location of the input on the touch-sensitive display.
  • 48. The method of claim 17, wherein the method further comprises: after displaying the first image of the plurality of still images, displaying another image of the plurality of still images a predetermined time after displaying the first image, wherein the first image and the another image were captured with different focal planes.
  • 49. The method of claim 17, further comprising: determining depth information of a scene captured in the plurality of still images with the plurality of different focal planes, wherein the depth information is determined based on image data of the plurality of still images.
  • 50. The method of claim 17, wherein the method further comprises: after capturing the plurality of still images, displaying, via the touch-sensitive display, the first image of the plurality of still images corresponding to the first image data without displaying other images of the plurality of still images.
  • 51. The method of claim 17, further comprising: in response to detecting the first input, displaying, via the touch-sensitive display, the second image without displaying other images of the plurality of still images.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/528,941, filed Aug. 1, 2019, entitled “CAPTURING AND DISPLAYING IMAGES WITH MULTIPLE FOCAL PLANES”, which claims priority to U.S. Provisional Application No. 62/739,093, filed Sep. 28, 2018, entitled “CAPTURING AND DISPLAYING IMAGES WITH MULTIPLE FOCAL PLANES”, the contents of which are hereby incorporated by reference in their entireties.

US Referenced Citations (1093)
Number Name Date Kind
4518237 Mizokami May 1985 A
4933702 Komatsuzaki et al. Jun 1990 A
5463443 Tanaka et al. Oct 1995 A
5557358 Mukai et al. Sep 1996 A
5615384 Allard et al. Mar 1997 A
5617526 Oran et al. Apr 1997 A
5825353 Will Oct 1998 A
6262769 Anderson et al. Jul 2001 B1
6268864 Chen et al. Jul 2001 B1
6278466 Chen Aug 2001 B1
6359837 Tsukamoto Mar 2002 B1
6429896 Aruga et al. Aug 2002 B1
6483878 Yonezawa et al. Nov 2002 B1
6522347 Sakai et al. Feb 2003 B1
6621524 Iijima et al. Sep 2003 B1
6677981 Mancuso et al. Jan 2004 B1
6726094 Rantze et al. Apr 2004 B1
6728784 Mattaway Apr 2004 B1
6731308 Tang et al. May 2004 B1
6809724 Shiraishi et al. Oct 2004 B1
6809759 Chiang Oct 2004 B1
6819867 Mayer et al. Nov 2004 B2
6900840 Schinner et al. May 2005 B1
7185054 Ludwig et al. Feb 2007 B1
7463304 Murray Dec 2008 B2
7515178 Fleischman et al. Apr 2009 B1
7571014 Lambourne et al. Aug 2009 B1
7583892 Okumura Sep 2009 B2
7801971 Amidon et al. Sep 2010 B1
7903171 Takabatake et al. Mar 2011 B2
8169463 Enstad et al. May 2012 B2
8185839 Jalon et al. May 2012 B2
8189087 Misawa et al. May 2012 B2
8203640 Kim et al. Jun 2012 B2
8274544 Kurtz et al. Sep 2012 B2
8295546 Craig et al. Oct 2012 B2
8350945 Yumiki Jan 2013 B2
8370448 Galchev Feb 2013 B2
8390628 Harding et al. Mar 2013 B2
8405680 Gomes et al. Mar 2013 B1
8423089 Song et al. Apr 2013 B2
8493408 Williamson et al. Jul 2013 B2
8576304 Ishibashi Nov 2013 B2
8624836 Miller et al. Jan 2014 B1
8638371 Laberge et al. Jan 2014 B2
8675084 Bolton et al. Mar 2014 B2
8723988 Thorn May 2014 B2
8736704 Jasinski et al. May 2014 B2
8736716 Prentice May 2014 B2
8742890 Gocho et al. Jun 2014 B2
8762895 Mehta et al. Jun 2014 B2
8817158 Saito Aug 2014 B2
8848097 Makii Sep 2014 B2
8885978 Cote et al. Nov 2014 B2
8896652 Ralston Nov 2014 B2
8914752 Spiegel Dec 2014 B1
9001226 Ng et al. Apr 2015 B1
9094576 Karakotsios Jul 2015 B1
9153031 El-Saban et al. Oct 2015 B2
9158974 Laska et al. Oct 2015 B1
9172866 Ito et al. Oct 2015 B2
9185062 Yang et al. Nov 2015 B1
9185291 Shabtay et al. Nov 2015 B1
9207837 Paretti et al. Dec 2015 B2
9223486 Shin et al. Dec 2015 B2
9230241 Singh et al. Jan 2016 B1
9230355 Ahuja et al. Jan 2016 B1
9245177 Perez Jan 2016 B2
9246961 Walkin et al. Jan 2016 B2
9250797 Roberts et al. Feb 2016 B2
9253531 Relyea et al. Feb 2016 B2
9264660 Petterson et al. Feb 2016 B1
9288476 Sandrew et al. Mar 2016 B2
9298263 Geisner et al. Mar 2016 B2
9313397 Harris et al. Apr 2016 B2
9313401 Frey et al. Apr 2016 B2
9325970 Sakayori Apr 2016 B2
9342230 Bastien et al. May 2016 B2
9349414 Furment et al. May 2016 B1
9360671 Zhou Jun 2016 B1
9380264 Vakalapudi Jun 2016 B1
9423868 Iwasaki Aug 2016 B2
9448708 Bennett et al. Sep 2016 B1
9451144 Dye Sep 2016 B2
9462017 Siracusano, Jr. Oct 2016 B1
9467812 Jung et al. Oct 2016 B2
9544563 Cheng et al. Jan 2017 B1
9592428 Binder Mar 2017 B2
9600178 Yun et al. Mar 2017 B2
9602559 Barros et al. Mar 2017 B1
9609221 Kim et al. Mar 2017 B2
9626589 Graham et al. Apr 2017 B1
9628416 Henderson Apr 2017 B2
9635314 Barkley et al. Apr 2017 B2
9667881 Harris et al. May 2017 B2
9686497 Terry Jun 2017 B1
9704250 Gilmour et al. Jul 2017 B1
9716825 Manzari et al. Jul 2017 B1
9747504 Ma et al. Aug 2017 B2
9749543 Kim et al. Aug 2017 B2
9760976 Kameyama Sep 2017 B2
9767613 Bedikian et al. Sep 2017 B1
9800951 Carlson et al. Oct 2017 B1
9819877 Faulkner et al. Nov 2017 B1
9819912 Maruta Nov 2017 B2
9942463 Kuo et al. Apr 2018 B2
9948589 Gonnen et al. Apr 2018 B2
9973674 Dye et al. May 2018 B2
10015298 Yang et al. Jul 2018 B2
10021294 Kwon et al. Jul 2018 B2
10055887 Gil et al. Aug 2018 B1
10091411 Ha et al. Oct 2018 B2
10095385 Walkin et al. Oct 2018 B2
10139218 Matsushita Nov 2018 B2
10152222 Ozawa et al. Dec 2018 B2
10176622 Waggoner et al. Jan 2019 B1
10187587 Hasinoff et al. Jan 2019 B2
10194189 Goetz et al. Jan 2019 B1
10225463 Yun et al. Mar 2019 B2
10230901 Harris et al. Mar 2019 B2
10270983 Van Os et al. Apr 2019 B1
10284812 Van Os et al. May 2019 B1
10289265 Kulkarni May 2019 B2
10297034 Nash et al. May 2019 B2
10304231 Saito May 2019 B2
10313652 Falstrup et al. Jun 2019 B1
10325417 Scapel et al. Jun 2019 B1
10326942 Shabtay et al. Jun 2019 B2
10345592 Samec et al. Jul 2019 B2
10353532 Holz et al. Jul 2019 B1
10362272 Van Os et al. Jul 2019 B1
10375313 Van Os et al. Aug 2019 B1
10379719 Scapel et al. Aug 2019 B2
10389977 Van Os et al. Aug 2019 B1
10397469 Yan et al. Aug 2019 B1
10397500 Xu et al. Aug 2019 B1
10410426 Kamini et al. Sep 2019 B2
10447908 Lee et al. Oct 2019 B2
10467729 Perera et al. Nov 2019 B1
10467775 Waggoner et al. Nov 2019 B1
10521091 Anzures et al. Dec 2019 B2
10521948 Rickwald et al. Dec 2019 B2
10523625 Allen et al. Dec 2019 B1
10523879 Dye et al. Dec 2019 B2
10523976 Hemmati et al. Dec 2019 B2
10574895 Lee et al. Feb 2020 B2
10585551 Lee et al. Mar 2020 B2
10614139 Fujioka et al. Apr 2020 B2
10638058 Matsunaga Apr 2020 B2
10645294 Manzari et al. May 2020 B1
10652470 Manzari et al. May 2020 B1
10657695 Chand et al. May 2020 B2
10659405 Chang et al. May 2020 B1
10674072 Manzari et al. Jun 2020 B1
10681282 Manzari et al. Jun 2020 B1
10698575 Walkin et al. Jun 2020 B2
10735642 Manzari et al. Aug 2020 B1
10735643 Manzari et al. Aug 2020 B1
10771741 Reynolds et al. Sep 2020 B1
10791273 Manzari et al. Sep 2020 B1
10798035 Lewis et al. Oct 2020 B2
10845968 Scapel et al. Nov 2020 B2
10855910 Tano et al. Dec 2020 B2
10902661 Mourkogiannis et al. Jan 2021 B1
10909586 Avedissian et al. Feb 2021 B2
10924446 Paul Feb 2021 B1
10958850 Kwak et al. Mar 2021 B2
10963145 Voss et al. Mar 2021 B1
10972655 Ostap et al. Apr 2021 B1
11039074 Manzari et al. Jun 2021 B1
11054973 Manzari et al. Jul 2021 B1
11079913 Kim et al. Aug 2021 B1
11120528 Seely et al. Sep 2021 B1
11212449 Manzari et al. Dec 2021 B1
11258619 Libin Feb 2022 B2
11321857 Stauber et al. May 2022 B2
11350026 Manzari et al. May 2022 B1
11360634 Chang et al. Jun 2022 B1
11418699 Manzari et al. Aug 2022 B1
11449188 Chang et al. Sep 2022 B1
11468625 Manzari et al. Oct 2022 B2
11539876 Manzari et al. Dec 2022 B2
20010030597 Inoue et al. Oct 2001 A1
20010041007 Aoki Nov 2001 A1
20020070945 Kage Jun 2002 A1
20020101446 Tang et al. Aug 2002 A1
20020140803 Gutta et al. Oct 2002 A1
20020167604 Ban et al. Nov 2002 A1
20020171737 Tullis et al. Nov 2002 A1
20030025802 Mayer, Jr. et al. Feb 2003 A1
20030107664 Suzuki Jun 2003 A1
20030112938 Kanakubo et al. Jun 2003 A1
20030122930 Schofield et al. Jul 2003 A1
20030160756 Numano Aug 2003 A1
20030160861 Barlow et al. Aug 2003 A1
20030174216 Iguchi et al. Sep 2003 A1
20030184587 Ording et al. Oct 2003 A1
20030225836 Lee et al. Dec 2003 A1
20040003040 Beavers et al. Jan 2004 A1
20040041924 White et al. Mar 2004 A1
20040061796 Honda et al. Apr 2004 A1
20040090469 Moon et al. May 2004 A1
20040095473 Park May 2004 A1
20040189861 Tom et al. Sep 2004 A1
20040201699 Parulski et al. Oct 2004 A1
20040239763 Notea et al. Dec 2004 A1
20050015286 Rudnik et al. Jan 2005 A1
20050024517 Luciano Feb 2005 A1
20050099492 Orr May 2005 A1
20050124365 Balasuriya et al. Jun 2005 A1
20050134695 Deshpande et al. Jun 2005 A1
20050144247 Christensen et al. Jun 2005 A1
20050189419 Igarashi et al. Sep 2005 A1
20050206981 Hung Sep 2005 A1
20050210380 Kramer et al. Sep 2005 A1
20050210403 Satanek Sep 2005 A1
20050237383 Soga et al. Oct 2005 A1
20050248660 Stavely et al. Nov 2005 A1
20050270397 Battles Dec 2005 A1
20060002315 Theurer et al. Jan 2006 A1
20060002523 Bettis et al. Jan 2006 A1
20060026521 Hotelling et al. Feb 2006 A1
20060033831 Ejima et al. Feb 2006 A1
20060098085 Nichols et al. May 2006 A1
20060098634 Umemoto et al. May 2006 A1
20060132482 Oh et al. Jun 2006 A1
20060158730 Kira Jul 2006 A1
20060170781 Sobol Aug 2006 A1
20060187322 Janson et al. Aug 2006 A1
20060209067 Pellacini et al. Sep 2006 A1
20060228040 Simon et al. Oct 2006 A1
20060233192 Mihara Oct 2006 A1
20060275025 Labaziewicz et al. Dec 2006 A1
20070004389 Wallace et al. Jan 2007 A1
20070024614 Tam et al. Feb 2007 A1
20070025711 Marcus et al. Feb 2007 A1
20070025714 Shiraki Feb 2007 A1
20070025723 Baudisch et al. Feb 2007 A1
20070031062 Pal et al. Feb 2007 A1
20070040810 Dowe et al. Feb 2007 A1
20070097088 Battles May 2007 A1
20070101355 Chung et al. May 2007 A1
20070109417 Hyttfors et al. May 2007 A1
20070113099 Takikawa et al. May 2007 A1
20070124783 Ahiska et al. May 2007 A1
20070140675 Yanagi et al. Jun 2007 A1
20070146503 Shiraki Jun 2007 A1
20070153112 Ueda et al. Jul 2007 A1
20070165103 Arima et al. Jul 2007 A1
20070195350 Hattori Aug 2007 A1
20070222789 Yoshio et al. Sep 2007 A1
20070228259 Hohenberger Oct 2007 A1
20070254640 Bliss Nov 2007 A1
20070257992 Kato Nov 2007 A1
20070273769 Takahashi Nov 2007 A1
20070291152 Suekane et al. Dec 2007 A1
20080030592 Border et al. Feb 2008 A1
20080084484 Ochi et al. Apr 2008 A1
20080106601 Matsuda May 2008 A1
20080122796 Jobs et al. May 2008 A1
20080129759 Jeon et al. Jun 2008 A1
20080129825 Deangelis et al. Jun 2008 A1
20080131019 Ng Jun 2008 A1
20080143840 Corkum et al. Jun 2008 A1
20080192020 Kang et al. Aug 2008 A1
20080218611 Parulski et al. Sep 2008 A1
20080222558 Cho et al. Sep 2008 A1
20080284855 Umeyama et al. Nov 2008 A1
20080297587 Kurtz et al. Dec 2008 A1
20080298571 Kurtz et al. Dec 2008 A1
20080309811 Fujinawa et al. Dec 2008 A1
20080313278 Hochberg Dec 2008 A1
20090009612 Tico et al. Jan 2009 A1
20090021576 Linder et al. Jan 2009 A1
20090021600 Watanabe Jan 2009 A1
20090022422 Sorek et al. Jan 2009 A1
20090027515 Maruyama et al. Jan 2009 A1
20090027539 Kunou Jan 2009 A1
20090040332 Yoshino et al. Feb 2009 A1
20090046075 Kim et al. Feb 2009 A1
20090046097 Franklin Feb 2009 A1
20090051783 Kim et al. Feb 2009 A1
20090066817 Sakamaki Mar 2009 A1
20090073285 Terashima Mar 2009 A1
20090077460 Li et al. Mar 2009 A1
20090102918 Sakamoto et al. Apr 2009 A1
20090102933 Harris et al. Apr 2009 A1
20090109316 Matsui Apr 2009 A1
20090117936 Maeng May 2009 A1
20090144639 Nims et al. Jun 2009 A1
20090164587 Gavita et al. Jun 2009 A1
20090167671 Kerofsky Jul 2009 A1
20090167672 Kerofsky Jul 2009 A1
20090174763 Bengtsson et al. Jul 2009 A1
20090175511 Lee et al. Jul 2009 A1
20090244318 Makii Oct 2009 A1
20090249244 Robinson et al. Oct 2009 A1
20090251484 Zhao et al. Oct 2009 A1
20090256780 Small et al. Oct 2009 A1
20090262206 Park Oct 2009 A1
20090263044 Imagawa et al. Oct 2009 A1
20090276700 Anderson et al. Nov 2009 A1
20090287790 Upton et al. Nov 2009 A1
20090309897 Morita et al. Dec 2009 A1
20090315671 Gocho et al. Dec 2009 A1
20090319897 Kotler et al. Dec 2009 A1
20090322901 Subbotin et al. Dec 2009 A1
20100011065 Scherpa et al. Jan 2010 A1
20100020221 Tupman et al. Jan 2010 A1
20100020222 Jones et al. Jan 2010 A1
20100033615 Mori Feb 2010 A1
20100039498 Liu et al. Feb 2010 A1
20100039522 Huang Feb 2010 A1
20100042926 Bull et al. Feb 2010 A1
20100066853 Aoki et al. Mar 2010 A1
20100066889 Ueda et al. Mar 2010 A1
20100066890 Ueda et al. Mar 2010 A1
20100066895 Ueda et al. Mar 2010 A1
20100085416 Hegde et al. Apr 2010 A1
20100093400 Ju et al. Apr 2010 A1
20100097322 Hu et al. Apr 2010 A1
20100097438 Ujii Apr 2010 A1
20100121636 Burke et al. May 2010 A1
20100123737 Williamson et al. May 2010 A1
20100124941 Cho May 2010 A1
20100153847 Fama Jun 2010 A1
20100162160 Stallings et al. Jun 2010 A1
20100162171 Felt et al. Jun 2010 A1
20100164893 Shin et al. Jul 2010 A1
20100169435 Osullivan et al. Jul 2010 A1
20100188426 Ohmori et al. Jul 2010 A1
20100194931 Kawaguchi et al. Aug 2010 A1
20100208122 Yumiki Aug 2010 A1
20100231735 Burian et al. Sep 2010 A1
20100231777 Shintani et al. Sep 2010 A1
20100232703 Aiso Sep 2010 A1
20100232704 Thorn Sep 2010 A1
20100238327 Griffith et al. Sep 2010 A1
20100247077 Yamamoto et al. Sep 2010 A1
20100251119 Geppert et al. Sep 2010 A1
20100251158 Geppert et al. Sep 2010 A1
20100259645 Kaplan et al. Oct 2010 A1
20100277470 Margolis Nov 2010 A1
20100283743 Coddington Nov 2010 A1
20100289825 Shin et al. Nov 2010 A1
20100289910 Kamshilin et al. Nov 2010 A1
20100302280 Szeliski et al. Dec 2010 A1
20100317410 Song et al. Dec 2010 A1
20100318928 Neuman et al. Dec 2010 A1
20100318939 Moon Dec 2010 A1
20110008033 Ichimiya et al. Jan 2011 A1
20110013049 Thörn Jan 2011 A1
20110018970 Wakabayashi Jan 2011 A1
20110019058 Sakai et al. Jan 2011 A1
20110058052 Bolton et al. Mar 2011 A1
20110072394 Victor et al. Mar 2011 A1
20110074710 Weeldreyer et al. Mar 2011 A1
20110074830 Rapp et al. Mar 2011 A1
20110085016 Kristiansen et al. Apr 2011 A1
20110085017 Robinson et al. Apr 2011 A1
20110109581 Ozawa et al. May 2011 A1
20110115875 Sadwick et al. May 2011 A1
20110115932 Shin et al. May 2011 A1
20110126148 Krishnaraj et al. May 2011 A1
20110138332 Miyagawa Jun 2011 A1
20110157379 Kimura Jun 2011 A1
20110161836 Mu et al. Jun 2011 A1
20110176039 Lo Jul 2011 A1
20110187879 Ochiai Aug 2011 A1
20110193995 Goh et al. Aug 2011 A1
20110199495 Laberge et al. Aug 2011 A1
20110221755 Geisner et al. Sep 2011 A1
20110234853 Hayashi et al. Sep 2011 A1
20110242369 Misawa et al. Oct 2011 A1
20110249073 Cranfill et al. Oct 2011 A1
20110249078 Abuan et al. Oct 2011 A1
20110249086 Guo et al. Oct 2011 A1
20110252146 Santamaria et al. Oct 2011 A1
20110273526 Mehin et al. Nov 2011 A1
20110296163 Abernethy et al. Dec 2011 A1
20110304632 Evertt et al. Dec 2011 A1
20120002001 Prentice Jan 2012 A1
20120002898 Côté et al. Jan 2012 A1
20120011456 Noda et al. Jan 2012 A1
20120019551 Pettigrew et al. Jan 2012 A1
20120019610 Hornyak et al. Jan 2012 A1
20120026378 Pang et al. Feb 2012 A1
20120033028 Murphy et al. Feb 2012 A1
20120036480 Warner et al. Feb 2012 A1
20120054278 Taleb et al. Mar 2012 A1
20120056830 Suzuki et al. Mar 2012 A1
20120056997 Jang Mar 2012 A1
20120057064 Gardiner et al. Mar 2012 A1
20120062784 Van et al. Mar 2012 A1
20120069028 Bouguerra Mar 2012 A1
20120069206 Hsieh Mar 2012 A1
20120079378 Goossens Mar 2012 A1
20120092436 Pahud et al. Apr 2012 A1
20120105579 Jeon et al. May 2012 A1
20120114108 Katis et al. May 2012 A1
20120120277 Tsai et al. May 2012 A1
20120127189 Park et al. May 2012 A1
20120127346 Sato et al. May 2012 A1
20120133797 Sato et al. May 2012 A1
20120162242 Amano et al. Jun 2012 A1
20120169776 Rissa et al. Jul 2012 A1
20120173383 Badawiyeh et al. Jul 2012 A1
20120185355 Kilroy Jul 2012 A1
20120188394 Park et al. Jul 2012 A1
20120194559 Lim Aug 2012 A1
20120206452 Geisner et al. Aug 2012 A1
20120206495 Endo et al. Aug 2012 A1
20120206619 Nitta et al. Aug 2012 A1
20120206621 Chen et al. Aug 2012 A1
20120235990 Yamaji Sep 2012 A1
20120243802 Fintel et al. Sep 2012 A1
20120249853 Krolczyk et al. Oct 2012 A1
20120274830 Kameyama et al. Nov 2012 A1
20120293605 Seferian et al. Nov 2012 A1
20120293611 Lee Nov 2012 A1
20120296972 Backer Nov 2012 A1
20120304079 Rideout et al. Nov 2012 A1
20120309520 Evertt et al. Dec 2012 A1
20120320141 Bowen et al. Dec 2012 A1
20130009858 Lacey Jan 2013 A1
20130010170 Matsuzawa et al. Jan 2013 A1
20130038546 Mineo Feb 2013 A1
20130038771 Brunner et al. Feb 2013 A1
20130055113 Chazin et al. Feb 2013 A1
20130055119 Luong Feb 2013 A1
20130057472 Dizac et al. Mar 2013 A1
20130061155 Hon Mar 2013 A1
20130076908 Bratton et al. Mar 2013 A1
20130083222 Matsuzawa et al. Apr 2013 A1
20130088413 Raffle et al. Apr 2013 A1
20130088614 Lee Apr 2013 A1
20130091298 Ozzie et al. Apr 2013 A1
20130093904 Wagner et al. Apr 2013 A1
20130101164 Leclerc et al. Apr 2013 A1
20130109425 Kerger et al. May 2013 A1
20130132865 Li May 2013 A1
20130135315 Bares et al. May 2013 A1
20130141362 Asanuma et al. Jun 2013 A1
20130141513 Setton et al. Jun 2013 A1
20130141524 Karunamuni et al. Jun 2013 A1
20130147933 Kulas et al. Jun 2013 A1
20130155308 Wu et al. Jun 2013 A1
20130155474 Roach et al. Jun 2013 A1
20130159900 Pendharkar Jun 2013 A1
20130162781 Hubner et al. Jun 2013 A1
20130165186 Choi Jun 2013 A1
20130166580 Maharajh et al. Jun 2013 A1
20130169742 Wu et al. Jul 2013 A1
20130179831 Izaki Jul 2013 A1
20130194378 Brown Aug 2013 A1
20130201104 Ptucha et al. Aug 2013 A1
20130201203 Warner Aug 2013 A1
20130201307 Schloter et al. Aug 2013 A1
20130208136 Takatsuka et al. Aug 2013 A1
20130210563 Hollinger Aug 2013 A1
20130216206 Dubin et al. Aug 2013 A1
20130219276 Shan Aug 2013 A1
20130222663 Rydenhag et al. Aug 2013 A1
20130225140 Greisson Aug 2013 A1
20130239057 Ubillos et al. Sep 2013 A1
20130246948 Chen et al. Sep 2013 A1
20130265311 Na et al. Oct 2013 A1
20130265467 Matsuzawa et al. Oct 2013 A1
20130278576 Lee et al. Oct 2013 A1
20130282180 Layton Oct 2013 A1
20130286251 Wood et al. Oct 2013 A1
20130290905 Luvogt et al. Oct 2013 A1
20130328770 Parham Dec 2013 A1
20130329074 Zhang et al. Dec 2013 A1
20130336545 Pritikin et al. Dec 2013 A1
20130346916 Williamson et al. Dec 2013 A1
20140007021 Akiyama et al. Jan 2014 A1
20140009639 Lee Jan 2014 A1
20140018053 Cho et al. Jan 2014 A1
20140022399 Rashid et al. Jan 2014 A1
20140026074 Cortes et al. Jan 2014 A1
20140028872 Lee et al. Jan 2014 A1
20140028885 Ma et al. Jan 2014 A1
20140033043 Kashima Jan 2014 A1
20140033100 Noda et al. Jan 2014 A1
20140037178 Park Feb 2014 A1
20140043368 Yu Feb 2014 A1
20140043424 Gava et al. Feb 2014 A1
20140043517 Yim et al. Feb 2014 A1
20140047389 Aarabi Feb 2014 A1
20140049536 Neuman et al. Feb 2014 A1
20140055554 Du et al. Feb 2014 A1
20140063175 Jafry et al. Mar 2014 A1
20140063176 Modai et al. Mar 2014 A1
20140063313 Choi et al. Mar 2014 A1
20140071061 Lin et al. Mar 2014 A1
20140071325 Kawahara et al. Mar 2014 A1
20140078371 Kinoshita Mar 2014 A1
20140092272 Choi Apr 2014 A1
20140095122 Appleman et al. Apr 2014 A1
20140099994 Bishop et al. Apr 2014 A1
20140104449 Masarik et al. Apr 2014 A1
20140105372 Nowack et al. Apr 2014 A1
20140108084 Bargetzi et al. Apr 2014 A1
20140108568 Lee Apr 2014 A1
20140108928 Mumick Apr 2014 A1
20140118560 Bala et al. May 2014 A1
20140118563 Mehta et al. May 2014 A1
20140123005 Forstall et al. May 2014 A1
20140132735 Lee et al. May 2014 A1
20140143678 Mistry et al. May 2014 A1
20140152886 Morgan-Mar et al. Jun 2014 A1
20140160231 Middleton et al. Jun 2014 A1
20140160304 Galor et al. Jun 2014 A1
20140176469 Lim Jun 2014 A1
20140176565 Adeyoola et al. Jun 2014 A1
20140184524 Schiefer et al. Jul 2014 A1
20140192212 He et al. Jul 2014 A1
20140192233 Kakkori et al. Jul 2014 A1
20140201126 Zadeh et al. Jul 2014 A1
20140204229 Leung et al. Jul 2014 A1
20140205207 Bhatt Jul 2014 A1
20140215356 Brander et al. Jul 2014 A1
20140215404 Kong et al. Jul 2014 A1
20140218371 Du et al. Aug 2014 A1
20140218461 Deland Aug 2014 A1
20140218599 Nakamura et al. Aug 2014 A1
20140229831 Chordia et al. Aug 2014 A1
20140229835 Ravine Aug 2014 A1
20140232838 Jorgensen et al. Aug 2014 A1
20140240471 Srinivasa et al. Aug 2014 A1
20140240531 Nakai et al. Aug 2014 A1
20140240577 Masugi Aug 2014 A1
20140247368 Chinn Sep 2014 A1
20140267126 Åberg et al. Sep 2014 A1
20140267867 Lee et al. Sep 2014 A1
20140280812 Bealkowski et al. Sep 2014 A1
20140281983 Xian et al. Sep 2014 A1
20140282223 Bastien et al. Sep 2014 A1
20140285698 Geiss Sep 2014 A1
20140300635 Suzuki Oct 2014 A1
20140300722 Garcia Oct 2014 A1
20140300779 Yeo et al. Oct 2014 A1
20140310598 Sprague et al. Oct 2014 A1
20140327639 Papakipos et al. Nov 2014 A1
20140331149 Labey Nov 2014 A1
20140333671 Phang et al. Nov 2014 A1
20140333824 Xiu Nov 2014 A1
20140349754 Kaneoka et al. Nov 2014 A1
20140351753 Shin et al. Nov 2014 A1
20140354759 Cranfill et al. Dec 2014 A1
20140354845 Mølgaard et al. Dec 2014 A1
20140359438 Matsuki Dec 2014 A1
20140362091 Bouaziz et al. Dec 2014 A1
20140362274 Christie et al. Dec 2014 A1
20140364228 Rimon Dec 2014 A1
20140368601 Decharms Dec 2014 A1
20140368719 Kaneko et al. Dec 2014 A1
20140372856 Radakovitz et al. Dec 2014 A1
20140373081 Dodson et al. Dec 2014 A1
20140375747 Martinez et al. Dec 2014 A1
20150022649 Koppal Jan 2015 A1
20150022674 Koss et al. Jan 2015 A1
20150033149 Kuchoor Jan 2015 A1
20150033192 Bohannon et al. Jan 2015 A1
20150035825 Zhou et al. Feb 2015 A1
20150042852 Lee et al. Feb 2015 A1
20150043806 Sunkavalli et al. Feb 2015 A1
20150049233 Choi Feb 2015 A1
20150058413 Ge Feb 2015 A1
20150058754 Rauh Feb 2015 A1
20150067513 Zambetti et al. Mar 2015 A1
20150067541 Owens et al. Mar 2015 A1
20150070362 Hirai Mar 2015 A1
20150078621 Choi et al. Mar 2015 A1
20150078680 Shakib et al. Mar 2015 A1
20150078726 Shakib et al. Mar 2015 A1
20150085174 Shabtay et al. Mar 2015 A1
20150092077 Feder et al. Apr 2015 A1
20150095804 Grossman et al. Apr 2015 A1
20150106720 Backer Apr 2015 A1
20150109417 Zirnheld Apr 2015 A1
20150116353 Miura Apr 2015 A1
20150116448 Gottlieb Apr 2015 A1
20150116542 Lee Apr 2015 A1
20150135109 Zambetti et al. May 2015 A1
20150135234 Hall May 2015 A1
20150138079 Lannsjö May 2015 A1
20150145950 Murphy et al. May 2015 A1
20150146079 Kim May 2015 A1
20150149927 Walkin et al. May 2015 A1
20150150141 Szymanski et al. May 2015 A1
20150154448 Murayama et al. Jun 2015 A1
20150172534 Miyakawa et al. Jun 2015 A1
20150177914 Coyner et al. Jun 2015 A1
20150181135 Shimosato Jun 2015 A1
20150189138 Xie et al. Jul 2015 A1
20150189162 Kuo et al. Jul 2015 A1
20150193196 Lin et al. Jul 2015 A1
20150194186 Lee et al. Jul 2015 A1
20150208001 Nonaka et al. Jul 2015 A1
20150212723 Lim et al. Jul 2015 A1
20150213001 Levy et al. Jul 2015 A1
20150213604 Li et al. Jul 2015 A1
20150220249 Snibbe et al. Aug 2015 A1
20150248198 Somlai-Fisher et al. Sep 2015 A1
20150248583 Sekine et al. Sep 2015 A1
20150249775 Jacumet Sep 2015 A1
20150249785 Mehta et al. Sep 2015 A1
20150254855 Patankar et al. Sep 2015 A1
20150256749 Frey et al. Sep 2015 A1
20150256796 Ma Sep 2015 A1
20150264202 Pawlowski Sep 2015 A1
20150264304 Chastney et al. Sep 2015 A1
20150271389 Huang et al. Sep 2015 A1
20150277686 Laforge et al. Oct 2015 A1
20150286724 Knaapen et al. Oct 2015 A1
20150288868 Slavin et al. Oct 2015 A1
20150289104 Jung et al. Oct 2015 A1
20150296077 Wakeyama et al. Oct 2015 A1
20150297185 Mccormack et al. Oct 2015 A1
20150301338 Van Heugten Oct 2015 A1
20150301731 Okamoto et al. Oct 2015 A1
20150304366 Bader-Natal et al. Oct 2015 A1
20150304413 Park Oct 2015 A1
20150310583 Hume et al. Oct 2015 A1
20150312182 Langholz Oct 2015 A1
20150312184 Langholz et al. Oct 2015 A1
20150312185 Langholz et al. Oct 2015 A1
20150319006 Plummer et al. Nov 2015 A1
20150319144 Barton et al. Nov 2015 A1
20150334075 Wang et al. Nov 2015 A1
20150334140 Singh et al. Nov 2015 A1
20150334291 Cho et al. Nov 2015 A1
20150341536 Huang et al. Nov 2015 A1
20150347824 Saari et al. Dec 2015 A1
20150350141 Yang et al. Dec 2015 A1
20150350143 Lemay et al. Dec 2015 A1
20150350533 Harris et al. Dec 2015 A1
20150350535 Voss Dec 2015 A1
20150358484 Permude Dec 2015 A1
20150358584 Mattson Dec 2015 A1
20150362998 Park et al. Dec 2015 A1
20150365587 Ha et al. Dec 2015 A1
20150370426 Carrigan et al. Dec 2015 A1
20150370458 Chen Dec 2015 A1
20150373065 Holmquist et al. Dec 2015 A1
20160012567 Siddiqui et al. Jan 2016 A1
20160014059 Rathod Jan 2016 A1
20160014477 Siders Jan 2016 A1
20160026371 Lu et al. Jan 2016 A1
20160029004 Campbell Jan 2016 A1
20160044236 Matsuzawa et al. Feb 2016 A1
20160048598 Fujioka et al. Feb 2016 A1
20160048599 Fujioka et al. Feb 2016 A1
20160048725 Holz et al. Feb 2016 A1
20160048903 Fujioka et al. Feb 2016 A1
20160050169 Ben Atar et al. Feb 2016 A1
20160050351 Lee et al. Feb 2016 A1
20160050446 Fujioka et al. Feb 2016 A1
20160057173 Singman et al. Feb 2016 A1
20160065832 Kim Mar 2016 A1
20160065861 Steinberg et al. Mar 2016 A1
20160065930 Chandra et al. Mar 2016 A1
20160072861 Woolsey et al. Mar 2016 A1
20160073185 Kannappan et al. Mar 2016 A1
20160077725 Maeda Mar 2016 A1
20160080639 Choi et al. Mar 2016 A1
20160080657 Chuang et al. Mar 2016 A1
20160088280 Sadi et al. Mar 2016 A1
20160092035 Crocker et al. Mar 2016 A1
20160098094 Minkkinen Apr 2016 A1
20160099901 Allen et al. Apr 2016 A1
20160099987 Shamma Apr 2016 A1
20160117829 Yoon et al. Apr 2016 A1
20160127636 Ito et al. May 2016 A1
20160127638 Guo et al. May 2016 A1
20160132200 Walkin et al. May 2016 A1
20160132201 Shaw et al. May 2016 A1
20160139785 Griffin et al. May 2016 A1
20160142450 Paul et al. May 2016 A1
20160142649 Yim May 2016 A1
20160148384 Bud et al. May 2016 A1
20160162039 Eilat et al. Jun 2016 A1
20160163084 Corazza et al. Jun 2016 A1
20160173869 Srikanth et al. Jun 2016 A1
20160180259 Marianko et al. Jun 2016 A1
20160188181 Smith Jun 2016 A1
20160210602 Siddique et al. Jul 2016 A1
20160212319 Harris et al. Jul 2016 A1
20160212374 Usbergo et al. Jul 2016 A1
20160217601 Tsuda et al. Jul 2016 A1
20160219217 Williams et al. Jul 2016 A1
20160225175 Kim et al. Aug 2016 A1
20160226926 Singh et al. Aug 2016 A1
20160227016 Kim et al. Aug 2016 A1
20160227095 Yoshizawa et al. Aug 2016 A1
20160227121 Matsushita Aug 2016 A1
20160231902 Sirpal et al. Aug 2016 A1
20160241777 Rav-Acha et al. Aug 2016 A1
20160241793 Shanmugavadivelu et al. Aug 2016 A1
20160247288 Omori et al. Aug 2016 A1
20160247309 Li et al. Aug 2016 A1
20160255268 Kang et al. Sep 2016 A1
20160259413 Anzures et al. Sep 2016 A1
20160259497 Bauer et al. Sep 2016 A1
20160259498 Foss et al. Sep 2016 A1
20160259499 Kocienda 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
20160267067 Mays et al. Sep 2016 A1
20160277708 Rintel et al. Sep 2016 A1
20160277903 Poosala et al. Sep 2016 A1
20160283097 Voss et al. Sep 2016 A1
20160284123 Hare et al. Sep 2016 A1
20160306422 Parham et al. Oct 2016 A1
20160306504 Brunsch et al. Oct 2016 A1
20160307324 Higuchi et al. Oct 2016 A1
20160308920 Brunsch et al. Oct 2016 A1
20160316038 Jolfaei Oct 2016 A1
20160316147 Bernstein et al. Oct 2016 A1
20160320849 Koo Nov 2016 A1
20160335041 Wachter et al. Nov 2016 A1
20160337570 Tan et al. Nov 2016 A1
20160337582 Shimauchi et al. Nov 2016 A1
20160352661 Yang et al. Dec 2016 A1
20160353030 Tang et al. Dec 2016 A1
20160357353 Miura et al. Dec 2016 A1
20160357387 Bovet et al. Dec 2016 A1
20160360097 Penha et al. Dec 2016 A1
20160360116 Penha et al. Dec 2016 A1
20160364106 Koum et al. Dec 2016 A1
20160366323 Chen et al. Dec 2016 A1
20160366344 Pan et al. Dec 2016 A1
20160370974 Stenneth Dec 2016 A1
20160373631 Titi et al. Dec 2016 A1
20160373650 Kim et al. Dec 2016 A1
20160380780 Stephenson et al. Dec 2016 A1
20170006162 Bargetzi et al. Jan 2017 A1
20170006210 Dye et al. Jan 2017 A1
20170011773 Lee Jan 2017 A1
20170013179 Kang et al. Jan 2017 A1
20170018289 Morgenstern Jan 2017 A1
20170019604 Kim et al. Jan 2017 A1
20170024100 Pieper et al. Jan 2017 A1
20170024872 Olsson et al. Jan 2017 A1
20170026565 Hong et al. Jan 2017 A1
20170031557 Xiangli et al. Feb 2017 A1
20170034449 Eum et al. Feb 2017 A1
20170034583 Long et al. Feb 2017 A1
20170039686 Miura et al. Feb 2017 A1
20170041549 Kim et al. Feb 2017 A1
20170041677 Anderson et al. Feb 2017 A1
20170046065 Zeng et al. Feb 2017 A1
20170048450 Lee et al. Feb 2017 A1
20170048461 Lee et al. Feb 2017 A1
20170048494 Boyle et al. Feb 2017 A1
20170048817 Yang et al. Feb 2017 A1
20170054960 Chien et al. Feb 2017 A1
20170061635 Petrovich et al. Mar 2017 A1
20170064184 Tsai Mar 2017 A1
20170064200 Castillo et al. Mar 2017 A1
20170064205 Choi et al. Mar 2017 A1
20170083189 Yang et al. Mar 2017 A1
20170092329 Kim et al. Mar 2017 A1
20170094019 Ahmed et al. Mar 2017 A1
20170094161 Graham et al. Mar 2017 A1
20170097621 Ackmann et al. Apr 2017 A1
20170109912 Lee et al. Apr 2017 A1
20170111567 Pila Apr 2017 A1
20170111587 Herbst et al. Apr 2017 A1
20170111595 Soni et al. Apr 2017 A1
20170111616 Li et al. Apr 2017 A1
20170124664 Savenok et al. May 2017 A1
20170126592 El Ghoul May 2017 A1
20170139572 Sunkavalli et al. May 2017 A1
20170150904 Park et al. Jun 2017 A1
20170178287 Anderson Jun 2017 A1
20170180811 Quirino et al. Jun 2017 A1
20170186162 Mihic et al. Jun 2017 A1
20170206779 Lee et al. Jul 2017 A1
20170220212 Yang et al. Aug 2017 A1
20170230576 Sparks et al. Aug 2017 A1
20170230585 Nash et al. Aug 2017 A1
20170237888 Harris et al. Aug 2017 A1
20170243389 Wild et al. Aug 2017 A1
20170244896 Chien et al. Aug 2017 A1
20170244897 Jung et al. Aug 2017 A1
20170257559 Stricker Sep 2017 A1
20170257596 Murata et al. Sep 2017 A1
20170264817 Yan et al. Sep 2017 A1
20170272654 Poindexter, Jr. Sep 2017 A1
20170280494 Jung et al. Sep 2017 A1
20170285764 Kim et al. Oct 2017 A1
20170285916 Xu et al. Oct 2017 A1
20170287220 Khalid et al. Oct 2017 A1
20170302840 Hasinoff et al. Oct 2017 A1
20170309174 Gonzales et al. Oct 2017 A1
20170315772 Lee et al. Nov 2017 A1
20170324784 Taine et al. Nov 2017 A1
20170336926 Chaudhri et al. Nov 2017 A1
20170336928 Chaudhri et al. Nov 2017 A1
20170336960 Chaudhri et al. Nov 2017 A1
20170336961 Heo et al. Nov 2017 A1
20170344253 Zhang Nov 2017 A1
20170352379 Oh et al. Dec 2017 A1
20170354888 Benedetto et al. Dec 2017 A1
20170357382 Miura et al. Dec 2017 A1
20170357425 Smith et al. Dec 2017 A1
20170357434 Coffman et al. Dec 2017 A1
20170357917 Holmes et al. Dec 2017 A1
20170358071 Yamaoka et al. Dec 2017 A1
20170359191 Smith et al. Dec 2017 A1
20170359285 Weinig et al. Dec 2017 A1
20170359504 Manzari et al. Dec 2017 A1
20170359505 Manzari et al. Dec 2017 A1
20170359506 Manzari et al. Dec 2017 A1
20170366729 Itoh Dec 2017 A1
20170373868 Deets, Jr. Dec 2017 A1
20180007315 Kim et al. Jan 2018 A1
20180013949 Han Jan 2018 A1
20180021684 Benedetto Jan 2018 A1
20180034867 Zahn et al. Feb 2018 A1
20180035031 Kwak et al. Feb 2018 A1
20180047200 O'Hara et al. Feb 2018 A1
20180048820 Hinkel Feb 2018 A1
20180052571 Seol et al. Feb 2018 A1
20180061158 Greene Mar 2018 A1
20180070144 Tang et al. Mar 2018 A1
20180077332 Shimura et al. Mar 2018 A1
20180081522 Greenberg et al. Mar 2018 A1
20180088787 Bereza et al. Mar 2018 A1
20180091728 Brown et al. Mar 2018 A1
20180091732 Wilson et al. Mar 2018 A1
20180095616 Valdivia et al. Apr 2018 A1
20180095649 Valdivia et al. Apr 2018 A1
20180096487 Nash et al. Apr 2018 A1
20180101297 Yang et al. Apr 2018 A1
20180103074 Rosenberg Apr 2018 A1
20180107367 Rinneberg et al. Apr 2018 A1
20180109722 Laroia et al. Apr 2018 A1
20180113577 Burns et al. Apr 2018 A1
20180114543 Novikoff Apr 2018 A1
20180120661 Kilgore et al. May 2018 A1
20180123986 Faulkner et al. May 2018 A1
20180124128 Faulkner et al. May 2018 A1
20180124299 Brook May 2018 A1
20180124359 Faulkner May 2018 A1
20180129224 Hur May 2018 A1
20180131732 Aronoff et al. May 2018 A1
20180131876 Bernstein et al. May 2018 A1
20180131878 Charlton et al. May 2018 A1
20180139374 Yu May 2018 A1
20180146132 Manzari et al. May 2018 A1
20180152611 Li et al. May 2018 A1
20180157455 Troy et al. Jun 2018 A1
20180184008 Kondo Jun 2018 A1
20180184061 Kitsunai et al. Jun 2018 A1
20180191944 Carbonell et al. Jul 2018 A1
20180191965 Faulkner et al. Jul 2018 A1
20180198985 Ishitsuka Jul 2018 A1
20180199025 Holzer et al. Jul 2018 A1
20180199164 Bargetzi et al. Jul 2018 A1
20180203577 Astavans et al. Jul 2018 A1
20180204111 Zadeh et al. Jul 2018 A1
20180205797 Faulkner Jul 2018 A1
20180213144 Kim et al. Jul 2018 A1
20180213161 Kanda et al. Jul 2018 A1
20180227341 Rizzi Aug 2018 A1
20180227479 Parameswaran et al. Aug 2018 A1
20180227482 Holzer et al. Aug 2018 A1
20180227505 Baltz et al. Aug 2018 A1
20180228003 O'Driscoll et al. Aug 2018 A1
20180234608 Sudo et al. Aug 2018 A1
20180249047 Marlatt Aug 2018 A1
20180253194 Javadi Sep 2018 A1
20180262677 Dye et al. Sep 2018 A1
20180267703 Kamimaru et al. Sep 2018 A1
20180270420 Lee et al. Sep 2018 A1
20180278823 Horesh Sep 2018 A1
20180284979 Choi et al. Oct 2018 A1
20180288310 Goldenberg Oct 2018 A1
20180293959 Monga et al. Oct 2018 A1
20180295079 Longo Oct 2018 A1
20180302551 Yamajo et al. Oct 2018 A1
20180302568 Kim et al. Oct 2018 A1
20180308282 Yokoi Oct 2018 A1
20180308480 Jang et al. Oct 2018 A1
20180309801 Rathod Oct 2018 A1
20180332559 Gudivada et al. Nov 2018 A1
20180335901 Manzari et al. Nov 2018 A1
20180335927 Anzures et al. Nov 2018 A1
20180335929 Scapel et al. Nov 2018 A1
20180335930 Scapel et al. Nov 2018 A1
20180336715 Rickwald et al. Nov 2018 A1
20180341448 Behzadi et al. Nov 2018 A1
20180343383 Ito et al. Nov 2018 A1
20180348764 Zhang et al. Dec 2018 A1
20180349008 Manzari et al. Dec 2018 A1
20180349659 Manzari et al. Dec 2018 A1
20180352165 Zhen et al. Dec 2018 A1
20180364665 Clymer et al. Dec 2018 A1
20180367483 Rodriguez et al. Dec 2018 A1
20180367484 Rodriguez et al. Dec 2018 A1
20180375676 Bader-natal et al. Dec 2018 A1
20180376122 Park et al. Dec 2018 A1
20190007589 Kadambala et al. Jan 2019 A1
20190025943 Jobs et al. Jan 2019 A1
20190028419 Sullivan Jan 2019 A1
20190028650 Bernstein et al. Jan 2019 A1
20190029513 Gunnerson et al. Jan 2019 A1
20190034849 Romaine et al. Jan 2019 A1
20190051032 Chu et al. Feb 2019 A1
20190058827 Park et al. Feb 2019 A1
20190068670 Adam et al. Feb 2019 A1
20190080189 Van Os et al. Mar 2019 A1
20190082097 Manzari et al. Mar 2019 A1
20190089873 Misawa et al. Mar 2019 A1
20190102049 Anzures et al. Apr 2019 A1
20190102145 Wilberding et al. Apr 2019 A1
20190108684 Callaghan Apr 2019 A1
20190114740 Ogino et al. Apr 2019 A1
20190121216 Shabtay et al. Apr 2019 A1
20190124021 Demattei Apr 2019 A1
20190138259 Bagaria et al. May 2019 A1
20190138951 Brownhill et al. May 2019 A1
20190141030 Cockerill et al. May 2019 A1
20190149706 Rivard et al. May 2019 A1
20190173939 Lewis et al. Jun 2019 A1
20190174054 Srivastava et al. Jun 2019 A1
20190199926 An et al. Jun 2019 A1
20190199963 Ahn et al. Jun 2019 A1
20190199993 Babu et al. Jun 2019 A1
20190205861 Bace Jul 2019 A1
20190206031 Kim et al. Jul 2019 A1
20190222769 Srivastava et al. Jul 2019 A1
20190222775 Ahn Jul 2019 A1
20190228495 Tremblay et al. Jul 2019 A1
20190235743 Ono Aug 2019 A1
20190236142 Balakrishnan et al. Aug 2019 A1
20190250812 Davydov et al. Aug 2019 A1
20190253619 Davydov et al. Aug 2019 A1
20190289201 Nishimura et al. Sep 2019 A1
20190289271 Paulus et al. Sep 2019 A1
20190297039 Rodriguez et al. Sep 2019 A1
20190303861 Mathias et al. Oct 2019 A1
20190318538 Li et al. Oct 2019 A1
20190339825 Anzures et al. Nov 2019 A1
20190342507 Dye et al. Nov 2019 A1
20190342519 Van Os et al. Nov 2019 A1
20190347181 Cranfill et al. Nov 2019 A1
20190361575 Ni et al. Nov 2019 A1
20190361694 Gordon et al. Nov 2019 A1
20190362555 Chen et al. Nov 2019 A1
20190370805 Van Os et al. Dec 2019 A1
20190379821 Kobayashi et al. Dec 2019 A1
20190379837 Kim et al. Dec 2019 A1
20200045245 Van Os et al. Feb 2020 A1
20200050502 Ghafourifar et al. Feb 2020 A1
20200053288 Kim et al. Feb 2020 A1
20200055515 Herman et al. Feb 2020 A1
20200059605 Liu et al. Feb 2020 A1
20200068121 Wang Feb 2020 A1
20200082599 Manzari Mar 2020 A1
20200104038 Kamath et al. Apr 2020 A1
20200105003 Stauber et al. Apr 2020 A1
20200106952 Missig et al. Apr 2020 A1
20200106965 Malia et al. Apr 2020 A1
20200128191 Sun et al. Apr 2020 A1
20200135191 Nourbakhsh Apr 2020 A1
20200142577 Manzari et al. May 2020 A1
20200143593 Rudman et al. May 2020 A1
20200152186 Koh et al. May 2020 A1
20200183548 Anzures et al. Jun 2020 A1
20200186378 Six et al. Jun 2020 A1
20200195887 Van Os et al. Jun 2020 A1
20200204725 Li Jun 2020 A1
20200213530 Ahn Jul 2020 A1
20200221020 Manzari et al. Jul 2020 A1
20200234508 Shaburov et al. Jul 2020 A1
20200236278 Yeung et al. Jul 2020 A1
20200242788 Jacobs Jul 2020 A1
20200244879 Hohjoh Jul 2020 A1
20200274726 Setteboun et al. Aug 2020 A1
20200279279 Chaudhuri Sep 2020 A1
20200285806 Radakovitz et al. Sep 2020 A1
20200285851 Lin et al. Sep 2020 A1
20200296329 Tang et al. Sep 2020 A1
20200302913 Marcinkiewicz Sep 2020 A1
20200335133 Vaucher Oct 2020 A1
20200336660 Dong et al. Oct 2020 A1
20200336674 Bernstein et al. Oct 2020 A1
20200358963 Manzari et al. Nov 2020 A1
20200380768 Harris et al. Dec 2020 A1
20200380781 Barlier et al. Dec 2020 A1
20200383157 Lee et al. Dec 2020 A1
20200385116 Sabripour et al. Dec 2020 A1
20200395012 Kim et al. Dec 2020 A1
20200400957 Van Heugten Dec 2020 A1
20200410763 Hare et al. Dec 2020 A1
20200412975 Al Majid et al. Dec 2020 A1
20210005003 Chong et al. Jan 2021 A1
20210043189 Pyun Feb 2021 A1
20210058351 Viklund et al. Feb 2021 A1
20210064317 Juenger et al. Mar 2021 A1
20210065134 Chhabra et al. Mar 2021 A1
20210065448 Goodrich et al. Mar 2021 A1
20210065454 Goodrich et al. Mar 2021 A1
20210096703 Anzures et al. Apr 2021 A1
20210097695 Lundberg et al. Apr 2021 A1
20210097768 Malia et al. Apr 2021 A1
20210099568 Depue et al. Apr 2021 A1
20210099761 Zhang Apr 2021 A1
20210099829 Soto et al. Apr 2021 A1
20210136129 Ponnusamy et al. May 2021 A1
20210144336 Van Os et al. May 2021 A1
20210146838 Goseberg et al. May 2021 A1
20210152503 Rodriguez et al. May 2021 A1
20210152505 Baldwin et al. May 2021 A1
20210158622 Leelaphattarakij et al. May 2021 A1
20210158830 Boehlke May 2021 A1
20210168108 Antmen et al. Jun 2021 A1
20210176204 Geppert et al. Jun 2021 A1
20210182169 Mardente et al. Jun 2021 A1
20210195084 Olajos et al. Jun 2021 A1
20210195093 Manzari et al. Jun 2021 A1
20210201953 Takahashi et al. Jul 2021 A1
20210217106 Hauser et al. Jul 2021 A1
20210264656 Barlier et al. Aug 2021 A1
20210265032 Burgess et al. Aug 2021 A1
20210266274 Liu et al. Aug 2021 A1
20210287343 Kaida Sep 2021 A1
20210306288 Boyd et al. Sep 2021 A1
20210318798 Manzari et al. Oct 2021 A1
20210323406 So et al. Oct 2021 A1
20210333864 Harvey et al. Oct 2021 A1
20210349680 Kim et al. Nov 2021 A1
20210352172 Kim et al. Nov 2021 A1
20210360199 Oz et al. Nov 2021 A1
20210373750 Manzari et al. Dec 2021 A1
20210375042 Chen et al. Dec 2021 A1
20210397338 Davydov et al. Dec 2021 A1
20210409359 Eirinberg et al. Dec 2021 A1
20220004356 Kim et al. Jan 2022 A1
20220044459 Zacharia et al. Feb 2022 A1
20220046186 Fayad et al. Feb 2022 A1
20220046222 Meier Feb 2022 A1
20220050578 Waldman et al. Feb 2022 A1
20220053142 Manzari et al. Feb 2022 A1
20220070380 Bernstein et al. Mar 2022 A1
20220070385 Van Os et al. Mar 2022 A1
20220103758 Manzari et al. Mar 2022 A1
20220122089 Bonilla Kuhlmann et al. Apr 2022 A1
20220124241 Manzari et al. Apr 2022 A1
20220244836 O'leary et al. Aug 2022 A1
20220247918 O'leary et al. Aug 2022 A1
20220247919 O'leary et al. Aug 2022 A1
20220262022 Stauber et al. Aug 2022 A1
20220264028 Manzari et al. Aug 2022 A1
20220276041 Dryer et al. Sep 2022 A1
20220278992 Baker et al. Sep 2022 A1
20220286314 Meyer et al. Sep 2022 A1
20220294992 Manzari et al. Sep 2022 A1
20220319100 Manzari et al. Oct 2022 A1
20220345785 Yang et al. Oct 2022 A1
20220353425 Manzari et al. Nov 2022 A1
20220365643 Triverio et al. Nov 2022 A1
20220365739 Chang et al. Nov 2022 A1
20220365740 Chang et al. Nov 2022 A1
20220368548 Chang et al. Nov 2022 A1
20220368659 Chang et al. Nov 2022 A1
20220368742 Chang et al. Nov 2022 A1
20220374136 Chang et al. Nov 2022 A1
20220382417 Zhang Dec 2022 A1
20220382440 Manzari et al. Dec 2022 A1
20220382443 Clarke et al. Dec 2022 A1
20220417440 Bernstein et al. Dec 2022 A1
20230004264 Anzures et al. Jan 2023 A1
20230020616 Manzari et al. Jan 2023 A1
20230041125 Kim et al. Feb 2023 A1
20230094453 O'Leary et al. Mar 2023 A1
20230098395 O'Leary et al. Mar 2023 A1
20230109787 O'Leary et al. Apr 2023 A1
20230143275 Opara et al. May 2023 A1
20230188674 Van Os et al. Jun 2023 A1
20230209179 Manzari et al. Jun 2023 A1
20230229297 Manzari et al. Jul 2023 A1
20230252659 Stauber et al. Aug 2023 A1
20230254573 Manzari et al. Aug 2023 A1
20230262317 O'Leary et al. Aug 2023 A1
20230283884 Van Os et al. Sep 2023 A1
Foreign Referenced Citations (474)
Number Date Country
2015100713 Jun 2015 AU
2013368443 Mar 2016 AU
2017100683 Jan 2018 AU
2015297035 Jun 2018 AU
2729392 Aug 2011 CA
2845537 Sep 2014 CA
2965700 May 2016 CA
2729392 May 2017 CA
1437365 Aug 2003 CN
1499878 May 2004 CN
1689327 Oct 2005 CN
1705346 Dec 2005 CN
1890996 Jan 2007 CN
1901717 Jan 2007 CN
101068311 Nov 2007 CN
101075173 Nov 2007 CN
101243383 Aug 2008 CN
101282422 Oct 2008 CN
101300830 Nov 2008 CN
101310519 Nov 2008 CN
101355655 Jan 2009 CN
101364031 Feb 2009 CN
101388965 Mar 2009 CN
101427574 May 2009 CN
101431564 May 2009 CN
101576996 Nov 2009 CN
101681462 Mar 2010 CN
101682622 Mar 2010 CN
101778220 Jul 2010 CN
101853132 Oct 2010 CN
101854247 Oct 2010 CN
101883213 Nov 2010 CN
101917529 Dec 2010 CN
101931691 Dec 2010 CN
201788344 Apr 2011 CN
102075727 May 2011 CN
102084327 Jun 2011 CN
102088554 Jun 2011 CN
102215217 Oct 2011 CN
102272700 Dec 2011 CN
102428655 Apr 2012 CN
102457661 May 2012 CN
102474560 May 2012 CN
102567953 Jul 2012 CN
102572369 Jul 2012 CN
202309894 Jul 2012 CN
202330968 Jul 2012 CN
102625036 Aug 2012 CN
102651731 Aug 2012 CN
102855079 Jan 2013 CN
103037075 Apr 2013 CN
103039064 Apr 2013 CN
103051837 Apr 2013 CN
103051841 Apr 2013 CN
103052961 Apr 2013 CN
103222247 Jul 2013 CN
103237191 Aug 2013 CN
103297719 Sep 2013 CN
103309602 Sep 2013 CN
103324329 Sep 2013 CN
103384235 Nov 2013 CN
103442774 Dec 2013 CN
103458215 Dec 2013 CN
103491298 Jan 2014 CN
103649985 Mar 2014 CN
103685925 Mar 2014 CN
103702029 Apr 2014 CN
103702039 Apr 2014 CN
103718152 Apr 2014 CN
103748610 Apr 2014 CN
103777742 May 2014 CN
103916582 Jul 2014 CN
103947190 Jul 2014 CN
103970472 Aug 2014 CN
104010158 Aug 2014 CN
104081335 Oct 2014 CN
104270597 Jan 2015 CN
104346080 Feb 2015 CN
104346099 Feb 2015 CN
104423946 Mar 2015 CN
104427288 Mar 2015 CN
104461288 Mar 2015 CN
104469143 Mar 2015 CN
104602133 May 2015 CN
104754203 Jul 2015 CN
104813322 Jul 2015 CN
104836947 Aug 2015 CN
104869046 Aug 2015 CN
104903834 Sep 2015 CN
104952063 Sep 2015 CN
104980578 Oct 2015 CN
105094957 Nov 2015 CN
105138259 Dec 2015 CN
105141498 Dec 2015 CN
105190511 Dec 2015 CN
105204846 Dec 2015 CN
105210018 Dec 2015 CN
105229571 Jan 2016 CN
105245774 Jan 2016 CN
105264473 Jan 2016 CN
105338256 Feb 2016 CN
105389173 Mar 2016 CN
105391778 Mar 2016 CN
105474163 Apr 2016 CN
105493138 Apr 2016 CN
105554429 May 2016 CN
105589637 May 2016 CN
105611215 May 2016 CN
105620393 Jun 2016 CN
105630290 Jun 2016 CN
105637855 Jun 2016 CN
105653031 Jun 2016 CN
105765967 Jul 2016 CN
105794196 Jul 2016 CN
105900376 Aug 2016 CN
105981372 Sep 2016 CN
105991915 Oct 2016 CN
106067947 Nov 2016 CN
106161956 Nov 2016 CN
106210184 Dec 2016 CN
106210550 Dec 2016 CN
106210855 Dec 2016 CN
106257540 Dec 2016 CN
106257909 Dec 2016 CN
106303280 Jan 2017 CN
106303648 Jan 2017 CN
106303690 Jan 2017 CN
106341611 Jan 2017 CN
106375662 Feb 2017 CN
106412214 Feb 2017 CN
106412412 Feb 2017 CN
106412445 Feb 2017 CN
106445219 Feb 2017 CN
106471793 Mar 2017 CN
106534619 Mar 2017 CN
106575149 Apr 2017 CN
106713946 May 2017 CN
106791357 May 2017 CN
106791377 May 2017 CN
106791420 May 2017 CN
106921829 Jul 2017 CN
107066523 Aug 2017 CN
107077274 Aug 2017 CN
107079141 Aug 2017 CN
107122049 Sep 2017 CN
107491257 Dec 2017 CN
107533356 Jan 2018 CN
107533417 Jan 2018 CN
107534656 Jan 2018 CN
107566721 Jan 2018 CN
107580693 Jan 2018 CN
107704177 Feb 2018 CN
107728876 Feb 2018 CN
107770448 Mar 2018 CN
107800945 Mar 2018 CN
107820011 Mar 2018 CN
107924113 Apr 2018 CN
107992248 May 2018 CN
108353126 Jul 2018 CN
108391053 Aug 2018 CN
108513070 Sep 2018 CN
108549522 Sep 2018 CN
108668083 Oct 2018 CN
108712609 Oct 2018 CN
108769562 Nov 2018 CN
108848308 Nov 2018 CN
108886569 Nov 2018 CN
109005366 Dec 2018 CN
109061985 Dec 2018 CN
109196825 Jan 2019 CN
109313530 Feb 2019 CN
109496425 Mar 2019 CN
109639970 Apr 2019 CN
109644229 Apr 2019 CN
110784615 Feb 2020 CN
111580671 Aug 2020 CN
111784615 Oct 2020 CN
111901475 Nov 2020 CN
111901476 Nov 2020 CN
111917980 Nov 2020 CN
112154658 Dec 2020 CN
112291627 Jan 2021 CN
112598677 Apr 2021 CN
112637477 Apr 2021 CN
202110328601 Apr 2022 CN
201670652 Dec 2017 DK
201670753 Jan 2018 DK
201670755 Jan 2018 DK
201670627 Feb 2018 DK
0651543 May 1995 EP
0651543 Dec 1997 EP
1278099 Jan 2003 EP
1592212 Nov 2005 EP
1953663 Aug 2008 EP
0651543 Sep 2008 EP
1981262 Oct 2008 EP
2056568 May 2009 EP
2194508 Jun 2010 EP
2237536 Oct 2010 EP
2430766 Mar 2012 EP
2454872 May 2012 EP
2482179 Aug 2012 EP
2487613 Aug 2012 EP
2487913 Aug 2012 EP
2430766 Dec 2012 EP
2579572 Apr 2013 EP
2627073 Aug 2013 EP
2634751 Sep 2013 EP
2640060 Sep 2013 EP
2682855 Jan 2014 EP
2830297 Jan 2015 EP
2843530 Mar 2015 EP
2446619 Oct 2015 EP
2950198 Dec 2015 EP
2966855 Jan 2016 EP
2972677 Jan 2016 EP
2430766 Mar 2016 EP
3008575 Apr 2016 EP
3012732 Apr 2016 EP
3026636 Jun 2016 EP
3033837 Jun 2016 EP
3038427 Jun 2016 EP
3051525 Aug 2016 EP
3104590 Dec 2016 EP
3107065 Dec 2016 EP
3120217 Jan 2017 EP
2761582 Mar 2017 EP
3033837 Mar 2017 EP
3209012 Aug 2017 EP
3211587 Aug 2017 EP
2194508 Dec 2017 EP
2258103 May 2018 EP
3333544 Jun 2018 EP
2556665 Aug 2018 EP
3033837 Oct 2018 EP
3393119 Oct 2018 EP
3135028 Jan 2019 EP
2482179 Mar 2019 EP
3457680 Mar 2019 EP
3012732 May 2019 EP
3008575 Jul 2019 EP
3120217 Apr 2020 EP
3633975 Apr 2020 EP
3163866 May 2020 EP
3736676 Nov 2020 EP
2682855 Feb 2021 EP
3787285 Mar 2021 EP
2307383 May 1997 GB
2515797 Jan 2015 GB
2519363 Apr 2015 GB
2523670 Sep 2015 GB
40022327 Nov 2020 HK
1038MUM2005 Jun 2007 IN
2-179078 Jul 1990 JP
9-116792 May 1997 JP
11-355617 Dec 1999 JP
2000-207549 Jul 2000 JP
2000-244905 Sep 2000 JP
2001-245204 Sep 2001 JP
2001-298649 Oct 2001 JP
2003-8964 Jan 2003 JP
2003-18438 Jan 2003 JP
2003-32597 Jan 2003 JP
2003-241293 Aug 2003 JP
2003-248549 Sep 2003 JP
2003-338975 Nov 2003 JP
200415595 Jan 2004 JP
2004-135074 Apr 2004 JP
2005-31466 Feb 2005 JP
2005-94696 Apr 2005 JP
2005-191641 Jul 2005 JP
2005-191985 Jul 2005 JP
2005-311699 Nov 2005 JP
3872041 Jan 2007 JP
2007-28211 Feb 2007 JP
2007-124398 May 2007 JP
2007-150921 Jun 2007 JP
2008-66978 Mar 2008 JP
2008-99330 Apr 2008 JP
2008-236534 Oct 2008 JP
2009-105919 May 2009 JP
2009-212899 Sep 2009 JP
2009-273023 Nov 2009 JP
2009-545256 Dec 2009 JP
2010-117444 May 2010 JP
2010-119147 May 2010 JP
2010-160581 Jul 2010 JP
2010-182023 Aug 2010 JP
2010-268052 Nov 2010 JP
2011-87167 Apr 2011 JP
2011-91570 May 2011 JP
2011-124864 Jun 2011 JP
2011-211552 Oct 2011 JP
2011-249887 Dec 2011 JP
2012-79302 Apr 2012 JP
2012-89973 May 2012 JP
2012-124608 Jun 2012 JP
2012-147379 Aug 2012 JP
2013-70303 Apr 2013 JP
2013-101528 May 2013 JP
2013-106289 May 2013 JP
2013-524683 Jun 2013 JP
2013-546238 Dec 2013 JP
2014-23083 Feb 2014 JP
2014-60501 Apr 2014 JP
2014-71835 Apr 2014 JP
2014-87126 May 2014 JP
2014-170982 Sep 2014 JP
2014-212415 Nov 2014 JP
2015-1716 Jan 2015 JP
2015-5255 Jan 2015 JP
2015-11507 Jan 2015 JP
2015-22716 Feb 2015 JP
2015-25897 Feb 2015 JP
2015-50713 Mar 2015 JP
2015-76717 Apr 2015 JP
2015-091098 May 2015 JP
2015-146619 Aug 2015 JP
2015-149095 Aug 2015 JP
2015-170234 Sep 2015 JP
2015-180987 Oct 2015 JP
2015-201839 Nov 2015 JP
2015-534742 Dec 2015 JP
2016-1446 Jan 2016 JP
2016-66978 Apr 2016 JP
2016-72965 May 2016 JP
2016-129315 Jul 2016 JP
2016-174282 Sep 2016 JP
2016-175175 Oct 2016 JP
2017-34474 Feb 2017 JP
2017-228843 Dec 2017 JP
2018-7158 Jan 2018 JP
2018-56719 Apr 2018 JP
2018-107711 Jul 2018 JP
2018-121235 Aug 2018 JP
2019-62556 Apr 2019 JP
2019-145108 Aug 2019 JP
2019-203399 Nov 2019 JP
2020-42602 Mar 2020 JP
6982047 Nov 2021 JP
10-2005-0086630 Aug 2005 KR
10-2009-0066319 Jun 2009 KR
10-2012-0004928 Jan 2012 KR
10-2012-0025872 Mar 2012 KR
10-2012-0048397 May 2012 KR
10-2012-0054406 May 2012 KR
10-2012-0057696 Jun 2012 KR
10-2012-0093322 Aug 2012 KR
10-2013-0033445 Apr 2013 KR
10-1341095 Dec 2013 KR
10-1343591 Dec 2013 KR
10-2014-0019631 Feb 2014 KR
10-2014-0049850 Apr 2014 KR
10-2014-0062801 May 2014 KR
10-2015-0014290 Feb 2015 KR
10-2015-0024899 Mar 2015 KR
10-2016-0016910 Feb 2016 KR
10-2016-0019145 Feb 2016 KR
10-2016-0020396 Feb 2016 KR
10-2016-0020791 Feb 2016 KR
10-2016-0047891 May 2016 KR
10-2016-0075583 Jun 2016 KR
10-1674959 Nov 2016 KR
10-2017-0123125 Nov 2017 KR
10-1799223 Nov 2017 KR
10-2017-0135975 Dec 2017 KR
10-2018-0017227 Feb 2018 KR
10-2018-0037076 Apr 2018 KR
10-2018-0085931 Jul 2018 KR
10-2018-0095331 Aug 2018 KR
10-2018-0108847 Oct 2018 KR
10-2018-0137610 Dec 2018 KR
10-2019-0034248 Apr 2019 KR
10-2020-0039030 Apr 2020 KR
10-2338576 Dec 2021 KR
1610470 Nov 1990 SU
9939307 Aug 1999 WO
0118665 Mar 2001 WO
2004032507 Apr 2004 WO
2005043892 May 2005 WO
2005060501 Jul 2005 WO
2007126707 Nov 2007 WO
2008014301 Jan 2008 WO
2008020655 Feb 2008 WO
2008025120 Mar 2008 WO
2008030779 Mar 2008 WO
2008109644 Sep 2008 WO
2009005914 Jan 2009 WO
2009078091 Jun 2009 WO
2010059426 May 2010 WO
2010077048 Jul 2010 WO
2010102678 Sep 2010 WO
2010077048 Oct 2010 WO
2010131869 Nov 2010 WO
2010134275 Nov 2010 WO
2010137513 Dec 2010 WO
2011007264 Jan 2011 WO
2010131869 Feb 2011 WO
2010059426 May 2011 WO
2011126505 Oct 2011 WO
2011146605 Nov 2011 WO
2011146839 Nov 2011 WO
2011161145 Dec 2011 WO
2012001947 Jan 2012 WO
2012006251 Jan 2012 WO
2012019163 Feb 2012 WO
2012037170 Mar 2012 WO
2012051720 Apr 2012 WO
2012170118 Dec 2012 WO
2013082325 Jun 2013 WO
2013114821 Aug 2013 WO
2013152453 Oct 2013 WO
2013152454 Oct 2013 WO
2013189058 Dec 2013 WO
2014052871 Apr 2014 WO
2014058937 Apr 2014 WO
2014066115 May 2014 WO
2014105276 Jul 2014 WO
2014159779 Oct 2014 WO
2014160819 Oct 2014 WO
2014165141 Oct 2014 WO
2014185028 Nov 2014 WO
2014200734 Dec 2014 WO
2014200798 Dec 2014 WO
2015023044 Feb 2015 WO
2015026864 Feb 2015 WO
2015037211 Mar 2015 WO
2015059349 Apr 2015 WO
2015080744 Jun 2015 WO
2015085042 Jun 2015 WO
2015112868 Jul 2015 WO
2014200798 Aug 2015 WO
2015144209 Oct 2015 WO
2015152953 Oct 2015 WO
2015166684 Nov 2015 WO
2015183438 Dec 2015 WO
2015187494 Dec 2015 WO
2015190666 Dec 2015 WO
2016028806 Feb 2016 WO
2016028807 Feb 2016 WO
2016028808 Feb 2016 WO
2016028809 Feb 2016 WO
2016064435 Apr 2016 WO
2016073804 May 2016 WO
2016073804 Jul 2016 WO
2016145129 Sep 2016 WO
2016168154 Oct 2016 WO
2016172619 Oct 2016 WO
2016203282 Dec 2016 WO
2016204936 Dec 2016 WO
2017058834 Apr 2017 WO
2017071559 May 2017 WO
2017153771 Sep 2017 WO
2017164716 Sep 2017 WO
2017201326 Nov 2017 WO
2017218143 Dec 2017 WO
2017218153 Dec 2017 WO
2017218193 Dec 2017 WO
2018006053 Jan 2018 WO
2018048838 Mar 2018 WO
2018049430 Mar 2018 WO
2018057268 Mar 2018 WO
2018099037 Jun 2018 WO
2018144339 Aug 2018 WO
2018159864 Sep 2018 WO
2018212802 Nov 2018 WO
2018213401 Nov 2018 WO
2018213415 Nov 2018 WO
2018232333 Dec 2018 WO
2019050562 Mar 2019 WO
2019067131 Apr 2019 WO
2019216997 Nov 2019 WO
2020227386 Nov 2020 WO
2021112983 Jun 2021 WO
Non-Patent Literature Citations (1099)
Entry
Applicant Initiated Interview Summary received for U.S. Appl. No. 17/190,879, dated Oct. 26, 2021, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/528,257, dated Nov. 18, 2021, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/121,610, dated Oct. 29, 2021, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/220,596, dated Aug. 18, 2021, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/476,404, dated Mar. 18, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/528,257, dated Feb. 3, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/733,718, dated Nov. 17, 2021, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/121,610, dated Mar. 31, 2022, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/157,166, dated Apr. 13, 2022, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/157,166, dated Dec. 9, 2021, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/157,166, dated Dec. 15, 2021, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/157,166, dated Jan. 5, 2022, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/190,879, dated Nov. 19, 2021, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/220,596, dated Nov. 4, 2021, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/220,596, dated Nov. 18, 2021, 27 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/354,376, dated Apr. 11, 2022, 5 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/354,376, dated Feb. 16, 2022, 5 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/354,376, dated Mar. 23, 2022, 6 pages.
Decision on Appeal received for U.S. Appl. No. 15/995,040, dated Dec. 29, 2021, 14 pages.
Decision on Appeal received for U.S. Appl. No. 16/144,629, dated Jan. 18, 2022, 8 pages.
Decision to Grant received for Danish Patent Application No. PA201770719, dated Feb. 3, 2022, 2 pages.
Decision to Grant received for European Patent Application No. 16784025.5, dated Nov. 11, 2021, 2 pages.
Decision to Grant received for European Patent Application No. 17809168.2, dated Oct. 21, 2021, 3 pages.
Decision to Grant received for European Patent Application No. 19729395.4, dated Dec. 9, 2021, 2 pages.
Decision to Grant received for Japanese Patent Application No. 2018-182607, dated Apr. 13, 2022, 3 pages (1 page of English Translation and 2 pages of Official Copy).
Decision to Grant received for Japanese Patent Application No. 2019-203399, dated Oct. 20, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy).
Decision to Grant received for Japanese Patent Application No. 2019-566087, dated Jan. 26, 2022, 2 pages (1 page of English Translation and 1 page of Official Copy).
Decision to Refuse received for European Patent Application No. 19204230.7, dated Feb. 4, 2022, 15 pages.
Demetriou, Soteris, “Analyzing & Designing the Security of Shared Resources on Smartphone Operating Systems, Dissertation”, University of Illinois at Urbana-Champaign Online available at: https://www.ideals.illinois.edu/bitstream/handle/2142/100907/DEMETRIOU-DISSERTATION-2018.pdf?sequence=1&isAllowed=n, 2018, 211 pages.
Dutta, Tushar Subhra., “Warning! iOS Apps with Camera Access Permission Can Spy On You”, Online available at: https://web.archive.org/web/20180219092123/https://techviral.net/ios-apps-camera-can-spy/, Feb. 19, 2018, 3 pages.
Ex Parte Quayle Action received for U.S. Appl. No. 17/121,610, mailed on Dec. 9, 2021, 7 pages.
Examiner-Initiated Interview Summary received for U.S. Appl. No. 17/027,373, dated Mar. 31, 2022, 4 pages.
Examiner-Initiated Interview Summary received for U.S. Appl. No. 17/220,596, dated Oct. 7, 2021, 2 pages.
Extended European Search Report received for European Patent Application No. 21202358.4, dated Dec. 6, 2021, 8 pages.
Extended European Search Report received for European Patent Application No. 22151131.4, dated Mar. 24, 2022, 6 pages.
Intention to Grant received for Danish Patent Application No. PA202070617, dated Nov. 15, 2021, 2 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/031643, dated Nov. 18, 2021, 27 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/046877, dated Mar. 1, 2022, 17 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2021/046877, mailed on Jan. 5, 2022, 10 pages.
King, Julie Adair., “How to Check the Exposure Meter on Your Nikon D5500”, Online available at: https://www.dummies.com/article/home-auto-hobbies/photography/how-to-check-the-exposuremeter-on-your-nikon-d5500-142677, Mar. 26, 2016, 6 pages.
Minutes of the Oral Proceedings received for European Patent Application No. 19204230.7, mailed on Feb. 2, 2022, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 17/476,404, dated Feb. 8, 2022, 26 pages.
Non-Final Office Action received for U.S. Appl. No. 15/995,040, dated Apr. 8, 2022, 21 pages.
Non-Final Office Action received for U.S. Appl. No. 17/027,373, dated Feb. 2, 2022, 17 pages.
Non-Final Office Action received for U.S. Appl. No. 17/220,596, dated Jun. 10, 2021, 31 pages.
Notice of Acceptance received for Australian Patent Application No. 2019218241, dated Mar. 9, 2022, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2020239711, dated Dec. 16, 2021, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2020260413, dated Oct. 14, 2021, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2021254567, dated Nov. 17, 2021, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2022200966, dated Feb. 25, 2022, 3 pages.
Notice of Allowance received for Chinese Patent Application No. 202010287950.2, dated Mar. 22, 2022, 7 pages (03 pages Of English Translation and 04 pages of Official Copy).
Notice of Allowance received for Chinese Patent Application No. 202010600197.8, dated Feb. 9, 2022, 5 pages (1 page of English Translation and 4 pages of Official Copy).
Notice of Allowance received for Chinese Patent Application No. 202010601484.0, dated Nov. 23, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy).
Notice of Allowance received for Chinese Patent Application No. 202011480411.7, dated Feb. 18, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Japanese Patent Application No. 2019-194597, dated Nov. 19, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2021-0022053, dated Nov. 23, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2021-7020693, dated Dec. 27, 2021, 5 pages (1 page of English Translation and 4 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2021-7035687, dated Dec. 30, 2021, 5 pages (1 page of English Translation and 4 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2021-7036337, dated Apr. 5, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2022-7002829, dated Feb. 12, 2022, 6 pages (1 page of English Translation and 5 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 17/157,166, dated Nov. 16, 2021, 6 pages.
Notice of Allowance received for U.S. Appl. No. 16/144,629, dated Apr. 7, 2022, 8 pages.
Notice of Allowance received for U.S. Appl. No. 16/528,257, dated Jan. 14, 2022, 10 pages.
Notice of Allowance received for U.S. Appl. No. 16/733,718, dated Oct. 20, 2021, 24 pages.
Notice of Allowance received for U.S. Appl. No. 16/835,651, dated Nov. 10, 2021, 9 pages.
Notice of Allowance received for U.S. Appl. No. 17/121,610, dated Mar. 11, 2022, 5 pages.
Notice of Allowance received for U.S. Appl. No. 17/157,166, dated Mar. 30, 2022, 6 pages.
Notice of Allowance received for U.S. Appl. No. 17/190,879, dated Nov. 10, 2021, 8 pages.
Notice of Allowance received for U.S. Appl. No. 17/220,596, dated Oct. 21, 2021, 43 pages.
Notice of Allowance received for U.S. Appl. No. 17/354,376, dated Jan. 27, 2022, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/354,376, dated Mar. 4, 2022, 5 pages.
Notice of Allowance received for U.S. Appl. No. 17/354,376, dated Mar. 30, 2022, 5 pages.
Office Action received for Australian Patent Application No. 2019338180, dated Feb. 18, 2022, 3 pages.
Office Action received for Australian Patent Application No. 2020239717, dated Dec. 15, 2021, 6 pages.
Office Action received for Australian Patent Application No. 2020239717, dated Mar. 16, 2022, 4 pages.
Office Action received for Australian Patent Application No. 2021107587, dated Feb. 1, 2022, 6 pages.
Office Action received for Australian Patent Application No. 2021201295, dated Jan. 14, 2022, 3 pages.
Office Action received for Australian Patent Application No. 2021203903, dated Feb. 24, 2022, 3 pages.
Office Action received for Chinese Patent Application No. 2019104001792, dated Dec. 27, 2021, 32 pages (13 pages of English Translation and 19 pages of Official Copy).
Office Action received for Chinese Patent Application No. 2020101266614, dated Mar. 4, 2022, 13 pages (8 pages of English Translation and 5 pages of Official Copy).
Office Action received for Chinese Patent Application No. 2020102879502, dated Nov. 19, 2021, 8 pages (5 pages of English Translation and 3 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202011480411.7, dated Jan. 12, 2022, 7 pages (4 pages of English Translation and 3 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202110328602.X, dated Mar. 24, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy).
Office Action received for Chinese Patent Application No. 2021107666687, dated Feb. 16, 2022, 12 pages (6 pages of English Translation and 6 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202180002106.3, dated Feb. 16, 2022, 12 pages (6 pages of English Translation and 6 pages of Official Copy).
Office Action received for Danish Patent Application No. PA201770719, dated Nov. 16, 2021, 2 pages.
Office Action received for European Patent Application No. 18779093.6, dated Mar. 17, 2022, 4 pages.
Office Action received for European Patent Application No. 20205496.1, dated Nov. 10, 2021, 5 pages.
Office Action received for European Patent Application No. 20206197.4, dated Mar. 18, 2022, 7 pages.
Office Action received for European Patent Application No. 20210373.5, dated Dec. 9, 2021, 7 pages.
Office Action received for Indian Patent Application No. 201818025015, dated Feb. 4, 2022, 7 pages.
Office Action received for Indian Patent Application No. 201818046896, dated Feb. 2, 2022, 7 pages.
Office Action received for Indian Patent Application No. 202014041529, dated Dec. 6, 2021, 6 pages.
Office Action received for Indian Patent Application No. 202014041530, dated Dec. 8, 2021, 7 pages.
Office Action received for Indian Patent Application No. 202118021941, dated Mar. 23, 2022, 5 pages.
Office Action received for Japanese Patent Application No. 2019-566087, dated Oct. 18, 2021, 10 pages (6 pages of English Translation and 4 pages of Official Copy).
Office Action received for Japanese Patent Application No. 2020-159338, dated Dec. 8, 2021, 9 pages (5 pages of English Translation and 4 pages of Official Copy).
Office Action received for Japanese Patent Application No. 2020-159840, dated Dec. 10, 2021, 13 pages (7 pages of English Translation and 6 pages of Official Copy).
Office Action received for Japanese Patent Application No. 2020-159840, dated Mar. 28, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy).
Office Action received for Korean Patent Application No. 10-2021-7036337, dated Dec. 8, 2021, 6 pages (2 pages of English Translation and 4 pages of Official Copy).
Office Action received for Korean Patent Application No. 10-2022-7006310, dated Mar. 8, 2022, 6 pages (2 pages of English Translation and 4 pages of Official Copy).
Record of Oral Hearing received for U.S. Appl. No. 16/144,629, mailed on Jan. 28, 2022, 13 pages.
Sigdel, Prakash, “How to record WhatsApp voice massage without continue holding down button”, Available Online at: https://www.youtube.com/watch?v=m3Hz6TXtOPA, Dec. 6, 2017, 9 pages.
Tech Stuff, “Telegram 4.0: Video Messages + Telescope, Payments and more . . . ”, Available Online at: https://www.youtube.com/watch?v=y0alJRPH7nQ, May 19, 2017, 46 pages.
Whitacre, Michele, “Photography 101 | Exposure Meter”, Online available at: https://web.archive.org/web/20160223055834/http://www.michelewhitacrephotographyblog.com, Feb. 23, 2016, 4 pages.
Wu, et al., “Security Threats to Mobile Multimedia Applications: Camera-Based Attacks on Mobile Phones”, IEEE Communications Magazine, Available online at: http://www.ieeeprojectmadurai.in/BASE/ANDROID/Security%20Threats%20to%20Mobile.pdf, Mar. 2014, pp. 80-87.
[B612] Addition of facial recognition bear/cat stamps and AR background function having moving sparkles or hearts, Available Online at: <URL, htpps://apptopi.jp/2017/0l/22/b612>, Jan. 22, 2017, 11 pages.
Advisory Action received for U.S. Appl. No. 16/144,629, dated Dec. 13, 2019, 9 pages.
Advisory Action received for U.S. Appl. No. 16/144,629, dated Jan. 6, 2021, 10 pages.
Android Police, “Galaxy S9+ In-Depth Camera Review”, See Especially 0:43-0:53; 1:13-1:25; 1:25-1:27; 5:11-5:38; 6:12-6:26, Available Online at <https://www.youtube.com/watch?v=GZHYCdMCv-w>, Apr. 19, 2018, 3 pages.
Androidcentral, “How do I respond to group messages from notification bar?”, Available online at: https://forums.androidcentral.com/ask-question/952030-how-do-i-respond-group-messages-notification-bar.html, Mar. 25, 2019, 3 pages.
Applicant Initiated Interview Summary received for U.S. Appl. No. 16/790,619, dated Jul. 28, 2020, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/271,583 dated Mar. 2, 2020, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/271,583, dated Jul. 14, 2020, 4 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/995,040, dated Dec. 23, 2019, 5 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/995,040, dated Jul. 27, 2020, 4 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/995,040, dated Nov. 24, 2020, 4 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,629, dated Jul. 2, 2020, 5 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/144,629, dated Nov. 23, 2020, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/528,941, dated Jun. 19, 2020, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/528,941, dated Nov. 10, 2020, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,100, dated Feb. 19, 2020, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/586,344, dated Feb. 27, 2020, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/599,433, dated Apr. 20, 2021, 7 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/733,718, dated Nov. 2, 2020, 4 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/799,481, dated Jul. 24, 2020, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/027,317, dated Dec. 21, 2020, 4 pages.
AstroVideo, “AstroVideo enables you to use a low-cost,low-light video camera to capture astronomical images.”, Available online at: https://www.coaa.co.uk/astrovideo.htm, Retrieved on: Nov. 18, 2019, 5 pages.
Brief Communication regarding Oral Proceedings received for European Patent Application No. 17184710.6, dated Feb. 19, 2020, 2 pages.
Brief Communication regarding Oral Proceedings received for European Patent Application No. 17184710.6, dated Mar. 9, 2020, 2 pages.
Certificate of Examination received for Australian Patent Application No. 2017100683, dated Jan. 16, 2018, 2 pages.
Certificate of Examination received for Australian Patent Application No. 2019100420, dated Jul. 3, 2019, 2 pages.
Certificate of Examination received for Australian Patent Application No. 2019100499, dated Aug. 15, 2019, 2 pages.
Certificate of Examination received for Australian Patent Application No. 2019100794, dated Dec. 19, 2019, 2 pages.
Certificate of Examination received for Australian Patent Application No. 2019101062, dated Jun. 2, 2020, 2 pages.
Certificate of Examination received for Australian Patent Application No. 2020100189, dated May 12, 2020, 2 pages.
Certificate of Examination received for Australian Patent Application No. 2020100720, dated Nov. 11, 2020, 2 pages.
Certificate of Examination received for Australian Patent Application No. 2020101043, dated Dec. 22, 2020, 2 pages.
Certificate of Examination received for Australian Patent Application No. 2020101324, dated Sep. 7, 2020, 2 pages.
Certificate of Examination received for Australian Patent Application No. 2020104220, dated Apr. 1, 2021, 2 pages.
Channel Highway, “Virtual Makeover in Real-time and in full 3D”, Available online at: https://www.youtube.com/watch?v=NgUbBzb5qZg, Feb. 16, 2016, 1 page.
Clover Juli, “Moment Pro Camera App for iOS Gains Zebra Striping for Displaying Over and Underexposed Areas”, Online Available at: https://web.archive.org/web/20190502081353/https://www.macrumors.com/2019/05/01/momentcamera-app-zebra-striping-and-morel, May 1, 2019, 8 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 14/641,251, dated Jun. 17, 2016, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 15/268,115, dated Apr. 13, 2018, 11 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 15/268,115, dated Mar. 21, 2018, 9 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 15/273,453, dated Dec. 21, 2017, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 15/273,453, dated Feb. 8, 2018, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 15/273,453, dated Nov. 27, 2017, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 15/273,503, dated Nov. 2, 2017, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 15/273,503, dated Nov. 24, 2017, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 15/858,175, dated Sep. 21, 2018, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/109,552, dated Jun. 13, 2019, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/143,097, dated Nov. 8, 2019, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/143,396, dated Jan. 30, 2020, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/144,572, dated Mar. 21, 2019, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/147,432, dated Jan. 18, 2019, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/147,432, dated Jul. 16, 2019, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/191,117, dated Dec. 9, 2019, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/191,117, dated Feb. 28, 2020, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/191,117, dated Nov. 20, 2019, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/511,578, dated Feb. 13, 2020, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/582,595, dated Apr. 7, 2020, 5 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/582,595, dated Apr. 22, 2020, 5 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/583,020, dated Mar. 24, 2020, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/584,044, dated Apr. 16, 2020, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/584,044, dated Jan. 29, 2020, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/584,044, dated Mar. 4, 2020, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/584,100, dated Feb. 21, 2020, 9 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/584,693, dated Feb. 21, 2020, 15 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/584,693, dated Mar. 4, 2020, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/584,693, dated Mar. 20, 2020, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/586,314, dated Apr. 8, 2020, 5 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/586,314, dated Mar. 4, 2020, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/586,344, dated Apr. 7, 2020, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/586,344, dated Jan. 23, 2020, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/586,344, dated Mar. 17, 2020, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/790,619, dated Oct. 13, 2020, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/799,481, dated Oct. 27, 2020, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/825,879, dated Jul. 23, 2021, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/835,651, dated Jul. 28, 2021, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/835,651, dated Jun. 14, 2021, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/840,719, dated Jul. 8, 2021, 8 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/840,719, dated May 14, 2021, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/027,484, dated May 14, 2021, 5 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/027,484, dated May 28, 2021, 5 pages.
Corrected Search Report and Opinion received for Danish Patent Application No. PA201870364, dated Sep. 5, 2018, 13 pages.
Decision of Refusal received for Japanese Patent Application No. 2018-243463, dated Feb. 25, 2019, 8 pages.
Decision of Refusal received for Japanese Patent Application No. 2018-545502, dated Feb. 25, 2019, 11 pages.
Decision on Appeal received for Japanese Patent Application No. 2018-225131, dated Mar. 11, 2021, 5 pages.
Decision on Appeal received for Japanese Patent Application No. 2018-545502, dated Mar. 25, 2021, 3 pages.
Decision to grant received for Danish Patent Application No. PA201570788, dated Jul. 10, 2017, 2 pages.
Decision to Grant received for Danish Patent Application No. PA201570791, dated Jun. 7, 2017, 2 pages.
Decision to Grant received for Danish Patent Application No. PA201670627, dated Nov. 29, 2018, 2 pages.
Decision to Grant received for Danish Patent Application No. PA201670753, dated Mar. 6, 2019, 2 pages.
Decision to Grant received for Danish Patent Application No. PA201670755, dated Mar. 6, 2019, 2 pages.
Decision to Grant received for Danish Patent Application No. PA201870362, dated May 15, 2020, 2 pages.
Decision to Grant received for Danish Patent Application No. PA201970601, dated Feb. 3, 2021, 2 pages.
Decision to Grant received for Danish Patent Application No. PA201970603, dated May 21, 2021, 2 pages.
Decision to Grant received for European Patent Application No. 15712218.5, dated Jun. 7, 2018, 2 pages.
Decision to Grant received for European Patent Application No. 18176890.4, dated Jul. 9, 2020, 3 pages.
Decision to Grant received for European Patent Application No. 18183054.8, dated Jan. 21, 2021, 3 pages.
Decision to Grant received for European Patent Application No. 18209460.7, dated Apr. 9, 2021, 2 pages.
Decision to Grant received for European Patent Application No. 18214698.5, dated Sep. 10, 2020, 3 pages.
Decision to Grant received for Japanese Patent Application No. 2018-243463, dated Aug. 17, 2020, 2 pages.
Decision to Grant received for Japanese Patent Application No. 2020-070418, dated Feb. 8, 2021, 3 pages.
Decision to Grant received for Japanese Patent Application No. 2020-184470, dated Jul. 1, 2021, 3 pages.
Decision to Grant received for Japanese Patent Application No. 2020-184471, dated Jul. 1, 2021, 3 pages.
Decision to Grant received for Japanese Patent Application No. 2021-051385, dated Jul. 8, 2021, 3 pages.
Decision to Refuse received for European Patent Application No. 17184710.6, dated Jun. 16, 2020, 9 pages.
Decision to Refuse received for European Patent Application No. 19724959.2, dated Jun. 22, 2021, 13 pages.
Decision to Refuse received for Japanese Patent Application No. 2018-225131, dated Jul. 8, 2019, 6 pages.
Decision to Refuse received for Japanese Patent Application No. 2018-243463, dated Jul. 8, 2019, 5 pages.
Decision to Refuse received for Japanese Patent Application No. 2018-545502, dated Jul. 8, 2019, 5 pages.
Digital Trends, “ModiFace Partners with Samsung to Bring AR Makeup to the Galaxy S9”, Available online at: https://www.digitaltrends.com/mobile/modiface-samsung-partnership-ar-makeup-galaxy-s9/, 2018, 16 pages.
European Search Report received for European Patent Application No. 18209460.7, dated Mar. 15, 2019, 4 pages.
European Search Report received for European Patent Application No. 18214698.5, dated Mar. 21, 2019, 5 pages.
European Search Report received for European Patent Application No. 20206196.6, dated Dec. 8, 2020, 4 pages.
European Search Report received for European Patent Application No. 20206197.4, dated Nov. 30, 2020, 4 pages.
European Search Report received for European Patent Application No. 20210373.5, dated Apr. 13, 2021, 4 pages.
European Search Report received for European Patent Application No. 21157252.4, dated Apr. 16, 2021, 4 pages.
European Search Report received for European Patent Application No. 21163791.3, dated May 6, 2021, 5 pages.
Examiner Initiated-Interview Summary received for U.S. Appl. No. 16/528,941, dated Dec. 1, 2020, 2 pages.
Examiner's Answer to Appeal Brief received for U.S. Appl. No. 15/995,040, dated Jun. 23, 2021, 31 pages.
Examiner's Answer to Appeal Brief received for U.S. Appl. No. 16/144,629, dated Jul. 21, 2021, 21 pages.
Extended European Search Report (includes Supplementary European Search Report and Search Opinion) received for European Patent Application No. 17184710.6, dated Nov. 28, 2017, 10 pages.
Extended European Search Report received for European Patent Application No. 16784025.5, dated Apr. 16, 2018, 11 pages.
Extended European Search Report received for European Patent Application No. 19204230.7, dated Feb. 21, 2020, 7 pages.
Extended European Search Report received for European Patent Application No. 20166552.8, dated Jun. 12, 2020, 9 pages.
Extended European Search Report received for European Patent Application No. 20168009.7, dated Sep. 11, 2020, 12 pages.
Extended European Search Report received for European Patent Application No. 20205496.1, dated Mar. 11, 2021, 11 pages.
Extended Search Report received for European Patent Application 17809168.2, dated Jun. 28, 2018, 9 pages.
Fedko Daria, “AR Hair Styles”, Online Available at <https://www.youtube.com/watch?v=FrS6tHRbFE0>, Jan. 24, 2017, 2 pages.
Feng et al., “3D Direct Human-Computer Interface Paradigm Based on Free Hand Tracking”, Chinese Journal of Computers, vol. 37, No. 6, Jun. 30, 2014, 15 pages.
Final Office Action received for U.S. Patent Application No. 15/268,115, dated Oct. 11, 2017, 48 pages.
Final Office Action received for U.S. Appl. No. 15/728,147, dated Aug. 29, 2018, 39 pages.
Final Office Action received for U.S. Appl. No. 15/728,147, dated May 28, 2019, 45 pages.
Final Office Action received for U.S. Appl. No. 15/995,040, dated Oct. 17, 2019, 20 pages.
Final Office Action received for U.S. Appl. No. 15/995,040, dated Sep. 2, 2020, 21 pages.
Final Office Action received for U.S. Appl. No. 16/143,396, dated Jun. 20, 2019, 14 pages.
Final Office Action received for U.S. Appl. No. 16/144,629, dated Sep. 11, 2020, 22 pages.
Final Office Action received for U.S. Appl. No. 16/144,629, dated Sep. 18, 2019, 22 pages.
Final Office Action received for U.S. Appl. No. 16/271,583, dated Aug. 26, 2020, 18 pages.
Final Office Action received for U.S. Appl. No. 16/528,941, dated Jul. 13, 2020, 15 pages.
Franks Tech Help,“DSLR Camera Remote Control on Android Tablet, DSLR Dashboard, Nexus 10, Canon Camera, OTG Host Cable”, Available online at: https://www.youtube.com/watch?v=DD4dCVinreU, Dec. 10, 2013, 1 page.
Fuji Film, “Taking Pictures Remotely: Free iPhone/Android App Fuji Film Camera Remote”, Available at <http://app.fujifilm-dsc.com/en/camera_remote/guide05.html>, Apr. 22, 2014, 3 pages.
Gadgets Portal, “Galaxy J5 Prime Camera Review! (vs J7 Prime) 4K”, Available Online at: https://www.youtube.com/watch?v=Rf2Gy8QmDqc, Oct. 24, 2016, 3 pages.
Gavin's Gadgets, “Honor 10 Camera App Tutorial—How to use All Modes + 90 Photos Camera Showcase”, See Especially 2:58-4:32, Available Online at <https://www.youtube.com/watch?v=M5XZwXJcK74>, May 26, 2018, 3 pages.
Gibson Andrews, “Aspect Ratio: What it is and Why it Matters”, Retrieved from <https://web.archive.org/web/20190331225429/https:/digital-photography-school.com/aspect-ratio-what-it-is-and-why-it-matters/>, Paragraphs: “Adjusting aspect ratio in-camera”, “Cropping in post-processing”, Mar. 31, 2019, 10 pages.
GSM Arena, “Honor 10 Review: Camera”, Available Online at: <https://web.archive.org/web/20180823142417/https://www.gsmarena.com/honor_10-review-1771p5.php>, Aug. 23, 2018, 11 pages.
Hall Brent, “Samsung Galaxy Phones Pro Mode (S7/S8/S9/Note 8/Note 9): When, why, & How yo Use It”, See Especially 3:18-5:57, Available Online at <https://www.youtube.com/watch?v=KwPxGUDRkTg>, Jun. 19, 2018, 3 pages.
Helpvideostv, “How to Use Snap Filters on Snapchat”, Retrieved from <https://www.youtube.com/watch?v=oR-7cIWPszU&feature=youtu.be>, Mar. 22, 2017, pp. 1-2.
Hernández Carlos, “Lens Blur in the New Google Camera App”, Available online at: https://research.googleblog.com/2014/04/lens-blur-in-new-google-camera-app.html, https://ai.googleblog.com/2014/04/lens-blur-in-new-google-camera-app.html, Apr. 16, 2014, 6 pages.
Huawei Mobile PH, “Huawei P10 Tips & Tricks: Compose Portraits with Wide Aperture (Bokeh)”, Available Online at <https://www.youtube.com/watch?v=WM4yo5-hrrE>, Mar. 30, 2017, 2 pages.
Iluvtrading, “Galaxy S10 / S10+: How to Use Bright Night Mode for Photos (Super Night Mode)”, Online Available at: https://www.youtube.com/watch?v=SfZ7Us1S1Mk, Mar. 11, 2019, 4 pages.
Iluvtrading, “Super Bright Night Mode: Samsung Galaxy S1O vs Huawei P30 Pro (Review/How to/Explained)”, Online Available at: https://www.youtube.com/watch?v=d4r3PWioY4Y, Apr. 26, 2019, 4 pages.
Imagespacetv, “Olympus OM-D E-M1 Mark II—Highlights & Shadows with Gavin Hoey”, Online available at: https://www.youtube.com/watch?v=goEhh1n--hQ, Aug. 3, 2018, 3 pages.
Intention to Grant received for Danish Patent Application No. PA201570788, dated Mar. 27, 2017, 2 pages.
Intention to Grant received for Danish Patent Application No. PA201570791, dated Mar. 7, 2017, 2 pages.
Intention to Grant received for Danish Patent Application No. PA201670627, dated Jun. 11, 2018, 2 pages.
Intention to Grant received for Danish Patent Application No. PA201670753, dated Oct. 29, 2018, 2 pages.
Intention to Grant received for Danish Patent Application No. PA201670755, dated Nov. 13, 2018, 2 pages.
Intention to Grant received for Danish Patent Application No. PA201870362, dated Feb. 14, 2020, 2 pages.
Intention to Grant received for Danish Patent Application No. PA201970593, dated Apr. 13, 2021, 2 pages.
Intention to Grant received for Danish Patent Application No. PA201970601, dated Sep. 21, 2020, 2 pages.
Intention to Grant received for Danish Patent Application No. PA201970603, dated Jan. 13, 2021, 2 pages.
Intention to Grant received for Danish Patent Application No. PA202070611, dated May 5, 2021, 2 pages.
Intention to Grant received for European Patent Application No. 15712218.5, dated Jan. 24, 2018, 7 pages.
Intention to Grant received for European Patent Application No. 16784025.5, dated Jul. 15, 2021, 8 pages.
Intention to Grant received for European Patent Application No. 17809168.2, dated Jun. 25, 2021, 8 pages.
Intention to Grant received for European Patent Application No. 18176890.4, dated Feb. 28, 2020, 8 pages.
Intention to Grant received for European Patent Application No. 18183054.8, dated Nov. 5, 2020, 6 pages.
Intention to Grant received for European Patent Application No. 18209460.7, dated Jan. 15, 2021, 8 pages.
Intention to Grant received for European Patent Application No. 18214698.5, dated Apr. 21, 2020, 8 pages.
International Preliminary Report on Patentability and Written Opinion received for PCT Application No. PCT/US2016/029030, dated Nov. 2, 2017, 35 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/019298, dated Mar. 16, 2017, 12 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/035321, dated Dec. 27, 2018, 11 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2018/015591, dated Dec. 19, 2019, 10 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2018/048151, dated Apr. 9, 2020, 14 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/017363, dated Aug. 20, 2020, 9 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/024067, dated Nov. 19, 2020, 12 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/031202, dated Nov. 19, 2020, 13 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/049101, dated Mar. 25, 2021, 17 pages.
International Search Report & Written Opinion received for PCT Patent Application No. PCT/US2016/029030, dated Aug. 5, 2016, 37 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/019298, dated Jul. 13, 2015, 17 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/035321, dated Oct. 6, 2017, 15 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2018/015591, dated Jun. 14, 2018, 14 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2018/048151, dated Jan. 10, 2019, 23 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/017363, dated Aug. 12, 2019, 12 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/024067, dated Oct. 9, 2019, 18 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/031202, dated Oct. 4, 2019, 19 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/049101, dated Dec. 16, 2019, 26 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/031643, dated Dec. 2, 2020, 33 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/031643, dated Nov. 2, 2020, 34 pages.
Invitation to Pay Addition Fees received for PCT Patent Application No. PCT/US2017/035321, dated Aug. 17, 2017, 3 pages.
Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2019/049101, dated Oct. 24, 2019, 17 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2018/048151, dated Nov. 6, 2018, 18 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/017363, dated Jun. 17, 2019, 8 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/024067, dated Jul. 16, 2019, 13 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/031202, dated Aug. 8, 2019, 12 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/031643, dated Sep. 9, 2020, 30 pages.
Invitation to Pay Search Fees received for European Patent Application No. 18704732.9, dated Jun. 2, 2021, 3 pages.
Invitation to Pay Search Fees received for European Patent Application No. 19724959.2, dated Feb. 25, 2020, 3 pages.
“iPhone User Guide for iOS 4.2 and 4.3 Software”, Available at: https://manuals.info.apple.com/Manuals/1000/MA1539/en_US/iPhone_iOS4_User_Guide.pdf, 2011, 274 pages.
Johnson Dave, “What is the Clips app on an iPhone?': How to use your iPhone's free video-editing app, and make custom videos for social media”, Available online at: https://www.businessinsidercom/what-is-clips-on-iphone?IR=T, Oct. 26, 2019, 14 pages.
KK World, “Redmi Note 7 Pro Night Camera Test I Night Photography with Night Sight & Mode”, Online Available at: https:/lwww.youtube.com/watch?v=3EKjGBjX3PY, Mar. 26, 2019, 4 pages.
Kozak Tadeusz, “When You're Video Chatting on Snapchat, How Do You Use Face Filters?”, Quora, Online Available at: https://www.quora.com/When-youre-video-chatting-on-Snapchat-how-do-you-use-face-filters, Apr. 29, 2018, 1 page.
Lang Brian, “How to Audio & Video Chat with Multiple Users at the Same Time in Groups”, Snapchat 101, Online Available at: <https://smartphones.gadgethacks.com/how-to/snapchat-101-audio-video-chat-with-multiple-users-same-time-groups-0184113/>, Apr. 17, 2018, 4 pages.
Minutes of the Oral Proceedings received for European Patent Application No. 19724959.2, mailed on Jun. 14, 2021, 6 pages.
Minutes of the Oral Proceedings received for European Patent Application No. 19729395.4, mailed on Jul. 21, 2021, 6 pages.
Mobiscrub, “Galaxy S4 mini camera review”, Available Online at: https://www.youtube.com/watch?v=KYKOydw8QT8, Aug. 10, 2013, 3 pages.
Mobiscrub, “Samsung Galaxy S5 Camera Review—Hd Video”, Available Online on: https://www.youtube.com/watch?v=BFgwDtNKMjg, Mar. 27,2014, 3 pages.
Modifacechannel, “Sephora 3D Augmented Reality Mirror”, Available Online at: https://www.youtube.com/watch?v=wwBO4PU9EXI, May 15, 2014, 1 page.
Neurotechnology, “Sentimask Sdk”, Available at: https://www.neurotechnology.com/sentimask.html, Apr. 22, 2018, 5 pages.
Non-Final Office Action received for U.S. Appl. No. 16/035,422, dated Nov. 30, 2018, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 17/157,166, dated Jul. 9, 2021, 12 pages.
Non-Final Office Action received for U.S. Appl. No. 14/869,807, dated Dec. 2, 2016, 23 pages.
Non-Final Office Action received for U.S. Appl. No. 15/136,323, dated Apr. 6, 2017, 27 pages.
Non-Final Office Action received for U.S. Appl. No. 15/268,115, dated Apr. 13, 2017, 44 pages.
Non-Final Office Action received for U.S. Appl. No. 15/273,522, dated Nov. 30, 2016, 15 pages.
Non-Final Office Action received for U.S. Appl. No. 15/273,544, dated May 25, 2017, 18 pages.
Non-Final Office Action received for U.S. Appl. No. 15/728,147, dated Feb. 22, 2018, 20 pages.
Non-Final Office Action received for U.S. Appl. No. 15/728,147, dated Jan. 31, 2019, 41 pages.
Non-Final Office Action received for U.S. Appl. No. 15/863,369, dated Apr. 4, 2018, 15 pages.
Non-Final Office Action received for U.S. Appl. No. 15/995,040, dated Apr. 15, 2020, 19 pages.
Non-Final Office Action received for U.S. Appl. No. 15/995,040, dated May 16, 2019, 24 pages.
Non-Final Office Action received for U.S. Appl. No. 16/109,552, dated Oct. 17, 2018, 16 pages.
Non-Final Office Action received for U.S. Appl. No. 16/143,097, dated Feb. 28, 2019, 17 pages.
Non-Final Office Action received for U.S. Appl. No. 16/143,396, dated Jan. 7, 2019, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 16/144,572, dated Nov. 30, 2018, 8 pages.
Non-Final Office Action received for U.S. Appl. No. 16/144,629, dated Mar. 13, 2020, 24 pages.
Non-Final Office Action received for U.S. Appl. No. 16/144,629, dated Mar. 29, 2019, 18 pages.
Non-Final Office Action received for U.S. Appl. No. 16/271,583, dated May 6, 2020, 24 pages.
Non-Final Office Action received for U.S. Appl. No. 16/271,583, dated Nov. 29, 2019, 18 pages.
Non-Final Office Action received for U.S. Appl. No. 16/383,403, dated Aug. 23, 2019, 10 pages.
Non-Final Office Action received for U.S. Appl. No. 16/528,941, dated Dec. 7, 2020, 15 pages.
Non-Final Office Action received for U.S. Appl. No. 16/528,941, dated Jan. 30, 2020, 14 pages.
Non-Final Office Action received for U.S. Appl. No. 16/582,595, dated Nov. 26, 2019, 17 pages.
Non-Final Office Action received for U.S. Appl. No. 16/583,020, dated Nov. 14, 2019, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 16/599,433, dated Jan. 28, 2021, 16 pages.
Non-Final Office Action received for U.S. Appl. No. 16/733,718, dated Sep. 16, 2020, 25 pages.
Non-Final Office Action received for U.S. Appl. No. 16/790,619, dated May 4, 2020, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 16/799,481, dated May 1, 2020, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 16/825,879, dated May 5, 2021, 12 pages.
Non-Final Office Action received for U.S. Appl. No. 17/027,317, dated Nov. 17, 2020, 17 pages.
Non-Final Office Action received for U.S. Appl. No. 17/121,610, dated May 13, 2021, 17 pages.
Notice of Acceptance received for Australian Patent Application No. 2016252993, dated Dec. 19, 2017, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2017286130, dated Apr. 26, 2019, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2018279787, dated Dec. 10, 2019, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2019213341, dated Aug. 25, 2020, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2019266049, dated Nov. 24, 2020, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2019266225, dated Dec. 23, 2020, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2020201969, dated Mar. 26, 2021, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2020267151, dated Dec. 9, 2020, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2020277216, dated Mar. 15, 2021, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2021200789, dated Feb. 26, 2021, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2021201167, dated Mar. 15, 2021, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2021203210, dated Jul. 9, 2021, 3 pages.
Notice of Allowance received for Brazilian Patent Application No. 112018074765-3, dated Oct. 8, 2019, 2 pages.
Notice of Allowance received for Chinese Patent Application No. 201580046237.6, dated Aug. 29, 2018, 4 pages.
Notice of Allowance received for Chinese Patent Application No. 201680023520.1, dated Jun. 28, 2019, 2 pages.
Notice of Allowance received for Chinese Patent Application No. 201710657424.9, dated May 8, 2020, 2 pages.
Notice of Allowance received for Chinese Patent Application No. 201780002533.5, dated Apr. 14, 2020, 2 pages.
Notice of Allowance received for Chinese Patent Application No. 201810566134.8, dated Apr. 7, 2020, 3 pages.
Notice of Allowance received for Chinese Patent Application No. 201810664927.3, dated Jul. 19, 2019, 2 pages.
Notice of Allowance received for Chinese Patent Application No. 201811512767.7, dated Jul. 27, 2020, 4 pages.
Notice of Allowance received for Chinese Patent Application No. 201880056514.5, dated Jan. 11, 2021, 2 pages.
Notice of Allowance received for Chinese Patent Application No. 201910400180.5, dated Nov. 5, 2020, 2 pages.
Notice of Allowance received for Chinese Patent Application No. 201910692978.1, dated Feb. 4, 2021, 6 pages.
Notice of Allowance received for Chinese Patent Application No. 201910864074.2, dated Mar. 10, 2021, 2 pages.
Notice of Allowance received for Chinese Patent Application No. 201911202668.3, dated Feb. 4, 2021, 5 pages.
Notice of Allowance received for Chinese Patent Application No. 201911219525.3, dated Sep. 29, 2020, 2 pages.
Notice of Allowance received for Chinese Patent Application No. 202010287953.6, dated Mar. 18, 2021, 7 pages.
Notice of Allowance received for Chinese Patent Application No. 202010287961.0, dated Mar. 9, 2021, 8 pages.
Notice of Allowance received for Chinese Patent Application No. 202010287975.2, dated Mar. 1, 2021, 7 pages.
Notice of Allowance received for Japanese Patent Application No. 2018-171188, dated Jul. 16, 2019, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2018-183504, dated Sep. 27, 2019, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2018-7026743, dated Mar. 20, 2019, 7 pages.
Notice of Allowance received for Korean Patent Application No. 10-2018-7028849, dated Feb. 1, 2019, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2018-7034780, dated Jun. 19, 2019, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2018-7036893, dated Jun. 12, 2019, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2019-7027042, dated Nov. 26, 2020, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2019-7035478, dated Apr. 24, 2020, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2020-0052618, dated Mar. 23, 2021, 5 pages.
Notice of Allowance received for Korean Patent Application No. 10-2020-0143726, dated Nov. 10, 2020, 5 pages.
Notice of Allowance received for Korean Patent Application No. 10-2020-0155924, dated Nov. 23, 2020, 7 pages.
Notice of Allowance received for Korean Patent Application No. 10-2020-7021870, dated Apr. 26, 2021, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2020-7031855, dated Mar. 22, 2021, 5 pages.
Notice of Allowance received for Korean Patent Application No. 10-2020-7032110, dated Mar. 8, 2021, 4 pages.
Notice of Allowance received for Korean Patent Application No. 10-2021-7019525, dated Jul. 13, 2021, 5 pages.
Notice of Allowance received for Taiwanese Patent Application No. 104107328, dated Jun. 12, 2017, 3 pages.
Notice of Allowance received for U.S. Appl. No. 16/035,422, dated Apr. 10, 2019, 6 pages.
Notice of Allowance received for U.S. Appl. No. 16/528,941, dated Aug. 10, 2021, 5 pages.
Notice of Allowance received for U.S. Appl. No. 16/528,941, dated May 19, 2021, 5 pages.
Notice of Allowance received for U.S. Appl. No. 14/641,251, dated May 18, 2016, 13 pages.
Notice of Allowance received for U.S. Appl. No. 14/869,807, dated Jun. 21, 2017, 9 pages.
Notice of Allowance received for U.S. Appl. No. 14/869,807, dated Oct. 10, 2017, 9 pages.
Notice of Allowance received for U.S. Appl. No. 15/136,323, dated Feb. 28, 2016, 9 pages.
Notice of Allowance received for U.S. Appl. No. 15/136,323, dated Oct. 12, 2017, 8 pages.
Notice of Allowance received for U.S. Appl. No. 15/268,115, dated Mar. 7, 2018, 15 pages.
Notice of Allowance received for U.S. Appl. No. 15/273,453, dated Oct. 12, 2017, 11 pages.
Notice of Allowance received for U.S. Appl. No. 15/273,503, dated Aug. 14, 2017, 9 pages.
Notice of Allowance received for U.S. Appl. No. 15/273,522, dated Mar. 28, 2017, 9 pages.
Notice of Allowance received for U.S. Appl. No. 15/273,522, dated May 19, 2017, 2 pages.
Notice of Allowance received for U.S. Appl. No. 15/273,522, dated May 23, 2017, 2 pages.
Notice of Allowance received for U.S. Appl. No. 15/273,544, dated Mar. 13, 2018, 8 pages.
Notice of Allowance received for U.S. Appl. No. 15/273,544, dated Oct. 27, 2017, 8 pages.
Notice of Allowance received for U.S. Appl. No. 15/728,147, dated Aug. 19, 2019, 13 pages.
Notice of Allowance received for U.S. Appl. No. 15/858,175, dated Jun. 1, 2018, 8 pages.
Notice of Allowance received for U.S. Appl. No. 15/858,175, dated Sep. 12, 2018, 8 pages.
Notice of Allowance received for U.S. Appl. No. 15/863,369, dated Jun. 28, 2018, 8 pages.
Notice of Allowance received for U.S. Appl. No. 15/975,581, dated Oct. 3, 2018, 25 pages.
Notice of Allowance received for U.S. Appl. No. 16/109,552, dated Mar. 13, 2019, 25 pages.
Notice of Allowance received for U.S. Appl. No. 16/109,552, dated May 13, 2019, 2 pages.
Notice of Allowance received for U.S. Appl. No. 16/110,514, dated Apr. 29, 2019, 9 pages.
Notice of Allowance received for U.S. Appl. No. 16/110,514, dated Mar. 13, 2019, 11 pages.
Notice of Allowance received for U.S. Appl. No. 16/143,097, dated Aug. 29, 2019, 23 pages.
Notice of Allowance received for U.S. Appl. No. 16/143,201, dated Feb. 8, 2019, 9 pages.
Notice of Allowance received for U.S. Appl. No. 16/143,201, dated Nov. 28, 2018, 14 pages.
Notice of Allowance received for U.S. Appl. No. 16/143,396, dated Nov. 27, 2019, 8 pages.
Notice of Allowance received for U.S. Appl. No. 16/144,572, dated Feb. 28, 2019, 7 pages.
Notice of Allowance received for U.S. Appl. No. 16/147,432, dated Dec. 18, 2018, 13 pages.
Notice of Allowance received for U.S. Appl. No. 16/147,432, dated May 20, 2019, 6 pages.
Notice of Allowance received for U.S. Appl. No. 16/191,117, dated Oct. 29, 2019, 9 pages.
Notice of Allowance received for U.S. Appl. No. 16/271,583, dated Apr. 14, 2021, 6 pages.
Notice of Allowance received for U.S. Appl. No. 16/271,583, dated Dec. 9, 2020, 6 pages.
Notice of Allowance received for U.S. Appl. No. 16/271,583, dated Jul. 23, 2021, 6 pages.
Notice of Allowance received for U.S. Appl. No. 16/271,583, dated May 10, 2021, 3 pages.
Notice of Allowance received for U.S. Appl. No. 16/383,403, dated Jan. 10, 2020, 11 pages.
Notice of Allowance received for U.S. Appl. No. 16/511,578, dated Nov. 18, 2019, 12 pages.
Notice of Allowance received for U.S. Appl. No. 16/582,595, dated Mar. 20, 2020, 9 pages.
Notice of Allowance received for U.S. Appl. No. 16/583,020, dated Apr. 1, 2020, 5 pages.
Notice of Allowance received for U.S. Appl. No. 16/583,020, dated Feb. 28, 2020, 5 pages.
Notice of Allowance received for U.S. Appl. No. 16/584,044, dated Dec. 11, 2019, 15 pages.
Notice of Allowance received for U.S. Appl. No. 16/584,044, dated Mar. 30, 2020, 16 pages.
Notice of Allowance received for U.S. Appl. No. 16/584,044, dated Nov. 14, 2019, 13 pages.
Notice of Allowance received for U.S. Appl. No. 16/584,100, dated Apr. 8, 2020, 12 pages.
Notice of Allowance received for U.S. Appl. No. 16/584,100, dated Jan. 14, 2020, 13 pages.
Notice of Allowance received for U.S. Appl. No. 16/584,693, dated Jan. 15, 2020, 15 pages.
Notice of Allowance received for U.S. Appl. No. 16/584,693, dated May 4, 2020, 12 pages.
Notice of Allowance received for U.S. Appl. No. 16/586,314, dated Apr. 1, 2020, 8 pages.
Notice of Allowance received for U.S. Appl. No. 16/586,314, dated Jan. 9, 2020, 10 pages.
Notice of Allowance received for U.S. Appl. No. 16/586,344, dated Dec. 16, 2019, 12 pages.
Notice of Allowance received for U.S. Appl. No. 16/586,344, dated Mar. 27, 2020, 12 pages.
Notice of Allowance received for U.S. Appl. No. 16/599,433, dated May 14, 2021, 11 pages.
Notice of Allowance received for U.S. Appl. No. 16/733,718, dated Feb. 5, 2021, 14 pages.
Notice of Allowance received for U.S. Appl. No. 16/790,619, dated Sep. 8, 2020, 6 pages.
Notice of Allowance received for U.S. Appl. No. 16/799,481, dated Sep. 8, 2020, 6 pages.
Notice of Allowance received for U.S. Appl. No. 16/825,879, dated Jul. 13, 2021, 9 pages.
Notice of Allowance received for U.S. Appl. No. 16/835,651, dated Jul. 23, 2021, 8 pages.
Notice of Allowance received for U.S. Appl. No. 16/835,651, dated Jun. 1, 2021, 10 pages.
Notice of Allowance received for U.S. Appl. No. 16/840,719, dated Apr. 30, 2021, 13 pages.
Notice of Allowance received for U.S. Appl. No. 17/027,317, dated Apr. 12, 2021, 7 pages.
Notice of Allowance received for U.S. Appl. No. 17/027,317, dated Jan. 13, 2021, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/027,484, dated May 3, 2021, 11 pages.
Office Action received for Australian Patent Application No. 2017100683, dated Sep. 20, 2017, 3 pages.
Office Action received for Australian Patent Application No. 2017100684, dated Jan. 24, 2018, 4 pages.
Office Action received for Australian Patent Application No. 2017100684, dated Oct. 5, 2017, 4 pages.
Office Action Received for Australian Patent Application No. 2017286130, dated Jan. 21, 2019, 4 pages.
Office Action received for Australian Patent Application No. 2019100499, dated Jun. 28, 2019, 4 pages.
Office Action received for Australian Patent Application No. 2019100794, dated Oct. 3, 2019, 4 pages.
Office Action received for Australian Patent Application No. 2019101062, dated Apr. 22, 2020, 2 pages.
Office Action received for Australian Patent Application No. 2019101062, dated Dec. 5, 2019, 3 pages.
Office Action received for Australian Patent Application No. 2019213341, dated Jun. 30, 2020, 6 pages.
Office Action received for Australian Patent Application No. 2019218241, dated Apr. 1, 2021, 3 pages.
Office Action received for Australian Patent Application No. 2019266225, dated Nov. 23, 2020, 4 pages.
Office Action received for Australian Patent Application No. 2020100189, dated Apr. 1, 2020, 3 pages.
Office Action received for Australian Patent Application No. 2020100720, dated Jul. 9, 2020, 7 pages.
Office Action received for Australian Patent Application No. 2020100720, dated Sep. 1, 2020, 5 pages.
Office Action received for Australian Patent Application No. 2020101043, dated Aug. 14, 2020, 5 pages.
Office Action received for Australian Patent Application No. 2020101043, dated Oct. 30, 2020, 4 pages.
Office Action received for Australian Patent Application No. 2020201969, dated Sep. 25, 2020, 5 pages.
Office Action received for Australian Patent Application No. 2020239717, dated Jun. 23, 2021, 7 pages.
Office Action received for Australian Patent Application No. 2020260413, dated Jun. 24, 2021, 2 pages.
Office Action received for Australian Patent Application No. 2020277216, dated Dec. 17, 2020, 5 pages.
Office Action received for Chinese Patent Application No. 201580046237.6, dated Feb. 6, 2018, 10 pages.
Office Action received for Chinese Patent Application No. 201680023520.1, dated Jan. 3, 2019, 10 pages.
Office Action received for Chinese Patent Application No. 201710657424.9, dated Sep. 17, 2019, 23 pages.
Office Action received for Chinese Patent Application No. 201780002533.5, dated Apr. 25, 2019, 17 pages.
Office Action received for Chinese Patent Application No. 201780002533.5, dated Feb. 3, 2020, 6 pages.
Office Action received for Chinese Patent Application No. 201780002533.5, dated Sep. 26, 2019, 21 pages.
Office Action received for Chinese Patent Application No. 201810566134.8, dated Aug. 13, 2019, 14 pages.
Office Action received for Chinese Patent Application No. 201810664927.3, dated Mar. 28, 2019, 11 pages.
Office Action received for Chinese Patent Application No. 201811446867.4, dated Dec. 31, 2019, 12 pages.
Office Action received for Chinese Patent Application No. 201811446867.4, dated May 6, 2020, 10 pages.
Office Action received for Chinese Patent Application No. 201811446867.4, dated Sep. 8, 2020, 9 pages.
Office Action received for Chinese Patent Application No. 201811512767.7, dated Dec. 20, 2019, 14 pages.
Office Action received for Chinese Patent Application No. 201811512767.7, dated Jun. 4, 2020, 6 pages.
Office Action received for Chinese Patent Application No. 201880056514.5, dated Sep. 2, 2020, 7 pages.
Office Action received for Chinese Patent Application No. 201910400180.5, dated Jun. 1, 2020, 11 pages.
Office Action received for Chinese Patent Application No. 201910692978.1, dated Apr. 3, 2020, 19 pages.
Office Action received for Chinese Patent Application No. 201910692978.1, dated Nov. 4, 2020, 4 pages.
Office Action received for Chinese Patent Application No. 201910704856.X, dated Apr. 6, 2021, 13 pages.
Office Action received for Chinese Patent Application No. 201910704856.X, dated Dec. 9, 2020, 23 pages.
Office Action received for Chinese Patent Application No. 201910704856.X, dated May 27, 2020, 26 pages.
Office Action received for Chinese Patent Application No. 201910864074.2, dated Sep. 23, 2020, 11 pages.
Office Action received for Chinese Patent Application No. 201911202668.3, dated Aug. 4, 2020, 13 pages.
Office Action received for Chinese Patent Application No. 201911219525.3, dated Jul. 10, 2020, 7 pages.
Office Action received for Chinese Patent Application No. 202010126661.4, dated Feb. 3, 2021, 16 pages.
Office Action received for Chinese Patent Application No. 202010218168.5, dated Feb. 9, 2021, 21 pages.
Office Action received for Chinese Patent Application No. 202010287950.2, dated Feb. 20, 2021, 22 pages.
Office Action received for Chinese Patent Application No. 202010287953.6, dated Jan. 14, 2021, 14 pages.
Office Action received for Chinese Patent Application No. 202010287958.9, dated Jan. 5, 2021, 16 pages.
Office Action received for Chinese Patent Application No. 202010287961.0, dated Dec. 30, 2020, 16 pages.
Office Action received for Chinese Patent Application No. 202010287975.2, dated Dec. 30, 2020, 17 pages.
Office Action received for Chinese Patent Application No. 202010600151.6, dated Apr. 29, 2021, 11 pages.
Office Action received for Chinese Patent Application No. 202010601484.0, dated Jun. 3, 2021, 13 pages.
Office Action received for Chinese Patent Application No. 202011243876.0, dated Apr. 6, 2021, 11 pages.
Office Action received for Danish Patent Application No. PA201570788, dated Apr. 8, 2016, 11 pages.
Office Action received for Danish Patent Application No. PA201570788, dated Sep. 13, 2016, 3 pages.
Office action received for Danish Patent Application No. PA201570791, dated Apr. 6, 2016, 12 pages.
Office action received for Danish Patent Application No. PA201570791, dated Sep. 6, 2016, 4 pages.
Office Action received for Danish Patent Application No. PA201670627, dated Apr. 5, 2017, 3 pages.
Office Action received for Danish Patent Application No. PA201670627, dated Nov. 6, 2017, 2 pages.
Office Action received for Danish Patent Application No. PA201670627, dated Oct. 11, 2016, 8 pages.
Office Action received for Danish Patent Application No. PA201670753, dated Dec. 20, 2016, 7 pages.
Office Action received for Danish Patent Application No. PA201670753, dated Jul. 5, 2017, 4 pages.
Office Action received for Danish Patent Application No. PA201670753, dated Mar. 23, 2018, 5 pages.
Office Action received for Danish Patent Application No. PA201670755, dated Apr. 6, 2017, 5 pages.
Office Action received for Danish Patent Application No. PA201670755, dated Apr. 20, 2018, 2 pages.
Office Action received for Danish Patent Application No. PA201670755, dated Dec. 22, 2016, 6 pages.
Office Action received for Danish Patent Application No. PA201670755, dated Oct. 20, 2017, 4 pages.
Office Action received for Danish Patent Application No. PA201770563, dated Aug. 13, 2018, 5 pages.
Office Action received for Danish Patent Application No. PA201770563, dated Jan. 28, 2020, 3 pages.
Office Action received for Danish Patent Application No. PA201770563, dated Jun. 28, 2019, 5 pages.
Office Action received for Danish Patent Application No. PA201770719, dated Aug. 14, 2018, 6 pages.
Office Action received for Danish Patent Application No. PA201770719, dated Feb. 19, 2019, 4 pages.
Office Action received for Danish Patent Application No. PA201770719, dated Jan. 17, 2020, 4 pages.
Office Action received for Danish Patent Application No. PA201770719, dated Jun. 30, 2021, 3 pages.
Office Action received for Danish Patent Application No. PA201770719, dated Nov. 16, 2020, 5 pages.
Office Action received for Danish Patent Application No. PA201870362, dated Aug. 22, 2019, 4 pages.
Office Action received for Danish Patent Application No. PA201870362, dated Dec. 18, 2018, 2 pages.
Office Action received for Danish Patent Application No. PA201870363, dated Mar. 26, 2019, 3 pages.
Office Action received for Danish Patent Application No. PA201870364, dated Jan. 28, 2019, 8 pages.
Office Action received for Danish Patent Application No. PA201870364, dated Jun. 11, 2019, 11 pages.
Office Action received for Danish Patent Application No. PA201870366, dated Aug. 22, 2019, 3 pages.
Office Action received for Danish Patent Application No. PA201870366, dated Dec. 12, 2018, 3 pages.
Office Action received for Danish Patent Application No. PA201870367, dated Dec. 20, 2018, 5 pages.
Office Action received for Danish Patent Application No. PA201870368, dated Dec. 20, 2018, 5 pages.
Office Action received for Danish Patent Application No. PA201870368, dated Oct. 1, 2019, 6 pages.
Office Action received for Danish Patent Application No. PA201870623, dated Jan. 30, 2020, 2 pages.
Office Action received for Danish Patent Application No. PA201870623, dated Jul. 12, 2019, 4 pages.
Office Action received for Danish Patent Application No. PA201970592, dated Mar. 2, 2020, 5 pages.
Office Action received for Danish Patent Application No. PA201970592, dated Oct. 26, 2020, 5 pages.
Office Action received for Danish Patent Application No. PA201970593, dated Apr. 16, 2020, 2 pages.
Office Action received for Danish Patent Application No. PA201970593, dated Feb. 2, 2021, 2 pages.
Office Action received for Danish Patent Application No. PA201970593, dated Mar. 10, 2020, 4 pages.
Office Action received for Danish Patent Application No. PA201970595, dated Mar. 10, 2020, 4 pages.
Office Action received for Danish Patent Application No. PA201970600, dated Mar. 9, 2020, 5 pages.
Office Action received for Danish Patent Application No. PA201970601, dated Aug. 13, 2020, 3 pages.
Office Action received for Danish Patent Application No. PA201970601, dated Jan. 31, 2020, 3 pages.
Office Action received for Danish Patent Application No. PA201970601, dated Nov. 11, 2019, 8 pages.
Office Action received for Danish Patent Application No. PA201970603, dated Nov. 4, 2020, 3 pages.
Office Action received for Danish Patent Application No. PA201970605, dated Mar. 10, 2020, 5 pages.
Office Action received for Danish Patent Application No. PA202070611, dated Dec. 22, 2020, 7 pages.
Office Action received for European Patent Application 17809168.2, dated Jan. 7, 2020, 5 pages.
Office Action received for European Patent Application 17809168.2, dated Oct. 8, 2020, 4 pages.
Office Action received for European Patent Application No. 15712218.5, dated Aug. 3, 2017, 4 pages.
Office Action received for European Patent Application No. 16784025.5, dated Jul. 17, 2020, 6 pages.
Office Action received for European Patent Application No. 17184710.6, dated Dec. 21, 2018, 7 pages.
Office Action received for European Patent Application No. 18176890.4, dated Oct. 16, 2018, 8 pages.
Office Action received for European Patent Application No. 18183054.8, dated Feb. 24, 2020, 6 pages.
Office Action received for European Patent Application No. 18183054.8, dated Nov. 16, 2018, 8 pages.
Office Action received for European Patent Application No. 18209460.7, dated Apr. 10, 2019, 7 pages.
Office Action received for European Patent Application No. 18209460.7, dated Apr. 21, 2020, 5 pages.
Office Action received for European Patent Application No. 18214698.5, dated Apr. 2, 2019, 8 pages.
Office Action received for European Patent Application No. 18779093.6, dated Dec. 11, 2020, 4 pages.
Office Action received for European Patent Application No. 19204230.7, dated Sep. 28, 2020, 6 pages.
Office Action received for European Patent Application No. 19724959.2, dated Apr. 23, 2020, 10 pages.
Office Action received for European Patent Application No. 19729395.4, dated Jul. 15, 2020, 4 pages.
Office Action received for European Patent Application No. 19729395.4, dated Sep. 29, 2020, 10 pages.
Office Action received for European Patent Application No. 20166552.8, dated Mar. 24, 2021, 8 pages.
Office Action received for European Patent Application No. 20168009.7, dated Apr. 20, 2021, 6 pages.
Office Action received for European Patent Application No. 20206196.6, dated Jan. 13, 2021, 10 pages.
Office Action received for European Patent Application No. 20206197.4, dated Jan. 12, 2021, 9 pages.
Office Action received for European Patent Application No. 20210373.5, dated May 10, 2021, 9 pages.
Office Action received for European Patent Application No. 21157252.4, dated Apr. 23, 2021, 8 pages.
Office Action received for European Patent Application No. 21163791.3, dated Jun. 2, 2021, 8 pages.
Office Action received for Indian Patent Application No. 201814036470, dated Feb. 26, 2021, 7 pages.
Office Action received for Indian Patent Application No. 201917053025, dated Mar. 19, 2021, 7 pages.
Office Action received for Indian Patent Application No. 202018006172, dated May 5, 2021, 6 pages.
Office Action received for Japanese Patent Application No. 2018-182607, dated Apr. 6, 2020, 6 pages.
Office Action received for Japanese Patent Application No. 2018-182607, dated Jul. 20, 2020, 5 pages.
Office Action received for Japanese Patent Application No. 2018-225131, dated Aug. 17, 2020, 21 pages.
Office Action received for Japanese Patent Application No. 2018-225131, dated Mar. 4, 2019, 10 pages.
Office Action received for Japanese Patent Application No. 2018-545502, dated Aug. 17, 2020, 14 pages.
Office Action received for Japanese Patent Application No. 2019-194597, dated Jan. 18, 2021, 10 pages.
Office Action received for Japanese Patent Application No. 2020-070418, dated Aug. 3, 2020, 22 pages.
Office Action received for Japanese Patent Application No. 2020-184470, dated May 10, 2021, 3 pages.
Office Action received for Japanese Patent Application No. 2020-184471, dated May 10, 2021, 3 pages.
Office Action received for Japanese Patent Application No. 2020-193703, dated Apr. 19, 2021, 4 pages.
Office Action received for Korean Patent Application No. 10-2018-7026743, dated Jan. 17, 2019, 5 pages.
Office Action received for Korean Patent Application No. 10-2018-7034780, dated Apr. 4, 2019, 11 pages.
Office Action received for Korean Patent Application No. 10-2018-7036893, dated Apr. 9, 2019, 6 pages.
Office Action received for Korean Patent Application No. 10-2019-7027042, dated May 13, 2020, 6 pages.
Office Action received for Korean Patent Application No. 10-2019-7035478, dated Jan. 17, 2020, 17 pages.
Office Action received for Korean Patent Application No. 10-2020-0052618, dated Aug. 18, 2020, 11 pages.
Office Action received for Korean Patent Application No. 10-2020-7021870, dated Nov. 11, 2020, 11 pages.
Office Action received for Korean Patent Application No. 10-2020-7031855, dated Nov. 24, 2020, 6 pages.
Office Action received for Korean Patent Application No. 10-2020-7032110, dated Dec. 15, 2020, 6 pages.
Office Action received for Korean Patent Application No. 10-2021-0022053, dated Mar. 1, 2021, 11 pages.
Office Action received for Korean Patent Application No. 10-2021-7000954, dated Jan. 28, 2021, 5 pages.
Office Action received for Taiwanese Patent Application No. 104107328, dated Dec. 28, 2016, 4 pages.
Osxdaily, “How to Zoom the Camera on iPhone”, Available Online at: https://osxdaily.com/2012/04/18/zoom-camera-iphonel, Apr. 18, 2012, 6 pages.
Paine Steve, “Samsung Galaxy Camera Detailed Overview—User Interface”, Retrieved from: <https://www.youtube.com/watch?v=td8UYSySulo&feature=youtu.be>, Sep. 18, 2012, pp. 1-2.
PC World, “How to make AR Emojis on the Samsung Galaxy S9”, You Tube, Available Online: https://www.youtube.com/watch?v=8wQICfulkz0, Feb. 25, 2018, 2 pages.
Peckham James, “What is Apple Clips? Plus we teach you how to use it”, Available online at: https://www.techradar.com/how-to/what-is-apple-clips-and-how-to-use-it, Jul. 20, 2017, 11 pages.
Phonearena, “Sony Xperia Z5 camera app and UI overview”, Retrieved from <https://www.youtube.com/watch?v=UtDzdTsmkfU&feature=youtu.be>, Sep. 8, 2015, pp. 1-3.
PlayMemories Camera Apps, “PlayMemories Camera Apps Help Guide”, Available at: <https://www.playmemoriescameraapps.com/portal/manual/IS9104-NPIA09014_00-F00002/en/index.html>, 2012, 3 pages.
Pre-Appeal Review Report received for Japanese Patent Application No. 2018-182607, dated Jan. 21, 2021, 4 pages.
PreAppeal Review Report received for Japanese Patent Application No. 2018-225131, dated Jan. 24, 2020, 8 pages.
PreAppeal Review Report received for Japanese Patent Application No. 2018-545502, dated Jan. 24, 2020, 8 pages.
“Procamera Capture the Moment”, Online Available at: http://www.procamera-app.com/procamera_manual/ProCamera_Manual_EN.pdf, Apr. 21, 2016, 63 pages.
“Remote Shot for SmartWatch 2”, Available online at: https://play.google.com/store/apps/details?id=net.watea.sw2.rshot&h1=en, Nov. 21, 2017, 3 pages.
Result of Consultation received for European Patent Application No. 17184710.6, mailed on Feb. 21, 2020, 6 pages.
Result of Consultation received for European Patent Application No. 17184710.6, mailed on Feb. 28, 2020, 3 pages.
Result of Consultation received for European Patent Application No. 19204230.7, mailed on Nov. 16, 2020, 3 pages.
Result of Consultation received for European Patent Application No. 19204230.7, mailed on Sep. 24, 2020, 5 pages.
Result of Consultation received for European Patent Application No. 19724959.2, mailed on Sep. 4, 2020, 3 pages.
Result of Consultation received for European Patent Application No. 19729395.4, mailed on Jun. 22, 2021, 3 pages.
Result of Consultation received for European Patent Application No. 19729395.4, mailed on Jun. 23, 2021, 3 pages.
Ritchie Rene, “Clips app: The ultimate guide”, Available online at: https://www.imore.com/clips, May 13, 2017, 16 pages.
Rossignol Joe, “iOS 10 Concept Simplifies Lock Screen with Collapsed Notifications”, Available online at: https://www.macrumors.com/2016/06/16/ios-10-collapsed-notifications-concept/, Jun. 16, 2016, 10 pages.
Schiffhauer Alexander, “See the Light with Night Sight”, Available online at: https://www.blog.google/products/pixel/see-light-night-sight, Nov. 14, 2018, 6 pages.
Search Report and Opinion received for Danish Patent Application No. PA201770563, dated Oct. 10, 2017, 9 pages.
Search Report and Opinion received for Danish Patent Application No. PA201870362, dated Sep. 7, 2018, 9 pages.
Search Report and Opinion received for Danish Patent Application No. PA201870363, dated Sep. 11, 2018, 12 pages.
Search Report and Opinion received for Danish Patent Application No. PA201870364, dated Sep. 4, 2018, 12 pages.
Search Report and Opinion received for Danish Patent Application No. PA201870366, dated Aug. 27, 2018, 9 pages.
Search Report and Opinion received for Danish Patent Application No. PA201870367, dated Aug. 27, 2018, 9 pages.
Search Report and Opinion received for Danish Patent Application No. PA201870368, dated Sep. 6, 2018, 7 pages.
Search Report and Opinion received for Danish Patent Application No. PA201870623, dated Dec. 20, 2018, 8 pages.
Search Report and Opinion received for Danish Patent Application No. PA201970592, dated Nov. 7, 2019, 8 pages.
Search Report and Opinion received for Danish Patent Application No. PA201970593, dated Oct. 29, 2019, 10 pages.
Search Report and Opinion received for Danish Patent Application No. PA201970595, dated Nov. 8, 2019, 16 pages.
Search Report and Opinion received for Danish Patent Application No. PA201970600, dated Nov. 5, 2019, 11 pages.
Search Report and Opinion received for Danish Patent Application No. PA201970603, dated Nov. 15, 2019, 9 pages.
Search Report and Opinion received for Danish Patent Application No. PA201970605, dated Nov. 12, 2019, 10 pages.
Search Report received for Danish Patent Application No. PA201770719, dated Oct. 17, 2017, 9 pages.
Shaw et al., ““Skills for Closeups Photography””, Watson-Guptill Publications, Nov. 1999, 5 pages.
shiftdelete.net, “Oppo Reno 10× Zoom Ön Inceleme—Huawei P30 Pro'ya rakip mi geliyor?”, Available online at <https://www.youtube.com/watch?v=ev2wlUztdrg>, See especially 5:34-6:05., Apr. 24, 2019, 2 pages.
Smart Reviews, “Honor10 AI Camera's in Depth Review”, See Especially 2:37-2:48; 6:39-6:49, Available Online at <https://www.youtube.com/watch?v=oKFqRvxeDBQ>, May 31, 2018, 2 pages.
Snapchat Lenses, “How to Get All Snapchat Lenses Face Effect Filter on Android”, Retrived from: <https://www.youtube.com/watch?v=0PfnF1RInfw&feature=youtu.be>, Sep. 21, 2015, pp. 1-2.
“Sony Xperia XZ3 Camera Review—The Colors, Duke, the Colors!”, Android Headlines—Android News & Tech News, Available online at: <https://www.youtube.com/watch?v=mwpYXzWVOgw>, See especially 1:02-1:27, 2:282:30, Nov. 3, 2018, 3 pages.
Sony, “User Guide, Xperia XZ3, H8416/H9436/H9493”, Sony Mobile Communications Inc., Retrieved from <https://www-support-downloads.sonymobile.com/h8416/userguide_EN_H8416-H9436-H9493_2_Android9.0.pdf>, See pp. 86-102, 2018, 121 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 17184710.6, dated Sep. 17, 2019, 7 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 19204230.7, dated May 25, 2021, 10 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 19724959.2, dated Feb. 1, 2021, 9 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 19724959.2, dated Mar. 31, 2021, 3 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 19729395.4, dated Mar. 11, 2021, 7 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 19729395.4, dated Mar. 19, 2021, 9 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 15/136,323, dated Jan. 31, 2018, 6 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 15/863,369, dated Aug. 8, 2018, 4 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/143,201, dated Dec. 13, 2018, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/143,201, dated Dec. 19, 2018, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/143,201, dated Jan. 10, 2019, 2 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/733,718, dated Mar. 9, 2021, 21 pages.
Supplemental Notice of Allowance received for U.S. Appl. No. 16/733,718, dated Mar. 29, 2021, 2 pages.
Supplementary European Search Report received for European Patent Application No. 18176890.4, dated Sep. 20, 2018, 4 pages.
Supplementary European Search Report received for European Patent Application No. 18183054.8, dated Oct. 11, 2018, 4 pages.
Tech Smith, “Snagit 11 Snagit 11.4 Help”, Available at: http://assets.techsmith.com/Downloads/ua-tutorials-snagit-11/Snagit_11.pdf, Jan. 2014, 2 pages.
Tech With Brett, “How to Create Your AR Emoji on the Galaxy S9 and S9+”, Available online at: <https://www.youtube.com/watch?v=HHMdcBpC8MQ>, Mar. 16, 2018, 5 pages.
Techsmith, “Snagit® 11 Snagit 11.4 Help”, Available at: <http://assets.techsmith.com/Downloads/ua-tutorials-snagit-11/Snagit_11.pdf>, Jan. 2014, 146 pages.
Techtag, “Samsung J5 Prime Camera Review | True Review”, Available online at: https://www.youtube.com/watch?v=a_p906ai6PQ, Oct. 26, 2016, 3 pages.
Techtag, “Samsung J7 Prime Camera Review (Technical Camera)”, Available Online at: https://www.youtube.com/watch?v=AJPcLP8GpFQ, Oct. 4, 2016, 3 pages.
Telleen et al., “Synthetic Shutter Speed Imaging”, University of California, Santa Cruz, vol. 26, No. 3, 2007, 8 pages.
The Nitpicker, “Sony Xperia XZ3 | in-depth Preview”, Available online at: <https://www.youtube.com/watch?v=TGCKxBuiO5c>, See especially 12:40-17:25, Oct. 07, 2018, 3 pages.
Tico et al., “Robust method of digital image stabilization”, Nokia Research Center, ISCCSP, Malta, Mar. 12-14, 2008, pp. 316-321.
Travel Tech Sports Channel, “New Whatsapp update-voice message recording made easy—Want to record long voice messages”, Available Online at: https://www.youtube.com/watch?v=SEviqgsAdUk, Nov. 30, 2017, 13 pages.
Vickgeek, “Canon 80D Live View Tutorial | Enhance your image quality”, Available online at: https://www.youtube.com/watch?v=JGNCiy6Wt9c, Sep. 27, 2016, 3 pages.
Vivo India, “Bokeh Mode | Vivo V9”, Available Online at <https://www.youtube.com/watch?v=B5AIHhH5Rxs>, Mar. 25, 2018, 3 pages.
Wong Richard, “Huawei Smartphone (P20/P10/P9, Mate 10/9) Wide Aperture Mode Demo”, Available Online at <https://www.youtube.com/watch?v=eLY3LsZGDPA>, May 7, 2017, 2 pages.
Xeetechcare, “Samsung Galaxy S10—Super Night Mode & Ultra Fast Charging!”, Online Available at: https://www.youtube.com/watch?v=3bguV4FX6aA, Mar. 28, 2019, 4 pages.
Xiao et al., “Expanding the Input Expressivity of Smartwatches with Mechanical Pan, Twist, Tilt and Click”, 14th Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Apr. 26, 2014, pp. 193-196.
Xperia Blog, “Action Camera Extension Gives Smartwatch/Smartband Owners Ability to Control Sony Wireless Cameras”, Available at: <http://www.xperiablog.net/2014/06/13/action-camera-extension-gives-smartwatchsmartband-owners-ability-to-control-sony-wireless-cameras/>, Jun. 13, 2014, 10 pages.
X-Tech, “Test Make up via Slick Augmented Reality Mirror Without Putting It on”, Available Online at: http://x-tech.am/test-make-up-via-slick-augmented-reality-mirror-without-putting-it-on/, Nov. 29, 2014, 5 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,564, dated Mar. 14, 2022, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, dated Apr. 29, 2022, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,899, dated Apr. 27, 2022, 5 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/483,582, dated Feb. 15, 2022, 2 pages.
Final Office Action received for U.S. Appl. No. 17/483,564, dated Apr. 18, 2022, 23 pages.
Final Office Action received for U.S. Appl. No. 17/483,679, dated May 24, 2022, 21 pages.
Final Office Action received for U.S. Appl. No. 17/484,899, dated May 12, 2022, 29 pages.
Non-Final Office Action received for U.S. Appl. No. 17/483,549, dated Jan. 11, 2022, 5 pages.
Non-Final Office Action received for U.S. Appl. No. 17/483,564, dated Jan. 6, 2022, 23 pages.
Non-Final Office Action received for U.S. Appl. No. 17/483,679, dated Feb. 1, 2022, 19 pages.
Non-Final Office Action received for U.S. Appl. No. 17/484,899, dated Jan. 24, 2022, 24 pages.
Notice of Allowance received for U.S. Appl. No. 17/409,598, dated Jun. 21, 2022, 12 pages.
Notice of Allowance received for U.S. Appl. No. 17/483,549, dated Apr. 15, 2022, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/483,582, dated Apr. 19, 2022, 5 pages.
Notice of Allowance received for U.S. Appl. No. 17/483,582, dated Jan. 20, 2022, 10 pages.
Office Action received for Chinese Patent Application No. 202010126661.4, dated Jun. 2, 2022, 11 pages (7 pages of English Translation and 4 pages of Official Copy).
Office Action received for Japanese Patent Application No. 2021-565919, dated Jun. 13, 2022, 4 pages (2 pages of English Translation and 2 pages of Official Copy).
Office Action received for Korean Patent Application No. 10-2021-7017731, dated May 30, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy).
Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/995,040, dated Aug. 2, 2022, 5 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/476,404, dated Jul. 27, 2022, 6 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,564, dated Jul. 21, 2022, 5 pages.
Notice of Allowance received for Japanese Patent Application No. 2020-159338, dated Jul. 19, 2022, 3 pages (1 page of English Translation and 2 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 16/144,629, dated Jul. 25, 2022, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/027,373, dated Aug. 2, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/027,373, dated Jul. 12, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/409,598, dated Jul. 7, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/409,598, dated Jul. 18, 2022, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2021203177, dated Jul. 14, 2022, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2020-159840, dated Jul. 8, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 17/121,610, dated Jul. 7, 2022, 5 pages.
Notice of Allowance received for U.S. Appl. No. 17/121,610, dated Jul. 13, 2022, 4 pages.
Final Office Action received for U.S. Appl. No. 17/476,404, dated May 5, 2022, 30 pages.
Non-Final Office Action received for U.S. Appl. No. 17/466,824, dated May 11, 2022, 30 pages.
Notice of Acceptance received for Australian Patent Application No. 2021201295, dated May 10, 2022, 3 pages.
Notice of Allowance received for Chinese Patent Application No. 202180002106.3, dated May 5, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy).
Office Action received for Australian Patent Application No. 2021203177, dated May 4, 2022, 7 pages.
Office Action received for Chinese Patent Application No. 202110328597.2, dated Apr. 15, 2022, 18 pages (9 pages of English Translation and 9 pages of Official Copy).
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/026,818, dated Dec. 15, 2020, 7 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/026,818, dated Mar. 8, 2021, 4 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/223,794, dated Sep. 7, 2021, 3 pages.
Certificate of Examination received for Australian Patent Application No. 2021103004, dated Sep. 13, 2021, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/599,433, dated Aug. 13, 2021, 5 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/599,433, dated Oct. 14, 2021, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/733,718, dated Aug. 18, 2021, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/825,879, dated Aug. 13, 2021, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/825,879, dated Sep. 15, 2021, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/835,651, dated Aug. 10, 2021, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/835,651, dated Aug. 13, 2021, 2 pages.
Decision to Grant received for Danish Patent Application No. PA201970593, dated Sep. 7, 2021, 2 pages.
Decision to Grant received for Japanese Patent Application No. 2020-193703, dated Aug. 10, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy).
Final Office Action received for U.S. Appl. No. 17/026,818, dated Jan. 2021, 21 pages.
Intention to Grant received for European Patent Application No. 19729395.4, dated Jul. 23, 2021, 10 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/031760, dated Sep. 16, 2021, 18 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/034304, dated Oct. 11, 2021, 24 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2021/034304, dated Aug. 20, 2021, 16 pages.
“Nikon Digital Camera D7200 User's Manual”, Online available at: https://download.nikonimglib.com/archive3/dbHI400jWws903mGr6q98a4k8F90/D7200UM_SG(En)05.pdf, 2005, 416 pages.
Non-Final Office Action received for U.S. Appl. No. 16/528,257, dated Jul. 2021, 12 pages.
Non-Final Office Action received for U.S. Appl. No. 17/026,818, dated Nov. 25, 2020, 20 pages.
Non-Final Office Action received for U.S. Appl. No. 17/190,879, dated Oct. 13, 2021, 10 pages.
Non-Final Office Action received for U.S. Appl. No. 17/223,794, dated Jun. 16, 2021, 32 pages.
Notice of Allowance received for Chinese Patent Application No. 202010218168.5, dated Aug. 25, 2021, 6 pages (3 pages of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Chinese Patent Application No. 202010287958.9, dated Aug. 27, 2021, 6 pages (3 pages of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Chinese Patent Application No. 202010600151.6, dated Aug. 13, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy).
Notice of Allowance received for Chinese Patent Application No. 202011243876.0, dated Sep. 8, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2021-7000954, dated Aug. 18, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 16/599,433, dated Oct. 4, 2021, 13 pages.
Notice of Allowance received for U.S. Appl. No. 16/733,718, dated Jul. 29, 2021, 26 pages.
Notice of Allowance received for U.S. Appl. No. 16/825,879, dated Sep. 28, 2021, 8 pages.
Notice of Allowance received for U.S. Appl. No. 17/026,818, dated May 13, 2021, 10 pages.
Office Action received for Australian Patent Application No. 2020239711, dated Sep. 13, 2021, 5 pages.
Office Action received for Australian Patent Application No. 2020239717, dated Sep. 28, 2021, 6 pages.
Office Action received for Australian Patent Application No. 2021103004, dated Aug. 12, 2021, 5 pages.
Office Action received for Chinese Patent Application No. 202010287950.2, dated Aug. 10, 2021, 12 pages (6 pages of English Translation and 6 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202010600197.8, dated Jul. 2, 2021, 14 pages (6 pages of English Translation and 8 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202011480411.7, dated Aug. 2, 2021, 12 pages (6 pages of English Translation and 6 pages of Official Copy).
Office Action received for Danish Patent Application No. PA202070617, dated Sep. 24, 2021, 4 pages.
Office Action received for European Patent Application No. 18704732.9, dated Sep. 7, 2021, 10 pages.
Office Action received for European Patent Application No. 20168009.7, dated Sep. 13, 2021, 8 pages.
Office Action received for European Patent Application No. 20206197.4, dated Aug. 27, 2021, 6 pages.
Office Action received for Indian Patent Application No. 201814036860, dated Jul. 29, 2021, 8 pages.
Office Action received for Indian Patent Application No. 201817024430, dated Sep. 27, 2021, 8 pages.
Office Action received for Indian Patent Application No. 201818045872, dated Oct. 13, 2021, 7 pages.
Office Action received for Japanese Patent Application No. 2018-182607, dated Sep. 8, 2021, 7 pages (4 pages of English Translation and 3 pages of Official Copy).
Office Action received for Japanese Patent Application No. 2019-203399, dated Aug. 10, 2021, 4 pages (2 pages of English Translation and 2 pages of Official Copy).
Office Action received for Japanese Patent Application No. 2020-542592, dated Sep. 21, 2021, 5 pages (3 pages of English Translation and 2 pages of Official Copy).
Office Action received for Korean Patent Application No. 10-2020-7022663, dated Aug. 17, 2021, 11 pages (5 pages of English Translation and 6 pages of Official Copy).
Office Action received for Korean Patent Application No. 10-2021-7020693, dated Jul. 14, 2021, 7 pages (3 pages of English Translation and 4 pages of Official Copy).
Search Report and Opinion received for Danish Patent Application No. PA202070617, dated Dec. 23, 2020, 8 pages.
Senicar et al., “User-Centred Design and Development of an Intelligent Light Switch for Sensor Systems”, Technical Gazette, vol. 26, No. 2, available online at: https://hrcak.srce.hr/file/320403, 2019, pp. 339-345.
Corrected Notice of Allowance received for U.S. Appl. No. 16/144,629, dated Apr. 21, 2022, 5 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/157,166, dated Apr. 25, 2022, 4 pages.
Office Action received for Indian Patent Application No. 202118046032, dated Apr. 25, 2022, 6 pages.
Office Action received for Indian Patent Application No. 202118046033, dated Apr. 25, 2022, 7 pages.
Office Action received for Indian Patent Application No. 202118046044, dated Apr. 25, 2022, 6 pages.
Messelodi et al., “A Kalman filter based background updating algorithm robust to sharp illumination changes.”, International Conference on Image Analysis and Processing. Springer, Berlin, Heidelberg, 2005, pp. 163-170.
Certificate of Examination received for Australian Patent Application No. 2021107587, dated Apr. 29, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/121,610, dated May 20, 2022, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/484,279, dated Feb. 15, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/484,279, dated Feb. 28, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/484,307, dated Apr. 20, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/484,307, dated Feb. 10, 2022, 7 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/484,321, dated Mar. 24, 2022, 2 pages.
Intention to Grant received for European Patent Application No. 20168009.7, dated May 17, 2022, 9 pages.
Notice of Acceptance received for Australian Patent Application No. 2021203903, dated May 25, 2022, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2022202377, dated May 11, 2022, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2021-510849, dated May 16, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 17/483,684, dated Apr. 27, 2022, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/484,279, dated Jan. 26, 2022, 12 pages.
Notice of Allowance received for U.S. Appl. No. 17/484,279, dated May 13, 2022, 9 pages.
Notice of Allowance received for U.S. Appl. No. 17/484,307, dated Mar. 8, 2022, 11 pages.
Notice of Allowance received for U.S. Appl. No. 17/484,307, dated Nov. 30, 2021, 11 pages.
Notice of Allowance received for U.S. Appl. No. 17/484,321, dated Nov. 30, 2021, 10 pages.
Office Action received for Chinese Patent Application No. 202110327012.5, dated Apr. 29, 2022, 17 pages (10 pages of English Translation and 7 pages of Official Copy).
Supplemental Notice of Allowance received for U.S. Appl. No. 17/484,321, dated Mar. 1, 2022, 6 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/144,629, dated Jun. 23, 2022, 5 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/157,166, dated Jun. 29, 2022, 4 pages.
Notice of Acceptance received for Australian Patent Application No. 2019338180, dated Jun. 27, 2022, 3 pages.
Notice of Allowance received for Korean Patent Application No. 10-2020-0123805, dated Jun. 19, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2020-7022663, dated Jun. 23, 2022, 6 pages (2 pages of English Translation and 4 pages of Official Copy).
Office Action received for Indian Patent Application No. 202118028159, dated Jun. 27, 2022, 6 pages.
Office Action received for Korean Patent Application No. 10-2022-7010505, dated Jun. 14, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 17/525,664, dated Oct. 27, 2022, 11 pages.
Office Action received for Chinese Patent Application No. 202110766668.7, dated Sep. 15, 2022, 18 pages (9 pages of English Translation and 9 pages of Official Copy).
Drunk Beauty Flower Digital Technology, “iPhone XS Max Camera Tips, Tricks, Features and Complete Tutorial”, Available online at: https://www.ixigua.com/6606874981844386308?wid_try=1, Oct. 2, 2018, 2 pages (Official Copy Only). {See communication under 37 CFR § 1.98(a) (3)}.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/482,987, dated Apr. 11, 2022, 4 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484907, dated Jan. 10, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/484,907, dated Jun. 15, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/484,907, dated Mar. 18, 2022, 2 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/014271, dated Jul. 4, 2022, 23 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/024964, dated Aug. 4, 2022, 17 pages.
Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/014271, dated May 12, 2022, 20 pages.
Non-Final Office Action received for U.S. Appl. No. 17/356,322, dated Aug. 11, 2022, 17 pages.
Non-Final Office Action received for U.S. Appl. No. 17/482,987, dated Jan. 18, 2022, 25 pages.
Non-Final Office Action received for U.S. Appl. No. 17/484,907, dated Nov. 19, 2021, 24 pages.
Notice of Allowance received for U.S. Appl. No. 17/482,987, dated Jun. 23, 2022, 9 pages.
Notice of Allowance received for U.S. Appl. No. 17/482,987, dated May 11, 2022, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/483,684, dated Aug. 16, 2022, 9 pages.
Notice of Allowance received for U.S. Appl. No. 17/484,907, dated Jul. 25, 2022, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/484,907, dated Mar. 2, 2022, 13 pages.
Notice of Allowance received for U.S. Appl. No. 17/484,907, dated May 20, 2022, 13 pages.
Office Action received for Chinese Patent Application No. 202111323807.5, dated Jul. 15, 2022, 12 pages (6 pages of English Translation and 6 pages of Official Copy).
Office Action received for European Patent Application No. 20206196.6, dated Aug. 10, 2022, 13 pages.
Office Action received for Korean Patent Application No. 10-2022-7023077, dated Jul. 25, 2022, 6 pages (2 pages of English Translation and 4 pages of Official Copy).
Corrected Notice of Allowance received for U.S. Appl. No. 17/027,373, dated Oct. 26, 2022, 2 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/029261, dated Oct. 20, 2022, 18 pages.
Non-Final Office Action received for U.S. Appl. No. 17/482,977, dated Oct. 13, 2022, 20 pages.
Notice of Allowance received for Chinese Patent Application No. 201910400179.2, dated Oct. 9, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2022-0091730, dated Oct. 4, 2022, 5 pages (2 pages of English Translation and 3 pages of official copy).
Notice of Allowance received for U.S. Appl. No. 17/483,684, dated Oct. 24, 2022, 9 pages.
Notice of Allowance received for U.S. Appl. No. 17/740,032, dated Oct. 13, 2022, 11 pages.
Office Action received for Indian Patent Application No. 202215010325, dated Oct. 10, 2022, 7 pages.
Office Action received for Korean Patent Application No. 10-2021-7006145, dated Oct. 12, 2022, 14 pages (6 pages of English Translation and 8 pages of Official Copy).
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, dated Aug. 23, 2022, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 16/144,629, dated Aug. 24, 2022, 6 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/483,549, dated Aug. 24, 2022, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/483,684, dated Aug. 24, 2022, 6 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/484,907, dated Aug. 26, 2022, 2 pages.
Office Action received for Japanese Patent Application No. 2020-542592, dated Aug. 1, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy).
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,899, dated Sep. 1, 2022, 5 pages.
Hourunranta et al., “Video and Audio Editing for Mobile Applications”, IEEE International Conference on Multimedia and Expo, ICME 2006, Jul. 9, 2006, pp. 1305-1308.
Hurwitz, Jon, “Interface for Small-Screen Media Playback Control”, Online available at: https://www.tdcommons.org/cgi/viewcontent.cgi?article=4231&context=dpubs_series, Technical Disclosure Commons, Apr. 17, 2020, pp. 1-9.
Non-Final Office Action received for U.S. Appl. No. 17/476,404, dated Sep. 14, 2022, 31 pages.
Notice of Allowance received for U.S. Appl. No. 17/409,598, dated Sep. 14, 2022, 9 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 20205496.1, dated Sep. 8, 2022, 9 pages.
Advisory Action received for U.S. Appl. No. 17/483,679, dated Sep. 20, 2022, 8 pages.
Intention to Grant received for European Patent Application No. 21733324.4, dated Sep. 13, 2022, 7 pages.
Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/029261, dated Aug. 29, 2022, 16 pages.
Non-Final Office Action received for U.S. Appl. No. 17/483,542, dated Sep. 22, 2022, 18 pages.
Office Action received for European Patent Application No. 21163791.3, dated Sep. 20, 2022, 6 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/525,664, dated Nov. 3, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/740,032, dated Nov. 3, 2022, 6 pages.
European Search Report received for European Patent Application No. 22184844.3, dated Nov. 4, 2022, 4 pages.
Intention to Grant received for European Patent Application No. 20168009.7, dated Oct. 31, 2022, 9 pages.
Notice of Allowance received for Korean Patent Application No. 10-2022-7023077, dated Nov. 1, 2022, 8 pages (2 pages of English Translation and 6 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 17/732,191, dated Nov. 9, 2022, 12 pages.
Office Action received for Chinese Patent Application No. 202110328597.2, dated Oct. 10, 2022, 13 pages (7 pages of English Translation and 6 pages of Official Copy).
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/482,977, dated Dec. 5, 2022, 2 pages.
Intention to Grant received for European Patent Application No. 18704732.9, dated Dec. 6, 2022, 10 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/030589, dated Sep. 5, 2022, 26 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/030704, dated Nov. 9, 2022, 19 pages.
Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/030704, dated Sep. 15, 2022, 12 pages.
Invitation to Pay Search Fees received for European Patent Application No. 21728781.2, dated Dec. 2, 2022, 3 pages.
Non-Final Office Action received for U.S. Appl. No. 17/041,412, dated Dec. 5, 2022, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 17/483,679, dated Dec. 9, 2022, 31 pages.
Non-Final Office Action received for U.S. Appl. No. 17/510,168, dated Dec. 6, 2022, 11 pages.
Office Action received for Australian Patent Application No. 2021290292, dated Nov. 24, 2022, 2 pages.
Office Action received for Chinese Patent Application No. 202110328601.5, dated Nov. 2, 2022, 32 pages (19 pages of English Translation and 13 pages of Official Copy).
Office Action received for European Patent Application No. 22184853.4, dated Nov. 25, 2022, 7 pages.
QQ, “Method of QQ voice chat”, Online Available at: https://www.taodocs.com/p-47909082.html, May 25, 2016, 3 pages (Official Copy only) See Communication under 37 CFR § 1.98(a) (3).
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/466,824, dated Oct. 5, 2022, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/409,598, dated Sep. 30, 2022, 2 pages.
Examiner-Initiated Interview Summary received for U.S. Appl. No. 17/356,322, dated Sep. 29, 2022, 4 pages.
Final Office Action received for U.S. Appl. No. 15/995,040, dated Oct. 6, 2022, 27 pages.
Notice of Acceptance received for Australian Patent Application No. 2022215297, dated Sep. 26, 2022, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2021-565919, dated Oct. 3, 2022, 3 pages (1 page of English Translation and 2 of pages Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2022-7006310, dated Sep. 20, 2022, 8 pages (2 pages of English Translation and 6 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 17/027,373, dated Oct. 3, 2022, 5 pages.
Office Action received for Brazilian Patent Application No. BR122018076550-0, dated Sep. 28, 2022, 7 pages (1 page of English Translation and 6 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202111652452.4, dated Aug. 29, 2022, 23 pages (12 pages of English Translation and 11 pages of Official Copy).
Office Action received for Japanese Patent Application No. 2021-166686, dated Oct. 3, 2022, 3 pages (2 pages of English Translation and 1 page of Official Copy).
Shareit, “WhatsApp Easy Way to Record Long Voice Messages—New Update”, Retrieved from Internet: < https://www.youtube.com/watch?v=3MVnYGt8v1l>, Apr. 7, 2018, 39 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/995,040, dated Nov. 18, 2022, 5 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,542, dated Nov. 23, 2022, 4 pages.
European Search Report received for European Patent Application No. 22184853.4, dated Nov. 14, 2022, 5 pages.
Final Office Action received for U.S. Appl. No. 17/356,322, dated Nov. 29, 2022, 19 pages.
Final Office Action received for U.S. Appl. No. 17/466,824, dated Nov. 25, 2022, 35 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/031760, dated Nov. 24, 2022, 11 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/029273, dated Oct. 27, 2022, 19 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/029580, dated Nov. 7, 2022, 20 pages.
Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/029580, dated Sep. 5, 2022, 13 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2022/029273, dated Sep. 2, 2022, 13 pages.
Non-Final Office Action received for U.S. Appl. No. 17/483,564, dated Nov. 28, 2022, 24 pages.
Notice of Allowance received for Japanese Patent Application No. 2020-542592, dated Nov. 14, 2022, 2 pages (1 page of English Translation and 1 page of Official Copy).
Notice of Allowance received for U.S. Appl. No. 17/566,094, dated Nov. 22, 2022, 10 pages.
Office Action received for European Patent Application No. 22184844.3, dated Nov. 16, 2022, 7 pages.
Office Action received for Japanese Patent Application No. 2022-027861, dated Nov. 21, 2022, 4 pages (2 pages of English Translation and 2 pages of Official Copy).
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/356,322, dated Dec. 27, 2022, 4 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/476,404, dated Dec. 20, 2022, 2 pages.
Intention to Grant received for European Patent Application No. 20206197.4, dated Dec. 15, 2022, 10 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/034304, dated Dec. 15, 2022, 19 pages.
Office Action received for Australian Patent Application No. 2022201532, dated Dec. 19, 2022, 5 pages.
Office Action received for Chinese Patent Application No. 202110327012.5, dated Nov. 28, 2022, 16 pages (10 pages of English Translation and 6 pages of Official Copy).
Corrected Notice of Allowance received for U.S. Appl. No. 17/950,900, dated Jun. 30, 2023, 2 pages.
Notice of Allowance received for Korean Patent Application No. 10-2020-0124139, dated Jun. 19, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy).
Office Action received for Australian Patent Application No. 2022221466, dated Jun. 16, 2023, 2 pages.
Office Action received for European Patent Application No. 18779093.6, dated Jun. 28, 2023, 4 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,542, dated May 22, 2023, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, dated May 19, 2023, 3 pages.
Decision to Grant received for European Patent Application No. 20210373.5, dated May 19, 2023, 4 pages.
Final Office Action received for U.S. Appl. No. 17/483,564, dated May 25, 2023, 26 pages.
Final Office Action received for U.S. Appl. No. 17/542,947, dated May 25, 2023, 55 pages.
Intention to Grant received for European Patent Application No. 20206197.4, dated May 25, 2023, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 17/466,824, dated May 25, 2023, 33 pages.
Notice of Acceptance received for Australian Patent Application No. 2022201532, dated May 22, 2023, 3 pages.
Notice of Acceptance received for Australian Patent Application No. 2022204465, dated May 26, 2023, 3 pages.
Notice of Allowance received for Japanese Patent Application No. 2021-206121, dated May 15, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202110328597.2, dated May 15, 2023, 13 pages (6 pages of English Translation and 7 pages of Official Copy).
“6. Voice chat with friends through QQ”, Online available at: https://v.qq.com/x/page/a0166p7xrt0.html, Sep. 22, 2015, 1 page (Official Copy Only). {See Communication under 37 CFR § 1.98(a) (3)}.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/466,824, dated Apr. 20, 2023, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,564, dated Apr. 21, 2023, 5 pages.
Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20205496.1, dated Apr. 19, 2023, 1 page.
Corrected Notice of Allowance received for U.S. Appl. No. 17/041,412, dated Apr. 12, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/482,977, dated Apr. 24, 2023, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/950,900, dated Apr. 14, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/950,922, dated Apr. 14, 2023, 2 pages.
Decision to Grant received for Japanese Patent Application No. 2021-166686, dated Apr. 20, 2023, 2 pages (1 page of English Translation and 1 page of Official Copy).
Jiutian Technology, “Windows 8 Chinese version from entry to proficiency”, Jan. 1, 2014, 5 pages (Official Copy Only). {See Communication under 37 CFR § 1.98(a) (3)}.
Non-Final Office Action received for U.S. Appl. No. 17/903,946, dated Apr. 14, 2023, 17 pages.
Notice of Acceptance received for Australian Patent Application No. 2022218463, dated Apr. 18, 2023, 3 pages.
Notice of Allowance received for U.S. Appl. No. 17/041,412, dated Apr. 26, 2023, 11 pages.
Notice of Allowance received for U.S. Appl. No. 17/525,664, dated Apr. 26, 2023, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/940,672, dated Apr. 27, 2023, 9 pages.
Office Action received for Chinese Patent Application No. 202110327012.5, dated Mar. 16, 2023, 12 pages (7 pages of English Translation and 5 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202110328601.5, dated Mar. 24, 2023, 25 pages (15 pages of English Translation and 10 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202211072958.2, dated Apr. 5, 2023, 11 pages (6 pages of English Translation and 5 pages of Official Copy).
Office Action received for Indian Patent Application No. 202215025361, dated Mar. 29, 2023, 6 pages.
Result of Consultation received for European Patent Application No. 20205496.1, dated Apr. 18, 2023, 3 pages.
Song, Jianhua, “Guidelines for Network”, Feb. 29, 2008, 11 pages (Official Copy Only). {See Communication under 37 CFR § 1.98(a) (3)}.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/476,404, dated Jun. 2, 2023, 2 pages.
Board Decision received for Chinese Patent Application No. 201811446867.4, dated Apr. 26, 2023, 21 pages (5 pages of English Translation and 16 pages of Official copy).
Computerhilfen, “WhatsApp: Voice Message without Holding the Button”, Retrieved from Internet: < https://www.youtube.com/watch?v=ofFCKvs5URw>, Jan. 14, 2018, 9 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/944,765, dated Jun. 1, 2023, 5 pages.
Decision to Grant received for European Patent Application No. 21733324.4, dated Jun. 2, 2023, 3 pages.
Final Office Action received for U.S. Appl. No. 17/483,679, dated Jun. 13, 2023, 33 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/050916, dated May 15, 2023, 23 pages.
Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US2022/050916, mailed on Mar. 23, 2023, 16 pages.
Non-Final Office Action received for U.S. Appl. No. 15/995,040, dated Jun. 7, 2023, 26 pages.
Non-Final Office Action received for U.S. Appl. No. 17/484,899, dated Jun. 14, 2023, 41 pages.
Office Action received for European Patent Application No. 21202358.4, dated Jun. 9, 2023, 7 pages.
Yuan, Ye, “Iphone 4s Original Secrets”, China Railway Press, 2012, 15 pages (Official Copy Only). {See Communication under 37 CFR § 1.98(a) (3)}.
Applicant Initiated Interview Summary received for U.S. Appl. No. 17/721,039, dated Mar. 10, 2023, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/041,412, dated Jan. 31, 2023, 7 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/950,900, dated Jan. 26, 2023, 5 pages.
Board Opinion received for Chinese Patent Application No. 201811446867.4, dated Feb. 14, 2023, 11 pages (4 pages of English Translation and 7 pages of Official Copy).
Corrected Notice of Allowance received for U.S. Appl. No. 17/041,412, dated Mar. 23, 2023, 7 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/041,412, dated Mar. 31, 2023, 6 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/356,322, dated Feb. 15, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/356,322, dated Mar. 8, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/510,168, dated Mar. 16, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/510,168, dated Mar. 29, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/525,664, dated Apr. 11, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/525,664, dated Feb. 23, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/566,094, dated Feb. 8, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/566,094, dated Jan. 5, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/566,094, dated Jan. 23, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/566,094, dated Mar. 7, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/740,032, dated Feb. 15, 2023, 6 pages.
Dolan, Tim, “How to Make a Laptop Webcam into a Document Camera—IPEVO Mirror-Cam Review”, Retrieved from the Internet: URL: https://www.youtube.com/watch?v=-K8jyZ1hbbg, Aug. 29, 2020, 1 page.
Final Office Action received for U.S. Appl. No. 17/950,900, dated Jan. 23, 2023, 14 pages.
Hearing Notice received for Indian Patent Application No. 201817024430, dated Apr. 6, 2023, 2 pages.
Intention to Grant received for European Patent Application No. 20168009.7, dated Feb. 28, 2023, 10 pages.
Intention to Grant received for European Patent Application No. 20210373.5, dated Jan. 10, 2023, 12 pages.
Intention to Grant received for European Patent Application No. 21733324.4, dated Jan. 9, 2023, 9 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/046877, dated Apr. 6, 2023, 12 pages.
International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/044592, dated Mar. 14, 2023, 22 pages.
Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2022/044592, dated Jan. 16, 2023, 21 pages.
Larson, Tom, “How to Turn your Webcam into a Document Camera”, Retrieved from the Internet: URL: https://www.youtube.com/watchv=UlaW22FxRZM, Nov. 7, 2020, 1 page.
Non-Final Office Action received for U.S. Appl. No. 17/476,404, dated Mar. 30, 2023, 29 pages.
Non-Final Office Action received for U.S. Appl. No. 17/483,542, dated Jan. 31, 2023, 14 pages.
Non-Final Office Action received for U.S. Appl. No. 17/542,947, dated Mar. 2, 2023, 59 pages.
Non-Final Office Action received for U.S. Appl. No. 17/721,039, dated Feb. 2, 2023, 65 pages.
Non-Final Office Action received for U.S. Appl. No. 17/940,672, dated Mar. 16, 2023, 15 pages.
Non-Final Office Action received for U.S. Appl. No. 17/944,765, dated Jan. 18, 2023, 9 pages.
Non-Final Office Action received for U.S. Appl. No. 17/950,900, dated Dec. 1, 2022, 14 pages.
Notice of Acceptance received for Australian Patent Application No. 2021290292, dated Jan. 23, 2023, 3 pages.
Notice of Allowance received for Brazilian Patent Application No. BR122018076550-0, dated Jan. 3, 2022, 3 pages (1 page of English Translation and 2 pages of Official Copy).
Notice of Allowance received for Chinese Patent Application No. 202111323807.5, dated Jan. 10, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Japanese Patent Application No. 2022-027861, dated Feb. 13, 2023, 3 pages (1 page of English Translation and 2 pages of Official Copy).
Notice of Allowance received for Japanese Patent Application No. 2022-125792, dated Jan. 27, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2021-7006145, dated Mar. 6, 2023, 5 pages (2 pages of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2021-7017731, dated Feb. 28, 2023, 5 pages (2 pages of English Translation and 3 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2022-7010505, dated Dec. 26, 2022, 7 pages (2 pages of English Translation and 5 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 17/041,412, dated Mar. 15, 2023, 13 pages.
Notice of Allowance received for U.S. Appl. No. 17/356,322, dated Feb. 2, 2023, 11 pages.
Notice of Allowance received for U.S. Appl. No. 17/482,977, dated Jan. 24, 2023, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/510,168, dated Feb. 13, 2023, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/525,664, dated Feb. 14, 2023, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/566,094, dated Feb. 23, 2023, 8 pages.
Notice of Allowance received for U.S. Appl. No. 17/732,191, dated Feb. 27, 2023, 12 pages.
Notice of Allowance received for U.S. Appl. No. 17/740,032, dated Feb. 1, 2023, 9 pages.
Notice of Allowance received for U.S. Appl. No. 17/944,765, dated Apr. 5, 2023, 9 pages.
Notice of Allowance received for U.S. Appl. No. 17/950,900, dated Mar. 7, 2023, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/950,922, dated Apr. 5, 2023, 10 pages.
Office Action received for Australian Patent Application No. 2022204465, dated Mar. 10, 2023, 4 pages.
Office Action received for Australian Patent Application No. 2022218463, dated Mar. 17, 2023, 2 pages.
Office Action received for Chinese Patent Application No. 201980012481.9, dated Jan. 12, 2023, 18 pages (9 pages of English Translation and 9 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202110328602.X, dated Dec. 1, 2022, 28 pages (17 pages of English Translation 11 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202110766668.7, dated Jan. 20, 2023, 11 pages (6 pages of English Translation and 5 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202111652452.4, dated Feb. 11, 2023, 28 pages (13 pages of English Translation and 15 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202210063070.6, dated Jan. 5, 2023, 12 pages (6 pages of English Translation and 6 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202210849242.2, dated Jan. 20, 2023, 12 pages (6 pages of English Translation and 6 pages of Official Copy).
Office Action received for European Patent Application No. 19769316.1, dated Jan. 12, 2023, 10 pages.
Office Action received for European Patent Application No. 21728781.2, dated Mar. 1, 2023, 13 pages.
Office Action received for Indian Patent Application No. 202015008746, dated Mar. 6, 2023, 7 pages.
Office Action received for Indian Patent Application No. 202015013360, dated Mar. 17, 2023, 7 pages.
Office Action received for Indian Patent Application No. 202117009020, dated Feb. 6, 2023, 7 pages.
Office Action received for Indian Patent Application No. 202215025360, dated Mar. 29, 2023, 6 pages.
Office Action received for Indian Patent Application No. 202215025363, dated Mar. 29, 2023, 6 pages.
Office Action received for Indian Patent Application No. 202215025364, dated Mar. 29, 2023, 6 pages.
Office Action received for Indian Patent Application No. 202215026045, dated Mar. 31, 2023, 8 pages.
Office Action received for Japanese Patent Application No. 2021-187533, dated Feb. 6, 2023, 7 pages (4 pages of English Translation and 3 pages of Official Copy).
Office Action received for Japanese Patent Application No. 2021-206121, dated Feb. 20, 2023, 7 pages (3 pages of English Translation and 4 pages of Official Copy).
Office Action received for Korean Patent Application No. 10-2020-0124139, dated Jan. 17, 2023, 10 pages (5 pages of English Translation and 5 pages of Official Copy).
Office Action received for Korean Patent Application No. 10-2022-7043663, dated Jan. 6, 2023, 12 pages (5 pages of English Translation and 7 pages of Official Copy).
Office Action received for Korean Patent Application No. 10-2022-7033119, dated Mar. 29, 2023, 5 pages (2 pages of English Translation and 3 pages of Official Copy).
Result of Consultation received for European Patent Application No. 22184844.3, dated Feb. 1, 2023, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,564, dated Jun. 21, 2023, 4 pages.
Decision to Grant received for European Patent Application No. 20168009.7, dated Jun. 22, 2023, 4 pages.
Examiner Interview Summary received for U.S. Appl. No. 17/903,946, dated Jun. 28, 2023, 2 pages.
Notice of Allowance received for U.S. Appl. No. 17/950,900, dated Jun. 16, 2023, 6 pages.
Office Action received for Chinese Patent Application No. 202111652452.4, dated May 19, 2023, 15 pages (8 pages of English Translation and 7 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202211072261.5, dated Apr. 29, 2023, 17 pages (9 pages of English Translation and 8 pages of Official Copy).
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/542,947, dated Apr. 28, 2023, 4 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/041,412, dated May 17, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/525,664, dated May 17, 2023, 2 pages.
Decision to Refuse received for European Patent Application No. 202054961, dated May 12, 2023, 16 pages.
Minutes of the Oral Proceedings received for European Patent Application No. 20205496.1, mailed on May 9, 2023, 7 pages.
Non-Final Office Action received for U.S. Appl. No. 17/872,736, dated May 11, 2023, 17 pages.
Notice of Allowance received for Chinese Patent Application No. 202210063070.6, dated May 2, 2023, 2 pages (1 page of English Translation and 1 page of Official Copy).
Notice of Allowance received for U.S. Appl. No. 17/356,322, dated May 8, 2023, 10 pages.
Notice of Allowance received for U.S. Appl. No. 17/510, 168, dated May 3, 2023, 10 pages.
Office Action received for Australian Patent Application No. 2022228207, dated Apr. 28, 2023, 3 pages.
Office Action received for European Patent Application No. 22184844.3, dated Apr. 26, 2023, 5 pages.
Office Action received for European Patent Application No. 22184853.4, dated Apr. 26, 2023, 4 pages.
Summons to Attend Oral Proceedings received for European Patent Application No. 21163791.3, mailed on May 3, 2023, 6 pages.
Summons to Oral Proceedings received for European Patent Application No. 17184710.6, mailed on May 10, 2023, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/121,610, dated Jun. 7, 2022, 4 pages.
HuddleCamHD SimplTrack2 Auto Tracking Camera lnstallation & Operation Manual, Available Online at: https://huddlecamhd.com/wp-content/uploads/2021l01/SimplTrack2-User-Manual-v1_2-6-20.pdf, Jun. 2020, 41 pages.
Notice of Acceptance received for Australian Patent Application No. 2020239717, dated Jun. 1, 2022, 3 pages.
Notice of Allowance received for Korean Patent Application No. 10-2022-7016421, dated May 25, 2022, 6 pages (2 pages of English Translation and 4 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 17/027,373, dated Jun. 3, 2022, 8 pages.
Office Action received for Chinese Patent Application No. 202110328601.5, dated Apr. 27, 2022, 25 pages (14 pages of English Translation and 11 pages of Official Copy).
Office Action received for European Patent Application No. 19707557.5, dated Jun. 3, 2022, 5 pages.
Office Action received for European Patent Application No. 20210373.5, dated May 31, 2022, 5 pages.
Abdulezer et al., “Skype for Dummies”, Available Online at: https://ixn.es/Skype%20For%20Dummies.pdf, 2007, 361 pages.
Final Office Action received for U.S. Appl. No. 17/721,039, dated Jul. 6, 2023, 66 pages.
Intention to Grant received for European Patent Application No. 20166552.8, dated Jun. 29, 2023, 8 pages.
Notice of Allowance received for Australian Patent Application No. 2022228207, dated Jul. 3, 2023, 3 pages.
Notice of Allowance received for U.S. Appl. No. 17/483,564, dated Jul. 17, 2023, 46 pages.
Notice of Hearing received for Indian Patent Application No. 201818046896, dated Jul. 11, 2023, 2 pages.
Office Action received for Australian Patent Application No. 2022228121, dated Jul. 7, 2023, 3 pages.
Office Action received for Chinese Patent Application No. 202110766668.7, dated Jun. 7, 2023, 13 pages (9 pages of English Translation and 4 pages of Official Copy).
Office Action received for Japanese Patent Application No. 2021-187533, dated Jun. 26, 2023, 6 pages (3 pages of English Translation and 3 pages of Official Copy).
Summons to Oral Proceedings received for European Patent Application No. 19724959.2, mailed on Jul. 14, 2023, 6 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/483,679, dated Aug. 18, 2023, 2 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/484,899, dated Sep. 12, 2023, 6 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/542,947, dated Jul. 10, 2023, 4 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/721,039, dated Jul. 25, 2023, 3 pages.
Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/872,736, dated Jul. 25, 2023, 2 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/483,542, dated Aug. 25, 2023, 3 pages.
Corrected Notice of Allowance received for U.S. Appl. No. 17/944,765, dated Jul. 27, 2023, 5 pages.
Decision to Grant received for European Patent Application No. 18704732.9, dated Aug. 18, 2023, 3 pages.
Decision to Grant received for Japanese Patent Application No. 2023-083816, dated Aug. 9, 2023, 2 pages (1 page of English Translation and 1 page of Official Copy).
Ex-Parte Quayle Action received for U.S. Appl. No. 17/903,946, mailed on Aug. 4, 2023, 4 pages.
Extended European Search Report received for European Patent Application No. 23173036.7, dated Jul. 24, 2023, 13 pages.
Final Office Action received for U.S. Appl. No. 17/476,404, dated Sep. 12, 2023, 30 pages.
Garrison Dr., “An Analysis and Evaluation of Audio Teleconferencing to Facilitate Education at a Distance”, Online Available at: https://doi.org/10.1080/08923649009526713, American journal of distance education, vol. 4, No. 3, Sep. 24, 2009, 14 pages.
Hearing Notice received for Indian Patent Application No. 201814036860, dated Sep. 8, 2023, 2 pages.
Intention to Grant received for European Patent Application No. 21728781.2, dated Jul. 28, 2023, 9 pages.
Intention to Grant received for European Patent Application No. 22151131.4, dated Aug. 4, 2023, 10 pages.
International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/014271, dated Aug. 10, 2023, 17 pages.
Non-Final Office Action received for U.S. Appl. No. 17/483,679, dated Sep. 13, 2023, 32 pages.
Non-Final Office Action received for U.S. Appl. No. 17/684,843, dated Aug. 11, 2023, 23 pages.
Non-Final Office Action received for U.S. Appl. No. 17/732,204, dated Aug. 4, 2023, 18 pages.
Non-Final Office Action received for U.S. Appl. No. 17/740,104, dated Aug. 2, 2023, 15 pages.
Non-Final Office Action received for U.S. Appl. No. 18/114,880, dated Aug. 29, 2023, 10 pages.
Notice of Acceptance received for Australian Patent Application No. 2022221466, dated Aug. 31, 2023, 3 pages.
Notice of Allowance received for Chinese Patent Application No. 202110328601.5, dated Jul. 5, 2023, 5 pages (1 page of English Translation and 4 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2022-7033119, dated Jul. 26, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2022-7043663, dated Jul. 25, 2023, 8 pages (2 pages of English Translation and 6 pages of Official Copy).
Notice of Allowance received for Korean Patent Application No. 10-2023-7009943, dated Aug. 31, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy).
Notice of Allowance received for U.S. Appl. No. 17/483,542, dated Aug. 11, 2023, 9 pages.
Notice of Allowance received for U.S. Appl. No. 17/872,736, dated Aug. 21, 2023, 6 pages.
Notice of Allowance received for U.S. Appl. No. 17/872,736, dated Aug. 30, 2023, 4 pages.
Office Action received for Australian Patent Application No. 2022228191, dated Aug. 16, 2023, 4 pages.
Office Action received for Chinese Patent Application No. 201980012481.9, dated Jun. 8, 2023, 16 pages (9 pages of English Translation and 7 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202110328597.2, dated Jul. 18, 2023, 21 pages (6 pages of English Translation and 15 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202110328602.X, dated Jun. 29, 2023, 27 pages (18 pages of English Translation and 9 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202211072958.2, dated Jun. 20, 2023, 48 pages (24 pages of English Translation and 24 pages of Official Copy).
Office Action received for Chinese Patent Application No. 202211073034.4, dated May 30, 2023, 21 pages (10 pages of English Translation and 11 pages of Official Copy).
Office Action received for European Patent Application No. 21157252.4, dated Jul. 24, 2023, 5 pages.
Office Action received for Japanese Patent Application No. 2022-130725, dated Sep. 4, 2023, 2 pages (1 page of English Translation and 1 page of Official Copy).
Result of Consultation received for European Patent Application No. 22184844.3, mailed on Aug. 28, 2023, 3 pages.
Shangmeng Li, “The Design and Implementation of Mobile Terminal System of Multimedia Conference Based on Symbian Operating System”, China Academic Journal Electronic Publishing House, Online available at: http://www.cnki.net, 2011, 66 pages (Official Copy only). See Communication under 37 CFR § 1.98(a) (3).
Related Publications (1)
Number Date Country
20220006946 A1 Jan 2022 US
Provisional Applications (1)
Number Date Country
62739093 Sep 2018 US
Continuations (1)
Number Date Country
Parent 16528941 Aug 2019 US
Child 17479897 US