Patent Grant
11592959
This relates generally to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch sensitive surfaces that are used to display and navigate through content.
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 touch pads 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 images or viewing images that are associated with an album of images. Exemplary user interface objects include digital images, video, text files, audio files, icons, and other graphics. A user may 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 or iPhoto 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 existing methods for displaying and navigating through content are cumbersome and inefficient. For example, using a sequence of mouse-based inputs to select a representation of content and view the content associated with the representation of content or drill down through a hierarchy of content using many discrete inputs is tedious and creates a significant cognitive burden on a user. In addition, existing methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, there is a need for computing devices with faster, more efficient methods and interfaces for displaying and navigating through content. Such methods and interfaces may complement or replace conventional methods for displaying and navigating through content. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
The above deficiencies and other problems associated with user interfaces for computing 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 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 finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functions may include image editing, drawing, presenting, word processing, website creating, disk authoring, spreadsheet making, game playing, telephoning, video conferencing, e-mailing, instant messaging, workout support, digital photographing, digital videoing, web browsing, digital music playing, and/or digital video playing. Executable instructions for performing these functions may be included in a computer readable storage medium or other computer program product configured for execution by one or more processors.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method includes: displaying one or more thumbnails; and detecting a first contact and a second contact on the touch-sensitive surface. The method further includes, while continuing to detect the first contact and the second contact on the touch-sensitive surface; detecting a first multi-contact gesture that includes movement of the first contact and the second contact; and, in response to detecting the first multi-contact gesture; displaying content associated with a respective thumbnail; and enlarging the content associated with the respective thumbnail to a respective enlarged size in accordance with the first multi-contact gesture. The method further includes detecting termination of the first multi-contact gesture; and, in response to detecting termination of the first multi-contact gesture; when a resizing metric based on the first multi-contact gesture is below a predefined threshold, ceasing to display the content at the respective enlarged size; and, when the resizing metric based on the first multi-contact gesture is above the predefined threshold, displaying the content on the display in a predefined arrangement.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method includes: displaying one or more selectable objects; and detecting a first contact and a second contact on the touch-sensitive surface. The method further includes, while continuing to detect the first contact and the second contact on the touch-sensitive surface: detecting a first multi-contact gesture that includes movement of the first contact and the second contact; and, in response to detecting the first multi-contact gesture: displaying content associated with a respective selectable object; and enlarging the content associated with the respective selectable object to a respective enlarged size in accordance with the first multi-contact gesture. The method also includes detecting termination of the first multi-contact gesture; and, in response to detecting termination of the first multi-contact gesture: when a resizing metric based on the first multi-contact gesture is below a predefined threshold, ceasing to display the content at the respective enlarged size; and, when the resizing metric based on the first multi-contact gesture is above the predefined threshold, displaying the content on the display in a predefined arrangement.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method includes: displaying a plurality of album thumbnails. A respective album thumbnail represents a respective plurality of content items. The method also includes detecting a first contact and a second contact on the touch-sensitive surface. The method further includes, while continuing to detect the first contact and the second contact on the touch-sensitive surface: detecting a first multi-contact gesture that includes movement of the first contact and the second contact; and, in response to detecting the first multi-contact gesture, displaying representations of content items associated with the respective album thumbnail. The method also includes detecting termination of the first multi-contact gesture; and, in response to detecting termination of the first multi-contact gesture: when a first resizing metric based on the first multi-contact gesture is below a predefined threshold, ceasing to display the representations of the content items associated with the respective album thumbnail; and when the first resizing metric based on the first multi-contact gesture is above the predefined threshold, displaying the representations of the content items associated with the respective album thumbnail on the display in a first predefined arrangement. A respective representation of a content item is a respective content thumbnail that is associated with a respective content item. The method further includes, while displaying the representations of the content items associated with the respective album thumbnail on the display in the first predefined arrangement, detecting a third contact and a fourth contact on the touch-sensitive surface; and while continuing to detect the third contact and the fourth contact on the touch-sensitive surface: detecting a second multi-contact gesture that includes movement of the third contact and the fourth contact; and, in response to detecting the second multi-contact gesture, displaying the respective content item that is associated with the respective content thumbnail. The method further includes detecting termination of the second multi-contact gesture; and in response to detecting termination of the second multi-contact gesture: when a second resizing metric based on the second multi-contact gesture is below a predefined threshold, ceasing to display the respective content item that is associated with the respective content thumbnail; and when the second resizing metric based on the second multi-contact gesture is above the predefined threshold, displaying the respective content item in a second predefined arrangement.
In accordance with some embodiments, a method is performed at an electronic device with a display and a touch-sensitive surface. The method includes: displaying a presentation user interface configured to present content items from a set of content items in a predetermined sequence, the presentation user interface including: a display region for displaying a currently displayed content item in the set of content items; and a scrubber for navigating between content items in the set of content items. The scrubber includes: an ordered line of thumbnail representations for a plurality of content items in the set of content items. The ordered line is ordered in accordance with the predetermined sequence. The scrubber also includes an enlarged thumbnail representation of the currently displayed content item. The enlarged thumbnail representation is displayed in the ordered line at a position that is determined in accordance with the predetermined sequence. The method further includes detecting a first input at a location on the touch-sensitive surface that corresponds to a location on the scrubber for a respective content item in the set of content items; and, in response to detecting the first input, displaying the respective content item in the display region and displaying an enlarged thumbnail representation of the respective content item in the scrubber at a location on the scrubber that is determined in accordance with the predetermined sequence.
In accordance with some embodiments, an electronic device includes a display, a 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 the operations of any of the methods described above. In accordance with some embodiments, a graphical user interface on an electronic device with a display, a 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 above. In accordance with some embodiments, a computer readable storage medium has stored therein instructions which when executed by an electronic device with a display and a touch-sensitive surface, cause the device to perform the operations of any of the methods described above. In accordance with some embodiments, an electronic device includes: a display; a touch-sensitive surface; means for performing the operations of any of the methods described above. In accordance with some embodiments, an information processing apparatus, for use in an electronic device with a display and a touch-sensitive surface, includes means for performing the operations of any of the methods described above.
Thus, electronic devices with displays and touch-sensitive surfaces are provided with faster, more efficient methods and interfaces for displaying and navigating through content, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for displaying and navigating through content.
For a better understanding of the aforementioned embodiments of the invention as well as additional embodiments thereof, 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.
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 present invention. However, it will be apparent to one of ordinary skill in the art that the present invention 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. may be 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 present invention. The first contact and the second contact are both contacts, but they are not the same contact.
The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the description of the invention 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” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
As used herein, the term “resolution” of a display refers to the number of pixels (also called “pixel counts” or “pixel resolution”) along each axis or in each dimension of the display. For example, a display may have a resolution of 320×480 pixels. Furthermore, as used herein, the term “resolution” of a multifunction device refers to the resolution of a display in the multifunction device. The term “resolution” does not imply any limitations on the size of each pixel or the spacing of pixels. For example, compared to a first display with a 1024×768-pixel resolution, a second display with a 320×480-pixel resolution has a lower resolution. However, it should be noted that the physical size of a display depends not only on the pixel resolution, but also on many other factors, including the pixel size and the spacing of pixels. Therefore, the first display may have the same, smaller, or larger physical size, compared to the second display.
As used herein, the term “video resolution” of a display refers to the density of pixels along each axis or in each dimension of the display. The video resolution is often measured in a dots-per-inch (DPI) unit, which counts the number of pixels that can be placed in a line within the span of one inch along a respective dimension of the display.
Embodiments of computing devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the computing 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® and iPod Touch® devices from Apple Inc. of Cupertino, Calif. Other portable devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads), may also be 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 touch pad).
In the discussion that follows, a computing device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the computing device may include one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.
The device supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that may be executed on the device may 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 may be 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 may support the variety of applications with user interfaces that are intuitive and transparent to the user.
The user interfaces may include one or more soft keyboard embodiments. The soft keyboard embodiments may include standard (QWERTY) and/or non-standard configurations of symbols on the displayed icons of the keyboard, such as those described in U.S. patent application Ser. No. 11/459,606, “Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, and Ser. No. 11/459,615, “Touch Screen Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, the contents of which are hereby incorporated by reference in their entireties. The keyboard embodiments may include a reduced number of icons (or soft keys) relative to the number of keys in existing physical keyboards, such as that for a typewriter. This may make it easier for users to select one or more icons in the keyboard, and thus, one or more corresponding symbols. The keyboard embodiments may be adaptive. For example, displayed icons may be modified in accordance with user actions, such as selecting one or more icons and/or one or more corresponding symbols. One or more applications on the device may utilize common and/or different keyboard embodiments. Thus, the keyboard embodiment used may be tailored to at least some of the applications. In some embodiments, one or more keyboard embodiments may be tailored to a respective user. For example, one or more keyboard embodiments may be tailored to a respective user based on a word usage history (lexicography, slang, individual usage) of the respective user. Some of the keyboard embodiments may be adjusted to reduce a probability of a user error when selecting one or more icons, and thus one or more symbols, when using the soft keyboard embodiments.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 may have more or fewer components than shown, may combine two or more components, or may have a different configuration or arrangement of the components. The various components shown in
Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU 120 and the peripherals interface 118, may be controlled by memory controller 122.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data.
In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may be implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 may include 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 may communicate 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 may use 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), 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.11b, IEEE 802.11 g 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 may be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 may include display controller 156 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 control devices 116 may 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 may be coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and 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 screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.
A touch-sensitive display in some embodiments of touch screen 112 may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. Nos: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from portable device 100, whereas touch sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interlace is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to foe touch screen, device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
In some embodiments, device 100 may include a physical or virtual wheel (e.g., a click wheel) as input control device 116. A user may navigate among and internet with one or more graphical objects (e.g., icons) displayed in touch screen 112 by rotating the click wheel or by moving a point of contact with the click wheel (e.g., where the amount of movement of the point of contact is measured by its angular displacement with respect to a center point of the click wheel). The click wheel may also be used to select one or more of the displayed icons. For example, the user may press down on at least a portion of the click wheel or an associated button. User commands and navigation commands provided by the user via the click wheel may be processed by input controller 160 as well as one or more of the modules and/or sets of instructions in memory 102. For a virtual click wheel, the click wheel and click wheel controller may be part of touch screen 112 and display controller 156, respectively. For a virtual click wheel, the click wheel may be either an opaque or semitransparent object that appears and disappears on the touch screen display in response to user interaction with the device. In some embodiments, a virtual click wheel is displayed on the touch screen of a portable multifunction device and operated by user contact with the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 may also include one or more optical sensors 164.
Device 100 may also include one or more proximity sensors 166.
Device 100 may also include one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments memory 102 stores device/global internal state 157, as shown in
Operating system 126 (e.g., 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 on iPod (trademark of Apple Inc.) devices.
Contact/motion module 130 may detect contact with touch screen 112 (in conjunction with display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining 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, may include 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 may be applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detects contact on a touchpad. In some embodiments, contact/motion module 130 and controller 160 detects contact on a click wheel.
Contact/motion module 130 may detect a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns. Thus, a gesture may be 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.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the intensity 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 may be 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 properly data, and then generates screen image data to output to display controller 156.
Text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 may include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 may be used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 may he used 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 may use any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in 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, or IMPS).
In conjunction with RF circuitry 108, touch screen 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 (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact 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 touch screen 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, and speaker 111, video player module 145 includes executable instructions to display, present or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124).
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, music player module 146 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. In some embodiments, device 100 may include the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with RF circuitry 108, touch screen 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 screen 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 screen 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 may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display 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 screen 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 screen 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 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display 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 instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the content of which is hereby incorporated by reference in its entirety.
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 may be combined or otherwise re-arranged in various embodiments. For example, video player module 145 may be combined with music player module 146 into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 may be reduced.
The predefined set of functions that may be performed exclusively through a touch screen and/or a touchpad 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 may be displayed on device 100. In such embodiments, the touchpad may be referred to as a “menu button.” In some other embodiments, the menu button may be a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is(are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, 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 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected may correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identities 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 may utilize or call data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch the event information may also include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event 187 include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object (or 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 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 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event 187 also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers may interact 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, e.g., coordinating mouse movement and mouse button presses with or without single or multiple keyboard presses or holds, user movements 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 which may be utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In one embodiment, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 may be used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment device 100 also may accept verbal input for activation or deactivation of some functions through microphone 113.
Each of the above identified elements in
Attention is now directed towards embodiments of user interfaces (“UI”) that may be implemented on portable multifunction device 100.
In some embodiments, user interface 400B includes the following elements, or a subset or superset thereof:
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures ), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or stylus input). For example, a swipe gesture may be replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture may be replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice may be used simultaneously, or a mouse and finger contacts may be used simultaneously.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on a multifunction device with a display and a touch-sensitive surface, such as device 300 or portable multifunction device 100.
As described below, the method 600 provides an intuitive way to display and navigate through content. The method reduces the cognitive burden on a user when displaying and navigating through content, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to display and navigate through content faster and more efficiently conserves power and increases the time between battery charges.
In some embodiments, prior to displaying (602) the one or more thumbnails discussed in greater detail below, the device performs operations 604-608, as described in greater detail below with reference to
The device displays (610) one or more thumbnails (e.g., album thumbnails 5002 in
In some embodiments, the thumbnail is a selectable object (e.g., an icon) with a reduced scale image of a portion of content associated with the thumbnail (e.g., a reduced scale image is representative of a set of images), as illustrated in
In some embodiments, the thumbnail is a selectable object (e.g., an icon) with a reduced scale image of content associated with the thumbnail (e.g., when the thumbnail represents a single photo, the thumbnail is a reduced size representation of the single photo), as illustrated in
In some embodiments, each respective thumbnail of the one or more thumbnails is located (611) at a respective initial region (e.g., regions 5004 in
The device detects (612) a first contact and a second contact (e.g., contacts 5006 in
Operations 616-644 are performed while continuing to detect (614) the first contact and the second contact on the touch-sensitive surface (e.g., contacts 5006 with touch screen 112 in
Operations 622-644 are performed in response to defecting (620) the first multi-contact gesture (e.g., movement of contacts 5006 in
The device displays (622) content associated with a respective thumbnail. For example, displaying the content includes displaying representations 5008 of multiple photos in
In some embodiments, the content is initially displayed at a size that corresponds to the initial size of the respective thumbnail and at a location that is proximate to an initial region (e.g., 5004-3 in
In some embodiments, the content is a plurality of images (e.g., representations 5008 of content in
In some embodiments, displaying the content includes ceasing (628) to display the respective thumbnail (e.g., replacing the thumbnail with the content), as illustrated in
In some embodiments, while detecting the first contact and the second contact, the device determines (632) a resizing metric (e.g., by calculating a change in distance between contacts in the multi-contact gesture or by calculating a change in size of the content). In some embodiments, the resizing metric is a measure of the percentage change in the distance between the first contact and the second contact on the touch-sensitive surface from the initial positions (e.g., when the distance between the contacts 5006-b in
In some embodiments, in response to detecting the first multi-contact gesture, the device ceases (634) to display the respective thumbnail in an initial region. In some embodiments, ceasing to display the respective thumbnail in the initial region includes displaying an animation of the respective thumbnail, moving from its initial region to a region on the display that is associated with the first multi-contact gesture and transitioning the respective thumbnail to the content associated with the respective thumbnail. For example, in
The device enlarges (636) the content associated with the respective thumbnail to a respective enlarged size in accordance with the first multi-contact gesture. For example, in
In some embodiments, the first multi-contact gesture includes both de-pinching component(s) (e.g., movement of the contacts from a first location 5012-a on the touch screen 112 in
In some embodiments, the device enlarges (637) the content associated with the respective thumbnail to the respective enlarged size is in accordance with the resizing metric (e.g., when the resizing metric increases by one hundred percent, the size of the content increases by one hundred percent, etc.). In some embodiments, the device enlarges (638) the content associated with the respective thumbnail to the respective enlarged size is proportional to the resizing metric (e.g., if the proportionality is 1/2x, then when the resizing metric increases by one hundred percent, the size of the content is increased by fifty percent).
In some embodiments, in response to detecting the first multi-contact gesture, the device translates (640) the content across the display in accordance with the first multi-contact gesture. In some embodiments, enlarging and translating of the content occur simultaneously. For example, in
In some embodiments, in response to detecting the first multi-contact gesture, the device rotates (642) the content. For example, in
In some embodiments, the one or more thumbnails includes a plurality of thumbnails (e.g., 5002-1, 5002-2, 5002-4 and/or 5005-4 in
The device detects (650) termination of the first multi-contact gesture (e.g., detecting liftoff of the first contact and the second contact). Operations 654-694 are performed in response to detecting (652) termination of the first multi-contact gesture. When the resizing metric based on the first multi-contact gesture is (654) below a predefined threshold, the device ceases (655) to display the content at the respective enlarged size. For example, if the device detects a liftoff of contacts 5006-b in
In some embodiments, redisplaying the thumbnail includes displaying an animation of the content shrinking down to the size of the respective thumbnail, transforming into the respective thumbnail and moving back to the initial region of the respective thumbnail on the display. For example, in
In some embodiments, in response to detecting termination of the first multi-contact gesture, when the resizing metric based on the first multi-contact gesture is below the predefined threshold, the device redisplays (656) the respective thumbnail (e.g., album, thumbnail 5002-3 in
It should be understood that ceasing to display the content when the resizing metric is below the predefined threshold is particularly advantageous in situations where the user reviews the content (e.g., the representations 5008 of photos in an Album-3 or the full size photo 5014-8) without actually causing the device to perform an operation that opens the content. In other words, the user is able to preview the actual contents of the album and then cause the device to cease to display the previewed contents in a single gesture if the user decides that it is unnecessary to need to actually open the content. This preview operation is faster for the user and more computationally efficient for the computer and thus improves the speed and efficiency of the machine-user interface, thereby conserving energy and improving battery life.
When the resizing metric based on the first multi-contact gesture is above the predefined threshold, the device displays (658) the content on the display in a predefined arrangement. For example, in
In some embodiments, the predefined arrangement includes displaying the content at a predefined orientation. As one example, in
In some embodiments, in response to detecting the first multi-contact gesture, the device rotates the content to an arbitrary angle (e.g., six degrees) in accordance with the first multi-contact gesture (e.g., a primary axis 5016 between the first and second contact is rotated from a first orientation 5016-a to a second orientation 5016-b and the content 5014-8 is rotated accordingly, as described in greater detail above with reference to
In some embodiments, the content includes a plurality of content items (e.g., representations 5008 of the photos in
In some embodiments, displaying the content on the display in the predefined arrangement includes displaying (664) the content in a slideshow mode (e.g., Photo-8 5014-8 is displayed in a slideshow mode in
In some embodiments, enlarging the content includes resizing (672) the content to an arbitrary size (e.g., 5014-8 in
In other words, in the embodiment described above, in a first content manipulation mode (as illustrated in
In some embodiments, the one or more thumbnails include (684) the respective thumbnail and a plurality of other thumbnails arranged as an initial array of thumbnails (e.g., the multi-row arrangement of content thumbnails 5008 in
In these embodiments, while in slideshow mode, the device also detects a third contact and a fourth contact on the touch-sensitive surface (e.g., 5024-a in
In some embodiments, in response to detecting the second multi-contact gesture, the device also exits (690) the slideshow mode (e.g., as illustrated in
In some embodiments, the device also detects (692) termination of the second multi-contact gesture (e.g., detecting liftoff of the third contact and the fourth contact 5024-c in
In some embodiments, operations 604-608 are performed prior to displaying (602) the respective thumbnail. In some embodiments, the device displays (604) a plurality of pins on a map (e.g., 5026 in
In these embodiments, the first contact and the second contact on the touch-sensitive surface are detected with the respective thumbnail (e.g., contacts 5030 with touch screen 112 in
In some embodiments, when a resizing metric based on the first multi-contact gesture is below a predefined threshold, the device ceases to display the content at the respective enlarged size (e.g., the device displays the user interface including the respective thumbnail 5002-6, as illustrated in
In contrast, when the resizing metric based on the first multi-contact gesture is above the predefined threshold, the device displays the content on the display in a predefined arrangement. For example, the device displays the content in a multi-row array (e.g., the content thumbnails 5008 are displayed in a multi-row array in
Note that details of the processes described above with respect to method 600 (e.g.,
As described below, the method 700 provides an intuitive way to display and navigate through content. The method reduces the cognitive burden on a user when displaying and navigating through content, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to display and navigate through content faster and more efficiently conserves power and increases the time between battery charges.
The device displays (702) one or more selectable objects (e.g., icons 5002 in
Operations 708-714 are performed while continuing to detect (706) the first contact and the second contact on the touch-sensitive surface (e.g., contacts 5006 in
The device detects (708) a first multi-contact gesture that includes movement of the first contact and the second contact (e.g., movement of contacts 5006 away from a first location 5006-a in
The device detects (716) termination of the first multi-contact gesture (e.g., detecting liftoff of the first contact and the second contact 5006 in
Note that details of the processes described above with respect to method 600 (e.g.,
As described below, the method 800 provides an intuitive way to display and navigate through content. The method reduces the cognitive burden on a user when displaying and navigating through content, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to display and navigate through content faster and more efficiently conserves power and increases the time between battery charges.
The device displays (802) a plurality of album thumbnails (e.g., 5002 in
The device detects (808) a first contact and a second contact (e.g., 5006 in
Operations 814-820 are performed while continuing to detect (812) the first contact and the second contact on the touch-sensitive surface.
The device detects a first multi-contact gesture that includes movement of the first contact and the second contact (e.g., the device detects movement of contacts 5006 from a first location 5006-a in
In some embodiments, in response to detecting the first multi-contact gesture, the device ceases (820) to display the respective album thumbnail in an initial region of the respective album thumbnail (e.g., in
The device detects (822) termination of the first multi-contact gesture (e.g., by detecting liftoff of the first contact and the second contact 5006). Operations 826-830 are performed in response to detecting (824) termination of the first multi-contact gesture.
Operations 828-830 are performed when a first resizing metric based on the first multi-contact gesture is below a predefined threshold (e.g., when the device detects a liftoff of contacts 5006-b in
When the first resizing metric based on the first multi-contact gesture is above the predefined threshold, the device displays (832) the representations of the content items associated with the respective album thumbnail on the display in a first predefined arrangement (e.g., in a multi-row grid, as illustrated in
While displaying the representations of the content items associated with the respective album thumbnail on the display in the first predefined arrangement, the device detects (834) a third contact and a fourth contact on the touch-sensitive surface (e.g., contacts 5012 in
Operations 840-846 are performed while continuing to detect the third contact and the fourth contact on the touch-sensitive surface (e.g., 5012 in
In response to detecting the second multi-contact gesture, the device displays (844) the respective content item (e.g., 5014-8 in
The device detects (848) termination of the second multi-contact gesture (e.g., detecting liftoff of the third contact and the fourth contact).
Operations 852-870 are performed in response to detecting (850) termination of the second multi-contact gesture. Operations 854-856 are performed when a second resizing metric based on the second multi-contact gesture is (852) below a predefined threshold, the device ceases (854) to display the respective content item that is associated with the respective content thumbnail. In some embodiments, the device also redisplays (856) the respective content thumbnail. For example, in
Operations 860-870 are performed when the second resizing metric based on the second multi-contact gesture is above the predefined threshold. The device displays (860) the respective content item in a second predefined arrangement. In some embodiments, the content item is displayed at a predefined size (e.g., as a full-screen image in a slideshow of images from the album). For example, in
In some embodiments, the first predefined arrangement of the representations of the content items associated with the respective album thumbnail is (862) an initial array of content thumbnails (e.g., the array of content thumbnails 5008 in
While displaying the subsequent image (e.g., Photo-15, 5014-15 in
In some embodiments, in response to detecting the third multi-contact gesture, the device exits (866) the slideshow mode (e.g., as illustrated in
As described below, the method 900 provides an intuitive way to navigate through content. The method reduces the cognitive burden on a user when navigating through content, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to navigate through content faster and more efficiently conserves power and increases the time between battery charges.
The device displays (902) a presentation user interface configured to present content items (e.g., photos 5014 in
The ordered line is ordered (908) in accordance with the predetermined sequence. For example, the photos are arranged in ascending numerical order (e.g., ordered from Photo-1 to Photo-2 to Photo-3, etc.) and the thumbnail representations are ordered in accordance with the ascending numerical order of the photos with which they are associated (e.g., ordered from T1 to T2, to T3, etc.) In some embodiments, the plurality of content items includes (910) at least one video and at least one image. For example, Photo-8 in
In some embodiments, the ordered line is (912) a column (e.g., as illustrated in
In some embodiments, the ordered line is (916) a row (e.g., as illustrated in
The scrubber also includes an enlarged thumbnail representation (e.g., 5044 in
The enlarged thumbnail representation is (920) displayed in the ordered line at a position that is determined in accordance with the predetermined sequence. For example, in
In some embodiments, when the plurality of content items includes less than all of the content items in the set of content items (e.g., as illustrated in
When the respective content item is in the plurality of content items, displaying the enlarged thumbnail representation of the respective content item includes displaying (924) the enlarged thumbnail representation of the respective content item in the scrubber at a location on the scrubber that is determined in accordance with the predetermined sequence. For example, in
In contrast, when the respective content item is not in the plurality of content items, displaying the enlarged thumbnail representation of the respective content item includes inserting (926) the enlarged thumbnail representation of the respective content item in the scrubber at a location on the scrubber that is determined in accordance with the predetermined sequence. It should be understood that in order to display the enlarged thumbnail representation in this case, the other thumbnail representations in the scrubber will have to be adjusted (e.g., by removing a previously displayed thumbnail representation for another content item, or decreasing the size of one or more adjacent thumbnail representations). For example, in
The device detects (928) a first input on the touch-sensitive surface that corresponds to a location on the scrubber for a respective content item in the set of content items. As one example, the device detects movement of the contact (e.g., movement of contact 5046 from a first location 5046-a in
Operations 932-936 are performed in response to detecting 930 the first input. The device displays (932) the respective content item in the display region (e.g., Photo-15 5014-15 is displayed in content region 5034 in
It should be understood that, in some embodiments, the device displays an expanded thumbnail representation tor each content item in the se. of content items as the contact (e.g., 5046 in
When displaying a navigation interface for navigating through a set of content items, it is particularly advantageous to display a scrubber that includes thumbnail representations of a plurality of the content items in a set of content items, so that the user can readily determine which portion of the scrubber is associated with which content items in the set of content items (e.g., by looking a the thumbnail representations that are displayed in the scrubber). However, when the scrubber has a fixed length or width (e.g., the length or width of the display), as the number of content items in the set of content items increases, the thumbnail representations must decrease in size, and if the device continues to decrease the thumbnail representations in size, then the thumbnail representations cease to provide any visual indication of which portion of the scrubber is associated with which content items in the set of content items. However, by displaying thumbnail representations for only a subset of the content items, the device continues to provide the user with visual cues as to which portion of the scrubber is associated with which content items in the set of content items even as the number of content items increases beyond the number of thumbnail representations that can be displayed in the scrubber.
However, displaying thumbnail representations for only a subset of the content items, may create cognitive dissonance for the user when the user provides an input that corresponds to a respective location of the scrubber that includes a thumbnail representation for a first content item, and the device selects a second item that is associated with the respective location on the scrubber. Displaying an expanded thumbnail representation of the content item associated with the current location on the scrubber, as described above, avoids creating cognitive dissonance for the user, reducing confusion and increasing speed and accuracy of the user, thereby creating a more efficient machine-user interface.
In some embodiments, displaying the respective content item in the display region includes displaying (936) a visual indicator (e.g., voice memo indicator icon 5048 in
It should be understood that while the preceding examples for the methods described above (e.g., method 600, method 700, method 800 and method 900) have been given primarily with respect to album thumbnails, image thumbnails and images such as photos, the content items may be any kind of electronic document or representation of an electronic document (e.g., slideshow documents, word processing documents, spreadsheet documents, etc.) or portions of electronic documents (e.g., slides, pages, tables, etc.) without departing from the scope of the embodiments disclosed herein. In some embodiments, the content items include a slideshow document and the thumbnail for the slideshow document is a representation of the slideshow document, as described in greater detail with reference to
As described in greater detail above with reference to
As described in greater detail above with reference to
As described in greater detail above with reference to
As described in greater detail above with reference to
The operations in the information processing methods described above may be implemented by running one or more functional modules in information processing apparatus such as general purpose processors or application specific chips. These modules, combinations of these modules, and/or their combination with general hardware (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 utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated.
This application is a continuation of U.S. Non-Provisional application Ser. No. 16/983,815, filed on Aug. 3, 2020, which is a continuation of U.S. Non-Provisional application Ser. No. 16/402,057, filed on May 2, 2019, which is a continuation of U.S. Non-Provisional application Ser. No. 15/687,384, filed on Aug. 25, 2017, which is a continuation of U.S. Non-provisional application Ser. No. 14/253,783, filed on Apr. 15, 2014, which is a continuation of U.S. Non-Provisional application Ser. No. 12/789,441, filed on May 27, 2010, which claims the benefit of U.S. Provisional Application No. 61/335,520, filed on Jan. 6, 2010. The content of these applications is incorporated herein by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5416895 | Anderson et al. | May 1995 | A |
| 5463725 | Henckel et al. | Oct 1995 | A |
| 5565888 | Selker | Oct 1996 | A |
| 5583542 | Capps et al. | Dec 1996 | A |
| 5604861 | Douglas et al. | Feb 1997 | A |
| 5677708 | Matthews et al. | Oct 1997 | A |
| 5757368 | Gerpheide et al. | May 1998 | A |
| 5784061 | Moran et al. | Jul 1998 | A |
| 5825349 | Meier et al. | Oct 1998 | A |
| 5956035 | Sciammarella et al. | Sep 1999 | A |
| 5973694 | Steele et al. | Oct 1999 | A |
| 6073036 | Heikkinen et al. | Jun 2000 | A |
| 6154210 | Anderson | Nov 2000 | A |
| 6167469 | Safai et al. | Dec 2000 | A |
| 6237010 | Hui et al. | May 2001 | B1 |
| 6252596 | Garland et al. | Jun 2001 | B1 |
| 6272246 | Takai | Aug 2001 | B1 |
| 6292273 | Dow et al. | Sep 2001 | B1 |
| 6301586 | Yang et al. | Oct 2001 | B1 |
| 6334025 | Yamagami et al. | Dec 2001 | B1 |
| 6351556 | Loui et al. | Feb 2002 | B1 |
| 6606411 | Loui et al. | Aug 2003 | B1 |
| 6686938 | Jobs et al. | Feb 2004 | B1 |
| 6741268 | Hayakawa et al. | May 2004 | B1 |
| 6784925 | Tomat et al. | Aug 2004 | B1 |
| 6915011 | Loui et al. | Jul 2005 | B2 |
| 6920619 | Milekic | Jul 2005 | B1 |
| 6950989 | Rosenzweig et al. | Sep 2005 | B2 |
| 7015910 | Card et al. | Mar 2006 | B2 |
| 7139982 | Card et al. | Nov 2006 | B2 |
| 7164410 | Kupka | Jan 2007 | B2 |
| 7178111 | Glein et al. | Feb 2007 | B2 |
| 7325198 | Adcock et al. | Jan 2008 | B2 |
| 7380212 | Cody et al. | May 2008 | B2 |
| 7421449 | Williams et al. | Sep 2008 | B2 |
| 7434177 | Ording et al. | Oct 2008 | B1 |
| 7587671 | Saft et al. | Sep 2009 | B2 |
| 7627828 | Collison et al. | Dec 2009 | B1 |
| 7636733 | Rothmuller et al. | Dec 2009 | B1 |
| 7680340 | Luo et al. | Mar 2010 | B2 |
| 7716194 | Williams et al. | May 2010 | B2 |
| 7747625 | Gargi et al. | Jun 2010 | B2 |
| 7779358 | Gupta et al. | Aug 2010 | B1 |
| 7788592 | Williams et al. | Aug 2010 | B2 |
| 7823080 | Miyajima et al. | Oct 2010 | B2 |
| 7831100 | Gallagher et al. | Nov 2010 | B2 |
| 7843454 | Biswas | Nov 2010 | B1 |
| 7865215 | Bells et al. | Jan 2011 | B2 |
| 7970240 | Chao et al. | Jun 2011 | B1 |
| 7991234 | Fujioka et al. | Aug 2011 | B2 |
| 8024658 | Fagans et al. | Sep 2011 | B1 |
| 8028249 | Loui et al. | Sep 2011 | B2 |
| 8106856 | Matas et al. | Jan 2012 | B2 |
| RE43260 | Paalasmaa et al. | Mar 2012 | E |
| 8132116 | Schendel | Mar 2012 | B1 |
| 8200669 | Iampietro et al. | Jun 2012 | B1 |
| 8305355 | Forstall et al. | Nov 2012 | B2 |
| 8339420 | Hiraoka et al. | Dec 2012 | B2 |
| 8352471 | Oami | Jan 2013 | B2 |
| 8406473 | Tanaka et al. | Mar 2013 | B2 |
| 8566403 | Pascal et al. | Oct 2013 | B2 |
| 8571331 | Cifarelli et al. | Oct 2013 | B2 |
| 8698762 | Wagner et al. | Apr 2014 | B2 |
| 9021034 | Narayanan et al. | Apr 2015 | B2 |
| 9042646 | Das et al. | May 2015 | B2 |
| 9123086 | Freeland et al. | Sep 2015 | B1 |
| 9143601 | Padmanabhan et al. | Sep 2015 | B2 |
| 9183560 | Abelow | Nov 2015 | B2 |
| 9286546 | O'malley et al. | Mar 2016 | B2 |
| 9338242 | Suchland et al. | May 2016 | B1 |
| 9459792 | Matas et al. | Oct 2016 | B2 |
| 9870554 | Leung et al. | Jan 2018 | B1 |
| 9904906 | Kim et al. | Feb 2018 | B2 |
| 9916538 | Zadeh et al. | Mar 2018 | B2 |
| 10019136 | Ozog | Jul 2018 | B1 |
| 10051103 | Gordon et al. | Aug 2018 | B1 |
| 10204338 | Lee | Feb 2019 | B2 |
| 10303448 | Steven et al. | May 2019 | B2 |
| 10417588 | Kreisel et al. | Sep 2019 | B1 |
| 10489982 | Johnson et al. | Nov 2019 | B2 |
| 10509907 | Shear et al. | Dec 2019 | B2 |
| 10540400 | Dumant et al. | Jan 2020 | B2 |
| 10776965 | Stetson et al. | Sep 2020 | B2 |
| 20010014184 | Bubie et al. | Aug 2001 | A1 |
| 20020008763 | Kawamura et al. | Jan 2002 | A1 |
| 20020021758 | Chui et al. | Feb 2002 | A1 |
| 20020054233 | Juen | May 2002 | A1 |
| 20020057461 | Dow et al. | May 2002 | A1 |
| 20020070982 | Hill et al. | Jun 2002 | A1 |
| 20020093531 | Barile | Jul 2002 | A1 |
| 20020106199 | Ikeda | Aug 2002 | A1 |
| 20020135621 | Angiulo et al. | Sep 2002 | A1 |
| 20020168108 | Loui et al. | Nov 2002 | A1 |
| 20030033296 | Rothmuller | Feb 2003 | A1 |
| 20030048291 | Dieberger | Mar 2003 | A1 |
| 20030081135 | Boll | May 2003 | A1 |
| 20030090504 | Brook et al. | May 2003 | A1 |
| 20030108241 | Colmenarez et al. | Jun 2003 | A1 |
| 20030122787 | Zimmerman et al. | Jul 2003 | A1 |
| 20030149990 | Anttila et al. | Aug 2003 | A1 |
| 20030197687 | Shetter | Oct 2003 | A1 |
| 20040019640 | Bartram et al. | Jan 2004 | A1 |
| 20040046886 | Ambiru et al. | Mar 2004 | A1 |
| 20040119758 | Grossman et al. | Jun 2004 | A1 |
| 20040125150 | Adcock et al. | Jul 2004 | A1 |
| 20040135797 | Meier et al. | Jul 2004 | A1 |
| 20040135904 | Shiota et al. | Jul 2004 | A1 |
| 20040143590 | Wong et al. | Jul 2004 | A1 |
| 20040158555 | Seedman et al. | Aug 2004 | A1 |
| 20040167898 | Margolus et al. | Aug 2004 | A1 |
| 20040183830 | Cody et al. | Sep 2004 | A1 |
| 20040205504 | Phillips | Oct 2004 | A1 |
| 20040207722 | Koyama et al. | Oct 2004 | A1 |
| 20040212617 | Fitzmaurice et al. | Oct 2004 | A1 |
| 20050020317 | Koyama | Jan 2005 | A1 |
| 20050041035 | Nagatomo et al. | Feb 2005 | A1 |
| 20050044066 | Hooper et al. | Feb 2005 | A1 |
| 20050052427 | Wu et al. | Mar 2005 | A1 |
| 20050062130 | Ciancio et al. | Mar 2005 | A1 |
| 20050071736 | Schneider et al. | Mar 2005 | A1 |
| 20050071767 | Kirkland et al. | Mar 2005 | A1 |
| 20050073601 | Battles et al. | Apr 2005 | A1 |
| 20050076056 | Paalasmaa et al. | Apr 2005 | A1 |
| 20050083406 | Cozier | Apr 2005 | A1 |
| 20050102635 | Jiang et al. | May 2005 | A1 |
| 20050104848 | Yamaguchi et al. | May 2005 | A1 |
| 20050108253 | Metsatahti et al. | May 2005 | A1 |
| 20050128305 | Hamasaki et al. | Jun 2005 | A1 |
| 20050134719 | Beck | Jun 2005 | A1 |
| 20050134945 | Gallagher | Jun 2005 | A1 |
| 20050160377 | Sciammarella et al. | Jul 2005 | A1 |
| 20050183026 | Amano et al. | Aug 2005 | A1 |
| 20050195221 | Berger et al. | Sep 2005 | A1 |
| 20050275636 | Dehlin et al. | Dec 2005 | A1 |
| 20060001652 | Chiu et al. | Jan 2006 | A1 |
| 20060004685 | Pyhalammi et al. | Jan 2006 | A1 |
| 20060017692 | Wehrenberg et al. | Jan 2006 | A1 |
| 20060025218 | Hotta | Feb 2006 | A1 |
| 20060026521 | Hotelling | Feb 2006 | A1 |
| 20060026536 | Hotelling et al. | Feb 2006 | A1 |
| 20060036960 | Loui et al. | Feb 2006 | A1 |
| 20060061663 | Park | Mar 2006 | A1 |
| 20060072028 | Hong | Apr 2006 | A1 |
| 20060077266 | Nurmi et al. | Apr 2006 | A1 |
| 20060080386 | Roykkee et al. | Apr 2006 | A1 |
| 20060088228 | Marriott et al. | Apr 2006 | A1 |
| 20060090141 | Loui et al. | Apr 2006 | A1 |
| 20060136839 | Makela et al. | Jun 2006 | A1 |
| 20060155757 | Williams et al. | Jul 2006 | A1 |
| 20060156237 | Williams et al. | Jul 2006 | A1 |
| 20060156245 | Williams et al. | Jul 2006 | A1 |
| 20060156246 | Williams et al. | Jul 2006 | A1 |
| 20060164535 | Oyama | Jul 2006 | A1 |
| 20060265643 | Saft et al. | Nov 2006 | A1 |
| 20070008321 | Gallagher et al. | Jan 2007 | A1 |
| 20070016868 | Nurmi | Jan 2007 | A1 |
| 20070031115 | Oshikiri et al. | Feb 2007 | A1 |
| 20070081740 | Ciudad et al. | Apr 2007 | A1 |
| 20070097421 | Sorensen et al. | May 2007 | A1 |
| 20070112754 | Haigh et al. | May 2007 | A1 |
| 20070115373 | Gallagher et al. | May 2007 | A1 |
| 20070136778 | Birger et al. | Jun 2007 | A1 |
| 20070152984 | Ording et al. | Jul 2007 | A1 |
| 20070186154 | Anthony et al. | Aug 2007 | A1 |
| 20070192741 | Yoritate et al. | Aug 2007 | A1 |
| 20070204225 | Berkowitz et al. | Aug 2007 | A1 |
| 20070229678 | Barrus et al. | Oct 2007 | A1 |
| 20070245236 | Lee et al. | Oct 2007 | A1 |
| 20070271340 | Goodman et al. | Nov 2007 | A1 |
| 20080030456 | Asadi et al. | Feb 2008 | A1 |
| 20080052945 | Matas et al. | Mar 2008 | A1 |
| 20080057941 | Scott et al. | Mar 2008 | A1 |
| 20080059888 | Dunko | Mar 2008 | A1 |
| 20080062141 | Chaudhri | Mar 2008 | A1 |
| 20080091637 | Escamilla et al. | Apr 2008 | A1 |
| 20080133697 | Stewart et al. | Jun 2008 | A1 |
| 20080152201 | Zhang et al. | Jun 2008 | A1 |
| 20080168349 | Lamiraux et al. | Jul 2008 | A1 |
| 20080168402 | Blumenberg | Jul 2008 | A1 |
| 20080256577 | Funaki et al. | Oct 2008 | A1 |
| 20080282202 | Sunday | Nov 2008 | A1 |
| 20080309632 | Westerman et al. | Dec 2008 | A1 |
| 20090006965 | Bodin et al. | Jan 2009 | A1 |
| 20090021576 | Linder et al. | Jan 2009 | A1 |
| 20090063542 | Bull et al. | Mar 2009 | A1 |
| 20090077460 | Li et al. | Mar 2009 | A1 |
| 20090113315 | Fisher et al. | Apr 2009 | A1 |
| 20090113350 | Hibino et al. | Apr 2009 | A1 |
| 20090132921 | Hwangbo et al. | May 2009 | A1 |
| 20090161962 | Gallagher et al. | Jun 2009 | A1 |
| 20090198359 | Chaudhri | Aug 2009 | A1 |
| 20090210793 | Yee et al. | Aug 2009 | A1 |
| 20090216806 | Feuerstein et al. | Aug 2009 | A1 |
| 20090259967 | Davidson et al. | Oct 2009 | A1 |
| 20090278806 | Duarte et al. | Nov 2009 | A1 |
| 20090282371 | Curl et al. | Nov 2009 | A1 |
| 20090284551 | Stanton | Nov 2009 | A1 |
| 20090307623 | Agarawala et al. | Dec 2009 | A1 |
| 20090319472 | Jain et al. | Dec 2009 | A1 |
| 20100045828 | Gallagher et al. | Feb 2010 | A1 |
| 20100046842 | Conwell | Feb 2010 | A1 |
| 20100076976 | Sotirov et al. | Mar 2010 | A1 |
| 20100083173 | Germann et al. | Apr 2010 | A1 |
| 20100088641 | Choi | Apr 2010 | A1 |
| 20100103321 | Ishikawa et al. | Apr 2010 | A1 |
| 20100110228 | Ozawa et al. | May 2010 | A1 |
| 20100114891 | Oami | May 2010 | A1 |
| 20100124967 | Lutnick et al. | May 2010 | A1 |
| 20100125786 | Ozawa et al. | May 2010 | A1 |
| 20100150456 | Tanaka et al. | Jun 2010 | A1 |
| 20100179874 | Higgins et al. | Jul 2010 | A1 |
| 20100207892 | Lin et al. | Aug 2010 | A1 |
| 20100211575 | Collins et al. | Aug 2010 | A1 |
| 20100214442 | Uemura et al. | Aug 2010 | A1 |
| 20100251167 | Deluca et al. | Sep 2010 | A1 |
| 20100253807 | Matsumoto et al. | Oct 2010 | A1 |
| 20100283743 | Coddington | Nov 2010 | A1 |
| 20100287053 | Ganong et al. | Nov 2010 | A1 |
| 20100299601 | Kaplan et al. | Nov 2010 | A1 |
| 20100302179 | Ahn et al. | Dec 2010 | A1 |
| 20110035700 | Meaney et al. | Feb 2011 | A1 |
| 20110050564 | Alberth et al. | Mar 2011 | A1 |
| 20110050640 | Lundback et al. | Mar 2011 | A1 |
| 20110072394 | Victor et al. | Mar 2011 | A1 |
| 20110078717 | Drummond et al. | Mar 2011 | A1 |
| 20110099199 | Stalenhoef et al. | Apr 2011 | A1 |
| 20110099478 | Gallagher et al. | Apr 2011 | A1 |
| 20110126148 | Krishnaraj et al. | May 2011 | A1 |
| 20110145275 | Stewart | Jun 2011 | A1 |
| 20110145327 | Stewart | Jun 2011 | A1 |
| 20110246463 | Carson et al. | Oct 2011 | A1 |
| 20110267368 | Casillas et al. | Nov 2011 | A1 |
| 20110282867 | Palermiti et al. | Nov 2011 | A1 |
| 20120057081 | Petersson et al. | Mar 2012 | A1 |
| 20120058801 | Nurmi | Mar 2012 | A1 |
| 20120190386 | Anderson | Jul 2012 | A1 |
| 20120311444 | Chaudhri | Dec 2012 | A1 |
| 20130013650 | Shum | Jan 2013 | A1 |
| 20130021368 | Lee et al. | Jan 2013 | A1 |
| 20130022282 | Cooper | Jan 2013 | A1 |
| 20130040660 | Fisher et al. | Feb 2013 | A1 |
| 20130054634 | Chakraborty et al. | Feb 2013 | A1 |
| 20130061175 | Matas et al. | Mar 2013 | A1 |
| 20130145292 | Cohen et al. | Jun 2013 | A1 |
| 20130156275 | Amacker et al. | Jun 2013 | A1 |
| 20130198176 | Kim | Aug 2013 | A1 |
| 20130205210 | Jeon et al. | Aug 2013 | A1 |
| 20130239049 | Perrodin et al. | Sep 2013 | A1 |
| 20130285948 | Zhang | Oct 2013 | A1 |
| 20140025737 | Kruglick | Jan 2014 | A1 |
| 20140046914 | Das et al. | Feb 2014 | A1 |
| 20140064572 | Panzer et al. | Mar 2014 | A1 |
| 20140074825 | Wood et al. | Mar 2014 | A1 |
| 20140082533 | Kelley et al. | Mar 2014 | A1 |
| 20140089330 | Cui et al. | Mar 2014 | A1 |
| 20140092291 | Aoshima et al. | Apr 2014 | A1 |
| 20140165000 | Fleizach et al. | Jun 2014 | A1 |
| 20140181089 | Desmond et al. | Jun 2014 | A1 |
| 20140181205 | Sherrets et al. | Jun 2014 | A1 |
| 20140198234 | Kobayashi et al. | Jul 2014 | A1 |
| 20140222809 | Hochmuth et al. | Aug 2014 | A1 |
| 20140225925 | Hayashi et al. | Aug 2014 | A1 |
| 20140236882 | Rishe et al. | Aug 2014 | A1 |
| 20140250126 | Baldwin et al. | Sep 2014 | A1 |
| 20140282011 | Dellinger et al. | Sep 2014 | A1 |
| 20140282262 | Gregotski et al. | Sep 2014 | A1 |
| 20140289222 | Sharpe et al. | Sep 2014 | A1 |
| 20140337324 | Chao et al. | Nov 2014 | A1 |
| 20140341476 | Kulick et al. | Nov 2014 | A1 |
| 20140362274 | Christie et al. | Dec 2014 | A1 |
| 20140372436 | Makki et al. | Dec 2014 | A1 |
| 20140372889 | Lemay et al. | Dec 2014 | A1 |
| 20140372898 | Ayres et al. | Dec 2014 | A1 |
| 20150005013 | Cao et al. | Jan 2015 | A1 |
| 20150039616 | Rolston et al. | Feb 2015 | A1 |
| 20150078680 | Shakib et al. | Mar 2015 | A1 |
| 20150082250 | Wagner et al. | Mar 2015 | A1 |
| 20150130719 | Wehrenberg et al. | May 2015 | A1 |
| 20150177979 | Johansson et al. | Jun 2015 | A1 |
| 20150180980 | Welinder et al. | Jun 2015 | A1 |
| 20150185995 | Shoemaker et al. | Jul 2015 | A1 |
| 20150213001 | Levy et al. | Jul 2015 | A1 |
| 20150227611 | Xuan et al. | Aug 2015 | A1 |
| 20150227782 | Salvador et al. | Aug 2015 | A1 |
| 20150242689 | Mau | Aug 2015 | A1 |
| 20150244794 | Poletto et al. | Aug 2015 | A1 |
| 20150256491 | Eatough et al. | Sep 2015 | A1 |
| 20150262062 | Burger et al. | Sep 2015 | A1 |
| 20150287162 | Canan et al. | Oct 2015 | A1 |
| 20150309698 | Senderek et al. | Oct 2015 | A1 |
| 20150363409 | Wood et al. | Dec 2015 | A1 |
| 20160004820 | Moore | Jan 2016 | A1 |
| 20160019388 | Singla et al. | Jan 2016 | A1 |
| 20160044269 | Kang | Feb 2016 | A1 |
| 20160048263 | Hiraga et al. | Feb 2016 | A1 |
| 20160054845 | Takahashi et al. | Feb 2016 | A1 |
| 20160073034 | Mukherjee et al. | Mar 2016 | A1 |
| 20160110355 | Charania et al. | Apr 2016 | A1 |
| 20160140146 | Wexler et al. | May 2016 | A1 |
| 20160202889 | Shin et al. | Jul 2016 | A1 |
| 20160226804 | Hampson et al. | Aug 2016 | A1 |
| 20160234184 | Liu et al. | Aug 2016 | A1 |
| 20160239724 | Arfvidsson et al. | Aug 2016 | A1 |
| 20160255162 | Frieder et al. | Sep 2016 | A1 |
| 20160283483 | Jiang et al. | Sep 2016 | A1 |
| 20160321831 | Nakamura et al. | Nov 2016 | A1 |
| 20170019587 | Matas et al. | Jan 2017 | A1 |
| 20170026430 | Beckhardt et al. | Jan 2017 | A1 |
| 20170041549 | Kim et al. | Feb 2017 | A1 |
| 20170063753 | Probasco et al. | Mar 2017 | A1 |
| 20170093780 | Lieb et al. | Mar 2017 | A1 |
| 20170139554 | Nakabayashi et al. | May 2017 | A1 |
| 20170169295 | Park et al. | Jun 2017 | A1 |
| 20170192625 | Kim et al. | Jul 2017 | A1 |
| 20170244959 | Kumar et al. | Aug 2017 | A1 |
| 20170344257 | Gnedin et al. | Nov 2017 | A1 |
| 20170357382 | Miura et al. | Dec 2017 | A1 |
| 20170357409 | Wagner et al. | Dec 2017 | A1 |
| 20180034765 | Keszler et al. | Feb 2018 | A1 |
| 20180039406 | Kong et al. | Feb 2018 | A1 |
| 20180068019 | Novikoff et al. | Mar 2018 | A1 |
| 20180083901 | Mcgregor et al. | Mar 2018 | A1 |
| 20180143761 | Choi et al. | May 2018 | A1 |
| 20180181668 | Zhang et al. | Jun 2018 | A1 |
| 20180204111 | Zadeh et al. | Jul 2018 | A1 |
| 20180321048 | Li et al. | Nov 2018 | A1 |
| 20180364872 | Miura et al. | Dec 2018 | A1 |
| 20180367862 | Horii et al. | Dec 2018 | A1 |
| 20190073081 | Takahashi et al. | Mar 2019 | A1 |
| 20190258383 | Wagner et al. | Aug 2019 | A1 |
| 20190313012 | Matas | Oct 2019 | A1 |
| 20190339822 | Devine et al. | Nov 2019 | A1 |
| 20200356222 | Clarke et al. | Nov 2020 | A1 |
| 20200356590 | Clarke et al. | Nov 2020 | A1 |
| 20200363932 | Wagner et al. | Nov 2020 | A1 |
| 20210191578 | Miura et al. | Jun 2021 | A1 |
| 20210243356 | Matas et al. | Aug 2021 | A1 |
| 20220206647 | Clarke et al. | Jun 2022 | A1 |
| 20220276750 | Miura et al. | Sep 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 1404233 | Mar 2003 | CN |
| 1619541 | May 2005 | CN |
| 1717918 | Jan 2006 | CN |
| 1756273 | Apr 2006 | CN |
| 101196786 | Jun 2008 | CN |
| 101291409 | Oct 2008 | CN |
| 101854278 | Oct 2010 | CN |
| 102483758 | May 2012 | CN |
| 102681847 | Sep 2012 | CN |
| 102693311 | Sep 2012 | CN |
| 103081496 | May 2013 | CN |
| 104035666 | Sep 2014 | CN |
| 105103154 | Nov 2015 | CN |
| 105264480 | Jan 2016 | CN |
| 105874447 | Aug 2016 | CN |
| 107430483 | Dec 2017 | CN |
| 107710197 | Feb 2018 | CN |
| 1124175 | Aug 2001 | EP |
| 1148412 | Oct 2001 | EP |
| 1289210 | Mar 2003 | EP |
| 2509074 | Oct 2012 | EP |
| 2830093 | Mar 2003 | FR |
| 2420260 | May 2006 | GB |
| 2550639 | Nov 2017 | GB |
| 3-217976 | Sep 1991 | JP |
| 6-309138 | Nov 1994 | JP |
| 8-106469 | Apr 1996 | JP |
| 10-93848 | Apr 1998 | JP |
| 11-164175 | Jun 1999 | JP |
| 11-168694 | Jun 1999 | JP |
| 11-341425 | Dec 1999 | JP |
| 2000-112997 | Apr 2000 | JP |
| 2000-138883 | May 2000 | JP |
| 2000-138888 | May 2000 | JP |
| 2000-148591 | May 2000 | JP |
| 2000-163031 | Jun 2000 | JP |
| 2000-221879 | Aug 2000 | JP |
| 2000-244637 | Sep 2000 | JP |
| 2000-244673 | Sep 2000 | JP |
| 2000-350134 | Dec 2000 | JP |
| 2001-136303 | May 2001 | JP |
| 2001-265481 | Sep 2001 | JP |
| 2001-309019 | Nov 2001 | JP |
| 2002-152559 | May 2002 | JP |
| 2003-163820 | Jun 2003 | JP |
| 2003-338975 | Nov 2003 | JP |
| 2003-345491 | Dec 2003 | JP |
| 2003-348432 | Dec 2003 | JP |
| 2004-15586 | Jan 2004 | JP |
| 2004-32346 | Jan 2004 | JP |
| 2004-145291 | May 2004 | JP |
| 2004-153832 | May 2004 | JP |
| 2004-288208 | Oct 2004 | JP |
| 2004-336536 | Nov 2004 | JP |
| 2004-336711 | Nov 2004 | JP |
| 2005-38101 | Feb 2005 | JP |
| 2005-92386 | Apr 2005 | JP |
| 2005-100084 | Apr 2005 | JP |
| 2005-515530 | May 2005 | JP |
| 2005-150836 | Jun 2005 | JP |
| 2005-175991 | Jun 2005 | JP |
| 2005-182320 | Jul 2005 | JP |
| 2005-202483 | Jul 2005 | JP |
| 2005-202651 | Jul 2005 | JP |
| 2005-303728 | Oct 2005 | JP |
| 2005-321516 | Nov 2005 | JP |
| 2005-339420 | Dec 2005 | JP |
| 2006-67344 | Mar 2006 | JP |
| 2006-139340 | Jun 2006 | JP |
| 2006-140865 | Jun 2006 | JP |
| 2006-195592 | Jul 2006 | JP |
| 2006-203809 | Aug 2006 | JP |
| 2006-236249 | Sep 2006 | JP |
| 2007-515775 | Jun 2007 | JP |
| 2007-525775 | Sep 2007 | JP |
| 2007-287014 | Nov 2007 | JP |
| 2008-59614 | Mar 2008 | JP |
| 2008-106469 | May 2008 | JP |
| 2008-518330 | May 2008 | JP |
| 2008-236794 | Oct 2008 | JP |
| 2009-59042 | Mar 2009 | JP |
| 2010-503130 | Jan 2010 | JP |
| 2010-118056 | May 2010 | JP |
| 2013-83689 | May 2013 | JP |
| 2013-84282 | May 2013 | JP |
| 2013-140171 | Jul 2013 | JP |
| 2014-93003 | May 2014 | JP |
| 2014-95979 | May 2014 | JP |
| 5771242 | Aug 2015 | JP |
| 2016-35776 | Mar 2016 | JP |
| 2016-167299 | Sep 2016 | JP |
| 2016-201135 | Dec 2016 | JP |
| 202011127969 | Jul 2022 | JP |
| 10-2005-0101162 | Oct 2005 | KR |
| 10-2006-0032793 | Apr 2006 | KR |
| 10-2012-0058539 | Jun 2012 | KR |
| 10-2012-0092644 | Aug 2012 | KR |
| 10-2013-0026541 | Mar 2013 | KR |
| 10-2014-0067965 | Jun 2014 | KR |
| 10-2015-0131257 | Nov 2015 | KR |
| 10-2015-0131262 | Nov 2015 | KR |
| 10-1611895 | Apr 2016 | KR |
| 9954807 | Oct 1999 | WO |
| 200129702 | Apr 2001 | WO |
| 2003023593 | Mar 2003 | WO |
| 2003081458 | Oct 2003 | WO |
| 2005093550 | Oct 2005 | WO |
| 2005103863 | Nov 2005 | WO |
| 2006020305 | Feb 2006 | WO |
| 2006047697 | May 2006 | WO |
| 2008030779 | Mar 2008 | WO |
| 2009082814 | Jul 2009 | WO |
| 2009150425 | Dec 2009 | WO |
| 2009155991 | Dec 2009 | WO |
| 2010059188 | May 2010 | WO |
| 2011017653 | Feb 2011 | WO |
| 2011028424 | Mar 2011 | WO |
| 2011051091 | May 2011 | WO |
| 2011084856 | Jul 2011 | WO |
| 2012097385 | Jul 2012 | WO |
| 2014149473 | Sep 2014 | WO |
| 2014149488 | Sep 2014 | WO |
| 2014162659 | Oct 2014 | WO |
| 2014200734 | Dec 2014 | WO |
| 2016077834 | May 2016 | WO |
| 2016160632 | Oct 2016 | WO |
| Entry |
|---|
| US 2002/0018582 A1, 02/2002, Hagiwara et al. (withdrawn) |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/145,033, dated Apr. 30, 2021, 4 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 19724963.4, dated Jun. 22, 2021, 2 pages. |
| Final Office Action received for U.S. Appl. No. 16/145,033, dated Jul. 6, 2021,113 pages. |
| Intention to Grant received for European Patent Application No. 19724963.4, dated Sep. 20, 2021, 7 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 19724963.4, mailed on Sep. 3, 2021, 6 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201811136445.7, dated Aug. 11, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-000224, dated May 7, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-094529, dated Sep. 6, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7018255, dated Feb. 24, 2021, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2019266054, dated Aug. 23, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2019266054, dated Jun. 29, 2021, 3 pages. |
| Office Action received for Chinese Patent Application No. 201811136445.7, dated Apr. 14, 2021, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-138559, dated Apr. 9, 2021, 30 pages (6 pages of English Translation and 24 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-138559, dated Jul. 26, 2021, 37 pages (5 pages of English Translation and 32 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-079486, dated Jul. 16, 2021, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 19724963.4, mailed on Jul. 8, 2021, 3 pages. |
| Result of Consultation received for European Patent Application No. 19724963.4, mailed on May 31, 2021, 3 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17813778.2, mailed on Aug. 13, 2021, 13 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/584,776, dated May 13, 2021, 4 pages. |
| Advisory Action received for U.S. Appl. No. 14/253,783, dated Feb. 15, 2017, 6 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/109,487, dated Apr. 21, 2020, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/584,783, dated May 4, 2020, 3 pages. |
| Applicant-Initiated Interview Summary for U.S. Appl. No. 16/402,057, dated Mar. 16, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/145,033, dated Jun. 29, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/145,033, dated Nov. 24, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/450,531, dated Aug. 11, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,776, dated May 13, 2020, 9 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,776, dated Nov. 25, 2020, 5 pages. |
| Certificate of Examination received for Australian Patent Application No. 2019100490, dated Oct. 16, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 13/666,943, dated Aug. 11, 2016, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/281,524, dated Jun. 3, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/402,057, dated Jul. 6, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/450,531, dated Nov. 12, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/450,531, dated Oct. 30, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/983,815, dated Mar. 31, 2021, 6 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870385, dated Mar. 26, 2020, 2 pages. |
| Decision to Grant received for European Patent Application No. 11178259.5, dated Apr. 4, 2019, 3 pages. |
| European Search Report received for the European Patent Application No. 10172417.7, dated Jan. 7, 2011, 4 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 16/584,783, mailed on Feb. 17, 2021, 9 pages. |
| Examiner's Pre-Review Report received for Japanese Patent Application No. 2018-138559, dated Jul. 29, 2020, 6 pages. |
| Extended European Search Report received for European Patent Application No. 17813778.2, dated Jan. 10, 2020, 12 pages. |
| Extended European Search Report received for European Patent Application No. 18197554.1, dated Jun. 3, 2019, 11 pages. |
| Final Office Action received for U.S. Appl. No. 15/281,524, dated Dec. 27, 2018, 6 pages. |
| Final Office Action received for U.S. Appl. No. 16/145,033, dated Sep. 22, 2020, 49 pages. |
| Final Office Action received for U.S. Appl. No. 16/402,057, dated Oct. 17, 2019, 23 pages. |
| Final Office Action received for U.S. Appl. No. 16/584,783, dated May 19, 2020, 19 pages. |
| Final Office Action received for U.S. Appl. No. 14/253,783, dated Sep. 30, 2016, 18 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870385, dated Jan. 24, 2020, 2 pages. |
| Intention to Grant received for European Patent Application No. 11178259.5, dated Nov. 8, 2018, 16 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/035322, dated Dec. 27, 2018, 13 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/024790, dated Nov. 19, 2020, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/048169, dated Oct. 21, 2011, 9 pages. |
| International Search Report and Written Opinion Received for PCT Patent Application No. PCT/US2017/035322, dated Oct. 5, 2017, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/024790, dated Sep. 11, 2019, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/031442, dated Oct. 30, 2020, 28 pages. |
| Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US2019/024790, dated Jul. 18, 2019, 10 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2017/035322, dated Aug. 7, 2017, 4 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/031442, dated Aug. 25, 2020, 22 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 11178259.5, mailed on Nov. 2, 2018, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/275,294, dated Dec. 23, 2016., 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/275,294, dated Nov. 3, 2017, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/281,524, dated Jun. 19, 2018, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/391,269, dated Aug. 22, 2019, 44 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/687,384, dated Jul. 6, 2018, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/109,487, dated Feb. 5, 2020, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/145,033, dated Feb. 9, 2021, 55 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/145,033, dated Mar. 4, 2020, 50 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/402,057, dated May 23, 2019, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/450,531, dated Jun. 10, 2020, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,776, dated Aug. 18, 2020, 36 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,776, dated Feb. 13, 2020, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,783, dated Jan. 30, 2020, 18 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015201028, dated Mar. 21, 2017., 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017201548, dated Sep. 3, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018214074, dated Aug. 6, 2019, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019264623, dated Jan. 4, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019271873, dated Nov. 30, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017284958, dated Sep. 3, 2019, 3 pages. |
| Notice of Allowance received for Canadian Patent Application No. 2,935,875, dated May 3, 2017, 1 page. |
| Notice of Allowance received for Canadian Patent Application No. 2,984,527, dated Apr. 30, 2020, 1 page. |
| Notice of Allowance received for Chinese Patent Application No. 201811616429.8, dated Aug. 5, 2020, 3 pages. |
| Notice Of Allowance received for Japanese Patent Application No. 2014-259225, dated Feb. 27, 2017., 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2015-129152, dated May 8, 2017, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-057997, dated Apr. 23, 2018, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-132229, dated Jun. 25, 2018, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-123115, dated Nov. 30, 2020, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7034875, dated Dec. 12, 2018, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7007053, dated Dec. 19, 2019, 6 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7007053, dated Mar. 12, 2020, 6 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7005314, dated Mar. 23, 2020, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/666,943, dated Jun. 2, 2016, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/253,783, dated Apr. 14, 2017., 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/253,783, dated Jul. 12, 2017, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/253,783, dated Sep. 5, 2017, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/275,294, dated Jun. 6, 2018, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/275,294, dated Jun. 30, 2017., 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/281,524, dated Apr. 11, 2019, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/687,384, dated Jan. 8, 2019, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/109,487, dated Aug. 18, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/109,487, dated May 12, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/109,487, dated Nov. 23, 2020, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/402,057, dated Mar. 25, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/450,531 dated Sep. 25, 2020, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,776, dated Feb. 1, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/983,815, dated Jul. 26, 2021, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/983,815, dated Mar. 18, 2021, 11 pages. |
| Office Action received for Australian Patent Application No. 2017201548, dated Feb. 26, 2018, 2 pages. |
| Office Action received for Australian Patent Application No. 2018214074, dated May 9, 2019, 2 pages. |
| Office Action received for Australian Patent Application No. 2019100490, dated Jul. 26, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2019264623, dated Sep. 14, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2019271873, dated Oct. 5, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2017284958, dated Dec. 13, 2018, 3 pages. |
| Office Action received for Canadian Patent Application No. 2,984,527 dated Sep. 11, 2018, 5 pages. |
| Office Action received for Canadian Patent Application No. 2,984,527, dated Jul. 25, 2019, 4 pages. |
| Office Action received for Chinese Patent Application No. 201811136445.7, dated Oct. 28, 2020, 17 pages. |
| Office Action received for Chinese Patent Application No. 201811616429.8, dated May 7, 2020, 8 pages. |
| Office Action received for Chinese Patent Application No. 201811616429.8, dated Sep. 4, 2019, 26 pages. |
| Office Action received for Danish Patent Application No. PA201670608, dated Jan. 14, 2019, 7 pages. |
| Office Action received for Danish Patent Application No. PA201670608, dated Jan. 23, 2018, 10 pages. |
| Office Action received for Danish Patent Application No. PA201670609, dated Jan. 26, 2018, 8 pages. |
| Office Action received for Danish Patent Application No. PA201670609, dated Mar. 1, 2019, 9 pages. |
| Office Action received for Danish Patent Application No. PA201670609, dated May 4, 2020, 7 pages. |
| Office Action received for Danish Patent Application No. PA201670609, dated May 7, 2018, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870385, dated Aug. 23, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201970535, dated May 20, 2020, 3 pages. |
| Office Action received for Danish Patent Application No. PA201970535, dated Oct. 27, 2020, 6 pages. |
| Office Action received for European Patent Application No. 11178259.5, dated Nov. 10, 2015, 4 pages. |
| Office Action received for European Patent Application No. 17813778.2, dated Nov. 26, 2020, 10 pages. |
| Office Action received for European Patent Application No. 18197554.1, dated Jun. 15, 2020, 4 pages. |
| Office Action received for European Patent Application No. 19724963.4, dated Jul. 28, 2020, 6 pages. |
| Office Action received for Indian Patent Application No. 9044/CHENP/2014, dated Jan. 24, 2020, 6 pages. |
| Office Action received for Japanese Patent Application No. 2014-259225, dated May 27, 2016, 4 pages. |
| Office Action received for Japanese Patent Application No. 2015-129152, dated Sep. 23, 2016, 3 pages. |
| Office Action received for Japanese Patent Application No. 2017-057997, dated Jan. 9, 2018, 6 pages. |
| Office Action received for Japanese Patent Application No. 2017-132229, dated Mar. 16, 2018, 7 pages. |
| Office Action received for Japanese Patent Application No. 2018-138559, dated Jan. 27, 2020, 7 pages. |
| Office Action received for Japanese Patent Application No. 2018-138559, dated May 13, 2019, 10 pages. |
| Office Action received for Japanese Patent Application No. 2019-123115, dated Aug. 31, 2020, 9 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7007053, dated Mar. 18, 2019, 12 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7007053, dated Sep. 26, 2019, 9 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7018255, dated Sep. 10, 2020, 12 pages. |
| Partial European Search Report received for European Patent Application No. 18197554.1, dated Jan. 22, 2019, 8 pages. |
| Search Report and opinion received for Danish Patent Application No. PA201670608, dated Jan. 3, 2017, 15 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201670609, dated Feb. 1, 2017, 11 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870385, dated Nov. 16, 2018, 10 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970535, dated Nov. 5, 2019, 10 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 11178259.5, mailed on Feb. 19, 2018, 12 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19724963.4, mailed on Dec. 23, 2020, 8 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/584,776, dated Feb. 18, 2021, 3 pages. |
| Decision to Grant received for the European Patent Application No. 07814633.9, dated Sep. 2, 2010, 3 pages. |
| Intention to Grant received for the European Patent Application No. 07814633.9, dated Mar. 19, 2010, 4 pages. |
| Office Action received for European Patent Application No. 07814633.9, dated Aug. 10, 2009, 3 pages. |
| Decision to Grant received for the European Patent Application No. 10172417.7, dated Nov. 14, 2013, 3 pages. |
| Intention to Grant received for European Patent Application No. 10172417.7, dated Jul. 9, 2013, 10 pages. |
| Office Action received for European Patent Application No. 10172417.7, dated Oct. 15, 2010, 3 pages. |
| Office Action received for European Patent Application No. 10172417.7, dated Oct. 31, 2011, 6 pages. |
| Summons to Attend Oral Proceeding received for European Patent Application No. 10172417.7, Jan. 28, 2013, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/848,210, dated Jun. 30, 2011, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/848,210, dated Dec. 20, 2011, 5 pages. |
| Decision to Grant received for the European Patent Application No. 11178257.9, dated Jun. 20, 2013, 3 pages. |
| Extended European Search Report received for European Patent Application No. 11178257.9, dated Oct. 31, 2011, 5 pages. |
| Intention to Grant received for European Patent Application No. 11178257.9, dated Jan. 30, 2013, 9 pages. |
| European Search Report received for the European Application No. 11178259.5, dated Oct. 31, 2011, 8 pages. |
| Office Action received for European Patent Application No. 11178259.5, dated Jan. 4, 2013, 8 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 11178259.5, mailed on Feb. 11, 2015, 9 pages. |
| Office Action received for German Patent Application No. 11200700067.8, dated Sep. 14, 2010. |
| Non-Final Office Action received for U.S. Appl. No. 12/789,441, dated Jan. 17, 2013, 24 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/789,441, dated Dec. 6, 2013, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 12/789,441, dated Aug. 20, 2013, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/361,912, dated Mar. 22, 2012, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/361,912, dated Jul. 2, 2012, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/666,943, dated Oct. 26, 2015, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/666,943, dated Jun. 17, 2015, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/253,783, dated Feb. 23, 2016, 18 pages. |
| Notice of Allowance received for the Canadian Patent Application No. 2,853,273, dated Jan. 12, 2016, 1 page. |
| Office Action received for Canadian Patent Application No. 2,853,273, dated Feb. 23, 2015, 5 pages. |
| Board Opinion received for Chinese Reexamination Patent Application No. 200780001142.8, mailed on Oct. 21, 2014, 13 pages. |
| Office Action Received for Chinese Patent Application No. 200780001142.8, dated Jan. 8, 2010, 9 pages. |
| Decision to Grant received for Japanese Patent Application No. 2009-526943, dated Dec. 2, 2011, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2011265412, dated Nov. 12, 2014, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2013-140171, dated May 29, 2015, 4 pages. |
| Office Action received for Japanese Patent Application No. 2013-140171, dated Jul. 22, 2014, 4 pages. |
| Office Action Received for Japanese Patent Application No. 2014-259225, dated Nov. 20, 2015, 2 pages. |
| Office Action received for Australian Patent Application No. 2015201028, dated Mar. 15, 2016, 2 pages. |
| Office action received for Indian Patent Application No. 2797CHENP2008 , dated Jan. 29, 2014, 3 pages. |
| Office Action Received for Canadian Patent Application No. 2,627,118, dated Mar. 15, 2010, 4 pages. |
| Chen et al., “Event Detection from Flickr Data through Wavelet-based Spatial Analysis”, Proceeding of the 18th ACM Conference on Information and Knowledge Management, CIKM, Jan. 1, 2009, pp. 523-532. |
| Conneally Tim, “Apple Secures A Patent for A Multitouch Methodology”, available at <http://www.betanews.com/article/Apple-secures-a-patent-for-a-multitouch-methodology/1233074799>, Jan. 27, 2009, 1 page. |
| dailywireless.org,“GPS Blogging Phones”, Available online at <http://www.dailywireless.org/2005/08/25/gps-blogging-phones/>, retrieved on Aug. 25, 2005, Aug. 25, 2005, 4 pages. |
| Das et al., “Event Classification in Personal Image Collections”, IEEE Intl. Workshop on Media Information Analysis for Personal and Social Applications at ICME, 2009, 2009, pp. 1660-1663. |
| Das et al., “Event-based Location Matching for Consumer Image Collections”, CIVR, 2008, Proc. of the ACM Int. Conf. on Image and Video Retrieval, 2008, 5 pages. |
| Team 2: Portable Digital Photo Album, Available online at <http://courses.ece.ubc.ca/418/previous/W04/team2/index.html#Section1>, May 8, 2008, 16 pages. |
| Gallagher et al., “Image Annotation Using Personal Calendars as Context”, ACM Intl. Conf. on Multimedia, 2008, 2008, 4 pages. |
| Garmin, “Go, View Map, Save to Favorites, Cancel”, http://www8.garmin.com/buzz/nuvifone/m/g/sc-geotag-lg.jpg, retrieved on Mar. 13, 2015, 1 page. |
| Gears Leigh, “Orange SPV C600 Review”, Available at <http://www.coolsmartphone.com/article569.html>, retrieved on Apr. 14, 2006, 57 pages. |
| Google Earth Blog, “New Improved Panoramio—Geo Photo Sharing”, Available online at: <http://www.gearthblog.com/blog/archives/2006/06/new_improved_pa.html>, 2008, 1 page. |
| Han et al., “Density-Based Methods”, Data Mining Concepts and Techniques, Elsevier, 2006, pp. 418-420. |
| Han Jeffy. , “Multi-Touch Interaction Research”, available at <http://mrl.nyu.edu/˜jhan/ftirtouch/>, retrieved on Apr. 13, 2006, 4 pages. |
| Hinckley et al., “Sensing Techniques for Mobile Interaction”, Symposium on User Interface Software and Technology, CHI Letters, vol. 2, No. 2, Nov. 2000, pp. 91-100. |
| Hughes Neil, “Apple Explores Merging Cloud Content with Locally Stored Media Library”, Available at <http://appleinsider.com/articles/11/02/10/apple_explores_merging_cloud_content_with_locally_stored_media_library.html>, XP55040717, Feb. 10, 2011, 2 pages. |
| Imageviewpro, “The Simple Flash Photo Slide Show”, Available online at <www.imageviewpro.com/instructions>, 2009. |
| Jobs Steve, “iPhone Introduction in 2007 Complete”, available at <https://www.youtube.com/watch?v=9hUlxyE2Ns8>, Jan. 10, 2013, 3 pages. |
| Karlson et al., “AppLens and LaunchTile: Two Designs for One-Handed Thumb Use on Small Devices”, CHI 2005, Papers: Small Devices 1, Apr. 2-7, 2005, pp. 201-210. |
| Kyocera WX300K, “Way to Use a Camera”, JP, Nov. 18, 2005, pp. 206-212. |
| Liao, T.W. “Clustering of Time Series Data—a Survey”, Pattern Recognition. vol. 38, 2005, pp. 1857-1874. |
| Marwan et al., “Generalised Recurrence Plot Analysis for Spatial Data”, Physics Letters A, vol. 360, 2007, pp. 545-551. |
| Mozilla Developer Network, “Mouse Gesture Events”, Available online at <https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Mouse_gesture_events>, May 14, 2009, 3 pages. |
| ms mobiles.com—Simply Mobile, “New Program for Mobile Blogging for Pocket PC Release:My Blog”, Available online at <http://msmobiles.com/news.php/4067.html>, 2005, 1 page. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2007/077441, dated Mar. 10, 2009, 9 pages. |
| International Search Report and Written Opinion, received for PCT Patent Application No. PCT/US2007/077441, dated May 8, 2008, 13 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2007/077441, dated Jan. 28, 2008, , 5 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2011/020403, dated Jul. 19, 2012, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/020403, dated May 26, 2011, 14 pages. |
| Van Wijk et al., “Cluster and Calendar based Visualization of Time Series Data”, IEEE Comput. Soc., 1999, 7 pages. |
| VERSIONTRACKER,“Photogather—7.2.6. Hi-res Image Viewer & Editor for Palm”, Available online at <http://www.versiontracker.com/dyn/moreinfo/palm/4624>, retrieved on Jun. 12, 2006, 2006, 5 pages. |
| Willcom, “Operation Manual for WS003SH”, JP, Dec. 2005, pp. 4-1 to 4-7. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/153,703, dated May 11, 2022, 4 pages. |
| Extended European Search Report received for European Patent Application No. 22152524.9, dated May 2, 2022, 10 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7036310, dated Apr. 26, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2022201561, dated May 2, 2022, 3 pages. |
| Advisory Action received for U.S. Appl. No. 16/145,033, dated Nov. 2, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2020267310, dated Nov. 4, 2021, 2 pages. |
| Notice of acceptance received for Australian Patent Application No. 2021202225, dated Jun. 20, 2022, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/125,744, dated Oct. 21, 2021, 11 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020267396, dated Dec. 7, 2021, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-138559, dated Dec. 3, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/584,783, dated Dec. 20, 2021, 7 pages. |
| Result of Consultation received for European Patent Application No. 17813778.2, mailed on Dec. 6, 2021, 17 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/145,033, dated Oct. 7, 2021, 4 pages. |
| Decision on Appeal received for U.S. Appl. No. 16/584,783, mailed on Oct. 14, 2021, 12 pages. |
| Decision to Grant received for European Patent Application No. 19724963.4, dated Feb. 3, 2022, 2 pages. |
| Decision to Refuse received for European Patent Application No. 17813778.2, dated Jan. 24, 2022, 17 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 17813778.2, mailed on Jan. 21, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/125,744, dated Feb. 7, 2022, 10 pages. |
| Office Action received for German Patent Application No. 112007000067.8, dated Apr. 23, 2009, 15 pages (7 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for German Patent Application No. 112007000067.8, dated Sep. 14, 2010, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Summons to Oral Proceedings received for German Patent Application No. 112007000067.8, mailed on Dec. 8, 2021, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2021202225, dated Apr. 7, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/125,744, dated Mar. 10, 2022, 2 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020267310, dated Feb. 23, 2022, 3 pages. |
| Office Action received for Korean Patent Application No. 10-2021-7036310, dated Feb. 23, 2022, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2021-566100, dated May 27, 2022, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/125,744, dated Mar. 30, 2022, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/153,703, dated Mar. 30, 2022, 10 pages. |
| Office Action received for Japanese Patent Application No. 2020-079486, dated Mar. 11, 2022, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 18197554.1, mailed on Mar. 23, 2022, 7 pages. |
| T&GG Channel, “Canon IXUS 700 / Screenshots of deleting an image”, Online available at: https://www.youtube.com/watch?v=8BL_L5hKZUM, May 2015, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/125,744, dated Dec. 24, 2021, 2 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/031442, dated Nov. 18, 2021, 21 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019266054, dated Nov. 25, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/125,744, dated Dec. 8, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/153,703, dated Sep. 14, 2022, 2 pages. |
| Extended European Search Report received for European Patent Application No. 22164099.8, dated Aug. 25, 2022, 9 pages. |
| Hourunranta et al., “Video and Audio Editing for Mobile Applications”, Proceedings/2006 IEEE international Conference on Multimedia and Expo, ICME 2006, Jul. 9, 2006, pp. 1305-1308. |
| Hurwitz, Jon, “Interface For Small-Screen Media Playback Control”, Technical Disclosure Commons, Online available at: https://www.tdcommons.org/cgi/viewcontent.cgi?article=4231&context=dpubs_series, Apr. 17, 2020, pp. 1-9. |
| Jin-Chang et al., “Multi-modal Interface Techniques and Its Application for Multimedia Retrieval”, China Academic Journal Electronic Publishing House, 2002, pp. 115-117 (Official Copy Only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Office Action received for Chinese Patent Application No. 202011127969.7, dated Jul. 28, 2022, 25 pages (14 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202111487316.4, dated Aug. 8, 2022, 25 pages (13 pages of English Translation and 12 pages of Official Copy). |
| Office Action received for Indian Patent Application No. 202048019639, dated Sep. 27, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/153,703, dated Aug. 30, 2022, 8 pages. |
| Jin-Chang et al., “Multi-modal Interface Techniques and Its Application for Multimedia Retrieval”, China Academic Journal Electronic Publishing House, 2002, pp. 115-117. Cited by the Chinese Patent Office in an Office Action for related Patent Application No. 202011127969.7, dated Jul. 28, 2022. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 16/145,033, mailed on Aug. 4, 2022, 10 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022201561, dated Jul. 22, 2022, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-079486, dated Oct. 21, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Number | Date | Country | |
|---|---|---|---|
| 20220027039 A1 | Jan 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61335520 | Jan 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16983815 | Aug 2020 | US |
| Child | 17408220 | US | |
| Parent | 16402057 | May 2019 | US |
| Child | 16983815 | US | |
| Parent | 15687384 | Aug 2017 | US |
| Child | 16402057 | US | |
| Parent | 14253783 | Apr 2014 | US |
| Child | 15687384 | US | |
| Parent | 12789441 | May 2010 | US |
| Child | 14253783 | US |
