This relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces that display web pages.
The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has increased significantly in recent years. Exemplary touch-sensitive surfaces include touchpads and touch-screen displays. Such surfaces are widely used to manipulate user interface objects on a display.
Exemplary manipulations include adjusting the position and/or size of one or more user interface objects or activating buttons or opening files/applications represented by user interface objects, as well as associating metadata with one or more user interface objects or otherwise manipulating user interfaces. Exemplary user interface objects include digital images, video, text, icons, control elements such as buttons and other graphics. A user will, in some circumstances, need to perform such manipulations on user interface objects in a file management program (e.g., Finder from Apple Inc. of Cupertino, Calif.), an image management application (e.g., Aperture, iPhoto, Photos from Apple Inc. of Cupertino, Calif.), a digital content (e.g., videos and music) management application (e.g., iTunes from Apple Inc. of Cupertino, Calif.), a drawing application, a presentation application (e.g., Keynote from Apple Inc. of Cupertino, Calif.), a word processing application (e.g., Pages from Apple Inc. of Cupertino, Calif.), a website creation application (e.g., iWeb from Apple Inc. of Cupertino, Calif.), a disk authoring application (e.g., iDVD from Apple Inc. of Cupertino, Calif.), or a spreadsheet application (e.g., Numbers from Apple Inc. of Cupertino, Calif.).
But operations for performing these manipulations are predefined in software applications, and it is difficult to customize (e.g., change) performance of these manipulations, without revising the software applications. For example, a revised software application (e.g., an updated software application) needs to be downloaded and installed to customize (e.g., modify) performance of these manipulations. Thus, providing customized operations for modifying performance of such manipulations is time-consuming and inefficient, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, the present disclosure provides electronic devices with faster, more efficient methods for providing customized processing of touch inputs. Such methods and interfaces optionally complement or replace conventional methods for providing customized processing of touch inputs. Such methods and interfaces provide a more efficient human-machine interface by allowing customized processing of touch inputs. Further, such methods reduce the processing power consumed to process touch inputs, conserve power, reduce unnecessary/extraneous/repetitive inputs, and potentially reduce memory usage. For battery-operated devices, such methods and interfaces conserve battery power and increase the time between battery charges.
The above deficiencies and other problems associated with user interfaces for electronic devices with touch-sensitive surfaces are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, tablet computer, or handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device, such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen” or “touch-screen display”). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and/or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions optionally include image editing, drawing, presenting, word processing, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, note taking, and/or digital video playing. Executable instructions for performing these functions are, optionally, included in a non-transitory computer readable storage medium or other computer program product configured for execution by one or more processors. Alternatively, or in addition, executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface. The method includes: detecting a touch input on the touch-sensitive surface at a first location that corresponds to the displayed portion of a web page on the display, while displaying a user interface that corresponds to at least a portion of the web page on the display, and while detecting the touch input on the touch-sensitive surface, detecting an intensity of the touch input on the touch-sensitive surface, determining whether the intensity of the touch input on the touch-sensitive surface has changed from below a first intensity threshold to above the first intensity threshold, and in response to determining that the intensity of the touch input on the touch-sensitive surface has changed from below the first intensity threshold to above the first intensity threshold, generating a force down event that is distinct from a mouse down event.
In accordance with some embodiments, a method is performed at an electronic device with a display, a touch sensitive surface and one or more sensors that are configured to detect the intensity of inputs on the touch-sensitive surface. The method includes displaying, on the display, a content region including first content that contains an image; and, while displaying the first content in the content region on the display, detecting an input at a location that corresponds to the location of the image on the display. The method also includes, in response to detecting the input: in accordance with a determination that the input includes an intensity above a respective threshold and that the image is associated with a link to second content that is different from the first content, displaying a preview of the second content while maintaining display of at least a portion of the first content in the content region; and, in accordance with a determination that the input includes an intensity above a respective threshold and that the image is not associated with a link to additional content, displaying an enlarged version of the image while maintaining display of at least a portion of the first content in the content region.
In accordance with some embodiments, an electronic device includes a display, a touch-sensitive surface, one or more sensors to detect intensity of contacts with the touch-sensitive surface, one or more processors, memory, and one or more programs; the one or more programs are stored in the memory and configured to be executed by the one or more processors and the one or more programs include instructions for performing or causing performance of the operations of any of the methods described herein. In some embodiments, the electronic device includes one or more sensors to detect signals from a stylus associated with the electronic device. In accordance with some embodiments, a computer readable storage medium (e.g., a non-transitory computer readable storage medium, or alternatively, a transitory computer readable storage medium) has stored therein instructions which when executed by an electronic device with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface, cause the device to perform or cause performance of the operations of any of the methods described herein. In accordance with some embodiments, a graphical user interface on an electronic device with a display, a touch-sensitive surface, one or more sensors to detect intensity of contacts with the touch-sensitive surface, a memory, and one or more processors to execute one or more programs stored in the memory includes one or more of the elements displayed in any of the methods described above, which are updated in response to inputs, as described in any of the methods described herein. In accordance with some embodiments, an electronic device includes: a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface; and means for performing or causing performance of the operations of any of the methods described herein. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display and a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface, includes means for performing or causing performance of the operations of any of the methods described herein.
Thus, electronic devices with displays, touch-sensitive surfaces and one or more sensors to detect intensity of contacts with the touch-sensitive surface are provided with faster, more efficient methods and interfaces for customized processing of touch inputs, thereby increasing the effectiveness and efficiency of such devices, and user satisfaction with such devices. Furthermore, such methods and interfaces reduce processing power, reduce memory usage, reduce battery usage, and/or reduce unnecessary or extraneous or repetitive inputs. Furthermore, such methods and interfaces may complement or replace conventional methods for customized processing of touch inputs.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
Many electronic devices store applications to allow certain manipulations of displayed user interface objects in response to touch inputs. Such applications are hardcoded for predefined operations that define how touch inputs are to be processed. However, instructions included in a document (e.g., JavaScript instructions in a web page) can be used to provide customized operations. For example, instructions in the document can be tailored based on the content of the document (e.g., user interface objects defined in the document) to improve user experience. Because such documents (e.g., web pages) can be readily modified and used without installing them on the electronic devices, instructions included (e.g., embedded) in such documents offer flexibility as to how the content of the documents is delivered to users. However, conventional methods and user interfaces (e.g., those offered by conventional web pages with JavaScript instructions) are inefficient and/or incompatible in allowing operations based on an intensity of a touch input on a touch-sensitive surface. For example, generating a mouse moved event due to a change to the intensity of a touch input on the touch-sensitive surface without the touch input moving across the touch-sensitive surface can generate an error. By providing force events separate from mouse events, the describe methods streamline handling of changes to the intensity of a touch input on the touch-sensitive surface. In addition, because the force events are generated using a separate software module (e.g., a Webkit), instructions included in web pages do not need to define operations performed by the separate software module, thereby simplifying the instructions in the web pages. This also reduces the burden on web developers and facilitates development of web pages that can more efficiently handle changes to the intensity of a touch input on a touch-sensitive surface.
Below,
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. are, in some instances, used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without departing from the scope of the various described embodiments. The first contact and the second contact are both contacts, but they are not the same contact, unless the context clearly indicates otherwise.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch-screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch-screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a note taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU(s) 120 and the peripherals interface 118, is, optionally, controlled by memory controller 122.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU(s) 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
In some embodiments, peripherals interface 118, CPU(s) 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication optionally uses any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch-sensitive display system 112 and other input or control devices 116, with peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled with any (or none) of the following: a keyboard, infrared port, USB port, stylus, and/or a pointer device such as a mouse. The one or more buttons (e.g., 208,
Touch-sensitive display system 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user-interface objects.
Touch-sensitive display system 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic/tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch-sensitive display system 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on touch-sensitive display system 112. In some embodiments, a point of contact between touch-sensitive display system 112 and the user corresponds to a finger of the user or a stylus.
Touch-sensitive display system 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112. In some embodiments, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. of Cupertino, Calif.
Touch-sensitive display system 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen video resolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally makes contact with touch-sensitive display system 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch-sensitive display system 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 163.
Device 100 optionally also includes one or more accelerometers 167, gyroscopes 168, and/or magnetometers 169 (e.g., as part of an inertial measurement unit (IMU)) for obtaining information concerning the position (e.g., attitude) of the device.
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, position module (or set of instructions) 131, graphics module (or set of instructions) 132, haptic feedback module (or set of instructions) 133, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, applications (or sets of instructions) 136, web engine module 175, and one or more web pages 185. Furthermore, in some embodiments, memory 102 stores device/global internal state 157, as shown in
Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. In some embodiments, the external port is a Lightning connector that is the same as, or similar to and/or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif.
Contact/motion module 130 optionally detects contact with touch-sensitive display system 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes software components for performing various operations related to detection of contact (e.g., by a finger or by a stylus), such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts or stylus contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts and/or stylus contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event. Similarly, tap, swipe, drag, and other gestures are optionally detected for a stylus by detecting a particular contact pattern for the stylus.
Position module 131, in conjunction with accelerometers 167, gyroscopes 168, and/or magnetometers 169, optionally detects positional information concerning the device, such as the device's attitude (roll, pitch, and/or yaw) in a particular frame of reference. Position module 130 includes software components for performing various operations related to detecting the position of the device and detecting changes to the position of the device. In some embodiments, position module 131 uses information received from a stylus being used with the device to detect positional information concerning the stylus, such as detecting the positional state of the stylus relative to the device and detecting changes to the positional state of the stylus.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions (e.g., instructions used by haptic feedback controller 161) to produce tactile outputs using tactile output generator(s) 163 at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
Web Engine Module 175 (also called a web browser engine, layout engine, rendering engine, or Webkit) processes marked up content (e.g., HyperText Markup Language (HTML) documents, Extensible Markup Language (XML) documents, etc.). For example, web engine module 175 prepares a layout of the marked up content for display. In some embodiments, web engine module 175 processes instructions included in the marked up content (e.g., JavaScript instructions in web pages 185, etc.). In some embodiments, web engine module 175 is included in operating system 126. In some embodiments, web engine module 175 is integrated with browser module 147.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 includes executable instructions to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers and/or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, Apple Push Notification Service (APNs) or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (in sports devices and smart watches); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.
In conjunction with touch-sensitive display system 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, and/or delete a still image or video from memory 102.
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 includes executable instructions to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch-sensitive display system 112, or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes executable instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on touch screen 112, or on an external display connected wirelessly or via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video.
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display system 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display system 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 167, gyroscope(s) 168, magnetometer(s) 169, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch-sensitive display system 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (i.e., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
As used herein, a force event refers to a device-generated signal or device-generated data (e.g., a signal or a data object generated or updated by device 100) to indicate status or a change in status of a touch input, such as beginning (e.g., satisfying a minimum force intensity threshold), changing intensity (e.g., increasing or decreasing intensity of the touch input), or changing intensity status (e.g., hard press to exceed a high intensity threshold or release the touch input so that the intensity falls below the high intensity threshold) of the touch input. Although force events are associated with physical touches (e.g., touches with a finger and/or a stylus) on the touch-sensitive surface, the force events, as described herein, are distinct from the physical touches.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display system 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display system 112, when a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input-devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
As described above with respect to
In some embodiments, contact/motion module 130 sends event object 194 to one or more applications (e.g., applications 136 in
In some embodiments, the device uses web engine module 175 to process instructions in web page 185 based on information in event object 194. For example, in accordance with a determination that force (or intensity) of a touch input indicated in event object 194 meets predefined criteria, the device uses web engine module 175 to process instructions in web page 185 that corresponds to the force of the touch input indicated in event object 194.
In some embodiments, event object 194 includes force information. In some embodiments, a mouse event object includes force information (e.g., raw or normalized force applied by the touch input). In some embodiments, a touch event object includes force information. In some embodiments, a force event object includes force information.
Device 100 optionally also includes one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch-screen display.
In some embodiments, device 100 includes the touch-screen display, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In some embodiments, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch-sensitive display system 112 and/or one or more tactile output generators 163 for generating tactile outputs for a user of device 100.
Each of the above identified elements in
In some embodiments, the term “tactile output,” discussed above, refers to physical displacement of an accessory (e.g., stylus 203) of a device (e.g., device 100) relative to a previous position of the accessory, physical displacement of a component of an accessory relative to another component of the accessory, or displacement of the component relative to a center of mass of the accessory that will be detected by a user with the user's sense of touch. For example, in situations where the accessory or the component of the accessory 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 accessory or the component of the accessory. For example, movement of a component (e.g., the housing of stylus 203) is, optionally, interpreted by the user as a “click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as a “click” even when there is no movement of a physical actuator button associated with the stylus that is physically pressed (e.g., displaced) by the user's movements. 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., a “click,”), 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 stylus 203 is only one example of an electronic stylus, and that stylus 203 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 402 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more flash memory devices, or other non-volatile solid-state memory devices. Access to memory 402 by other components of stylus 203, such as CPU(s) 420 and the peripherals interface 418, is, optionally, controlled by memory controller 422.
Peripherals interface 418 can be used to couple input and output peripherals of the stylus to CPU(s) 420 and memory 402. The one or more processors 420 run or execute various software programs and/or sets of instructions stored in memory 402 to perform various functions for stylus 203 and to process data.
In some embodiments, peripherals interface 418, CPU(s) 420, and memory controller 422 are, optionally, implemented on a single chip, such as chip 404. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 408 receives and sends RF signals, also called electromagnetic signals. RF circuitry 408 converts electrical signals to/from electromagnetic signals and communicates with device 100 or 300, communications networks, and/or other communications devices via the electromagnetic signals. RF circuitry 408 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 408 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication optionally uses any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
I/O subsystem 406 couples input/output peripherals on stylus 203, such as other input or control devices 416, with peripherals interface 418. I/O subsystem 406 optionally includes optical sensor controller 458, intensity sensor controller 459, haptic feedback controller 461, and one or more input controllers 460 for other input or control devices. The one or more input controllers 460 receive/send electrical signals from/to other input or control devices 416. The other input or control devices 416 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, click wheels, and so forth. In some alternate embodiments, input controller(s) 460 are, optionally, coupled with any (or none) of the following: an infrared port and/or a USB port.
Stylus 203 also includes power system 462 for powering the various components. Power system 462 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices and/or portable accessories.
Stylus 203 optionally also includes one or more optical sensors 464.
Stylus 203 optionally also includes one or more contact intensity sensors 465.
Stylus 203 optionally also includes one or more proximity sensors 466.
Stylus 203 optionally also includes one or more tactile output generators 463.
Stylus 203 optionally also includes one or more accelerometers 467, gyroscopes 468, and/or magnetometers 470 (e.g., as part of an inertial measurement unit (IMU)) for obtaining information concerning the location and positional state of stylus 203.
In some embodiments, the software components stored in memory 402 include operating system 426, communication module (or set of instructions) 428, contact/motion module (or set of instructions) 430, position module (or set of instructions) 431, and Global Positioning System (GPS) module (or set of instructions) 435. Furthermore, in some embodiments, memory 402 stores device/global internal state 457, as shown in
Operating system 426 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 428 optionally facilitates communication with other devices over one or more external ports 424 and also includes various software components for handling data received by RF circuitry 408 and/or external port 424. External port 424 (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 Lightning connector that is the same as, or similar to and/or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif.
Contact/motion module 430 optionally detects contact with stylus 203 and other touch-sensitive devices of stylus 203 (e.g., buttons or other touch-sensitive components of stylus 203). Contact/motion module 430 includes software components for performing various operations related to detection of contact (e.g., detection of a tip of the stylus with a touch-sensitive display, such as touch screen 112 of device 100, or with another surface, such as a desk surface), such as determining if contact has occurred (e.g., detecting a touch-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 (e.g., across touch screen 112 of device 100), and determining if the contact has ceased (e.g., detecting a lift-off event or a break in contact). In some embodiments, contact/motion module 430 receives contact data from I/O subsystem 406. 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. As noted above, in some embodiments, one or more of these operations related to detection of contact are performed by the device using contact/motion module 130 (in addition to or in place of the stylus using contact/motion module 430).
Contact/motion module 430 optionally detects a gesture input by stylus 203. Different gestures with stylus 203 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 single tap gesture includes detecting a touch-down event followed by detecting a lift-off event at the same position (or substantially the same position) as the touch-down event (e.g., at the position of an icon). As another example, detecting a swipe gesture includes detecting a touch-down event followed by detecting one or more stylus-dragging events, and subsequently followed by detecting a lift-off event. As noted above, in some embodiments, gesture detection is performed by the device using contact/motion module 130 (in addition to or in place of the stylus using contact/motion module 430).
Position module 431, in conjunction with accelerometers 467, gyroscopes 468, and/or magnetometers 469, optionally detects positional information concerning the stylus, such as the stylus's attitude (roll, pitch, and/or yaw) in a particular frame of reference. Position module 431, in conjunction with accelerometers 467, gyroscopes 468, and/or magnetometers 469, optionally detects stylus movement gestures, such as flicks, taps, and rolls of the stylus. Position module 431 includes software components for performing various operations related to detecting the position of the stylus and detecting changes to the position of the stylus in a particular frame of reference. In some embodiments, position module 431 detects the positional state of the stylus relative to the device and detects changes to the positional state of the stylus relative to the device. As noted above, in some embodiments, device 100 or 300 determines the positional state of the stylus relative to the device and changes to the positional state of the stylus using position module 131 (in addition to or in place of the stylus using position module 431).
Haptic feedback module 433 includes various software components for generating instructions used by tactile output generator(s) 463 to produce tactile outputs at one or more locations on stylus 203 in response to user interactions with stylus 203.
GPS module 435 determines the location of the stylus and provides this information for use in various applications (e.g., to applications that provide location-based services such as an application to find missing devices and/or accessories).
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 402 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 402 optionally stores additional modules and data structures not described above.
Further,
In some embodiments, an indication (e.g., indication 516) is displayed on a touch-sensitive display (e.g., touch screen 112 of device 100). In some embodiments, indication 516 shows where the stylus will touch (or mark) the touch-sensitive display before the stylus touches the touch-sensitive display. In some embodiments, indication 516 is a portion of a mark that is being drawn on the touch-sensitive display. In some embodiments, indication 516 is separate from a mark that is being drawn on the touch-sensitive display and corresponds to a virtual “pen tip” or other element that indicates where a mark will be drawn on the touch-sensitive display.
In some embodiments, indication 516 is displayed in accordance with the positional state of stylus 203. For example, in some circumstances, indication 516 is displaced from (x,y) position 504 (as shown in
Further,
Although the terms, “x axis,” “y axis,” and “z axis,” are used herein to illustrate certain directions in particular figures, it will be understood that these terms do not refer to absolute directions. In other words, an “x axis” could be any respective axis, and a “y axis” could be a particular axis that is distinct from the x axis. Typically, the x axis is perpendicular to the y axis. Similarly, a “z axis” is distinct from the “x axis” and the “y axis,” and is typically perpendicular to both the “x axis” and the “y axis.”
Further,
Attention is now directed towards embodiments of user interfaces (“UI”) that are, optionally, implemented on portable multifunction device 100.
It should be noted that the icon labels illustrated in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures, etc.), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a stylus input).
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector,” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact or a stylus contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average or a sum) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be readily accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
In some embodiments, contact/motion module 130 and/or 430 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch-screen display can be set to any of a large range of predefined thresholds values without changing the trackpad or touch-screen display hardware. Additionally, in some embodiments, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds may include a low intensity threshold and a high intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the low intensity threshold results in a first operation, a contact with a characteristic intensity that exceeds the low intensity threshold and does not exceed the high intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the high intensity threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more intensity thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective option or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location (e.g., a drag gesture), at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm may be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The user interface figures (e.g.,
In some embodiments, the response of the device to inputs detected by the device depends on criteria based on the contact intensity during the input. For example, for some “light press” inputs, the intensity of a contact exceeding a low intensity threshold during the input triggers a first response. In some embodiments, the response of the device to inputs detected by the device depends on criteria that include both the contact intensity during the input and time-based criteria. For example, for some “deep press” inputs, the intensity of a contact exceeding a high intensity threshold during the input, greater than the low intensity threshold for a light press, triggers a second response only if a delay time has elapsed between meeting the low intensity threshold and meeting the high intensity threshold. This delay time is typically less than 200 ms in duration (e.g., 40, 100, or 120 ms, depending on the magnitude of the high intensity threshold, with the delay time increasing as the high intensity threshold increases). This delay time helps to avoid accidental deep press inputs. As another example, for some “deep press” inputs, there is a reduced-sensitivity time period that occurs after the time at which the low intensity threshold is met. During the reduced-sensitivity time period, the high intensity threshold is increased. This temporary increase in the high intensity threshold also helps to avoid accidental deep press inputs. For other deep press inputs, the response to detection of a deep press input does not depend on time-based criteria.
In some embodiments, one or more of the input intensity thresholds and/or the corresponding outputs vary based on one or more factors, such as user settings, contact motion, input timing, application running, rate at which the intensity is applied, number of concurrent inputs, user history, environmental factors (e.g., ambient noise), focus selector position, and the like. Exemplary factors are described in U.S. patent application Ser. Nos. 14/399,606 and 14/624,296, which are incorporated by reference herein in their entireties.
For example,
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold IL to an intensity between the light press intensity threshold IL and the deep press intensity threshold IH 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 IH to an intensity above the deep press intensity threshold IH is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold IT0 to an intensity between the contact-detection intensity threshold IT0 and the light press intensity threshold IL is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold IT0 to an intensity below the contact-detection intensity threshold IT0 is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments IT0 is zero. In some embodiments, IT0 is greater than zero. In some illustrations a shaded circle or oval is used to represent intensity of a contact on the touch-sensitive surface. In some illustrations, a circle or oval without shading is used represent a respective contact on the touch-sensitive surface without specifying the intensity of the respective contact.
In some embodiments, described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., the respective operation is performed on a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., the respective operation is performed on an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., the respective operation is performed on an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the description of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold. As described above, in some embodiments, the triggering of these responses also depends on time-based criteria being met (e.g., a delay time has elapsed between a low intensity threshold being met and a high intensity threshold being met).
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on an electronic device, such as portable multifunction device 100 or device 300, with a display, a touch-sensitive surface, and one or more sensors to detect intensity of contacts with the touch-sensitive surface.
In
Intensity diagram 730 in
Intensity diagram 730 in
In
In some embodiments, when the web browser or the web page includes instructions for handling the force down event, the device processes the force down event in accordance with the instructions for handling the force down event in the web browser or the web page (e.g., displaying region 708 in accordance with instructions for handling the force down event in the web page).
In
Intensity diagram 730 in
In some embodiments, when the web browser or the web page includes instructions for handling the force up event, the device processes the force up event in accordance with the instructions for handling the force up event in the web browser or the web page (e.g., visually distinguishing display region 708 in accordance with instructions in the web page for handling the force up event, or alternatively, ceasing to display region 708 in accordance with instructions in the web page for handling the force up event).
In
Intensity diagram 730 in
Intensity diagram 730 in
In
Intensity diagram 730 in
In some embodiments, a size of popup view 710 increases with the intensity applied by touch input 711 on touch-sensitive surface 651 until the intensity reaches the high intensity threshold IH. In some embodiments, in response to the intensity applied by touch input 711 on touch-sensitive surface 651 reaching the high intensity threshold IH (or the intensity applied by touch input 711 changing from below the high intensity threshold IH to above the high intensity threshold IH), popup view 710 is “locked” on display 650. For example, after the intensity applied by touch input 711 on touch-sensitive surface 651 reaching the high intensity threshold IH, popup view 710 remains on display 650 at the same size independent of a subsequent decrease of the intensity applied by touch input 711 on touch-sensitive surface 651 below the high intensity threshold IH.
In
In
In
Intensity diagram 730 in
In
In some embodiments, both the web browser and the web page include instructions for processing a force event of a same type (e.g., a force changed event, a force down event, or a force up event). In some embodiments, the device forgoes processing a force event in accordance with instructions in the web browser for processing the force event and processes the force event in accordance with instructions in the web page for processing the force event. More specifically, in some embodiments, the device disables execution of a set of instructions included in the web browser (e.g., the aforementioned instructions for processing one or more particular types of force event) in response to the will begin event. For example, in response to the will begin event, instructions in the web page that disable default processing of the one or more particular types of force events are executed. In some embodiments, disabling the default processing of the one or more particular types of force events is accomplished by executing a predefined method or function call provided by the web browser, which is invoked by instructions in the web page in response to the will begin event.
In some embodiments, instructions in the web page that correspond to certain force events (e.g., a force changed event, a force down event, and/or a force up event) are processed only if default processing of such force events is disabled, because if default processing of such force events is not disabled, such force events can be handled by the default operations (e.g., based on instructions for default operations in the web browser).
Intensity diagram 730 in
An overlap of force changed event 788 and mouse moved event 790 indicates movement of touch input 711 across touch-sensitive surface 651 while changing (e.g., increasing) the intensity applied by touch input 711 on touch-sensitive surface 651.
Mouse moved event 792 in
Force changed event 794 (without an associated mouse moved event) in
Mouse up event 796 in
Thus, by using a mouse event and a separate force event, locations changes of a touch input and intensity changes to the touch input can be tracked independently. This simplifies processing changes to touch inputs, thereby improving the efficiency of the device. In addition, this reduces potential errors in processing instructions in certain web pages (e.g., legacy web pages) that are not configured to handle force events. For example, if the device generates a mouse moved event in response to a change to the intensity applied by a touch input on touch-sensitive surface 651 and if the web page includes instructions to divide a certain number with a travel distance associated with the touch input, a change to the intensity applied by a touch input on touch-sensitive surface 651 without a movement of the touch input across touch-sensitive surface 651 (e.g., zero travel distance) would potentially generate a “division by zero” error. By separating mouse events and force events, a change to the intensity applied by a touch input on touch-sensitive surface 651 without a movement of the touch input across touch-sensitive surface 651 would generate a force event (e.g., a force changed event) without a mouse moved event, and the “division by zero” error can be avoided.
In
Although
As described below, method 800 provides an enhanced way to process touch inputs with instructions in a web page. Method 800 improves efficiency in processing touch inputs with instructions in a web page. In addition, method 800 improves compatibility in processing touch inputs with instructions in legacy web pages.
While displaying a user interface that corresponds to at least a portion of a web page on the display, the device detects (802) a touch input on the touch-sensitive surface at a first location that corresponds to the displayed portion of the web page on the display. For example, as shown in
In some embodiments, while detecting the touch input on the touch-sensitive surface, the device receives (804) an input that corresponds to a request to generate a mouse down event (e.g., clicking on a mouse button, providing a touch input on the touch-sensitive surface with sufficient intensity, etc.), and in response to receiving the input that corresponds to a request to generate a mouse down event, generates the mouse down event. For example, in
In some embodiments, while detecting the touch input on the touch-sensitive surface (and, in some embodiments, prior to detecting the intensity of the touch input that has changed from below the first intensity threshold to above the first intensity threshold), the device detects (806) an intensity of the touch input on the touch-sensitive surface (e.g., with the one or more sensors configured to detect intensity of contacts on the touch-sensitive surface), and determines whether the intensity of the touch input on the touch-sensitive surface has changed from below a second intensity threshold that is distinct from the first intensity threshold to above the second intensity threshold. In response to determining that the intensity of the touch input on the touch-sensitive surface has changed from below the second intensity threshold to above the second intensity threshold, the device generates a mouse down event. For example, in
In some embodiments, the second intensity threshold is higher than a detection intensity threshold. In some embodiments, the device processes instructions in the web page (e.g., instructions that correspond to a mouse moved event), distinct and separate from instructions in the web page that correspond to a mouse down event and instructions in the web page that correspond to a force down event, at least in response to determining that the intensity of the touch input on the touch-sensitive surface satisfies the detection intensity threshold (e.g., a mouse moved event generated in response to a movement of the touch input across the touch-sensitive surface while the intensity applied by the touch input satisfies the detection intensity threshold).
The device detects (808) an intensity of the touch input on the touch-sensitive surface (e.g., with the one or more sensors). In some embodiments, the intensity of the touch input on the touch-sensitive surface is detected subsequent to generating a mouse down event (e.g., operations 804 and/or 808). The device determines (810) whether the intensity of the touch input on the touch-sensitive surface has changed from below a first intensity threshold to above the first intensity threshold. In some embodiments, the first intensity threshold is higher than the second intensity threshold. In response to determining that the intensity of the touch input on the touch-sensitive surface has changed from below the first intensity threshold to above the first intensity threshold, the device generates (812) a force down event that is distinct from a mouse down event. For example,
In some embodiments, while detecting the touch input on the touch-sensitive surface, and in response to determining that the intensity of the touch input on the touch-sensitive surface has changed from below the first intensity threshold to above the first intensity threshold, the device processes (814,
In some embodiments, while detecting the touch input on the touch-sensitive surface, and subsequent to determining that the intensity of the touch input on the touch-sensitive surface has changed from below the first intensity threshold to above the first intensity threshold, the device determines whether the intensity of the touch input on the touch-sensitive surface has changed from above a third intensity threshold (e.g., a release threshold) to below the third intensity threshold. In response to determining that the intensity of the touch input on the touch-sensitive surface has changed from above the third intensity threshold to below the third intensity threshold, the device generates a force up event that is distinct from the force down event. For example, in
In some embodiments, the third intensity threshold is identical to the first intensity threshold (e.g., in
In some embodiments, while detecting the touch input on the touch-sensitive surface, subsequent to determining that the intensity of the touch input on the touch-sensitive surface has changed from above the third intensity threshold to below the third intensity threshold, the device determines whether the intensity of the touch input on the touch-sensitive surface has changed from above a fourth intensity threshold (e.g., a mouse release threshold) to below the fourth intensity threshold, and in response to determining that the intensity of the touch input on the touch-sensitive surface has changed from above the fourth intensity threshold to below the fourth intensity threshold, generating a mouse up event that is distinct from the force up event. For example, as shown in
In some embodiments, while detecting the touch input on the touch-sensitive surface, the device determines (818) whether the intensity of the touch input on the touch-sensitive surface has changed, and in response to determining that the intensity of the touch input on the touch-sensitive surface has changed, generates a force changed event. For example, in
In some embodiments, the device also determines whether the intensity of the touch input on the touch-sensitive surface has changed without crossing over the first intensity threshold or the second intensity threshold, and in response to determining that the intensity of the touch input on the touch-sensitive surface has changed without crossing over the first intensity threshold or the second intensity threshold, the device generates the force changed event. In some embodiments, the device determines that the intensity of the touch input on the touch-sensitive surface has crossed over the first intensity threshold or the second intensity threshold, and in response, generates a mouse down event, a force down event, a force up event, or a mouse up event without generating a force changed event.
In some embodiments, the intensity of the touch input on the touch-sensitive surface must be detected to change by a predetermined amount before the device generates the force changed event (e.g., the change in the intensity of the touch input needs to be more than the predetermined amount to trigger a force changed event). In some embodiments, force changed events are generated in accordance with a predetermined time interval (e.g., force changed events are generated no more frequent than the predetermined time interval).
In some embodiments, while detecting the touch input on the touch-sensitive surface, in response to determining that the intensity of the touch input on the touch-sensitive surface has changed and determining that the touch input has not moved across the touch-sensitive surface, the device generates (820) the force changed event without generating a mouse moved event. For example, in
In some embodiments, the force changed event is generated subsequent to determining that the intensity of the touch input on the touch-sensitive surface has changed from below the second intensity threshold to above the second intensity threshold and before determining that the intensity of the touch input on the touch-sensitive surface has changed from above the fourth intensity threshold to below the fourth intensity threshold. For example, in
In some embodiments, while detecting the touch input on the touch-sensitive surface, and in response to detecting an input that includes movement of the touch input and a change in intensity of the touch input on the touch-sensitive surface, the device generates (822) one or more mouse moved events that correspond to the touch input and generates one or more force changed events that correspond to the touch input. The one or more force changed events are separate from the one or more mouse moved events.
In some embodiments, the device provides the one or more force changed events (and optionally, the one or more mouse moved events) to a website that corresponds to the displayed web page. In some embodiments, in accordance with a determination that the website is not configured to accept force changed events, the one or more mouse moved events are provided to the website without the one or more force changed events. In accordance with a determination that the website is configured to accept force changed events, the one or more mouse moved events are provided to the website along with the one or more force changed events.
In some embodiments, while detecting the touch input on the touch-sensitive surface, in response to determining that force event will begin criteria are satisfied, the device generates (824,
In some embodiments, the device is configured to perform default operations in accordance with an intensity of the touch input satisfying and further exceeding the will begin intensity threshold (e.g., a touch input that satisfies a force event preview threshold at which a preview of a force-based operation that will be performed when the intensity of the touch input reaches the first intensity threshold, where the force event preview intensity threshold is greater than the will begin intensity threshold). The will begin event can be used to prevent the default operations (e.g., default operations that depend on the intensity of the touch input), and optionally, initiate custom operations defined in the web page (e.g., display of a map as shown in
In some embodiments, a combination of the mouse down event and the force will begin event is used to determine that the device includes one or more sensors to detect intensity of contacts with the touch-sensitive surface (compared to legacy devices that do not include one or more sensors to detect intensity of contacts with the touch-sensitive surface). For example, a device that does not include one or more sensors to detect intensity of contacts with the touch-sensitive surface does not generate a force will begin event. In some embodiments, in response to determining that the device does not include one or more sensors to detect intensity of contacts with the touch-sensitive surface (e.g., based on the absence of the force will begin event), the device forgoes processing instructions that correspond to respective force events. In some embodiments, a device that includes one or more sensors to detect intensity of contacts with the touch-sensitive surface generates a force will begin event in temporal proximity to generating a mouse down event (e.g., concurrent generation as shown in
In some embodiments, while detecting the touch input on the touch-sensitive surface, and in response to determining that force event preview criteria are satisfied: in accordance with a determination that the web page does not include instructions that correspond to the will begin event, the device processes (826) the touch input in accordance with (e.g., default) instructions in the first application (e.g., a software component configured to rendering web pages, such as Web Engine Module 175 in
In some embodiments, in accordance with a determination that the web page includes instructions that correspond to the will begin event, the device forgoes processing the touch input in accordance with (e.g., default) instructions in the first application (e.g., a software component configured to rendering web pages, such as Web Engine Module 175 in
In some embodiments, processing the touch input in accordance with instructions in the web page is conditioned on a setting in the web page. For example, the web page includes instructions to define a property (e.g., “prevent default operations” property) and sets the property to either prevent default operations or allow default operations. In accordance with the setting of the property, the device conditionally processes the touch input in accordance with instructions in the web page (e.g., if the property is set to prevent default operations) or in accordance with default instructions (e.g., if the property is set to allow default operations). In some embodiments, the property is associated with a respective user interface object. For example, a first user interface object is associated with a property that is set to prevent default operations and a second user interface object is associated with a property that is set to allow default operations. In some embodiments, the property is adjusted while the device processes the touch input (or while the device processes the instructions in the web page). For example, the property is initially set to allow default operations, and in accordance with instructions in the web page, subsequently set to prevent default operations. Alternatively, the property is initially set to prevent default operations, and in accordance with instructions in the web page, subsequently set to allow default operations.
In some embodiments, the instructions in the web page that correspond to the force down event are processed (828) using a first application (e.g., a software component configured to rendering web pages, such as Web Engine Module 175 in
In some embodiments, the tactile output that corresponds to the force down event (e.g., force down event 770,
In some embodiments, the device generates a tactile output that corresponds to the force up event using the tactile output module (e.g., Haptic Feedback Module 133) that is distinct and separate from the first application (e.g., Web Engine Module 175). In some embodiments, the tactile output that corresponds to the force up event is generated using the tactile output module without sending instructions from the first application to the tactile output module. In some embodiments, the tactile output module generates the tactile output based on the intensity determined by the one or more sensors.
In some embodiments, the force down and force up events are generated by a software component other than the first application (e.g., contact/motion module 130) and provided to the first application (e.g., Web Engine Module 175) so that the first application updates the user interface in coordination with the tactile output to be generated by the tactile output module when the touch input reaches the triggering intensity threshold. In this example, the tactile output is not generated in response the force down event (because the force down event is not sent to the tactile output module), rather, the force down event is provided to the first application to generate a visual or audible output in conjunction with the tactile output (if it is configured to do so). The tactile outputs are generated in response to signals or instructions, other than force down events or force up events.
In some embodiments, the first location on the touch-sensitive surface corresponds (830) to a first user interface object. The instructions in the web page that correspond to the mouse down event correspond to the first user interface object, and the instructions in the web page that correspond to the force down event correspond to the first user interface object. For example, instructions in the web page are configured to operate with respect to respective user interface objects (e.g., a first set of instructions for a force down event is configured for processing a force down event that corresponds to a first user interface object and a second set of instructions for a force down event is configured for processing a force down event that corresponds to a second user interface object).
In some embodiments, the web page defines a plurality of user interface objects and includes a plurality of sets of instructions that correspond to a force down event. Respective sets of instructions correspond to a force down event for respective user interface objects. For example, the web page includes (i) information defining the first user interface object and a second user interface object and (ii) instructions that correspond to a force down event for the first user interface object and instructions that correspond to a force down event for the second user interface object. Similarly, the web page may include location-specific or user-interface-object-specific instructions that correspond to events of different types (e.g., force up event, force changed event, and will begin event). In some embodiments, the web page includes (i) information defining the first user interface object and the second user interface object and (ii) instructions that correspond to a will begin event for the first user interface object and instructions that correspond to a will begin event for the second user interface object.
It should be understood that the particular order in which the operations in
Additionally, it should be noted that details of other processes described herein with respect to other methods described herein (e.g., method 900) are also applicable in an analogous manner to method 800 described above with respect to
As described below, method 900 provides an enhanced way to process touch inputs based on displayed content. Method 900 improves efficiency in accessing information associated with web pages. For example, by providing an enlarged image in response to a touch input on an image when the image is not associated with a linked content (e.g., not associated with a hyperlink) and providing a preview of the linked content in response to a touch input on an image when the image is associated with the linked content (e.g., associated with a hyperlink), method 900 provides additional information (be it an enlarged image or a preview of a linked content) associated with the image, thereby facilitating use of the information on the web page. In some circumstances, efficiency is increased because the additional information (e.g., preview of the linked content) enables the user to avoid selecting content (and thus switching to a new context corresponding to that content) not of current interest to the user, and to concentrate the user's efforts on other content more directly of current interest to the user.
The device displays (902), on the display, a content region including first content that contains an image (e.g., the web page with image 704, as shown in
In some embodiments, the content region is (904) a content region of a web browser. The first content is a first web page. The image is an image in the first web page. For example, the user interface shown in
While displaying the first content in the content region on the display, the device detects (906) an input at a location that corresponds to the location of the image on the display (e.g., touch input 707 on touch-sensitive surface 651 while focus selector 706 is positioned over image 704, or a touch input on display 650 over image 704 when display 650 is a touch-sensitive display).
In response to detecting the input, the device, in accordance with a determination that the input includes an intensity above a respective threshold and that the image is associated with a link to second content that is different from the first content, displays (908) a preview of the second content while maintaining display of at least a portion of the first content in the content region. For example, in
In some embodiments, the second content is (910) a second web page. The link to the second content is a hyperlink to the second web page that is associated with the image. For example, in
In accordance with a determination that the input includes an intensity above the respective threshold and that the image is not associated with a link to additional content, the device displays (912) an enlarged version of the image while maintaining display of at least a portion of the first content in the content region. For example, in
In some embodiments, displaying the preview of the second content includes (914) enlarging the image as the intensity of the input increases (e.g., display region 708 and the image in display region 708 enlarge as the intensity of touch input 707 increases, as shown in
In some embodiments, the device, in response to detecting the input and in accordance with a determination that the input does not include an intensity above the respective threshold and that the image is associated with a link to the second content, replaces (916) display of the first content in the content region with the second content. For example, as shown in
In some embodiments, the device, in response to detecting the input and in accordance with a determination that the input does not include an intensity above the respective threshold and that the image is not associated with a link to additional content, maintains (918) display of the first content in the content region. For example, display of the web page remains on the display, as shown in
It should be understood that the particular order in which the operations in
The operations in the information processing methods described above are, optionally implemented by running one or more functional modules in information processing apparatus such as general purpose processors (e.g., as described above with respect to
The 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 invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated.
This application claims priority to U.S. Provisional Application Ser. No. 62/184,816, filed Jun. 25, 2015, entitled “Devices and Methods for Processing Touch Inputs with Instructions in a Web Page,” and U.S. Provisional Application Ser. No. 62/172,187, filed Jun. 7, 2015, entitled “Devices and Methods for Processing Touch Inputs with Instructions in a Web Page” both of which are incorporated by reference herein in their entireties. This application relates to U.S. Provisional Application Ser. No. 62/129,954, filed Mar. 8, 2015, and U.S. Provisional Application Ser. No. 62/183,139, filed Jun. 22, 2015, both of which are incorporated by reference herein in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
5374787 | Miller et al. | Dec 1994 | A |
5463722 | Venolia | Oct 1995 | A |
5510813 | Makinwa | Apr 1996 | A |
5555354 | Strasnick et al. | Sep 1996 | A |
5559301 | Bryan, Jr. et al. | Sep 1996 | A |
5710896 | Seidl | Jan 1998 | A |
5793360 | Fleck | Aug 1998 | A |
5793377 | Moore | Aug 1998 | A |
5801692 | Muzio et al. | Sep 1998 | A |
5805144 | Scholder et al. | Sep 1998 | A |
5809267 | Moran et al. | Sep 1998 | A |
5825352 | Bisset et al. | Oct 1998 | A |
5844560 | Crutcher et al. | Dec 1998 | A |
5872922 | Hogan et al. | Feb 1999 | A |
5946647 | Miller et al. | Aug 1999 | A |
6002397 | Jaaskelainen, Jr. | Dec 1999 | A |
6031989 | Cordell | Feb 2000 | A |
6088019 | Rosenberg | Jul 2000 | A |
6088027 | Konar et al. | Jul 2000 | A |
6111575 | Martinez et al. | Aug 2000 | A |
6208329 | Ballare | Mar 2001 | B1 |
6208340 | Amin et al. | Mar 2001 | B1 |
6219034 | Elbing et al. | Apr 2001 | B1 |
6243080 | Molne | Jun 2001 | B1 |
6252594 | Xia et al. | Jun 2001 | B1 |
6396523 | Segal et al. | May 2002 | B1 |
6429846 | Rosenberg et al. | Aug 2002 | B2 |
6448977 | Braun et al. | Sep 2002 | B1 |
6459442 | Edwards et al. | Oct 2002 | B1 |
6563487 | Martin et al. | May 2003 | B2 |
6567102 | Kung | May 2003 | B2 |
6583798 | Hoek et al. | Jun 2003 | B1 |
6590568 | Astala et al. | Jul 2003 | B1 |
6661438 | Shiraishi et al. | Dec 2003 | B1 |
6735307 | Volckers | May 2004 | B1 |
6750890 | Sugimoto | Jun 2004 | B1 |
6822635 | Shahoian et al. | Nov 2004 | B2 |
6919927 | Hyodo | Jul 2005 | B1 |
7138983 | Wakai et al. | Nov 2006 | B2 |
7312791 | Hoshino et al. | Dec 2007 | B2 |
7411575 | Hill et al. | Aug 2008 | B2 |
7479949 | Jobs et al. | Jan 2009 | B2 |
7533352 | Chew et al. | May 2009 | B2 |
7577530 | Vignalou-Marche | Aug 2009 | B2 |
7614008 | Ording | Nov 2009 | B2 |
7619616 | Rimas Ribikauskas et al. | Nov 2009 | B2 |
7656413 | Khan et al. | Feb 2010 | B2 |
7683889 | Ribikauskas et al. | Mar 2010 | B2 |
7743348 | Robbins et al. | Jun 2010 | B2 |
7760187 | Kennedy | Jul 2010 | B2 |
7787026 | Flory et al. | Aug 2010 | B1 |
7797642 | Karam et al. | Sep 2010 | B1 |
7801950 | Eisenstadt et al. | Sep 2010 | B2 |
7812826 | Ording et al. | Oct 2010 | B2 |
7890862 | Kompe et al. | Feb 2011 | B2 |
7903090 | Soss et al. | Mar 2011 | B2 |
7952566 | Poupyrev et al. | May 2011 | B2 |
7956847 | Christie | Jun 2011 | B2 |
7973778 | Chen | Jul 2011 | B2 |
8040142 | Bokma | Oct 2011 | B1 |
8106856 | Matas et al. | Jan 2012 | B2 |
8125440 | Guyot-Sionnest | Feb 2012 | B2 |
RE43448 | Kimoto et al. | Jun 2012 | E |
8209628 | Davidson | Jun 2012 | B1 |
8363020 | Li et al. | Jan 2013 | B2 |
8390583 | Forutanpour et al. | Mar 2013 | B2 |
8423089 | Song et al. | Apr 2013 | B2 |
8446376 | Levy et al. | May 2013 | B2 |
8456431 | Victor | Jun 2013 | B2 |
8466889 | Tong et al. | Jun 2013 | B2 |
8508494 | Moore | Aug 2013 | B2 |
8542205 | Keller | Sep 2013 | B1 |
8581870 | Bokma et al. | Nov 2013 | B2 |
8587542 | Moore | Nov 2013 | B2 |
8593415 | Han et al. | Nov 2013 | B2 |
8625882 | Backlund et al. | Jan 2014 | B2 |
8638311 | Kang | Jan 2014 | B2 |
8665227 | Gunawan | Mar 2014 | B2 |
8669945 | Coddington | Mar 2014 | B2 |
8698765 | Keller | Apr 2014 | B1 |
8717305 | Williamson | May 2014 | B2 |
8743069 | Morton et al. | Jun 2014 | B2 |
8773389 | Freed | Jul 2014 | B1 |
8793577 | Schellingerhout et al. | Jul 2014 | B2 |
8799816 | Wells et al. | Aug 2014 | B2 |
8854316 | Shenfield | Oct 2014 | B2 |
8872729 | Lyons | Oct 2014 | B2 |
8872773 | Mak | Oct 2014 | B2 |
8875044 | Ozawa et al. | Oct 2014 | B2 |
8914732 | Jun et al. | Dec 2014 | B2 |
8952987 | Momeyer et al. | Feb 2015 | B2 |
8959430 | Spivak et al. | Feb 2015 | B1 |
8976128 | Moore | Mar 2015 | B2 |
9026932 | Dixon | May 2015 | B1 |
9030419 | Freed | May 2015 | B1 |
9030436 | Ikeda | May 2015 | B2 |
9069460 | Moore | Jun 2015 | B2 |
9086755 | Cho et al. | Jul 2015 | B2 |
9092058 | Kasahara | Jul 2015 | B2 |
9098188 | Kim | Aug 2015 | B2 |
9116571 | Zeliff | Aug 2015 | B2 |
9122364 | Kuwabara et al. | Sep 2015 | B2 |
9148618 | Matas et al. | Sep 2015 | B2 |
9164779 | Brakensiek | Oct 2015 | B2 |
9170607 | Bose | Oct 2015 | B2 |
9218105 | Masson | Dec 2015 | B2 |
9244562 | Rosenberg et al. | Jan 2016 | B1 |
9244576 | Vadagave et al. | Jan 2016 | B1 |
9244601 | Kim et al. | Jan 2016 | B2 |
9246487 | Casparian et al. | Jan 2016 | B2 |
9262002 | Momeyer et al. | Feb 2016 | B2 |
9304668 | Rezende et al. | Apr 2016 | B2 |
9307112 | Molgaard et al. | Apr 2016 | B2 |
9349552 | Huska et al. | May 2016 | B2 |
9361018 | Defazio et al. | Jun 2016 | B2 |
9389718 | Letourneur | Jul 2016 | B1 |
9389722 | Matsuki et al. | Jul 2016 | B2 |
9400581 | Bokma et al. | Jul 2016 | B2 |
9405367 | Jung et al. | Aug 2016 | B2 |
9417754 | Smith | Aug 2016 | B2 |
9436344 | Kuwabara et al. | Sep 2016 | B2 |
9471145 | Langlois et al. | Oct 2016 | B2 |
9477393 | Zambetti et al. | Oct 2016 | B2 |
9542013 | Dearman | Jan 2017 | B2 |
9600114 | Milam et al. | Mar 2017 | B2 |
9600116 | Tao et al. | Mar 2017 | B2 |
20010024195 | Hayakawa et al. | Sep 2001 | A1 |
20010045965 | Orbanes et al. | Nov 2001 | A1 |
20020008691 | Hanajima et al. | Jan 2002 | A1 |
20020015064 | Robotham | Feb 2002 | A1 |
20020109678 | Marmolin et al. | Aug 2002 | A1 |
20020140680 | Lu | Oct 2002 | A1 |
20020180763 | Kung | Dec 2002 | A1 |
20030001869 | Nissen | Jan 2003 | A1 |
20030086496 | Zhang et al. | May 2003 | A1 |
20030151589 | Bensen et al. | Aug 2003 | A1 |
20030184574 | Phillips et al. | Oct 2003 | A1 |
20030189647 | Kang | Oct 2003 | A1 |
20030206169 | Springer et al. | Nov 2003 | A1 |
20030222915 | Marion et al. | Dec 2003 | A1 |
20040021643 | Hoshino et al. | Feb 2004 | A1 |
20040056849 | Lohbihler et al. | Mar 2004 | A1 |
20040108995 | Hoshino et al. | Jun 2004 | A1 |
20040138849 | Schmidt | Jul 2004 | A1 |
20040150631 | Fleck | Aug 2004 | A1 |
20040150644 | Kincaid et al. | Aug 2004 | A1 |
20040174399 | Wu et al. | Sep 2004 | A1 |
20040219969 | Casey et al. | Nov 2004 | A1 |
20050012723 | Pallakoff | Jan 2005 | A1 |
20050110769 | DaCosta et al. | May 2005 | A1 |
20050125742 | Grotjohn et al. | Jun 2005 | A1 |
20050132297 | Milic-Frayling et al. | Jun 2005 | A1 |
20050134578 | Chambers et al. | Jun 2005 | A1 |
20050183017 | Cain | Aug 2005 | A1 |
20050190280 | Haas et al. | Sep 2005 | A1 |
20050204295 | Voorhees et al. | Sep 2005 | A1 |
20050223338 | Partanen | Oct 2005 | A1 |
20050229112 | Clay et al. | Oct 2005 | A1 |
20050289476 | Tokkonen | Dec 2005 | A1 |
20060022955 | Kennedy | Feb 2006 | A1 |
20060022956 | Lengeling et al. | Feb 2006 | A1 |
20060026536 | Hotelling et al. | Feb 2006 | A1 |
20060036971 | Mendel | Feb 2006 | A1 |
20060059436 | Nurmi | Mar 2006 | A1 |
20060067677 | Tokiwa et al. | Mar 2006 | A1 |
20060101347 | Runov et al. | May 2006 | A1 |
20060109252 | Kolmykov-Zotov et al. | May 2006 | A1 |
20060109256 | Grant et al. | May 2006 | A1 |
20060119586 | Grant et al. | Jun 2006 | A1 |
20060132455 | Rimas-Ribikauskas et al. | Jun 2006 | A1 |
20060132456 | Anson | Jun 2006 | A1 |
20060132457 | Rimas-Ribikauskas et al. | Jun 2006 | A1 |
20060136834 | Cao et al. | Jun 2006 | A1 |
20060136845 | Rimas-Ribikauskas et al. | Jun 2006 | A1 |
20060197753 | Hotelling | Sep 2006 | A1 |
20060212812 | Simmons et al. | Sep 2006 | A1 |
20060213754 | Jarrett et al. | Sep 2006 | A1 |
20060233248 | Rynderman et al. | Oct 2006 | A1 |
20060274042 | Krah | Dec 2006 | A1 |
20060277469 | Chaudhri et al. | Dec 2006 | A1 |
20060282778 | Barsness et al. | Dec 2006 | A1 |
20060284858 | Rekimoto | Dec 2006 | A1 |
20060290681 | Ho et al. | Dec 2006 | A1 |
20070024595 | Baker et al. | Feb 2007 | A1 |
20070024646 | Saarinen et al. | Feb 2007 | A1 |
20070080953 | Lii | Apr 2007 | A1 |
20070113681 | Nishimura et al. | May 2007 | A1 |
20070120835 | Sato | May 2007 | A1 |
20070124699 | Michaels | May 2007 | A1 |
20070168369 | Bruns | Jul 2007 | A1 |
20070168890 | Zhao et al. | Jul 2007 | A1 |
20070176904 | Russo | Aug 2007 | A1 |
20070186178 | Schiller | Aug 2007 | A1 |
20070222768 | Geurts et al. | Sep 2007 | A1 |
20070229455 | Martin et al. | Oct 2007 | A1 |
20070229464 | Hotelling et al. | Oct 2007 | A1 |
20070236450 | Colgate et al. | Oct 2007 | A1 |
20070236477 | Ryu et al. | Oct 2007 | A1 |
20070245241 | Bertram et al. | Oct 2007 | A1 |
20070257821 | Son | Nov 2007 | A1 |
20070270182 | Gulliksson et al. | Nov 2007 | A1 |
20070294295 | Finkelstein et al. | Dec 2007 | A1 |
20080001924 | dos los Reyes et al. | Jan 2008 | A1 |
20080024459 | Poupyrev | Jan 2008 | A1 |
20080034306 | Ording | Feb 2008 | A1 |
20080036743 | Westerman et al. | Feb 2008 | A1 |
20080051989 | Welsh | Feb 2008 | A1 |
20080052945 | Matas et al. | Mar 2008 | A1 |
20080066010 | Brodersen et al. | Mar 2008 | A1 |
20080094367 | Van De Ven et al. | Apr 2008 | A1 |
20080106523 | Conrad | May 2008 | A1 |
20080136790 | Hio | Jun 2008 | A1 |
20080155415 | Yoon et al. | Jun 2008 | A1 |
20080168395 | Ording et al. | Jul 2008 | A1 |
20080168403 | Westerman et al. | Jul 2008 | A1 |
20080202824 | Philipp et al. | Aug 2008 | A1 |
20080204427 | Heesemans et al. | Aug 2008 | A1 |
20080219493 | Tadmor | Sep 2008 | A1 |
20080222569 | Champion et al. | Sep 2008 | A1 |
20080259046 | Carsanaro | Oct 2008 | A1 |
20080263452 | Tomkins | Oct 2008 | A1 |
20080284866 | Mizutani | Nov 2008 | A1 |
20080294984 | Ramsay et al. | Nov 2008 | A1 |
20080297475 | Woolf et al. | Dec 2008 | A1 |
20080303799 | Schwesig et al. | Dec 2008 | A1 |
20080307359 | Louch et al. | Dec 2008 | A1 |
20080317378 | Steinberg et al. | Dec 2008 | A1 |
20080320419 | Matas et al. | Dec 2008 | A1 |
20090007017 | Anzures et al. | Jan 2009 | A1 |
20090046110 | Sadler | Feb 2009 | A1 |
20090058828 | Jiang et al. | Mar 2009 | A1 |
20090066668 | Kim et al. | Mar 2009 | A1 |
20090073118 | Yamaji et al. | Mar 2009 | A1 |
20090083665 | Anttila et al. | Mar 2009 | A1 |
20090085878 | Heubel et al. | Apr 2009 | A1 |
20090085881 | Keam | Apr 2009 | A1 |
20090085886 | Huang et al. | Apr 2009 | A1 |
20090100343 | Lee et al. | Apr 2009 | A1 |
20090102804 | Wong et al. | Apr 2009 | A1 |
20090102805 | Meijer et al. | Apr 2009 | A1 |
20090140985 | Liu | Jun 2009 | A1 |
20090158198 | Hayter et al. | Jun 2009 | A1 |
20090160793 | Rekimoto | Jun 2009 | A1 |
20090160814 | Li et al. | Jun 2009 | A1 |
20090167507 | Maenpaa | Jul 2009 | A1 |
20090167508 | Fadell et al. | Jul 2009 | A1 |
20090167704 | Terlizzi et al. | Jul 2009 | A1 |
20090169061 | Anderson et al. | Jul 2009 | A1 |
20090225037 | Williamson | Sep 2009 | A1 |
20090237374 | Li et al. | Sep 2009 | A1 |
20090247112 | Lundy et al. | Oct 2009 | A1 |
20090256947 | Ciurea et al. | Oct 2009 | A1 |
20090267906 | Schroderus | Oct 2009 | A1 |
20090282360 | Park et al. | Nov 2009 | A1 |
20090293009 | Meserth et al. | Nov 2009 | A1 |
20090303187 | Pallakoff | Dec 2009 | A1 |
20090307633 | Haughay, Jr. et al. | Dec 2009 | A1 |
20090322893 | Stallings et al. | Dec 2009 | A1 |
20100007926 | Imaizumi et al. | Jan 2010 | A1 |
20100011304 | Van Os | Jan 2010 | A1 |
20100013777 | Baudisch et al. | Jan 2010 | A1 |
20100017710 | Kim et al. | Jan 2010 | A1 |
20100026640 | Kim et al. | Feb 2010 | A1 |
20100026647 | Abe et al. | Feb 2010 | A1 |
20100039446 | Hillis et al. | Feb 2010 | A1 |
20100044121 | Simon et al. | Feb 2010 | A1 |
20100057235 | Wang et al. | Mar 2010 | A1 |
20100058231 | Duarte et al. | Mar 2010 | A1 |
20100070908 | Mori et al. | Mar 2010 | A1 |
20100073329 | Raman et al. | Mar 2010 | A1 |
20100083116 | Akifusa et al. | Apr 2010 | A1 |
20100085302 | Fairweather | Apr 2010 | A1 |
20100085314 | Kwok | Apr 2010 | A1 |
20100085317 | Park et al. | Apr 2010 | A1 |
20100088596 | Griffin et al. | Apr 2010 | A1 |
20100127983 | Irani et al. | May 2010 | A1 |
20100128002 | Stacy et al. | May 2010 | A1 |
20100138776 | Korhonen | Jun 2010 | A1 |
20100148999 | Casparian et al. | Jun 2010 | A1 |
20100149096 | Migos et al. | Jun 2010 | A1 |
20100156813 | Duarte et al. | Jun 2010 | A1 |
20100156818 | Burrough et al. | Jun 2010 | A1 |
20100156823 | Paleczny et al. | Jun 2010 | A1 |
20100156825 | Sohn et al. | Jun 2010 | A1 |
20100171713 | Kwok et al. | Jul 2010 | A1 |
20100175023 | Gatlin et al. | Jul 2010 | A1 |
20100180225 | Chiba et al. | Jul 2010 | A1 |
20100199227 | Xiao et al. | Aug 2010 | A1 |
20100211872 | Rolston et al. | Aug 2010 | A1 |
20100225604 | Homma et al. | Sep 2010 | A1 |
20100231534 | Chaudhri et al. | Sep 2010 | A1 |
20100235726 | Ording et al. | Sep 2010 | A1 |
20100235746 | Anzures | Sep 2010 | A1 |
20100271312 | Alameh et al. | Oct 2010 | A1 |
20100271500 | Park et al. | Oct 2010 | A1 |
20100289807 | Yu et al. | Nov 2010 | A1 |
20100302177 | Kim et al. | Dec 2010 | A1 |
20100302179 | Ahn et al. | Dec 2010 | A1 |
20100306702 | Warner | Dec 2010 | A1 |
20100308983 | Conte et al. | Dec 2010 | A1 |
20100309147 | Fleizach et al. | Dec 2010 | A1 |
20100313124 | Privault et al. | Dec 2010 | A1 |
20100313156 | Louch et al. | Dec 2010 | A1 |
20100313158 | Lee et al. | Dec 2010 | A1 |
20100313166 | Nakayama et al. | Dec 2010 | A1 |
20100315417 | Cho et al. | Dec 2010 | A1 |
20100315438 | Horodezky et al. | Dec 2010 | A1 |
20100321301 | Casparian et al. | Dec 2010 | A1 |
20100325578 | Mital et al. | Dec 2010 | A1 |
20110018695 | Bells | Jan 2011 | A1 |
20110050588 | Li et al. | Mar 2011 | A1 |
20110050591 | Kim et al. | Mar 2011 | A1 |
20110050594 | Kim et al. | Mar 2011 | A1 |
20110050629 | Homma et al. | Mar 2011 | A1 |
20110050630 | Ikeda | Mar 2011 | A1 |
20110050653 | Miyazawa et al. | Mar 2011 | A1 |
20110054837 | Ikeda | Mar 2011 | A1 |
20110055135 | Dawson et al. | Mar 2011 | A1 |
20110057886 | Ng et al. | Mar 2011 | A1 |
20110057903 | Yamano et al. | Mar 2011 | A1 |
20110061029 | Yeh et al. | Mar 2011 | A1 |
20110063248 | Yoon | Mar 2011 | A1 |
20110069012 | Martensson | Mar 2011 | A1 |
20110069016 | Victor | Mar 2011 | A1 |
20110074697 | Rapp et al. | Mar 2011 | A1 |
20110080350 | Almalki | Apr 2011 | A1 |
20110084910 | Almalki | Apr 2011 | A1 |
20110087983 | Shim | Apr 2011 | A1 |
20110093815 | Gobeil | Apr 2011 | A1 |
20110093817 | Song et al. | Apr 2011 | A1 |
20110107272 | Aguilar | May 2011 | A1 |
20110116716 | Kwon et al. | May 2011 | A1 |
20110141031 | McCullough et al. | Jun 2011 | A1 |
20110141052 | Bernstein et al. | Jun 2011 | A1 |
20110144777 | Firkins et al. | Jun 2011 | A1 |
20110145752 | Fagans | Jun 2011 | A1 |
20110145753 | Prakash | Jun 2011 | A1 |
20110145764 | Higuchi et al. | Jun 2011 | A1 |
20110149138 | Watkins | Jun 2011 | A1 |
20110163971 | Wagner et al. | Jul 2011 | A1 |
20110164042 | Chaudhri | Jul 2011 | A1 |
20110169765 | Aono | Jul 2011 | A1 |
20110175830 | Miyazawa et al. | Jul 2011 | A1 |
20110179368 | King et al. | Jul 2011 | A1 |
20110179381 | King | Jul 2011 | A1 |
20110181538 | Aono | Jul 2011 | A1 |
20110185299 | Hinckley et al. | Jul 2011 | A1 |
20110185300 | Hinckley et al. | Jul 2011 | A1 |
20110185316 | Reid et al. | Jul 2011 | A1 |
20110193809 | Walley et al. | Aug 2011 | A1 |
20110193881 | Rydenhag | Aug 2011 | A1 |
20110201387 | Paek et al. | Aug 2011 | A1 |
20110202834 | Mandryk et al. | Aug 2011 | A1 |
20110202853 | Mujkic | Aug 2011 | A1 |
20110205163 | Hinckley et al. | Aug 2011 | A1 |
20110209088 | Hinckley et al. | Aug 2011 | A1 |
20110209093 | Hinckley et al. | Aug 2011 | A1 |
20110209099 | Hinckley et al. | Aug 2011 | A1 |
20110210931 | Shai | Sep 2011 | A1 |
20110215914 | Edwards | Sep 2011 | A1 |
20110221684 | Rydenhag | Sep 2011 | A1 |
20110221776 | Shimotani et al. | Sep 2011 | A1 |
20110231789 | Bukurak et al. | Sep 2011 | A1 |
20110238690 | Arrasvuori et al. | Sep 2011 | A1 |
20110239110 | Garrett et al. | Sep 2011 | A1 |
20110242029 | Kasahara et al. | Oct 2011 | A1 |
20110246877 | Kwak et al. | Oct 2011 | A1 |
20110248948 | Griffin et al. | Oct 2011 | A1 |
20110252357 | Chaudhri | Oct 2011 | A1 |
20110252362 | Cho et al. | Oct 2011 | A1 |
20110258537 | Rives et al. | Oct 2011 | A1 |
20110263298 | Park | Oct 2011 | A1 |
20110267530 | Chun | Nov 2011 | A1 |
20110279381 | Tong et al. | Nov 2011 | A1 |
20110279395 | Kuwabara et al. | Nov 2011 | A1 |
20110279852 | Oda et al. | Nov 2011 | A1 |
20110285656 | Yaksick et al. | Nov 2011 | A1 |
20110285659 | Kuwabara et al. | Nov 2011 | A1 |
20110291951 | Tong | Dec 2011 | A1 |
20110296351 | Ewing, Jr. et al. | Dec 2011 | A1 |
20110304559 | Pasquero | Dec 2011 | A1 |
20110304577 | Brown et al. | Dec 2011 | A1 |
20110310049 | Homma et al. | Dec 2011 | A1 |
20120011437 | James et al. | Jan 2012 | A1 |
20120013541 | Boka et al. | Jan 2012 | A1 |
20120013542 | Shenfield | Jan 2012 | A1 |
20120019448 | Pitkanen et al. | Jan 2012 | A1 |
20120026110 | Yamano | Feb 2012 | A1 |
20120036556 | LeBeau et al. | Feb 2012 | A1 |
20120038580 | Sasaki | Feb 2012 | A1 |
20120044153 | Arrasvuori et al. | Feb 2012 | A1 |
20120056837 | Park et al. | Mar 2012 | A1 |
20120056848 | Yamano et al. | Mar 2012 | A1 |
20120062564 | Miyashita et al. | Mar 2012 | A1 |
20120062604 | Lobo | Mar 2012 | A1 |
20120066630 | Kim et al. | Mar 2012 | A1 |
20120066648 | Rolleston et al. | Mar 2012 | A1 |
20120081375 | Robert et al. | Apr 2012 | A1 |
20120084689 | Ledet et al. | Apr 2012 | A1 |
20120089932 | Kano et al. | Apr 2012 | A1 |
20120089951 | Cassidy | Apr 2012 | A1 |
20120096393 | Shim et al. | Apr 2012 | A1 |
20120098780 | Fujisawa et al. | Apr 2012 | A1 |
20120102437 | Worley et al. | Apr 2012 | A1 |
20120105358 | Momeyer et al. | May 2012 | A1 |
20120105367 | Son | May 2012 | A1 |
20120106852 | Khawand et al. | May 2012 | A1 |
20120113023 | Koch et al. | May 2012 | A1 |
20120126962 | Ujii et al. | May 2012 | A1 |
20120131495 | Goossens et al. | May 2012 | A1 |
20120139864 | Sleeman et al. | Jun 2012 | A1 |
20120146945 | Miyazawa et al. | Jun 2012 | A1 |
20120147052 | Homma et al. | Jun 2012 | A1 |
20120154328 | Kono | Jun 2012 | A1 |
20120159380 | Kocienda et al. | Jun 2012 | A1 |
20120169646 | Berkes et al. | Jul 2012 | A1 |
20120176403 | Cha et al. | Jul 2012 | A1 |
20120179967 | Hayes | Jul 2012 | A1 |
20120182226 | Tuli | Jul 2012 | A1 |
20120183271 | Forutanpour et al. | Jul 2012 | A1 |
20120206393 | Hillis et al. | Aug 2012 | A1 |
20120216114 | Privault et al. | Aug 2012 | A1 |
20120218203 | Kanki | Aug 2012 | A1 |
20120235912 | Laubach | Sep 2012 | A1 |
20120240044 | Johnson et al. | Sep 2012 | A1 |
20120249575 | Krolczyk et al. | Oct 2012 | A1 |
20120249853 | Krolczyk et al. | Oct 2012 | A1 |
20120256846 | Mak | Oct 2012 | A1 |
20120256847 | Mak | Oct 2012 | A1 |
20120256857 | Mak | Oct 2012 | A1 |
20120257071 | Prentice | Oct 2012 | A1 |
20120260220 | Griffin | Oct 2012 | A1 |
20120274591 | Rimas-Ribikauskas et al. | Nov 2012 | A1 |
20120274662 | Kim et al. | Nov 2012 | A1 |
20120284673 | Lamb et al. | Nov 2012 | A1 |
20120293449 | Dietz | Nov 2012 | A1 |
20120293551 | Momeyer et al. | Nov 2012 | A1 |
20120304132 | Sareen et al. | Nov 2012 | A1 |
20120304133 | Nan et al. | Nov 2012 | A1 |
20120306748 | Fleizach et al. | Dec 2012 | A1 |
20120306764 | Kamibeppu | Dec 2012 | A1 |
20120306765 | Moore | Dec 2012 | A1 |
20120306766 | Moore | Dec 2012 | A1 |
20120306772 | Tan et al. | Dec 2012 | A1 |
20120306778 | Wheeldreyer et al. | Dec 2012 | A1 |
20120311429 | Decker et al. | Dec 2012 | A1 |
20120311437 | Weeldreyer et al. | Dec 2012 | A1 |
20120311498 | Kluttz et al. | Dec 2012 | A1 |
20130002561 | Wakasa | Jan 2013 | A1 |
20130016042 | Makinen et al. | Jan 2013 | A1 |
20130019158 | Watanabe | Jan 2013 | A1 |
20130019174 | Gil et al. | Jan 2013 | A1 |
20130044062 | Bose et al. | Feb 2013 | A1 |
20130047100 | Kroeger et al. | Feb 2013 | A1 |
20130050131 | Lee et al. | Feb 2013 | A1 |
20130061172 | Huang et al. | Mar 2013 | A1 |
20130063389 | Moore | Mar 2013 | A1 |
20130067383 | Kataoka et al. | Mar 2013 | A1 |
20130067513 | Takami | Mar 2013 | A1 |
20130077804 | Glebe et al. | Mar 2013 | A1 |
20130082824 | Colley | Apr 2013 | A1 |
20130093691 | Moosavi | Apr 2013 | A1 |
20130097520 | Lewin | Apr 2013 | A1 |
20130097521 | Lewin | Apr 2013 | A1 |
20130097534 | Lewin | Apr 2013 | A1 |
20130097539 | M nsson | Apr 2013 | A1 |
20130097562 | Kermoian et al. | Apr 2013 | A1 |
20130113720 | Van Eerd et al. | May 2013 | A1 |
20130120295 | Kim et al. | May 2013 | A1 |
20130135243 | Hirsch et al. | May 2013 | A1 |
20130135499 | Song | May 2013 | A1 |
20130141364 | Lynn et al. | Jun 2013 | A1 |
20130141396 | Lynn et al. | Jun 2013 | A1 |
20130145313 | Roh et al. | Jun 2013 | A1 |
20130154948 | Schediwy et al. | Jun 2013 | A1 |
20130154959 | Lindsay et al. | Jun 2013 | A1 |
20130155018 | Dagdeviren | Jun 2013 | A1 |
20130159893 | Lewin | Jun 2013 | A1 |
20130162667 | Eskolin et al. | Jun 2013 | A1 |
20130169549 | Seymour et al. | Jul 2013 | A1 |
20130174094 | Heo et al. | Jul 2013 | A1 |
20130174179 | Park et al. | Jul 2013 | A1 |
20130179840 | Fisher et al. | Jul 2013 | A1 |
20130191791 | Rydenhag et al. | Jul 2013 | A1 |
20130198690 | Barsoum et al. | Aug 2013 | A1 |
20130212541 | Dolenc et al. | Aug 2013 | A1 |
20130222274 | Mori et al. | Aug 2013 | A1 |
20130222671 | Tseng et al. | Aug 2013 | A1 |
20130227450 | Na et al. | Aug 2013 | A1 |
20130232402 | Lu | Sep 2013 | A1 |
20130234929 | Libin | Sep 2013 | A1 |
20130249814 | Zeng | Sep 2013 | A1 |
20130257793 | Zeliff | Oct 2013 | A1 |
20130257817 | Yliaho | Oct 2013 | A1 |
20130265246 | Tae | Oct 2013 | A1 |
20130268875 | Han et al. | Oct 2013 | A1 |
20130278520 | Weng et al. | Oct 2013 | A1 |
20130325342 | Pylappan et al. | Dec 2013 | A1 |
20130326420 | Liu et al. | Dec 2013 | A1 |
20130326421 | Jo | Dec 2013 | A1 |
20130328770 | Parham | Dec 2013 | A1 |
20130332892 | Matsuki | Dec 2013 | A1 |
20130339909 | Ha | Dec 2013 | A1 |
20140002355 | Lee et al. | Jan 2014 | A1 |
20140002374 | Hunt et al. | Jan 2014 | A1 |
20140002386 | Rosenberg et al. | Jan 2014 | A1 |
20140026098 | Gilman | Jan 2014 | A1 |
20140028571 | St. Clair | Jan 2014 | A1 |
20140028601 | Moore | Jan 2014 | A1 |
20140049491 | Nagar et al. | Feb 2014 | A1 |
20140055367 | Dearman | Feb 2014 | A1 |
20140055377 | Kim | Feb 2014 | A1 |
20140059485 | Lehrian et al. | Feb 2014 | A1 |
20140063316 | Lee et al. | Mar 2014 | A1 |
20140078343 | Dai et al. | Mar 2014 | A1 |
20140082536 | Costa et al. | Mar 2014 | A1 |
20140092025 | Pala et al. | Apr 2014 | A1 |
20140109016 | Ouyang et al. | Apr 2014 | A1 |
20140111456 | Kashiwa et al. | Apr 2014 | A1 |
20140111670 | Lord et al. | Apr 2014 | A1 |
20140139471 | Matsuki | May 2014 | A1 |
20140152581 | Case | Jun 2014 | A1 |
20140157203 | Jeon et al. | Jun 2014 | A1 |
20140160063 | Yairi et al. | Jun 2014 | A1 |
20140160073 | Matsuki | Jun 2014 | A1 |
20140165006 | Chaudhri et al. | Jun 2014 | A1 |
20140168093 | Lawrence | Jun 2014 | A1 |
20140168153 | Deichmann et al. | Jun 2014 | A1 |
20140173517 | Chaudhri | Jun 2014 | A1 |
20140184526 | Cho | Jul 2014 | A1 |
20140210758 | Park et al. | Jul 2014 | A1 |
20140210798 | Wilson | Jul 2014 | A1 |
20140245202 | Yoon et al. | Aug 2014 | A1 |
20140267114 | Lisseman et al. | Sep 2014 | A1 |
20140267135 | Chhabra | Sep 2014 | A1 |
20140282084 | Murarka et al. | Sep 2014 | A1 |
20140282214 | Shirzadi et al. | Sep 2014 | A1 |
20140300569 | Matsuki et al. | Oct 2014 | A1 |
20140304651 | Johansson et al. | Oct 2014 | A1 |
20140306897 | Cueto | Oct 2014 | A1 |
20140306899 | Hicks | Oct 2014 | A1 |
20140310638 | Lee et al. | Oct 2014 | A1 |
20140313130 | Yamano | Oct 2014 | A1 |
20140333561 | Bull et al. | Nov 2014 | A1 |
20140344765 | Hicks et al. | Nov 2014 | A1 |
20140354845 | Molgaard et al. | Dec 2014 | A1 |
20140354850 | Kosaka et al. | Dec 2014 | A1 |
20140359528 | Murata | Dec 2014 | A1 |
20140380247 | Tecarro et al. | Dec 2014 | A1 |
20150015763 | Lee et al. | Jan 2015 | A1 |
20150020036 | Kim et al. | Jan 2015 | A1 |
20150026584 | Kobayakov et al. | Jan 2015 | A1 |
20150026592 | Mohammed et al. | Jan 2015 | A1 |
20150029149 | Andersson et al. | Jan 2015 | A1 |
20150033184 | Kim et al. | Jan 2015 | A1 |
20150046876 | Goldenberg | Feb 2015 | A1 |
20150058723 | Cieplinski et al. | Feb 2015 | A1 |
20150062052 | Bernstein et al. | Mar 2015 | A1 |
20150062068 | Shih et al. | Mar 2015 | A1 |
20150067495 | Bernstein et al. | Mar 2015 | A1 |
20150067496 | Missig et al. | Mar 2015 | A1 |
20150067497 | Cieplinski et al. | Mar 2015 | A1 |
20150067513 | Zambetti et al. | Mar 2015 | A1 |
20150067519 | Missig et al. | Mar 2015 | A1 |
20150067559 | Missig et al. | Mar 2015 | A1 |
20150067560 | Cieplinski et al. | Mar 2015 | A1 |
20150067563 | Bernstein et al. | Mar 2015 | A1 |
20150067596 | Brown et al. | Mar 2015 | A1 |
20150067601 | Bernstein et al. | Mar 2015 | A1 |
20150067602 | Bernstein et al. | Mar 2015 | A1 |
20150067605 | Zambetti et al. | Mar 2015 | A1 |
20150071547 | Keating et al. | Mar 2015 | A1 |
20150116205 | Westerman et al. | Apr 2015 | A1 |
20150121225 | Somasundaram et al. | Apr 2015 | A1 |
20150128092 | Lee et al. | May 2015 | A1 |
20150135109 | Zambetti et al. | May 2015 | A1 |
20150138126 | Westerman | May 2015 | A1 |
20150138155 | Bernstein et al. | May 2015 | A1 |
20150139605 | Wiklof | May 2015 | A1 |
20150143273 | Bernstein et al. | May 2015 | A1 |
20150149899 | Bernstein et al. | May 2015 | A1 |
20150149964 | Bernstein et al. | May 2015 | A1 |
20150149967 | Bernstein et al. | May 2015 | A1 |
20150153929 | Bernstein et al. | Jun 2015 | A1 |
20150160729 | Nakagawa | Jun 2015 | A1 |
20150205495 | Koide | Jul 2015 | A1 |
20150234446 | Nathan et al. | Aug 2015 | A1 |
20150253866 | Amm | Sep 2015 | A1 |
20150268813 | Bos | Sep 2015 | A1 |
20150321607 | Cho et al. | Nov 2015 | A1 |
20150332107 | Paniaras | Nov 2015 | A1 |
20150378519 | Brown et al. | Dec 2015 | A1 |
20150378982 | McKenzie et al. | Dec 2015 | A1 |
20150381931 | Uhma et al. | Dec 2015 | A1 |
20160004427 | Zambetti et al. | Jan 2016 | A1 |
20160004428 | Bernstein et al. | Jan 2016 | A1 |
20160004429 | Bernstein et al. | Jan 2016 | A1 |
20160004430 | Missig et al. | Jan 2016 | A1 |
20160004431 | Bernstein et al. | Jan 2016 | A1 |
20160004432 | Bernstein et al. | Jan 2016 | A1 |
20160011771 | Cieplinski | Jan 2016 | A1 |
20160019718 | Mukkamala et al. | Jan 2016 | A1 |
20160041750 | Cieplinski et al. | Feb 2016 | A1 |
20160048326 | Kim et al. | Feb 2016 | A1 |
20160062466 | Moussette et al. | Mar 2016 | A1 |
20160062619 | Reeve et al. | Mar 2016 | A1 |
20160070401 | Kim et al. | Mar 2016 | A1 |
20160132139 | Du | May 2016 | A1 |
20160188181 | Smith | Jun 2016 | A1 |
20160210025 | Bernstein et al. | Jul 2016 | A1 |
20160259412 | Flint et al. | Sep 2016 | A1 |
20160259413 | Anzures et al. | Sep 2016 | A1 |
20160259495 | Butcher | Sep 2016 | A1 |
20160259496 | Butcher | Sep 2016 | A1 |
20160259497 | Foss et al. | Sep 2016 | A1 |
20160259498 | Foss et al. | Sep 2016 | A1 |
20160259499 | Kocienda et al. | Sep 2016 | A1 |
20160259516 | Kudurshian et al. | Sep 2016 | A1 |
20160259517 | Butcher | Sep 2016 | A1 |
20160259518 | King et al. | Sep 2016 | A1 |
20160259519 | Foss et al. | Sep 2016 | A1 |
20160259527 | Kocienda et al. | Sep 2016 | A1 |
20160259528 | Foss et al. | Sep 2016 | A1 |
20160259536 | Kudurshian et al. | Sep 2016 | A1 |
20160274686 | Ruiz et al. | Sep 2016 | A1 |
20160274728 | Luo et al. | Sep 2016 | A1 |
20160274761 | Ruiz et al. | Sep 2016 | A1 |
20160320906 | Bokma et al. | Nov 2016 | A1 |
20160357305 | Wells et al. | Dec 2016 | A1 |
20160357368 | Federighi et al. | Dec 2016 | A1 |
20160357390 | Federighi et al. | Dec 2016 | A1 |
20160357404 | Ruiz et al. | Dec 2016 | A1 |
20160360116 | Penha et al. | Dec 2016 | A1 |
20170075520 | Bauer et al. | Mar 2017 | A1 |
20170075562 | Bauer et al. | Mar 2017 | A1 |
20170075563 | Bauer et al. | Mar 2017 | A1 |
Number | Date | Country |
---|---|---|
1808362 | Jul 2006 | CN |
101222704 | Jul 2008 | CN |
101320303 | Dec 2008 | CN |
101593077 | Dec 2009 | CN |
101809526 | Aug 2010 | CN |
102004593 | Apr 2011 | CN |
102112946 | Jun 2011 | CN |
102160021 | Aug 2011 | CN |
102385478 | Mar 2012 | CN |
102438092 | May 2012 | CN |
102662573 | Sep 2012 | CN |
102841677 | Dec 2012 | CN |
103097992 | May 2013 | CN |
100 59 906 | Jun 2002 | DE |
0 859 307 | Mar 1998 | EP |
0 880 090 | Nov 1998 | EP |
1 028 583 | Aug 2000 | EP |
1 406 150 | Apr 2004 | EP |
1 674 977 | Jun 2006 | EP |
1 882 902 | Jan 2008 | EP |
2 000 896 | Dec 2008 | EP |
2 017 701 | Jan 2009 | EP |
2 028 583 | Feb 2009 | EP |
2 141 574 | Jan 2010 | EP |
2 175 357 | Apr 2010 | EP |
2 196 893 | Jun 2010 | EP |
2 214 087 | Aug 2010 | EP |
2 226 715 | Sep 2010 | EP |
2 299 351 | Sep 2010 | EP |
2 302 496 | Mar 2011 | EP |
2 375 309 | Oct 2011 | EP |
2 375 314 | Oct 2011 | EP |
2 386 935 | Nov 2011 | EP |
2 407 868 | Jan 2012 | EP |
2 426 580 | Mar 2012 | EP |
2 447 818 | May 2012 | EP |
2 527 966 | Nov 2012 | EP |
2 530 677 | Dec 2012 | EP |
2 541 376 | Jan 2013 | EP |
2 555 500 | Feb 2013 | EP |
2 615 535 | Jul 2013 | EP |
2 631 737 | Aug 2013 | EP |
2 674 846 | Dec 2013 | EP |
2 733 578 | May 2014 | EP |
2 808 764 | Dec 2014 | EP |
2 809 058 | Dec 2014 | EP |
2 813 938 | Dec 2014 | EP |
2 402 105 | Dec 2004 | GB |
H07-151512 | Jun 1995 | JP |
H08-227341 | Sep 1996 | JP |
H09-330175 | Dec 1997 | JP |
H11-203044 | Jul 1999 | JP |
2001-202192 | Jul 2001 | JP |
2002-149312 | May 2002 | JP |
2003-157131 | May 2003 | JP |
2003-186597 | Jul 2003 | JP |
2004-054861 | Feb 2004 | JP |
2004-062648 | Feb 2004 | JP |
2004-070492 | Mar 2004 | JP |
2004-086733 | Mar 2004 | JP |
2005-031786 | Feb 2005 | JP |
2005-092386 | Apr 2005 | JP |
2005-135106 | May 2005 | JP |
2005-157842 | Jun 2005 | JP |
2006-185443 | Jul 2006 | JP |
2007-116384 | May 2007 | JP |
2007-264808 | Oct 2007 | JP |
2008-009759 | Jan 2008 | JP |
2008-015890 | Jan 2008 | JP |
2008-033739 | Feb 2008 | JP |
2008-146453 | Jun 2008 | JP |
2008-537615 | Sep 2008 | JP |
2008 305174 | Dec 2008 | JP |
2009-500761 | Jan 2009 | JP |
2009-211704 | Sep 2009 | JP |
2009-217543 | Sep 2009 | JP |
2010-009321 | Jan 2010 | JP |
2010-503130 | Jan 2010 | JP |
2010-055274 | Mar 2010 | JP |
2010-146507 | Jul 2010 | JP |
2010-152716 | Jul 2010 | JP |
2010-176174 | Aug 2010 | JP |
2010-176337 | Aug 2010 | JP |
2010-181934 | Aug 2010 | JP |
2010-541071 | Dec 2010 | JP |
2011-501307 | Jan 2011 | JP |
2011-048666 | Mar 2011 | JP |
2011-048686 | Mar 2011 | JP |
2011-048762 | Mar 2011 | JP |
2011-048832 | Mar 2011 | JP |
2011-053831 | Mar 2011 | JP |
2011-053973 | Mar 2011 | JP |
2011-059821 | Mar 2011 | JP |
2011-070342 | Apr 2011 | JP |
2011-100290 | May 2011 | JP |
2011-107823 | Jun 2011 | JP |
2011-123773 | Jun 2011 | JP |
2011-141868 | Jul 2011 | JP |
2011-192179 | Sep 2011 | JP |
2011-192215 | Sep 2011 | JP |
2011-242386 | Dec 2011 | JP |
2011-253556 | Dec 2011 | JP |
2011-257941 | Dec 2011 | JP |
2011-530101 | Dec 2011 | JP |
2012-043266 | Dec 2011 | JP |
2012-027940 | Feb 2012 | JP |
2012-043267 | Mar 2012 | JP |
2012-053754 | Mar 2012 | JP |
2012-053926 | Mar 2012 | JP |
2012-073873 | Apr 2012 | JP |
2012-509605 | Apr 2012 | JP |
2012-093820 | May 2012 | JP |
2012-123564 | Jun 2012 | JP |
2012-128825 | Jul 2012 | JP |
2013-030050 | Feb 2013 | JP |
2013-058149 | Mar 2013 | JP |
2013-080521 | May 2013 | JP |
2013-542488 | Nov 2013 | JP |
2014-130567 | Jul 2014 | JP |
2014-519109 | Aug 2014 | JP |
2015-153420 | Aug 2015 | JP |
2006-0071353 | Jun 2006 | KR |
2008-0045143 | Apr 2008 | KR |
2008-0054346 | Jun 2008 | KR |
2010 0133246 | Dec 2010 | KR |
2011 0086501 | Jul 2011 | KR |
2013 0099647 | Sep 2013 | KR |
2014 0079110 | Jun 2014 | KR |
20150021977 | Mar 2015 | KR |
WO 2005106637 | Nov 2005 | WO |
WO 2006013485 | Feb 2006 | WO |
WO 2006042309 | Apr 2006 | WO |
WO 2007121557 | Nov 2007 | WO |
WO 2008030976 | Mar 2008 | WO |
WO 2008064142 | May 2008 | WO |
WO 2009155981 | Dec 2009 | WO |
WO 2009158549 | Dec 2009 | WO |
WO 2010013876 | Feb 2010 | WO |
WO 2010090010 | Aug 2010 | WO |
WO 2011024389 | Mar 2011 | WO |
WO 2011024465 | Mar 2011 | WO |
WO 2011093045 | Aug 2011 | WO |
WO 2011105009 | Sep 2011 | WO |
WO 2011115187 | Sep 2011 | WO |
WO 2011121375 | Oct 2011 | WO |
WO 2012037664 | Mar 2012 | WO |
WO 2012096804 | Jul 2012 | WO |
WO 2012114760 | Aug 2012 | WO |
WO 2012150540 | Nov 2012 | WO |
WO 2013169299 | Nov 2013 | WO |
WO 2013169849 | Nov 2013 | WO |
WO 2013169851 | Nov 2013 | WO |
WO 2013169853 | Nov 2013 | WO |
WO 2013169854 | Nov 2013 | WO |
WO 2013169870 | Nov 2013 | WO |
WO 2013169875 | Nov 2013 | WO |
WO 2013169877 | Nov 2013 | WO |
WO 2013169882 | Nov 2013 | WO |
WO 2014105275 | Jul 2014 | WO |
WO 2014105276 | Jul 2014 | WO |
WO 2014105277 | Jul 2014 | WO |
WO 2014105278 | Jul 2014 | WO |
WO 2014105279 | Jul 2014 | WO |
WO 2014129655 | Aug 2014 | WO |
WO 2014149473 | Sep 2014 | WO |
WO 2014200733 | Dec 2014 | WO |
WO 2016200584 | Dec 2016 | WO |
Entry |
---|
Agarwal, “How to Copy and Paste Text on Window Phone 8,” Guiding Tech, http://web.archive.org/web20130709204246/http://www.guidingtech.com/20280/copy-paste-text-windows-phone-8/, Jul. 9, 2013, 10 pages. |
Azundris, “A Fire in the Sky,” http://web.archive.org/web/20140722062639/http://blog.azundrix.com/archives/168-A-fire-in-the-sky.html, Jul. 22, 2014, 8 pages. |
b-log—betriebsraum weblog, “Extremely Efficient Menu Selection: Marking Menus for the Flash Platform,” http://www.betriebsraum.de/blog/2009/12/11/extremely-efficient-menu-selection-marking-for-the-flash-platform, Dec. 11, 2009, 9 pages. |
Clark, “Global Moxie, Touch Means a Renaissance for Radial Menus,” http://globalmoxie.com/blog/radial-menus-for-touch-ui˜print.shtml, Jul. 17, 2012, 7 pages. |
Cohen, Cinemagraphs are Animated Gifs for Adults, http://www.tubefilter.com/2011/07/10/cinemagraph, Jul. 10, 2011, 3 pages. |
CrackBerry Forums, Windows 8 Bezel Control and Gestures, http://wwwforums.crackberry.com/blackberry-playbook-f222/windows-8-bezel-control-gestures-705129/, Mar. 1, 2012, 8 pages. |
Crook, “Microsoft Patenting Multi-Screen, Milti-Touch Gesures,” http://techcrunch.com/2011/08/25/microsoft-awarded-patents-for-multi-screen-multi-touch-gestures/, Aug. 25, 2011, 8 pages. |
cvil.ly—a design bog, Interesting Touch Interactions on Windows 8, http://cvil.ly/2011/06/04/interesting-touch-interactions-on-windows-8/, Jun. 4, 2011, 3 pages. |
Davidson, et al., “Extending 2D Object Arrangement with Pressure-Sensitive Layering Cues”, Proceedings of the 21st Annual ACM Symposium on User Interface Software and Technology, Oct. 19, 2008, 4 pages. |
Dinwiddle, et al., “Combined-User Interface for Computers, Television, Video Recorders, and Telephone, Etc”, ip.com Journal, Aug. 1, 1990. 3 Pages. |
Drinkwater, “Glossary: Pre/Post Alarm Image Buffer,” http://www.networkwebcams.com/ip-camera-learning-center/2008/07/17/glossary-prepost-alarm-image-buffer/, Jul. 17, 2008, 1 page. |
Fenlon, “The Case for Bezel Touch Gestures on Apple's iPad,” http://www.tested.com/tech/tablets/3104-the case-for-bezel-touch-gestures-on-apples-ipad/, Nov. 2, 2011, 6 pages. |
Flixel, “Cinemagraph Pro for Mac”, https://flixel.com/products/mac/cinemagraph-pro, 2014, 7 pages. |
Flock, “Cinemagraphics: What It Looks Like When a Photo Moves,” http://www.washingtonpost.com/blogs/blowpost/post/cinemagraphs-what-it-looks-like-when-a-photo-moves/2011/07-08/gl@AONez3H.blog.html, Jul. 12, 2011, 3 pages. |
Flowplayer, “Slowmotion: Flowplayer,” https://web.archive.org/web/20150226191526/http://flash.flowplayer.org/plugins/streaming/slowmotion.html, Feb. 26, 2015, 4 pages. |
Forlines, et al., “Glimpse: a Novel Input Model for Multi-level Devices”, Chi '05 Extended Abstracts on Human Factors in Computing Systems, Apr. 2, 2005, 4 pages. |
IBM et al., “Pressure-Sensitive Icons”, IBM Technical Disclosure Bulletin, vol. 33, No. 1B, Jun. 1, 1990, 3 pages. |
iCIMS Recruiting Software, “Blackberry Playbook Review,” http://www.tested.com/tech.tablets/5749-blackberry-playbook-review/, 2015, 11 pages. |
Kaaresoja, “Snap-Crackle-Pop: Tactile Feedback for Mobile Touch Screens,” Nokia Research Center, Helsinki, Finland, Proceedings of Eurohaptics vol. 2006, Jul. 3, 2006, 2 pages. |
Kronfli, “HTC Zoe Comes to Goole Play, Here's Everthing You Need to Know,” http://www.knowyourmobile.com/htc/htc-one/19550/what-htc-zoe, Aug. 14, 2014, 5 pages. |
Laurie, “The Power of the Right Click,” http://vlaurie.com/right-click/customize-context-menu.html, 2002-2016, 3 pages. |
McRitchie, “Internet Explorer Right-Click Menus,” http://web.archive.org/web-201405020/http:/dmcritchie.mvps.org/ie/rightie6.htm, May 2, 2014, 10 pages. |
Microsoft, “Use Radial Menus to Display Commands in OneNote for Windows 8,” https://support.office.com/en-us/article/Use-radial-menues-to-display-OneNote-commands-Od75f03f-cde7-493a-a8a0b2ed6f99fbe2, 2016, 5 pages. |
Minsky, “Computational Haptics the Sandpaper System for Synthesizing Texture for a Force-Feedback Display,” Massachusetts Institute of Technology, Jun. 1978, 217 pages. |
Nikon, “Scene Recognition System and Advanced SRS,” http://www.nikonusa.com/en.Learn-And-Explore/Article/ftlzi4rr/Scene-Recognition-System.html, Jul. 22, 2015, 2 pages. |
O'Hara, et al., “Pressure-Sensitive Icons”, ip.com Journal, ip.com Inc., West Henrietta, NY, US, Jun. 1, 1990, 2 Pages. |
Pallenberg, “Wow, the new iPad had gestures.” https://plus.google.com/+SaschaPallenberg/posts/aaJtJogu8ac, Mar. 7, 2012, 2 pages. |
PoliceOne.com, “COBAN Technoligies Pre-Event Buffer & Fail Safe Feature,” http://www.policeone.com/police-products/police-technology/mobile-computures/videos/5955587-COBAN-Technologies-Pre-Event, Nov. 11, 2010, 2 pages. |
Pradeep, “Android App Development—Microsoft Awarded With Patents on Gestures Supported on Windows 8,” http://mspoweruser.com/microsoft-awarded-with-patents-on-gestures-supported-on-windows-8/, Aug. 25, 2011, 16 pages. |
“Quickly Preview Songs in Windows Media Player 12 in Windows 7,” Quickly Preview Songs in Windows Media Player 12 in Windows 7. How-to Geek, Apr. 28, 2010, Web. May 8, 2010, http://web.archive.org/web/20100502013134/http://www.howtogeek.com/howto/16157/quickly-preview-songs-in-windows-media-center-12-in-windows-7>, 6 pages. |
Quinn, et al., “Zoofing! Faster List Selections with Pressure-Zoom-Flick-Scrolling”, Proceedings of the 21st Annual Conference of the Australian Computer-Human Interaction Special Interest Group on Design, Nov. 23, 2009, ACM Press, vol. 411, 8 pages. |
Rekimoto, et al., “PreSense: Interaction Techniques for Finger Sensing Input Devices”, Proceedings of the 16th Annual ACM Symposium on User Interface Software and Technology, Nov. 30, 2003, 10 pages. |
Rekimoto, et al., “PreSensell: Bi-directional Touch and Pressure Sensing Interactions with Tactile Feedback”, Conference on Human Factors in Computing Systems Archive, ACM, Apr. 22, 2006, 6 pages. |
Sony, “Intelligent Scene Recognition,” https://www.sony-asia.com/article/252999/section/product/product/dsc-t77, downloaded on May 20, 2016, 5 pages. |
Stross, “Wearing a Badge, and a Video Camera,” The New York Times, http://www.nytimes.com/2013/04/07/business/wearable-video-cameras-for-police-offers.html? R=0, Apr. 6, 2013, 4 pages. |
Taser, “Taser Axon Body Camera User Manual,” https://www.taser.com/images/support/downloads/product-resourses/axon—body—product—manual.pdf, Oct. 1, 2013, 24 pages. |
Tidwell, “Designing Interfaces,” O'Reilly Media, Inc., USA, Nov. 2005, 348 pages. |
Wikipedia, “AirDrop,”, Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/AirDrop, May 17, 2016, 5 pages. |
Wikipedia, “Cinemagraph,” Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/Cinemagraph, Last Modified Mar. 16, 2016, 2 pages. |
Wikipedia, “Context Menu,” Wikipedia, the free encyclopedia https://en.wikipedia.org/wiki/Context menu, Last Modified May 15, 2016, 4 pages. |
Wikipedia, “HTC One (M7),” Wikipedia, the free encyclopedia, https://en.wikipedia.org/wiki/HTC—One—(M7), Mar. 2013, 20 pages. |
Wikipedia, “Mobile Ad Hoc Network,” Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/Mobile—ad—hoc—network, May 20, 2016, 4 pages. |
Wikipedia, “Pie Menu,” Wikipedia, the free encyclopedia, http://en.wikipedia.org/wiki/Pie—menu, Last Modified Jun. 4, 2016, 3 pages. |
Wikipedia, “Quick Look,” from Wikipedia, the free encyclopedia, https;//en.wikipedia.org/wiki/Quick—Look, Last Modified Jan. 15, 2016, 3 pages. |
Wikipedia, “Sony Xperia Z1”, Wikipedia, the free encyclopedia, https://enwikipedia.org/wiki/Sony—Experia—Z1, Sep. 2013, 10 pages. |
YouTube, “Blackberry Playbook bezel interaction,” https://www.youtube.com/watch?v=YGkzFqnOwXI, Jan. 10, 2011, 2 pages. |
Office Action, dated Dec. 18, 2015, received in Australian Patent Application No. 2013368440, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
Office Action, dated Apr. 5, 2016, received in Korean Patent Application No. 10-2015-7018851, which corresponds with U.S. Appl. No. 14/536,426, 7 pages. |
Office Action, dated Jul. 21, 2016, received in European Patent Application No. 13795391.5, which corresponds with U.S. Appl. No. 14/536,426, 9 pages. |
Office Action, dated Dec. 17, 2015, received in U.S. Appl. No. 14/536,426, 28 pages. |
Final Office Action, dated May 6, 2016, received in U.S. Appl. No. 14/536,426, 23 pages. |
Office Action, dated Jul. 15, 2015, received in Australian Patent Application No. 2013259606, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
Notice of Allowance, dated May 23, 2016, received in Australian Patent Application No. 2013259606, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
Office Action, dated Nov. 18, 2016, received in Australian Patent Application No. 2015101231, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
Decision to Grant, dated Jul. 14, 2016, received in European Patent Application No. 13724100.6, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
Office Action, dated Mar. 4, 2016, received in Japanese Patent Application No. 2015-511644, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
Office Action, dated Feb. 1, 2016, received in Australian Patent Application No. 2013368441, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
Notice of Allowance, dated Mar. 30, 2016, received in Australian Patent Application No. 2013368441, which corresponds with U.S. Appl. No. 14/608,926, 1 page. |
Office Action, dated Apr. 21, 2016, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 6 pages. |
Office Action, dated May 6, 2016, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 6 pages. |
Office Action, dated Mar. 14, 2016, received in Japanese Patent Application No. 2015-549392, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
Office Action, dated May 12, 2016, received in Korean Patent Application No. 10-2015-7018853, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
Office Action, dated Jul. 17, 2015, received in Australian Patent Application No. 2013259613, which corresponds with U.S. Appl. No. 14/536,646, 5 pages. |
Office Action, dated May 31, 2016, received in Australian Patent Application No. 2013259613, which corresponds with U.S. Appl. No. 14/536,646, 4 pages. |
Notice of Allowance, dated Jul. 5, 2016, received in Australian Patent Application No. 2013259613, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
Office Action, dated Nov. 12, 2015, received in European Patent Application No. 13724102.2, which corresponds with U.S. Appl. No. 14/536,646, 6 pages. |
Office Action, dated May 31, 2016, received in European Patent Application No. 13724102.2, which corresponds with U.S. Appl. No. 14/536,646, 5 pages. |
Office Action, dated Feb. 29, 2016, received in Japanese Patent Application No. 2015-511645, which corresponds with U.S. Appl. No. 14/536,646, 5 pages. |
Office Action, dated Aug. 27, 2015, received in Australian Patent Application No. 2013259614, which corresponds with U.S. Appl. No. 14/536,141, 4 pages. |
Office Action, dated Jan. 7, 2016, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 10 pages. |
Office Action, dated Feb. 29, 2015, received in Japanese Patent Application No. 2015-511646, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
Office Action, dated Jan. 29, 2016, received in Australian Patent Application No. 2013368443, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
Notice of Allowance, dated Mar. 11, 2016, received in Australian Patent Application No. 2013368443, which corresponds with U.S. Appl. No. 14/536,141, 2 pages. |
Certificate of Grant, dated Jul. 7, 2016, received in Australian Patent Application No. 2013368443, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
Office Action, dated Jul. 4, 2016, received in Japanese Patent Application No. 2015-549393, which corresponds with U.S. Appl. No. 14/536,141, 4 pages. |
Office Action, dated Apr. 5, 2016, received in Korean Patent Application No. 10-2015-7018448, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
Office Action, dated Aug. 1, 2016, received in U.S. Appl. No. 14/536,203, 14 pages. |
Office Action, dated Jul. 9, 2015, received in Australian Patent Application No. 2013259630, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
Notice of Allowance, dated Jun. 15, 2016, received in Australian Patent Applicatin No. 2013259630, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
Office Action, dated Nov. 11, 2015, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
Office Action, dated May 31, 2016, received in European Patent Application No. 13724104.8, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
Office Action, dated Feb. 15, 2016, received in Japanese Patent Application No. 2015-511650, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
Office Action, dated Dec. 4, 2015, received in Korean Patent Application No. 2014-7034520, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
Office Action, dated Jul. 22, 2016, received in European Offfice Action No. 13798465.4, which corresponds with U.S. Appl. No. 14/608,965, 8 pages. |
Office Action, dated Aug. 10, 2015, received in Australian Patent Application No. 2013259637, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
Notice of Allowance, dated Jun. 28, 2016, received in Australian Patent Application No. 2013259637, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
Office Action, dated Jan. 29, 2016, received in Japanese Patent Application No. 2015-511652, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
Office Action, dated Dec. 4, 2015, received in Korean Patent Application No. 2014-7034530, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
Office Action, dated Aug. 18, 2015, received in Australian Patent Application No. 2013259642, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
Office Action, dated Jul. 25, 2016, received in Australian Patent Application No. 2013259642, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
Office Action, dated Jan. 7, 2016, received in European Patent Application No. 13724107.1, which corresponds with U.S. Appl. No. 14/536,291, 11 pages. |
Office Action, dated Mar. 8, 2016, recieved in Japanese Application No. 2015-511655, which corresponds with U.S. Appl. No. 14/536,291, 4 pages. |
Office Action, dated Jan. 15, 2016, received in Australian Patent Application No. 2013368445, which corresponds with U.S. Appl. No. 14/608,985, 3 pages. |
Office Action, dated Apr. 25, 2016, received in Japanese Patent Application No. 2015-550384, which corresponds with U.S. Appl. No. 14/608,985, 4 pages |
Office Action, dated Mar. 31, 2016, recieved in U.S. Appl. No. 14/864,737 , 17 pages. |
Notice of Allowance, dated Jul. 1, 2016, received in Chinese Patent Application No. 201620214376.7, which correresponds with U.S. Appl. No. 14/864,737, 3 pages. |
Certificate of Registration, dated Jun. 20, 2016, received in German Patent Application No. 202016001845.1, which correresponds with U.S. Appl. No. 14/864,737, 3 pages. |
Office Action, dated Apr. 5, 2016, received in Danish Patent Application No. 201500577, which corresponds with U.S. Appl. No. 14/864,737, 7 pages. |
Office Action, dated Jun. 27, 2016, received in U.S. Appl. No. 14/866,981, 22 pages. |
Office Action, dated May 10, 2016, received in Australian Patent Application No. 2016100254, which corresponds with U.S. Appl. No. 14/866,981, 6 pages. |
Notice of Allowance, dated Jul. 27, 2016, received in Chinese Patent Application No. 201620176169.7, which corresponds with U.S. Appl. No. 14/866,981, 3 pages. |
Certificate of Registration, dated Jun. 20, 2016, received in German Patent Application No. 202016001514.2, which corresponds with U.S. Appl. No. 14/864,737, 3 pages. |
Office Action, dated Mar. 18, 2016, received in Danish Patent Application No. 2016100254, which corresponds with U.S. Appl. No. 14/866,981, 9 pages. |
Office Action, dated May 19, 2016, received in Australian Patent Application No. 2016100251, which corresponds with U.S. Appl. No. 14/866,159, 5 pages. |
Office Action, dated Mar. 9, 2016, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 11 pages. |
Certificate of Registration, dated Jun. 30, 2016, received in German Patent Application No. 20201600156.9, which corresponds with U.S. Appl. No. 14/868,078, 3 pages. |
Office Action, dated Mar. 30, 2016, received in Australian Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 9 pages. |
Office Action, dated May 9, 2016, received in U.S. Appl. No. 14/863,432, 26 pages. |
Office Action, dated Apr. 4, 2016, received in Danish Patent Application No. 201500582, which corresponds with U.S. Appl. No. 14/863,432, 10 pages. |
Office Action, dated Mar. 22, 2016, received in Danish Patent Application No. 201500576, which corresponds with U.S. Appl. No. 14/866,511, 10 pages. |
Notice of Allowance, dated Jun. 8, 2016, received in Danish Patent Application No. 201500576, which corresponds with U.S. Appl. No. 14/866,511, 2 pages. |
Office Action, dated Mar. 28, 2016, received in U.S. Appl. No. 14/869,899, 17 pages. |
Office Action, dated Jun. 28, 2016, received in U.S. Appl. No. 14/869,899, 5 pages. |
Office Action, dated Feb. 3, 2016, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 9 pages. |
Office Action, dated Mar. 4, 2016, received in U.S. Appl. No. 14/866,992, 30 pages. |
Final Office Action, dated Jul. 29, 2016, received in U.S. Appl. No. 14/866,992, 35 pages. |
Office Action, dated Mar. 18, 2016, received in Danish Patent Application No. 201500593, which corresponds with U.S. Appl. No. 14/866,992, 10 pages. |
Office Action, dated Jun. 27, 2016, recieved in Danish Patent Application No. 201500593, which corresponds with U.S. Appl. No. 14/866,992, 7 pages. |
Office Action, dated Nov. 30, 2015, received in U.S. Appl. No. 14/845,217, 24 pages. |
Final Office Action, dated Apr. 22, 2016, recieved in U.S. Appl. No. 14/845,217, 36 pages. |
Office Action, dated Feb. 3, 2016, received in U.S. Appl. No. 14/856,517, 36 pages. |
Final Office Action, dated Jul. 13, 2016, received in U.S. Appl. No. 14/856,517, 30 pages. |
Office Action, dated Feb. 11, 2016, received in U.S. Appl. No. 14/856,519, 34 pages. |
Final Office Action, dated Jul. 15, 2016, received in U.S. Appl. No. 14/856,519, 31 pages. |
Office Action, dated Feb. 1, 2016, received in U.S. Appl. No. 14/857,645, 15 pages. |
Final Office Action, dated Jun. 16, 2016, received in U.S. Appl. No. 14/857,645, 12 pages. |
Office Action, dated Jan. 25, 2016, received in U.S. Appl. No. 14/864,580, 29 pages. |
Notice of Allowance, dated May 23, 2016, received in U.S. Appl. No. 14/864,580, 9 pages. |
Corrected Notice of Allowability, dated Jun. 16, 2016, received in U.S. Appl. No. 14/864,580, 2 pages. |
Notice of Allowance, dated Aug. 4, 2016, received in U.S. Appl. No. 14/864,580, 9 pages. |
Office Action, dated Apr. 8, 2016, received in Danish Patent Application No. 201500584, which corresponds with U.S. Appl. No. 14/864,580, 9 pages. |
Office Action, dated Apr. 19, 2016, received in U.S. Appl. No. 14/864,627, 9 pages. |
Office Action, dated Apr. 8, 2016, received in Danish Patent Application No. 201500585, which corresponds with U.S. Appl. No. 14/864,627, 9 pages. |
Office Action, dated Mar. 29, 2016, received in U.S. Appl. No. 14/866,361, 22 pages. |
Notice of Allowance, dated Jul. 19, 2016, received in U.S. Appl. No. 14/866,361, 8 pages. |
Office Action, dated Jun. 10, 2016, received in Australian Patent Application No. 2016100292, which corresponds with U.S. Appl. No. 14/866,361, 4 pages. |
Notice of Allowance/Grant, dated Jul. 1, 2016, received in Chinese Patent Application No. 201620251706.X, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
Certificate of Registration, dated Jun. 24, 2016, received in German Patent Application No. 202016001819.2, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
Office Action, dated Apr. 7, 2016, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 10 pages. |
Office Action, dated Mar. 22, 2016, received in Danish Patent Application No. 201500587, which corresponds with U.S. Appl. No. 14/866,987, 8 pages. |
Notice of Allowance, dated Jun. 10, 2016, received in Danish Patent Application No. 201500587, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
Certificate of Exam, dated Jul. 21, 2016, received in Australian Patent Application No. 2016100652, which corresponds with U.S. Appl. No. 14/866,989, 1 page. |
Office Action, dated Apr. 1, 2016, received in Danish Patent Application No. 201500589, which corresponds with U.S. Appl. No. 14/866,989, 8 pages. |
Notice of Allowance, dated Jun. 10, 2016, received in Danish Patent Application No. 201500589, which corresponds with U.S. Appl. No. 14/866,989, 2 pages. |
Office Action, dated Apr. 11, 2016, received in U.S. Appl. No. 14/871,236, 23 pages. |
Office Action, dated Jun. 28, 2016, received in U.S. Appl. No. 14/871,236, 21 pages. |
Office Action, dated Apr. 8, 2016, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 12 pages. |
Office Action, dated May 26, 2016, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 14 pages. |
Office Action, dated Apr. 6, 2016, received in Danish Patent Application No. 201500596, which corresponds with U.S. Appl. No. 14/870,882, 7 pages. |
Office Action, dated Jun. 9, 2016, received in Danish Patent Application No. 201500596, which corresponds with U.S. Appl. No. 14/870,882, 9 pages. |
Office Action, dated Apr. 7, 2016, received in Danish Patent Application No. 201500597, which corresponds with U.S. Appl. No. 14/871,227, 7 pages. |
Notice of Allowance, dated Jun. 21, 2016, received in Danish Patent Application No. 201500597, which corresponds with U.S. Appl. No. 14/871,227, 2 pages. |
Office Action, dated Apr. 18, 2016, received in Danish Patent Application No. 201500601, which corresponds with U.S. Appl. No. 14/871,336, 8 pages. |
Notice of Allowance, dated Apr. 18, 2016, received in Danish Patent Application No. 201500600, which corresponds with U.S. Appl. No. 14/871,462, 7 pages. |
Office Action, dated Apr. 29, 2016, received in U.S. Appl. No. 14/867,823, 28 pages. |
Office Action, dated Mar. 18, 2016, received in Danish Patent Application No. 201500594, which corresponds with U.S. Appl. No. 14/867,823, 10 pages. |
Office Action, dated May 10, 2016, received in U.S. Appl. No. 14/867,892, 28 pages. |
Office Action, dated Mar. 21, 2016, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 9 pages. |
Office Action, dated May 23, 2016, received in Australian Patent Application No. 2016100253, which corresponds with U.S. Appl. No. 14/867,990, 5 pages. |
Certificate of Registration, dated Jun. 16, 2016, received in German Patent No. 202016001489.8, which corresponds with U.S. Appl. No. 14/867,990, 3 pages. |
Office Action, dated Mar. 18, 2016, received in Danish Patent Application No. 201500581, which corresponds with U.S. Appl. No. 14/867,990, 9 pages. |
International Search Report and Written Opinion dated May 26, 2014, received in International Application No. PCT/US2013/040053, which corresponds to U.S. Appl. No. 14/535,671, 32 pages. |
International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040053, which corresponds to U.S. Appl. No. 14/535,671, 26 pages. |
International Search Report and Written Opinion dated Apr. 7, 2014, received in International Application No. PCT/US2013/069472, which corresponds to U.S. Appl. No. 14/608,895, 24 pages. |
International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069472, which corresponds with U.S. Appl. No. 14/608,895, 18 pages. |
International Search Report and Written Opinion dated Aug. 7, 2013, received in International Application No. PCT/US2013/040054, which corresponds to U.S. Appl. No. 14/536,235, 12 pages. |
International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040054, which corresponds to U.S. Appl. No. 14/536,235, 11 pages. |
International Search Report and Written Opinion dated Aug. 7, 2013, received in International Application No. PCT/US2013/040056, which corresponds to U.S. Appl. No. 14/536,367, 12 pages. |
International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040056, which corresponds to U.S. Appl. No. 14/536,367, 11 pages. |
Extended European Search Report, dated Nov. 6, 2015, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 7 pages. |
International Search Report and Written Opinion dated Aug. 6, 2013, received in International Application No. PCT/US2013/040058, which corresponds to U.S. Appl. No. 14/536,426, 12 pages. |
International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040058, which corresponds to U.S. Appl. No. 14/536,426, 11 pages. |
International Search Report and Written Opinion dated Feb. 5, 2014, received in International Application No. PCT/US2013/040061, which corresponds to U.S. Appl. No. 14/536,464, 30 pages. |
International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040061, which corresponds to U.S. Appl. No. 14/536,464, 26 pages. |
International Search Report and Written Opinion dated May 8, 2014, received in International Application No. PCT/US2013/040067, which corresponds to U.S. Appl. No. 14/536,644, 45 pages. |
International Preliminary Report dated Nov. 20, 2014, received in International Application No. PCT/US2013/040067, which corresponds to U.S. Appl. No. 14/536,644, 36 pages. |
International Search Report and Written Opinion dated Mar. 12, 2014, received in International Application No. PCT/US2013/069479, which corresponds to U.S. Appl. No. 14/608,926, 14 pages. |
International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069479, which corresponds with U.S. Appl. No. 14/608,926, 11 pages. |
International Search Report and Written Opinion dated Aug. 7, 2013, received in International Application No. PCT/US2013/040070, which corresponds to U.S. Appl. No. 14/535,646, 12 pages. |
International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040070, which corresponds to U.S. Appl. No. 14/536,646, 10 pages. |
International Search Report and Written Opinion dated Apr. 7, 2014, received in International Application No. PCT/US2013/040072, which corresponds to U.S. Appl. No. 14/536,141, 38 pages. |
International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/US2013/040072, which corresponds to U.S. Appl. No. 14/536,141, 32 pages. |
International Search Report and Written Opinion dated Apr. 7, 2014, received in International Application No. PCT/US2013/069483, which corresponds to U.S. Appl. No. 14/608,942, 18 pages. |
International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Application No. PCT/US2013/069483, which corresponds to U.S. Appl. No. 14/608,942, 13 pages. |
International Search Report and Written Opinion dated Mar. 3, 2014, received in International Application No. PCT/US2013/040087, which corresponds to U.S. Appl. No. 14/536,166, 35 pages. |
International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013/040087, which corresponds to U.S. Appl. No. 14/536,166, 29 pages. |
International Search Report and Written Opinion dated Aug. 7, 2013, received in International Application No. PCT/US2013/040093, which corresponds to U.S. Appl. No. 14/536,203, 11 pages. |
International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013040093, which corresponds to U.S. Appl. No. 14/536,203, 9 pages. |
International Search Report and Written Opinion dated Jul. 9, 2014, received in International Application No. PCT/US2013/069484, which corresponds to U.S. Appl. No. 14/608,965, 17 pages. |
International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Application No. PCT/US2013/069484, which corresponds with U.S. Appl. No. 14/608,965, 12 pages. |
International Search Report and Written Opinion dated Feb. 5, 2014, received in International Application No. PCT/US2013/040098, which corresponds to U.S. Appl. No. 14/536,247, 35 pages. |
International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013/040098, which corresponds to U.S. Appl. No. 14/536,247, 27 pages. |
International Search Report and Written Opinion dated Jan. 27, 2014, received in International Application No. PCT/US2013/040101, which corresponds to U.S. Appl. No. 14/536,267, 30 pages. |
International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013/040101, which corresponds to U.S. Appl. No. 14/536,267, 24 pages. |
International Search Report and Written Opinion dated Jan. 8, 2014, received in International Application No. PCT/US2013/040108, which corresponds to U.S. Appl. No. 14/536,291, 30 pages. |
International Preliminary Report on Patentability dated Nov. 20, 2014, received in International Application No. PCT/2013/040108, which corresponds to U.S. Appl. No. 14/536,291, 25 pages. |
International Search Report and Written Opinion dated Jun. 2, 2014, received in International Application No. PCT/US2013/069486, which corresponds to U.S. Appl. No. 14/608,985, 7 pages. |
International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Application No. PCT/US2013/069486, which corresponds with U.S. Appl. No. 14/608,985, 19 pages. |
International Search Report and Written Opinion dated Mar. 6, 2014, received in International Application No. PCT/US2013/069489, which corresponds with U.S. Appl. No. 14/609,006, 12 pages. |
International Preliminary Report on Patentability, dated Jun. 30, 2015, received in International Patent Application No. PCT/US2013/069489, which corresponds with U.S. Appl. No. 14/609,006, 10 pages. |
International Search Report and Written Opinion, dated Apr. 25, 2016, received in International Patent Application No. PCT/US2016/018758, which corresponds with U.S. Appl. No. 14/866,159, 15 pages. |
International Search Report and Written Opinion, dated Jul. 21, 2016, received in International Patent Application No. PCT/US2016/019913, which corresponds with U.S. Appl. No. 14/868,078, 16 pages. |
Angelov, “Sponsor Flip Wall With Jquery & CSS”, Tutorialzine. N.p., Mar. 24, 2010. Web. http://tutorialzine.com/2010/03/sponsor-wall-slip-jquery-css/, Mar. 24, 2010, 8 pages. |
Anonymous, “Nokia 808 PureView screenshots”, retrieved from Internet; no URL, Nov. 12, 2012, 8 pages. |
Anonymous, “Nokia 808 PureView User Guide,” http://download-fds.webapps.microsoft.com/supportFiles/phones/files/pdf—guides/devices/808/Nokia—808—UG—en—APAC.pdf, Jan. 1, 2012, 144 pages. |
Anonymous, “Notifications, Android 4.4 and Lower”, Android Developers, https://developer.android.com/design/patterns/notifications—k.html, May 24, 2015, 9 pages. |
Bolluyt, “5 Apple Watch Revelations from Apple's New WatchKit”, http://www.cheatsheet.com/tecnology/5-apple-watch-revelations-from-apples-new-watchkit.html/?a=viewall, Nov. 22, 2014, 3 pages. |
Dzyre, “10 Android Notification Features You Can Fiddle With”, http://www.hongkiat.com/blog/android-notification-features, Mar. 10, 2014, 10 pages. |
Elliot, “Mac System 7”, YouTube. Web. Mar. 8, 2017, http://www.youtube.com/watch?v=XLv22hfuuik, Aug. 3, 2011, 1 page. |
Farshad, “SageThumbs-Preview and Convert Pictures From Windows Context Menu”, https://web.addictivetips.com/windows-tips/sagethumbs-preview-and-convert-photos-from-windows-context-menu, Aug. 8, 2011, 5 pages. |
Flaherty, “Is Apple Watch's Pressure-Sensitive Screen a Bigger Deal Than the Gadget Itself?”, http://www.wired.com/2014/09/apple-watchs-pressure-sensitive-screen-bigger-deal-gadget, Sep. 15, 2014, 3 pages. |
Gardner, “Recenz—Recent Apps in One Tap”, You Tube, https://www.youtube.com/watch?v-qailSHRgsTo, May 15, 2015, 1 page. |
Gonzalo et al., “Zliding: Fluid Zooming and Sliding for High Precision Parameter Manipulation”, Department of Computer Science, University of Toronto, Seattle, Washington, Oct. 23, 2005, 10 pages. |
Grant, “Android's Notification Center”, https://www.objc.io/issues/11-android/android-notifications, Apr. 30, 2014, 26 pages. |
iPhoneOperator, “Wasser Liveeffekt fur Homescreen & Lockscreen—Aquaboard (Cydia)”, http://www.youtube.com/watch?v=fG9YMF-mBOQ, Sep. 22, 2012, 3 pages. |
iPodHacks 142: “Water Ripple Effects on the Home and Lock Screen: AquaBoard Cydia Tweak Review”, YouTube, https://www.youtube.com.watch?v-Auu—uRaYHJs, Sep. 24, 2012, 3 pages. |
Kiener, “Force Touch on iPhone”, https://www.youtube.com/watch?v=CEMmnsU5fC8, Aug. 4, 2015, 4 pages. |
Kost, “LR3-Deselect All Images But One”, Julieanne Kost's Blog, blogs.adobe.com/jkost/2011/12/Ir3-deselect-all-images-but-one.html, Dec. 22, 2011, 1 page. |
Kumar, “How to Enable Ripple Effect on Lock Screen of Galaxy S2”, YouTube, http, http://www.youtube.com/watch?v+B9-4M5abLXA, Feb. 12, 2013, 3 pages. |
Matthew, “How to Preview Photos and Images From Right-Click Context Menue in Windows [Tip]”, https://dottech.org/159009/add-image-preview-in-windows-context-menu-tip, Jul. 4, 2014, 5 pages. |
Microsoft, “Lumia—How to Personalize Your Start Screen”, https://www.youtube.com/watch?v=6GI5Z3TrSEs, Nov. 11, 2014, 3 pages. |
Mitroff, “Google Android 5.0 Lollipop,” http://www.cnet.com/products/google-android-5-0-lollipop, Mar. 12, 2015, 5 pages. |
Mohr, “Do Not Disturb—The iPhone Feature You Should Be Using”, http.www.wonderoftech.com/do-not-disturb-iphone, Jul. 14, 2014, 30 pages. |
Nacca, “NiLS Lock Screen Notifications / Floating Panel—Review”, https://www.youtube.com/watch?v=McT4QnS9TDY, Feb. 3, 2014, 4 pages. |
Phonebuff, “How to Pair Bluetooth on the iPhone”, https://www.youtube.com/watch?v=LudNwEar9A8, Feb. 8, 2012, 3 pages. |
VGJFeliz, “How to Master Android Lollipop Notifications in Four Minutes!”, https://www.youtube.com/watch?v=S-zBRG7GJgs, Feb. 8, 2015, 5 pages. |
Office Action, dated Mar. 15, 2017, received in U.S. Appl. No. 14/535,671, 13 pages. |
Office Action, dated Oct. 18, 2016, received in Australian Patent Application No. 2013368440, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
Notice of Allowance, dated Dec. 20, 2016, received in Australian Patent Application No. 2013368440, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
Office Action, dated Sep. 13, 2016, received in Japanese Patent Application No. 2015-547948, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
Patent, dated May 12, 2017, received in Japanese Patent Application No. 2015547948, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
Office Action, dated Feb. 24, 2017, received in Korean Patent Application No. 10-2015-7018851, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
Office Action, dated Apr. 5, 2017, received in U.S. Appl. No. 14/536,367, 16 pages. |
Certificate of Grant, dated Sep. 15, 2016, received in Australian Patent Australian Patent Application No. 2013259606, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
Office Action, dated May 15, 2017, received in Australian Patent Application No. 2016216580, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
Letters Patent, dated Aug. 10, 2016, received in European Patent Application No. 13724100.6, which corresponds with U.S. Appl. No. 14/536,426, 1 page. |
Office Action, dated Jan. 20, 2017, received in European Patent Application No. 15183980.0, which corresponds with U.S. Appl. No. 14/536,426, 5 pages. |
Office Action, dated Feb. 6, 2017, received in Japanese Patent Application No. 2015-511644, which corresponds with U.S. Appl. No. 14/536,426, 6 pages. |
Office Action, dated Mar. 9, 2017, received in U.S. Appl. No. 14/536,464, 21 pages. |
Office Action, dated Jan. 3, 2017, received in Australian Patent Application No. 2016201451, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
Office Action, dated May 4, 2017, received in Chinese Patent Application No. 201380068414.1, which corresponds with U.S. Appl. No. 14/608,926, 5 pages. |
Office Action, dated Nov. 11, 2016, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 6 pages. |
Notice of Allowance, dated Jan. 17, 2017, received in Japanese Patent Application No. 2015-549392, which corresponds with U.S. Appl. No. 14/608,926, 2 pages. |
Patent, dated Feb. 17, 2017, received in Japanese Patent Application No. 2015-549392, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
Notice of Allowance, dated Mar. 31, 2017, received in Korean Patent Application No. 2015-7018853, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
Office Action, dated Dec. 1, 2016, received in Chinese Patent Application No. 2013800362059, which corresponds with U.S. Appl. No. 14/536,646, 3 pages. |
Notice of Allowance, dated Jan. 4, 2017, received in European Patent Application No. 13724102.2, which corresponds with U.S. Appl. No. 14/536,646, 5 pages. |
Patent, dated May 26, 2017, received in European Patent Application No. 13724102.2, which corresponds with U.S. Appl. No. 14/536,646, 1 page. |
Notice of Allowance, dated Dec. 22, 2016, received in Japanese Patent Application No. 2015-511645, which corresponds with U.S. Appl. No. 14/536,646, 2 pages. |
Office Action, dated Apr. 3, 2017, received in U.S. Appl. No. 14/536,141, 11 pages. |
Office Action, dated Mar. 3, 2017, received in Chinese Patent Application No. 201380035893.7, which corresponds with U.S. Appl. No. 14/536,646, 8 pages. |
Notice of Allowance, dated Aug. 15, 2016, received in Australian Patent Application No. 2013259614, which corresponds with U.S. Appl. No. 14/536,141, 1 page. |
Office Action, dated Aug. 31, 2016, received in European Patent Application No. 13726053.5, which corresponds with U.S. Appl. No. 14/536,141, 10 pages. |
Office Action, dated Oct. 25, 2016, received in Japanese Patent Application No. 2015-511646, which corresponds with U.S. Appl. No. 14/536,141, 6 pages. |
Office Action, dated Dec. 8, 2016, received in U.S. Appl. No. 14/608,942, 9 pages. |
Notice of Allowance, dated May 12, 2017, received in U.S. Appl. No. 14/608,942, 10 pages. |
Office Action, dated Mar. 29, 2017, received in Australian patent Application No. 2016201303, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
Office Action, dated Oct. 7, 2016, received in European Patent Application No. 13798464.7, which corresponds with U.S. Appl. No. 14/608,942, 7 pages. |
Notice of Allowance, dated May 12, 2017, received in Japanese Patent Application No. 2015-549393, which corresponds with U.S. Appl. No. 14/608,942, 5 pages. |
Office Action, dated Feb. 24, 2017, received in Korean Patent Application No. 2015-7018448, which corresponds with U.S. Appl. No. 14/608,942, 4 pages. |
Notice of Allowance, dated Feb. 1, 2017, received in U.S. Appl. No. 14/536,203, 9 pages. |
Certificate of Grant, dated Oct. 21, 2016, received in Australian Patent Application No. 2013259630, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
Certificate of Patent, dated Sep. 9, 2016, received in Japanese Patent Application No. 2015-511650, which corresponds with U.S. Appl. No. 14/536,203, 3 pages. |
Notice of Allowance, dated Sep. 1, 2016, received in Korean Patent Application No. 2014-7034520, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
Office Action, dated Feb. 6, 2017, received in Korean Patent Application No. 2016-7033834, which corresponds with U.S. Appl. No. 14/536,203, 4 pages. |
Office Action, dated Oct. 20, 2016, received in U.S. Appl. No. 14/536,247, 10 pages. |
Final Office Action, dated Mar. 24, 2017, received in U.S. Appl. No. 14/536,247, 14 pages. |
Office Action, dated Mar. 24, 2017, received in U.S. Appl. No. 14/536,267, 12 pages. |
Certificate of Grant, dated Oct. 21, 2016, received in Australian Patent Application No. 2013259637, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
Office Action, dated Mar. 24, 2017, received in Australian Patent Application No. 2016204411, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
Office Action, dated Dec. 9, 2016, received in Chinese Patent Application No. 2016120601564130, which corresponds with U.S. Appl. No. 14/536,267, 4 pages. |
Notice of Allowance, dated Sep. 26, 2016, received in Japanese Patent Application No. 2015-511652, which corresponds with U.S. Appl. No. 14/536,267, 5 pages. |
Office Action, dated Mar. 3, 2017, received in Japanese Patent Application No. 2016-125839, which corresponds with U.S. Appl. No. 14/536,267, 6 pages. |
Notice of Allowance, dated Sep. 1, 2016, received in Korean Patent Application No. 2014-7034530, which corresponds with U.S. Appl. No. 14/536,267, 3 pages. |
Office Action, dated Jan. 5, 2017, received in Korean Patent Application No. 2016-7029533, which corresponds with U.S. Appl. No. 14/536,267, 2 pages. |
Office Action, dated Apr. 7, 2017, received in U.S. Appl. No. 14/536,291, 11 pages. |
Office Action, dated Aug. 10, 2016, received in Australian Patent Application No. 2013259642, which corresponds with U.S. Appl. No. 14/536,291, 4 pages. |
Innovation Patent, dated Sep. 1, 2016, received in Australian Patent Application No. 2016101481, which corresponds with U.S. Appl. No. 14/536,291, 1 page. |
Office Action, dated Sep. 29, 2016, received in Australian Patent Application No. 2016101481, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
Office Action, dated Aug. 22, 2016, received in European Patent Application No. 13724107.1, which corresponds with U.S. Appl. No. 14/536,291, 7 pages. |
Office Action, dated Mar. 23, 2017, received in European Patent Application No. 13724107.1, which corresponds with U.S. Appl. No. 14/536,291, 8 pages. |
Final Office Action, dated Dec. 22, 2016, received in Japanese Patent Application No. 2015-511655, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
Notice of Allowance, dated Jan. 18, 2017, received in Australian Patent Application No. 2013368445, which corresponds with U.S. Appl. No. 14/608,985, 3 pages. |
Office Action, dated Jul. 25, 2016, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 8 pages. |
Office Action, dated Feb. 27, 2017, received in European Patent Application No. 13811032.5, which corresponds with U.S. Appl. No. 14/608,985, 6 pages. |
Notice of Allowance, dated Jan. 24, 2017, received in Japanese Patent Application No. 2015-550384, which corresponds with U.S. Appl. No. 14/608,985, 5 pages. |
Patent, dated Feb. 24, 2017, received in Japanese Patent Application No. 2015550384, which corresponds with U.S. Appl. No. 14/608,985, 2 pages. |
Office Action, dated Nov. 4, 2016, received in Korean Patent Application No. 10-2015-7019984, which corresponds with U.S. Appl. No. 14/608,985, 8 pages. |
Office Action, dated Mar. 24, 2017, received in U.S. Appl. No. 14/609,006, 13 pages. |
Office Action, dated Apr. 19, 2017, received in U.S. Appl. No. 14/536,296, 12 pages. |
Office Action, dated Jan. 19, 2017, received in U.S. Appl. No. 14/609,042, 12 pages. |
Notice of Allowance, dated Feb. 27, 2017, received in U.S. Appl. No. 14/864,737, 9 pages. |
Patent, dated Aug. 3, 2016, received in Chinese Patent Application No. 201620214376.7, which corresponds with U.S. Appl. No. 14/864,737, 5 pages. |
Intention to Grant, dated Aug. 2, 2016, received in Danish Patent Application No. 201500577, which corresponds with U.S. Appl. No. 14/864,737, 2 pages. |
Office Action, dated May 15, 2017, received in Japanese Patent Application No. 2016-558331, which corresponds with U.S. Appl. No. 14/864,737, 5 pages. |
Office Action, dated May 18, 2017, received in Dutch Patent Application No. 2016452, which corresponds with U.S. Appl. No. 14/864,737, 22 pages. |
Notice of Allowance, dated Oct. 24, 2016, received in U.S. Appl. No. 14/866,981, 7 pages. |
Notice of Allowance, dated Feb. 10, 2017, received in U.S. Appl. No. 14/866,981, 5 pages. |
Patent, dated Nov. 2, 2016, received in Australian Patent Application No. 2016100254, which corresponds with U.S. Appl. No. 14/866,981, 1 page. |
Patent, dated Sep. 28, 2016, received in Chinese Patent Application No. 201620176169.7, which corresponds with U.S. Appl. No. 14/866,981, 4 pages. |
Office Action, dated Dec. 5, 2016, received in Danish Patent Application No. 201500575, which corresponds with U.S. Appl. No. 14/866,981, 3 pages. |
Office Action, dated Jul. 5, 2016, received in Chinese Patent Application No. 201620186008.6, which corresponds with U.S. Appl. No. 14/866,159, 3 pages. |
Certificate of Registration, dated Jun. 16, 2016, received in German Patent No. 202016001483.9, which corresponds with U.S. Appl. No. 14,866,159, 3 pages. |
Office Action, dated Sep. 27, 2016, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 4 pages. |
Office Action, dated Mar. 14, 2017, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 5 pages. |
Innovation (Unexamined) Patent, dated Aug. 4, 2016, received in Australian Patent Application No. 2016101201, which corresponds with U.S. Appl. No. 14/686,078, 1 page. |
Office Action, dated Oct. 12, 2016, received in Australian Patent Application No. 2016101201, which corresponds with U.S. Appl. No. 14/686,078, 3 pages. |
Notice of Allowance, dated Oct. 1, 2016, received in Chinese Patent Application No. 201620175847.8, which corresponds with U.S. Appl. No. 14/686,078, 1 page. |
Office Action, dated Sep. 2, 2016, received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 4 pages. |
Notice of Allowance, dated Jan. 30, 2017, received in received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 2 pages. |
Notice of Allowance, dated May 2, 2017, received in received in Danish Patent Application No. 201500588, which corresponds with U.S. Appl. No. 14/868,078, 2 pages. |
Office Action, dated May 18, 2017, received in Dutch Patent Application No. 2016376, which corresponds with U.S. Appl. No. 14/868,078, 15 pages. |
Notice of Allowance, dated Nov. 14, 2016, received in U.S. Appl. No. 14/863,432, 7 pages. |
Notice of Allowance, dated Apr. 27, 2017, received in U.S. Appl. No. 14/863,432, 7 pages. |
Office Action, dated Aug. 19, 2016, received in Australian Patent Application No. 2016100647, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
Notice of Allowance, dated Jan. 12, 2017, received in Chinese Patent Application No. 201620470063.8, which corresponds with U.S. Appl. No. 14/863,432, 1 page. |
Office Action and Additional Search Report, dated Oct. 7, 2016, received in Danish Patent Application No. 201500582, which corresponds with U.S. Appl. No. 14/863,432, 6 pages. |
Office Action, dated May 18, 2017, received in Dutch Patent Application No. 2016801, which corresponds with U.S. Appl. No. 14/863,432, 34 pages. |
Office Action, dated Oct. 13, 2016, received in U.S. Appl. No. 14/866,511, 27 pages. |
Final Office Action, dated Jan. 27, 2017, received in U.S. Appl. No. 14/866,511, 26 pages. |
Patent, dated Aug. 8, 2016, received in Australian Patent Application 2016100653, corresponds with U.S. Appl. No. 14/866,511, 1 page. |
Notice of Allowance, dated Jan. 12, 2017, received in Chinese Patent Application No. 201620470281.1, which corresponds with U.S. Appl. No. 14/866,511, 1 page. |
Patent, dated Jan. 23, 2017, received in Danish Patent Application No. 201500576, which corresponds with U.S. Appl. No. 14/866,511, 3 pages. |
Office Action, dated Jun. 9, 2017, received in Japanese Patent Application No. 2016558214, which corresponds with U.S. Appl. No. 14/866,511, 6 pages. |
Final Office Action, dated Sep. 2, 2016, received in U.S. Appl. No. 14/869,899, 22 pages. |
Notice of Allowance, dated Feb. 28, 2017, received in U.S. Appl. No. 14/869,899, 9 pages. |
Innovation (Unexamined) Patent, dated Aug. 25, 2016, received in Australian Patent Application No. 2016101438, which corresponds with U.S. Appl. No. 14/869,899, 1 page. |
Certificate of Examination, dated Oct. 11, 2016, received in Australian Patent Application No. 2016101438, which corresponds with U.S. Appl. No. 14/869,899, 1 page. |
Office Action, dated Oct. 7, 2016, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 6 pages. |
Office Action, dated Nov. 22, 2016, received in Danish Patent Application No. 201670594, which corresponds with U.S. Appl. No. 14/869,899, 9 pages. |
Office Action, dated Apr. 13, 2017, received in U.S. Appl. No. 14/866,992, 34 pages. |
Innovation Patent, dated Sep. 22, 2016, received in Australian Patent Application No. 2016101418, which corresponds with U.S. Appl. No. 14/866,992, 1 page. |
Office Action, dated Nov. 22, 2016, received in Australian Patent Application No. 2016101418, which corresponds with U.S. Appl. No. 14/866,992, 7 pages. |
Office Action, dated Feb. 7, 2017, received in Australian Patent Application No. 2016101418, which corresponds with U.S. Appl. No. 14/866,992, 5 pages. |
Office Action, dated Feb. 6, 2017, received in Danish Patent Application No. 201500593, which corresponds with U.S. Appl. No. 14/866,992, 4 pages. |
Notice of Allowance, dated Aug. 26, 2016, received in U.S. Appl. No. 14/845,217, 5 pages. |
Notice of Allowance, dated Jan. 4, 2017, received in U.S. Appl. No. 14/845,217, 5 pages. |
Office Action, dated May 2, 2017, received in U.S. Appl. No. 14/856,517, 34 pages. |
Office Action, dated May 18, 2017, received in U.S. Appl. No. 14/856,519, 35 pages. |
Office Action, dated Jun. 9, 2017, received in U.S. Appl. No. 14/856,520, 36 pages. |
Notice of Allowance, dated Oct. 24, 2016, received in U.S. Appl. No. 14/857,645, 6 pages. |
Office Action, dated Mar. 31, 2017, received in U.S. Appl. No. 14/857,700, 14 pages. |
Notice of Allowance, dated Dec. 28, 2016, received in U.S. Appl. No. 14/864,580, 8 pages. |
Office Action, dated Aug. 19, 2016, received in Australian Patent Application No. 2016100648, which corresponds with U.S. Appl. No. 14/864,580, 6 pages. |
Notice of Allowance, dated Nov. 8, 2016, received in Chinese Patent Application No. 201620470247.4, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
Certificate of Registration, dated Oct. 14, 2016, received in German Patent Application No. 20201600003234.9, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
Office Action, dated Oct. 7, 2016, received in Danish Patent Application No. 201500584, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
Office Action, dated May 5, 2017, received in Danish Patent Application No. 201500584, which corresponds with U.S. Appl. No. 14/864,580, 3 pages. |
Notice of Allowance, dated Nov. 23, 2016, received in U.S. Appl. No. 14/864,601, 12 pages. |
Notice of Allowance, dated Apr. 20, 2017, received in U.S. Appl. No. 14/864,601, 13 pages. |
Notice of Allowance, dated Jan. 31, 2017, received in U.S. Appl. No. 14/864,627, 7 pages. |
Office Action, dated Oct. 7, 2016, received in Danish Patent Application No. 201500585, which corresponds with U.S. Appl. No. 14/864,627, 3 pages. |
Office Action, dated May 4, 2017, received in Danish Patent Application No. 201500585, which corresponds with U.S. Appl. No. 14/864,627, 4 pages. |
Certificate of Examination, dated Dec. 8, 2016, received in Australian Patent Application No. 2016100292, which corresponds with U.S. Appl. No. 14/866,361, 1 page. |
Letters Patent, dated Aug. 3, 2016, received in Chinese Patent Application No. 201620251706.X, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
Office Action, dated Oct. 28, 2016, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 3 pages. |
Patent, dated Aug. 8, 2016, received in Australian Patent Application No. 2016100649, which corresponds with U.S. Appl. No. 14/866,987, 1 page. |
Office Action, dated Oct. 19, 2016, received in Chinese Patent Application No. 2016201470246.X, which corresponds with U.S. Appl. No. 14/866,987, 4 pages. |
Patent, dated May 3, 2017, received in Chinese Patent Application No. 2016201470246.X, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
Patent, dated Sep. 19, 2016, received in German Patent Application No. 202016002908.9, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
Notice of Allowance, dated Nov. 1, 2016, received in Danish Patent Application No. 201500587, which corresponds with U.S. Appl. No. 14/866,987, 2 pages. |
Office Action and Search Report, dated Sep. 9, 2016, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 7 pages. |
Office Action, dated Jan. 31, 2017, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
Office Action, dated Apr. 19, 2017, received in Danish Patent Application No. 201670463, which corresponds with U.S. Appl. No. 14/866,987, 3 pages. |
Notice of Allowance, dated Nov. 1, 2016, received in Danish Patent Application No. 201500589, which corresponds with U.S. Appl. No. 14/866,989, 2 pages. |
Final Office Action, dated Nov. 4, 2016, received in U.S. Appl. No. 14/871,236, 24 pages. |
Notice of Allowance, dated Feb. 28, 2017, received in U.S. Appl. No. 14/871,236, 9 pages. |
Innovation (Unexamined) Patent, dated Aug. 25, 2016, received in Australian Patent Application No. 2016101433, which corresponds with U.S. Appl. No. 14/871,236, 1 page. |
Office Action, dated Oct. 14, 2016, received in Australian Patent Application No. 2016101433, which corresponds with U.S. Appl. No. 14/871,236, 3 pages. |
Office Action and Additional Search Report, dated Sep. 30, 2016, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 10 pages. |
Innovation (Unexamined) Patent, dated Aug. 25, 2016, received in Australian Patent Application No. 2016101436, which corresponds with U.S. Appl. No. 14/871,236, 1 pages. |
Office Action, dated Oct. 31, 2016, received in Australian Patent Application No. 2016101438, which corresponds with U.S. Appl. No. 14/871,236, 6 pages. |
Office Action, dated Oct. 17, 2016, received in Australian Patent Application No. 2016203040, which corresponds with U.S. Appl. No. 14/871,227, 7 pages. |
Office Action, dated Oct. 18, 2016, received in Australian Patent Application No. 2016101431, which corresponds with U.S. Appl. No. 14/871,227, 3 pages. |
Office Action, dated Apr. 13, 2017, received in Australian Patent Application No. 2016101431, which corresponds with U.S. Appl. No. 14/871,227, 4 pages. |
Patent, dated Sep. 26, 2016, received in Danish Patent Application No. 201500597, which corresponds with U.S. Appl. No. 14/871,227, 7 pages. |
Office Action, dated Mar. 24, 2017, received in Japanese Patent Application No. 2016-533201, which corresponds with U.S. Appl. No. 14/871,227, 6 pages. |
Office Action, dated Oct. 14, 2016, received in Australian Patent Application No. 2016101437, which corresponds with U.S. Appl. No. 14/871,336, 2 pages. |
Office Action, dated Apr. 11, 2017, received in Australian Patent Application No. 2016101437, which corresponds with U.S. Appl. No. 14/871,336, 4 pages. |
Office Action, dated Oct. 18, 2016, received in Danish Patent Application No. 201500601, which corresponds with U.S. Appl. No. 14/871,336, 3 pages. |
Notice of Allowance, dated Mar. 23, 2017, received in Danish Patent Application No. 201500601, which corresponds with U.S. Appl. No. 14/871,336, 2 pages. |
Innovation Patent, dated Aug. 25, 2016, received in Australian Patent Application No. 2016101435, which corresponds with U.S. Appl. No. 14/871,462, 1 page. |
Office Action, dated Oct. 4, 2016, received in Australian Patent Application No. 2016101435, which corresponds with U.S. Appl. No. 14/871,462, 3 pages. |
Office Action, dated Oct. 4, 2016, received in Australian Patent Application No. 2016231505, which corresponds with U.S. Appl. No. 14/871,462, 3 pages. |
Office Action, dated Apr. 20, 2017, received in Chinese Patent Application No. 201621044346.2, which corresponds with U.S. Appl. No. 14/871,462, 3 pages. |
Grant, dated Aug. 30, 2016, received in Danish Patent Application No. 201500600, which corresponds with U.S. Appl. No. 14/871,462, 2 pages. |
Office Action, dated Mar. 13, 2017, received in Japanese Patent Application No. 2016-183289, which corresponds with U.S. Appl. No. 14/871,462, 5 pages. |
Final Office Action, dated Sep. 28, 2016, received in U.S. Appl. No. 14/867,823, 31 pages. |
Office Action, dated May 11, 2017, received in U.S. Appl. No. 14/867,823, 42 pages. |
Office Action, dated Sep. 7, 2016, received in Danish Patent Application No. 201500594, which corresponds with U.S. Appl. No. 14/867,823, 4 pages. |
Office Action, dated May 15, 2017, received in Danish Patent Application No. 201500594, which corresponds with U.S. Appl. No. 14/867,823, 4 pages. |
Final Office Action, dated Nov. 2, 2016, received in U.S. Appl. No. 14/867,892, 48 pages. |
Office Action, dated Sep. 14, 2016, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 4 pages. |
Office Action, dated May 4, 2017, received in Danish Patent Application No. 201500598, which corresponds with U.S. Appl. No. 14/867,892, 4 pages. |
Office Action, dated Mar. 1, 2017, received in U.S. Appl. No. 14/869,855, 14 pages. |
Office Action, dated Feb. 9, 2017, received in U.S. Appl. No. 14/869,873, 17 pages. |
Office Action, dated Jul. 5, 2016, received in Chinese Patent Application No. 201620176221.9, which corresponds with U.S. Appl. No. 14/867,990, 4 pages. |
Office Action, dated Oct. 25, 2016, received in Chinese Patent Application No. 201620176221.9, which corresponds with U.S. Appl. No. 14/867,990, 7 pages. |
Office Action, dated Sep. 26, 2016, received in Danish Patent Application No. 201500581, which corresponds with U.S. Appl. No. 14/867,990, 5 pages. |
Office Action, dated May 3, 2017, received in Danish Patent Application No. 201500581, which corresponds with U.S. Appl. No. 14/867,990, 5 pages. |
Office Action, dated Nov. 25, 2016, received in U.S. Appl. No. 15/081,771, 17 pages. |
Final Office Action, dated Jun. 2, 2017, received in U.S. Appl. No. 15/081,771, 17 pages. |
Final Office Action, dated May 1, 2017, received in U.S. Appl. No. 15/136,782, 18 pages. |
Office Action, dated May 23, 2017, received in Danish Patent Application No. 201770190, which corresponds with U.S. Appl. No. 15/136,782, 7 pages. |
Office Action, dated Jan. 20, 2017, received in U.S. Appl. No. 15/231,745, 21 pages. |
Office Action and Search Report, dated Oct. 17, 2016, received in Danish Patent Application No. 201670587, which corresponds with U.S. Appl. No. 15/231,745, 9 pages. |
Office Action (Search Report), dated Dec. 14, 2016, received in Danish Patent Application No. 201670590, which corresponds with U.S. Appl. No. 15/231,745, 9 pages. |
Office Action (Search Report), dated Nov. 10, 2016, received in Danish Patent Application No. 201670591, which corresponds with U.S. Appl. No. 15/231,745, 12 pages. |
Office Action and Search Report, dated Oct. 26, 2016, received in Danish Patent Application No. 201670592, which corresponds with U.S. Appl. No. 15/231,745, 8 pages. |
Office Action, dated Jan. 5, 2017, received in Danish Patent Application No. 201670592, which corresponds with U.S. Appl. No. 15/231,745, 3 pages. |
Office Action and Search Report, dated Oct. 12, 2016, received in Danish Patent Application No. 201670593, which corresponds with U.S. Appl. No. 15/231,745, 7 pages. |
Extended European Search Report, dated Oct. 7, 2016, received in European Patent Application No. 16177863.4, which corresponds with U.S. Appl. No. 14/536,267, 12 pages. |
Extended European Search Report, dated Mar. 15, 2017, received in European Patent Application No. 17153418.3, which corresponds with U.S. Appl. No. 14/536,648, 7 pages. |
International Search Report and Written Opinion, dated Oct. 14, 2016, received in International Patent Application No. PCT/US2016/020697, which corresponds with U.S. Appl. No. 14/866,981, 21 pages. |
International Search Report and Written Opinion, dated Oct. 31, 2016, received in International Patent Application No. PCT/US2016/033578, which corresponds with U.S. Appl. No. 14/863,432, 36 pages. |
International Search Report and Written Opinion, dated Nov. 14, 2016, received in International Patent Application No. PCT/US2016/033541, which corresponds with U.S. Appl. No. 14/866,511, 29 pages. |
International Search Report and Written Opinion, dated Aug. 29, 2016, received in International Patent Application No. PCT/US2016/021400, which corresponds with U.S. Appl. No. 14/869,899, 48 pages. |
International Search Report and Written Opinion, dated Jan. 12, 2017, received in International Patent No. PCT/US2016/046419, which corresponds with U.S. Appl. No. 14/866,992, 23 pages. |
International Search Report and Written Opinion, dated Dec. 15, 2016, received in International Patent Application No. PCT/US2016/046403, which corresponds with U.S. Appl. No. 15/009,661, 17 pages. |
International Search Report and Written Opinion, dated Feb. 27, 2017, received in International Patent Application No. PCT/US2016/046407, which corresponds with U.S. Appl. No. 15/009,688, 30 pages. |
Extended European Search Report, dated Jun. 8, 2017, received in European Patent Application No. 16189425.8, which corresponds with U.S. Appl. No. 14/866,989, 8 pages. |
Extended European Search Report, dated Dec. 21, 2016, received in European Patent Application No. 16189790.5, which corresponds with U.S. Appl. No. 14/871,462, 8 pages. |
International Search Report and Written Opinion, dated Jan. 3, 2017, received in International Patent Application No. PCT/US2016/046214, which corresponds with U.S. Appl. No. 15/231,745, 25 pages. |
Office Action, dated Jun. 29, 2017, received in U.S. Appl. No. 14/608,895, 30 pages. |
Office Action, dated Jul. 26, 2017, received in U.S. Appl. No. 14/536,235, 14 pages. |
Office action, dated Aug. 3, 2017, received in U.S. Appl. No. 14/536,426, 10 pages. |
Office Action, dated Jul. 17, 2017, received in U.S. Appl. No. 14/536,166, 19 pages. |
Notice of Allowance, dated Jul. 10, 2017, received in U.S. Appl. No. 14/609,042, 8 pages. |
Notice of Allowance, dated Jun. 19, 2017, received in U.S. Appl. No. 14/864,737, 8 pages. |
Office Action, dated Jun. 30, 2017, received in U.S. Appl. No. 14/856,522, 22 pages. |
Notice of Allowance, dated Jun. 16, 2017, received in in U.S. Appl. No. 14/857,645, 5 pages. |
Office Action, dated Jul. 6, 2017, received in U.S. Appl. No. 14/867,892, 55 pages. |
Brownlee, “Android 5.0 Lollipop Feature Review!”, https//www.youtube.com/watch?v=pEDQ1z1-PvU, Oct. 27, 2014, 5 pages. Jun. 16 Foreign. |
Google-Chrome, “Android 5.0 Lollipop”, http://androidlovernet/android-os/android-5-0-lollipop/android-5-0-lollipop-recent-apps-card-google-search.html, Oct. 19, 2014, 10 pages. Jun. 16 Foreign. |
YouTube, “How to Master Android Lollipop Notifications in Four Minutes!”, Video Gadgets Journal (VGJFelix), https://www.youtube.com/watch?v=S-zBRG7GGJgs, Feb. 8, 2015, 4 pages. Jun. 29 Foreign. |
Patent, dated May 26, 2017, received in Korean Patent Application No. 20157018851, which corresponds with U.S. Appl. No. 14/536,426, 3 pages. |
Office Action, dated Jul. 4, 2017, received in European Patent Application No. 13795392.3, which corresponds with U.S. Appl. No. 14/608,926, 4 pages. |
Patent, dated Jun. 30, 2017, received in Korean Patent Application No. 2015-7018853, which corresponds with U.S. Appl. No. 14/608,926, 3 pages. |
Office Action, dated Jul. 21, 2017, received in Australian Patent Application No. 2016262773, which corresponds with U.S. Appl. No. 14/536,141, 3 pages. |
Notice of Allowance, dated Jun. 30, 2017, received in Japanese Patent Application No. 2015-511646, which corresponds with U.S. Appl. No. 14/536,141, 5 pages. |
Office Action, dated Jun. 16, 2017, received in Chinese Patent Application No. 201380068295.X, which corresponds with U.S. Appl. No. 14/608,942, 6 pages. |
Patent, dated Jun. 16, 2017, received in Japanese Patent Application No. 2015549393, which corresponds with U.S. Appl. No. 14/608,942, 3 pages. |
Office Action, dated Jul. 4, 2017, received in Australian Patent Application No. 2016238917, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
Office Action, dated Jun. 23, 2017, received in Japanese Patent Application No. 2016173113, which corresponds with U.S. Appl. No. 14/536,203, 5 pages. |
Office Action, dated Jul. 21, 2017, received in Australian Patent Application No. 2016216658, which corresponds with U.S. Appl. No. 14/536,291, 3 pages. |
Patent, dated May 18, 2017, received in Australian Patent Application No. 2013368445, which corresponds with U.S. Appl. No. 14/608,985, 1 page. |
Office Action, dated May 19, 2017, received in Chinese Patent Application No. 201380068399.0, which corresponds with U.S. Appl. No. 14/608,985, 5 pages. |
Office Action, dated Jul. 21, 2017, received in Australian Patent Application No. 2016247194, which corresponds with U.S. Appl. No. 14/536,648, 3 pages. |
Notice of Allowance, dated Jun. 23, 2017, received in Japanese Patent Application No. 2016-558331, which corresponds with U.S. Appl. No. 14/864,737, 5 pages. |
Office Action, dated Jul. 7, 2017, received in Danish Patent Application No. 201500575, 4 pages. |
Office Action, dated Jul. 6, 2017, received in Danish Patent Application No. 201500574, which corresponds with U.S. Appl. No. 14/866,159, 3 pages. |
Office Action, dated Jun. 12, 2017, received in Danish Patent Application No. 201500582, which corresponds with U.S. Appl. No. 14/863,432, 5 pages. |
Notice of Allowance, dated Jul. 14, 2017, received in Japanese Patent Application No. 2016558214, which corresponds with U.S. Appl. No. 14/866,511, 5 pages. |
Office Action, dated Jul. 3, 2017, received in Danish Patent Application No. 201500592, which corresponds with U.S. Appl. No. 14/869,899, 5 pages. |
Office Action, dated Jun. 15, 2017, received in Danish Patent Application No. 201500579, which corresponds with U.S. Appl. No. 14/866,361, 2 pages. |
Office Action, dated Jul. 31, 2017, received in Japanese Patent Application No. 2017126445, which corresponds with U.S. Appl. No. 14/866,987, 4 pages. |
Office Action, dated Jun. 16, 2017, received in Japanese Patent Application No. 2016-233450, which corresponds with U.S. Appl. No. 14/866,989, 6 pages. |
Office Action, dated Jun. 15, 2017, received in Danish Patent Application No. 201500595, which corresponds with U.S. Appl. No. 14/871,236, 4 pages. |
Office Action, dated Jun. 29, 2017, received in Danish Patent Application No. 201670587, which corresponds with U.S. Appl. No. 15/231,745, 4 pages. |
Office Action, dated Jul. 6, 2017, received in Danish Patent Application No. 201670590, which corresponds with U.S. Appl. No. 15/231,745, 3 pages. |
Office Action, dated Jul. 27, 2017, received in Australian Patent Application No. 2017100535, which corresponds with U.S. Appl. No. 15/272,341, 4 pages. |
Search Report, dated Jun. 22, 2017, received in Dutch Patent Application No. 2016375, which corresponds with U.S. Appl. No. 14/866,981, 17 pages. |
Search Report, dated Jun. 19, 2017, received in Dutch Patent Application No. 2016377, which corresponds with U.S. Appl. No. 14/866,159, 13 pages. |
Extended European Search Report, dated Jun. 22, 2017, received in European Patent Application No. 16189421.7, which corresponds with U.S. Appl. No. 14/866,987, 7 pages. |
Extended European Search Report, dated Jul. 25, 2017, received in European Patent Application No. 17171972.7, which corresponds with U.S. Appl. No. 14/870,882, 12 pages. |
Extended European Search Report, dated Jul. 25, 2017, received in European Patent Application No. 1717226.3, which corresponds with U.S. Appl. No. 14/871,336, 9 pages. |
Number | Date | Country | |
---|---|---|---|
20160357389 A1 | Dec 2016 | US |
Number | Date | Country | |
---|---|---|---|
62184816 | Jun 2015 | US | |
62172187 | Jun 2015 | US |