Patent Grant
11782575
The present disclosure relates generally to computer user interfaces, and more specifically to techniques for viewing and sharing relevant media items.
The size of user media libraries continues to grow, along with the amount of media sharing between device users. As such, devices are increasingly expected to have thoughtfully-designed user interfaces for handling such activity.
Some techniques for viewing and sharing relevant media items using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for viewing and sharing relevant media items. Such methods and interfaces optionally complement or replace other methods for viewing and sharing relevant media items. 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. Further, such methods and interfaces reduce the number of unnecessary, extraneous, or repetitive inputs by a user.
In accordance with some embodiments, a method is performed at a device with a display and one or more input devices. The method comprises: receiving, via the one or more input devices, a first input; in response to receiving the first input, displaying, on the display, a suggested collection of media items for sharing with a recipient, wherein the suggested collection is relevant to a message conversation with the recipient; subsequent to displaying the suggested collection of media items, receiving, via the one or more input devices, a second input representing a request to transmit at least a portion of the suggested collection of media items to the recipient; and in response to receiving the second input, transmitting a message to the recipient as part of the message conversation that provides access to the at least a portion of the suggested collection of media items.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display and one or more input devices, the one or more programs including instructions for: receiving, via the one or more input devices, a first input; in response to receiving the first input, displaying, on the display, a suggested collection of media items for sharing with a recipient, wherein the suggested collection is relevant to a message conversation with the recipient; subsequent to displaying the suggested collection of media items, receiving, via the one or more input devices, a second input representing a request to transmit at least a portion of the suggested collection of media items to the recipient; and in response to receiving the second input, transmitting a message to the recipient as part of the message conversation that provides access to the at least a portion of the suggested collection of media items.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; one or more input devices; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving, via the one or more input devices, a first input; in response to receiving the first input, displaying, on the display, a suggested collection of media items for sharing with a recipient, wherein the suggested collection is relevant to a message conversation with the recipient; subsequent to displaying the suggested collection of media items, receiving, via the one or more input devices, a second input representing a request to transmit at least a portion of the suggested collection of media items to the recipient; and in response to receiving the second input, transmitting a message to the recipient as part of the message conversation that provides access to the at least a portion of the suggested collection of media items.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; one or more input devices; means for receiving, via the one or more input devices, a first input; means for, responsive to receiving the first input, displaying, on the display, a suggested collection of media items for sharing with a recipient, wherein the suggested collection is relevant to a message conversation with the recipient; means for, subsequent to displaying the suggested collection of media items, receiving, via the one or more input devices, a second input representing a request to transmit at least a portion of the suggested collection of media items to the recipient; and means for, responsive to receiving the second input, transmitting a message to the recipient as part of the message conversation that provides access to the at least a portion of the suggested collection of media items.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display and one or more input devices, the one or more programs including instructions for: receiving, via the one or more input devices, a first input; in response to receiving the first input, displaying, on the display, a suggested collection of media items for sharing with a recipient, wherein the suggested collection is relevant to a message conversation with the recipient; subsequent to displaying the suggested collection of media items, receiving, via the one or more input devices, a second input representing a request to transmit at least a portion of the suggested collection of media items to the recipient; and in response to receiving the second input, transmitting a message to the recipient as part of the message conversation that provides access to the at least a portion of the suggested collection of media items.
In accordance with some embodiments, a method is performed at a device with a display and one or more input devices. The method comprises: receiving an indication, from an external device, that a first user has shared a first collection of media items with a second user; subsequent to receiving the indication that the first user has shared the first collection of media items with the second user, outputting a prompt to share, with the first user, one or more suggested media items associated with the second user that are related to the first collection of media items based on a context, wherein: the context is determined based on the first collection of media items, and the one or more suggested media items are not included in the first collection.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display and one or more input devices, the one or more programs including instructions for: receiving an indication, from an external device, that a first user has shared a first collection of media items with a second user; subsequent to receiving the indication that the first user has shared the first collection of media items with the second user, outputting a prompt to share, with the first user, one or more suggested media items associated with the second user that are related to the first collection of media items based on a context, wherein: the context is determined based on the first collection of media items, and the one or more suggested media items are not included in the first collection.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; one or more input devices; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: receiving an indication, from an external device, that a first user has shared a first collection of media items with a second user; subsequent to receiving the indication that the first user has shared the first collection of media items with the second user, outputting a prompt to share, with the first user, one or more suggested media items associated with the second user that are related to the first collection of media items based on a context, wherein: the context is determined based on the first collection of media items, and the one or more suggested media items are not included in the first collection.
In accordance with some embodiments, an electronic device is described. The electronic device comprises: a display; one or more input devices; means for receiving an indication, from an external device, that a first user has shared a first collection of media items with a second user; means for subsequent to receiving the indication that the first user has shared the first collection of media items with the second user, outputting a prompt to share, with the first user, one or more suggested media items associated with the second user that are related to the first collection of media items based on a context, wherein: the context is determined based on the first collection of media items, and the one or more suggested media items are not included in the first collection.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display and one or more input devices, the one or more programs including instructions for: receiving an indication, from an external device, that a first user has shared a first collection of media items with a second user; subsequent to receiving the indication that the first user has shared the first collection of media items with the second user, outputting a prompt to share, with the first user, one or more suggested media items associated with the second user that are related to the first collection of media items based on a context, wherein: the context is determined based on the first collection of media items, and the one or more suggested media items are not included in the first collection.
Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
Thus, devices are provided with faster, more efficient methods and interfaces for viewing and sharing relevant media items, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for viewing and sharing relevant media items.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
There is a need for electronic devices that provide efficient methods and interfaces for viewing and sharing relevant media items. For example, there is a need for electronic devices that provide quick and easy access to relevant sharing suggestions, and improved interfaces for interacting with the media of the sharing suggestion. Further, there is a need for devices that provide improved interfaces for managing and saving received shared media. Such techniques can reduce the cognitive burden on a user who accesses media items for sharing, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
Below,
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.
A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more depth camera sensors 175.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700 and 900 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
In some embodiments, the display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed in proximity of application icon 572B, as shown in
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
As used herein, the terms “open application” or “executing application” refer to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application is, optionally, any one of the following types of applications:
As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
In
At
In some embodiments, the one or more input affordances include a keyboard (e.g., 604D). For example, keyboard 604E shown in
In some embodiments, the suggestion is based on (e.g., one or more) participants in the conversation. For example, device 600 displays input suggestion 606B because there are media items (e.g., in a media library associated with device 600) that include depictions of the participants (e.g., users 603A, 603B, and/or 603C) of the conversation represented by transcript 604A. For example, device 600 displays input suggestion 606B because there are media items (e.g., in a media library associated with device 600) associated with an event known to have been attended by the participants (e.g., users 603A, 603B, and/or 603C) of the conversation represented by transcript 604A. Thus, in the example shown in
As shown in
In some embodiments, an input suggestion (e.g., 606C) is displayed in response to receiving entry at a keyboard (e.g., 604E). For example, as shown in
In some embodiments, a sharing interface includes multiple pages. For example, as shown in
As shown in
In some embodiments, a suggested collection (e.g., such represented by interface 612) is suggested (e.g., by device 600) based on one or more factors. In some embodiments, a suggested collection is determined to be relevant to a message conversation (e.g., represented by transcript 604A). In some embodiments, suggesting a collection includes displaying a suggested collection interface for a suggested collection determined to be relevant to the message conversation. In some embodiments, a suggested collection is suggested based on content (e.g., text, or one or media items) in a transcript (e.g., 604A) of the message conversation.
In some embodiments, content in the transcript is textual content. In some embodiments, a suggested collection is determined to be relevant to the textual content. In some embodiments, the suggested collection of media items is determined to be relevant to the message conversation with the recipient based on a geographic location mentioned (e.g. included) in the transcript of the message conversation. For example, device 600 can suggest the collection in suggested collection interface 612 based on the message text 604C from William that mentions the geographic location “Lake Tahoe” (e.g., requesting photos from Lake Tahoe last weekend) as shown in
The text relevant to the suggested collection does not need to relate to geography. In some embodiments, the suggested collection of media items is determined to be relevant to the message conversation with the recipient based on a reference to a time (e.g., a textual reference to a particular time, date or date range, or relative description (e.g., last week)) mentioned (e.g. included) in the transcript of the message conversation. For example, device 600 can suggest the collection in suggested collection interface 612 based on the message text 604C from William that mentions the time “last weekend” (requesting photos from Lake Tahoe last weekend) as shown in
The text relevant to the suggested collection does not need to relate to time or geography. For example, other text (e.g., phrases or keywords) in a message conversation can cause a relevant collection of media items to be suggested for sharing. For instance, mention of the term “birthday” can cause a suggestion of a collection of media from a birthday celebration (e.g., includes birthday in the title, or is on a date known to be the birthday of one or more persons depicted in the collection). Of course, other text in a message conversation can be relevant to a collection of media items.
In some embodiments, content in the transcript is media content. In some embodiments, a suggested collection is determined to be relevant to the media content. For example, the suggested collection of interface 612 can be suggested by device 600 based on the received media items shared by William. In this example, the received media items shared by William (represented by 604B) are associated with the location Lake Tahoe and the time range December 1 to December 4. Notably, device 600 can suggest the suggested collection represented by suggested collection interface 612 because the suggested collection is also associated with the location Lake Tahoe and the time range December 1 to December 4.
In some embodiments, the suggested collection of media items is determined to be relevant to the message conversation with the recipient based on the identity of one or more participants in the message conversation. In some embodiments, a participant is a user associated with a user account (e.g., of cloud based service, of social media). In some embodiments, a participant is a contact (e.g., from an address book) associated with the device (e.g., 600) or a user of the device. In some embodiments, the suggested collection of media items is a collection of media items in which one or more of the participants (or more than a threshold number of the participants) in the conversation appear in media items in the suggested collection. For example, the suggested collection of media items (of 612) includes media items taken during a camping trip (e.g., to Lake Tahoe) that some or all of the participants (e.g., 603A, 603B, and 603C) in the conversation attended. Thus the collection of media items is suggested for sharing with the participants in the conversation because the participants in the conversation attended the camping trip.
In some embodiments, the suggested collection of media items is determined to be relevant to the message conversation with the recipient based on an event known to have been attended by one or more participants in the message conversation. In some embodiments, an event includes media items captured at one or more geographic locations and within a particular time range. For example, the suggested collection of interface 612 corresponds to an event defined by, and optionally includes media items captured at, the geographic location “Lake Tahoe” and the time range December 1 to December 4. In some embodiments, an event is automatically determined (e.g., based on geographic locations and capture times of the media items). In some embodiments, the event is user-created (e.g., a user creates a collection manually using device 600). As an example, suggested collection interface 612 can be suggested based on data associated with the suggested collection that indicates the participants in the conversation attended an event associated with the suggested collection. For instance, the suggested collection of media items, represented by suggested collection interface 612, can correspond to an event (e.g., Lake Tahoe media taken between December 1 and December 4) known to have been attended by William (e.g., based on identification of a face associated with William in media items of the suggested collection, or based on other metadata associated with the media items of the suggested collection).
At
In some embodiments, the device (e.g., 600) displays one or more interfaces associated with applications other than the photos application. For example, application selector region 610A in
In some embodiments, in response to selection of the application affordance (e.g., 604G), the device (e.g., 600) displays a sharing interface not associated with a photos application. For example, in response to user input 616, device 600 can display an interface associated with affordance 610A (e.g., an application storefront for accessing interfaces to download one or more applications) or with affordance 610C (e.g., interfaces for sharing content music-related). In some embodiments, while displaying a sharing affordance not associated with a photos application, the device displays a sharing interface associated with the photos application in response to user input. For example, the user input can be one or more swipes at a location of one or more other sharing interfaces. For instance, two left swipes from an interface of the music application (represented by affordance 610C) causes sharing interface 610 associated with the photos application to be displayed (e.g., because the respective affordances 610B and 60C are separated by one icon). For example, if a sharing interface includes multiple pages (e.g., like 610), a swipe received while displaying an end page in a direction away from the other pages causes the device to display a sharing interface for the next adjacent application. In some embodiments, the most recent sharing interface is displayed in response to selection (e.g., 616) of an application affordance (e.g., 604G). For example, if the sharing interface 610 was the most recently displayed sharing interface that was previously displayed, device 600 displays sharing interface 610 in response to user input 616.
In some embodiments, the device (e.g., 600) displays a suggested collection interface (e.g., 612) without displaying a sharing interface (e.g., 610). For example, as described herein throughout, device 600 can display one or more elements of a suggested collection interface (e.g., 612) without displaying a sharing interface (e.g., 610) (e.g., without displaying paging dots, or application affordances).
In some embodiments, suggested collections determined to be relevant to the message conversation are displaying in an order (e.g., of descending relevance). In some embodiments, the order is based on relevance to the message conversation. For example, if the suggested collection of interface 612 is related to the transcript 604A in
In this example, the photos requested by William in transcript 604A correspond to the suggested collection represented by suggested collection interface 612 (e.g., the “first” suggested collection). Thus, the user can swipe to return to interface 612. At
In some embodiments, the device (e.g., 600) enters into a selection mode (e.g., in response to user input) after displaying a suggested collection interface (e.g., 612). In some embodiments, the device (e.g., 600) is in selection mode (e.g., initially) upon display of a suggested collection interface (e.g., 612). In some embodiments, a suggested collection interface (e.g., 612) includes one or more of the features of 814, as described below.
In some embodiments, the device (e.g., 600) shares fewer than all of the media items in a suggested collection. In some embodiments, a suggested collection interface (e.g., 612) has fewer than all media items selected initially. For example, a curated set of fewer than all media items can be selected and presented upon the initial display of interface 612 (e.g., similar to as shown in
As shown in
In some embodiments, a change to the selection of media items causes a displayed indication (e.g., 612E) of an amount of selected media to be updated. In some embodiments, the indication of the amount of selected media is included in a sharing affordance (e.g., 612E). For example, as shown in
As shown in
In some embodiments, a one-up view (e.g., 636) includes an indication of an amount of media items that are currently selected. In some embodiments, a one-up view includes an indication of a total amount of media items in the respective collection of media items. For example, indicator 636D shown in
While displaying a media item in the one-up view, the device optionally provides the user with the option to view another media item from the suggested collection in the one-up view without having to return to the grid view. In some embodiments, the device receives user input (e.g., 638) while displaying a first media item in a one up view, and in response, replaces display of the first media item (e.g., 612G in
As shown in
In some embodiments, in response to toggling selection, the device updates an indication of an amount of selected media. For example, as shown in
In some embodiments, the device (e.g., 600) receives user input and, in response to receiving the user input, replaces display of the one-up view with display of the grid view. For example, at
In some embodiments, the set of media items that are currently selected is independent of how the media items are viewed. For example,
At
In some embodiments, in response to receiving selection of a sharing affordance, the device (e.g., 600) inserts a representation (e.g., 604H) of the suggested collection of media items (e.g., represented by suggested collection interface 612) into a text entry field (e.g., of a messaging interface). For example, in response to receiving user input 646, device 600 displays message interface 604 as shown in
In some embodiments, the device (e.g., 600) receives input of text in a text entry field that includes a representation of a suggested collection. For example, in FIG. AJ, device 600 receives input of the text “Here you go!” (e.g., via typing in keyboard region) to accompany representation 604H.
In some embodiments, the device (e.g., 600) receives user input (e.g., 647) selection of a send affordance (e.g., 604I) of a message interface (e.g., 604). In some embodiments, in response to receiving selection of the send affordance, the device (e.g., 600) transmits a message (e.g., 604J) that provides access to the suggested collection. For example, at
As shown in
In some embodiments, a representation of a suggested collection includes descriptive information (e.g., title, date, geographic location). For example, representation 604H includes text representing a geographic location associated with the suggested collection, “Lake Tahoe”. This can also be considered the title of the suggested collection, however a title can be different than a geographic location associated with the collection (e.g., “Lake Tahoe” could instead have the title “Lynne's Birthday Celebration” as defined by (e.g., user-defined) metadata associated with the suggested collection). In some embodiments, a representation of a suggested collection includes an indication of time. For example, representation 604H includes the text “December 1 to 4”, representing the dates December 1st to December 4th. In some embodiments, a representation of a suggested collection includes an indication of an amount of media being shared. For example, representation 604H includes the text “22 photos and 1 video”, identifying the number of photos and videos being shared. In some embodiments, a representation of a suggested collection includes an expiration time. For example, representation 604H includes the text “Link expires January 8”, which indicates that the access provided to a recipient (e.g., via a link) will expire at a particular time.
In some embodiments, a representation (e.g., 604H) of a collection includes an indication of transmission status (e.g., uploading, downloading, and/or a progress of the upload/download). In some embodiments, a representation (e.g., 604H) of a collection includes link expiration time (e.g., expires in 13 days). For example, in
At
In some embodiments, a personalized media interface includes representations of one or more pre-selected collections of media items related based on a context. For example, personalized media interface 658 includes a memories region 658B, that includes representations of collections that are related to a context (e.g., the location San Diego during the month of November 2017, or the location Washington D.C. during the summer of 2017). In some embodiments, the pre-selection collections can be shared (e.g., similar to a suggested collection). In some embodiments, the pre-selected collections are related to one or more of a message conversation and/or one or more recipients associated with device 600.
As described above, a sharing suggestion region 658A can include one or more suggestions (e.g., prompts) to share one or more suggested collections of media items with one or more suggested recipients. Sharing suggestion region 658A includes a prompt 660 to share a suggested collection of media items with four suggested potential recipients (e.g., represented by the four faces under the title card). In some embodiments, the prompt includes an indication of the one or more recipients. In some embodiments, an indication of a recipient includes an identified face associated with the recipient. In this example, four identified faces 660A are shown in prompt 660, each representing a suggested recipient. In some embodiments, an indication of a recipient includes a name associated with the recipient. In this example, only three of the identified faces are associated with names, and thus prompt 660 only includes three names 660B: Sue, Anna, and John. Thus, in this example, the fourth face was identified as having been depicted in at least one media item in the suggested collection of media items, however the identified face has not been matched with a known profile (e.g., a profile that includes one or more of a name or contact information associated with an identified face). In some embodiments, the identified face is not matched because a profile for the face does not exist. In some embodiments, the identified face is not matched because a profile for the recipient has not previously been associated with any identified face. For example, the device 600 includes correct contact information for the person of the identified face, but the contact information is not associated with the identified face in device 600.
In some embodiments, a suggested recipient is suggested based on an identified face associated with the recipient. As touched on above, a suggested recipient displayed at prompt 660 can be a recipient whose identified face is present in one or more media items in the suggested collection of media items. In this example, at least one media item from the suggested collection “Lake Tahoe” includes a depiction of the respective identified faces of each of Sue, Anna, and John. Further, as will be explained in detail below, a suggested recipient can be an identified face for which contact information is not currently associated (e.g., by device 600). In this way, by presenting the user with a face depicted in the photos, the user can be reminded of parties to whom they may wish to send data, even if the device is not currently able to (e.g., lacks associated contact information). Further, as shown below with respect to
In some embodiments, the prompt (e.g., 660) includes information associated with the suggested collection. In some embodiments, the information includes one or more of a title of the suggested collection, an indication of an event associated with the suggested collection, an indication of a geographic location associated with the suggested collection, or an indication of a time (e.g., date, date range) associated with the suggested collection. For example, prompt 660 includes an indication 660C of a geographic location “Lake Tahoe” and an indication 660D of a time range “December 1 to 4”. In some embodiments, the prompt includes one or more representations of one or more media items of the suggested collection of media items. For example, prompt 660 includes a title card 660E which depicts a media item (e.g., photo) from the Lake Tahoe collection. In other examples, the media item is a video or images played in sequence.
As can be seen in
In some embodiments, in response to user input (e.g., 656), the device (e.g., 600) displays a prompt to share a different suggested collection (e.g., than the suggested collection of 612) with a recipient (e.g., 603B, William). For example, after navigating to a sharing interface (e.g., “For You” tab) of a photos application (e.g., after displaying the message conversation in a messaging application), the device displays one or more additional suggestions for sending to the recipient that was already shared with, William. In this way, the device provides a convenient path to share additional content (e.g., related to one or more conversations or other contexts) with the recipient with whom the user of the current device is in a sharing relationship (e.g., a suggestion was previously made or the user previously transmitted access to media items).
In some embodiments, in response to user input (e.g., 656), the device (e.g., 600) displays a different suggested media collection (e.g., of 626) if a first suggested collection (e.g., of 612) was previously transmitted to the recipient. For example, the device provides a new suggestion after the first suggested collection of interface 612 was shared by the user (e.g., as shown in
In some embodiments, in response to user input (e.g., 656), the device (e.g., 600) displays a different suggested media collection if the first suggested collection (e.g., of 612) was not previously transmitted to the recipient. For example, the device provides a new suggestion if the first suggestion was not acted upon by the user. In some embodiments, if the first suggested collection (e.g., of 612) was not previously shared, in response to receiving user input (e.g., 656), the device displays a prompt to share the first suggested collection (e.g., 612) with the recipient. For example, if the user has not previously transmitted access to the suggested collection while in a messages application, the device provides a prompt and opportunity to transmit the suggested collection to the recipient again (e.g., at a personalized media interface 658 of a photos application).
Using the prompt 660 in sharing suggestion region 658A, a user can easily share a suggested collection of media items with one or more suggested recipients. In some embodiments, the device (e.g., 600) receives user input (e.g., 662) associated with a prompt (e.g., 660) in the sharing suggestion region (e.g., 658A). For example, at
In some embodiments, in response to user input (e.g., 662) associated with the prompt (e.g., 660), the device (e.g., 600) transmits a message to one or more suggested recipients that provides access to the suggested collection of media items. For example, in response to user input 662, device 600 immediately shares (e.g., transmits a message) the suggested collection with one or more of the suggested recipients (e.g., Sue, Anna, John).
At
In some embodiments, a recipient confirmation interface (e.g., 666) includes an affordance for adding a recipient. For example, recipient confirmation interface 666 includes affordance 666F. In this example, in response to user input corresponding to selection of 666F, device 600 provides an interface for selecting one or more additional recipient. An interface for selecting one or more additional recipient can include one or more of the features of contact selection user interface 670 of
As described briefly above, device 600 can provide a quick and easily-accessed interface for associating a suggested recipient with contact information. In some embodiments, the device (e.g., 600) receives user input associated with a suggested recipient (e.g., not associated with contact information). For example, at
In some embodiments, in response to receiving user input associated with a suggested recipient, the device (e.g., 600) provides (e.g., displays) an interface for associating the suggested recipient with contact information. For example,
At
In some embodiments, the device (e.g., 600) receives user input associated with a suggested recipient, and in response to receiving such input, toggles selection of the suggested recipient. For example, at
In some embodiments, a recipient confirmation interface (e.g., 666) includes one or more affordances for sharing the corresponding suggested collection of media items. For example, as shown in
At
In some embodiments, the device receives user input (e.g., 679) associated with (e.g., corresponding to selection of an affordance associated with) a collection of media items that has been shared. For example, at
In some embodiments, in response to receiving user input (e.g., 679) associated with a collection of media items that have been shared, the device (e.g., 600) displays a shared collection management interface (e.g., 678). For example, in response to receiving user input 679, device 600 displays exemplary shared collection management interface 680, as shown in FIG. 6AAA. In some embodiments, a shared collection management interface (e.g., 680) includes information related to the shared collection, including one or more of the following (as shown in FIG. 6AAA): a geographic location (e.g., Lake Tahoe), a time (e.g., December 1 to 4), an amount of media items shared (e.g., 22 photos and 1 video), an expiration time (e.g., January 8), and recipient information (e.g., the collection was shared with William and Gregg).
The device optionally provides the user with the option to cease sharing a previously shared collection of media items that can still be accessed by one or more recipients (e.g., access to a shared collection has not expired). In some embodiments, an interface (e.g., 680) associated with a personalized media interface (e.g., 658) includes an option (e.g., 680A) to cease sharing the collection of media items. For example, shared collection management interface 680 includes affordance 680A for ceasing to share the associated shared collection from Lake Tahoe.
At FIG. 6AAB, device 600 receives user input 682 corresponding to selection of affordance 680A, representing a request to stop (also referred to as cease) sharing the associated collection of media items. In some embodiments, in response to receiving user input representing a request to stop sharing a collection of media items, the device (e.g., 600) ceases providing access to one or more of the recipients of the shared collection. For example, if the device 600 previously provided access via predetermined cloud-based service to a user account, such access (e.g., permission to access the media items) can be revoked by transmitting a message to the cloud-based service (e.g., a server). For example, if device 600 previously provided a direct link for accessing the media items, the device can cause such link to be deactivated. For instance, if the media items are hosted on a server and accessed via the link, the device 600 can transmit a message that causes the server to cease to provide access to the media items when a device requests a connection via the address in the link (e.g., deactivates the link).
FIG. 6AAC illustrates an exemplary representation of an expired shared collection of media items. For example, FIG. 6AAC depicts message interface 604, which includes transcript 604A and representation 604H, representing the Lake Tahoe collection of media items shared by Lynne, the user of device 600. In some embodiments, a shared collection of media items expires in response to an expiration time passing. For example, in
As described below, method 700 provides an intuitive way for sharing a suggested collection of media items. The method reduces the cognitive burden on a user for sharing a collection of media items, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to share a collection of media items faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 600) receives (702), via the one or more input devices (e.g., one or more of a touch sensitive display, a touch sensitive surface, a mouse, or the like), a first input (e.g., 608, 614, 616, 620, or 656).
In response to receiving the first input, the electronic device (e.g., 600) displays (704), on the display (e.g., 602), a suggested collection of media items (e.g., represented by 612) for sharing with a recipient (e.g., 603B, 603C), wherein the suggested collection is relevant to a message conversation (e.g., transcript 604A of message interface 604 in
Displaying a suggested collection of media items for sharing with a recipient that is relevant to a message conversation with that recipient allows the user to quickly identify media that the user is likely to want to share with the recipient. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
Subsequent to displaying the suggested collection of media items, the electronic device (e.g., 600) receives (706), via the one or more input devices, a second input (e.g., 630 of
In response to receiving the second input, the electronic device (e.g., 600) transmits (708) a message (e.g., 631 of
In some embodiments, further in response to receiving the first input, and while displaying at least a portion of the suggested collection of media items, the electronic device (e.g., 600) displays (710), on the display, an indication of selected media (e.g., 612E of
Displaying an indication of selected media that identifies an initial set of selected media items allows the user to quickly view a pre-selected set of media from a relevant collection of media items, reducing the number of inputs required to select and transmit media items to the recipient. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, while displaying the indication of selected media that identifies the initial set of selected media items, the electronic device (e.g., 600) receives (712), via the one or more input devices, the second input (e.g., 630, or selection of 604I (e.g., 647)) representing the request to transmit at least a portion of the suggested collection of media items to the recipient. In response to receiving the second input, the electronic device (e.g., 600) transmits (714) a message (e.g., 631 as shown in
Transmitting a message to the recipient as part of the message conversation that provides access to the initial set of selected media items allows the user to quickly send a pre-selected set of media from a relevant collection of media items, reducing the number of inputs required to select and transmit media items to the recipient. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the indication of selected media is a first affordance (e.g., 612E) and the second input (e.g., 630, 646) corresponds to selection (716) of the first affordance, and the first affordance includes an indication of an amount of media items included in the initial set of selected media items. In some embodiments, an amount of media items corresponds to a total number of selected media items. For example, affordance 612E includes the exemplary amount “ALL” in
In some embodiments, the initial set of selected media items includes (718) fewer than all media items in the suggested collection of media items. For example, suggested collection interface 612 of
In some embodiments, the electronic device (e.g., 600) receives (722), via the one or more input devices, input (e.g., 632 of
Receiving input representing a change to the initial set of selected media items from the suggested collection to form a user-selected set of selected media items from the suggested collection, and transmitting a message to the recipient as part of the message conversation that provides access to the user-selected set of selected media items allows the user to quickly modify a pre-selected set of media from a relevant collection of media items, reducing the number of inputs required to select and transmit media items to the recipient. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the indication (e.g., 612E) of selected media comprises (730) an indication of an amount of media items from the suggested collection that are currently selected, and updating the indication of selected media comprises updating the indication to include display of the amount of media items in the user-selected set of selected media items (e.g., 612E as shown in
Updating the indication to include display of the amount of media items in the user-selected set of selected media items provides the user with visual feedback about the amount of media items that are selected. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, while displaying the suggested collection of media items, and while in a media item selection mode, the electronic device (e.g., 600) receives (734), via the one or more input devices, a third input (e.g., 632 or 634) associated with a first media item (e.g., 612G) of the suggested collection of media items (e.g., represented by interface 612). In accordance with a determination (736) that the third input associated with the first media item is a first gesture (e.g., user input 632) (e.g., a tap on single media), the electronic device: toggles (738) whether the first media item is selected without displaying the first media item in a one-up view (e.g., as shown in
Entering or forgoing entering into a media item selection mode, depending on whether a input that causes a one-up view to be displayed is a second gesture or a first gesture, respectively, provides with user with more control of the device by allowing gesture-dependent, different outcomes from a input. Providing additional control of the device without cluttering the UI with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first gesture (e.g., user input 632) is a tap gesture, and the second gesture (e.g., user input 634) is selected from the group consisting of: a de-pinch gesture (e.g., movement of two contacts apart from each other by more than a threshold distance), a long press gesture (e.g., a contact exceeding a predetermined length of time), and a hard press gesture (e.g., a contact with a characteristic intensity that exceeds a threshold intensity such as a threshold intensity that is greater than a nominal contact detection intensity threshold at which a tap input can be detected).
In some embodiments, while displaying the first media item in the one-up view, and while in the media item selection mode (746) the electronic device (e.g., 600): receives (748), via the one or more input devices, a fourth input (e.g., 640) associated with the first media item displayed in the one-up view (e.g., 612F as shown in
In some embodiments, the suggested collection of media items is determined to be relevant (720) to the message conversation with the recipient based on an identified face associated with the recipient (e.g., face displayed for recipient 603B of
Selecting media items based on an identified face associated with the recipient allows the user to quickly identify media that the user is likely to want to share with the recipient. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the suggested collection of media items is determined to be relevant (732) to the message conversation with the recipient based on an event known to have been attended by the recipient, and one or more media items in the suggested collection of media items for sharing with the recipient are selected based on an indication that the one more media items in the suggested collection are associated with (e.g., depict, or were taken at the time and place of, or include metadata identifying) the event known to have been attended by the recipient. For example, the suggested collection represented by suggested collection interface 612 (e.g., as shown in
Selecting media items based on the event known to have been attended by the recipient allows the user to quickly identify media that the user is likely to want to share with the recipient. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, receiving the first input comprises receiving (752) the first input while displaying, on the display, a transcript (e.g., 604A) of the message conversation with the recipient. For example, device 600 receives user input 608 in
Receiving a input (that causes display of a suggested collection of media items for sharing with a recipient) while displaying a transcript of the message conversation with the recipient allows the user to quickly view and share relevant media with the recipient by reducing the number of inputs needed to access the relevant media. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the suggested collection of media items is determined (754) to be relevant to the message conversation with the recipient based on the identity of one or more participants (e.g., 603B and/or 603C) in the message conversation. For example, a participant can be a user associated with a user account (e.g., of cloud-based service, of a social media service), or a contact (e.g., from an address book) associated with the electronic device or a user (e.g., account) of the electronic device (e.g., 600). In some embodiments, the collection of media items is a collection of media items in which one or more of the participants (or more than a threshold number of the participants) in the conversation appear in media items in the suggested collection. For example, the collection of media items includes photos and/or videos of a camping trip that some or all of the participants in the conversation attended and thus the collection of media items is suggested for sharing with the participants in the conversation because the participants in the conversation attended the camping trip.
Suggesting a collection of media items that are determined to be relevant to participants of a message conversation with the recipient allows the user to quickly identify media that the user is likely to want to share with the recipient. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the suggested collection of media items (e.g., represented by interface 612) is determined (756) to be relevant to the message conversation with the recipient (e.g., 603B) based on content (e.g., text, or media items (images, videos)) of the transcript (e.g., 604A of
Suggesting a collection of media items that are determined to be relevant to content of the transcript of a message conversation with the recipient allows the user to quickly identify media that the user is likely to want to share with the recipient. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the suggested collection of media items (e.g., represented by interface 612) is determined (758) to be relevant to the message conversation with the recipient (e.g., 603B) based on text (e.g., 604C) of messages included in the transcript (e.g., 604A of
In some embodiments, the suggested collection of media items (e.g., represented by interface 612) is determined (760) to be relevant to the message conversation with the recipient (e.g., 603B) based on a reference to a time (e.g., “last weekend” in message 604C) mentioned (e.g. included) in the transcript (e.g., 604A of
In some embodiments, the suggested collection of media items (e.g., represented by interface 612) is determined (762) to be relevant to the message conversation with the recipient (e.g., 603B) based on a geographic location (e.g., “Lake Tahoe” in message 604C) mentioned (e.g. included) in the transcript (e.g., 604A of
In some embodiments, the suggested collection of media items (e.g., represented by interface 612) is determined (764) to be relevant to the message conversation with the recipient (e.g., 603B) based on a collection of media items that was received from the recipient and that is represented in the transcript of the message conversation (e.g., representation 604B). In some embodiments, In some embodiments, the electronic device received the media items in the collection of media items from the recipient that are represented in the transcript. In some embodiments, the electronic device received a link or other data for accessing the media items, in the collection of media items from the recipient that are represented in the transcript, from a remote device (e.g., a server).
In some embodiments, prior to displaying (e.g.,
Displaying an affordance while displaying the transcript allows the user to quickly access media that the user is likely to want to share with the recipient. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, prior to displaying the sharing affordance that corresponds to the suggested collection of media items, and while displaying the transcript (e.g., 604A of
In some embodiments, receiving the first input comprises receiving (776) input (e.g., 614) corresponding to selection of a portion (e.g., 604F of
Receiving input corresponding to selection of a portion of a message in the transcript allows the user to quickly access media that the user is likely to want to share with the recipient that is related to the selected portion, reducing the number of inputs needed to do so. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, prior to receiving the first input (e.g., 620 of
In some embodiments, the input corresponding to selection of the affordance (e.g., 610B) associated with the photos application is the first input and the display of the photos application user interface (e.g., 610) includes display of the suggested collection of media items (e.g., 612) for sharing with the recipient (e.g., 603B). For example, the electronic device can display interfaces 610 and 612 as shown in
In some embodiments, the transcript (e.g., 604A) of the message conversation with the recipient is displayed (778) concurrently with the suggested collection of media items (e.g., represented by interface 612) for sharing with the recipient. For example, transcript 604A is displayed concurrently with suggested collection interface 612 in
In some embodiments, transmitting the message to the recipient as part of the message conversation that provides access to the at least a portion of the suggested collection of media items comprises inserting (7102) a representation (e.g., 631 of
In some embodiments, transmitting the message to the recipient as part of the message conversation that provides access to the at least a portion of the suggested collection of media items comprises (794): in accordance with a determination that the recipient (e.g., 603B) is eligible to receive messages through a predetermined cloud-based service (e.g., a recipient is associated with a device that can receive messages through a specific cloud-based service for sending and/or receiving electronic messages (e.g., via the internet)), the electronic device (e.g., 600) provides (796) access to the at least a portion of the suggested collection of media items through the predetermined cloud-based service, wherein the access provided through the predetermined cloud service restricts access by users other than the recipient; and in accordance with a determination that the recipient is not eligible to receive messages through the predetermined cloud-based service, the electronic device provides (798) access to the at least a portion of the suggested collection of media items by sending a link (e.g., publically-accessible, non-guessable URL) to the recipient, wherein the access provided by sending a link does not restrict access by users other than the recipient. In some embodiments, providing access through the cloud-based service provides access to the recipient only, and the recipient is not permitted or able to forward access to another party (e.g., another user of the cloud-based service). For example, the access provided is limited to an account associated with the recipient.
Providing restricted access to a collection of media through a predetermined service, dependent on whether the recipient is eligible to receive messages through the service, increases the security of sharing media items by the user without requiring additional input. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, transmitting the message to the recipient as part of the message conversation that provides access to the at least a portion of the suggested collection of media items comprises transmitting (7100), to the recipient, the media items in the at least a portion of the suggested collection of media items.
In some embodiments, subsequent to transmitting the message (e.g., 604J of
Causing termination of recipient's access rights increases the security of sharing media items by the user without requiring an excessive number of inputs to ensure control of media items. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, subsequent to transmitting the message to the recipient as part of the message conversation that provides access to the at least a portion of the suggested collection of media items (7104): the electronic device (e.g., 600) receives (7106), via the one or more input devices, a fifth input (e.g., 656 of
Displaying a prompt to share the suggested collection with a suggested recipient different than the recipient allows the user to quickly identify an additional recipient with whom the user is likely to want to share media. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, in response to the fifth input, the device displays a prompt to share a different suggested collection (than the suggested collection displayed in response to the first input) with the recipient (e.g., 603B). For example, after navigating to a sharing interface (e.g., “For You” tab) of a photos application (e.g., after displaying the message conversation in a messaging application), the device displays one or more additional suggestions for sending to the recipient (e.g., 603B). Thus, the device provides a convenient path to share additional content (e.g., related to conversations or other relationship) with the recipient with whom the user of the current device is in a sharing relationship (e.g., a suggestion was previously made or the user previously transmitted access to media items). In some embodiments, the device displays a different suggested media collection if the suggested collection was previously transmitted to the recipient. For example, the device provides a new suggestion after the first suggestion (e.g., of suggested collection interface 612) was acted upon by the user (e.g., sent to recipient 603B). In some embodiments, the device displays a different suggested media collection if the suggested collection was not previously transmitted to the recipient (e.g., 603B). For example, the device provides a new suggestion if the first suggestion was not acted upon by the user. In some embodiments, if the first suggestion was previously not acted upon by the user, in response to receiving the fifth input, the device displays a prompt to share the suggested collection with the recipient. For example, if the user has not previously transmitted access to the suggested collection while in a messages application, the device provides a prompt and opportunity to transmit the suggested collection to the recipient again (e.g., at a sharing interface of a photos application).
In some embodiments, the suggested recipient is suggested based on one or more of (7110): an identified face (e.g., shown in 660A of
In some embodiments, while displaying an interface (e.g., 666 of
In some embodiments, the suggested recipient (e.g., associated with 666E of
Note that details of the processes described above with respect to method 700 (e.g.,
In some embodiments, the device (e.g., 600) receives an indication that a collection of media items has been shared with the device. For example, device 600 can receive a message that includes information for accessing the shared collection (e.g., the media items themselves, a link, or other data for accessing the shared collection). In some embodiments, the device (e.g., 600) displays a representation (e.g., 804C) of the received shared collection. In some embodiments, the device displays the representation of the received shared media collection in a transcript (e.g., 804A) of a message conversation. For example, message interface 804 also includes an exemplary representation 804C of a received shared collection of media items that has been shared with Lynne by William. For example, William has provided access (e.g., as described above) to the shared collection of media items to Lynne (e.g., provided access via a cloud-based service to a device or account associated with Lynne). Techniques for providing access to a collection of media items are discussed above, and hereby incorporated.
In some embodiments, the representation (e.g., 804CD) of the received shared collection includes an indication of transfer status. For example, an indication of transfer status can include an indication that the received shared collection is currently being uploaded or downloaded. As shown in
While a received shared collection is downloading, a representation (e.g., 804C) of the shared collection might cease to be displayed (e.g., due to user action, or due to new messages inserted into a transcript that includes the representation). Accordingly, device 600 can display a notification (e.g., a pop-up window or banner) to provide a user with easy access to the collection upon completion of the download. Thus, the user can continue using device 600 and does not need to continually monitor the download, or perform an extraneous number of inputs to find the original (e.g., selected) representation of the shared collection.
At
At
In some embodiments, the device (e.g., 600) receives user input (e.g., 810) associated with the affordance (e.g., 809) and, in response, displays one or more representations of media items in the received shared collection of media items. For example, at
In response to receiving a shared collection (e.g., 804C), the device 600 optionally provides the user with the option to quickly and easily share back media with the other participants in the conversation. In some embodiments, the device (e.g., 600) displays one or more prompts (e.g., 811A, 813) to share back media in response to receiving an indication that another user (e.g., 805B) has shared media with a user of the device (e.g., 805A). In some embodiments, a prompt (e.g., 811A, 813) is displayed at message interface (e.g., 804) concurrently with a transcript of a message conversation (e.g., 804A). For example,
In some embodiments, user input corresponding to selection of a prompt (e.g., 811A, 813) to share back media causes display of a suggested collection interface (e.g., that includes one or more features as described above with respect to interfaces 612 and/or 634). In some embodiments, user input corresponding to selection of a prompt (e.g., 811A, 813) to share back media causes display of another prompt interface (e.g., 854, described below).
A shared collection interface such as 814 can be used to view media items. For example, still referring to
The device that receives a shared collection of media items optionally provides the user with the option to save one or more of the media items into a media library associated with the user. This can be beneficial because, as described above, access to received shared media can expire. In some embodiments, the receiving party (e.g., of a shared collection) can add one or more media items, from the shared collection, to a media library. In some embodiments, the receiving party can access the media items in the media library after access provided by the sharer has expired (e.g., after expiration time, or after access is revoked). For example, the access provided by the sharer to the shared media can be hosted by a third-party cloud service, which facilitates the sharing from the sharing party to the receiving party. This can provide the benefit of simplifying the process for sharing. For instance, the sharer does not need to worry about creating and maintaining a dedicated connection to the receiving party (e.g., via proximity dependent technology such as Wi-Fi or Bluetooth, or via non-proximity dependent technology such as file transfer protocol (FTP) or a virtual private network (VPN) (or the like) between two devices). Further, the sharer also does not need to worry about facilitating third-party hosting, such as dealing with manually configuring or hosting an environment for sharing (e.g., a website). However, the hosting can be temporary, thus limiting the time for accessing the shared collection.
In view of the above, interfaces for saving media items are discussed below. In some embodiments, a shared collection interface provides the ability to save media items from a received shared collection. In some embodiments, a shared collection interface (e.g., 814) includes an affordance for saving one or more media items to a media library associated with the user of the device (e.g., 600). For example, still referring to
At
The device optionally provides the user with the option to add fewer than all of the media items in a received shared collection to a media library.
At
In some embodiments, while in a selection mode, the device (e.g., 600) disables one or more affordance for saving media items. For example, in
In some embodiments, while in a selection mode, the device (e.g., 600) displays an indication of an amount of media items that are currently selected. For example, in
In some embodiments, in response to entering a selection mode, an initial set of media items are currently selected. In some embodiments, the initial set of media items includes all media items in the collection of media items. For example, in
As described above with respect to one-up view 636 (e.g.,
In some embodiments, navigating between media items in a one-up view can be performed while not in a selection mode. For example, if user input 826 is received while not in a selection mode (e.g., at interface 814 as shown in
In some embodiments, a user input representing a request to toggle selection of a media item corresponds to input at a location of a media item. For example, a user touch anywhere on media item 816B (e.g., not just on a selection indicator or unselected indicator) causes device 600 to select it or unselect it, depending on the current selection state.
In some embodiments, the user input representing a request to toggle selection of a media is selection of an unselected indicator (e.g., 824C). For example, at
In some embodiments, subsequent to (e.g., in response to) a change in the currently selected media items, the device (e.g., 600) updates a displayed indication of an amount of media items that are currently selected. For example, in
After customizing the selection of media items, the device optionally provides the user with the option to add the selected items to a media library (e.g., as discussed previously). At
In some embodiments, a shared collection interface (e.g., 814) in grid view includes one or more features of suggested collection interface 612 as described with respect to
In some embodiments, the device (e.g., 600) transitions a displayed shared collection interface (e.g., 814) from a grid view to a one-up view. In some embodiments, the device (e.g., 600) transitions a displayed shared collection interface (e.g., 814) from a one-up view to a grid view. In some embodiments, the transition is performed in response to user input. For example, device 600 can receive user input (e.g., a tap, a gesture, a key press) at
While displaying media items in a grid view, the device optionally provides the user with the option to select and add one or more of the media items in the received collection into a media library. In some embodiments, while in a grid view, the device (e.g., 600) receives user input (e.g., 834) representing a request to enter into a selection mode and, in response, enters into a selection mode. For example, at
For example, in
In some embodiments, in response to entering into a selection mode, the device (e.g., 600) displays an affordance for saving a selection of media items. For example, in
In some embodiments, while in a selection mode, the device (e.g., 600) displays an indication of an amount of media items that are currently selected. For example, in
In some embodiments, in response to entering a selection mode, an initial set of media items are currently selected. In some embodiments, the initial set of media items includes all media items in the collection of media items. For example, in
As described previously, while in a selection mode, the user can customize selection of media items. In some embodiments, while displaying a shared collection interface (e.g., 814) in a grid view, and while in a selection mode, the device (e.g., 600) receives user input representing a request to toggle selection of a media item. For example, at
In some embodiments, the device (e.g., 600) updates an indication of an amount of currently selected media items in response to toggling selection of a media item. For example,
In some embodiments, in response to receiving user input representing the request to transition to a one-up view that is associated with a location of a media item, the device (e.g., 600) displays the media item in a one-up view. For example, at
In some embodiments, if a request to transition between a grid view and a one-up view is received while the device (e.g., 600) is currently in a selection mode, the device stays in the selection mode after transitioning between the grid view and the one-up view. For example, in
While in selection mode, a user might wish to view a particular media item in a one-up view, without toggling selection of that media item. In some embodiments, in response to receiving a user input associated with a media item that causes a transition between a one-up view and a grid view while in a selection mode, the device (e.g., 600) enters a one-up view without toggling selection of the media item. For example, in response to receiving user input 838 at
In some embodiments, the device (e.g., 600) toggle selections if a user input associated with a location of a media item is a first gesture (e.g., 836), and transitions to a one-up view without toggling selection if the user input (e.g., 838) is a second gesture different than the first gesture. For example, in response to a tap gesture represented by user input 836 (
In some embodiments, the set of media items that are currently selected remain unchanged in response to transitioning between a grid view and a one-up view (e.g., transitioning either from grid view, or to grid view). For example, as shown in
After entering into one-up view and selection mode in response to the same user input (e.g., as shown in
In some embodiments, after adding the media items to the library, the device (e.g., 600) exits selection mode. For example, turning briefly back to
In some embodiments, the library interface is associated with a photos application. For example, displaying library interface 852 can include opening or launching a photos application.
After receiving a shared collection, the device optionally provides the user with the option to view a personalized media interface (e.g., as described above with respect to interface 658 of
In some embodiments, a prompt to share media items includes one or more of the features of sharing prompt 854. In some embodiments, a prompt (e.g., 854) includes an indication of a context. In some embodiments, the context is a context that is related to both the received shared collection and the suggested collection. For example, prompt 854 includes region 854A, which includes text that indicates that the sharer (William) has shared media items related to the location Lake Tahoe and the time period December 1 to 4, and that there are suggested media items (e.g., 854F and 854G) related to that context that are available to share: “William shared his photos from Lake Tahoe December 1 to 4. Would you like to share yours?” In some embodiments, a prompt (e.g., 854) includes representations of one or more suggested media items. For example, prompt 854 includes representations of media items 854F and 854G from the suggested collection. In some embodiments, a prompt (e.g., 854) includes one or more of the features of interfaces 612 and/or 814, as described herein throughout. For example, prompt 854 includes a title card 854B (e.g., that includes an indication of a geographic location associated with the suggested collection (Lake Tahoe), an indication of a time period associated with the suggested collection (“December 1 to 4” (e.g., December 1 to 4)), and a representative image (e.g., from the suggested collection)).
In some embodiments, the prompt includes an affordance for sharing the suggested collection with a recipient (e.g., the user who shared the received collection that causes the prompt to be displayed). For example, prompt 854 includes sharing affordance 854C. In some embodiments, the affordance for sharing (e.g., 854C) includes one or more of the features as described above with respect to any of affordances 604I, 612E, 664A, 666G, or 666H. For example, if the user changes selection of the media items for sharing, affordance 854C can be updated to reflect the number of selected media items (e.g., “Share 22” if 22 media items are selected).
In some embodiments, a prompt (e.g., 854) includes an affordance (e.g., 854D) for entering a selection mode. For example, prompt 854 includes select affordance 854D for entering a selection mode. Select affordance 854D includes one or more of the features as described above with respect to affordance 814E. For example, in response to user selection of select affordance 854D, device 600 enters selection mode (e.g., allowing user-customization of the media items that are selected for sharing). In some embodiments, a prompt (e.g., 854) is displayed (e.g., initially) in selection mode. For example, device 600 can display prompt 854 in selection mode without first requiring user input (e.g., of select affordance 854D). In some embodiments, fewer than all media items of the suggested collection are selected for sharing. For example, the suggested collection of
The discussion above (e.g., with respect to
In some embodiments, the suggested media items are not included in the received shared collection. For example, device 600 suggests media items (e.g., the collection represented by interface 854) to share back with William that were not received in the collection shared by William (e.g., in the shared collection represented by 804C). In this way, device 600 prevents sharing or display of duplicate media items (e.g., already shared between, and thus already possessed by, two users). In some embodiments, the device (e.g., 600) identifies the one or more media items that share the context is performed by the device. In some embodiments, the identifying is performed by a remote device (e.g., a server).
In some embodiments, the prompt (e.g., 854) is displayed in response to further user action after receiving an indication of a shared collection from another user (e.g., 804C of
In some embodiments, the prompt is displayed in response to receiving the indication that a first user (e.g., 803B) has shared a first collection with a second user (e.g., of device 600). For example, as described above, in response to receiving an indication that William (e.g., user 803B) has shared the Lake Tahoe collection associated with representation 804C in
At
In some embodiments, in response to receiving a request to share a suggested collection of media items (e.g., 856), the device (e.g., 600) immediately transmits a message that provides access to media items of the suggested collection (e.g., the selected media items). For example, device 600 can display message interface 804 as shown in
In some embodiments, a representation of a collection of media items is associated with a displayed indication of receipt. For example in
As described below, method 900 provides an intuitive way for sharing a suggested collection of media items that is related to a received collection of media items. The method reduces the cognitive burden on a user for sharing a suggested collection of media items that is related to a received collection of media items, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to share a suggested collection of media items that is related to a received collection of media items faster and more efficiently conserves power and increases the time between battery charges.
The electronic device (e.g., 600) receives (902) an indication, from an external device (e.g., 100, 300, 500), that a first user (e.g., a device or account associated with a first user) has shared (e.g., provided access to (e.g., via a link and/or corresponding permission), or has sent the actual media items) a first collection of media items with a second user (e.g., a device (e.g., 600) or account associated with the second user). For example, in
Subsequent to (e.g., in response to) receiving the indication that the first user has shared the first collection of media items with the second user, the electronic device (e.g., 600) outputs (904) (e.g., displays, on the display) a prompt (e.g., 811A of
Displaying a prompt to share, with the first user, one or more suggested media items associated with the second user that are related to a first collection of media items (shared by the first user) based on a context allows the second user to quickly identify media items that are the user is likely to want to share with the first user. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the prompt (e.g., 854) is output in response to user input (e.g., selection of 811A or 813 of
In some embodiments, identifying the one or more media items that share the context is performed by the electronic device (e.g., 600). In some embodiments, identifying the one or more media items that share the context is performed by one or more remote devices (e.g., a server).
In some embodiments, while displaying a representation (e.g., 854F or 854G of
The electronic device (e.g., 600) receives (912), via the one or more input devices, a first input (e.g., 856 of
In response to receiving the first input (e.g., 856 of
In some embodiments, subsequent to receiving the indication (e.g., 804C of
Selecting suggested media items from a media library of the user that includes media added from the first collection, and excluding from the suggestion the media items from the first collection allows the user to quickly identify and send media items that have not already been received from the first user without requiring an excessive number of inputs or placing a high cognitive burden on the user. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the context is determined (926) based on an identified face being identified in: one or more media items in the first collection of media items, and one or more media items in the one or more suggested media items. In some embodiments, the one or more media items in the first collection of media items, and the one or more media items in the one or more suggested media items are different media items. For example, the exemplary first collection received from William (e.g., 805B), represented in interface 814J of
Using a determined context based on an identified face being depicted in the first collection and in the one or more suggested media items allows the user to quickly identify media that the second user is likely to want to share with the first user, in particular that depicts a face common to both sets of media. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the context is determined (928) based on an event associated with the first collection of media items and the one or more suggested media items. For example, the exemplary first collection received from William (e.g., 805B), represented in interface 814 of
Using a determined context based on an event associated with the first collection and the one or more suggested media items allows the user to quickly identify media that the second user is likely to want to share with the first user. Performing an optimized operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the event corresponds to a range of time, and wherein the first collection and the one or more suggested media items respectively include (930) one or more media items captured during the range of time. In some embodiments, a range of time is a range that begins at a first particular time of day and/or on a first particular date, and ends at a second particular time of day and/or on a second particular date. In some embodiments, media item includes or is associated with metadata indicating that the media item was captured at a particular time within the range of time. For example, the exemplary first collection received from William (e.g., 805B), represented in interface 814 of
In some embodiments, the event corresponds to a geographic location, and the first collection and the one or more suggested media items respectively include (932) one or more media items captured at the geographic location. In some embodiments, media item includes or is associated with metadata indicating that the media item was captured at or near (e.g., in another geographic location) the geographic location. In some embodiments, the event corresponds to a plurality of geographic locations (e.g., media items taken during a road trip at multiple locations). For example, the exemplary first collection received from William (805B), represented in interface 814 of
In some embodiments, subsequent to receiving the indication that the first user has shared the first collection of media items with the second user, the electronic device (e.g., 600) displays (934), on the display, a second affordance (e.g., 804C of
In some embodiments, the electronic device (e.g., 600) receives (936), via the one or more input devices, a third input (e.g., 810 of
In some embodiments, while displaying the interface for viewing the first collection, the electronic device (e.g., 600) displays (940) a third affordance (e.g., 814C of
In some embodiments, prior to receiving the fourth input representing selection of the third affordance, and while displaying the interface for viewing the first collection, the electronic device (e.g., 600) receives (946), via the one or more input devices, a fifth input (e.g., 822 of
In some embodiments, in accordance with a determination (956) that the sixth input is a first gesture (e.g., a tap on a media item) (e.g., user input 828 of
Toggling, or forgoing toggling and entering a one-up view of media item, depending on whether an input is a first gesture or a second gesture, respectively, provides with user with more control of the device by allowing gesture-dependent, different outcomes from a input. Providing additional control of the device without cluttering the UI with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, displaying the representation (e.g., 816B of
In some embodiments, while in the media item selection mode, the electronic device (e.g., 600) receives (962), via the one or more input devices, input (e.g., 828 of
In some embodiments, the interface (e.g., 814 as shown in
Entering or forgoing entering into a media item selection mode, depending on whether an input that causes a one-up view to be displayed is a fourth gesture or a third gesture, respectively, provides with user with more control of the device by allowing gesture-dependent, different outcomes from an input. Providing additional control of the device without cluttering the UI with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the first collection of media items includes a first set of media items that are included in a media library associated with the second user, the first collection of media items includes a second set of media items that are not included in the media library associated with the second user, and displaying the interface for viewing the first collection that includes a depiction of at least a portion of the first collection of media items (e.g., a single media item in a one-up view, or a title card and a plurality of photos from the first collection) comprises: displaying (980) representations of the first set of media items that are not included in the media library associated with the second user without displaying representations of the second set of media items that are included in the media library associated with the second user. For example, the electronic device (e.g., 600) does not display (e.g., at interface 814) representations of media items in the first collection that were already included in the second user's (e.g., 805A) media library before the first user (e.g., 805B) shared the first collection. For example, this can avoid adding duplicate media items to a library and makes more efficient use of display space, by not displaying media items that are not new to the user.
Forgoing displaying representations of the second set of media items that are included in the media library associated with the second user allows the user to view only media items that are not already included in their media library, avoiding display and review of duplicate media items. Performing an operation when a set of conditions has been met without requiring further input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the electronic device (e.g., 600) receives (982), via the one or more input devices, a seventh input (e.g., 806 of
Displaying a third affordance, which causes an interface for viewing the first collection, to be displayed upon completion of a download while content that does not include a first affordance for doing the same is no longer displayed allows the user to quickly access a first collection without requiring excessive input to seek out the first affordance for selection. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
In some embodiments, the indication that the first user has shared the first collection of media items with the second user includes a link for accessing the first collection of media items, and wherein displaying the second affordance (e.g., 804C of
In some embodiments, subsequent to the expiration of the link for accessing the first collection of media items, receiving, via the one or more input devices, a ninth input (e.g., such as 812 of
Displaying the user interface for viewing the first collection in response despite selection of an expired link, in accordance with at least a portion of the first collection having been downloaded, provides the user with quick access to the downloaded media without requiring excessive input to seek out the downloaded media items in a library interface. Reducing the number of inputs needed to perform an operation enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
Note that details of the processes described above with respect to method 900 (e.g.,
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery to users of sharing suggestions or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.
The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted and relevant sharing suggestions that are of greater interest to the user. Accordingly, use of such personal information data enables users to review a sharing suggestion yet control whether to share the content with others. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user's general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.
The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of providing sharing suggestions, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In another example, users can select not to provide, or limit, data for determining sharing suggestions relevant to the user's activity or device. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.
Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and suggested to users by inferring preferences or relevance based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the sharing suggestion services, or publicly available information.
This application claims priority to U.S. Provisional Application No. 62/668,018, entitled “USER INTERFACES FOR SHARING CONTEXTUALLY RELEVANT MEDIA CONTENT”, filed May 7, 2018, the entire content of which is hereby incorporated by reference.
| 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 | Matthew et al. | Oct 1997 | A |
| 5757368 | Gerpheide et al. | May 1998 | A |
| 5784061 | Moran et al. | Jul 1998 | A |
| 5815657 | Willians et al. | Sep 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 |
| 6097371 | Siddiqui et al. | Aug 2000 | A |
| 6154210 | Anderson | Nov 2000 | A |
| 6167469 | Safai et al. | Dec 2000 | A |
| 6199012 | Hasegawa | Mar 2001 | B1 |
| 6237010 | Hui et al. | May 2001 | B1 |
| 6252596 | Garland | Jun 2001 | B1 |
| 6272246 | Takai | Aug 2001 | B1 |
| 6292273 | Dow et al. | Sep 2001 | B1 |
| 6301586 | Yang et al. | Oct 2001 | B1 |
| 6334025 | Yamagami | Dec 2001 | B1 |
| 6351556 | Loui et al. | Feb 2002 | B1 |
| 6416471 | Kumar et al. | Jul 2002 | B1 |
| 6594654 | Salam et al. | Jul 2003 | B1 |
| 6606411 | Loui et al. | Aug 2003 | B1 |
| 6629793 | Miller | Oct 2003 | B1 |
| 6662023 | Helle | Dec 2003 | B1 |
| 6686938 | Jobs et al. | Feb 2004 | B1 |
| 6741268 | Hayakawa | May 2004 | B1 |
| 6784925 | Tomat et al. | Aug 2004 | B1 |
| 6912694 | Harrison et al. | Jun 2005 | B1 |
| 6915011 | Loui et al. | Jul 2005 | B2 |
| 6920619 | Milekic | Jul 2005 | B1 |
| 6950989 | Rosenzweig et al. | Sep 2005 | B2 |
| 6987991 | Nelson | Jan 2006 | B2 |
| 6990452 | Ostermann et al. | Jan 2006 | B1 |
| 7015910 | Card et al. | Mar 2006 | B2 |
| 7139982 | Card et al. | Nov 2006 | B2 |
| 7164410 | Kupka | Jan 2007 | B2 |
| 7167731 | Nelson | Jan 2007 | B2 |
| 7178111 | Glein et al. | Feb 2007 | B2 |
| 7302650 | Allyn et al. | Nov 2007 | B1 |
| 7305350 | Bruecken | Dec 2007 | B1 |
| 7325198 | Adcock et al. | Jan 2008 | B2 |
| 7380212 | Cody et al. | May 2008 | B2 |
| 7419469 | Vacca | Sep 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 | Dec 2009 | B1 |
| 7669135 | Cunningham et al. | Feb 2010 | B2 |
| 7680340 | Luo et al. | Mar 2010 | B2 |
| 7716194 | Williams et al. | May 2010 | B2 |
| 7747625 | Gargi et al. | Jun 2010 | B2 |
| 7773460 | Holt | Aug 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 | Nov 2010 | B2 |
| 7843454 | Biswas | Nov 2010 | B1 |
| 7865215 | Bells et al. | Jan 2011 | B2 |
| 7970240 | Chao et al. | Jun 2011 | B1 |
| 7970827 | Cumberbatch et al. | Jun 2011 | B1 |
| 7991234 | Hamasaki et al. | Aug 2011 | B2 |
| 8024658 | Fagans et al. | Sep 2011 | B1 |
| 8028249 | Loui et al. | Sep 2011 | B2 |
| 8074172 | Kocienda et al. | Dec 2011 | B2 |
| 8105208 | Oleson et al. | Jan 2012 | B2 |
| 8106856 | Matas et al. | Jan 2012 | B2 |
| 8121945 | Rackle et al. | Feb 2012 | B2 |
| RE43260 | Paalasmaa et al. | Mar 2012 | E |
| 8132116 | Schendel | Mar 2012 | B1 |
| 8200669 | Iampietro et al. | Jun 2012 | B1 |
| 8232973 | Kocienda et al. | Jul 2012 | B2 |
| 8255810 | Moore et al. | Aug 2012 | B2 |
| 8290478 | Shim et al. | Oct 2012 | B2 |
| 8305355 | Matas et al. | Nov 2012 | B2 |
| 8339420 | Hiraoka | Dec 2012 | B2 |
| 8352471 | Oami | Jan 2013 | B2 |
| 8406473 | Tanaka | Mar 2013 | B2 |
| 8453940 | Diamond | Jun 2013 | B2 |
| 8462997 | Pettit et al. | Jun 2013 | B2 |
| 8467770 | Ben Ayed | Jun 2013 | B1 |
| 8543081 | Scott et al. | Sep 2013 | B2 |
| 8543927 | McKinley et al. | Sep 2013 | B1 |
| 8554694 | Ward et al. | Oct 2013 | B1 |
| 8566403 | Pascal et al. | Oct 2013 | B2 |
| 8571331 | Cifarelli | Oct 2013 | B2 |
| 8595798 | Anand et al. | Nov 2013 | B2 |
| 8624836 | Miller et al. | Jan 2014 | B1 |
| 8666361 | Chu et al. | Mar 2014 | B2 |
| 8698762 | Wagner et al. | Apr 2014 | B2 |
| 8700158 | Mass et al. | Apr 2014 | B2 |
| 8706628 | Phillips | Apr 2014 | B2 |
| 8825445 | Hoffman et al. | Sep 2014 | B2 |
| 8893023 | Perry et al. | Nov 2014 | B2 |
| 8931703 | Mullen et al. | Jan 2015 | B1 |
| 8934717 | Newell et al. | Jan 2015 | B2 |
| 8948819 | Yun et al. | Feb 2015 | B2 |
| 8996639 | Faaborg et al. | Mar 2015 | B1 |
| 9021034 | Narayanan et al. | Apr 2015 | B2 |
| 9042646 | Das et al. | May 2015 | B2 |
| 9123086 | Freeland et al. | Sep 2015 | B1 |
| 9125566 | Libbus et al. | Sep 2015 | B2 |
| 9143601 | Padmanabhan et al. | Sep 2015 | B2 |
| 9143907 | Caldwell et al. | Sep 2015 | B1 |
| 9164663 | Berard | Oct 2015 | B1 |
| 9183560 | Abelow | Nov 2015 | B2 |
| 9213754 | Zhang et al. | Dec 2015 | B1 |
| 9286546 | O'malley et al. | Mar 2016 | B2 |
| 9317870 | Tew et al. | Apr 2016 | B2 |
| 9338242 | Suchland | May 2016 | B1 |
| 9459792 | Matas et al. | Oct 2016 | B2 |
| 9600178 | Yun et al. | Mar 2017 | B2 |
| 9600630 | Keegan et al. | Mar 2017 | B2 |
| 9740399 | Paek et al. | Aug 2017 | B2 |
| 9800525 | Lerner et al. | Oct 2017 | B1 |
| 9870554 | Leung et al. | Jan 2018 | B1 |
| 9904906 | Kim et al. | Feb 2018 | B2 |
| 9906928 | Kim et al. | Feb 2018 | B2 |
| 9916538 | Zadeh et al. | Mar 2018 | B2 |
| 9998888 | Chang et al. | Jun 2018 | B1 |
| 10003938 | Chang et al. | Jun 2018 | B2 |
| 10013601 | Ebersman et al. | Jul 2018 | B2 |
| 10019136 | Ozog | Jul 2018 | B1 |
| 10051103 | Gordon | Aug 2018 | B1 |
| 10083213 | Podgorny et al. | Sep 2018 | B1 |
| 10204338 | Lee | Feb 2019 | B2 |
| 10275116 | Decker et al. | Apr 2019 | B2 |
| 10303448 | Steven et al. | May 2019 | B2 |
| 10341826 | Chang et al. | Jul 2019 | B2 |
| 10417588 | Kreisel et al. | Sep 2019 | B1 |
| 10425284 | Dellinger et al. | Sep 2019 | B2 |
| 10445425 | Jon et al. | Oct 2019 | B2 |
| 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 |
| 10796480 | Chen et al. | Oct 2020 | B2 |
| 10873786 | Folse et al. | Dec 2020 | B2 |
| 11194467 | Zhu et al. | Dec 2021 | B2 |
| 11327649 | Spivak et al. | May 2022 | B1 |
| 20010014184 | Bubie et al. | Aug 2001 | A1 |
| 20010031622 | Kivela et al. | Oct 2001 | A1 |
| 20020008763 | Kawamura et al. | Jan 2002 | A1 |
| 20020021758 | Chui | Feb 2002 | A1 |
| 20020029169 | Oki et al. | Mar 2002 | A1 |
| 20020054233 | Juen | May 2002 | A1 |
| 20020057461 | Dow et al. | May 2002 | A1 |
| 20020068600 | Chihara et al. | Jun 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 |
| 20020142734 | Wickstead | Oct 2002 | A1 |
| 20020168108 | Loui et al. | Nov 2002 | A1 |
| 20030002391 | Biggs | Jan 2003 | A1 |
| 20030033296 | Rothmuller et al. | 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 |
| 20030177067 | Cowell et al. | Sep 2003 | A1 |
| 20030182628 | Lira | Sep 2003 | A1 |
| 20030197687 | Shetter | Oct 2003 | A1 |
| 20040019640 | Bartram et al. | Jan 2004 | A1 |
| 20040046886 | Ambiru et al. | Mar 2004 | A1 |
| 20040077462 | Brown et al. | Apr 2004 | A1 |
| 20040078752 | Johnson | Apr 2004 | A1 |
| 20040083474 | Mckinlay et al. | Apr 2004 | A1 |
| 20040119758 | Grossman et al. | Jun 2004 | A1 |
| 20040125150 | Adcock 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 |
| 20040168107 | Sharp et al. | Aug 2004 | A1 |
| 20040181771 | Anonsen et al. | Sep 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 |
| 20040218472 | Narayanaswami et al. | Nov 2004 | A1 |
| 20040225966 | Besharat et al. | Nov 2004 | A1 |
| 20040246607 | Watson et al. | Dec 2004 | A1 |
| 20050015803 | Macrae et al. | Jan 2005 | 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 | Mar 2005 | A1 |
| 20050073601 | Battles et al. | Apr 2005 | A1 |
| 20050076056 | Paalasmaa et al. | Apr 2005 | A1 |
| 20050081150 | Beardow | 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 |
| 20050156873 | Walter et al. | Jul 2005 | A1 |
| 20050160377 | Sciammarella et al. | Jul 2005 | A1 |
| 20050183026 | Amano et al. | Aug 2005 | A1 |
| 20050195221 | Berger et al. | Sep 2005 | A1 |
| 20050197063 | White et al. | Sep 2005 | A1 |
| 20050198024 | Sakata et al. | Sep 2005 | A1 |
| 20050202846 | Glass et al. | Sep 2005 | A1 |
| 20050256712 | Yamada et al. | Nov 2005 | A1 |
| 20050275636 | Dehlin et al. | Dec 2005 | A1 |
| 20050289173 | Vacca | Dec 2005 | A1 |
| 20060000900 | Fernandes et al. | Jan 2006 | A1 |
| 20060001652 | Chiu et al. | Jan 2006 | A1 |
| 20060004685 | Pyhalammi et al. | Jan 2006 | A1 |
| 20060010098 | Goodnow et al. | Jan 2006 | A1 |
| 20060017692 | Wehrenberg et al. | Jan 2006 | A1 |
| 20060025218 | Hotta | Feb 2006 | A1 |
| 20060026521 | Hotelling et al. | Feb 2006 | A1 |
| 20060026536 | Hotelling et al. | Feb 2006 | A1 |
| 20060036960 | Loui | Feb 2006 | A1 |
| 20060053386 | Kuhl et al. | Mar 2006 | A1 |
| 20060061663 | Park | Mar 2006 | A1 |
| 20060072028 | Hong | Apr 2006 | A1 |
| 20060077266 | Nurmi | Apr 2006 | A1 |
| 20060080386 | Roykkee et al. | Apr 2006 | A1 |
| 20060088228 | Marriott et al. | Apr 2006 | A1 |
| 20060090141 | Loui et al. | Apr 2006 | A1 |
| 20060122748 | Nou | Jun 2006 | A1 |
| 20060136839 | Makela | Jun 2006 | A1 |
| 20060155578 | Eisenberger et al. | Jul 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 |
| 20060173749 | Ward et al. | Aug 2006 | A1 |
| 20060179114 | Deeds | Aug 2006 | A1 |
| 20060217104 | Cho | Sep 2006 | A1 |
| 20060218500 | Sauve et al. | Sep 2006 | A1 |
| 20060265643 | Saft et al. | Nov 2006 | A1 |
| 20060271605 | Petruzzo | Nov 2006 | A1 |
| 20060277469 | Chaudhri et al. | Dec 2006 | A1 |
| 20070002077 | Gopalakrishnan | Jan 2007 | A1 |
| 20070008321 | Gallagher et al. | Jan 2007 | A1 |
| 20070016868 | Nurmi | Jan 2007 | A1 |
| 20070031115 | Oshikiri et al. | Feb 2007 | A1 |
| 20070067733 | Moore et al. | Mar 2007 | A1 |
| 20070081740 | Ciudad et al. | Apr 2007 | A1 |
| 20070096765 | Kagan | May 2007 | A1 |
| 20070097421 | Sorensen et al. | May 2007 | A1 |
| 20070101279 | Chaudhri et al. | May 2007 | A1 |
| 20070101355 | Chung et al. | May 2007 | A1 |
| 20070112754 | Haigh et al. | May 2007 | A1 |
| 20070115373 | Gallagher et al. | May 2007 | A1 |
| 20070135043 | Hayes et al. | Jun 2007 | A1 |
| 20070136778 | Birger et al. | Jun 2007 | A1 |
| 20070143495 | Porat | Jun 2007 | A1 |
| 20070152984 | Ording et al. | Jul 2007 | A1 |
| 20070186154 | Anthony et al. | Aug 2007 | A1 |
| 20070192741 | Yoritate et al. | Aug 2007 | A1 |
| 20070194110 | Esplin et al. | Aug 2007 | A1 |
| 20070194113 | Esplin et al. | Aug 2007 | A1 |
| 20070204225 | Berkowitz et al. | Aug 2007 | A1 |
| 20070229678 | Barrus et al. | Oct 2007 | A1 |
| 20070245236 | Lee | Oct 2007 | A1 |
| 20070254712 | Chitti | Nov 2007 | A1 |
| 20070261537 | Eronen et al. | Nov 2007 | A1 |
| 20070271340 | Goodman et al. | Nov 2007 | A1 |
| 20080027586 | Hern et al. | Jan 2008 | A1 |
| 20080030456 | Asadi | Feb 2008 | A1 |
| 20080040265 | Hi et al. | Feb 2008 | A1 |
| 20080057926 | Forstall et al. | Mar 2008 | A1 |
| 20080057941 | Scott et al. | Mar 2008 | A1 |
| 20080059888 | Dunko | Mar 2008 | A1 |
| 20080062141 | Chandhri | Mar 2008 | A1 |
| 20080076637 | Gilley et al. | Mar 2008 | A1 |
| 20080077936 | Goel et al. | Mar 2008 | A1 |
| 20080091637 | Escamilla et al. | Apr 2008 | A1 |
| 20080133479 | Zelevinsky et al. | Jun 2008 | A1 |
| 20080133697 | Stewart et al. | Jun 2008 | A1 |
| 20080152201 | Zhang et al. | Jun 2008 | A1 |
| 20080155474 | Duhig et al. | Jun 2008 | A1 |
| 20080168144 | Lee | Jul 2008 | A1 |
| 20080168349 | Lamiraux et al. | Jul 2008 | A1 |
| 20080168366 | Kocienda et al. | Jul 2008 | A1 |
| 20080168402 | Blumenberg | Jul 2008 | A1 |
| 20080183909 | Lim et al. | Jul 2008 | A1 |
| 20080247519 | Abella et al. | Oct 2008 | A1 |
| 20080256577 | Funaki et al. | Oct 2008 | A1 |
| 20080259829 | Rosenblatt | Oct 2008 | A1 |
| 20080282202 | Sunday | Nov 2008 | A1 |
| 20080309632 | Westerman et al. | Dec 2008 | A1 |
| 20090005011 | Christie et al. | Jan 2009 | A1 |
| 20090006965 | Bodin et al. | Jan 2009 | A1 |
| 20090021576 | Linder et al. | Jan 2009 | A1 |
| 20090037326 | Chitti et al. | Feb 2009 | A1 |
| 20090054743 | Stewart | Feb 2009 | A1 |
| 20090057396 | Barbour et al. | Mar 2009 | A1 |
| 20090060170 | Coughlan et al. | Mar 2009 | A1 |
| 20090063542 | Bull et al. | Mar 2009 | A1 |
| 20090070675 | Li | Mar 2009 | A1 |
| 20090077460 | Li et al. | Mar 2009 | A1 |
| 20090085881 | Keam | Apr 2009 | A1 |
| 20090106695 | Perry et al. | Apr 2009 | A1 |
| 20090113315 | Fisher et al. | Apr 2009 | A1 |
| 20090113350 | Hibino et al. | Apr 2009 | A1 |
| 20090132921 | Hwangbo et al. | May 2009 | A1 |
| 20090144639 | Nims et al. | Jun 2009 | A1 |
| 20090161962 | Gallagher et al. | Jun 2009 | A1 |
| 20090177981 | Christie et al. | Jul 2009 | A1 |
| 20090195497 | Fitzgerald et al. | Aug 2009 | A1 |
| 20090198359 | Chaudhri | Aug 2009 | A1 |
| 20090198581 | Lidestri | Aug 2009 | A1 |
| 20090205041 | Michalske | Aug 2009 | A1 |
| 20090210793 | Yee et al. | Aug 2009 | A1 |
| 20090216556 | Martin et al. | Aug 2009 | A1 |
| 20090216806 | Feuerstein et al. | Aug 2009 | A1 |
| 20090231960 | Hutcheson | Sep 2009 | A1 |
| 20090254840 | Churchill et al. | Oct 2009 | A1 |
| 20090259967 | Davidson et al. | Oct 2009 | A1 |
| 20090262088 | Moll-Carrillo et al. | Oct 2009 | A1 |
| 20090276463 | Miller | Nov 2009 | A1 |
| 20090278806 | Duarte et al. | Nov 2009 | A1 |
| 20090282371 | Curl | Nov 2009 | A1 |
| 20090284471 | Longe et al. | Nov 2009 | A1 |
| 20090284551 | Stanton | Nov 2009 | A1 |
| 20090300598 | Choi | Dec 2009 | A1 |
| 20090306969 | Goud et al. | Dec 2009 | A1 |
| 20090307623 | Agarawala et al. | Dec 2009 | A1 |
| 20090311993 | Horodezky | Dec 2009 | A1 |
| 20090313579 | Poulson | Dec 2009 | A1 |
| 20090319467 | Berg et al. | Dec 2009 | A1 |
| 20090319472 | Jain et al. | Dec 2009 | A1 |
| 20100042926 | Bull et al. | Feb 2010 | A1 |
| 20100045828 | Gallagher | Feb 2010 | A1 |
| 20100046842 | Conwell | Feb 2010 | A1 |
| 20100048358 | Tchao et al. | Feb 2010 | A1 |
| 20100054519 | Mulvey et al. | Mar 2010 | A1 |
| 20100064255 | Rottier et al. | Mar 2010 | A1 |
| 20100076976 | Sotirov et al. | Mar 2010 | A1 |
| 20100082481 | Lin et al. | Mar 2010 | A1 |
| 20100083173 | Germann et al. | Apr 2010 | A1 |
| 20100088616 | Park et al. | Apr 2010 | A1 |
| 20100103321 | Ishikawa et al. | Apr 2010 | A1 |
| 20100110228 | Ozawa et al. | May 2010 | A1 |
| 20100114891 | Oami | May 2010 | A1 |
| 20100123724 | Moore et al. | May 2010 | A1 |
| 20100124967 | Lutnick et al. | May 2010 | A1 |
| 20100125785 | Moore et al. | May 2010 | A1 |
| 20100125786 | Ozawa et al. | May 2010 | A1 |
| 20100150456 | Tanaka | Jun 2010 | A1 |
| 20100151908 | Skarby et al. | Jun 2010 | A1 |
| 20100151918 | Annambhotla et al. | Jun 2010 | A1 |
| 20100157742 | Relyea et al. | Jun 2010 | A1 |
| 20100179874 | Higgins et al. | Jul 2010 | A1 |
| 20100179991 | Lorch et al. | Jul 2010 | A1 |
| 20100190468 | Scott et al. | Jul 2010 | A1 |
| 20100194692 | Orr et al. | Aug 2010 | A1 |
| 20100198453 | Dorogusker et al. | Aug 2010 | A1 |
| 20100202368 | Hans | Aug 2010 | A1 |
| 20100207892 | Lin et al. | Aug 2010 | A1 |
| 20100211575 | Collins et al. | Aug 2010 | A1 |
| 20100211685 | Mcdowall et al. | Aug 2010 | A1 |
| 20100214442 | Uemura et al. | Aug 2010 | A1 |
| 20100222645 | Nadler et al. | Sep 2010 | A1 |
| 20100223145 | Dragt | Sep 2010 | A1 |
| 20100223563 | Green | Sep 2010 | A1 |
| 20100225962 | Okigami et al. | Sep 2010 | A1 |
| 20100226213 | Drugge | Sep 2010 | A1 |
| 20100251167 | Deluca et al. | Sep 2010 | A1 |
| 20100253807 | Matsumoto et al. | Oct 2010 | A1 |
| 20100269055 | Daikeler et al. | Oct 2010 | A1 |
| 20100281374 | Schulz et al. | Nov 2010 | A1 |
| 20100287053 | Ganong et al. | Nov 2010 | A1 |
| 20100292600 | Dibenedetto et al. | Nov 2010 | A1 |
| 20100295795 | Wilairat | Nov 2010 | A1 |
| 20100299601 | Kaplan | Nov 2010 | A1 |
| 20100302179 | Ahn et al. | Dec 2010 | A1 |
| 20100306185 | Smith et al. | Dec 2010 | A1 |
| 20100325194 | Williamson et al. | Dec 2010 | A1 |
| 20110004835 | Yanchar et al. | Jan 2011 | A1 |
| 20110009109 | Hyon | Jan 2011 | A1 |
| 20110010195 | Cohn | Jan 2011 | A1 |
| 20110012919 | Tai et al. | Jan 2011 | A1 |
| 20110029750 | Jang et al. | Feb 2011 | A1 |
| 20110035700 | Meaney et al. | Feb 2011 | A1 |
| 20110050564 | Alberth et al. | Mar 2011 | A1 |
| 20110050640 | Lundback et al. | Mar 2011 | A1 |
| 20110059769 | Brunolli | Mar 2011 | A1 |
| 20110061010 | Wasko | Mar 2011 | A1 |
| 20110072394 | Victor et al. | Mar 2011 | A1 |
| 20110074699 | Marr et al. | Mar 2011 | A1 |
| 20110078025 | Shrivastav | Mar 2011 | A1 |
| 20110078717 | Drummond et al. | Mar 2011 | A1 |
| 20110083111 | Forutanpour et al. | Apr 2011 | A1 |
| 20110087747 | Hirst et al. | Apr 2011 | A1 |
| 20110088086 | Swink et al. | Apr 2011 | A1 |
| 20110093728 | Das | Apr 2011 | A1 |
| 20110098928 | Hoffman et al. | Apr 2011 | A1 |
| 20110099199 | Stalenhoef et al. | Apr 2011 | A1 |
| 20110099478 | Gallagher et al. | Apr 2011 | A1 |
| 20110106954 | Chatterjee et al. | May 2011 | A1 |
| 20110113337 | Liu et al. | May 2011 | A1 |
| 20110126148 | Krishnaraj et al. | May 2011 | A1 |
| 20110130168 | Vendrow et al. | Jun 2011 | A1 |
| 20110137678 | Williams | Jun 2011 | A1 |
| 20110145275 | Stewart | Jun 2011 | A1 |
| 20110145327 | Stewart | Jun 2011 | A1 |
| 20110159959 | Mallinson et al. | Jun 2011 | A1 |
| 20110163969 | Freddy et al. | Jul 2011 | A1 |
| 20110167369 | Van Os | Jul 2011 | A1 |
| 20110193878 | Seo et al. | Aug 2011 | A1 |
| 20110197165 | Filippov et al. | Aug 2011 | A1 |
| 20110201387 | Paek et al. | Aug 2011 | A1 |
| 20110202883 | Oh et al. | Aug 2011 | A1 |
| 20110205851 | Harris | Aug 2011 | A1 |
| 20110218765 | Rogers et al. | Sep 2011 | A1 |
| 20110227872 | Huska et al. | Sep 2011 | A1 |
| 20110234152 | Frossen et al. | Sep 2011 | A1 |
| 20110246463 | Carson, Jr. et al. | Oct 2011 | A1 |
| 20110248992 | Van et al. | Oct 2011 | A1 |
| 20110251892 | Laracey | Oct 2011 | A1 |
| 20110267368 | Casillas et al. | Nov 2011 | A1 |
| 20110271223 | Cruz moreno et al. | Nov 2011 | A1 |
| 20110279323 | Hung et al. | Nov 2011 | A1 |
| 20110282867 | Palermiti et al. | Nov 2011 | A1 |
| 20110294525 | Jonsson | Dec 2011 | A1 |
| 20110296324 | Goossens et al. | Dec 2011 | A1 |
| 20110304685 | Khedouri et al. | Dec 2011 | A1 |
| 20110307880 | Hilerio et al. | Dec 2011 | A1 |
| 20120001922 | Escher et al. | Jan 2012 | A1 |
| 20120008526 | Borghei | Jan 2012 | A1 |
| 20120015779 | Powch et al. | Jan 2012 | A1 |
| 20120036029 | Esplin et al. | Feb 2012 | A1 |
| 20120036220 | Dare et al. | Feb 2012 | A1 |
| 20120036460 | Cieplinski et al. | Feb 2012 | A1 |
| 20120044062 | Jersa et al. | Feb 2012 | A1 |
| 20120047447 | Haq | Feb 2012 | A1 |
| 20120056830 | Suzuki et al. | Mar 2012 | A1 |
| 20120057081 | Petersson et al. | Mar 2012 | A1 |
| 20120058801 | Nurmi | Mar 2012 | A1 |
| 20120059664 | Georgiev et al. | Mar 2012 | A1 |
| 20120059787 | Brown et al. | Mar 2012 | A1 |
| 20120060089 | Heo et al. | Mar 2012 | A1 |
| 20120060092 | Hill et al. | Mar 2012 | A1 |
| 20120066628 | Ens et al. | Mar 2012 | A1 |
| 20120071770 | Grey et al. | Mar 2012 | A1 |
| 20120079122 | Brown et al. | Mar 2012 | A1 |
| 20120083258 | Rabii | Apr 2012 | A1 |
| 20120084210 | Farahmand | Apr 2012 | A1 |
| 20120092383 | Hysek et al. | Apr 2012 | A1 |
| 20120101887 | Harvey et al. | Apr 2012 | A1 |
| 20120116550 | Hoffman et al. | May 2012 | A1 |
| 20120117507 | Tseng et al. | May 2012 | A1 |
| 20120131441 | Jitkoff et al. | May 2012 | A1 |
| 20120136780 | El-awady et al. | May 2012 | A1 |
| 20120136855 | Ni et al. | May 2012 | A1 |
| 20120143013 | Davis et al. | Jun 2012 | A1 |
| 20120150446 | Chang et al. | Jun 2012 | A1 |
| 20120169608 | Forutanpour et al. | Jul 2012 | A1 |
| 20120190386 | Anderson | Jul 2012 | A1 |
| 20120191603 | Nuzzi | Jul 2012 | A1 |
| 20120197523 | Kirsch | Aug 2012 | A1 |
| 20120206495 | Endo et al. | Aug 2012 | A1 |
| 20120209829 | Thomas et al. | Aug 2012 | A1 |
| 20120254263 | Hiestermann et al. | Oct 2012 | A1 |
| 20120258684 | Franz et al. | Oct 2012 | A1 |
| 20120290109 | Engelberg et al. | Nov 2012 | A1 |
| 20120302256 | Pai et al. | Nov 2012 | A1 |
| 20120310674 | Faulkner et al. | Dec 2012 | A1 |
| 20120310760 | Phillips et al. | Dec 2012 | A1 |
| 20120311032 | Murphy et al. | Dec 2012 | A1 |
| 20120311444 | Chaudhri | Dec 2012 | A1 |
| 20120324390 | Tao | Dec 2012 | A1 |
| 20130013327 | Horseman | Jan 2013 | A1 |
| 20130013650 | Shum | Jan 2013 | A1 |
| 20130017846 | Schoppe | Jan 2013 | A1 |
| 20130021368 | Lee et al. | Jan 2013 | A1 |
| 20130022282 | Cooper | Jan 2013 | A1 |
| 20130027341 | Mastandrea | Jan 2013 | A1 |
| 20130031490 | Joo et al. | Jan 2013 | A1 |
| 20130036380 | Symons | Feb 2013 | A1 |
| 20130040660 | Fisher et al. | Feb 2013 | A1 |
| 20130044072 | Kobayashi et al. | Feb 2013 | A1 |
| 20130047034 | Salomon et al. | Feb 2013 | A1 |
| 20130050263 | Khoe et al. | Feb 2013 | A1 |
| 20130054634 | Chakraborty et al. | Feb 2013 | A1 |
| 20130055147 | Vasudev et al. | Feb 2013 | A1 |
| 20130061175 | Matas et al. | Mar 2013 | A1 |
| 20130063383 | Anderssonreimer et al. | Mar 2013 | A1 |
| 20130069893 | Brinda et al. | Mar 2013 | A1 |
| 20130093715 | Marsden et al. | Apr 2013 | A1 |
| 20130103814 | Carrasco et al. | Apr 2013 | A1 |
| 20130111579 | Newman et al. | May 2013 | A1 |
| 20130117365 | Padmanabhan et al. | May 2013 | A1 |
| 20130117696 | Robertson et al. | May 2013 | A1 |
| 20130137073 | Nacey et al. | May 2013 | A1 |
| 20130143512 | Hernandez et al. | Jun 2013 | A1 |
| 20130145292 | Cohen et al. | Jun 2013 | A1 |
| 20130156275 | Amacker et al. | Jun 2013 | A1 |
| 20130159919 | Leydon | Jun 2013 | A1 |
| 20130190083 | Toy et al. | Jul 2013 | A1 |
| 20130198176 | Kim | Aug 2013 | A1 |
| 20130204897 | Mcdougall | Aug 2013 | A1 |
| 20130205210 | Jeon | Aug 2013 | A1 |
| 20130222270 | Winkler et al. | Aug 2013 | A1 |
| 20130225118 | Jang et al. | Aug 2013 | A1 |
| 20130239049 | Perrodin et al. | Sep 2013 | A1 |
| 20130239063 | Ubillos et al. | Sep 2013 | A1 |
| 20130246202 | Tobin | Sep 2013 | A1 |
| 20130246329 | Pasquero et al. | Sep 2013 | A1 |
| 20130254685 | Batraski et al. | Sep 2013 | A1 |
| 20130254705 | Mooring et al. | Sep 2013 | A1 |
| 20130260896 | Miura et al. | Oct 2013 | A1 |
| 20130262155 | Hinkamp | Oct 2013 | A1 |
| 20130275923 | Griffin et al. | Oct 2013 | A1 |
| 20130275924 | Weinberg et al. | Oct 2013 | A1 |
| 20130285948 | Zhang | Oct 2013 | A1 |
| 20130290013 | Forrester | Oct 2013 | A1 |
| 20130295872 | Guday et al. | Nov 2013 | A1 |
| 20130300645 | Fedorov | Nov 2013 | A1 |
| 20130304276 | Flies | Nov 2013 | A1 |
| 20130320080 | Olson et al. | Dec 2013 | A1 |
| 20130325970 | Roberts et al. | Dec 2013 | A1 |
| 20130332856 | Sanders et al. | Dec 2013 | A1 |
| 20130345978 | Lush et al. | Dec 2013 | A1 |
| 20140006769 | Chory et al. | Jan 2014 | A1 |
| 20140022183 | Ayoub et al. | Jan 2014 | A1 |
| 20140025737 | Kruglick | Jan 2014 | A1 |
| 20140046914 | Das et al. | Feb 2014 | A1 |
| 20140058860 | Roh et al. | Feb 2014 | A1 |
| 20140058935 | Mijares | Feb 2014 | A1 |
| 20140059493 | Kim | Feb 2014 | A1 |
| 20140064572 | Panzer et al. | Mar 2014 | A1 |
| 20140066105 | Bridge et al. | Mar 2014 | A1 |
| 20140068520 | Missig et al. | Mar 2014 | A1 |
| 20140073298 | Rossmann | Mar 2014 | A1 |
| 20140074407 | Hernandez-Silveira et al. | Mar 2014 | A1 |
| 20140074570 | Hope et al. | Mar 2014 | A1 |
| 20140074717 | Evans | Mar 2014 | A1 |
| 20140074825 | Wood et al. | Mar 2014 | A1 |
| 20140074893 | Griffin | Mar 2014 | A1 |
| 20140075234 | Stekkelpak et al. | Mar 2014 | A1 |
| 20140081854 | Sanchez et al. | Mar 2014 | A1 |
| 20140082383 | De Cesare et al. | Mar 2014 | A1 |
| 20140082384 | De Cesare et al. | Mar 2014 | A1 |
| 20140082533 | Kelley | Mar 2014 | A1 |
| 20140089330 | Cui et al. | Mar 2014 | A1 |
| 20140092291 | Aoshima et al. | Apr 2014 | A1 |
| 20140094124 | Dave et al. | Apr 2014 | A1 |
| 20140123005 | Forstall et al. | May 2014 | A1 |
| 20140128021 | Walker et al. | May 2014 | A1 |
| 20140129255 | Woodson et al. | May 2014 | A1 |
| 20140134947 | Stouder-Studenmund | May 2014 | A1 |
| 20140143145 | Kortina et al. | May 2014 | A1 |
| 20140143678 | Mistry et al. | May 2014 | A1 |
| 20140149198 | Kim et al. | May 2014 | A1 |
| 20140156262 | Yuen et al. | Jun 2014 | A1 |
| 20140163954 | Joshi et al. | Jun 2014 | A1 |
| 20140164241 | Neuwirth | Jun 2014 | A1 |
| 20140164938 | Petterson et al. | Jun 2014 | A1 |
| 20140165000 | Fleizach et al. | Jun 2014 | A1 |
| 20140172864 | Shum | Jun 2014 | A1 |
| 20140176475 | Myers et al. | Jun 2014 | A1 |
| 20140179272 | Zhang et al. | Jun 2014 | A1 |
| 20140181089 | Desmond et al. | Jun 2014 | A1 |
| 20140181205 | Sherrets | Jun 2014 | A1 |
| 20140181558 | Taha et al. | Jun 2014 | A1 |
| 20140187314 | Perry et al. | Jul 2014 | A1 |
| 20140187323 | Perry | Jul 2014 | A1 |
| 20140189584 | Weng et al. | Jul 2014 | A1 |
| 20140195826 | Wojcik et al. | Jul 2014 | A1 |
| 20140195918 | Friedlander | Jul 2014 | A1 |
| 20140198234 | Kobayashi et al. | Jul 2014 | A1 |
| 20140208250 | Ording et al. | Jul 2014 | A1 |
| 20140222809 | Hochmuth et al. | Aug 2014 | A1 |
| 20140225925 | Hayashi et al. | Aug 2014 | A1 |
| 20140229831 | Chordia et al. | Aug 2014 | A1 |
| 20140236459 | Boesch et al. | Aug 2014 | A1 |
| 20140236882 | Rishe | Aug 2014 | A1 |
| 20140240122 | Roberts et al. | Aug 2014 | A1 |
| 20140244495 | Davis et al. | Aug 2014 | A1 |
| 20140245177 | Maklouf et al. | Aug 2014 | A1 |
| 20140250126 | Baldwin et al. | Sep 2014 | A1 |
| 20140250391 | Jong et al. | Sep 2014 | A1 |
| 20140282011 | Dellinger et al. | Sep 2014 | A1 |
| 20140282103 | Crandall | Sep 2014 | A1 |
| 20140282207 | Wouhaybi et al. | Sep 2014 | A1 |
| 20140282211 | Ady et al. | Sep 2014 | A1 |
| 20140282262 | Gregotski et al. | Sep 2014 | A1 |
| 20140287821 | Barclay et al. | Sep 2014 | A1 |
| 20140289222 | Sharpe et al. | Sep 2014 | A1 |
| 20140289660 | Min | Sep 2014 | A1 |
| 20140293755 | Geiser et al. | Oct 2014 | A1 |
| 20140294167 | Kim et al. | Oct 2014 | A1 |
| 20140304738 | Nakaoka et al. | Oct 2014 | A1 |
| 20140310618 | Venkatesh | Oct 2014 | A1 |
| 20140317543 | Kim | Oct 2014 | A1 |
| 20140325384 | Kobayashi | Oct 2014 | A1 |
| 20140325408 | Leppanen et al. | Oct 2014 | A1 |
| 20140330824 | Johnson et al. | Nov 2014 | A1 |
| 20140337207 | Zhang et al. | Nov 2014 | A1 |
| 20140337324 | Chao et al. | Nov 2014 | A1 |
| 20140337438 | Govande et al. | Nov 2014 | A1 |
| 20140337450 | Choudhary et al. | Nov 2014 | A1 |
| 20140341476 | Kulick et al. | Nov 2014 | A1 |
| 20140359441 | Lehtiniemi et al. | Dec 2014 | A1 |
| 20140362056 | Zambetti et al. | Dec 2014 | A1 |
| 20140362274 | Christie et al. | Dec 2014 | A1 |
| 20140365944 | Moore 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 |
| 20150006376 | Nuthulapati et al. | Jan 2015 | A1 |
| 20150012425 | Mathew | Jan 2015 | A1 |
| 20150026615 | Choi et al. | Jan 2015 | A1 |
| 20150039494 | Sinton et al. | Feb 2015 | A1 |
| 20150039616 | Roiston et al. | Feb 2015 | A1 |
| 20150046828 | Desai et al. | Feb 2015 | A1 |
| 20150052212 | Flam | Feb 2015 | A1 |
| 20150057945 | White et al. | Feb 2015 | A1 |
| 20150058720 | Smadja et al. | Feb 2015 | A1 |
| 20150066758 | Denardis et al. | Mar 2015 | A1 |
| 20150067513 | Zambetti et al. | Mar 2015 | A1 |
| 20150078680 | Shakib et al. | Mar 2015 | A1 |
| 20150082250 | Wagner et al. | Mar 2015 | A1 |
| 20150089660 | Song et al. | Mar 2015 | A1 |
| 20150098309 | Adams et al. | Apr 2015 | A1 |
| 20150100537 | Grieves et al. | Apr 2015 | A1 |
| 20150100982 | Sirpal et al. | Apr 2015 | A1 |
| 20150112990 | Van Os et al. | Apr 2015 | A1 |
| 20150113435 | Phillips | Apr 2015 | A1 |
| 20150121405 | Ekselius et al. | Apr 2015 | A1 |
| 20150130719 | Wehrenberg et al. | May 2015 | A1 |
| 20150130830 | Nagasaki et al. | May 2015 | A1 |
| 20150160856 | Jang et al. | Jun 2015 | A1 |
| 20150172393 | Oplinger et al. | Jun 2015 | A1 |
| 20150177937 | Poletto et al. | Jun 2015 | A1 |
| 20150177979 | Johansson et al. | Jun 2015 | A1 |
| 20150180980 | Welinder | Jun 2015 | A1 |
| 20150185995 | Shoemaker et al. | Jul 2015 | A1 |
| 20150188861 | Esplin et al. | Jul 2015 | A1 |
| 20150201062 | Shih et al. | Jul 2015 | A1 |
| 20150205509 | Scriven et al. | Jul 2015 | A1 |
| 20150213001 | Levy et al. | Jul 2015 | A1 |
| 20150217163 | Amis et al. | Aug 2015 | A1 |
| 20150220774 | Ebersman et al. | Aug 2015 | A1 |
| 20150222586 | Ebersman et al. | Aug 2015 | A1 |
| 20150227166 | Lee et al. | Aug 2015 | A1 |
| 20150227611 | Bao et al. | Aug 2015 | A1 |
| 20150227782 | Salvador et al. | Aug 2015 | A1 |
| 20150242114 | Hirabayashi 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 |
| 20150269432 | Motoi | Sep 2015 | A1 |
| 20150269848 | Yuen et al. | Sep 2015 | A1 |
| 20150286391 | Jacobs et al. | Oct 2015 | A1 |
| 20150287162 | Canan et al. | Oct 2015 | A1 |
| 20150295901 | Woodward et al. | Oct 2015 | A1 |
| 20150301506 | Koumaiha | Oct 2015 | A1 |
| 20150309698 | Senderek et al. | Oct 2015 | A1 |
| 20150324751 | Orenstein et al. | Nov 2015 | A1 |
| 20150334546 | Diamond | Nov 2015 | A1 |
| 20150341695 | Pattan | Nov 2015 | A1 |
| 20150347711 | Soli et al. | Dec 2015 | A1 |
| 20150347824 | Saari et al. | Dec 2015 | A1 |
| 20150347985 | Gross et al. | Dec 2015 | A1 |
| 20150348009 | Brown et al. | Dec 2015 | A1 |
| 20150350141 | Yang et al. | Dec 2015 | A1 |
| 20150350861 | Soli et al. | Dec 2015 | A1 |
| 20150355804 | Nguyen et al. | Dec 2015 | A1 |
| 20150363409 | Wood et al. | Dec 2015 | A1 |
| 20150370323 | Cieplinski et al. | Dec 2015 | A1 |
| 20150370455 | Van Os et al. | Dec 2015 | A1 |
| 20160004393 | Faaborg et al. | Jan 2016 | A1 |
| 20160004820 | Moore | Jan 2016 | A1 |
| 20160014266 | Bhatt | Jan 2016 | A1 |
| 20160019388 | Singla et al. | Jan 2016 | A1 |
| 20160022202 | Peterson et al. | Jan 2016 | A1 |
| 20160026730 | Hasan | Jan 2016 | A1 |
| 20160027420 | Eronen | Jan 2016 | A1 |
| 20160028869 | Bhatt | Jan 2016 | A1 |
| 20160041966 | Pasquero et al. | Feb 2016 | A1 |
| 20160044269 | Kang | Feb 2016 | A1 |
| 20160048263 | Hiraga et al. | Feb 2016 | A1 |
| 20160054845 | Takahashi et al. | Feb 2016 | A1 |
| 20160058336 | Blahnik et al. | Mar 2016 | A1 |
| 20160062589 | Wan et al. | Mar 2016 | A1 |
| 20160065505 | Iskander | Mar 2016 | A1 |
| 20160066005 | Davis et al. | Mar 2016 | A1 |
| 20160073034 | Mukherjee et al. | Mar 2016 | A1 |
| 20160073223 | Woolsey et al. | Mar 2016 | A1 |
| 20160088335 | Zucchetta | Mar 2016 | A1 |
| 20160092431 | Motoi | Mar 2016 | A1 |
| 20160098137 | Kim et al. | Apr 2016 | A1 |
| 20160098186 | Sugiura | Apr 2016 | A1 |
| 20160110355 | Charania et al. | Apr 2016 | A1 |
| 20160132232 | Baba et al. | May 2016 | A1 |
| 20160140146 | Wexler et al. | May 2016 | A1 |
| 20160150063 | Choi et al. | May 2016 | A1 |
| 20160165032 | Chang | Jun 2016 | A1 |
| 20160180568 | Bullivant et al. | Jun 2016 | A1 |
| 20160182410 | Janakiraman et al. | Jun 2016 | A1 |
| 20160188181 | Smith | Jun 2016 | A1 |
| 20160202889 | Shin | Jul 2016 | A1 |
| 20160210568 | Krupa et al. | Jul 2016 | A1 |
| 20160217601 | Tsuda et al. | Jul 2016 | A1 |
| 20160224540 | Stewart et al. | Aug 2016 | A1 |
| 20160226713 | Dellinger et al. | Aug 2016 | A1 |
| 20160226804 | Hampson et al. | Aug 2016 | A1 |
| 20160234184 | Liu et al. | Aug 2016 | A1 |
| 20160239724 | Arfvidsson et al. | Aug 2016 | A1 |
| 20160253864 | Weber et al. | Sep 2016 | A1 |
| 20160255162 | Frieder et al. | Sep 2016 | A1 |
| 20160261675 | Block et al. | Sep 2016 | A1 |
| 20160274756 | Sakaguchi | Sep 2016 | A1 |
| 20160283483 | Jiang et al. | Sep 2016 | A1 |
| 20160294958 | Zhang et al. | Oct 2016 | A1 |
| 20160295384 | Shan et al. | Oct 2016 | A1 |
| 20160320931 | Kovacs et al. | Nov 2016 | A1 |
| 20160321831 | Nakamura et al. | Nov 2016 | A1 |
| 20160321932 | Mitchell et al. | Nov 2016 | A1 |
| 20160327911 | Elm et al. | Nov 2016 | A1 |
| 20160337301 | Rollins et al. | Nov 2016 | A1 |
| 20160357363 | Decker et al. | Dec 2016 | A1 |
| 20160358133 | Van os et al. | Dec 2016 | A1 |
| 20160358134 | Van os et al. | Dec 2016 | A1 |
| 20160358180 | Van os et al. | Dec 2016 | A1 |
| 20160359771 | Sridhar | Dec 2016 | A1 |
| 20170004507 | Henderson et al. | Jan 2017 | A1 |
| 20170019587 | Matas et al. | Jan 2017 | A1 |
| 20170026430 | Beckhardt et al. | Jan 2017 | A1 |
| 20170041549 | Kim | Feb 2017 | A1 |
| 20170048686 | Chang et al. | Feb 2017 | A1 |
| 20170063753 | Probasco | Mar 2017 | A1 |
| 20170068439 | Mohseni | Mar 2017 | A1 |
| 20170075878 | Jon et al. | Mar 2017 | A1 |
| 20170078621 | Sahay et al. | Mar 2017 | A1 |
| 20170087469 | Hardee et al. | Mar 2017 | A1 |
| 20170093769 | Lind et al. | Mar 2017 | A1 |
| 20170093780 | Lieb | Mar 2017 | A1 |
| 20170123571 | Huang et al. | May 2017 | A1 |
| 20170134321 | Ushio et al. | May 2017 | A1 |
| 20170139554 | Nakabayashi et al. | May 2017 | A1 |
| 20170169295 | Park et al. | Jun 2017 | A1 |
| 20170180811 | Quirino et al. | Jun 2017 | A1 |
| 20170192625 | Kim et al. | Jul 2017 | A1 |
| 20170239524 | Lee et al. | Aug 2017 | A1 |
| 20170243508 | Cheng et al. | Aug 2017 | A1 |
| 20170244959 | Ranjeet et al. | Aug 2017 | A1 |
| 20170269792 | Xu et al. | Sep 2017 | A1 |
| 20170339264 | Steel et al. | Nov 2017 | A1 |
| 20170344257 | Gnedin | Nov 2017 | A1 |
| 20170354845 | Williams et al. | Dec 2017 | A1 |
| 20170357382 | Miura et al. | Dec 2017 | A1 |
| 20170357409 | Wagner et al. | Dec 2017 | A1 |
| 20170359302 | Van Os et al. | Dec 2017 | A1 |
| 20170359623 | Folse et al. | Dec 2017 | A1 |
| 20180034765 | Keszler | Feb 2018 | A1 |
| 20180039406 | Kong | Feb 2018 | A1 |
| 20180047189 | Diverdi et al. | Feb 2018 | A1 |
| 20180063324 | Van Meter, II | Mar 2018 | A1 |
| 20180068019 | Novikoff et al. | Mar 2018 | A1 |
| 20180081515 | Block et al. | Mar 2018 | A1 |
| 20180083901 | Mcgregor et al. | Mar 2018 | A1 |
| 20180121074 | Peron et al. | May 2018 | A1 |
| 20180143761 | Choi | May 2018 | A1 |
| 20180146349 | Chang et al. | May 2018 | A1 |
| 20180181668 | Zhang et al. | Jun 2018 | A1 |
| 20180204111 | Zadeh et al. | Jul 2018 | A1 |
| 20180239520 | Hinckley et al. | Aug 2018 | A1 |
| 20180253194 | Javadi | Sep 2018 | A1 |
| 20180270627 | Chang et al. | Sep 2018 | A1 |
| 20180309801 | Rathod | Oct 2018 | A1 |
| 20180316964 | Dillon et al. | Nov 2018 | A1 |
| 20180321048 | Li et al. | Nov 2018 | A1 |
| 20180329586 | Sundstrom et al. | Nov 2018 | A1 |
| 20180329622 | Missig et al. | Nov 2018 | A1 |
| 20180349020 | Jon et al. | Dec 2018 | A1 |
| 20180364872 | Miura et al. | Dec 2018 | A1 |
| 20180367484 | Rodriguez et al. | Dec 2018 | A1 |
| 20180367862 | Horii et al. | Dec 2018 | A1 |
| 20190026011 | Wang et al. | Jan 2019 | A1 |
| 20190073081 | Takahashi et al. | Mar 2019 | A1 |
| 20190102049 | Anzures et al. | Apr 2019 | A1 |
| 20190155382 | Ikuta et al. | May 2019 | A1 |
| 20190184234 | Packles et al. | Jun 2019 | A1 |
| 20190187889 | Moon et al. | Jun 2019 | A1 |
| 20190220243 | Decker et al. | Jul 2019 | A1 |
| 20190232110 | Williams | Aug 2019 | A1 |
| 20190232111 | Williams | Aug 2019 | A1 |
| 20190250813 | Block et al. | Aug 2019 | A1 |
| 20190258383 | Wagner et al. | Aug 2019 | A1 |
| 20190265844 | Burkert et al. | Aug 2019 | A1 |
| 20190303423 | Thimbleby | Oct 2019 | A1 |
| 20190313012 | Matas | Oct 2019 | A1 |
| 20190320301 | Chang et al. | Oct 2019 | A1 |
| 20190334782 | Dellinger et al. | Oct 2019 | A1 |
| 20190349463 | Soli et al. | Nov 2019 | A1 |
| 20200089374 | Hill et al. | Mar 2020 | A1 |
| 20200089402 | Kakani et al. | Mar 2020 | A1 |
| 20200104038 | Kamath et al. | Apr 2020 | A1 |
| 20200110798 | Jon et al. | Apr 2020 | A1 |
| 20200118325 | Sasikumar et al. | Apr 2020 | A1 |
| 20200149921 | Hoffman et al. | May 2020 | A1 |
| 20200211250 | Sasikumar et al. | Jul 2020 | A1 |
| 20200213437 | Bhatt | Jul 2020 | A1 |
| 20200225746 | Bar-Zeev et al. | Jul 2020 | A1 |
| 20200335133 | Vaucher | Oct 2020 | A1 |
| 20200356222 | Clarke et al. | Nov 2020 | A1 |
| 20200356590 | Clarke et al. | Nov 2020 | A1 |
| 20200363932 | Wagner et al. | Nov 2020 | A1 |
| 20200379560 | Krasadakis | Dec 2020 | A1 |
| 20200379638 | Zhu et al. | Dec 2020 | A1 |
| 20200380208 | Garcia, III et al. | Dec 2020 | A1 |
| 20210034860 | Bednarowicz et al. | Feb 2021 | A1 |
| 20210042028 | Block et al. | Feb 2021 | A1 |
| 20210042132 | Park et al. | Feb 2021 | A1 |
| 20210092488 | Folse et al. | Mar 2021 | A1 |
| 20210149549 | Ubillos et al. | May 2021 | A1 |
| 20210150121 | Thimbleby | May 2021 | A1 |
| 20210191578 | Miura et al. | Jun 2021 | A1 |
| 20210243356 | Matas et al. | Aug 2021 | A1 |
| 20210263700 | Decker et al. | Aug 2021 | A1 |
| 20210289067 | Dellinger et al. | Sep 2021 | A1 |
| 20210342535 | Garcia et al. | Nov 2021 | A1 |
| 20220027039 | Wagner et al. | Jan 2022 | A1 |
| 20220047918 | Williams et al. | Feb 2022 | A1 |
| 20220057931 | Zhu et al. | Feb 2022 | A1 |
| 20220206647 | Clarke et al. | Jun 2022 | A1 |
| 20220264184 | Folse et al. | Aug 2022 | A1 |
| 20220276750 | Miura et al. | Sep 2022 | A1 |
| 20220291793 | Zambetti et al. | Sep 2022 | A1 |
| 20220345785 | Yang et al. | Oct 2022 | A1 |
| 20220382443 | Clarke et al. | Dec 2022 | A1 |
| 20220386085 | Chang et al. | Dec 2022 | A1 |
| 20230012755 | D'auria et al. | Jan 2023 | A1 |
| 20230013809 | D'auria et al. | Jan 2023 | A1 |
| 20230019337 | D'auria et al. | Jan 2023 | A1 |
| 20230024084 | D'auria et al. | Jan 2023 | A1 |
| 20230031103 | Decker et al. | Feb 2023 | A1 |
| 20230066552 | Van Os et al. | Mar 2023 | A1 |
| 20230152964 | Zhu et al. | May 2023 | A1 |
| 20230179700 | Bhatt | Jun 2023 | A1 |
| 20230221836 | Clarke et al. | Jul 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 2015100705 | Jun 2015 | AU |
| 2016100796 | Jun 2016 | AU |
| 2897539 | Oct 2014 | CA |
| 1404233 | Mar 2003 | CN |
| 1443427 | Sep 2003 | CN |
| 1536511 | Oct 2004 | CN |
| 1619541 | May 2005 | CN |
| 1717918 | Jan 2006 | CN |
| 1756273 | Apr 2006 | CN |
| 1782685 | Jun 2006 | CN |
| 1997050 | Jul 2007 | CN |
| 101061484 | Oct 2007 | CN |
| 101129059 | Feb 2008 | CN |
| 101196786 | Jun 2008 | CN |
| 101291409 | Oct 2008 | CN |
| 101505320 | Aug 2009 | CN |
| 101796476 | Aug 2010 | CN |
| 101822020 | Sep 2010 | CN |
| 101827363 | Sep 2010 | CN |
| 101828411 | Sep 2010 | CN |
| 101854278 | Oct 2010 | CN |
| 101939740 | Jan 2011 | CN |
| 101978374 | Feb 2011 | CN |
| 102483758 | May 2012 | CN |
| 102646081 | Aug 2012 | CN |
| 102681847 | Sep 2012 | CN |
| 102693311 | Sep 2012 | CN |
| 102989159 | Mar 2013 | CN |
| 103081496 | May 2013 | CN |
| 103154954 | Jun 2013 | CN |
| 103297610 | Sep 2013 | CN |
| 103460651 | Dec 2013 | CN |
| 103577108 | Feb 2014 | CN |
| 103581456 | Feb 2014 | CN |
| 103902808 | Jul 2014 | CN |
| 103914238 | Jul 2014 | CN |
| 103973899 | Aug 2014 | CN |
| 104035666 | Sep 2014 | CN |
| 104288983 | Jan 2015 | CN |
| 104471521 | Mar 2015 | CN |
| 104487927 | Apr 2015 | CN |
| 104487928 | Apr 2015 | CN |
| 104508426 | Apr 2015 | CN |
| 104685470 | Jun 2015 | CN |
| 104981762 | Oct 2015 | CN |
| 105103154 | Nov 2015 | CN |
| 105264480 | Jan 2016 | CN |
| 105378728 | Mar 2016 | CN |
| 105874447 | Aug 2016 | CN |
| 106415476 | Feb 2017 | CN |
| 106843711 | Jun 2017 | CN |
| 107430483 | Dec 2017 | CN |
| 107710197 | Feb 2018 | CN |
| 109600456 | Apr 2019 | CN |
| 1124175 | Aug 2001 | EP |
| 1148412 | Oct 2001 | EP |
| 1289210 | Mar 2003 | EP |
| 1705883 | Sep 2006 | EP |
| 2172833 | Apr 2010 | EP |
| 2426902 | Mar 2012 | EP |
| 2509074 | Oct 2012 | EP |
| 2632139 | Aug 2013 | EP |
| 2830093 | Mar 2003 | FR |
| 2420260 | May 2006 | GB |
| 2470585 | Dec 2010 | GB |
| 2550639 | Nov 2017 | GB |
| 3-217976 | Sep 1991 | JP |
| 6-309138 | Nov 1994 | JP |
| 7-334463 | Dec 1995 | JP |
| 8-106469 | Apr 1996 | JP |
| 10-90333 | Apr 1998 | JP |
| 10-93848 | Apr 1998 | JP |
| 10-202715 | Aug 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-133293 | May 2001 | JP |
| 2001-136303 | May 2001 | JP |
| 2001-265481 | Sep 2001 | JP |
| 2001-309019 | Nov 2001 | JP |
| 2002-73486 | Mar 2002 | JP |
| 2002-152559 | May 2002 | JP |
| 2003-163820 | Jun 2003 | JP |
| 2003-296246 | Oct 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-258738 | Sep 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-339017 | Dec 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 |
| 2008-272301 | Nov 2008 | JP |
| 2009-59042 | Mar 2009 | JP |
| 2009-147889 | Jul 2009 | JP |
| 2010-12335 | Jan 2010 | JP |
| 2010-503130 | Jan 2010 | JP |
| 2010-118056 | May 2010 | JP |
| 2012-53642 | Mar 2012 | JP |
| 2012-203537 | Oct 2012 | JP |
| 2012-533117 | Dec 2012 | JP |
| 2013-29925 | Feb 2013 | JP |
| 2013-54468 | Mar 2013 | JP |
| 2013-83689 | May 2013 | JP |
| 2013-84282 | May 2013 | JP |
| 2013-140171 | Jul 2013 | JP |
| 2014-44724 | Mar 2014 | JP |
| 2014-93003 | May 2014 | JP |
| 2014-95979 | May 2014 | JP |
| 2014-216868 | Nov 2014 | JP |
| 5771242 | Aug 2015 | JP |
| 2015-531916 | Nov 2015 | JP |
| 2016-35776 | Mar 2016 | JP |
| 2016-167299 | Sep 2016 | JP |
| 2016-201135 | Dec 2016 | JP |
| 20040067514 | Jul 2004 | KR |
| 10-2005-0101162 | Oct 2005 | KR |
| 10-2006-0032793 | Apr 2006 | KR |
| 10-2009- 0112132 | Oct 2009 | KR |
| 10-2012-0058539 | Jun 2012 | KR |
| 2012-0092644 | Aug 2012 | KR |
| 10-2013- 0026541 | Mar 2013 | KR |
| 10-2013-0109466 | Oct 2013 | KR |
| 2014-0067965 | Jun 2014 | KR |
| 10-2014- 0105309 | Sep 2014 | KR |
| 10-2015-0131257 | Nov 2015 | KR |
| 2015-0131262 | Nov 2015 | KR |
| 10-1611895 | Apr 2016 | KR |
| 498240 | Aug 2002 | TW |
| 200512616 | Apr 2005 | TW |
| 201210368 | Mar 2012 | TW |
| 201240499 | Oct 2012 | TW |
| 199954807 | 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 |
| 2007000012 | Jan 2007 | WO |
| 2007142703 | Dec 2007 | WO |
| 2007149731 | Dec 2007 | WO |
| 2008030779 | Mar 2008 | WO |
| 2008114491 | Sep 2008 | WO |
| 2009032998 | Mar 2009 | 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 |
| 2012075322 | Jun 2012 | WO |
| 2012097385 | Jul 2012 | WO |
| 2013169854 | Nov 2013 | WO |
| 2013169870 | Nov 2013 | WO |
| 2013169877 | Nov 2013 | WO |
| 2014002711 | Jan 2014 | WO |
| 2014022711 | Feb 2014 | WO |
| 2014074407 | May 2014 | WO |
| 2014149473 | Sep 2014 | WO |
| 2014149488 | Sep 2014 | WO |
| 2014162659 | Oct 2014 | WO |
| 2014197340 | Dec 2014 | WO |
| 2014200734 | Dec 2014 | WO |
| 2015029313 | Mar 2015 | WO |
| 2015087084 | Jun 2015 | WO |
| 2016077834 | May 2016 | WO |
| 2016126733 | Aug 2016 | WO |
| 2016160632 | Oct 2016 | WO |
| 2017027632 | Feb 2017 | WO |
| Entry |
|---|
| US 2002/0018582 A1, 02/2002, Hagiwara et al. (withdrawn) |
| Notice of Allowance received for U.S. Appl. No. 15/687,384, dated Jan. 8, 2019, 8 pages. |
| Office Action received for Chinese Patent Application No. 201610371774.4, dated Dec. 19, 2018, 13 pages (5 pages of English Translation and 8 pages of Official copy). |
| Office Action received for Danish Patent Application No. PA201670608, dated Jan. 14, 2019, 7 pages. |
| Office Action received for Taiwanese Patent Application No. 104132636, dated Dec. 13, 2018, 26 pages (9 pages of English Translation and 17 pages of Official Copy). |
| Decision to Grant received for European Patent Application No. 11178259.5, dated Apr. 4, 2019, 3 pages. |
| Extended European Search Report received for European Patent Application No. 18213157.3, dated Apr. 12, 2019, 8 pages. |
| Final Office Action received for U.S. Appl. No. 15/614,121, dated Apr. 8, 2019, 32 pages. |
| Non-Final Office Action received forU. S. U.S. Appl. No. 15/554,204, dated Apr. 17, 2019, 19 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201580028677.9, dated Apr. 2, 2019, 2 pages (1 pages of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 15/281,524, dated Apr. 11, 2019, 7 pages. |
| Office Action received for Australian Patent Application No. 2018206772, dated Apr. 1, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201770423, dated Mar. 29, 2019, 6 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7007053, dated Mar. 18, 2019, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/863,069, dated Mar. 29, 2019, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 15/616,480, dated Mar. 28, 2019, 2 pages. |
| Advisory Action received for U.S. Appl. No. 14/863,099, dated Sep. 8, 2016, 3 pages,. |
| Dharmasena, Anusha, “iMessage-send as text message Option”, YouTube, Available online at: https://www.youtube.com/watch?v=hXG-MdlW6FA, Feb. 18, 2013, 1 page. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/774,664, mailed on May 31, 2018, 28 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/863,099, mailed on Jul. 28, 2017, 31 pages. |
| Final Office Action received for U.S. Appl. No. 14/774,664, dated Aug. 25, 2017, 23 pages. |
| Final Office Action received for U.S. Appl. No. 14/863,099, dated Apr. 21, 2016, 20 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/027882, dated Sep. 24, 2015, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2013/032498, dated Feb. 10, 2014, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2014/027882, dated Oct. 10, 2014, 11 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2014/027882, dated Aug. 5, 2014, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/774,664, dated Mar. 7, 2017, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/863,099, dated Dec. 2, 2015, 12 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-545918, dated Jul. 22, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510284850.3, dated Jun. 21, 2019, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201610371774.4, dated Jul. 8, 2019, 6 pages (3 pages of English Translation and 3 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2017-7024570, dated Jul. 10, 2019, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Certification of Examination received for Australian Patent Application No. 2018100158, dated Oct. 23, 2018, 2 pages. |
| Office Action received for Japanese Patent Application No. 2017-545918, dated Sep. 14, 2018 (7 pages of English Translation and 5 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2017-7024570, dated Sep. 28, 2018, 14 pages (6 pages of English Translation and 8 pages of Official copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/281,524, dated Jun. 3, 2019, 2 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. 14/869,877, dated Jun. 11, 2019, 35 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/402,057, dated May 23, 2019, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/863,069, dated Jun. 18, 2019, 6 pages. |
| Office Action received for Australian Patent Application No. 2016270323, dated May 29, 2019, 4 pages. |
| Office Action received for Japanese Patent Application No. 2018-138559, dated May 13, 2019, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 14/846,574, dated May 10, 2019, 36 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,606, dated May 8, 2019, 28 pages. |
| Office Action received for Australian Patent Application No. 2017286296, dated May 8, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2018214074, dated May 9, 2019, 2 pages. |
| Office Action received for European Patent Application No. 16804040.0, dated May 13, 2019, 12 pages. |
| Partial Supplementary European Search Report received for European Patent Application No. 17810749.6, dated Apr. 25, 2019, 8 pages. |
| Extended European Search Report received for European Patent Application No. 16762356.0, dated Nov. 9, 2018, 10 Pages. |
| Intention to Grant received for European Patent Application No. 11178259.5, dated Nov. 8, 2018, 23 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 11178259.5, mailed on Nov. 2, 2018, 8 pages. |
| Search Report received for Danish Patent Application No. PA201870385, dated Nov. 16, 2018, 10 Pages. |
| Certificate of Examination received for Australian Patent Application No. 2018101855, dated Aug. 6, 2019, 2 pages. |
| Office Action received for Australian Patent Application No. 2019100490, dated Jul. 26, 2019, 4 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/863,069, dated Aug. 15, 2019, 3 pages. |
| Supplementary European Search Report received for European Patent Application No. 17810749.6, dated Aug. 6, 2019, 6 pages. |
| Advisory Action received for U.S. Appl. No. 14/253,783, dated Feb. 15, 2017, 6 Pages. |
| Advisory Action received for U.S. Appl. No. 14/869,877, dated Jan. 5, 2017, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/870,793, dated Apr. 13, 2017, 3 pages. |
| European Search Report received forthe European Patent Application No. 10172417.7, dated Jan. 7, 2011, 4 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/870,793, dated Apr. 16, 2018, 15 pages. |
| Extended European Search Report received for European Patent Application No. 16804040.0, dated Feb. 26, 2018, 9 pages. |
| Final Office Action received for U.S. Appl. No. 14/599,424, dated Jun. 28, 2018, 12 pages. |
| Final Office Action received for U.S. Appl. No. 14/599,425, dated Jun. 12, 2018, 45 pages. |
| Final Office Action received for U.S. Appl. No. 14/599,425, dated May 19, 2017, 24 pages. |
| Final Office Action received for U.S. Appl. No. 14/841,606, dated Sep. 7, 2018, 34 pages. |
| Final Office Action received for U.S. Appl. No. 14/863,069, dated Jul. 5, 2018, 19 pages. |
| Final Office Action received for U.S. Appl. No. 14/864,759, dated Sep. 4, 2018, 24 pages. |
| Final Office Action received for U.S. Appl. No. 14/869,877, dated Apr. 26, 2018, 18 pages. |
| Final Office Action received for U.S. Appl. No. 14/869,877, dated Aug. 3, 2016, 13 pages. |
| Final Office Action received for U.S. Appl. No. 14/870,726, dated Apr. 19, 2017, 17 pages. |
| Final Office Action received for U.S. Appl. No. 14/870,793, dated Jan. 19, 2017, 16 pages. |
| Final Office Action received for U.S. Appl. No. 14/253,783, dated Sep. 30, 2016, 18 pages. |
| Intention to Grant received for European Patent Application No. 16706081.3, dated Jul. 18, 2018, 8 pages. |
| Intention to Grant received for European Patent Application No. 16706081.3, dated Jun. 11, 2018, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/032474, dated Dec. 15, 2016, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/053353, dated Sep. 21, 2017, 15 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/014997, dated Dec. 21, 2017, 16 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/016216, dated May 4, 2017, 14 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/021403, dated Sep. 21, 2017, 21 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/025418, dated Dec. 21,2017, 16 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/034175, dated Dec. 14, 2017, 14 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/046828, dated Mar. 1, 2018, 19 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/048044, dated Mar. 22, 2018, 8 pages. |
| International Search Report & Written Opinion received for PCT Patent Application No. PCT/US2016/014997, dated Aug. 31, 2016, 21 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/US2015/053353, dated May 9, 2016, 21 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/016216, dated Jun. 27, 2016, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/021403, dated May 12, 2016, 23 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/025418, dated Jul. 1, 2016, 20 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/034175, dated Oct. 7, 2016, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/046828, dated Dec. 15, 2016, 22 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/048044, dated Oct. 31, 2016, 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/US2017/035554, dated Sep. 22, 2017, 42 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/036608, dated Oct. 20, 2017, 15 pages. |
| Invitation to Pay Addition Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2016/014997, dated May 2, 2016, 5 pages. |
| Invitation to Pay Addition Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2016/016216, dated Apr. 20, 2016, 6 pages. |
| Invitation to Pay Addition Fees received for PCT Patent Application No. PCT/US2017/036608, dated Aug. 14, 2017, 2 pages. |
| Invitation to Pay Additional fees received for PCT Patent Application No. PCT/US2015/053353, dated Jan. 21, 2016, 7 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2016/034175, dated Aug. 11, 2016, 3 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2016/046828, dated Sep. 23, 2016, 2 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/US2017/035554, dated Jul. 20, 2017, 2 pages. |
| Invitation to Restrict or Pay Additional Fees received for PCT Patent Application No. PCT/US2016/016216, dated Dec. 19, 2016, 9 pages. |
| “iOS Security”, White Paper, Online Available at: <https://web.archive.org/web/20150526223200/http://www.apple.com/business/docs/iOS_Security_Guide.pdf>, Apr. 2015, 55 pages. |
| “iPhone User Guide For iOS 7.1 Software”, Online Available at: <https://manuals.info.apple.com/MANUALS/1000/MA1681/en_US/ip>, Mar. 10, 2014, pp. 1-162. |
| Mugs, Online Available at: <https://web.archive.org/web/20151029034349/http://le-mugs.com/>, Oct. 29, 2015. |
| Non Final Office Action received for U.S. Appl. No. 14/869,877, dated Jan. 29, 2016, 18 pages. |
| Non Final Office Action received for U.S. Appl. No. 14/869,877, dated Jun. 16, 2017, 17 pages. |
| Non Final Office Action received for U.S. Appl. No. 14/869,877, dated Oct. 5, 2018, 19 pages. |
| Non Final Office Action received for U.S. Appl. No. 14/870,793, dated Apr. 19, 2016, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/599,424, dated Jan. 17, 2018, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/599,425, dated Jan. 11, 2018, 42 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/599,425, dated Oct. 26, 2016, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,606, dated Dec. 7, 2017, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/846,574, dated Nov. 29, 2017, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/863,069, dated Oct. 5, 2017, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/864,759, dated Mar. 20, 2018, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/870,726, dated Sep. 16, 2016, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/142,661, dated Jan. 25, 2017, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/188,081, dated Jun. 8, 2017, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/188,081, dated Mar. 30, 2018, 21 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/687,384, dated Jul. 6, 2018, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/985,570, dated Aug. 16, 2018, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/846,574, dated Jun. 22, 2017, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/846,574, dated Sep. 20, 2018, 61 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015267240, dated Apr. 10, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2016229847, dated Sep. 12, 2018, 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. 2015201028, dated Mar. 21, 2017, 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 Japanese Patent Application No. 2014-259225, dated Feb. 27, 2017, 3 pages (Official Copy Only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Notice of Allowance received for Japanese Patent Application No. 2015-129152, dated May 8, 2017, 3 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Notice of Allowance received for Japanese Patent Application No. 2017-057997, dated Apr. 23, 2018, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Notice of Allowance received for Japanese Patent Application No. 2017-132229, dated Jun. 25, 2018, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Notice of Allowance received forTaiwanese Patent Application No. 104117509, dated Mar. 31, 2017, 3 pages (Official Copy Only) (See Communication under 37 CFR § 198(a) (3)). |
| Notice of Allowance received for U.S. Appl. No. 13/666,943, dated Aug. 11, 2016, 2 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. 2017, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/870,726, dated Sep. 11, 2018, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/142,661, dated Feb. 15, 2018, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/142,661, dated Oct. 4, 2017, 22 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/876,673, dated May 4, 2018, 27 pages. |
| Office Action received for Japanese Patent Application No. 2016-569945, dated Nov. 10, 2017, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2015267240, dated Apr. 10, 2017, 5 pages. |
| Office Action received for Australian Patent Application No. 2015267240, dated Mar. 21, 2018, 5 pages. |
| Office Action received for Australian Patent Application No. 2016100796, dated Aug. 26, 2016, 6 pages. |
| Office Action received for Australian Patent Application No. 2016100796, dated Feb. 13, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2016215440, dated Mar. 13, 2018, 3 pages. |
| Office Action received for Australian Patent Application No. 2016229847, dated Jul. 3, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2017100231, dated Apr. 13, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2017100667, dated Aug. 3, 2017, 9 pages. |
| Office Action received for Australian Patent Application No. 2017101375, dated Dec. 1, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2017101375, dated Feb. 19, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2017201548, dated Feb. 26, 2018, 2 pages. |
| Office Action received for Australian Patent Application No. 2018100158, dated Apr. 23, 2018, 5 pages. |
| Office Action received for Canadian Patent Application No. 2,984,527 dated Sep. 11, 2018, 5 pages. |
| Office Action received for Chinese Patent Application No. 201510284850.3, dated Jul. 9, 2018, 11 pages (2 pages of English Translation and 9 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201510284850.3, dated Nov. 28, 2017, 15 pages (5 pages of English Translation and 10 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201580028677.9, dated May 25, 2018, 14 pages (4 pages of English Translation and 10 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201620509515.9, dated Nov. 9, 2016, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for Danish Patent Application No. PA201670362, dated Jan. 29, 2018, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670362, dated Jun. 1, 2017, 6 pages. |
| Office Action received for Danish Patent Application No. PA201670362, dated Nov. 21, 2016, 11 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 May 7, 2018, 4 pages. |
| Office Action received for Danish Patent Application No. PA201670749, dated Jan. 30, 2017, 11 pages. |
| Office Action received for Danish Patent Application No. PA201670749, dated Oct. 3, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670751, dated Jan. 13, 2017, 9 pages. |
| Office Action received for Danish Patent Application No. PA201670751, dated Nov. 13, 2017, 2 pages. |
| Office Action received for Danish Patent Application No. PA201770423, dated Jun. 12, 2018, 7 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. 15730890.9, dated Aug. 3, 2017, 4 pages. |
| Office Action received for Japanese Patent Application No. 2014-259225, dated May 27, 2016, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2015-129152, dated Sep. 23, 2016, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-569945, dated Sep. 10, 2018, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2017-057997, dated Jan. 9, 2018, 6 pages (3 pages of English translation and 3 pages of official copy). |
| Office Action received for Japanese Patent Application No. 2017-132229, dated Mar. 16, 2018, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104117509, dated Aug. 22, 2016, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104132636, dated Mar. 23, 2017, 25 pages (10 pages of English Translation and 15 pages of Official copy). |
| Office Action received forTaiwanese Patent Application No. 104132636, dated Oct. 31, 2017, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| 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. PA201770423, dated Oct. 4, 2017, 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. 15730890.9, mailed on Sep. 10, 2018, 11 pages. |
| Written Opinion Issued from International Preliminary Examining Authority for PCT Application No. PCT/US2016/016216, dated Feb. 20, 2017, 12 pages. |
| Communication Regarding Intention to Grant received forthe European Patent Application No. 07814633.9, dated Mar. 19, 2010, 4 pages. |
| Decision to Grant received forthe European Patent Application No. 07814633.9, dated Sep. 2, 2010, 3 pages. |
| Office Action received for European Patent Application No. 07814633.9, dated Aug. 10, 2009, 3 pages. |
| Decision to Grant received forthe 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. 31, 2011, 6 pages. |
| Summons to Attend Oral Proceeding received for European Patent Application No. 10172417.7, Jan. 28, 2013, 6 pages., 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. |
| 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 forthe 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. |
| 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. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,372, dated Dec. 5, 2014, 11 pages. |
| Final Office Action received for U.S. Appl. No. 14/599,425, dated Oct. 8, 2015, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/599,425, dated Mar. 17, 2015, 16 pages. |
| Notice of Allowance received forthe 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, 19 pages (7 pages of English Translation and 12 pages of Official copy). |
| Decision to Grant received for Japanese Patent Application No. 2009-526943, dated Dec. 2, 2011, 3 pages (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| 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 (Official Copy only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Office Action received for Japanese Patent Application No. 2013-140171, dated Jul. 22, 2014, 4 pages (2 pages of English Translation and 2 pages of Official copy). |
| Office Action Received for Japanese Patent Application No. 2014-259225, dated Nov. 20, 2015, 2 pages (Official copy Only) (See Communication under 37 CFR § 198(a) (3)). |
| Office Action received for Australian Patent Application No. 2015100734, dated Jul. 29, 2015, 5 pages. |
| Office Action received for Australian Patent Application No. 2015201028, dated Mar. 15, 2016, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201520358505.5, dated Jan. 13, 2016, 3 pages (2 pages of English Translation and 1 page of Official Copy). |
| Office action received for Indian Patent Application No. 2797CHENP2008 , dated Jan. 29, 2014, 3 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. |
| Codrington, Simon, “Intuitive Scrolling Interfaces with CSS Scroll Snap Points”, Online Available at: <https://www.sitepoint.com/intuitive-scrolling-interfaces-with-css-scroll-snap-points/>, Dec. 8, 2015, 14 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, pp. 1660-1663. |
| Das, et al., “Event-based Location Matching for Consumer Image Collections”, Consumer Image Collections, CIVR, 2008, Proc. of the ACM Int. Conf. on Image and Video Retrieval, 2008, 5 pages. |
| Filipowicz, Luke, “How to use the QuickType keyboard in iOS 8”, Online Available at: < <https://www.imore.com/comment/568232>, Oct. 11, 2014, pp. 1-17. |
| Gallagher, et al., “Image Annotation Using Personal Calendars as Context”, ACM Intl. Conf. on Multimedia, 2008, 4 pages. |
| Han, et al., “Density-Based Methods”, Data Mining Concepts and Techniques, Elsevier, 2006, pp. 418-420. |
| 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. |
| Inews and Tech, “How To Use The QuickType Keyboard In IOS 8”, Online Available at: < http://www.inewsandtech.com/how-to-use-the-quicktype-keyboard-in-ios-8/>, Sep. 17, 2014, 6 pages. |
| Jobs, Steve, “iPhone Introduction in 2007 (Complete)”, Online 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. (Official Copy Only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Liao. T. Warren, “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”, Online Available at: <https://developer.mozilla.org/en-US/docs/Web/Guide/Events/Mouse_gesture_events>, May 14, 2009, 3 pages. |
| 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 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. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/032474, dated Aug. 19, 2015, 8 pages. |
| Razykdreview, “In Depth Review of Apple Watch Activity and Workout App”, Online Available at: < https://www.youtube.com/watch?v=GkKl3qlK0ow>, May 11, 2015, 1 page. |
| Rizknows, “Garmin Connect Mobile App—REVIEW#2”, Online Available at: < https://www.youtube.com/watch?v=7my3wMpeRbE>, Oct. 22, 2015, 1 page. |
| Tomic, et al. “Emoticons”, FIP—Journal of Finance and Law, vol. 1, No. 1, 2013, pp. 35-42. |
| Tweedie, Steven, “Create and Customize Your Own Emojis with ‘Makemoji’ for iPhone”, Online Available at: < http://www.businessinsider.com/create-custom-emojis-with-makemoji-app-2014-8>, Aug. 19, 2014, 6 pages. |
| Van Wijk, et al. “Cluster and Calendar based Visualization of Time Series Data”, IEEE Comput. Soc., 1999, 7 pages. |
| Whitwam, Ryan, “Facer is Fast Becoming the De Facto Custom Watch Face Maker for Android Wear”, Online Available at: <http://www.androidpolice.com/2014/09/19/facer-is-fast-becoming-the-de-facto-custom-watch-face-maker-for-android-wear>, Sep. 19, 2014, 11 pages. |
| Willcom, “Operation Manual for WS003SH”, Jp, Dec. 2005, pp. 4-1 to 4-7. (Official Copy Only) (See Communication under 37 CFR § 1.98(a) (3)). |
| Extended European Search Report received for European Patent Application No. 19163212.4, dated Jun. 25, 2019, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/188,081, dated Jun. 26, 2019, 8 pages. |
| Office Action received for Australian Patent Application No. 2018279037, dated Jun. 18, 2019, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2017-7034558, dated Jun. 4, 2019, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Wikipedia, “Enhanced Multi-Level Precedence and Pre-emption Service”, Available online at: https ://de.wikipedia.org/w/index.php?%20title=Enhanced%20Multi%E3%83%BCLevel_Precedence_And_Pre-emption_Service&oldid=123047429, Oct. 2013, 2 pages (Official copy only) {See Communication under 37 CFR § 1.98(a) (3)}. |
| Non-Final Office Action received for U.S. Appl. No. 14/846,574, dated Sep. 30, 2019, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/391,269, dated Aug. 22, 2019, 44 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-562330, dated Sep. 20, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680008151.9, dated Aug. 27, 2019, 24 pages (11 pages of English Translation and 13 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201811616429.8, dated Sep. 4, 2019, 26 pages (15 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7034558, dated Sep. 25, 2019, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Ikeda, Masaru, “beGLOBAL Seoul 2015 Startup Battle: Talkey”, YouTube Publisher, Retrieved via URL: https://www.youtube.com/watch?v=4Wkp7sAAIdg, May 14, 2015, 1 page. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/554,204, dated Oct. 11, 2019, 5 pages. |
| Certificate of Examination received for Australian Patent Application No. 2019100490, dated Oct. 16, 2019, 2 pages. |
| Final Office Action received for U.S. Appl. No. 16/402,057, dated Oct. 17, 2019, 23 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7007053, dated Sep. 26, 2019, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 15/188,081, dated Dec. 13, 2018, 10 pages. |
| Final Office Action received for U.S. Appl. No. 15/281,524, dated Dec. 27, 2018, 6 pages. |
| Hughes, Neil, “Apple Explores Merging Cloud Content with Locally Stored Media Library”, available at <https://appleinsider.com/articles/11/02/10/apple_explores_merging_cloud_content_ with_locally_stored_media_library.html>, XP55040717, published on Feb. 10, 2011, 2 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/US2017/036608, dated Dec. 27, 2018, 12 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7034875, dated Dec. 12, 2018, 4 pages (1 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 15/616,480, dated Jan. 3, 2019, 8 pages. |
| Office Action received for Australian Patent Application No. 2017284958, dated Dec. 13, 2018, 3 pages. |
| Decision on Appeal received for U.S. Appl. No. 14/863,099, dated Aug. 22, 2019, 9 pages. |
| Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US2019/024790, dated Jul. 18, 2019, 10 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018214074, dated Aug. 6, 2019, 3 pages. |
| Office Action received for Canadian Patent Application No. 2,984,527, dated Jul. 25, 2019, 4 pages. |
| Office Action received for European Patent Application No. 17810749.6, dated Aug. 20, 2019, 9 pages. |
| Office Action received for Japanese Patent Application No. 2016-569945, dated Jul. 29, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Extended European Search Report received for European Patent Application No. 17813824.4, dated Dec. 5, 2019, 7 pages. |
| “How to Send and Receive files over Bluetooth on an Android Phone”, Online Available at: https://web.archive.org/web/20160529062240/http://www.androidtipsandhacks.com/android/send-receive-files-bluetooth-android-phone/, May 29, 2016, 7 pages. |
| “Kamcord—Wikipedia”, Online Available at: https://en.wikipedia.org/w/index.php?title=Kamcord&oldid=712263010>, Mar. 28, 2016, 2 pages. |
| “Kamcord Developers”, Online Available at: https://web.archive.org/web/20140827043641/http://www.kamcord.com/developers, Aug. 27, 2014, 7 pages. |
| “Kamcord Developers—Quick Start Guide”, Online Available at: https://web.archive.org/web/20140801055705/https://www.kamcord.com/developers/docs/ios/features-and-settings/, Aug. 1, 2014, 10 pages. |
| Office Action received for Chinese Patent Application No. 201610371774.4, dated Dec. 2, 2019, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201811330077.X, dated Nov. 13, 2019, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 14/841,606, dated Feb. 28, 2019, 3 pages. |
| Extended European Search Report received for European Patent Application No. 16844879.3, dated Mar. 1, 2019, 6 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2016215440, dated Feb. 28, 2019, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/188,081, dated Mar. 20, 2019, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/985,570, dated Mar. 13, 2019, 22 pages. |
| Office Action received for Australian Patent Application No. 2018101855, dated Feb. 22, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201670609, dated Mar. 1, 2019, 9 pages. |
| Office Action received for Japanese Patent Application No. 2017-562330, dated Jan. 18, 2019, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Preliminary Opinion received for European Patent Application No. 15730890.9, dated Mar. 7, 2019, 4 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/863,069, dated Mar. 1, 2019, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/870,726, dated Mar. 6, 2019, 6 pages. |
| Hazra et al., “Sentiment Learning Using Twitter Ideograms”, 8th Annual Industrial Automation and Electromechanical Engineering Conference, 2017, pp. 115-120. |
| Komninos et al., “Text Input on a Smart Watch”, IEEE, 2014, pp. 50-58. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 14/846,574, dated Feb. 3, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/554,204, dated Jan. 31, 2020, 3 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870385, dated Jan. 24, 2020, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/109,487, dated Feb. 5, 2020, 19 pages. |
| Office Action received for Australian Patent Application No. 2018279037, dated Jan. 17, 2020, 4 pages. |
| Office Action received for Indian Patent Application No. 9044/CHENP/2014, dated Jan. 24, 2020, 6 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 16804040.0, mailed on Jan. 24, 2020, 11 pages. |
| Wikipedia, “Emoji”, Available online at https://en.wikipedia.org/w/index.php?title=Emoji&oldid=648831795, Feb. 25, 2015, 12 pages. |
| Wikipedia, “Emoticon”, Available online at https://en.wikipedia.org/w/index.php?title=Emoticon&oldid=648776142, Feb. 25, 2015, 9 pages. |
| Final Office Action received for U.S. Appl. No. 15/554,204, dated Oct. 31, 2019, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/614,121, dated Nov. 4, 2019, 44 pages. |
| Office Action received for Australian Patent Application No. 2018206772, dated Nov. 6, 2019, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7029673, dated Nov. 5, 2019, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Internet Blog Post, “[Pc] Pre-Customization of Black Desert's Characters”, Online Available at: https://blog.naver.com/hsh6051/220209813968, Dec. 14, 2014, 41 pages (21 pages of English translation and 20 pages of Official Copy). |
| Decision on Appeal received for U.S. Appl. No. 14/774,664, dated Sep. 12, 2019, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/024790, dated Sep. 11, 2019, 18 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017284958, dated Sep. 3, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870385, dated Aug. 23, 2019, 3 pages. |
| Decision to Grant received for European Patent Application No. 16706081.3, dated Nov. 29, 2018, 2 pages. |
| Extended European Search Report received for European Patent Application No. 16807953.1, dated Dec. 4, 2018, 7 pages |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/035554, dated Dec. 20, 2018, 39 pages. |
| IOS 8 Release, “Quick Type Keyboard on iOS 8 Makes Typing Easier”, Online available at: < https://www.youtube.com/watch?v=0CIdLR4fhVU >, Jun. 3, 2014, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/614,121, dated Nov. 30, 2018, 28 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/599,424, dated Dec. 13, 2018, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/599,425, dated Dec. 19, 2018, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/864,759, dated Dec. 14, 2018, 10 pages. |
| Office Action received for Australian Patent Application No. 2016270323, dated Nov. 26, 2018, 4 pages. |
| Extended European Search Report received for European Patent Application No. 17813778.2, dated Jan. 10, 2020, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/454,884, dated Jan. 14, 2020, 41 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-569945, dated Jan. 7, 2020, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7007053, dated Dec. 19, 2019, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 14/863,069, dated Feb. 6, 2019, 6 pages. |
| Office Action received for Australian Patent Application No. 2016215440, dated Jan. 22, 2019, 2 pages. |
| Office Action received for Korean Patent Application No. 10-2017-7034558, dated Dec. 15, 2018, 15 pages (7 pages of English Translation and 8 pages of Official Copy). |
| Partial European Search Report received for European Patent Application No. 18197554.1, dated Jan. 22, 2019, 8 pages. |
| Advisory Action received for U.S. Appl. No. 14/846,574, dated Jul. 31, 2020, 8 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/450,531, dated Aug. 11, 2020, 5 pages. |
| Office Action received for European Patent Application No. 19724963.4, dated Jul. 28, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 14/846,574, dated Jul. 21, 2020, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/554,204, dated Jul. 13, 2020, 10 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/407,590, dated Jun. 5, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/454,884, dated Jun. 2, 2020, 3 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 16804040.0, mailed on May 28, 2020, 15 pages. |
| Final Office Action received for U.S. Appl. No. 14/846,574, dated Jun. 4, 2020, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/378,136, dated Jun. 2, 2020, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/450,531, dated Jun. 10, 2020, 10 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870385, dated Mar. 26, 2020, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/389,722, dated Apr. 3, 2020, 15 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018206772, dated Mar. 17, 2020, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7005314, dated Mar. 24, 2020, 6 pages (2 page of English Translation and 4 pages of Official Copy). |
| 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/109,487, dated May 12, 2020, 8 pages. |
| Office Action received for Chinese Patent Application No. 201680008151.9, dated Apr. 20, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680013193.1, dated Mar. 25, 2020, 21 pages (8 pages of English Translation and 13 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA201670609, dated May 4, 2020, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/614,121, dated Feb. 13, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2018206772, dated Feb. 6, 2020, 4 pages. |
| Office Action received for Chinese Patent Application No. 201680031609.2, dated Jan. 15, 2020, 20 pages (7 pages of English Translation and 13 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-138559, dated Jan. 27, 2020, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/389,722, dated Jul. 7, 2020, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/402,057, dated Jul. 6, 2020, 2 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/869,877, mailed on Jun. 26, 2020, 14 pages. |
| Office Action received for Chinese Patent Application No. 201680049868.8, dated May 25, 2020, 30 pages (19 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201811330077.X, dated May 18, 2020, 9 pages (3 pages of English Translation and 6 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 15/554,204, dated Mar. 12, 2020, 3 pages. |
| Applicant-Initiated Interview Summary for U.S. Appl. No. 16/402,057, dated Mar. 16, 2020, 3 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7007053, dated Mar. 12, 2020, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 15/614,121, dated Mar. 6, 2020, 8 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7038235, dated Mar. 9, 2020, 15 pages (7 pages of English Translation and 8 pages of Official Copy). |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/109,487, dated Apr. 21, 2020, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/363,945, dated Apr. 24, 2020, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/407,590, dated Apr. 10, 2020, 12 pages. |
| Office Action received for Chinese Patent Application No. 201710439448.7, dated Mar. 27, 2020, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/363,945, dated Aug. 13, 2020, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/554,204, dated Aug. 19, 2020, 3 pages. |
| Final Office Action received for U.S. Appl. No. 16/407,590, dated Aug. 25, 2020,14 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201811616429.8, dated Aug. 5, 2020, 3 pages (2 pages of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/109,487, dated Aug. 18, 2020, 8 pages. |
| Office Action received for Australian Patent Application No. 2017277971, dated Aug. 12, 2020, 3 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17810749.6, mailed on Aug. 12, 2020, 11 pages. |
| 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. 201610371774.4, dated Jun. 4, 2020, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201680008151.9, dated Jun. 16, 2020, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for Australian Patent Application No. 2017277971, dated Jun. 3, 2020, 3 pages. |
| Office Action received for European Patent Application No. 18197554.1, dated Jun. 15, 2020, 4 pages. |
| Intention to Grant received for European Patent Application No. 16844879.3, dated May 11, 2020, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/377,892, dated May 21, 2020, 9 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017286296, dated May 1, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018279037, dated May 13, 2020, 3 pages. |
| Office Action received for Chinese Patent Application No. 201811616429.8, dated May 7, 2020, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for European Patent Application No. 18213157.3, dated May 15, 2020,7 pages. |
| Result of Consultation received for European Patent Application No. 17810749.6, mailed on Dec. 15, 2020, 3 pages. |
| Advisory Action received for U.S. Appl. No. 16/454,884, dated Jan. 1, 2021, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 14/846,574, dated Jan. 14, 2021, 5 pages. |
| Result of Consultation received for European Patent Application No. 17810749.6, mailed on Jan. 18, 2021, 3 pages. |
| Result of Consultation received for European Patent Application No. 17810749.6, mailed on Jan. 21, 2021, 21 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19724963.4, mailed on Dec. 23, 2020, 8 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/377,892, dated Oct. 13, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/378,136, dated Oct. 13, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/407,590, dated Nov. 17, 2020, 6 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. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/584,783, dated May 4, 2020, 3 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. |
| Decision to Grant received for European Patent Application No. 16844879.3, dated Sep. 24, 2020, 2 pages. |
| Decision to Refuse received for European Patent Application No. 16804040.0, dated Nov. 4, 2020, 18 pages. |
| Examiner's Pre-Review Report received for Japanese Patent Application No. 2018-138559, dated Jul. 29, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 16/454,884, dated Sep. 11, 2020, 28 pages. |
| Final Office Action received for U.S. Appl. No. 16/584,783, dated May 19, 2020, 19 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/US2020/031442, dated Oct. 30, 2020, 28 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/031442, dated Aug. 25, 2020, 22 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 16804040.0, mailed on Nov. 2, 2020, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/846,574, dated Sep. 24, 2020, 29 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. |
| Non-Final Office Action received for U.S. Appl. No. 16/601,064, dated Oct. 7, 2020, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/614,121, dated Aug. 27, 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/363,945, dated Sep. 23, 2020, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/450,531 dated Sep. 25, 2020, 7 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 Chinese Patent Application No. 201680013193.1, dated Sep. 7, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680031609.2, dated Aug. 20, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680049868.8, dated Oct. 20, 2020, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201710439448.7, dated Oct. 10, 2020, 19 pages (8 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201811136445.7, dated Oct. 28, 2020, 17 pages (10 pages of English Translation and 7 pages of Official Copy). |
| 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. 16807953.1, dated Sep. 10, 2020, 4 pages. |
| Office Action received for European Patent Application No. 19163212.4, dated Oct. 12, 2020, 4 pages. |
| Office Action received for Japanese Patent Application No. 2019-123115, dated Aug. 31, 2020, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2019-151358, dated Oct. 2, 2020, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2019-7029673, dated Sep. 3, 2020, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-7018255, dated Sep. 10, 2020, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 16807953.1, mailed on Sep. 24, 2020, 3 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201970535, dated Nov. 5, 2019, 10 pages. |
| Ritchie Rene, “QuickType keyboard in iOS 8: Explained”, Retrieved via URL: https://www.imore.com/quicktype-keyboards-ios-8-explained, Jun. 21, 2014, pp. 1-19. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/454,884, dated Dec. 4, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/601,064, dated Dec. 14, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/736,711, dated Oct. 16, 2020, 3 pages. |
| Final Office Action received for U.S. Appl. No. 16/389,722, dated Dec. 8, 2020, 18 pages. |
| Final Office Action received for U.S. Appl. No. 16/736,711, dated Dec. 10, 2020, 11 pages. |
| International Search Report and written Opinion received for PCT Patent Application No. PCT/US2020/028215, dated Aug. 10, 2020, 18 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/028215, dated Jun. 19, 2020, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/736,711, dated Jun. 11, 2020, 10 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019271873, dated Nov. 30, 2020, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-123115, dated Nov. 30, 2020, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/407,590, dated Dec. 16, 2020, 6 pages. |
| Office Action received for Australian Patent Application No. 2020204259, dated Nov. 30, 2020, 8 pages. |
| Office Action received for Australian Patent Application No. 2020204506, dated Dec. 7, 2020, 6 pages. |
| Office Action received for European Patent Application No. 16762356.0, dated Dec. 11, 2020, 7 pages. |
| Office Action received for European Patent Application No. 17813778.2, dated Nov. 26, 2020, 10 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/377,892, dated Mar. 26, 2021,2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/378,136, dated Mar. 26, 2021,2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/983,815, dated Mar. 31, 2021, 6 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201680031609.2, dated Mar. 18, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/407,590, dated Mar. 22, 2021, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/983,815, dated Mar. 18, 2021, 11 pages. |
| Office Action received for Chinese Patent Application No. 201680013193.1, dated Feb. 1, 2021, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/389,722, dated Feb. 11, 2021, 4 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 16/584,783, dated Feb. 17, 2021, 9 pages. |
| Extended European Search Report received for European Patent Application No. 20197945.7, dated Feb. 9, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/846,574, dated Feb. 9, 2021, 12 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/584,776, dated Feb. 18, 2021, 3 pages. |
| Advisory Action received for U.S. Appl. No. 16/377,892, dated Apr. 9, 2021, 4 pages. |
| Advisory Action received for U.S. Appl. No. 16/378,136, dated Apr. 12, 2021, 4 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020204506, dated Apr. 8, 2021, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/407,590, dated Apr. 9, 2021, 3 pages. |
| Office Action received for European Patent Application No. 16807953.1, dated Apr. 7, 2021, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7029673, dated Apr. 8, 2021, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/846,574, dated Apr. 15, 2021, 3 pages. |
| Decision to Refuse received for European Patent Application No. 17810749.6, dated Jan. 29, 2021, 24 pages. |
| Final Office Action received for U.S. Appl. No. 16/377,892, dated Jan. 28, 2021, 11 pages. |
| Final Office Action received for U.S. Appl. No. 16/378,136, dated Jan. 28, 2021, 9 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 17810749.6, mailed on Jan. 26, 2021, 8 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019264623, dated Jan. 4, 2021, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201710439448.7, dated Jan. 26, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2019-151358, dated Jan. 22, 2021, 4 pages (1 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/584,776, dated Feb. 1, 2021, 9 pages. |
| Office Action received for Japanese Patent Application No. 2020-010239, dated Jan. 4, 2021, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/378,136, dated Jun. 11, 2021, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/389,722, dated Jun. 3, 2021, 17 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/378,136, dated Jun. 3, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/736,711, dated Jun. 8, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/814,770, dated Jun. 1, 2021, 9 pages. |
| Result of Consultation received for European Patent Application No. 19724963.4, mailed on May 31, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/736,711, dated May 17, 2021, 6 pages. |
| Intention to Grant received for European Patent Application No. 18213157.3, dated May 19, 2021, 8 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201680013193.1, dated May 7, 2021, 5 pages (1 page of English Translation and 4 pages 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 U.S. Appl. No. 16/377,892, dated May 24, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/601,064, dated May 17, 2021, 9 pages. |
| 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). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 16762356.0, mailed on May 10, 2021, 10 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. 16/389,722, dated Mar. 9, 2021, 5 pages. |
| Final Office Action received for U.S. Appl. No. 16/601,064, dated Mar. 8, 2021, 8 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017277971, dated Feb. 17, 2021, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201680049868.8, dated Feb. 9, 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). |
| Notice of Allowance received for U.S. Appl. No. 16/736,711, dated Apr. 21, 2021, 8 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). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/846,574, dated Apr. 30, 2021, 3 pages. |
| Result of Consultation received for European Patent Application No. 19724963.4, mailed on Jul. 8, 2021, 3 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). |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 19724963.4, mailed on Jun. 22, 2021, 2 pages. |
| Office Action received for Australian Patent Application No. 2019266054, dated Jun. 29, 2021, 3 pages. |
| Office Action received for Australian Patent Application No. 2019266054, dated Aug. 23, 2021, 4 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022200514, dated Apr. 17, 2023, 3 pages. |
| Advisory Action received for U.S. Appl. No. 16/389,722, dated Jun. 9, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/388,493, dated Feb. 17, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/389,722, dated Feb. 18, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/389,722, dated May 31, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/389,722, dated Nov. 4, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/389,722, dated Sep. 7, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/679,967, dated Feb. 10, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/679,967, dated Jun. 1, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/679,967, dated Oct. 25, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/068,386, dated Apr. 24, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/068,386, dated Jan. 13, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/068,386, dated Sep. 21, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/116,775, dated Nov. 3, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/126,571, dated Jan. 27, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/153,703, dated May 11, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/327,204, dated Jan. 25, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/408,220, dated Oct. 18, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/516,537, dated Jul. 5, 2022, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/516,537, dated Nov. 22, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/542,947, dated Apr. 28, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/542,947, dated Jul. 10, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/744,499, dated Jan. 27, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/744,500, dated May 30, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/862,097, dated Mar. 1, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/862,097, dated May 18, 2023, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/885,807, dated May 26, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/951,875, dated Feb. 28, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/951,875, dated Jun. 27, 2023, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/952,027, dated May 30, 2023, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/153,922, dated May 12, 2023, 2 pages. |
| Board Decision received for Chinese Patent Application No. 201510284850.3, dated Mar. 3, 2022, 27 pp. (1 page of English Translation and 26 pages of Official Copy). |
| Board Opinion received for Chinese Patent Application No. 201510284850.3, dated Jul. 2, 2021, 13 pages (3 pages of English Translation and 10 pages of Official Copy). |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 18197554.1, dated Feb. 6, 2023, 8 pages. |
| Canon Ixus 700—Additional Evidence and Information, 2023, 3 pages (Official Copy Only) (See Communication Under Rule 37 Cfr § 1.98(a) (3)). |
| Canon, “Camera User Guide Canon (UK) Ltd”, Online available at: https://bedienungsanleitungdeutsch.de/bedienungsanleitunghandbuch/Canon_Digital_lxu_s_700 En.pdf, 2005, 196 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/377,892, dated Aug. 11, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/378,136, dated Aug. 11, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/736,711, dated Jun. 17, 2021, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/116,775, dated Jan. 28, 2022, 2 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/125,744, dated Dec. 24, 2021, 2 page. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/125,744, dated Mar. 10, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/125,744, dated Mar. 30, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/153,703, dated Jan. 19, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/153,703, dated Nov. 10, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/153,703, dated Sep. 14, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/373,272, dated Apr. 26, 2022, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/697,539, dated Feb. 1, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/744,499, dated Mar. 21, 2023, 4 pages. |
| Decision on Appeal received for U.S. Appl. No. 16/454,884, dated Feb. 16, 2022, 12 pages. |
| Decision on Appeal received for U.S. Appl. No. 16/584,783, dated Oct. 14, 2021, 12 pages. |
| Decision to Grant received for European Patent Application No. 16762356.0, dated Apr. 26, 2022, 2 pages. |
| Decision to Grant received for European Patent Application No. 18213157.3, dated Feb. 24, 2022, 2 pages. |
| Decision to Grant received for European Patent Application No. 19724963.4, dated Feb. 3, 2022, 2 pages. |
| Decision to Grant received for European Patent Application No. 20197945.7, mailed on Jul. 20, 2023, 2 pp. |
| Decision to Refuse received for European Patent Application No. 17813778.2, mailed on Jan. 24, 2022, 17 pp. |
| Decision to Refuse received for European Patent Application No. 18197554.1, mailed on Mar. 21, 2023, 17 pp. |
| European Search Report received for European Patent Application No. 21165295.3, mailed on Jun. 18, 2021, 4 pp. |
| Examiner's Answer to Appeal Brief received for U.S. Patent Application No. 16/454,884, mailed on Sep. 17, 2021, 33 pp. |
| Extended European Search Report received for European Patent Application No. 22150207.3, mailed on Apr. 11, 2022, 11 pp. |
| Extended European Search Report received for European Patent Application No. 22152524.9, mailed on May 02, 2022, 10 pp. |
| Extended European Search Report received for European Patent Application No. 22164099.8, mailed on Aug. 25, 2022, 9 pp. |
| Extended European Search Report received for European Patent Application No. 22170561.9, mailed on Aug. 10, 2022, 11 pp. |
| Extended European Search Report received for European Patent Application No. 22173249.8, mailed on Aug. 19, 2022, 15 pp. |
| Final Office Action received for U.S. Patent Application No. 16/389,722, mailed on Dec. 06, 2021, 19 pp. |
| Final Office Action received for U.S. Patent Application No. 16/389,722, mailed on Mar. 17, 2023, 14 pp. |
| Final Office Action received for U.S. Patent Application No. 16/679,967, mailed on Nov. 10, 2021, 14 pp. |
| Final Office Action received for U.S. Patent Application No. 17/068,386, mailed on Mar. 03, 2022, 29 pp. |
| Final Office Action received for U.S. Patent Application No. 17/068,386, mailed on May 08, 2023, 23 pp. |
| Final Office Action received for U.S. Patent Application No. 17/516,537, mailed on Oct. 11, 2022, 9 pp. |
| Final Office Action received for U.S. Patent Application No. 17/542,947, mailed on May 25, 2023, 55 pp. |
| Final Office Action received for U.S. Appl. No. 17/862,097, dated Apr. 24, 2023, 17 pages. |
| Final Office Action received for U.S. Appl. No. 17/951,875, dated May 30, 2023, 12 pages. |
| Fono et al., “EyeWindows: Evaluation of Eye-Controlled Zooming Windows for Focus Selection”, CHI 2005, Conference Proceedings, Conference on Human Factors In Computing Systems, Apr. 2-7, 2005, pp. 151-160. |
| Google, “Android User's Guide”, Retrieved from the Internet: https://static.googleusercontent.com/media/www.google.com/en//help/hc/pdfs/mobile/And roidUsersGuide-30-100.pdf, Feb. 23, 2011, 140 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. |
| Intention to Grant received for European Patent Application No. 16762356.0, dated Dec. 23, 2021, 8 pages. |
| Intention to Grant received for European Patent Application No. 18213157.3, dated Oct. 27, 2021, 8 pages. |
| Intention to Grant received for European Patent Application No. 19724963.4, dated Sep. 20, 2021, 7 pages. |
| Intention to Grant received for European Patent Application No. 20197945.7, dated Mar. 28, 2023, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/028215, dated Dec. 16, 2021, 13 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2020/031442, dated Nov. 18, 2021, 21 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/029297, dated Aug. 11, 2022, 13 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/030589, dated Sep. 5, 2022, 26 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/044637, dated Mar. 15, 2023, 19 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/044637, dated Jan. 20, 2023, 12 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2023/021734, dated Jul. 12, 2023, 12 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 (Official Copy only) (See Communication Under Rule 37 CFR § 1.98(a) (3)). |
| Jurick et al., “iPhone Hacks”, Tips & Tools for Unlocking the Power of Your iPhone & iPod touch, online: https://api.pageplace.de/preview/DT0400.9780596550974 A23629666/preview-9780596550974A23629666.pdf, Apr. 2009, 49 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 16762356.0, dated Dec. 17, 2021, 5 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 17813778.2, dated Jan. 21, 2022, 7 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 18197554.1, dated Feb. 22, 2023, 9 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 19724963.4, dated Sep. 3, 2021, 6 pages. |
| Non-Final Office Action received for U.S Appl. No. 16/679,967, dated Sep. 2, 2021, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/388,493, dated Dec. 9, 2021, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/389,722, dated Jul. 7, 2022, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/679,967, dated Apr. 19, 2022, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/068,386, dated Jan. 30, 2023, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/068,386, dated Jul. 15, 2021, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/068,386, dated Oct. 28, 2021, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/116,775, dated Aug. 24, 2021, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/126,571, dated Dec. 21, 2021, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/153,703, dated Mar. 30, 2022, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/327,204, dated Nov. 26, 2021, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/408,220, dated Aug. 3, 2022, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/516,537, dated May 5, 2022, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/519,229, dated Oct. 4, 2022, 7 paages. |
| Non-Final Office Action received for U.S. Appl. No. 17/542,947, dated Mar. 2, 2023, 59 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/744,499, dated Dec. 7, 2022, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/744,500, dated Apr. 19, 2023, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/862,097, dated Feb. 1, 2023, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/885,807, dated May 12, 2023, 50 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/951,875, dated Jan. 23, 2023, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/952,027, dated Apr. 28, 2023, 46 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/153,922, dated May 10, 2023, 7 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019266054, dated Nov. 25, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020204259, dated Jun. 11, 2021, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020210234, dated Feb. 3, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020267310, dated Feb. 23, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020267396, dated Dec. 7, 2021, 3 pages. |
| Notice of acceptance received for Australian Patent Application No. 2021202225, dated Jun. 20, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021203216, dated Jul. 26, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021203636, dated Apr. 14, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021218036, dated May 9, 2023, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022201561, dated Jul. 22, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022201810, dated Jun. 14, 2023, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022209277, dated Apr. 28, 2023, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201780034193.4, dated Oct. 20, 2021, 4 pages. (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201780034203.4, dated Jan. 17, 2022, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 202111644466.1, dated Mar. 30, 2023, 2 pages (01 page of English Translation and 01 page of Official Copy). |
| 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 Japanese Patent Application No. 2020-010239, dated Sep. 3, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| 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). |
| Notice of Allowance received for Japanese Patent Application No. 2021-023661, dated Apr. 10, 2023, 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 Japanese Patent Application No. 2021-566100, dated Jan. 27, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-163700, dated Mar. 3, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. Oct. 2019-7029673, dated Aug. 3, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. Oct. 2021-7036016, dated Sep. 28, 2022, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. Oct. 2021-7036310, dated Apr. 26, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/377,892, dated Sep. 9, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/378,136, dated Sep. 22, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/388,493, dated Jun. 20, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/454,884, dated May 18, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,783, dated Dec. 20, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/679,967, dated Jun. 15, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/679,967, dated Nov. 2, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/814,770, dated Sep. 17, 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. 17/116,775, dated Jan. 18, 2022, 10 paages. |
| Notice of Allowance received for U.S. Appl. No. 17/125,744, dated Feb. 7, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/125,744, dated Oct. 21, 2021, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/126,571, dated Mar. 11, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/153,703, dated Aug. 30, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/153,703, dated Dec. 22, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/327,204, dated May 18, 2022, 18 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/373,272, dated Feb. 9, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/408,220, dated Nov. 15, 2022, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/516,537, dated Apr. 17, 2023, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/516,537, dated Dec. 27, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/519,229, dated Nov. 10, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/697,539, dated Nov. 29, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/739,664, dated Dec. 7, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/744,499, dated Mar. 15, 2023, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/951,875, dated Jul. 26, 2023, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/153,922, dated Jul. 26, 2023, 9 pages. |
| Office Action received for Australian Patent Application No. 2020210234, dated Jul. 30, 2021, 7 pages. |
| Office Action received for Australian Patent Application No. 2020267310, dated Nov. 4, 2021, 2 pages. |
| Office Action received for Australian Patent Application No. 2021202225, dated Apr. 7, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2021203216, dated Mar. 7, 2022, 8 pages. |
| Office Action received for Australian Patent Application No. 2021203636, dated Mar. 23, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2021218036, dated Apr. 13, 2023, 3 pages. |
| Office Action received for Australian Patent Application No. 2021218036, dated Jun. 21, 2022, 5 pages. |
| Office Action received for Australian Patent Application No. 2021218036, dated Nov. 16, 2022, 4 pages. |
| Office Action received for Australian Patent Application No. 2022200514, dated Feb. 15, 2023, 2 pages. |
| Office Action received for Australian Patent Application No. 2022200514, dated Jan. 17, 2023, 3 pages. |
| Office Action received for Australian Patent Application No. 2022201561, dated May 2, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2022201810, dated Mar. 15, 2023, 2 pages. |
| Office Action received for Australian Patent Application No. 2022203278, dated May 10, 2023, 4 pages. |
| Office Action received for Australian Patent Application No. 2022209277, dated Mar. 10, 2023, 6 pages. |
| Office Action received for Australian Patent Application No. 2022235618, dated Jul. 4, 2023, 2 pages. |
| Office Action received for Australian Patent Application No. 2022235618, dated May 19, 2023, 2 pages. |
| Office Action received for Australian Patent Application No. 2022235634, dated May 25, 2023, 4 pages. |
| Office Action received for Chinese Patent Application No. 201780033901.2, dated Jun. 28, 2023, 28 pages (14 pages of English Translation and 14 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201780033901.2, dated Nov. 23, 2022, 44 pages (24 pages of English Translation and 20 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201780034193.4, dated Jun. 8, 2021, 16 pages (7 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201780034203.4, dated Jul. 14, 2021, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201780034203.4, dated Sep. 24, 2021, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| 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. 202011127969.7, dated Mar. 17, 2023, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202011127969.7, dated Nov. 24, 2022, 26 pages (16 pages of English Translation 10 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202080040442.2, dated Apr. 29, 2023, 12 pages (5 pages of English Translation and 7 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 Chinese Patent Application No. 202111487316.4, dated Dec. 28, 2022, 13 pages (8 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202111487316.4, dated Jun. 7, 2023, 20 pages (10 pages of English Translation and 10 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202111644466.1, dated Nov. 2, 2022, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for European Patent Application No. 16807953.1, dated Oct. 7, 2022, 6 pages. |
| Office Action received for European Patent Application No. 17813824.4, dated Nov. 30, 2021, 8 pages. |
| Office Action received for European Patent Application No. 20197945.7, dated Nov. 18, 2022, 5 pages. |
| Office Action received for European Patent Application No. 20723742.1, dated Jan. 2, 2023, 10 pages. |
| Office Action received for European Patent Application No. 20729331.7, dated Jan. 4, 2023, 12 pages. |
| Office Action received for European Patent Application No. 21165295.3, dated Jul. 1, 2021, 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). |
| Office Action received for Indian Patent Application No. 202048019639, dated Sep. 27, 2022, 5 pages. |
| 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). |
| Office Action received for Japanese Patent Application No. 2020-079486, dated Mar. 11, 2022, 8 page (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2021-023661, dated Feb. 25, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2021-023661, dated Oct. 3, 2022, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2021-163700, dated Oct. 7, 2022, 4 pages (2 pages of English Translation and 2 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). |
| Office Action received for Korean Patent Application No. 10-2021-7036016, dated Nov. 10, 2021, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| 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). |
| Phandroid, “How to record & stream using YouTube Gaming”, Available online at: https://www.youtube.com/watch?v=8H5Q1L9M_qI, Jun. 1, 2016, 3 pages. |
| Programmatically download APK from google play store, retrieved from the Internet: https://stackoverflow.com/questions/13703982/prog rammaticallydownload-apk-from-google-play-store/13704021#13704021, Dec. 10, 2012, 2 pages. |
| Puryear Blake, “A modular framework for home healthcare monitoring”, Online available at: https://scholarworks.uark.edu/cgi/viewcontent.cgi?article=1009&context=csceuht, May 2012, 92 pages. |
| Record of Oral Hearing received for U.S. Appl. No. 16/454,884, dated Feb. 14, 2022, 13 pages. |
| Result of Consultation received for European Patent Application No. 16762356.0, dated Nov. 29, 2021, 3 pages. |
| Result of Consultation received for European Patent Application No. 17813778.2, dated Dec. 6, 2021, 17 pages. |
| Result of Consultation received for European Patent Application No. 18197554.1, dated Feb. 3, 2023, 3 pages. |
| Sansford Steve, “Streaming Android Games with OBS on Linux”, Available online at: https://www.youtube.com/watch?v=twyh32Ud8vQ, May 20, 2016, 3 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17813778.2, dated Aug. 13, 2021, 13 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 18197554.1, dated Mar. 23, 2022, 7 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19163212.4, dated Dec. 15, 2021, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20723742.1, dated Jul. 21, 2023, 12 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20729331.7, dated May 22, 2023, 15 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 21165295.3, dated Jul. 25, 2023, 14 pages. |
| Summons to Oral Proceedings received for German Patent Application No. 112007000067.8, dated Dec. 8, 2021, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/697,539, dated Feb. 21, 2023, 2 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. |
| Willem Jonker, “Secure Data Management”, Online available at: http://ndl.ethernet.edu.et/bitstream/123456789/21649/1/291.pdf, Sep. 17, 2010, 177 pages. |
| Xzulas,“PS4 to Twitch—How to Broadcast Gameplay - Camera and Audio Settings”, Available online at: https://www.youtube.com/watch?v=TyTR64RFOwl, Nov. 3, 2014, 4 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20190339822 A1 | Nov 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62668018 | May 2018 | US |
