Patent Grant
11899895
This disclosure relates generally to user interfaces for setting up an electronic device.
User interaction with electronic devices has increased significantly in recent years. These devices can be devices such as computers, tablet computers, televisions, multimedia devices, or mobile devices. Sometimes a user may be setting up a first electronic device. The user may therefore desire efficient setup processes for the first electronic device.
In some circumstances, an output device (e.g., an audio output device, such as a smart speaker) can operate as an output device for the first electronic device (e.g., set-top box), and in some circumstances, the first electronic device can be setup with settings values associated with a user profile. Enhancing the processes for setting an output device for the first electronic device and/or populating settings values for the first electronic device improve a user's experience with the first electronic device and decreases user interaction time, which is particularly important where input devices are battery-operated.
Some embodiments described in this disclosure are directed to ways to facilitate associating an output device with the first electronic device using a second electronic device. Some embodiments described in this disclosure are directed to ways to add an additional user to the first electronic device using a second electronic device. The full descriptions of the embodiments are provided in the Drawings and the Detailed Description, and it is understood that the Summary provided above does not limit the scope of the disclosure in any way.
It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
For a better understanding of the various described embodiments, reference should be made to the Detailed Description below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
In the following description of embodiments, reference is made to the accompanying drawings which form a part hereof, and in which it is shown by way of illustration specific embodiments that are optionally practiced. It is to be understood that other embodiments are optionally used and structural changes are optionally made without departing from the scope of the disclosed embodiments.
There is a need for electronic devices that provide efficient user interfaces and mechanisms for associating an output device with a first electronic device and/or adding an additional user to the first electronic device. In some implementations, a second electronic device with which an output device is associated facilitates associating the output device with the first electronic device. In some implementations, a second electronic device that is associated with an additional user facilitates associating the additional user with the first electronic device. Such techniques can reduce the cognitive burden on a user who uses such devices. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
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 touch pads), 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 or a television with a touch-sensitive surface (e.g., a touch screen display and/or a touch pad). In some embodiments, the device does not have a touch screen display and/or a touch pad, but rather is capable of outputting display information (such as the user interfaces of the disclosure) for display on a separate display device, and capable of receiving input information from a separate input device having one or more input mechanisms (such as one or more buttons, a touch screen display and/or a touch pad). In some embodiments, the device has a display, but is capable of receiving input information from a separate input device having one or more input mechanisms (such as one or more buttons, a touch screen display and/or a touch pad). In some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, “displaying” content includes causing to display the content (e.g., video data rendered or decoded by display controller 156) by transmitting, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content.
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. Further, as described above, it should be understood that the described electronic device, display and touch-sensitive surface are optionally distributed amongst two or more devices. Therefore, as used in this disclosure, information displayed on the electronic device or by the electronic device is optionally used to describe information outputted by the electronic device for display on a separate display device (touch-sensitive or not). Similarly, as used in this disclosure, input received on the electronic device (e.g., touch input received on a touch-sensitive surface of the electronic device) is optionally used to describe input received on a separate input device, from which the electronic device receives input information.
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, a television channel browsing 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 or non-portable devices with touch-sensitive displays, though the devices need not include touch-sensitive displays or displays in general, as described above.
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 or non-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 (HSDPA), 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, intensity sensor controller 159, haptic feedback controller 161 and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input 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, infrared port, 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. As described above, the touch-sensitive operation and the display operation of touch-sensitive display 112 are optionally separated from each other, such that a display device is used for display purposes and a touch-sensitive surface (whether display or not) is used for input detection purposes, and the described components and functions are modified accordingly. However, for simplicity, the following description is provided with reference to a touch-sensitive display. 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 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®, iPod Touch®, and iPad® 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 (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch 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 or non-portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, 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 (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 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.
The touch screen 112 optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward) and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.
Device 100 optionally also includes one or more physical buttons, such as “home” or menu button 204. As previously described, 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 one embodiment, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 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.
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.
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 described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90% or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the description of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting 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.
In some embodiments, display controller 508 causes the various user interfaces of the disclosure to be displayed on display 514. Further, input to device 500 is optionally provided by remote 510 via remote interface 512, which is optionally a wireless or a wired connection. In some embodiments, input to device 500 is provided by a multifunction device 511 (e.g., a smartphone) on which a remote control application is running that configures the multifunction device to simulate remote control functionality, as will be described in more detail below. In some embodiments, multifunction device 511 corresponds to one or more of device 100 in
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 described with reference to
In addition, in methods described herein where one or more steps are contingent upon one or more conditions having been met, it should be understood that the described method can be repeated in multiple repetitions so that over the course of the repetitions all of the conditions upon which steps in the method are contingent have been met in different repetitions of the method. For example, if a method requires performing a first step if a condition is satisfied, and a second step if the condition is not satisfied, then a person of ordinary skill would appreciate that the claimed steps are repeated until the condition has been both satisfied and not satisfied, in no particular order. Thus, a method described with one or more steps that are contingent upon one or more conditions having been met could be rewritten as a method that is repeated until each of the conditions described in the method has been met. This, however, is not required of system or computer readable medium claims where the system or computer readable medium contains instructions for performing the contingent operations based on the satisfaction of the corresponding one or more conditions and thus is capable of determining whether the contingency has or has not been satisfied without explicitly repeating steps of a method until all of the conditions upon which steps in the method are contingent have been met. A person having ordinary skill in the art would also understand that, similar to a method with contingent steps, a system or computer readable storage medium can repeat the steps of a method as many times as are needed to ensure that all of the contingent steps have been performed.
In some embodiments, electronic device 500 includes one or more tactile output generators, where the one or more tactile output generators generate different types of tactile output sequences, as described below in Table 1. In some embodiments, a particular type of tactile output sequence generated by the one or more tactile output generators of the device corresponds to a particular tactile output pattern. For example, a tactile output pattern specifies characteristics of a tactile output, such as the amplitude of the tactile output, the shape of a movement waveform of the tactile output, the frequency of the tactile output, and/or the duration of the tactile output. When tactile outputs with different tactile output patterns are generated by a device (e.g., via one or more tactile output generators that move a moveable mass to generate tactile outputs), the tactile outputs may invoke different haptic sensations in a user holding or touching the device. While the sensation of the user is based on the user's perception of the tactile output, most users will be able to identify changes in waveform, frequency, and amplitude of tactile outputs generated by the device.
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, “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.
One or more of the embodiments disclosed herein optionally include one or more of the features disclosed in the following patent applications: “User Interfaces For Interacting with Channels that Provide Content that Plays in a Media Browsing Application”, filed Mar. 24, 2019), “User Interfaces For a Media Browsing Application”, filed Mar. 24, 2019), and “User Interface Specific to Respective Content Items”, filed Mar. 24, 2019), each of which is hereby incorporated by reference.
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.
Users interact with electronic devices in many different manners, including using electronic devices in ways that cause the electronic devices to generate outputs (e.g., audio, video, or otherwise). In some circumstances, associating an output device with an electronic device can allow the outputs generated by the electronic device to be produced by the output device (e.g., the output device can be a speaker that produces audio corresponding to audio signals generated by the electronic device and transmitted to the output device). The embodiments described below provide ways in which a second electronic device (e.g., smartphone or other device associated with an output device) facilitates associating an output device with a first electronic device (e.g., set-top box or other device not associated with the output device). Using the second electronic device to facilitate the association of the output device with the first electronic device enhances interactions with the first and second electronic devices, thus reducing the amount of time a user needs to perform operations with the first and/or second electronic devices, and reducing the power usage of the first and second devices, which increases battery life for battery-powered devices. It is understood that people use devices. When a person uses a device, that person is optionally referred to as a user of the device.
In some embodiments, the first electronic device is a set-top box (e.g., device 500 in
User interface 602 is optionally a user interface of the setup process for device 500. User interface 602 optionally includes a first selectable option 620 that initiates the setup process for device 500 during which a second device, such as device 511, will be used to facilitate populating the one or more settings of device 500. User interface 602 optionally also includes a second selectable option 622 that initiates the setup process for device 500 during which the second device is not used to facilitate populating the one or more settings of device 500—in some embodiments, the settings are instead provided manually to device 500 (e.g., using a remote control device, such as device 510 in
In some embodiments, as part of the setup process for device 500, if device 511 is associated with an output device (e.g., a smart speaker, or any other device that is able to generate outputs, such as audio outputs, video outputs, or otherwise), device 500 is able to automatically provide an option to a user of device 500 to associate the output device with device 500 (e.g., in addition to device 511). In this way, the output device can be efficiently associated with device 500 as part of the setup process for device 500. Various examples of the treatment of an output device by device 500 during the setup process for device 500 will now be described.
For example, in
In
In
In various other scenarios, device 500 optionally responds differently than as described with reference to
Device 500 optionally does not display an option to associate an output device with device 500 as part of the setup process of device 500 when device 511 is not associated with an output device. For example, in
As another example, even if an output device is associated with the same location as device 500, device 500 optionally does not display an option to become associated with the output device if that output device is not associated with device 511 (e.g., the device 511 that is in communication with device 500 during the setup process). For example, in
In some embodiments, if multiple output devices have been associated with each other (e.g., as a stereo pair) when the setup process of device 500 occurs, device 500 optionally displays an option to associate the pair (or more) of output devices with device 500. For example, in
In some embodiments, if multiple output devices have been associated with device 511 when the setup process of device 500 occurs, device 500 optionally displays an option to associate a selected one of the output devices with device 500. For example, in
In some embodiments, additionally or alternatively to the embodiments described above with reference to output devices, device 511 is able to operate as a remote control input device to device 500 (e.g., to provide directional inputs to device 500 and/or to provide button-press inputs to device 500, such as the directional and button press inputs described with reference to
In
As described below, the method 700 provides ways in which a second electronic device facilitates associating an output device with a first electronic device. The method reduces the cognitive burden on a user when interacting with a user interface of the device of the disclosure, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, increasing the efficiency of the user's interaction with the user interface conserves power and increases the time between battery charges.
Method 700 is optionally performed at a first electronic device 500 in communication with a display generation component 514 and one or more input devices (e.g., a mobile device (e.g., a tablet, a smartphone, a media player, or a wearable device), or a computer, optionally in communication with one or more of a mouse (e.g., external), trackpad (optionally integrated or external), touchpad (optionally integrated or external), remote control device (e.g., external), another mobile device (e.g., separate from the electronic device), a handheld device (e.g., external), and/or a controller (e.g., external), etc.). In some embodiments, the first electronic device is a set-top box in communication with a television and a remote control device). In some embodiments, the display generation component is a display integrated with the electronic device (optionally a touch screen display), external display such as a monitor, projector, television, or a hardware component (optionally integrated or external) for projecting a user interface or causing a user interface to be visible to one or more users, etc.
In some embodiments, the first electronic device receives (702), via the one or more input devices, an input corresponding to a request to initiate a setup process for the first electronic device, such as selection of option 620 in
In some embodiments, in response to receiving the input corresponding to the request to initiate the setup process for the first electronic device, the first electronic device initiates (704) the setup process for the first electronic device, such as described with reference to
In some embodiments, the setup process includes in accordance with a determination that the one or more criteria are not satisfied, such as device 500 and output device 612a being associated with Rooms 1 and 2, respectively, in
In some embodiments, the setup process includes in accordance with a determination that the respective output device is not associated with the second electronic device, such as output device 612a not being associated with device 511 in
In some embodiments, the one or more criteria include a criterion that is satisfied when the first electronic device and the respective output device are associated with a same location, such as device 500 and output device 612a both being associated with Room 1 in
In some embodiments, before initiating the setup process, the respective output device and a second respective output device were associated with each other as a group of respective output devices (e.g., paired together as a stereo pair of output devices, for example in a smart home configuration associated with the second electronic device), such as devices 612a and 612b in
In some embodiments, before initiating the setup process, the respective output device and a second respective output device were not associated with each other (e.g., not paired together as a stereo pair of output devices, for example in a smart home configuration associated with the second electronic device), such as devices 612a and 612b in
In some embodiments, the setup process includes causing display, on the second electronic device, of a respective selectable option that is selectable to display, on the second electronic device, a user interface for controlling the first electronic device, such as display of option 640 on device 511 in
It should be understood that the particular order in which the operations in
The operations in the information processing methods described above are, optionally, implemented by running one or more functional modules in an information processing apparatus such as general purpose processors (e.g., as described with respect to
Users interact with electronic devices in many different manners, including using electronic devices to access various content, provide various functionality, interact with various devices, etc. In some embodiments, an electronic device can be configured with a first user profile (e.g., values for various settings on the electronic device, such as Wi-Fi settings, content account settings, etc., that correspond to the first user profile) to facilitate the above interactions. In some circumstances, additional user profiles can be added to the electronic device such that the electronic device is able to switch between the different user profiles and provide different sets of functionality based on the different user profiles (e.g., providing access to different sets of content from different content providers based on different content account settings of the currently active user profile(s)). The embodiments described below provide ways in which a second electronic device (e.g., smartphone) can be used to facilitate populating settings on a first electronic device (e.g., set-top box) with values for a new user (e.g., in addition to an existing user) on the first electronic device. Using the second electronic device to facilitate adding new users to the first electronic device enhances interactions with the first and second electronic devices, thus reducing the amount of time a user needs to add an additional user to the first electronic device, and reducing the power usage of the first and second devices, which increases battery life for battery-powered devices. It is understood that people use devices. When a person uses a device, that person is optionally referred to as a user of the device.
As described above, in some embodiments, the first electronic device is a set-top box (e.g., device 500 in
User interface 802 is optionally a user interface of the setup process for device 500 (e.g., as described with reference to
In
Because device 500 optionally has not been configured with a user profile, the next user profile added to device 500 will optionally become the primary and/or default user profile of device 500. Therefore, the setup process initiated from
In
In some embodiments, additional users can be added to device 500. For example, in
In
In response, device 500 optionally displays user interface 832, as shown in
In addition to displaying user interface 832, device 500 optionally transmits an indication to device 511b to cause device 511b to display a user interface element 823 overlaid on whatever user interface device 511b was displaying when device 500 displayed user interface 832. In some embodiments, device 511b displays user interface element 823 without and before either of options 834 or 834 is selected (e.g., with a click on remote 510). User interface element 823 is analogous to user interface element 821 described with reference to
In
If the authentication information (if required) is entered into device 511b correctly in
In
In some embodiments, a second electronic device (e.g., device 511b) facilitates purchase and/or login operations performed at a first electronic device (e.g., device 500). For example, in
In response to the input in
In response to the input in
In
In response to the input in
In
In some embodiments, the processes described with reference to
In response to the input in
In some embodiments, in response to detecting selection of selectable option 898a, and optionally in accordance with successful authentication input detected at device 511b as previously described, device 511b transmits the user account credentials for Content Provider A associated with and/or stored on device 511b to device 500, and device 500 signs into Content Provider A using those account credentials, thus providing access to content from Content Provider A at device 500. In some embodiments, if the authentication input detected at device 511b is not successful, the process to sign into Content Provider A on device 500 is not completed. In some embodiments, in response to detecting selection of selectable option 898b and subsequent manual input of user account credentials at device 511b, device 511b transmits those account credentials to device 500 which signs into Content Provider A using those account credentials, thus providing access to content from Content Provider A at device 500 (assuming those account credentials are valid credentials for Content Provider A).
As described below, the method 900 provides ways in which a second electronic device facilitates adding an additional user to a first electronic device. The method reduces the cognitive burden on a user when interacting with a user interface of the device of the disclosure, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, increasing the efficiency of the user's interaction with the user interface conserves power and increases the time between battery charges.
In some embodiments, method 900 is performed at a first electronic device 500 in communication with a display generation component 514 and one or more input devices (e.g., a mobile device (e.g., a tablet, a smartphone, a media player, or a wearable device), or a computer, optionally in communication with one or more of a mouse (e.g., external), trackpad (optionally integrated or external), touchpad (optionally integrated or external), remote control device (e.g., external), another mobile device (e.g., separate from the electronic device), a handheld device (e.g., external), and/or a controller (e.g., external), etc.). In some embodiments, the first electronic device is a set-top box in communication with a television and a remote control device. In some embodiments, the display generation component is a display integrated with the electronic device (optionally a touch screen display), external display such as a monitor, projector, television, or a hardware component (optionally integrated or external) for projecting a user interface or causing a user interface to be visible to one or more users, etc.
In some embodiments, after (e.g., after or while the first user profile is associated with the first electronic device) a first user profile of a first user has been associated with the first electronic device, such as in
In some embodiments, in response to receiving the input corresponding to the request to associate the additional user with the first electronic device, the first electronic device causes display (904), on a second electronic device, such as device 511b in
In some embodiments, in response to receiving an indication (e.g., from the second electronic device via Bluetooth, Wi-Fi, etc. or via a server or other device with which both the first electronic device and the second electronic are in communication) that the selectable option has been selected (906), such as in
In some embodiments, in response to receiving the indication that the selectable option has been selected, in accordance with a determination that the second electronic device is associated with a third user profile of a third user (e.g., content account information, account login information, user profile information, television provider information, etc. (e.g., settings associated with users as described with reference to method 700) of the third user has been setup on the second electronic device, such that the second electronic device is able to provide access to content associated with one or more content accounts of the third user, different from the first user), the first electronic device initiates a process to associate the third user profile of the third user, different from the first profile and the second profile, with the first electronic device as the additional user associated with the first electronic device, such as if device 511b in
In some embodiments, in response to receiving the input corresponding to the request to associate the additional user with the first electronic device, the first electronic device displays, via the display generation component, a respective user interface, such as user interface 832 in
In some embodiments, associating the first user profile with the first electronic device includes populating (e.g., transferring) a first set of settings of the first electronic device with a first set of values associated with the first user profile, such as the settings values populated for settings 1-3810 in
In some embodiments, associating the second user profile with the first electronic device does not include providing primary content provider settings associated with the second user profile to the first electronic device (e.g., does not include transferring from the second electronic device to the first electronic device the respective settings). For example, the second portion of the first set of settings includes primary content account settings, and those are optionally not populated with values associated with multiple users. In some embodiments, primary content provider settings are optionally only populated with values for the primary user. In some embodiments, the primary content provider settings (e.g., cable provider, satellite provider, internet provider, etc. settings) optionally allow the first electronic device to provide access to content from the primary content provider and/or from secondary content providers associated the primary content provider (e.g., individual content providers/networks to whose content access is provided by virtue of the user's single account with the primary content provider). Therefore, in some embodiments, switching from the first user profile to the second user profile on the first electronic device does not cause the first electronic device to operate according to content provider settings associated with the second user-rather, the first electronic device optionally continues to operate according to the content provider settings associated with the first user. The above-described manner of not populating primary content provider settings for additional users ensures that switching user profiles on the electronic device to the second user profile from the first user profile will not cause a discontinuity in the content provider-related content accessible via the first electronic device, which simplifies the interaction between the user and the electronic device and enhances the operability of the electronic device and makes the user-device interface more efficient, which additionally reduces power usage and improves battery life of the electronic device by enabling the user to use the electronic device more quickly and efficiency while reducing errors in the usage of the device.
In some embodiments, in accordance with a determination that primary content provider settings associated with the first user profile is associated with the first electronic device, associating the second user profile with the first electronic device does not include providing the primary content provider settings associated with the second user profile to the first electronic device, and in accordance with a determination that the primary content provider settings associated with the first user profile is not associated with the first electronic device, associating the second user profile with the first electronic device does not include providing the primary content provider settings associated with the second user profile to the first electronic device. In some embodiments, the primary content provider settings for the second user are not populated in the first electronic device whether or not the first user (e.g., the primary user) has primary content provider settings populated in the first electronic device. In some embodiments, if the first user does not have primary content provider settings populated in the first electronic device, then adding the second user to the first electronic device does populate those primary content provider settings with values corresponding to the second user. The above-described manner of not populating primary content provider settings for additional users ensures that switching user profiles on the electronic device to the second user profile from the first user profile will not cause a discontinuity in the content provider-related content accessible via the first electronic device, which simplifies the interaction between the user and the electronic device and enhances the operability of the electronic device and makes the user-device interface more efficient, which additionally reduces power usage and improves battery life of the electronic device by enabling the user to use the electronic device more quickly and efficiency while reducing errors in the usage of the device.
In some embodiments, the first portion of the first set of settings includes online content account settings for the electronic device, and the second set of values associated with the second user profile includes online content account settings associated with the second user profile. In some embodiments, online content store and/or online content storage settings are populated with values for both the first and the second user, such that switching between the first and second user profiles on the first electronic device does cause the first electronic device to switch between accessing the online content store/storage according to the first user settings and the second user setting when the active profile is switched on the first electronic device. The above-described manner of online content store/storage settings for additional users ensures that switching user profiles on the electronic device to the second user profile from the first user profile will cause corresponding personal content (e.g., content purchases, online content storage data, etc.) access to switch, which simplifies the interaction between the user and the electronic device and enhances the security and privacy of the electronic device and makes the user-device interface more efficient, which additionally reduces power usage and improves battery life of the electronic device by enabling the user to use the electronic device more quickly and efficiency while reducing errors in the usage of the device.
In some embodiments, in response to receiving the input corresponding to the request to associate the additional user with the first electronic device, such as selection of option 834 in
It should be understood that the particular order in which the operations in
The operations in the information processing methods described above are, optionally, implemented by running one or more functional modules in an information processing apparatus such as general purpose processors (e.g., as described with respect to
As described above, one aspect of the present technology includes facilitating output device association with an electronic device and/or facilitating the transfer of user profile information to an electronic device. The present disclosure contemplates that in some instances, the data utilized 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 ID's, 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, user account data can be used to facilitate adding user settings to an electronic device. Accordingly, use of such personal information data enables users to use electronic devices in coordinated manners. 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 network services, 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 enable wireless connection between multiple electronic devices. 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 initiating a data transfer from one electronic device to another electronic device that their personal information data will be accessed and then reminded again just before personal information data is accessed by the device(s).
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, some user profile settings values (e.g., those designated by the user), but not all, can be transferred from one device to another to facilitate adding an additional user to the other device.
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated.
This application claims the benefit of U.S. Provisional Application No. 63/041,981, filed Jun. 21, 2020, and U.S. Provisional Application No. 63/197,472, filed Jun. 6, 2021, the contents of which are incorporated herein by reference in their entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 2718550 | Hoyt et al. | Sep 1955 | A |
| 4672677 | Yamakawa | Jun 1987 | A |
| 5029223 | Fujisaki | Jul 1991 | A |
| 5483261 | Yasutake | Jan 1996 | A |
| 5488204 | Mead et al. | Jan 1996 | A |
| 5585866 | Miller et al. | Dec 1996 | A |
| 5596373 | White et al. | Jan 1997 | A |
| 5621456 | Florin et al. | Apr 1997 | A |
| 5818439 | Nagasaka et al. | Oct 1998 | A |
| 5825352 | Bisset et al. | Oct 1998 | A |
| 5835079 | Shieh | Nov 1998 | A |
| 5880411 | Gillespie et al. | Mar 1999 | A |
| 5886690 | Pond et al. | Mar 1999 | A |
| 5926230 | Niijima et al. | Jul 1999 | A |
| 6021320 | Bickford et al. | Feb 2000 | A |
| 6028600 | Rosin et al. | Feb 2000 | A |
| 6049333 | Lajoie et al. | Apr 2000 | A |
| 6188391 | Seely et al. | Feb 2001 | B1 |
| 6310610 | Beaton et al. | Oct 2001 | B1 |
| 6323846 | Westerman et al. | Nov 2001 | B1 |
| 6405371 | Oosterhout et al. | Jun 2002 | B1 |
| 6487722 | Okura et al. | Nov 2002 | B1 |
| 6570557 | Westerman et al. | May 2003 | B1 |
| 6628304 | Mitchell et al. | Sep 2003 | B2 |
| 6677932 | Westerman | Jan 2004 | B1 |
| 6690387 | Zimmerman et al. | Feb 2004 | B2 |
| 6745391 | Macrae et al. | Jun 2004 | B1 |
| 6909837 | Unger | Jun 2005 | B1 |
| 6928433 | Goodman et al. | Aug 2005 | B2 |
| 7015894 | Morohoshi | Mar 2006 | B2 |
| 7039879 | Bergsten et al. | May 2006 | B2 |
| 7103906 | Katz et al. | Sep 2006 | B1 |
| 7134089 | Celik et al. | Nov 2006 | B2 |
| 7184064 | Zimmerman et al. | Feb 2007 | B2 |
| 7213255 | Markel et al. | May 2007 | B2 |
| 7293275 | Krieger et al. | Nov 2007 | B1 |
| 7330192 | Brunner et al. | Feb 2008 | B2 |
| 7596761 | Lemay et al. | Sep 2009 | B2 |
| 7614008 | Ording | Nov 2009 | B2 |
| 7631278 | Miksovsky et al. | Dec 2009 | B2 |
| 7633076 | Huppi et al. | Dec 2009 | B2 |
| 7636897 | Koralski et al. | Dec 2009 | B2 |
| 7649526 | Ording et al. | Jan 2010 | B2 |
| 7650569 | Allen et al. | Jan 2010 | B1 |
| 7653883 | Hotelling et al. | Jan 2010 | B2 |
| 7657849 | Chaudhri et al. | Feb 2010 | B2 |
| 7663607 | Hotelling et al. | Feb 2010 | B2 |
| 7694231 | Kocienda et al. | Apr 2010 | B2 |
| 7712051 | Chadzelek et al. | May 2010 | B2 |
| 7783892 | Russell et al. | Aug 2010 | B2 |
| 7810043 | Ostojic et al. | Oct 2010 | B2 |
| 7814023 | Rao et al. | Oct 2010 | B1 |
| 7827483 | Unbedacht et al. | Nov 2010 | B2 |
| 7836475 | Angiolillo et al. | Nov 2010 | B2 |
| 7844914 | Andre et al. | Nov 2010 | B2 |
| 7849487 | Vosseller | Dec 2010 | B1 |
| 7856605 | Ording et al. | Dec 2010 | B2 |
| 7917477 | Hutson et al. | Mar 2011 | B2 |
| 7956846 | Ording et al. | Jun 2011 | B2 |
| 7957762 | Herz et al. | Jun 2011 | B2 |
| 7970379 | White et al. | Jun 2011 | B2 |
| 8006002 | Kalayjian et al. | Aug 2011 | B2 |
| 8026805 | Rowe | Sep 2011 | B1 |
| 8082523 | Forstall et al. | Dec 2011 | B2 |
| 8094132 | Frischling et al. | Jan 2012 | B1 |
| 8115731 | Varanda | Feb 2012 | B2 |
| 8145617 | Verstak et al. | Mar 2012 | B1 |
| 8170931 | Ross et al. | May 2012 | B2 |
| 8205240 | Ansari et al. | Jun 2012 | B2 |
| 8239784 | Hotelling et al. | Aug 2012 | B2 |
| 8279180 | Hotelling et al. | Oct 2012 | B2 |
| 8291452 | Yong et al. | Oct 2012 | B1 |
| 8299889 | Kumar et al. | Oct 2012 | B2 |
| 8301484 | Kumar | Oct 2012 | B1 |
| 8312484 | Mccarty et al. | Nov 2012 | B1 |
| 8312486 | Briggs et al. | Nov 2012 | B1 |
| 8325160 | St. Pierre et al. | Dec 2012 | B2 |
| 8346798 | Spiegelman et al. | Jan 2013 | B2 |
| 8370874 | Chang et al. | Feb 2013 | B1 |
| 8381135 | Hotelling et al. | Feb 2013 | B2 |
| 8386588 | Cooley | Feb 2013 | B1 |
| 8407737 | Ellis | Mar 2013 | B1 |
| 8416217 | Eriksson et al. | Apr 2013 | B1 |
| 8418202 | Ahmad-taylor | Apr 2013 | B2 |
| 8424048 | Lyren et al. | Apr 2013 | B1 |
| 8479122 | Hotelling et al. | Jul 2013 | B2 |
| 8495499 | Denise | Jul 2013 | B1 |
| 8516063 | Fletcher | Aug 2013 | B2 |
| 8516525 | Jerding et al. | Aug 2013 | B1 |
| 8560398 | Few et al. | Oct 2013 | B1 |
| 8584165 | Kane et al. | Nov 2013 | B1 |
| 8607163 | Plummer | Dec 2013 | B2 |
| 8613015 | Gordon et al. | Dec 2013 | B2 |
| 8613023 | Narahara et al. | Dec 2013 | B2 |
| 8625974 | Pinson | Jan 2014 | B1 |
| 8674958 | Kravets et al. | Mar 2014 | B1 |
| 8683362 | Shiplacoff et al. | Mar 2014 | B2 |
| 8683517 | Carpenter et al. | Mar 2014 | B2 |
| 8730190 | Moloney | May 2014 | B2 |
| 8742885 | Brodersen et al. | Jun 2014 | B2 |
| 8754862 | Zaliva | Jun 2014 | B2 |
| 8762852 | Davis et al. | Jun 2014 | B2 |
| 8769408 | Madden et al. | Jul 2014 | B2 |
| 8782706 | Ellis | Jul 2014 | B2 |
| 8850471 | Kilar et al. | Sep 2014 | B2 |
| 8850490 | Thomas et al. | Sep 2014 | B1 |
| 8869207 | Earle | Oct 2014 | B1 |
| 8887202 | Hunter et al. | Nov 2014 | B2 |
| 8930839 | He et al. | Jan 2015 | B2 |
| 8952987 | Momeyer et al. | Feb 2015 | B2 |
| 8963847 | Hunt | Feb 2015 | B2 |
| 8983950 | Askey et al. | Mar 2015 | B2 |
| 8988356 | Tseng | Mar 2015 | B2 |
| 8990857 | Yong et al. | Mar 2015 | B2 |
| 9007322 | Young | Apr 2015 | B1 |
| 9066146 | Suh et al. | Jun 2015 | B2 |
| 9081421 | Lai et al. | Jul 2015 | B1 |
| 9092057 | Varela et al. | Jul 2015 | B2 |
| 9116569 | Stacy et al. | Aug 2015 | B2 |
| 9118967 | Sirpal et al. | Aug 2015 | B2 |
| 9129656 | Prather et al. | Sep 2015 | B2 |
| 9141200 | Bernstein et al. | Sep 2015 | B2 |
| 9196309 | Schultz et al. | Nov 2015 | B2 |
| 9214290 | Xie et al. | Dec 2015 | B2 |
| 9215273 | Jonnala et al. | Dec 2015 | B2 |
| 9219634 | Morse et al. | Dec 2015 | B1 |
| 9235317 | Matas et al. | Jan 2016 | B2 |
| 9241121 | Rudolph | Jan 2016 | B2 |
| 9244600 | Mcintosh et al. | Jan 2016 | B2 |
| 9247014 | Rao | Jan 2016 | B1 |
| 9247174 | Sirpal et al. | Jan 2016 | B2 |
| 9285977 | Greenberg et al. | Mar 2016 | B1 |
| 9319727 | Phipps et al. | Apr 2016 | B2 |
| 9348458 | Hotelling et al. | May 2016 | B2 |
| 9357250 | Newman et al. | May 2016 | B1 |
| 9380343 | Webster et al. | Jun 2016 | B2 |
| 9414108 | Sirpal et al. | Aug 2016 | B2 |
| 9454288 | Raffle et al. | Sep 2016 | B2 |
| 9514476 | Kay et al. | Dec 2016 | B2 |
| 9532111 | Christie et al. | Dec 2016 | B1 |
| 9538310 | Fjeldsoe-nielsen et al. | Jan 2017 | B2 |
| 9542060 | Brenner et al. | Jan 2017 | B1 |
| 9560399 | Kaya et al. | Jan 2017 | B2 |
| 9575944 | Neil et al. | Feb 2017 | B2 |
| 9591339 | Christie et al. | Mar 2017 | B1 |
| 9600159 | Lawson et al. | Mar 2017 | B2 |
| 9602566 | Lewis et al. | Mar 2017 | B1 |
| 9639241 | Penha et al. | May 2017 | B2 |
| 9652118 | Hill et al. | May 2017 | B2 |
| 9652448 | Pasquero et al. | May 2017 | B2 |
| 9658740 | Chaudhri | May 2017 | B2 |
| 9774917 | Christie et al. | Sep 2017 | B1 |
| 9792018 | Van Os et al. | Oct 2017 | B2 |
| 9807462 | Wood | Oct 2017 | B2 |
| 9864508 | Dixon et al. | Jan 2018 | B2 |
| 9864509 | Howard et al. | Jan 2018 | B2 |
| 9871905 | Habiger et al. | Jan 2018 | B1 |
| 9913142 | Folse et al. | Mar 2018 | B2 |
| 9933937 | Lemay et al. | Apr 2018 | B2 |
| 9973800 | Yellin et al. | May 2018 | B2 |
| 10019142 | Van Os et al. | Jul 2018 | B2 |
| 10025499 | Howard et al. | Jul 2018 | B2 |
| 10079872 | Thomas et al. | Sep 2018 | B1 |
| 10091558 | Christie et al. | Oct 2018 | B2 |
| 10116996 | Christie et al. | Oct 2018 | B1 |
| 10126904 | Agnetta et al. | Nov 2018 | B2 |
| 10168871 | Wallters et al. | Jan 2019 | B2 |
| 10200761 | Christie et al. | Feb 2019 | B1 |
| 10205985 | Lue-sang et al. | Feb 2019 | B2 |
| 10209866 | Johnston et al. | Feb 2019 | B2 |
| 10237599 | Gravino et al. | Mar 2019 | B1 |
| 10275148 | Matas et al. | Apr 2019 | B2 |
| 10282088 | Kim et al. | May 2019 | B2 |
| 10303422 | Woo | May 2019 | B1 |
| 10405015 | Kite et al. | Sep 2019 | B2 |
| 10521188 | Christie et al. | Dec 2019 | B1 |
| 10551995 | Ho et al. | Feb 2020 | B1 |
| 10552470 | Todd et al. | Feb 2020 | B2 |
| 10564823 | Dennis et al. | Feb 2020 | B1 |
| 10601808 | Nijim et al. | Mar 2020 | B1 |
| 10606539 | Bernstein et al. | Mar 2020 | B2 |
| 10631042 | Zerr | Apr 2020 | B2 |
| 10795490 | Chaudhri et al. | Oct 2020 | B2 |
| 10827007 | Kode | Nov 2020 | B2 |
| 11062358 | Lewis et al. | Jul 2021 | B1 |
| 20020015024 | Westerman et al. | Feb 2002 | A1 |
| 20020026637 | Markel et al. | Feb 2002 | A1 |
| 20020042920 | Thomas et al. | Apr 2002 | A1 |
| 20020060750 | Istvan et al. | May 2002 | A1 |
| 20020085045 | Vong et al. | Jul 2002 | A1 |
| 20020100063 | Herigstad et al. | Jul 2002 | A1 |
| 20020112239 | Goldman | Aug 2002 | A1 |
| 20020113816 | Mitchell et al. | Aug 2002 | A1 |
| 20020144269 | Connelly | Oct 2002 | A1 |
| 20020171686 | Kamen et al. | Nov 2002 | A1 |
| 20030001907 | Bergsten et al. | Jan 2003 | A1 |
| 20030005445 | Schein et al. | Jan 2003 | A1 |
| 20030009757 | Kikinis | Jan 2003 | A1 |
| 20030011641 | Totman et al. | Jan 2003 | A1 |
| 20030013483 | Ausems et al. | Jan 2003 | A1 |
| 20030088872 | Maissel et al. | May 2003 | A1 |
| 20030093790 | Logan et al. | May 2003 | A1 |
| 20030126600 | Heuvelman | Jul 2003 | A1 |
| 20030149628 | Abbosh et al. | Aug 2003 | A1 |
| 20030158950 | Sako | Aug 2003 | A1 |
| 20030167471 | Roth et al. | Sep 2003 | A1 |
| 20030177075 | Burke | Sep 2003 | A1 |
| 20030177498 | Ellis et al. | Sep 2003 | A1 |
| 20030192060 | Levy | Oct 2003 | A1 |
| 20030221191 | Khusheim | Nov 2003 | A1 |
| 20030228130 | Tanikawa et al. | Dec 2003 | A1 |
| 20030234804 | Parker et al. | Dec 2003 | A1 |
| 20040019497 | Volk et al. | Jan 2004 | A1 |
| 20040046801 | Lin et al. | Mar 2004 | A1 |
| 20040070573 | Graham | Apr 2004 | A1 |
| 20040088328 | Cook et al. | May 2004 | A1 |
| 20040090463 | Celik et al. | May 2004 | A1 |
| 20040133909 | Ma | Jul 2004 | A1 |
| 20040139401 | Unbedacht et al. | Jul 2004 | A1 |
| 20040161151 | Iwayama et al. | Aug 2004 | A1 |
| 20040168184 | Steenkamp et al. | Aug 2004 | A1 |
| 20040193421 | Blass | Sep 2004 | A1 |
| 20040252120 | Hunleth et al. | Dec 2004 | A1 |
| 20040254883 | Kondrk et al. | Dec 2004 | A1 |
| 20040254958 | Volk | Dec 2004 | A1 |
| 20040267715 | Polson et al. | Dec 2004 | A1 |
| 20050012599 | Dematteo | Jan 2005 | A1 |
| 20050071761 | Kontio | Mar 2005 | A1 |
| 20050071785 | Chadzelek et al. | Mar 2005 | A1 |
| 20050076363 | Dukes et al. | Apr 2005 | A1 |
| 20050091254 | Stabb et al. | Apr 2005 | A1 |
| 20050091597 | Ackley | Apr 2005 | A1 |
| 20050162398 | Eliasson et al. | Jul 2005 | A1 |
| 20050162402 | Watanachote | Jul 2005 | A1 |
| 20050186988 | Lim et al. | Aug 2005 | A1 |
| 20050190059 | Wehrenberg | Sep 2005 | A1 |
| 20050223335 | Ichikawa | Oct 2005 | A1 |
| 20050235316 | Ahmad-taylor | Oct 2005 | A1 |
| 20050257166 | Tu | Nov 2005 | A1 |
| 20050283358 | Stephanick et al. | Dec 2005 | A1 |
| 20060017692 | Wehrenberg et al. | Jan 2006 | A1 |
| 20060020904 | Aaltonen et al. | Jan 2006 | A1 |
| 20060026521 | Hotelling et al. | Feb 2006 | A1 |
| 20060029374 | Park | Feb 2006 | A1 |
| 20060031872 | Hsiao et al. | Feb 2006 | A1 |
| 20060033724 | Chaudhri et al. | Feb 2006 | A1 |
| 20060053449 | Gutta | Mar 2006 | A1 |
| 20060069998 | Artman et al. | Mar 2006 | A1 |
| 20060071905 | Varanda | Apr 2006 | A1 |
| 20060080352 | Boubez et al. | Apr 2006 | A1 |
| 20060097991 | Hotelling et al. | May 2006 | A1 |
| 20060107304 | Cleron et al. | May 2006 | A1 |
| 20060112346 | Miksovsky et al. | May 2006 | A1 |
| 20060112352 | Tseng et al. | May 2006 | A1 |
| 20060117267 | Koralski et al. | Jun 2006 | A1 |
| 20060120624 | Jojic et al. | Jun 2006 | A1 |
| 20060195479 | Spiegelman et al. | Aug 2006 | A1 |
| 20060195512 | Rogers et al. | Aug 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060224987 | Caffarelli | Oct 2006 | A1 |
| 20060248113 | Leffert et al. | Nov 2006 | A1 |
| 20060265637 | Marriott et al. | Nov 2006 | A1 |
| 20060271968 | Zellner | Nov 2006 | A1 |
| 20060282856 | Errico et al. | Dec 2006 | A1 |
| 20060294545 | Morris et al. | Dec 2006 | A1 |
| 20070005569 | Hurst-hiller et al. | Jan 2007 | A1 |
| 20070009229 | Liu | Jan 2007 | A1 |
| 20070011702 | Vaysman | Jan 2007 | A1 |
| 20070028267 | Ostojic et al. | Feb 2007 | A1 |
| 20070038957 | White | Feb 2007 | A1 |
| 20070073596 | Alexander et al. | Mar 2007 | A1 |
| 20070092204 | Wagner et al. | Apr 2007 | A1 |
| 20070150802 | Wan et al. | Jun 2007 | A1 |
| 20070154163 | Cordray | Jul 2007 | A1 |
| 20070157220 | Cordray et al. | Jul 2007 | A1 |
| 20070157249 | Cordray et al. | Jul 2007 | A1 |
| 20070168413 | Barletta et al. | Jul 2007 | A1 |
| 20070186254 | Tsutsui et al. | Aug 2007 | A1 |
| 20070199035 | Schwartz et al. | Aug 2007 | A1 |
| 20070204057 | Shaver et al. | Aug 2007 | A1 |
| 20070229465 | Sakai et al. | Oct 2007 | A1 |
| 20070233880 | Nieh et al. | Oct 2007 | A1 |
| 20070244902 | Seide et al. | Oct 2007 | A1 |
| 20070248317 | Bahn | Oct 2007 | A1 |
| 20080046928 | Poling et al. | Feb 2008 | A1 |
| 20080059884 | Ellis et al. | Mar 2008 | A1 |
| 20080065989 | Conroy et al. | Mar 2008 | A1 |
| 20080066010 | Brodersen et al. | Mar 2008 | A1 |
| 20080077562 | Schleppe | Mar 2008 | A1 |
| 20080092168 | Logan et al. | Apr 2008 | A1 |
| 20080092173 | Shannon et al. | Apr 2008 | A1 |
| 20080111822 | Horowitz et al. | May 2008 | A1 |
| 20080120668 | Yau | May 2008 | A1 |
| 20080127281 | Van et al. | May 2008 | A1 |
| 20080155475 | Duhig | Jun 2008 | A1 |
| 20080189740 | Carpenter et al. | Aug 2008 | A1 |
| 20080189742 | Ellis et al. | Aug 2008 | A1 |
| 20080216020 | Plummer | Sep 2008 | A1 |
| 20080222677 | Woo et al. | Sep 2008 | A1 |
| 20080235588 | Gonze et al. | Sep 2008 | A1 |
| 20080243817 | Chan et al. | Oct 2008 | A1 |
| 20080250312 | Curtis | Oct 2008 | A1 |
| 20080260252 | Borgaonkar et al. | Oct 2008 | A1 |
| 20080270886 | Gossweiler et al. | Oct 2008 | A1 |
| 20080276279 | Gossweiler et al. | Nov 2008 | A1 |
| 20080301260 | Goldeen et al. | Dec 2008 | A1 |
| 20080301579 | Jonasson et al. | Dec 2008 | A1 |
| 20080301734 | Goldeen et al. | Dec 2008 | A1 |
| 20080307343 | Robert et al. | Dec 2008 | A1 |
| 20080307458 | Kim et al. | Dec 2008 | A1 |
| 20080307459 | Migos | Dec 2008 | A1 |
| 20080320391 | Lemay et al. | Dec 2008 | A1 |
| 20080320532 | Lee | Dec 2008 | A1 |
| 20090055385 | Jeon et al. | Feb 2009 | A1 |
| 20090063521 | Bull et al. | Mar 2009 | A1 |
| 20090063975 | Rottler et al. | Mar 2009 | A1 |
| 20090089837 | Momosaki | Apr 2009 | A1 |
| 20090094662 | Chang et al. | Apr 2009 | A1 |
| 20090119754 | Schubert | May 2009 | A1 |
| 20090158325 | Johnson | Jun 2009 | A1 |
| 20090158326 | Hunt et al. | Jun 2009 | A1 |
| 20090161868 | Chaudhry | Jun 2009 | A1 |
| 20090164944 | Webster et al. | Jun 2009 | A1 |
| 20090165054 | Rudolph | Jun 2009 | A1 |
| 20090174679 | Westerman | Jul 2009 | A1 |
| 20090177301 | Hayes | Jul 2009 | A1 |
| 20090177989 | Ma et al. | Jul 2009 | A1 |
| 20090178083 | Carr et al. | Jul 2009 | A1 |
| 20090228491 | Malik | Sep 2009 | A1 |
| 20090239587 | Negron et al. | Sep 2009 | A1 |
| 20090256807 | Nurmi | Oct 2009 | A1 |
| 20090259957 | Slocum et al. | Oct 2009 | A1 |
| 20090278916 | Ito | Nov 2009 | A1 |
| 20090282444 | Laksono et al. | Nov 2009 | A1 |
| 20090288079 | Zuber et al. | Nov 2009 | A1 |
| 20090313100 | Ingleshwar | Dec 2009 | A1 |
| 20090322962 | Weeks | Dec 2009 | A1 |
| 20090327952 | Karas et al. | Dec 2009 | A1 |
| 20100009629 | Jung et al. | Jan 2010 | A1 |
| 20100031162 | Wiser et al. | Feb 2010 | A1 |
| 20100053220 | Ozawa et al. | Mar 2010 | A1 |
| 20100053432 | Cheng et al. | Mar 2010 | A1 |
| 20100057696 | Miyazawa et al. | Mar 2010 | A1 |
| 20100064313 | Beyabani | Mar 2010 | A1 |
| 20100080163 | Krishnamoorthi et al. | Apr 2010 | A1 |
| 20100083181 | Matsushima et al. | Apr 2010 | A1 |
| 20100095240 | Shiplacoff et al. | Apr 2010 | A1 |
| 20100100899 | Bradbury et al. | Apr 2010 | A1 |
| 20100104269 | Prestenback et al. | Apr 2010 | A1 |
| 20100115592 | Belz et al. | May 2010 | A1 |
| 20100121714 | Bryant et al. | May 2010 | A1 |
| 20100146442 | Nagasaka et al. | Jun 2010 | A1 |
| 20100153881 | Dinn | Jun 2010 | A1 |
| 20100153999 | Yates | Jun 2010 | A1 |
| 20100159898 | Krzyzanowski et al. | Jun 2010 | A1 |
| 20100162172 | Aroner | Jun 2010 | A1 |
| 20100194998 | Lee et al. | Aug 2010 | A1 |
| 20100198822 | Glennon et al. | Aug 2010 | A1 |
| 20100205628 | Davis et al. | Aug 2010 | A1 |
| 20100211636 | Starkenburg et al. | Aug 2010 | A1 |
| 20100223646 | Goldeen et al. | Sep 2010 | A1 |
| 20100229194 | Blanchard et al. | Sep 2010 | A1 |
| 20100235744 | Schultz et al. | Sep 2010 | A1 |
| 20100251304 | Donoghue et al. | Sep 2010 | A1 |
| 20100257005 | Phenner et al. | Oct 2010 | A1 |
| 20100269145 | Ingrassia et al. | Oct 2010 | A1 |
| 20100275143 | Fu et al. | Oct 2010 | A1 |
| 20100277337 | Brodersen et al. | Nov 2010 | A1 |
| 20100293190 | Kaiser et al. | Nov 2010 | A1 |
| 20100293586 | Simoes et al. | Nov 2010 | A1 |
| 20100312824 | Smith et al. | Dec 2010 | A1 |
| 20100325660 | Holden | Dec 2010 | A1 |
| 20100333142 | Busse et al. | Dec 2010 | A1 |
| 20100333143 | Civanlar et al. | Dec 2010 | A1 |
| 20110004831 | Steinberg et al. | Jan 2011 | A1 |
| 20110047513 | Onogi et al. | Feb 2011 | A1 |
| 20110052146 | Murthy et al. | Mar 2011 | A1 |
| 20110054649 | Sarkis et al. | Mar 2011 | A1 |
| 20110055762 | Jung et al. | Mar 2011 | A1 |
| 20110055870 | Yum et al. | Mar 2011 | A1 |
| 20110071977 | Nakajima et al. | Mar 2011 | A1 |
| 20110078739 | Grad | Mar 2011 | A1 |
| 20110080935 | Kim et al. | Apr 2011 | A1 |
| 20110087992 | Wang et al. | Apr 2011 | A1 |
| 20110090402 | Huntington et al. | Apr 2011 | A1 |
| 20110093415 | Rhee et al. | Apr 2011 | A1 |
| 20110119715 | Chang et al. | May 2011 | A1 |
| 20110131607 | Thomas et al. | Jun 2011 | A1 |
| 20110154194 | Mathai et al. | Jun 2011 | A1 |
| 20110154305 | Leroux et al. | Jun 2011 | A1 |
| 20110157029 | Tseng | Jun 2011 | A1 |
| 20110162022 | Xia | Jun 2011 | A1 |
| 20110163971 | Wagner et al. | Jul 2011 | A1 |
| 20110167339 | Emay | Jul 2011 | A1 |
| 20110175930 | Hwang et al. | Jul 2011 | A1 |
| 20110179388 | Fleizach et al. | Jul 2011 | A1 |
| 20110179453 | Poniatowski | Jul 2011 | A1 |
| 20110197153 | King et al. | Aug 2011 | A1 |
| 20110209177 | Sela et al. | Aug 2011 | A1 |
| 20110218948 | De et al. | Sep 2011 | A1 |
| 20110231280 | Farah | Sep 2011 | A1 |
| 20110231823 | Fryc et al. | Sep 2011 | A1 |
| 20110231872 | Gharachorloo et al. | Sep 2011 | A1 |
| 20110231878 | Hunter et al. | Sep 2011 | A1 |
| 20110246332 | Alcodray et al. | Oct 2011 | A1 |
| 20110281517 | Ukkadam | Nov 2011 | A1 |
| 20110283304 | Roberts et al. | Nov 2011 | A1 |
| 20110283333 | Ukkadam | Nov 2011 | A1 |
| 20110289064 | Lebeau et al. | Nov 2011 | A1 |
| 20110289317 | Darapu et al. | Nov 2011 | A1 |
| 20110289419 | Yu et al. | Nov 2011 | A1 |
| 20110289421 | Jordan et al. | Nov 2011 | A1 |
| 20110289452 | Jordan et al. | Nov 2011 | A1 |
| 20110289531 | Moonka et al. | Nov 2011 | A1 |
| 20110289534 | Jordan et al. | Nov 2011 | A1 |
| 20110296351 | Ewing et al. | Dec 2011 | A1 |
| 20110302532 | Missig | Dec 2011 | A1 |
| 20110307631 | Park et al. | Dec 2011 | A1 |
| 20110312278 | Matsushita et al. | Dec 2011 | A1 |
| 20110321072 | Patterson et al. | Dec 2011 | A1 |
| 20120019674 | Ohnishi et al. | Jan 2012 | A1 |
| 20120036552 | Dare et al. | Feb 2012 | A1 |
| 20120042245 | Askey et al. | Feb 2012 | A1 |
| 20120042343 | Laligand et al. | Feb 2012 | A1 |
| 20120053887 | Nurmi | Mar 2012 | A1 |
| 20120054178 | Tran et al. | Mar 2012 | A1 |
| 20120054642 | Balsiger et al. | Mar 2012 | A1 |
| 20120054797 | Skog et al. | Mar 2012 | A1 |
| 20120059910 | Cassidy | Mar 2012 | A1 |
| 20120060092 | Hill et al. | Mar 2012 | A1 |
| 20120064204 | Davila et al. | Mar 2012 | A1 |
| 20120084136 | Seth et al. | Apr 2012 | A1 |
| 20120093481 | Mcdowell et al. | Apr 2012 | A1 |
| 20120096011 | Kay et al. | Apr 2012 | A1 |
| 20120102573 | Spooner et al. | Apr 2012 | A1 |
| 20120105367 | Son et al. | May 2012 | A1 |
| 20120110616 | Kilar et al. | May 2012 | A1 |
| 20120110621 | Gossweiler | May 2012 | A1 |
| 20120114303 | Chung et al. | May 2012 | A1 |
| 20120117584 | Gordon | May 2012 | A1 |
| 20120139938 | Khedouri et al. | Jun 2012 | A1 |
| 20120144003 | Rosenbaum et al. | Jun 2012 | A1 |
| 20120158524 | Hintz et al. | Jun 2012 | A1 |
| 20120173991 | Roberts et al. | Jul 2012 | A1 |
| 20120174157 | Stinson et al. | Jul 2012 | A1 |
| 20120198020 | Parker et al. | Aug 2012 | A1 |
| 20120198336 | Novotny et al. | Aug 2012 | A1 |
| 20120210366 | Wong et al. | Aug 2012 | A1 |
| 20120215684 | Kidron | Aug 2012 | A1 |
| 20120216113 | Li | Aug 2012 | A1 |
| 20120216117 | Arriola et al. | Aug 2012 | A1 |
| 20120216296 | Kidron | Aug 2012 | A1 |
| 20120221498 | Kaszynski et al. | Aug 2012 | A1 |
| 20120222056 | Donoghue et al. | Aug 2012 | A1 |
| 20120233640 | Odryna et al. | Sep 2012 | A1 |
| 20120242704 | Bamford et al. | Sep 2012 | A1 |
| 20120260291 | Wood | Oct 2012 | A1 |
| 20120260293 | Young et al. | Oct 2012 | A1 |
| 20120262371 | Lee et al. | Oct 2012 | A1 |
| 20120262407 | Hinckley et al. | Oct 2012 | A1 |
| 20120266069 | Moshiri et al. | Oct 2012 | A1 |
| 20120272261 | Reynolds et al. | Oct 2012 | A1 |
| 20120284753 | Roberts et al. | Nov 2012 | A1 |
| 20120290933 | Rajaraman et al. | Nov 2012 | A1 |
| 20120291079 | Gordon et al. | Nov 2012 | A1 |
| 20120308143 | Bellegarda et al. | Dec 2012 | A1 |
| 20120311443 | Chaudhri et al. | Dec 2012 | A1 |
| 20120311638 | Reyna et al. | Dec 2012 | A1 |
| 20120317482 | Barraclough et al. | Dec 2012 | A1 |
| 20120323938 | Skeen et al. | Dec 2012 | A1 |
| 20120324504 | Archer et al. | Dec 2012 | A1 |
| 20120327125 | Kutliroff et al. | Dec 2012 | A1 |
| 20130014150 | Seo et al. | Jan 2013 | A1 |
| 20130014159 | Wiser et al. | Jan 2013 | A1 |
| 20130021288 | Kaerkkaeinen et al. | Jan 2013 | A1 |
| 20130024895 | Yong et al. | Jan 2013 | A1 |
| 20130031585 | Itagaki et al. | Jan 2013 | A1 |
| 20130033643 | Kim et al. | Feb 2013 | A1 |
| 20130042271 | Yellin et al. | Feb 2013 | A1 |
| 20130061234 | Piira et al. | Mar 2013 | A1 |
| 20130061267 | Cansino et al. | Mar 2013 | A1 |
| 20130067366 | Almosnino | Mar 2013 | A1 |
| 20130073403 | Tuchman et al. | Mar 2013 | A1 |
| 20130083076 | Liu et al. | Apr 2013 | A1 |
| 20130097009 | Akadiri | Apr 2013 | A1 |
| 20130110978 | Gordon et al. | May 2013 | A1 |
| 20130124998 | Pendergast et al. | May 2013 | A1 |
| 20130132874 | He et al. | May 2013 | A1 |
| 20130132966 | Chanda et al. | May 2013 | A1 |
| 20130151300 | Le et al. | Jun 2013 | A1 |
| 20130173034 | Reimann et al. | Jul 2013 | A1 |
| 20130174193 | Yu et al. | Jul 2013 | A1 |
| 20130179812 | Bianrosa et al. | Jul 2013 | A1 |
| 20130179995 | Basile et al. | Jul 2013 | A1 |
| 20130198686 | Kawai et al. | Aug 2013 | A1 |
| 20130205312 | Huang | Aug 2013 | A1 |
| 20130212531 | Yoshida | Aug 2013 | A1 |
| 20130227482 | Thorsander et al. | Aug 2013 | A1 |
| 20130247105 | Jovanovski et al. | Sep 2013 | A1 |
| 20130262431 | Garner et al. | Oct 2013 | A1 |
| 20130262558 | Wood et al. | Oct 2013 | A1 |
| 20130262619 | Goodwin et al. | Oct 2013 | A1 |
| 20130262633 | Goodwin et al. | Oct 2013 | A1 |
| 20130263189 | Garner | Oct 2013 | A1 |
| 20130283154 | Sasakura | Oct 2013 | A1 |
| 20130283168 | Brown et al. | Oct 2013 | A1 |
| 20130283317 | Guntupalli et al. | Oct 2013 | A1 |
| 20130283318 | Wannamaker | Oct 2013 | A1 |
| 20130285937 | Billings et al. | Oct 2013 | A1 |
| 20130290233 | Ferren et al. | Oct 2013 | A1 |
| 20130290848 | Billings et al. | Oct 2013 | A1 |
| 20130291018 | Billings et al. | Oct 2013 | A1 |
| 20130291037 | Im et al. | Oct 2013 | A1 |
| 20130294755 | Arme et al. | Nov 2013 | A1 |
| 20130312044 | Itagaki | Nov 2013 | A1 |
| 20130326499 | Mowatt et al. | Dec 2013 | A1 |
| 20130326554 | Shkedi | Dec 2013 | A1 |
| 20130326561 | Pandey | Dec 2013 | A1 |
| 20130332838 | Naggar et al. | Dec 2013 | A1 |
| 20130332960 | Young et al. | Dec 2013 | A1 |
| 20130340006 | Kwan | Dec 2013 | A1 |
| 20130346564 | Warrick | Dec 2013 | A1 |
| 20130347044 | Lee et al. | Dec 2013 | A1 |
| 20140006635 | Braness et al. | Jan 2014 | A1 |
| 20140006795 | Han et al. | Jan 2014 | A1 |
| 20140006951 | Hunter | Jan 2014 | A1 |
| 20140012859 | Heilprin et al. | Jan 2014 | A1 |
| 20140013283 | Matas et al. | Jan 2014 | A1 |
| 20140020017 | Stern et al. | Jan 2014 | A1 |
| 20140024341 | Johan | Jan 2014 | A1 |
| 20140033245 | Barton et al. | Jan 2014 | A1 |
| 20140049692 | Sirpal et al. | Feb 2014 | A1 |
| 20140052683 | Kirkham et al. | Feb 2014 | A1 |
| 20140053116 | Smith et al. | Feb 2014 | A1 |
| 20140053195 | Sirpal et al. | Feb 2014 | A1 |
| 20140059605 | Sirpal et al. | Feb 2014 | A1 |
| 20140059615 | Sirpal et al. | Feb 2014 | A1 |
| 20140059625 | Dourado et al. | Feb 2014 | A1 |
| 20140059635 | Sirpal et al. | Feb 2014 | A1 |
| 20140068654 | Marlow et al. | Mar 2014 | A1 |
| 20140071068 | Shih et al. | Mar 2014 | A1 |
| 20140074454 | Brown et al. | Mar 2014 | A1 |
| 20140075313 | Bachman et al. | Mar 2014 | A1 |
| 20140075316 | Li | Mar 2014 | A1 |
| 20140075394 | Nawle et al. | Mar 2014 | A1 |
| 20140075574 | Zheng et al. | Mar 2014 | A1 |
| 20140082497 | Chalouhi et al. | Mar 2014 | A1 |
| 20140088952 | Fife et al. | Mar 2014 | A1 |
| 20140089816 | Dipersia et al. | Mar 2014 | A1 |
| 20140098102 | Raffle et al. | Apr 2014 | A1 |
| 20140104646 | Nishiyama | Apr 2014 | A1 |
| 20140109204 | Papillon et al. | Apr 2014 | A1 |
| 20140111416 | Sugiura | Apr 2014 | A1 |
| 20140115636 | Stuckman | Apr 2014 | A1 |
| 20140123006 | Chen et al. | May 2014 | A1 |
| 20140129232 | Jones et al. | May 2014 | A1 |
| 20140130097 | Londero | May 2014 | A1 |
| 20140136946 | Matas | May 2014 | A1 |
| 20140137029 | Stephenson et al. | May 2014 | A1 |
| 20140137030 | Matas | May 2014 | A1 |
| 20140143260 | Simonson et al. | May 2014 | A1 |
| 20140143683 | Underwood et al. | May 2014 | A1 |
| 20140156792 | Roberts et al. | Jun 2014 | A1 |
| 20140157204 | Roberts et al. | Jun 2014 | A1 |
| 20140157329 | Roberts et al. | Jun 2014 | A1 |
| 20140164966 | Kim et al. | Jun 2014 | A1 |
| 20140168071 | Ahmed et al. | Jun 2014 | A1 |
| 20140171153 | Kienzle et al. | Jun 2014 | A1 |
| 20140172622 | Baronshin | Jun 2014 | A1 |
| 20140172953 | Blanksteen | Jun 2014 | A1 |
| 20140173660 | Correa et al. | Jun 2014 | A1 |
| 20140184471 | Martynov et al. | Jul 2014 | A1 |
| 20140189523 | Shuttleworth et al. | Jul 2014 | A1 |
| 20140189574 | Stallings et al. | Jul 2014 | A1 |
| 20140189606 | Shuttleworth et al. | Jul 2014 | A1 |
| 20140196064 | Kennedy et al. | Jul 2014 | A1 |
| 20140196069 | Ahmed et al. | Jul 2014 | A1 |
| 20140208268 | Jimenez | Jul 2014 | A1 |
| 20140208360 | Kardatzke | Jul 2014 | A1 |
| 20140219637 | Mcintosh et al. | Aug 2014 | A1 |
| 20140224867 | Werner et al. | Aug 2014 | A1 |
| 20140244751 | Tseng | Aug 2014 | A1 |
| 20140245148 | Silva et al. | Aug 2014 | A1 |
| 20140245186 | Tseng | Aug 2014 | A1 |
| 20140245222 | Kovacevic et al. | Aug 2014 | A1 |
| 20140250465 | Mulholland et al. | Sep 2014 | A1 |
| 20140250479 | Lee et al. | Sep 2014 | A1 |
| 20140253463 | Hicks | Sep 2014 | A1 |
| 20140259074 | Ansari et al. | Sep 2014 | A1 |
| 20140278072 | Fino et al. | Sep 2014 | A1 |
| 20140278940 | Wade | Sep 2014 | A1 |
| 20140282208 | Chaudhri | Sep 2014 | A1 |
| 20140282636 | Petander et al. | Sep 2014 | A1 |
| 20140282677 | Mantell et al. | Sep 2014 | A1 |
| 20140289226 | English et al. | Sep 2014 | A1 |
| 20140289751 | Hsu et al. | Sep 2014 | A1 |
| 20140310742 | Kim | Oct 2014 | A1 |
| 20140317653 | Mlodzinski | Oct 2014 | A1 |
| 20140333530 | Agnetta et al. | Nov 2014 | A1 |
| 20140337607 | Peterson et al. | Nov 2014 | A1 |
| 20140340358 | Martinoli | Nov 2014 | A1 |
| 20140341109 | Cartmell et al. | Nov 2014 | A1 |
| 20140344247 | Procopio et al. | Nov 2014 | A1 |
| 20140344291 | Simonson et al. | Nov 2014 | A9 |
| 20140344294 | Skeen et al. | Nov 2014 | A1 |
| 20140351691 | Neil et al. | Nov 2014 | A1 |
| 20140359598 | Oliver et al. | Dec 2014 | A1 |
| 20140365479 | Lyons et al. | Dec 2014 | A1 |
| 20140365481 | Novosel et al. | Dec 2014 | A1 |
| 20140365604 | Lewis et al. | Dec 2014 | A1 |
| 20140365919 | Shaw et al. | Dec 2014 | A1 |
| 20140366040 | Parker et al. | Dec 2014 | A1 |
| 20140366047 | Thomas et al. | Dec 2014 | A1 |
| 20150020127 | Doshi et al. | Jan 2015 | A1 |
| 20150039685 | Lewis et al. | Feb 2015 | A1 |
| 20150046866 | Shimadate | Feb 2015 | A1 |
| 20150067582 | Donnelly et al. | Mar 2015 | A1 |
| 20150067724 | Johnson et al. | Mar 2015 | A1 |
| 20150074552 | Chai et al. | Mar 2015 | A1 |
| 20150074603 | Abe et al. | Mar 2015 | A1 |
| 20150082187 | Wallters et al. | Mar 2015 | A1 |
| 20150095460 | Berger et al. | Apr 2015 | A1 |
| 20150095845 | Chun et al. | Apr 2015 | A1 |
| 20150113429 | Edwards et al. | Apr 2015 | A1 |
| 20150121408 | Jacoby et al. | Apr 2015 | A1 |
| 20150134653 | Bayer et al. | May 2015 | A1 |
| 20150150049 | White | May 2015 | A1 |
| 20150150066 | Park et al. | May 2015 | A1 |
| 20150153571 | Ballard et al. | Jun 2015 | A1 |
| 20150161251 | Ramanarayanan et al. | Jun 2015 | A1 |
| 20150169705 | Korbecki et al. | Jun 2015 | A1 |
| 20150169975 | Kienzle et al. | Jun 2015 | A1 |
| 20150186002 | Suzuki et al. | Jul 2015 | A1 |
| 20150189347 | Oztaskent et al. | Jul 2015 | A1 |
| 20150195624 | Gossweiler, III | Jul 2015 | A1 |
| 20150205591 | Jitkoff et al. | Jul 2015 | A1 |
| 20150237389 | Grouf et al. | Aug 2015 | A1 |
| 20150296072 | Zhou et al. | Oct 2015 | A1 |
| 20150301729 | Wang et al. | Oct 2015 | A1 |
| 20150309670 | Wheeler et al. | Oct 2015 | A1 |
| 20150312603 | Singh et al. | Oct 2015 | A1 |
| 20150317343 | Cselle et al. | Nov 2015 | A1 |
| 20150334464 | Shin | Nov 2015 | A1 |
| 20150346975 | Lee et al. | Dec 2015 | A1 |
| 20150350741 | Rajaraman et al. | Dec 2015 | A1 |
| 20150355816 | Shim | Dec 2015 | A1 |
| 20150363035 | Hinckley et al. | Dec 2015 | A1 |
| 20150365729 | Kaya et al. | Dec 2015 | A1 |
| 20150370435 | Kirmse et al. | Dec 2015 | A1 |
| 20150370455 | Van Os et al. | Dec 2015 | A1 |
| 20150370920 | Van Os et al. | Dec 2015 | A1 |
| 20150373107 | Chan et al. | Dec 2015 | A1 |
| 20150382047 | Van Os et al. | Dec 2015 | A1 |
| 20150382066 | Heeter et al. | Dec 2015 | A1 |
| 20160004425 | Yoon et al. | Jan 2016 | A1 |
| 20160004772 | Kim et al. | Jan 2016 | A1 |
| 20160004773 | Jannink et al. | Jan 2016 | A1 |
| 20160005013 | Perry | Jan 2016 | A1 |
| 20160014461 | Leech et al. | Jan 2016 | A1 |
| 20160021412 | Zito, Jr. | Jan 2016 | A1 |
| 20160035119 | Lee et al. | Feb 2016 | A1 |
| 20160036897 | Kim et al. | Feb 2016 | A1 |
| 20160041702 | Wang | Feb 2016 | A1 |
| 20160043962 | Kim | Feb 2016 | A1 |
| 20160066004 | Lieu et al. | Mar 2016 | A1 |
| 20160066021 | Thomas et al. | Mar 2016 | A1 |
| 20160066040 | Webster et al. | Mar 2016 | A1 |
| 20160066049 | Mountain | Mar 2016 | A1 |
| 20160078526 | Nations et al. | Mar 2016 | A1 |
| 20160080815 | Ruffini et al. | Mar 2016 | A1 |
| 20160092042 | Yenigalla et al. | Mar 2016 | A1 |
| 20160092559 | Lind et al. | Mar 2016 | A1 |
| 20160096113 | Decoufle | Apr 2016 | A1 |
| 20160099991 | Lonkar et al. | Apr 2016 | A1 |
| 20160105540 | Kwon et al. | Apr 2016 | A1 |
| 20160110064 | Shapira | Apr 2016 | A1 |
| 20160127783 | Garcia Navarro | May 2016 | A1 |
| 20160127789 | Roberts et al. | May 2016 | A1 |
| 20160133230 | Daniels et al. | May 2016 | A1 |
| 20160142783 | Bagga et al. | May 2016 | A1 |
| 20160165307 | Lavender et al. | Jun 2016 | A1 |
| 20160188902 | Jin | Jun 2016 | A1 |
| 20160191639 | Dai et al. | Jun 2016 | A1 |
| 20160192017 | Tirpak | Jun 2016 | A1 |
| 20160231885 | Lee et al. | Aug 2016 | A1 |
| 20160249105 | Carney Landow | Aug 2016 | A1 |
| 20160255379 | Langan et al. | Sep 2016 | A1 |
| 20160277785 | Newman et al. | Sep 2016 | A1 |
| 20160345070 | Beeson et al. | Nov 2016 | A1 |
| 20160357305 | Wells et al. | Dec 2016 | A1 |
| 20160357352 | Matas et al. | Dec 2016 | A1 |
| 20160357355 | Carrigan et al. | Dec 2016 | A1 |
| 20160357366 | Migos et al. | Dec 2016 | A1 |
| 20160370982 | Penha et al. | Dec 2016 | A1 |
| 20170010846 | Bernstein et al. | Jan 2017 | A1 |
| 20170010847 | Bernstein et al. | Jan 2017 | A1 |
| 20170013295 | Wertheimer et al. | Jan 2017 | A1 |
| 20170046039 | Karunamuni et al. | Feb 2017 | A1 |
| 20170046339 | Bhat et al. | Feb 2017 | A1 |
| 20170068402 | Lochhead et al. | Mar 2017 | A1 |
| 20170068511 | Brown et al. | Mar 2017 | A1 |
| 20170094360 | Keighran et al. | Mar 2017 | A1 |
| 20170097969 | Stein et al. | Apr 2017 | A1 |
| 20170115867 | Bargmann | Apr 2017 | A1 |
| 20170124594 | Naiga et al. | May 2017 | A1 |
| 20170132659 | Dirks et al. | May 2017 | A1 |
| 20170132829 | Blas et al. | May 2017 | A1 |
| 20170134778 | Christie et al. | May 2017 | A1 |
| 20170140748 | Roberts et al. | May 2017 | A1 |
| 20170188116 | Major et al. | Jun 2017 | A1 |
| 20170192642 | Fishman et al. | Jul 2017 | A1 |
| 20170195736 | Chai et al. | Jul 2017 | A1 |
| 20170201850 | Raleigh et al. | Jul 2017 | A1 |
| 20170214975 | Schmidt et al. | Jul 2017 | A1 |
| 20170220228 | Sang et al. | Aug 2017 | A1 |
| 20170242913 | Tijssen et al. | Aug 2017 | A1 |
| 20170245017 | Chaudhri et al. | Aug 2017 | A1 |
| 20170251257 | Obrien | Aug 2017 | A1 |
| 20170300151 | Lue-sang et al. | Oct 2017 | A1 |
| 20170339443 | Lue-sang et al. | Nov 2017 | A1 |
| 20170344553 | Evnine et al. | Nov 2017 | A1 |
| 20170345040 | Pimnack et al. | Nov 2017 | A1 |
| 20170353603 | Grunewald et al. | Dec 2017 | A1 |
| 20170357387 | Clarke | Dec 2017 | A1 |
| 20170359722 | Folse et al. | Dec 2017 | A1 |
| 20170364246 | Van Os et al. | Dec 2017 | A1 |
| 20180011580 | Lebowitz et al. | Jan 2018 | A1 |
| 20180041814 | Christie et al. | Feb 2018 | A1 |
| 20180063591 | Newman et al. | Mar 2018 | A1 |
| 20180070121 | Zimmerman et al. | Mar 2018 | A1 |
| 20180070138 | Chai et al. | Mar 2018 | A1 |
| 20180107353 | Lee | Apr 2018 | A1 |
| 20180113579 | Johnston et al. | Apr 2018 | A1 |
| 20180130097 | Tran et al. | May 2018 | A1 |
| 20180136800 | Johnston et al. | May 2018 | A1 |
| 20180146377 | Folse et al. | May 2018 | A1 |
| 20180189076 | Liston et al. | Jul 2018 | A1 |
| 20180253900 | Finding et al. | Sep 2018 | A1 |
| 20180275855 | Van Os et al. | Sep 2018 | A1 |
| 20180293771 | Piemonte et al. | Oct 2018 | A1 |
| 20180295403 | Christie et al. | Oct 2018 | A1 |
| 20180302680 | Cormican | Oct 2018 | A1 |
| 20180343497 | Brown et al. | Nov 2018 | A1 |
| 20180349509 | Abou Mahmoud et al. | Dec 2018 | A1 |
| 20180367834 | Carpenter et al. | Dec 2018 | A1 |
| 20190012048 | Johnston et al. | Jan 2019 | A1 |
| 20190020925 | Christie et al. | Jan 2019 | A1 |
| 20190028769 | Jeon et al. | Jan 2019 | A1 |
| 20190045271 | Christie et al. | Feb 2019 | A1 |
| 20190052744 | Jung et al. | Feb 2019 | A1 |
| 20190058921 | Christie et al. | Feb 2019 | A1 |
| 20190066672 | Wood et al. | Feb 2019 | A1 |
| 20190073104 | Wang | Mar 2019 | A1 |
| 20190073680 | Knox | Mar 2019 | A1 |
| 20190129588 | Johnston et al. | May 2019 | A1 |
| 20190138163 | Howland et al. | May 2019 | A1 |
| 20190141399 | Auxer et al. | May 2019 | A1 |
| 20190258373 | Davydov et al. | Aug 2019 | A1 |
| 20190272853 | Moore | Sep 2019 | A1 |
| 20190342616 | Domm et al. | Nov 2019 | A1 |
| 20190354264 | Van Os et al. | Nov 2019 | A1 |
| 20190373320 | Balsamo | Dec 2019 | A1 |
| 20200068274 | Aher et al. | Feb 2020 | A1 |
| 20200084488 | Christie et al. | Mar 2020 | A1 |
| 20200099985 | Keighran et al. | Mar 2020 | A1 |
| 20200133631 | Christie et al. | Apr 2020 | A1 |
| 20200137175 | Ganci, Jr. | Apr 2020 | A1 |
| 20200257415 | Clarke | Aug 2020 | A1 |
| 20200272666 | Van Os et al. | Aug 2020 | A1 |
| 20200301567 | Park et al. | Sep 2020 | A1 |
| 20200301575 | Lindholm et al. | Sep 2020 | A1 |
| 20200304863 | Domm et al. | Sep 2020 | A1 |
| 20200304876 | Cielak et al. | Sep 2020 | A1 |
| 20200304879 | Ellingford | Sep 2020 | A1 |
| 20200304880 | Diaz Delgado et al. | Sep 2020 | A1 |
| 20200363934 | Van Os et al. | Nov 2020 | A1 |
| 20200374595 | Yang et al. | Nov 2020 | A1 |
| 20200380029 | Chen | Dec 2020 | A1 |
| 20200382845 | Payne | Dec 2020 | A1 |
| 20200396507 | Balsamo | Dec 2020 | A1 |
| 20210021903 | Christie et al. | Jan 2021 | A1 |
| 20210168424 | Sharma | Jun 2021 | A1 |
| 20210181901 | Johnston et al. | Jun 2021 | A1 |
| 20210195277 | Thurlow et al. | Jun 2021 | A1 |
| 20210286454 | Beaumier et al. | Sep 2021 | A1 |
| 20210306711 | Ellingford et al. | Sep 2021 | A1 |
| 20210337280 | Diaz Delgado et al. | Oct 2021 | A1 |
| 20210345004 | Christie et al. | Nov 2021 | A1 |
| 20210365134 | Beaumier et al. | Nov 2021 | A1 |
| 20210406995 | Peters et al. | Dec 2021 | A1 |
| 20220132215 | Venugopal et al. | Apr 2022 | A1 |
| 20220179526 | Schöberl | Jun 2022 | A1 |
| 20220244824 | Cielak | Aug 2022 | A1 |
| 20220321940 | Christie et al. | Oct 2022 | A1 |
| 20220329891 | Christie et al. | Oct 2022 | A1 |
| 20220337914 | Christie et al. | Oct 2022 | A1 |
| 20220360858 | Christie et al. | Nov 2022 | A1 |
| 20220413796 | Christie et al. | Dec 2022 | A1 |
| 20230022781 | Lindholm et al. | Jan 2023 | A1 |
| 20230033604 | Diaz Delgado et al. | Feb 2023 | A1 |
| 20230096458 | Van Os et al. | Mar 2023 | A1 |
| 20230127228 | Clarke | Apr 2023 | A1 |
| 20230132595 | Van Os et al. | May 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 2009255409 | Jul 2012 | AU |
| 2016100476 | May 2016 | AU |
| 2017101431 | Nov 2017 | AU |
| 2018100810 | Jul 2018 | AU |
| 1295419 | May 2001 | CN |
| 1391765 | Jan 2003 | CN |
| 1985277 | Jun 2007 | CN |
| 101160932 | Apr 2008 | CN |
| 101228570 | Jul 2008 | CN |
| 101317149 | Dec 2008 | CN |
| 101370104 | Feb 2009 | CN |
| 101436110 | May 2009 | CN |
| 101465993 | Jun 2009 | CN |
| 101529437 | Sep 2009 | CN |
| 101699505 | Apr 2010 | CN |
| 101706704 | May 2010 | CN |
| 101719125 | Jun 2010 | CN |
| 101860447 | Oct 2010 | CN |
| 102098537 | Jun 2011 | CN |
| 102103460 | Jun 2011 | CN |
| 102265586 | Nov 2011 | CN |
| 102325144 | Jan 2012 | CN |
| 102819715 | Dec 2012 | CN |
| 102859484 | Jan 2013 | CN |
| 102880404 | Jan 2013 | CN |
| 102890615 | Jan 2013 | CN |
| 102955653 | Mar 2013 | CN |
| 102981695 | Mar 2013 | CN |
| 103037265 | Apr 2013 | CN |
| 103177738 | Jun 2013 | CN |
| 103399967 | Nov 2013 | CN |
| 103516933 | Jan 2014 | CN |
| 103546816 | Jan 2014 | CN |
| 103562848 | Feb 2014 | CN |
| 103620531 | Mar 2014 | CN |
| 103620541 | Mar 2014 | CN |
| 103620639 | Mar 2014 | CN |
| 103686418 | Mar 2014 | CN |
| 103985045 | Aug 2014 | CN |
| 103999017 | Aug 2014 | CN |
| 104508618 | Apr 2015 | CN |
| 104822098 | Aug 2015 | CN |
| 105264479 | Jan 2016 | CN |
| 105303372 | Feb 2016 | CN |
| 105308634 | Feb 2016 | CN |
| 105308923 | Feb 2016 | CN |
| 105336350 | Feb 2016 | CN |
| 105657554 | Jun 2016 | CN |
| 105812849 | Jul 2016 | CN |
| 105828098 | Aug 2016 | CN |
| 105955520 | Sep 2016 | CN |
| 105955607 | Sep 2016 | CN |
| 105989085 | Oct 2016 | CN |
| 105992068 | Oct 2016 | CN |
| 106101982 | Nov 2016 | CN |
| 202016003233 | Aug 2016 | DE |
| 0608708 | Aug 1994 | EP |
| 0624853 | Nov 1994 | EP |
| 2386984 | Nov 2011 | EP |
| 2453667 | May 2012 | EP |
| 2535844 | Dec 2012 | EP |
| 2574089 | Mar 2013 | EP |
| 2605203 | Jun 2013 | EP |
| 2642402 | Sep 2013 | EP |
| 2672703 | Dec 2013 | EP |
| 2704032 | Mar 2014 | EP |
| 2725531 | Apr 2014 | EP |
| 2879398 | Jun 2015 | EP |
| 2000-112977 | Apr 2000 | JP |
| 2000-163031 | Jun 2000 | JP |
| 2001-197445 | Jul 2001 | JP |
| 2002-027381 | Jan 2002 | JP |
| 2002-342033 | Nov 2002 | JP |
| 2003-99452 | Apr 2003 | JP |
| 2003-534737 | Nov 2003 | JP |
| 2004-62237 | Feb 2004 | JP |
| 2006-31219 | Feb 2006 | JP |
| 2007-124465 | May 2007 | JP |
| 2007-512640 | May 2007 | JP |
| 2007-140910 | Jun 2007 | JP |
| 2007-294068 | Nov 2007 | JP |
| 2008-71112 | Mar 2008 | JP |
| 2008-135911 | Jun 2008 | JP |
| 2009-60328 | Mar 2009 | JP |
| 2009-206957 | Sep 2009 | JP |
| 2009-260947 | Nov 2009 | JP |
| 2010-28437 | Feb 2010 | JP |
| 2010-56595 | Mar 2010 | JP |
| 2010-509684 | Mar 2010 | JP |
| 2010-114733 | May 2010 | JP |
| 2011-512701 | Apr 2011 | JP |
| 2011-154455 | Aug 2011 | JP |
| 2011-182146 | Sep 2011 | JP |
| 2011-205562 | Oct 2011 | JP |
| 2011-257930 | Dec 2011 | JP |
| 2012-95123 | May 2012 | JP |
| 2012-123685 | Jun 2012 | JP |
| 2012-208622 | Oct 2012 | JP |
| 2013-8369 | Jan 2013 | JP |
| 2013-223150 | Oct 2013 | JP |
| 2014-81740 | May 2014 | JP |
| 2014-102660 | Jun 2014 | JP |
| 2015-50655 | Mar 2015 | JP |
| 2015-70404 | Apr 2015 | JP |
| 2001-0005939 | Jan 2001 | KR |
| 2001-0035356 | May 2001 | KR |
| 10-2002-0010151 | Feb 2002 | KR |
| 10-2007-0114329 | Dec 2007 | KR |
| 10-2009-0106104 | Oct 2009 | KR |
| 10-2010-0039194 | Apr 2010 | KR |
| 10-2011-0036408 | Apr 2011 | KR |
| 10-2011-0061811 | Jun 2011 | KR |
| 10-2012-0076682 | Jul 2012 | KR |
| 10-2012-0124445 | Nov 2012 | KR |
| 10-2013-0014712 | Feb 2013 | KR |
| 10-2013-0058034 | Jun 2013 | KR |
| 10-2013-0137969 | Dec 2013 | KR |
| 10-2014-0041939 | Apr 2014 | KR |
| 10-2019-0033658 | Mar 2019 | KR |
| 10-2022-0041231 | Mar 2022 | KR |
| 200622893 | Jul 2006 | TW |
| 200719204 | May 2007 | TW |
| 201337717 | Sep 2013 | TW |
| 201349049 | Dec 2013 | TW |
| 201351261 | Dec 2013 | TW |
| 1994009438 | Apr 1994 | WO |
| 1999040728 | Aug 1999 | WO |
| 2004063862 | Jul 2004 | WO |
| 2005050652 | Jun 2005 | WO |
| 2005109345 | Nov 2005 | WO |
| 2007078623 | Jul 2007 | WO |
| 2008005135 | Jan 2008 | WO |
| 2008060486 | May 2008 | WO |
| 2009016607 | Feb 2009 | WO |
| 2009039786 | Apr 2009 | WO |
| 2009148781 | Dec 2009 | WO |
| 2010022570 | Mar 2010 | WO |
| 2010025168 | Mar 2010 | WO |
| 2010118690 | Oct 2010 | WO |
| 2011095693 | Aug 2011 | WO |
| 2012012446 | Jan 2012 | WO |
| 2012061760 | May 2012 | WO |
| 2012088665 | Jul 2012 | WO |
| 2013000741 | Jan 2013 | WO |
| 2013149128 | Oct 2013 | WO |
| 2013169849 | Nov 2013 | WO |
| 2013169877 | Nov 2013 | WO |
| 2013149128 | Feb 2014 | WO |
| 2014105276 | Jul 2014 | WO |
| 2014144908 | Sep 2014 | WO |
| 2014177929 | Nov 2014 | WO |
| 2014200730 | Dec 2014 | WO |
| 2015200227 | Dec 2015 | WO |
| 2015200228 | Dec 2015 | WO |
| 2015200537 | Dec 2015 | WO |
| 2016030437 | Mar 2016 | WO |
| 2016048308 | Mar 2016 | WO |
| 2016048310 | Mar 2016 | WO |
| 2016111065 | Jul 2016 | WO |
| 2017008079 | Jan 2017 | WO |
| 2017124116 | Jul 2017 | WO |
| 2017200923 | Nov 2017 | WO |
| 2017218104 | Dec 2017 | WO |
| 2018081157 | May 2018 | WO |
| Entry |
|---|
| Applicant Initiated Interview Summary received for U.S. Appl. No. 17/210,352, dated Feb. 28, 2022, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/876,715, dated Apr. 11, 2022, 4 Pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/876,715, dated Apr. 19, 2022, 4 Pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/142,635, dated Mar. 10, 2022, 2 Pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/233,990, dated Mar. 8, 2022, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/233,990, dated Oct. 20, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/872,274, dated Aug. 12, 2022, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/945,724, dated Aug. 31, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/000,112, dated Jun. 17, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/065,387, dated Mar. 30, 2022, 2 Pages. |
| Extended European Search Report received for European Patent Application No. 22167405.4, dated Jul. 4, 2022, 11 Pages. |
| Final Office Action received for U.S. Appl. No. 16/175,565, dated May 27, 2022, 33 pages. |
| Final Office Action received for U.S. Appl. No. 16/584,790, dated Jun. 14, 2022, 37 pages. |
| Final Office Action received for U.S. Appl. No. 16/697,090, dated Feb. 23, 2022, 25 pages. |
| Final Office Action received for U.S. Appl. No. 16/827,910, dated Feb. 28, 2022, 17 pages. |
| Final Office Action received for U.S. Appl. No. 16/888,453, dated Apr. 8, 2022, 39 pages. |
| Final Office Action received for U.S. Appl. No. 17/133,550, dated Feb. 11, 2022, 18 pages. |
| Final Office Action received for U.S. Appl. No. 17/210,352, dated Jun. 3, 2022, 21 pages. |
| Final Office Action received for U.S. Appl. No. 17/379,785, dated Oct. 28, 2022, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/167,801, dated May 18, 2022, 17 Pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/697,090, dated Jul. 7, 2022, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/827,910, dated Sep. 14, 2022, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/827,926, dated Apr. 25, 2022, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/888,478, dated May 2, 2022, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/133,550, dated Sep. 9, 2022, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/379,785, dated Mar. 30, 2022, 18 Pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/457,901, dated Apr. 28, 2022, 24 Pages. |
| Notice of Allowance received for U.S. Appl. No. 15/719,404, dated Jul. 13, 2022, 8 Pages. |
| Notice of Allowance received for U.S. Appl. No. 15/719,404, dated Nov. 9, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/876,715, dated Apr. 4, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/876,715, dated Aug. 3, 2022, 7 Pages. |
| Notice of Allowance received for U.S. Appl. No. 16/233,990, dated Feb. 22, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/233,990, dated May 26, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/233,990, dated Oct. 5, 2022, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/827,918, dated Feb. 7, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/827,918, dated Jun. 8, 2022, 9 Pages. |
| Notice of Allowance received for U.S. Appl. No. 16/827,931, dated Apr. 19, 2022, 7 Pages. |
| Notice of Allowance received for U.S. Appl. No. 16/865,172, dated Apr. 13, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/865,172, dated Aug. 25, 2022, 8 Pages. |
| Notice of Allowance received for U.S. Appl. No. 16/872,274, dated Apr. 19, 2022, 10 Pages. |
| Notice of Allowance received for U.S. Appl. No. 16/945,724, dated Apr. 4, 2022, 8 Pages. |
| Notice of Allowance received for U.S. Appl. No. 16/945,724, dated Jul. 20, 2022, 8 Pages. |
| Notice of Allowance received for U.S. Appl. No. 17/000,112, dated Jun. 3, 2022, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/000,112, dated Oct. 18, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/654,578, dated Oct. 25, 2022, 8 pages. |
| Search Report received for Chinese Patent Application No. 201780066823.6, dated Nov. 1, 2022, 4 pages (2 pages of English Translation and 2 Pages of Official Copy). |
| Search Report received for Chinese Patent Application No. 201680050096.X, dated Jan. 10, 2022, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 15/167,801, dated Feb. 16, 2018, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/167,801, dated Apr. 23, 2018, 3 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/167,801, dated Jul. 29, 2019, 3 pages. |
| Corrected Notice of Allowability received for U.S. Appl. No. 16/108,519, dated Dec. 22, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/242,575, dated Dec. 15, 2016, 7 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/242,575, dated Nov. 16, 2016, 7 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/255,664, dated Aug. 29, 2017, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/267,671, dated Nov. 29, 2018, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/749,288, dated Sep. 21, 2017, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/276,633, dated Sep. 10, 2019, 7 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/695,880, dated Jun. 11, 2018, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/714,904, dated Sep. 7, 2018, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/876,715, dated Oct. 20, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/010,280, dated Aug. 6, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/036,810, dated Nov. 19, 2018, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/827,931, dated Dec. 6, 2021, 4 pages. |
| Cover Flow—Wikipedia, Available online at: <https://en.wikipedia.org/w/index.php?t%20itle=Cover%20Flow&oldid=879285208>, Jan. 20, 2019, 3 pages. |
| Examiner Initiated Interview Summary received for U.S. Appl. No. 15/390,377, dated Oct. 30, 2017, 2 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 15/876,715, dated Aug. 18, 2020, 16 pages. |
| Extended European Search Report received for European Patent Application No. 17813728.7, dated Feb. 11, 2019, 8 pages. |
| Extended European Search Report received for European Patent Application No. 20190698.9, dated Oct. 30, 2020, 6 pages. |
| Extended European Search Report received for European Patent Application No. 20199219.5, dated Apr. 22, 2021, 8 pages. |
| Final Office Action received for U.S. Appl. No. 14/255,664, dated Oct. 17, 2016, 16 pages. |
| Final Office Action received for U.S. Appl. No. 14/267,671, dated May 23, 2018, 17 pages. |
| Final Office Action received for U.S. Appl. No. 14/267,671, dated Oct. 26, 2016, 21 pages. |
| Final Office Action received for U.S. Appl. No. 14/271,179, dated Dec. 15, 2016, 10 pages. |
| Final Office Action received for U.S. Appl. No. 14/271,179, dated Jun. 20, 2019, 15 pages. |
| Final Office Action received for U.S. Appl. No. 14/271,179, dated Jun. 21, 2018, 14 pages. |
| Final Office Action received for U.S. Appl. No. 14/746,095, dated Jul. 16, 2018, 33 pages. |
| Final Office Action received for U.S. Appl. No. 14/746,662, dated Apr. 24, 2017, 8 pages. |
| Final Office Action received for U.S. Appl. No. 14/746,662, dated Jun. 27, 2017, 9 pages. |
| Final Office Action received for U.S. Appl. No. 15/167,801, dated Apr. 5, 2019, 18 pages. |
| Final Office Action received for U.S. Appl. No. 15/167,801, dated May 28, 2020, 17 pages. |
| Final Office Action received for U.S. Appl. No. 15/167,801, dated Nov. 29, 2017, 12 pages. |
| Final Office Action received for U.S. Appl. No. 15/235,000, dated Dec. 19, 2018, 33 pages. |
| Final Office Action received for U.S. Appl. No. 15/235,000, dated Mar. 13, 2018, 31 pages. |
| Final Office Action received for U.S. Appl. No. 15/272,393, dated Mar. 25, 2019, 54 pages. |
| Final Office Action received for U.S. Appl. No. 15/272,397, dated Mar. 7, 2017, 23 pages. |
| Final Office Action received for U.S. Appl. No. 15/276,633, dated Jul. 26, 2017, 15 pages. |
| Final Office Action received for U.S. Appl. No. 15/276,633, dated Oct. 29, 2018, 12 pages. |
| Final Office Action received for U.S. Appl. No. 15/390,377, dated Nov. 9, 2017, 18 pages. |
| Final Office Action received for U.S. Appl. No. 15/507,229, dated Jul. 15, 2020, 20 pages. |
| Final Office Action received for U.S. Appl. No. 15/507,229, dated Sep. 18, 2019, 15 pages. |
| Final Office Action received for U.S. Appl. No. 15/719,404, dated Aug. 8, 2019, 19 pages. |
| Final Office Action received for U.S. Appl. No. 15/719,404, dated Mar. 30, 2021, 19 pages. |
| Final Office Action received for U.S. Appl. No. 15/876,715, dated Nov. 5, 2018, 15 pages. |
| Final Office Action received for U.S. Appl. No. 16/108,519, dated Dec. 12, 2019, 10 pages. |
| Final Office Action received for U.S. Appl. No. 16/108,519, dated Nov. 25, 2020, 12 pages. |
| Final Office Action received for U.S. Appl. No. 16/126,962, dated Apr. 8, 2020, 20 pages. |
| Final Office Action received for U.S. Appl. No. 16/136,005, dated Mar. 9, 2020, 9 pages. |
| Final Office Action received for U.S. Appl. No. 16/142,635, dated Feb. 3, 2021, 23 pages. |
| Final Office Action received for U.S. Appl. No. 16/144,077, dated Jul. 12, 2019, 22 pages. |
| Final Office Action received for U.S. Appl. No. 16/175,565, dated Nov. 12, 2020, 40 pages. |
| Final Office Action received for U.S. Appl. No. 16/233,990, dated Jan. 11, 2021, 17 pages. |
| Final Office Action received for U.S. Appl. No. 16/584,790, dated Jun. 15, 2021, 30 pages. |
| Final Office Action received for U.S. Appl. No. 16/584,790, dated May 27, 2020, 27 pages. |
| Final Office Action received for U.S. Appl. No. 16/682,443, dated Mar. 9, 2021, 9 pages. |
| Final Office Action received for U.S. Appl. No. 16/697,090, dated Jan. 27, 2021, 18 pages. |
| Final Office Action received for U.S. Appl. No. 16/827,918, dated Jul. 8, 2021, 31 pages. |
| Final Office Action received for U.S. Appl. No. 16/827,926, dated Mar. 17, 2021, 44 pages. |
| Final Office Action received for U.S. Appl. No. 16/865,172, dated Feb. 12, 2021, 29 pages. |
| Final Office Action received for U.S. Appl. No. 16/872,274, dated Dec. 23, 2021, 20 pages. |
| Final Office Action received for U.S. Appl. No. 16/888,478, dated Nov. 15, 2021, 27 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2014/057272, dated May 28, 2015, 4 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2014/057280, dated May 27, 2015, 4 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2015/037027, dated Sep. 28, 2015, 3 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2015/037030, dated Dec. 10, 2015, 7 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2015/037520, dated Mar. 7, 2016, 6 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2017/029448, dated Jul. 13, 2017, 3 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2017/031764, dated Aug. 7, 2017, 2 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2017/058132, dated Mar. 27, 2018, 6 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2019/034921, dated Nov. 19, 2019, 5 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2020/024452, dated Aug. 6, 2020, 6 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2020/024485, dated Aug. 3, 2020, 6 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2020/024486, dated Aug. 11, 2020, 6 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2020/024492, dated Aug. 10, 2020, 6 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2020/035423, dated Oct. 13, 2020, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/208,099, dated Jun. 25, 2015, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/242,575, dated Mar. 21, 2016, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/255,664, dated Apr. 1, 2016, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/262,435, dated Feb. 22, 2016, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/267,671, dated Apr. 1, 2016, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/267,671, dated Dec. 1, 2017, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/267,671, dated May 26, 2017, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/271,179, dated May 29, 2015, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/271,179, dated Oct. 5, 2018, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/271,179, dated Sep. 21, 2017, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/746,095, dated Dec. 1, 2017, 34 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/746,095, dated Jul. 25, 2019, 33 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/746,620, dated Jan. 11, 2017, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/746,662, dated Aug. 9, 2016, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/749,288, dated Oct. 12, 2016, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/167,801 dated Mar. 24, 2017, 12 Pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/167,801, dated Aug. 30, 2018, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/167,801, dated Dec. 11, 2020, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/167,801, dated Sep. 3, 2021, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/167,801, dated Sep. 26, 2019, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/224,370, dated Oct. 3, 2017, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/235,000, dated Jul. 14, 2017, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/235,000, dated Jul. 25, 2018, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/235,000, dated Jun. 26, 2019, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/272,393, dated Oct. 2, 2018, 52 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/272,397, dated Nov. 22, 2016, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/276,633, dated Feb. 23, 2018, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/276,633, dated Mar. 5, 2019, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/276,633, dated Nov. 17, 2016, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/390,377, dated Apr. 5, 2017, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/414,493, dated Oct. 6, 2017, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/507,229, dated Feb. 27, 2020, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/507,229, dated Jun. 3, 2019, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/674,992, dated May 11, 2018, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/719,404, dated Dec. 14, 2018, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/719,404, dated Nov. 26, 2021, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/719,404, dated Oct. 16, 2020, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/798,092, dated Dec. 20, 2017, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/876,715, dated Jun. 4, 2018, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/876,715, dated Sep. 10, 2019, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/990,327, dated Jul. 31, 2018, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/010,280, dated Mar. 7, 2019, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/108,519, dated Apr. 5, 2021, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/108,519, dated Aug. 2, 2019, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/108,519, dated May 8, 2020, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/126,962, dated Aug. 25, 2020, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/126,962, dated Sep. 3, 2019, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/136,005, dated Sep. 9, 2020, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/136,005, dated Sep. 18, 2019, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/142,635, dated Jun. 8, 2020, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/142,635, dated Jun. 11, 2021, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,077, dated Feb. 19, 2019, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/144,077, dated Nov. 27, 2019, 40 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/175,565, dated Sep. 20, 2021, 33 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/233,990, dated Jul. 9, 2021, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/233,990, dated Jun. 18, 2020, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/392,467, dated Sep. 27, 2019, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,790, dated Dec. 23, 2020, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,790, dated Dec. 26, 2019, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/584,790, dated Feb. 1, 2022, 33 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/682,443, dated Sep. 23, 2020, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/697,090, dated Aug. 3, 2021, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/697,090, dated Jul. 6, 2020, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/827,910, dated Jun. 17, 2021, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/827,918, dated Dec. 10, 2020, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/827,926, dated Oct. 29, 2020, 45 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/827,931, dated Mar. 3, 2021, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/865,172 dated Jun. 29, 2021, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/865,172, dated Aug. 20, 2020, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/872,274, dated Jul. 9, 2021, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/888,453, dated Jun. 4, 2021, 37 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/888,478, dated Feb. 8, 2021, 24 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/945,724, dated Jul. 19, 2021, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/000,112, dated Dec. 7, 2021, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/065,387, dated Jan. 28, 2021, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/065,387, dated Jun. 1, 2021, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/133,550, dated Jun. 8, 2021, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/210,352, dated Oct. 18, 2021, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/175,565, dated Mar. 4, 2020, 36 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/208,099, dated Feb. 3, 2016, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/242,575, dated Oct. 27, 2016, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/255,664, dated May 5, 2017, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/262,435, dated Aug. 16, 2016, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/267,671, dated Sep. 19, 2018, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/746,095, dated Dec. 31, 2019, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/746,620, dated Sep. 25, 2017, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/746,662, dated Sep. 25, 2017, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/749,288, dated May 25, 2017, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/272,393, dated Jan. 15, 2020, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/272,393, dated Sep. 18, 2019, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/272,397, dated Oct. 18, 2017, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/276,633, dated Aug. 26, 2019, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/390,377, dated Jul. 2, 2018, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/414,493, dated Mar. 14, 2018, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/674,992, dated Oct. 1, 2018, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/695,880, dated Feb. 28, 2018, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/695,880, dated Oct. 18, 2017, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/714,904, dated May 22, 2018, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/798,092, dated Jun. 7, 2018, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/798,092, dated Oct. 9, 2018, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/833,618, dated Mar. 14, 2018, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/876,715, dated Oct. 14, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/990,327, dated Jan. 11, 2019, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/010,280, dated Jul. 29, 2019, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/036,810, dated Oct. 31, 2018, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/108,519, dated Sep. 21, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/136,005, dated Feb. 24, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/136,005, dated Jun. 9, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/142,635, dated Nov. 10, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/144,077, dated May 8, 2020, 15 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/392,467, dated Mar. 23, 2020, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/682,443, dated Aug. 20, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/682,443, dated Nov. 17, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/726,179, dated Jun. 17, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/726,179, dated Sep. 30, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/827,926, dated Nov. 1, 2021, 35 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/827,931, dated Jan. 5, 2022, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/827,931, dated Sep. 15, 2021, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/827,942, dated Apr. 28, 2021, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/827,942, dated Jan. 22, 2021, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/827,942, dated Oct. 5, 2020, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/865,172, dated Dec. 16, 2021, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/945,724, dated Dec. 20, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/065,387, dated Dec. 1, 2021, 10 pages. |
| Patent Board Decision received for U.S. Appl. No. 15/876,715, dated Aug. 3, 2021, 8 pages. |
| Restriction Requirement received for U.S. Appl. No. 14/208,099, dated Feb. 24, 2015, 5 pages. |
| Search Report received for Chinese Patent Application No. 201580028382.1, dated Oct. 12, 2018, 5 pages (2 pages of English Translation & 3 pages of Official copy). |
| Search Report received for Chinese Patent Application No. 201780033590.X, dated Mar. 24, 2021, 4 pages (2 page of English Translation and 2 pages of Official Copy). |
| Search Report received for Chinese Patent Application No. 201910469185.3, dated Feb. 23, 2021, 6 pages (3 page of English Translation and 3 page of Official Copy). |
| Search Report received for Chinese Patent Application No. 201910587972.8, dated Jan. 4, 2022, 4 pages (2 page of English Translation and 2 pages of Official Copy). |
| Search Report received for Danish Patent Application No. PA 201670581, dated Apr. 4, 2017, 2 pages. |
| Search Report received for Danish Patent Application No. PA 201670581, dated Feb. 5, 2018, 1 page. |
| Search Report received for Danish Patent Application No. PA 201670581, dated Nov. 3, 2016, 1 page. |
| Search Report received for Danish Patent Application No. PA 201870354, dated Sep. 26, 2018, 4 pages. |
| Search Report received for Danish Patent Application No. PA201670582, dated Feb. 9,2017, 1 pages. |
| Search Report received for Danish Patent Application No. PA201670582, dated Mar. 6, 2018, 2 pages. |
| Search Report received for Danish Patent Application No. PA201670582, dated Oct. 28, 2016, 4 pages. |
| Search Report received for Danish Patent Application No. PA201770200, Completed on Jul. 12, 2017, 4 pages. |
| Search Report received for Taiwanese Patent Application No. 104120369, dated Aug. 8, 2016, 2 Pages (1 page of official copy & 1 page of English translation). |
| Search Report received for Taiwanese Patent Application No. 104120385, dated Nov. 25, 2016, 2 Pages (1 page of official copy & 1 page of English translation). |
| Supplemental Notice of Allowability received for U.S. Appl. No. 16/827,942, dated Nov. 4, 2020, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 15/798,092, dated Jan. 9, 2019, 2 pages. |
| Akhtar Iyaz, “Movies Anywhere: Everything You Need To Know”, Available online at: <https://www.cnet.com/how-to/movies-anywhere-ultraviolet-movies-locker-streaming-redeem-faq/>, 2017, 8 pages. |
| Alvarez Edgar, “Sling TV Redesign Makes It Easy to Find Your Favorite Content”, Engadget, Available online at: <https://www.engadget.com/2016/01/05/sling-tv-major-redesign/>, May 1, 2016, pp. 1-12. |
| Bishop Bryan, “Netflix Introduces One Unified TV Interface to Rule them All”, The Verge, Available online at: <https://www.theverge.com/2013/11/13/5098224/netflix-introduces-one-unified-tv-interface-to-rule-them-all>, Nov. 13, 2013, 3 pages. |
| Bohn Dieter, “Rebooting WebOS: How LG Rethought the Smart TV”, The Verge, Available online at: <http://www.theverge.com/2014/1/6/5279220/rebooting-webos-how-lg-rethought-the-smart-tv>, Jan. 6, 2014, 5 pages. |
| Cheredar Tom, “Verizon's Viewdini Lets You Watch Netflix, Comcast, & Hulu Videos from a Single App”, Available online at: <venturebeat.com>, May 22, 2012, 6 pages. |
| episodecalendar.com, “Keep track of your favorite TV shows!—TV Episode Calendar”, Available Online at: <https://web.archive.org/web/20140517060612/https://episodecalendar.com/>, May 17, 2014, 6 pages. |
| Fingas Roger, “Walmart's Vudu to get Native Apple TV”, AppleInsider, 2017, pp. 1-4. |
| Grey Melissa, “Comcast's New X2 Platform Moves your DVR Recordings from the Box to the Cloud”, Engadget, Available online at: <http://www.engadget.com/2013/06/11/comcast-x2-platform/>, Jun. 11, 2013, 15 pages. |
| International Standard—ISO, “Ergonomic Requirements for Office Work with Visual Display Terminals (VDTs)”, Part 13: User Guidance, Zurich, CH, vol. 9241-13, XP001525163, Section 10, Jul. 15, 1998, 40 pages. |
| Kaijser Martijn, “Mimic Skin for Kodi 15.x: Installation and Showcase”, Time 2:23-2:28, Available online at: <https://www.youtube.com/watch?v=RGfpbUWkgQ&t=143s>, Aug. 3, 2015, 1 page. |
| Lee et al., “A Multi-Touch Three Dimensional Touch-Sensitive Tablet”, CHI'85 Proceedings, Apr. 1985, pp. 21-25. |
| Li Xiaoshan, “CNTV, Hulu, BBC iPlayer Comparative Study on User Interface of Three Network TV Stations”, Modern Communication (Journal of Communication University of China), Issue 11, Nov. 5, 2010, pp. 156-158. See attached Communication 37 CFR § 1.98(a) (3). |
| Ng Gary, “New Netflix User Interface Coming This Month, First Redesign in Four Years”, iPhone in Canada, Available online at: <https://www.iphoneincanada.ca/news/new-netflix-user-interface/>, Jun. 1, 2015, 3 pages. |
| Panzarino Matthew, “Apple Announces Voice Activated Siri Assistant Feature for iOS 5, Integrates Wolfram Alpha and Wikipedia”, Available online at: <www.thenextweb.com>, Oct. 4, 2011, pp. 1-6. |
| Pierce David, “Got Hulu and Netflix? You Need an App to Search It All”, Wired, Available online at: <https://www.wired.com/2016/03/got-hulu-netflix-need-app-search/>, Mar. 10, 2016, pp. 1-4. |
| Rubine Dean, “Combining Gestures and Direct Manipulation”, CHI'92, May 3-7, 1992, pp. 659-660. |
| Rubine Dean H., “The Automatic Recognition of Gestures”, CMU-CS-91-202, Submitted in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy in Computer Science at Carnegie Mellon University, Dec. 1991, 285 pages. |
| Westerman Wayne, “Hand Tracking, Finger Identification, and Chordic Manipulation on a Multi-Touch Surface”, A Dissertation Submitted to the Faculty of the University of Delaware in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy in Electrical Engineering, 1999, 363 pages. |
| Final Office Action received for U.S. Appl. No. 16/697,090, dated Dec. 14, 2022, 28 pages. |
| Final Office Action received for U.S. Appl. No. 16/827,910, dated Mar. 15, 2023, 18 pages. |
| Final Office Action received for U.S. Appl. No. 16/827,926, dated Apr. 18, 2023, 32 pages. |
| Final Office Action received for U.S. Appl. No. 16/888,478, dated Feb. 13, 2023, 27 pages. |
| Final Office Action received for U.S. Appl. No. 17/133,550, dated Feb. 15, 2023, 22 pages. |
| Final Office Action received for U.S. Appl. No. 17/586,625, dated May 4, 2023, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/167,801, dated Feb. 8, 2023, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/175,565, dated Feb. 17, 2023, 33 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/379,785, dated Mar. 9, 2023, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/586,625, dated Sep. 1, 2022, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/651,731, dated Apr. 25, 2023, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/656,610, dated Feb. 6, 2023, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/660,622, dated Dec. 20, 2022, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/937,410, dated Mar. 2, 2023, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/937,704, dated Mar. 30, 2023, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/060,902, dated Mar. 10, 2023, 8 pages. |
| Notice of Allowability received for U.S. Appl. No. 17/457,901, dated Mar. 8, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/233,990, dated Jan. 31, 2023, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/584,790, dated Feb. 3, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/888,453, dated Mar. 1, 2023, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/210,352, dated Dec. 5, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/210,352, dated Mar. 16, 2023, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/367,227, dated Mar. 23, 2023, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/457,901, dated Nov. 16, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/654,578, dated Feb. 15, 2023, 8 pages. |
| Search Report received for Chinese Patent Application No. 201811143102.3, dated Nov. 22, 2022, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Search Report received for Chinese Patent Application No. 201911313480.6, dated Jan. 20, 2023, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Search Report received for Chinese Patent Application No. 201911313496.7, dated Jan. 20, 2023, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Search Report Received for Chinese Patent Application No. 201911313497.1, dated Apr. 11, 2023, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Search Report received for Chinese Patent Application No. 201911313497.1, dated Dec. 14, 2022, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Search Report received for Chinese Patent Application No. 202010011436.6, dated Dec. 15, 2022, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Search Report Received for European Patent Application No. 20718506.7, dated Mar. 21, 2023, 2 pages. |
| Anonymous, “Video Progress Bar—YouTube Help”, Retrieved from the Internet: <URL:https://web.archive.org/web/20190317001501/https://support.google.com/youtube/answer/7174115?hl=en>, [retrieved on Mar. 22, 20232], Mar. 17, 2019, 2 pages. |
| Apple, “The control is all yours”, Available online at : <https://www.apple.com.cn/privacy/control/>, [Retrieved Dec. 29, 2022], Nov. 30, 2022, 12 pages. See attached Communication 37 CFR § 1.98(a)(3). |
| Drews et al., “Virtual Jukebox—Reviving a Classic”, Proceedings of the 35th Hawaii International Conference on System Sciences, 2022, 7 pages. |
| Jin et al., “Pricing Sponsored Content in Wireless Networks with Multiple Content Providers”, The Fourth IEEE Workshop on Smart Data Pricing 2015, 2015, pp. 668-673. |
| Kimbler, Kristofer, “App Store Strategies for Service Providers”, 2010 4th International Conference on Intelligence in Next Generation Networks, Nov. 18, 2010, 5 pages. |
| Meng et al., “Role Authorization Based Web Service Access Control Model”, Journal of Lanzhou University (Natural Science Edition), vol. 42, No. 2, 2007, pp. 84-88. See attached Communication 37 CFR § 1.98(a)(3). |
| Tinari, George, “What's New in the Netflix Redesign and How to Use It”, Retrieved from the Internet: <https://web.archive.org/web/20161110092133/https://www.guidingtech.com/48443/netflix-redesign-overview/ >, [retrieved on Mar. 22, 2023]., Nov. 10, 2016, 9 pages. |
| Wang et al., “Authorization Management Mechanism of Web Application System”, Network and Information Technology, vol. 25, No. 11, 2006, 3 pages. See attached Communication 37 CFR § 1.98(a)(3). |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/888,453, dated Jul. 26, 2023, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/367,227, dated Jul. 27, 2023, 2 pages. |
| Final Office Action received for U.S. Appl. No. 17/660,622, dated May 24, 2023, 20 pages. |
| Final Office Action received for U.S. Appl. No. 17/937,410, dated Aug. 3, 2023, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/719,404, dated May 10, 2023, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/656,610, dated Jul. 26, 2023, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/657,913, dated Jul. 21, 2023, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/146,336, dated Aug. 3, 2023, 23 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/827,910, dated Aug. 3, 2023, 21 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/888,453, dated Jun. 21, 2023, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/888,478, dated Aug. 2, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/654,578, dated Jun. 13, 2023, 7 pages. |
| Search Report received for Chinese Patent Application No. 202010662190.9, dated Apr. 28, 2023, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Search Report received for Chinese Patent Application No. 202010662206.6, dated Apr. 28, 2023, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Search Report received for Chinese Patent Application No. 202010662994.9, dated Apr. 28, 2023, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Beer et al., “The Odds of Running a Nonlinear TV Program Using Web Technologies”, IEEE International Symposium on Broadband Multimedia Systems and Broadcasting (BMSB), 2011, 4 pages. |
| Biao et al., “Research on UI Optimization of Chinese Network Television Stations”, Southeast Communications, 2013, 4 pages. See attached Communication 37 CFR § 1.98(a)(3). |
| Budhraja et al., “Probability Based Playlist Generation Based on Music Similarity and User Customization”, National Conference on Computing and Communication Systems, 2012, 5 pages. |
| Search Report received for Chinese Patent Application No. 202210799020.4, dated Jul. 27, 2023, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Cheng, Luo, “The Designing of Dynamic Play-list Based on Flash Streaming Media Technology”, Computer and Telecommunication, 2008, 3 pages. See attached Communication 37 CFR § 1.98(a)(3). |
| Liu, Chang, “Functions and Design of Multi-Screen Playing System in TV Variety Studio”, Modern TV Technology, 2013, 5 pages. See attached Communication 37 CFR § 1.98(a)(3). |
| Zhang et al., “Music Playlist Prediction via Detecting Song Moods”, IEEE China Summit and International Conference on Signal and Information Processing, 2013, pp. 174-178. |
| Number | Date | Country | |
|---|---|---|---|
| 20210397306 A1 | Dec 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 63197472 | Jun 2021 | US | |
| 63041981 | Jun 2020 | US |
