Device, method, and graphical user interface for wirelessly pairing with peripheral device and displaying status information relating to peripheral device

Abstract

To provide a faster and more efficient method and interface for pairing with a peripheral device and displaying status information relating to the peripheral device.SOLUTION: A device displays a first user interface on a display. While the first user interface is displayed, the device detects a pairing request for pairing a first peripheral device with an electronic device, and determines whether the first peripheral device meets coupling criteria requiring the first peripheral device to be coupled with a second peripheral device. The device displays a pairing affordance that, when activated by user input, initiates pairing between the electronic device and the first peripheral device. Following a determination that the first peripheral device does not meet the coupling criteria, the device displays information regarding the coupling between the first peripheral device and the second peripheral device.SELECTED DRAWING: Figure 5B

Description

[Technical Field]

[0001] The present invention relates generally to wireless pairing of electronic devices, including but not limited to pairing an electronic device with a peripheral device and displaying status information about the peripheral device. [Background technology]

[0002] The use of wireless peripheral devices that communicate with users' electronic devices (e.g., smartphones, tablets, or other computing devices) has increased significantly in recent years. Wireless pairing technologies, such as Bluetooth®, are often used to connect ("pair") peripherals to such devices.

[0003] However, conventional methods for performing pairing are cumbersome and inefficient, especially when multiple peripheral devices are involved. For example, a user may need to individually pair each peripheral with a given electronic device before using the peripheral with the device. Summary of the Invention

[0004] Therefore, there is a need for electronic devices with faster, more efficient methods and interfaces for pairing with and displaying status information about peripheral devices. Such methods and interfaces, optionally, complement or replace conventional methods for pairing peripherals. Such methods and interfaces reduce the number, range, and / or type of inputs from a user, creating a more efficient human-machine interface. In battery-operated devices, such methods and interfaces conserve power and extend the time between battery charges.

[0005] The above-mentioned drawbacks and other problems associated with user interfaces of electronic devices are reduced or eliminated by the disclosed devices. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a notebook computer, a tablet computer, or a handheld device). In some embodiments, the device is a personal electronic device (e.g., a wearable electronic device such as a watch). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also known as a "touch screen" or "touchscreen display"). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or instruction sets stored in the memory for performing a number of functions. In some embodiments, a user interacts with the GUI primarily through stylus and / or finger contacts and gestures on the touch-sensitive surface. In some embodiments, the functionality optionally includes image editing, drawing, presenting, word processing, spreadsheet creation, game playing, making phone calls, video conferencing, emailing, instant messaging, training support, digital photography, digital videography, web browsing, digital music playback, note taking, and / or digital video playback, and executable instructions to perform those functionality are optionally contained on a non-transitory computer-readable storage medium or other computer program product configured to be executed by one or more processors.

[0006] According to some embodiments, a method is performed on an electronic device comprising a display, radio frequency (RF) circuitry for wirelessly communicating with one or more peripheral devices, and one or more input devices for receiving input from a user. The device displays a first user interface on the display. While displaying the first user interface, the device detects a pairing request to pair a first peripheral device with the electronic device. In response to detecting the pairing request, the device determines whether the first peripheral device meets binding criteria requiring the first peripheral device to be coupled to a second peripheral device. In accordance with a determination that the first peripheral device meets the binding criteria, the device displays a pairing affordance that, when activated by user input, initiates pairing of the electronic device with the first peripheral device. In accordance with a determination that the first peripheral device does not meet the binding criteria, the device displays information regarding the binding of the first peripheral device with the second peripheral device.

[0007] According to some embodiments, an electronic device includes a display, radio frequency (RF) circuitry for wirelessly communicating with one or more peripheral devices, one or more input devices for receiving input from a user, and a processing unit coupled to the display unit, the radio frequency (RF) circuitry, and the one or more input devices. The processing unit enables display of a first user interface on the display unit. While displaying the first user interface, the processing unit detects a pairing request to pair a first peripheral device with the electronic device. In response to detecting the pairing request, the processing unit determines whether the first peripheral device meets binding criteria requiring the first peripheral device to be coupled to a second peripheral device. In accordance with a determination that the first peripheral device meets the binding criteria, the processing unit enables display of a pairing affordance that, when activated by user input, initiates pairing of the electronic device with the first peripheral device. In accordance with a determination that the first peripheral device does not meet the binding criteria, the processing unit enables display of information regarding the binding of the first peripheral device with the second peripheral device.

[0008] Thus, electronic devices that include a display, radio frequency (RF) circuitry, and one or more input devices are provided with faster, more efficient methods and interfaces for pairing with and displaying status information about peripheral devices, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces can complement or replace traditional methods for pairing peripherals. [Brief explanation of the drawings]

[0009] For a better understanding of the various described embodiments, reference should be made to the following detailed description in conjunction with the following drawings, in which like reference numerals refer to corresponding parts throughout the drawings, in which:

[0010] [Figure 1A] 1 is a block diagram illustrating a portable multifunction device having a touch-sensitive display in accordance with some embodiments.

[0011] [Figure 1B] FIG. 2 is a block diagram illustrating exemplary components for event processing according to some embodiments.

[0012] [Figure 2] 1 illustrates a portable multifunction device with a touch screen according to some embodiments.

[0013] [Figure 3] FIG. 1 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface in accordance with some embodiments.

[0014] [Figure 4A] 1 illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

[0015] [Figure 4B] 1 illustrates an exemplary user interface for a multifunction device having a touch-sensitive surface separate from a display in accordance with some embodiments.

[0016] [Figure 5A] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5B] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5C] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5D] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5E] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5F] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5G] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5H] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5I] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5J] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5K] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5L] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5M]1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5N] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5O] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5P] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5Q] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5R] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5S] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5T] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5U] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5V]1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5W] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5X] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5Y] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 5Z] 1 illustrates an exemplary user interface for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments.

[0017] [Figure 6A] FIG. 1 is a flow diagram illustrating a method for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 6B] FIG. 1 is a flow diagram illustrating a method for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. [Figure 6C] FIG. 1 is a flow diagram illustrating a method for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments.

[0018] [Figure 7] FIG. 1 is a functional block diagram of an electronic device according to some embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0019] Many conventional electronic devices have the ability to pair with peripheral devices. However, when two or more peripheral devices are associated (e.g., two earbuds, or two earbuds and an earbud case), the conventional electronic device typically must be individually paired with each peripheral device before use. In contrast, as described herein, associated peripheral devices can be paired to a given device simultaneously, thereby providing the ability to synchronize pairing among multiple peripheral devices in response to a single pairing action. Providing users with improved pairing capabilities improves device usability and makes the user-device interface more efficient (e.g., by helping users efficiently pair with multiple associated peripheral devices in a single action, thereby reducing user errors when attempting to pair a given device to multiple associated peripheral devices). Without this improved pairing process, users must take the additional step of individually pairing their device with different peripheral devices to achieve the same functionality as described herein. Individually pairing a device with multiple peripheral devices can be a time-consuming process, and users are more prone to error due to the increased number of user inputs required to complete the pairing process.

[0020] Furthermore, conventional electronic devices display little or no status information about paired peripherals. However, as described herein, status information about peripherals (e.g., one or more battery levels) is displayed when the peripherals are in close proximity to the device. Providing status information for peripherals improves device usability and makes the user device interface more efficient (e.g., by providing access to information about peripherals without the user having to physically inspect each peripheral), thereby allowing the user to use the device and peripherals more quickly and efficiently.

[0021] Below, Figures 1A-1B, 2, 3, and 7 provide descriptions of exemplary devices. Figures 4A-4B and 5A-5Z illustrate exemplary user interfaces for selectively pairing a peripheral device with an exemplary device and selectively displaying status information about the peripheral device on the exemplary device. Figures 6A-6C are flow diagrams illustrating methods for pairing an electronic device with a peripheral device and displaying status information about the peripheral device. The user interfaces of Figures 5A-5Z are used to explain the processes of Figures 6A-6C. Exemplary Devices

[0022] Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments being described. However, it will be apparent to those skilled in the art that the various embodiments described may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

[0023] In this specification, terms such as "first," "second," etc. are used to describe various elements in some examples, but it will be understood that these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first contact can be referred to as a second contact, and similarly, a second contact can be referred to as a first contact, without departing from the scope of the various embodiments being described. Although a first contact and a second contact are both contacts, they are not the same contact unless the context clearly dictates otherwise.

[0024] The terminology used in the description of various embodiments set forth herein is for the purpose of describing particular embodiments only and is not intended to be limiting. Within the description of the various embodiments set forth and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. Also, as used herein, the term "and / or" should be understood to refer to and include any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "includes," "including," "comprises," and / or "comprising," as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0025] As used herein, the term "if" is optionally interpreted to mean "when," "upon," "in response to determining," or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if [a stated condition or event] is detected" are optionally interpreted to mean "upon determining" or "in response to determining," or "upon detecting [the stated condition or event]" or "in response to detecting [the stated condition or event]," depending on the context.

[0026] 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 include, but are not limited to, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad), are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer having a touch-sensitive surface (e.g., a touchscreen display and / or touchpad).

[0027] In the following discussion, we describe an electronic device that includes a display and a touch-sensitive surface. However, it should be understood that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and / or a joystick.

[0028] The device typically supports a variety of applications such as one or more of a note-taking application, a drawing application, a presentation application, a word processing application, a website creation application, a disc authoring application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a training support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

[0029] Various applications running on the device optionally use at least one common physical user-interface device, such as a touch-sensitive surface. One or more features of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or changed for each application and / or within each application. In this way, the common physical architecture of the device (such as the touch-sensitive surface) optionally supports various applications with user interfaces that are intuitive and transparent to the user.

[0030] Attention now turns to embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 having touch-sensitive display system 112, according to some embodiments. Touch-sensitive display system 112 may conveniently be referred to as a "touch screen" or simply a touch-sensitive display. Device 100 includes memory 102 (optionally including one or more computer-readable storage media), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input / output (I / O) subsystem 106, other input or control devices 116, and external port 124. Device 100 optionally includes one or more light sensors 164. Device 100 optionally includes one or more intensity sensors 165 for detecting the intensity of a contact on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 that generate tactile output on device 100 (e.g., generate tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0031] As used herein and in the claims, the term “tactile output” refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, that will be detected by a user with the user's sense of touch. For example, in a situation where a device or a component of a device is in contact with a touch-sensitive surface of a user (e.g., the fingers, palm, or other part of the user's hand), the tactile output produced by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a “downclick” or “upclick” of a physical actuator button. In some cases, a user feels a tactile sensation such as a “downclick” or “upclick” even when no movement of a physical actuator button associated with the touch-sensitive surface has been physically pressed (e.g., displaced) by the user's action. As another example, movement of a touch-sensitive surface is optionally interpreted or perceived by a user as "roughness" of the touch-sensitive surface, even when there is no change in the smoothness of the touch-sensitive surface. While such user interpretation of touch depends on the user's personal sensory perception, there are many sensory perceptions of touch that are common to the majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "upclick," "downclick," "roughness"), unless otherwise specified, the generated tactile output corresponds to a physical displacement of the device, or a component of the device, that produces the described sensory perception for a typical (or average) user.

[0032] It should be understood that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than those shown, optionally combines two or more components, or optionally has a different configuration or arrangement of its components. The various components shown in FIG. 1A are implemented in hardware, software, firmware, or a combination thereof, including one or more signal processing circuits and / or application specific integrated circuits.

[0033] Memory 102 optionally includes high-speed random access memory, and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100, such as CPU(s) 120 and peripherals interface 118, is optionally controlled by memory controller 122.

[0034] A peripheral interface 118 may be used to couple input and output peripherals of the device with the CPU(s) 120 and memory 102. The one or more processors 120 operate or execute various software programs and / or instruction sets stored in memory 102 to perform various functions and process data for the device 100.

[0035] In some embodiments, peripheral interface 118, CPU(s) 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.

[0036] RF (radio frequency) circuitry 108 transmits and receives RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to or from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, etc. RF circuitry 108 optionally communicates wirelessly with networks, such as the Internet, also known as the World Wide Web (WWW), an intranet, and / or wireless networks, such as cellular telephone networks, wireless local area networks (LANs) and / or metropolitan area networks (MANs), and with other devices. The wireless communication optionally uses any of a plurality of communication standards, protocols, and technologies, including Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (WDMA), and the like.Wireless technology may include wireless technology such as wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11n), 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 (XMPP)), Session Initiation Protocol for Instant Messaging and Presence Leveraging (SIP)), and protocols for cellular communication (e.g., cellular datagrams). Examples of suitable communication protocols include, but are not limited to, Simple Interconnect Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS), and / or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

[0037] Audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuit 110 receives audio data from peripherals interface 118, converts the audio data into electrical signals, and transmits the electrical signals to speaker 111. Speaker 111 converts the electrical signals into sound waves audible to humans. Audio circuit 110 also receives electrical signals converted from sound waves by microphone 113. Audio circuit 110 converts the electrical signals into audio data and transmits the audio data to peripherals interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to memory 102 and / or RF circuit 108 by peripherals interface 118. In some embodiments, audio circuit 110 also includes a headset jack (e.g., 212, FIG. 2 ). The headset jack provides an interface between audio circuitry 110 and a detachable audio input / output peripheral, such as an output-only headphone or a headset with both an output (e.g., mono or binaural headphones) and an input (e.g., a microphone).

[0038] I / O subsystem 106 couples input / output peripherals on device 100, such as touch-sensitive display system 112 and other input or control devices 116, with peripheral interface 118. I / O subsystem 106 optionally includes display controller 156, light sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. One or more input controllers 160 receive electrical signals from and send electrical signals to other input or control devices 116. Other input or control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, etc. In some alternative embodiments, input controller(s) 160 are optionally coupled to any (or none) of a keyboard, infrared port, USB port, stylus, and / or pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) optionally include up / down buttons for volume control of the speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., 206, FIG. 2).

[0039] Touch-sensitive display system 112 provides an input and output interface between the device and a user. Display controller 156 receives electrical signals from and / or sends electrical signals to touch-sensitive display system 112. Touch-sensitive display system 112 displays visual output to the user. This visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output corresponds to user interface objects. As used herein, the term "affordance" refers to a user-interactive graphical user interface object (e.g., a graphical user interface object configured to respond to input directed towards the graphical user interface object). Examples of user-interactive graphical user interface objects include, but are not limited to, a button, a slider, an icon, a selectable menu item, a switch, a hyperlink, or other user interface control.

[0040] Touch-sensitive display system 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic and / or tactile contact. Touch-sensitive display system 112 and display controller 156 (along with any associated modules and / or instruction sets in memory 102) detect contacts (and any movement or disruption of contact) on touch-sensitive display system 112 and translate the detected contacts into interactions with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touch-sensitive display system 112. In one example embodiment, the point of contact between touch-sensitive display system 112 and the user corresponds to the user's finger or stylus.

[0041] Touch-sensitive display system 112 optionally uses liquid crystal display (LCD), light emitting polymer display (LPD), or light emitting diode (LED) technology, although other display technologies are used in other embodiments. Touch-sensitive display system 112 and display controller 156 optionally use any of a number of now known or later developed touch sensing technologies to detect contact and any movement or disruption thereof, including, but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch-sensitive display system 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone®, iPod Touch®, and iPad® from Apple Inc. (Cupertino, California).

[0042] Touch-sensitive display system 112 optionally has a video resolution greater than 100 dpi. In some embodiments, the touchscreen video resolution exceeds 400 dpi (e.g., 500 dpi, 800 dpi, or higher). A user optionally contacts touch-sensitive display system 112 using any suitable object or accessory, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may be less precise than stylus-based input due to the larger area of ​​finger contact on the touchscreen. In some embodiments, the device translates the coarse finger-based input into precise pointer / cursor positions or commands to perform the action desired by the user.

[0043] In some embodiments, in addition to the touchscreen, device 100 optionally includes a touchpad (not shown) for activating or deactivating certain functions. In some embodiments, the touchpad is a touch-sensitive area of ​​the device that, unlike the touchscreen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from touch-sensitive display system 112 or an extension of the touch-sensitive surface formed by the touchscreen.

[0044] Device 100 also includes a power system 162 that provides power to the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, power failure detection circuitry, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of electrical power within a portable device.

[0045] Device 100 also optionally includes one or more light sensors 164. FIG. 1A shows a light sensor coupled to light sensor controller 158 in I / O subsystem 106. Light sensor(s) 164 optionally include a charge-coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) phototransistor. Light sensor(s) 164 receive light from the environment, projected through one or more lenses, and convert the light into data representing an image. In conjunction with imaging module 143 (also called a camera module), light sensor(s) 164 optionally capture still images and / or video. In some embodiments, the light sensor is located on the back of device 100, opposite touch-sensitive display system 112 on the front of the device, so that the touchscreen can be used as a viewfinder for still and / or video image acquisition. In some embodiments, another light sensor is placed on the front of the device so that an image of the user is captured (e.g., for a selfie, for a video conference while the user is viewing other video conference participants on the touchscreen, etc.).

[0046] Device 100 also optionally includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I / O subsystem 106. Contact intensity sensor(s) 165 optionally include one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor(s) 165 receive contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is juxtaposed with or proximate to the touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touchscreen display system 112, which is located on the front of device 100.

[0047] Device 100 also optionally includes one or more proximity sensors 166. Figure 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternatively, proximity sensor 166 is coupled to input controller 160 in I / O subsystem 106. In some embodiments, the proximity sensor turns off and disables touch-sensitive display system 112 when the multifunction device is placed near a user's ear (e.g., when the user is making a phone call).

[0048] Device 100 also optionally includes one or more tactile output generators 167. FIG. 1A shows tactile output generators coupled to tactile feedback controller 161 in I / O subsystem 106. Tactile output generator(s) 167 optionally include one or more electroacoustic devices, such as speakers or other audio components, and / or electromechanical devices that convert energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components that convert electrical signals into tactile output on the device). Tactile output generator(s) 167 receive tactile feedback generation instructions from haptic feedback module 133 and generate tactile outputs on device 100 that can be sensed by a user of device 100. In some embodiments, at least one tactile output generator is located on or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112) and generates a tactile output, optionally by moving the touch-sensitive surface vertically (e.g., in / out of the surface of device 100) or horizontally (e.g., 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 of device 100, opposite touch-sensitive display system 112, which is located on the front of device 100.

[0049] Device 100 also optionally includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternatively, accelerometer 168 is optionally coupled to input controller 160 in I / O subsystem 106. In some embodiments, information is displayed on the touchscreen display in a portrait or landscape view based on analysis of data received from the one or more accelerometers. In addition to accelerometer(s) 168, device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information regarding the location and orientation (e.g., portrait or landscape) of device 100.

[0050] In some embodiments, software components stored in memory 102 include an operating system 126, a communications module (or instruction set) 128, a touch / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a haptic feedback module (or instruction set) 133, a text input module (or instruction set) 134, a Global Positioning System (GPS) module (or instruction set) 135, and applications (or instruction sets) 136. Additionally, in some embodiments, as shown in Figures 1A and 3, memory 102 stores device / global internal state 157. Device / global internal state 157 includes one or more of: active application state, which indicates which applications, if any, are currently active; display state, which indicates which applications, views, or other information occupy various areas of touch-sensitive display system 112; sensor state, which includes information obtained from the device's various sensors and other input or control devices 116; and position and / or location information regarding the device's position and / or orientation.

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

[0052] Communications module 128 facilitates communication with other devices via one or more external ports 124 and also includes various software components for processing data received by RF circuitry 108 and / or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE®, etc.) is adapted to couple to other devices directly or indirectly via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector identical to, similar to, and / or compatible with the 30-pin connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. In some embodiments, the external port is a Lightning connector identical to, similar to, and / or compatible with the Lightning connector used in some iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.

[0053] Contact / motion module 130 optionally detects contact with touch-sensitive display system 112 (in cooperation with display controller 156) and with other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact / motion module 130 includes software components for performing various operations related to detecting contact (e.g., by a finger or stylus), such as determining if contact has occurred (e.g., detecting a finger-down event), determining the intensity of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining if the contact has stopped (e.g., detecting a finger-up event or an interruption of the contact). Contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point, as represented by the series of contact data, optionally includes determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point. These actions are optionally applied to a single contact (e.g., a single finger contact or a stylus contact) or multiple simultaneous contacts (e.g., "multi-touch" / multiple finger contacts). In some embodiments, contact / motion module 130 and display controller 156 detect contacts on the touchpad.

[0054] Contact / motion module 130 optionally detects gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different movements, timing, and / or strength of the detected contacts). Thus, gestures are optionally detected by detecting particular contact patterns. For example, detecting a finger tap gesture involves detecting a finger-down event, followed by detecting a finger-up (lift-off) event at the same location (or substantially the same location) as the finger-down event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface involves detecting a finger-down event, followed by detecting one or more finger drag events, followed by detecting a finger-up (lift-off) event. Similarly, taps, swipes, drags, and other gestures are optionally detected with respect to a stylus by detecting particular contact patterns with respect to the stylus.

[0055] In some embodiments, detecting a finger tap gesture depends on the length of time between detecting a finger-down event and detecting a finger-up event, but is not related to the intensity of the finger contact between detecting the finger-down event and detecting the finger-up event. In some embodiments, a tap gesture is detected according to determining that the length of time between the finger-down event and the finger-up event is less than a predetermined value (e.g., less than 0.1, 0.2, 0.3, 0.4, or 0.5 seconds), regardless of whether the intensity of the finger contact during the tap meets a given intensity threshold (greater than a nominal contact-detection intensity threshold), such as a light or deep pressure intensity threshold. Thus, a finger tap gesture can satisfy certain input criteria that do not require the characteristic intensity of the contact to meet a given intensity threshold for the particular input criteria to be met. For clarity, finger contacts in a tap gesture generally need to meet a nominal contact-detection intensity threshold below which the contact is not detected in order to detect a finger-down event. A similar analysis applies to detecting a stylus tap gesture or other contact. In cases where the device is capable of detecting contact of a finger or stylus hovering over the touch-sensitive surface, the nominal contact-detection intensity threshold optionally does not correspond to physical contact between the finger or stylus and the touch-sensitive surface.

[0056] In a similar manner, the same concepts apply to other types of gestures. For example, swipe gestures, pinch gestures, de-pinch gestures, and / or long press gestures are optionally detected based on meeting criteria that are either unrelated to the intensity of the contacts included in the gesture or that do not require the contacts performing the gesture to reach an intensity threshold in order to be recognized. For example, a swipe gesture is detected based on the amount of movement of one or more contacts, a pinch gesture is detected based on the movement of two or more contacts toward each other, a de-pinch gesture is detected based on the movement of two or more contacts away from each other, and a long press gesture is detected based on the duration of contact on the touch-sensitive surface that is less than a threshold amount of movement. Thus, a statement that a particular gesture recognition criterion does not require the intensity of a contact(s) to meet a respective intensity threshold in order for the particular gesture recognition criterion to be satisfied means that the particular gesture recognition criterion can be satisfied when the contact(s) in the gesture do not reach their respective intensity threshold, and can also be satisfied in situations where one or more of the contacts in the gesture do not reach or exceed their respective intensity threshold. In some embodiments, a tap gesture is detected based on a determination that a finger-down event and a finger-up event are detected within a predetermined time period, regardless of whether the contacts are above or below their respective intensity thresholds during the predetermined time period, and a swipe gesture is detected based on a determination that a movement of the contact is greater than a predetermined magnitude, even if the contacts exceed their respective intensity thresholds at the end of the movement of the contact. Even in implementations in which gesture detection is affected by the intensity of the contact performing the gesture (e.g., the device detects long presses more quickly when the intensity of the contact exceeds an intensity threshold, or the device is slow to detect tap inputs when the intensity of the contact is higher), detection of those gestures does not require the contact to reach a particular intensity threshold, as long as the criteria for recognizing the gesture can be met in situations in which the contact does not reach the particular intensity threshold (e.g., even if the amount of time required to recognize the gesture varies).

[0057] The contact intensity threshold, duration threshold, and movement threshold may, in some circumstances, be combined in various different combinations to create heuristics for distinguishing between two or more different gestures directed at the same input element or region, thereby enabling multiple different interactions with the same input element to provide a richer set of user interactions and responses. A statement that a particular set of gesture recognition criteria does not require that the intensity of a contact(s) meet a respective intensity threshold for that particular gesture recognition criterion to be satisfied does not preclude the simultaneous evaluation of other intensity-dependent gesture recognition criteria to identify other gestures with criteria that are satisfied when the gesture includes a contact having an intensity above the respective intensity threshold. For example, in some circumstances, a first gesture recognition criterion for a first gesture that does not require that the intensity of a contact(s) meet a respective intensity threshold for that first gesture recognition criterion to be satisfied competes with a second gesture recognition criterion for a second gesture that depends on the contact(s) reaching a respective intensity threshold. In such a competition, a gesture is optionally not recognized as satisfying the first gesture recognition criteria for the first gesture if the second gesture recognition criteria for the second gesture are satisfied first. For example, if the contact reaches the respective intensity threshold before moving a predetermined amount of movement, a deep press gesture is detected rather than a swipe gesture. Conversely, if the contact moves a predetermined amount of movement before reaching the respective intensity threshold, a swipe gesture is detected rather than a deep press gesture. Even in such a situation, the first gesture recognition criteria for the first gesture still do not require that the intensity of the contact(s) meet the respective intensity threshold for the first gesture recognition criteria to be satisfied, because if the contact remains below the respective intensity threshold until the end of the gesture (e.g., a swipe gesture with a contact that does not increase in intensity above the respective intensity threshold), the gesture would be recognized by the first gesture recognition criteria as a swipe gesture.In this way, certain gesture recognition criteria that do not require the intensity of the contact(s) to meet a respective intensity threshold for the particular gesture recognition criterion to be satisfied are still dependent on the intensity of the contact with respect to the intensity threshold, in the sense that (A) in some circumstances, they ignore the intensity of the contact with respect to the intensity threshold (e.g., for a tap gesture), and / or (B) in some circumstances, the particular gesture recognition criterion (e.g., for a long press gesture) will not function if a competing set of intensity-dependent gesture recognition criteria (e.g., for a deep press gesture) recognizes an input as corresponding to an intensity-dependent gesture before the particular gesture recognition criterion recognizes the gesture corresponding to the input (e.g., for a long press gesture that competes with a deep press gesture for recognition).

[0058] Graphics module 132 includes various known software components for rendering and displaying graphics on touch-sensitive display system 112 or other display, including components for modifying the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including, but not limited to, text, web pages, icons (such as user interface objects including soft keys), digital images, video, and animation.

[0059] In some embodiments, graphics module 132 stores data representing the graphics to be used. Each graphic is optionally assigned a corresponding code. Graphics module 132 receives one or more codes specifying the graphics to be displayed, including coordinate data and other graphic characteristic data, as needed, from an application or the like, and then generates screen image data to output to display controller 156.

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

[0061] Text input module 134 is optionally a component of graphics module 132 and provides a soft keyboard for entering text in various applications (e.g., contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).

[0062] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for use in location-based calling, to the camera 143 as photo / video metadata, and to applications that provide location-based services such as weather widgets, local yellow pages widgets, and maps / navigation widgets).

[0063] Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof: • a contacts module 137 (sometimes called an address book or contact list); ●Telephone module 138, ●Video conferencing module 139, ● an email client module 140; ● Instant messaging (IM) module 141; ●Training support module 142, a camera module 143 for still and / or video images, ● Image management module 144; ● Browser module 147, ●Calendar module 148, a widget module 149, optionally including one or more of a weather widget 149-1, a stock price widget 149-2, a calculator widget 149-3, an alarm clock widget 149-4, a dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6; a widget creation module 150 for creating user-created widgets 149-6; ● Search module 151, • a video and music player module 152, optionally consisting of a video player module and a music player module; ● Memo module 153, Map module 154, and / or ●Online video module 155.

[0064] 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 rights management, voice recognition, and voice duplication.

[0065] Contacts module 137, along with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, includes executable instructions (e.g., stored in memory 102 or in application internal state 192 of contacts module 137 in memory 370) for managing an address book or contact list, including adding name(s) to the address book, removing name(s) from the address book, associating phone number(s), email address(es), street address(es), or other information with names, associating images with names, categorizing and sorting names, providing phone numbers and / or email addresses to initiate and / or facilitate communication by telephone 138, video conference 139, email 140, or IM 141, etc.

[0066] In cooperation with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 includes executable instructions for entering a series of characters corresponding to a telephone number, accessing one or more telephone numbers in address book 137, modifying an entered telephone number, dialing each telephone number, conducting a conversation, and disconnecting or hanging up when the conversation is completed. As noted above, wireless communication optionally uses any of a number of communication standards, protocols, and technologies.

[0067] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and terminate video conferences between a user and one or more other participants according to the user's commands.

[0068] In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, email client module 140 contains executable instructions for composing, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 144, email client module 140 greatly facilitates composing and sending emails with still or video images captured by camera module 143.

[0069] Instant message module 141, together with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, includes executable instructions to enter text strings corresponding to instant messages, modify entered text, send each instant message (e.g., using Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for telephone-based instant messaging, or using XMPP, SIMPLE, Apple Push Notification Service (APNs), or IMPS for Internet-based instant messaging), receive instant messages, and view received instant messages. In some embodiments, sent and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments, such as those supported by MMS and / or Enhanced Messaging Service (EMS). As used herein, "instant message" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs, or IMPS).

[0070] Together with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154, and the music player module 146, the training support module 142 includes executable instructions to create workouts (e.g., with time, distance, and / or calorie burn goals), communicate with training sensors (in the sports device and the smartwatch), receive training sensor data, calibrate sensors used to monitor the workouts, select and play music for the workouts, and display, store, and transmit the workout data.

[0071] Camera module 143, along with touch-sensitive display system 112, display controller 156, light sensor(s) 164, light sensor controller 158, contact module 130, graphics module 132, and image management module 144, includes executable instructions to capture still images or video (including video streams) and store them in memory 102, change characteristics of the still images or video, and / or delete the still images or video from memory 102.

[0072] Image management module 144, along with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slide show or album), and storing still and / or video images.

[0073] Browser module 147, along with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, contains executable instructions for browsing the Internet according to user commands, including retrieving, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0074] Calendar module 148, along with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) according to user instructions.

[0075] Widget modules 149, along with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, are optionally mini-applications downloaded and used by users (e.g., weather widget 149-1, stock price widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5), or mini-applications created by users (e.g., user-created widget 149-6). In some embodiments, widgets include Hypertext Markup Language (HTML) files, Cascading Style Sheets (CSS) files, and JavaScript files. In some embodiments, widgets include Extensible Markup Language (XML) files and JavaScript files (e.g., Yahoo! Widgets).

[0076] In conjunction with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget creation module 150 contains executable instructions for creating widgets (e.g., turning user-specified portions of a web page into widgets).

[0077] In cooperation with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search memory 102 for text, music, sound, images, video, and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with a user's instructions.

[0078] In cooperation with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 contains executable instructions that enable a user to download and play recorded music or other sound files stored in one or more file formats, such as MP3 or AAC files, as well as executable instructions to display, present, or otherwise play videos (e.g., on touch-sensitive display system 112 or on an external display connected wirelessly or via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (a trademark of Apple Inc.).

[0079] In conjunction with touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 contains executable instructions for creating and managing notes, to-do lists, and the like according to user commands.

[0080] In cooperation with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data about businesses and other points of interest at or near a particular location, and other location-based data) in accordance with user commands.

[0081] In cooperation with touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, online video module 155 contains executable instructions that enable a user to access, view, receive (e.g., by streaming and / or downloading), and play (e.g., on touchscreen 112 or on an external display connected wirelessly or via external port 124) online videos in one or more file formats, such as H.264, and send and otherwise manage emails with links to particular online videos. In some embodiments, instant messaging module 141 is used to send links to particular online videos, rather than email client module 140.

[0082] Each of the above-identified modules and applications corresponds to executable instruction sets that perform one or more of the functions described above and methods described in the present application (e.g., computer-implemented methods and other information processing methods described herein). The modules (i.e., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, various subsets of the modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the above-identified modules and data structures. Additionally, memory 102 optionally stores additional modules and data structures not described above.

[0083] In some embodiments, device 100 is a device in which operation of a predetermined set of functions on the device is performed exclusively through a touchscreen and / or touchpad. Using the touchscreen and / or touchpad as the primary input control device for operation of device 100 optionally reduces the number of physical input control devices (push buttons, dials, etc.) on device 100.

[0084] The set of predetermined functions performed only through the touchscreen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 to a main menu, home menu, or root menu from any user interface displayed on device 100. In such 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 rather than a touchpad.

[0085] 1B is a block diagram illustrating exemplary components for event processing, according to some embodiments. In some embodiments, memory 102 (in FIG. 1A) or 370 (in FIG. 3) includes an event sorter 170 (e.g., within operating system 126) and a respective application 136-1 (e.g., any of applications 136, 137-155, 380-390 described above).

[0086] Event sorter 170 receives the event information and determines application 136-1 and application view 191 of application 136-1 to which the event information should be delivered. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192 that indicates the current application view(s) that are displayed on touch-sensitive display system 112 when the application is active or running. In some embodiments, device / global internal state 157 is used by event sorter 170 to determine which application(s) are currently active, and application internal state 192 is used by event sorter 170 to determine application view 191 to which the event information should be delivered.

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

[0088] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user's touch on touch-sensitive display system 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, accelerometer(s) 168, and / or microphone 113 (via audio circuitry 110). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.

[0089] 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, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or for longer than a predetermined period of time).

[0090] In some embodiments, the event sorter 170 also includes a hit view determination module 172 and / or an active event recognizer determination module 173 .

[0091] Hit view determination module 172 provides software procedures for determining where in one or more views a sub-event occurred when touch-sensitive display system 112 displays more than one view. A view consists of the controls and other elements that a user can see on the display.

[0092] Another aspect of a user interface associated with an application is the set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which the touch is detected optionally corresponds to a programmatic level within the application's programmatic or view hierarchy. For example, the lowest-level view in which the touch is detected is optionally referred to as the hit view, and the set of events that are recognized as appropriate inputs is optionally determined based at least in part on the hit view of the initial touch that initiates the touch gesture.

[0093] Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should process the sub-events. In most situations, the hit view is the lowest-level view in which the initiating sub-event occurs (i.e., the first sub-event in a series of sub-events that form an event or potential event). Once a hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

[0094] Active event recognizer determination module 173 determines which view(s) in the view hierarchy should receive the particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive the particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that contain the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with one particular view, views higher in the hierarchy still remain actively participating views.

[0095] Event dispatcher module 174 dispatches event information to event recognizers (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores event information obtained by each event receiver module 182 in an event queue.

[0096] In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In still other embodiments, event sorter 170 is a stand-alone module or part of another module stored in memory 102, such as contact / motion module 130.

[0097] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each containing instructions for processing touch events that occur within a respective view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, each application view 191 includes multiple 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 higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, the corresponding event handler 190 includes one or more of a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or invokes data updater 176, object updater 177, or GUI updater 178 to update application internal state 192. Instead, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of the data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

[0098] Each event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event recognizer 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (optionally including sub-event delivery instructions).

[0099] The event receiver 182 receives event information from the event sorter 170. The event information includes information about a sub-event, for example, information about a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as the position of the sub-event. When the sub-event involves a touch movement, the event information also optionally includes the speed and direction of the sub-event. In some embodiments, the event includes a rotation of the device from one orientation to another (e.g., from portrait to landscape or vice versa), and the event information includes corresponding information about the device's current orientation (also called the device's attitude).

[0100] The event comparator 184 compares the event information to predefined event or sub-event definitions and determines the event or sub-event, or determines or updates the state of the event or sub-event, based on the comparison. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes a definition of an event (e.g., a predetermined sequence of sub-events), such as Event 1 (187-1) and Event 2 (187-2). In some embodiments, the sub-events in Event 187 include, for example, a touch start, a touch end, a touch movement, a touch cessation, and multiple touches. In one example, the definition for Event 1 (187-1) is a double tap on a displayed object. The double tap includes, for example, a first touch (touch start) for a predetermined phase on the displayed object, a first lift-off (touch end) for a predetermined phase on the displayed object, a second touch (touch start) for a predetermined phase on the displayed object, and a second lift-off (touch end) for a predetermined phase. In another example, the definition of event 2 (187-2) is a drag on a displayed object. Drag includes, for example, a touch (or contact) of a predetermined magnitude on a displayed object, a movement of the touch across touch-sensitive display system 112, and a lift-off of the touch (end of the touch). In some embodiments, the event also includes information about one or more associated event handlers 190.

[0101] In some embodiments, event definition 187 includes a definition of the event for each 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 touch-sensitive display system 112, when a touch is detected on touch-sensitive display system 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, event comparator 184 uses the results of the hit test to determine which event handler 190 to activate. For example, event comparator 184 selects the event handler associated with the sub-event and object that triggers the hit test.

[0102] In some embodiments, each event 187 definition also includes a delay action that delays delivery of the event information until it is determined whether a set of sub-events corresponds to the event recognizer's event type.

[0103] If the respective event recognizer 180 determines that the sequence of sub-events does not match any event in the event definition 186, the respective event recognizer 180 enters an event disabled, event failed, or event finished state and thereafter ignores subsequent sub-events of the touch gesture. In this situation, any other event recognizers that remain active for the hit view continue to track and process sub-events of the ongoing touch gesture.

[0104] In some embodiments, corresponding event recognizers 180 include metadata 183 with configurable properties, flags, and / or lists that indicate to actively participating event recognizers how the event delivery system should perform sub-event delivery. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact with each other or how event recognizers are enabled to interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how sub-events are delivered to various levels in the view or programmatic hierarchy.

[0105] In some embodiments, each event recognizer 180 activates an event handler 190 associated with an event when one or more specific sub-events of the event are recognized. In some embodiments, each event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is separate from sending (and deferring sending) sub-events to the respective hit view. In some embodiments, the event recognizer 180 pops a flag associated with the recognized event, and the event handler 190 associated with that flag captures the flag and performs a predetermined process.

[0106] In some embodiments, the event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with a set of sub-events or to an actively participating view. The event handler associated with the set of sub-events or the actively participating view receives the event information and performs predetermined processing.

[0107] In some embodiments, data updater 176 creates and updates data used by application 136-1. For example, data updater 176 updates phone numbers used by contacts module 137 or stores video files used by video player module 145. In some embodiments, object updater 177 creates and updates objects used by application 136-1. For example, object updater 177 creates new user interface objects or updates the positions of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on the touch-sensitive display.

[0108] In some embodiments, event handler(s) 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0109] It should be understood that the foregoing description of event processing of a user's touch on a touch-sensitive display also applies to other forms of user input for operating multifunction device 100 using input devices, not all of which are initiated on the touchscreen. For example, mouse movements and mouse button presses, contact movements such as tapping, dragging, scrolling on a touchpad, optionally coordinated with single or multiple keyboard presses or holds, pen stylus input, device movement, verbal commands, detected eye movement, biometric input, and / or any combination thereof, are optionally utilized as inputs corresponding to sub-events that define the recognized event.

[0110] FIG. 2 illustrates portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A ) according to some embodiments. The touchscreen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as other embodiments described below, a user can select one or more of the graphics by performing a gesture on the graphics, for example, using one or more fingers 202 (not drawn to scale) or one or more styluses 203 (not drawn to scale). In some embodiments, selection of one or more graphics is performed when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, upward and / or downward), and / or rolling of a finger in contact with device 100 (right to left, left to right, upward and / or downward). In some implementations or situations, accidental contact with a graphic does not select the graphic, for example, if the gesture corresponding to selection is a tap, a swipe gesture sweeping over an application icon optionally does not select the corresponding application.

[0111] Device 100 also optionally includes one or more physical buttons, such as a "home" or menu button 204. As mentioned above, menu button 204 is optionally used to navigate to any application 136 in a set of applications optionally running on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key within a GUI displayed on a touchscreen display.

[0112] In some embodiments, device 100 includes a touchscreen display, a menu button 204, a push button 206 for powering the device on / off and locking the device, volume control button(s) 208, a subscriber identity module (SIM) card slot 210, a headset jack 212, and an external docking / charging port 124. Push button 206 is optionally used to power the device on / off by pressing and holding the button down for a predetermined period of time, to lock the device by pressing and releasing the button before the predetermined period of time has elapsed, and / or to unlock the device or begin the unlocking process. In some embodiments, device 100 also accepts verbal input through microphone 113 to activate or deactivate some features. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting contact intensity on touch-sensitive display system 112 and / or one or more tactile output generators 167 for generating tactile outputs to a user of device 100.

[0113] FIG. 3 is a block diagram of an exemplary multifunction device having a display and a touch-sensitive surface, according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia playback device, a navigation device, an educational device (such as a child's learning toy), a gaming system, or a control device (e.g., a home or commercial 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 320 for interconnecting these components. Communication bus 320 optionally includes circuitry (sometimes called a chipset) that interconnects and controls communication between system components. Device 300 includes input / output (I / O) interface 330, which includes display 340, which is typically a touchscreen display. I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350, as well as a touchpad 355, a tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A ), sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch-sensitive sensors, and / or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A ). Memory 370 includes high-speed random-access memory such as DRAM, SRAM, DDR RAM, or other random-access solid-state memory devices, and optionally includes 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 310.In some embodiments, memory 370 stores programs, modules, and data structures similar to, or a subset of, programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A). Additionally, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, ​​word processing module 384, website creation module 386, disc authoring module 388, and / or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store those modules.

[0114] 3 is optionally stored in one or more of the memory devices mentioned above. Each of the identified modules corresponds to an instruction set that performs the functions described above. The identified modules or programs (i.e., instruction sets) need not be implemented as separate software programs, procedures, or modules; thus, various subsets of those modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the identified modules and data structures. Additionally, memory 370 optionally stores additional modules and data structures not described above.

[0115] Attention is now directed to embodiments of a user interface (“UI”) that is optionally implemented on portable multifunction device 100.

[0116] 4A shows an exemplary user interface for a menu of applications on portable multifunction device 100, according to some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof: signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals; ●Time 404, ●Bluetooth indicator 405, ● Battery status indicator 406, • A tray 408 with icons for frequently used applications, such as: an icon 416 for the phone module 138, labeled "Phone," optionally including an indicator 414 of the number of missed calls or voicemail messages; An icon 418 for the email client module 140, labeled "Mail", optionally including an indicator 410 of the number of unread emails; ○ An icon 420 for the browser module 147, labeled "Browser", and ○ An icon 422 for the video and music player module 152, also called the iPod (trademark of Apple Inc.) module 152, labeled "iPod", and ● Icons for other applications, such as: ○ Icon 424 for IM module 141, labeled "Messages"; ○ Icon 426 for the calendar module 148, labeled "Calendar", ○ Icon 428 for the image management module 144, labeled "Photos"; ○ An icon 430 for the camera module 143, labeled "camera"; ○ Icon 432 for the online video module 155, labeled "Online Video"; Icon 434 for stock widget 149-2, labeled "Stock Prices" ○ Icon 436 for the map module 154, labeled "Map"; ○ Icon 438 for weather widget 149-1, labeled "Weather" ○ Icon 440 for alarm clock widget 149-4, labeled "Clock" ○ An icon 442 for the training support module 142, labeled "Training Support"; ○ An icon 444 for the notes module 153, labeled "Notes," and ○ An icon 446 for a settings application or module that provides access to settings related to the device 100 and its various applications 136.

[0117] Note that the icon labels shown in FIG. 4A are merely examples. For example, in some embodiments, 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 each application icon includes the name of the application corresponding to the respective application icon. In some embodiments, the label for a particular application icon is different from the name of the application corresponding to that particular application icon.

[0118] 4B shows an exemplary user interface on a device (e.g., device 300, FIG. 3) having touch-sensitive surface 451 (e.g., tablet or touchpad 355, FIG. 3) separate from display 450. Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting the intensity of a contact on touch-sensitive surface 451, and / or one or more tactile output generators 359 for generating a tactile output for a user of device 300.

[0119] FIG. 4B shows an example user interface on a device (e.g., device 300, FIG. 3) that has touch-sensitive surface 451 (e.g., tablet or touchpad 355, FIG. 3) separate from display 450. While many of the following examples are given with reference to input on touchscreen display 112 (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface separate from the display, as shown in FIG. 4B . In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B ) has a major axis (e.g., 452 in FIG. 4B ) that corresponds to a major axis (e.g., 453 in FIG. 4B ) on the display (e.g., 450). According to these embodiments, the device detects contact with touch-sensitive surface 451 (e.g., 460 and 462 in FIG. 4B ) at locations that correspond to respective locations on the display (e.g., 460 corresponds to 468, and 462 corresponds to 470 in FIG. 4B ). In this manner, when the touch-sensitive surface is separate from the display, user input (e.g., contacts 460 and 462, and their movement) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B ) is used by the device to operate a user interface on the display (e.g., 450 in FIG. 4B ) of the multifunction device. It should be understood that similar methods are optionally used for the other user interfaces described herein.

[0120] Additionally, while the following examples are given primarily with reference to finger input (e.g., finger touches, finger tap gestures, finger swipe gestures, etc.), it should be understood that in some embodiments, one or more of those finger inputs are replaced with input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of a touch) followed by cursor movement along the path of the swipe (e.g., instead of a touch movement). As another example, a tap gesture is optionally replaced with a mouse click while the cursor is positioned over the tap gesture location (e.g., instead of detecting a touch and then ceasing contact detection). Similarly, it should be understood that when multiple user inputs are detected simultaneously, multiple computer mice are optionally used simultaneously, or a mouse and finger touches are optionally used simultaneously.

[0121] As used herein, the term “focus selector” refers to an input element that indicates the current portion of a user interface with which a user is interacting. In some implementations involving a cursor or other location marker, the cursor functions as a “focus selector” such that when input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B ) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations involving a touchscreen display (e.g., touch-sensitive display system 112 in FIG. 1A or touchscreen in FIG. 4A ) that enables direct interaction with user interface elements on the touchscreen display, a contact detected on the touchscreen functions as a “focus selector” such that when input (e.g., a press input by a contact) is detected on the touchscreen display at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations, focus is moved from one region of the user interface to another region of the user interface (e.g., by using the tab key or arrow keys to move focus from one button to another) without a corresponding cursor movement or contact movement on the touchscreen display. In these implementations, the focus selector moves to follow the movement of focus between various regions of the user interface. Regardless of the specific form taken by the focus selector, the focus selector is generally a user interface element (or a contact on a touchscreen display) that is controlled by the user to communicate the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user intends to interact with).For example, while a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, touch, or selection box) over a corresponding button indicates that the user intends to activate that corresponding button (and not other user interface elements shown on the device's display). User Interface and Associated Processing

[0122] Attention is now directed to embodiments of user interfaces (“UIs”) and associated processing that may be implemented on an electronic device such as portable multifunction device 100 or device 300, which includes a display, radio frequency (RF) circuitry for wirelessly communicating with one or more peripheral devices, one or more input devices (e.g., a touch-sensitive surface) for receiving input from a user, and (optionally) one or more sensors for detecting the intensity of contact with the touch-sensitive surface.

[0123] 5A-5Z show exemplary user interfaces for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIGS. 6A-6C. For ease of explanation, some of the embodiments are discussed with reference to operations performed on a device having touch-sensitive display system 112. In such embodiments, the focus selector is optionally a respective finger or stylus contact, a representative point corresponding to a finger or stylus contact (e.g., the face centroid of each contact or a point associated with each contact), or the face centroid of two or more contacts detected on touch-sensitive display system 112. However, similar operations, along with a focus selector, are optionally performed on a device having display 450 and separate touch-sensitive surface 451 in response to detecting contacts on touch-sensitive surface 451 while displaying the user interface shown in the figures on display 450.

[0124] 5A shows an exemplary user interface on display 100 of device 112. While displaying the user interface, device 100 periodically and repeatedly listens for wireless broadcast signals (e.g., pairing requests) from one or more peripheral devices (e.g., earbuds 502-1 and 502-2 and earbud case 502-3) to pair the peripheral devices with device 100. In some embodiments, as shown throughout FIGS. 5A-5Z, device 100 can detect pairing requests from peripheral devices when the peripheral devices are within threshold distance 508 of device 100 and cannot detect pairing requests from peripheral devices when the peripheral devices are outside threshold distance 508. For example, the bottom of Figure 5A shows an example spatial relationship (e.g., physical distance) between device 100 and earbuds 502-1 and 502-2 and earbud case 502-3, where earbuds 502-1 and 502-2 and earbud case 502-3 are outside threshold distance 508 of device 100. In contrast, Figure 5B shows a case where earbuds 502-1, earbuds 502-2 and earbud case 502-3 (collectively referred to as earbud set 503) are within threshold distance 508 of device 100, and the device is able to detect a pairing request from a peripheral device. (Note that earbuds are also called earpods, earbuds, and in-ear headphones.)

[0125] FIG. 5B shows an exemplary user interface for initiating pairing between device 100 and a peripheral device (e.g., earbud 502-1), displayed subsequent to the user interface of FIG. 5A. In FIG. 5B, device 100 detects a pairing request from a peripheral device (e.g., earbud 502-1 and part of earbud set 503 shown in FIG. 5A) that is within threshold distance 508. In response to detecting the pairing request from earbud 502-1, device 100 determines whether earbud 502-1 meets the coupling criteria. In the example shown in FIG. 5B, the coupling criteria are met when earbud 502-1 is placed within and / or electrically coupled to earbud case 502-3 to form earbud set 503. After device 100 determines that earbud 502-1 meets the coupling criteria, device 100 displays window 520-1 showing earbud set 503 overlaying the first user interface. Window 520-1 includes a "Connect" button 522-1 that, when activated by user input (e.g., a tap gesture), initiates pairing of device 100 with the peripherals of earbud set 503 (e.g., earbuds 502-1 and 502-2 and earbud case 502-3 shown in FIG. 5A).

[0126] 5C-5E show exemplary user interfaces for initiating pairing of device 100 with a peripheral device (e.g., earbud 502-1 of earbud set 503) that are displayed subsequent to the user interface of FIG. 5B. In FIG. 5C, device 100 detects tap gesture 530-1 on button 522-1. In response to detecting tap gesture 530-1, device 100 initiates pairing of device 100 with the peripheral device of earbud set 503. In FIG. 5D, while device 100 is pairing with the peripheral device of earbud set 503, device 100 displays "Connect..." notification graphic 523-1 in window 520-1. 5E , after device 100 pairs with earbud set 503 peripherals, device 100 displays status information in window 520-1, including battery level graphic 526-1 indicating the battery level of earbuds 502-1 and 502-2 and battery level graphic 526-2 indicating the battery level of earbud case 502-3. Device 100 also displays “Done” button 524-1, which, when activated by user input such as a tap gesture, causes window 520-1 to cease displaying and allows the user to perform other conventional operations on device 100. In some embodiments, window 520-1 ceases displaying after a predetermined period of time, even if the “Done” button is not activated.

[0127] 5F shows an exemplary user interface displayed subsequent to the user interface of FIG. 5A for displaying information regarding pairing between device 100 and a peripheral device (e.g., earbud 502-1) when the coupling criteria are not met. In FIG. 5F, device 100 detects a pairing request from earbud 502-1 within threshold distance 508. In response to detecting the pairing request from earbud 502-1, device 100 determines whether earbud 502-1 meets the coupling criteria. In the example shown in FIG. 5F, the coupling criteria are not met when earbud 502-1 is not placed within and / or electrically coupled to earbud case 502-3. Two different examples in which earbud 502-1 does not meet the coupling criteria are shown at the bottom of FIG. 5F. In the lower left of Figure 5F, earbud 502-1 and earbud case 502-3 are within threshold distance 508, but earbud 502-2 is not within threshold distance 508. In the lower right of Figure 5F, earbud 502-1, earbud 502-2, and earbud case 502-3 are all within threshold distance 508. However, in both exemplary embodiments, earbud 502-1 is not located within or electrically coupled to earbud case 502-3, and therefore does not meet the coupling criteria. After device 100 determines that earbud 502-1 does not meet the binding criteria, device 100 displays window 520-2 overlaying the first user interface displaying information about binding earbud 502-1 (and optionally earbud 502-2) to case 502-3 (such as graphics instructing the user to "Place Earpods in Case" and "Make sure both earpods are in the case!").After earbud 502-1 meets the binding criteria (e.g., after earbud 502-1 is placed in earbud case 502-3 as shown in FIG. 5B), device 100 displays a user interface as shown in FIG. 5B to pair device 100 with earbud set 503.

[0128] FIG. 5G shows an exemplary user interface displayed following the user interface of FIG. 5E for displaying certain status information about a peripheral device after the peripheral device has previously paired with device 100. In FIG. 5G, device 100 detects a pairing request from earbud 502-1. After detecting the pairing request, device 100 displays window 520-3 overlaying the user interface. Window 520-3 includes a battery level graphic 526-3 for earbud 502-1. In this example, earbud 502-1 is identified as user Emily's left earbud by the graphic (e.g., "L") displayed in window 520-3. In other examples, the earbud may be identified as the right earbud by displaying a different graphic (e.g., the "R" graphic shown for earbud 502-2 in FIG. 5H). Also as shown, battery level graphic 526-3 for earbud 502-1 indicates a battery level of "50%."

[0129] 5H-5P show exemplary user interfaces that follow the user interface of FIG. 5E for displaying specific information about two or more peripheral devices after at least one peripheral device has paired with device 100.

[0130] 5H, device 100 detects pairing requests from each of earbuds 502-1 and 502-2. After detecting the pairing requests, device 100 determines that earbuds 502-1 and 502-2 are part of the defined set, for example, because both earbuds 502-1 and 502-2 have previously paired with device 100 in a single pairing process. In response to determining that earbuds 502-1 and 502-2 are part of the defined set, device 100 displays window 520-4 overlaying its user interface. Window 520-4 displays battery level graphic 526-4 indicating a battery level of "50%" for earbud 502-1 and battery level graphic 526-5 indicating a battery level of "100%" for earbud 502-2.

[0131] In Figure 5I, device 100 detects pairing requests from earbuds 502-4 and 502-5 and earbud case 502-3. Earbuds 502-4 and 502-5 are shown in bold black at the bottom of Figure 5I to indicate that earbuds 502-4 and 502-5 have not previously paired with device 100 to form part of a defined set. After detecting the pairing requests, device 100 determines that earbuds 502-4 and 502-5 are not part of the defined set because, for example, both earbuds 502-4 and 502-5 have not previously been paired with device 100. In response to determining that earbuds 502-4 and 502-5 are not part of the defined set, device 100 displays window 520-5 overlaying the user interface. Because earbuds 502-4 and 502-5 have not previously been paired with device 100 (as indicated by a graphic such as an "!" displayed adjacent to each of earbuds 502-4 and 502-5), whereas earbud case 502-3 has previously been paired with device 100, window 520-5 includes information regarding a mismatch between earbuds 502-4 and 502-5 and earbud case 502-3. Window 520-5 also includes a "Connect" button 522-2 that, when activated by user input (e.g., a tap gesture), initiates pairing of earbuds 502-4 and 502-5 with device 100 pursuant to a determination that earbuds 502-4 and 502-5 meet the coupling criteria.

[0132] 5J-5K show exemplary user interfaces subsequent to the user interface of FIG. 5E for selectively displaying separate or combined status information for two or more peripheral devices based on the peripheral device's status characteristics. In these examples, device 100 detects pairing requests from each of earbuds 502-1 and 502-2. After detecting the pairing requests, device 100 determines that earbuds 502-1 and 502-2 are part of a defined set, for example, because earbuds 502-1 and 502-2 have both previously paired with device 100 in a single pairing process. In response to determining that earbuds 502-1 and 502-2 are part of the defined set, device 100 determines whether the difference in battery levels (an example of a status characteristic) between earbuds 502-1 and 502-2 exceeds or does not exceed a predetermined threshold (e.g., 10%). 5J, if device 100 determines that the difference does not exceed the predetermined threshold, device 100 displays window 520-6 in window 520-4 overlaid on the user interface and containing combined status information for both earbuds 502-1 and 502-2 (e.g., displaying a single battery level graphic 526-6 of 50% for earbuds 502-1 and 502-2). Conversely, if device 100 determines that the difference exceeds the predetermined threshold, as shown in FIG. 5K, device 100 displays window 520-7 in window 520-5 overlaid on the user interface and containing separate status information for each of earbuds 502-1 and 502-2 (e.g., displaying battery level graphic 526-7 indicating a battery level of 50% for earbud 502-1 and battery level graphic 526-8 indicating a battery level of 100% for earbud 502-2).

[0133] 5L-5P show alternative exemplary user interfaces to those displayed in FIGS. 5H-5K.

[0134] In FIG. 5L, after device 100 detects a pairing request from at least one of earbuds 502-1 and 502-2 and earbud case 502-3 and determines that earbuds 502-1 and 502-2 and earbud case 502-3 are part of a predefined set, device 100 displays window 520-8 containing status information for each of earbuds 502-1 and 502-2 and earbud case 502-3 (e.g., displaying battery level graphic 526-9 indicating a 50% battery level for earbud 502-1, battery level graphic 526-10 indicating a 100% battery level for earbud 502-2, and battery level graphic 526-11 indicating a 100% battery level for earbud case 502-3) overlaid on the user interface.

[0135] Figure 5M is similar to Figure 5L, except that device 100 determines that the battery level of earbud 502-1 is below a minimum charge threshold. In response to determining that the battery level of earbud 502-1 is below a minimum charge threshold, device 100 displays window 520-9 overlaying the user interface with status information for earbud 502-1, including a low battery graphic 527.

[0136] Figure 5N is similar to Figure 5M, except that device 100 determines that earbuds 502-1 and 502-2 of Figure 5M are coupled to earbud case 502-3 (which includes a power source for the earbuds) of Figure 5M to form earbud set 503. In response to determining that earbuds 502-1 and 502-2 are coupled to a power source, device 100 displays window 520-10 overlaying the user interface with status information indicating that earbuds 502-1 and 502-2 are charging (e.g., battery charging graphic 528-1 indicating that earbuds 502-1 and 502-2 are charging, and battery level graphic 526-11 indicating a battery level of 100% for earbud case 502-3).

[0137] Figure 5O is similar to Figure 5N, except that device 100 determines that earbud set 503 is coupled to an external power source 535 (e.g., a wall outlet). In response to determining that earbud set 503 is coupled to an external power source 535, device 100 displays window 520-11 containing status information overlaid on the user interface indicating that earbuds 502-1 and 502-2 and earbud case 502-3 are charging (e.g., displaying battery charging graphic 528-2 indicating that earbud 502-1 is charging and has a battery level of 30%, battery charging graphic 528-3 indicating that earbud 502-2 is charging and has a battery level of 70%, and battery charging graphic 528-4 indicating that earbud case 502-3 is charging and has a battery level of 70%).

[0138] 5P is similar to FIG. 5I, except that earbud 502-1 has previously been paired with device 100, while earbud 502-5 has not previously been paired with device 100. After device 100 detects pairing requests from earbuds 502-1 and 502-5 and determines that earbuds 502-1 and 502-5 are not part of a predefined set, device 100 displays window 520-12 overlaying its user interface. Window 520-12 contains information about the mismatch between earbuds 502-1 and 502-5, indicating to the user that earbuds 502-1 and 502-5 are not part of a predefined set and must be paired before use. Window 520-12 also includes a "Connect" button 522-3 that, when activated by user input (e.g., a tap gesture), initiates pairing of earbuds 502-1 and 502-5 with device 100 to form a predefined set.

[0139] 5Q-5Z show exemplary user interfaces for pairing an electronic device with one or more peripheral devices and displaying status information about the peripheral device(s) while the electronic device is in a locked state, according to some embodiments.

[0140] 5Q shows an example user interface on display 112 of device 100 while device 100 is in a locked state. In this example, the example user interface while device 100 is in a locked state is a lock screen. While displaying the lock screen, device 100 repeatedly listens for pairing requests from peripheral devices, such as earbud 502-1, earbud 502-2, and earbud case 502-3, to pair the peripheral devices with device 100. In this example, earbud 502-1, earbud 502-2, and earbud case 502-3 are outside threshold distance 508 of device 100. Therefore, device 100 cannot detect pairing requests from earbud 502-1, earbud 502-2, or earbud case 502-3.

[0141] 5R shows an exemplary user interface for initiating pairing between device 100 and a peripheral device (e.g., an earbud of earbud set 503), displayed subsequent to the user interface of FIG. 5Q. In FIG. 5R, device 100 detects a pairing request from earbud 503 when earbud set 503 is within threshold distance 508. In response to detecting a pairing request from the earbud, device 100 determines whether the earbud meets the binding criteria. In this example, the binding criteria are met when the earbud is placed in and / or electrically coupled to an earbud case to form earbud set 503. After device 100 determines that the earbud meets the binding criteria, device 100 displays window 520-13 overlaying the first user interface, showing the earbud sets 503 that are within threshold distance 508 of device 100. Window 520 also includes an "Unlock to Connect" button 522-4 that, when activated by user input (e.g., a tap gesture), initiates pairing of device 100 with the peripherals of earbud set 503 (e.g., earbuds 502-1 and 502-2 and earbud case 502-3 shown in FIG. 5Q).

[0142] 5S-5U show exemplary user interfaces displayed following the user interface of FIG. 5R for initiating pairing of device 100 with a peripheral device based on a first authentication input (e.g., a finger input on fingerprint sensor 204). In FIG. 5S, after device 100 determines that earbud 502-1 meets the binding criteria, device 100 detects touch input 530-2 (e.g., a static press or tap) on fingerprint sensor 204. In response to detecting a valid user authentication input via touch input 530-2, device 100 initiates pairing of device 100 with the peripheral device of earbud set 503. In FIG. 5T, while device 100 is pairing the peripheral device of earbud set 503, device 100 displays a "Connect..." notification graphic 523-2 in window 520-13. 5U, after device 100 pairs with earbuds 502-1, 502-2, and earbud case 502-3, device 100 displays status information (e.g., battery charging graphic 528-5 indicating that earbuds 502-1 and 502-2 are charging, and battery level graphic 526-12 indicating a 100% battery level for earbud case 502-3) in window 520-13. Device 100 also displays “Done” button 524-2 that, when activated by user input such as a tap gesture, stops displaying window 520-13 and allows the user to perform other actions on device 100.

[0143] 5V-5Y show exemplary user interfaces displayed following the user interface of FIG. 5R for initiating pairing between device 100 and a peripheral device (e.g., an earbud of earbud set 503) based on a second authentication input (e.g., a passcode typed on a keypad). In FIG. 5V, after device 100 determines that an earbud of earbud set 503 meets the binding criteria, device 100 detects tap gesture 530-3 on "Unlock to Connect" button 522-4. In FIG. 5W, in response to detecting tap gesture 530-3, device 100 displays a user interface including keypad 536 to authenticate the user. In this example, keypad 536 is a numeric keypad having unique number inputs 537-1 through 537-9 corresponding to the numbers 1 through 9, respectively. Device 100 then detects a user authentication input via tap gesture 530-4 (e.g., a tap gesture) on one or more of number inputs 537-1 through 537-9. In response to device 100 detecting a valid authentication input, device 100 initiates pairing of device 100 with the peripherals of earbud set 503. In FIG. 5X, while device 100 is pairing with earbud set 503, device 100 displays a "Connect..." notification graphic 523-3 in window 520-13. Furthermore, while device 100 is pairing, device 100 maintains a lock screen display and continues to operate in a locked state. In FIG. 5Y, as similarly shown in FIG. 5U, after device 100 pairs with the peripherals of earbud set 503, device 100 displays status information in window 520-13 (e.g., displaying battery charging graphic 528-6 indicating that earbuds 502-1 and 502-2 of earbud set 503 are charging, and battery level graphic 526-13 indicating a 100% battery level for earbud case 502-3 of earbud set 503).Device 100 also displays a "Done" button 524-2 that, when activated by user input such as a tap gesture, stops displaying window 520-13 and allows the user to perform other conventional operations on device 100.

[0144] FIG. 5Z shows an example user interface displayed following the user interface of FIG. 5Y or 5U for displaying certain status information about peripheral devices after the peripheral devices have previously paired with device 100. In FIG. 5Z, device 100 detects pairing requests from earbuds 502-1 and 502-2. After detecting the pairing requests, device 100 displays window 520-14 overlaying the user interface. Window 520-14 includes battery level graphics 526-14 (an example of status information) for earbuds 502-1 and 502-2. As shown, battery level graphics 526-14 for earbuds 502-1 and 502-2 show a battery level of "50%."

[0145] 6A-6C are flow diagrams illustrating a method 600 for pairing an electronic device with a peripheral device and displaying status information about the peripheral device, according to some embodiments. Method 600 is performed on an electronic device (e.g., device 300 of FIG. 3 or portable multifunction device 100 of FIG. 1A) that includes a display, radio frequency (RF) circuitry for wirelessly communicating with one or more peripheral devices, and one or more input devices (e.g., a touch-sensitive surface) for receiving input from a user. In some embodiments, the display is a touchscreen display, and the touch-sensitive surface is on or integrated into the display. In some embodiments, the display is separate from the touch-sensitive surface. Some operations of method 600 are optionally combined, and / or the order of some operations is optionally changed.

[0146] As described below, method 600 provides an intuitive way to pair peripherals with a device and display peripheral status information. The method reduces the number, range, and / or nature of inputs from a user when pairing peripherals with a device and displaying peripheral status information, thereby creating a more efficient human-machine interface. In battery-operated electronic devices, enabling users to more quickly and efficiently pair peripherals with a device and display status information conserves power and increases the time between battery charges.

[0147] The device displays (602) a first user interface (e.g., a home screen, an application user interface, a wake screen, a lock screen, etc.) on a display.

[0148] While displaying the first user interface, the device detects (604) a pairing request to pair a first peripheral device (e.g., earbuds 502-1 and 502-2, earbud case 502-3, etc.) with the electronic device. In some embodiments, the pairing request is detected when the user touches one or both of the earbuds or earbud case of the electronic device or brings the electronic device and earbuds within a threshold distance of each other. In some embodiments, the electronic device detects the presence and proximity of the earbud(s) or earbud case by wireless signals (e.g., broadcast Bluetooth signals or Bluetooth pairing requests) emitted by the earbud(s) or earbud case. In some embodiments, the electronic device detects the presence and proximity of the earbud(s) or earbud case by other proximity sensing mechanisms (e.g., other RF signal sensing mechanisms) embedded in the electronic device and the earbuds and / or earbud case.

[0149] In some embodiments, detecting a pairing request to pair the first peripheral device with the electronic device includes detecting a wireless signal transmitted from the first peripheral device and determining, based on the detected wireless signal, that the first peripheral device satisfies a proximity criterion (606). In some embodiments, the proximity criterion includes a criterion that is met when a signal strength of the wireless signal from the first peripheral device exceeds a signal strength threshold. In some embodiments, the proximity criterion includes a criterion that is met when the electronic device and the earbud are within a threshold distance of each other. For example, as shown in FIG. 5F, the first peripheral device (e.g., earbud 502-1) is within threshold distance 508 of the electronic device 100.

[0150] In response to detecting the pairing request, the device determines 608 whether the first peripheral device meets coupling criteria that require the first peripheral device to be coupled (e.g., electrically, magnetically, and / or wirelessly) to a second peripheral device. The second peripheral device is separate from the electronic device, and both the first and second peripheral devices are external to the electronic device. In some embodiments, as shown in FIG. 5B (as part of earbud set 503), the first peripheral device is an earbud (e.g., earbud 502-1) and the second peripheral device is an earbud case (e.g., earbud case 502-3) for storing and charging the first earbud, and the coupling criteria require the earbud and case to be in proximity to each other (e.g., the earbud is in the case and, optionally, electrically connected to the case) and to the electronic device. In some embodiments, the first peripheral device is an earbud (e.g., earbud 502-1) and the second peripheral device is a second earbud (e.g., earbud 502-2), and the coupling criteria require that the first earbud and the second earbud are coupled to each other via a case (e.g., earbud case 502-3). For example, both earbuds are electrically connected to the case (e.g., when placed inside the case with the lid closed). In some embodiments, the first peripheral device is the first earbud and the second peripheral device is the second earbud, and the coupling criteria require that the first earbud and the second earbud are in proximity to each other and to the device (e.g., both the first earbud and the second earbud are stored in an earbud case or placed near each other without a case). In some embodiments, the first peripheral device is an earbud case and the second peripheral device is one or both earbuds, and the coupling criteria require that the earbud and case be coupled to each other or placed in close proximity to each other and the device.

[0151] In some embodiments, the coupling criteria include criteria that are met when the first peripheral device is coupled (610) (e.g., electrically, magnetically, and / or wirelessly) to a third peripheral device that is separate from the second peripheral device. In some embodiments, the first peripheral device is an earbud, the second peripheral device is another earbud, and the third peripheral device is an earbud case, and the coupling criteria require that the first earbud and the second earbud are electrically coupled to each other via the earbud case. For example, as shown in FIG. 5B , earbud 502-1, earbud 502-2, and earbud case 502-3 are all coupled to form earbud set 503.

[0152] In some embodiments, the first peripheral device is one or more earbuds and the second peripheral device is a case for the one or more earbuds (612).

[0153] In some embodiments, the coupling criteria include criteria that are met when one or more earbuds are inside the case and / or electrically coupled to the case (614). In some embodiments, as shown in FIG. 5B, earbuds 502-1 and 502-2 are inside and electrically coupled to earbud case 502-3 to form earbud set 503. In some embodiments, the coupling criteria include an additional criterion that is met when the lid of the case is closed.

[0154] 5B , the device displays (616) a pairing affordance (e.g., a button or other icon (e.g., "Connect" 522-1)) in a window (e.g., window 520-1) overlaying the first user interface that, when activated by user input, initiates pairing of the electronic device with the first peripheral device. In some embodiments, the pairing affordance also initiates pairing with the second peripheral device (and any other peripheral devices coupled to the first and / or second peripheral devices) when activated by user input.

[0155] Following a determination that the first peripheral device does not meet the binding criteria, the device displays (618) information regarding the binding between the first peripheral device and the second peripheral device (e.g., in a graphical display in window 520-2, as shown in FIG. 5F).

[0156] Optionally, pairing associated with a peripheral device, such as when a peripheral device is coupled to another peripheral device, provides a user with the ability to synchronize pairing among multiple peripheral devices in response to a single pairing action. Providing users with improved pairing capabilities improves device usability and makes the user-device interface more efficient (e.g., by helping users efficiently pair a given device with multiple associated peripheral devices in response to a single action, thereby reducing user errors when attempting to pair a given device to multiple associated peripheral devices). Without this improved pairing process, users must take the additional step of individually pairing their device with different peripheral devices to achieve the same functionality as described herein. Individually pairing a device with multiple peripheral devices can be a time-consuming process, and users are more prone to error due to the increased number of user inputs required to complete the pairing process.

[0157] In some embodiments, after the electronic device is paired with the first peripheral device, the device displays status information (e.g., model, manufacturer, icon, color, and / or battery level) about the first peripheral device and the second peripheral device in a second user interface (620). For example, as shown in FIG. 5H, the first peripheral device is earbud 502-1, the second peripheral device is earbud 502-2, and the second user interface is window 520-4. Window 520-4 displays battery level graphic 526-4 for earbud 502-1 and battery level graphic 526-5 for earbud 502-2.

[0158] Displaying status information about a peripheral device after the peripheral device has paired with the device provides the user with information about the peripheral device (e.g., one or more battery levels) when the peripheral device is in proximity to the device. Providing status information about peripheral devices improves device usability and makes the user device interface more efficient (e.g., by providing access to information about peripheral devices without the user having to physically inspect each peripheral device), thereby allowing the user to use the device and peripherals more quickly and efficiently.

[0159] In some embodiments, after pairing the electronic device with the first peripheral device, the device determines (622) whether the second peripheral device and the first peripheral device are part of a defined set of associated peripheral devices that have previously been paired with the electronic device. For example, when the electronic device has previously paired with a set of earbuds and their case in a single pairing process (e.g., as shown in FIGS. 5C-5E ), the electronic device stores a pairing profile that defines the set of earbuds and their case as a set of associated peripherals. In some embodiments, if one set of associated peripherals includes two earbuds and a case and another set of associated peripherals includes a set of speakers, the speakers and earbuds do not belong to the same set of associated peripherals because they were not paired with the electronic device in a single pairing process. In some embodiments, the first peripheral device and the second peripheral device are part of a defined set if the first peripheral device and the second peripheral device have previously been paired with the electronic device in a single pairing process. Following a determination that the second peripheral device and the first peripheral device are part of a predefined set of associated peripheral devices previously paired with the electronic device, the device displays status information (e.g., model, manufacturer, icon, color, and / or battery level) regarding the first peripheral device and the second peripheral device (e.g., as shown in FIGS. 5H and 5J-5O). In some embodiments, corresponding graphics may be displayed to indicate a peripheral heuristic (e.g., a graphic indicating a case lid is opening). Following a determination that the second peripheral device and the first peripheral device are not part of a predefined set of associated peripheral devices previously paired with the electronic device, the device displays information regarding a mismatch between the first peripheral device and the second peripheral device (e.g., as shown in FIGS. 5I and 5P).

[0160] Displaying information about whether two or more peripheral devices have previously paired with a device in a single pairing process, thus forming a set of associated peripheral devices, provides a user with the ability to quickly identify whether the peripheral devices are available for immediate use or whether they need to be paired with each other before use. Providing improved pairing capabilities for multiple peripherals for a given device improves device usability and makes the user-device interface more efficient (e.g., by helping a user quickly understand when a peripheral is available for use or, alternatively, when a peripheral needs to be paired with the device before use). Without this information, a user may mistakenly attempt to use a peripheral that is not part of the defined set (e.g., by using one or more unpaired earbuds and attempting to stream media content from the device to the earbuds) and subsequently discover that at least one of the peripherals cannot work with the device.

[0161] In some embodiments, displaying information about a mismatch between the first peripheral device and the second peripheral device comprises displaying a second pairing affordance (e.g., a button or other icon (e.g., "Connect" 522-2)) in a window (e.g., window 520-5) overlaying the first user interface that, when activated by user input, initiates pairing of the electronic device with the second peripheral device (624), as shown in FIG. 5I. In some embodiments, the second pairing affordance, when activated by user input, also initiates pairing with any other peripheral devices coupled to the first and / or second peripheral device.

[0162] In some embodiments, displaying status information (e.g., model, manufacturer, icon, color, and / or battery level) for the first peripheral device and the second peripheral device includes displaying a single composite peripheral status characteristic (e.g., composite battery level) for the first peripheral device and the second peripheral device pursuant to a determination that a difference between a first peripheral status characteristic (e.g., battery level) of the first peripheral device and a second peripheral status characteristic (e.g., battery level) of the second peripheral device is less than a predetermined threshold and the first peripheral device and the second peripheral device are the same type of peripheral device (e.g., earbuds) (626). In some embodiments, the predetermined threshold value of the numerical difference is 5%, 10%, 15%, or 20%.

[0163] In some embodiments, displaying status information (e.g., model, manufacturer, icon, color, and / or battery level) for the first peripheral device and the second peripheral device includes displaying a first peripheral device status characteristic (e.g., battery level of the first peripheral device) for the first peripheral device and displaying a second peripheral device status characteristic (e.g., battery level of the second peripheral device) for the second peripheral device (628) in accordance with a determination that a difference between a first peripheral device status characteristic (e.g., battery level) of the first peripheral device and a second peripheral device status characteristic (e.g., battery level) of the second peripheral device is greater than a predetermined threshold and the first peripheral device and the second peripheral device are the same type of peripheral device (e.g., earbuds) (e.g., as shown in FIG. 5L). In some embodiments, the predetermined threshold difference in numerical difference is 5%, 10%, 15%, or 20%.

[0164] In some embodiments, displaying the status information for the first peripheral device includes displaying a low battery graphic 630 in accordance with a determination that the battery level for the first peripheral device is below a minimum charge threshold (e.g., as shown in FIG. 5M). In some embodiments, the minimum charge threshold is 10%, 15%, or 20%.

[0165] In some embodiments, displaying the status information of the first peripheral device includes displaying a battery charging graphic (632) in accordance with determining that the first peripheral device is connected to a power source (e.g., as shown in FIGS. 5N-5O). In some embodiments, the power source is a battery or a wall outlet. In some embodiments, the first peripheral device is an earbud and the power source is integrated into the second peripheral device (e.g., a case).

[0166] In some embodiments, the electronic device is in a locked state (e.g., a lock screen, a wake screen for a locked state, etc., as shown in FIGS. 5Q-5Y) while displaying the first user interface (634). After activating a pairing affordance (e.g., the “Connect” button 522-3 in window 520-12 of FIG. 5V), the device presents (e.g., on a display and / or audibly) a request for authentication input from the user (e.g., displaying a passcode keypad 536 as shown in FIG. 5W) to pair the first peripheral device with the electronic device. The device receives the authentication input from the user. In some embodiments, the received authentication input is the same as the authentication input (e.g., a fingerprint scan, a passcode, a slide gesture, etc.) that unlocks the electronic device. In response to receiving the authentication input, the device pairs the first peripheral device with the electronic device (e.g., as shown in FIGS. 5X-5Y) and maintains the electronic device in a locked state.

[0167] Providing pairing functionality between a device and a peripheral while the device is in a locked state improves device usability and makes the user-device interface more efficient by reducing the number of user inputs required to pair the device with a peripheral, thereby reducing user errors when operating / interacting with the device.

[0168] In some embodiments, the device maintains (636) the display of the first user interface associated with the locked state of the electronic device while pairing the first peripheral with the electronic device.

[0169] In some embodiments, the device maintains (638) the display of the first user interface associated with the locked state of the electronic device after the pairing of the first peripheral device with the electronic device is completed.

[0170] In some embodiments, after pairing of the first peripheral device with the electronic device is complete, while maintaining the display of the first user interface associated with the locked state of the electronic device, the device displays (640) status information about the first peripheral device (e.g., single earbud, mismatch, battery status, etc.) (e.g., as shown in window 520-13 of FIG. 5Z).

[0171] 6A-6C are merely examples, and are not intended to represent the only order in which the operations may be performed. Those skilled in the art will recognize various ways to reorder the operations described herein.

[0172] According to some embodiments, FIG. 7 illustrates a functional block diagram of an electronic device 700 configured according to the principles of various described embodiments. The functional blocks of this device are optionally implemented by hardware, software, or a combination of hardware and software to implement the principles of various described embodiments. Those skilled in the art will understand that the functional blocks described in FIG. 7 are optionally combined or separated into sub-blocks to implement the principles of various described embodiments. Thus, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.

[0173] 7 , the electronic device 700 includes a display unit 702 configured to display a user interface, an RF circuit unit 704 for wirelessly communicating with one or more peripheral devices, one or more input device units 706 for receiving input from a user, and a processing unit 708 coupled to the display unit 702, the RF circuit unit 704, and the one or more input device units 706. The processing unit 708 includes a display enabling unit 710, a detecting unit 712, a determining unit 714, a presenting unit 716, a receiving unit 718, a pairing unit 720, and a maintaining unit 722.

[0174] The processing unit 708 is configured to enable display of a first user interface on the display unit 702 (e.g., with the display enablement unit 710). While displaying the first user interface, the processing unit 708 is configured to detect (e.g., with the detection unit 712) a pairing request to pair a first peripheral device with the electronic device. In response to detecting the pairing request, the processing unit 708 is configured to determine (e.g., with the determination unit 714) whether the first peripheral device satisfies a binding criterion requiring the first peripheral device to be coupled to a second peripheral device. In accordance with a determination that the first peripheral device satisfies the binding criterion, the processing unit 708 is configured to enable display of a pairing affordance (e.g., with the display enablement unit 710) that, when activated by a user input, initiates pairing of the electronic device and the first peripheral device. In accordance with a determination that the first peripheral device does not satisfy the coupling criteria, the processing unit 708 (e.g., using the display enabling unit 710) is configured to enable the display of information regarding the coupling between the first peripheral device and the second peripheral device.

[0175] In some embodiments, detecting a pairing request to pair the first peripheral device with the electronic device includes detecting a wireless signal transmitted from the first peripheral device and determining that the first peripheral device meets a proximity criterion based on the detected wireless signal.

[0176] In some embodiments, the coupling criteria include criteria that are met when the first peripheral device is coupled to a third peripheral device that is distinct from the second peripheral device.

[0177] In some embodiments, the first peripheral device is one or more earbuds and the second peripheral device is a case for the one or more earbuds.

[0178] In some embodiments, the coupling criteria include criteria that are met when one or more earbuds are inside the case and / or electrically coupled to the case.

[0179] In some embodiments, the processing unit 708 is configured to enable (e.g., using the display enablement unit 710) the display of status information regarding the first peripheral device and the second peripheral device in the second user interface after the electronic device is paired with the first peripheral device.

[0180] In some embodiments, the processing unit 708 is configured to, after pairing the electronic device and the first peripheral device, determine (e.g., with the determining unit 714) whether the second peripheral device and the first peripheral device are part of a predefined set of associated peripheral devices that have been previously paired with the electronic device. In accordance with a determination that the second peripheral device and the first peripheral device are part of the predefined set of associated peripheral devices that have been previously paired with the electronic device, the processing unit 708 is configured to enable (e.g., with the display enabling unit 710) a display of status information regarding the first peripheral device and the second peripheral device. In accordance with a determination that the second peripheral device and the first peripheral device are part of the predefined set of associated peripheral devices that have been previously paired with the electronic device, the processing unit 708 is configured to enable (e.g., with the display enabling unit 710) a display of information regarding a mismatch between the first peripheral device and the second peripheral device.

[0181] In some embodiments, displaying information regarding a mismatch between the first peripheral device and the second peripheral device includes displaying a second pairing affordance that, when activated by user input, initiates pairing of the electronic device with the second peripheral device.

[0182] In some embodiments, displaying status information regarding the first peripheral device and the second peripheral device includes displaying a single composite peripheral status characteristic regarding the first peripheral device and the second peripheral device in accordance with a determination that a difference between the first peripheral status characteristic of the first peripheral device and the second peripheral status characteristic of the second peripheral device is less than a predetermined threshold and the first peripheral device and the second peripheral device are the same type of peripheral device (e.g., earbuds).

[0183] In some embodiments, displaying status information regarding the first peripheral device and the second peripheral device includes displaying a first peripheral device status characteristic regarding the first peripheral device and a second peripheral device status characteristic regarding the second peripheral device in accordance with a determination that a difference between a first peripheral device status characteristic of the first peripheral device and a second peripheral device status characteristic of the second peripheral device is greater than a predetermined threshold and the first peripheral device and the second peripheral device are the same type of peripheral device (e.g., earbuds).

[0184] In some embodiments, displaying the status information for the first peripheral device includes displaying a low battery graphic pursuant to a determination that the battery level for the first peripheral device is below a minimum charge threshold.

[0185] In some embodiments, displaying the status information of the first peripheral device includes displaying a battery charge graphic in accordance with determining that the first peripheral device is connected to a power source.

[0186] In some embodiments, the electronic device is in a locked state while displaying the first user interface, and the processing unit 708 is configured to, after activation of the pairing affordance, present a request for authentication input from the user to pair the first peripheral device with the electronic device (e.g., using the presenting unit 716), receive the authentication input from the user (e.g., using the receiving unit 718), and, in response to receiving the authentication input, pair the first peripheral device with the electronic device (e.g., using the pairing unit 720), and maintain the electronic device in the locked state (e.g., using the maintaining unit 722).

[0187] In some embodiments, the processing unit 708 is configured to maintain the display of the first user interface associated with the lock state of the electronic device while pairing the first peripheral device with the electronic device (e.g., using the maintaining unit 722).

[0188] In some embodiments, the processing unit 708 is configured to maintain the display of the first user interface associated with the lock state of the electronic device after pairing the first peripheral device with the electronic device (e.g., using the maintaining unit 722).

[0189] In some embodiments, the processing unit 708 is configured to enable (e.g., with the display enablement unit 710) the display of status information regarding the first peripheral device after pairing the first peripheral device with the electronic device while maintaining the display of the first user interface associated with the locked state of the electronic device.

[0190] The operations in the information processing methods described above are optionally performed by executing one or more functional modules within an information processing device, such as a general-purpose processor (e.g., as described above with respect to Figures 1A and 3) or an application-specific chip.

[0191] 6A-6C are optionally performed by components shown in FIGS. 1A-1B or 7. For example, at least some of the functionality described in FIGS. 6A-6C is optionally performed by event sorter 170, event recognizer 180, and event handler 190. Event monitor 171 of event sorter 170 detects contacts on touch-sensitive display 112, and event dispatcher module 174 delivers event information to application 136-1. A corresponding event recognizer 180 of application 136-1 compares the event information with a corresponding event definition 186 to determine whether a first contact at a first location on the touch-sensitive surface (or rotation of the device) corresponds to a predetermined event or sub-event, such as selecting an object on a user interface or rotating the device from one orientation to another. When a corresponding predetermined event or sub-event is detected, event recognizer 180 activates event handler 190 associated with detecting the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses a corresponding GUI updater 178 to update what is displayed by the application. Similarly, it will be apparent to one skilled in the art how other processes may be implemented based on the components depicted in FIGS. 1A-1B.

[0192] The foregoing description has been set forth with reference to specific embodiments for purposes of explanation. However, the exemplary discussion above is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teachings. These embodiments were chosen and described in order to best explain the principles of the invention and its practical application, and thereby enable others skilled in the art to best utilize the invention and the various described embodiments with various modifications suited to the particular uses contemplated.

Claims

1. 1. An electronic device comprising a display, radio frequency (RF) circuitry for wirelessly communicating with one or more peripheral devices, and one or more input devices for receiving input from a user, displaying a first user interface on the display; detecting a pairing request to pair a first peripheral device with the electronic device while displaying the first user interface; In response to detecting the pairing request, determining whether the first peripheral device meets a coupling criterion requiring the first peripheral device to be coupled to a second peripheral device; According to a determination that the first peripheral device meets the coupling criteria, displaying a pairing affordance that, when activated by user input, initiates pairing between the electronic device and the first peripheral device; displaying information regarding the binding of the first peripheral device and the second peripheral device in accordance with a determination that the first peripheral device does not meet the binding criteria; A method comprising:

2. 2. The method of claim 1, wherein detecting the pairing request to pair the first peripheral device with the electronic device comprises detecting a wireless signal transmitted from the first peripheral device and determining that the first peripheral device meets a proximity criterion based on the detected wireless signal.

3. The method of claim 1 or 2, wherein the coupling criteria include criteria that are met when the first peripheral device is coupled to a third peripheral device that is distinct from the second peripheral device.

4. The method of claim 1 , wherein the first peripheral device is one or more earbuds and the second peripheral device is a case for the one or more earbuds.

5. The method of claim 4 , wherein the coupling criteria include criteria that are met when the one or more earbuds are at least one of: inside the case and electrically coupled to the case.

6. displaying status information regarding the first peripheral device and the second peripheral device on a second user interface after the electronic device is paired with the first peripheral device; 6. The method of claim 1, comprising:

7. determining, after pairing the electronic device with the first peripheral device, whether the second peripheral device and the first peripheral device are part of a defined set of associated peripheral devices that have previously been paired with the electronic device; displaying status information regarding the first peripheral device and the second peripheral device in accordance with a determination that the second peripheral device and the first peripheral device are part of a predefined set of associated peripheral devices that have previously been paired with the electronic device; and displaying information regarding a mismatch between the first peripheral device and the second peripheral device according to a determination that the second peripheral device and the first peripheral device are not part of a predefined set of associated peripheral devices previously paired with the electronic device; and 7. The method of claim 1, comprising:

8. 8. The method of claim 7, wherein displaying information regarding the mismatch between the first peripheral device and the second peripheral device includes displaying a second pairing affordance that, when activated by user input, initiates pairing of the electronic device with the second peripheral device.

9. 9. The method of claim 7 or 8, wherein displaying the status information regarding the first peripheral device and the second peripheral device comprises displaying a single composite peripheral status characteristic regarding the first peripheral device and the second peripheral device in accordance with a determination that a difference between a first peripheral status characteristic of the first peripheral device and a second peripheral status characteristic of the second peripheral device is less than a predetermined threshold and the first peripheral device and the second peripheral device are the same type of peripheral device.

10. 10. The method of claim 7, wherein displaying status information regarding the first peripheral device and the second peripheral device comprises displaying the first peripheral device status characteristic regarding the first peripheral device and the second peripheral device status characteristic regarding the second peripheral device in accordance with a determination that a difference between a first peripheral device status characteristic of the first peripheral device and a second peripheral device status characteristic of the second peripheral device is greater than a predetermined threshold and the first peripheral device and the second peripheral device are the same type of peripheral device.

11. 11. The method of claim 7, wherein displaying the status information for the first peripheral device includes displaying a low battery graphic pursuant to a determination that a battery level for the first peripheral device is below a minimum charge threshold.

12. 12. The method of claim 7, wherein displaying the status information of the first peripheral device comprises displaying a battery charge graphic in accordance with determining that the first peripheral device is connected to a power source.

13. The electronic device is in a locked state while displaying the first user interface, and the method further comprises: presenting a request for authentication input from a user after activation of the pairing affordance to pair the first peripheral device with the electronic device; receiving the authentication input from the user; In response to receiving the authentication input, pairing the first peripheral device with the electronic device; maintaining the electronic device in the locked state; 13. The method of any one of claims 1 to 12, comprising:

14. maintaining a display of the first user interface associated with the locked state of the electronic device while pairing the first peripheral device with the electronic device; 14. The method of claim 13, comprising:

15. maintaining a display of the first user interface associated with the locked state of the electronic device after completing pairing of the first peripheral device with the electronic device; 15. The method of claim 13 or 14, comprising:

16. displaying status information about the first peripheral device after the pairing between the first peripheral device and the electronic device is completed while maintaining display of the first user interface associated with the locked state of the electronic device; 16. The method of claim 15, comprising:

17. The display and Radio frequency (RF) circuitry for wireless communication with one or more peripheral devices; one or more input devices for receiving input from a user; one or more processors; Memory and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising: Displaying a first user interface on the display; Detecting a pairing request to pair a first peripheral device with the electronic device while displaying the first user interface; In response to detecting the pairing request, determining whether the first peripheral device meets a coupling criterion requiring the first peripheral device to be coupled to a second peripheral device; According to a determination that the first peripheral device meets the coupling criteria, displaying a pairing affordance that, when activated by user input, initiates pairing between the electronic device and the first peripheral device; displaying information regarding the binding between the first peripheral device and the second peripheral device in accordance with a determination that the first peripheral device does not satisfy the binding criteria. An electronic device comprising instructions for:

18. The display and Radio frequency (RF) circuitry for wireless communication with one or more peripheral devices; one or more input devices for receiving input from a user; means for displaying a first user interface on the display; means for detecting a pairing request to pair a first peripheral device with the electronic device while displaying the first user interface; a means that is enabled in response to detecting the pairing request, means for determining whether the first peripheral device satisfies a coupling criterion requiring the first peripheral device to be coupled to a second peripheral device; pursuant to a determination that the first peripheral device meets the coupling criteria, means for displaying a pairing affordance that, when activated by user input, initiates pairing between the electronic device and the first peripheral device; and means for displaying information regarding the binding of the first peripheral device and the second peripheral device in accordance with a determination that the first peripheral device does not satisfy the binding criteria; a means for An electronic device comprising:

19. 1. A computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by an electronic device comprising a display, radio frequency (RF) circuitry for wirelessly communicating with one or more peripheral devices, and one or more input devices for receiving input from a user, cause the device to: Displaying a first user interface on the display; detecting a pairing request to pair a first peripheral device with the electronic device while displaying the first user interface; In response to detecting the pairing request, determining whether the first peripheral device satisfies a coupling criterion requiring the first peripheral device to be coupled to a second peripheral device; According to a determination that the first peripheral device meets the coupling criteria, displaying a pairing affordance that, when activated by user input, initiates pairing between the electronic device and the first peripheral device; displaying information regarding the binding of the first peripheral device and the second peripheral device in accordance with a determination that the first peripheral device does not satisfy the binding criteria. A computer-readable storage medium.

20. The display and Radio frequency (RF) circuitry for wireless communication with one or more peripheral devices; one or more input devices for receiving input from a user or one or more processors; Memory and and one or more programs stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing any one of the methods of claims 1 to 16.

21. 17. A computer-readable storage medium storing one or more programs, the one or more programs including instructions that, when executed by an electronic device comprising a display, radio frequency (RF) circuitry for wirelessly communicating with one or more peripheral devices, and one or more input devices for receiving input from a user, cause the device to perform any one of the methods recited in claims 1 to 16.

22. 17. A graphical user interface on an electronic device comprising a display, radio frequency (RF) circuitry for wirelessly communicating with one or more peripheral devices, one or more input devices for receiving input from a user, a memory, and one or more processors for executing one or more programs stored in the memory, the graphical user interface comprising a user interface displayed according to any one of the methods of claims 1 to 16.

23. The display and Radio frequency (RF) circuitry for wireless communication with one or more peripheral devices; one or more input devices for receiving input from a user; and one or more processors. Memory and means for carrying out any one of the methods according to claims 1 to 16; An electronic device comprising:

24. A display unit; a radio frequency (RF) circuit unit for wireless communication with one or more peripheral devices; one or more input device units for receiving input from a user; a processing unit coupled to the display unit, the RF circuit unit, and the one or more input devices; 1. An electronic device comprising: Enabling display of a first user interface on the display unit; Detecting a pairing request to pair a first peripheral device with the electronic device while displaying the first user interface; In response to detecting the pairing request, determining whether the first peripheral device meets a coupling criterion requiring the first peripheral device to be coupled to a second peripheral device; According to a determination that the first peripheral device meets the coupling criteria, enabling display of a pairing affordance that, when activated by user input, initiates pairing between the electronic device and the first peripheral device; enable display of information regarding a binding between the first peripheral device and the second peripheral device in accordance with a determination that the first peripheral device does not satisfy the binding criteria; 1. An electronic device configured to:

25. 25. The electronic device of claim 24, wherein detecting the pairing request to pair the first peripheral device with the electronic device comprises detecting a wireless signal transmitted from the first peripheral device and determining that the first peripheral device meets a proximity criterion based on the detected wireless signal.

26. 26. The electronic device of claim 24 or 25, wherein the coupling criteria include criteria that are met when the first peripheral device is coupled to a third peripheral device that is distinct from the second peripheral device.

27. 27. The electronic device of any one of claims 24 to 26, wherein the first peripheral device is one or more earbuds and the second peripheral device is a case for the one or more earbuds.

28. 28. The electronic device of claim 27, wherein the coupling criteria include criteria that are met when the one or more earbuds are at least one of: inside the case and electrically coupled to the case.

29. The processing unit enabling display of status information regarding the first peripheral device and the second peripheral device in a second user interface after the electronic device is paired with the first peripheral device; 29. An electronic device according to any one of claims 24 to 28, configured so as to

30. The processing unit determining, after pairing the electronic device with the first peripheral device, whether the second peripheral device and the first peripheral device are part of a defined set of associated peripheral devices that have previously been paired with the electronic device; enable display of status information regarding the first peripheral device and the second peripheral device in accordance with a determination that the second peripheral device and the first peripheral device are part of a predefined set of associated peripheral devices that have been previously paired with the electronic device; enable display of information regarding a mismatch between the first peripheral device and the second peripheral device according to a determination that the second peripheral device and the first peripheral device are not part of a predefined set of associated peripheral devices previously paired with the electronic device; The electronic device according to any one of claims 24 to 29, configured as follows:

31. 31. The electronic device of claim 30, wherein displaying information regarding the mismatch between the first peripheral device and the second peripheral device includes displaying a second pairing affordance that, when activated by user input, initiates pairing of the electronic device with the second peripheral device.

32. 32. The electronic device of claim 30 or 31, wherein displaying the status information regarding the first peripheral device and the second peripheral device comprises displaying a single composite peripheral status characteristic regarding the first peripheral device and the second peripheral device in accordance with a determination that a difference between a first peripheral status characteristic of the first peripheral device and a second peripheral status characteristic of the second peripheral device is less than a predetermined threshold and the first peripheral device and the second peripheral device are the same type of peripheral device.

33. 33. The electronic device of claim 30, wherein displaying status information regarding the first peripheral device and the second peripheral device comprises displaying the first peripheral device status characteristic regarding the first peripheral device and the second peripheral device status characteristic regarding the second peripheral device in accordance with a determination that a difference between a first peripheral device status characteristic of the first peripheral device and a second peripheral device status characteristic of the second peripheral device is greater than a predetermined threshold and the first peripheral device and the second peripheral device are the same type of peripheral device.

34. 34. The electronic device of claim 30, wherein displaying the status information for the first peripheral device comprises displaying a low battery graphic pursuant to a determination that a battery level for the first peripheral device is below a minimum charge threshold.

35. 35. The electronic device of claim 30, wherein displaying the status information for the first peripheral device comprises displaying a battery charge graphic in accordance with determining that the first peripheral device is connected to a power source.

36. The electronic device is in a locked state while displaying the first user interface, and the processing unit: presenting a request for authentication input from a user to pair the first peripheral device with the electronic device after activation of the pairing affordance; receiving the authentication input from the user; In response to receiving the authentication input, Pairing the first peripheral device with the electronic device; maintaining the electronic device in the locked state; 36. An electronic device according to any one of claims 30 to 35, configured so as to

37. The processing unit maintaining a display of the first user interface associated with the locked state of the electronic device while pairing the first peripheral device with the electronic device; 37. The electronic device of claim 36, configured to:

38. The processing unit maintaining a display of the first user interface associated with the lock state of the electronic device after completing pairing of the first peripheral device with the electronic device; 38. An electronic device according to claim 36 or 37, configured so as to

39. The processing unit After the pairing of the first peripheral device and the electronic device is completed, while maintaining the display of the first user interface associated with the locked state of the electronic device, enable display of status information related to the first peripheral device.

39. The electronic device of claim 38, configured to:

Images