Patent Grant
10884592
The present disclosure relates generally to computer user interfaces, and more specifically to techniques for displaying content.
As the technology of electronic devices advances, the form factor of many electronic devices is being reduced. For devices capable of displaying content, the display screens of these devices are also being decreased in size. Accordingly, there is a need for techniques for displaying content on reduced-size displays.
Some techniques for providing the ability to enlarge and navigate arbitrary content independent of the content displayed on a screen—at any time—is a crucial feature for modern operating systems. Existing systems allow zooming with either keyboard commands or multi-finger gestures. Limited size and lack of a keyboard make it a challenge to implement these solutions. It is desirable for a zoom solution to allow the ability to zoom in/out and pan around the enlarged content, and provide useful feedback (e.g., indicate what portion of the content is being displayed).
Some techniques for enlarging and navigating content using electronic devices, however, are generally cumbersome and inefficient. For example, existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, there is a need for electronic devices with faster, more efficient methods and interfaces for enlarging and navigating displayed content. Such methods and interfaces optionally complement or replace other methods for displaying content. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
In accordance with some embodiments, a method is performed at an electronic device with a display, a rotatable input mechanism, one or more processors, and memory. The method includes: displaying content on the display, wherein the content includes a first edge and a second edge opposite the first edge; detecting a first user input; in response to detecting the first user input, displaying an enlarged view of the content that does not include the first edge; detecting a rotation of the rotatable input mechanism in a first rotation direction; and in response to detecting the rotation, translating the enlarged view of the content in a first translation direction on the display to display the first edge of the content.
In accordance with some embodiments, an electronic device includes a display unit configured to display a graphic user interface, a rotatable input unit configured to receive rotations, and a processing unit coupled to the display unit and the rotatable input unit. The processing unit is configured to enable display of content on the display unit, wherein the content includes a first edge and a second edge opposite the first edge; detect a first user input; in response to detecting the first user input, enable display of an enlarged view of the content that does not include the first edge; detect a rotation of the rotatable input unit in a first rotation direction; and in response to detecting the rotation, enable translation of the enlarged view of the content in a first translation direction on the display unit to display the first edge of the content.
In accordance with some embodiments, an electronic device includes a display, a rotatable input mechanism, optionally a touch-sensitive surface, one or more processors, memory, and one or more programs. The one or programs are stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for performing the operations of the methods described above. In accordance with some embodiments, a computer-readable storage medium has stored therein instructions, which when executed by an electronic device with a display optionally a touch-sensitive surface, and a rotatable input mechanism, cause the device to perform the operation of the methods described above. In accordance with some embodiments, an electronic device includes a display, optionally a touch-sensitive surface, a rotatable input mechanism, and means for performing the operation of the methods described above.
Thus, devices are provided with faster, more efficient methods and interfaces for enlarging and navigating displayed content, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for displaying content.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
There is a need for electronic devices that provide efficient methods and interfaces for viewing content. Some modern electronic devices include a relatively small display. In order to efficiently view content on a small display, it may be advantageous to enlarge (e.g., magnify or zoom) displayed content and provide intuitive techniques for viewing and navigating portions of the content in the enlarged view (e.g., scanning from top left to bottom right). A rotatable input mechanism may be used to translate an enlarged view of content, which may allow a user to navigate to different portions of the content without touching the display and obscuring the user's view of the display. Such techniques can reduce the cognitive burden on a user who access content of a relatively small display, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
Below,
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a”, “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The term “if” may be 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” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, 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 may support a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 may include one or more computer-readable storage mediums. The computer-readable storage mediums may be tangible and non-transitory. Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 may control access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may be implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button may disengage a lock of touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) may turn power to device 100 on or off. The user may be able to customize a functionality of one or more of the buttons. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.
A touch-sensitive display in some embodiments of touch screen 112 may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 may include 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 may be a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 may include 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 may also include one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 may also include one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 may also include one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which may be 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 may include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 may be used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. For example, video player module may be combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 may be reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected may 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 may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 may utilize or call data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which may 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 may also include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers may interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In one embodiment, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that may be implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples which follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Techniques for detecting and processing touch intensity may be found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms may permit device 500 to be worn by a user.
Input mechanism 508 may be a microphone, in some examples. Personal electronic device 500 can include various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can be a non-transitory computer-readable storage medium, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described above, including process 1100 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that may be displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location 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 intensity of a contact on the touch-sensitive surface may be characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
Various exemplary techniques for displaying and navigating (e.g., zooming and translating) content on a user interface of an electronic device using a rotatable input mechanism are described below.
In
It should be recognized that the terms “top edge,” “bottom edge,” “right edge,” and “left edge” have been chosen for purposes of clarity and are used in relation to the orientations of the specific exemplary embodiments depicted in the figures. A person having ordinary skill in the art would recognize that a top edge in some embodiments may correspond to a right, left, or bottom edge in other embodiments, and so forth.
In response to detecting the first user input, personal electronic device 600 displays an enlarged view of content 610.
In some embodiments, the enlarged view of the content is centered on a location associated with the first user input. In
In some embodiments, the magnification of the enlarged view is predetermined by, for example, an operation system setting, parameter, or the like. In some embodiments, the magnification level is persistent. In other words, the magnification of the enlarged view may be determined by a previous level of magnification displayed by personal electronic device 600, such as the last time a view of content was enlarged. Optionally, the magnification of the enlarged view may be adjusted. In some embodiments, the magnification is adjustable by a user input (e.g., a two-finger drag gesture on the touch-sensitive display or a touch combined with a rotation of the rotatable input mechanism as described in greater detail below with reference to
In some embodiments, personal electronic device 600 displays a user interface object that provides an indication of which portion of the content is being displayed in the enlarged view.
In some embodiments, indication 850 includes a first user interface object and a second user interface object, where the first user interface object is overlaid on the enlarged view of the content and the second user interface object is overlaid on the first user interface object. Exemplary indicator 850 has a translucent user interface object 852 that represents the size and shape of the content 610. Indicator 850 further includes an opaque user interface object 854 within user interface object 852 that indicates the size and location of the portion of the content currently displayed in the enlarged view. The size and location of the enlarged view is represented by the size and location of user interface object 854 compared to user interface object 852. For example, indicator 850 in
In some embodiments, the rotatable input mechanism 604 is located adjacent to a portion of the touch-sensitive display 602 and the indication 850 is displayed adjacent to the rotatable input mechanism 604, as illustrated, for example, in
Once the right edge 615 of content 610 is reached as shown in
In response to detecting further rotation 815, the enlarged view may be translated in direction 820 to display a second edge of content 610.
Once the left edge 616 of content 610 is displayed, further rotation 835 of the rotatable input mechanism 604 in the first rotation direction may cause the enlarged view to be translated horizontally in direction 830 along a path vertically displaced from the previous horizontal path. For example, in response to further rotation 835 of the rotatable input mechanism 604 in the first rotation direction, the enlarged view is translated horizontally from the lower left corner of the content 610 defined by left edge 616 and lower edge 618 to the lower right corner of the content defined by lower edge 618 and right edge 615, as illustrated by
Once the enlarged view has reached the bottom right corner of the content 610, further rotation 845 of the rotatable input mechanism 604 in the first rotation direction may cause the enlarged view to be translated in direction 840 to the top left corner of the content defined by left edge 616 and top edge 617. In some embodiments, translating the enlarged view includes determining whether the translation has reached a first corner of the content (e.g., the bottom right corner) defined by the first edge (e.g., the right edge 615) and a third edge perpendicular to the first edge (e.g., the bottom edge 618). In accordance with a determination that the translation has reached the first corner, the enlarged view is translated toward a second corner of the content (e.g., the top left corner) defined by the second edge (e.g., the left edge 616) and a fourth edge perpendicular to the second edge (e.g., the top edge 617). In some embodiments, the second corner is diagonally opposite from the first corner.
The path of translation of the enlarged view according to the techniques described above with respect to
In the example illustrated in
In the embodiment depicted by
In some embodiments, diagonal translation is performed at a faster rate than horizontal translation. For example, a given amount of rotation of the rotatable input mechanism 604 may cause the enlarged view to be translated a certain amount in the horizontal direction (e.g., direction 810 or 830), whereas the same amount of rotation may cause a greater amount of translation along a diagonal direction (e.g., direction 820 or 840). Accordingly, diagonal translation may appear to occur faster than horizontal translation. That is, translating the enlarged view may include determining whether the enlarged view is to be translated horizontally or diagonally. In accordance with a determination that the enlarged view is to be translated horizontally, the translation is performed at a first speed, and in accordance with a determination that the enlarged view is to be translated diagonally, the translation is performed at a second speed that is greater than the first speed.
Exemplary techniques will now be described for causing the display to be transitioned back to a non-enlarged view of content 610. In some embodiments, a third user input is detected while the enlarged view is being displayed. In response to detecting the third user input, the content is displayed as it was immediately prior to detection of the user input that caused the enlarged view to be displayed. In some embodiments, the type of user input that causes the display to revert back to its initial state is the same as the user input that causes personal electronic device 600 to display the enlarged view (e.g., touch 705 or a two-finger double tap while the enlarged view is being displayed). For example, while an enlarged view of the content is being displayed (e.g., enlarged view 710), personal electronic device 600 may detect the third user input. In response to detecting the third user input, personal electronic device 600 may replace the display of the enlarged view (e.g., enlarged view 710) with a display of a non-enlarged view of the content (e.g., the view of content 610 displayed in
In some embodiments, while displaying an enlarged view of content, personal electronic device 600 performs different operations in response rotation of the rotatable input mechanism 604 depending on the operational state of the device. For example, personal electronic device 600 may operate in a first state in which rotation of the rotatable input mechanism 604 causes the enlarged view to be translated according to the techniques described above. Personal electronic device 600 may, alternatively, operate in a second operational state in which it performs a second operation that is different from the first operation in response to rotation of the rotatable input mechanism 604 while an enlarged view is displayed. For example, personal electronic device 600 may respond to a rotation of the rotatable input mechanism 604 by scrolling through a list of potentially selectable user interface objects or translating the content vertically. In some embodiments, while in the second operational state and displaying an enlarged view of content 610, personal electronic device 600 performs whatever operation it is configured to perform were it not displaying an enlarged view of the content (i.e., as if the content were not enlarged). That is, personal electronic device performs the same operation on the enlarged view of content 610 as it would if content 610 were not enlarged.
A user may switch between the first operational state and the second operational state by performing a user input while the enlarged view is displayed. That is, in response to detecting a fourth user input and (e.g., a two-finger single tap), the personal electronic device 600 is changed from a first operational state to a second operational state, where in the first operational state, rotation of the rotatable input mechanism 604 performs a first operation, and in the second state, rotation of the rotatable input mechanism 604 performs a second operation that is different than the first operation. In some embodiments, the operational state is persistent in the sense that upon displaying the enlarged view of the content, personal electronic device 600 is set to operate in the same state as when an enlarged view was last displayed.
In some embodiments, the rotatable input mechanism 604 can be used in combination with another input to adjust the magnification of the enlarged view. That is, while displaying the enlarged view of the content, a user input and a rotation of the rotatable input mechanism 604 can be detected. In response to detecting the user input and the rotation of the rotatable input mechanism 604, the magnification of the enlarged view is adjusted.
In some embodiments, a non-transitory computer-readable storage medium stores one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and a rotatable input mechanism, cause the device to perform any of the techniques described above.
As described below, method 1100 provides an intuitive way for enlarging the view of displayed content and viewing the enlarged view. The method reduces the cognitive burden on a user for enlarging the view of displayed content and viewing the enlarged view, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to enlarge the view of displayed content and view the enlarged view faster and more efficiently conserves power and increases the time between battery charges.
At block 1102, content is displayed on the display, where the content includes a first edge and a second edge opposite the first edge.
At block 1104, a first user input is detected.
At block 1106, an enlarged view of the content is displayed in response to the first user input. The enlarged view of the content does not include the first edge.
At block 1108, a rotation of the rotatable input mechanism in a first rotation direction is detected.
At block 1110, in response to detecting the rotation of the rotatable input mechanism, the enlarged view of the content is translated in a first translation direction on the display to display the first edge of the content.
In accordance with some embodiments,
As shown in
The processing unit 1208 is configured to: enable (e.g., with display enabling unit 1210) display of content on the display unit, where the content includes a first edge and a second edge opposite the first edge; detect (e.g., with detecting unit 1212) a first user input; in response to detecting the first user input, enable (e.g., with display enabling unit 1210) display of an enlarged view of the content that does not include the first edge; detect (e.g., with detecting unit 1212) a rotation of the rotatable input unit in a first rotation direction; and in response to detecting the rotation, enable (e.g., with display enabling unit 1210) translation of the enlarged view of the content in a first translation direction on the display unit to display the first edge of the content.
In some embodiments, processing unit 1208 is further configured to detect (e.g., with detecting unit 1212) further rotation of the rotatable input unit in the first rotation direction and, in response to detecting the further rotation, enable (e.g., with display enabling unit 1210) translation of the enlarged view in a second translation direction on the display to display the second edge of the content, where the second translation direction is different than the first translation direction.
In some embodiments, the first user input includes a two-finger double tap on the touch-sensitive surface unit. In some embodiments, the enlarged view of the content is centered on a location associated with the first user input. In some embodiments, the enlarged view of the content includes a predetermined area of the content. In some embodiments, the first translation direction is horizontal and the second translation direction is diagonal.
In some embodiments, processing unit 1208 is further configured to, further in response to detecting the further rotation, and before translating the enlarged view in the second direction, enable (e.g., with display enabling unit 1210) pausing of translation of the enlarged view. In some embodiments, processing unit 1208 is further configured to: determine (e.g., with determining unit 1214) whether the translation has reached the first edge of the content or the second edge of the content; in accordance with a determination that the translation has reached the first edge of the content or the second edge of the content, enable (e.g., with display enabling unit 1210) pausing of translation of the enlarged view in response to further rotation of the rotatable input unit in the first rotation direction; and in accordance with a determination that the translation has not reached the first edge of the content or the second edge of the content, enable (e.g., with display enabling unit 1210) continuing translation of the enlarged view in the same translation direction in response to further rotation of the rotatable input unit in the first rotation direction.
In some embodiments, the enlarged view is translated from a first portion of the content to a second portion of the content, where the second portion of the content is displaced vertically from the first portion. In some embodiments, the first portion and the second portion at least partially overlap.
In some embodiments, rotation of the rotatable input unit in the first rotation direction causes the enlarged view to be translated horizontally from left to right or diagonally downward and to the left, and rotation of the rotatable input unit in a second rotation direction, opposite the first rotation direction, causes the enlarged view to be translated horizontally from right to left or diagonally upward and to the right.
In some embodiments, enabling translation of the enlarged view includes: determining whether the translation has reached a first corner of the content defined by the first edge and a third edge perpendicular to the first edge; in accordance with a determination that the translation has reached the first corner, enabling (e.g., with display enabling unit 1210) translation of the enlarged view toward a second corner of the content defined by the second edge and a fourth edge perpendicular to the second edge, where the second corner is diagonally opposite from the first corner; and in accordance with a determination that the translation has not reached the first corner of the content, enabling (e.g., with display enabling unit 1210) continuing translation of the enlarged view in the same direction. In some embodiments, the first corner is a bottom right corner of the content and the second corner is an upper left corner of the content.
In some embodiments, enabling translation of the enlarged view includes: determining whether the enlarged view is to be translated horizontally or diagonally; in accordance with a determination that the enlarged view is to be translated horizontally, enabling (e.g., with display enabling unit 1210) translation at a first speed; in accordance with a determination that the enlarged view is to be translated diagonally, enabling translation at a second speed that is greater than the first speed.
In some embodiments, displaying the enlarged view of the content includes displaying a first portion of the content, and the processing unit 1208 is further configured to: in response to rotation of the rotatable input unit in the first rotation direction, enable (e.g., with display enabling unit 1210) display of an indication of the size and location of the first portion of the content relative to the entire content. In some embodiments, the indication includes a first user interface object and a second user interface object, where the first user interface object is overlaid on the first portion of the content and the second user interface object is overlaid on the first user interface object. In some embodiments, the size and location of the second user interface object relative to the first user interface object indicates the size and location of the first portion relative to the entire content. In some embodiments, the first user interface object is translucent and the second user interface object is opaque. In some embodiments, the rotatable input unit is located adjacent to a portion of the display unit and the indication is displayed adjacent to the rotatable input unit.
In some embodiments, processing unit 1208 is further configured to: detect (e.g., with detecting unit 1212) a third user input; and in response to detecting the third user input, enable (e.g., with display enabling unit 1210) display of the content as it was displayed immediately prior to detecting the first user input.
In some embodiments, processing unit 1208 is further configured to: detect (e.g., with detecting unit 1212) a fourth user input; and in response to detecting the fourth user input, change (e.g., with operational state setting unit 1216) the electronic device from a first operational state to a second operational state, where: in the first operational state, rotation of the rotatable input unit performs a first operation, and in the second state, rotation of the rotatable input unit performs a second operation that is different than the first operation.
In some embodiments, processing unit 1208 is further configured to: while the enlarged view of the content is displayed, detect (e.g., with detecting unit 1212) a fifth user input and detecting a second rotation of the rotatable input unit; and in response to detecting the fifth user input and the second rotation of the rotatable input unit, enable (e.g., with display enabling unit 1210) adjustment of the magnification of the enlarged view. In some embodiments, the fifth user input is a touch on the touch-sensitive surface unit. In some embodiments, the touch and at least a portion of the second rotation are detected essentially simultaneously. In some embodiments, in accordance with the second rotation being in a first rotation direction, the magnification is increased; and in accordance with the second rotation being in a second rotation direction, the magnification is decreased.
The operations described above with reference to
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
This application is a continuation of U.S. patent application Ser. No. 14/841,646, filed Aug. 31, 2015, entitled “CONTROL OF SYSTEM ZOOM MAGNIFICATION USING A ROTATABLE INPUT MECHANISM,” which claims priority to U.S. Provisional Application No. 62/177,001, filed Mar. 2, 2015, entitled “CONTROL OF SYSTEM ZOOM MAGNIFICATION USING A ROTATABLE INPUT MECHANISM. The content of these applications are hereby incorporated by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4358837 | Yamazaki et al. | Nov 1982 | A |
| 4395134 | Luce | Jul 1983 | A |
| 4623261 | Muto | Nov 1986 | A |
| 5088070 | Shiff | Feb 1992 | A |
| 5204600 | Kahkoska | Apr 1993 | A |
| 5220260 | Schuler | Jun 1993 | A |
| 5297110 | Ohira et al. | Mar 1994 | A |
| 5313229 | Gilligan et al. | May 1994 | A |
| 5323363 | Hysek et al. | Jun 1994 | A |
| 5329501 | Meister et al. | Jul 1994 | A |
| 5477508 | Will | Dec 1995 | A |
| 5508978 | Kalbermatter et al. | Apr 1996 | A |
| 5511157 | Wang | Apr 1996 | A |
| 5519393 | Brandestini | May 1996 | A |
| 5528260 | Kent | Jun 1996 | A |
| 5563631 | Masunaga | Oct 1996 | A |
| 5581670 | Bier et al. | Dec 1996 | A |
| 5590219 | Gourdol | Dec 1996 | A |
| 5689628 | Robertson | Nov 1997 | A |
| 5691747 | Amano | Nov 1997 | A |
| 5739775 | Brandestini | Apr 1998 | A |
| 5751260 | Nappi et al. | May 1998 | A |
| 5795301 | Yasukawa et al. | Aug 1998 | A |
| 5825353 | Will | Oct 1998 | A |
| 5852413 | Bacchi et al. | Dec 1998 | A |
| 5861889 | Wallace et al. | Jan 1999 | A |
| 5874961 | Bates et al. | Feb 1999 | A |
| 5903229 | Kishi | May 1999 | A |
| 5940521 | East et al. | Aug 1999 | A |
| 5960366 | Duwaer | Sep 1999 | A |
| 5982710 | Rawat et al. | Nov 1999 | A |
| 6005579 | Sugiyama et al. | Dec 1999 | A |
| 6064388 | Reyzin | May 2000 | A |
| 6081256 | Herget et al. | Jun 2000 | A |
| 6128006 | Rosenberg et al. | Oct 2000 | A |
| 6144381 | Lection et al. | Nov 2000 | A |
| 6157381 | Bates et al. | Dec 2000 | A |
| 6161957 | Guanter | Dec 2000 | A |
| 6192258 | Kamada et al. | Feb 2001 | B1 |
| 6203190 | Stotz | Mar 2001 | B1 |
| 6249689 | Aizawa | Jun 2001 | B1 |
| 6266098 | Cove et al. | Jul 2001 | B1 |
| 6281903 | Martin et al. | Aug 2001 | B1 |
| 6297795 | Kato et al. | Oct 2001 | B1 |
| 6300939 | Decker et al. | Oct 2001 | B1 |
| 6305234 | Thies et al. | Oct 2001 | B1 |
| 6310648 | Miller et al. | Oct 2001 | B1 |
| 6323846 | Westerman et al. | Nov 2001 | B1 |
| 6336126 | Bjorklund et al. | Jan 2002 | B1 |
| 6339438 | Bates et al. | Jan 2002 | B1 |
| 6351657 | Yamada | Feb 2002 | B2 |
| 6369794 | Sakurai et al. | Apr 2002 | B1 |
| 6396482 | Griffin et al. | May 2002 | B1 |
| 6407749 | Duke | Jun 2002 | B1 |
| 6477117 | Narayanaswami et al. | Nov 2002 | B1 |
| 6489950 | Griffin et al. | Dec 2002 | B1 |
| 6525997 | Narayanaswami et al. | Feb 2003 | B1 |
| 6535461 | Karhu | Mar 2003 | B1 |
| 6556222 | Narayanaswami | Apr 2003 | B1 |
| 6570557 | Westerman et al. | May 2003 | B1 |
| 6570583 | Kung et al. | May 2003 | B1 |
| 6597374 | Baker et al. | Jul 2003 | B1 |
| 6600936 | Kärkkäinen et al. | Jul 2003 | B1 |
| 6636197 | Goldenberg et al. | Oct 2003 | B1 |
| 6636246 | Gallo et al. | Oct 2003 | B1 |
| 6647338 | Hamberger et al. | Nov 2003 | B1 |
| 6661438 | Shiraishi et al. | Dec 2003 | B1 |
| 6677932 | Westerman | Jan 2004 | B1 |
| 6686904 | Sherman et al. | Feb 2004 | B1 |
| 6686911 | Levin et al. | Feb 2004 | B1 |
| 6700564 | McLoone et al. | Mar 2004 | B2 |
| 6720860 | Narayanaswami | Apr 2004 | B1 |
| 6763226 | Mczeal, Jr. | Jul 2004 | B1 |
| 6788220 | Netzer | Sep 2004 | B2 |
| 6809275 | Cheng et al. | Oct 2004 | B1 |
| 6809724 | Shiraishi et al. | Oct 2004 | B1 |
| 6842169 | Griffin et al. | Jan 2005 | B2 |
| 6937228 | Yu | Aug 2005 | B2 |
| 6961060 | Mochizuki et al. | Nov 2005 | B1 |
| 6967642 | SanGiovanni | Nov 2005 | B2 |
| 6967903 | Guanter | Nov 2005 | B2 |
| 6977868 | Brewer et al. | Dec 2005 | B2 |
| 7002558 | Keely | Feb 2006 | B2 |
| 7016824 | Waupotitsch et al. | Mar 2006 | B2 |
| 7020853 | Skoll et al. | Mar 2006 | B2 |
| 7046230 | Zadesky et al. | May 2006 | B2 |
| 7058904 | Khan et al. | Jun 2006 | B1 |
| 7075513 | Silfverberg | Jul 2006 | B2 |
| 7081905 | Raghunath | Jul 2006 | B1 |
| 7091964 | Wong et al. | Aug 2006 | B2 |
| 7116317 | Gregorio et al. | Oct 2006 | B2 |
| 7130664 | Williams | Oct 2006 | B1 |
| 7143355 | Yamaguchi et al. | Nov 2006 | B2 |
| 7146005 | Anft et al. | Dec 2006 | B1 |
| 7168047 | Huppi | Jan 2007 | B1 |
| 7227963 | Yamada et al. | Jun 2007 | B1 |
| 7256770 | Hinckley et al. | Aug 2007 | B2 |
| 7272077 | Nobs | Sep 2007 | B2 |
| 7286063 | Gauthey et al. | Oct 2007 | B2 |
| 7286119 | Yamaguchi et al. | Oct 2007 | B2 |
| 7298385 | Kazi et al. | Nov 2007 | B2 |
| 7317449 | Robbins et al. | Jan 2008 | B2 |
| 7333084 | Griffin | Feb 2008 | B2 |
| 7439975 | Hsu | Oct 2008 | B2 |
| 7463239 | Ledbetter et al. | Dec 2008 | B2 |
| 7469381 | Ording | Dec 2008 | B2 |
| 7469386 | Bear et al. | Dec 2008 | B2 |
| 7472047 | Kramer et al. | Dec 2008 | B2 |
| 7477890 | Narayanaswami | Jan 2009 | B1 |
| 7489303 | Pryor | Feb 2009 | B1 |
| 7499040 | Zadesky et al. | Mar 2009 | B2 |
| 7506269 | Lang | Mar 2009 | B2 |
| 7519468 | Orr et al. | Apr 2009 | B2 |
| 7543239 | Viswanathan et al. | Jun 2009 | B2 |
| 7596761 | Lemay et al. | Sep 2009 | B2 |
| 7600192 | Hashimoto et al. | Oct 2009 | B1 |
| 7614008 | Ording | Nov 2009 | B2 |
| 7633076 | Huppi et al. | Dec 2009 | B2 |
| 7653883 | Hotelling et al. | Jan 2010 | B2 |
| 7657849 | Chaudhri et al. | Feb 2010 | B2 |
| 7663607 | Hotelling et al. | Feb 2010 | B2 |
| 7710393 | Tsuk et al. | May 2010 | B2 |
| 7710409 | Robbin et al. | May 2010 | B2 |
| 7720552 | Lloyd | May 2010 | B1 |
| 7794138 | Hilfiker | Sep 2010 | B2 |
| 7814436 | Schrag et al. | Oct 2010 | B2 |
| 7844914 | Andre et al. | Nov 2010 | B2 |
| 7844915 | Platzer et al. | Nov 2010 | B2 |
| 7856255 | Tsuchiya et al. | Dec 2010 | B2 |
| 7916157 | Kelley et al. | Mar 2011 | B1 |
| 7956847 | Christie | Jun 2011 | B2 |
| 7957762 | Herz et al. | Jun 2011 | B2 |
| 7965276 | Martin et al. | Jun 2011 | B1 |
| 8001488 | Lam | Aug 2011 | B1 |
| 8006002 | Kalayjian et al. | Aug 2011 | B2 |
| 8009144 | Yajima | Aug 2011 | B2 |
| 8046705 | Hunleth et al. | Oct 2011 | B2 |
| 8130205 | Forstall et al. | Mar 2012 | B2 |
| 8132123 | Schrag et al. | Mar 2012 | B2 |
| 8140996 | Tomkins | Mar 2012 | B2 |
| 8191011 | Abanami et al. | May 2012 | B2 |
| 8194036 | Braun et al. | Jun 2012 | B1 |
| 8201102 | Lee et al. | Jun 2012 | B2 |
| 8230358 | Chaudhri | Jul 2012 | B1 |
| 8239784 | Hotelling et al. | Aug 2012 | B2 |
| 8266550 | Cleron et al. | Sep 2012 | B1 |
| 8279180 | Hotelling et al. | Oct 2012 | B2 |
| 8307306 | Komatsu | Nov 2012 | B2 |
| 8311727 | Eckstein et al. | Nov 2012 | B2 |
| 8365090 | Ording | Jan 2013 | B2 |
| 8381135 | Hotelling et al. | Feb 2013 | B2 |
| 8427432 | Kim et al. | Apr 2013 | B2 |
| 8448083 | Migos et al. | May 2013 | B1 |
| 8479122 | Hotelling et al. | Jul 2013 | B2 |
| 8487882 | Inaba et al. | Jul 2013 | B2 |
| 8533623 | St. Jacques | Sep 2013 | B2 |
| 8549429 | Tsuruta et al. | Oct 2013 | B2 |
| 8566722 | Gordon et al. | Oct 2013 | B2 |
| 8627236 | Jung et al. | Jan 2014 | B2 |
| 8665209 | Rimas-Ribikauskas et al. | Mar 2014 | B2 |
| 8669945 | Coddington | Mar 2014 | B2 |
| 8677283 | Fong | Mar 2014 | B2 |
| 8686944 | Charlton et al. | Apr 2014 | B1 |
| 8717302 | Qin et al. | May 2014 | B1 |
| 8799816 | Wells et al. | Aug 2014 | B2 |
| 8824245 | Lau et al. | Sep 2014 | B2 |
| 8860674 | Lee et al. | Oct 2014 | B2 |
| 8952886 | Tsuk et al. | Feb 2015 | B2 |
| 8954887 | Tseng et al. | Feb 2015 | B1 |
| 9001625 | Essery et al. | Apr 2015 | B2 |
| 9007057 | Villaret | Apr 2015 | B2 |
| 9007302 | Bandt-Horn | Apr 2015 | B1 |
| 9007323 | Araki | Apr 2015 | B2 |
| 9020538 | White et al. | Apr 2015 | B1 |
| 9052814 | Ording | Jun 2015 | B2 |
| 9104705 | Fujinaga | Aug 2015 | B2 |
| 9176652 | Patel et al. | Nov 2015 | B1 |
| 9182876 | Kim et al. | Nov 2015 | B2 |
| 9189089 | Sutton et al. | Nov 2015 | B2 |
| 9195219 | Hong et al. | Nov 2015 | B2 |
| 9229624 | Wei et al. | Jan 2016 | B2 |
| 9268400 | Gomez Sainz-Garcia | Feb 2016 | B2 |
| 9395867 | Griffin et al. | Jul 2016 | B2 |
| 9395905 | Wherry | Jul 2016 | B2 |
| 9442649 | Davis et al. | Sep 2016 | B2 |
| 9448691 | Suda | Sep 2016 | B2 |
| D778912 | Akana et al. | Feb 2017 | S |
| 9582187 | Gil et al. | Feb 2017 | B2 |
| 9620312 | Ely et al. | Apr 2017 | B2 |
| 9651922 | Hysek et al. | May 2017 | B2 |
| 9666178 | Loubiere et al. | May 2017 | B2 |
| 9678571 | Robert et al. | Jun 2017 | B1 |
| 9696809 | Temple | Jul 2017 | B2 |
| 9772769 | Shimazu | Sep 2017 | B2 |
| 9798443 | Gray | Oct 2017 | B1 |
| 9823828 | Zambetti et al. | Nov 2017 | B2 |
| D813239 | Akana et al. | Mar 2018 | S |
| 9921711 | Oh et al. | Mar 2018 | B2 |
| 9965144 | Nakamura et al. | May 2018 | B2 |
| 9984539 | Moussette et al. | May 2018 | B2 |
| 10019097 | Ely et al. | Jul 2018 | B2 |
| 10048802 | Shedletsky et al. | Aug 2018 | B2 |
| 10057470 | Kim et al. | Aug 2018 | B2 |
| 10097496 | Dye et al. | Oct 2018 | B2 |
| 10133439 | Brichter et al. | Nov 2018 | B1 |
| 10175652 | Ely et al. | Jan 2019 | B2 |
| 10216147 | Ely et al. | Feb 2019 | B2 |
| 10216352 | Liang et al. | Feb 2019 | B2 |
| 10222909 | Shedletsky et al. | Mar 2019 | B2 |
| 10275117 | Zambetti et al. | Apr 2019 | B2 |
| D849749 | Akana et al. | May 2019 | S |
| 10289218 | Young | May 2019 | B1 |
| 10296125 | Ely et al. | May 2019 | B2 |
| 10324620 | Balaram | Jun 2019 | B2 |
| 10331081 | Ely et al. | Jun 2019 | B2 |
| 10331082 | Ely et al. | Jun 2019 | B2 |
| 10339721 | Dascola et al. | Jul 2019 | B1 |
| 10642467 | Merminod et al. | May 2020 | B2 |
| 20010004337 | Paratte | Jun 2001 | A1 |
| 20010011991 | Wang et al. | Aug 2001 | A1 |
| 20010041596 | Forlenzo et al. | Nov 2001 | A1 |
| 20010043514 | Kita | Nov 2001 | A1 |
| 20020015024 | Westerman et al. | Feb 2002 | A1 |
| 20020019296 | Freeman et al. | Feb 2002 | A1 |
| 20020027547 | Kamijo et al. | Mar 2002 | A1 |
| 20020030665 | Ano | Mar 2002 | A1 |
| 20020030668 | Hoshino et al. | Mar 2002 | A1 |
| 20020036623 | Kano | Mar 2002 | A1 |
| 20020047860 | Ceulaer et al. | Apr 2002 | A1 |
| 20020054164 | Uemura | May 2002 | A1 |
| 20020063684 | Tran | May 2002 | A1 |
| 20020101457 | Lang | Aug 2002 | A1 |
| 20020101458 | Sangiovanni | Aug 2002 | A1 |
| 20020118169 | Hinckley et al. | Aug 2002 | A1 |
| 20020118605 | Born et al. | Aug 2002 | A1 |
| 20020126099 | Engholm | Sep 2002 | A1 |
| 20020154150 | Ogaki et al. | Oct 2002 | A1 |
| 20020154175 | Abello et al. | Oct 2002 | A1 |
| 20020171689 | Fox et al. | Nov 2002 | A1 |
| 20020186621 | Lai | Dec 2002 | A1 |
| 20030020671 | Santoro et al. | Jan 2003 | A1 |
| 20030025673 | Ledbetter et al. | Feb 2003 | A1 |
| 20030043209 | Pearson | Mar 2003 | A1 |
| 20030052901 | Fukuchi | Mar 2003 | A1 |
| 20030058241 | Hsu | Mar 2003 | A1 |
| 20030076301 | Tsuk et al. | Apr 2003 | A1 |
| 20030081507 | Kitazawa | May 2003 | A1 |
| 20030098891 | Molander | May 2003 | A1 |
| 20030103044 | Sunda et al. | Jun 2003 | A1 |
| 20030112279 | Irimajiri | Jun 2003 | A1 |
| 20030115384 | Sonehara et al. | Jun 2003 | A1 |
| 20030123329 | Guanter et al. | Jul 2003 | A1 |
| 20030137540 | Klevenz | Jul 2003 | A1 |
| 20030142081 | Iizuka et al. | Jul 2003 | A1 |
| 20030142288 | Kinrot et al. | Jul 2003 | A1 |
| 20030189598 | Lipstein et al. | Oct 2003 | A1 |
| 20030210286 | Gerpheide et al. | Nov 2003 | A1 |
| 20040013042 | Farine | Jan 2004 | A1 |
| 20040027793 | Haraguchi et al. | Feb 2004 | A1 |
| 20040038667 | Vance | Feb 2004 | A1 |
| 20040047244 | Iino et al. | Mar 2004 | A1 |
| 20040073935 | Kang | Apr 2004 | A1 |
| 20040085328 | Maruyama et al. | May 2004 | A1 |
| 20040100479 | Nakano et al. | May 2004 | A1 |
| 20040113819 | Gauthey et al. | Jun 2004 | A1 |
| 20040130580 | Howard et al. | Jul 2004 | A1 |
| 20040130581 | Howard et al. | Jul 2004 | A1 |
| 20040145595 | Bennett | Jul 2004 | A1 |
| 20040150621 | Bohn | Aug 2004 | A1 |
| 20040155907 | Yamaguchi et al. | Aug 2004 | A1 |
| 20040170270 | Takashima et al. | Sep 2004 | A1 |
| 20040196267 | Kawai et al. | Oct 2004 | A1 |
| 20040218472 | Narayanaswami et al. | Nov 2004 | A1 |
| 20040225613 | Narayanaswami et al. | Nov 2004 | A1 |
| 20040230599 | Moore et al. | Nov 2004 | A1 |
| 20040233162 | Kobayashi | Nov 2004 | A1 |
| 20040239649 | Ludtke | Dec 2004 | A1 |
| 20040239692 | Balle et al. | Dec 2004 | A1 |
| 20040252119 | Hunleth et al. | Dec 2004 | A1 |
| 20040264301 | Howard et al. | Dec 2004 | A1 |
| 20050007884 | Lorenzato | Jan 2005 | A1 |
| 20050012723 | Pallakoff | Jan 2005 | A1 |
| 20050028111 | Schrag et al. | Feb 2005 | A1 |
| 20050081164 | Hama et al. | Apr 2005 | A1 |
| 20050091604 | Davis | Apr 2005 | A1 |
| 20050097466 | Levi Montalcini | May 2005 | A1 |
| 20050116941 | Wallington | Jun 2005 | A1 |
| 20050136955 | Mumick et al. | Jun 2005 | A1 |
| 20050162423 | Goggin | Jul 2005 | A1 |
| 20050168566 | Tada et al. | Aug 2005 | A1 |
| 20050183012 | Petro et al. | Aug 2005 | A1 |
| 20050190059 | Wehrenberg | Sep 2005 | A1 |
| 20050191994 | May et al. | Sep 2005 | A1 |
| 20050195216 | Kramer et al. | Sep 2005 | A1 |
| 20050209051 | Santomassimo et al. | Sep 2005 | A1 |
| 20050215848 | Lorenzato | Sep 2005 | A1 |
| 20050231512 | Niles et al. | Oct 2005 | A1 |
| 20050259077 | Adams et al. | Nov 2005 | A1 |
| 20060007129 | Pletikosa | Jan 2006 | A1 |
| 20060017692 | Wehrenberg et al. | Jan 2006 | A1 |
| 20060020904 | Aaltonen et al. | Jan 2006 | A1 |
| 20060022956 | Lengeling et al. | Feb 2006 | A1 |
| 20060026521 | Hotelling et al. | Feb 2006 | A1 |
| 20060026535 | Hotelling et al. | Feb 2006 | A1 |
| 20060026536 | Hotelling et al. | Feb 2006 | A1 |
| 20060028444 | Hinckley et al. | Feb 2006 | A1 |
| 20060028446 | Liberty et al. | Feb 2006 | A1 |
| 20060033724 | Chaudhri et al. | Feb 2006 | A1 |
| 20060055700 | Niles et al. | Mar 2006 | A1 |
| 20060064716 | Sull et al. | Mar 2006 | A1 |
| 20060085751 | O'brien et al. | Apr 2006 | A1 |
| 20060090090 | Perng | Apr 2006 | A1 |
| 20060092177 | Blasko | May 2006 | A1 |
| 20060112350 | Kato | May 2006 | A1 |
| 20060136173 | Case et al. | Jun 2006 | A1 |
| 20060143574 | Ito et al. | Jun 2006 | A1 |
| 20060152480 | Senn | Jul 2006 | A1 |
| 20060181506 | Fyke | Aug 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060212905 | Matsuda et al. | Sep 2006 | A1 |
| 20060224945 | Khan et al. | Oct 2006 | A1 |
| 20060255683 | Suzuki et al. | Nov 2006 | A1 |
| 20060268019 | Wang et al. | Nov 2006 | A1 |
| 20060268020 | Han | Nov 2006 | A1 |
| 20060290671 | Bohn et al. | Dec 2006 | A1 |
| 20070002019 | Lane et al. | Jan 2007 | A1 |
| 20070031119 | Iwanaga | Feb 2007 | A1 |
| 20070046635 | Nishiyama et al. | Mar 2007 | A1 |
| 20070063995 | Bailey et al. | Mar 2007 | A1 |
| 20070070090 | Debettencourt et al. | Mar 2007 | A1 |
| 20070073917 | Larson et al. | Mar 2007 | A1 |
| 20070085841 | Tsuk et al. | Apr 2007 | A1 |
| 20070097151 | Rosenberg | May 2007 | A1 |
| 20070106949 | Narita et al. | May 2007 | A1 |
| 20070120819 | Young et al. | May 2007 | A1 |
| 20070132733 | Ram | Jun 2007 | A1 |
| 20070132789 | Ording et al. | Jun 2007 | A1 |
| 20070168369 | Bruns | Jul 2007 | A1 |
| 20070176910 | Simek et al. | Aug 2007 | A1 |
| 20070180379 | Osato | Aug 2007 | A1 |
| 20070182595 | Ghasabian | Aug 2007 | A1 |
| 20070182999 | Anthony et al. | Aug 2007 | A1 |
| 20070209017 | Gupta et al. | Sep 2007 | A1 |
| 20070211042 | Kim et al. | Sep 2007 | A1 |
| 20070226646 | Nagiyama et al. | Sep 2007 | A1 |
| 20070229458 | Moon | Oct 2007 | A1 |
| 20070236475 | Wherry | Oct 2007 | A1 |
| 20070236479 | Wang et al. | Oct 2007 | A1 |
| 20070237493 | Hall et al. | Oct 2007 | A1 |
| 20070239837 | Jablokov et al. | Oct 2007 | A1 |
| 20070242569 | Inoue et al. | Oct 2007 | A1 |
| 20070247435 | Benko et al. | Oct 2007 | A1 |
| 20070279401 | Ramstein et al. | Dec 2007 | A1 |
| 20070290045 | Cisar | Dec 2007 | A1 |
| 20070296711 | Yee et al. | Dec 2007 | A1 |
| 20080001915 | Pihlaja et al. | Jan 2008 | A1 |
| 20080004084 | Park | Jan 2008 | A1 |
| 20080020810 | Park | Jan 2008 | A1 |
| 20080040692 | Sunday et al. | Feb 2008 | A1 |
| 20080043028 | Tanaka | Feb 2008 | A1 |
| 20080052945 | Matas et al. | Mar 2008 | A1 |
| 20080062127 | Brodersen et al. | Mar 2008 | A1 |
| 20080062141 | Chandhri | Mar 2008 | A1 |
| 20080066135 | Brodersen et al. | Mar 2008 | A1 |
| 20080123473 | Ozawa et al. | May 2008 | A1 |
| 20080125196 | Ryu | May 2008 | A1 |
| 20080129520 | Lee | Jun 2008 | A1 |
| 20080148177 | Lang et al. | Jun 2008 | A1 |
| 20080150901 | Lowles et al. | Jun 2008 | A1 |
| 20080155461 | Ozaki | Jun 2008 | A1 |
| 20080155475 | Duhig | Jun 2008 | A1 |
| 20080158149 | Levin | Jul 2008 | A1 |
| 20080163116 | Lee et al. | Jul 2008 | A1 |
| 20080163119 | Kim et al. | Jul 2008 | A1 |
| 20080165124 | Kim | Jul 2008 | A1 |
| 20080165140 | Christie et al. | Jul 2008 | A1 |
| 20080165153 | Platzer et al. | Jul 2008 | A1 |
| 20080168349 | Lamiraux | Jul 2008 | A1 |
| 20080168382 | Louch et al. | Jul 2008 | A1 |
| 20080168384 | Platzer et al. | Jul 2008 | A1 |
| 20080168404 | Ording | Jul 2008 | A1 |
| 20080172634 | Choi et al. | Jul 2008 | A1 |
| 20080174570 | Jobs et al. | Jul 2008 | A1 |
| 20080186808 | Lee | Aug 2008 | A1 |
| 20080204478 | Hung | Aug 2008 | A1 |
| 20080207281 | Tsuchiya et al. | Aug 2008 | A1 |
| 20080216001 | Ording et al. | Sep 2008 | A1 |
| 20080224995 | Perkunder | Sep 2008 | A1 |
| 20080257701 | Wlotzka | Oct 2008 | A1 |
| 20080279475 | Lee et al. | Nov 2008 | A1 |
| 20080288880 | Reponen et al. | Nov 2008 | A1 |
| 20080318635 | Yoon et al. | Dec 2008 | A1 |
| 20080320391 | Lemay et al. | Dec 2008 | A1 |
| 20090007019 | Kobayashi et al. | Jan 2009 | A1 |
| 20090015550 | Koski | Jan 2009 | A1 |
| 20090030800 | Grois | Jan 2009 | A1 |
| 20090046110 | Sadler et al. | Feb 2009 | A1 |
| 20090050465 | Asada | Feb 2009 | A1 |
| 20090051649 | Rondel | Feb 2009 | A1 |
| 20090059730 | Lyons et al. | Mar 2009 | A1 |
| 20090064031 | Bull et al. | Mar 2009 | A1 |
| 20090070705 | Ording | Mar 2009 | A1 |
| 20090070711 | Kwak et al. | Mar 2009 | A1 |
| 20090079698 | Takashima et al. | Mar 2009 | A1 |
| 20090098912 | Kim et al. | Apr 2009 | A1 |
| 20090100373 | Pixley et al. | Apr 2009 | A1 |
| 20090109069 | Takasaki et al. | Apr 2009 | A1 |
| 20090119678 | Shih et al. | May 2009 | A1 |
| 20090125811 | Bethurum | May 2009 | A1 |
| 20090143117 | Shin et al. | Jun 2009 | A1 |
| 20090144642 | Crystal | Jun 2009 | A1 |
| 20090152452 | Lee et al. | Jun 2009 | A1 |
| 20090156255 | Shin et al. | Jun 2009 | A1 |
| 20090193359 | Anthony et al. | Jul 2009 | A1 |
| 20090196124 | Mooring | Aug 2009 | A1 |
| 20090199130 | Tserr et al. | Aug 2009 | A1 |
| 20090204920 | Beverley et al. | Aug 2009 | A1 |
| 20090204929 | Baurmann et al. | Aug 2009 | A1 |
| 20090231271 | Heubel et al. | Sep 2009 | A1 |
| 20090241150 | White et al. | Sep 2009 | A1 |
| 20090288039 | Mail et al. | Nov 2009 | A1 |
| 20090289905 | Ahn | Nov 2009 | A1 |
| 20090315867 | Sakamoto et al. | Dec 2009 | A1 |
| 20090325563 | Horodezky et al. | Dec 2009 | A1 |
| 20100001967 | Yoo | Jan 2010 | A1 |
| 20100029327 | Jee | Feb 2010 | A1 |
| 20100058223 | Price et al. | Mar 2010 | A1 |
| 20100058226 | Flake | Mar 2010 | A1 |
| 20100058240 | Bull et al. | Mar 2010 | A1 |
| 20100064255 | Rottler et al. | Mar 2010 | A1 |
| 20100070926 | Abanami et al. | Mar 2010 | A1 |
| 20100073692 | Waltman et al. | Mar 2010 | A1 |
| 20100079500 | O'sullivan et al. | Apr 2010 | A1 |
| 20100088634 | Tsuruta et al. | Apr 2010 | A1 |
| 20100093400 | Ju et al. | Apr 2010 | A1 |
| 20100110044 | Englund | May 2010 | A1 |
| 20100113101 | Tanada | May 2010 | A1 |
| 20100128570 | Smith et al. | May 2010 | A1 |
| 20100141609 | Frisbee | Jun 2010 | A1 |
| 20100146387 | Hoover | Jun 2010 | A1 |
| 20100148945 | Yun et al. | Jun 2010 | A1 |
| 20100164908 | Hill et al. | Jul 2010 | A1 |
| 20100169097 | Nachman et al. | Jul 2010 | A1 |
| 20100173678 | Kim et al. | Jul 2010 | A1 |
| 20100187074 | Manni | Jul 2010 | A1 |
| 20100188268 | Grignani et al. | Jul 2010 | A1 |
| 20100199232 | Mistry et al. | Aug 2010 | A1 |
| 20100201692 | Niles et al. | Aug 2010 | A1 |
| 20100211498 | Aabye et al. | Aug 2010 | A1 |
| 20100211919 | Brown et al. | Aug 2010 | A1 |
| 20100214243 | Birnbaum et al. | Aug 2010 | A1 |
| 20100220562 | Hozumi et al. | Sep 2010 | A1 |
| 20100223055 | Mclean | Sep 2010 | A1 |
| 20100229130 | Edge et al. | Sep 2010 | A1 |
| 20100235742 | Hsu et al. | Sep 2010 | A1 |
| 20100248778 | Biswas | Sep 2010 | A1 |
| 20100259481 | Oh | Oct 2010 | A1 |
| 20100267424 | Kim et al. | Oct 2010 | A1 |
| 20100269038 | Tsuda | Oct 2010 | A1 |
| 20100271340 | Nagashima et al. | Oct 2010 | A1 |
| 20100271342 | Nagashima et al. | Oct 2010 | A1 |
| 20100271343 | Nagashima et al. | Oct 2010 | A1 |
| 20100277126 | Naeimi et al. | Nov 2010 | A1 |
| 20100283743 | Coddington | Nov 2010 | A1 |
| 20100315417 | Cho et al. | Dec 2010 | A1 |
| 20100325575 | Platzer et al. | Dec 2010 | A1 |
| 20100331145 | Lakovic et al. | Dec 2010 | A1 |
| 20110003665 | Burton et al. | Jan 2011 | A1 |
| 20110006980 | Taniguchi et al. | Jan 2011 | A1 |
| 20110014956 | Lee et al. | Jan 2011 | A1 |
| 20110022472 | Zon | Jan 2011 | A1 |
| 20110025311 | Chauvin et al. | Feb 2011 | A1 |
| 20110025624 | Goto | Feb 2011 | A1 |
| 20110055752 | Rubinstein et al. | Mar 2011 | A1 |
| 20110057877 | Nagashima et al. | Mar 2011 | A1 |
| 20110057886 | Ng et al. | Mar 2011 | A1 |
| 20110072345 | Lim | Mar 2011 | A1 |
| 20110074719 | Yeh et al. | Mar 2011 | A1 |
| 20110074828 | Capela et al. | Mar 2011 | A1 |
| 20110086613 | Doudkine et al. | Apr 2011 | A1 |
| 20110090255 | Wilson et al. | Apr 2011 | A1 |
| 20110093812 | Fong | Apr 2011 | A1 |
| 20110099509 | Horagai | Apr 2011 | A1 |
| 20110102455 | Temple | May 2011 | A1 |
| 20110126155 | Krishnaraj et al. | May 2011 | A1 |
| 20110128226 | Jensen | Jun 2011 | A1 |
| 20110131494 | Ono et al. | Jun 2011 | A1 |
| 20110131531 | Russell et al. | Jun 2011 | A1 |
| 20110157046 | Lee et al. | Jun 2011 | A1 |
| 20110164042 | Chaudhri | Jul 2011 | A1 |
| 20110167262 | Ross et al. | Jul 2011 | A1 |
| 20110187355 | Dixon et al. | Aug 2011 | A1 |
| 20110193878 | Seo et al. | Aug 2011 | A1 |
| 20110199342 | Vartanian et al. | Aug 2011 | A1 |
| 20110202834 | Mandryk et al. | Aug 2011 | A1 |
| 20110202859 | Fong | Aug 2011 | A1 |
| 20110202866 | Huang et al. | Aug 2011 | A1 |
| 20110224967 | Van Schaik | Sep 2011 | A1 |
| 20110248948 | Griffin et al. | Oct 2011 | A1 |
| 20110252357 | Chaudhri | Oct 2011 | A1 |
| 20110252362 | Cho et al. | Oct 2011 | A1 |
| 20110252369 | Chaudhri | Oct 2011 | A1 |
| 20110271183 | Bose et al. | Nov 2011 | A1 |
| 20110271233 | Radakovitz et al. | Nov 2011 | A1 |
| 20110275940 | Nims et al. | Nov 2011 | A1 |
| 20110279384 | Miller et al. | Nov 2011 | A1 |
| 20110296312 | Boyer et al. | Dec 2011 | A1 |
| 20110298830 | Lam | Dec 2011 | A1 |
| 20110302493 | Runstedler et al. | Dec 2011 | A1 |
| 20110307842 | Chiang et al. | Dec 2011 | A1 |
| 20110316888 | Sachs et al. | Dec 2011 | A1 |
| 20120011437 | James et al. | Jan 2012 | A1 |
| 20120026198 | Maesaka | Feb 2012 | A1 |
| 20120030627 | Nurmi et al. | Feb 2012 | A1 |
| 20120032988 | Katayama | Feb 2012 | A1 |
| 20120038582 | Grant | Feb 2012 | A1 |
| 20120044267 | Fino | Feb 2012 | A1 |
| 20120050185 | Davydov et al. | Mar 2012 | A1 |
| 20120054670 | Rainisto | Mar 2012 | A1 |
| 20120056848 | Yamano et al. | Mar 2012 | A1 |
| 20120062398 | Durand | Mar 2012 | A1 |
| 20120066638 | Ohri | Mar 2012 | A1 |
| 20120068925 | Wong et al. | Mar 2012 | A1 |
| 20120083260 | Arriola et al. | Apr 2012 | A1 |
| 20120089951 | Cassidy | Apr 2012 | A1 |
| 20120092383 | Hysek et al. | Apr 2012 | A1 |
| 20120099406 | Lau et al. | Apr 2012 | A1 |
| 20120105484 | Cul Yanding | May 2012 | A1 |
| 20120127071 | Jitkoff et al. | May 2012 | A1 |
| 20120131504 | Fadell et al. | May 2012 | A1 |
| 20120155223 | Hoover | Jun 2012 | A1 |
| 20120159380 | Kocienda et al. | Jun 2012 | A1 |
| 20120162261 | Kim et al. | Jun 2012 | A1 |
| 20120169776 | Rissa et al. | Jul 2012 | A1 |
| 20120174005 | Deutsch et al. | Jul 2012 | A1 |
| 20120179998 | Nesladek et al. | Jul 2012 | A1 |
| 20120186951 | Wu et al. | Jul 2012 | A1 |
| 20120192110 | Wu | Jul 2012 | A1 |
| 20120197743 | Grigg et al. | Aug 2012 | A1 |
| 20120226977 | Lengeling et al. | Sep 2012 | A1 |
| 20120236037 | Lessing et al. | Sep 2012 | A1 |
| 20120256863 | Zhang et al. | Oct 2012 | A1 |
| 20120256960 | Chaudhri | Oct 2012 | A1 |
| 20120272145 | Ryan et al. | Oct 2012 | A1 |
| 20120272181 | Rogers et al. | Oct 2012 | A1 |
| 20120278725 | Gordon et al. | Nov 2012 | A1 |
| 20120289290 | Chae et al. | Nov 2012 | A1 |
| 20120290472 | Mullen et al. | Nov 2012 | A1 |
| 20120304113 | Patten et al. | Nov 2012 | A1 |
| 20120306765 | Moore | Dec 2012 | A1 |
| 20120324390 | Tao | Dec 2012 | A1 |
| 20120327006 | Israr et al. | Dec 2012 | A1 |
| 20130019182 | Gil et al. | Jan 2013 | A1 |
| 20130024780 | Sutedja et al. | Jan 2013 | A1 |
| 20130024811 | Gleadall et al. | Jan 2013 | A1 |
| 20130027412 | Roddy | Jan 2013 | A1 |
| 20130038636 | Fujiwaka | Feb 2013 | A1 |
| 20130055160 | Yamada et al. | Feb 2013 | A1 |
| 20130067390 | Kwiatkowski et al. | Mar 2013 | A1 |
| 20130073932 | Migos et al. | Mar 2013 | A1 |
| 20130097566 | Berglund | Apr 2013 | A1 |
| 20130111342 | Alameh et al. | May 2013 | A1 |
| 20130111384 | Kim et al. | May 2013 | A1 |
| 20130111407 | Mullen | May 2013 | A1 |
| 20130117689 | Lessing et al. | May 2013 | A1 |
| 20130117698 | Park et al. | May 2013 | A1 |
| 20130135228 | Won et al. | May 2013 | A1 |
| 20130135234 | Hisano et al. | May 2013 | A1 |
| 20130135236 | Yano | May 2013 | A1 |
| 20130139102 | Miura et al. | May 2013 | A1 |
| 20130141342 | Bokma et al. | Jun 2013 | A1 |
| 20130142016 | Pozzo di borgo et al. | Jun 2013 | A1 |
| 20130145292 | Cohen et al. | Jun 2013 | A1 |
| 20130147747 | Takagi | Jun 2013 | A1 |
| 20130154933 | Sheik-nainar | Jun 2013 | A1 |
| 20130169579 | Havnor | Jul 2013 | A1 |
| 20130176020 | Chauvin et al. | Jul 2013 | A1 |
| 20130205939 | Meerovitsch | Aug 2013 | A1 |
| 20130208013 | Yuu et al. | Aug 2013 | A1 |
| 20130218517 | Ausserlechner | Aug 2013 | A1 |
| 20130222301 | Lee et al. | Aug 2013 | A1 |
| 20130226444 | Johansson et al. | Aug 2013 | A1 |
| 20130258819 | Hoover | Oct 2013 | A1 |
| 20130262564 | Wall et al. | Oct 2013 | A1 |
| 20130282360 | Shimota et al. | Oct 2013 | A1 |
| 20130282459 | Smets et al. | Oct 2013 | A1 |
| 20130290116 | Hepworth et al. | Oct 2013 | A1 |
| 20130303087 | Hauser et al. | Nov 2013 | A1 |
| 20130305187 | Phillips et al. | Nov 2013 | A1 |
| 20130326401 | Van Os | Dec 2013 | A1 |
| 20130339343 | Hierons et al. | Dec 2013 | A1 |
| 20130339345 | Soto Matamala et al. | Dec 2013 | A1 |
| 20130342457 | Cox et al. | Dec 2013 | A1 |
| 20140028554 | De los reyes et al. | Jan 2014 | A1 |
| 20140028688 | Houjou et al. | Jan 2014 | A1 |
| 20140028735 | Williams et al. | Jan 2014 | A1 |
| 20140040742 | Park et al. | Feb 2014 | A1 |
| 20140075368 | Kim et al. | Mar 2014 | A1 |
| 20140092037 | Kim | Apr 2014 | A1 |
| 20140105278 | Bivolarsky | Apr 2014 | A1 |
| 20140106734 | Lee | Apr 2014 | A1 |
| 20140132640 | Sharma et al. | May 2014 | A1 |
| 20140136443 | Kinsey et al. | May 2014 | A1 |
| 20140136981 | Xiang et al. | May 2014 | A1 |
| 20140137020 | Sharma et al. | May 2014 | A1 |
| 20140139422 | Mistry et al. | May 2014 | A1 |
| 20140139637 | Mistry et al. | May 2014 | A1 |
| 20140143678 | Mistry et al. | May 2014 | A1 |
| 20140143737 | Mistry et al. | May 2014 | A1 |
| 20140157160 | Cudak et al. | Jun 2014 | A1 |
| 20140160078 | Seo et al. | Jun 2014 | A1 |
| 20140172136 | Ura | Jun 2014 | A1 |
| 20140204229 | Leung et al. | Jul 2014 | A1 |
| 20140215340 | Shetty et al. | Jul 2014 | A1 |
| 20140222916 | Foley et al. | Aug 2014 | A1 |
| 20140237382 | Grandhi | Aug 2014 | A1 |
| 20140253487 | Bezinge et al. | Sep 2014 | A1 |
| 20140258935 | Nishida et al. | Sep 2014 | A1 |
| 20140260776 | Burleson | Sep 2014 | A1 |
| 20140282132 | Daly, IV | Sep 2014 | A1 |
| 20140282142 | Lin | Sep 2014 | A1 |
| 20140282214 | Shirzadi et al. | Sep 2014 | A1 |
| 20140288680 | Hoffman et al. | Sep 2014 | A1 |
| 20140292668 | Fricklas et al. | Oct 2014 | A1 |
| 20140298233 | Pettey et al. | Oct 2014 | A1 |
| 20140306989 | Doubleday et al. | Oct 2014 | A1 |
| 20140328147 | Yang et al. | Nov 2014 | A1 |
| 20140330435 | Stoner et al. | Nov 2014 | A1 |
| 20140333670 | Agnetta et al. | Nov 2014 | A1 |
| 20140347289 | Suh et al. | Nov 2014 | A1 |
| 20140362024 | Hicks | Dec 2014 | A1 |
| 20140372115 | Lebeau et al. | Dec 2014 | A1 |
| 20150036555 | Shin et al. | Feb 2015 | A1 |
| 20150046871 | Lewis | Feb 2015 | A1 |
| 20150058744 | Dhingra et al. | Feb 2015 | A1 |
| 20150067497 | Cieplinski et al. | Mar 2015 | A1 |
| 20150074615 | Han et al. | Mar 2015 | A1 |
| 20150077398 | Yairi et al. | Mar 2015 | A1 |
| 20150085621 | Hong et al. | Mar 2015 | A1 |
| 20150121224 | Krasnahill, Jr. | Apr 2015 | A1 |
| 20150149899 | Bernstein et al. | May 2015 | A1 |
| 20150178041 | Uskoreit | Jun 2015 | A1 |
| 20150199012 | Palmer | Jul 2015 | A1 |
| 20150199110 | Nakazato | Jul 2015 | A1 |
| 20150234518 | Teller et al. | Aug 2015 | A1 |
| 20150234562 | Ording | Aug 2015 | A1 |
| 20150261310 | Walmsley et al. | Sep 2015 | A1 |
| 20150269944 | Wang | Sep 2015 | A1 |
| 20150277559 | Vescovi et al. | Oct 2015 | A1 |
| 20150302301 | Petersen | Oct 2015 | A1 |
| 20150370425 | Chen et al. | Dec 2015 | A1 |
| 20150370529 | Zambetti et al. | Dec 2015 | A1 |
| 20150378447 | Nagano et al. | Dec 2015 | A1 |
| 20150378555 | Ramanathan et al. | Dec 2015 | A1 |
| 20160011758 | Dornbush et al. | Jan 2016 | A1 |
| 20160034133 | Wilson et al. | Feb 2016 | A1 |
| 20160034148 | Wilson et al. | Feb 2016 | A1 |
| 20160034152 | Wilson et al. | Feb 2016 | A1 |
| 20160034153 | Lejeune et al. | Feb 2016 | A1 |
| 20160034166 | Wilson et al. | Feb 2016 | A1 |
| 20160034167 | Wilson et al. | Feb 2016 | A1 |
| 20160054710 | Jo et al. | Feb 2016 | A1 |
| 20160062466 | Moussette et al. | Mar 2016 | A1 |
| 20160062487 | Foss et al. | Mar 2016 | A1 |
| 20160062567 | Yang et al. | Mar 2016 | A1 |
| 20160062571 | Dascola et al. | Mar 2016 | A1 |
| 20160062573 | Dascola et al. | Mar 2016 | A1 |
| 20160062582 | Wilson et al. | Mar 2016 | A1 |
| 20160062608 | Foss et al. | Mar 2016 | A1 |
| 20160063828 | Moussette et al. | Mar 2016 | A1 |
| 20160063850 | Yang et al. | Mar 2016 | A1 |
| 20160065509 | Yang et al. | Mar 2016 | A1 |
| 20160065525 | Dye et al. | Mar 2016 | A1 |
| 20160071241 | Karunamuni et al. | Mar 2016 | A1 |
| 20160098016 | Ely et al. | Apr 2016 | A1 |
| 20160162164 | Phillips et al. | Jun 2016 | A1 |
| 20160170436 | Farrar et al. | Jun 2016 | A1 |
| 20160170598 | Zambetti et al. | Jun 2016 | A1 |
| 20160170608 | Zambetti et al. | Jun 2016 | A1 |
| 20160170624 | Zambetti et al. | Jun 2016 | A1 |
| 20160170625 | Zambetti et al. | Jun 2016 | A1 |
| 20160180820 | Pascucci et al. | Jun 2016 | A1 |
| 20160202866 | Zambetti et al. | Jul 2016 | A1 |
| 20160209939 | Zambetti et al. | Jul 2016 | A1 |
| 20160231883 | Zambetti et al. | Aug 2016 | A1 |
| 20160259499 | Kocienda et al. | Sep 2016 | A1 |
| 20160259530 | Everitt et al. | Sep 2016 | A1 |
| 20160259535 | Fleizach et al. | Sep 2016 | A1 |
| 20160269540 | Butcher et al. | Sep 2016 | A1 |
| 20160327911 | Eim et al. | Nov 2016 | A1 |
| 20160357420 | Wilson et al. | Dec 2016 | A1 |
| 20170010678 | Tuli | Jan 2017 | A1 |
| 20170010751 | Shedietsky et al. | Jan 2017 | A1 |
| 20170045958 | Battlogg | Feb 2017 | A1 |
| 20170053542 | Wilson et al. | Feb 2017 | A1 |
| 20170089735 | Ruh | Mar 2017 | A1 |
| 20170104902 | Kim et al. | Apr 2017 | A1 |
| 20170208466 | Seo et al. | Jul 2017 | A1 |
| 20170269692 | Eck et al. | Sep 2017 | A1 |
| 20170315716 | Zambetti et al. | Nov 2017 | A1 |
| 20170357427 | Wilson et al. | Dec 2017 | A1 |
| 20170358181 | Moussette et al. | Dec 2017 | A1 |
| 20180024683 | Ely et al. | Jan 2018 | A1 |
| 20180067557 | Robert et al. | Mar 2018 | A1 |
| 20180074690 | Zambetti et al. | Mar 2018 | A1 |
| 20180081453 | Ely | Mar 2018 | A1 |
| 20180088532 | Ely et al. | Mar 2018 | A1 |
| 20180088797 | Mcatee et al. | Mar 2018 | A1 |
| 20180210516 | Zambetti et al. | Jul 2018 | A1 |
| 20180307363 | Ely et al. | Oct 2018 | A1 |
| 20180335891 | Shedletsky et al. | Nov 2018 | A1 |
| 20180335901 | Manzari et al. | Nov 2018 | A1 |
| 20180336866 | Triverio et al. | Nov 2018 | A1 |
| 20180341344 | Foss et al. | Nov 2018 | A1 |
| 20180367489 | Dye et al. | Dec 2018 | A1 |
| 20190033862 | Groden et al. | Jan 2019 | A1 |
| 20190050055 | Chaudhri et al. | Feb 2019 | A1 |
| 20190056700 | Matsuno et al. | Feb 2019 | A1 |
| 20190072912 | Pandya et al. | Mar 2019 | A1 |
| 20190080066 | Van Os et al. | Mar 2019 | A1 |
| 20190080072 | Van Os et al. | Mar 2019 | A1 |
| 20190101870 | Pandya et al. | Apr 2019 | A1 |
| 20190163324 | Shedletsky et al. | May 2019 | A1 |
| 20190163329 | Yang et al. | May 2019 | A1 |
| 20190212885 | Zambetti et al. | Jul 2019 | A1 |
| 20190243471 | Foss et al. | Aug 2019 | A1 |
| 20190274565 | Soli et al. | Sep 2019 | A1 |
| 20190279520 | Wilson et al. | Sep 2019 | A1 |
| 20200081538 | Moussette et al. | Mar 2020 | A1 |
| 20200081539 | Moussette et al. | Mar 2020 | A1 |
| 20200110522 | Zambetti et al. | Apr 2020 | A1 |
| 20200145361 | Dye et al. | May 2020 | A1 |
| 20200167047 | Dascola et al. | May 2020 | A1 |
| 20200272287 | Yang et al. | Aug 2020 | A1 |
| 20200272293 | Zambetti et al. | Aug 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2012200689 | Mar 2012 | AU |
| 2014100584 | Jul 2014 | AU |
| 2016231505 | Oct 2016 | AU |
| 2018100429 | May 2018 | AU |
| 2018100429 | Aug 2018 | AU |
| 1263425 | Aug 2000 | CN |
| 1330310 | Jan 2002 | CN |
| 1341889 | Mar 2002 | CN |
| 1398366 | Feb 2003 | CN |
| 1549998 | Nov 2004 | CN |
| 1757011 | Apr 2006 | CN |
| 1797295 | Jul 2006 | CN |
| 1811899 | Aug 2006 | CN |
| 101101595 | Jan 2008 | CN |
| 101431545 | May 2009 | CN |
| 101446802 | Jun 2009 | CN |
| 101625620 | Jan 2010 | CN |
| 101876877 | Nov 2010 | CN |
| 101893992 | Nov 2010 | CN |
| 101976171 | Feb 2011 | CN |
| 101241407 | Jul 2011 | CN |
| 102402328 | Apr 2012 | CN |
| 102508707 | Jun 2012 | CN |
| 102591579 | Jul 2012 | CN |
| 102750066 | Oct 2012 | CN |
| 102859482 | Jan 2013 | CN |
| 102902453 | Jan 2013 | CN |
| 102902454 | Jan 2013 | CN |
| 102905181 | Jan 2013 | CN |
| 101034328 | Feb 2013 | CN |
| 102981770 | Mar 2013 | CN |
| 103069378 | Apr 2013 | CN |
| 103154878 | Jun 2013 | CN |
| 103270486 | Aug 2013 | CN |
| 103460164 | Dec 2013 | CN |
| 103703437 | Apr 2014 | CN |
| 103782252 | May 2014 | CN |
| 103793138 | May 2014 | CN |
| 103858088 | Jun 2014 | CN |
| 103870255 | Jun 2014 | CN |
| 103914261 | Jul 2014 | CN |
| 103970413 | Aug 2014 | CN |
| 104166458 | Nov 2014 | CN |
| 107797657 | Mar 2018 | CN |
| 108139863 | Jun 2018 | CN |
| 108304106 | Jul 2018 | CN |
| 108369455 | Aug 2018 | CN |
| 1052566 | Nov 2000 | EP |
| 1168149 | Jan 2002 | EP |
| 1406158 | Apr 2004 | EP |
| 1486860 | Dec 2004 | EP |
| 1505484 | Feb 2005 | EP |
| 1637969 | Mar 2006 | EP |
| 1850213 | Oct 2007 | EP |
| 1942401 | Jul 2008 | EP |
| 1944677 | Jul 2008 | EP |
| 1956433 | Aug 2008 | EP |
| 1956446 | Aug 2008 | EP |
| 2124131 | Nov 2009 | EP |
| 2207084 | Jul 2010 | EP |
| 2224317 | Sep 2010 | EP |
| 2237140 | Oct 2010 | EP |
| 2302492 | Mar 2011 | EP |
| 2360902 | Aug 2011 | EP |
| 2385451 | Nov 2011 | EP |
| 2551784 | Jan 2013 | EP |
| 2610738 | Jul 2013 | EP |
| 2733579 | May 2014 | EP |
| 2733598 | May 2014 | EP |
| 2741176 | Jun 2014 | EP |
| 3401770 | Nov 2018 | EP |
| 2392773 | Mar 2004 | GB |
| 2489580 | Oct 2012 | GB |
| 55-80084 | Jun 1980 | JP |
| 5-88812 | Apr 1993 | JP |
| 6-348408 | Dec 1994 | JP |
| 7-152478 | Jun 1995 | JP |
| 11-110106 | Apr 1999 | JP |
| 2000-503153 | Mar 2000 | JP |
| 2000-305760 | Nov 2000 | JP |
| 2001-100905 | Apr 2001 | JP |
| 2001-202178 | Jul 2001 | JP |
| 2001-202181 | Jul 2001 | JP |
| 2002-288690 | Oct 2002 | JP |
| 2003-248544 | Sep 2003 | JP |
| 2003-330586 | Nov 2003 | JP |
| 2003-330856 | Nov 2003 | JP |
| 2004-21522 | Jan 2004 | JP |
| 2004-184396 | Jul 2004 | JP |
| 2004-259063 | Sep 2004 | JP |
| 2005-4891 | Jan 2005 | JP |
| 2005-196077 | Jul 2005 | JP |
| 2006-11690 | Jan 2006 | JP |
| 2006-140990 | Jun 2006 | JP |
| 2006-185273 | Jul 2006 | JP |
| 2007-170995 | Jul 2007 | JP |
| 2007-179544 | Jul 2007 | JP |
| 2008-97057 | Apr 2008 | JP |
| 2008-518539 | May 2008 | JP |
| 2008-157974 | Jul 2008 | JP |
| 2008-539513 | Nov 2008 | JP |
| 2009-59382 | Mar 2009 | JP |
| 2009-510404 | Mar 2009 | JP |
| 2009-128296 | Jun 2009 | JP |
| 2009-246553 | Oct 2009 | JP |
| 2009-294526 | Dec 2009 | JP |
| 2010-257051 | Nov 2010 | JP |
| 2011-8540 | Jan 2011 | JP |
| 2011-90640 | May 2011 | JP |
| 2011-96043 | May 2011 | JP |
| 2011-530738 | Dec 2011 | JP |
| 2012-58979 | Mar 2012 | JP |
| 2012-155698 | Aug 2012 | JP |
| 2013-114844 | Jun 2013 | JP |
| 2013-122738 | Jun 2013 | JP |
| 2013-137750 | Jul 2013 | JP |
| 2014-42164 | Mar 2014 | JP |
| 2016-538653 | Dec 2016 | JP |
| 10-2004-0107472 | Dec 2004 | KR |
| 10-0630154 | Sep 2006 | KR |
| 10-2010-0003589 | Jan 2010 | KR |
| 10-2010-0109277 | Oct 2010 | KR |
| 10-2011-0093090 | Aug 2011 | KR |
| 10-2011-0114294 | Oct 2011 | KR |
| 10-2012-0071468 | Jul 2012 | KR |
| 10-2012-0079707 | Jul 2012 | KR |
| 10-2013-0027017 | Mar 2013 | KR |
| I269202 | Dec 2006 | TW |
| D122820 | May 2008 | TW |
| 200843452 | Nov 2008 | TW |
| 201119339 | Jun 2011 | TW |
| I349212 | Sep 2011 | TW |
| I381305 | Jan 2013 | TW |
| I384394 | Feb 2013 | TW |
| I394410 | Apr 2013 | TW |
| I395498 | May 2013 | TW |
| I405106 | Aug 2013 | TW |
| 201403363 | Jan 2014 | TW |
| I426416 | Feb 2014 | TW |
| 201421340 | Jun 2014 | TW |
| I443547 | Jul 2014 | TW |
| 199308517 | Apr 1993 | WO |
| 199619872 | Jun 1996 | WO |
| 200169369 | Sep 2001 | WO |
| 2003021568 | Mar 2003 | WO |
| 2006037545 | Apr 2006 | WO |
| 2006042309 | Apr 2006 | WO |
| 2008004772 | Jan 2008 | WO |
| 2008030976 | Mar 2008 | WO |
| 2008033853 | Mar 2008 | WO |
| 2008085742 | Jul 2008 | WO |
| 2008086218 | Jul 2008 | WO |
| 2008106777 | Sep 2008 | WO |
| 2009026508 | Feb 2009 | WO |
| 2009085378 | Jul 2009 | WO |
| 2009097592 | Aug 2009 | WO |
| 2010024969 | Mar 2010 | WO |
| 2010150768 | Dec 2010 | WO |
| 2011126502 | Oct 2011 | WO |
| 2012006494 | Jan 2012 | WO |
| 2012080020 | Jun 2012 | WO |
| 2013105664 | Jul 2013 | WO |
| 2013114844 | Aug 2013 | WO |
| 2013133901 | Sep 2013 | WO |
| 2013169842 | Nov 2013 | WO |
| 2013169846 | Nov 2013 | WO |
| 2013169849 | Nov 2013 | WO |
| 2013169875 | Nov 2013 | WO |
| 2014105276 | Jul 2014 | WO |
| 2014189197 | Nov 2014 | WO |
| 2015034969 | Mar 2015 | WO |
| 2016144385 | Sep 2016 | WO |
| 2016144563 | Sep 2016 | WO |
| 2017027625 | Feb 2017 | WO |
| 2018048518 | Mar 2018 | WO |
| 2018048632 | Mar 2018 | WO |
| Entry |
|---|
| Non-Final Office Action received for U.S. Appl. No. 14/913,349, dated Jan. 2, 2020, 25 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,308, dated Jan. 15, 2020, 7 pages. |
| Office Action received for Chinese Patent Application No. 201910454076.4, dated Dec. 18, 2019, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA201970259, dated Jan. 15, 2020, 4 pages. |
| Office Action received for Indian Patent Application No. 201617008291, dated Jan. 14, 2020, 7 pages. |
| Office Action received for Indian Patent Application No. 201617008296, dated Jan. 14, 2020, 7 pages. |
| Advisory Action received for U.S. Appl. No. 14/913,349, dated Oct. 29, 2019, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/913,349, dated Oct. 7, 2019, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/147,413, dated Oct. 28, 2019, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 14/641,308, dated Oct. 10, 2019, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/655,253, dated Mar. 31, 2020, 5 pages. |
| Intention to Grant received for European Patent Application No. 14772494.2, dated Mar. 16, 2020, 10 pages. |
| Office Action received for Taiwanese Patent Application No. 104107318, dated Feb. 18, 2020, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 16/147,413, dated Nov. 25, 2019, 2019, 6 pages. |
| European Search Report received for European Patent Application No. 19173371.6, dated Oct. 30, 2019, 7 pages. |
| European Search Report received for European Patent Application No. 19199004.3, dated Nov. 12, 2019, 6 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,950, dated Nov. 25, 2019, 24 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/049237, dated Oct. 31, 2019, 18 pages. |
| Office Action received for Chinese Patent Application No. 201580046339.8, dated Oct. 31, 2019, 9 pages (3 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for European Patent Application No. 19173371.6, dated Nov. 12, 2019, 11 pages. |
| Office Action received for European Patent Application No. 19173886.3, dated Nov. 12, 2019, 9 pages. |
| Office Action received for European Patent Application No. 19199004.3, dated Nov. 22, 2019, 10 pages. |
| Office Action received for Korean Patent Application No. 10-2018-7033888, dated Nov. 28, 2019, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7007748, dated Nov. 15, 2019, 9 pages (3 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7028736, dated Nov. 28, 2019, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Extended European Search Report received for European Patent Application No. 19217240.1, dated May 25, 2020, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/384,726, dated May 14, 2020, 16 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7007748, dated May 6, 2020, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7028736, dated May 7, 2020, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Non-Final Office Action received for U.S. Appl. No. 14/913,349, dated Apr. 22, 2020, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/358,483, dated May 1, 2020, 37 pages. |
| Office Action received for Australian Patent Application No. 2019216614, dated Apr. 1, 2020, 4 pages. |
| Office Action received for Chinese Patent Application No. 201910164962.3, dated Apr. 8, 2020, 25 pages (13 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130518, dated Oct. 15, 2015, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Decision to Grant received for European Patent Application No. 14772001.5, dated Dec. 5, 2019, 2 pages. |
| European Search Report received for European Patent Application No. 19206249.5, dated Dec. 19, 2019, 4 pages. |
| Office Action received for Chinese Patent Application No. 201910454069.4, dated Dec. 20, 2019, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 16/144,950, dated Feb. 20, 2020, 5 pages. |
| Decision on Appeal received for Korean Patent Application No. 10-2016-7008474, dated Jan. 29, 2020, 21 pages (2 pages of English Translation and 19 pages of Official Copy). |
| Decision to Grant received for European Patent Application No. 14772002.3, dated Feb. 20, 2020, 2 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7010872, dated Feb. 10, 2020, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Indian Patent Application No. 201617009428, dated Feb. 26, 2020, 7 pages. |
| Office Action received for Korean Patent Application No. 10-2017-7024506, dated Feb. 19, 2020, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/641,308, dated Mar. 10, 2020, 4 pages. |
| Extended European Search Report received for European Patent Application No. 19195247.2, dated Mar. 9, 2020, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/147,413, dated Mar. 11, 2020, 22 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,950, dated Mar. 19, 2020, 14 pages. |
| Office Action received for Chinese Patent Application No. 201580077206.7, dated Feb. 3, 2020, 29 pages (8 pages of English Translation and 21 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/147,413, dated Jun. 2, 2020, 4 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019201628, dated Sep. 10, 2019, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/049,052, dated Sep. 16, 2019, 5 pages. |
| Office Action received for European Patent Application No. 14771688.0, dated Sep. 16, 2019, 7 pages. |
| Andrews, Phillip., “Advanced Photoshop Elements for Digital Photographers”, Chapters 7.04-7.05, Feb. 20, 2004, 12 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/144,950, dated Jan. 29, 2020, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/818,500, dated Jan. 30, 2020, 5 pages. |
| Decision on Appeal received for Korean Patent Application No. 10-2018-7010872, dated Jan. 20, 2020, 20 pages (3 pages of English Translation and 17 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 15/655,253, dated Feb. 4, 2020, 20 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/049237, dated Jan. 8, 2020, 21 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/913,345, dated Feb. 10, 2020, 10 pages. |
| Office Action received for European Patent Application No. 19206249.5, dated Jan. 20, 2020, 8 pages. |
| Office Action received for Indian Patent Application No. 201617009216, dated Jan. 24, 2020, 6 pages. |
| Verth, Van, et al., “Essential Mathematics for Games and Interactive Applications”, Programmers Guide, Morgan Kaufmann publishers, Mar. 25, 2004, 37 pages. |
| Advisory Action received for U.S. Appl. No. 15/049,052, dated Sep. 11, 2017, 2 pages. |
| Advisory Action received for U.S. Appl. No. 15/049,058, dated Oct. 18, 2017, 3 pages. |
| Advisory Action received for U.S. Appl. No. 15/049,064, dated May 10, 2017, 3 Pages. |
| Agarwal, Deepesh, “DexClock—Live Clock and Date Blended into Beautiful Artwork as Your Desktop Wallpaper”, Available at: https://www.megaleecher.net/DexCiock_Wallpaper_Designs, Jul. 6, 2013, 4 pages. |
| Apple, “iPhone User's Guide”, Available at: <http://mesnotices.20minutes.fr/manuel-notice-mode-emploi/APPLE/IPHONE%2D%5FE#>, Retrieved on Mar. 27, 2008, Jun. 2007, 137 pages. |
| Arraich, Jay, “Bevel and ErnbossPhotoshop Tips”, Webpage [online], www.arraich.com. Available on: <http://web.archive.org/we b/20021203061806/http://www.arraich.com/effects1/bevelandemboss.htm>, Feb. 19, 2008, 8 pages. |
| Arraich, Jay, “Drop ShadowPhotoshop Tips”, Webpage [online], www.arraich.com, Available on: <http://web.archive.org/web/20021215195819/www.arraich.com/effects1/dropshadow.htm>, Feb. 19, 2008, 7 pages. |
| Brinkmann, Martin, “How to Zoom In FirefoxGhacks”, Available at: <https://web.archive.org/web/20130804034728/https://www.ghacks.net/2009/02/23/how-to-zoom-in-firefox/>, Feb. 23, 2009, 11 pages. |
| Colt, Sam, “Here's One Way Apple's Smartwatch Could Be Better Than Anything Else”, Business Insider, Aug. 21, 2014, pp. 1-4. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/641,252, dated Aug. 28, 2018, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/641,252, dated Jul. 9, 2018, 25 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/641,252, dated May 10, 2018, 10 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/829,573, dated Aug. 9, 2018, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/829,573, dated Sep. 11, 2018, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/830,629, dated Feb. 13, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/841,656, dated Apr. 11, 2018, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/841,656, dated May 7, 2018, 14 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/927,768, dated Aug. 7, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/927,768, dated Jul. 9, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/055,489, dated Feb. 26, 2019, 2 pages. |
| “Creating a Drop Shadow Effect on Text”, Developing Webs Photoshop Tutorials, Webpage [online]. www.dwphotoshop.com, Avaiable on: <https://www.dwphotoshop.com/photoshop/dropshadow.php>, Feb. 19, 2008, 3 pages. |
| Decision on Appeal received for Korean Patent Application No. 10-2016-7008449, dated Jul. 30, 2019, 29 pages (7 pages of English Translationn and 22 pages of Official Copy). |
| Decision to Grant received for Danish Patent Application No. PA201570781, dated Jul. 17, 2017, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201670117, dated Nov. 20, 2017, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201770181, dated Mar. 7, 2018, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870631, dated May 15, 2019, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870632, dated May 14, 2019, 2 pages. |
| Decision to Grant received for European Patent Application No. 18157131.6, dated May 16, 2019, 2 pages. |
| Dewsberry, Victor, “Designing for Small Screens”, AVA Publishing, 2005, 27 pages. |
| Extended European Search Report received for European Patent Application No. 19156614.0, dated May 28, 2019, 9 pages. |
| Final Office Action Received for U.S. Appl. No. 10/874,788, dated Feb. 17, 2011, 10 Pages. |
| Final Office Action Received for U.S. Appl. No. 10/874,788, dated Feb. 22, 2008, 23 pages. |
| Final Office Action Received for U.S. Appl. No. 10/874,788, dated May 12, 2011, 18 pages. |
| Final Office Action received for U.S. Appl. No. 13/038,276, dated Mar. 11, 2016, 36 pages. |
| Final Office Action received for U.S. Appl. No. 13/038,276, dated Mar. 27, 2014, 24 pages. |
| Final Office Action Received for U.S. Appl. No. 13/526,462, dated May 8, 2014, 19 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,308, dated Jul. 1, 2019, 46 pages. |
| Final Office Action received for U.S. Appl. No. 14/641,308, dated Mar. 14, 2018, 42 pages. |
| Final Office Action received for U.S. Appl. No. 14/830,629, dated Apr. 16, 2018, 27 pages. |
| Final Office Action received for U.S. Appl. No. 14/839,912, dated Jul. 30, 2019, 42 pages. |
| Final Office Action received for U.S. Appl. No. 14/839,912, dated Sep. 13, 2018, 31 pages. |
| Final Office Action received for U.S. Appl. No. 14/913,345, dated Oct. 26, 2018, 20 pages. |
| Final Office Action Received for U.S. Appl. No. 14/913,349, dated Jul. 22, 2019, 20 pages. |
| Final Office Action received for U.S. Appl. No. 14/913,349, dated Jul. 30, 2018, 18 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,049, dated Jul. 12, 2018, 24 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,049, dated May 23, 2017, 23 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,052, dated Mar. 1, 2018, 15 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,052, dated May 17, 2017, 13 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,052, dated Oct. 2, 2018, 16 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,058, dated Aug. 8, 2018, 23 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,058, dated May 8, 2017, 21 pages. |
| Final Office Action received for U.S. Appl. No. 15/049,064, dated Feb. 27, 2017, 13 Pages. |
| Final Office Action received for U.S. Appl. No. 16/147,413, dated Sep. 3, 2019, 19 pages. |
| “Headset Button Controller v7.3 APK Full APP Download for Andriod, Blackberry, iPhone”, Jan. 27, 2014, 11 pages. |
| Intention to Grant received for Danish Patent Application No. PA201570781, dated Dec. 8, 2016, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201670117, dated Apr. 21, 2017, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201770794, dated Aug. 15, 2019, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870631, dated Apr. 5, 2019, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870632, dated Apr. 5, 2019, 2 pages. |
| Intention to Grant received for European Patent Application No. 14772001.5, dated Mar. 22, 2019, 17 pages. |
| Intention to Grant received for European Patent Application No. 14772002.3, dated Jun. 24, 2019, 9 pages. |
| Intention to Grant received for European Patent Application No. 18157131.6, dated Jan. 9, 2019, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2012/025519, dated Sep. 12, 2013, 6 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/053951, dated Mar. 17, 2016, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/053957, dated Mar. 17, 2016, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/053958, dated Mar. 17, 2016, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/053961, dated Jul. 21, 2016, 24 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/019320, dated Mar. 16, 2017, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/019321, dated Mar. 16, 2017, 8 Pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/019322, dated Mar. 16, 2017, 11 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/045936, dated Mar. 16, 2017, 9 Pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/045965, dated Dec. 27, 2016, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/047704, dated Mar. 16, 2017, 19 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/019637, dated Sep. 21, 2017, 12 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2012/025519, dated Jun. 11, 2012, 7 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2014/053951, dated Dec. 8, 2014, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2014/053957, dated Feb. 19, 2015, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2014/053958, dated Feb. 19, 2015, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/019320, dated Jul. 2, 2015, 14 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/019321, dated Jun. 3, 2015, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/019322, dated Jun. 18, 2015, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/045936, dated Nov. 4, 2015, 12 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/045965, dated Feb. 1, 2016, 20 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/047704, dated Feb. 22, 2016, 25 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/019637, dated Aug. 18, 2016, 18 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2014/053961, dated Jul. 11, 2016, 10 pages. |
| International Written Opinion received for PCT Patent Application No. PCT/US2014/053961, dated Jul. 11, 2016, 22 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2014/053961, dated Aug. 3, 2015, 6 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/047704, dated Dec. 16, 2015, 10 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2016/019637, dated Jun. 1, 2016, 6 pages. |
| Kamijo, Noboru, “Next Generation Mobile System—WatchPad1.5”, Available at: <http://researcher.ibm.com/researcher/view_group_subpage.php?id=5617>, retrieved on Jul. 4, 2015, 2 pages. |
| NDTV, “Sony SmartWatch 2 Launched in India for Rs. 14,990”, Available at <http://gadgets.ndtv.com/others/news/sony-smartwatch-2-launched-in-india-for-rs-14990-420319>, Sep. 18, 2013, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/874,788, dated Feb. 3, 2009, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/874,788, dated Jul. 27, 2007, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 10/874,788, dated May 14, 2008, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/038,276, dated Jul. 29, 2015, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/038,276, dated Sep. 12, 2013, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,308, dated Dec. 20, 2018, 43 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/641,308, dated Jun. 23, 2017, 53 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/829,573, dated Jan. 22, 2018, 26 Pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/830,629, dated Dec. 1, 2016, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/830,629, dated Jun. 15, 2017, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,912, dated Feb. 12, 2018, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,912, dated Feb. 26, 2019, 36 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,912, dated Jun. 8, 2017, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,914, dated Oct. 19, 2017, 46 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,656, dated Jul. 26, 2017, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/913,345, dated Apr. 5, 2018, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/913,345, dated Jun. 26, 2019, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/913,349, dated Apr. 2, 2019, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/913,349, dated Jan. 11, 2018, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/913,350, dated May 14, 2018, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,049, dated Dec. 15, 2017, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,049, dated Feb. 6, 2019, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,049, dated Nov. 9, 2016, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,052, dated May 31, 2018, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,052, dated Nov. 29, 2016, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,052, dated Sep. 21, 2017, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,058, dated Feb. 20, 2018, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,058, dated Jun. 5, 2019, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,058, dated Nov. 16, 2016, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/049,064, dated Oct. 27, 2016, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/655,253, dated Jul. 10, 2019, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/818,500, dated Aug. 30, 2019, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,950, dated Mar. 6, 2019, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/147,413, dated Feb. 7, 2019, 18 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2014315319, dated Oct. 12, 2017, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2014315324, dated Sep. 28, 2017, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2014315325, dated Apr. 19, 2017, 3 Pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017276285, dated Apr. 3, 2019, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018200289, dated Jul. 23, 2019, 3 pages. |
| Notice of Allowance and Search Report received for Taiwanese Patent Application No. 104128687, dated Jun. 7, 2016, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Notice of Allowance received for Chinese Patent Application No. 201480059543.9, dated Sep. 4, 2019, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201480060044.1, dated Mar. 29, 2019, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201480060082.7, dated Mar. 12, 2019, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Danish Patent Application No. PA201570776, dated Feb. 8, 2017, 2 pages. |
| Notice of Allowance received for Danish Patent Application No. PA201670118, dated Mar. 30, 2017, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-537945, dated Aug. 3, 2018, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2016-537946, dated Mar. 26, 2018, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2016-537947, dated Jun. 5, 2017, 3 pages (Official Copy only). {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Japanese Patent Application No. 2017-545561, dated Jul. 12, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2018-083313, dated Jul. 1, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2018-090084, dated May 24, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2018-143982, dated Apr. 8, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7008449, dated Aug. 9, 2019, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7002695, dated Oct. 8, 2018, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7032106, dated Jun. 28, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 103130517, dated May 14, 2018, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 103130518, dated May 19, 2016, 2 pages (Official Copy only). {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Taiwanese Patent Application No. 103130519, dated Oct. 27, 2016, 3 pages (Official Copy only). {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Taiwanese Patent Application No. 103130520, dated Apr. 25, 2018, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 104107327, dated Jul. 19, 2019, 5 pages (2 pages of English Translation and 3 pages of Official copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 104107333, dated Nov. 8, 2016, 2 pages (Official Copy Only). {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for Taiwanese Patent Application No. 104107334, dated Jan. 26, 2017, 3 pages (Official Copy Only). {See Communication under 37 CFR § 1.98(a) (3)}. |
| Notice of Allowance received for U.S. Appl. No. 10/874,788, dated Mar. 14, 2012, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/038,276, dated Nov. 3, 2016, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/038,276, dated Nov. 30, 2016, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,241, dated Apr. 13, 2017, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,241, dated Jan. 31, 2017, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,241, dated Mar. 24, 2017, 3 Pages. |
| Notice of Allowance received for U.S. Appl. No. 14/641,252, dated Apr. 11, 2018, 14 pages. |
| Notice of Allow Allowance received for U.S. Appl. No. 14/641,252, dated Jul. 18, 2018, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/829,573, dated Apr. 25, 2018, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/830,629, dated Oct. 17, 2018, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,914, dated Jun. 22, 2018, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/841,656, dated Feb. 12, 2018, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/841,656, dated Mar. 5, 2018, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/913,350, dated Dec. 19, 2018, 27 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/049,049, dated Jul. 25, 2019, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/049,064, dated Jul. 18, 2017, 24 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/927,768, dated May 31, 2019, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/055,489, dated Jan. 9, 2019, 24 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/055,489, dated Jan. 25, 2019, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/055,489, dated Nov. 8, 2018, 28 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/109,120, dated Sep. 11 2019, 12 pages. |
| Office Action and Search Report received for Danish Patent Application No. PA201670118, dated Jul. 1, 2016, 7 pages. |
| Office Action received for Danish Patent Application No. PA201770794, dated Dec. 19, 2017, 8 pages. |
| Office Action received for Korean Patent Application No. 10-2018-7010872, dated Dec. 21, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2014315234, dated Apr. 19, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2014315234, dated Jul. 12, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2014315234, dated Nov. 2, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2014315319, dated Aug. 3, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2014315319, dated Oct. 17, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2014315324, dated Aug. 8, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2014315324, dated Oct. 21, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2014315325, dated Nov. 3, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2016229407, dated Aug. 15, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2016229407, dated May 27, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2017254897, dated Aug. 29, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2017254897, dated Jun. 28, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2017276285, dated Nov. 26, 2018, 2 pages. |
| Office Action received for Australian Patent Application No. 2018200289, dated Apr. 9, 2019, 5 pages. |
| Office Action received for Australian Patent Application No. 2018200289, dated Dec. 4, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2018200998, dated Jan. 30, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2018200998, dated Mar. 9, 2018, 5 pages. |
| Office Action received for Australian Patent Application No. 2019201628, dated May 13, 2019, 2 pages. |
| Office Action received for Australian Patent Application No. 2019216614, dated Aug. 22, 2019, 3 pages. |
| Office Action received for Chinese Patent Application No. 201480059543.9, dated Feb. 28, 2019, 16 pages (4 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201480059543.9, dated Jan. 26, 2018, 17 pages (4 pages of English Translation and 13 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201480059543.9, dated Sep. 19, 2018, 18 pages (5 pages of English Translation and 13 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201480060044.1, dated Jan. 26, 2018, 15 pages (5 pages of English translation and 10 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201480060044.1, dated Sep. 25, 2018, 6 pages (3 pages of English translation and 3 pages of official copy). |
| Office Action received for Chinese Patent Application No. 201480060082.7, dated Jan. 26, 2018, 15 pages (4 pages of English translation and 11 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201480060082.7, dated Sep. 25, 2018, 6 pages (3 pages of English Translation and 3 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201480060083.1, dated Aug. 13, 2019, 6 pages (3 pages of English Translation and 3 pages of Offical Copy). |
| Office Action received for Chinese Patent Application No. 201480060083.1, dated Dec. 5, 2018, 11 pages (5 pages of English Translation and 6 pages of Offical Copy). |
| Office Action received for Chinese Patent Application No. 201580046339.8, dated Feb. 26, 2019, 18 pages (6 pages of English Translation and 12 pages of Offical Copy). |
| Office Action received for Danish Patent Application No. PA201570776, dated Aug. 19, 2016, 3 pages. |
| Office Action received for Danish Patent Application No. PA201570776, dated Jan. 26, 2016, 12 pages. |
| Office Action received for Danish Patent Application No. PA201570781, dated Aug. 19, 2016, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670117, dated Jan. 12, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670117, dated Jun. 13, 2016, 10 pages. |
| Office Action received for Danish Patent Application No. PA201670118, dated Feb. 2, 2017, 2 pages. |
| Office Action received for Danish Patent Application No. PA201670118, dated Oct. 25, 2016, 3 Pages. |
| Office Action received for Danish Patent Application No. PA201770181, dated Jan. 3, 2018, 2 Pages. |
| Office Action received for Danish Patent Application No. PA201770181, dated Jun. 13, 2017, 6 pages. |
| Office Action received for Danish Patent Application No. PA201770794, dated Apr. 5, 2018, 4 pages. |
| Office Action received for Danish Patent Application No. PA201770794, dated Jun. 13, 2019, 2 pages. |
| Office Action received for Danish Patent Application No. PA201770794, dated Oct. 30, 2018, 3 pages. |
| Office Action received for European Patent Application No. 14771688.0, dated Jan. 21, 2019, 8 pages. |
| Office Action received for European Patent Application No. 14771688.0, dated May 31, 2018, 6 pages. |
| Office Action received for European Patent Application No. 14771688.0, dated Nov. 30, 2017, 15 pages. |
| Office Action received for European Patent Application No. 14772001.5, dated Feb. 14, 2018, 5 pages. |
| Office Action received for European Patent Application No. 14772001.5, dated May 30, 2017, 10 pages. |
| Office Action received for European Patent Application No. 14772002.3, dated Jul. 4, 2017, 8 pages. |
| Office Action received for European Patent Application No. 14772494.2, dated Jun. 20, 2017, 7 pages. |
| Office Action received for European Patent Application No. 14772494.2, dated Oct. 2, 2018, 9 pages. |
| Office Action received for European Patent Application No. 16710372.0, dated Feb. 22, 2019, 7 pages. |
| Office Action received for European Patent Application No. 18157131.6, dated May 8, 2018, 12 pages. |
| Office Action received for Japanese Patent Application No. 2016-537945, dated Apr. 7, 2017, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-537945, dated Jan. 9, 2018, 5 pages (2 pages of English Translation and 3 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2016-537946, dated Aug. 7, 2017, 8 pages (4 Pages of English Translation and 4 Pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-537946, dated Jan. 30, 2017, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-537947, dated Feb. 24, 2017, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-537948, dated Apr. 6, 2018, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-537948, dated Jun. 9, 2017, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-537948, dated Sep. 3, 2018, 4 pages (2 pages of English Translation and 2 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2017-545561, dated Aug. 6, 2018, 8 pages (4 pages of English Translation and 4 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2018-083313, dated Feb. 12, 2019, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-090084, dated Feb. 15, 2019, 6 pages (3 pages of English Translation and 3 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2018-143982, dated Dec. 7, 2018, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008449, dated Jan. 12, 2017, 15 pages (6 pages of English Translation and 9 pages of official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008449, dated Jan. 16, 2018, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008449, dated Nov. 27, 2017, 6 pages (33 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008474, dated Aug. 6, 2018, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008474, dated Dec. 30, 2016, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008474, dated May 15, 2018, 7 pages (33 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008474, dated Nov. 27, 2017, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008488, dated Feb. 8, 2018, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008488, dated Jan. 12, 2017, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008488, dated Nov. 27, 2017, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008682, dated Dec. 30, 2016, 11 pages (4 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008682, dated Feb. 8, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7008682, dated Nov. 27, 2017, Nov. 27, 2017, 7 pages (3 page of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7024506, dated Aug. 12, 2019, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7024506, dated Sep. 28, 2018, 11 pages (4 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7002695, dated Feb. 27, 2018, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7002695, dated Jun. 19, 2018, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7010872, dated Feb. 13, 2019, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7010872, dated May 21, 2018, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7013265, dated Aug. 10, 2018, 12 pages (5 pages of English Translation and 7 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2018-7013265, dated Jun. 14, 2019, 6 pages (2 pages of English Translation and 4 pages of official copy). |
| Office Action received for Korean Patent Application No. 10-2018-7032106, dated Dec. 26, 2018, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130517, dated Jul. 29, 2016, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130517, dated Feb. 6, 2018, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130517, dated Feb. 22, 2016, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130519, dated Mar. 25, 2016, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130520, dated Apr. 17, 2017, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130520, dated Jan. 23, 2018, 05 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130520, dated May 23, 2016, 38 pages (15 pages of English Translation and 23 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 103130520, dated Oct. 1, 2015, 58 pages (22 pages of English Translation and 36 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 103130520, dated Sep. 29, 2016, 39 pages (16 pages of English Translation and 23 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104107318, dated Dec. 26, 2018, 33 pages (9 pages of English Translation and 24 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104107327, dated Sep. 28, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104107333, dated May 17, 2016, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104107334, dated Sep. 19, 2016, 15 pages (6 pages of English Translation and 9 pages of Official Copy only). |
| Office Action received for Taiwanese Patent Application No. 104128701, dated Jul. 22, 2016, 25 pages (9 pages of English Translation and 16 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104128701, dated Mar. 16, 2017, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Partial European Search Report received for European Patent Application No. 19173371.6, dated Jul. 18, 2019, 17 pages. |
| Partial European Search Report received for European Patent Application No. 19173886.3, dated Jul. 18, 2019, 15 pages. |
| Raghunath, et al, “User Interfaces for Applications on a Wrist Watch”, Journal of Personal and Ubiquitous Computing, vol. 6, 2002, pp. 17-30. |
| Restriction Requirement received for U.S. Appl. No. 10/874,788, dated Nov. 9, 2010, 6 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870631, dated Dec. 6, 2018, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870632, dated Dec. 3, 2018, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970259, dated Jul. 19, 2019, 10 pages. |
| Search Report received for Danish Patent Application No. PA201570781, dated Mar. 8, 2016, 10 pages. |
| Search Report received for European Patent Application No. 18157131.6, dated Apr. 19, 2018, 4 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 14772001.5, dated Nov. 14, 2018, 5 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 14772001.5, dated Oct. 4, 2018, 15 pages. |
| “The interview with a key person. IBM and CITIZEN met and applied Linux to a watch”, ASCII Corporation, vol. 25, No. 12, Dec. 12, 2001, pp. 136-143 (Official Copy only). {See Communication under 37 CFR § 1.98(a) (3)}. |
| The Window Club, “How to Set GIF as Background Windows 7”, Online Available at <https://www.youtube.com/watch?v=tUec42Qd7ng>, Dec. 24, 2012, pp. 1-5. |
| “Watchpad 1.5 demo”, YouTube.com, Online Available at: <https://www.youtube.com/watch?v=7xjvVbeUn80>, Uploaded on Jun. 20, 2010, 2 pages. |
| “WatchPad 1.5”, Online Available at: <http://web.archive.org/web/20011205071448/http://www.tri.ibm.com:80/projects/ngm/index_e.htm>, Dec. 5, 2001, 2 pages. |
| WIKIPEDIA, “Rotary encoder”, Online Available at <https://en.wikipedia.org/wiki/Rotary_encoder>, Retrieved on May 17, 2017, 17 pages (10 pages of English Translation and 7 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/913,345, dated Apr. 13, 2020, 4 pages. |
| Final Office Action received for U.S. Appl. No. 15/818,500, dated Apr. 6, 2020, 15 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7013265, dated Apr. 1, 2020, 4 pages (1 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104107329, dated Mar. 5, 2020, 22 pages (9 pages of English Translation and 13 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 14/641,303, dated Nov. 14, 2019, 4 pages. |
| Advisory Action received for U.S. Appl. No. 14/839,912, dated Nov. 14, 2019, 6 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/913,345, dated Nov. 4, 2019, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/655,253, dated Nov. 12, 2019, 3 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 14/839,912, dated Nov. 5, 2019, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/109,120, dated Nov. 12, 2019, 2 pages. |
| Decision on Appeal received for Korean Patent Application No. 10-2016-7008488, dated Oct. 18, 2019, 33 pages (4 pages of English Translation and 29 pages of Official Copy). |
| Decision to Grant received for Danish Patent Application No. PA201770794, dated Nov. 11, 2019, 2 pages. |
| European Search Report received for European Patent Application No. 19173886.3, dated Oct. 30, 2019, 8 pages. |
| Intention to Grant received for European Patent Application No. 14772002.3, dated Nov. 6, 2019, 9 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-537948, dated Nov. 11. 2019, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7008488, dated Oct. 25, 2019, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 14/752,662, dated Oct. 5, 2018, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/841,646, dated Nov. 21, 2018, 5 pages. |
| Advisory Action received for U.S. Appl. No. 14/868,757, dated Jan. 17, 2019, 5 pages. |
| Decision to Grant received for European Patent Application No. 15782209.9, dated Feb. 14, 2019, 2 pages. |
| Final Office Action received for U.S. Appl. No. 14/752,662, dated Jun. 21, 2018, 15 pages. |
| Final Office Action received for U.S. Appl. No. 14/841,646, dated Aug. 2, 2018, 22 pages. |
| Final Office Action received for U.S. Appl. No. 14/868,757, dated Sep. 20, 2018, 18 pages. |
| Intention to Grant received for European Patent Application No. 15782209.9, dated Sep. 28, 2018, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/038161, dated Mar. 16, 2017, 9 Pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/054310, dated Sep. 14, 2017, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/031064, dated Dec. 14, 2017, 7 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/038161, dated Sep. 4, 2015, 12 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/054310, dated Jan. 20, 2016, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/031064, dated Aug. 8, 2016, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/752,662, dated Dec. 28, 2018, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/752,662, dated Sep. 8, 2017, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,646, dated Dec. 1, 2017, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/868,757, dated Dec. 19, 2017, 17 pages. |
| Notice of Allowance received for Taiwanese Patent Application No. 104133281, dated Mar. 29, 2018, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/841,646, dated Apr. 18, 2019, 7 pages. |
| Office Action received for Danish Patent Application No. PA201570775, dated Aug. 23, 2016, 7 pages. |
| Office Action received for Danish Patent Application No. PA201570775, dated Mar. 21, 2016, 12 pages. |
| Office Action received for Danish Patent Application No. PA201570775, dated Mar. 28, 2017, 3 Pages. |
| Office Action received for Danish Patent Application No. PA201570775, dated Oct. 25, 2017, 3 pages. |
| Office Action received for Taiwanese Patent Application No. 104107330, dated Sep. 17, 2018, 17 pages. |
| Office Action received for Taiwanese Patent Application No. 104133281, dated Mar. 30, 2017, 10 Pages. |
| Office Action received for Taiwanese Patent Application No. 104133281, dated Sep. 1, 2016, 10 pages. |
| Office Action received for Chinese Patent Application No. 201580046339.8, dated Jun. 3, 2020, 19 pages (10 pages of English Translation and 9 pages of Official Copy). |
| Decision to Grant received for European Patent Application No. 14772494.2, dated Jul. 23, 2020, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/263,280, dated Jul. 27, 2020, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/734,173, dated Jul. 23, 2020, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/147,413, dated Jul. 20, 2020, 11 pages. |
| Office Action received for Australian Patent Application No. 2019206101, dated Jul. 14, 2020, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2017-7024506, dated Jul. 8, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2018-7033888, dated Jul. 7, 2020, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/818,500, dated Oct. 13, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/930,300, dated Oct. 27, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/358,483, dated Sep. 28, 2020, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/147,413, dated Sep. 17, 2020, 7 pages. |
| Examiner-Initiated Interview Summary received for U.S. Appl. No. 14/913,349, dated Oct. 27, 2020, 3 pages. |
| Feng, Lipeng, “Bound for computer lovers”, Dec. 31, 2009, 2 pages (Official Copy Only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Intention to Grant received for European Patent Application No. 19199004.3, dated Sep. 14, 2020, 9 pages. |
| Intention to Grant received for Indian Patent Application No. 201617009216, dated Aug. 27, 2020, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/655,253, dated Sep. 10, 2020, 17 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/930,300, dated Aug. 5, 2020, 14 pages. |
| Office Action received for Australian Patent Application No. 2019216614, dated Aug. 13, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2019257521, dated Aug. 7, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2019257521, dated Oct. 21, 2020, 6 pages. |
| Office Action received for Australian Patent Application No. 2019272034, dated Sep. 14, 2020, 4 pages. |
| Office Action received for Chinese Patent Application No. 201680012759.9, dated Jun. 19, 2020, 18 pages (7 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201810074876.9, dated Jul. 31, 2020, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201910164962.3, dated Sep. 18, 2020, 19 pages (6 pages of English Translation and 13 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201910454069.4, dated Jul. 24, 2020, 8 pages (5 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2019-088503, dated Jul. 31, 2020, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7019035, dated Aug. 28, 2020, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7022802, dated on Aug. 28, 2020, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104107329, dated Jul. 24, 2020, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Pedersen, Isabel, “Ready to Wear (or Not) Examining the Rhetorical Impact of Proposed Wearable Devices”, 2013 IEEE International Symposium of Technology and Society (ISTAS) Social Implications of Wearable Computing and Augmediated Reality III Everyday Life, Dec. 31, 2013, pp. 201-202. |
| Rev. Some Culture, “It's super easy for middle-aged and elderly people to learn compute”, Jul. 31, 2013, 2 pages (Official Copy Only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Tong et al., “Discussion About the Influence of Wearable Device on Mobile Operators' Service”, Telecom science, Oct. 31, 2014, pp. 134-142 (Official Copy Only)(See Communication under 37 CFR § 1.98(a)(3)). |
| WZ Science Alliance, “Very simple geriatrics computer and Internet bestselling upgrade”, Sep. 30, 2013, 3 pages (Official Copy Only)(See Communication under 37 CFR § 1.98(a)(3)). |
| Number | Date | Country | |
|---|---|---|---|
| 20190354268 A1 | Nov 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62177001 | Mar 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14841646 | Aug 2015 | US |
| Child | 16525082 | US |
