Patent Grant
12184969
The present disclosure relates generally to computer user interfaces, and more specifically to techniques for avatar creation and editing.
Avatars are used to represent the users of electronic devices. The avatars can represent the appearance of a user or can represent an idealized or completely fictional representation of the user. Avatars can then be associated with a user so that the appearance of the avatar to others indicates triggers an association or link with the user.
Some techniques for avatar creation and editing using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for avatar creation and editing. Such methods and interfaces optionally complement or replace other methods for avatar creation and editing. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
In accordance with an embodiment, an electronic device with a display and one or more cameras displays displaying a placeholder avatar on the display, wherein the display of the placeholder avatar is based on a first position of a user with respect to a field of view of the one or more cameras of the electronic device. While displaying the placeholder avatar, the electronic device detects movement of the user to a second position with respect to the field of view of the one or more cameras. In response to detecting the movement of the user to the second position with respect to the field of view of the one or more cameras, the electronic device, in accordance with a determination that the second position of the user with respect to the field of view of the one or more cameras meets the first set of image criteria, captures first image data of the user with the one or more cameras; and in accordance with a determination that the second position of the user with respect to the field of view of the one or more cameras does not meet the first set of image criteria and while continuing to display the placeholder avatar, provides first guidance to the user to change position with respect to the electronic device to a first target position.
An embodiment of a transitory computer readable storage medium stores one or more programs, the one or more programs comprise instructions, which when executed by one or more processors of an electronic device with a display and one or more cameras, cause the device to display a placeholder avatar on the display, wherein the display of the placeholder avatar is based on a first position of a user with respect to a field of view of the one or more cameras of the electronic device; while displaying the placeholder avatar, detect movement of the user to a second position with respect to the field of view of the one or more cameras; in response to detecting the movement of the user to the second position with respect to the field of view of the one or more cameras: in accordance with a determination that the second position of the user with respect to the field of view of the one or more cameras meets the first set of image criteria, capture first image data of the user with the one or more cameras; and in accordance with a determination that the second position of the user with respect to the field of view of the one or more cameras does not meet the first set of image criteria and while continuing to display the placeholder avatar, provide first guidance to the user to change position with respect to the electronic device to a first target position.
In accordance with an embodiment, an electronic device with a display and one or more input devices displays an avatar editing user interface that includes concurrently display, on the display, of an avatar having a plurality of editable features; a feature-selection control region that includes representations of a plurality of avatar features, including a first avatar feature that is currently selected for modification and a second avatar feature that is not currently selected for modification; and a feature-option control region that includes representations of a plurality of options for the first avatar feature for selection including a first option for the first avatar feature that is currently selected and a second option for the first avatar feature that is not currently selected; while displaying the avatar editing user interface, detecting an input in the avatar editing user interface; and in response to detecting the input: in accordance with a determination that the input corresponds to selection of the second avatar feature in the feature-selection control region: updating the feature-selection control region to indicate that the second avatar feature is currently selected; and updating the feature-option control region to include representations of a plurality of options for the second avatar feature for selection including a first option for the second avatar feature that is currently selected and a second option for the second avatar feature that is not currently selected; in accordance with a determination that the input corresponds to selection of the second option for the first avatar feature in the feature-option control region: updating the feature-option control region to indicate that the second option for the first avatar feature is currently selected; and updating the avatar to change the appearance of the first avatar feature in accordance with the second option for the first avatar feature.
An embodiment of a transitory computer readable storage medium stores one or more programs, the one or more programs comprise instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the device to display an avatar editing user interface that includes concurrently displaying, on the display: an avatar having a plurality of editable features; a feature-selection control region that includes representations of a plurality of avatar features, including a first avatar feature that is currently selected for modification and a second avatar feature that is not currently selected for modification; a feature-option control region that includes representations of a plurality of options for the first avatar feature for selection including a first option for the first avatar feature that is currently selected and a second option for the first avatar feature that is not currently selected; while displaying the avatar editing user interface, detect an input in the avatar editing user interface; and in response to detecting the input: in accordance with a determination that the input corresponds to selection of the second avatar feature in the feature-selection control region: update the feature-selection control region to indicate that the second avatar feature is currently selected; and update the feature-option control region to include representations of a plurality of options for the second avatar feature for selection including a first option for the second avatar feature that is currently selected and a second option for the second avatar feature that is not currently selected; in accordance with a determination that the input corresponds to selection of the second option for the first avatar feature in the feature-option control region: update the feature-option control region to indicate that the second option for the first avatar feature is currently selected; and update the avatar to change the appearance of the first avatar feature in accordance with the second option for the first avatar feature.
In accordance with an embodiment, an electronic device with a display and one or more input devices displays a messaging interface for a messaging application for transmitting messages between a first user of the device and other users, wherein the first user is represented in the messaging application by an avatar of the user that distinguishes the first user of the device from other users; while displaying the messaging user interface, receives a first request to display a sticker user interface for selecting stickers to send to a second user; in response to the first request to display the sticker user interface, displays a sticker user interface that includes a first plurality of avatar stickers generated based on the avatar of the user, including concurrently displaying, on the display: a first avatar sticker generated based on a modification of the avatar that represents the user, and a second avatar sticker generated based on a modification of the avatar that represents the user and is different from the first avatar sticker; while displaying the plurality affordance for the avatar selection interface on the display, detects, via the one or more input devices, a sequence of one or more inputs that corresponds to a request to send a respective avatar sticker from the first user to the second user via the messaging application; and in response to detecting the sequence of one or more inputs: in accordance with a determination that the sequence of one or more inputs corresponds to selection of the first avatar sticker, sends the first avatar sticker to the second user from the first user to the second user via the messaging application; and in accordance with a determination that the sequence of one or more inputs corresponds to selection of the second avatar sticker, sends the second avatar sticker from the first user to the second user via the messaging application.
An embodiment of a transitory computer readable storage medium stores one or more programs, the one or more programs comprise instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the device to display a messaging interface for a messaging application for transmitting messages between a first user of the device and other users, wherein the first user is represented in the messaging application by an avatar of the user that distinguishes the first user of the device from other users; while displaying the messaging user interface, receive a first request to display a sticker user interface for selecting stickers to send to a second user; in response to the first request to display the sticker user interface, display a sticker user interface that includes a first plurality of avatar stickers generated based on the avatar of the user, including concurrently displaying, on the display: a first avatar sticker generated based on a modification of the avatar that represents the user, and a second avatar sticker generated based on a modification of the avatar that represents the user and is different from the first avatar sticker; while displaying the plurality affordance for the avatar selection interface on the display, detect, via the one or more input devices, a sequence of one or more inputs that corresponds to a request to send a respective avatar sticker from the first user to the second user via the messaging application; and in response to detecting the sequence of one or more inputs: in accordance with a determination that the sequence of one or more inputs corresponds to selection of the first avatar sticker, send the first avatar sticker to the second user from the first user to the second user via the messaging application; and in accordance with a determination that the sequence of one or more inputs corresponds to selection of the second avatar sticker, send the second avatar sticker from the first user to the second user via the messaging application.
In accordance with an embodiment, an electronic device with a display and a touch-sensitive surface displays, on the display, an avatar editing interface including an avatar having a plurality of editable features; while a respective feature of the plurality of editable features is a currently selected feature, detects, on the touch-sensitive surface a first gesture that includes movement of one or more contacts on the touch-sensitive surface; in response to detecting the first gesture: in accordance with a determination that the first gesture is a first type of gesture and that the respective feature is a first feature, updates the display of the avatar by modifying a first characteristic of the first feature, wherein the first characteristic of the first feature is associated with the first gesture type; and in accordance with a determination that the first gesture is a second type of gesture that is different from the first type of gesture and that the respective feature is the first feature, updates the display of the avatar by modifying a second characteristic of the first feature that is different from the first characteristic of the first feature, wherein the second characteristic of the first feature is associated with the second gesture type.
A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by one or more processors of an electronic device with a display and one or more input devices, cause the device to: display, on the display, an avatar editing interface including an avatar having a plurality of editable features, while a respective feature of the plurality of editable features is a currently selected feature, detect, on the touch-sensitive surface a first gesture that includes movement of one or more contacts on the touch-sensitive surface; in response to detecting the first gesture: in accordance with a determination that the first gesture is a first type of gesture and that the respective feature is a first feature, update the display of the avatar by modifying a first characteristic of the first feature, wherein the first characteristic of the first feature is associated with the first gesture type; and in accordance with a determination that the first gesture is a second type of gesture that is different from the first type of gesture and that the respective feature is the first feature, update the display of the avatar by modifying a second characteristic of the first feature that is different from the first characteristic of the first feature, wherein the second characteristic of the first feature is associated with the second gesture type.
Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
Thus, devices are provided with faster, more efficient methods and interfaces for avatar creation and editing, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for avatar creation and editing.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
There is a need for electronic devices that provide efficient methods and interfaces for avatar creation and editing. For example, while programs already exist for creating and editing avatars, these programs are inefficient and difficult to use compared to the techniques below, which allow a user to create and edit avatars to be as realistic or unrealistic as necessary. Such techniques can reduce the cognitive burden on a user who creates and edits an avatar, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
Below,
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
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 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 module 137, e-mail client module 140, instant messaging (IM) module 141, browser module 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 module 138 for use in location-based dialing; to camera module 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 module 138, video conference module 139, e-mail client module 140, or IM module 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.
Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
Attention is now directed towards embodiments of user interfaces (“UP”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
In
In
Subsequent to (or in response to), successfully authenticating the entered username and password, device starts a profile picture creation process, as depicted in
Placeholder avatar 617 is a silhouette or mannequin that does not represent specific characteristics of the user, except for, in some examples, the gender of the user. For example, placeholder avatar 617 optionally is an outline of a generic person and does not depend on detected characteristics (e.g., skin tone, face shape, or hair style) of the user (e.g., as detected by captured image data). In response to the user selecting to continue the avatar creation process, for example, via touch 619 on affordance 618, device 600 determines the relative positioning of the user with respect to the field of view of the camera. If the user is properly aligned with the field of view, device 600 captures image data of the user using camera 602 and/or other sensors. If, however, the user is not properly aligned, device 600 updates avatar creation interface 615, such as depicted in
In
Device 600 continues to evaluate image data to determine whether image criteria are met. If the criteria are not met, device 600 updates avatar creation interface 615 to provide additional user feedback, such as seen in
Specifically, in
Similarly, in
In
As depicted in
Once device 600 has captured sufficient image data to generate an avatar for the user, avatar creation interface 615 is updated as depicted in
In
As described below, method 700 provides an intuitive way for creating a user avatar. The method reduces the cognitive burden on a user for creating a user avatar, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to create avatars faster and more efficiently conserves power and increases the time between battery charges.
An electronic device (e.g., device 600 of
While displaying the placeholder avatar, the electronic device detects (704) movement of the user to a second position with respect to the field of view of the one or more cameras. For example, optionally, the electronic device uses image data from a camera (e.g., 602) to determine when the user is in a different relative position with the electronic device. In some embodiments, the first image data includes both still data (e.g., a single image) and video data (e.g., a series of sequential images). In some embodiments, instead of the electronic device detecting movement of the user, the electronic device is continuously evaluating captured image data to determine if the image criteria (described below) are met.
In response to detecting the movement of the user (706) to the second position with respect to the field of view of the one or more cameras the electronic device: in accordance with a determination that the second position of the user with respect to the field of view of the one or more cameras (e.g., 602) meets the first set of image criteria (e.g., as shown in
In accordance with some embodiments, the electronic device, after capturing the first image data, generates (714) a user-specific avatar (e.g., 624, 625) (e.g., a 2D or 3D model with features that reflect the user's features) that contains features selected based on an appearance of the user determined based on the first image data (e.g., generating a 3D avatar representing the user based on at least the first image data and the second image data). In some examples, the avatar reflects characteristics of the user such as skin tone, eye color, hair color, hair style, and facial hair. In some examples, generating the user-specific avatar occurs after capturing additional image data (e.g., from one or more additional positions of the user) and the generation of the user-specific avatar is further based on the additional image data. In some examples, the user-specific avatar includes only a head. In some examples, the user-specific avatar includes a head, neck, shoulders, and part of a torso. In some examples, the user-specific avatar is a full-body avatar.
In accordance with some embodiments, the electronic device displays the generated user-specific avatar (e.g., 624, 625) on the display (e.g.,
In accordance with some embodiments, the electronic device displays (716) a view finder graphical element (e.g., 616) (e.g., a circle representing the middle of the field of view of the one or more cameras) concurrently with the display of the placeholder avatar (e.g., 617), wherein the display of the view finder graphical element, relative to the display of the placeholder avatar, is based on first or second position of the user with respect to the field of view of the one or more cameras (e.g.,
In accordance with some embodiments, the electronic device determines whether the second position (e.g., orientation, user proximity, user position within the one or more cameras' field of view, and/or lighting of the user) of the user with respect to the field of view of the one or more cameras (e.g., 602) meets the first set of image criteria (e.g., criteria about proximity to the one or more cameras, orientation of the user, lighting, or relative position of the user to the one or more cameras). By determining whether second image data meets image criteria, the electronic device provides an enhanced avatar creation process that avoids using low quality or incorrect image data. Additionally, by providing feedback to the user regarding the image data, the electronic device is more likely to capture the image data needed to efficiently generate an accurate avatar of the user. Eliminating the use of incorrect or low quality image data makes the electronic device more efficient, reduces power usage, and improves battery life of the device.
In accordance with some embodiments the electronic device, after capturing the first image data, provides second guidance (e.g., 623) to the user to change position with respect to the electronic device to a second target position (e.g., displaying the user outline with a rotation to indicate that the user should rotate their head or displaying textual or other visual instructions to rotate the user's head); updates the display of the placeholder avatar (e.g.,
In accordance with some embodiments, the first guidance (e.g., 620-622) is provided to the user (712) without changing an appearance of the placeholder avatar (e.g., 617 in
In accordance with some embodiments, providing the first guidance (e.g., 620-622) includes providing user feedback (e.g., haptic feedback, visual feedback, or audible feedback) when the second position of the user with respect to the field of view of the one or more cameras meets the first set of image criteria or providing instructions (e.g., textual instructions, animated instructions, or audio instructions) based on how the user should be positioned relative to the field of view of the one or more cameras (e.g., instruction the user to either move the electronic device or reposition themselves) to be in the first target position with respect to the device. By providing user feedback when the first set of image criteria are met, the usability of the electronic device is enhanced by keeping the user informed of the creation process.
In accordance with some embodiments, the electronic device, after capturing (718) the first image data (e.g., displaying a calculated skin tone based on the first image data or displaying a range of skin tones based on the first image data) displays (720) information (e.g.,
In accordance with some embodiments, displaying (722) information indicating one or more suggested skin tone colors selected based on the first image data is displayed without applying any of the suggested skin tone colors to an avatar. In some embodiments the electronic device generates the user-specific placeholder avatar (e.g., 624) based the first image data and using a predetermined skin tone color independent of the first image data (e.g., generating a black and white avatar that has shapes and features that resemble the user in the first image data without any skin tone coloring); and displays the user-specific placeholder avatar prior to receiving the user input confirming the respective suggested skin tone color. In some examples, generating the user-specific avatar occurs after capturing additional image data (e.g., from one or more additional positions of the user) and the generation of the user-specific avatar is further based on the additional image data. By allowing a user to select a new skin tone before painting the generated avatar, the electronic device provides a more accessible avatar creation process that reduces the risk of a user being disappointed with the skin tone that was selected based on the captured image data. This reduces the likelihood that the user will have to repeat the avatar creation process, which makes the electronic device more efficient, reduces power usage, and improves battery life of the device.
In accordance with some embodiments the electronic device, in response to capturing the first image data, updates a display of a progress indicator (e.g., an indicator around the view finder graphical element or a bar indicator), wherein the display of the progress indicator is based on the amount of avatar image data captured. In some examples, the progress indicator indicates progress towards achieving a target amount of image data for generating an avatar.
In accordance with some embodiments the electronic device captures image data of the user (e.g., the first image data or other image data) and, in accordance with a determination that the image data of the user fails to meet a lighting criteria (
In accordance with some embodiments the electronic device determines a physical feature (e.g., a hair style, facial hair, or eye color) or an accessory feature (e.g., eye glasses, piercings, or tattoos) of the user based on the first image data, and generates the user-specific avatar includes adding a representation of the physical feature or the accessory feature to the user-specific avatar (e.g.,
In accordance with some embodiments, generating the user-specific avatar based on the first image data includes generating a plurality of avatars and wherein the plurality of avatars include a first avatar and a second avatar different than the first avatar, and the electronic device displays the plurality of avatars and receives user input selecting one of the plurality of avatars. In some examples, each of the avatars in the plurality of avatars is different. In some examples, the plurality of avatars different based on variations to a predefined set of characteristics for the avatar.
In accordance with some embodiments the electronic device, after generating the user-specific avatar, stores the avatar as a recipe (e.g., a non-graphical representation of the avatar), wherein the recipe defines the avatar structure (e.g., eyes, nose, mouth, glasses) and avatar parameters (e.g., eye color, nose size, mouth shape, glasses type). By storing the user-specific avatar as a recipe, the electronic device is able to more efficiently store and transmit the user-specific avatar by sending smaller amounts of data, such as only have to send changes to the user-specific avatar recipe instead of the entire user-specific avatar recipe. Thus, the electronic device is more efficient, reduces power usage, and improves battery life of the device.
Note that details of the processes described above with respect to method 700 (e.g.,
In accordance with some embodiments,
As shown in
The processing unit 806 is configured to display (e.g., using display enabling unit 810) a placeholder avatar on the display, wherein the display of the placeholder avatar is based on a first position of a user with respect to a field of view of the one or more cameras of the electronic device. The processing unit 806 is configured to, while displaying the placeholder avatar, detect (e.g., using detecting unit 812) movement of the user to a second position with respect to the field of view of the one or more cameras. In response to detecting the movement of the user to the second position with respect to the field of view of the one or more cameras, the processing unit 806 is configured to: in accordance with a determination that the second position of the user with respect to the field of view of the one or more cameras meets the first set of image criteria, capture (e.g., using image capturing unit 814) first image data of the user with the one or more cameras, and in accordance with a determination that the second position of the user with respect to the field of view of the one or more cameras does not meet the first set of image criteria and while continuing to display the placeholder avatar, provide (e.g., using providing unit 816) first guidance to the user to change position with respect to the electronic device to a first target position.
In some embodiments, the processing unit 806 is further configured to, after capturing the first image data, generating (e.g., using generating unit 818) a user-specific avatar that contains features selected based on an appearance of the user determined based on the first image data.
In some embodiments, the processing unit 806 is further configured to display (e.g., using display enabling unit 810) the generated user-specific avatar on the display.
In some embodiments, the processing unit 806 is further configured to display (e.g., using display enabling unit 810) a view finder graphical element concurrently with the display of the placeholder avatar, wherein the display of the view finder graphical element, relative to the display of the placeholder avatar, is based on first or second position of the user with respect to the field of view of the one or more cameras.
In some embodiments, the processing unit 806 is further configured to determine (e.g., using determining unit 820) whether the second position of the user with respect to the field of view of the one or more cameras meets the first set of image criteria.
In some embodiments, the processing unit 806 is further configured to, after capturing the first image data, provide (e.g., using providing unit 816) second guidance to the user to change position with respect to the electronic device to a second target position; update (e.g., using updating unit 822) the display of the placeholder avatar based on image data captured after the first image data; after providing the second guidance, determine (e.g., using determining unit 820) whether a third position of the user with respect to the electronic device meets a second set of image criteria; in accordance with a determination that the second detected position meets the second set of image criteria, capture (e.g., using image capturing unit 814) second image data of the user with the one or more cameras; and in accordance with a determination that the second detected position does not meet the second set of image criteria, continue to provide (e.g., using providing unit 816) the second guidance to the user to change position with respect to the electronic device to the second target position.
In some embodiments the first guidance is provided to the user without changing an appearance of the placeholder avatar based on the first image data.
In some embodiments providing the first guidance includes providing user feedback when the second position of the user with respect to the field of view of the one or more cameras meets the first set of image criteria or providing instructions based on how the user should be positioned relative to the field of view of the one or more cameras to be in the first target position with respect to the device.
In some embodiments, the processing unit 806 is further configured to, after capturing the first image data: display (e.g., using display enabling unit 810) information indicating one or more suggested skin tone colors selected based on the first image data; receive (e.g., using receiving unit 824) user input confirming a respective suggested skin tone color of the one or more skin tone colors selected base on the first image data; and wherein generating the user-specific avatar is further based on the suggested skin tone color.
In some embodiments displaying information indicating one or more suggested skin tone colors selected based on the first image data is displayed without applying any of the suggested skin tone colors to an avatar.
In some embodiments, the processing unit 806 is further configured to generate (e.g., using generating unit 818) the user-specific placeholder avatar based the first image data and using a predetermined skin tone color independent of the first image data; and display (e.g., using display enabling unit 810) the user-specific placeholder avatar prior to receiving the user input confirming the respective suggested skin tone color.
In some embodiments, the processing unit 806 is further configured to, in response to capturing the first image data, update (e.g., using updating unit 822) a display of a progress indicator, wherein the display of the progress indicator is based on the amount of avatar image data captured.
In some embodiments the first image data includes both still data and video data.
In some embodiments, the processing unit 806 is further configured to capture (e.g., using image capturing unit 814) image data of the user; and in accordance with a determination that the image data of the user fails to meet a lighting criteria, display (e.g., using display enabling unit 810) instructions for the user to change the lighting for the field of view of the one or more cameras.
In some embodiments, the processing unit 806 is further configured to determine (e.g., using determining unit 820) a physical feature or an accessory feature of the user based on the first image data, and generating the user-specific avatar includes adding a representation of the physical feature or the accessory feature to the user-specific avatar.
In some embodiments the user-specific avatar is expression independent regardless of whether the user has an expression in the first image data.
In some embodiments generating the user-specific avatar based on the first image data includes generating a plurality of avatars and wherein the plurality of avatars include a first avatar and a second avatar different than the first avatar, the processing unit further configured to: display (e.g., using display enabling unit 810) the plurality of avatars; and receive (e.g., using receiving unit 824) user input selecting one of the plurality of avatars.
In some embodiments, the processing unit 806 is further configured to, after generating the user-specific avatar, store (e.g., using storing unit 826) the avatar as a recipe, wherein the recipe defines the avatar structure and avatar parameters.
In some embodiments the placeholder avatar is a predetermined silhouette of a person independent of the image data of the user.
The operations described above with reference to
In
Feature-selection control region 900B includes a ribbon of feature representations 907-911. Each representation corresponds to a feature (e.g., eyes, ears, nose, face, eyeglasses, hair, chin, eyebrows) for avatar 901. If additional feature representations are available but cannot be display due to space constraints, device 600 displays the additional feature representations in response to user input, such as a swipe on feature-selection control region 900B. Additionally, feature-control region 900B includes an indicator showing the currently selected avatar feature. In the case of
Feature-option control region 900C includes a ribbon of option representations 902-906 that correspond to different available options for the selected avatar feature. For example, in
As described below, method 1000 provides an intuitive way for customizing a user avatar. The method reduces the cognitive burden on a user for customizing a user avatar, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to customizing a user avatar faster and more efficiently conserves power and increases the time between battery charges.
An electronic device (e.g., device 600 of
While displaying the avatar editing user interface, the electronic device detects (1004) an input in the avatar editing user interface (e.g., 912). In response to detecting the input (1006) and in accordance with a determination that the input corresponds to selection of the second avatar feature (e.g., 908 in
In accordance with a determination that the input (e.g., 923) corresponds to selection of the second option (e.g., 917) for the first avatar feature in the feature-option control region (1014), the electronic device updates (1016) the feature-option control region to indicate that the second option for the first avatar feature is currently selected (
In accordance with some embodiments, displaying the avatar editing user interface further includes the electronic device concurrently displaying on the display a color-selection region (e.g., 900D) that includes representations of a plurality of color options (e.g., 918-922) for the first avatar feature, including a first color that is currently selected (e.g., 920) and a second color (e.g., 918, 919, 921, or 922) that is not currently selected, wherein the color-selection region is displayed concurrently with the avatar (e.g., 901), the feature-selection control region (e.g., 900B), and the feature-option control region (e.g., 900C). In some embodiments the electronic device, while displaying the color-selection region, in response to detection of a user input (e.g., 924) corresponding to selection of the second color (e.g., 922), updating the display of the first avatar feature in the avatar based on the second color (e.g.,
In accordance with some embodiments, the first avatar feature is avatar clothing (e.g., a shirt, hat, or tie) and updating the display of the first avatar feature in the avatar based on the second color includes updating the color of the avatar clothing to the second color (e.g., changing the entire color of the clothing or some portion of the clothing, such as a color of part of a clothing pattern). In some embodiments, the first avatar feature (e.g., 924) is an avatar accessory (e.g., glasses, a hat, piercing, or jewelry).
In accordance with some embodiments, the display is a touch-sensitive display and the electronic device, in response to receiving a gesture (e.g., a touch-and-drag gesture or a pinch gesture) on the touch-sensitive display, modifies a characteristic of first avatar feature based on the gesture; and updates the display of the avatar based on the modified parameter. In some examples, the received gesture is a pinch gesture, a touch-and-drag gesture, or other type of gesture. In some embodiments, the modification occurs in accordance with the processes described with respect to
In accordance with some embodiments the electronic device displays an avatar management interface including a plurality of previously saved avatars (e.g., a 3×3 listing of avatars); receives user input selecting a previously saved avatar; and in response to the user input selecting the previously save avatar, displays the previously saved avatar in the avatar editing user interface. By providing for different variations of a generated avatar, the electronic device provides enhances the avatar editing process by making it faster for a user to select an avatar that the user is comfortable sharing as representative of the user, which makes the electronic device more efficient, reduces power usage, and improves battery life of the device.
In accordance with some embodiments the electronic device, after updating the avatar to change the appearance of the first avatar feature in accordance with the second option for the first avatar feature, stores the avatar as an avatar recipe (e.g., a non-graphical representation of the avatar), wherein the avatar recipe defines avatar structure, including the second option, (e.g., eyes, nose, mouth, glasses) and avatar parameters (e.g., eye color, nose size, mouth shape, glasses type).
In accordance with some embodiments the electronic device sends the avatar recipe to a contact. In some examples, the avatar recipe is sent to another user in response to a user input corresponding to a request to send the avatar recipe to the other user. For example, the avatar recipe is sent to another user as described below with respect to process 1300 of
In accordance with some embodiments, the electronic device, in accordance with not detecting, via the one or more input devices, input associated with the avatar editing user interface for a predetermined period of time (e.g., after a predetermined period of time after lift-off, after the user breaks contact with the touch screen), updates the display of the avatar with an avatar animation.
In accordance with some embodiments, the electronic device updates the avatar to change the appearance of the first avatar feature in accordance with the second option for the first avatar feature (e.g., in
In some embodiments, the electronic device, while displaying the avatar, in response to detecting input via one or more input devices of the electronic device (e.g., a mouse cursor or touch), updates the eyes of the avatar based on a position associated with the input (e.g., the position of a cursor on the screen or the position of a touch input). In some embodiments, the electronic device updates the avatar based on an animation loop, wherein the animation loop includes a series of expressions for the avatar. In some embodiments, the animation loop has a time duration and the electronic device determines a random time offset less than the time duration, wherein updating the avatar based on the animation loop includes updating the avatar starting at a position in the animation loop based on the random time offset (e.g., to avoid synchronization of the animation loop with other avatars that are displaying the same animation loop). In some embodiments, the electronic device ceases to update the avatar based on the animation loop after a predetermined period of time. By animating an avatar according to an animation loop with a random beginning time, the electronic device is enhanced by ensuring that multiple avatars (e.g., avatars for different users) displayed together are not animated in unison. This increases the likelihood that the user will sustain interaction with the avatar in the customization process or in other situations.
In accordance with some embodiments,
As shown in
The processing unit 1106 is configured to display (e.g., using display enabling unit 1110) an avatar editing user interface that includes concurrently displaying, the display includes: an avatar having a plurality of editable features; a feature-selection control region that includes representations of a plurality of avatar features, including a first avatar feature that is currently selected for modification and a second avatar feature that is not currently selected for modification; a feature-option control region that includes representations of a plurality of options for the first avatar feature for selection including a first option for the first avatar feature that is currently selected and a second option for the first avatar feature that is not currently selected. The processing unit 1106 is further configured to, while displaying the avatar editing user interface, detect (e.g., using detecting unit 1112) an input in the avatar editing user interface. In response to detecting the input, the processing unit 1106 is configured to, in accordance with a determination that the input corresponds to selection of the second avatar feature in the feature-selection control region, update (e.g., using updating unit 1114) the feature-selection control region to indicate that the second avatar feature is currently selected; and update (e.g., using updating unit 1114) the feature-option control region to include representations of a plurality of options for the second avatar feature for selection including a first option for the second avatar feature that is currently selected and a second option for the second avatar feature that is not currently selected. The processing unit 1106 is further configured to, in accordance with a determination that the input corresponds to selection of the second option for the first avatar feature in the feature-option control region, update (e.g., using updating unit 1114) the feature-option control region to indicate that the second option for the first avatar feature is currently selected; and update (e.g., using updating unit 1114) the avatar to change the appearance of the first avatar feature in accordance with the second option for the first avatar feature.
In some embodiments, in response to detecting the input and in accordance with a determination that the input corresponds to selection of the second option for the first avatar feature in the feature-option control region, the feature-option control region is updated without updating the avatar-feature control region.
In some embodiments, in response to detecting the input and in accordance with a determination that the input corresponds to selection of the second avatar feature in the feature-selection control region, the feature-selection control region is updated without updating the avatar.
In some embodiments, the display of the avatar editing user interface further includes concurrently display on the display of a color-selection region that includes representations of a plurality of color options for the first avatar feature, including a first color that is currently selected and a second color that is not currently selected, wherein the color-selection region is displayed concurrently with the avatar, the feature-selection control region, and the feature-option control region.
In some embodiments the processing unit 1106 is further configured to, while displaying the color-selection region, in response to detection of a user input corresponding to selection of the second color, update (e.g., using updating unit 1114) the display of the first avatar feature in the avatar based on the second color.
In some embodiments, the first avatar feature is avatar clothing and updating the display of the first avatar feature in the avatar based on the second color includes updating the color of the avatar clothing to the second color.
In some embodiments, the first avatar feature is an avatar accessory.
In some embodiments, the display unit is a touch-sensitive display unit, the processing unit 1106 further configured to, in response to receiving a gesture on the touch-sensitive display, modify (e.g., using modifying unit 1116) a characteristic of first avatar feature based on the gesture; and update (e.g., using updating unit 1114) the display of the avatar based on the modified parameter.
In some embodiments the processing unit 1106 is further configured to display (e.g., using display enabling unit 1110) an avatar management interface including a plurality of previously saved avatars; and receive (e.g., using receiving unit 1118) user input selecting a previously saved avatar; and in response the user input selecting the previously save avatar, display (e.g., using display enabling unit 1110) the previously saved avatar in the avatar editing user interface.
In some embodiments the processing unit 1106 is further configured to, after updating the avatar to change the appearance of the first avatar feature in accordance with the second option for the first avatar feature, store (e.g., using storing unit 1120) the avatar as an avatar recipe, wherein the avatar recipe defines avatar structure, including the second option, and avatar parameters.
In some embodiments the processing unit 1106 is further configured to send (e.g., using sending unit 1122) the avatar recipe to a contact.
In some embodiments the processing unit 1106 is further configured to receive (e.g., using receiving unit 1118) an avatar recipe for a first contact; and display (e.g., using display enabling unit 1110) a contact information for a plurality of contacts, including the first contact, wherein the contact information displayed for the first contact includes an avatar based on the avatar recipe for the first contact.
In some embodiments, the display of the avatar includes an indicator for the first avatar feature when the first avatar feature is currently selected.
In some embodiments, the representations in the feature-selection control region have a shape based on the shape of their respective avatar features.
In some embodiments, the representations in the feature-option control region have a shape based on the shape of their respective avatar feature options.
In some embodiments the processing unit 1106 is further configured to, in accordance with not detecting, via the one or more input devices, input associated with the avatar editing user interface for a predetermined period of time, update (e.g., using updating unit 1114) the display of the avatar with an avatar animation.
In some embodiments, updating the avatar to change the appearance of the first avatar feature in accordance with the second option for the first avatar feature includes modifying an expression of the avatar based on the second option.
In some embodiments the processing unit 1106 is further configured to, while displaying the avatar, in response to detecting input via one or more input devices of the electronic device, update (e.g., using updating unit 1114) the eyes of the avatar based on a position associated with the input.
In some embodiments the processing unit 1106 is further configured to update (e.g., using updating unit 1114) the avatar based on an animation loop, wherein the animation loop includes a series of expressions for the avatar.
In some embodiments the animation loop has a time duration and the processing unit 1106 is further configured to determine (e.g., using determining unit 1124) a random time offset less than the time duration, wherein updating the avatar based on the animation loop includes updating the avatar starting at a position in the animation loop based on the random time offset.
In some embodiments the processing unit 1106 is further configured to cease to update the avatar based on the animation loop after a predetermined period of time.
In some embodiments, updating the avatar to change the appearance of the first avatar feature in accordance with the second option for the first avatar feature includes transitioning the first avatar feature based on the first option to the first avatar feature based on the second option via an animation.
The operations described above with reference to
In
Messaging interface 1203 includes message area 1208, which is empty in
As depicted in
As depicted in
Once the user is done entering text in text entry field 1213, the user indicates that the message is ready to be sent by, for example, selecting send button 1220 via touch 1221 on display 1201. In response, device 1200 prepares the message that includes, in the example of
As depicted in
The stickers in sticker interface 1227 are, optionally, generated based on context obtained from, for example, device 600 (e.g., location, weather at the location, calendar appointments) or the messaging interface (e.g., messages that have already been received or sent, and/or message text that has been entered but not sent, and/or the recipient of the sticker).
In
In response to device 600 receiving drag and drop gesture 1231, which drags sticker 1230 from sticker interface 1227 to text box 1224, a sticker is attached to text box 1223. Specifically, sticker 1232, which is identical to sticker 1230 in
In response to a selection of sticker 1229 via, for example, touch 1234, sticker 1229 and the already entered text portion of the message are sent to Joe and displayed in messaging interface 1203 as text box 1235 and sticker 1236, as depicted in
As described below, method 1300 provides an intuitive way for using avatar stickers in messages. The method reduces the cognitive burden on a user for using avatar stickers in messages, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to use avatar stickers in messages faster and more efficiently conserves power and increases the time between battery charges.
An electronic device (e.g., device 600 of
In response to the first request to display the sticker user interface, the electronic device displays (1306) a sticker user interface that includes a first plurality of avatar stickers (e.g., 1228-1230) generated based on the avatar of the user, including concurrently displaying, on the display: a first avatar sticker (e.g., 1228) generated based on a modification (e.g., to generate an avatar sticker avatar recipe parameters are added, changed, and/or removed from the avatar recipe to generate avatar stickers) of the avatar that represents the user (e.g., 1223) (e.g., modified to be smiling, have an umbrella, or to be running), and a second avatar sticker (e.g., 1229) generated based on a modification of the avatar that represents the user and is different from the first avatar sticker. By modifying an existing avatar to produce avatar stickers for a user, the electronic device is able to operate more efficiently and has more flexibility by being able to change what stickers are generated and/or displayed without having to first generate a baseline avatar, which makes the electronic device more efficient, reduces power usage, and improves battery life of the device.
The electronic device, while displaying the plurality affordance for the avatar selection interface on the display, detects (1308), via the one or more input devices (e.g., display 601), a sequence of one or more inputs (e.g., gesture 1231 or 1234) that corresponds to a request to send a respective avatar sticker (1230) from the first user to the second user via the messaging application. In some examples, the sequence of one or more inputs corresponds to a gesture that selects a sticker, drags the sticker to a particular location in the messaging interface, and releases the selected sticker. In some examples, the sequence of one or more inputs is a tap gesture of a selected sticker for sending to another user.
In response to detecting the sequence of one or more inputs (1310): the electronic device, in accordance with a determination that the sequence of one or more inputs corresponds to selection of the first avatar sticker, sends (1312) the first avatar sticker to the second user from the first user to the second user via the messaging application (e.g.,
In accordance with some embodiments, the avatar of the user is based on an avatar recipe (1316) (e.g., a non-graphical representation of the avatar). In some examples, the avatar recipe is a structured document, such as XML, that defines avatar features and avatar parameters that are used to generate the avatar. In some embodiments, the first avatar sticker was generated (1318) by modifying a first parameter of the avatar recipe for the avatar of the user. In some embodiments, the first avatar sticker (e.g., 1228) is animated (e.g., in the first avatar sticker, the avatar is waving, winking, or being rained on). In some embodiments, the second avatar sticker (e.g., 1230) includes a prop (e.g., an umbrella, a flag, or other object besides the avatar or objects normally associated with the avatar, such as eyeglasses). In some examples, the avatar recipe for the avatar of the user includes a parameter representing an expression or emotion of the user. Optionally, the addition of an expression or emotion parameter to the avatar recipe will affect how multiple features in the first avatar sticker are generated. In one example, a happy emotion changes the appearance of the mouth, eyes, and contour of the face in the corresponding first avatar sticker as compared to the appearance of these features in an avatar sticker generated from an unmodified sticker. In some embodiments, the second avatar sticker was generated (1320) by adding a second parameter to the avatar recipe for the avatar of the user. In some examples, a parameter is added to the avatar recipe, such as a parameter representing an accessory for the avatar. In one example, an umbrella parameter is added so that the avatar sticker will include the avatar generated from the avatar recipe under an umbrella. In some embodiments, sending the first avatar sticker to the second user includes sending a recipe representing the first avatar sticker to the user. By using an avatar recipe to generate and/or transmit the avatar stickers, smaller amounts of data can be transmitted faster and processing requirements are lower, which improves the performance (e.g., battery life and responsiveness) of the electronic devices involved.
In accordance with some embodiments, as part of sending the first avatar sticker to the second user from the first user to the second user via the messaging application the electronic device, in accordance with a determination that a device associated with the second user supports avatar recipes (e.g., the device is using the same messaging application as the first user or a different, compatible messaging application), sends (1322) the first avatar sticker to the second user includes sending a recipe representing the first avatar sticker to the user and in accordance with a determination that the device associated with the second user does not support avatar recipes, sends (1324) a graphical representation of the first avatar sticker to the user. By sending the first avatar stick as a recipe, the electronic device is able to send less data and send it more quickly as compared to sending a graphical representation, which improves the efficient and performance of the electronic device. Additionally, in some embodiments, the data can be reduced even more by only sending the additions or modification to a baseline avatar for the user of the electronic device that the recipient's electronic device already has access to.
In accordance with some embodiments, the sticker user interface is displayed concurrently with at least a portion of the messaging interface (e.g.,
In accordance with some embodiments, the electronic device, prior to receiving the request to display the sticker user interface, receives user input for a textual portion (e.g., 1213) of a user message and sends the textual portion of the user message to the second user via the messaging application after detecting the sequence of one or more inputs (e.g.,
In accordance with some embodiments, the electronic device, after sending the first avatar sticker or the second avatar sticker, while displaying the plurality affordance for the avatar selection interface on the display, detecting, via the one or more input devices, a second sequence of one or more inputs that corresponds to a request to send a respective avatar sticker from the first user to the second user via the messaging application (e.g.,
In accordance with some embodiments,
As shown in
The processing unit 1406 is configured to display (e.g., using display enabling unit 1410) a messaging interface for a messaging application for transmitting messages between a first user of the device and other users, wherein the first user is represented in the messaging application by an avatar of the user that distinguishes the first user of the device from other users. The processing unit 1406 is further configured to, while displaying the messaging user interface, receive (e.g., using receiving unit 1412) a first request to display a sticker user interface for selecting stickers to send to a second user. In response to the first request to display the sticker user interface, the processing unit 1406 is configured to display (e.g., using display enabling unit 1410) a sticker user interface that includes a first plurality of avatar stickers generated based on the avatar of the user, including concurrently displaying, on the display unit: a first avatar sticker generated based on a modification of the avatar that represents the user, and a second avatar sticker generated based on a modification of the avatar that represents the user and is different from the first avatar sticker. The processing unit 1406 is configured to while displaying the plurality affordance for the avatar selection interface on the display, detect (e.g., using detecting unit 1414), via the one or more input devices, a sequence of one or more inputs that corresponds to a request to send a respective avatar sticker from the first user to the second user via the messaging application. In response to detecting the sequence of one or more inputs: the processing unit 1406 is configured to, in accordance with a determination that the sequence of one or more inputs corresponds to selection of the first avatar sticker, send (e.g., using sending unit 1416) the first avatar sticker to the second user from the first user to the second user via the messaging application; and in accordance with a determination that the sequence of one or more inputs corresponds to selection of the second avatar sticker, send (e.g., using sending unit 1416) the second avatar sticker from the first user to the second user via the messaging application.
In some embodiments, the avatar of the user is based on an avatar recipe. In some embodiments, the first avatar sticker was generated by modifying a first parameter of the avatar recipe for the avatar of the user. In some embodiments, the second avatar sticker was generated by adding a second parameter (e.g., a parameter adding an accessory or specifying a facial expression) to the avatar recipe for the avatar of the user. In some embodiments, sending the first avatar sticker to the second user includes sending a recipe representing the first avatar sticker to the second user.
In some embodiments, the processing unit 1406 being configured to send the first avatar sticker to the second user from the first user to the second user via the messaging application further comprises the processing unit 1406 being further configured to, in accordance with a determination that a device associated with the second user supports avatar recipes, send (e.g., using sending unit 1416) the first avatar sticker to the second user includes sending a recipe representing the first avatar sticker to the user; and in accordance with a determination that the device associated with the second user does not support avatar recipes, send (e.g., using sending unit 1416) a graphical representation of the first avatar sticker to the user.
In some embodiments, the sticker user interface is displayed concurrently with at least a portion of the messaging interface. In some embodiments, the first avatar sticker is animated. In some embodiments, the second avatar sticker includes a prop.
In some embodiments the processing unit 1406 is further configured to, prior to receiving the request to display the sticker user interface, receive (e.g., using receiving unit 1418) user input for a textual portion of a user message; and send (e.g., using sending unit 1416) the textual portion of the user message to the second user via the messaging application after detecting the sequence of one or more inputs.
In some embodiments the processing unit 1406 is further configured to, after sending the first avatar sticker or the second avatar sticker, while displaying the plurality affordance for the avatar selection interface on the display, detect, via the one or more input devices, a second sequence of one or more inputs that corresponds to a request to send a respective avatar sticker from the first user to the second user via the messaging application; and in response to detecting the second sequence of one or more inputs, in accordance with a determination that the sequence of one or more inputs corresponds to selection of the second avatar sticker, send the second avatar sticker from the first user to the second user via the messaging application.
The operations described above with reference to
In
Avatar customization interface 1500 also includes indicators 1512 that provide a visual indication of what avatar feature is currently selected for editing in the feature-selection control region. In some embodiments, other indicators are used, such as highlighting, circles, movement of the feature, and/or other styles of indicators.
Avatar customization interface 1500 enables editing of the selected avatar feature in response to gestures received on display 601 when display 601 is a touch sensitive display. Device 600 determines the appropriate modification to avatar 1501 based on any of several factors, including the type of gesture (e.g., tap, pinch, drag, rotation), the direction (e.g., vertical, horizontal, clockwise, counter clockwise, expanding, squeezing), the currently selected avatar feature, and/or the location of the gesture.
For example, if pinch gesture 1513 in
As another example, if vertical drag gesture 1514 of
If pinch gesture 1526 in
If vertical drag gesture 1527 of
As described below, method 1600 provides an intuitive way for using gestures to edit an avatar. The method reduces the cognitive burden on a user for using gestures to edit an avatar, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to use gestures to edit an avatar faster and more efficiently conserves power and increases the time between battery charges.
An electronic device has a display and a touch-sensitive surface. The electronic device displays (1602), on the display, an avatar editing interface (e.g., 1500) including an avatar (e.g., 1501) having a plurality of editable features (e.g., an avatar generated from the process described above or an avatar retrieved from memory or a remote server). In some embodiments, the avatar editing interface includes a first selection indicator with feature affordances (e.g., 1512) (e.g., hair, nose, eye brows, eyes, ears, glasses) of one or more of the plurality of editable features selectable for editing.
While a respective feature of the plurality of editable features is a currently selected feature (e.g., feature corresponding to representation 1508), the electronic device detects (1604), on the touch-sensitive surface, a first gesture (e.g., gesture 1513 or gesture 1514) (e.g., a swipe, a pinch, a drag, a rotation) that includes movement of one or more contacts on the touch-sensitive surface.
In response to detecting the first gesture (1606) and in accordance with a determination that the first gesture (e.g., 1513 or 1514) is a first type of gesture (e.g., a pinch) and that the respective feature is a first feature (e.g., ears), the electronic device updates (1608) the display of the avatar by modifying a first characteristic (e.g.,
In response to detecting the first gesture (e.g., 1526 or 1527) and in accordance with a determination that the gesture is a first type of gesture (e.g., a pinch gesture) and that the respective feature is a second feature (e.g., nose), the electronic device updates (1612) the display of the avatar by modifying a first characteristic (e.g.,
In accordance with some embodiments the electronic device, in response to detecting the first gesture (e.g., 1526 or 1527) and in accordance with a determination that the first gesture is a second type of gesture (e.g., vertical drag) that is different from the first type of gesture (e.g., a pinch) and that the respective feature is the second feature (e.g., nose), updates (1614) the display of the avatar by modifying a second characteristic (e.g.,
In accordance with some embodiments, the first type of gesture is a pinch gesture, the first feature is a nose, and wherein the first characteristic is the width of the nose. In some embodiments, the second type of gesture is a vertical drag and the second characteristic is the vertical position of the first feature. Examples of other gestures are described above with reference to Table 1.
In accordance with some embodiments, the electronic device, in accordance with a determination that the first gesture modifies the first characteristic beyond a first allowable range for the first characteristic, ceases to modify the first characteristic of the first feature. In some embodiments, the electronic device, during the first gesture, detects an input that corresponds to a modification of the first characteristic beyond an allowable range for the first characteristic. After modifying the first characteristic beyond the allowable range for the first characteristic, the electronic device detects an end of the gesture. In response to detecting the end of the first gesture, the electronic device updates the display of the avatar by modifying the first characteristic of the first feature to be within a second allowable range for the second characteristic. In some examples, user input is received that exceeds an allowable range for the characteristic. In response to the user input, the characteristic is modified beyond the allowable range for the characteristic. In response to the termination of the user input, the display of the characteristic reverts back to an edge or within the allowable range for the characteristic. By putting limits on the amount that certain features can be modified, the electronic device improves avatar customization by ensure that the user does not create an invalid avatar, which wastes resources (e.g., processing time or battery power) of the electronic device.
In accordance with some embodiments, the first gesture is detected at a location on the touch-sensitive surface that is distinct from the location at which the first feature is displayed (
In accordance with some embodiments, the electronic device receives (1616) user input selecting a preset characteristic set (e.g., 1519) for the respective feature (e.g., 1509) (e.g., a nose), wherein the preset characteristic set includes a value for the first characteristic (e.g., a nose width) and a value for a third characteristic (e.g., a nose length) without having any value for the second characteristic; and in response to receiving the user input, updates (1618) the display of the avatar based on the first value and the second value. In some examples, the preset characteristic set does not include any value for the second characteristic or includes a value for the second characteristic that is overridden by a previous user-set value for the second characteristic. In some embodiments, the third characteristic is not modifiable other than selection of one or more preset characteristic sets. In some embodiments, the display of the avatar based on the value for the first characteristic and the value for the third characteristic is based on a previously user-set value for the second characteristic. In some embodiments, the user input selecting the preset characteristic set is a selection of an affordance associated with the present characteristic, wherein the affordance has a shape representative of one or more values in the preset characteristic set. In some embodiments, in response to receiving the user input, the electronic device requests the preset characteristic set from a remote server. By using previously user-set parameters for a characteristic of an avatar feature, the electronic device enhances the avatar editing interface by minimizing the reentry of parameters and required interactions after a user selects a new preset for a given feature.
In accordance with some embodiments,
As shown in
The processing unit 1706 is configured to display (e.g., using display enabling unit 1710), on the display, an avatar editing interface including an avatar having a plurality of editable features. While a respective feature of the plurality of editable features is a currently selected feature, the processing unit 1706 is further configured to detect (e.g., using detecting unit 1712), on the touch-sensitive surface a first gesture that includes movement of one or more contacts on the touch-sensitive surface. In response to detecting the first gesture, the processing unit 1706 is further configured to, in accordance with a determination that the first gesture is a first type of gesture and that the respective feature is a first feature, update (e.g., using updating unit 1714) the display of the avatar by modifying a first characteristic of the first feature, wherein the first characteristic of the first feature is associated with the first gesture type; and in accordance with a determination that the first gesture is a second type of gesture that is different from the first type of gesture and that the respective feature is the first feature, update (e.g., using updating unit 1714) the display of the avatar by modifying a second characteristic of the first feature that is different from the first characteristic of the first feature, wherein the second characteristic of the first feature is associated with the second gesture type.
In some embodiments, the processing unit 1706 is further configured to, in response to detecting the first gesture and in accordance with a determination that the gesture is a first type of gesture and that the respective feature is a second feature, update (e.g., using updating unit 1714) the display of the avatar by modifying a first characteristic of the second feature, wherein the first characteristic of the second feature is associated with the first gesture type. In some embodiments, the first characteristic of the second feature is different from the first characteristic of the first feature.
In some embodiments, the processing unit 1706 is further configured to, in response to detecting the first gesture and in accordance with a determination that the first gesture is a second type of gesture that is different from the first type of gesture and that the respective feature is the second feature, update (e.g., using updating unit 1714) the display of the avatar by modifying a second characteristic of the second feature that is different from the first characteristic of the second feature, wherein the second characteristic of the second feature is associated with the second gesture type.
In some embodiments, the second characteristic of second feature is different from the second characteristic of the first feature. In some embodiments, the avatar editing interface includes a first selection indicator with feature affordances of one or more of the plurality of editable features selectable for editing. In some embodiments, the first type of gesture is a pinch gesture, the first feature is a nose, and wherein the first characteristic is the width of the nose. In some embodiments, the second type of gesture is a vertical drag and the second characteristic is the vertical position of the first feature.
In some embodiments, the processing unit 1706 is further configured to, in accordance with a determination that the first gesture modifies the first characteristic beyond a first allowable range for the first characteristic, cease to modify (e.g., using updating unit 1714) the first characteristic of the first feature.
In some embodiments, the processing unit 1706 is further configured to, during the first gesture, detect (e.g., using detecting unit 1712) an input that corresponds to a modification of the first characteristic beyond an allowable range for the first characteristic; after modifying the first characteristic beyond the allowable range for the first characteristic, detect (e.g., using detecting unit 1712) an end of the gesture; and in response to detecting the end of the first gesture, update (e.g., using updating unit 1714) the display of the avatar by modifying the first characteristic of the first feature to be within a second allowable range for the second characteristic.
In some embodiments, the first gesture is detected at a location on the touch-sensitive surface that is distinct from the location at which the first feature is displayed.
In some embodiments, the processing unit 1706 is further configured to receive (e.g., using receiving unit 1716) user input selecting a preset characteristic set for the respective feature, wherein the preset characteristic set includes a value for the first characteristic and a value for a third characteristic without having any value for the second characteristic; and in response to receiving the user input, update (e.g., using updating unit 1714) the display of the avatar based on the first value and the second value.
In some embodiments, the third characteristic is not modifiable other than selection of one or more preset characteristic sets. In some embodiments, the display of the avatar based on the value for the first characteristic and the value for the third characteristic is based on a previously user-set value for the second characteristic.
In some embodiments, the user input selecting the preset characteristic set is a selection of an affordance associated with the present characteristic, wherein the affordance has a shape representative of one or more values in the preset characteristic set.
In some embodiments, the processing unit 1706 is further configured to, in response to receiving the user input, request (e.g., using requesting unit 1718) the preset characteristic set from a remote server.
The operations described above with reference to
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
This application is a continuation of U.S. patent application Ser. No. 16/259,771, entitled “AVATAR CREATION AND EDITING”, filed Jan. 28, 2019, which is a continuation of U.S. patent application Ser. No. 15/713,490, now U.S. Pat. No. 10,362,219, entitled “AVATAR CREATION AND EDITING”, filed Sep. 22, 2017, which claims priority to U.S. Provisional Patent Application 62/399,294, entitled “AVATAR CREATION AND EDITING”, filed Sep. 23, 2016, the content of which are hereby incorporated by reference in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3633354 | Stemmler | Jan 1972 | A |
| 4847819 | Hong | Jul 1989 | A |
| 4945521 | Klaus | Jul 1990 | A |
| 5383165 | Vaucher | Jan 1995 | A |
| 6084598 | Chekerylla | Jul 2000 | A |
| 6272246 | Takai | Aug 2001 | B1 |
| 6351556 | Loui et al. | Feb 2002 | B1 |
| 6606411 | Loui et al. | Aug 2003 | B1 |
| 6621524 | Iijima et al. | Sep 2003 | B1 |
| 6915011 | Loui et al. | Jul 2005 | B2 |
| 7180524 | Axelrod | Feb 2007 | B1 |
| 7227976 | Jung et al. | Jun 2007 | B1 |
| 7325198 | Adcock et al. | Jan 2008 | B2 |
| 7421449 | Williams et al. | Sep 2008 | B2 |
| 7636733 | Rothmuller et al. | Dec 2009 | B1 |
| 7680340 | Luo et al. | Mar 2010 | B2 |
| 7716057 | Horvitz | May 2010 | B2 |
| 7716194 | Williams et al. | May 2010 | B2 |
| 7747625 | Gargi et al. | Jun 2010 | B2 |
| 7751285 | Cain et al. | Jul 2010 | B1 |
| 7788592 | Williams et al. | Aug 2010 | B2 |
| 7831100 | Gallagher et al. | Nov 2010 | B2 |
| 7840668 | Sylvain et al. | Nov 2010 | B1 |
| 7843454 | Biswas | Nov 2010 | B1 |
| 7908554 | Blattner | Mar 2011 | B1 |
| 7991234 | Fujioka et al. | Aug 2011 | B2 |
| 8028249 | Loui et al. | Sep 2011 | B2 |
| RE43260 | Paalasmaa et al. | Mar 2012 | E |
| 8156060 | Borzestowski et al. | Apr 2012 | B2 |
| 8169438 | Baraff et al. | May 2012 | B1 |
| 8200669 | Iampietro et al. | Jun 2012 | B1 |
| 8234218 | Robinson et al. | Jul 2012 | B2 |
| 8280979 | Kunz et al. | Oct 2012 | B2 |
| 8295546 | Craig et al. | Oct 2012 | B2 |
| 8352471 | Oami | Jan 2013 | B2 |
| 8390628 | Harding et al. | Mar 2013 | B2 |
| 8406473 | Tanaka et al. | Mar 2013 | B2 |
| 8423089 | Song et al. | Apr 2013 | B2 |
| 8506396 | Snyder et al. | Aug 2013 | B1 |
| 8571331 | Cifarelli et al. | Oct 2013 | B2 |
| 8584031 | Moore et al. | Nov 2013 | B2 |
| 8732609 | Bayersdorfer et al. | May 2014 | B1 |
| 8896652 | Ralston | Nov 2014 | B2 |
| 8934717 | Newell et al. | Jan 2015 | B2 |
| 8996639 | Faaborg et al. | Mar 2015 | B1 |
| 9021034 | Narayanan et al. | Apr 2015 | B2 |
| 9041764 | Wang et al. | May 2015 | B2 |
| 9042646 | Das et al. | May 2015 | B2 |
| 9094576 | Karakotsios | Jul 2015 | B1 |
| 9123086 | Freeland et al. | Sep 2015 | B1 |
| 9143601 | Padmanabhan et al. | Sep 2015 | B2 |
| 9153031 | El-saban et al. | Oct 2015 | B2 |
| 9183560 | Abelow | Nov 2015 | B2 |
| 9207837 | Paretti et al. | Dec 2015 | B2 |
| 9230241 | Singh et al. | Jan 2016 | B1 |
| 9230355 | Ahuja et al. | Jan 2016 | B1 |
| 9245177 | Perez | Jan 2016 | B2 |
| 9246961 | Walkin et al. | Jan 2016 | B2 |
| 9264660 | Petterson et al. | Feb 2016 | B1 |
| 9286546 | O'malley et al. | Mar 2016 | B2 |
| 9298257 | Hwang | Mar 2016 | B2 |
| 9298263 | Geisner et al. | Mar 2016 | B2 |
| 9349414 | Furment et al. | May 2016 | B1 |
| 9411506 | Prado | Aug 2016 | B1 |
| 9448708 | Bennett et al. | Sep 2016 | B1 |
| 9489074 | Oonishi | Nov 2016 | B2 |
| 9542070 | Xu et al. | Jan 2017 | B2 |
| 9602559 | Barros et al. | Mar 2017 | B1 |
| 9625987 | Lapenna et al. | Apr 2017 | B1 |
| 9628416 | Henderson | Apr 2017 | B2 |
| 9686497 | Terry | Jun 2017 | B1 |
| 9760976 | Kameyama | Sep 2017 | B2 |
| 9786084 | Bhat et al. | Oct 2017 | B1 |
| 9870554 | Leung et al. | Jan 2018 | B1 |
| 9916538 | Zadeh et al. | Mar 2018 | B2 |
| 9948589 | Gonnen et al. | Apr 2018 | B2 |
| 9949697 | Iscoe et al. | Apr 2018 | B2 |
| 10062133 | Mishra et al. | Aug 2018 | B1 |
| 10095385 | Walkin et al. | Oct 2018 | B2 |
| 10139218 | Matsushita | Nov 2018 | B2 |
| 10204338 | Lee | Feb 2019 | B2 |
| 10270983 | Van Os et al. | Apr 2019 | B1 |
| 10289265 | Kulkarni | May 2019 | B2 |
| 10303448 | Steven et al. | May 2019 | B2 |
| 10325416 | Scapel et al. | Jun 2019 | B1 |
| 10325417 | Scapel et al. | Jun 2019 | B1 |
| 10341612 | Imaoka | Jul 2019 | B2 |
| 10375313 | Van Os et al. | Aug 2019 | B1 |
| 10376153 | Tzvieli | Aug 2019 | B2 |
| 10379719 | Scapel et al. | Aug 2019 | B2 |
| 10410434 | Scapel et al. | Sep 2019 | B1 |
| 10417588 | Kreisel et al. | Sep 2019 | B1 |
| 10489982 | Johnson et al. | Nov 2019 | B2 |
| 10496244 | Reynolds et al. | Dec 2019 | B2 |
| 10505726 | Andon et al. | Dec 2019 | B1 |
| 10509907 | Shear et al. | Dec 2019 | B2 |
| 10521091 | Anzures et al. | Dec 2019 | B2 |
| 10521948 | Rickwald et al. | Dec 2019 | B2 |
| 10540400 | Dumant et al. | Jan 2020 | B2 |
| 10580221 | Scapel et al. | Mar 2020 | B2 |
| 10620590 | Guzman et al. | Apr 2020 | B1 |
| 10628985 | Mishra et al. | Apr 2020 | B2 |
| 10657695 | Chand et al. | May 2020 | B2 |
| 10659405 | Chang et al. | May 2020 | B1 |
| 10698575 | Walkin et al. | Jun 2020 | B2 |
| 10708545 | Rivard et al. | Jul 2020 | B2 |
| 10776965 | Stetson et al. | Sep 2020 | B2 |
| 10789753 | Miller et al. | Sep 2020 | B2 |
| 10796480 | Chen | Oct 2020 | B2 |
| 10798035 | Lewis et al. | Oct 2020 | B2 |
| 10810409 | Bacivarov et al. | Oct 2020 | B2 |
| 10811055 | Kimber et al. | Oct 2020 | B1 |
| 10817981 | Belkin | Oct 2020 | B1 |
| 10845968 | Scapel et al. | Nov 2020 | B2 |
| 10855910 | Tano et al. | Dec 2020 | B2 |
| 10902661 | Mourkogiannis et al. | Jan 2021 | B1 |
| 10984569 | Bondich et al. | Apr 2021 | B2 |
| 11061372 | Chen et al. | Jul 2021 | B1 |
| 11107261 | Scapel et al. | Aug 2021 | B2 |
| 11188190 | Blackstock et al. | Nov 2021 | B2 |
| 11217036 | Albuz et al. | Jan 2022 | B1 |
| 11361521 | Lee et al. | Jun 2022 | B2 |
| 11467713 | Buzyn et al. | Oct 2022 | B2 |
| 11592959 | Wagner et al. | Feb 2023 | B2 |
| 11729339 | Morii | Aug 2023 | B2 |
| 11798246 | Lee et al. | Oct 2023 | B2 |
| 20010019330 | Bickmore et al. | Sep 2001 | A1 |
| 20010050689 | Park | Dec 2001 | A1 |
| 20020054157 | Hayashi et al. | May 2002 | A1 |
| 20020135581 | Russell et al. | Sep 2002 | A1 |
| 20020168108 | Loui et al. | Nov 2002 | A1 |
| 20020180797 | Bachmann | Dec 2002 | A1 |
| 20030033296 | Rothmuller et al. | Feb 2003 | A1 |
| 20030074647 | Andrew et al. | Apr 2003 | A1 |
| 20030075409 | Bauer et al. | Apr 2003 | A1 |
| 20030135769 | Loughran | Jul 2003 | A1 |
| 20030140309 | Saito et al. | Jul 2003 | A1 |
| 20030206170 | Bickmore et al. | Nov 2003 | A1 |
| 20040019640 | Bartram et al. | Jan 2004 | A1 |
| 20040075699 | Franchi et al. | Apr 2004 | A1 |
| 20040125150 | Adcock et al. | Jul 2004 | A1 |
| 20040167898 | Margolus et al. | Aug 2004 | A1 |
| 20040179039 | Blattner et al. | Sep 2004 | A1 |
| 20040203342 | Sibecas et al. | Oct 2004 | A1 |
| 20040225966 | Besharat et al. | Nov 2004 | A1 |
| 20050044066 | Hooper et al. | Feb 2005 | A1 |
| 20050076056 | Paalasmaa et al. | Apr 2005 | A1 |
| 20050122543 | Walker | Jun 2005 | A1 |
| 20050124389 | Yang | Jun 2005 | A1 |
| 20050125744 | Hubbard et al. | Jun 2005 | A1 |
| 20050128305 | Hamasaki et al. | Jun 2005 | A1 |
| 20050134945 | Gallagher | Jun 2005 | A1 |
| 20050168566 | Tada et al. | Aug 2005 | A1 |
| 20050174216 | Lintell | Aug 2005 | A1 |
| 20050190653 | Chen | Sep 2005 | A1 |
| 20050195221 | Berger et al. | Sep 2005 | A1 |
| 20050248574 | Ashtekar et al. | Nov 2005 | A1 |
| 20050257042 | Sierra et al. | Nov 2005 | A1 |
| 20050261031 | Seo et al. | Nov 2005 | A1 |
| 20060020904 | Aaltonen et al. | Jan 2006 | A1 |
| 20060035632 | Sorvari et al. | Feb 2006 | A1 |
| 20060036960 | Loui et al. | Feb 2006 | A1 |
| 20060055700 | Niles et al. | Mar 2006 | A1 |
| 20060090141 | Loui et al. | Apr 2006 | A1 |
| 20060155757 | Williams et al. | Jul 2006 | A1 |
| 20060156237 | Williams et al. | Jul 2006 | A1 |
| 20060156245 | Williams et al. | Jul 2006 | A1 |
| 20060156246 | Williams et al. | Jul 2006 | A1 |
| 20060166708 | Kim et al. | Jul 2006 | A1 |
| 20060188144 | Sasaki et al. | Aug 2006 | A1 |
| 20060294465 | Ronen et al. | Dec 2006 | A1 |
| 20070003915 | Templeman | Jan 2007 | A1 |
| 20070008321 | Gallagher et al. | Jan 2007 | A1 |
| 20070024614 | Tam et al. | Feb 2007 | A1 |
| 20070052851 | Ochs et al. | Mar 2007 | A1 |
| 20070097113 | Lee et al. | May 2007 | A1 |
| 20070112754 | Haigh et al. | May 2007 | A1 |
| 20070113181 | Blattner et al. | May 2007 | A1 |
| 20070115373 | Gallagher et al. | May 2007 | A1 |
| 20070162872 | Hong et al. | Jul 2007 | A1 |
| 20070168863 | Blattner et al. | Jul 2007 | A1 |
| 20070171091 | Nisenboim et al. | Jul 2007 | A1 |
| 20070192718 | Voorhees et al. | Aug 2007 | A1 |
| 20070226653 | Moore et al. | Sep 2007 | A1 |
| 20070245236 | Lee et al. | Oct 2007 | A1 |
| 20070260984 | Marks et al. | Nov 2007 | A1 |
| 20080046839 | Mehra et al. | Feb 2008 | A1 |
| 20080052242 | Merritt et al. | Feb 2008 | A1 |
| 20080062141 | Chaudhri | Mar 2008 | A1 |
| 20080082934 | Kocienda et al. | Apr 2008 | A1 |
| 20080091637 | Escamilla et al. | Apr 2008 | A1 |
| 20080095470 | Chao et al. | Apr 2008 | A1 |
| 20080098031 | Ducharme | Apr 2008 | A1 |
| 20080152201 | Zhang et al. | Jun 2008 | A1 |
| 20080155428 | Lee | Jun 2008 | A1 |
| 20080158232 | Shuster | Jul 2008 | A1 |
| 20080201438 | Mandre et al. | Aug 2008 | A1 |
| 20080250315 | Eronen | Oct 2008 | A1 |
| 20080256577 | Funaki et al. | Oct 2008 | A1 |
| 20080298571 | Kurtz et al. | Dec 2008 | A1 |
| 20080309677 | Fleury et al. | Dec 2008 | A1 |
| 20080316227 | Fleury et al. | Dec 2008 | A1 |
| 20090006965 | Bodin et al. | Jan 2009 | A1 |
| 20090027337 | Hildreth | Jan 2009 | A1 |
| 20090031240 | Hildreth | Jan 2009 | A1 |
| 20090044113 | Jones et al. | Feb 2009 | A1 |
| 20090063542 | Bull et al. | Mar 2009 | A1 |
| 20090066817 | Sakamaki | Mar 2009 | A1 |
| 20090077497 | Cho et al. | Mar 2009 | A1 |
| 20090100342 | Jakobson et al. | Apr 2009 | A1 |
| 20090113350 | Hibino et al. | Apr 2009 | A1 |
| 20090144173 | Mo et al. | Jun 2009 | A1 |
| 20090144639 | Nims et al. | Jun 2009 | A1 |
| 20090161962 | Gallagher et al. | Jun 2009 | A1 |
| 20090198359 | Chaudhri | Aug 2009 | A1 |
| 20090201297 | Johansson | Aug 2009 | A1 |
| 20090202114 | Morin et al. | Aug 2009 | A1 |
| 20090210793 | Yee et al. | Aug 2009 | A1 |
| 20090216691 | Borzestowski et al. | Aug 2009 | A1 |
| 20090216806 | Feuerstein et al. | Aug 2009 | A1 |
| 20090231356 | Bames et al. | Sep 2009 | A1 |
| 20090233650 | Hosono | Sep 2009 | A1 |
| 20090249247 | Tseng et al. | Oct 2009 | A1 |
| 20090251484 | Zhao et al. | Oct 2009 | A1 |
| 20090254624 | Baudin et al. | Oct 2009 | A1 |
| 20090254859 | Arrasvuori et al. | Oct 2009 | A1 |
| 20090254862 | Viginisson et al. | Oct 2009 | A1 |
| 20090271705 | Sheng et al. | Oct 2009 | A1 |
| 20090297022 | Pettigrew et al. | Dec 2009 | A1 |
| 20090300513 | Nims et al. | Dec 2009 | A1 |
| 20090300525 | Jolliff | Dec 2009 | A1 |
| 20090319472 | Jain et al. | Dec 2009 | A1 |
| 20090325701 | Andres Del Valle | Dec 2009 | A1 |
| 20100009747 | Reville et al. | Jan 2010 | A1 |
| 20100026640 | Kim et al. | Feb 2010 | A1 |
| 20100030660 | Edwards | Feb 2010 | A1 |
| 20100045828 | Gallagher et al. | Feb 2010 | A1 |
| 20100046842 | Conwell | Feb 2010 | A1 |
| 20100076976 | Sotirov et al. | Mar 2010 | A1 |
| 20100097375 | Tadaishi et al. | Apr 2010 | A1 |
| 20100114891 | Oami | May 2010 | A1 |
| 20100123724 | Moore et al. | May 2010 | A1 |
| 20100123915 | Kashimoto | May 2010 | A1 |
| 20100124941 | Cho | May 2010 | A1 |
| 20100124967 | Lutnick et al. | May 2010 | A1 |
| 20100125811 | Moore et al. | May 2010 | A1 |
| 20100149573 | Pat et al. | Jun 2010 | A1 |
| 20100150456 | Tanaka et al. | Jun 2010 | A1 |
| 20100153386 | Tysowski | Jun 2010 | A1 |
| 20100153847 | Fama | Jun 2010 | A1 |
| 20100156807 | Stallings et al. | Jun 2010 | A1 |
| 20100179874 | Higgins et al. | Jul 2010 | A1 |
| 20100188426 | Ohmori et al. | Jul 2010 | A1 |
| 20100203968 | Gill et al. | Aug 2010 | A1 |
| 20100211575 | Collins et al. | Aug 2010 | A1 |
| 20100211899 | Fujioka | Aug 2010 | A1 |
| 20100218089 | Chao et al. | Aug 2010 | A1 |
| 20100251176 | Fong et al. | Sep 2010 | A1 |
| 20100257469 | Kim et al. | Oct 2010 | A1 |
| 20100277470 | Margolis | Nov 2010 | A1 |
| 20100287053 | Ganong et al. | Nov 2010 | A1 |
| 20100302138 | Poot | Dec 2010 | A1 |
| 20100317410 | Song et al. | Dec 2010 | A1 |
| 20110004524 | Paul et al. | Jan 2011 | A1 |
| 20110007174 | Bacivarov et al. | Jan 2011 | A1 |
| 20110016425 | Homburg et al. | Jan 2011 | A1 |
| 20110050564 | Alberth et al. | Mar 2011 | A1 |
| 20110057903 | Yamano et al. | Mar 2011 | A1 |
| 20110061017 | Ullrich et al. | Mar 2011 | A1 |
| 20110072394 | Victor et al. | Mar 2011 | A1 |
| 20110074807 | Inada et al. | Mar 2011 | A1 |
| 20110078717 | Drummond et al. | Mar 2011 | A1 |
| 20110099199 | Stalenhoef et al. | Apr 2011 | A1 |
| 20110099478 | Gallagher et al. | Apr 2011 | A1 |
| 20110119610 | Hackborn et al. | May 2011 | A1 |
| 20110126148 | Krishnaraj et al. | May 2011 | A1 |
| 20110145275 | Stewart | Jun 2011 | A1 |
| 20110145327 | Stewart | Jun 2011 | A1 |
| 20110163969 | Freddy et al. | Jul 2011 | A1 |
| 20110163971 | Wagner et al. | Jul 2011 | A1 |
| 20110175832 | Miyazawa et al. | Jul 2011 | A1 |
| 20110205182 | Miyazawa et al. | Aug 2011 | A1 |
| 20110221755 | Geisner et al. | Sep 2011 | A1 |
| 20110239115 | Williams et al. | Sep 2011 | A1 |
| 20110246463 | Carson et al. | Oct 2011 | A1 |
| 20110248992 | Van et al. | Oct 2011 | A1 |
| 20110249073 | Cranfill et al. | Oct 2011 | A1 |
| 20110249078 | Abuan et al. | Oct 2011 | A1 |
| 20110252344 | Van Os | Oct 2011 | A1 |
| 20110256848 | Bok et al. | Oct 2011 | A1 |
| 20110265002 | Hong et al. | Oct 2011 | A1 |
| 20110267368 | Casillas et al. | Nov 2011 | A1 |
| 20110282867 | Palermiti et al. | Nov 2011 | A1 |
| 20110285656 | Yaksick et al. | Nov 2011 | A1 |
| 20110302518 | Zhang | Dec 2011 | A1 |
| 20110304632 | Evertt et al. | Dec 2011 | A1 |
| 20120011449 | Sasson et al. | Jan 2012 | A1 |
| 20120017180 | Flik et al. | Jan 2012 | A1 |
| 20120057081 | Petersson et al. | Mar 2012 | A1 |
| 20120058801 | Nurmi | Mar 2012 | A1 |
| 20120059787 | Brown et al. | Mar 2012 | A1 |
| 20120069028 | Bouguerra | Mar 2012 | A1 |
| 20120075328 | Goossens | Mar 2012 | A1 |
| 20120079378 | Goossens | Mar 2012 | A1 |
| 20120084692 | Bae | Apr 2012 | A1 |
| 20120102399 | Nicholson | Apr 2012 | A1 |
| 20120113008 | Makinen et al. | May 2012 | A1 |
| 20120113762 | Frost | May 2012 | A1 |
| 20120158515 | K. | Jun 2012 | A1 |
| 20120174029 | Bastide et al. | Jul 2012 | A1 |
| 20120190386 | Anderson | Jul 2012 | A1 |
| 20120206452 | Geisner et al. | Aug 2012 | A1 |
| 20120210263 | Perry et al. | Aug 2012 | A1 |
| 20120254318 | Poniatowski | Oct 2012 | A1 |
| 20120256967 | Baldwin et al. | Oct 2012 | A1 |
| 20120293686 | Kam et al. | Nov 2012 | A1 |
| 20120299945 | Aarabi | Nov 2012 | A1 |
| 20120309520 | Evertt et al. | Dec 2012 | A1 |
| 20120311444 | Chaudhri | Dec 2012 | A1 |
| 20120314047 | Kasahara et al. | Dec 2012 | A1 |
| 20130013650 | Shum | Jan 2013 | A1 |
| 20130014019 | Kim et al. | Jan 2013 | A1 |
| 20130015946 | Lau et al. | Jan 2013 | A1 |
| 20130022282 | Cooper | Jan 2013 | A1 |
| 20130024781 | Douillet et al. | Jan 2013 | A1 |
| 20130024802 | Zeng et al. | Jan 2013 | A1 |
| 20130038759 | Jo et al. | Feb 2013 | A1 |
| 20130040660 | Fisher et al. | Feb 2013 | A1 |
| 20130063366 | Paul | Mar 2013 | A1 |
| 20130067391 | Pittappilly et al. | Mar 2013 | A1 |
| 20130101164 | Leclerc et al. | Apr 2013 | A1 |
| 20130113956 | Anderson et al. | May 2013 | A1 |
| 20130117365 | Padmanabhan et al. | May 2013 | A1 |
| 20130117383 | Hymel et al. | May 2013 | A1 |
| 20130135315 | Bares et al. | May 2013 | A1 |
| 20130141365 | Lynn et al. | Jun 2013 | A1 |
| 20130141513 | Setton et al. | Jun 2013 | A1 |
| 20130145292 | Cohen et al. | Jun 2013 | A1 |
| 20130147933 | Kulas et al. | Jun 2013 | A1 |
| 20130156275 | Amacker et al. | Jun 2013 | A1 |
| 20130157646 | Ferren et al. | Jun 2013 | A1 |
| 20130157729 | Tabe | Jun 2013 | A1 |
| 20130159900 | Pendharkar | Jun 2013 | A1 |
| 20130160141 | Tseng et al. | Jun 2013 | A1 |
| 20130194378 | Brown | Aug 2013 | A1 |
| 20130198176 | Kim | Aug 2013 | A1 |
| 20130198210 | Lee et al. | Aug 2013 | A1 |
| 20130201104 | Ptucha et al. | Aug 2013 | A1 |
| 20130234964 | Kim et al. | Sep 2013 | A1 |
| 20130238686 | O'donoghue et al. | Sep 2013 | A1 |
| 20130263043 | Sarbin et al. | Oct 2013 | A1 |
| 20130275875 | Gruber et al. | Oct 2013 | A1 |
| 20130285948 | Zhang | Oct 2013 | A1 |
| 20130286161 | Lv et al. | Oct 2013 | A1 |
| 20130290905 | Luvogt et al. | Oct 2013 | A1 |
| 20130293686 | Blow et al. | Nov 2013 | A1 |
| 20130305189 | Kim | Nov 2013 | A1 |
| 20130322218 | Burkhardt et al. | Dec 2013 | A1 |
| 20130342730 | Lee et al. | Dec 2013 | A1 |
| 20140015784 | Oonishi | Jan 2014 | A1 |
| 20140043329 | Wang et al. | Feb 2014 | A1 |
| 20140046914 | Das et al. | Feb 2014 | A1 |
| 20140047389 | Aarabi | Feb 2014 | A1 |
| 20140055554 | Du et al. | Feb 2014 | A1 |
| 20140064572 | Panzer et al. | Mar 2014 | A1 |
| 20140074893 | Griffin | Mar 2014 | A1 |
| 20140078144 | Berriman | Mar 2014 | A1 |
| 20140089330 | Cui et al. | Mar 2014 | A1 |
| 20140115488 | Hackborn | Apr 2014 | A1 |
| 20140123005 | Forstall et al. | May 2014 | A1 |
| 20140137013 | Matas | May 2014 | A1 |
| 20140143682 | Druck et al. | May 2014 | A1 |
| 20140143693 | Goossens | May 2014 | A1 |
| 20140149878 | Mischari et al. | May 2014 | A1 |
| 20140157167 | Zhu | Jun 2014 | A1 |
| 20140164938 | Petterson et al. | Jun 2014 | A1 |
| 20140164955 | Thiruvidam et al. | Jun 2014 | A1 |
| 20140168217 | Kim et al. | Jun 2014 | A1 |
| 20140172622 | Baronshin | Jun 2014 | A1 |
| 20140181089 | Desmond et al. | Jun 2014 | A1 |
| 20140181219 | Wang et al. | Jun 2014 | A1 |
| 20140195972 | Lee et al. | Jul 2014 | A1 |
| 20140198234 | Kobayashi et al. | Jul 2014 | A1 |
| 20140218371 | Du et al. | Aug 2014 | A1 |
| 20140218394 | Hochmuth et al. | Aug 2014 | A1 |
| 20140222809 | Hochmuth et al. | Aug 2014 | A1 |
| 20140236882 | Rishe et al. | Aug 2014 | A1 |
| 20140237393 | Van Wie et al. | Aug 2014 | A1 |
| 20140250126 | Baldwin et al. | Sep 2014 | A1 |
| 20140267618 | Esteban et al. | Sep 2014 | A1 |
| 20140282011 | Dellinger et al. | Sep 2014 | A1 |
| 20140289222 | Sharpe et al. | Sep 2014 | A1 |
| 20140300635 | Suzuki | Oct 2014 | A1 |
| 20140306898 | Cueto | Oct 2014 | A1 |
| 20140333671 | Phang et al. | Nov 2014 | A1 |
| 20140336808 | Taylor et al. | Nov 2014 | A1 |
| 20140337324 | Chao et al. | Nov 2014 | A1 |
| 20140341476 | Kulick et al. | Nov 2014 | A1 |
| 20140351720 | Mn | Nov 2014 | A1 |
| 20140359441 | Lehtiniemi et al. | Dec 2014 | A1 |
| 20140362091 | Bouaziz et al. | Dec 2014 | A1 |
| 20140362274 | Christie et al. | Dec 2014 | A1 |
| 20140368601 | Decharms | Dec 2014 | A1 |
| 20140372436 | Makki et al. | Dec 2014 | A1 |
| 20140372889 | Lemay et al. | Dec 2014 | A1 |
| 20150005013 | Cao et al. | Jan 2015 | A1 |
| 20150011204 | Seo et al. | Jan 2015 | A1 |
| 20150033192 | Bohannon et al. | Jan 2015 | A1 |
| 20150035825 | Zhou et al. | Feb 2015 | A1 |
| 20150036883 | Deri et al. | Feb 2015 | A1 |
| 20150037545 | Sun | Feb 2015 | A1 |
| 20150042571 | Lombardi et al. | Feb 2015 | A1 |
| 20150043046 | Iwamoto | Feb 2015 | A1 |
| 20150058754 | Rauh | Feb 2015 | A1 |
| 20150062052 | Bernstein et al. | Mar 2015 | A1 |
| 20150070378 | Kriese et al. | Mar 2015 | A1 |
| 20150077502 | Jordan et al. | Mar 2015 | A1 |
| 20150078621 | Choi et al. | Mar 2015 | A1 |
| 20150078680 | Shakib et al. | Mar 2015 | A1 |
| 20150082193 | Wallace et al. | Mar 2015 | A1 |
| 20150082446 | Flowers et al. | Mar 2015 | A1 |
| 20150091896 | Tarquini et al. | Apr 2015 | A1 |
| 20150100537 | Grieves et al. | Apr 2015 | A1 |
| 20150113435 | Phillips | Apr 2015 | A1 |
| 20150149899 | Bernstein et al. | May 2015 | A1 |
| 20150149927 | Walkin et al. | May 2015 | A1 |
| 20150153952 | Grossman et al. | Jun 2015 | A1 |
| 20150177937 | Poletto et al. | Jun 2015 | A1 |
| 20150195179 | Skare et al. | Jul 2015 | A1 |
| 20150213001 | Levy et al. | Jul 2015 | A1 |
| 20150213604 | Li | Jul 2015 | A1 |
| 20150227166 | Lee et al. | Aug 2015 | A1 |
| 20150227611 | Xuan et al. | Aug 2015 | A1 |
| 20150242689 | Mau | Aug 2015 | A1 |
| 20150244794 | Poletto et al. | Aug 2015 | A1 |
| 20150248235 | Offenberg et al. | Sep 2015 | A1 |
| 20150253740 | Nishijima et al. | Sep 2015 | A1 |
| 20150254396 | Tamura et al. | Sep 2015 | A1 |
| 20150262062 | Burger et al. | Sep 2015 | A1 |
| 20150281145 | Ji | Oct 2015 | A1 |
| 20150287162 | Canan et al. | Oct 2015 | A1 |
| 20150302624 | Burke | Oct 2015 | A1 |
| 20150309698 | Senderek et al. | Oct 2015 | A1 |
| 20150312175 | Langholz | Oct 2015 | A1 |
| 20150312182 | Langholz | Oct 2015 | A1 |
| 20150312184 | Langholz et al. | Oct 2015 | A1 |
| 20150312185 | Langholz et al. | Oct 2015 | A1 |
| 20150317945 | Andress et al. | Nov 2015 | A1 |
| 20150334075 | Wang et al. | Nov 2015 | A1 |
| 20150350141 | Yang et al. | Dec 2015 | A1 |
| 20150363409 | Wood et al. | Dec 2015 | A1 |
| 20150366293 | Clarkson | Dec 2015 | A1 |
| 20150370529 | Zambetti et al. | Dec 2015 | A1 |
| 20160004820 | Moore | Jan 2016 | A1 |
| 20160005211 | Sarkis et al. | Jan 2016 | A1 |
| 20160006987 | Li et al. | Jan 2016 | A1 |
| 20160019388 | Singla et al. | Jan 2016 | A1 |
| 20160030844 | Nair et al. | Feb 2016 | A1 |
| 20160034133 | Wilson et al. | Feb 2016 | A1 |
| 20160050169 | Ben Atar et al. | Feb 2016 | A1 |
| 20160054845 | Takahashi et al. | Feb 2016 | A1 |
| 20160062582 | Wilson et al. | Mar 2016 | A1 |
| 20160073034 | Mukherjee et al. | Mar 2016 | A1 |
| 20160086387 | Os et al. | Mar 2016 | A1 |
| 20160092035 | Crocker et al. | Mar 2016 | A1 |
| 20160092043 | Missig et al. | Mar 2016 | A1 |
| 20160103427 | Westra et al. | Apr 2016 | A1 |
| 20160117147 | Zambetti et al. | Apr 2016 | A1 |
| 20160132200 | Walkin et al. | May 2016 | A1 |
| 20160134840 | Mcculloch | May 2016 | A1 |
| 20160140146 | Wexler et al. | May 2016 | A1 |
| 20160150215 | Chen et al. | May 2016 | A1 |
| 20160163084 | Corazza et al. | Jun 2016 | A1 |
| 20160187995 | Rosewall | Jun 2016 | A1 |
| 20160217601 | Tsuda et al. | Jul 2016 | A1 |
| 20160226804 | Hampson et al. | Aug 2016 | A1 |
| 20160226926 | Singh et al. | Aug 2016 | A1 |
| 20160227121 | Matsushita | Aug 2016 | A1 |
| 20160234184 | Liu et al. | Aug 2016 | A1 |
| 20160247309 | Li et al. | Aug 2016 | A1 |
| 20160259413 | Anzures et al. | Sep 2016 | A1 |
| 20160259497 | Foss et al. | Sep 2016 | A1 |
| 20160259498 | Foss et al. | Sep 2016 | A1 |
| 20160259499 | Kocienda et al. | Sep 2016 | A1 |
| 20160259518 | King et al. | Sep 2016 | A1 |
| 20160259519 | Foss et al. | Sep 2016 | A1 |
| 20160259527 | Kocienda et al. | Sep 2016 | A1 |
| 20160259528 | Foss et al. | Sep 2016 | A1 |
| 20160267067 | Mays et al. | Sep 2016 | A1 |
| 20160275724 | Adeyoola et al. | Sep 2016 | A1 |
| 20160284123 | Hare | Sep 2016 | A1 |
| 20160323507 | Chong et al. | Nov 2016 | A1 |
| 20160327911 | Eim et al. | Nov 2016 | A1 |
| 20160328875 | Fang et al. | Nov 2016 | A1 |
| 20160357282 | Block et al. | Dec 2016 | A1 |
| 20160357720 | Thimbleby | Dec 2016 | A1 |
| 20160370974 | Stenneth | Dec 2016 | A1 |
| 20170003659 | Nakanishi | Jan 2017 | A1 |
| 20170018289 | Morgenstern | Jan 2017 | A1 |
| 20170032554 | O'Donovan et al. | Feb 2017 | A1 |
| 20170046065 | Zeng et al. | Feb 2017 | A1 |
| 20170061635 | Petrovich et al. | Mar 2017 | A1 |
| 20170068439 | Mohseni | Mar 2017 | A1 |
| 20170069124 | Tong et al. | Mar 2017 | A1 |
| 20170078621 | Sahay et al. | Mar 2017 | A1 |
| 20170082983 | Katzer et al. | Mar 2017 | A1 |
| 20170083086 | Mazur et al. | Mar 2017 | A1 |
| 20170111616 | Li et al. | Apr 2017 | A1 |
| 20170123571 | Huang et al. | May 2017 | A1 |
| 20170124751 | Ross | May 2017 | A1 |
| 20170131886 | Kim et al. | May 2017 | A1 |
| 20170140214 | Matas et al. | May 2017 | A1 |
| 20170164888 | Matsuda et al. | Jun 2017 | A1 |
| 20170178287 | Anderson | Jun 2017 | A1 |
| 20170193684 | Du et al. | Jul 2017 | A1 |
| 20170206095 | Gibbs et al. | Jul 2017 | A1 |
| 20170220212 | Yang et al. | Aug 2017 | A1 |
| 20170236298 | Vetter | Aug 2017 | A1 |
| 20170244959 | Angela et al. | Aug 2017 | A1 |
| 20170255169 | Lee et al. | Sep 2017 | A1 |
| 20170269715 | Kim et al. | Sep 2017 | A1 |
| 20170285916 | Xu et al. | Oct 2017 | A1 |
| 20170286913 | Liu et al. | Oct 2017 | A1 |
| 20170322711 | Robinson et al. | Nov 2017 | A1 |
| 20170323266 | Seo | Nov 2017 | A1 |
| 20170332045 | Mette et al. | Nov 2017 | A1 |
| 20170336926 | Chaudhri et al. | Nov 2017 | A1 |
| 20170336928 | Chaudhri et al. | Nov 2017 | A1 |
| 20170337554 | Mokhasi et al. | Nov 2017 | A1 |
| 20170352091 | Chen et al. | Dec 2017 | A1 |
| 20170357382 | Miura et al. | Dec 2017 | A1 |
| 20180004404 | Delfino et al. | Jan 2018 | A1 |
| 20180024726 | Hviding | Jan 2018 | A1 |
| 20180034867 | Zahn et al. | Feb 2018 | A1 |
| 20180047200 | O'hara et al. | Feb 2018 | A1 |
| 20180059903 | Lim et al. | Mar 2018 | A1 |
| 20180067633 | Wilson et al. | Mar 2018 | A1 |
| 20180074693 | Jones et al. | Mar 2018 | A1 |
| 20180081515 | Block et al. | Mar 2018 | A1 |
| 20180083901 | Mcgregor et al. | Mar 2018 | A1 |
| 20180088787 | Bereza et al. | Mar 2018 | A1 |
| 20180091732 | Wilson et al. | Mar 2018 | A1 |
| 20180095635 | Valdivia et al. | Apr 2018 | A1 |
| 20180095649 | Valdivia et al. | Apr 2018 | A1 |
| 20180114543 | Novikoff | Apr 2018 | A1 |
| 20180121060 | Jeong et al. | May 2018 | A1 |
| 20180131878 | Charlton et al. | May 2018 | A1 |
| 20180165862 | Sawaki | Jun 2018 | A1 |
| 20180165863 | Kubo et al. | Jun 2018 | A1 |
| 20180181668 | Zhang et al. | Jun 2018 | A1 |
| 20180189549 | Inomata | Jul 2018 | A1 |
| 20180191944 | Carbonell et al. | Jul 2018 | A1 |
| 20180204111 | Zadeh et al. | Jul 2018 | A1 |
| 20180246639 | Han et al. | Aug 2018 | A1 |
| 20180268589 | Grant | Sep 2018 | A1 |
| 20180275750 | Zeng | Sep 2018 | A1 |
| 20180321048 | Li et al. | Nov 2018 | A1 |
| 20180324353 | Kim et al. | Nov 2018 | A1 |
| 20180329587 | Ko et al. | Nov 2018 | A1 |
| 20180335927 | Anzures et al. | Nov 2018 | A1 |
| 20180335929 | Scapel et al. | Nov 2018 | A1 |
| 20180335930 | Scapel et al. | Nov 2018 | A1 |
| 20180336715 | Rickwald et al. | Nov 2018 | A1 |
| 20180349795 | Boyle et al. | Dec 2018 | A1 |
| 20180364872 | Miura et al. | Dec 2018 | A1 |
| 20190050045 | Jha et al. | Feb 2019 | A1 |
| 20190058827 | Park et al. | Feb 2019 | A1 |
| 20190072909 | Misaki et al. | Mar 2019 | A1 |
| 20190080070 | Van Os et al. | Mar 2019 | A1 |
| 20190088018 | Shenton et al. | Mar 2019 | A1 |
| 20190096106 | Shapiro et al. | Mar 2019 | A1 |
| 20190139207 | Jeong et al. | May 2019 | A1 |
| 20190158735 | Wilson et al. | May 2019 | A1 |
| 20190160378 | Fajt et al. | May 2019 | A1 |
| 20190235748 | Seol et al. | Aug 2019 | A1 |
| 20190266775 | Lee et al. | Aug 2019 | A1 |
| 20190266807 | Lee et al. | Aug 2019 | A1 |
| 20190295056 | Wright | Sep 2019 | A1 |
| 20190310761 | Agarawala et al. | Oct 2019 | A1 |
| 20190339847 | Scapel et al. | Nov 2019 | A1 |
| 20190342507 | Dye | Nov 2019 | A1 |
| 20190347868 | Scapel et al. | Nov 2019 | A1 |
| 20190354265 | Winnemoeller | Nov 2019 | A1 |
| 20190369836 | Faulkner et al. | Dec 2019 | A1 |
| 20190371033 | Scapel et al. | Dec 2019 | A1 |
| 20200034025 | Brady et al. | Jan 2020 | A1 |
| 20200045245 | Van Os et al. | Feb 2020 | A1 |
| 20200068095 | Nabetani | Feb 2020 | A1 |
| 20200089302 | Kim et al. | Mar 2020 | A1 |
| 20200201540 | Zambetti et al. | Jun 2020 | A1 |
| 20200226848 | Van Os et al. | Jul 2020 | A1 |
| 20200234481 | Scapel et al. | Jul 2020 | A1 |
| 20200234508 | Shaburov | Jul 2020 | A1 |
| 20200264738 | Lee et al. | Aug 2020 | A1 |
| 20200265234 | Lee et al. | Aug 2020 | A1 |
| 20200285851 | Lin et al. | Sep 2020 | A1 |
| 20200358725 | Scapel et al. | Nov 2020 | A1 |
| 20200380103 | Hosoda | Dec 2020 | A1 |
| 20200380768 | Harris et al. | Dec 2020 | A1 |
| 20200380781 | Barlier et al. | Dec 2020 | A1 |
| 20200402304 | Hwang et al. | Dec 2020 | A1 |
| 20200409533 | Blackstock et al. | Dec 2020 | A1 |
| 20200410763 | Hare et al. | Dec 2020 | A1 |
| 20200412975 | Al Majid et al. | Dec 2020 | A1 |
| 20210005003 | Chong et al. | Jan 2021 | A1 |
| 20210056769 | Scapel et al. | Feb 2021 | A1 |
| 20210058351 | Viklund et al. | Feb 2021 | A1 |
| 20210065448 | Goodrich et al. | Mar 2021 | A1 |
| 20210065454 | Goodrich et al. | Mar 2021 | A1 |
| 20210089136 | Hossain et al. | Mar 2021 | A1 |
| 20210096703 | Anzures et al. | Apr 2021 | A1 |
| 20210099568 | Depue et al. | Apr 2021 | A1 |
| 20210099761 | Zhang | Apr 2021 | A1 |
| 20210152505 | Baldwin et al. | May 2021 | A1 |
| 20210168108 | Antmen et al. | Jun 2021 | A1 |
| 20210191578 | Miura et al. | Jun 2021 | A1 |
| 20210264656 | Barlier et al. | Aug 2021 | A1 |
| 20210287343 | Kaida | Sep 2021 | A1 |
| 20210311609 | Dandoko | Oct 2021 | A1 |
| 20210335055 | Scapel et al. | Oct 2021 | A1 |
| 20210349426 | Chen et al. | Nov 2021 | A1 |
| 20210349427 | Chen et al. | Nov 2021 | A1 |
| 20210349611 | Chen et al. | Nov 2021 | A1 |
| 20210349612 | Triverio | Nov 2021 | A1 |
| 20210375042 | Chen et al. | Dec 2021 | A1 |
| 20210390753 | Scapel et al. | Dec 2021 | A1 |
| 20210405831 | Mourkogiannis et al. | Dec 2021 | A1 |
| 20220027039 | Wagner et al. | Jan 2022 | A1 |
| 20220070385 | Van Os et al. | Mar 2022 | A1 |
| 20220084279 | Lindmeier et al. | Mar 2022 | A1 |
| 20220124140 | Okina et al. | Apr 2022 | A1 |
| 20220134234 | Sachson et al. | May 2022 | A1 |
| 20220206675 | Hawkes | Jun 2022 | A1 |
| 20220229546 | Lee et al. | Jul 2022 | A1 |
| 20220253136 | Holder et al. | Aug 2022 | A1 |
| 20220262080 | Burton et al. | Aug 2022 | A1 |
| 20220276750 | Miura et al. | Sep 2022 | A1 |
| 20220291793 | Zambetti et al. | Sep 2022 | A1 |
| 20220301041 | Lee et al. | Sep 2022 | A1 |
| 20220319075 | Hu et al. | Oct 2022 | A1 |
| 20220374137 | Triverio et al. | Nov 2022 | A1 |
| 20220392132 | Sepulveda et al. | Dec 2022 | A1 |
| 20230004270 | Chen et al. | Jan 2023 | A1 |
| 20230043249 | Van Os et al. | Feb 2023 | A1 |
| 20230214107 | Zambetti et al. | Jul 2023 | A1 |
| 20230229283 | Long et al. | Jul 2023 | A1 |
| 20230283884 | Van Os et al. | Sep 2023 | A1 |
| 20230297206 | Miura et al. | Sep 2023 | A1 |
| 20230305688 | Triverio et al. | Sep 2023 | A1 |
| 20230343053 | Scapel et al. | Oct 2023 | A1 |
| 20230350564 | Chen et al. | Nov 2023 | A1 |
| 20230384860 | Dedonato et al. | Nov 2023 | A1 |
| 20240029334 | Sepulveda et al. | Jan 2024 | A1 |
| 20240036717 | Triverio | Feb 2024 | A1 |
| 20240077937 | Rickwald et al. | Mar 2024 | A1 |
| 20240104859 | Chand et al. | Mar 2024 | A1 |
| 20240144626 | Van Os et al. | May 2024 | A1 |
| 20240256101 | Miura et al. | Aug 2024 | A1 |
| 20240257486 | El Asmar et al. | Aug 2024 | A1 |
| 20240259676 | Wilson et al. | Aug 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 2015101639 | Dec 2015 | AU |
| 2017100683 | Jan 2018 | AU |
| 2015297035 | Jun 2018 | AU |
| 2356232 | Mar 2002 | CA |
| 2792987 | Oct 2011 | CA |
| 1083229 | Mar 1994 | CN |
| 2602404 | Feb 2004 | CN |
| 101042618 | Sep 2007 | CN |
| 101055646 | Oct 2007 | CN |
| 101098535 | Jan 2008 | CN |
| 101128794 | Feb 2008 | CN |
| 101196786 | Jun 2008 | CN |
| 101203821 | Jun 2008 | CN |
| 101291409 | Oct 2008 | CN |
| 101329707 | Dec 2008 | CN |
| 101692681 | Apr 2010 | CN |
| 101742053 | Jun 2010 | CN |
| 101796476 | Aug 2010 | CN |
| 101854278 | Oct 2010 | CN |
| 102012738 | Apr 2011 | CN |
| 102035990 | Apr 2011 | CN |
| 102075727 | May 2011 | CN |
| 102142149 | Aug 2011 | CN |
| 102163098 | Aug 2011 | CN |
| 102271241 | Dec 2011 | CN |
| 102298797 | Dec 2011 | CN |
| 102446059 | May 2012 | CN |
| 102447873 | May 2012 | CN |
| 102483758 | May 2012 | CN |
| 202217134 | May 2012 | CN |
| 102622085 | Aug 2012 | CN |
| 102681847 | Sep 2012 | CN |
| 102693311 | Sep 2012 | CN |
| 102750070 | Oct 2012 | CN |
| 102790826 | Nov 2012 | CN |
| 102854979 | Jan 2013 | CN |
| 103081496 | May 2013 | CN |
| 103092469 | May 2013 | CN |
| 103516894 | Jan 2014 | CN |
| 103703438 | Apr 2014 | CN |
| 103713843 | Apr 2014 | CN |
| 103744671 | Apr 2014 | CN |
| 103927190 | Jul 2014 | CN |
| 103947190 | Jul 2014 | CN |
| 104035666 | Sep 2014 | CN |
| 104182741 | Dec 2014 | CN |
| 104246793 | Dec 2014 | CN |
| 104270597 | Jan 2015 | CN |
| 104376160 | Feb 2015 | CN |
| 104753762 | Jul 2015 | CN |
| 104869346 | Aug 2015 | CN |
| 104898402 | Sep 2015 | CN |
| 104952063 | Sep 2015 | CN |
| 104981762 | Oct 2015 | CN |
| 105100462 | Nov 2015 | CN |
| 105103154 | Nov 2015 | CN |
| 105190700 | Dec 2015 | CN |
| 105264480 | Jan 2016 | CN |
| 105378728 | Mar 2016 | CN |
| 105391937 | Mar 2016 | CN |
| 105611215 | May 2016 | CN |
| 105611275 | May 2016 | CN |
| 105653031 | Jun 2016 | CN |
| 106303690 | Jan 2017 | CN |
| 106792147 | May 2017 | CN |
| 106909064 | Jun 2017 | CN |
| 107533356 | Jan 2018 | CN |
| 107561904 | Jan 2018 | CN |
| 107924113 | Apr 2018 | CN |
| 107944397 | Apr 2018 | CN |
| 110046020 | Jul 2019 | CN |
| 112634416 | Apr 2021 | CN |
| 201670652 | Dec 2017 | DK |
| 0579093 | Jan 1994 | EP |
| 1215867 | Jun 2002 | EP |
| 1429291 | Jun 2004 | EP |
| 1592212 | Nov 2005 | EP |
| 1736931 | Dec 2006 | EP |
| 1777611 | Apr 2007 | EP |
| 2040146 | Mar 2009 | EP |
| 2302493 | Mar 2011 | EP |
| 2416563 | Feb 2012 | EP |
| 2437148 | Apr 2012 | EP |
| 2615607 | Jul 2013 | EP |
| 2653961 | Oct 2013 | EP |
| 2677775 | Dec 2013 | EP |
| 2720126 | Apr 2014 | EP |
| 2990887 | Mar 2016 | EP |
| 3026636 | Jun 2016 | EP |
| 3047884 | Jul 2016 | EP |
| 3051525 | Aug 2016 | EP |
| 3079044 | Oct 2016 | EP |
| 3101958 | Dec 2016 | EP |
| 3190563 | Jul 2017 | EP |
| 3211587 | Aug 2017 | EP |
| 2556665 | Aug 2018 | EP |
| 3401770 | Nov 2018 | EP |
| 2370208 | Jun 2002 | GB |
| 53-31170 | Mar 1978 | JP |
| 56-621 | Jan 1981 | JP |
| 3007616 | Feb 1995 | JP |
| 9-9072 | Jan 1997 | JP |
| 10-506472 | Jun 1998 | JP |
| 10-293860 | Nov 1998 | JP |
| 11-109066 | Apr 1999 | JP |
| 11-312159 | Nov 1999 | JP |
| 2000-76460 | Mar 2000 | JP |
| 2000-112997 | Apr 2000 | JP |
| 2000-162349 | Jun 2000 | JP |
| 2000-244637 | Sep 2000 | JP |
| 2001-144884 | May 2001 | JP |
| 2001-273064 | Oct 2001 | JP |
| 2001-313886 | Nov 2001 | JP |
| 2002-251238 | Sep 2002 | JP |
| 2003-9404 | Jan 2003 | JP |
| 2003-219217 | Jul 2003 | JP |
| 2003-233616 | Aug 2003 | JP |
| 2004-28918 | Jan 2004 | JP |
| 2004-519033 | Jun 2004 | JP |
| 2004-184396 | Jul 2004 | JP |
| 2005-521890 | Jul 2005 | JP |
| 2005-532607 | Oct 2005 | JP |
| 2006-102327 | Apr 2006 | JP |
| 2006-520053 | Aug 2006 | JP |
| 2007-528240 | Oct 2007 | JP |
| 2007-287014 | Nov 2007 | JP |
| 2008-59614 | Mar 2008 | JP |
| 2008-97202 | Apr 2008 | JP |
| 2008-236794 | Oct 2008 | JP |
| 2009-59042 | Mar 2009 | JP |
| 2009-217612 | Sep 2009 | JP |
| 2010-503130 | Jan 2010 | JP |
| 2010-118056 | May 2010 | JP |
| 2011-515726 | May 2011 | JP |
| 2011-517810 | Jun 2011 | JP |
| 2011-525648 | Sep 2011 | JP |
| 2011-209887 | Oct 2011 | JP |
| 2011-530101 | Dec 2011 | JP |
| 2012-18569 | Jan 2012 | JP |
| 2012-38292 | Feb 2012 | JP |
| 2012-123475 | Jun 2012 | JP |
| 2013-3671 | Jan 2013 | JP |
| 2013-83689 | May 2013 | JP |
| 2013-84282 | May 2013 | JP |
| 2013-92989 | May 2013 | JP |
| 2013-97760 | May 2013 | JP |
| 2013-101528 | May 2013 | JP |
| 2013-232230 | Nov 2013 | JP |
| 2014-93003 | May 2014 | JP |
| 2014-95979 | May 2014 | JP |
| 2014-206817 | Oct 2014 | JP |
| 2014-222439 | Nov 2014 | JP |
| 2015-504619 | Feb 2015 | JP |
| 2016-35776 | Mar 2016 | JP |
| 2016-136324 | Jul 2016 | JP |
| 2016-201135 | Dec 2016 | JP |
| 2017-54195 | Mar 2017 | JP |
| 2017-521804 | Aug 2017 | JP |
| 2017-527917 | Sep 2017 | JP |
| 2017-531225 | Oct 2017 | JP |
| 62-40301 | Nov 2017 | JP |
| 62-66736 | Jan 2018 | JP |
| 2018-514838 | Jun 2018 | JP |
| 2018-106365 | Jul 2018 | JP |
| 2018-116067 | Jul 2018 | JP |
| 2019-145108 | Aug 2019 | JP |
| 2019-164825 | Sep 2019 | JP |
| 10-2004-0009115 | Jan 2004 | KR |
| 10-2004-0046272 | Jun 2004 | KR |
| 10-2004-0107489 | Dec 2004 | KR |
| 10-2005-0086630 | Aug 2005 | KR |
| 10-2008-0050336 | Jun 2008 | KR |
| 10-2010-0086052 | Jul 2010 | KR |
| 10-2011-0028581 | Mar 2011 | KR |
| 10-2012-0058539 | Jun 2012 | KR |
| 10-2012-0092644 | Aug 2012 | KR |
| 10-2012-0113252 | Oct 2012 | KR |
| 10-2012-0132134 | Dec 2012 | KR |
| 10-2014-0033088 | Mar 2014 | KR |
| 10-2014-0049340 | Apr 2014 | KR |
| 10-2014-0067965 | Jun 2014 | KR |
| 10-2014-0073232 | Jun 2014 | KR |
| 10-2015-0008996 | Jan 2015 | KR |
| 10-2015-0024899 | Mar 2015 | KR |
| 10-2015-0067197 | Jun 2015 | KR |
| 10-1540544 | Jul 2015 | KR |
| 10-2015-0131257 | Nov 2015 | KR |
| 10-2015-0131262 | Nov 2015 | KR |
| 10-1587115 | Jan 2016 | KR |
| 10-2016-0016910 | Feb 2016 | KR |
| 10-1611895 | Apr 2016 | KR |
| 10-2016-0047891 | May 2016 | KR |
| 10-2016-0063058 | Jun 2016 | KR |
| 10-1655078 | Sep 2016 | KR |
| 10-2016-0146942 | Dec 2016 | KR |
| 10-2017-0081391 | Jul 2017 | KR |
| 10-2017-0112267 | Oct 2017 | KR |
| 10-2017-0112406 | Oct 2017 | KR |
| 10-2017-0117306 | Oct 2017 | KR |
| 10-2018-0017227 | Feb 2018 | KR |
| 10-1875907 | Jul 2018 | KR |
| 10-2019-0114034 | Oct 2019 | KR |
| 10-2020-0101206 | Aug 2020 | KR |
| 10-2020-0132995 | Nov 2020 | KR |
| 10-2338576 | Dec 2021 | KR |
| 199840795 | Sep 1998 | WO |
| 199966394 | Dec 1999 | WO |
| 199966395 | Dec 1999 | WO |
| 2003085460 | Oct 2003 | WO |
| 2004010672 | Jan 2004 | WO |
| 2004079530 | Sep 2004 | WO |
| 2006076557 | Jul 2006 | WO |
| 2006094308 | Sep 2006 | WO |
| 2007120981 | Oct 2007 | WO |
| 2009032998 | Mar 2009 | WO |
| 2009073607 | Jun 2009 | WO |
| 2009082814 | Jul 2009 | WO |
| 2009114239 | Sep 2009 | WO |
| 2009133710 | Nov 2009 | WO |
| 2009150425 | Dec 2009 | WO |
| 2009155991 | Dec 2009 | WO |
| 2010059188 | May 2010 | WO |
| 2011017653 | Feb 2011 | WO |
| 2011028424 | Mar 2011 | WO |
| 2011051091 | May 2011 | WO |
| 2011084856 | Jul 2011 | WO |
| 2011084860 | Jul 2011 | WO |
| 2011127309 | Oct 2011 | WO |
| 2011130849 | May 2012 | WO |
| 2012097385 | Jul 2012 | WO |
| 2012128361 | Sep 2012 | WO |
| 2012170354 | Dec 2012 | WO |
| 2013082325 | Jun 2013 | WO |
| 2013120851 | Aug 2013 | WO |
| 2013152453 | Oct 2013 | WO |
| 2013152454 | Oct 2013 | WO |
| 2013152455 | Oct 2013 | WO |
| 2013169851 | Nov 2013 | WO |
| 2013169854 | Nov 2013 | WO |
| 2013169870 | Nov 2013 | WO |
| 2013169877 | Nov 2013 | WO |
| 2013189058 | Dec 2013 | WO |
| 2014024000 | Feb 2014 | WO |
| 2014053063 | Apr 2014 | WO |
| 2014094199 | Jun 2014 | WO |
| 2014105279 | Jul 2014 | WO |
| 2014149473 | Sep 2014 | WO |
| 2014149488 | Sep 2014 | WO |
| 2014162659 | Oct 2014 | WO |
| 2014195851 | Dec 2014 | WO |
| 2014200734 | Dec 2014 | WO |
| 2015034960 | Mar 2015 | WO |
| 2015084891 | Jun 2015 | WO |
| 2015144209 | Oct 2015 | WO |
| 2015183756 | Dec 2015 | WO |
| 2015187458 | Dec 2015 | WO |
| 2016022203 | Feb 2016 | WO |
| 2016022204 | Feb 2016 | WO |
| 2016022205 | Feb 2016 | WO |
| 2016036218 | Mar 2016 | WO |
| 2016036522 | Mar 2016 | WO |
| 2016042926 | Mar 2016 | WO |
| 2016045005 | Mar 2016 | WO |
| 2016057062 | Apr 2016 | WO |
| 2016064435 | Apr 2016 | WO |
| 2016077834 | May 2016 | WO |
| 2016101124 | Jun 2016 | WO |
| 2016101131 | Jun 2016 | WO |
| 2016101132 | Jun 2016 | WO |
| 2016144385 | Sep 2016 | WO |
| 2016144975 | Sep 2016 | WO |
| 2016145129 | Sep 2016 | WO |
| 201661556 | Oct 2016 | WO |
| 2017030646 | Feb 2017 | WO |
| 2017077751 | May 2017 | WO |
| 2017153771 | Sep 2017 | WO |
| 2017201326 | Nov 2017 | WO |
| 2017213439 | Dec 2017 | WO |
| 2017218193 | Dec 2017 | WO |
| 2018006053 | Jan 2018 | WO |
| 2018049430 | Mar 2018 | WO |
| 2018057272 | Mar 2018 | WO |
| 2018212802 | Nov 2018 | WO |
| 2019216997 | Nov 2019 | WO |
| 2019216999 | Nov 2019 | WO |
| 2020226785 | Nov 2020 | WO |
| 2021050190 | Mar 2021 | WO |
| 2021071532 | Apr 2021 | WO |
| 2022147146 | Jul 2022 | WO |
| Entry |
|---|
| Board Opinion received for Chinese Patent Application No. 201911199054.4, mailed on May 10, 2024, 24 pages (13 pages of English Translation and 11 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/204,908, mailed on Jul. 2, 2024, 4 pages. |
| Communication for Board of Appeal received for European Patent Application No. 19204230.7, mailed on Jun. 18, 2024, 15 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/220,715, mailed on Jun. 24, 2024, 2 pages. |
| Intention to Grant received for European Patent Application No. 23173355.1, mailed on Jun. 28, 2024, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/204,908, mailed on Jun. 5, 2024, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/220,715, mailed on Jun. 13, 2024, 10 pages. |
| Board Decision received for Chinese Patent Application No. 202010295272.4, mailed on Dec. 14, 2023, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 18/137,353, mailed on Jan. 9, 2024, 9 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/137,353, mailed on Jan. 31, 2024, 2 pages. |
| Decision on Appeal received for U.S. Appl. No. 16/259,771, mailed on Feb. 8, 2024, 18 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 17/461,014, mailed on Jan. 29, 2024, 13 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 19212057.4, mailed on Jan. 31, 2024, 6 pages. |
| Notice of Allowance received for Chinese Patent Application No. 202310124087.2, mailed on Jan. 25, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2023282284, mailed on Jan. 19, 2024, 6 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2023-0064928, mailed on Sep. 22, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/971,456, mailed on Oct. 16, 2023, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/197,242, mailed on Apr. 4, 2024, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/220,715, mailed on Apr. 8, 2024, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/220,715, mailed on Apr. 25, 2024, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201780033901.2, mailed on Apr. 16, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 18/138,634, mailed on Apr. 18, 2024, 9 pages. |
| Office Action received for Chinese Patent Application No. 202110530629.7, mailed on Mar. 14, 2024, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/031,765, mailed on Apr. 9, 2024, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/031,765, mailed on Apr. 19, 2024, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/138,634, mailed on May 20, 2024, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/197,242, mailed on May 15, 2024, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/241,802, mailed on May 17, 2024, 57 pages. |
| Notice of Hearing received for Indian Patent Application No. 201814036472, mailed on May 9, 2024, 2 pages. |
| Office Action received for European Patent Application No. 22729935.1, mailed on May 10, 2024, 7 pages. |
| Office Action received for Japanese Patent Application No. 2022-170806, mailed on May 13, 2024, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/197,242, mailed on Mar. 27, 2024, 2 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/033376, mailed on Mar. 18, 2024, 21 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2023/033376, mailed on Jan. 24, 2024, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,765, mailed on Apr. 2, 2024, 34 pages. |
| Office Action received for Japanese Patent Application No. 2022-194369, mailed on Mar. 15, 2024, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2023-7039673, mailed on Feb. 20, 2024, 11 pages (2 pages of English Translation and 9 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 17/031,765, mailed on Nov. 13, 2023, 5 pages. |
| Decision to Grant received for Japanese Patent Application No. 2023-146062, mailed on Nov. 13, 2023, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7029729, mailed on Nov. 9, 2023, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2022263576, mailed on Nov. 13, 2023, 3 pages. |
| Office Action received for Chinese Patent Application No. 201780033901.2, mailed on Oct. 31, 2023, 17 pages (10 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2022-170806, mailed on Nov. 17, 2023, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,765, mailed on Oct. 31, 2023, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/137,353, mailed on Nov. 9, 2023, 10 pages. |
| Office Action received for Chinese Patent Application No. 202310124087.2, mailed on Sep. 9, 2023, 24 pages (13 pages of English Translation and 11 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 17/031,765, mailed on Sep. 1, 2023, 37 pages. |
| Final Office Action received for U.S. Appl. No. 18/119,789, mailed on Aug. 30, 2023, 29 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/093,408, mailed on Aug. 30, 2023, 59 pages. |
| Office Action received for European Patent Application No. 21728746.5, mailed on Aug. 21, 2023, 4 pages. |
| Rozario, Hamlin, “How to Edit Photos on iPhone & iPad”, Online Available at: https://osxdaily.com/2020/01/23/how-to-edit-photos-on-iphone-ipad/, Jan. 23, 2020, 10 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022263576, mailed on Dec. 12, 2023, 3 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 18/119,789, mailed on Jan. 22, 2024, 45 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/138,634, mailed on Jan. 16, 2024, 14 pages. |
| Office Action received for European Patent Application No. 21728746.5, mailed on Jan. 11, 2024, 4 pages. |
| [B612] Addition of facial recognition bear/cat stamps and AR background function having moving sparkles or hearts, Available Online at: <URL, htpps://apptopi.jp/2017/0l/22/b612>, Jan. 22, 2017, 11 pages. |
| Advisory Action received for U.S. Appl. No. 13/082,035, mailed on Jun. 19, 2015, 5 pages. |
| Advisory Action received for U.S. Appl. No. 13/082,035, mailed on Oct. 23, 2013, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/833,014, mailed on Jan. 27, 2017, 3 pages. |
| Advisory Action received for U.S. Appl. No. 16/259,771, mailed on Feb. 26, 2020, 3 pages. |
| Advisory Action received for U.S. Appl. No. 16/259,771, mailed on Jul. 14, 2020, 6 pages. |
| Advisory Action received for U.S. Appl. No. 16/806,981, mailed on Jun. 14, 2021, 6 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/109,487, mailed on Apr. 21, 2020, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/259,771, mailed on May 5, 2020, 10 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/806,981, mailed on Jan. 28, 2022, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 17/031,671, mailed on Aug. 2, 2021, 5 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 17/031,671, mailed on Jun. 13, 2022, 7 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 17/031,671, mailed on Nov. 8, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 13/082,035, mailed on Apr. 4, 2013, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 13/082,035, mailed on Aug. 1, 2016, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 13/082,035, mailed on Jan. 29, 2015, 3 pages. |
| Applicant-Initiated interview Summary received for U.S. Appl. No. 13/082,035, mailed on Oct. 30, 2013, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 14/866,560, mailed on Jan. 30, 2019, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 14/866,560, mailed on Jul. 26, 2018, 3 pages. |
| Applicant-Initiated interview Summary received for U.S. Appl. No. 14/866,560, mailed on May 14, 2019, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 14/866,560, mailed on Oct. 21, 2019, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/259,771, mailed on Apr. 18, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/519,850, mailed on Jun. 26, 2020, 4 pages. |
| Applicant-Initiated interview Summary received for U.S. Appl. No. 16/599,433, mailed on Apr. 20, 2021, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/663,062, mailed on Dec. 18, 2020, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/833,436, mailed on Jan. 27, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/833,436, mailed on Jul. 1, 2021, 2 pages. |
| Applicant-Initiated interview Summary received for U.S. Appl. No. 17/031,654, mailed on Feb. 1, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,765, mailed on Dec. 15, 2021 , 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/031,765, mailed on May 23, 2022, 5 pages. |
| Applicant-Initiated interview Summary received for U.S. Appl. No. 17/031,765, mailed on Sep. 22, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/093,408, mailed on Jul. 1, 2022, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/093,408, mailed on Mar. 1, 2022, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/373,163, mailed on Apr. 11, 2022, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 19172407.9, mailed on Nov. 9, 2020, 1 page. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 19172407.9, mailed on Nov. 20, 2020, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20176616.9, mailed on Jun. 9, 2022, 1 page. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 20176616.9, mailed on May 27, 2022, 1 page. |
| Certificate of Examination received for Australian Patent Application No. 2019100420, mailed on Jul. 3, 2019, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2019100497, mailed on Jul. 29, 2019, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2019100794, mailed on Dec. 19, 2019, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2019101019, mailed on Nov. 12, 2019, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2019101667, mailed on Mar. 20, 2020, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2020100189, mailed on May 12, 2020, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2020100675, mailed on Jun. 30, 2020, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2020101043, mailed on Dec. 22, 2020, 2 pages. |
| Certificate of Examination received for Australian Patent Application No. 2020101715, mailed on Oct. 6, 2020, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/713,490, mailed on May 1, 2019, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/142,288, mailed on Jul. 30, 2019, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/143,097, maiied on Nov. 8, 2019, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/519,850, mailed on Jul. 30, 2019, 5 pages. Notice of Allowance received for U.S. Appl. No. 16/519,850, mailed on Nov. 8, 2019, 3 pages. Notice of Allowance received for U.S. Appl. No. 16/519,850, mailed on Nov. 2, 2020, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/519,850, mailed on Sep. 8, 2020, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/599,433, mailed on Aug. 13, 2021, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/599,433, mailed on Oct. 14, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/663,062, mailed on Apr. 14, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/663,062, mailed on Jul. 21, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/091,460, mailed on Feb. 16, 2022, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/091,460, mailed on Feb. 25, 2022, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/125,744, mailed on Dec. 8, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/125,744, mailed on Dec. 24, 2021, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/125,744, mailed on Mar. 10, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/125,744, mailed on Mar. 30, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/373,163, mailed on Jul. 15, 2022, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/373,163, mailed on Jun. 27, 2022, 5 pages. |
| Decision on Appeai received for Korean Patent Application No. 10-2021-7002582, mailed on May 13, 2022, 29 pages. |
| Decision on Appeai received for U.S. Appl. No. 14/833,014, mailed on Oct. 30, 2019, 10 pages. |
| Decision on Appeal received for U.S. Appl. No. 16/259,771, mailed on Aug. 19, 2021, 12 pages. |
| Decision to Grant received for Danish Patent Application No. PA201670320, mailed on Oct. 18, 2018, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870372, mailed on Jun. 17, 2020, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870375, mailed on Jul. 24, 2019, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870377, mailed on May 14, 2019, 2 pages. |
| Decision to Grant received for European Patent Application No. 15759998.6, mailed on Jun. 18, 2020, 2 pages. |
| Decision to Grant received for European Patent Application No. 19172407.9, mailed on Jun. 17, 2021, 2 pages. |
| Decision to Grant received for European Patent Application No. 20168021.2, mailed on Feb. 3, 2022, 2 pages. |
| Decision to Grant received for Japanese Patent Application No. 2018-182607, mailed on Apr. 13, 2022, 3 pages. |
| Decision to Grant received for Japanese Patent Application No. 2020-193703, mailed on Aug. 10, 2021, 3 pages. |
| Decision to Refuse received for European Patent Application No. 17813778.2, mailed on Jan. 24, 2022, 17 pages. |
| Decision to Refuse received for European Patent Application No. 19204230.7, mailed on Feb. 4, 2022, 15 pages. |
| Decision to Refuse received for European Patent Application No. 19724959.2, mailed on Jun. 22, 2021, 13 pages. |
| European Search Report received for European Patent Application No. 19172407.9, mailed on Oct. 9, 2019, 4 pages. |
| European Search Report received for European Patent Application No. 19181242.9, mailed on Nov. 27, 2019, 4 pages. |
| European Search Report received for European Patent Application No. 20168021.2, mailed on Jul. 8, 2020, 4 pages. |
| Examiner Interview Summary received for U.S. Appl. No. 16/806,981, mailed on Mar. 26, 2021, 2 pages. |
| Examiner-Initiated Interview Summary received for U.S. Appl. No. 16/806,981, mailed on Jan. 13, 2022, 4 pages. |
| Examiner-Initiated Interview Summary received for U.S. Appl. No. 16/806,981, mailed on May 24, 2021, 4 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/833,014, mailed on Nov. 2, 2017, 48 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 16/259,771, mailed on May 26, 2023, 23 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 16/259,771, mailed on Oct. 23, 2020, 15 pages. |
| Examiner's Pre-Review Report received for Japanese Patent Application No. 2019- 215503, mailed on Aug. 20, 2021, 15 pages. |
| Extended European Search Report received for European Patent Application No. 17813778.2, mailed on Jan. 10, 2020, 12 pages. |
| Extended European Search Report received for European Patent Application No. 17853657.9, mailed on May 28, 2020, 9 pages. |
| Extended European Search Report received for European Patent Application No. 19204230.7, mailed on Feb. 21, 2020, 7 pages. |
| Extended European Search Report received for European Patent Application No. 19212057.4, mailed on Feb. 27, 2020, 8 pages. |
| Extended European Search Report received for European Patent Application No. 20176616.9, mailed on Sep. 8, 2020, 7 Pages. |
| Extended European Search Report received for European Patent Application No. 22154034.7, mailed on May 11, 2022, 14 pages. |
| Final Office Action received for U.S. Appl. No. 13/082,035, mailed on Apr. 16, 2015, 24 pages. |
| Final Office Action received for U.S. Appl. No. 13/082,035, mailed on Aug. 15, 2013, 24 pages. |
| Final Office Action received for U.S. Appl. No. 14/833,014, mailed on Oct. 26, 2016, 32 pages. |
| Final Office Action received for U.S. Appl. No. 14/866,560, mailed on Oct. 9, 2018, 22 pages. |
| Final Office Action received for U.S. Appl. No. 15/352,215, mailed on Mar. 7, 2019, 22 pages. |
| Final Office Action received for U.S. Appl. No. 16/116,221, mailed on Mar. 22, 2019, 35 pages. |
| Final Office Action received for U.S. Appl. No. 16/259,771, mailed on Aug. 12, 2022, 25 pages. |
| Final Office Action received for U.S. Appl. No. 16/259,771, mailed on Nov. 18, 2019, 13 pages. |
| Final Office Action received for U.S. Appl. No. 16/806,981, mailed on Apr. 14, 2021, 24 pages. |
| Final Office Action received for U.S. Appl. No. 16/806,981, mailed on Mar. 1, 2022, 33 pages. |
| Final Office Action received for U.S. Appl. No. 16/833,436, mailed on Sep. 21, 2021, 29 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,671, mailed on Sep. 7, 2021, 27 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,765, mailed on Oct. 29, 2021, 34 pages. |
| Final Office Action received for U.S. Appl. No. 17/093,408, mailed on May 18, 2022, 41 pages. |
| Here are Warez Files:Eve Online Character Creator, Online Available at: <http://theherearewarezfiles.blogspot.com/2014/03/eve-online-character-creator-download.html>, Mar. 3, 2014, 7 pages. |
| Intention to Grant received for Danish Patent Application No. PA201670320, mailed on May 17, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870372, mailed on Feb. 13, 2020, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870375, mailed on Jun. 3, 2019, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870375, mailed on Mar. 26, 2019, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870377, mailed on Mar. 26, 2019, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA202070623, mailed on Jul. 20, 2022, 2 pages. |
| Intention to Grant received for European Patent Application No. 15759998.6, mailed on Apr. 17, 2020, 10 pages. |
| Intention to Grant received for European Patent Application No. 15759998.6, mailed on Nov. 21, 2019, 12 pages. |
| Intention to Grant received for European Patent Application No. 19172407.9, mailed on Feb. 11, 2021, 9 pages. |
| Intention to Grant received for European Patent Application No. 19181242.9, mailed on Oct. 28, 2021, 16 pages. |
| Intention to Grant received for European Patent Application No. 20168021.2, mailed on Apr. 15, 2021, 8 pages. |
| Intention to Grant received for European Patent Application No. 20168021.2, mailed on Sep. 20, 2021, 8 pages. |
| International Pretiminary Report on Patentability received for PCT Patent Appkication No. PCT/US2011/031616, mailed on Oct. 18, 2012, 6 pages. |
| International Preliminary Report on Patentability received for PCT Patent Apptication No. PCT/US2015/046262, mailed on Mar. 16, 2017, 26 pages |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/035322, mailed on Dec. 27, 2018, 13 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/049795, mailed on Apr. 4, 2019, 16 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/023793, mailed on Nov. 19, 2020, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/024067, mailed on Nov. 19, 2020, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Appiication No. PCT/US2020/014176, mailed on Jul. 29, 2021, 9 pages. |
| International Search Report and Written Opinion received for PCT Application No. PCT/US2017/049795, mailed on Dec. 27, 2017., 26 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/031616, mailed on Aug. 30, 2011, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2011/048169, mailed on Oct. 21, 2011., Oct. 21, 2011, 9 pages. |
| International Search Report and Written Opinion Received for PCT Patent Application No. PCT/US2017/035322, mailed on Oct. 5, 2017, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/023793, mailed on Aug. 27, 2019, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/024067, mailed on Oct. 9, 2019, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/014176, mailed on Mar. 26, 2020, 12 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/031096, mailed on Oct. 13, 2021, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2021/031212, mailed on Sep. 21, 2021, 21 pages. |
| Invitation to Pay Additionai Fees received for PCT Patent Application No. PCT/US2017/035322, mailed on Aug. 7, 2017, 4 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2017/049795, mailed on Nov. 3, 2017, 3 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/023793, mailed on Jul. 5, 2019, 11 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2019/024067, mailed on Jul. 16, 2019, 13 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2021/031096, mailed on Aug. 19, 2021, 8 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2021/031212, mailed on Jul. 28, 2021, 19 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 19724959.2, mailed on Feb. 25, 2020, 3 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 17813778.2, mailed on Jan. 21, 2022, 7 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 19181242.9, mailed on Dec. 15, 2020, 6 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 19204230.7, mailed on Feb. 2, 2022, 9 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 19724959.2, mailed on Jun. 14, 2021, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/082,035, mailed on Apr. 21, 2016, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/082,035, mailed on Dec. 19, 2012, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/082,035, mailed on Sep. 11, 2014, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/866,560, mailed on Apr. 19, 2018, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/866,560, mailed on Apr. 30, 2019, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/275,294, mailed on Dec. 23, 2016., 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/275,294, mailed on Nov. 3, 2017, 29 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/352,215, mailed on Sep. 20, 2018, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/391,269, mailed on Aug. 22, 2019, 44 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/109,487, mailed on Feb. 5, 2020, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/116,221, mailed on Nov. 13, 2018, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/142,288, mailed on Nov. 20, 2018, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/142,305, mailed on Nov. 23, 2018, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/142,328, mailed on Nov. 8, 2018, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/143,097, mailed on Feb. 28, 2019, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/259,771, mailed on Jan. 25, 2022, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/259,771, mailed on May 8, 2019, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/519,850, mailed on Mar. 23, 2020, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/599,433, mailed on Jan. 28, 2021, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/663,062, mailed on Oct. 28, 2020, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/806,981, mailed on Nov. 13, 2020, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/806,981, mailed on Sep. 1, 2021, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/833,436, mailed on Mar. 29, 2021, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,654, mailed on Nov. 19, 2020, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,671, mailed on Apr. 1, 2022, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,671, mailed on Apr. 30, 2021, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,765, mailed on Jun. 28, 2021, 32 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,765, mailed on Mar. 29, 2022, 33 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/091,460, mailed on Sep. 10, 2021, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/093,408, mailed on Dec. 8, 2021, 37 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/370,505, mailed on Jul. 6, 2022, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/373,163, mailed on Jan. 27, 2022, 14 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017330212, mailed on Apr. 28, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019265357, mailed on Dec. 24, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019266049, mailed on Nov. 24, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019271873, mailed on Nov. 30, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Apptication No. 2020213402, mailed on Sep. 21, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020239749, mailed on May 27, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020267310, mailed on Feb. 23, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020294208, mailed on Mar. 2, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021201295, mailed on May 10, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022201561, mailed on Jul. 22, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017284958, mailed on Sep. 3, 2019, 3 Pages. |
| Notice of Allowance received for Chinese Patent Appiication No. 201510557356.X, mailed on Mar. 5, 2020, 2 pages. |
| Notice of Allowance received for Chinese Patent Appiication No. 201811616429.8, mailed on Aug. 5, 2020, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201910315328.5, mailed on Aug. 24, 2022, 4 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201910379481.4, mailed on Nov. 9, 2020, 6 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201910692978.1, mailed on Feb. 4, 2021, 6 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201911202668.3, mailed on Feb. 4, 2021, 5 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201911219525.3, mailed on Sep. 29, 2020, 2 pages. |
| Notice of Allowance received for Danish Patent Application No. PA201570563, mailed on May 24, 2016, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-107114, mailed on Mar. 22, 2019, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2018-184254, mailed on Jun. 15, 2020, 5 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-123115, mailed on Nov. 30, 2020, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-511767, mailed on Mar. 30, 2020, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-120086, mailed on Nov. 15, 2021, 5 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-159825, mailed on Mar. 25, 2022, 5 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2021-000224, mailed on May 7, 2021, 4 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2021-094529, mailed on Sep. 6, 2021, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2018-7034875, mailed on Dec. 12, 2018, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7005369, mailed on Oct. 26, 2020, 4 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7007053, mailed on Dec. 19, 2019, 6 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7007053, mailed on Mar. 12, 2020, 6 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7005314, mailed on Mar. 23, 2020, 6 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7018255, mailed on Feb. 24, 2021, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7031855, mailed on Mar. 22, 2021, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7032147, mailed on May 12, 2021, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7019525, mailed on Jul. 13, 2021, 5 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2021-7023617, mailed on Dec. 21, 2021, 6 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7002829, mailed on Feb. 12, 2022, 6 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7016421, mailed on May 25, 2022, 6 pages. |
| Notice of Allowance received for Netherland Patent Application No. 2019753, mailed on Jul. 6, 2018, 6 pages. |
| Notice of Allowance received for Taiwanese Patent Application No. 104128684, mailed on Feb. 23, 2017, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/082,035, mailed on Oct. 5, 2016, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/833,014, mailed on Nov. 20, 2019, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/866,560, mailed on Nov. 15, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/275,294, mailed on Jun. 6, 2018, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/275,294, mailed on Jun. 30, 2017., 8 Pages. |
| Notice of Allowance received for U.S. Appl. No. 15/352,215, mailed on Nov. 27, 2019, 20 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/713,490, mailed on Mar. 20, 2019, 15 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/109,487, mailed on Aug. 18, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/109,487, mailed on May 12, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/109,487, mailed on Nov. 23, 2020, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/110,514, mailed on Apr. 29, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/110,514, mailed on Mar. 13, 2019, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/116,221, mailed on Nov. 22, 2019, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/116,221, mailed on Sep. 20, 2019, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/142,288, mailed on Jun. 24, 2019, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/142,288, mailed on Mar. 27, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/142,288, mailed on May 1, 2019, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/142,305, mailed on Apr. 3, 2019, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/142,305, mailed on May 1, 2019, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/142,328, mailed on Apr. 5, 2019, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,097, mailed on Aug. 29, 2019, 23 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,201, mailed on Feb. 8, 2019, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/143,201, mailed on Nov. 28, 2018, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/519,850, mailed on Aug. 26, 2020, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/599,433, mailed on May 14, 2021, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/599,433, mailed on Oct. 4, 2021, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/663,062, mailed on Jul. 13, 2021, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/663,062, mailed on Mar. 24, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/833,436, mailed on Jul. 7, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,654, mailed on Feb. 10, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/031,654, mailed on May 27, 2021, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/091,460, mailed on Apr. 28, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/091,460, mailed on Feb. 4, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/091,460, mailed on May 23, 2022, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/125,744, mailed on Feb. 7, 2022, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/125,744, mailed on Oct. 21, 2021, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/373,163, mailed on Jul. 27, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/373,163, mailed on May 11, 2022, 8 pages. |
| Office Action received for Australian Patent Application No. 2017330212, mailed on Feb. 21, 2020, 2 pages. |
| Office Action received for Australian Patent Application No. 2019100794, mailed on Oct. 3, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2019271873, mailed on Oct. 5, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2020100189, mailed on Apr. 1, 2020, 3 pages. |
| Office Action received for Australian Patent Application No. 2020101043, mailed on Aug. 14, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2020101043, mailed on Oct. 30, 2020, 4 pages. |
| Office Action received for Australian Patent Application No. 2020239749, mailed on Jan. 21, 2022, 4 pages. |
| Office Action received for Australian Patent Application No. 2020239749, mailed on Jul. 16, 2021, 5 pages. |
| Office Action received for Australian Patent Application No. 2020267310, mailed on Nov. 4, 2021, 2 pages. |
| Office Action received for Australian Patent Application No. 2020294208, mailed on Dec. 17, 2021, 2 pages. |
| Office Action received for Australian Patent Application No. 2021201295, mailed on Jan. 14, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2021202254, mailed on Jun. 20, 2022, 2 pages. |
| Office Action received for Australian Patent Application No. 2022201561, mailed on May 2, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2017284958, mailed on Dec. 13, 2018, 3 pages. |
| Office Action received for Chinese Patent Application No. 201510557356.X, mailed on Aug. 15, 2019, 12 pages. |
| Office Action received for Chinese Patent Application No. 201510557356.X, mailed on Dec. 29, 2017, 11 pages. |
| Office Action received for Chinese Patent Application No. 201510557356.X, mailed on Nov. 23, 2018, 12 pages. |
| Office Action received for Chinese Patent Application No. 201520679198.0, mailed on Jun. 24, 2016, 5 pages. |
| Office Action received for Chinese Patent Application No. 201621208900.6, mailed on Apr. 26, 2017, 2 pages. |
| Office Action received for Chinese Patent Application No. 201810411708.4, mailed on Feb. 24, 2022, 10 pages. |
| Office Action received for Chinese Patent Application No. 201810411708.4, mailed on Feb. 26, 2021, 16 pages. |
| Office Action received for Chinese Patent Application No. 201810411708.4, mailed on Nov. 12, 2021, 12 pages. |
| Office Action received for Chinese Patent Application No. 201811616429.8, mailed on May 7, 2020, 8 pages. |
| Office Action received for Chinese Patent Application No. 201811616429.8, mailed on Sep. 4, 2019, 26 pages. |
| Office Action received for Chinese Patent Application No. 201910315328.5, mailed on Nov. 30, 2021, 21 pages. |
| Office Action received for Chinese Patent Application No. 201910379481.4, mailed on Mar. 2, 2020, 18 pages. |
| Office Action received for Chinese Patent Application No. 201910691865.X, mailed on Aug. 4, 2021, 10 pages. |
| Office Action received for Chinese Patent Application No. 201910691865.X, mailed on Feb. 4, 2021, 16 pages. |
| Office Action received for Chinese Patent Application No. 201910691865.X, mailed on Jul. 8, 2020, 17 pages. |
| Office Action received for Chinese Patent Application No. 201910691872.X, mailed on Jun. 3, 2020, 10 pages. |
| Office Action received for Chinese Patent Application No. 201910691872.X, mailed on Jun. 23, 2021, 10 pages. |
| Office Action received for Chinese Patent Application No. 201910691872.X mailed on Mar. 24, 2021, 19 pages. |
| Office Action received for Chinese Patent Application No. 201910691872.X, mailed on Nov. 10, 2021, 16 pages. |
| Office Action received for Chinese Patent Application No. 201910692978.1, mailed on Apr. 3, 2020, 19 pages. |
| Office Action received for Chinese Patent Application No. 201910692978.1, mailed on Nov. 4, 2020, 4 pages. |
| Office Action received for Chinese Patent Application No. 201911199054.4, mailed on Jan. 20, 2021, 19 pages. |
| Office Action received for Chinese Patent Application No. 201911199054.4, mailed on Jul. 3, 2020, 15 pages. |
| Office Action received for Chinese Patent Application No. 201911199054.4, mailed on Jun. 10, 2021, 13 pages. |
| Office Action received for Chinese Patent Application No. 201911202668.3, mailed on Aug. 4, 2020, 13 pages. |
| Office Action received for Chinese Patent Application No. 201911219525.3, mailed on Jul. 10, 2020, 7 pages. |
| Office Action received for Chinese Patent Application No. 202010330318.1, mailed on Jul. 13, 2021, 12 pages. |
| Office Action received for Chinese Patent Application No. 202010330318.1, mailed on Mar. 31, 2021, 13 pages. |
| Office Action received for Chinese Patent Application No. 202010330318.1, mailed on Nov. 19, 2020, 18 pages. |
| Office Action received for Chinese Patent Application No. 202110820692.4, mailed on Mar. 15, 2022, 18 pages. |
| Office Action received for Danish Patent Application No. PA201670319, mailed on Aug. 2, 2016, 6 pages. |
| Office Action received for Danish Patent Application No. PA201670319, mailed on Jun. 21, 2017, 6 pages. |
| Office Action received for Danish Patent Application No. PA201670319, mailed on Nov. 24, 2016, 7 pages. |
| Office Action received for Danish Patent Application No. PA201670320, mailed on Aug. 4, 2016, 9 pages. |
| Office Action received for Danish Patent Application No. PA201670320, mailed on Dec. 5, 2016, 4 pages. |
| Office Action received for Danish Patent Application No. PA201670320, mailed on Jan. 18, 2018, 2 pages. |
| Office Action received for Danish Patent Application No. PA201670320, mailed on Jul. 3, 2017, 4 pages. |
| Office Action received for Danish Patent Application No. PA201670608, mailed on Jan. 14, 2019, 7 pages. |
| Office Action received for Danish Patent Application No. PA201670608, mailed on Jan. 23, 2018, 10 pages. |
| Office Action received for Danish Patent Application No. PA201670609, mailed on Jan. 26, 2018, 8 pages. |
| Office Action received for Danish Patent Application No. PA201670609, mailed on Mar. 1, 2019, 9 pages. |
| Office Action received for Danish Patent Application No. PA201670609, mailed on May 4, 2020, 7 pages. |
| Office Action received for Danish Patent Application No. PA201670609, mailed on May 7, 2018, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870366, mailed on Aug. 22, 2019, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870366, mailed on Dec. 12, 2018, 3 pages. |
| Office Action received for Danish Patent Application No. PA201870367, mailed on Dec. 20, 2018, 5 pages. |
| Office Action received for Danish Patent Application No. PA201870368, mailed on Dec. 20, 2018, 5 pages. |
| Office Action received for Danish Patent Application No. PA201870368, mailed on Oct. 1, 2019, 6 pages. |
| Office Action received for Danish Patent Application No. PA201870372, mailed on Aug. 20, 2019, 2 pages. |
| Office Action received for Danish Patent Application No. PA201870372, mailed on Jan. 31, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870374, mailed on Feb. 6, 2019, 5 pages. |
| Office Action received for Danish Patent Application No. PA201870374, mailed on Jun. 17, 2019, 5 pages. |
| Office Action received for Danish Patent Application No. PA201870375, mailed on Jan. 31, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA201870377, mailed on Jan. 31, 2019, 4 pages. |
| Office Action received for Danish Patent Application No. PA202070623, mailed on Aug. 24, 2021, 3 pages. |
| Office Action received for Danish Patent Application No. PA202070623, mailed on May 23, 2022, 3 pages. |
| Office Action received for Danish Patent Application No. PA202070624, mailed on Feb. 4, 2022, 4 pages. |
| Office Action received for Danish Patent Application No. PA202070624, mailed on Jun. 16, 2021, 5 pages. |
| Office Action received for Danish Patent Application No. PA202070625, mailed on Feb. 8, 2022, 2 pages. |
| Office Action received for Danish Patent Application No. PA202070625, mailed on Jun. 16, 2021, 3 pages. |
| Office Action received for European Patent Application No. 15759998.6, mailed on Dec. 19, 2018, 6 pages. |
| Office Action received for European Patent Application No. 15759998.6, mailed on Jul. 16, 2018, 6 pages. |
| Office Action received for European Patent Application No. 15759998.6, mailed on May 29, 2019, 6 pages. |
| Office Action received for European Patent Application No. 17813778.2, mailed on Nov. 26, 2020, 10 pages. |
| Office Action received for European Patent Application No. 17853657.9, mailed on Apr. 1, 2021, 6 pages. |
| Office Action received for European Patent Application No. 19172407.9, mailed on Oct. 18, 2019, 7 pages. |
| Office Action received for European Patent Application No. 19181242.9, mailed on Dec. 6, 2019, 9 pages. |
| Office Action received for European Patent Application No. 19204230.7, mailed on Sep. 28, 2020, 6 pages. |
| Office Action received for European Patent Application No. 19212057.4, mailed on Mar. 9, 2021, 6 pages. |
| Office Action received for European Patent Application No. 19724959.2, mailed on Apr. 23, 2020, 10 pages. |
| Office Action received for European Patent Application No. 20168021.2, mailed on Jul. 22, 2020, 8 pages. |
| Office Action received for European Patent Application No. 20176616.9, mailed on Jun. 10, 2021, 4 pages. |
| Office Action received for Indian Patent Application No. 201814036470, mailed on Feb. 26, 2021, 7 pages. |
| Office Action received for Indian Patent Application No. 201814036472, mailed on Jul. 8, 2021, 8 pages. |
| Office Action received for Japanese Patent Application No. 2017-510631, mailed on Mar. 2, 2018, 12 pages. |
| Office Action received for Japanese Patent Application No. 2018-107114, mailed on Oct. 9, 2018, 4 pages. |
| Office Action received for Japanese Patent Application No. 2018-182607, mailed on Apr. 6, 2020, 6 pages. |
| Office Action received for Japanese Patent Application No. 2018-182607, mailed on Jul. 20, 2020, 5 pages. |
| Office Action received for Japanese Patent Application No. 2018-182607, mailed on Sep. 8, 2021, 7 pages. |
| Office Action received for Japanese Patent Application No. 2018-184254, mailed on Mar. 2, 2020, 8 pages. |
| Office Action received for Japanese Patent Application No. 2019-123115, mailed on Aug. 31, 2020, 9 pages. |
| Office Action received for Japanese Patent Application No. 2019-215503, mailed on Feb. 5, 2021, 12 pages. |
| Office Action received for Japanese Patent Application No. 2019-215503, mailed on Jul. 3, 2020, 12 pages. |
| Office Action received for Japanese Patent Application No. 2020-120086, mailed on May 21, 2021, 6 pages. |
| Office Action received for Japanese Patent Application No. 2020-120086, mailed on Nov. 20, 2020, 6 pages. |
| Office Action received for Japanese Patent Application No. 2020-159823, mailed on Dec. 23, 2021, 8 pages. |
| Office Action received for Japanese Patent Application No. 2020-159824, mailed on Dec. 17, 2021, 13 pages. |
| Office Action received for Japanese Patent Application No. 2020-159825, mailed on Dec. 10, 2021, 4 pages. |
| Office Action received for Japanese Patent Application No. 2020-193703, mailed on Apr. 19, 2021, 4 pages. |
| Office Action received for Japanese Patent Application No. 2021-092483, mailed on Apr. 1, 2022, 8 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7005369, mailed on Mar. 13, 2020, 12 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7007053, mailed on Mar. 18, 2019, 12 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7007053, mailed on Sep. 26, 2019, 9 pages. |
| Office Action received for Korean Patent Application No. 10-2020-0123852, mailed on Jun. 9, 2022, 10 pages. |
| Office Action received for Korean Patent Application No. 10-2020-0123857, mailed on Jun. 9, 2022, 12 pages. |
| Office Action received for Korean Patent Application No. 10-2020-0123887, mailed on Jun. 9, 2022, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7018255, mailed on Sep. 10, 2020, 12 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7031855, mailed on Nov. 24, 2020, 6 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7032147, mailed on Feb. 16, 2021, 6 pages. |
| Office Action received for Korean Patent Application No. 10-2021-7002582, mailed on Apr. 16, 2021, 13 pages. |
| Office Action received for Korean Patent Application No. 10-2021-7002582, mailed on Oct. 29, 2021, 6 pages. |
| Office Action received for Korean Patent Application No. 10-2022-7003364, mailed on Apr. 22, 2022, 14 pages. |
| Office Action received for Netherland Patent Application No. 2019753, mailed on Apr. 12, 2018, 8 pages. |
| Office Action received for Taiwanese Patent Application No. 100111887, mailed on Oct. 7, 2013, 23 pages. |
| Office Action received for Taiwanese Patent Application No. 104128684, mailed on Nov. 8, 2016, 24 pages. |
| Pre-Appeal Review Report received for Japanese Patent Application No. 2018-182607, mailed on Jan. 21, 2021, 4 pages. |
| Record of Oral Hearing received for U.S. Appl. No. 16/259,771, mailed on Aug. 4, 2021, 15 pages. |
| Result of Consultation received for European Patent Application No. 17813778.2, mailed on Dec. 6, 2021, 17 pages. |
| Result of Consultation received for European Patent Application No. 19172407.9, mailed on Nov. 5, 2020, 17 pages. |
| Result of Consultation received for European Patent Application No. 19204230.7, mailed on Nov. 16, 2020, 3 pages. |
| Result of Consultation received for European Patent Application No. 19204230.7, mailed on Sep. 24, 2020, 5 pages. |
| Result of Consultation received for European Patent Application No. 19724959.2, mailed on Sep. 4, 2020, 3 pages. |
| Result of Consultation received for European Patent Application No. 19181242.9, mailed on Dec. 1, 2020, 12 pages. |
| Search Report and opinion received for Danish Patent Application No. PA201670608, mailed on Jan. 3, 2017, 15 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201670609, mailed on Feb. 1, 2017, 11 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870366, mailed on Aug. 27, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870367, mailed on Aug. 27, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870368, mailed on Sep. 6, 2018, 7 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870372, mailed on Sep. 14, 2018, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870372, mailed on Sep. 17, 2018, 10 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870374, mailed on Aug. 27, 2018, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870375, mailed on Aug. 23, 2018, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870377, mailed on Sep. 4, 2018, 8 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070623, mailed on Dec. 21, 2020, 9 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070624, mailed on Dec. 10, 2020, 10 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA202070625, mailed on Dec. 17, 2020, 9 pages. |
| Search Report and Opinion received for Netherlands Patent Application No. 2015364, issued on Jul. 4, 2017, 12 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17813778.2, mailed on Aug. 13, 2021, 13 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19172407.9, mailed on Jun. 24, 2020, 14 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19181242.9, mailed on Jun. 16, 2020, 12 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19181242.9, mailed on May 19, 2022, 7 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19204230.7, mailed on May 25, 2021, 10 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19724959.2, mailed on Feb. 1, 2021, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19724959.2, mailed on Mar. 31, 2021, 3 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 20176616.9, mailed on Dec. 17, 2021, 7 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/833,014, mailed on Mar. 12, 2020, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 15/713,490, mailed on May 30, 2019, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/143,201, mailed on Dec. 13, 2018, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/143,201, mailed on Dec. 19, 2018, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/143,201, mailed on Jan. 10, 2019, 2 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 16/833,436, mailed on Jul. 14, 2022, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/833,014, mailed on Mar. 21, 2016, 26 pages. |
| Office Action received for Australian Patent Application No. 2015101183, issued on Nov. 6, 2015, 4 pages. |
| Office Action received for Chinese Patent Application No. 2015206791980, mailed on Mar. 7, 2016, 6 pages. |
| Office Action Received for Chinese Patent Application No. 2015206791980, mailed on Nov. 18, 2015, 4 pages. |
| Ali et al., “Facial Expression Recognition Using Human to Animated-Character Expression Translation”, Oct. 12, 2019, 8 pages. |
| Applivgames, ““Super Mario Run” Stickers for iMessage: Free Delivery Started!”, Available online at: <https://games.app-liv.jp/archives/178627>, Sep. 13, 2016, 3 pages. |
| Carretero et al., “Preserving Avatar Genuineness in Different Display Media”, Mobile Networks and Applications, Kluwer Academic Publishers, BO, vol. 13, No. 6, Jul. 15, 2008, pp. 627-634. |
| Chen et al., “Event Detection from Flickr Data through Wavelet-based Spatial Analysis”, Proceeding of the 18th ACM Conference on Information and Knowledge Management, CIKM, Jan. 1, 2009, pp. 523-532. |
| Contents Pocket, “Line Stamp Information”, Available online at: <https://web.archive.org/web/20150404080541/http://contents-pocket.net/linestamp.html>, Apr. 2015, 2 pages. |
| Das et al., “Event Classification in Personal Image Collections”, IEEE Intl. Workshop on Media Information Analysis for Personal and Social Applications at ICME, 2009, 2009, pp. 1660-1663. |
| Das et al., “Event-based Location Matching for Consumer Image Collections”, CIVR, 2008, Proc. of the ACM Int. Conf. on Image and Video Retrieval, 2008, 5 pages. |
| Enterbrain, “No. 5 Create your own Avatar Mii Studio”, vol. 26, No. 11, P.138, Feb. 24, 2011, 4 pages. |
| Fedko Daria, “AR Hair Styles”, Online Available at <https://www.youtube.com/watch?v=FrS6tHRbFE0>, Jan. 24, 2017, 2 pages. |
| Flatlinevertigo, “Black Desert Online :: Intro to Hair Customization”, Online Available at: <https://www.youtube.com/watch?v=9MCbfd_eMEg>, Sep. 9, 2015, 3 pages. |
| Gallagher et al., “Image Annotation Using Personal Calendars as Context”, ACM Intl. Conf. on Multimedia, 2008, 2008, 4 pages. |
| Gao et al., “Automatic Unpaired Shape Deformation Transfer”, ACM Transactions on Graphics, online available at: https://doi.org/10.1145/3272127.3275028, 2018, 11 pages. |
| Han et al., “Density-Based Methods”, Data Mining Concepts and Techniques, Elsevier, 2006, pp. 418-420. |
| Horowitz Paul, “Always Show Scroll Bars in Mac OS X”, OS X Daily, available online at: URL:http:jjosxdaily.com/2011/08/03/show-scroll-bars-mac-os-x-lion/, Aug. 3, 2011, 7 pages. |
| Hughes Neil, “Apple Explores Merging Cloud Content with Locally Stored Media Library”, Available at http://appleinsider.com/articles/11/02/10/apple_explores_merging_cloud_content_with_locally_stored_media_library.html>, XP55040717, Feb. 10, 2011, 2 pages. |
| Ilovex, ““Stripe Generator”, a tool that makes it easy to create striped materials”, Online available at : https://www.ilovex.co.jp/blog/system/webconsulting/stripe-generator.html, May 2, 2012, 3 pages. |
| Koti Kotresh, “Colour with Asian Paints.A Mobail App by Android Application—2018”, Available Online at <https://www.youtube.com/watch?v=M6EIO7ErYd0&feature=youtu.be&t=81>, May 6, 2018, 2 pages. |
| Kozak Tadeusz, “When You're Video Chatting on Snapchat, How Do You Use Face Filters?”, Quora, Online Available at: https://www.quora.com/When-youre-video-chatting-on-Snapchat-how-do-you-use-face-filters, Apr. 29, 2018, 1 page. |
| Kyoko Makino, “How to Make a Lookalike Face Icon for Your Friend”, ASCII, Japan Weekly, ASCII Media Works Inc., vol. 24, pp. 90-93, Jul. 17, 2014, 7 pages. |
| Lang Brian, “How to Audio & Video Chat with Multiple Users at the Same Time in Groups”, Snapchat 101, Online Available at: https://smartphones.gadgethacks.com/how-to/snapchat-101-audio-video-chat-with-multiple-users-same-time-groups-0184113/>, Apr. 17, 2018, 4 pages. |
| Liao, T.W. , “Clustering of Time Series Data—a Survey”, Pattern Recognition, vol. 38, 2005, pp. 1857-1874. |
| Marwan et al., “Generalised Recurrence Plot Analysis for Spatial Data”, Physics Letters A, vol. 360, 2007, pp. 545-551. |
| Mitsuru Takeuchi, “Face Shape Selection for Automatic Avatar Generation”, 13th Annual Conference Proceedings of Virtual Reality Society of Japan tournament Papers [DVD-ROM], The Virtual Reality Society of Japan, Sep. 24, 2008, 7 pages. |
| Neurotechnology, “Sentimask SDK”, Available at: https://www.neurotechnology.com/sentimask.html, Apr. 22, 2018, 5 pages. |
| Noh et al., “Expression Cloning”, Proceedings of the 28th annual conference on Computer Graphics and Interactive Techniques, ACM SIGGRAPH, Los Angeles, CA, USA, Aug. 12-17, 2001, 12 pages. |
| Intention To Grant received for Danish Patent Application No. PA201570563, mailed on Mar. 17, 2016, 7 pages. |
| PC World, “How to make AR Emojis on the Samsung Galaxy S9”, You Tube, Available Online: https://www.youtube.com/watch?v=8wQICfulkz0, Feb. 25, 2018, 2 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/046262, mailed on Mar. 15, 2016, 34 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/046262, mailed on Nov. 23, 2015, 7 pages. |
| Pumarola et al., “GANimation: Anatomically-aware Facial Animation from a Single Image”, Proceedings of the European Conference on Computer Vision (ECCV), Jul. 24, 2018, 16 pages. |
| Pyun et al., “An Example-Based Approach for Facial Expression Cloning”, SIGGRAPH Symposium on Computer Animation, The Eurographics Association (2003), 2003, 10 pages. |
| Rosa et al., “Stripe Generator—a Free Tool for the Web Design Community”, Available online at: http://www.stripegenerator.com/, Mar. 28, 2019, 10 pages. |
| Singh Lovepreet, “Samsung Galaxy Watch: How to Change Watch Face—Tips and Tricks”, Online available at: <https://www.youtube.com/watch?pp=desktop&v=IN7gPxTZ1qU>, Dec. 4, 2018, 80 pages. |
| Slashgear, “Samsung AR Emoji demo on the Galaxy S9”, Available Online at <https://www.youtube.com/watch?v=GQwNKzY4C9Y>, Feb. 25, 2018, 3 pages. |
| Spellburst,“The SIMS 3: Create a SIM With Me | #2—Dark Fairy + Full CC List!”, Available online at: <https://www.youtube.com/watch?v=Dy_5g9B-wkA>, Oct. 9, 2017, 2 pages. |
| Tech With Brett, “How to Create Your AR Emoji on the Galaxy S9 and S9+”, Available online at: <https://www.youtube.com/watch?v=HHMdcBpC8MQ>, Mar. 16, 2018, 5 pages. |
| Theunlockr, “Galaxy Watch Complete Walkthrough: The Best Watch They've Made So Far”, Available online at: https://www.youtube.com/watch?v=xiEClfe1SN4, Sep. 11, 2018, 27 pages. |
| Tsuchihashi et al., “Generation of Caricatures by Automatic Selection of Templates for Shapes and Placement of Facial Parts”, Technical Report of the Institute of Image Information and Television Engineers, Japan, The Institute of Image Information and Television Engineers, vol. 33, No. 11, pp. 77-80., Feb. 8, 2009, 7 pages. |
| Van Wijk et al., “Cluster and Calendar based Visualization of Time Series Data”, IEEE Comput. Soc., 1999, 7 pages. |
| Vidstube, “Bitmoji Clockface on Fitbit Versa Sense/Versa 3/Versa 2”, Available online at: <https://www.youtube.com/watch?v=4V_xDnSLeHE>, Retrieved on Dec. 30, 2020, Jun. 30, 2019, 1 page. |
| Woolsey Amanda, “How to Customize the Clock on the Apple Watch”, Available online at: <https://www.youtube.com/watch?v=t-3Bckdd9B4>, Retrieved on Dec. 11, 2020, Apr. 25, 2015, 1 page. |
| Zhang et al., “Facial Expression Retargeting from Human to Avatar Made Easy”, IEEE Transactions on Visualization and Computer Graphics, Aug. 2020, 14 pages. |
| Zhao et al., “An Event-related Potential Comparison of Facial Expression Processing between Cartoon and Real Faces”, Online available at: https://www.biorxiv.org/content/10.1101/333898v2, Jun. 18, 2018, 31 pages. |
| Zy News, “Generate Cartoon Face within Three Seconds, you are the New-generation Expression Emperor”, Online available at: <http://inews.ifeng.com/48551936/news.shtml>, Apr. 22, 2016, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/138,634, mailed on Feb. 9, 2024, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/197,242, mailed on Feb. 22, 2024, 2 pages. |
| Decision to Refuse received for European Patent Application No. 17853657.9, mailed on Feb. 2, 2024, 17 pages. |
| Decision to Refuse received for European Patent Application No. 19212057.4, mailed on Feb. 5, 2024, 18 pages. |
| Notice of Hearing received for Indian Patent Application No. 201814036470, mailed on Feb. 7, 2024, 4 pages. |
| Record of Oral Hearing received for U.S. Appl. No. 16/259,771, mailed on Feb. 4, 2024, 15 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/197,242, mailed on Mar. 18, 2024, 2 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/031979, mailed on Mar. 12, 2024, 16 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2023/031979, mailed on Jan. 19, 2024, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/197,242, mailed on Mar. 6, 2024, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/220,715, mailed on Mar. 7, 2024, 11 pages. |
| Office Action received for Chinese Patent Application No. 202010295272.4, mailed on Feb. 5, 2024, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2024-7004853, mailed on Mar. 4, 2024, 6 pages (2 pages of English Transtation and 4 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/093,408, mailed on Sep. 13, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/093,408, mailed on Sep. 20, 2023, 3 pages. |
| Krotov, Ilya, “Bellus3D app experience”, Available online at: https://www.youtube.com/watch?v=aSu688IY26c&t=45s, Aug. 17, 2021, 2 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2023200039, mailed on Aug. 31, 2023, 3 pages. |
| Advisory Action received for U.S. Appl. No. 17/031,765, mailed on Dec. 12, 2022, 7 pages. |
| Advisory Action received for U.S. Appl. No. 17/093,408, mailed on Jun. 5, 2023, 4 pages. |
| Interview Summary received for U.S. Appl. No. 17/031,671, mailed on Dec. 9, 2022, 5 pages. |
| Interview Summary received for U.S. Appl. No. 17/031,671, mailed on May 23, 2023, 3 pages. |
| Interview Summary received for U.S. Appl. No. 17/031,765, mailed on Apr. 17, 2023, 4 pages. |
| Interview Summary received for U.S. Appl. No. 17/031,765, mailed on May 3, 2023, 6 pages. |
| Interview Summary received for U.S. Appl. No. 17/031,765, mailed on Nov. 16, 2022, 5 pages. |
| Interview Summary received for U.S. Appl. No. 17/093,408, mailed on Jan. 5, 2023, 3 pages. |
| Interview Summary received for U.S. Appl. No. 17/093,408, mailed on May 10, 2023, 3 pages. |
| Interview Summary received for U.S. Appl. No. 17/093,408, mailed on May 25, 2023, 2 pages. |
| Interview Summary received for U.S. Appl. No. 17/370,505, mailed on Oct. 17, 2022, 4 pages. |
| Interview Summary received for U.S. Appl. No. 17/461,014, mailed on Feb. 21, 2023, 3 pages. |
| Interview Summary received for U.S. Appl. No. 17/744,499, mailed on Jan. 27, 2023, 3 pages. |
| Interview Summary received for U.S. Appl. No. 17/746,179, mailed on Nov. 28, 2022, 4 pages. |
| Interview Summary received for U.S. Appl. No. 17/941,962, mailed on May 30, 2023, 2 pages. |
| Interview Summary received for U.S. Appl. No. 18/119,789, mailed on Jul. 31, 2023, 4 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 19181242.9, mailed on Oct. 5, 2022, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/370,505, mailed on Apr. 4, 2023, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/370,505, mailed on Apr. 28, 2023, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/370,505, mailed on Mar. 8, 2023, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/525,664, mailed on Apr. 11, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/525,664, mailed on Feb. 23, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/525,664, mailed on May 17, 2023, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/525,664, mailed on Nov. 3, 2022, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/744,499, mailed on Mar. 21, 2023, 4 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/941,962, mailed on Apr. 14, 2023, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/941,962, mailed on Aug. 3, 2023, 2 pages. |
| Decision to Grant received for European Patent Application No. 19181242.9, mailed on Mar. 23, 2023, 3 pages. |
| Decision to Grant received for Japanese Patent Application No. 2021-166686, mailed on Apr. 20, 2023, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Decision to Grant received for Japanese Patent Application No. 2023-083816, mailed on Aug. 9, 2023, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Decision to Refuse received for Japanese Patent Application No. 2020-159824, mailed on Sep. 30, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Droid Life,“20+ Galaxy S9, S9+ Tips and Tricks”, Available Online at: https://www.youtube.com/watch?v−sso0mYTfV6w, Mar. 22, 2018, pp. 1-33. |
| European Search Report received for European Patent Application No. 22164099.8, mailed on Aug. 25, 2022, 9 pages. |
| European Search Report received for European Patent Application No. 22179347.4, mailed on Oct. 13, 2022, 7 pages. |
| Extended European Search Report received for European Patent Application No. 23168077.8, mailed on Jul. 11, 2023, 12 pages. |
| European Search Report received for European Patent Application No. 23173355.1, mailed on Aug. 4, 2023, 8 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,671, mailed on Nov. 15, 2022, 27 pages. |
| Final Office Action received for U.S. Appl. No. 17/031,765, mailed on Sep. 12, 2022, 37 pages. |
| Final Office Action received for U.S. Appl. No. 17/093,408, mailed on Mar. 2, 2023, 51 pages. |
| Final Office Action received for U.S. Appl. No. 17/461,014, mailed on Apr. 6, 2023, 24 pages. |
| Gauging Gadgets, “How to Customize Watch Faces—Garmin Venu Tutorial”, Online Available at: https://www.youtube.com/watch?v=dxajKKulaP0, Jan. 7, 2020, 14 pages. |
| Intention to Grant received for European Patent Application No. 19181242.9, mailed on Nov. 17, 2022, 9 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/031096, mailed on Nov. 24, 2022, 11 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2021/031212, mailed on Nov. 24, 2022, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2022/029811, mailed on Nov. 7, 2022, 15 pages. |
| Invitation to Pay Additional Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2022/029811, mailed on Sep. 14, 2022, 9 pages. |
| Jin-Chang et al., “Multi-modal Interface Techniques and Its Application for Multimedia Retrieval”, China Academic Journal Electronic Publishing House, 2002, pp. 115-117 (Official Copy only) (See Communication Under Rule 37 CFR § 1.98(a) (3). |
| Lein et al., “Patternizer”, Available online at: https://patternizer.com/, Apr. 2016, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,671, mailed on Mar. 17, 2023, 34 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/031,765, mailed on Mar. 28, 2023, 31 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/093,408, mailed on Sep. 14, 2022, 46 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/461,014, mailed on Dec. 7, 2022, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/744,499, mailed on Dec. 7, 2022, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/746,179, mailed on Oct. 25, 2022, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/827,004, mailed on Nov. 9, 2022, 27 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/119,789, mailed on Jun. 28, 2023, 31 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021202254, mailed on Nov. 16, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022200965, mailed on May 11, 2023, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022215297, mailed on Sep. 26, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2022220279, mailed on Sep. 27, 2022, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201780058426.4, mailed on Jun. 30, 2023, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 202110820692.4, mailed on Nov. 16, 2022, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Danish Patent Application No. PA202070623, mailed on Sep. 20, 2022, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2019-215503, mailed on Aug. 26, 2022, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2020-159823, mailed on Jul. 24, 2023, 23 pages (1 page of English Translation and 22 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-092483, mailed on Sep. 30, 2022, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2021-153573, mailed on Feb. 17, 2023, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0123852, mailed on Mar. 9, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0123852, mailed on Nov. 28, 2022, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0123857, mailed on Feb. 21, 2023, 6 pages (1 page of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0123887, mailed on Nov. 28, 2022, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7003364, mailed on Jul. 28, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2022-7009437, mailed on Jun. 22, 2023, 7 pages (2 pages of English Translation and 5 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/833,436, mailed on Sep. 8, 2022, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/370,505, mailed on Feb. 2, 2023, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/525,664, mailed on Apr. 26, 2023, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/525,664, mailed on Feb. 14, 2023, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/525,664, mailed on Oct. 27, 2022, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/736,925, mailed on Apr. 24, 2023, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/736,925, mailed on Aug. 3, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/744,499, mailed on Mar. 15, 2023, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/746,179, mailed on Mar. 6, 2023, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/941,962, mailed on Jul. 3, 2023, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/941,962, mailed on Mar. 10, 2023, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/941,962, mailed on May 3, 2023, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/971,456, mailed on Jun. 26, 2023, 9 pages. |
| Office Action received for Australian Patent Application No. 2022200965, mailed on Feb. 14, 2023, 4 pages. |
| Office Action received for Australian Patent Application No. 2023200039, mailed on Jul. 4, 2023, 2 pages. |
| Office Action received for Chinese Patent Application No. 201780033901.2, mailed on Jun. 28, 2023, 28 pages (14 pages of English Translation and 14 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201780033901.2, mailed on Nov. 23, 2022, 44 pages (24 pages of English Translation and 20 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201780058426.4, mailed on Dec. 2, 2022, 11 pages (5 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202010295272.4, mailed on Feb. 27, 2023, 15 pages (6 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202011127969.7, mailed on Jul. 28, 2022, 25 pages (14 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202011127969.7, mailed on Mar. 17, 2023, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202011127969.7, mailed on Nov. 24, 2022, 26 pages (16 pages of English Translation 10 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA202070625, mailed on Sep. 23, 2022, 4 pages. |
| Office Action received for European Patent Application No. 20704768.9, mailed on Mar. 24, 2023, 8 pages. |
| Office Action received for European Patent Application No. 22154034.7, mailed on May 26, 2023, 10 pages. |
| Office Action received for Indian Patent Application No. 202015008746, mailed on Mar. 6, 2023, 7 pages. |
| Office Action received for Indian Patent Application No. 202015008747, mailed on Mar. 15, 2023, 10 pages. |
| Office Action received for Indian Patent Application No. 202215026045, mailed on Mar. 31, 2023, 8 pages. |
| Office Action received for Indian Patent Application No. 202215026505, mailed on Feb. 8, 2023, 9 pages. |
| Office Action received for Japanese Patent Application No. 2020-159823, mailed on Aug. 15, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2021-153573, mailed on Oct. 17, 2022, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2021-166686, mailed on Oct. 3, 2022, 3 pages (2 pages of English Translation and 1 page of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2020-0123857, mailed on Dec. 16, 2022, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7003364, mailed on Dec. 26, 2022, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2022-7009437, mailed on Nov. 30, 2022, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2023-0064928, mailed on Jun. 9, 2023, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Pavlakos et al., “Expressive Body Capture: 3D Hands, Face, and Body from a Single Image”, In Proceedings of the IEEE/CVF conference on computer vision and pattern recognition 2019, online available at https://arxiv.org/abs/1904.05866, 2019, pp. 10975-10985. |
| Pre-Appeal Review Report received for Japanese Patent Application No. 2020-159823, mailed on Jan. 12, 2023, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17853657.9, mailed on May 2, 2023, 8 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19212057.4, mailed on Apr. 19, 2023, 9 pages. |
| Summons to Oral Proceedings received for European Patent Application No. 19724959.2, mailed on Jul. 14, 2023, 6 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/746,179, mailed on Apr. 3, 2023, 2 pages. |
| Takahashi et al., “Neural network modeling of altered facial expression recognition in autism spectrum disorders based on predictive processing framework”, Scientific reports, online available at :—https://www.nature.com/articles/s41598-021-94067-x, Jul. 26, 2021, 14 pages. |
| Wikipedia, “Emoji”, Online Available at: https://web.archive.org/web/20140829025736/https://en.wikipedia.org/wiki/Emoji, 2014, 13 pages. |
| Zollhöfer et al., “State of the Art on Monocular 3D Face Reconstruction, Tracking, and Applications”, In Computer graphics forum May 2018 (vol. 37, No. 2), online available at https://studios.disneyresearch.com/wp-content/uploads/2019/03/State-of-the-Art-on-Monocular-3D-Face-Reconstruction-Tracking-and-Applications-1.pdf., 2018, 28 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/119,789, mailed on Sep. 27, 2023, 3 pages. |
| Communication for Board of Appeal received for European Patent Application No. 19724959.2, mailed on Sep. 27, 2023, 14 pages. |
| Office Action received for Australian Patent Application No. 2023201250, mailed on Sep. 11, 2023, 3 pages. |
| Office Action received for Chinese Patent Application No. 202010295272.4, mailed on Aug. 28, 2023, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 17/031,671, mailed on Dec. 8, 2023, 16 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2022/029811, mailed on Nov. 30, 2023, 10 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2023/023273, mailed on Sep. 15, 2023, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 18/197,242, mailed on Dec. 7, 2023, 24 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2023201250, mailed on Nov. 21, 2023, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/971,456, mailed on Dec. 4, 2023, 2 pages. |
| Communication for Board of Appeal received for European Patent Application No. 19204230.7, mailed on Feb. 16, 2024, 1 page. |
| Office Action received for Chinese Patent Application No. 201780033901.2, mailed on Jan. 26, 2024, 14 pages (7 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for European Patent Application No. 22154034.7, mailed on Feb. 19, 2024, 8 pages. |
| Office Action received for Korean Patent Application No. 10-2023-7032383, mailed on Feb. 5, 2024, 16 pages (7 pages of English Translation and 9 pages of Official Copy). |
| Summons to Oral Proceedings received for European Patent Application No. 19204230.7, mailed on Feb. 19, 2024, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/138,634, mailed on May 2, 2024, 5 pages. |
| Decision to Grant received for Japanese Patent Application No. 2023-572180, mailed on Apr. 22, 2024, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for European Patent Application No. 23168077.8, mailed on Apr. 25, 2024, 7 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 17/031,765, mailed on May 2, 2024, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 18/241,802, mailed on Jul. 17, 2024, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/197,242, mailed on Jul. 22, 2024, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 18/220,715, mailed on Jul. 23, 2024, 2 pages. |
| Intention to Grant received for European Patent Application No. 21728746.5, mailed on Jul. 12, 2024, 10 pages. |
| Invitation to Pay Search Fees received for European Patent Application No. 21727979.3, mailed on Jul. 10, 2024, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/197,242, mailed on Jul. 10, 2024, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 18/204,908, mailed on Jul. 24, 2024, 6 pages. |
| Office Action received for Chinese Patent Application No. 202010295272.4, mailed on Jun. 11, 2024, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Ff14startup, How to create a character for beginners in FF14 and recommended races, Available online at: https://ff14startup.net/character-making-99/, Sep. 20, 2016, 16 pages (Official Copy Only) {See Communication Under Rule 37 CFR § 1.98(a) (3)}. |
| Maruberi, “[App Introduction] #3 Luxambra (Selecting the game to play with Hotman next after Maruberi)”, Available online at: https://www.youtube.com/watch?v=e4ukNZ-1OrY, Jun. 22, 2014, 2 pages (Official Copy Only) {See Communication Under Rule 37 CFR § 1.98(a) (3)}. |
| Non-Final Office Action received for U.S. Appl. No. 18/375,309, mailed on Jul. 29, 2024, 19 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2023282284, mailed on Jul. 18, 2024, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2023-043407, mailed on Jul. 26, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2023-0189466, mailed on Jul. 22, 2024, 8 pages (2 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for European Patent Application No. 22164099.8, mailed on Jul. 29, 2024, 10 pages. |
| Office Action received for Korean Patent Application No. 10-2023-7037034, mailed on Jul. 22, 2024, 23 pages (11 pages of English Translation and 12 pages of Official Copy). |
| WPshopmart, “Top 20 Creative Animated Login Form In HTML & CSS”, https://youtu.be/TDqT-7BnkD8?si =-R69GDvfR_IGrh2H, Dec. 6, 2019, 3 pages. |
| FF14startup, How to create a character for beginners in FF14 and recommended races, Available online at: https://ff14startup.net/character-making-99/, Sep. 20, 2016, 16 pages. |
| Maruberi, “[App Introduction] #3 Luxambra (Selecting the game to play with Hotman next after Maruberi)”, Available online at: https://www.youtube.com/watch?v=e4ukNZ-1OrY, Jun. 22, 2014, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2022-170806, mailed on Aug. 9, 2024, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202280036173.1, mailed on Jul. 21, 2024, 12 pages (6 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 202280036173.1, mailed on May 10, 2024, 16 pages (8 pages of English Translation and 8 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 18/204,908, mailed on Aug. 13, 2024, 2 pages. |
| Office Action received for Australian Patent Application No. 2023219926, mailed on Aug. 24, 2024, 5 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230379573 A1 | Nov 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62399294 | Sep 2016 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16259771 | Jan 2019 | US |
| Child | 18230465 | US | |
| Parent | 15713490 | Sep 2017 | US |
| Child | 16259771 | US |
