Patent Grant
11314330
This relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that generate tactile outputs to provide haptic feedback.
The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Example touch-sensitive surfaces include touchpads and touch-screen displays. Such surfaces are widely used to manipulate user interfaces and objects therein on a display. User interface objects can include icons and notifications displayed in a lock screen user interface, as well as the locked-mode controls of an application having functionality available to the user while the device operates in a locked mode (e.g., prior to authentication of the user, for example through entry of a passcode or fingerprint or other user authentication information).
Example locked screen features include icons for accessing applications or device features available in the device's locked mode. Examples include a flashlight icon for toggling a state of a flashlight in the device, a camera application, and features within the camera application that are accessible in the device's locked mode. User manipulations of user interface features include adjusting the position and/or size of one or more user interface objects or activating buttons or opening files/applications represented by user interface objects, as well as associating metadata with one or more user interface objects or otherwise manipulating user interfaces. Example user interface objects include digital images, video, text, icons, control elements such as buttons and other graphics. A user will, in some circumstances, need to perform such manipulations on user interface objects in a file management program (e.g., Finder from Apple Inc. of Cupertino, Calif.), an image management application (e.g., Aperture, iPhoto, Photos from Apple Inc. of Cupertino, Calif.), a digital content (e.g., videos and music) management application (e.g., iTunes from Apple Inc. of Cupertino, Calif.), a drawing application, a presentation application (e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processing application (e.g., Pages from Apple Inc. of Cupertino, Calif.), or a spreadsheet application (e.g., Numbers from Apple Inc. of Cupertino, Calif.).
Haptic feedback, typically in combination with visual and/or audio feedback, is often used to indicate a particular state of electronic devices.
But methods for performing these manipulations are cumbersome and inefficient. For example, using a sequence of mouse based inputs to select one or more user interface objects and perform one or more actions on the selected user interface objects is tedious and creates a significant cognitive burden on a user. In addition, these methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, there is a need for electronic devices with faster, more efficient methods and interfaces for providing haptic feedback to a user while providing access to locked mode device features, but preventing accidental activation of such features, and for providing an improved camera application user interface that provides tactile outputs that confirm user actions, but suppresses or reduces the generation of tactile outputs when such tactile outputs would disrupt or reduce the quality of the audio portion of media captured in certain operating modes. Such methods and interfaces optionally complement or replace conventional methods for providing access to locked mode features, and capturing media with a camera application. Such methods and interfaces reduce the number, extent, and/or nature of the inputs from a user and produce a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.
The above deficiencies and other problems associated with user interfaces for electronic devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch-screen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, note taking, and/or digital video playing. Executable instructions for performing these functions are, optionally, included in a non-transitory computer readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, a method performed at an electronic device with a display, a touch-sensitive surface, and one or more tactile output generators, includes displaying, on the display, a user interface that includes a respective user interface element, wherein the respective user interface element is associated with a respective operation. The method further includes detecting, on the touch-sensitive surface, a user input directed to the respective user interface element, including detecting a contact at a location that corresponds to the respective user interface element and detecting a first portion of the user input that includes an increase in intensity of the contact followed by a second portion of the user input that includes a decrease in intensity of the contact. The method further includes, in response to detecting the user input, displaying a transformation of the respective user interface element, wherein a degree of the transformation is determined based on an intensity of the user input; and in accordance with a determination that the first portion of the user input satisfies feed-forward criteria, wherein the feed-forward criteria include a requirement that a characteristic intensity of the contact increase above a feed-forward intensity threshold in order for the feed-forward criteria to be met, generating a first tactile output without performing the respective operation.
The method further includes, in accordance with a determination that the second portion of the user input satisfies activation criteria, wherein the activation criteria include a requirement that the characteristic intensity of the contact decrease below an activation intensity threshold: generating a second tactile output; and performing, at the device, the respective operation associated with the respective user interface element. Further, the method includes, in accordance with a determination that the characteristic intensity of the contact does not satisfy the feed-forward intensity threshold during the user input: forgoing generating the first tactile output and the second tactile output; and forgoing performing the respective operation associated with the respective user interface element.
In accordance with some embodiments, a method performed at an electronic device with one or more input devices, one or more output devices, and one or more tactile output generators, includes displaying a camera user interface for capturing media, wherein the camera has a plurality of media capture modes. The method further includes, while displaying the camera user interface, detecting, via the one or more input devices, activation of a capture affordance, and in response to detecting, via the one or more input devices, activation of the capture affordance: in accordance with a determination that the activation of the capture affordance was detected while the camera user interface was in a first media capture mode, wherein capturing media in the first media capture mode includes capturing media of a first type that includes one or more images captured without audio: capturing media of the first type, and generating a first tactile output. The method further includes, in response to detecting, via the one or more input devices, activation of the capture affordance: in accordance with a determination that the activation of the capture affordance was detected while the camera user interface was in a second media capture mode that is distinct from the first media capture mode, wherein capturing media in the second media capture mode includes capturing media of a second type that includes a sequence of images and corresponding audio: capturing media of the second type, and forgoing generating the first tactile output in response to activation of the capture affordance.
In accordance with some embodiments, an electronic device includes a display, a touch-sensitive surface, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally one or more tactile output generators, one or more processors, and memory storing one or more programs; the one or more programs are configured to be executed by the one or more processors and the one or more programs include instructions for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, a computer readable storage medium has stored therein instructions, which, when executed by an electronic device with a display, a touch-sensitive surface, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, and optionally one or more tactile output generators, cause the device to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a graphical user interface on an electronic device with a display, a touch-sensitive surface, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally one or more tactile output generators, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described herein, which are updated in response to inputs, as described in any of the methods described herein. In accordance with some embodiments, an electronic device includes: a display, a touch-sensitive surface, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, and optionally one or more tactile output generators; and means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display, a touch-sensitive surface, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, and optionally one or more tactile output generators, includes means for performing or causing performance of the operations of any of the methods described herein.
Thus, electronic devices with displays, touch-sensitive surfaces, optionally one or more sensors to detect intensities of contacts with the touch-sensitive surface, optionally one or more tactile output generators, optionally one or more device orientation sensors, and optionally an audio system, are provided with improved methods and interfaces for providing tactile outputs, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for providing tactile outputs.
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.
Many electronic devices have graphical user interfaces for use when the device is in a locked mode of operation, for authenticating the user, as well as for providing access to a reduced set of device features, such as for toggling a state of a flashlight in the device, and for enabling use of a camera in the device using a camera application. As described in more detail below, to ensure that user inputs to access such features are not accidental, a variety of intensity-based criteria, time-base criteria, and tactile outputs are employed to both make use of the device efficient and intuitive, thereby enabling intuitive and fast access to the locked mode features while reducing the likelihood of inadvertent activations of such features.
Many electronic devices provide feedback as input is detected at a graphical user interface to provide an indication of the effects the input has on device operations. Methods described herein provide haptic feedback, often in conjunction with visual and/or audio feedback, to help a user understand the effects of detected inputs on device operations and to provide information to a user about the state of a device.
Below,
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact, unless the context clearly indicates otherwise.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Example embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch-screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a note taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. Using tactile outputs to provide haptic feedback to a 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, a tactile output pattern specifies characteristics of a tactile output, such as the amplitude of the tactile output, the shape of a movement waveform of the tactile output, the frequency of the tactile output, and/or the duration of the tactile output.
When tactile outputs with different tactile output patterns are generated by a device (e.g., via one or more tactile output generators that move a moveable mass to generate tactile outputs), the tactile outputs may invoke different haptic sensations in a user holding or touching the device. While the sensation of the user is based on the user's perception of the tactile output, most users will be able to identify changes in waveform, frequency, and amplitude of tactile outputs generated by the device. Thus, the waveform, frequency and amplitude can be adjusted to indicate to the user that different operations have been performed. As such, tactile outputs with tactile output patterns that are designed, selected, and/or engineered to simulate characteristics (e.g., size, material, weight, stiffness, smoothness, etc.); behaviors (e.g., oscillation, displacement, acceleration, rotation, expansion, etc.); and/or interactions (e.g., collision, adhesion, repulsion, attraction, friction, etc.) of objects in a given environment (e.g., a user interface that includes graphical features and objects, a simulated physical environment with virtual boundaries and virtual objects, a real physical environment with physical boundaries and physical objects, and/or a combination of any of the above) will, in some circumstances, provide helpful feedback to users that reduces input errors and increases the efficiency of the user's operation of the device. Additionally, tactile outputs are, optionally, generated to correspond to feedback that is unrelated to a simulated physical characteristic, such as an input threshold or a selection of an object. Such tactile outputs will, in some circumstances, provide helpful feedback to users that reduces input errors and increases the efficiency of the user's operation of the device.
In some embodiments, a tactile output with a suitable tactile output pattern serves as a cue for the occurrence of an event of interest in a user interface or behind the scenes in a device. Examples of the events of interest include activation of an affordance (e.g., a real or virtual button, or toggle switch) provided on the device or in a user interface, success or failure of a requested operation, reaching or crossing a boundary in a user interface, entry into a new state, switching of input focus between objects, activation of a new mode, reaching or crossing an input threshold, detection or recognition of a type of input or gesture, etc. In some embodiments, tactile outputs are provided to serve as a warning or an alert for an impending event or outcome that would occur unless a redirection or interruption input is timely detected. Tactile outputs are also used in other contexts to enrich the user experience, improve the accessibility of the device to users with visual or motor difficulties or other accessibility needs, and/or improve efficiency and functionality of the user interface and/or the device. Tactile outputs are optionally accompanied with audio outputs and/or visible user interface changes, which further enhance a user's experience when the user interacts with a user interface and/or the device, and facilitate better conveyance of information regarding the state of the user interface and/or the device, and which reduce input errors and increase the efficiency of the user's operation of the device.
As shown in
As shown in
Although specific frequencies, amplitudes, and waveforms are represented in the sample tactile output patterns in
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU(s) 120 and the peripherals interface 118, is, optionally, controlled by memory controller 122.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU(s) 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
In some embodiments, peripherals interface 118, CPU(s) 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication optionally uses any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch-sensitive display system 112 and other input or control devices 116, with peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled with any (or none) of the following: a keyboard, infrared port, USB port, stylus, and/or a pointer device such as a mouse. The one or more buttons (e.g., 208,
Touch-sensitive display system 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term “affordance” refers to a user-interactive graphical user interface object (e.g., a graphical user interface object that is configured to respond to inputs directed toward the graphical user interface object). Examples of user-interactive graphical user interface objects include, without limitation, a button, slider, icon, selectable menu item, switch, hyperlink, or other user interface control.
Touch-sensitive display system 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch-sensitive display system 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch-sensitive display system 112. In some embodiments, a point of contact between touch-sensitive display system 112 and the user corresponds to a finger of the user or a stylus.
Touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112. In some embodiments, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.
Touch-sensitive display system 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen video resolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally makes contact with touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch-sensitive display system 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, haptic feedback module (or set of instructions) 133, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 stores device/global internal state 157, as shown in
Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. In some embodiments, the external port is a Lightning connector that is the same as, or similar to and/or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif.
Contact/motion module 130 optionally detects contact with touch-sensitive display system 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact (e.g., by a finger or by a stylus), such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts or stylus contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event. Similarly, tap, swipe, drag, and other gestures are optionally detected for a stylus by detecting a particular contact pattern for the stylus.
In some embodiments, detecting a finger tap gesture depends on the length of time between detecting the finger-down event and the finger-up event, but is independent of the intensity of the finger contact between detecting the finger-down event and the finger-up event. In some embodiments, a tap gesture is detected in accordance with a determination that the length of time between the finger-down event and the finger-up event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4 or 0.5 seconds), independent of whether the intensity of the finger contact during the tap meets a given intensity threshold (greater than a nominal contact-detection intensity threshold), such as a light press or deep press intensity threshold. Thus, a finger tap gesture can satisfy particular input criteria that do not require that the characteristic intensity of a contact satisfy a given intensity threshold in order for the particular input criteria to be met. For clarity, the finger contact in a tap gesture typically needs to satisfy a nominal contact-detection intensity threshold, below which the contact is not detected, in order for the finger-down event to be detected. A similar analysis applies to detecting a tap gesture by a stylus or other contact. In cases where the device is capable of detecting a finger or stylus contact hovering over a touch sensitive surface, the nominal contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch sensitive surface.
The same concepts apply in an analogous manner to other types of gestures. For example, a swipe gesture, a pinch gesture, a depinch gesture, and/or a long press gesture are optionally detected based on the satisfaction of criteria that are either independent of intensities of contacts included in the gesture, or do not require that contact(s) that perform the gesture reach intensity thresholds in order to be recognized. For example, a swipe gesture is detected based on an amount of movement of one or more contacts; a pinch gesture is detected based on movement of two or more contacts towards each other; a depinch gesture is detected based on movement of two or more contacts away from each other; and a long press gesture is detected based on a duration of the contact on the touch-sensitive surface with less than a threshold amount of movement. As such, the statement that particular gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met means that the particular gesture recognition criteria are capable of being satisfied if the contact(s) in the gesture do not reach the respective intensity threshold, and are also capable of being satisfied in circumstances where one or more of the contacts in the gesture do reach or exceed the respective intensity threshold. In some embodiments, a tap gesture is detected based on a determination that the finger-down and finger-up event are detected within a predefined time period, without regard to whether the contact is above or below the respective intensity threshold during the predefined time period, and a swipe gesture is detected based on a determination that the contact movement is greater than a predefined magnitude, even if the contact is above the respective intensity threshold at the end of the contact movement. Even in implementations where detection of a gesture is influenced by the intensity of contacts performing the gesture (e.g., the device detects a long press more quickly when the intensity of the contact is above an intensity threshold or delays detection of a tap input when the intensity of the contact is higher), the detection of those gestures does not require that the contacts reach a particular intensity threshold so long as the criteria for recognizing the gesture can be met in circumstances where the contact does not reach the particular intensity threshold (e.g., even if the amount of time that it takes to recognize the gesture changes).
Contact intensity thresholds, duration thresholds, and movement thresholds are, in some circumstances, combined in a variety of different combinations in order to create heuristics for distinguishing two or more different gestures directed to the same input element or region so that multiple different interactions with the same input element are enabled to provide a richer set of user interactions and responses. The statement that a particular set of gesture recognition criteria do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met does not preclude the concurrent evaluation of other intensity-dependent gesture recognition criteria to identify other gestures that do have a criterion that is met when a gesture includes a contact with an intensity above the respective intensity threshold. For example, in some circumstances, first gesture recognition criteria for a first gesture—which do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met—are in competition with second gesture recognition criteria for a second gesture—which are dependent on the contact(s) reaching the respective intensity threshold. In such competitions, the gesture is, optionally, not recognized as meeting the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are met first. For example, if a contact reaches the respective intensity threshold before the contact moves by a predefined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves by the predefined amount of movement before the contact reaches the respective intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such circumstances, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the first gesture recognition criteria to be met because if the contact stayed below the respective intensity threshold until an end of the gesture (e.g., a swipe gesture with a contact that does not increase to an intensity above the respective intensity threshold), the gesture would have been recognized by the first gesture recognition criteria as a swipe gesture. As such, particular gesture recognition criteria that do not require that the intensity of the contact(s) meet a respective intensity threshold in order for the particular gesture recognition criteria to be met will (A) in some circumstances ignore the intensity of the contact with respect to the intensity threshold (e.g. for a tap gesture) and/or (B) in some circumstances still be dependent on the intensity of the contact with respect to the intensity threshold in the sense that the particular gesture recognition criteria (e.g., for a long press gesture) will fail if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognize an input as corresponding to an intensity-dependent gesture before the particular gesture recognition criteria recognize a gesture corresponding to the input (e.g., for a long press gesture that is competing with a deep press gesture for recognition).
Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions (e.g., instructions used by haptic feedback controller 161) to produce tactile outputs using tactile output generator(s) 167 at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 includes executable instructions to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers and/or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, Apple Push Notification Service (APNs) or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and video and music player module 152, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (in sports devices and smart watches); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.
In conjunction with touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, and/or delete a still image or video from memory 102.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 includes executable instructions to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch-sensitive display system 112, or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes executable instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen 112, or on an external display connected wirelessly or via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display system 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display system 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch-sensitive display system 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display system 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display system 112, when a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video and music player module 152. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input-devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
In some embodiments, the tactile output module includes haptic feedback module 133. In some embodiments, haptic feedback module 133 aggregates and combines tactile outputs for user interface feedback from software applications on the electronic device (e.g., feedback that is responsive to user inputs that correspond to displayed user interfaces and alerts and other notifications that indicate the performance of operations or occurrence of events in user interfaces of the electronic device). Haptic feedback module 133 includes one or more of: waveform module 123 (for providing waveforms used for generating tactile outputs), mixer 125 (for mixing waveforms, such as waveforms in different channels), compressor 127 (for reducing or compressing a dynamic range of the waveforms), low-pass filter 129 (for filtering out high frequency signal components in the waveforms), and thermal controller 131 (for adjusting the waveforms in accordance with thermal conditions). In some embodiments, haptic feedback module 133 is included in haptic feedback controller 161 (
In some embodiments, haptic feedback module 133 also includes trigger module 121 (e.g., a software application, operating system, or other software module that determines a tactile output is to be generated and initiates the process for generating the corresponding tactile output). In some embodiments, trigger module 121 generates trigger signals for initiating generation of waveforms (e.g., by waveform module 123). For example, trigger module 121 generates trigger signals based on preset timing criteria. In some embodiments, trigger module 121 receives trigger signals from outside haptic feedback module 133 (e.g., in some embodiments, haptic feedback module 133 receives trigger signals from hardware input processing module 146 located outside haptic feedback module 133) and relays the trigger signals to other components within haptic feedback module 133 (e.g., waveform module 123) or software applications that trigger operations (e.g., with trigger module 121) based on activation of a user interface element (e.g., an application icon or an affordance within an application) or a hardware input device (e.g., a home button or an intensity-sensitive input surface, such as an intensity-sensitive touch screen). In some embodiments, trigger module 121 also receives tactile feedback generation instructions (e.g., from haptic feedback module 133,
Waveform module 123 receives trigger signals (e.g., from trigger module 121) as an input, and in response to receiving trigger signals, provides waveforms for generation of one or more tactile outputs (e.g., waveforms selected from a predefined set of waveforms designated for use by waveform module 123, such as the waveforms described in greater detail below with reference to
Mixer 125 receives waveforms (e.g., from waveform module 123) as an input, and mixes together the waveforms. For example, when mixer 125 receives two or more waveforms (e.g., a first waveform in a first channel and a second waveform that at least partially overlaps with the first waveform in a second channel) mixer 125 outputs a combined waveform that corresponds to a sum of the two or more waveforms. In some embodiments, mixer 125 also modifies one or more waveforms of the two or more waveforms to emphasize particular waveform(s) over the rest of the two or more waveforms (e.g., by increasing a scale of the particular waveform(s) and/or decreasing a scale of the rest of the waveforms). In some circumstances, mixer 125 selects one or more waveforms to remove from the combined waveform (e.g., the waveform from the oldest source is dropped when there are waveforms from more than three sources that have been requested to be output concurrently by tactile output generator 167).
Compressor 127 receives waveforms (e.g., a combined waveform from mixer 125) as an input, and modifies the waveforms. In some embodiments, compressor 127 reduces the waveforms (e.g., in accordance with physical specifications of tactile output generators 167 (
Low-pass filter 129 receives waveforms (e.g., compressed waveforms from compressor 127) as an input, and filters (e.g., smooths) the waveforms (e.g., removes or reduces high frequency signal components in the waveforms). For example, in some instances, compressor 127 includes, in compressed waveforms, extraneous signals (e.g., high frequency signal components) that interfere with the generation of tactile outputs and/or exceed performance specifications of tactile output generator 167 when the tactile outputs are generated in accordance with the compressed waveforms. Low-pass filter 129 reduces or removes such extraneous signals in the waveforms.
Thermal controller 131 receives waveforms (e.g., filtered waveforms from low-pass filter 129) as an input, and adjusts the waveforms in accordance with thermal conditions of device 100 (e.g., based on internal temperatures detected within device 100, such as the temperature of haptic feedback controller 161, and/or external temperatures detected by device 100). For example, in some cases, the output of haptic feedback controller 161 varies depending on the temperature (e.g. haptic feedback controller 161, in response to receiving same waveforms, generates a first tactile output when haptic feedback controller 161 is at a first temperature and generates a second tactile output when haptic feedback controller 161 is at a second temperature that is distinct from the first temperature). For example, the magnitude (or the amplitude) of the tactile outputs may vary depending on the temperature. To reduce the effect of the temperature variations, the waveforms are modified (e.g., an amplitude of the waveforms is increased or decreased based on the temperature).
In some embodiments, haptic feedback module 133 (e.g., trigger module 121) is coupled to hardware input processing module 146. In some embodiments, other input controller(s) 160 in
In some embodiments, the tactile output module includes haptic feedback controller 161 (e.g., haptic feedback controller 161 in
In some embodiments, as shown in
In some embodiments, the tactile output module includes amplifier 163. In some embodiments, amplifier 163 receives waveforms (e.g., from haptic feedback controller 161) and amplifies the waveforms prior to sending the amplified waveforms to tactile output generator 167 (e.g., any of tactile output generators 167 (
In some embodiments, the tactile output module includes sensor 169, which is coupled to tactile output generator 167. Sensor 169 detects states or state changes (e.g., mechanical position, physical displacement, and/or movement) of tactile output generator 167 or one or more components of tactile output generator 167 (e.g., one or more moving parts, such as a membrane, used to generate tactile outputs). In some embodiments, sensor 169 is a magnetic field sensor (e.g., a Hall effect sensor) or other displacement and/or movement sensor. In some embodiments, sensor 169 provides information (e.g., a position, a displacement, and/or a movement of one or more parts in tactile output generator 167) to haptic feedback controller 161 and, in accordance with the information provided by sensor 169 about the state of tactile output generator 167, haptic feedback controller 161 adjusts the waveforms output from haptic feedback controller 161 (e.g., waveforms sent to tactile output generator 167, optionally via amplifier 163).
Device 100 optionally also includes one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch-screen display.
In some embodiments, device 100 includes the touch-screen display, menu button 204 (sometimes called home button 204), push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensities of contacts on touch-sensitive display system 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above identified elements in
Attention is now directed towards embodiments of user interfaces (“UI”) that are, optionally, implemented on portable multifunction device 100.
It should be noted that the icon labels illustrated in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures, etc.), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or a stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector,” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average or a sum) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be readily accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch-screen display can be set to any of a large range of predefined thresholds values without changing the trackpad or touch-screen display hardware. Additionally, in some implementations a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, a value produced by low-pass filtering the intensity of the contact over a predefined period or starting at a predefined time, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first intensity threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second intensity threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more intensity thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective option or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location (e.g., a drag gesture), at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm may be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The user interface figures described herein optionally include various intensity diagrams that show the current intensity of the contact on the touch-sensitive surface relative to one or more intensity thresholds (e.g., a contact detection intensity threshold IT0, a light press intensity threshold ITL, a deep press intensity threshold ITD) (e.g., that is at least initially higher than ITL), and/or one or more other intensity thresholds (e.g., an intensity threshold ITH that is lower than ITL)). This intensity diagram is typically not part of the displayed user interface, but is provided to aid in the interpretation of the figures. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold IT0 below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
In some embodiments, the response of the device to inputs detected by the device depends on criteria based on the contact intensity during the input. For example, for some “light press” inputs, the intensity of a contact exceeding a first intensity threshold during the input triggers a first response. In some embodiments, the response of the device to inputs detected by the device depends on criteria that include both the contact intensity during the input and time-based criteria. For example, for some “deep press” inputs, the intensity of a contact exceeding a second intensity threshold during the input, greater than the first intensity threshold for a light press, triggers a second response only if a delay time has elapsed between meeting the first intensity threshold and meeting the second intensity threshold. This delay time is typically less than 200 ms (milliseconds) in duration (e.g., 40, 100, or 120 ms, depending on the magnitude of the second intensity threshold, with the delay time increasing as the second intensity threshold increases). This delay time helps to avoid accidental recognition of deep press inputs. As another example, for some “deep press” inputs, there is a reduced-sensitivity time period that occurs after the time at which the first intensity threshold is met. During the reduced-sensitivity time period, the second intensity threshold is increased. This temporary increase in the second intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to detection of a deep press input does not depend on time-based criteria.
In some embodiments, one or more of the input intensity thresholds and/or the corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application running, rate at which the intensity is applied, number of concurrent inputs, user history, environmental factors (e.g., ambient noise), focus selector position, and the like. Example factors are described in U.S. patent application Ser. Nos. 14/399,606 and 14/624,296, which are incorporated by reference herein in their entireties.
For example,
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold ITL to an intensity between the light press intensity threshold ITL and the deep press intensity threshold ITD is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold ITD to an intensity above the deep press intensity threshold ITD is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold IT0 to an intensity between the contact-detection intensity threshold IT0 and the light press intensity threshold ITL is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold IT0 to an intensity below the contact-detection intensity threshold IT0 is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments IT0 is zero. In some embodiments, IT0 is greater than zero. In some illustrations a shaded circle or oval is used to represent intensity of a contact on the touch-sensitive surface. In some illustrations, a circle or oval without shading is used represent a respective contact on the touch-sensitive surface without specifying the intensity of the respective contact.
In some embodiments, described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., the respective operation is performed on a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., the respective operation is performed on an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., the respective operation is performed on an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the description of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. As described above, in some embodiments, the triggering of these responses also depends on time-based criteria being met (e.g., a delay time has elapsed between a first intensity threshold being met and a second intensity threshold being met).
Although only specific frequencies, amplitudes, and waveforms are represented in the sample tactile output patterns in
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device, such as portable multifunction device 100 or device 300, with a display, a touch-sensitive surface, (optionally) one or more tactile output generators for generating tactile outputs, and (optionally) one or more sensors to detect intensities of contacts with the touch-sensitive surface.
In some embodiments, tactile output 518, and other tactile outputs 522, 524, 528, 530, 532, 558, 570, 572, 588, 596, 589, 585 and 569 are implemented using various ones of tactile outputs types described above with respect to
In some embodiments, tactile output 522 is generated (e.g., with tactile output intensity level 520b) in accordance with the intensity of contact 514 reaching intensity threshold ITD, but tactile outputs are not generated prior to the intensity of contact 514 reaching intensity threshold ITD.
With reference to
In some embodiments, a minimum time interval TIB is enforced between generation of sequential tactile outputs, such that if a tactile output is generated at time T, no tactile output is generated at any time between time T and time T+TIB. For example, synchronous tactile output graph 592 shows that, in some embodiments in which tactile outputs are generated synchronously with capturing images, a first tactile output, corresponding to the image captured at time t0, is generated. Generation of a second tactile output, corresponding to the image captured at time t1, is forgone, because the second tactile output would be generated during the time interval TIB since the first tactile output was generated. A third tactile output, corresponding to the image captured at time t2, is generated, because the third tactile output is generated after the time interval TIB since the first tactile output was generated. Similarly, generation of tactile outputs corresponding to images captured at times t3, t5, and t7, is forgone, while tactile outputs corresponding to images captured at times t4 and t6 are generated.
In another example, asynchronous tactile output graph 593 shows that, in some embodiments in which tactile outputs are generated asynchronously with capturing images, after the first tactile output, corresponding to the image captured at time t0, is generated, additional tactile outputs are repeatedly generated at time intervals equal to TIB, while the input intensity remains above intensity threshold ITH, and without regard to times t1, t2, t3, t4, t5, t6, and t7 at which the additional images were captured.
Lock Screen UI with Intensity-Based Activation Criteria and Tactile Feedback
As described below, method 600 provides an intuitive way to access features that user's commonly want to remain available even while a device is operating in a locked mode of operation. The method reduces the number, extent, and/or nature of the inputs from a user when activating a locked-mode device feature, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to activate locked-mode device features, while preventing accidental activation of such features conserves power and increases the time between battery charges, without unduly burdening the user of the device.
Method 600, which is performed at (and thus performed by) an electronic device with a display, a touch-sensitive surface, and one or more tactile output generators (602), includes displaying (604), on the display, a user interface that includes a respective user interface element, wherein the respective user interface element is associated with (e.g., corresponds to) a respective operation. For example, as shown in
Method 600 further includes detecting (606), on the touch-sensitive surface, a user input directed to the respective user interface element, including detecting a contact at a location that corresponds to the respective user interface element and detecting a first portion of the user input that includes an increase in intensity of the contact followed by a second portion of the user input that includes a decrease in intensity of the contact. For example, the user input can be touch input 514, discussed above with reference to
Method 600 further includes, in response to detecting the user input (608), displaying (610) a transformation of the respective user interface element, wherein a degree of the transformation is determined based on an intensity of the user input (e.g., increasing a size, or scale, of the respective user interface element from its initial size or scale, opacity, brightness and/or changing one or more colors of the respective user interface element from its initial color(s). In some embodiments, the transformation in visual appearance of a respective user interface element progresses as a function of detected intensity of the user input corresponding to (directed to) the respective user interface element. Examples of such transformations are discussed above with reference to flashlight icon in
Method 600 further includes, in accordance with a determination (612) that the first portion of the user input satisfies feed-forward criteria, wherein the feed-forward criteria include a requirement that a characteristic intensity of the contact increase above a feed-forward intensity threshold (e.g., increases above a predefined intensity threshold, such as deep press threshold ITD, as shown in
Method 600 further includes, in accordance with a determination (620) that the second portion of the user input satisfies activation criteria, wherein the activation criteria include a requirement that the characteristic intensity of the contact decrease below an activation intensity threshold: generating (622) a second tactile output, and performing (624), at the device, the respective operation associated with the respective user interface element (e.g., activating/deactivating a function associated with the respective user interface element, such as toggling a flashlight on or off (see above discussion of
In some embodiments, the activation intensity threshold is a first intensity threshold, such as deep press threshold ITD, or a second intensity threshold that is lower than the first intensity threshold. In some embodiments, the activation intensity threshold is selected to be a predetermined amount less than the first intensity threshold or a predetermined amount less than a peak intensity of the contact during the user input.
In some embodiments, the first tactile output and the second tactile output are distinct instances of the same tactile output. For example, the first tactile output and the second tactile output have the same tactile output pattern, the same amplitude, and the same duration. In some embodiments, the first tactile output and the second tactile output are different tactile outputs. For example, the first tactile output and the second tactile output differ by one or more of: tactile output pattern, amplitude, and duration.
Method 600 further includes, in accordance with a determination (626) that the characteristic intensity of the contact does not satisfy the feed-forward intensity threshold during the user input (e.g., the detected intensity of the user input remains below the intensity threshold, for example during a tap or a long press user input): forgoing (628) generating the first tactile output and the second tactile output, and forgoing (630) performing the respective operation associated with the respective user interface element. Forgoing generation of the first tactile output and the second tactile output in the recited circumstance in conjunction with generation of those tactile outputs in other circumstances, as described above, promotes efficient use of the device by letting the user know, via the generation or absence of tactile outputs, when the user's input has not satisfied the criteria (e.g., the feed-forward intensity threshold) for causing cause initiation or performance of the respective operation.
In some embodiments, the activation criteria further include (634) a requirement that the contact remain on the touch-sensitive surface for at least a predefined threshold amount of time in order for the activation criteria to be met (e.g., a predefined amount of time since the contact was detected). See above discussion of predefined time period TA with respect to
In some embodiments, in accordance with a determination that the first portion of the user input satisfies the feed-forward intensity threshold requirement, the first tactile output is generated, and in accordance with a determination that the second portion of the user input satisfies the activation intensity threshold requirement, the second tactile output is generated, without regard to whether the activation time duration requirement is met. More generally, the first and second tactile outputs are generated based on intensity of the contact without regard to whether the operation is performed.
In some embodiments, generation of the first and/or second tactile outputs also requires that the contact remain on the touch-sensitive surface for at least the predefined threshold amount of time (e.g., the feed-forward criteria and the activation criteria both include a time duration requirement, as discussed above with reference to
In some embodiments, the respective operation is performed (632) while continuing to detect the contact on the touch-sensitive surface, and, after performing the respective operation, the transformation of the respective user interface element continues to be displayed as the intensity of the contact decreases. An example of this is discussed above with reference to
In some embodiments of method 600, the user interface that includes (635) the respective user interface element is displayed in accordance with a determination that the device is in a locked state. For example, in some embodiments, the user interface (e.g., a wake screen interface) is displayed in response to waking the device from a screen-off state to a screen-on state.
In some embodiments of method 600, the electronic device includes (636) a flashlight (e.g., a light on the device that serves as a flashlight, such as a light optionally used as a camera flash), and the respective user interface element is a flashlight icon for controlling a state (e.g., an on-off state) of the flashlight. Such embodiments are discussed above with reference to
In some embodiments of method 600, the electronic device includes (638) a camera, and the respective user interface element is a camera application icon for displaying a camera application user interface for the camera. Such embodiments are discussed above with reference to
In some embodiments of method 600, displaying the transformation of the respective user interface element includes (640) displaying a first transformation of the respective user interface element as the intensity of the user input increases, and reversing the first transformation as the intensity of the user input decreases. Such embodiments are discussed above with reference to flashlight icon 510 (e.g.,
In some embodiments of method 600, the degree of the transformation of the respective user interface element increases as the intensity of the input increases and decreases as the intensity of the input decreases (e.g., a higher characteristic intensity causes a greater change to the respective user interface element). Such embodiments are discussed above with reference to flashlight icon 510 (e.g.,
In some embodiments of method 600, the degree of the displaying the transformation of the respective user interface element starts (644) when the detected intensity of the user input satisfies (e.g., is above) a second intensity threshold (e.g., hint threshold ITH) that is below the feed-forward intensity threshold (e.g., deep press threshold ITD).
In some embodiments of method 600, the feed-forward criteria (see operation 612) further include (650) a requirement that the contact remain at the location that corresponds to the respective user interface element (e.g., a requirement that contact 514 remain at the location of flashlight icon 510,
In some embodiments of method 600, the feed-forward criteria further include (652) a requirement that the contact remain on the touch-sensitive surface for at least a predefined threshold amount of time in order for the feed-forward criteria to be met. For example, the amount of time the contact remains on the touch-sensitive surface would be measured starting when the contact is first detected, and would need to continue for at least the predefined amount of time (e.g., the activation time, TA, shown in
In some embodiments of method 600, the first tactile output includes (654) a sequence of tactile output components that change as the intensity of the contact increases (e.g., the amplitude, frequency and/or temporal spacing between sequential tactile output components increases or decreases as the intensity of the contact increases).
In some embodiments, method 600 includes, in accordance with a determination (656) that, after meeting the feed-forward criteria, the user input meets cancellation criteria, wherein the cancellation criteria include a requirement that the contact move more than a threshold distance from the respective activatable user interface object: reversing the transformation of the respective user interface object; forgoing performing the respective operation; and generating a cancellation tactile output. In some embodiments, the cancellation tactile output is the same as the second tactile output. An example of such an input that meets such cancellation criteria is discussed above with reference to
In some embodiments method 600 includes repeated activation of the user interface object in response to repetition of the activation gesture (e.g., toggling the state of the device's flashlight, again) with the same input continuing to be detected on the touch-sensitive surface, and example of which is shown in
Such embodiments of method 600 further includes, in accordance with a determination (664) that the fourth portion of the user input satisfies the activation criteria: generating (665) the second tactile output (or an instance of the second tactile output), and performing (666), at the device, the respective operation associated with the respective user interface element (e.g., toggling the state of the flashlight). In some embodiments, the transformation of the respective user interface element includes a further transformation in its visual appearance (e.g., a change in the colors of the flashlight icon when toggling the flashlight on or off). In some embodiments, performing the respective operation, such as toggling a state of a flashlight, includes performing a different sub-operation such as toggling a flashlight that was turned on by the user input from on to off, or toggling a flashlight that was turned off by the user input from off to on.
In some embodiments of method 600, the user interface is a first user interface (667), and method 600 includes detecting (668) a second user input (e.g., a press of a home button, or an upward swipe gesture starting from an edge of the device, and example of which is discussed above with reference to
In some embodiments, method 600 is repeated in response to a second user input on a second user interface element (e.g., a camera icon) associated with a second respective operation (e.g., displaying a camera application user interface), as discussed above with reference to
In such embodiments, method 600 further includes, in response to detecting (672) the second user input: displaying (673) a transformation of the second respective user interface element, wherein a degree of the of the second respective user interface element transformation is determined based on an intensity of the second user input (e.g., increasing a size, or scale, of the second respective user interface element from its initial size or scale, opacity, brightness and/or changing one or more colors of the respective user interface element from its initial color(s)), and in accordance with a determination that the first portion of the second user input satisfies the feed-forward criteria, generating (674) a third tactile output without performing the second respective operation. In some embodiments, the transformation in visual appearance of the second respective user interface element progresses as a function of detected intensity of the second user input corresponding to (directed to) the second respective user interface element.
In such embodiments, method 600 further includes, in accordance with a determination (675) that the second portion of the second user input satisfies the activation criteria: generating (676) a fourth tactile output, and performing (678), at the device, the second respective operation associated with the second respective user interface element (e.g., activating/deactivating a function associated with the respective user interface element, such as displaying a camera user interface). In some embodiments, the transformation of the respective user interface element includes a further transformation in its visual appearance (e.g., inverting or changing the colors of a flashlight icon when toggling the flashlight on or off). In some embodiments, the third tactile output and the fourth tactile output are distinct instances of the same tactile output. For example, the third tactile output and the fourth tactile output have the same tactile output pattern, the same amplitude, and the same duration. In some embodiments, the third tactile output and the fourth tactile output are different tactile outputs. For example, the third tactile output and the fourth tactile output differ by one or more of: tactile output pattern, amplitude, and duration.
Finally, in such embodiments, method 600 includes, in accordance with a determination (678) that a characteristic intensity of the second contact does not satisfy the feed-forward intensity threshold during the second user input (e.g., the detected intensity of the user input remains below the intensity threshold, such a light-intensity tap or long press): forgoing (679) generating the third tactile output and the fourth tactile output, and forgoing (680) performing the second respective operation associated with the second respective user interface element.
In some embodiments, method 600 includes, in accordance with a determination (681) that the respective operation associated with the respective user interface element includes activating a function associated with the respective user interface element (e.g., toggling a state of a device setting, such as from a first state to a second state, such as turning a flashlight on), the first tactile output and/or the second tactile output are instances of a first reference tactile output. Furthermore, in such embodiments, method 600 includes, in accordance with a determination (682) that the respective operation includes deactivating the function associated with the respective user interface element (e.g., toggling a state of a device setting, such as from the second state to the first state, such as turning the flashlight off), the first tactile output and/or the second tactile output are instances of a second reference tactile output that is distinct from the first reference tactile output. For example, one or more of the tactile outputs generated when activating a function are different from one or more of the corresponding tactile outputs when deactivating the function.
In some embodiments of method 600, the user interface includes (683) a third respective user interface element (e.g., a notification element, such as element 504 in
In some embodiments of method 600, the user interface includes (686) a plurality of user interface elements, other than the respective user interface element (e.g., the plurality of user interface elements are notifications, such as missed notifications, as shown in
In some embodiments of method 600, the user interface includes (690) a plurality of user interface elements, other than the respective user interface element (e.g., the plurality of user interface elements are notifications, such as missed notifications, as shown in
In some embodiments of method 600, the user interface includes (694) a background (e.g., wallpaper), and method 600 includes: detecting (696) a sixth user input (e.g., user input 562,
In some embodiments of method 600, displaying the animation of the background includes progressing through the animation of the background as the intensity of the sixth user input increases, and reversing the progression through the animation as the intensity of the sixth user input decreases. See above discussion of
It should be understood that the particular order in which the operations in
Context-Sensitive Tactile Output Suppression or Reduction in Camera Application
As described below, method 700 provides an intuitive visual and tactile feedback to users of a camera application, which facilitates efficient use of the camera application by users, and suppresses and/or reduces the amplitude of various tactile outputs so as to avoid interference with recording the audio portion of media being captured by the camera application. The method thereby facilitates capturing media with audio, without interference from tactile outputs, while still providing, in non-audio recording contexts of the camera application, tactile outputs that facilitate efficient use of the camera application by users, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, using tactile outputs to enable a user to select camera user interface features faster and more efficiently conserves power and increases the time between battery charges.
Method 700, which is performed at (and thus performed by) an electronic device with one or more input devices, one or more output devices, and one or more tactile output generators (702), includes displaying (704) a camera user interface for capturing media, wherein the camera has a plurality of media capture modes. Method 700 further includes, while displaying the camera user interface, detecting (706), via the one or more input devices, activation of a capture affordance (e.g., a displayed shutter button or a physical button that serves as a shutter button such as a volume up button). Method 700 further includes, in response (708) to detecting, via the one or more input devices, activation of the capture affordance: in accordance with a determination (710) that the activation of the capture affordance was detected while the camera user interface was in a first media capture mode (e.g., a still image capture mode), wherein capturing media in the first media capture mode includes capturing media of a first type that includes one or more images captured without audio: capturing (712) media of the first type (e.g., a still image), and generating (714) a first tactile output. An example of activation of a camera application's capture affordance and generation of a first tactile output is discussed above with reference to
Method 700 further includes, in response (708) to detecting, via the one or more input devices, activation of the capture affordance: in accordance with a determination (716) that the activation of the capture affordance was detected while the camera user interface was in a second media capture mode (e.g., a video capture or live photo capture mode) that is distinct from the first media capture mode, wherein capturing media in the second media capture mode includes capturing media of a second type that includes a sequence of images and corresponding audio (e.g., recording video, or capturing a live photo): capturing (716) media of the second type (e.g., a video, or a live photo), and forgoing (718) generating the first tactile output in response to activation of the capture affordance. An example of activation of a camera application's capture affordance while in a video capture mode, and forgoing generation of the first tactile output is discussed above with reference to
In some embodiments, method 700 includes detects a sequence of activations of the capture affordance, including a first activation of the capture affordance detected while the camera user interface is in the first media capture mode, and a second activation of the capture affordance detected while the camera user interface is in the second media capture mode. It is noted that, generating tactile outputs provides a user of the device with confirmation that an intended result has been achieved, but forgoing generating tactile outputs while recording media that includes audio reduces interference of the tactile outputs with the captured audio.
In some embodiments, method 700 includes, in response to detecting, via the one or more input devices, the activation of the capture affordance, in accordance with the determination that the activation of the capture affordance was detected while the camera user interface was in the second media capture mode, generating a (720) second tactile output that has a lower amplitude than the first tactile output in conjunction with capturing the media of the second type. In some embodiments, the second tactile output includes the first tactile output reduced to zero. More generally, in some embodiments, tactile outputs generated in the second media capture mode in response to activation of the capture affordance are reduced with respect to tactile outputs generated in the first media capture mode in response to activation of the capture affordance. It is noted that, generally, generating tactile outputs provides user with confirmation that an intended result has been achieved, but generating tactile outputs with lower amplitude while recording media that includes audio reduces interference of the tactile outputs with the captured audio, etc.
In some embodiments of method 700, the second tactile output includes (722) the first tactile output with reduced amplitude (e.g., the second tactile output is the result of attenuating an instance of the first tactile output). It is noted that reducing tactile output amplitude still provides the user with some feedback regarding a user input, or regarding an operation being performed by the device in response to a user input, but reduces interference with audio capture.
In some embodiments of method 700, for a respective tactile output generated while capturing the media of the second type, the respective tactile output is selected (724) based on a determination that the respective tactile output interferes with the captured media by an amount that is below a predefined threshold. Such embodiments provide the user with confirmation that an intended result has been achieved for certain predefined operations regardless of operating mode, thereby making use of the device and camera application more efficient, while reducing or minimizing disruption to media captured in certain operating modes (e.g., noise reduction for recorded audio).
In some embodiments of method 700, the second tactile output includes (726) the first tactile output with scale reduced to zero (e.g., the second tactile output includes or is implemented as tactile silence). Such embodiments, which reduce the scale of a tactile output to zero, remove all interference with audio capture, while still providing tactile outputs and their attendant benefits in other contexts of the camera application.
Generation of tactile outputs when a camera application is operating in a burst mode is discussed above with reference to
In some embodiments, tactile output generation for the sequence of images is asynchronous with the burst interval (e.g., see “Asynchronous Tactile Output” graphs 593,
Forgoing generation of tactile outputs based on time intervals from preceding tactile outputs reduces excessive generation of tactile outputs, thereby complying with hardware specifications and limitations and protecting tactile output generators. In addition, forgoing generation of tactile outputs based on time intervals from preceding tactile outputs reduces overloading the user with tactile outputs, thereby allowing the user to focus on more important tactile outputs. Thus, these features (e.g., 730-738 or a subset thereof) protect the device and makes the user-device interface more efficient (e.g., by providing more important tactile outputs and reducing user mistakes and/or unintended operations when operating/interacting with the device).
In some embodiments, method 700 including detecting (740) a user input to switch from a first respective media capture mode to a second respective media capture mode. For example, see above discussion of
Such embodiments of method 700 further include, in response (742) to detecting the user input: switching (744) the camera user interface from the first respective media capture mode to the second respective media capture mode; and generating (746) a third tactile output. More generally, in some embodiments, a tactile output (e.g., a third tactile output) is generated in conjunction with switching between media capture modes. In some embodiments, the third tactile output is different (e.g., has a different tactile output pattern) from the first tactile output and/or the second tactile output. These features provide the user of the device with confirmation that an intended result has been achieved, which helps avoid repeated user inputs that attempt to perform a function that has already been performed.
In some embodiments, method 700 includes, while displaying (750) the camera user interface, detecting, via the one or more input devices, a second user input (e.g., user input 598,
In such embodiments, method 700 further includes, in response to detecting the second user input via the one or more input devices, performing (752) the operation in the camera user interface and generating a fourth tactile output without regard to whether the camera user interface is in the first media capture mode (e.g., still image capture) or the second media capture mode (e.g., video capture or live photo capture). More generally, in some embodiments, a tactile output (e.g., the fourth tactile output) is generated in accordance with performing an operation in the user interface (e.g., an operation other than activation of the capture affordance) regardless of media capture mode. For example, the fourth tactile output is generated in accordance with performing the operation (e.g., changing a filter) in the first media capture mode (e.g., still photo capture), and the fourth tactile output (or an instance of the fourth tactile output) is also generated in accordance with performing the operation (e.g., changing a filter) in the second media capture mode (e.g., without regard to whether media, such as a video or a live photo, is being captured in the second media capture mode, and optionally even while buffering media to be captured, prior to detecting activation of the capture affordance, such as for a live photo), rather than being reduced in the second media capture mode. In some embodiments, the fourth tactile output is different (e.g., has a different tactile output pattern) from the first tactile output, and/or from the second tactile output, and/or from the third tactile output. Such embodiments consistently provide a user with confirmation that an intended result has been achieved for certain predefined operations, regardless of operating mode.
In some embodiments of method 700, the operation in the camera user interface includes changing a scale (e.g., changing a zoom factor, as shown in
In some embodiments of method 700, the operation in the camera user interface includes changing a filter setting of the camera user interface (e.g., tapping on a filter setting different from a currently-selected filter setting, or scrolling to or through a filter setting in a scrollable sequence of filter settings; see above discussion of
It should be understood that the particular order in which the operations in
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 invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated.
This application claims priority to U.S. Provisional Application Ser. No. 62/507,138, filed May 16, 2017, which is incorporate by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5959624 | Johnston, Jr. et al. | Sep 1999 | A |
| 5990869 | Kubica et al. | Nov 1999 | A |
| 6211861 | Rosenberg et al. | Apr 2001 | B1 |
| 6424251 | Byre | Jul 2002 | B1 |
| 6433771 | Yocum et al. | Aug 2002 | B1 |
| 6560165 | Barker | May 2003 | B1 |
| 7130664 | Williams | Oct 2006 | B1 |
| 7305257 | Ladouceur et al. | Dec 2007 | B2 |
| 7308253 | Moody et al. | Dec 2007 | B2 |
| 7469381 | Ording | Dec 2008 | B2 |
| 7479949 | Jobs et al. | Jan 2009 | B2 |
| 7720213 | Desai et al. | May 2010 | B2 |
| 7809406 | Weinans | Oct 2010 | B2 |
| 7958456 | Ording et al. | Jun 2011 | B2 |
| 7978183 | Rosenberg et al. | Jul 2011 | B2 |
| 8026814 | Heinze et al. | Sep 2011 | B1 |
| 8131848 | Denise | Mar 2012 | B1 |
| 8165640 | Mullen | Apr 2012 | B2 |
| 8204548 | Blinn et al. | Jun 2012 | B1 |
| 8207832 | Yun et al. | Jun 2012 | B2 |
| 8209606 | Ording | Jun 2012 | B2 |
| 8266550 | Cleron et al. | Sep 2012 | B1 |
| 8331268 | Hicks, III | Dec 2012 | B2 |
| 8509856 | Blinn et al. | Aug 2013 | B1 |
| 8548418 | Jintaseranee et al. | Oct 2013 | B1 |
| 8619051 | Lacroix et al. | Dec 2013 | B2 |
| 8624864 | Birnbaum et al. | Jan 2014 | B2 |
| 8659571 | Birnbaum et al. | Feb 2014 | B2 |
| 8676274 | Li | Mar 2014 | B2 |
| 8698766 | Ali et al. | Apr 2014 | B2 |
| 8712383 | Hayes et al. | Apr 2014 | B1 |
| 8717151 | Forutanpour et al. | May 2014 | B2 |
| 8750296 | Bosschaert et al. | Jun 2014 | B2 |
| 8754757 | Ullrich et al. | Jun 2014 | B1 |
| 8768838 | Hoffman | Jul 2014 | B1 |
| 8773356 | Martin et al. | Jul 2014 | B2 |
| 8886252 | Luke et al. | Nov 2014 | B2 |
| 8886576 | Sanketi et al. | Nov 2014 | B1 |
| 8914743 | Nakajima et al. | Dec 2014 | B2 |
| 9088668 | Salvador | Jul 2015 | B1 |
| 9092953 | Mortimer et al. | Jul 2015 | B1 |
| 9100805 | Oshita | Aug 2015 | B2 |
| 9110529 | Kido | Aug 2015 | B2 |
| 9110562 | Eldawy | Aug 2015 | B1 |
| 9166823 | Karmarkar | Oct 2015 | B2 |
| 9189932 | Kerdemelidis | Nov 2015 | B2 |
| 9247525 | Jacobs et al. | Jan 2016 | B2 |
| 9304675 | Lemay et al. | Apr 2016 | B2 |
| 9335924 | Jobs et al. | May 2016 | B2 |
| 9357052 | Ullrich | May 2016 | B2 |
| 9411422 | McClendon et al. | Aug 2016 | B1 |
| 9430796 | So | Aug 2016 | B1 |
| 9509829 | Culbert et al. | Nov 2016 | B2 |
| 9542820 | Moussette et al. | Jan 2017 | B2 |
| 9548050 | Gruber et al. | Jan 2017 | B2 |
| 9588586 | Rihn | Mar 2017 | B2 |
| 9600175 | Araki | Mar 2017 | B2 |
| 9652140 | Song et al. | May 2017 | B2 |
| 9658760 | Tee et al. | May 2017 | B2 |
| 9665960 | Masters et al. | May 2017 | B1 |
| 9690382 | Moussette et al. | Jun 2017 | B1 |
| 9830784 | Moussette et al. | Nov 2017 | B2 |
| 9852590 | Bhatia | Dec 2017 | B2 |
| 9864432 | Moussette et al. | Jan 2018 | B1 |
| 9928699 | Moussette et al. | Mar 2018 | B2 |
| 9954996 | Christie et al. | Apr 2018 | B2 |
| 9984539 | Moussette et al. | May 2018 | B2 |
| 10013162 | Fleizach et al. | Jul 2018 | B2 |
| 10034129 | Ellis et al. | Jul 2018 | B1 |
| 10276000 | Moussette et al. | Apr 2019 | B2 |
| 10791273 | Manzari et al. | Sep 2020 | B1 |
| 20010002126 | Rosenberg et al. | May 2001 | A1 |
| 20020080112 | Braun et al. | Jun 2002 | A1 |
| 20020115478 | Fujisawa et al. | Aug 2002 | A1 |
| 20040088353 | Mendelsohn et al. | May 2004 | A1 |
| 20040095311 | Tarlton et al. | May 2004 | A1 |
| 20040213401 | Aupperle et al. | Oct 2004 | A1 |
| 20040233161 | Shahoian et al. | Nov 2004 | A1 |
| 20050231489 | Ladouceur et al. | Oct 2005 | A1 |
| 20050275638 | Kolmykov-Zotov et al. | Dec 2005 | A1 |
| 20050285846 | Funaki | Dec 2005 | A1 |
| 20060026521 | Hotelling et al. | Feb 2006 | A1 |
| 20060026535 | Hotelling et al. | Feb 2006 | A1 |
| 20060045252 | Gorti et al. | Mar 2006 | A1 |
| 20060248183 | Barton | Nov 2006 | A1 |
| 20070046627 | Soh et al. | Mar 2007 | A1 |
| 20070055770 | Karmakar et al. | Mar 2007 | A1 |
| 20070088560 | Mock et al. | Apr 2007 | A1 |
| 20070106457 | Rosenberg | May 2007 | A1 |
| 20070132789 | Ording et al. | Jun 2007 | A1 |
| 20070146316 | Poupyrev et al. | Jun 2007 | A1 |
| 20070193436 | Chu | Aug 2007 | A1 |
| 20070226646 | Nagiyama et al. | Sep 2007 | A1 |
| 20070274503 | Klemm et al. | Nov 2007 | A1 |
| 20070283239 | Morris | Dec 2007 | A1 |
| 20080024459 | Poupyrev et al. | Jan 2008 | A1 |
| 20080122796 | Jobs et al. | May 2008 | A1 |
| 20080161062 | Harris et al. | Jul 2008 | A1 |
| 20080174570 | Jobs et al. | Jul 2008 | A1 |
| 20080270931 | Bamford | Oct 2008 | A1 |
| 20090075694 | Kim | Mar 2009 | A1 |
| 20090085878 | Heubel et al. | Apr 2009 | A1 |
| 20090128581 | Brid et al. | May 2009 | A1 |
| 20090135142 | Fu et al. | May 2009 | A1 |
| 20090167508 | Fadell et al. | Jul 2009 | A1 |
| 20090167509 | Fadell et al. | Jul 2009 | A1 |
| 20090167704 | Terlizzi et al. | Jul 2009 | A1 |
| 20090178008 | Herz et al. | Jul 2009 | A1 |
| 20090215432 | Matsuoka | Aug 2009 | A1 |
| 20090215479 | Karmarkar | Aug 2009 | A1 |
| 20090222902 | Bender et al. | Sep 2009 | A1 |
| 20090228825 | Van O's et al. | Sep 2009 | A1 |
| 20090231271 | Heubel et al. | Sep 2009 | A1 |
| 20090284463 | Morimoto et al. | Nov 2009 | A1 |
| 20090292990 | Park et al. | Nov 2009 | A1 |
| 20090303031 | Strohallen et al. | Dec 2009 | A1 |
| 20090322497 | Ku et al. | Dec 2009 | A1 |
| 20090325645 | Bang et al. | Dec 2009 | A1 |
| 20090325647 | Cho et al. | Dec 2009 | A1 |
| 20100017489 | Birnbaum et al. | Jan 2010 | A1 |
| 20100077328 | Berg et al. | Mar 2010 | A1 |
| 20100099445 | Song et al. | Apr 2010 | A1 |
| 20100114974 | Jung et al. | May 2010 | A1 |
| 20100141411 | Ahn et al. | Jun 2010 | A1 |
| 20100144395 | Komiya | Jun 2010 | A1 |
| 20100156818 | Burrough et al. | Jun 2010 | A1 |
| 20100188327 | Frid et al. | Jul 2010 | A1 |
| 20100231367 | Cruz-Hernandez et al. | Sep 2010 | A1 |
| 20100231534 | Chaudhri et al. | Sep 2010 | A1 |
| 20100231537 | Pisula et al. | Sep 2010 | A1 |
| 20100267424 | Kim et al. | Oct 2010 | A1 |
| 20100299638 | Choi | Nov 2010 | A1 |
| 20100302003 | Zellner | Dec 2010 | A1 |
| 20100302042 | Barnett et al. | Dec 2010 | A1 |
| 20100321411 | Paek et al. | Dec 2010 | A1 |
| 20110001707 | Faubert et al. | Jan 2011 | A1 |
| 20110017828 | Pine | Jan 2011 | A1 |
| 20110018695 | Bells et al. | Jan 2011 | A1 |
| 20110027381 | Gradl et al. | Feb 2011 | A1 |
| 20110053577 | Lee et al. | Mar 2011 | A1 |
| 20110055753 | Horodezky et al. | Mar 2011 | A1 |
| 20110061028 | Bachman et al. | Mar 2011 | A1 |
| 20110074695 | Rapp et al. | Mar 2011 | A1 |
| 20110081889 | Gao et al. | Apr 2011 | A1 |
| 20110102349 | Harris | May 2011 | A1 |
| 20110126148 | Krishnaraj et al. | May 2011 | A1 |
| 20110141142 | Leffert et al. | Jun 2011 | A1 |
| 20110148608 | Grant et al. | Jun 2011 | A1 |
| 20110179388 | Fleizach et al. | Jul 2011 | A1 |
| 20110190595 | Bennett et al. | Aug 2011 | A1 |
| 20110202843 | Morris | Aug 2011 | A1 |
| 20110210926 | Pasquero et al. | Sep 2011 | A1 |
| 20110252346 | Chaudhri et al. | Oct 2011 | A1 |
| 20110264491 | Birnbaum et al. | Oct 2011 | A1 |
| 20110266375 | Ono et al. | Nov 2011 | A1 |
| 20110267181 | Kildal | Nov 2011 | A1 |
| 20110267294 | Kildal | Nov 2011 | A1 |
| 20110270358 | Davis et al. | Nov 2011 | A1 |
| 20110271181 | Tsai et al. | Nov 2011 | A1 |
| 20110279380 | Weber | Nov 2011 | A1 |
| 20110279381 | Tong | Nov 2011 | A1 |
| 20110316698 | Palin et al. | Dec 2011 | A1 |
| 20120016879 | Groux et al. | Jan 2012 | A1 |
| 20120019365 | Tuikka et al. | Jan 2012 | A1 |
| 20120026110 | Yamano | Feb 2012 | A1 |
| 20120027216 | Tirry et al. | Feb 2012 | A1 |
| 20120028577 | Rodriguez et al. | Feb 2012 | A1 |
| 20120044251 | Mark et al. | Feb 2012 | A1 |
| 20120050324 | Jeong et al. | Mar 2012 | A1 |
| 20120056806 | Rosenberg et al. | Mar 2012 | A1 |
| 20120062491 | Coni et al. | Mar 2012 | A1 |
| 20120105367 | Son et al. | May 2012 | A1 |
| 20120173770 | Walker et al. | Jul 2012 | A1 |
| 20120174033 | Joo | Jul 2012 | A1 |
| 20120191704 | Jones | Jul 2012 | A1 |
| 20120216139 | Ording et al. | Aug 2012 | A1 |
| 20120229276 | Ronkainen | Sep 2012 | A1 |
| 20120249461 | Flanagan et al. | Oct 2012 | A1 |
| 20120268412 | Cruz-Hernandez et al. | Oct 2012 | A1 |
| 20120286943 | Rothkopf et al. | Nov 2012 | A1 |
| 20120286944 | Forutanpour et al. | Nov 2012 | A1 |
| 20120299857 | Grant et al. | Nov 2012 | A1 |
| 20120299859 | Kinoshita | Nov 2012 | A1 |
| 20120306631 | Hughes | Dec 2012 | A1 |
| 20120306632 | Fleizach et al. | Dec 2012 | A1 |
| 20120306790 | Kyung et al. | Dec 2012 | A1 |
| 20120311477 | Mattos et al. | Dec 2012 | A1 |
| 20120327006 | Israr et al. | Dec 2012 | A1 |
| 20130031507 | George | Jan 2013 | A1 |
| 20130091462 | Gray et al. | Apr 2013 | A1 |
| 20130165226 | Thorner | Jun 2013 | A1 |
| 20130167058 | Levee et al. | Jun 2013 | A1 |
| 20130174100 | Seymour et al. | Jul 2013 | A1 |
| 20130174137 | Kim | Jul 2013 | A1 |
| 20130201115 | Heubel | Aug 2013 | A1 |
| 20130222224 | Eriksson et al. | Aug 2013 | A1 |
| 20130225300 | Brinlee | Aug 2013 | A1 |
| 20130234929 | Libin | Sep 2013 | A1 |
| 20130244633 | Jacobs et al. | Sep 2013 | A1 |
| 20130262298 | Morley | Oct 2013 | A1 |
| 20130265268 | Okumura et al. | Oct 2013 | A1 |
| 20130282325 | Takahashi et al. | Oct 2013 | A1 |
| 20130290442 | Dgani | Oct 2013 | A1 |
| 20130300684 | Kim et al. | Nov 2013 | A1 |
| 20130307786 | Heubel | Nov 2013 | A1 |
| 20130316744 | Newham et al. | Nov 2013 | A1 |
| 20130318437 | Jung et al. | Nov 2013 | A1 |
| 20130321317 | Hirukawa | Dec 2013 | A1 |
| 20130321337 | Graham et al. | Dec 2013 | A1 |
| 20130326367 | Nakamura et al. | Dec 2013 | A1 |
| 20130332721 | Chaudhri et al. | Dec 2013 | A1 |
| 20140002386 | Rosenberg et al. | Jan 2014 | A1 |
| 20140007005 | Libin et al. | Jan 2014 | A1 |
| 20140024414 | Fuji | Jan 2014 | A1 |
| 20140039900 | Heubel et al. | Feb 2014 | A1 |
| 20140059427 | Dombrowski et al. | Feb 2014 | A1 |
| 20140074716 | Ni | Mar 2014 | A1 |
| 20140075375 | Hwang et al. | Mar 2014 | A1 |
| 20140082501 | Bae et al. | Mar 2014 | A1 |
| 20140091857 | Bernstein | Apr 2014 | A1 |
| 20140092037 | Kim | Apr 2014 | A1 |
| 20140132568 | Hirose et al. | May 2014 | A1 |
| 20140168105 | Zhou | Jun 2014 | A1 |
| 20140168110 | Araki et al. | Jun 2014 | A1 |
| 20140168124 | Park et al. | Jun 2014 | A1 |
| 20140176415 | Buuck et al. | Jun 2014 | A1 |
| 20140176452 | Aleksov et al. | Jun 2014 | A1 |
| 20140176455 | Araki et al. | Jun 2014 | A1 |
| 20140181222 | Geris et al. | Jun 2014 | A1 |
| 20140181756 | Kuo | Jun 2014 | A1 |
| 20140197946 | Park et al. | Jul 2014 | A1 |
| 20140207880 | Malkin et al. | Jul 2014 | A1 |
| 20140210740 | Lee | Jul 2014 | A1 |
| 20140215494 | Kim | Jul 2014 | A1 |
| 20140218317 | Aberg et al. | Aug 2014 | A1 |
| 20140232657 | Aviles et al. | Aug 2014 | A1 |
| 20140232679 | Whitman | Aug 2014 | A1 |
| 20140253319 | Chang | Sep 2014 | A1 |
| 20140258857 | Dykstra-Erickson et al. | Sep 2014 | A1 |
| 20140267076 | Birnbaum et al. | Sep 2014 | A1 |
| 20140273858 | Panther et al. | Sep 2014 | A1 |
| 20140281924 | Chipman et al. | Sep 2014 | A1 |
| 20140282011 | Dellinger et al. | Sep 2014 | A1 |
| 20140292501 | Lim et al. | Oct 2014 | A1 |
| 20140292668 | Fricklas et al. | Oct 2014 | A1 |
| 20140292706 | Hunt et al. | Oct 2014 | A1 |
| 20140298172 | Choi | Oct 2014 | A1 |
| 20140300454 | Lacroix et al. | Oct 2014 | A1 |
| 20140304651 | Johansson et al. | Oct 2014 | A1 |
| 20140320402 | Stahlberg | Oct 2014 | A1 |
| 20140320431 | Cruz-Hernandez et al. | Oct 2014 | A1 |
| 20140320435 | Modarres et al. | Oct 2014 | A1 |
| 20140325440 | Kondo | Oct 2014 | A1 |
| 20140329567 | Chan et al. | Nov 2014 | A1 |
| 20140333564 | Hong et al. | Nov 2014 | A1 |
| 20140340316 | Gu et al. | Nov 2014 | A1 |
| 20140351698 | Nakagawa | Nov 2014 | A1 |
| 20140358709 | Wu | Dec 2014 | A1 |
| 20140363113 | McGavran et al. | Dec 2014 | A1 |
| 20140368440 | Polyakov et al. | Dec 2014 | A1 |
| 20150002477 | Cheatham, III et al. | Jan 2015 | A1 |
| 20150020015 | Zhou | Jan 2015 | A1 |
| 20150050966 | West | Feb 2015 | A1 |
| 20150054727 | Saboune et al. | Feb 2015 | A1 |
| 20150062052 | Bernstein et al. | Mar 2015 | A1 |
| 20150067495 | Bernstein et al. | Mar 2015 | A1 |
| 20150067496 | Missig et al. | Mar 2015 | A1 |
| 20150067497 | Cieplinski | Mar 2015 | A1 |
| 20150067563 | Bernstein et al. | Mar 2015 | A1 |
| 20150067596 | Brown et al. | Mar 2015 | A1 |
| 20150070150 | Levesque et al. | Mar 2015 | A1 |
| 20150070153 | Bhatia | Mar 2015 | A1 |
| 20150070260 | Saboune et al. | Mar 2015 | A1 |
| 20150077335 | Taguchi et al. | Mar 2015 | A1 |
| 20150078586 | Ang et al. | Mar 2015 | A1 |
| 20150082183 | Hale et al. | Mar 2015 | A1 |
| 20150089613 | Tippett et al. | Mar 2015 | A1 |
| 20150097657 | Gandhi et al. | Apr 2015 | A1 |
| 20150103028 | Ruemelin et al. | Apr 2015 | A1 |
| 20150116205 | Westerman | Apr 2015 | A1 |
| 20150116239 | Kaplan et al. | Apr 2015 | A1 |
| 20150123775 | Kerdemelidis | May 2015 | A1 |
| 20150134531 | Xia | May 2015 | A1 |
| 20150135109 | Zambetti et al. | May 2015 | A1 |
| 20150138046 | Moon | May 2015 | A1 |
| 20150145656 | Levesque et al. | May 2015 | A1 |
| 20150145657 | Levesque et al. | May 2015 | A1 |
| 20150149899 | Bernstein et al. | May 2015 | A1 |
| 20150149964 | Bernstein | May 2015 | A1 |
| 20150153828 | Monkhouse et al. | Jun 2015 | A1 |
| 20150153830 | Hirose et al. | Jun 2015 | A1 |
| 20150156196 | Kim et al. | Jun 2015 | A1 |
| 20150169059 | Behles et al. | Jun 2015 | A1 |
| 20150199172 | Ringuette et al. | Jul 2015 | A1 |
| 20150201065 | Shim et al. | Jul 2015 | A1 |
| 20150227173 | Hwang | Aug 2015 | A1 |
| 20150227204 | Gipson et al. | Aug 2015 | A1 |
| 20150227280 | Westerman et al. | Aug 2015 | A1 |
| 20150227589 | Chakrabarti et al. | Aug 2015 | A1 |
| 20150234464 | Yliaho | Aug 2015 | A1 |
| 20150244848 | Park et al. | Aug 2015 | A1 |
| 20150248161 | Komori et al. | Sep 2015 | A1 |
| 20150253835 | Yu | Sep 2015 | A1 |
| 20150254570 | Florence et al. | Sep 2015 | A1 |
| 20150254947 | Komori et al. | Sep 2015 | A1 |
| 20150261296 | Yoshikawa | Sep 2015 | A1 |
| 20150261387 | Petersen | Sep 2015 | A1 |
| 20150268725 | Levesque et al. | Sep 2015 | A1 |
| 20150286288 | Lee et al. | Oct 2015 | A1 |
| 20150293592 | Cheong et al. | Oct 2015 | A1 |
| 20150301697 | Petrell et al. | Oct 2015 | A1 |
| 20150301838 | Steeves | Oct 2015 | A1 |
| 20150323996 | Obana et al. | Nov 2015 | A1 |
| 20150332226 | Wu et al. | Nov 2015 | A1 |
| 20150332565 | Cho et al. | Nov 2015 | A1 |
| 20150346916 | Jisrawi et al. | Dec 2015 | A1 |
| 20150347010 | Yang et al. | Dec 2015 | A1 |
| 20150350146 | Cary et al. | Dec 2015 | A1 |
| 20150365306 | Chaudhri et al. | Dec 2015 | A1 |
| 20160007290 | Lindemann et al. | Jan 2016 | A1 |
| 20160034152 | Wilson et al. | Feb 2016 | A1 |
| 20160034253 | Bang et al. | Feb 2016 | A1 |
| 20160036996 | Midholt et al. | Feb 2016 | A1 |
| 20160041750 | Cieplinski et al. | Feb 2016 | A1 |
| 20160062464 | Moussette et al. | Mar 2016 | A1 |
| 20160062465 | Moussette et al. | Mar 2016 | A1 |
| 20160062466 | Moussette et al. | Mar 2016 | A1 |
| 20160062467 | Buxton et al. | Mar 2016 | A1 |
| 20160062590 | Karunamuni et al. | Mar 2016 | A1 |
| 20160063496 | Royyuru et al. | Mar 2016 | A1 |
| 20160063825 | Moussette et al. | Mar 2016 | A1 |
| 20160063826 | Morrell et al. | Mar 2016 | A1 |
| 20160063827 | Moussette et al. | Mar 2016 | A1 |
| 20160063828 | Moussette et al. | Mar 2016 | A1 |
| 20160063850 | Yang et al. | Mar 2016 | A1 |
| 20160065525 | Dye et al. | Mar 2016 | A1 |
| 20160103830 | Cheong et al. | Apr 2016 | A1 |
| 20160123745 | Cotier et al. | May 2016 | A1 |
| 20160161922 | Shin | Jun 2016 | A1 |
| 20160165038 | Lim et al. | Jun 2016 | A1 |
| 20160179203 | Modarres et al. | Jun 2016 | A1 |
| 20160187988 | Levesque et al. | Jun 2016 | A1 |
| 20160189492 | Hamam et al. | Jun 2016 | A1 |
| 20160205244 | Dvortsov et al. | Jul 2016 | A1 |
| 20160246376 | Birnbaum et al. | Aug 2016 | A1 |
| 20160259435 | Qian et al. | Sep 2016 | A1 |
| 20160259499 | Kocienda et al. | Sep 2016 | A1 |
| 20160259519 | Foss et al. | Sep 2016 | A1 |
| 20160259528 | Foss et al. | Sep 2016 | A1 |
| 20160259542 | Chaudhri et al. | Sep 2016 | A1 |
| 20160295010 | Miller | Oct 2016 | A1 |
| 20160313875 | Williams et al. | Oct 2016 | A1 |
| 20160339750 | Elnajjar | Nov 2016 | A1 |
| 20160342973 | Jueng et al. | Nov 2016 | A1 |
| 20160349936 | Cho et al. | Dec 2016 | A1 |
| 20160357354 | Chen et al. | Dec 2016 | A1 |
| 20160357362 | Gauci et al. | Dec 2016 | A1 |
| 20160357363 | Decker et al. | Dec 2016 | A1 |
| 20170001121 | Cheong et al. | Jan 2017 | A1 |
| 20170031495 | Smith | Feb 2017 | A1 |
| 20170046024 | Dascola | Feb 2017 | A1 |
| 20170068511 | Brown et al. | Mar 2017 | A1 |
| 20170075520 | Bauer et al. | Mar 2017 | A1 |
| 20170075534 | Leschenko | Mar 2017 | A1 |
| 20170083096 | Rihn et al. | Mar 2017 | A1 |
| 20170102916 | Noble et al. | Apr 2017 | A1 |
| 20170185729 | Boray et al. | Jun 2017 | A1 |
| 20170201786 | Pyhalammi et al. | Jul 2017 | A1 |
| 20170357317 | Chaudhri et al. | Dec 2017 | A1 |
| 20170357318 | Chaudhri et al. | Dec 2017 | A1 |
| 20170357319 | Chaudhri et al. | Dec 2017 | A1 |
| 20170357320 | Chaudhri et al. | Dec 2017 | A1 |
| 20170358181 | Moussette et al. | Dec 2017 | A1 |
| 20180067557 | Robert et al. | Mar 2018 | A1 |
| 20180082552 | Moussette et al. | Mar 2018 | A1 |
| 20180129292 | Moussette et al. | May 2018 | A1 |
| 20180204425 | Moussette et al. | Jul 2018 | A1 |
| 20180367489 | Dye et al. | Dec 2018 | A1 |
| 20190026017 | Lee et al. | Jan 2019 | A1 |
| 20190033970 | Mellor et al. | Jan 2019 | A1 |
| 20190050055 | Chaudhri et al. | Feb 2019 | A1 |
| 20190138103 | Robert et al. | May 2019 | A1 |
| 20190213846 | Moussette et al. | Jul 2019 | A1 |
| 20190332179 | Robert et al. | Oct 2019 | A1 |
| 20200110466 | Moussette et al. | Apr 2020 | A1 |
| 20200111334 | Moussette et al. | Apr 2020 | A1 |
| 20200286343 | Moussette et al. | Sep 2020 | A1 |
| 20210117005 | Robert et al. | Apr 2021 | A1 |
| 20210192904 | Moussette et al. | Jun 2021 | A1 |
| 20210264748 | Moussette et al. | Aug 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 2016100246 | Apr 2016 | AU |
| 2016100653 | Jun 2016 | AU |
| 101232665 | Jul 2008 | CN |
| 101375582 | Feb 2009 | CN |
| 101631162 | Jan 2010 | CN |
| 101901048 | Dec 2010 | CN |
| 102330123 | Feb 2012 | CN |
| 102420906 | Apr 2012 | CN |
| 102484664 | May 2012 | CN |
| 102609078 | Jul 2012 | CN |
| 102651920 | Aug 2012 | CN |
| 103503428 | Jan 2014 | CN |
| 103649885 | Mar 2014 | CN |
| 103793051 | May 2014 | CN |
| 1038438424 | Jun 2014 | CN |
| 104049743 | Sep 2014 | CN |
| 104049746 | Sep 2014 | CN |
| 104123035 | Oct 2014 | CN |
| 104142781 | Nov 2014 | CN |
| 104321723 | Jan 2015 | CN |
| 104375633 | Feb 2015 | CN |
| 104412201 | Mar 2015 | CN |
| 104423595 | Mar 2015 | CN |
| 104471521 | Mar 2015 | CN |
| 104487929 | Apr 2015 | CN |
| 104508618 | Apr 2015 | CN |
| 104536643 | Apr 2015 | CN |
| 104598149 | May 2015 | CN |
| 104685444 | Jun 2015 | CN |
| 104685447 | Jun 2015 | CN |
| 104903835 | Sep 2015 | CN |
| 104932681 | Sep 2015 | CN |
| 105027034 | Nov 2015 | CN |
| 105144057 | Dec 2015 | CN |
| 105260049 | Jan 2016 | CN |
| 105278746 | Jan 2016 | CN |
| 105759957 | Jul 2016 | CN |
| 102010048745 | Apr 2012 | DE |
| 1 406 150 | Apr 2004 | EP |
| 2 141 569 | Jan 2010 | EP |
| 2 194 697 | Jun 2010 | EP |
| 2 328 063 | Jan 2011 | EP |
| 2 378 406 | Oct 2011 | EP |
| 2 386 935 | Nov 2011 | EP |
| 2 434 387 | Mar 2012 | EP |
| 2 728 445 | May 2014 | EP |
| 2 733 575 | May 2014 | EP |
| 2 821 912 | Jan 2015 | EP |
| 2 827 225 | Jan 2015 | EP |
| 2 846 226 | Mar 2015 | EP |
| 2 846 549 | Mar 2015 | EP |
| 2 847 658 | Mar 2015 | EP |
| 2 857 933 | Apr 2015 | EP |
| 2 950 182 | Dec 2015 | EP |
| 2 955 608 | Dec 2015 | EP |
| 2 977 859 | Jan 2016 | EP |
| 2532766 | Jun 2016 | GB |
| 2533572 | Jun 2016 | GB |
| 1999068888 | Mar 1999 | JP |
| 2000209311 | Jul 2000 | JP |
| 2004064117 | Feb 2004 | JP |
| 2004363999 | Dec 2004 | JP |
| 2005276089 | Oct 2005 | JP |
| 2008181365 | Aug 2008 | JP |
| 2008282125 | Nov 2008 | JP |
| 2009265818 | Nov 2009 | JP |
| 2010114702 | May 2010 | JP |
| 2010136151 | Jun 2010 | JP |
| 2010152716 | Jul 2010 | JP |
| 2010268086 | Nov 2010 | JP |
| 2011004397 | Jan 2011 | JP |
| 2011129019 | Jun 2011 | JP |
| 2011159110 | Aug 2011 | JP |
| 2013503578 | Jan 2013 | JP |
| 2013507059 | Feb 2013 | JP |
| 2013103430 | May 2013 | JP |
| 2013528855 | Jul 2013 | JP |
| JR 2013162167 | Aug 2013 | JP |
| 201300879 | Oct 2013 | JP |
| 2014164754 | Sep 2014 | JP |
| 2014215639 | Nov 2014 | JP |
| 2014229150 | Dec 2014 | JP |
| 2015007836 | Jan 2015 | JP |
| 2015015600 | Jan 2015 | JP |
| 2015519655 | Jul 2015 | JP |
| 20060006843 | Jan 2006 | KR |
| 20090113186 | Oct 2009 | KR |
| 20100056396 | May 2010 | KR |
| 20110136220 | Dec 2011 | KR |
| 20130075412 | Jul 2013 | KR |
| 20140002563 | Jan 2014 | KR |
| 20140025552 | Mar 2014 | KR |
| 20140094489 | Jul 2014 | KR |
| 20150013264 | Feb 2015 | KR |
| I388995 | Mar 2013 | TW |
| WO 0124158 | Apr 2001 | WO |
| WO 2004053830 | Jun 2004 | WO |
| WO 2008075082 | Jun 2008 | WO |
| WO 2012081182 | Jun 2012 | WO |
| WO 2013089294 | Jun 2013 | WO |
| WO 2013156815 | Oct 2013 | WO |
| WO 2013169300 | Nov 2013 | WO |
| WO 2013169842 | Nov 2013 | WO |
| WO 2013169853 | Nov 2013 | WO |
| WO 2013169854 | Nov 2013 | WO |
| WO 2013169865 | Nov 2013 | WO |
| WO 2013169875 | Nov 2013 | WO |
| WO 2013173838 | Nov 2013 | WO |
| WO 2014095756 | Jun 2014 | WO |
| WO 2014105275 | Jul 2014 | WO |
| WO 2015092379 | Jun 2015 | WO |
| WO 2015116056 | Aug 2015 | WO |
| WO 2015187274 | Dec 2015 | WO |
| WO 2016036509 | Mar 2016 | WO |
| WO 2016171848 | Oct 2016 | WO |
| WO 2017027526 | Feb 2017 | WO |
| WO 2017065365 | Apr 2017 | WO |
| Entry |
|---|
| Office Action, dated Mar. 22, 2019, received in Australian Patent Application No. 2017251751, which corresponds with U.S. Appl. No. 15/270,885, 3 pages. |
| Office Action, dated Feb. 2, 2019, received in Chinese Patent Application No. 2017107348777, which corresponds with U.S. Appl. No. 15/270,885, 10 pages. |
| Intention to Grant, dated Feb. 1, 2019, received in European Patent Application No. 17177493.8, which corresponds with U.S. Appl. No. 15/270,885, 4 pages. |
| Notice of Allowance, dated Feb. 13, 2019, received in Danish Patent Application No. 2016-70724, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Office Action, dated Apr. 2, 2019, received in Chinese Patent Application No. 2017800042913, which corresponds with U.S. Appl. No. 15/272,380, 5 pages. |
| Patent, dated Jan. 4, 2019, received in Danish Patent Application No. 201670729, which corresponds with U.S. Appl. No. 15/272,380, 7 pages. |
| Patent, dated Mar. 13, 2019, received in Danish Patent Application No. 201670735, which corresponds with U.S. Appl. No. 15/272,380, 3 pages. |
| Notification to Grant, dated Apr. 10, 2019, received in Chinese Patent Application No. 201710736303.3, which corresponds with U.S. Appl. No. 15/271,534, 6 pages. |
| Office Action, dated Mar. 5, 2019, received in Chinese Patent Application No. 201710736331.5, which corresponds with U.S. Appl. No. 15/271,108, 6 pages. |
| Office Action, dated Mar. 21, 2019, received in Korean Patent Application No. 2019-7000444, which corresponds with U.S. Appl. No. 14/869,870, 3 pages. |
| Office Action, dated Feb. 12, 2019, received in U.S. Appl. No. 15/823,436, 7 pages. |
| Notice of Allowance, dated Apr. 11, 2019, received in U.S. Appl. No. 15/863,765, 10 pages. |
| Office Action, dated Feb. 13, 2019, received in U.S. Appl. No. 16/240,684, 9 pages. |
| Notice of Allowance, dated Mar. 19, 2019, received in U.S. Appl. No. 16/240,684, 5 pages. |
| Office Action, dated Oct. 15, 2016, received in Chinese Patent Application No. 201780030418.9, which corresponds with U.S. Appl. No. 15/619,359, 3 pages. |
| Office Action, dated Oct. 4, 2019, received in European Patent Application No. 17733235.0, which corresponds with U.S. Appl. No. 15/619,359, 4 pages. |
| Office Action, dated Nov. 14, 2019, received in Australian Patent Application No. 2017251751, which corresponds with U.S. Appl. No. 15/270,885, 3 pages. |
| Patent, dated Oct. 25, 2019, received in Chinese Patent Application No. 201710734877.7, which corresponds with U.S. Appl. No. 15/270,885, 6 pages. |
| Office Action, dated Sep. 27, 2019, received in Danish Patent Application No. 201670720, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Patent, dated Nov. 1, 2019, received in Chinese Patent Application No. 201710728497.2, which corresponds with U.S. Appl. No. 15/271,653, 6 pages. |
| Dosher et al., “Human Interaction with Small Haptic Effects”, University of Washington, Seattle, WA, Jun. 2005, 16 pages. |
| Immersion, “The Value of Haptics”, San Jose, California, 2010, 12 pages. |
| Sulaiman et al., “User Haptic Experience and the Design of Drawing Interfaces”, Interacting with Computers, http://doi.org/10.1016/j.intcom.2009.11.009, Dec. 5, 2009, 20 pages. |
| VladMaxSoft, “Make Your iPhone Ring Louder When Inside a Pocket or Bag with Ringing Pocket Tweak”, https://www.reddit.com/r/jailbreak/comments/1zj6zx/release_make_your_iphone_ring_louder_when_inside/, Mar. 4, 2014, 8 pages. |
| Notice of Allowance, dated Jan. 31, 2018, received in U.S. Appl. No. 15/619,359, 8 pages. |
| Notice of Allowance, dated Oct. 2, 2017, received in U.S. Appl. No. 15/619,359, 9 pages. |
| Certificate of Grant, dated May 18, 2017, received in Australian Patent Application No. 2017100428, which corresponds with U.S. Appl. No. 15/619,359, 1 page. |
| Office Action, dated Jun. 27, 2017, received in Australian Patent Application No. 2017100482, which corresponds with U.S. Appl. No. 15/619,359, 7 pages. |
| Certificate of Examination, dated Oct. 27, 2017, received in Australian Patent Application No. 2017100482, which corresponds with U.S. Appl. No. 15/619,359, 1 page. |
| Office Action, dated Jan. 24, 2018, received in Danish Patent Application No. 201770369, which corresponds with U.S. Appl. No. 15/619,359, 6 pages. |
| Notice of Allowance, dated Dec. 14, 2016, received in U.S. Appl. No. 15/270,885, 13 pages. |
| Notice of Allowance, dated Apr. 10, 2017, received in U.S. Appl. No. 15/270,885, 5 pages. |
| Notice of Allowance, dated Jul. 21, 2017, received in U.S. Appl. No. 15/270,885, 10 pages. |
| Notice of Allowance, dated Nov. 22, 2017, received in U.S. Appl. No. 15/270,885, 5 pages. |
| Notice of Acceptance, dated Aug. 18, 2017, received in Australian Patent Application No. 2017216447, which corresponds with U.S. Appl. No. 15/270,885, 3 pages. |
| Grant, dated Dec. 21, 2017, received in Australian Application No. 2017216447, which corresponds with U.S. Appl. No. 15/270,885, 1 page. |
| Notice of Acceptance, dated Aug. 21, 2017, received in Australian Patent Application No. 2017216475, which corresponds with U.S. Appl. No. 15/270,885, 3 pages. |
| Grant, dated Dec. 21, 2017, received in Australian Application No. 2017216475, which corresponds with U.S. Appl. No. 15/270,885, 1 page. |
| Office Action, dated Jan. 5, 2017, received in Danish Patent Application No. 201670721, which corresponds with U.S. Appl. No. 15/270,885, 7 pages. |
| Office Action, dated Jul. 20, 2017, received in Danish Patent Application No. 201670721, which corresponds with U.S. Appl. No. 15/270,885, 2 pages. |
| Decision to Grant, dated Oct. 25, 2017, received in Danish Patent Application No. 201670721, which corresponds with U.S. Appl. No. 15/270,885, 2 pages. |
| Office action, dated Jan. 18, 2017, received in Danish Patent Application No. 201670726, which corresponds with U.S. Appl. No. 15/270,885, 7 pages. |
| Office Action, dated Apr. 5, 2017, received in Danish Patent Application No. 201670726, which corresponds with U.S. Appl. No. 15/270,885, 2 pages. |
| Notice of Allowance, dated Jul. 18, 2017, received in Danish Patent Application No. 201670726, which corresponds with U.S. Appl. No. 15/270,885, 2 pages. |
| Patent, dated Oct. 16, 2017, received in Danish Patent Application No. 201670726, which corresponds with U.S. Appl. No. 15/270,885, 2 pages. |
| Office Action, dated Aug. 25, 2017, received in European patent Application No. 17177160.3, which corresponds with U.S. Appl. No. 15/270,885, 3 pages. |
| Office Action, dated Jan. 24, 2018, received in European Patent Application No. 17177160.3, which corresponds with U.S. Appl. No. 15/270,885, 4 pages. |
| Office Action, dated Jan. 17, 2017, received in U.S. Appl. No. 15/271,073, 8 pages. |
| Notice of Allowance, dated May 2, 2017, received in U.S. Appl. No. 15/271,073, 5 pages. |
| Notice of Allowance, dated Aug. 21, 2017, received in Australian Application No. 2017213578, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Grant, dated Dec. 21, 2017, received in Australian Application No. 2017213578, which corresponds with U.S. Appl. No. 15/271,073, 1 page. |
| Notice of Allowance, dated Sep. 7, 2017, received in Australian Application No. 2017216471, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Grant, dated Dec. 21, 2017, received in Australian Application No. 2017216471, which corresponds with U.S. Appl. No. 15/271,073, 1 page. |
| Notice of Allowance, dated Aug. 24, 2017, received in Australian Application No. 2017216453, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Grant, dated Dec. 21, 2017, received in Australian Application No. 2017216453, which corresponds with U.S. Appl. No. 15/271,073, 1 page. |
| Office Action, dated Sep. 8, 2017, received in Chinese Application No. 201710735308.4, which corresponds with U.S. Appl. No. 15/271,073, 4 pages. |
| Office Action, dated Jan. 20, 2017, received in Danish Patent Application No. 201670720, which corresponds with U.S. Appl. No. 15/271,073, 9 pages. |
| Office Action, dated Sep. 4, 2017, received in Danish Patent Application No. 201670720, which corresponds with U.S. Appl. No. 15/271,073, 4 pages. |
| Office Action, dated Apr. 5, 2017, received in Danish Patent Application No. 2016-70724, which corresponds with U.S. Appl. No. 15/271,073, 5 pages. |
| Office Action, dated Aug. 1, 2017, received in Danish Patent Application No. 2016-70724, which corresponds with U.S. Appl. No. 15/271,073, 5 pages. |
| Office Action, dated Feb. 14, 2018, received in Danish Patent Application No. 2016-70724, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Office Action, dated Jan. 25, 2017, received in Danish Patent Application No. 201670725, which corresponds with U.S. Appl. No. 15/271,073, 6 pages. |
| Office Action, dated Apr. 5, 2017, received in Danish Patent Application No. 201670725, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Office Action, dated Oct. 12, 2017, received in Danish Patent Application No. 201670725, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Office Action, dated May 16, 2018, received in Danish Patent Application No. 201670725, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Office Action, dated Feb. 10, 2017, received in U.S. Appl. No. 15/272,380, 18 pages. |
| Notice of Allowance, dated Dec. 6, 2017, received in U.S. Appl. No. 15/272,380, 11 pages. |
| Notice of Allowance, dated Mar. 8, 2018, received in U.S. Appl. No. 15/272,380, 11 pages. |
| Certificate of Grant, dated Aug. 23, 2017, received in Australian Patent Application No. 2017101092, which corresponds with U.S. Appl. No. 15/272,380, 1 page. |
| Office Action, dated Oct. 4, 2017, received in Australian Patent Application No. 2017101092, which correspond with U.S. Appl. No. 15/272,380, 8 pages. |
| Certificate of Grant, dated Apr. 26, 2018, received in Australian Patent Application No. 2018100429, which corresponds with U.S. Appl. No. 15/272,380, 1 page. |
| Office Action, dated May 31, 2018, received in Australian Patent Application No. 2018100429, which corresponds with U.S. Appl. No. 15/272,380, 5 pages. |
| Office Action, dated Feb. 23, 2017, received in Danish Patent Application No. 201670729, which corresponds with U.S. Appl. No. 15/272,380, 9 pages. |
| Office Action, dated Aug. 28, 2017, received in Danish Patent Application No. 201670729, which corresponds with U.S. Appl. No. 15/272,380, 3 pages. |
| Office Action, dated Mar. 9, 2018, received in Danish Patent Application No. 01670729, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Office Action, dated May 17, 2018, received in Danish Patent Application No. 01670729, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Office Action, dated Jan. 24, 2017, received in Danish Patent Application No. 201670735, which corresponds with U.S. Appl. No. 15/272,380, 8 pages. |
| Office Action, dated Jul. 27, 2017, received in Danish Patent Application No. 201670735, which corresponds with U.S. Appl. No. 15/272,380, 3 pages. |
| Office Action, dated Dec. 7, 2017, received in Danish Patent Application No. 201670735, which corresponds with U.S. Appl. No. 15/272,380, 3 pages. |
| Office Action, dated Jan. 11, 2017, received in Danish Patent Application No. 201670736, which corresponds with U.S. Appl. No. 15/272,380, 11 pages. |
| Office Action, dated Aug. 30, 2017, received in Danish Patent Application No. 201670736, which corresponds with U.S. Appl. No. 15/272,380, 4 pages. |
| Office Action, dated Mar. 16, 2018, received in Danish Patent Application No. 201670736, which corresponds with U.S. Appl. No. 15/272,380, 4 pages. |
| Office Action, dated Jan. 30, 2017, received in Danish Patent Application No. 201670737, which corresponds with U.S. Appl. No. 15/272,380, 9 pages. |
| Office Action, dated Aug. 31, 2017, received in Danish U.S. Appl. No. 15/272,380 (7423DK03), which corresponds with U.S. Appl. No. 15/272,380, 4 pages. |
| Notice of Allowance, dated Feb. 22, 2017, received in U.S. Appl. No. 15/271,534 (7442), 13 pages. |
| Office Action, dated Jan. 10, 2017, received in U.S. Appl. No. 15/271,653 (7443), 9 pages. |
| Office Action, dated Sep. 13, 2017, received in Chinese U.S. Appl. No. 15/271,653.2 (7443CN), which corresponds with U.S. Appl. No. 15/271,653, 3 pages. |
| Office Action, dated Jan. 27, 2017, received in U.S. Appl. No. 15/271,708 (7444), 8 pages. |
| Notice of Allowance, dated Apr. 5, 2017, received in U.S. Appl. No. 15/271,708 (7444), 5 pages. |
| Office Action, dated Nov. 22, 2017, received in Chinese U.S. Appl. No. 15/271,108.5 (7444CN), which corresponds with U.S. Appl. No. 15/271,108, 3 pages. |
| Office Action, dated Nov. 30, 2015, received in U.S. Appl. No. 14/835,708 (7467), 28 pages. |
| Final Office Action, dated May 20, 2016, received in U.S. Appl. No. 14/835,708 (7467), 7 pages. |
| Notice of Allowance, dated Aug. 29, 2016, received in U.S. Appl. No. 14/835,708 (7467), 9 pages. |
| Office Action, dated Oct. 30, 2017, received in Australian U.S. Appl. No. 14/835,708 (7467AU), which corresponds with U.S. Appl. No. 14/835,708, 2 pages. |
| Notice of Acceptance, dated Apr. 5, 2018, received in Australian U.S. Appl. No. 14/835,708 (7467AU), which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Office Action, dated May 11, 2018, received in Japanese U.S. Appl. No. 14/835,708 (7467JP), which corresponds with U.S. Appl. No. 14/835,708, 8 pages. |
| Office Action, dated Dec. 26, 2017, received in Korean Patent Application No. 2017-7005874 (7467KR), which corresponds with U.S. Appl. No. 14/835,708, 11 pages. |
| Office Action, dated Aug. 1, 2016, received in Taiwanese U.S. Appl. No. 14/835,708 (7467TW), which corresponds with U.S. Appl. No. 14/835,708, 17 pages. |
| Office Action, dated Dec. 20, 2016, received in Taiwanese Patent Application No. 104126890, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Office Action, dated Dec. 28, 2016, received in Taiwanese Patent Application No. 104126890, which corresponds with U.S. Appl. No. 14/835,708, 3 pages. |
| Patent, dated Apr. 11, 2018, received in Taiwanese Patent Application No. 104126890, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Office action, dated Apr. 5, 2017, received in Taiwanese Patent Application No. 105139726, which corresponds with U.S. Appl. No. 14/835,708, 2 pages. |
| Notice of Allowance, dated Jul. 21, 2017, received in Taiwanese Patent Application No. 105139726, which corresponds with U.S. Appl. No. 14/835,708, 6 pages. |
| Patent, dated Nov. 1, 2017, received in Taiwanese Patent Application No. 105139726, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Office Action, dated Feb. 12, 2016, received in U.S. Appl. No. 14/869,825, 15 pages. |
| Final Office Action, dated Jul. 8, 2016, received in U.S. Appl. No. 14/869,825, 20 pages. |
| Office Action, dated Dec. 27, 2016, received in U.S. Appl. No. 14/869,825, 27 pages. |
| Office Action, dated Feb. 12, 2016, received in U.S. Appl. No. 14/869,829, 20 pages. |
| Final Office Action, dated Aug. 8, 2016, received in U.S. Appl. No. 14/869,829, 28 pages. |
| Office Action, dated Mar. 7, 2017, received in U.S. Appl. No. 14/869,829, 24 pages. |
| Final Office Action, dated Jul. 24, 2017, received in U.S. Appl. No. 14/869,829, 30 pages. |
| Examiner's Answer, dated Mar. 21, 2018, received in U.S. Appl. No. 14/869,829, 8 pages. |
| Office Action, dated Feb. 18, 2016, received in U.S. Appl. No. 14/869,834, 17 pages. |
| Final Office Action, dated Aug. 8, 2016, received in U.S. Appl. No. 14/869,834, 22 pages. |
| Office Action, dated Mar. 7, 2017, received in U.S. Appl. No. 14/869,834, 20 pages. |
| Final Office Action, dated Jul. 25, 2017, received in U.S. Appl. No. 14/869,834, 18 pages. |
| Notice of Allowance, dated Nov. 7, 2017, received in U.S. Appl. No. 14/869,834, 9 pages. |
| Office Action, dated Feb. 17, 2016, received in U.S. Appl. No. 14/869,835, 15 pages. |
| Final Office Action, dated Aug. 4, 2016, received in U.S. Appl. No. 14/869,835, 21 pages. |
| Office Action, dated Jan. 6, 2017, received in U.S. Appl. No. 14/869,835, 17 pages. |
| Final Office Action, dated Jun. 28, 2017, received in U.S. Appl. No. 14/869,835, 24 pages. |
| Office Action, dated Nov. 30, 2017, received in U.S. Appl. No. 14/869,835, 8 pages. |
| Notice of Allowance, dated May 29, 2018, received in U.S. Appl. No. 14/869,835, 12 pages. |
| Office Action, dated Dec. 30, 2015, received in U.S. Appl. No. 14/869,837, 35 pages. |
| Final Office Action, dated Jun. 30, 2016, received in U.S. Appl. No. 14/869,837, 37 pages. |
| Office Action, dated Jan. 17, 2017, received in U.S. Appl. No. 14/869,837, 27 pages. |
| Notice of Allowance, dated Jul. 31, 2017, received in U.S. Appl. No. 14/869,837, 27 pages. |
| Office Action, dated Aug. 31, 2017, received in Danish Patent Application No. 201770372, 10 pages. |
| Office Action, dated Apr. 17, 2018, received in Danish Patent Application No. 201770372, 5 pages. |
| Office Action, dated Mar. 7, 2018, received in U.S. Appl. No. 15/688,754, 9 pages. |
| International Search Report and Written Opinion, dated Nov. 29, 2017, received in International Patent Application No. PCT/US2017/037004, which corresponds with U.S. Appl. No. 15/619,359, 21 pages. |
| Extended European Search Report, dated Oct. 20, 2017, received in European Patent Application No. 17177493.8, 6 pages. |
| Invitation to Pay Additional Fees, dated Nov. 8, 2017, received in International Patent Application No. PCT/US2017/045152, which corresponds with U.S. Appl. No. 15/270,885, 17 pages. |
| International Search Report and Written Opinion, dated Jan. 18, 2018, received in International Patent Application No. PCT/US2017/045152, which corresponds with U.S. Appl. No. 15/270,885, 20 pages. |
| Extended European Search Report, dated Jan. 10, 2018, received in European Patent Application No. 17186196.6, which corresponds with U.S. Appl. No. 15/271,073, 8 pages. |
| Extended European Search Report, dated Jan. 9, 2018, received in European Patent Application No. 17186312.9, which corresponds with U.S. Appl. No. 15/271,073, 6 pages. |
| Extended European Search Report, dated Jan. 5, 2018, received in European Patent Application No. 17186313.7, which corresponds with U.S. Appl. No. 15/271,073, 9 pages. |
| International Search Report and Written Opinion, dated Jan. 16, 2018, received in International Patent Application No. PCT/US2017/045740, which corresponds with U.S. Appl. No. 15/271,073, 19 pages. |
| International Search Report and Written Opinion, dated Jan. 18, 2018, received in International Patent Application No. PCT/US2017/044851, which corresponds with U.S. Appl. No. 15/272,380, 17 pages. |
| International Search Report and Written Opinion, dated Mar. 15, 2016, received in International Patent Application No. PCT/US2015/041858, which corresponds with U.S. Appl. No. 14/835,708, 31 pages. |
| Office Action, dated May 23, 2019, received in Australian Patent Application No. 2017286532, which corresponds with U.S. Appl. No. 15/619,359, 3 pages. |
| Office Action, dated May 10, 2019, received in European Patent Application No. 17733235.0, which corresponds with U.S. Appl. No. 15/619,359, 9 pages. |
| Intention to Grant, dated Jul. 4, 2019, received in Danish Patent Application No. 201770369, which corresponds with U.S. Appl. No. 15/619,359, 2 pages. |
| Grant, dated Jul. 8, 2019, received in Danish Patent Application No. 201770369, which corresponds with U.S. Appl. No. 15/619,359, 2 pages. |
| Patent, dated Jul. 12, 2019, received in Danish Patent Application No. 2017 70369, which corresponds with U.S. Appl. No. 15/619,359, 4 pages. |
| Office Action, dated Aug. 9, 2019, received in Australian Patent Application No. 2017251751, which corresponds with U.S. Appl. No. 15/270,885, 5 pages. |
| Notice of Allowance, dated Aug. 14, 2019, received in Chinese Patent Application No. 201710734877.7, which corresponds with U.S. Appl. No. 15/270,885, 5 pages. |
| Decision to Grant, dated May 16, 2019, received in European Patent Application No. 17177160.3, which corresponds with U.S. Appl. No. 15/270,885, 1 page. |
| Patent, dated Jun. 12, 2019, received in European Patent Application No. 17177160.3, which corresponds with U.S. Appl. No. 15/270,885, 3 page. |
| Decision to Grant, dated Apr. 18, 2019, received in European Patent Application No. 17177493.8, which corresponds with U.S. Appl. No. 15/270,885, 4 pages. |
| Patent, dated May 27, 2019, received in European Patent Application No. 17177493.8, which corresponds with U.S. Appl. No. 15/270,885, 2 pages. |
| Office Action, dated Aug. 1, 2019, received in European Patent Application No. 19168886.0, which corresponds with U.S. Appl. No. 15/270,885, 5 pages. |
| Notice of Acceptance, dated Apr. 26, 2019, received in Australian Patent Application No. 201761484, which corresponds with U.S. Appl. No. 15/271,073, 3 pages. |
| Notice of Allowance, dated Jul. 1, 2019, received in Chinese Patent Application No. 201710735308.4, which corresponds with U.S. Appl. No. 15/271,073, 5 pages. |
| Office Action, dated Jul. 16, 2019, received in Chinese Patent Application No. 2017800042913, which corresponds with U.S. Appl. No. 15/272,380, 6 pages. |
| Office Action, dated Jun. 5, 2019, received in Chinese Patent Application No. 2018108328493, which corresponds with U.S. Appl. No. 15/272,380, 4 pages. |
| Office Action, dated May 14, 2019, received in Danish Patent Application No. 201670736, which corresponds with U.S. Appl. No. 15/272,380, 3 pages. |
| Office Action, dated Aug. 5, 2019, received in Japanese Patent Application No. 2019-090875, which corresponds with U.S. Appl. No. 15/272,380, 7 pages. |
| Office Action, dated Jul. 23, 2109, received in Chinese Patent Application No. 2018110167326.2, which corresponds with U.S. Appl. No. 15/275,083, 6 pages. |
| Notice of Allowance, dated Apr. 23, 2019, received in Japanese Patent Application No. 2018550359, which corresponds with U.S. Appl. No. 15/275,083, 4 pages. |
| Patent, dated May 17, 2019, received in Japanese Patent Application No. 2018550359, which corresponds with U.S. Appl. No. 15/275,083, 4 pages. |
| Patent, dated Jun. 7, 2019, received in Chinese Patent Application No. 201710736303.3, which corresponds with U.S. Appl. No. 15/271,534, 6 pages. |
| Notice of Allowance, dated Jul. 31, 2019, received in Chinese Patent Application No. 201710736331.5, which corresponds with U.S. Appl. No. 15/271,108, 3 pages. |
| Office Action, dated Apr. 18, 2019, received in Chinese Patent Application No. 201580044092.6, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Office Action, dated Apr. 18, 2019, received in European Patent Application No. 15748122.7, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Notice of Allowance, dated May 24, 2019, received in Japanese Patent Application No. 2017509011, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Patent, dated Jun. 14, 2019, received in Japanese Patent Application No. 2017509011, which corresponds with U.S. Appl. No. 14/835,708, 3 pages. |
| Notice of Allowance, dated May 9, 2019, received in U.S. Appl. No. 14/869,829, 8 pages. |
| Notice of Allowance, dated Jun. 26, 2019, received in U.S. Appl. No. 14/869,829, 8 pages. |
| Office Action, dated May 3, 2019, received in Australian Patent Application No. 2018202796, which corresponds with U.S. Appl. No. 14/869,834, 2 pages. |
| Office Action, dated May 10, 2019, received in Danish Patent Application No. 201770372, 5 pages. |
| Notice of Allowance, dated Jul. 24, 2019, received in U.S. Appl. No. 15/823,436, 5 pages. |
| Office Action, dated Jul. 17, 2019, received in U.S. Appl. No. 16/355,621, 7 pages. |
| Office Action, dated Aug. 21, 2019, received in U.S. Appl. No. 16/508,218, 9 pages. |
| European Search Report, dated Jul. 16, 2019, received in European Patent Application No. 19168886.0, which corresponds with U.S. Appl. No. 15/270,885, 6 pages. |
| Certificate of Grant, dated Aug. 28, 2019, received in Australian Patent Application No. 201761484, which corresponds with U.S. Appl. No. 15/271,073, 4 pages. |
| Patent, dated Aug. 27, 2019, received in Chinese Application No. 201710735308.4, which corresponds with U.S. Appl. No. 15/271,073, 6 pages. |
| Patent, dated Jun. 26, 2019, received in Danish Patent Application No. 2016-70724, which corresponds with U.S. Appl. No. 15/271,073, 4 pages. |
| Intention to Grant, dated Sep. 5, 2019, received in Danish Patent Application No. 201670725, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Notice of Allowance, dated Sep. 4, 2019, received in Chinese Patent Application No. 201710728497.2, which corresponds with U.S. Appl. No. 15/271,653, 5 pages. |
| Patent, dated Sep. 3, 2019, received in Chinese Patent Application No. 201710736331.5, which corresponds with U.S. Appl. No. 15/271,108, 6 pages. |
| Notice of Allowance, dated Sep. 10, 2019, received in Korean Patent Application No. 2019-7000444, which corresponds with U.S. Appl. No. 14/869,870, 4 pages. |
| Notice of Allowance, dated Sep. 18, 2019, received in U.S. Appl. No. 15/863,765, 8 pages. |
| Intention to Grant, dated Dec. 7, 2018, received in European Patent Application No. 17177160.3, which corresponds with U.S. Appl. No. 15/270,885, 7 pages. |
| Office Action, dated Oct. 5, 2018, received in Australian Patent Application No. 201761484, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Office Action, dated Jan. 3, 2019, received in Chinese Application No. 201710735308.4, which corresponds with U.S. Appl. No. 15/271,073, 6 pages. |
| Intention to Grant, dated Nov. 21, 2018, received in Danish Patent Application No. 201670735, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Office Action, dated Oct. 26, 2018, received in European Patent Application No. 18183341.9, which corresponds with U.S. Appl. No. 15/272,380, 7 pages. |
| Office Action, dated Jan. 14, 2019, received in European Patent Application No. 18191063.9, which corresponds with U.S. Appl. No. 15/275,083, 9 pages. |
| Office Action, dated Nov. 23, 2018, received in Chinese Patent Application No. 201710736303.3, which corresponds with U.S. Appl. No. 15/271,534, 7 pages. |
| Office Action, dated Dec. 29, 2018, received in Chinese Patent Application No. 201710728497.2, which corresponds with U.S. Appl. No. 15/271,653, 6 pages. |
| Office Action, dated Dec. 14, 2018, received in Japanese Patent Application No. 2017509011, which corresponds with U.S. Appl. No. 14/835,708, 8 pages. |
| Final Office Action, dated Nov. 8, 2018, received in Korean Patent Application No. 2017-7005874, which corresponds with U.S. Appl. No. 14/835,708, 3 pages. |
| Notice of Allowance, dated Dec. 20, 2018, received in U.S. Appl. No. 15/905,671, 9 pages. |
| International Preliminary Report on Patentability, dated Dec. 18, 2018, received in International Patent Application No. PCT/US2017/037004, which corresponds with U.S. Appl. No. 15/619,359, 12 pages. |
| European Search Report, dated Dec. 3, 2018, received in European Patent Application No. 18191063.9, which corresponds with U.S. Appl. No. 15/275,083, 4 pages. |
| Office Action, dated Jun. 15, 2018, received in Danish Patent Application No. 201670735, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Notice of Allowance, dated Jul. 12, 2018, received in U.S. Appl. No. 15/275,083, 22 pages. |
| Office Action, dated Jul. 20, 2018, received in U.S. Appl. No. 15/905,671, 7 pages. |
| Office Action, dated Aug. 6, 2018, received in Danish Patent Application No. 201770369, which corresponds with U.S. Appl. No. 15/619,359, 5 pages. |
| Office Action, dated Aug. 14, 2018, received in Danish Patent Application No. 201670720, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Certificate of Examination, dated Aug. 7, 2018, received in Australian Patent Application No. 2018100429, which corresponds with U.S. Appl. No. 15/272,380, 1 page. |
| Notice of Allowance, dated Oct. 2, 2018, received in Danish Patent Application No. 201670729, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Office Action, dated Jul. 25, 2018, received in Danish Patent Application No. 201670737, which corresponds with U.S. Appl. No. 15/272,380, 5 pages. |
| Notice of Allowance, dated Aug. 27, 2018, received in U.S. Appl. No. 15/273,688, 27 pages. |
| Certificate of Grant, dated Aug. 2, 2018, received in Australian Patent Application No. 2015312344, which corresponds with U.S. Appl. No. 14/835,708, 1 page. |
| Final Office Action, dated Jul. 17, 2018, received in Korean Patent Application No. 2017-7005874, which corresponds with U.S. Appl. No. 14/835,708, 3 pages. |
| Notice of Allowance, dated Aug. 27, 2018, received in U.S. Appl. No. 15/688,754, 5 pages. |
| European Search Report, dated Sep. 27, 2018, received in European Patent Application No. 18183341.9, which corresponds with U.S. Appl. No. 15/271,073, 4 pages. |
| International Search Report and Written Opinion, dated Aug. 22, 2018, received in International Patent Application No. PCT/US2018032936, which corresponds with U.S. Appl. No. 15/972,040, 14 pages. |
| Intention to Grant, dated Feb. 28, 2020, received in European Patent Application No. 17186312.9, which corresponds with U.S. Appl. No. 15/271,073, 5 pages. |
| Notice of Acceptance, dated Feb. 17, 2020, received in Australian Patent Application No. 2018202796, which corresponds with U.S. Appl. No. 14/869,834, 3 pages. |
| Notice of Allowance, dated Feb. 3, 2020, received in Japanese Patent Application No. 2018-558694, which corresponds with U.S. Appl. No. 15/619,359, 5 pages. |
| Patent, dated Feb. 4, 2020, received in Danish Patent Application No. 201670725, which corresponds with U.S. Appl. No. 15/272,380, 4 pages. |
| Notification to Grant, dated Jan. 16, 2020, received in Chinese Patent Application No. 2017800042913, which corresponds with U.S. Appl. No. 15/272,380, 6 pages. |
| Decision to Grant, dated Feb. 17, 2020, received in Danish Patent Application No. 201670736, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Notice of Allowance, dated Feb. 24, 2020, received in Korean Patent Appiication No. 2017-7005874, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Office Action, dated Feb. 11, 2020, received in Korean Patent Application No. 2019-7036500, which corresponds with U.S. Appl. No. 14/869,829, 2 pages. |
| Notice of Allowance, dated Feb. 14, 2020, received in U.S. Appl. No. 16/355,621, 9 pages. |
| Office Action, dated Feb. 10, 2020, received in U.S. Appl. No. 16/705,673, 6 pages. |
| Office Action, dated Nov. 18, 2019, received in Australian Patent Application No. 2017286532, which corresponds with U.S. Appl. No. 15/619,359 2 pages. |
| Notice of Acceptance, dated Dec. 19, 2019, received in Australian Patent Application No. 2017251751, which corresponds with U.S. Appl. No. 15/270,885, 3 pages. |
| Decision to Grant, dated Dec. 19, 2019, received in Danish Patnet Application No. 201670725, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Intention to Grant, dated Dec. 18, 2019, received in Danish Patent Application No. 201670736, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Office Action, dated Dec. 11, 2019, received in Chinese Patent Application No. 201580044092.6, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Oral Summons, dated Jan. 2, 2020, received in Korean Patent Application No. 2017-7005874, which corresponds with U.S. Appl. No. 14/835,708, 5 pages. |
| Patent, dated Dec. 10, 2019, received in Korean Patent Application No. 2019-7000444, which corresponds with U.S. Appl. No. 14/869,870, 4 pages. |
| Office Action, dated Nov. 26, 2019, received in Australian Patent Application No. 2019202429, which corresponds with U.S. Appl. No. 16/240,684, 2 pages. |
| Final Office Action, dated Dec. 12, 2019, received in U.S. Appl. No. 16/355,621, 8 pages. |
| Notice of Allowance, dated Dec. 4, 2019, received in U.S. Appl. No. 16/508,218, 5 pages. |
| Notice of Acceptance, dated Apr. 2, 2020, received in Australian Patent Application No. 2017286532, which corresponds with U.S. Appl. No. 15/619,359, 3 pages. |
| Office Action, dated Jun. 3, 2020, received in Chinese Patent Application No. 201780030418.9, which corresponds with U.S. Appl. No. 15/619,359, 3 pages. |
| Certificate of Grant, dated Apr. 30, 2020, received in Australian Patent Application No. 2017251751, which corresponds with U.S. Appl. No. 15/270,885, 1 page. |
| Patent, dated May 6, 2020, received in European Patent Application No. 17186196.6, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Patent, dated May 6, 2020, received in European Patent Application No. 17186312.9, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Patent, dated May 19, 2020, received in Danish Patent Application No. 201670736, which corresponds with U.S. Appl. No. 15/272,380, 4 pages. |
| Office Action, dated Jun. 15, 2020, received in European Patent Application No. 20155940.8, which corresponds with U.S. Appl. No. 15/272,380, 8 pages. |
| Office Action, dated Apr. 17, 2020, received in Japanese Patent Application No. 2019-090875, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Office Action, dated May 27, 2020, received in Chinese Patent Application No. 2018110167326.2, which corresponds with U.S. Appl. No. 15/275,083, 4 pages. |
| Office Action, dated Jun. 22, 2020, received in Japanese Patent Application No. 2019-046172, which corresponds with U.S. Appl. No. 14/869,829, 7 pages. |
| Patent, dated Jun. 18, 2020, received in Australian Patent Application No. 2018202796, which corresponds with U.S. Appl. No. 14/869,834, 3 pages. |
| Office Action, dated Jun. 1, 2020, received in Australian Patent Application No. 2018271107, which corresponds with U.S. Appl. No. 15/972,040, 4 pages. |
| Final Office Action, dated May 18, 2020, received in U.S. Appl. No. 16/705,673, 7 pages. |
| Office Action, dated Jun. 24, 2020, received in U.S. Appl. No. 16/553,064, 21 pages. |
| European Search Report, dated Jun. 2, 2020, received in European Patent Application No. 20155940.8, which corresponds with U.S. Appl. No. 15/271,073, 4 pages. |
| Certificate of Grant, dated Aug. 13, 2020, received in Australian Patent Application No. 2017286532, which corresponds with U.S. Appl. No. 15/619,359, 4 pages. |
| Notice of Allowance, dated Oct. 30, 2020, received in Korean Patent Application No. 2018-7032284, which corresponds with U.S. Appl. No. 15/619,359, 5 pages. |
| Intention to Grant, dated Sep. 11, 2020, received in European Patent Application No. 19168886.0, which corresponds with U.S. Appl. No. 15/270,885, 11 pages. |
| Office Action, dated Sep. 30, 2020, received in European Patent Application No. 17186313.7, which corresponds with U.S. Appl. No. 15/271,073, 5 pages. |
| Notice of Allowance, dated Sep. 11, 2020, received in Japanese Patent Application No. 2019-090875, which corresponds with U.S. Appl. No. 15/272,380, 5 pages. |
| Office Action, dated Aug. 28, 2020, received in Chinese Patent Application No. 201580044092.6, which corresponds with U.S. Appl. No. 14/835,708, 10 pages. |
| Office Action, dated Dec. 1, 2020, received in Chinese Patent Application No. 201580044092.6, which corresponds with U.S. Appl. No. 14/835,708, 8 pages. |
| Office Action, dated Sep. 3, 2020, received in Korean Patent Application No. 2019-7036500, which corresponds with U.S. Appl. No. 14/869,829, 5 pages. |
| Patent, dated Oct. 29, 2020, received in Korean Patent Application No. 2019-7036500, which corresponds with U.S. Appl. No. 14/869,829, 4 pages. |
| Notice of Allowance, dated Nov. 26, 2020, received in Australian Patent Application No. 2018271107, which corresponds with U.S. Appl. No. 15/972,040, 2 pages. |
| Office Action, dated Oct. 30, 2020, received in Japanese Patent Application No., which corresponds with U.S. Appl. No. 15/972,040. |
| Office action, dated Nov. 19, 2020, received in Korean Patent Application No. 2020-7030968, which corresponds with U.S. Appl. No. 15/823,436 pages. |
| Final Office Action, dated Sep. 23, 2020, received in U.S. Appl. No. 16/157,891, 16 pages. |
| Notice of Acceptance, dated Sep. 30, 2020, received in Australian Patent Application No. 2019202429, which corresponds with U.S. Appl. No. 16/240,684, 3 pages. |
| Office Action, dated Sep. 8, 2020, received in U.S. Appl. No. 16/705,673, 6 pages. |
| Notice of Allowance, dated Sep. 17, 2020, received in U.S. Appl. No. 16/553,064, 3 pages. |
| Office Action, dated Sep. 1, 2020, received in U.S. Appl. No. 16/846,124, 8 pages. |
| Notice of Allowance, dated Sep. 22, 2020, received in U.S. Appl. No. 16/846,124, 5 pages. |
| Office Action, dated Oct. 9, 2020, received in U.S. Appl. No. 16/885,166, 9 pages. |
| Decision to Refuse, dated Feb. 15, 2021, received in European Patent Application No. 17733235.0, which corresponds with U.S. Appl. No. 15/619,359, 14 pages. |
| Patent, dated Jan. 27, 2021, received in Korean Patent Application No. 2018-7032284, which corresponds with U.S. Appl. No. 15/619,359, 3 pages. |
| Decision to Grant, dated Jan. 28, 2021, received in European Patent Application No. 19168886.0, which corresponds with U.S. Appl. No. 15/270,885, 4 pages. |
| Patent, dated Feb. 24, 2021, received in European Patent Application No. 19168886.0, which corresponds with U.S. Appl. No. 15/270,885, 4 pages. |
| Office Action, dated Feb. 4, 2021, received in Chinese Patent Application No. 2018108328493, which corresponds with U.S. Appl. No. 15/272,380, 1 page. |
| Office Action, dated Apr. 26, 2021, received in European Patent Application No. 18183341.9, which corresponds with U.S. Appl. No. 15/272,380, 6 pages. |
| Office Action, dated Feb. 2, 2021, received in Chinese Patent Application No. 2018110167326.2, which corresponds with U.S. Appl. No. 15/275,083, 2 pages. |
| Office Action, dated Mar. 22, 2021, received in Australian Patent Application No. 2020202916, which corresponds with U.S. Appl. No. 14/869,829, 3 pages. |
| Notice of Allowance, dated Feb. 22, 2021, received in Japanese Patent Application No. 2019-046172, which corresponds with U.S. Appl. No. 14/869,829, 2 pages. |
| Patent, dated Mar. 8, 2021, received in Japanese Patent Application No. 2019-046172, which corresponds with U.S. Appl. No. 14/869,829, 3 pages. |
| Certificate of Grant, dated Mar. 18, 2021, received in Australian Patent Application No. 2018271107, which corresponds with U.S. Appl. No. 15/972,040, 3 pages. |
| Office Action, dated Mar. 8, 2021, received in Japanese Patent Application No. 2019-562305, which corresponds with U.S. Appl. No. 15/972,040, 2 pages. |
| Notice of Allowance, dated Apr. 5, 2021, received in Korean Patent Application No. 2020-7030968, which corresponds with U.S. Appl. No. 15/823,436 3 pages. |
| Office Action, dated Feb. 5, 2021, received in U.S. Appl. No. 16/157,891, 18 pages. |
| Certificate of Grant, dated Jan. 28, 2021, received in Australian Patent Application No. 2019202429, which corresponds with U.S. Appl. No. 16/240,684, 3 pages. |
| Office Action, dated Mar. 8, 2021, received in Japanese Patent Application No. 2020-035108, which corresponds with U.S. Appl. No. 16/355,621, 2 pages. |
| Notice of Allowance, dated Feb. 25, 2021, received in U.S. Appl. No. 16/885,166, 9 pages. |
| Office Action, dated Feb. 26, 2021, received in Korean Patent Application No. 2021-7002786, which corresponds with U.S. Appl. No. 16/885,166, 4 pages. |
| Office Action, dated May 3, 2021, received in European Patent Application No. 17751545.9, which corresponds with U.S. Appl. No. 15/272,380, 6 pages. |
| Office Action, dated Apr. 29, 2021, received in European Patent Application No. 18191063.9, which corresponds with U.S. Appl. No. 15/275,083, 3 pages. |
| Office Action, dated May 6, 2021, received in Australian Patent Application No. 2020203587, which corresponds with U.S. Appl. No. 16/885,166, 3 pages. |
| Office Action, dated Mar. 10, 2020, received in Chinese Patent Application No. 201780030418.9, which corresponds with U.S. Appl. No. 15/619,359, 3 pages. |
| Patent, dated Mar. 4, 2020, received in Japanese Patent Application No. 2018-558694, which corresponds with U.S. Appl. No. 15/619,359, 6 pages. |
| Office Action, dated Mar. 31, 2020, received in Korean Patent Application No. 2018-7032284, which corresponds with U.S. Appl. No. 15/619,359, 2 pages. |
| Decision to Grant, dated Apr. 9, 2020, received in European Patent Application No. 17186196.6, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Decision to Grant, dated Apr. 9, 2020, received in European Patent Application No. 17186312.9, which corresponds with U.S. Appl. No. 15/271,073, 2 pages. |
| Office Action, dated Apr. 3, 2020, received in Chinese Patent Application No. 2018108328493, which corresponds with U.S. Appl. No. 15/272,380, 8 pages. |
| Patent, dated Mar. 26, 2020, received in Korean Patent Application No. 2017-7005874, which corresponds with U.S. Appl. No. 14/835,708, 4 pages. |
| Office Action, dated Mar. 24, 2020, received in U.S. Appl. No. 16/157,891, 16 pages. |
| Office Action, dated Jan. 11, 2021, received in Chinese Patent Application No. 201780030418.9, which corresponds with U.S. Appl. No. 15/619,359, 6 pages. |
| Office Action, dated Jan. 15, 2021, received in Chinese Patent Application No. 202010082072.0, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Office Action, dated Jun. 16, 2021, received in Chinese Patent Application No. 202010082072.0, which corresponds with U.S. Appl. No. 15/272,380, 2 pages. |
| Notice of Allowance, dated Jun. 3, 2021, received in Australian Patent Application No. 2020202916, which corresponds with U.S. Appl. No. 14/869,829, 3 pages. |
| Office Action, dated Jul. 29, 2021, received in Australian Patent Application No. 2020289876, which corresponds with U.S. Appl. No. 15/972,040, 4 pages. |
| Patent, dated Jul. 5, 2021, received in Korean Patent Application No. 2020-7030968, which corresponds with U.S. Appl. No. 15/823,436, 4 pages. |
| Final Office Action, dated Jul. 6, 2020, received in U.S. Appl. No. 16/157,891, 21 pages. |
| Office Action, dated Sep. 14, 2021, received in Chinese Patent Application No. 202010238633.1, which corresponds with U.S. Appl. No. 16/157,891, 2 pages. |
| Final Office Action, dated Aug. 30, 2021, received in Korean Patent Application No. 2021-7002786, which corresponds with U.S. Appl. No. 16/885,166, 3 pages. |
| Office Action, dated Jun. 9, 2021, received in U.S. Appl. No. 17/138,664, 10 pages. |
| Notice of Allowance, dated Aug. 27, 2021, received in U.S. Appl. No. 17/138,664, 5 pages. |
| Office Action, dated Sep. 28, 2021, received in Chinese Patent Application No. 202010238671.7, which corresponds with U.S. Appl. No. 15/273,688, 1 page. |
| Notice of Allowance, dated Oct. 8, 2021, received in Japanese Patent Application No. 2020-172113, which corresponds with U.S. Appl. No. 15/273,688, 2 pages. |
| Certificate of Grant, dated Oct. 22, 2021, received in Australian Patent Application No. 202020916, which corresponds with U.S. Appl. No. 14/869,829, 3 pages. |
| Office Action, dated Sep. 30, 2021, received in European Patent Application No. 18730541.2, which corresponds with U.S. Appl. No. 15/972,040, 8 pages. |
| Office Action, dated Sep. 18, 2021, received in Chinese Patent Application No. 201911032592.4, which corresponds with U.S. Appl. No. 15/688,754, 7 pages. |
| Notice of Allowance, dated Sep. 24, 2021, received in Chinese Patent Application No. 201910901923.7, which corresponds with U.S. Appl. No. 15/863,765, 6 pages. |
| Notice of Allowance, dated Sep. 23, 2021, received in Chinese Patent Application No. 201911023034.1, which corresponds with U.S. Appl. No. 16/240,684, 2 pages. |
| Intent to Grant, dated Oct. 9, 2021, received in Australian Patent Application No. 2020294270, which corresponds with U.S. Appl. No. 16/508,218, 2 pages. |
| Notice of Allowance, dated Oct. 28, 2021, received in Australian Patent Application No. 2020203587, which corresponds with U.S. Appl. No. 16/885,166, 3 pages. |
| Intention to Grant, dated Dec. 23, 2021, received in European Patent Application No. 17186313.7, which corresponds with U.S. Appl. No. 15/271,073, 7 pages. |
| Office Action, dated Nov. 30, 2021, received in European Patent Application No. 20155940.8, which corresponds with U.S. Application No. 15/272,380, 7 pages. |
| Patent, dated Oct. 28, 2021, received in Japanese Patent Application No. 2020-172113, which corresponds with U.S. Appl. No. 15/273,688, 3 pages. |
| Notice of Allowance, dated Dec. 13, 2021, received in Australian Patent Application No. 2020289876, which corresponds with U.S. Appl. No. 15/972,040, 3 pages. |
| Patent, dated Dec. 14, 2021, received in Chinese Application Patent No. 201910901923.7, which corresponds with U.S. Appl. No. 15/863,765, 6 pages. |
| Notice of Allowance, dated Dec. 17, 2021, received in U.S. Appl. No. 16/157,891, 14 pages. |
| Patent, dated Nov. 2, 2021, received in Chinese Application Patent No. 201911023034.1, which corresponds with U.S. Appl. No. 16/240,684, 6 pages. |
| Notice of Allowance, dated Dec. 7, 2021, received in Korean Patent Application No. 2021-7021011, which corresponds with U.S. Appl. No. 16/705,673, 5 pages. |
| Notice of Allowance, dated Nov. 25, 2021, received in Korean Patent Application No. 2021-7002786, which corresponds with U.S. Appl. No. 16/885,166, 2 pages. |
| Notice of Allowance, dated Feb. 9, 2022, received in Chinese Application Patent No. 202010082072.2, which corresponds with U.S. Appl. No. 15/272.380, 1 page. |
| Notice of Allowance, dated Jan. 6, 2022, received in Chinese Application Patent No. 201911032592.4, which corresponds with U.S. Appl. No. 15/688,754, 1 page. |
| Office Action, dated Jan. 17, 2022, received in Japanese Patent Application No. 2020-035108, which corresponds with U.S. Appl. No. 16/355,621, 2 pages. |
| Patent, dated Jan. 27, 2022, received in Korean Patent Application No. 2021-7002786, which corresponds with U.S. Appl. No. 16/885,166, 6 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20180335848 A1 | Nov 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62507138 | May 2017 | US |
