KR20190142782A - Multi-Device Charging User Interface - Google Patents

Abstract

The present disclosure generally relates to user interfaces for charging electronic devices. In a first device having a display, it is detected that at least one of the first device or the second device has entered a wireless charging state. In response to detecting that at least one of the first device or the second device has entered the wireless charging state, and in accordance with a determination that the first device and the second device are being wirelessly charged by the same wireless charging device, Display an indication of the state of charge for the second device.

Description

Multi-Device Charging User Interface

Cross Reference of Related Application

This application is filed on June 4, 2017 and filed with the invention "MULTI-DEVICE CHARGING USER INTERFACE," US Patent Application No. 62 / 514,924, filed September 9, 2017, and entitled "MULTI- US Patent Application No. 62 / 556,387, DEVICE CHARGING USER INTERFACE, and Danish Patent Application PA201870024, filed Jan. 12, 2018, entitled "MULTI-DEVICE CHARGING USER INTERFACE," The contents of which are hereby incorporated by reference in their entirety.

This application is related to US patent application Ser. No. 62 / 514,875, filed Jun. 4, 2017, entitled "SYNCHRONIZING COMPLEMENTARY NOTIFICATIONS ACROSS RELATED COMPUTING DEVICES CONNECTED TO A WIRELESS CHARGING APPARATUS." The entirety is incorporated by reference.

Technical Field

FIELD The present disclosure relates generally to computer user interfaces, and more particularly to techniques for charging a plurality of electronic devices.

Many modern electronic devices operate on rechargeable batteries. The charge level of the battery of the device decreases as the device is operated, so the device needs to be recharged from time to time for continued use. In addition, some users have a number of electronic devices and / or devices that require charging via a cable. Accordingly, there is a need for techniques for wirelessly charging multiple electronic devices.

However, some techniques for charging multiple electronic devices are generally cumbersome and inefficient. For example, some existing techniques for determining the charge level of one or more devices (eg, while one or more devices are being charged) use a complex and time consuming user interface, which may be multiple key presses or keystrokes. It may include. Existing techniques require more time than is needed, wasting user time and device energy. These previous considerations are particularly important for providing a user-friendly interface.

Thus, the present technique provides electronic devices with faster and more efficient methods and interfaces for charging multiple electronic devices. Such methods and interfaces optionally complement or replace other methods for charging multiple electronic devices. Such methods and interfaces reduce the cognitive burden on the user and create a more efficient human-machine interface. Such methods and interfaces improve the user experience, save power, and increase the time between battery charges.

In some embodiments, a computer-implemented method performed at a first device having a display includes: detecting that at least one of the first device or the second device has entered a wireless charging state; And in response to detecting that at least one of the first device or the second device has entered the wireless charging state, and in accordance with a determination that the first device and the second device are being wirelessly charged by the same wireless charging device. And displaying an indication of the state of charge for the second device.

In some embodiments, the non-transitory computer readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display, where the electronic device is a first device and the one or more programs are: Detect that at least one of the first device or the second device has entered a wireless charging state; In response to detecting that at least one of the first device or the second device has entered the wireless charging state, and in accordance with a determination that the first device and the second device are being wirelessly charged by the same wireless charging device, Instructions for displaying an indication of the state of charge for the second device.

In some embodiments, the temporary computer readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device having a display, where the electronic device is a first device and the one or more programs are: Detect that at least one of the first device or the second device has entered a wireless charging state; In response to detecting that at least one of the first device or the second device has entered the wireless charging state, and in accordance with a determination that the first device and the second device are being wirelessly charged by the same wireless charging device, Instructions for displaying an indication of the state of charge for the second device.

In some embodiments, an electronic device includes a display, one or more processors, and a memory that stores one or more programs configured to be executed by one or more processors, wherein the one or more programs are: at least one of an electronic device or a second device. Detect that one has entered a wireless charging state; In response to detecting that at least one of the electronic device or the second device has entered the wireless charging state, and in accordance with a determination that the electronic device and the second device are being wirelessly charged by the same wireless charging device, 2 instructions for displaying an indication of the state of charge for the device.

In some embodiments, the electronic device comprises a display; Means for detecting that at least one of the electronic device or the second device has entered a wireless charging state; And in response to detecting that at least one of the electronic device or the second device has entered the wireless charging state, and in accordance with a determination that the electronic device and the second device are being wirelessly charged by the same wireless charging device, Means for displaying an indication of the state of charge for the second device.

In some embodiments, a computer-implemented method performed on a device includes: receiving a first user input representing a request for a charge level while the device is being wirelessly charged and at a first charge level; In response to receiving the first user input, outputting a first non-visual indication of the first charge level of the device; While the device is being wirelessly charged at a second charge level that is different from the first charge level, receiving a second user input representing a request for a charge level; And in response to receiving the second user input, outputting a second non-visual indication of the second charge level of the device, wherein the second non-visual indication is different from the first non-visual indication. .

In some embodiments, a non-transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device, wherein the one or more programs are: While present, receiving a first user input representing a request for a charge level; In response to receiving the first user input, output a first non-visual indication of the first charge level of the device; While the device is charging wirelessly at a second charge level that is different from the first charge level, receive a second user input that represents a request for a charge level; In response to receiving the second user input, instructions for outputting a second non-visual indication of the second charge level of the device, wherein the second non-visual indication is different from the first non-visual indication. .

A temporary computer readable storage medium for storing one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs being: while the device is being wirelessly charged and at a first charge level, Receive a first user input representing a request; In response to receiving the first user input, output a first non-visual indication of the first charge level of the device; While the device is charging wirelessly at a second charge level that is different from the first charge level, receive a second user input that represents a request for a charge level; In response to receiving the second user input, instructions for outputting a second non-visual indication of the second charge level of the device, wherein the second non-visual indication is different from the first non-visual indication. .

In some embodiments, an electronic device includes one or more processors; And a memory that stores one or more programs configured to be executed by the one or more processors, wherein the one or more programs are configured to: express a request for a charge level while the device is being wirelessly charged and at a first charge level. 1 receive user input; In response to receiving the first user input, output a first non-visual indication of the first charge level of the device; While the device is charging wirelessly at a second charge level that is different from the first charge level, receive a second user input that represents a request for a charge level; In response to receiving the second user input, instructions for outputting a second non-visual indication of the second charge level of the device, wherein the second non-visual indication is different from the first non-visual indication. .

In some embodiments, the electronic device comprises: means for receiving a first user input representing a request for a charge level while the device is being wirelessly charged and at a first charge level; Means for outputting a first non-visual indication of the first charge level of the device in response to receiving the first user input; Means for receiving a second user input representing a request for a charge level while the device is being wirelessly charged at a second charge level that is different from the first charge level; And in response to receiving the second user input, means for outputting a second non-visual indication of the second charge level of the device, wherein the second non-visual indication is different from the first non-visual indication. Do.

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 temporary computer readable storage medium or other computer program product configured for execution by one or more processors.

Thus, devices are provided with faster and more efficient methods and interfaces for charging electronic devices, thereby increasing the effectiveness, efficiency and user satisfaction of such devices. Such methods and interfaces may complement or replace other methods for charging electronic devices.

For a better understanding of the various described embodiments, reference should be made to the following detailed description of the invention in connection with the following drawings in which like reference numerals indicate corresponding parts throughout the figures thereof.
1A is a block diagram illustrating a portable multifunction device having a touch-sensitive display in accordance with some embodiments.
1B is a block diagram illustrating example components for event processing in accordance with some embodiments.
2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.
3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, in accordance with some embodiments.
4A illustrates an example user interface for a menu of applications on a portable multifunction device, in accordance with some embodiments.
4B illustrates an example user interface for a multifunction device having a touch-sensitive surface separate from the display, in accordance with some embodiments.
5A illustrates a personal electronic device in accordance with some embodiments.
5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.
6A-6A illustrate example user interfaces for charging electronic devices in accordance with some embodiments.
7A-7E are flow diagrams illustrating methods of charging electronic devices, in accordance with some embodiments.
8A-8E illustrate example user interfaces for charging electronic devices, in accordance with some embodiments.
9A and 9B are flow diagrams illustrating methods of charging electronic devices, in accordance with some embodiments.
10 is a block diagram of an example wireless charging device, in accordance with some embodiments.
11A-11D illustrate example scenarios for charging electronic devices, in accordance with some embodiments.

The following description describes example methods, parameters, and the like. However, it should be appreciated that this description is not intended as a limitation on the scope of the present disclosure but instead is provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methods and interfaces for charging multiple devices. In one example, when multiple devices are being charged by the same charging device, the charge levels of all of the devices being charged are displayed simultaneously on one device. In another example, the device provides a non-visual indication of the charge level of the device itself and / or the charge level of another device (eg, another device being charged at the same time). Such techniques can reduce the cognitive burden on a user charging multiple devices, thereby improving productivity. In addition, such techniques can reduce processor and battery power otherwise wasted with redundant user inputs.

In the following, FIGS. 1A, 1B, 2, 3, 4A, 4B, 5A and 5B provide a description of example devices for performing techniques for charging electronic devices. 6A-6A illustrate example user interfaces for charging electronic devices. 7A-7E are flow diagrams illustrating methods of charging electronic devices, in accordance with some embodiments. The user interfaces of FIGS. 6A-6A are used to illustrate the processes described below, including the processes of FIGS. 7A-7E. 8A-8E also illustrate example user interfaces for charging electronic devices. 9A and 9B are flow diagrams illustrating methods of charging electronic devices, in accordance with some embodiments. The user interfaces of FIGS. 8A-8E are used to illustrate the processes described below, including the processes of FIGS. 9A-9B.

Although the following description uses terms such as "first", "second", and the like 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, without departing from the scope of the various embodiments described, the first touch may be referred to as the second touch, and similarly, the second touch may be referred to as the first touch. 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 variously 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 is intended. It is also to 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 items listed. The terms “include”, “including”, “comprise”, and / or “comprising”, as used herein, refer to features, integers, and the like. Specify presence of steps, steps, actions, elements, and / or components, but exist one or more other features, integers, steps, actions, elements, components, and / or groups thereof Or it will be further understood that no addition is excluded.

The term "if" optionally refers to "when" or "upon" or "in response to determining" or "depending on context". In response to detecting ”. Similarly, the phrase "if determined" or "if a [state or event mentioned] is detected" may optionally be "on decision" or "in response to a decision" or "[state or state mentioned] depending on the context). ] On detection "or" in response to detecting [state or event mentioned]] ".

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 communication device, such as a mobile phone, that also includes other functions such as PDA and / or music player functions. Exemplary embodiments of portable multifunction devices restrict iPhone®, iPod Touch®, and iPad® devices from Apple Inc., Cupertino, CA, USA. Includes without. Other portable electronic devices such as laptop or tablet computers with touch sensitive surfaces (eg, touch screen displays and / or touchpads) are optionally used. In some embodiments, it should also be understood that the device is not a portable communication device but a desktop computer having a touch-sensitive surface (eg, a touch screen display and / or a touchpad).

In the discussion that follows, an electronic device comprising a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices such as a physical keyboard, mouse and / or joystick.

The device typically supports a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website authoring applications, disk authoring applications, spreadsheet applications, game applications, telephony applications, video conferencing applications, email Applications, instant messaging applications, athletic assistance applications, photo management applications, digital camera applications, digital video camera applications, web browsing applications, digital music player applications, and / or digital video player applications.

Various applications running on the device optionally use at least one universal physical user interface device, such as a touch-sensitive surface. Corresponding information displayed on the device, as well as one or more functions of the touch-sensitive surface, are optionally coordinated and / or changed from one application to the next and / or within an individual application. In this way, the universal physical architecture (such as touch-sensitive surface) of the device optionally supports various applications using user interfaces that are intuitive and transparent to the user.

Attention is now directed to embodiments of portable devices with touch-sensitive displays. 1A is a block diagram illustrating a portable multifunction device 100 having a touch-sensitive display system 112, in accordance with some embodiments. The touch-sensitive display 112 is sometimes referred to as "touch screen" for convenience and sometimes referred to as or referred to as "touch-sensitive display system". Device 100 may include memory 102 (optionally including one or more computer readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripheral interface 118, RF Circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input control devices 116, and external port 124 It includes. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors for detecting the intensity of contacts on device 100 (eg, a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). 165). Device 100 may optionally include a touch pad 355 of device 100 or touch sensitive display system 112 of device 100 (eg, for generating tactile outputs on device 100). One or more tactile output generators 167 for generating tactile outputs on the same touch-sensitive surface. These components optionally communicate over one or more communication buses or signal lines 103.

As used in the specification and claims, the term "strength" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of the contact (eg, finger contact) on the touch-sensitive surface, or touch-sensitive It refers to a substitute (proxy) for the force or pressure of contact on the surface. The intensity of the contact has a range of values that includes at least four distinct values and more typically includes hundreds (eg, at least 256) distinct values. The intensity of the contact is optionally determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors below 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 (eg, weighted average) to determine an estimated force of the contact. Similarly, a pressure sensitive tip of the stylus is optionally used to determine the pressure of the stylus on the touch sensitive surface. Alternatively, the size and / or changes in the detected contact area on the touch-sensitive surface, the capacitance and / or changes therein in the touch-sensitive surface near the contact, and / or the touch-sensitive in the vicinity of the contact Surface resistance and / or variations thereon are optionally used as a substitute for the force or pressure of contact on the touch-sensitive surface. In some implementations, alternative measurements for contact force or pressure are directly used to determine whether the intensity threshold has been exceeded (eg, the intensity threshold is described in units corresponding to the alternative measurements). In some implementations, alternative measurements for contact force or pressure are converted to estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (eg, the intensity threshold is Pressure threshold measured in units of pressure). Using the intensity of contact as an attribute of user input may otherwise display affordances (eg, on a touch-sensitive display) and / or (eg, touch-sensitive display, touch-sensitive surface, or Enable user access to additional device functions that may not be accessible by the user on a reduced size device with limited real estate to receive user input (via a physical or mechanical control such as a knob or button) Let's do it.

As used in the specification and claims, the term “tactile output” refers to the physical displacement of the device relative to its previous position, the component of the device relative to other components of the device (eg, a housing) (eg, a touch-sensitive surface). ), Or the displacement of the component with respect to the center of mass of the device to be detected by the user using the user's tactile sense. For example, in situations where a device or component of the device is in contact with a touch sensitive user's surface (eg, a finger, palm, or other area of the user's hand), the tactile output generated by the physical displacement may be generated by the device or by the user. It will be interpreted as tactile sensation corresponding to a perceived change in the physical characteristics of the component of the device. For example, movement of a touch-sensitive surface (eg, 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, the user may feel tactile, such as “down click” or “up click” even when there is no movement of the physical actuator button associated with the touch-sensitive surface that is physically pressed (eg, displaced) by the user's movement. Will feel. As another example, the movement of the touch-sensitive surface is optionally interpreted by the user as "roughness" of the touch-sensitive surface even when there is no change in the smoothness of the touch-sensitive surface. Or detected. While these interpretations of touch by the user will be susceptible to the user's sensory perception, there are many touch sensory perceptions that are common to the majority of users. Thus, when tactile output is described as corresponding to a user's specific sensory perception (eg, "up click", "down click", "roughness"), unless otherwise stated, the generated tactile output is typical (or On average) corresponds to the physical displacement of the device or component thereof that will produce the described sensory perception of the user.

Device 100 is only one example of a portable multifunction device, and device 100 optionally has more or fewer components than shown, optionally, combines two or more components, or optionally a component. It should be understood that these have different configurations or arrangements. The various components shown in FIG. 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing circuits and / or application-specific integrated circuits (ASICs).

Memory 102 optionally includes high speed random access memory, and optionally also one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Non-volatile memory such as. Memory controller 122 optionally controls access to memory 102 by other components of device 100.

Peripheral interface 118 may be used to couple input and output peripherals of the device to CPU 120 and memory 102. One or more processors 120 run or execute various sets of software programs and / or instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripheral 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.

Radio frequency (RF) circuitry 108 receives and transmits RF signals, also referred to as electromagnetic signals. RF circuitry 108 converts electrical signals into / from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes, but is not limited to, an antenna system, an RF transceiver, one or more amplifiers, tuners, one or more oscillators, digital signal processors, CODEC chipsets, subscriber identity module (SIM) cards, memory, and the like. And, well known circuitry for performing these functions. The RF circuitry 108 may optionally include networks, such as the Internet, intranet, and / or wireless networks, also referred to as the World Wide Web (WWW), such as cellular telephone networks, wireless local area networks, and / or MANs. (metropolitan area network), and other devices by wireless communication. RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by short-range communication radio. Wireless communications may optionally include Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSPAA), Evolution (EV-DO) Data-Only, 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, protocols for email (e.g., Internet message access protocol (IMAP) and / or post office protocol (POP)), instant messaging (e.g., extensible messaging) and presence protocol), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (IMPLE), Instant Messaging and Presence Service (IMPS) , And / or a plurality of communication standards, protocols, including but not limited to any other suitable communication protocol, including, but not limited to, Short Message Service (SMS), or communication protocols not yet developed at the time of filing of this document. And any of the techniques.

The audio circuitry 110, the speaker 111, and the microphone 113 provide an audio interface between the user and the device 100. The audio circuit unit 110 receives audio data from the peripheral interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts an electrical signal into a sound wave that can be heard by a person. Audio circuitry 110 also receives electrical signals converted from sound waves by microphone 113. The audio circuitry 110 converts the electrical signal into audio data and transmits the audio data to the peripheral interface 118 for processing. Audio data is optionally withdrawn from memory 102 and / or RF circuitry 108 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 (eg, 212 of FIG. 2). The headset jack is provided between the audio circuitry 110 and the detachable audio input / output peripherals, such as a headset having output-only headphones, or both an output (eg one or both ear headphones) and an input (eg a microphone). Provide an interface.

I / O subsystem 106 couples input / output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripheral interface 118. I / O subsystem 106 may optionally include one or more input controllers for display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and other input or control devices. 160). One or more input controllers 160 receive / transmit electrical signals from / to other input control devices 116. Other input control devices 116 optionally include physical buttons (eg, push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and the like. In some alternative embodiments, input controller (s) 160 is optionally coupled to (or not coupled to) any of a pointer device, such as a keyboard, an infrared port, a USB port, and a mouse. . One or more buttons (eg, 208 of FIG. 2) optionally include an up / down button for volume control of the speaker 111 and / or the microphone 113. One or more buttons optionally include a push button (eg, 206 of FIG. 2).

Quick press of a push button initiates processes that selectively use gestures on the touch screen to unlock the touch screen 112 or unlock the device, which is a December 2005 23 As described in US Patent Application No. 11 / 322,549, "Unlocking a Device by Performing Gestures on an Unlock Image," filed on a date (US Pat. No. 7,657,849), which is hereby incorporated by reference in its entirety. do. Longer pressing of a push button (eg, 206) optionally powers the device 100 on or off. The functionality of one or more buttons is, 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 the user. Display controller 156 receives and / or transmits electrical signals from / to touch screen 112. The touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively referred to as "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 a user based on haptic and / or tactile contact. The touch screen 112 and the display controller 156 are in contact with the touch screen 112 (and any movement or interruption of the contact) (with any associated modules and / or sets of instructions in the memory 102). And convert the detected contact into an interaction with user interface objects (eg, one or more soft keys, icons, web pages or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to the user's finger.

The touch screen 112 optionally uses liquid crystal display (LCD) technology, light emitting polymer display (LPD) technology, or light emitting diode (LED) technology, but other display technologies are used in other embodiments. The touch screen 112 and the display controller 156 optionally select one or more contact points with capacitive, resistive, infrared, and surface acoustic wave technologies as well as other proximity sensor arrays, or the touch screen 112. Detects a contact and any movement or interruption thereof using any of a number of currently known or later developed touch sensing techniques, including but not limited to other factors for determining. In an exemplary embodiment, projected mutual capacitance sensing technology such as found on iPhone® and iPod Touch® from Apple Inc., Cupertino, Calif., Is used.

Touch-sensitive displays in some embodiments of touch screen 112 may optionally include the following US Pat. Nos. 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), And / or 6,677,932 (Westerman) And / or similar to the multi-touch sensitive touchpads described in US Patent Publication No. 2002 / 0015024A1, each of which is incorporated herein by reference in its entirety. However, touch screen 112 displays visual output from device 100, while touch-sensitive touchpads do not provide visual output.

Touch sensitive displays in some embodiments of touch screen 112 are described in the following applications: (1) US Patent Application No. 11 / 381,313, filed May 2, 2006, "Multipoint Touch Surface Controller "; (2) US Patent Application No. 10 / 840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) US Patent Application No. 10 / 903,964, filed July 30, 2004, "Gestures For Touch Sensitive Input Devices"; (4) US Patent Application No. 11 / 048,264, entitled "Gestures For Touch Sensitive Input Devices," filed Jan. 31, 2005; (5) US Patent Application No. 11 / 038,590, filed January 18, 2005, "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices"; (6) US patent application Ser. No. 11 / 228,758, filed September 16, 2005, "Virtual Input Device Placement On A Touch Screen User Interface"; (7) US Patent Application No. 11 / 228,700, filed September 16, 2005, "Operation Of A Computer With A Touch Screen Interface"; (8) US Patent Application No. 11 / 228,737, filed September 16, 2005, "Activating Virtual Keys Of A Touch-Screen Virtual Keyboard"; And (9) US Patent Application No. 11 / 367,749, "Multi-Functional Hand-Held Device", filed March 3, 2006. All of these applications are incorporated herein by reference in their entirety.

The 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 contacts the touch screen 112 using any suitable object or appendage, such as a stylus, a finger, or the like. In some embodiments, the user interface is designed to operate primarily using finger based contacts and gestures, which may be less precise than stylus based input due to the wider contact area 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 certain functions. In some embodiments, the touchpad, unlike the touch screen, is a touch-sensitive area of the device that does not display visual output. The touchpad is optionally an extension of the touch-sensitive surface formed by the touch screen or a touch-sensitive surface separate from the touch screen 112.

Device 100 also includes a power system 162 for powering various components. The power system 162 optionally includes a power management system, one or more power sources (eg, battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator. (Eg, a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in portable devices.

Device 100 also optionally includes one or more optical sensors 164. 1A illustrates an optical sensor coupled to an optical sensor controller 158 in I / O subsystem 106. Optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor 164 receives light from the environment, which is projected through one or more lenses, and converts the light into data representing an image. In conjunction with imaging module 143 (also referred to as camera module), optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the back side of the device 100 opposite the touch screen display 112 on the front of the device so that the touch screen display can be used as a viewfinder for still and / or video image acquisition. To be. In some embodiments, the optical sensor is located on the front of the device, optionally allowing the user's image to be acquired for video conferencing while the user views other video conferencing participants on the touch screen display. In some embodiments, the position of the light sensor 164 can be changed by the user (eg, by rotating the lens and sensor in the device housing) such that the single light sensor 164 is imaged with the touch screen display. It is used for both conference and still and / or video image acquisition.

Device 100 also optionally includes one or more contact intensity sensors 165. 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 in I / O subsystem 106. The contact intensity sensor 165 may optionally include one or more piezo resistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (eg, Sensors used to measure the force (or pressure) of the contact on the touch-sensitive surface). The contact intensity sensor 165 receives contact intensity information (eg, pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with or in proximity to a touch-sensitive surface (eg, touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back side of the device 100, opposite the touch screen display 112 located on the front side of the device 100.

Device 100 also optionally includes one or more proximity sensors 166. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is optionally coupled to input controller 160 in I / O subsystem 106. Proximity sensor 166 may optionally include US Patent Applications 11 / 241,839, "Proximity Detector In Handheld Device"; 11 / 240,788, "Proximity Detector In Handheld Device"; 11 / 620,702, "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586,862, "Automated Response To And Sensing Of User Activity In Portable Devices"; And 11 / 638,251, "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is located near the user's ear (eg, when the user is making a phone call).

Device 100 also optionally includes one or more tactile output generators 167. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components and / or a motor, solenoid, electroactive polymer, piezo actuator, electrostatic actuator, or other tactile output generation. Electromechanical devices that convert energy into linear motion, such as a component (eg, a component that converts electrical signals into tactile outputs on the device). The contact intensity sensor 165 receives tactile feedback generation instructions from the haptic feedback module 133 and generates tactile outputs on the device 100 that can be sensed by the user of the device 100. In some embodiments, the at least one tactile output generator is located with or close to the touch-sensitive surface (eg, touch-sensitive display system 112), and optionally, perpendicularly (eg, to) the touch-sensitive surface. To produce tactile output by moving in or out of the surface of device 100 or laterally (eg, back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back side of the device 100 opposite the touch screen display 112 located on the front side of the device 100.

Device 100 also optionally includes one or more accelerometers 168. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I / O subsystem 106. Accelerometer 168 may optionally include US Patent Publication No. 20050190059, "Acceleration-based Theft Detection System for Portable Electronic Devices" and US Patent Publication No. 20060017692, "Methods And Apparatuses For Operating A Portable Device Based On An". Accelerometer ", both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed in a portrait view or a landscape view on a touch screen display based on analysis of data received from one or more accelerometers. The device 100 optionally includes a magnetometer (not shown), in addition to the accelerometer (s) 168, and a GPS for obtaining information regarding the position and orientation (eg, vertical or horizontal) of the device 100. Or GLONASS or other global navigation system) receiver (not shown).

In some embodiments, 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 a set of instructions) 132, a text input module (or set of instructions) 134, a GPS module (or set of instructions) 135, and applications (or sets of instructions) 136. . In addition, in some embodiments, memory 102 of FIG. 1A or 370 of FIG. 3 stores device / global internal state 157 as shown in FIGS. 1A and 3. The device / global internal state 157, if present, includes an active application state indicating which applications are currently active; Display status indicating which applications, views, or other information occupy various areas of touch screen display 112; Sensor status including information obtained from various sensors of the device and input control devices 116; And location information regarding the location and / or attitude of the device.

Operating system 126 (e.g., an embedded operating system such as Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or VxWorks) provides general system tasks (e.g., memory management, storage device control, power management, etc.). Various software components and / or drivers for controlling and managing the network, and facilitating communication between various hardware and software components.

The communication module 128 enables communication with other devices via one or more external ports 124 and also for processing data received by the RF circuitry 108 and / or the external port 124. It includes various software components. The external port 124 (eg, Universal Serial Bus (USB), FireWire, etc.) is configured to couple directly to other devices or indirectly through a network (eg, the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (eg, 30-pin) connector that is the same as, similar to, and / or compatible with the 30-pin connector used in iPod® (trademark of Apple Inc.) devices.

The contact / motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156), and other touch-sensitive devices (eg, a touchpad or physical click wheel). . The contact / motion module 130 determines whether a contact has occurred (eg, detecting a finger-down event), the intensity of the contact (eg, the force or pressure of the contact, or the contact's Determining a substitute for force or pressure, determining if there is a movement of contact and tracking the movement across the touch-sensitive surface (eg, detecting one or more finger-dragging events). And various software components for performing various operations related to the detection of a contact, such as determining whether the contact has been stopped (eg, detecting a finger-up event or contact break). Include them. The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of a contact point represented by a series of contact data optionally determines the speed (size), speed (size and direction), and / or acceleration (change in size and / or direction) of the contact point. It involves doing. These actions optionally apply to single contacts (eg, one finger contacts) or to multiple simultaneous contacts (eg, “multi-touch” / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect a contact on the touchpad.

In some embodiments, contact / motion module 130 may determine whether the action was performed by the user (eg, determine whether the user “clicked” on the icon) a set of one or more intensity thresholds. Use In some embodiments, at least a subset of the intensity thresholds is determined in accordance with the software parameters (eg, the intensity thresholds are not determined by the activation thresholds of specific physical actuators, and changing the physical hardware of the device 100 is Can be adjusted without). For example, the mouse “click” threshold of a trackpad or touch screen display can be set to any of a wide range of predefined thresholds without changing the trackpad or touch screen display hardware. In addition, in some implementations, a user of the device can perform one or more of a set of intensity thresholds (eg, by adjusting individual intensity thresholds and / or by adjusting a plurality of intensity thresholds all at once with a system level click “strength” parameter). You are provided with software settings to adjust this.

The contact / motion module 130 optionally detects a gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (eg, different motions, timings, and / or intensities of detected contacts). Thus, the gesture is optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture may include detecting a finger-down event followed by a finger-at the same location (or substantially the same location) as the finger-down event (eg, at the icon's location). Detecting an up (liftoff) event. As another example, detecting a finger swipe gesture on a touch-sensitive surface detects a finger-down event followed by one or more finger-dragging events, followed by finger-up (liftoff). ) Detecting the event.

Graphics module 132 renders graphics on touch screen 112 or other displays, including components for modifying the visual effects (eg, brightness, transparency, saturation, contrast, or other visual properties) of the displayed graphics. It includes various known software components for display. As used herein, the term “graphics” includes without limitation text, web pages, icons (eg, user interface objects including soft keys), digital images, videos, animations, and the like. , Any object that can be displayed to the user.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes from applications or the like that specify graphics to be displayed, along with coordinate data and other graphics attribute data, if necessary, and then generates screen image data to display controller 156. Output

The haptic feedback module 133 is used by the haptic output generator (s) 167 to generate tactile outputs at one or more locations on the device 100 in response to user interactions with the device 100. It includes various software components for generating instructions.

Optionally, the text input module 134, which is a component of the graphics module 132, may require various applications (eg, contact 137, email 140, IM 141, browser 147, and text input). Soft keyboards for inputting text into any other application).

The GPS module 135 determines the location of the device and uses this information to call 138 for use in various applications (eg, for use in location based dialing; camera 143 as photo / video metadata). And to applications that provide location based services such as weather widgets, local yellow page widgets and map / navigation widgets.

The applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:

연락처 모듈(137)(때때로 주소록 또는 연락처 목록으로 지칭됨);

A contact module 137 (sometimes referred to as an address book or contact list);

전화 모듈(138);

Telephone module 138;

화상 회의 모듈(139);

Video conferencing module 139;

이메일 클라이언트 모듈(140);

Email client module 140;

인스턴트 메시징(IM) 모듈(141);

Instant messaging (IM) module 141;

운동 지원 모듈(142);

Exercise support module 142;

정지 및/또는 비디오 이미지들을 위한 카메라 모듈(143);

Camera module 143 for still and / or video images;

이미지 관리 모듈(144);

Image management module 144;

비디오 재생기 모듈;

Video player module;

음악 재생기 모듈;

A music player module;

브라우저 모듈(147);

Browser module 147;

캘린더 모듈(148);

Calendar module 148;

날씨 위젯(149-1), 주식 위젯(149-2), 계산기 위젯(149-3), 알람 시계 위젯(149-4), 사전 위젯(149-5), 및 사용자에 의해 획득되는 다른 위젯들뿐 아니라 사용자-생성 위젯들(149-6) 중 하나 이상을 선택적으로 포함하는 위젯 모듈들(149);

Weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user Widget modules 149, optionally including one or more of user-created widgets 149-6;

사용자-생성 위젯들(149-6)을 만들기 위한 위젯 생성기 모듈(150);

Widget generator module 150 for creating user-created widgets 149-6;

검색 모듈(151);

Search module 151;

비디오 재생기 모듈 및 음악 재생기 모듈을 통합하는 비디오 및 음악 재생기 모듈(152);

A video and music player module 152 that integrates a video player module and a music player module;

메모 모듈(153);

A memo module 153;

지도 모듈(154); 및/또는

Map module 154; And / or

온라인 비디오 모듈(155).

Online video module 155.

Examples of other applications 136, optionally stored in memory 102, include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital copyrights. Management, speech recognition and speech replication.

Together with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the contact module 137 may optionally include an address book or a contact list ( For example, stored in the application internal state 192 of the contact module 137 in the memory 102 or the memory 370. This includes: adding name (s) to the address book; that; Deleting name (s) from the address book; Associating telephone number (s), email 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 email addresses to initiate and / or facilitate communication by telephone 138, video conferencing module 139, email 140, or IM 141.

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 In conjunction with the input module 134, the telephone module 138 optionally enters a sequence of characters corresponding to the telephone number, accesses one or more telephone numbers in the contact module 137, and modifies the entered telephone number. It is used to dial, dial an individual phone number, have a conversation, and disconnect or disconnect when the conversation is complete. As mentioned above, wireless communication optionally uses any of a plurality of communication standards, protocols and technologies.

RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, light sensor 164, light sensor controller 158, contact / motion In conjunction with module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, video conferencing module 139 may be associated with the user and one or more other users. Executable instructions to initiate, initiate, and end a video conference between the participants.

The email client module 140, along with the RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, provides user instructions. Executable instructions to respond to, create, send, receive, and manage email. In conjunction with the image management module 144, the email client module 140 makes it very easy to create and send emails with still or video images taken with the camera module 143.

The instant messaging module 141, along with the RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, Enter a sequence of characters corresponding to the message, modify the previously entered characters (eg, Short Message Service (SMS) or Multimedia Message Service for phone-based instant messages) , MMS) protocol, or XMPP, SIMPLE or IMPS for Internet-based instant messages), executable instructions for sending individual instant messages, receiving instant messages, and viewing received instant messages. . In some embodiments, sent and / or received instant messages optionally include graphics, pictures, audio files, video files and / or other attachments supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant messaging" refers to telephone-based messages (eg, messages sent using SMS or MMS) and Internet-based messages (eg, messages sent using XMPP, SIMPLE or IMPS). S) both.

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, together with the music player module, exercise support module 142 devises exercises (eg, with time, distance, and / or calorie consumption goals); Communicate with athletic sensors (sports devices); Receive exercise sensor data; Calibrate sensors used to monitor exercise; Select and play music for a workout; Executable instructions for displaying, storing, and transmitting athletic data.

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 captures still images or videos (including video streams) and stores them in memory 102, modifies the characteristics of still images or videos, or captures still images or videos from memory 102. Executable instructions for deleting the video.

Together with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, and the camera module 143, the image management module 144 stops and And / or executable instructions for arranging, modifying (eg, editing), or otherwise manipulating, labeling, deleting, presenting (eg, in a digital slide show or album) and / or storing video images. .

The browser module 147, along with the RF circuitry 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132 and the text input module 134, is a web page. Executable instructions to browse the Internet in accordance with user instructions, including searching for, linking to, receiving, and displaying attachments and other files linked to web pages, as well as portions thereof or portions thereof Include them.

RF circuitry 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module ( In conjunction with 147, the calendar module 148 is executable to generate, display, modify, and store calendars and data associated with calendars (eg, calendar entries, to-do lists, etc.) in accordance with user instructions. Contains instructions.

Widget modules, along 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. 149 may be selectively downloaded and used by the user (eg, weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary). Widget 149-5), or mini-applications generated by a user (eg, user-generated widget 149-6). In some embodiments, the widget includes a Hypertext Markup Language (HTML) file, a Cascading Style Sheets (CSS) file, and a JavaScript (JavaScript) file. In some embodiments, the widget includes an Extensible Markup Language (XML) file and a JavaScript file (eg, Yahoo! widgets).

Widget generator module, 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 150 is optionally used by the user to create widgets (eg, changing a user specific portion of the web page to a widget).

In conjunction with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the search module 151 may generate one or more search criteria according to user instructions. Executable instructions for retrieving text, music, sound, image, video, and / or other files in memory 102 that match ones (eg, one or more user-specific search terms).

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 The video and music player module 152 executes instructions that allow a user to download and play recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and videos. Executable instructions to display, display, or otherwise play back on the touch screen 112 or on an externally connected display via an external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

Together with the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, and the text input module 134, the memo module 153 is capable of taking notes, to do according to user instructions. Executable instructions for creating and managing to-do lists and the like.

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 may optionally include, in accordance with user instructions, data associated with the maps and maps (eg, driving directions; data about shops and other points of interest at or near a particular location). And other location-based data).

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, In conjunction with the email client module 140 and the browser module 147, the online video module 155 allows a user to access and browse online videos in one or more file formats, such as H.264, (eg, streaming and And / or by downloading), playing (eg, on a touch screen or on an external connected display via external port 124), sending an email with a link to a particular online video, and otherwise managing it Contains instructions. In some embodiments, instant messaging module 141 rather than email client module 140 is used to send a link to a particular online video. Additional descriptions of online video applications are described in U.S. Provisional Patent Application 60 / 936,562, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," filed June 20, 2007 and 31 December 2007. See, for example, US Patent Application No. 11 / 968,067, "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," which is hereby incorporated by reference in its entirety, which is hereby incorporated by reference in its entirety. .

Each of the modules and applications identified above are executable instructions for performing one or more of the functions described above and the methods described herein (eg, computer-implemented methods and other information processing methods described herein). Corresponds to the set. These modules (eg, sets of instructions) need not be implemented as separate software programs, procedures or modules, so that various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. . For example, the video player module is optionally combined with the music player module into a single module (eg, the video and music player module 152 of FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. In addition, the memory 102 optionally stores additional modules and data structures not described above.

In some embodiments, device 100 is a device in which operation of a predefined set of functions on a device is performed exclusively through a touch screen and / or a touchpad. By using the touch screen and / or touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, etc.) on device 100 is selectively reduced.

The predefined set of functions performed solely via the touch screen and / or touch pad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 from any user interface displayed on the device 100 to the main, home, or root menu. In these embodiments, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of the touchpad.

1B is a block diagram illustrating example components for event processing in accordance with some embodiments. In some embodiments, memory (102 of FIG. 1A or 370 of FIG. 3) may include event classifier 170 (eg, in operating system 126) and individual applications 136-1 (eg, the applications described above). (137-151, 155, 380-390).

The event classifier 170 receives the event information, and determines an application 136-1 to transmit the event information, and an application view 191 of the application 136-1. The event classifier 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, application 136-1 includes an application internal state 192 that represents the current application view (s) displayed on touch-sensitive display 112 when the application is active or running. In some embodiments, the device / global internal state 157 is used by the event classifier 170 to determine which application (s) are currently active, and the application internal state 192 may be assigned to the event classifier 170. Is used to determine application views 191 to convey event information.

In some embodiments, application internal state 192 is a user indicating resume information to be used when application 136-1 resumes execution, information being displayed by or ready to be displayed by application 136-1. Interface state information, a state queue to enable the user to return to the previous state or view of the application 136-1, and a redo / undo queue of previous actions taken by the user. Include additional information such as one or more.

Event monitor 171 receives event information from peripherals interface 118. The event information includes information about the subevent (eg, user touch on the touch-sensitive display 112 as part of a multi-touch gesture). Peripheral interface 118 may be from I / O subsystem 106 or a sensor such as proximity sensor 166, accelerometer (s) 168, and / or microphone 113 (via audio circuitry 110). Send the information you receive. The information that peripheral interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (eg, receiving input exceeding a predetermined noise threshold and / or input for exceeding a predetermined duration). .

In some embodiments, event classifier 170 also includes a hit view determination module 172 and / or an active event recognizer determination module 173.

The hit view determination module 172 provides software procedures for determining where a subevent occurred within one or more views when the touch-sensitive display 112 displays more than one view. Views consist 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 referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. Application views (of individual applications) for which a touch is detected optionally correspond to program levels within the application's program or view hierarchy. For example, the lowest level view in which a touch is detected is optionally referred to as a hit view, and the set of events recognized as appropriate inputs is, optionally, based at least in part on the hit view of the initial touch initiating a touch based gesture. Is determined.

The hit view determination module 172 receives information related to subevents of a touch based gesture. If the application has multiple views organized in a hierarchy, the hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle the subevent. In most situations, the hit view is the lowest level view in which an initiating subevent (eg, a first subevent in a sequence of subevents forming an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all subevents related to the same touch or input source that caused it to be identified as a hit view.

The active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of subevents. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of subevents. In other embodiments, the active event recognizer determination module 173 determines that all views including the physical location of the subevent are actively involved views, so that all actively involved views are specific to the subevents. Determine that you need to receive the sequence. In other embodiments, even if touch subevents are entirely confined to an area associated with one particular view, the parent views in the hierarchy will still remain as actively participating views.

Event dispatcher module 174 dispatches event information to an event recognizer (eg, event recognizer 180). In embodiments that include an active event recognizer determination module 173, the event dispatcher module 174 delivers event information to an event recognizer determined by the active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information in an event queue, where the event information is retrieved by individual event receiver 182.

In some embodiments, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In still other embodiments, the event classifier 170 is a standalone module or part of another module stored in the memory 102, such as the 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 is a touch event that occurs within an individual view of an application's user interface. Instructions for processing them. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a high level object from which application 136-1 inherits methods and other attributes. to be. In some embodiments, the individual event handler 190 is one of the data updater 176, the object updater 177, the GUI updater 178, and / or the event data 179 received from the event classifier 170. It includes the above. Event handler 190 optionally uses or invokes data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more individual event handlers 190. Further, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included within individual application view 191.

Individual event recognizer 180 receives event information (eg, event data 179) from event classifier 170 and identifies the event from the event information. The event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of metadata 183 and event delivery instructions 188 (optionally including subevent delivery instructions).

The event receiver 182 receives event information from the event classifier 170. The event information includes information regarding sub-events, for example touch or touch movement. Depending on the subevent, the event information also includes additional information such as the location of the subevent. If the subevent is related to the motion of the touch, the event information also optionally includes the speed and direction of the subevent. In some embodiments, the events include rotation of the device from one orientation to another (eg, from vertical orientation to landscape orientation, or vice versa), wherein the event information is referred to as the device's current orientation (also referred to as the device attitude). Corresponding information).

The event comparator 184 compares the event information with predefined event or subevent definitions, and determines an event or subevent based on the comparison, or determines or updates the status of the event or subevent. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 include definitions of events (eg, predefined sequences of subevents), for example event 1 187-1, event 2 187-2, and the like. In some embodiments, subevents within event 187 include, for example, touch start, touch end, touch move, touch cancel, and multiple touch. In one example, the definition for event 1 187-1 is a double tap on the displayed object. The double tap is, for example, a first touch on the displayed object during the predetermined phase (start of touch), a first liftoff during the predetermined phase (end of touch), the displayed object during the predetermined phase. A second touch on the touch (touch start), and a second liftoff (touch end) during the predetermined phase. In another example, the definition for event 2 187-2 is dragging on the displayed object. Dragging includes, for example, a touch (or touch) on the displayed object during a predetermined phase, the movement of the touch across the touch-sensitive display 112, and the liftoff (touch end) of the touch. In some embodiments, the event also includes information about one or more associated event handlers 190.

In some embodiments, event definition 187 includes a definition of an event for an individual user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view in which three user interface objects are displayed on the touch-sensitive display 112, when a touch is detected on the touch-sensitive display 112, the event comparator 184 may display three user interface objects. A heat test is performed to determine which of these are associated with the touch (subevent). When each displayed object is associated with an individual event handler 190, the event comparator uses the results 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 object and subevent that triggers the hit test.

In some embodiments, the definition for the individual event 187 also includes delayed actions that delay delivery of event information until after determining whether the sequence of subevents corresponds to or does not correspond to the event type of the event recognizer. .

If the individual event recognizer 180 determines that the series of subevents does not match any of the events in the event definitions 186, the individual event recognizer 180 may not be able to event, fail the event, or terminate the event. After entering the state, the individual event recognizer ignores subsequent subevents of the touch based gesture. In this situation, other event recognizers, if any, remain active for the hit view to continue tracking and processing subevents of the ongoing touch-based gesture.

In some embodiments, the individual event recognizer 180 may configure configurable attributes, flags, and / or lists that indicate how the event delivery system should perform subevent delivery for actively participating event recognizers. Has metadata 183. In some embodiments, metadata 183 includes configurable attributes, flags, and / or lists that indicate how or to which event recognizers interact with each other. In some embodiments, metadata 183 includes configurable attributes, flags, and / or lists that indicate whether subevents are delivered at various levels in the view or program hierarchy.

In some embodiments, the individual event recognizer 180 activates an event handler 190 associated with the event when one or more specific subevents of the event are recognized. In some embodiments, individual event recognizer 180 passes event information associated with the event to event handler 190. Activating the event handler 190 is separate from sending (and delaying sending) subevents to individual hit views. In some embodiments, event recognizer 180 sends 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 subevent delivery instructions that convey event information about a subevent without activating the event handler. Instead, subevent delivery instructions deliver event information to event handlers associated with a series of subevents or to actively participating views. Event handlers associated with a series of subevents or actively participating views receive event information and perform a predetermined process.

In some embodiments, data updater 176 generates and updates data used in application 136-1. For example, the data updater 176 updates the phone number used in the contact module 137 or stores the video file used in the video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, the object updater 177 creates a new user interface object or updates the location of the user interface object. GUI updater 178 updates the GUI. For example, the GUI updater 178 prepares display information for display on the touch-sensitive display and sends it to the graphics module 132.

In some embodiments, event handler (s) 190 includes or accesses 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 within a single module of individual application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

The foregoing discussion regarding event handling of user touches on touch-sensitive display also applies to other forms of user inputs for operating multifunction devices 100 having input devices, all of which are disclosed on touch screens. It should be understood that it is not. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or hold; Contact movements such as tap, drag, scroll, and the like on the touchpad; Pen stylus inputs; Movement of the device; Verbal instructions; Detected eye movements; Biometric inputs; And / or any combination thereof are optionally used as inputs corresponding to subevents defining an event to be recognized.

2 illustrates a portable multifunction device 100 having a touch screen 112, in accordance with some embodiments. The touch screen optionally displays one or more graphics within the user interface (UI) 200. In this embodiment as well as in other embodiments described below, the user may, for example, have one or more fingers 202 (not shown to scale in the figure) or one or more stylus 203 (scale in the drawing). May be used to select one or more of the graphics by making a gesture on the graphics. In some embodiments, the selection of one or more graphics occurs when the user stops contacting the one or more graphics. In some embodiments, the gesture may optionally include one or more taps of a finger in contact with device 100, one or more swipes (from left to right, from right to left, up and / or down) And / or rolling (right to left, left to right, up and / or down). In some implementations or situations, the graphic is not selected if it is inadvertently contacted with the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over the application icon optionally does not select the corresponding application.

Device 100 also optionally includes one or more physical buttons, such as “home” or menu button 204. As described above, the menu button 204 is optionally used to navigate to any application 136 in the set of applications that are selectively executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in the GUI displayed on the touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 to turn the device on and off and lock the device, volume control button (s) 208. Subscriber identity module (SIM) card slot 210, headset jack 212, and docking / charging external port 124. Push button 206 may optionally power on / off the device by pressing the button and holding the button pressed for a predefined time interval; Lock the device by pressing the button and releasing the button before the predefined time interval has elapsed; Used 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 via microphone 113. Device 100 may also optionally be configured to generate tactile outputs for the user of device 100 and / or one or more contact intensity sensors 165 to detect the intensity of the contacts on touch screen 112. One or more tactile output generators 167.

3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 may be a laptop computer, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (eg, home or industrial). Controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses for interconnecting these components ( 320). Communication buses 320 optionally include circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between them. Device 300 includes an input / output (I / O) interface 330 that includes a display 340, which is typically a touch screen display. I / O interface 330 is also optionally a tactile output for generating tactile outputs on keyboard and / or mouse (or other pointing device) 350 and touchpad 355, device 300. Generator 357 (eg, similar to tactile output generator (s) 167 described above with reference to FIG. 1A), and sensors 359 (eg, contact intensity sensor (s) described above with reference to FIG. 1A. Light sensor, acceleration sensor, proximity sensor, touch-sensitive sensor, and / or contact intensity sensor). Memory 370 includes fast random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; Optionally include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices located remotely from CPU (s) 310. In some embodiments, memory 370 is programs, modules, and data structures similar to programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). , Or a subset thereof. Also, memory 370 optionally stores additional programs, modules, and data structures that are not present in memory 102 of portable multifunction device 100. For example, the memory 370 of the device 300 may optionally include a drawing module 380, a presentation module 382, a word processing module 384, a website authoring module 386, a disk authoring module 388. ) And / or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store such modules.

Each of the above identified elements in FIG. 3 is optionally stored in one or more of the aforementioned memory devices. Each of the above identified modules corresponds to a set of instructions for performing the above-described function. The modules or programs (eg, sets of instructions) identified above need not be implemented as separate software programs, procedures or modules, so that various subsets of these modules may optionally be combined in various embodiments. Or otherwise rearranged. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Also, memory 370 optionally stores additional modules and data structures not described above.

Attention is now directed to embodiments of user interfaces that are optionally implemented, for example, on the portable multifunction device 100.

4A illustrates an example user interface for a menu of applications on portable multifunction device 100, in accordance with some embodiments. Similar user interfaces are optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

셀룰러 및 Wi-Fi 신호들과 같은 무선 통신(들)을 위한 신호 세기 표시자(들)(402);

Signal strength indicator (s) 402 for wireless communication (s), such as cellular and Wi-Fi signals;

시간(404);

Time 404;

블루투스 표시자(405);

A Bluetooth indicator 405;

배터리 상태 표시자(406);

Battery status indicator 406;

다음과 같은, 빈번하게 사용되는 애플리케이션들에 대한 아이콘들을 갖는 트레이(408):

Tray 408 with icons for frequently used applications, such as:

o An icon 416 for telephony module 138 labeled “telephone” optionally including an indicator 414 of the number of missed calls or voicemail messages;

o An icon 418 for the email client module 140 labeled "mail" that optionally includes an indicator 410 of the number of unread emails;

o An icon 420 for the browser module 147 labeled “Browser”; and

o Icon 422 for video and music player module 152 labeled “iPod”, also referred to as iPod (trademark of Apple Inc.) module 152; and

다음과 같은, 다른 애플리케이션들에 대한 아이콘들:

Icons for other applications, such as:

o An icon 424 for the IM module 141 labeled "Message";

o An icon 426 for the calendar module 148 labeled "Calendar";

o An icon 428 for the image management module 144 labeled "Photo";

o An icon 430 for camera module 143 labeled “camera”;

o An icon 432 for the online video module 155 labeled "online video";

o An icon 434 for stock widget 149-2, labeled "Stock";

o An icon 436 for the map module 154 labeled "Map";

o An icon 438 for the weather widget 149-1 labeled "Weather";

o An icon 440 for the alarm clock widget 149-4 labeled "Clock";

o Icon 442 for workout support module 142 labeled “Workout Support”;

o An icon 444 for the note module 153 labeled “Notes”; and

o Icon 446 for the settings application or module, labeled “Settings”, which provides access to the settings for device 100 and its various applications 136.

It should be noted that the icon labels shown in FIG. 4A are merely illustrative. For example, icon 422 for video and music player module 152 is labeled "Music" or "Music Player." Other labels are optionally used for various application icons. In some embodiments, the label for the individual application icon includes the name of the application corresponding to the individual application icon. In some embodiments, the label for a particular application icon is separate from the name of the application corresponding to the particular application icon.

FIG. 4B illustrates a device (eg, FIG. 3) having a touch-sensitive surface 451 (eg, tablet or touchpad 355 of FIG. 3) separate from display 450 (eg, touch screen display 112). An example user interface on device 300 is shown. Device 300 may also optionally include one or more contact intensity sensors (eg, one or more of sensors 359) and / or device 300 for detecting the intensity of contacts on touch-sensitive surface 451. One or more tactile output generators 357 for generating tactile outputs for the user.

Some of the following examples will be provided with reference to inputs on touch screen display 112 (combined with touch-sensitive surface and display), but in some embodiments, the device is separate from the display as shown in FIG. 4B. Detect inputs on a personal touch-sensitive surface. In some embodiments, the touch-sensitive surface (eg, 451 of FIG. 4B) has a major axis (eg, 452 of FIG. 4B) corresponding to the major axis (eg, 453 of FIG. 4B) on the display (eg, 450). According to these embodiments, the device may interact with the touch-sensitive surface 451 at locations corresponding to individual locations on the display (eg, in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). Detect contacts (eg, 460 and 462 of FIG. 4B). In this way, user inputs (eg, contacts 460 and 462 and their movements) detected by the device on the touch-sensitive surface (eg, 451 of FIG. 4B) may cause the touch-sensitive surface to be separate from the display. When used by the device to manipulate the user interface on the display of the multifunction device (eg, 450 of FIG. 4B). It should be understood that similar methods are optionally used for the other user interfaces described herein.

Additionally, while the following examples are given with reference to finger inputs (eg, finger contacts, finger tap gestures, finger swipe gestures), in some embodiments, one or more of the finger inputs may be connected to another input device. It should be understood that it is replaced by input from (eg, mouse based input or stylus input). For example, the swipe gesture is optionally replaced by mouse click (eg, instead of contact) and movement of the cursor along the path of the subsequent swipe (eg, instead of movement of the contact). As another example, the tap gesture is optionally replaced with a mouse click while the cursor is positioned over the location of the tap gesture (eg, instead of stopping detecting the contact following detection of the contact). Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice are selectively used simultaneously, or mouse and finger contacts are optionally used simultaneously.

5A illustrates an example personal electronic device 500. Device 500 includes a body 502. In some embodiments, device 500 may include some or all of the features described with respect to devices 100, 300 (eg, FIGS. 1A-4B). In some embodiments, device 500 has a touch-sensitive display screen 504 (hereinafter touch screen 504). Alternatively or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. Like the devices 100, 300, in some embodiments, the touch screen 504 (or touch-sensitive surface) is, optionally, one for detecting the intensity of applied contacts (eg, touches). The above intensity sensors are included. One or more intensity sensors of the touch screen 504 (or touch-sensitive surface) may provide output data representing the intensity of the touches. The user interface of device 500 may respond to touches based on the strength of the touches, meaning that touches of different intensities may invoke different user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity are described, for example, in related applications: May 8, 2013 and entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application, an international patent application PCT / US2013 / 040061 (published as WIPO Publication No. WO / 2013/169849), and filed November 11, 2013 and entitled "Device, Method, and Graphical User Interface" for Transitioning Between Touch Input to Display Output Relationships, "International Patent Application PCT / US2013 / 069483, published as WIPO Publication No. WO / 2014/105276, each of which is incorporated herein by reference in its entirety.

In some embodiments, device 500 has one or more input mechanisms 506, 508. The input mechanisms 506, 508, if included, may 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) are such that the device 500 may be, for example, a hat, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, chains, pants, belts, shoes, wallets. It can be attached to a backpack, etc. These attachment mechanisms allow the device 500 to be worn by a user.

5B shows an example personal electronic device 500. In some embodiments, device 500 may include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has a bus 512 that operatively couples I / O section 514 with one or more computer processors 516 and memory 518. I / O section 514 may be connected to display 504, which may have a touch-sensitive component 522, and, optionally, an intensity sensor 524 (eg, a contact intensity sensor). In addition, I / O section 514 may include communication unit 530 to receive application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and / or other wireless communication techniques. It can be connected with. Device 500 may include input mechanisms 506 and / or 508. The input mechanism 506 is optionally a rotatable input device or for example a pushable and rotatable input device. In some examples, input mechanism 508 is, optionally, a button.

In some examples, input mechanism 508 is optionally a microphone. The personal electronic device 500 may optionally include a GPS sensor 532, an accelerometer 534, a direction sensor 540 (eg, compass), gyroscope 536, motion sensor 538, and / or their Various sensors, such as a combination, may all be operatively connected to the I / O section 514.

The memory 518 of the personal electronic device 500, when executed by, for example, one or more computer processors 516, causes the computer processors to process processes 700, 900 (FIGS. 7A-7E, FIG. One or more non-transitory computer readable storage media for storing computer executable instructions, which may enable performing the techniques described below, including FIGS. 9A and 9B). A computer readable storage medium can be any medium that can tangibly contain or store computer executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is temporary computer readable storage medium. In some examples, the storage medium is a non-transitory computer readable storage medium. Non-transitory computer readable storage media may include, but are not limited to, magnetic, optical, and / or semiconductor storage. Examples of such storage include optical disks based on magnetic disks, CD, DVD, or Blu-ray technologies, as well as persistent solid state memory such as flash, solid state drives, and the like. The personal electronic device 500 is not limited to the components and configurations of FIG. 5B, and may include other or additional components in a number of configurations.

As used herein, the term " affordance " refers to a user interaction that is selectively displayed on the display screen of devices 100, 300, and / or 500 (FIGS. 1A, 3, and 5A and 5B). Refers to a user-interactive graphical user interface object. For example, images (eg icons), buttons, and text (eg hyperlinks) each optionally constitute an affordance.

As used herein, the term "focus selector" refers to an input element that represents the current portion of the user interface with which the user is interacting. In some implementations that include a cursor or other location marker, the touch-sensitive surface (eg, FIG. 3) while the cursor is over a particular user interface element (eg, a button, window, slider or other user interface element). When an input (eg, a press input) is detected on the touchpad 355 of FIG. 4 or the touch-sensitive surface 451 of FIG. 4B, the cursor is “focus selector” such that a particular user interface element is adjusted according to the detected input. Function as. Some implementations include a touch screen display (eg, touch sensitive display system 112 of FIG. 1A or touch screen 112 of FIG. 4A) that enables direct interaction with user interface elements on the touch screen display. In particular, when an input (eg, a press input by contact) is detected on a touch screen display at a location of a particular user interface element (eg, a button, window, slider or other user interface element), the particular user interface element is detected. The contact detected on the touch screen functions as a "focus selector" so that it is adjusted according to the input. In some implementations, the focus is one of the user interface without moving the corresponding cursor or moving the contact on the touch screen display (eg, by using a tab key or an arrow key to move the focus from one button to another). Is moved from the area of to another area of the user interface; In such implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the particular form of the focus selector, the focus selector is generally used to convey the user's intended interaction with the user interface (eg, by presenting to the device an element of the user interface the user wishes to interact with). Is a user interface element (or contact on a touch screen display) controlled by the. For example, while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touch screen), the position of the focus selector (e.g., cursor, contact, or selection box) on an individual button is placed on the display of the device. Unlike the other user interface elements shown, this will indicate that the user is trying to activate an individual button.

As used in the specification and claims, the term "characteristic strength" of a contact refers to the 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 may optionally be a predefined number of intensity samples, or (e.g. after detecting a contact, before detecting a lift off of the contact, before or after detecting the onset of movement of the contact, Predetermined period of time (eg, prior to detecting an end of contact, before or after detecting an increase in the intensity of the contact, and / or before or after detecting a decrease in the intensity of the contact) 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) based on the set of intensity samples collected. The characteristic intensity of a contact may optionally include 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, and a top 10 percentile value of the intensities of the contact. ), Half of the maximum value of the intensities of the contact, 90 percent of the maximum value of the intensities of the contact, and the like. In some embodiments, the duration of the contact is used to determine the characteristic strength (eg, when the characteristic strength is an average of the strength 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 the operation was performed by the 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, as a result of the contact having a characteristic strength that does not exceed the first threshold, the first operation is performed and as a result of the contact having a characteristic strength that exceeds the first intensity threshold but does not exceed the second intensity threshold, the second The operation is performed, and as a result of the contact having the characteristic strength exceeding the second threshold, the third operation is performed. In some embodiments, the comparison between the characteristic strength and one or more thresholds is used to determine whether to perform one or more operations, rather than being used to determine whether to perform the first or second operation. Whether to perform an action or to suspend performing an individual action).

In some embodiments, a portion of the gesture is identified to determine the characteristic strength. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from the start position to the end position, at which point the strength of the contact increases. In this example, the characteristic strength of the contact at the end position is optionally based only on the portion of the continuous swipe contact (eg, only on the portion of the swipe contact at the end position), rather than the entire swipe contact. In some embodiments, a smoothing algorithm is optionally applied to the strengths of the swipe contact before determining the characteristic strength of the contact. For example, the smoothing algorithm may optionally include one of an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. It includes one or more. In some situations, these smoothing algorithms eliminate narrow spikes or dips in the strengths of the swipe contact to determine the characteristic strength.

The intensity of the contact on the touch-sensitive surface is optionally characterized for one or more intensity thresholds, such as contact detection intensity thresholds, light press intensity thresholds, deep press intensity thresholds, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to the intensity at which the device will perform operations typically associated with clicking a button or trackpad of a physical mouse. In some embodiments, the deep press intensity threshold corresponds to the intensity at which the device will perform operations different from those typically associated with clicking a button or trackpad of a physical mouse. In some embodiments, when a contact is detected with a characteristic strength below the light click intensity threshold (eg, and above the nominal touch detection intensity threshold (contact no longer detected)), the device is lightly pressed. The focus selector will move in response to the movement of the contact on the touch-sensitive surface without performing an action associated with the threshold or the deep press intensity threshold. In general, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.

The increase in the characteristic intensity of the contact from the intensity below the light press intensity threshold to the intensity between the light click intensity threshold and the deep click intensity threshold is sometimes referred to as a "light press" input. An increase in the characteristic intensity of a contact from an intensity below the deep click intensity threshold to an intensity above the deep click intensity threshold is sometimes referred to as a "deep click" input. An increase in the characteristic intensity of a contact from an intensity below the touch detection intensity threshold to an intensity between the touch detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting contact on the touch surface. The reduction in the characteristic intensity of a contact from an intensity above the touch detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a 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 detect an individual press input performed in response to detecting a gesture including an individual press input or performed with an individual contact (or a plurality of contacts). In response to, wherein the individual press input is detected based at least in part on detecting an increase in intensity of the contact (or the plurality of contacts) above the press input intensity threshold. In some embodiments, the individual actions are performed in response to detecting an increase in the intensity of an individual contact above the click input intensity threshold (eg, a “down stroke” of the individual click input). In some embodiments, the press input includes an increase in the strength of an individual contact above the press input intensity threshold and a subsequent decrease in the intensity of the contact below the press input intensity threshold, wherein the individual action is an individual below the press input threshold. Is performed in response to detecting a subsequent decrease in the intensity of the contact of (e.g., an " up stroke " of the individual press input).

In some embodiments, the device employs intensity hysteresis to avoid accidental inputs, sometimes referred to as " jitter, " For example, the hysteresis intensity threshold is a unit of X intensity lower than the click input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or any suitable ratio of the click input intensity threshold). As such, in some embodiments, the press input includes an increase in the intensity of an individual contact above the press input intensity threshold and a subsequent decrease in the intensity of the contact below the hysteresis intensity threshold corresponding to the press input intensity threshold. The operation of is performed in response to detecting a subsequent decrease in the intensity of the individual contact below the hysteresis intensity threshold (eg, an "up stroke" of the individual press input). Similarly, in some embodiments, the press input causes the device to increase the intensity of contact from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, and optionally, to an intensity below the hysteresis intensity. Only when detecting a subsequent decrease in the intensity of the contact is detected, the individual actions are performed in response to detecting a press input (e.g., an increase in the intensity of the contact or a decrease in the intensity of the contact).

For convenience of explanation, the description of the operations performed in response to a press input associated with the press input intensity threshold or in response to a gesture comprising a press input may optionally include an increase in the strength of the contact above the press input intensity threshold, a hysteresis intensity threshold. An increase in the intensity of the contact from an intensity below the click input intensity threshold, a decrease in the intensity of the contact below the click input intensity threshold, and / or an intensity of the contact below the hysteresis intensity threshold corresponding to the click input intensity threshold. Triggered in response to detecting either of the decreases. In addition, in the examples in which the operation is described as being performed in response to detecting a decrease in the intensity of the contact below the click input intensity threshold, the action is optionally below the hysteresis intensity threshold that corresponds to and is lower than the press input intensity threshold. Is performed in response to detecting a decrease in the intensity of the contact.

As used herein, an “installed application” is a software application that is downloaded onto an electronic device (eg, devices 100, 300, and / or 500) and ready to be launched (eg, opened) on the device. Refers to. In some embodiments, the downloaded application is an application installed through an installation program that extracts program portions from the downloaded package and integrates the extracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “running application” are states retained (eg, as part of device / global internal state 157 and / or application internal state 192). Refers to a software application having information. An open or running application is optionally any of the following application types:

애플리케이션이 사용되고 있는 디바이스의 디스플레이 스크린 상에 현재 디스플레이되는 활성 애플리케이션;

An active application currently displayed on the display screen of the device on which the application is being used;

현재 디스플레이되지 않지만, 애플리케이션에 대한 하나 이상의 프로세스들이 하나 이상의 프로세서들에 의해 프로세싱되고 있는 백그라운드 애플리케이션(또는 백그라운드 프로세스); 및

A background application (or background process) that is not currently displayed, but one or more processes for the application are being processed by one or more processors; And

실행 중이 아니지만, 메모리(각각 휘발성 및 비휘발성)에 저장되고 애플리케이션의 실행을 재개하는 데 사용될 수 있는 상태 정보를 갖는 보류(suspended) 또는 휴면(hibernated) 애플리케이션.

A suspended or hibernated application that is not running but has state information that is stored in memory (volatile and nonvolatile, respectively) and can be used to resume execution of the application.

As used herein, the term “closed application” refers to software applications that do not have retained state information (eg, state information for closed applications is not stored in the memory of the device). Thus, closing the application includes stopping and / or removing application processes for the application and removing state information for the application from the memory of the device. In general, opening a second application while in the first application does not close the first application. When the second application is displayed and the first application stops being displayed, the first application becomes a background application.

Attention is now directed to embodiments of user interfaces (“UIs”) and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

6A-6A illustrate example user interfaces for charging multiple electronic devices in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes of FIGS. 7A and 7E.

6A shows primary device 610 (eg, a smartphone), secondary device 620 (eg, smartwatch), and charging device 600. In some embodiments, primary device 610 is portable multifunction device 100, device 300, device 500, or another electronic device having a display (eg, an electronic watch, tablet computer). In some embodiments, secondary device 620 is portable multifunction device 100, device 300, device 500, or another electronic device with or without a display (eg, a smartphone, an electronic watch, a tablet computer). , Battery-operated earphones (eg, AirPods®, etc.). In some embodiments, secondary device 620 includes a case, dock, and the like, where secondary device 620 interfaces with charging device 600.

In some embodiments, the primary device 610 and the secondary device 620 may be connected via a pulse that they transmit (eg, via a wireless communication link such as Bluetooth®, or by charging coils of the charging device 600). For example, as a backup communication method). In some embodiments, primary device 610 and / or secondary device 620 are included in a set of devices associated with each other (eg, associated with, or paired with, the same iCloud® account). In some embodiments, the set of devices associated with each other includes one or more of devices paired with at least one other device in the set, and devices associated with the same user account (eg, iCloud®). In some embodiments, the devices are otherwise configured to exchange data. For example, devices are logged in on the same WiFi network.

Charging device 600 is configured to charge primary device 610 and secondary device 620. Optionally, charging device 600 is configured to wirelessly charge primary device 610 and / or secondary device 620. In some embodiments, charging device 600 includes a substantially flat surface (eg, a mat) on which primary device 610 and secondary device 620 can be placed for wireless charging. Primary device 610 and secondary device 620 are configured to enter a wireless charging state when disposed on charging device 600. Optionally, charging device 600 is capable of wireless and / or wired communication. In one example, charging device 600 may be in wireless communication with primary device 610, secondary device 620, and / or other electronic devices via a Bluetooth® and / or near field communication (NFC) protocol or over a wireless network. It is possible. In some embodiments, charging device 600 is wireless charging device 1002 (discussed below) or includes one or more features or elements of wireless charging device 1002.

6B-6F illustrate one embodiment of a user interface when primary device 610 is placed on charging device 600 for charging. 6B shows the primary device 610 disposed on the charging device 600. When primary device 610 is placed on charging device 600, primary device 610 enters a wireless charging state (eg, primary device 610 prevents charging in response to being placed on a charging mat). Started). In response to detecting that it has entered a wireless charging state, the primary device 610 provides an indication of the state of charge (eg, a visual or other type of indication that the state of charge of the primary device 610 has changed).

In the illustrated embodiment, as shown in FIG. 6B, the indication of the state of charge for primary device 610 includes a haptic output (eg, primary device 610 when placed on charging device 600). Provide output). Primary device 610 is also displaying a visual indication (eg, animation or graphical interface object (s)) that it has entered a wireless charging state. FIG. 6C illustrates an example in which the graphical representation of the primary device 610 (eg, an iPhone®) is rotated, flipped, twisted, and / or tumbled to indicate that the primary device 610 has entered a state of charge. Shows the animation. In another embodiment, primary device 610 displays charge state indicator 644 (discussed in more detail below) shown in FIG. 6F and / or indicates that primary device 610 has entered a charged state. The battery icon 644-2 or the setting status indicator 645 in the charge status indicator 644 to pulse or flash.

After the animation shown in FIG. 6C, the primary device 610 displays the charge state interface 640 with the charge state indicator 641 as shown in FIG. 6D. Charge status indicator 641 includes a charge status platter showing the charge level of primary device 610.

In the embodiment shown in FIG. 6D, the charge status indicator 641 includes a battery indicator 641-1, which is a textual representation as a percentage (68%) of the charge level of the battery of the primary device 610. 641-1A), a graphical representation of the charge level 641-1B (battery icon partially filled in proportion to the charge level of the primary device 610), and a current status indication that the primary device 610 is currently charging ( 641-1C) (lightning display). The charge status indicator 641 also includes a graphic identifier 641 of the primary device 610 that includes a name associated with the primary device 610 (Device 1) and a representative image of the primary device 610 (thumbnail image of the iPhone®). -2). In some embodiments, the charge status indicator 641 includes one or more of the features included in the battery indicator 641-1 and the graphic identifier 641-2.

In some embodiments, displaying the charge status indicator 641 includes a fly-in animation of the charge status platter. In some embodiments, the graphical representation of the fill level includes a partially filled ring. In some embodiments, the indication of the filling level is referred to as an animation representing the filling level (eg, a ripple and / or impact effect representing a filling level (eg, varying based on the filling level), referred to herein as a “ripple” effect). Or a color-based indication of the charge level (eg, green for full charge, yellow for some charges, and red for low charge / no charge).

Optionally, charge status indicator 641 is displayed as long as primary device 610 is being charged and removed after primary device 610 is no longer charged (eg, removed from charging device 600). (Eg, display is stopped). Optionally, the charge state interface 640 includes a setting state indicator 645 indicating the state of various device settings (eg, do not disturb, GPS, Bluetooth®, etc.).

After the charge state interface 640 is displayed (eg, for a predetermined amount of time), the primary device 610 animates the transition to the other more compact charge state indicator 644 shown in FIG. 6F. 6E shows an exemplary transition in which the charge state indicator 641 is reduced in size and the set state indicator 645 translates off the right edge of the display 612. Charge state indicator 644 includes the same features of battery indicator 641-1 described above and indicates the state of charge for primary device 610. In some embodiments, the charge status indicator 644 may include a setting status indicator 645 (eg, a Bluetooth® status) and one or more charge level indicators (eg, a text indication 641-1A) and a battery icon ( 641-1B)).

Next, as shown in FIG. 6G, the secondary device 620, along with the primary device 610, is disposed on the charging device 600 and enters a wireless charging state. In response to the secondary device 620 being disposed on the charging device 600, the primary device 610 detects that the secondary device 620 has entered a wireless charging state. Optionally, primary device 610 receives data from secondary device 620 via a communication link (eg, pulses transmitted via Bluetooth® or charging coils of charging device 600), where the data is secondary. Indicates that the device 620 has entered a wireless charging state and / or represents the charging state of the secondary device 620. In some embodiments, secondary device 620 is disposed on charging device 600 before primary device 610 is disposed on charging device 600.

Detecting that at least one of the primary device 610 or the secondary device 620 has entered a wireless charging state (eg, disposed on the charging device 600) and the primary device 610 and the secondary device 620 In response to determining that both are being wirelessly charged by the same charging device 600, the primary device 610 displays an indication of the state of charge for the secondary device 620. In the illustrated embodiment, the primary device 610 displays the secondary device 620 by displaying an animation in which the graphical representation of the secondary device 620 is rotated, flipped, twisted and / or rotated as shown in FIG. 6H. ) Has changed the charging state (eg, the secondary device 620 has entered the charging state).

After the animation, the primary device 610 has a charge state indicator 641 for the primary device 610 and a charge state indicator 642 for the secondary device 620, as shown in FIG. 6I. Display the charge status interface 640. Similar to the charge status indicator 641 for the primary device 610, the charge status indicator for the secondary device 620 includes an identifier (representative image and name) of the secondary device 620, (text and graphics The charging level of the secondary device 620 (in both forms) and the secondary device 620 are currently charging (lightning indication). In some embodiments, the secondary device 620 also outputs (eg, displays) an indication of its charge level (eg, a visual or non-visual indication of the charge level).

In some embodiments, displaying an indication of the state of charge for the secondary device 620 includes a fly-in animation of the state of charge indicator 641 and / or the state of charge indicator 642. In some embodiments, primary device 610 displays charge status indicator 644 and / or displays battery icon () within charge status indicator 644 to indicate that secondary device 620 has entered a charged state. 644-2) or set status indicator 645 pulses or flashes.

In some embodiments, upon detecting that the primary device 610 enters a wireless charging state or that another device enters the wireless charging state while the primary device 610 is placed on the charging device 600, Primary device 610 displays an indication (eg, a platter) of the state of charge for each device being wirelessly charged by charging device 600. In this sense, primary device 610 is a “hero device” that displays a multi-device charge state interface that includes a charge state platter for each device currently being charged on charging device 600. .

In some embodiments, primary device 610 displays charge status indicators (eg, 641, 642) in a particular order. In FIG. 6I, the charge status indicator 641 and the charge status indicator 642 are displayed on the display 612 in an ordered arrangement (eg, a vertical list). In some embodiments, the charge status indicators are displayed in a horizontal list. In some embodiments, the ordered arrangement is a predetermined arrangement based on the type of device associated with each individual charge status indicator (eg, the phone is always first, then the watch, then the earphone (eg, the iPhone®). , Then Apple Watch®, then AirPods). In some embodiments, the ordered arrangement is based at least in part on the order in which each individual device enters the wireless charging state (eg, first-in, first-in of charge state indicators for individual devices). first-out (FIFO) list). In some embodiments, the charge state indicator of a device that displays a charge state interface (eg, primary device 610) is always displayed first (eg, on top or on the leftmost side), and then the indicators are first in, first out order. Listed as.

In some embodiments, charge state interface 640 depends on certain conditions (eg, primary device 610 displays a different charge state interface based on certain conditions). In one example, primary device 610 determines whether it is in a low disturbance condition (eg, in a do not disturb mode, or in a dark room). In accordance with the determination that it is not in a low disturbance condition, the primary device 610 displays an indication of the state of charge for the secondary device 620 as described above (eg, displays the indication normally). Alternatively, upon determining that the primary device 610 is in a low disturbance condition, the primary device 610 may display a low disturbance indication (eg, red-shift and / or lower amount of charge) for the secondary device 620. Display a charge status indicator 642 or 644 having a light output of < RTI ID = 0.0 >

As described above, in some embodiments, primary device 610 is included in a set of devices associated with each other. In one such example, the primary device 610 determines whether the secondary device 620 is included in the set of devices associated with each other. In accordance with the determination that the secondary device 620 is included in the set of devices associated with each other, the primary device 610 displays an indication of the state of charge for the secondary device 620 as described above. Alternatively, in accordance with a determination that the secondary device 620 is not included in the set of devices associated with each other, the primary device 610 may display an indication of the state of charge for the secondary device 620 (eg, the charge state indicator 642). Hold).

Referring now to FIGS. 6J and 6K, after displaying the charge state indicators 641, 642, the primary device 610 may revert to the primary device (similar to the transition described above with reference to FIGS. 6D-6F). Display an animated transition from the state of charge interface 640 of 610 to the state of charge indicator 644.

Next, as shown in FIG. 6K, user input 650 (eg, a tab) is detected on battery icon 644-2 within charge status indicator 644 (eg, battery icon 644-2). And / or charge status indicator 644 is a selectable affordance. In response, primary device 610 provides charge status indicators for all devices that are currently being charged on charge device 600 (eg, having charge status indicator 641 and charge status indicator 642). Display the state of charge interface 640). In the illustrated embodiment, displaying the charge status interface 640 in response to user input 650 causes charge status indicator 644 (including battery icon 644-2) to be removed from display 612. The animation includes removing and transitioning the charge state interface 640 onto the display 612. As shown in Figures 6K-6M, the animation is the reverse of the animation shown in Figures 6I-6K.

Next, referring to FIG. 6N, the device 600 stops displaying the charge state interface 640 that includes an indication of the charge state for the secondary device 620 (eg, charge state indicator 642). do. In the illustrated embodiment, display 612 of primary device 610 enters a mode (eg, sleep mode) in which display 612 is inactive (eg, turned off or not currently displaying any content). . In some embodiments, display 612 is inactive when no inputs or alerts (eg, emails, text messages, phone calls, etc.) are received or detected for a predetermined amount of time. .

While display 612 is inactive, primary device 610 receives user input 651 (eg, a touch input such as a tap). In response to receiving the user input 651, the primary device 610 displays an indication of the state of charge for the primary device 610 and / or an indication of the state of charge for the secondary device 620. In the illustrated embodiment, in response to receiving user input 651, primary device 610 determines whether user input 651 is detected for a threshold amount of time (eg, user input 651 is tapped). Determine whether it is tap and hold). In response to determining that user input 651 is detected for a threshold amount of time, primary device 610 is charged state indicator 641 associated with primary device 610 and charge state indicator 642 associated with secondary device 620. Display a charge state interface 640, 6N-6P illustrate exemplary transitions from inactive display 612 to charge state interface 640, where charge state indicators 641, 642 are in response to user input 651. Appear gradually in the image. In some embodiments, primary device 610 displays charge status indicator 644 and / or flashes battery icon 644-2 in response to user input 651. In this manner, primary device 610 allows a user to "check in" on the state of the devices being charged on charging device 600. In some embodiments, primary device 610 periodically provides charging status information by illuminating display 612 at regular intervals to show charging information (eg, display displays charging status interface 640). Is activated at predetermined time intervals to display.

When the user input 651 is removed from the display 612, the primary device 610 stops displaying the charge state interface 640 (eg, the display 612 returns to inactive state). Alternatively, upon determining that the user input 651 is not detected for the threshold amount of time, the primary device 610 withholds displaying the charge state interface 640.

Referring now to FIG. 6Q, primary device 610 and secondary device 620 are charging on charging device 600, and primary device 610 is displaying charging interface 640. While the primary device 610 and the secondary device 620 are charging on the charging device 600, and the primary device 610 is displaying the charging interface 640, as shown in FIG. 6R, the third device 630A (eg, a tablet computer) is added to the charging device 600 and enters a wireless charging state.

In response to the third device 630A entering a wireless charging state, the third device (eg, by the primary device 610, the third device 630A, and / or the charging device 600) A determination is made whether 630A) is the preferred device (eg, a new primary or hero device). In the illustrated embodiment, whether the third device 630A is the preferred device is determined by the display size of the third device 630A (eg, the display size of the third device 630A relative to the display size of the primary device 610). Based on. The third device 630A is the preferred device because the third device 630A has a larger display than the primary device 610 and the secondary device 620. Thus, the charge state interface 640 stops displaying on the primary device 610 and is displayed at the third device 630A, which is the preferred device.

As shown in FIG. 6R, the charge state interface 640 on the third device 630A includes a charge state indicator 643 for the third device 630A. Since third device 630A is the preferred device, charge state indicator 643 is displayed over charge state indicators 641, 642 for primary and secondary devices 610, 620.

In some embodiments, primary device 610 detects that third device 630A has entered a wireless charging state and determines the display size of third device 630A (eg, primary device 610 is Receive display size information from the third device 630A, or otherwise access information regarding the display size of the third device 630A). In accordance with the determination that the display size of the third device 630A is greater than the display size of the primary device 610, the primary device 610 determines that the third device 630A is the preferred device and sets its charge level (eg, Transmit to third device 630A for display on third device 630A). In some embodiments, transmitting the charge level to the third device 630A may direct the state of charge directly (eg, via charging device 600 or Bluetooth® communication) or indirectly (eg, iCloud®, Transmission via an external network or server).

In some embodiments, the preferred device is determined based on a predetermined hierarchy of devices. For example, primary device 610 may maintain a list indicating a hierarchy of devices (from least preferred to least preferred): third device 630A, primary device 610, and secondary device. (620). Thus, determining whether the device is the preferred device includes determining whether the device is higher in the hierarchy—in this example, the third device 630 is the preferred device over the primary device 610.

Referring now to FIG. 6S, an alternative embodiment is shown where a different third device (eg, third device 630B) is added to the charging device 600 instead of the third device 630A described above. In response to detecting that the third device 630B has entered the wireless charging state, the primary device 610 determines that the third device 630B is not the preferred device (eg, the display size of the third device 630B). Not greater than the display size of the primary device 610), an indication of the state of charge for the third device 630B (eg, the charge state indicator 643) on the display 612. In some embodiments, displaying an indication of the state of charge for the third device 630B includes displaying the state of charge indicator 644 and / or pulsed a battery icon (eg, 644-2). Include.

Although devices 600, 610, 620, 630B are configured as shown in FIG. 6S, secondary device 620 is removed from charging device 600. The primary device 610 detects that the secondary device 620 has exited the wireless charging state (eg, by receiving data from the secondary device 620), and in response, the secondary device 620 is no longer charging. Is displayed. In some embodiments, primary device 610 flashes a battery icon in charge status indicator 644. In the embodiment shown in FIGS. 6T-6V, the primary device 610 removes the charge state indicator 642 for the secondary device 620, and charge state indicator 641 and charge state indicator 643. ) Is displayed to indicate that primary device 610 and third device 630 are still being charged. 6T and 6U show an example animation for removing the charge status indicator 642, which highlights (eg, blinks) (FIG. 6T) the charge status indicator 642 and then charges it. The status indicator 642 provides a visual effect of disappearing (FIG. 6U).

Turning now to the configuration shown in FIG. 6V, the primary device 610 is removed from the charging device 600. In response to being removed from the charging device 600, as shown in FIG. 6W, the primary device 610 ends the wireless charging state and stops displaying the charge state interface 640. The primary device 610 also displays the interface 660 of the active application (eg, the interface to the inbox of the email application) (eg, in response to a user selection of the email application icon). In FIG. 6X, the primary device 610 is placed back on the charging device 600 while displaying the interface 660, and in response, displaying an indication of the charging state while also displaying the interface 660 of the active application. (Eg, display, enlarge, and / or pulse charge status indicator 644 and / or battery icon 644-2). In this way, primary device 610 has minimal interference to interface 660 of the active application (eg, without displaying charge status indicator 641 on top of interface 660 of the active application). ) Provide an indication of a state of charge (eg, primary device 610 has entered a wireless state of charge). In some embodiments, primary device 610 subsequently stops displaying charge status indicator 644, but maintains display of battery icon 644-2, as shown in FIG. 6Y. In some embodiments, in response to the secondary device 620 being placed on the charging device 600 while the active application is displayed, the primary device 610 may display (eg, display) the state of charge of the secondary device 620. Instead of displaying the charge status indicator 642, the charge status indicator 644 is also displayed while also displaying the interface 660 of the active application.

Next, in FIG. 6z, the primary device 610 detects an input 652 on the battery icon 644-2. In response, the primary device 610 displays a charge status indicator 641 and a charge status indicator 643 corresponding to the primary device 610 and the third device 630B, respectively. As shown in the embodiment illustrated in FIG. 6AA, the charge status indicator 641 and the charge status indicator 643 are visually overlaid on the interface 660 of the active application. In some embodiments, the primary device 610 is in direct response to being disposed with the third device 630B on the charging device 600 (eg, as described with reference to FIG. 6X). Instead of displaying 644), display the charge status indicator 641 and the charge status indicator 643 overlaid on the interface 660 of the active application.

Referring now to FIGS. 6A-6A, some embodiments of multi-device charge state interfaces and charge state indicators are described. In FIG. 6AB, the primary device 610 displays the visual representations of the devices (eg, the charge status indicators 641A, 642A, 643A) positioned relative to the visual representation of the charging device (eg, 646). Physical locations of devices on 600. The positioning of the visual representations reflects the actual physical positioning of the devices on the charging device 600. Indications of the physical locations include identifying information of the devices D1, D2, D3. Thus, the user can see the display 612 of the primary device 610 and can recognize the identity and positioning of each device currently being wirelessly charged. In addition, the charge status indicators 641A, 642A, 643A indicate the charge level of each device having a ring that is filled in proportion to the percentage charge. 6ac shows an embodiment of a multi-device charge state interface when four devices are being charged by charging device 600.

In FIG. 6Ad, the charge status indicator 647 includes a lightning bolt icon and a ring that is filled in proportion to the charge percentage. The charge status indicator 648 of FIG. 6ae includes text indicating the percentage of charge and a ring filled in proportion to the percentage of charge. The charge state indicator 649 of FIGS. 6AF and 6AG includes a ring that is filled in proportion to the percentage of charge and an animated ripple effect (eg, a Ripple effect), where the magnitude of the animated ripple effect is filled. Proportional to percentage. In Fig. 6af, the device is only partially charged, which is manifested by the ring being partially filled and the relatively small ripple effect partially surrounding the ring. In contrast, in FIG. 6ag, the device is fully charged, which is manifested by the ring being fully filled and the relatively large ripple effect completely surrounding the ring.

7A-7E are flow diagrams illustrating a method for charging electronic devices, in accordance with some embodiments. The method 700 is performed at a first device (eg, 100, 300, 500, or 610) having a display (eg, 612). Optionally, the first device comprises a touch-sensitive surface (eg, a touch-sensitive display). Some operations of the method 700 are optionally combined, some orders are optionally changed, and some operations are optionally omitted.

As described below, the method 700 provides an intuitive way to charge electronic devices (eg, to determine the charge level of one or more devices). This method reduces the user's cognitive burden on charging electronic devices, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing a user to charge electronic devices faster and more efficiently improves the user experience, saves power, and increases the time between battery charges.

At block 702, the first device detects that at least one of the first device (eg, 610) or the second device (eg, 620) has entered a wireless charging state. In some embodiments, in response to detecting that the first device has entered a wireless charging state, the first device provides a haptic output (eg, 800). Providing a haptic output in response to detecting that the first device has entered a wireless charging state provides the user with feedback that the first device has successfully started charging and provides charging information without the user having to activate or view the display. Reduce the number of inputs by providing Reducing the number of inputs needed to provide an improved feedback to a user and perform an action (eg, by helping the user provide appropriate inputs and reducing user mistakes when operating and / or interacting with a device) It improves the device's operability and makes the user-device interface more efficient, which additionally allows the user to use the device more quickly and efficiently, thereby reducing the device's power usage and improving battery life.

At block 704, in response to detecting that at least one of the first device or the second device has entered the wireless charging state, and wherein the first device and the second device are wireless by the same wireless charging device (eg, 600) In accordance with the determination that the device is being charged, the first device displays, on the display, an indication of the state of charge for the second device (eg, 642). In some embodiments, displaying the indication of the state of charge for the second device comprises displaying a visual indication (eg, 642) that at least one of the first device or the second device has entered the wireless state of charge. In some embodiments, the first device displays a charge status indicator on the display, where the indication of the charge status for the second device is an animation associated with the charge status indicator (eg, FIG. 6H). Displaying an indication of the state of charge for the second device on the display of the first device is improved for the user with respect to the state of charge of the second device by causing the state of charge to be provided on a device that is more suitable for providing charge state information. Provide feedback, especially when the second device (eg, a pair of earbuds) does not include a display or has limited means for providing a state of charge. It also reduces or eliminates the need to provide a separate input at the second device to obtain a charge level of the second device, thereby reducing the number of inputs needed to obtain the state of charge of the second device. Benefits of providing improved feedback to the user and reducing the number of inputs required to perform an action have been described above.

Optionally, in block 706, displaying an indication of the state of charge for the second device includes: a first state of charge indicator (eg, 641) associated with the first device and a second state of charge associated with the second device; Displaying a state of charge interface (eg, 640) including a child (eg, 642). Displaying charge state indicators of both the first device and the second device provides improved feedback by having the charge state of multiple devices displayed on a single device. Displaying an indication of the state of charge of multiple devices on a single display reduces the need to provide separate inputs at each device to obtain charge levels individually to obtain the state of charge of each device. Reduce the number of inputs needed to Benefits of providing improved feedback to the user and reducing the number of inputs required to perform an action have been described above.

In some embodiments, displaying the charge state interface includes displaying the first charge state indicator and the second charge state indicator in an ordered arrangement (eg, vertically) on the display. In some embodiments, the ordered arrangement is a predetermined arrangement based on the type of device associated with each individual state of charge indicator. In some embodiments, the ordered arrangement is based at least in part on the order in which each individual device entered the wireless charging state. Ordering the arrangement based on the order in which each individual device enters the wireless charging state is by placing the most relevant information (eg, the charge level of the most recently charged device) in a more prominent position. Improve feedback to the user. The benefits of providing improved visual feedback to the user have been described above.

In some embodiments, displaying the charge state interface may indicate, on the display, a charge level for the first device (eg, 641-1A or 641-1B) and an indication that the first device is currently being charged (eg, 641). Displaying a first charge status indicator comprising -1C). In some embodiments, displaying the charge state interface includes displaying on the display, a second charge state indicator that includes a charge level for the second device and an indication that the second device is currently being charged. In some embodiments, displaying the charge level for the device may include textual representation of the charge level (eg, 644-1), graphical representation of the charge level (eg, 644-2), animation indicating the charge level (eg, 649). ), And a color-based indication indicative of the filling level.

Optionally, at block 708, the first device displays, on the display, a charging state interface that is animatedly transitioning to an icon (eg, 644-2), after which the charging state interface is displayed. Stop (eg, FIGS. 6I-6K). Optionally, at block 710, following the cease of displaying the charging state interface, the first device receives a user input selection of the icon (eg, 650). Optionally, in block 712, in response to receiving the user input selection of the icon, the first device displays a charge state interface on the display (eg, FIGS. 6K-6M). Stopping displaying the charge state interface and then displaying it again in response to the selection of the icon charges the user interface without complicating the user interface with persistent charge state information, which may interfere with other information on the display. Make it easy to access status information. Providing additional control options without complicating the interface with the additional displayed controls can be achieved by reducing the number of user errors (eg, by helping the user to provide appropriate inputs when operating and / or interacting with the device). It improves operability and makes the user-device interface more efficient, which additionally allows the user to use the device more quickly and efficiently, thereby reducing the device's power usage and improving battery life.

In some embodiments, prior to detecting that at least one of the first device or the second device has entered the wireless charging state, the first device displays an interface (eg, 660) of the active application on the display and charging Displaying an indication of the status includes simultaneously displaying on the display an indication of the charging status (eg, 644) and an interface of the active application. Optionally, the indication of the state of charge is visually overlaid on the interface of the active application (eg, FIG. 6aa).

In some embodiments, the indication of the state of charge is a selectable affordance (eg, 644-2). Optionally, at block 714, the first device receives a user input selection (eg, 652) of the indication of the state of charge. Optionally, in block 716, in response to receiving a user input selection of an indication of the state of charge, the first device may, on the display, display a first state of charge indicator (eg, 641) associated with the first device; Display a charge state interface that includes a second charge state indicator (eg, 642) associated with the second device.

Optionally, at block 718, the first device detects that the third device (eg, 630A or 630B) has entered a wireless charging state. In some embodiments, in response to detecting that the third device has entered a wireless charging state, and in accordance with a determination that the first device and the third device are being wirelessly charged by the same wireless charging device, the first device may be , On the display, displays an indication of the state of charge for the third device (eg, 643). Optionally, in block 720, in response to detecting that the third device has entered the wireless charging state, the first device determines whether the third device is the preferred device. In some embodiments, determining whether the third device is the preferred device includes determining whether the third device is a device that includes a display larger than the display of the first device. Optionally, at block 722, according to determining that the third device is the preferred device, the first device withholds displaying (eg, FIG. 6R) an indication of the state of charge for the third device (eg, Transmit the charge level of the first device to the third device) for display on the third device. Optionally, at block 724, according to the determination that the third device is not the preferred device, the first device displays, on the display, an indication of the state of charge for the third device (eg, FIG. 6S).

Determining whether the third device is the preferred device (eg, based on the display size) and transmitting the charge level of the first device to the third device is more suitable (eg, preferred) for providing charge status information. ) Provide improved feedback to the user about the state of charge of the first and third devices by having the state of charge of at least two devices provided on the device (eg, the third device). It also reduces or eliminates the need to provide separate inputs at each device to obtain individual charge levels, thereby reducing the number of inputs needed to obtain the state of charge of both the first and third devices. Let's do it. Benefits of providing improved feedback to the user and reducing the number of inputs required to perform an action have been described above.

In some embodiments, subsequent to displaying an indication of the state of charge for the second device, and while the first device and the second device are being wirelessly charged by the same wireless charging device, the first device is connected to the second device. Stop displaying the indication of the state of charge for the device (eg, FIG. 6N). Optionally, at block 726, while the display is inactive, the first device receives user input (eg, 651) associated with the device. In some embodiments, in response to receiving a user input associated with the device, the first device displays, on the display, an indication of the state of charge for the second device (eg, FIG. 6P). In some embodiments, the indication of the state of charge for the second device is a visual indication (eg, flashing or magnifying) associated with the state of charge indicator (eg, 644). In some embodiments, the first device receives a user input selection (eg, 650) of the charge status indicator. In some embodiments, in response to receiving a user input selection of a charge status indicator, the first device may, on the display, with a first charge status indicator (eg, 641) and a second device associated with the first device. Display a charge state interface (eg, 640) that includes an associated second charge state indicator (eg, 642).

Optionally, in block 728, in response to receiving user input associated with the device, the first device determines whether user input associated with the device is detected for a threshold amount of time. Optionally, at block 730, according to the determination that the user input associated with the device is detected for a threshold amount of time, and while the user input associated with the device is still detected, the first device is configured to display the first device on the display. Display a charge state interface that includes a first charge state indicator associated with a second charge state indicator associated with a second device (eg, FIG. 6P). Optionally, at block 732, according to the determination that no user input associated with the device is detected for the threshold amount of time, the first device suspends displaying the state of charge interface on the display. Optionally, at block 734, according to the determination that user input associated with the device is detected for a threshold amount of time, the first device stops detecting user input associated with the device. Optionally, in block 736, in response to stopping detecting the user input associated with the device, the first device stops displaying the charge state interface.

Optionally, at block 738, the first device detects that the second device has exited the wireless charging state (eg, FIG. 6T). Optionally, at block 740, in response to detecting that the second device has exited the wireless charging state, and determining that the first device and the second device are no longer being wirelessly charged by the same wireless charging device. Accordingly, the first device displays, on the display, a second indication of the state of charge for the second device (eg, highlight 642 in FIG. 6T). In some embodiments, displaying a second indication of the state of charge for the second device includes displaying a visual indication that the second device has exited the wireless state of charge (eg, removal of 642 in FIGS. 6U and 6V). Include.

Optionally, in block 742, in response to detecting that at least one of the first device or the second device has entered the wireless charging state, and the first device and the second device are wirelessly charged by the same wireless charging device. In accordance with the determination that it is being made, the first device determines whether the first device is in a low disturbance condition. Optionally, in block 744, upon determining that the first device is in a low disturbance condition, the first device may display on the display a low disturbance indication of the state of charge for the second device (eg, redshift and / or). Display 642 or 644 with a lower amount of light output. Optionally, at block 746, according to the determination that the first device is not in a low disturbance condition, the first device displays, on the display, an indication of the state of charge for the second device (eg, 642).

In some embodiments, the first device and the second device are included in a set of devices associated with each other. In some embodiments, the set of devices associated with each other includes one or more of devices paired with at least one other device in the set, and devices associated with the same user account. Optionally, at block 748, the first device detects that the fourth device has entered a wireless charging state. Optionally, at block 750, the first device determines whether the fourth device is included in the set of devices associated with each other. Optionally, in block 752, in response to detecting that the fourth device has entered the wireless charging state, in accordance with a determination that the first device and the fourth device are being wirelessly charged by the same wireless charging device, and According to the determination that the four devices are included in the set of devices associated with each other, the first device displays, on the display, an indication of the state of charge for the fourth device (eg, 642, 643, or 644). Optionally, in block 754, in response to detecting that the fourth device has entered the wireless charging state, in accordance with a determination that the first device and the fourth device are being wirelessly charged by the same wireless charging device, and According to the determination that the four devices are not included in the set of devices associated with each other, the first device withholds displaying an indication of the state of charge for the fourth device on the display.

In some embodiments, while the first device and the second device are being wirelessly charged by the same wireless charging device, the first device may, on the display, be in a state of charge for the second device at predetermined time intervals. Display the indication.

In some embodiments, the first device and the second device are connected via a communication link. In some embodiments, the first device receives data representing the state of charge of the second device from the second device over the communication link.

In some embodiments, further, in response to detecting that at least one of the first device or the second device has entered the wireless charging state, and the first device and the second device are wirelessly charged by the same wireless charging device. In accordance with the determination that it is, the first device displays on the display an indication of the physical location of the second device on the wireless charging device (eg, 642A in FIG. 6A).

Note that the details of the processes described above in connection with the method 700 (eg, FIGS. 7A-7E) are also applicable in a similar manner to the methods described below. For example, the method 900 optionally includes one or more features of the various methods described above with reference to the method 700. For example, display of an indication of the state of charge for the second device as described above with reference to block 704 of method 700 provides in addition to the non-visual indication (s) described in method 900. Can be. Similarly, the non-visual indication (s) described in method 900 may be provided in addition to the display of an indication of the state of charge for the second device as described above with reference to block 704 of method 700. have. For brevity, these details are not repeated below.

Referring now to FIGS. 8A-8E, techniques and non-visual interfaces for communicating a charge level of an electronic device are described. 8A shows the charging device 600 and the primary device 610 described above with reference to FIGS. 6A-6A. Primary device 610 is charging on device 610 and displays a charge status indicator 644 indicating that primary device 610 has a first charge level of 50%. While being charged on charging device 600 at a first charge level, primary device 610 may display a user input 850 (eg, display) that represents a request for a charge level (eg, charge level of primary device 610). Tap on 612). In response to receiving the user input 850, the primary device 610 outputs a first non-visual indication 800 (eg, audible sound and / or haptic vibration) of the first charge level of the primary device 610. do. The type (eg, audible or haptic) or characteristic (eg, amplitude, frequency, duration, modulation pattern) of the first non-visual indication 800 may include the number of curves (eg, adjacent to each corner of the primary device 610). , Two curves). In some embodiments, the first non-visual indication 800 is a transition of the wireless charging state of the primary device 610 (eg, placing the primary device 610 on the charging device 600 or charging device ( Output from the primary device 610).

8B shows the primary device 610 being charged on the charging device 600 at a second charge level of 100% (eg, after the device has been charged for some length of time after user input 850). . While primary device 610 is being charged on charging device 600 at a second charge level, primary device 610 may display a user input 851 (eg, a tap on display 612) that expresses another request for the charge level. ). In response to receiving user input 851, primary device 610 outputs a second non-visual indication 802 (eg, audible sound and / or haptic vibration) of the second charge level of primary device 610. do. The type or characteristic of the second non-visual indication 802 is represented again by the number of curves (eg, four curves) adjacent to each corner of the primary device 610. In some embodiments, the second non-visual indication 802 is a transition of the wireless charging state of the primary device 610 (eg, placing the primary device 610 on the charging device 600 or the charging device ( Output from the primary device 610).

As shown in FIGS. 8A and 8B, since the second charge level (100%) is different from the first charge level (50%), the second non-visual indication 802 is the first non-visual indication ( 800) (e.g., include different types of indications or different characteristics). In some embodiments, the second non-visual indication 802 and the first non-visual indication 800 include the same type of indication (eg, both include a haptic output or both display an audio output). In relation to one or more characteristics (eg, they have different amplitudes, frequencies, durations, and / or modulation patterns). In some embodiments, the second non-visual indication 802 and the first non-visual indication 800 include different types of indications.

Although user inputs 850 and 851 are described above as taps on display 612, in some embodiments, a request for a charge level is released by tap and hold on display 612, display 612. Maintaining, or user input voice commands (eg, "Siri, what is the charge level of my device?"). In some embodiments, prior to outputting the non-visual indication, the primary device 610 determines whether the user input includes a touch input that is continuously detected during the threshold time length, and then the touch input is the threshold time length. The display is output in accordance with the determination that is detected continuously. In some embodiments, primary device 610 responds to a request for a charge level of primary device 610 when it is not being charged on charging device 600.

In some embodiments, the non-visual indications include a haptic output that indicates the current charge level of the primary device 610. Optionally, one or more output characteristics of the haptic output depend on the charge level of the primary device 610. Exemplary output characteristics of the haptic output include: the time length of the haptic output, the number of individual haptic pulses of the haptic output, and the frequency between the individual haptic pulses of the haptic output. In some embodiments, the length of the haptic indicates (eg, is directly proportional to) the level of filling. In the example applied to the charge levels described in FIGS. 8A and 8B, since the second charge level is greater than the first charge level, the first non-visual indication 800 is the first haptic for the first length of time. And the second non-visual indication 802 includes a second haptic output for a second length of time longer than the first length of time. In some embodiments, primary device 610 provides a series of decaying haptic taps to indicate a relatively low charge level, and a series of haptic buzzes with increasing frequency to indicate a relatively higher charge level. do. In one example applied to the charge levels described in FIGS. 8A and 8B, the first non-visual indication 800 includes a first plurality of individual haptic pulses provided with attenuating frequency between the pulses, and a second Non-visual indication 802 includes a second plurality of individual haptic pulses provided with increasing frequency between the pulses.

In some embodiments, the non-visual indications include an audible output that indicates the current charge level of the primary device 610. Optionally, one or more output characteristics of the audible output depend on the charge level of the primary device 610. Exemplary output characteristics of the audible output include: the length of time of the audible output, the number of individual audible signals of the audible output, the volume of the audible output, the modulation pattern, and the frequency of the audible output. In some embodiments, primary device 610 provides a short audible sound to indicate a relatively low charge level and a longer audible sound to indicate a relatively higher charge level (eg, a negative length). Is proportional to the charge, or the individual lengths of the multiple notes are based on the charge level threshold (s)). In one example applied to the filling levels described in FIGS. 8A and 8B, the first non-visual indication 800 includes a first audible output having a first length of time, and a second non-visual indication 802. Includes a second audible output having a second length of time longer than the first length of time. In some embodiments, the frequency of the audible sound indicates a charge level (eg, the negative frequency is directly proportional to the charge level). In one example applied to the charge levels described in FIGS. 8A and 8B, the first non-visual indication 800 includes an audio signal having a first characteristic frequency, and the second non-visual indication 802 is a second signal. An audio signal having a second characteristic frequency higher than one characteristic frequency.

Referring now to FIG. 8C, while the primary device 610 is being charged on the charging device 600, the secondary device 620 is disposed on the charging device 600. Secondary device 620 has a charge level of 75%. Primary device 610 receives user input 852 (eg, a tap on display 612) that represents a request for a charge level of secondary device 620. In some embodiments, user input 852 may be a tap and hold on display 612, a hand to hold on display 612, or a user input voice command (eg, “Siri, my Apple Watch”). How about charging? "

In response to receiving the user input 852, the primary device 610 outputs a non-visual indication 804 of the charge level of the secondary device 620. In some embodiments, one or more of the techniques, features, and / or features described above in connection with the first and second non-visual indications 800, 802 apply to the non-visual indication 804. To represent the charge level of the secondary device 620. In some embodiments, the non-visual indication 804 of the charge level of the secondary device 602 causes the transition of the wireless charging state of the secondary device 620 (eg, the secondary device 620 on the charging device 600). Deploying or removing the secondary device 620 from the charging device 600).

Referring now to FIGS. 8D and 8E, techniques for providing a low-charge alert are described. 8D shows primary device 610 being charged on charging device 600 and displaying a calendar application. The primary device 610 indicates a time of 9:55 and the calendar application indicates that there are meetings scheduled for 10:00 AM to 11:00 AM. Charge state indicator 644 indicates that primary device 610 has a charge level of 15%.

In response to being removed from the charging device 600, as shown in FIG. 8E (eg, the primary device 610 transitions from a state of wireless charging to a state not being wirelessly charged), the primary device 610 Before the current charge level (15%) of the primary device 610 reaches the depleted charge level (eg, 0%, 5%, 10%, etc.) of the primary device 610, Estimate whether it is sufficient to provide battery charging to the primary device 610 for a period of time. In the example shown, the primary device 610 is the calendar data associated with the primary device 610 (eg, events on a calendar application, a user's calendar linked to the primary device 610, or on the primary device 610). The period of time is determined based on the data from the user account which is logged in. Accordingly, primary device 610 may be configured such that 15% charge of primary device 610 is over primary device 610 over a calendared meeting (eg, for 1 hour 5 minutes) before the charge level reaches a depleted charge level. Estimate whether or not enough to provide battery charging.

In accordance with the presumption that the charge level is sufficient, the primary device 610 outputs a non-visual indication of the charge level of the primary device 610 according to one of the techniques described above (eg, a typical audible or haptic output). In accordance with the presumption that the current charge level is not sufficient, the primary device 610 outputs a non-visual indication 806 (eg, an audible or haptic low-charge alert) that represents the low charge level of the primary device 610. . In one example, the non-visual indication 806 includes an audible voice output such as "You will want to charge your phone if you want your phone to stand up during your next meeting." In some embodiments, the primary device 610 is independent of the current charge level (eg, even if the current charge is 50%, unless charging of the primary device 610 is expected to persist during user's meetings during the day). Passes a low charge alarm.

9A and 9B are flow diagrams illustrating a method for charging electronic devices, in accordance with some embodiments. The method 900 is performed at a device having a display (eg, 100, 300, 500 or 610). Optionally, the device includes a touch sensitive surface (eg, a touch sensitive display). Some operations of the method 900 are optionally combined, some orders are optionally changed, and some operations are optionally omitted.

As described below, the method 900 provides an intuitive method for charging electronic devices. This method reduces the user's cognitive burden on charging electronic devices, thereby creating a more efficient human-machine interface. For battery-operated computing devices, allowing a user to charge electronic devices faster and more efficiently improves the user experience, saves power, and increases the time between battery charges.

At block 902, while the device is charging wirelessly and at a first charge level, the device receives a first user input (eg, 850) that represents a request for a charge level.

At block 904, in response to receiving the first user input, the device outputs a first non-visual indication of the first charge level of the device (eg, 800). Outputting a non-visual indication of the first charge level of the device provides the user with feedback about the device being charged and the charge level of the device, and the user must view or activate the display or select another interface object. There is no need to reduce the number of inputs by providing charging information. The benefits of providing improved feedback to the user and reducing the number of inputs needed to perform the action have been described above. Outputting a non-visual indication also improves the operability of the device by allowing the charge level of the device to be delivered in a subtle or inconspicuous manner (eg, without activating the display at night and illuminating the surrounding environment). The benefits of improving the operation of the device are similar to those described above for providing improved feedback to the user and reducing the number of inputs needed to perform the operation.

At block 906, while the device is being wirelessly charged at a second charge level that is different from the first charge level, the device receives a second user input (eg, 851) representing a request for the charge level.

At block 908, in response to receiving the second user input, the device outputs a second non-visual indication (eg, 802) of the second charge level of the device, wherein the second non-visual indication is generated by the first non-visual indication. 1 is different from the non-visual indication. Here again, outputting a non-visual indication of the charge level of the device allows the device to provide the user with inconspicuous feedback about the device being charged and the charge level of the device, the user viewing the display or It reduces the number of inputs by providing charging information without having to activate or select another interface object. Furthermore, outputting a second non-visual indication different from the first non-visual indication is improved by conveying information about the charge level of the device in the difference between the first output and the second output as well as the second output itself. Feedback to the user. The difference in the outputs may indicate a change in the charge level between the first charge level and the second charge level. The benefits of these effects have been described above.

In some embodiments, one or more of the first user input and the second user input is a transition of the wireless charging state of the device. In some embodiments, the transition of the wireless charging state is a transition from a state in which the device is not charging wirelessly to a state in which the device is charging wirelessly on the wireless charging device. In some embodiments, the transition of the wireless charging state is a transition from the state in which the device is charging wirelessly on the wireless charging device to the state in which the device is not charging wirelessly.

In some embodiments, at least one of the first user input and the second user input is a user input voice command.

In some embodiments, one or more of the first user input and the second user input is a touch input on a touch-sensitive surface (eg, 612) of the device. In some embodiments, in accordance with a determination that a touch input is continuously detected for a threshold length of time, the device outputs a non-visual indication of the charge level of the device (eg, 800).

In some embodiments, outputting a non-visual indication of the charge level of the device includes providing a haptic output indicative of the charge level of the device, where the haptic output has an output characteristic that depends on the charge level of the device. In some embodiments, the output characteristic is one or more of: the length of time of the haptic output, the number of individual haptic pulses of the haptic output, and the frequency between the individual haptic pulses of the haptic output. In some embodiments, in response to the first user input, the device provides a first haptic output indicative of the first charge level, wherein the first haptic output is provided for a first length of time; In response to the second user input, the device provides a second haptic output indicative of the second charge level, wherein the second haptic output is provided for a second length of time, and the second user input is subsequent to the first user input. Received, the second time length is longer than the first time length.

In some embodiments, in response to the first user input, the device provides a third haptic output indicative of the first charge level, wherein the third haptic output is provided with a first plurality of frequencies that attenuate between pulses. Containing individual haptic pulses of; In response to the second user input, the device provides a fourth haptic output indicative of the second charge level, wherein the fourth haptic output includes a second plurality of individual haptic pulses provided with increasing frequency between the pulses. And the second user input is received subsequent to the first user input.

In some embodiments, outputting a non-visual indication of the charge level of the device includes providing an audible output indicative of the charge level, where the audible output has an output characteristic that depends on the charge level of the device. In some embodiments, the output characteristic is one or more of the length of time of the audible output, the number of individual audible signals of the audible output, the volume of the audible output, the modulation pattern, and the frequency of the audible output.

In some embodiments, in response to the first user input, provide a first audible output indicative of a first charge level, wherein the first audible output is provided for a first length of time; In response to the second user input, the device provides a second audible output indicative of the second charge level, wherein the second audible output is provided for a second length of time, and the second user input is subsequent to the first user input. Received, the second time length is longer than the first time length. In some embodiments, in response to the first user input, the device provides a third audible output that indicates the first charge level, wherein the third audible output includes an audio signal having a first characteristic frequency; In response to the second user input, the device provides a fourth audible output indicative of the second charge level, wherein the fourth audible output includes an audio signal having a second characteristic frequency and the second user input is a first user Received following the input, the second characteristic frequency is higher than the first characteristic frequency.

Optionally, at block 910, while the device is being wirelessly charged, the device receives a third user input (eg, 852) that represents a request for a charge level of a second device (eg, 620), Here, the second device is charging wirelessly at the third charge level. Optionally, in block 912, in response to receiving the third user input, the device outputs a third non-visual indication (eg, 804) of the third charge level of the second device. In some embodiments, the second device is charging wirelessly on the same wireless charging device (eg, 600) as the first device. In some embodiments, the third user input is a transition of the wireless charging state of the second device. Outputting a non-visual indication of the charge level of the second device on the first device is improved for the user with respect to the charge state of the second device by causing the charge state to be provided on a device that is more suitable for providing charge state information. Provides feedback, especially when the second device does not include means for providing non-visual (eg, inconspicuous) output or has limited means for providing a state of charge. It also reduces or eliminates the need to provide a separate input at the second device to obtain a charge level of the second device, thereby reducing the number of inputs needed to obtain the state of charge of the second device. Benefits of providing improved feedback to the user and reducing the number of inputs required to perform an action have been described above.

Optionally, at block 914, while the device is being wirelessly charged and at the fourth charge level, the device is moved from the device being wirelessly charged on the wireless charging device to the device is not being wirelessly charged. Receive a fourth user input representing a transition of the wireless charging state of the device. Optionally, in block 916, in response to receiving the fourth user input, the device provides battery charge to the device for a period of time before the fourth charge level reaches a depleted charge level of the device. Estimate whether it is sufficient to Optionally, at block 918, in accordance with the presumption that the fourth charge level is not sufficient, the device outputs a fourth non-visual indication of the fourth charge level of the device (eg, 806). Optionally, at block 920, according to the presumption that the fourth charge level is sufficient, the device outputs a fifth non-visual indication of the fourth charge level of the device, wherein the fourth non-visual indication is a fifth ratio. It is different from the visual display. Providing different outputs when the device's charge level is deemed insufficient to last for that period of time compared to the output when the device's charge level is determined to be sufficient is that the device stops charging even though the device's charge is relatively low. By alerting the user of what is present, they provide improved feedback to the user and help the device prevent the charge from running out unexpectedly. The alert provides the user with the opportunity to take action to ensure that the device does not run out of charge (eg, to extend battery life by setting the device to a low power mode, or to charge the device at another location). The benefits of providing improved user feedback have been described above.

In some embodiments, estimating whether the fourth charge level is sufficient to provide battery charge to the device for a period of time before the charge level of the device reaches a depleted charge level is based on calendar data associated with the device. Determining the period of time, and determining whether the fourth charge level is sufficient to provide battery charge to the device by the end of the period before the charge level of the device reaches a depleted charge level. do. In some embodiments, the fourth non-visual indication of the fourth charge level of the device is an audible or haptic output that indicates a low charge level of the device. In some embodiments, the fourth non-visual indication of the fourth charge level of the device is an audible voice output indicating a low charge level of the device.

The details of the processes described above with respect to method 900 (eg, FIGS. 9A and 9B) also apply in a similar manner to the other methods described above with respect to method 700 (eg, FIGS. 7A-7E). Note that it is possible. For example, method 700 optionally includes one or more features of the various methods described above with reference to method 900.

Embodiments described herein describe techniques for synchronizing information between one or more devices on a wireless charging device (also referred to as a "wireless charging apparatus"). According to some embodiments, the wireless charging device can be configured to receive information from each computing device disposed on the wireless charging device. Such information may include, for example, a unique identifier (ID) associated with the computing device, one or more unique IDs of other computing devices known to the computing device (eg, previously / actively paired computing devices, associated or common user). Set of devices associated with the account), and the battery state of the computing device (also referred to as the "charge state"). In this manner, when new computing devices are deployed on the wireless charging device, the wireless charging device may reference unique IDs to identify when at least two related computing devices exist. For example, with a wireless charging device, a first computing device and a second computing device are (1) disposed on a wireless charging device (eg, being wirelessly charged by a wireless charging device—each device being " Also referred to as being in a "wireless charging state"-), (2) when identifying that they are related to each other, the wireless charging device causes the first computing device to replace and / or replace information displayed by the second computing device. And display information regarding the second computing device.

For example, consider a scenario where the first computing device is a smartphone device and the second computing device is a smaller device associated with the smartphone device (eg, a smart watch device paired with a smartphone). In such a scenario, when the smart watch device is placed on the wireless charging device (with a smartphone device already present), the wireless charging device (1) identifies a relationship between the devices, and (2) the smart watch device Can notify the smartphone device of the presence / battery status. The smartphone device may then generate a notification associated with the battery status of the smart watch device, such as through one or more animations / sounds that provide a pleasant user experience. As mentioned above, the smart watch device may also be configured to generate a notification (eg, a complementary notification) with a notification generated by the smartphone device. In particular, the smartphone device can be configured to indicate to the wireless charging device a time delay to be honored by the smartphone device before generating a notification associated with the battery status of the smart watch device. The wireless charging device then provides a time delay to the smart watch device. In this manner, the smart watch device may display, according to a time delay, a notification that includes one or more animations / sounds that complement the animations / sounds included in the notification generated by the smartphone device.

In addition, it is noted that the smartphone device and smart watch device may issue relevant updates to the wireless charging device periodically / responsibly while being connected to the wireless charging device. For example, the smartphone device may indicate to the wireless charging device whether the smartphone device is appropriate to display a notification associated with the smart watch. Relevance may be based, for example, on whether the smartphone device is locked / unlocked, in use / not in use, and the like. For example, when the smartphone device is in an unlocked state / in use, the smartphone device may refuse to display any notifications associated with the smart watch device. In some examples, the smartphone device may display a notification (eg, pop-up or other visual indication) of the battery status of the smart watch device, such that the user can continue to be notified. Additionally, each of the smartphone device and smart watch device may provide battery status updates to the wireless charging device as they are charged such that various useful features can be implemented. This may, for example, enable the smartphone device to display the latest battery status of the smart watch device when the smart watch device is removed from the wireless charging surface, thereby improving the user experience.

A more detailed discussion of these techniques is described below and in connection with FIGS. 10 and 11A-11D, which show detailed diagrams of systems and methods that can be used to implement these techniques.

10 shows a block diagram 1000 of different computing devices that may be configured to implement various aspects of the techniques described herein, in accordance with some embodiments. Specifically, FIG. 10 shows a high level overview of a wireless charging device 1002 configured to communicate with and provide charge to different computing devices 1020. Although not shown in FIG. 10, wireless charging device 1002 (also referred to as device 1002) and computing devices 1020 each comprise at least one processor, at least one memory, and at least one storage device. It is to be understood that they can collectively, which collectively enable these devices to operate in accordance with the present disclosure. For example, in a given device, the instructions may be stored in at least one storage device and loaded into at least one memory for execution by the at least one processor to enable the techniques described herein to be implemented. In some embodiments, each of devices 1002, 1020 includes one or more features of devices 100, 300, or 500. In some embodiments, device 600 includes one or more features of devices 100, 300, 500, or 1002.

As shown in FIG. 10, the wireless charging device 1002 includes a power source 1004, one or more indicators 1006, a memory for storing device information 1010 (not shown in FIG. 10), one The communication components 1008, and at least one wireless charging surface 1012, may be included. According to some embodiments, wireless charging surface 1012 is such that one or more computing devices 1020 are in proximity to (eg, directly on or otherwise functionally) the wireless charging surface 1012. Any form of wireless (eg, inductive) charging technique may be implemented that enables receiving a charge when deployed. For example, the wireless charging surface 1012 may implement Qi wireless charging technology, Power Matters Alliance (PMA) technology, or any other form of wireless charging technology. However, note that wireless charging techniques are not required to implement the techniques described herein. In some embodiments, wireless charging surface 1012 is by any component (eg, conductor-based charging component) that enables computing devices 1020 to receive a charge and communicate with wireless charging device 1002. It may be replaced or supplemented.

According to some embodiments, indicators 1006 included in wireless charging device 1002 may include, for example, light emitting diodes (LEDs) representing various information to an end user of wireless charging device 1002. Can be. For example, the LEDs may indicate whether power source 1004 is receiving power from the power source, whether at least one computing device 1020 is properly connected to and being charged through wireless charging surface 1012, and the like. Can be. According to some embodiments, the communication component 1008 may cause the wireless charging device 1002 to inform the computing devices 1020 (eg, via Bluetooth, near field communication (NFC), WiFi, or any suitable communication technology). And receive information from it. According to some embodiments, computing devices 1020 communicate directly. For example, computing devices 1020-1 and 1020-2, when paired by Bluetooth, can exchange information related to battery status directly over their Bluetooth communication link. According to some embodiments, the aforementioned information is computed with the wireless charging device 1002 using "in-band" communication consistent with any wireless charging technology implemented by the wireless charging device 1002. May be transmitted between devices 1020. For example, the data signal may be transmitted via a wireless charging technology medium (eg, one or more communication signal pulses transmitted via an induction coil). In this way, pre-existing relationships-such as Bluetooth pairing, NFC pairing, WiFi pairing, etc.-are not required for the wireless charging device 1002 to communicate effectively with the computing devices 1020. In addition, implementing in-band communication is such that a given computing device 1020 is the minimum mode in which primary communication components (eg, cellular, Bluetooth, NFC, WiFi, etc.) within the computing device 1020 are disabled—eg, an airplane. Even when operating in mode-, the wireless charging device 1002 can still communicate with the computing device 1020.

Note that the internal components of the wireless charging device 1002 shown in FIG. 10 and described herein do not represent an exhaustive list of what may be included in the wireless charging device 1002. In some embodiments, wireless charging device 1002 may include any number of components that contribute or complement the embodiments described herein. In some examples, wireless charging device 1002 may include display devices / speakers that may be used to notify end users about information associated with wireless charging device 1002 and / or computing device 1020. . In some examples, wireless charging device 1002 may use any form of input device, such as a touch-screen, biometric sensor, buttons, dial, slider, etc., to enable interactions with wireless charging device 1002 to occur. It may include. In some examples, the wireless charging device 1002 can be via any communication components (eg, cellular, Bluetooth, NFC, WiFi, etc.) that enable the wireless charging device 1002 to communicate with the computing devices 1020. Providing communication capabilities).

According to some embodiments, device information 1010 may be used by wireless charging device 1002 to manage the flow of information between computing devices 1020 in accordance with the techniques described herein. For example, when computing device 1020 is deployed on wireless charging device 1002, computing device 1020 may be described herein, eg, via in-band or other communication techniques described herein. One or more packets 1028 may be transmitted that contain relevant information that may enable the described techniques to be effectively implemented. For example, as shown in FIG. 10, a packet 1028 sent by computing device 1020 may be a unique identifier (ID) 1022 for computing device 1020, another known to computing device 1020. One or more known unique IDs 1022 of computing devices 1020, and other information 1026 associated with computing device 1020, the purpose of which is described in more detail below.

According to some embodiments, unique ID 1022 may take any form that enables computing device 1020 to be uniquely identifiable. For example, the unique ID 1022 may be based on hardware / software attributes (eg, identifiers) associated with the computing device 1020. However, in some cases, particularly to protect privacy, it may be desirable to separate the unique ID 1022 from the attributes of the computing device 1020. For example, unique ID 1022 may be a randomly generated string that is not associated with hardware / software attributes of computing device 1020. In this manner, nearby malicious devices attempting to snoop on information transmitted between computing device 1020 and wireless charging device 1002 may only collect harmless data. In addition, the embodiments described herein periodically refresh the unique IDs 1022 of the computing devices 1020 to further-thwart any malicious activity that may be attempted. It may include.

As described above, the packet (s) 1028 transmitted by the computing device 1020 also represent one or more unique IDs 1022 of other computing devices 1020 related to the computing device 1020. Known unique IDs 1024 may be included. According to some embodiments, such other computing devices 1020 may be actively paired or previously paired with the computing device 1020, which may be in direct communication with the computing device 1020 (eg, via Bluetooth or NFC). Devices, such as wearable devices, headphones, speakers, sensors, and the like. In this manner, and as described in more detail herein, wireless charging device 1002 uses unique IDs 1022 and known unique IDs 1024 provided by various computing devices 1020, One of the computing devices 1020 can identify when interactions should occur between specific computing devices.

Additionally, and as described above, the packet (s) 1028 transmitted by the computing device 1020 may be used by the wireless charging device 1002 to implement the techniques described herein. Other information 1026 about 1020 may be included. For example, other information 1026 may include computing device 1020 including model information (eg, device name, model, color, display characteristics (eg, size, dimension, area), etc.) associated with computing device 1020. ), An indication of the type of), state information (eg, lock / unlock) associated with the computing device 1020, battery information associated with the computing device 1020, and the like.

Additionally, and not shown in FIG. 10, the various computing devices 1020 described herein allow the computing devices 1020 to interface with the wireless charging device 1002-for example (eg, Receiving energy (eg, used to charge one or more batteries of the receiving device) from the wireless charging device 1002, via the wireless charging surface 1012, communicating with the wireless charging device 1002, and the like. May include-it will be understood to include hardware / software components. It will further be appreciated that the various computing devices 1020 may include hardware / software elements that enable the computing devices 1020 to implement the techniques described herein at various levels. For example, computing devices 1020 (eg, laptops, tablets, smartphones, etc.) having larger display devices are known computing when they are placed on / removed from the wireless charging device 1002. It may be designated as primary / high-priority devices, displaying information about devices 1020. Continuing with this example, computing devices 1020 (eg, smart watches) with smaller displays are only available when no primary / high-priority devices are present on the wireless charging device 1002. It may be designated as secondary / low-priority devices for which information should be displayed. For example, when only the smart watch computing device 1020 is present on the wireless charging device 1002 and a pair of wireless headphones is placed on the wireless charging device 1002, the smart watch computing device 1020 is wireless. It may be responsible for displaying information about wireless headphones with / on behalf of the headphones. The foregoing examples are not intended to be encompassed in any manner, and the computing devices 1020 described herein may be configured in any manner to achieve different variations to the techniques described herein. Be careful.

Accordingly, FIG. 10 describes an overview of different configurations of wireless charging apparatus 1002 / computing devices 1020 that may be used to enable implementation of the embodiments described herein. As described in more detail below, these components are via synchronized / complementary notifications, for example, when two or more related computing devices 1020 are placed on the wireless charging device 1002 for charging. This can be used to provide a rich user experience.

11A-11D show conceptual diagrams of example computing devices 1020 displaying complementary notifications in a synchronized manner when placed on and removed from the wireless charging device 1002, in accordance with some embodiments. . In some embodiments, fewer devices than all devices disposed on or removed from the wireless charging device provide notification in accordance with the techniques described herein (eg, the primary device displays a state of charge and other The device (s) do not provide notification in response to placement / removal from the wireless charging device). As shown in FIG. 11A, the first step 1110 may include the computing device 1020-1 being disposed on the wireless charging device 1002. This may be the case, for example, when a user places computing device 1020-1 on wireless charging device 1002 with the intent to charge computing device 1020-1 via the wireless charging techniques described herein. I can express it. As shown in FIG. 11A, step 1110 may include the computing device 1020-1 transmitting one or more packets 1028 to the wireless charging device 1002. As described above, these packets 1028 may include information associated with computing device 1020-1, eg, unique ID 1022, known unique IDs 1024, and other information 1026. .

As shown in FIG. 11A, example information sent by packets 1028 is placed in device information 1010 by wireless charging device 1002. For example, the value "DEVICE_1" can be assigned as unique ID 1022, the values "DEVICE_2" and "DEVICE_3" can be assigned as known unique IDs 1024, and the value "SMARTPHONE, 52% BAT". May be assigned as other information 1026. In this example, computing device 1020-1 has an assigned unique ID 1022 of "DEVICE_1", where computing device 1020-1 is two other computing devices 1020-unique ID 1022. It was previously paired with computing device 1020-2 with ("DEVICE_2"), and computing device 1020-3 with unique ID 1022 ("DEVICE_3"). Also in this example, computing device 1020-1 is a smartphone device with a 52% battery level when computing device 1020-1 is disposed on wireless charging device 1002. In addition, as shown in FIG. 11A, the wireless charging device 1002 includes a device 1010-1 on the wireless charging device 1002 within the device information 1010 for the computing device 1020-1. May be assigned a " status information " attribute 1100 that identifies whether it is present or not. The “state information” attribute 1100 may also be used to provide additional information about the computing device 1020-1, such as other arrangements where the computing device 1020-1 is disposed on the wireless charging device 1002 (as previously described above). It may identify whether it is assigned as a high-priority / low-priority device for displaying complementary notifications associated with related computing devices 1020. As described in more detail herein, the "state information" attribute 1100 causes the wireless charging device 1002 to cause other computing devices 1020-2, 1020-3 to be placed on the wireless charging device 1002. Allow them to respond appropriately to and direct them when placed / removed from them. In some examples, “state information” is at least partially filled by information received from computing device 1020 (eg, via received packet (s) 1028).

In the example shown in FIG. 11A, the computing device 1020-1 is the first and only computing device 1020 present on the wireless charging device 1002. In this regard, and in accordance with some embodiments, computing device 1020-1 may be responsible for displaying its own battery status, which is shown in FIG. 11A as notification 1102. As shown in FIG. 11A, the notification 1102 is, by one or more animations / sounds, (1) the type of computing device 1020-1 (eg, “smartphone”), and (2) computing It may indicate a battery state for the device 1020-1. It is noted that the content associated with the notification 1102 shown in FIG. 11A is merely exemplary, and any content of any form, sequence, manner, etc. may be used when generating the notification 1102.

Thus, at the end of the first step 1110 shown in FIG. 11A, the first computing device 1020-1 provides useful information via the notification 1102, and any included in the computing device 1020-1. Power is being received from the wireless charging device 1002 to charge the internal batteries of the. At this point, computing device 1020-1 is now a complementary device for displaying complementary notifications associated with computing devices 1020-2, 1020-3 when they are placed on wireless charging device 1002. Can function. For example, the second step 1120 shown in FIG. 11B may include a second computing device, computing device 1020-2, disposed on the wireless charging device 1002. As shown in FIG. 11B, and in accordance with the techniques described herein, the computing device 1020-2 wirelessly transmits information about the computing device 1020-2 via one or more packets 1028. It can be provided to the charging device 1002. For example, computing device 1020-2 may have value "DEVICE_2" as unique ID 1022, values "DEVICE_1" and "DEVICE_3" as known unique IDs 1024, and value "WEARABLE as other information 1026. , 17% BAT ". For example, in FIG. 11A, computing device 1020-2 may represent a smart watch, fitness tracker, augmented reality device, sensor, or the like.

In short, each of the computing devices 1020 disposed on the wireless charging device 1002 may issue packets 1028 periodically / responsibly to provide relevant updates to the wireless charging device 1002. Note that For example, device information 1010 may be updated to manage state attributes for each computing device 1020, indicating whether or not the computing device 1020 can display complementary notifications. Again, this may be based on, for example, whether the computing device 1020 is locked / unlocked, in use / not in use, and the like. In another example, the device information 1010 may be updated to reflect the battery states of the computing devices 1020 when the computing devices 1020 are charged via the wireless charging device 1002, for example, as shown in FIG. As shown by the battery state of the computing device 1020-1 proceeding from 52% to 60% between the times when step 1110 of 11a and step 1120 of FIG. 11b occur. In particular, various useful features can be implemented by keeping the battery states up to date in the device information 1010. For example, when a pair of headphones is removed from the wireless charging device 1002 and an associated device with a display (eg, laptop, tablet, smartphone, smart watch) remains on the wireless charging device 1002, The associated device may display an indication of the latest battery status of the headphones. In this way, the user who is removing the headphones from the wireless charging device 1002 can immediately receive an easy-to-read indication of the battery status of the headphones (via the display of the associated device), thereby improving the user experience. . Thus, in some embodiments, the wireless charging apparatus (eg, 1002) receives one or more packets sent by the computing device (eg, 1020).

In some embodiments, the computing device (eg, 1020) receives one or more packets transmitted by the wireless charging device (eg, 1002). For example, a smartphone device (eg, device 1020-1 of FIG. 11B) can provide information (eg, battery charge level) regarding the battery state of the wearable device (eg, device 1020-2 of FIG. 11B). The packet 1028 may be included. In this example, the smartphone device proceeds to display its own battery status and an indication of the battery status of the wearable device.

Additionally, by updating device information, one or more of computing devices 1020 may immediately display a summary of information about associated devices disposed on wireless charging device 1002. This may be, for example, when the trigger occurs at a given computing device 1020, such as when the home / power button is pressed on the computing device 1020, the computing device 1020 lying on the wireless charging device 1002. While being moved (eg, nudged by the user), when the computing device 1020 detects that the user is in proximity to the computing device 1020, and so on. For example, when a smartphone, smart watch, and a pair of headphones are being charged on the wireless charging device 1002, the smartphone, in response to any of the triggers described above, has its own battery status, smart It may be configured to display the battery status of the watch, and the latest summary of the battery status of the headphones. According to some embodiments, the smartphone may also be configured to cause one or more of the smartwatch / headphones to present information via complementary notifications in a synchronous manner (or, if desired, asynchronous manner).

Turning now back to FIG. 11B, according to some embodiments, computing devices 1002 and 1020 are configured to omit them from packets 1028 whenever known unique IDs 1024 represent duplicate information. Note that it can be. For example, consider a first computing device 1020 (and vice versa) that is only paired with a second computing device 1020. In this example, when the first computing device 1020 is disposed on the wireless charging device 1002 and provides a known unique ID 1024 corresponding to the unique ID 1022 of the second computing device, the second computing device It will be redundant that 1020 provides a known unique ID 1024 corresponding to the unique ID 1022 of the first computing device 1020. Instead, the wireless charging device 1002 uses the second computing device 1020 for known unique IDs 1024 of the first computing device 1020 (managed within the device information 1010) to identify the relationship. The relationship can be easily identified by comparing the unique ID 1022 of and the same techniques described herein can be performed according to the identification of the relationship.

In any case, when the information associated with the computing device 1020-2 is integrated into the device information 1010, the wireless charging device 1002 is associated with the computing device 1020-1 and the computing device 1020-2 with each other. May be identified (eg, in a paired relationship or associated with a set of devices or a common user account). The wireless charging device 1002 then queries the computing device 1020-1 (eg, via one or more packets 1028) so that the computing device 1020-1 associates with the computing device 1020-2. To identify whether or not there is a willingness to display notification 1106 (eg, possible or capable). According to some embodiments, the query is performed by the computing device 1020-2 to minimize the number of messages sent between the computing device 1020-1, the wireless charging device 1002, and the computing device 1020-2. May include other information 1026 provided by it, thereby reducing overall latency and improving the overall user experience. In particular, this approach will allow computing device 1020-1 to possess the information needed to display within notification 1106 if computing device 1020-1 accepts the responsibility to do so. For example, the computing device 1020-1 accepts the acceptance of displaying the notification 1106 when the computing device 1020-1 remains on the wireless charging device 1002 and is in a locked and / or inactive state. Can be represented. Alternatively, computing device 1020-1 may indicate a refusal to display notification 1106 when computing device 1020-1 is in an unlocked state and / or actively used by a user. .

In the example shown in FIG. 11B, the computing device 1020-1 wirelessly accepts the acceptance of displaying the notification 1106 in association with the computing device 1020-2 being placed on the wireless charging device 1002. The charging device 1002 is shown. According to some embodiments, computing device 1020-1 may indicate acceptance by transmitting one or more packets 1028 to wireless charging device 1002. According to some embodiments, packets 1028 may represent a time delay that computing device 1020-1 plans for displaying notification 1106. In this manner, the wireless charging device 1002 may forward the time delay to the computing device 1020-2, where the time delay is also accepted by the computing device 1020-1 for displaying the notification 1106. Indirectly to the computing device 1020-2. Optionally, computing device 1020-2 may prepare to display a supplemental notification 1108 (eg, a supplemental notification to a notification by a primary device) in accordance with a time delay provided by computing device 1020-1. have.

As shown in FIG. 11B, the notification 1106 is displayed by the computing device 1020-1 when a time delay is met, and provides information about the computing device 1020-2 via one or more animations / sounds. Can be represented. For example, animations / sounds can convey the state of “wearable battery 17%”. Moreover, upon meeting the time delay, and in conjunction with the notification 1106, the notification 1108 generated by the computing device 1020-2 may include, for example, the computing device 1020-2 being a display device (eg, a smart watch). May include other information presented via one or more animations / sounds. In another example, if computing device 1020-2 does not include a display device but includes one or more LEDs, the LED (s) may inform the user, such as animations / displayed by computing device 1020-1. It can be used to deliver pulsating animations that match the sounds. In another example, the LED (s) may be a solid light of a first color (eg, orange) indicating that computing device 1020-2 is being charged, and computing device 1020-2 being fully charged. Solid light, etc., of a second color (eg, green), indicating that there is; In either case, useful information about the computing device 1020-2 and the computing device 1020-2 may be useful when the computing device 1020-2 includes only a small display device or no display device at all. As displayed in aesthetically pleasing manner between 1020-2), the user experience can be enhanced.

As described herein, computing devices 1020 will be regularly placed on wireless charging device 1002 under anticipated use-case environments. To capture how the embodiments described herein manage such events, FIG. 11C shows (while computing device 1020-1 and computing device 1020-2 remain on wireless charging device 1002). ) Shows a third step 1130 in which the third computing device 1020-3 is disposed on the wireless charging device 1002. As shown in FIG. 11C, and in accordance with the techniques described herein, the computing device 1020-3 wirelessly transmits information about the computing device 1020-3 via one or more packets 1028. It can be provided to the charging device 1002. For example, computing device 1020-3 may have value "DEVICE_3" as unique ID 1022, values "DEVICE_1" and "DEVICE_2" as known unique IDs 1024, and value "HEADPHONES as other information 1026. , 23% BAT ". For example, in FIG. 11C, computing device 1020-3 may represent a pair of wireless headphones associated with both computing device 1020-1 and computing device 1020-2.

As shown in FIG. 11C and as previously described above, the wireless charging device 1002 can receive the packets 1028 and add information about the computing device 1020-3 to the device information 1010. have. Subsequently, the wireless charging device 1002 can identify that the computing device 1020-1 and the computing device 1020-2 are known to the computing device 1020-3, and relate to the computing device 1020-3. Messages containing information may be issued (eg, via packets 1028). Such information may also include the type of computing device 1020-3, the battery status of the computing device 1020-3, and the like. The computing device 1020-1 and the computing device 1020-2 may then indicate whether they are willing to display a notification in association with the appearance of the computing device 1020-3 (as described herein). have. According to some embodiments, when two or more computing devices 1020 are involved in displaying a notification, the primary computing device (eg, computing device 1020-1) may indicate a time delay at which the notification should be displayed. Where other computing devices 1020 operate according to a time delay.

For example, in FIG. 11C, computing device 1020-1 may indicate to wireless charging device 1002 the time delay for notification 1114 to be displayed at computing device 1020-1. The wireless charging device 1002 may then provide a time delay to both the computing device 1020-2 and the computing device 1020-3, thus computing device 1020-2 and computing device 1020-10. 3) may prepare to display the notifications 1118 and 1122, respectively. As shown in FIG. 11C, the notification 1114 displayed by the computing device 1020-1 may present the information “headphone battery 23%” by one or more animations / sounds. Additionally, the notification 1118 generated by the computing device 1020-2 may convey other information about the computing device 1020-3 by one or more animations / sounds. For example, if computing device 1020-2 continues with the example scenario described above that represents a smart watch, computing device 1020-2 may be configured with notification 1114 displayed by computing device 1020-1. Other information can be displayed together. Additionally, in this example scenario, the notification 1122 generated by the computing device 1020-3 may be optional, and one or more animations according to a time delay, and one or more of the notification 1114 and the notification 1118. Can be used to convey other information by way of sound / sounds. For example, computing device 1020-3, which may represent a pair of wireless headphones in FIG. 11C, may include an LED that operates with animations / sounds. In another example, one or more of the speakers included in a pair of wireless headphones can be used to reproduce an audible sound that works with animations / sounds.

Additionally, note that computing devices 1020 will be regularly removed from wireless charging device 1002 under anticipated use-case scenarios. In order to capture how the embodiments described herein manage such events, FIG. 11D shows a fourth step 1140 in which the computing device 1020-2 is removed from the wireless charging device 1002 (computing Device 1020-1 and computing device 1020-3 remain on the wireless charging device 1002 while device 1020-2 is shown indicated by an "X"). As shown in FIG. 11D, and in accordance with the techniques described herein, the device information 1010 may be updated to reflect that the computing device 1020-2 is no longer present in the wireless charging device 1002. have. Subsequently, the wireless charging device 1002 indicates to the associated computing devices 1020-eg, the computing device 1020-1 and the computing device 1020-3 that the computing device 1020-2 no longer exists. May be configured to notify. At this point, computing device 1020-1 may optionally send a notification 1126 (eg, providing a current battery state of computing device 1020-2 via one or more animations / sounds, for example). As described herein, during lockout / use). Additionally, computing device 1020-3 may optionally provide notification 1132 that provides, via one or more animations / sounds, other information about the computing device 1020-2 (as previously described herein). ) Can be displayed.

Thus, FIGS. 11A-11D show that computing devices 1020 are (1) removed from their placement / wireless charging device 1002 onto the wireless charging device 1002, and (2) other known computing devices. Scenarios that may provide information and notifications in the presence of 1020 are shown. One or more of the features described above in connection with FIGS. 10 and 11A-11D can be used to perform the techniques described in connection with FIGS. 6A-6A, 7A-7E, 8A-8E, and 9A-9B. Can be used.

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. Embodiments have been selected and described in order to best explain the principles of the techniques and their practical application. Thus, those skilled in the art will be able to make the best use of the techniques and various embodiments using various modifications as appropriate for the particular use contemplated.

Although the present disclosure and examples have been described fully with reference to the accompanying drawings, it should be noted that various changes and modifications will be apparent to those of ordinary skill 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.

Claims (64)

As a computer implemented method,
In a first device having a display,
The first device is in a wireless charging state in which the first device is being wirelessly charged by a wireless charging device, and a first visual indication of the charging state for the second device is not displayed on the display of the first device. While not, detecting that the second device has entered a wireless charging state in which the second device is being wirelessly charged by the wireless charging device;
The second device is connected to the wireless charging device while the first device is in the wireless charging state and the first visual indication of the charging state for the second device is not displayed on the display of the first device. In response to detecting that the second device has entered a wireless state of charge being wirelessly charged, displaying, on the display of the first device, the first visual indication of the state of charge for the second device. step; And
While the first device is in the wireless charging state where the first device is being wirelessly charged by the wireless charging device, the second device is in the wireless charging state being wirelessly charged by the wireless charging device. While the second device is present, and while the first visual indication of the state of charge for the second device is not displayed on the display of the first device:
Detecting that the second device has exited a wireless charging state; And
In response to detecting that the second device has been removed from the wireless charging device and has ended the wireless charging state, and that the first device and the second device are no longer being wirelessly charged by the same wireless charging device. In accordance with the determination, displaying on the display a second visual indication of a state of charge for the second device. The method of claim 1, wherein displaying a visual indication of the state of charge for the second device comprises displaying a visual indication that at least one of the first device or the second device has entered a wireless charge state. , Computer implemented method. The method of claim 2, wherein the computer-implemented method is
Displaying, on the display, a charge status indicator, wherein the visual indication of the charge status for the second device is an animation associated with the charge status indicator. 4. The method of claim 1, wherein displaying a visual indication of the state of charge for the second device comprises: a first state of charge indicator associated with the first device and a first state associated with the second device. 2 displaying a charge status interface comprising a charge status indicator. 5. The computer implemented method of claim 4, wherein displaying the state of charge interface comprises displaying the first state of charge indicator and the second state of charge indicator in an ordered arrangement on the display. 6. The computer-implemented method of claim 5, wherein the ordered arrangement is a predetermined arrangement based on the type of device associated with each individual charge status indicator. The method of claim 5, wherein the ordered arrangement is based at least in part on the order in which each individual device enters a wireless charging state. The method of claim 4, wherein displaying the state of charge interface comprises:
Displaying, on the display, the first state of charge indicator comprising a charge level for the first device and an indication that the first device is currently being charged; And
Displaying, on the display, the second charge state indicator comprising a charge level for the second device and an indication that the second device is currently being charged. The method of claim 4, wherein displaying the charge level for the device comprises text display of the charge level, graphical display of the charge level, animation indicating the charge level, and color-based indicating the charge level. Displaying one or more of the indications. The method according to any one of claims 4 to 9,
Displaying, on the display, the state of charge interface animatingly transitioning to an icon, after which the state of charge interface stops being displayed;
Subsequent to stopping displaying the charge state interface, receiving a user input selection of the icon; And
In response to receiving the user input selection of the icon, displaying the charge state interface on the display. The computer implemented method of claim 1, wherein the computer implemented method comprises:
Further comprising displaying an interface of an active application on the display prior to detecting that the second device has entered a wireless charging state,
Displaying the indication of a state of charge comprises simultaneously displaying on the display the first visual indication of state of charge and the interface of the active application. The computer implemented method of claim 11 wherein the indication of a state of charge is visually overlaid on the interface of the active application. The computer-implemented method of claim 11, wherein the first visual indication of a state of charge is a selectable affordance, and the computer implemented method comprises:
Receiving a user input selection of the first visual indication of a state of charge; And
In response to receiving the user input selection of the first visual indication of a state of charge, on the display, a third state of charge indicator associated with the first device and a fourth state of charge indicator associated with the second device And displaying the charging state interface. The method according to any one of claims 1 to 13,
The first device is in a wireless charging state in which the first device is being wirelessly charged by the wireless charging device, and a visual indication of the charging state for the third device is not displayed on the display of the first device. While detecting that the third device has entered a wireless charging state in which the third device is being wirelessly charged by the wireless charging device; And
The third device is wirelessly charged by the wireless charging device while the first device is in the wireless charging state and no visual indication of the state of charge for the third device is displayed on the display of the first device. In response to detecting that the third device has entered a wireless charging state that is being:
Determining whether the third device is a preferred device;
Withholding, on the display of the first device, displaying the visual indication of the state of charge for the third device in accordance with determining that the third device is a preferred device; And
In response to determining that the third device is not a preferred device, displaying, on the display of the first device, the visual indication of the state of charge for the third device. (delete) The computer of claim 14, wherein determining whether the third device is a preferred device comprises determining whether the third device is a device that includes a display larger than the display of the first device. How to implement. The method of claim 14,
Further, according to determining that the third device is a preferred device, transmitting the charge level of the first device to the third device. 18. The method of any one of claims 1-14, 16 or 17, subsequent to displaying the first visual indication of the state of charge for the second device, and the first device and the While the second device is being wirelessly charged by the same wireless charging device:
Stopping displaying the first visual indication of a state of charge for the second device;
While the display is inactive, receiving user input associated with the device; And
In response to receiving the user input associated with the device, displaying on the display the first visual indication of a state of charge for the second device. 19. The method of claim 18, wherein the first visual indication of the state of charge for the second device is a visual indication associated with a state of charge indicator.
Receiving a user input selection of the charge status indicator; And
In response to receiving the user input selection of the charge state indicator, a charge state comprising on the display a fifth charge state indicator associated with the first device and a sixth charge state indicator associated with the second device And displaying the interface. The method of claim 18,
Further, in response to receiving the user input associated with the device, determining whether the user input associated with the device is detected for a threshold amount of time;
A seventh state of charge indicator associated with the first device, upon the determination that the user input associated with the device is detected for a threshold amount of time, and while the user input associated with the device continues to be detected And displaying a charge state interface including an eighth charge state indicator associated with the second device; And
In response to determining that the user input associated with the device is not detected for a threshold amount of time, suspending displaying the state of charge interface on the display. The method of claim 20,
Further, upon detecting that the user input associated with the device is detected for a threshold amount of time, stopping detecting the user input associated with the device; And
In response to stopping detecting the user input associated with the device, stopping displaying the charge state interface. (delete) The computer-implemented method of claim 1, wherein displaying the second visual indication of a state of charge for the second device comprises displaying a visual indication that the second device has exited a wireless state of charge. The method according to any one of claims 1 to 14, 16 to 21, or 23,
In response to detecting that the first device has entered a wireless charging state, further comprising providing a haptic output. The method according to any one of claims 1 to 14, 16 to 21, 23, or 24,
Additionally, in response to detecting that the second device has entered a wireless charging state while the first device is in the wireless charging state, determining whether the first device is in a low disturbance condition. step;
Displaying, on the display, a low disturbance indication of the state of charge for the second device in accordance with determining that the first device is in a low disturbance condition; And
In response to determining that the first device is not in a low disturbance condition, displaying on the display the first visual indication of a state of charge for the second device. 26. The method of any one of claims 1 to 14, 16 to 21, or 23 to 25, wherein the first device and the second device are included in a set of devices associated with each other, Computer implementation method. 27. The method of claim 26, wherein the set of devices associated with each other includes one or more of devices paired with at least one other device in the set, and devices associated with the same user account. The method of claim 26,
Detecting that the fourth device has entered a wireless charging state;
Determining whether the fourth device is included in the set of devices associated with each other;
In response to detecting that the fourth device has entered a wireless charging state, and in accordance with a determination that the first device and the fourth device are being wirelessly charged by the same wireless charging device:
Displaying, on the display, an indication of the state of charge for the fourth device in accordance with a determination that the fourth device is included in the set of devices associated with each other; And
In response to determining that the fourth device is not included in the set of devices associated with each other, on the display, suspending displaying an indication of the state of charge for the fourth device. . The method according to any one of claims 1 to 14, 16 to 21, or 23 to 28,
While on the display, displaying an indication of the state of charge for the second device at predetermined time intervals while the first device and the second device are being wirelessly charged by the same wireless charging device. Including, computer-implemented method. 30. The device of any one of claims 1-14, 16-21, or 23-29, wherein the first device and the second device are connected via a communication link and the computer The implementation method is
And receiving, from the second device over the communication link, data representing a state of charge of the second device. The method according to any one of claims 1 to 14, 16 to 21, or 23 to 30,
Additionally, in response to detecting that the second device has entered a wireless charging state while the first device is in the wireless charging state, on the display, the physical location of the second device on the wireless charging device may be determined. And displaying the indication. A non-transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, wherein the electronic device is a first device and the one or more programs are:
The first device is in a wireless charging state in which the first device is being wirelessly charged by a wireless charging device, and a first visual indication of the charging state for the second device is not displayed on the display of the first device. While not, detecting that the second device has entered a wireless charging state in which the second device is being wirelessly charged by the wireless charging device;
The second device is connected to the wireless charging device while the first device is in the wireless charging state and the first visual indication of the charging state for the second device is not displayed on the display of the first device. In response to detecting that the second device has entered a wireless state of charge being wirelessly charged, displaying, on the display of the first device, the first visual indication of the state of charge for the second device; ;
While the first device is in the wireless charging state where the first device is being wirelessly charged by the wireless charging device, the second device is in the wireless charging state being wirelessly charged by the wireless charging device. While the second device is present, and while the first visual indication of the state of charge for the second device is not displayed on the display of the first device:
Detect that the second device has exited a wireless charging state;
In response to detecting that the second device has been removed from the wireless charging device and has ended the wireless charging state, and that the first device and the second device are no longer being wirelessly charged by the same wireless charging device. And, on the display, instructions for displaying, on the display, a second visual indication of a state of charge for the second device. As an electronic device,
display;
One or more processors; And
A memory storing one or more programs configured to be executed by the one or more processors, wherein the one or more programs are:
The first device is in a wireless charging state in which the first device is being wirelessly charged by a wireless charging device, and a first visual indication of the charging state for the second device is not displayed on the display of the first device. While not, detecting that the second device has entered a wireless charging state in which the second device is being wirelessly charged by the wireless charging device;
The second device is connected to the wireless charging device while the first device is in the wireless charging state and the first visual indication of the charging state for the second device is not displayed on the display of the first device. In response to detecting that the second device has entered a wireless state of charge being wirelessly charged, displaying, on the display of the first device, the first visual indication of the state of charge for the second device; ;
While the first device is in the wireless charging state where the first device is being wirelessly charged by the wireless charging device, the second device is in the wireless charging state being wirelessly charged by the wireless charging device. While the second device is present, and while the first visual indication of the state of charge for the second device is not displayed on the display of the first device:
Detect that the second device has exited a wireless charging state;
In response to detecting that the second device has been removed from the wireless charging device and has ended the wireless charging state, and that the first device and the second device are no longer being wirelessly charged by the same wireless charging device. And, according to the determination, instructions for displaying, on the display, a second visual indication of the state of charge for the second device. As an electronic device,
display;
The first device is in a wireless charging state in which a first device is being wirelessly charged by a wireless charging device, and a first visual indication of the charging state for the second device is not displayed on the display of the first device. Means for detecting that the second device has entered a wireless charging state in which the second device is being wirelessly charged by the wireless charging device;
The second device is connected to the wireless charging device while the first device is in the wireless charging state and the first visual indication of the charging state for the second device is not displayed on the display of the first device. In response to detecting that the second device has entered a wireless state of charge being wirelessly charged, displaying, on the display of the first device, the first visual indication of the state of charge for the second device. Means for; And
While the first device is in the wireless charging state where the first device is being wirelessly charged by the wireless charging device, the second device is in the wireless charging state being wirelessly charged by the wireless charging device. Means while the second device is present and while the first visual indication of the state of charge for the second device is not displayed on the display of the first device:
Means for detecting that the second device has exited a wireless charging state; And
In response to detecting that the second device has been removed from the wireless charging device and has ended the wireless charging state, and that the first device and the second device are no longer being wirelessly charged by the same wireless charging device. And, according to the determination, means for displaying, on the display, a second visual indication of the state of charge for the second device. A non-transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device having a display, wherein the one or more programs are one of claims 1 to 14 and 16 to 21. Or instructions for performing the method of any one of claims 23-31. As an electronic device,
display;
One or more processors; And
32. A memory device comprising: a memory for storing one or more programs configured to be executed by the one or more processors, wherein the one or more programs are one of claims 1 to 14, 16 to 21, or 23 to 31. An electronic device comprising instructions for performing the method of claim 1. As an electronic device,
display; And
32. An electronic device comprising means for performing the method of any one of claims 1-14, 16-21, or 23-31. As a computer implemented method,
On the device,
While the device is charging wirelessly and at a first charge level, receiving a first user input representing a request for a charge level;
In response to receiving the first user input, outputting a first non-visual indication of the first charge level of the device;
While the device is being wirelessly charged at a second charge level that is different from the first charge level, receiving a second user input representing a request for a charge level; And
In response to receiving the second user input, outputting a second non-visual indication of the second charge level of the device, wherein the second non-visual indication is the first non-visual indication. And computer-implemented method. The method of claim 38, wherein at least one of the first user input and the second user input is a transition of a wireless charging state of the device. 40. The computer implemented method of claim 39 wherein the transition of the wireless charging state is a transition from a state in which the device is not charging wirelessly to a state in which the device is charging wirelessly on a wireless charging device. The method of claim 39, wherein the transition of the wireless charging state is a transition from a state in which the device is wirelessly charged on a wireless charging device to a state in which the device is not wirelessly charged. The computer implemented method of claim 38 wherein at least one of the first user input and the second user input is a user input voice command. The method of claim 38, wherein the device comprises a touch-sensitive surface, wherein at least one of the first user input and the second user input is a touch input on the touch-sensitive surface, wherein the computer-implemented method includes:
And outputting a non-visual indication of the charge level of the device in accordance with the determination that the touch input is continuously detected for a threshold length of time. 44. The method of any of claims 38-43, wherein outputting a non-visual indication of the charge level of the device comprises:
Providing a haptic output indicative of the charge level, the haptic output having an output characteristic dependent on the charge level of the device. 45. The computer-implemented method of claim 44, wherein the output characteristic is one or more of the length of time of the haptic output, the number of individual haptic pulses of the haptic output, and the frequency between the individual haptic pulses of the haptic output. 45. The method of claim 44, wherein the computer implemented method is
In response to the first user input, providing a first haptic output indicative of the first level of charge, the first haptic output being provided for a first length of time; And
In response to the second user input, providing a second haptic output indicative of the second charge level, wherein the second haptic output is provided for a second length of time;
The second user input is received subsequent to the first user input,
And the second time length is longer than the first time length. 45. The method of claim 44, wherein the computer implemented method is
In response to the first user input, providing a third haptic output indicative of the first charge level, wherein the third haptic output comprises a first plurality of individual haptic pulses provided with attenuating frequency between the pulses; Includes-; And
In response to the second user input, providing a fourth haptic output indicative of the second charge level, wherein the fourth haptic output comprises a second plurality of individual haptic pulses provided with increasing frequency between the pulses; Contains-additionally contains
And the second user input is received subsequent to the first user input. 48. The method of any one of claims 38-47, wherein outputting a non-visual indication of the charge level of the device comprises:
Providing an audible output indicative of the charge level, the audible output having an output characteristic dependent on the charge level of the device. 49. The computer implemented method of claim 48, wherein the output characteristic is one or more of a length of time of the audible output, a number of individual audible signals of the audible output, a volume of the audible output, a modulation pattern, and a frequency of the audible output. 49. The method of claim 48, wherein the computer implemented method is
In response to the first user input, providing a first audible output indicative of the first charge level, wherein the first audible output is provided for a first length of time; And
In response to the second user input, providing a second audible output indicative of the second charge level, wherein the second audible output is provided for a second length of time;
The second user input is received subsequent to the first user input,
And the second time length is longer than the first time length. 49. The method of claim 48, wherein the computer implemented method is
In response to the first user input, providing a third audible output representative of the first charge level, the third audible output comprising an audio signal having a first characteristic frequency; And
In response to the second user input, providing a fourth audible output indicative of the second charge level, wherein the fourth audible output includes an audio signal having a second characteristic frequency;
The second user input is received subsequent to the first user input,
And the second characteristic frequency is higher than the first characteristic frequency. The method of any one of claims 38-51,
While the device is being wirelessly charged, receiving a third user input representing a request for a charge level of a second device, the second device being wirelessly charged at a third charge level; And
In response to receiving the third user input, outputting a third non-visual indication of the third charge level of the second device. The computer implemented method of claim 52 wherein the second device is being wirelessly charged on the same wireless charging device as the first device. 54. The computer implemented method of claim 52 or 53 wherein the third user input is a transition of a wireless charging state of the second device. 55. The method of any one of claims 38 to 54 wherein the computer implemented method is
While the device is being wirelessly charged and at a fourth charge level, the transition of the wireless charging state of the device from a state where the device is wirelessly charged on a wireless charging device to a state where the device is not wirelessly charged Receiving a fourth user input representing a;
In response to receiving the fourth user input, the fourth charge level provides battery charging to the device for a period of time before the charge level of the device reaches a depleted charge level. Estimating whether it is sufficient;
Outputting a fourth non-visual indication of the fourth charge level of the device in accordance with the estimate that the fourth charge level is not sufficient; And
Outputting a fifth non-visual indication of the fourth charge level of the device in accordance with the presumption that the fourth charge level is sufficient, wherein the fourth non-visual indication is the fifth non-visual indication. Computer-implemented method that is different from the visual display. 56. The method of claim 55, wherein estimating whether the fourth charge level is sufficient to provide battery charge to the device for a period of time before the charge level of the device reaches a depleted charge level,
Determining the schedule period based on calendar data associated with the device; And
Determining whether the fourth charge level is sufficient to provide battery charge to the device by the end of the period of time before the charge level of the device reaches a depleted charge level. . 57. The method of claim 55 or 56, wherein the fourth non-visual indication of the fourth charge level of the device is an audible or haptic output that indicates a low charge level of the device. 58. The computer implemented method of any of claims 55-57, wherein the fourth non-visual indication of the fourth charge level of the device is an audible voice output indicative of a low charge level of the device. A non-transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device, wherein the one or more programs are:
While the device is charging wirelessly and at a first charge level, receive a first user input representing a request for a charge level;
In response to receiving the first user input, output a first non-visual indication of the first charge level of the device;
Receive a second user input representing a request for a charge level while the device is being wirelessly charged at a second charge level that is different from the first charge level;
In response to receiving the second user input, instructions for outputting a second non-visual indication of the second charge level of the device, wherein the second non-visual indication is the first non-visual A non-transitory computer readable storage medium different from the display. As an electronic device,
One or more processors; And
A memory storing one or more programs configured to be executed by the one or more processors, wherein the one or more programs are:
While the device is charging wirelessly and at a first charge level, receive a first user input representing a request for a charge level;
In response to receiving the first user input, output a first non-visual indication of the first charge level of the device;
Receive a second user input representing a request for a charge level while the device is being wirelessly charged at a second charge level that is different from the first charge level;
In response to receiving the second user input, instructions for outputting a second non-visual indication of the second charge level of the device, wherein the second non-visual indication is the first non-visual Electronic device, different from the indication. As an electronic device,
Means for receiving a first user input expressing a request for a charge level while the device is being wirelessly charged and at a first charge level;
Means for outputting a first non-visual indication of the first charge level of the device in response to receiving the first user input;
Means for receiving a second user input representing a request for a charge level while the device is being wirelessly charged at a second charge level that is different from the first charge level; And
In response to receiving the second user input, means for outputting a second non-visual indication of the second charge level of the device, wherein the second non-visual indication is the first non-visual Electronic device, different from the indication. A non-transitory computer readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device, the one or more programs comprising instructions for performing the method of any one of claims 38-58. And a non-transitory computer readable storage medium. As an electronic device,
One or more processors; And
59. An electronic device comprising memory for storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for performing the method of any one of claims 38-58. As an electronic device,
59. An electronic device comprising means for performing the method of any one of claims 38-58.

Images