User interface for controlling or presenting information of multiple cellular identifiers on an electronic device

Abstract

The present disclosure relates to a user interface for controlling or presenting information of multiple cellular identifiers on an electronic device. In some embodiments, the electronic device presents a settings user interface associated with the cellular identifier. In some embodiments, the first electronic device accesses the first cellular identifier regardless of how the first electronic device is connected to the second electronic device, and the first electronic device accesses the second cellular identifier when the first electronic device is connected to the second electronic device. In some embodiments, the electronic device presents a visual indication of a cellular identifier associated with a communication function. In some embodiments, the electronic device presents a visual indication of the status of the cellular identifier activated on the electronic device. In some embodiments, the electronic device presents a prompt associated with one or more cellular identifiers that have been removed from the electronic device.

Description

[0001] This application is a divisional application of an invention patent application with an application date of August 30, 2019, application number 201980059391.5, and invention name “User interface for controlling or presenting information about multiple cellular identifiers on an electronic device”. Technical Field

[0002] The present disclosure generally relates to electronic devices that control or present information about multiple cellular identifiers of the device, and user interaction with such devices. Background Art

[0003] In recent years, the interaction between users and electronic devices has increased significantly. These devices can be devices such as computers, tablet computers, televisions, multimedia devices, mobile devices, etc.

[0004] In some cases, users want to view information about the cellular identifier (e.g., SIM card, eSIMS, etc.) of the electronic device, such as which operations are performed using the cellular identifier of the electronic device. Enhancing these interactions can improve the user's experience with the device and reduce the user interaction time, which is particularly important when the input device is battery-powered. Summary of the invention

[0005] Some embodiments described in the present disclosure relate to one or more electronic devices that present a settings user interface associated with a cellular identifier. Some embodiments described in the present disclosure relate to one or more first electronic devices that access a first cellular identifier regardless of how the one or more first electronic devices are connected to one or more second electronic devices, and a method for the one or more first electronic devices to access a second cellular identifier when the one or more first electronic devices are connected to one or more second electronic devices. Some embodiments described in the present disclosure relate to one or more electronic devices that present a visual indication of a cellular identifier associated with a communication function. Some embodiments described in the present disclosure relate to one or more electronic devices that present a visual indication of the status of a cellular identifier activated on an electronic device. Some embodiments described in the present disclosure relate to one or more electronic devices that present a prompt associated with a cellular identifier that has been removed from one or more electronic devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, in which like reference numerals designate corresponding parts throughout the several views.

[0007] Figure 1Ais a block diagram showing a portable multifunction device with a touch-sensitive display according to some embodiments.

[0008] Figure 1B is a block diagram illustrating example components for event processing according to some embodiments.

[0009] Figure 2 A portable multifunction device with a touch screen according to some embodiments is shown.

[0010] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.

[0011] Figure 4A An exemplary user interface for an application menu on a portable multifunction device according to some embodiments is shown.

[0012] Figure 4B An exemplary user interface is shown for a multifunction device having a touch-sensitive surface separate from the display according to some embodiments.

[0013] Figure 5A A personal electronic device according to some embodiments is shown.

[0014] Figure 5B is a block diagram illustrating a personal electronic device according to some embodiments.

[0015] Figure 5C-5D Example components of a personal electronic device with a touch-sensitive display and an intensity sensor are shown according to some embodiments.

[0016] Figure 5E-Figure 5H Exemplary components and user interfaces of a personal electronic device according to some embodiments are shown.

[0017] Figure 6A-6R An exemplary method for an electronic device to present a settings user interface associated with a cellular identifier according to some embodiments of the present disclosure is shown.

[0018] Figure 7A-Figure 7I is a flow chart illustrating a method of presenting a settings user interface associated with a cellular identifier according to some embodiments of the present disclosure.

[0019] Figure 8A-8U An exemplary method of a first electronic device accessing a first cellular identifier regardless of how the first electronic device is connected to a second electronic device according to some embodiments of the present disclosure, and an exemplary method of the first electronic device accessing a second cellular identifier when the first electronic device is connected to the second electronic device are shown.

[0020] Figure 9A-9His a flow chart illustrating a method of accessing a first cellular identifier on a first electronic device regardless of how the first electronic device is connected to a second electronic device and accessing a second cellular identifier on the first electronic device when the first electronic device is connected to the second electronic device according to some embodiments of the present disclosure.

[0021] Figures 10A-10MM An exemplary method for an electronic device to present a visual indication of a cellular identifier associated with a communication function according to some embodiments of the present disclosure is shown.

[0022] Figure 11A-Figure 11Q is a flow chart illustrating a method of presenting a visual indication of a cellular identifier associated with a communication function according to some embodiments of the present disclosure.

[0023] Figures 12A-12K An exemplary method is shown for an electronic device to present a visual indication of a status of a cellular identifier activated on the electronic device according to some embodiments of the present disclosure.

[0024] Figures 13A-13F is a flow chart illustrating a method of presenting a visual indication of a status of a cellular identifier activated on an electronic device according to some embodiments of the present disclosure.

[0025] Figure 14A-14JJ An exemplary method is shown in which an electronic device presents a prompt related to a previously removed cellular identifier according to some embodiments of the present disclosure.

[0026] Figure 15A-Figure 15O is a flow chart illustrating a method of presenting a prompt associated with a previously removed cellular identifier according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0027] The following description sets forth exemplary methods, parameters, etc. However, it should be appreciated that such description is not intended to limit the scope of the present disclosure, but is provided as a description of exemplary embodiments.

[0028] There is a need for electronic devices to provide efficient methods and interfaces for presenting information about a device's cellular identifier (e.g., SIM card, eSIM, etc.). Such techniques may reduce the cognitive burden on users who use such devices and / or wish to control their use of such devices. In addition, such techniques may reduce processor power and battery power that would otherwise be wasted on redundant user input.

[0029] Although the following description uses the terms "first", "second", etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another element. For example, a first touch can be named a second touch and similarly a second touch can be named a first touch without departing from the scope of the various described embodiments. Both the first touch and the second touch are touches, but they are not the same touch.

[0030] The terms used in the description of various described embodiments herein are only for the purpose of describing specific embodiments, and are not intended to be limited. As used in the description of various described embodiments and in the appended claims, the singular forms "one" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more items in the associated listed items. It will also be understood that the term "includes", "including", "comprises" and / or "comprising" when used in this specification specifies the presence of stated features, integers, steps, operations, elements and / or parts, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their grouping.

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

[0032] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple iPod from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads) are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads).

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

[0034] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a fitness 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.

[0035] Various applications executed on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or adjusted and / or varied within the respective applications. In this way, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports a variety of applications with a user interface that is intuitive and clear to the user.

[0036] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1Ais a block diagram showing a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to as or referred to as a "touch-sensitive display system." The device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0037] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four different values ​​and more typically includes hundreds of different values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted averaged) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical control / mechanical control, such as a knob or button).

[0038] As used in this specification and 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, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical characteristic of the device or 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 "press click" or "release click" to a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when there is no change in the smoothness of the touch-sensitive surface, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. Although such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user.

[0039] It should be understood that device 100 is merely one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. Figure 1A The various components shown in the EMBODIMENTS 2000 are implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application specific integrated circuits.

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

[0041] The peripheral device interface 118 can be used to couple the input peripheral devices and output peripheral devices of the device to the CPU 120 and the memory 102. The one or more processors 120 run or execute various software programs and / or instruction sets stored in the memory 102 to perform various functions of the device 100 and process data. In some embodiments, the peripheral device interface 118, the CPU 120, and the memory controller 122 are optionally implemented on a single chip such as the chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0042] RF (radio frequency) circuit 108 receives and sends RF signals, also referred to as electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memories, and the like. RF circuit 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also referred to as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communications (NFC) fields, such as through short-range communications radio components. Wireless communication optionally uses any of a variety of communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE802.11g, IEEE 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (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 Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols that have not been developed as of the filing date of this document.

[0043] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to humans. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals into audio data and transmits the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., Figure 2 The headset jack provides an interface between the audio circuit 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset having both output (e.g., a single or dual-ear headset) and input (e.g., a microphone).

[0044] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some alternative embodiments, the input controller 160 is optionally coupled to any of the following (or none of the following): a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g., Figure 2 208) optionally includes an increase / decrease button for volume control of the speaker 111 and / or the microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2 206).

[0045] A quick press of the push button optionally disengages the lock of the touch screen 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image" (i.e., U.S. Patent No. 7,657,849), which is hereby incorporated by reference in its entirety. A long press of the push button (e.g., 206) optionally turns the device 100 on or off. The functions of one or more buttons are optionally user-customizable. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0046] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen 112. The touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

[0047] The touch screen 112 has a touch-sensitive surface, sensor, or sensor group that accepts input from a user based on tactile and / or haptic contact. The touch screen 112 and display controller 156 (together with any associated modules and / or instruction sets in memory 102) detect contact on the touch screen 112 (and any movement or interruption of the contact) and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to a finger of the user.

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

[0049] The touch-sensitive display in some embodiments of the touch screen 112 is optionally similar to the multi-touch-sensitive touch pad described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman et al.), and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, the touch screen 112 displays visual output from the device 100, while the touch-sensitive touch pad does not provide visual output.

[0050] In some embodiments, the touch-sensitive display of the touch screen 112 is as described in the following patent applications: (1) U.S. patent application No. 11 / 381,313, entitled “Multipoint Touch Surface Controller,” filed on May 2, 2006; (2) U.S. patent application No. 10 / 840,862, entitled “Multipoint Touchscreen,” filed on May 6, 2004; (3) U.S. patent application No. 10 / 903,964, entitled “Gestures For Touch Sensitive Input Devices,” filed on July 30, 2004; (4) U.S. patent application No. 11 / 048,264, entitled “Gestures For Touch Sensitive Input Devices,” filed on January 31, 2005; (5) U.S. patent application No. 11 / 086,874, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed on January 18, 2005 and (9) U.S. patent application No. 11 / 367,749, filed on March 3, 2006, entitled “Multi-Functional Hand-Held Device.” All of these applications are hereby incorporated by reference in their entirety.

[0051] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of ​​the finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the actions desired by the user.

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

[0053] The device 100 also includes a power system 162 for powering the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

[0054] Device 100 optionally also includes one or more optical sensors 164 . Figure 1AAn optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. The optical sensor 164 optionally includes a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with the imaging module 143 (also called a camera module), the optical sensor 164 optionally captures a static image or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for static images and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that the user's image is optionally obtained for video conferencing while the user views other video conference participants on the touch screen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that a single optical sensor 164 is used with the touch screen display for both video conferencing and static image and / or video image acquisition.

[0055] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1A A contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite to touch screen display 112 located on the front of device 100.

[0056] Device 100 optionally also includes one or more proximity sensors 166 . Figure 1AA proximity sensor 166 is shown coupled to the peripherals interface 118. Alternatively, the proximity sensor 166 is optionally coupled to the input controller 160 in the I / O subsystem 106. The proximity sensor 166 is optionally implemented as described in the following U.S. patent applications: No. 11 / 241,839, entitled "Proximity Detector In Handheld Device"; No. 11 / 240,788, entitled "Proximity Detector In Handheld Device"; No. 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; No. 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and No. 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. In some embodiments, when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.

[0057] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1AA tactile output generator is shown coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component; and / or an electromechanical device for converting energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component for converting an electrical signal into a tactile output on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates a tactile output on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one tactile output generator is arranged in parallel or adjacent to a touch-sensitive surface (e.g., a touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 100) or laterally (e.g., backward and forward in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on the back of the device 100, opposite the touch screen display 112 located on the front of the device 100.

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

[0059] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and an application (or instruction set) 136. In addition, in some embodiments, memory 102 ( Figure 1A ) or 370( Figure 3 ) storage device / global internal state 157, such as Figure 1A and Figure 3 . The device / global internal state 157 includes one or more of the following: an active application state, which indicates which applications (if any) are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; a sensor state, including information obtained from the device's various sensors and input control devices 116; and position information about the device's position and / or posture.

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

[0061] The communication module 128 facilitates communication with other devices through one or more external ports 124, and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.

[0062] The contact / motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger press event), determining the contact strength (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of the contact point being represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single finger contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on the touch pad.

[0063] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touchscreen display hardware, the mouse "click" threshold of a touchpad or touchscreen can be set to any one of a large range of predefined thresholds. In addition, in some specific implementations, a software setting is provided to the user of the device for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).

[0064] The contact / motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event, and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event.

[0065] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual attributes) 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, videos, animations, etc.

[0066] In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes for specifying the graphics to be displayed from an application program, etc., and also receives coordinate data and other graphic attribute data together if necessary, and then generates screen image data to be output to the display controller 156.

[0067] Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator 167 to produce tactile output at one or more locations on device 100 in response to user interaction with device 100 .

[0068] Text input module 134, which is optionally a component of graphics module 132, 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).

[0069] 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 dialing; to the camera 143 as picture / video metadata; and to applications that provide location-based services, such as the Weather widget, the Local Pages widget, and the Maps / Navigation widget).

[0070] The application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:

[0071] Contacts module 137 (sometimes called address book or contact list);

[0072] Telephone module 138;

[0073] Video conferencing module 139;

[0074] Email client module 140;

[0075] Instant messaging (IM) module 141;

[0076] Fitness support module 142;

[0077] A camera module 143 for still images and / or video images;

[0078] Image management module 144;

[0079] Video player module;

[0080] Music player module;

[0081] Browser module 147;

[0082] Calendar module 148;

[0083] A widget module 149, which optionally includes one or more of the following: a weather widget 149-1, a stock widget 149-2, a calculator widget 149-3, an alarm widget 149-4, a dictionary widget 149-5, and other widgets acquired by the user and a widget 149-6 created by the user;

[0084] A widget creator module 150 for forming a user-created widget 149-6;

[0085] Search module 151;

[0086] Video and music player module 152, which merges the video player module and the music player module;

[0087] Notepad module 153;

[0088] Map module 154; and / or

[0089] Online video module 155.

[0090] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

[0091] In conjunction with the touch screen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (e.g., stored in the application internal state 192 of the contact module 137 in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140, or IM 141; and the like.

[0092] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, phone module 138 is optionally used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in contact module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0093] In combination with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact / motion module 130, the graphics module 132, the text input module 134, the contact module 137 and the telephone module 138, the video conferencing module 139 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.

[0094] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 144, email client module 140 makes it very easy to create and send emails with still images or video images captured by camera module 143.

[0095] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0096] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154 and the music player module, the fitness support module 142 includes executable instructions for creating a fitness (e.g., with time, distance and / or calorie burn goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.

[0097] In conjunction with the touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132 and image management module 144, the camera module 143 includes executable instructions for the following operations: capturing still images or videos (including video streams) and storing them in the memory 102, modifying the characteristics of the still images or videos, or deleting the still images or videos from the memory 102.

[0098] In conjunction with touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions for arranging, modifying (e.g., editing), or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

[0099] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions, including searching, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0100] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the email client module 140 and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying and storing calendars and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

[0101] In conjunction with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, and the browser module 147, the desktop widget module 149 is a mini-application that is optionally downloaded and used by the user (e.g., the weather desktop widget 149-1, the stock desktop widget 149-2, the calculator desktop widget 149-3, the alarm desktop widget 149-4, and the dictionary desktop widget 149-5) or a mini-application created by the user (e.g., the user-created desktop widget 149-6). In some embodiments, the desktop widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the desktop widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., the Yahoo! desktop widget).

[0102] In combination with the RF circuit 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134 and browser module 147, the desktop widget creator module 150 is optionally used by a user to create a desktop widget (e.g., converting a user-specified portion of a web page into a desktop widget).

[0103] In combination with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the search module 151 includes executable instructions for searching the memory 102 for text, music, sound, images, videos and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

[0104] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch screen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

[0105] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the notepad module 153 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.

[0106] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the GPS module 135 and the browser module 147, the map module 154 is optionally used to receive, display, modify and store maps and data associated with the maps (e.g., driving directions, data relating to stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

[0107] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions for performing the following operations: allowing a user to access, browse, receive (e.g., by streaming and / or downloading), playback (e.g., on the touch screen or on an external display connected via external port 124), send an email with a link to a specific online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a specific online video. Additional descriptions of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.

[0108] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as independent software programs, processes, or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. For example, a video player module is optionally combined with a music player module into a single module (e.g., Figure 1A In some embodiments, the memory 102 optionally stores a subset of the above modules and data structures. In addition, the memory 102 optionally stores additional modules and data structures not described above.

[0109] In some embodiments, the device 100 is a device where the operation of a predefined set of functions on the device is performed exclusively through a touch screen and / or a touch pad. By using a touch screen and / or a touch pad as the primary input control device for operating the device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on the device 100 is optionally reduced.

[0110] A predefined set of functions that are performed exclusively through the touch screen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main menu, a home menu, or a root menu from any user interface displayed on the 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.

[0111] Figure 1B 1 is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 370( Figure 3 ) includes an event classifier 170 (e.g., in the operating system 126) and a corresponding application 136-1 (e.g., any one of the aforementioned applications 137 to 151, 155, 380 to 390).

[0112] Event classifier 170 receives event information and determines the application 136-1 and the application view 191 of application 136-1 to which the event information is to be delivered. Event classifier 170 includes event monitor 171 and event distributor module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates one or more current application views displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device / global internal state 157 is used by event classifier 170 to determine which application(s) is currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information is to be delivered.

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

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

[0115] In some embodiments, event monitor 171 sends requests to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 transmits event information. In other embodiments, peripheral device interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or receiving an input for more than a predetermined duration).

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

[0117] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides software procedures for determining where within one or more views a sub-event has occurred. A view consists of controls and other elements that a user can see on the display.

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

[0119] Hit view determination module 172 receives information related to sub-events of touch-based gestures. 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 where the sub-events should be processed. In most cases, the hit view is the lowest level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

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

[0121] Event distributor module 174 distributes event information to event recognizers (e.g., event recognizers 180). In embodiments including active event recognizer determination module 173, event distributor module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event distributor module 174 stores the event information in an event queue, which is retrieved by corresponding event receivers 182.

[0122] In some embodiments, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In yet another embodiment, event classifier 170 is a standalone module or is part of another module stored in memory 102, such as contact / motion module 130.

[0123] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring in a corresponding view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, the corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more event recognizers in event recognizers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit (not shown) or application 136-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178, and / or event data 179 received from event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views in application view 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.

[0124] The corresponding event identifier 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies the event based on the event information. The event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event identifier 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (which optionally include sub-event delivery instructions).

[0125] Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of the touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another orientation (for example, from a longitudinal orientation to a transverse orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

[0126] Event comparator 184 compares event information with predefined event or sub-event definitions, and determines an event or sub-event based on the comparison, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 includes the definition of an event (e.g., a predefined sequence of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in event (187) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1 (187-1) is a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on a displayed object, a first lift-off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on a displayed object, and a second lift-off (touch end) of a predetermined duration. In another example, the definition of event 2 (187-2) is a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on a displayed object, movement of the touch on the touch-sensitive display 112, and lifting of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0127] In some embodiments, event definition 187 includes definitions of events for corresponding user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view displaying three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with a sub-event and the object that triggered the hit test.

[0128] In some embodiments, the definition of the corresponding event (187) also includes a delay action that delays the delivery of the event information until it has been determined that the sub-event sequence does or does not correspond to the event type of the event identifier.

[0129] When a corresponding event recognizer 180 determines that a sequence of sub-events does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

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

[0131] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with the tag obtains the tag and performs a predefined process.

[0132] In some embodiments, the event delivery instructions 188 include a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers the event information to an event handler associated with a sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or with an actively participating view receives the event information and performs a predetermined process.

[0133] In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contact module 137 or stores video files used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates new user interface objects or updates the position 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 a touch-sensitive display.

[0134] In some embodiments, event handler 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0135] It should be understood that the above discussion of event processing for user touches on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 100, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holddowns; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events defining an event to be recognized.

[0136] Figure 2A portable multifunction device 100 with a touch screen 112 according to some embodiments is shown. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more of these graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics will occur when the user interrupts contact with the one or more graphics. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or rolling of fingers that have been in contact with the device 100 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

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

[0138] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and for locking the device, one or more volume adjustment buttons 208, a user identity module (SIM) card slot 210, an earphone jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and keeping the button in a pressed state for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval passes; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input for activating or deactivating certain functions through a microphone 113. The device 100 also optionally includes one or more contact strength sensors 165 for detecting the strength of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for a user of the device 100.

[0139] Figure 3300 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 does not have to be portable. In some embodiments, the device 300 is a laptop, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). The device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuits (sometimes referred to as a chipset) that interconnect system components and control communications between system components. The device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or a mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above reference Figure 1A The tactile output generator 167 described above), sensor 359 (e.g., optical sensor, acceleration sensor, proximity sensor, touch sensor and / or contact intensity sensor (similar to the above reference Figure 1A The memory 370 may include a high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and may optionally include a 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. The memory 370 may optionally include one or more storage devices located away from the CPU 310. In some embodiments, the memory 370 stores data related to the portable multifunction device 100 ( Figure 1A ) or a subset thereof. In addition, 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 a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.

[0140] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the previously mentioned memory device. Each module in the above-mentioned modules corresponds to the instruction set for performing the above-mentioned functions. The above-mentioned modules or programs (e.g., instruction sets) do not have to be implemented as independent software programs, processes or modules, and therefore the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores the subset of the above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0141] Attention is now turned to an embodiment of a user interface that is optionally implemented on, for example, portable multifunction device 100.

[0142] Figure 4A An exemplary user interface of an application menu on portable multifunction device 100 according to some embodiments is shown. 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:

[0143] Signal strength indicators 402 for wireless communications such as cellular signals and Wi-Fi signals;

[0144] Time 404;

[0145] Bluetooth indicator 405;

[0146] Battery status indicator 406;

[0147] A tray 408 with icons for commonly used applications, such as:

[0148] o An icon 416 of the phone module 138 labeled "Phone," which optionally includes an indicator 414 of the number of missed calls or voicemails;

[0149] o an icon 418 of the email client module 140 labeled “Mail”, the icon 418 optionally including an indicator 410 of the number of unread emails;

[0150] o An icon 420 labeled "Browser" of the browser module 147; and

[0151] o An icon 422 labeled “iPod” for a video and music player module 152 (also referred to as an iPod (trademark of Apple Inc.) module 152); and

[0152] Icons of other applications, such as:

[0153] o Icon 424 labeled "Message" of IM module 141;

[0154] o An icon 426 labeled “Calendar” of the calendar module 148;

[0155] o Icon 428 labeled “Photos” of the image management module 144;

[0156] o An icon 430 labeled “Camera” of the camera module 143;

[0157] ○ Icon 432 labeled “Online Video” of the online video module 155;

[0158] ○ Icon 434 labeled “Stock Market” of the Stock Market Desktop Applet 149-2;

[0159] o An icon 436 labeled “Map” of the map module 154;

[0160] ○ Icon 438 labeled “Weather” of the Weather widget 149-1;

[0161] ○ Icon 440 labeled as “Clock” of the alarm clock desktop applet 149-4;

[0162] o An icon 442 labeled “Fitness Support” of the fitness support module 142;

[0163] o An icon 444 labeled "Notepad" of the Notepad module 153; and

[0164] o An icon 446 labeled “Settings” for a settings application or module that provides access to settings for the device 100 and its various applications 136 .

[0165] It should be noted that Figure 4A The icon labels shown in are exemplary only. For example, icon 422 of 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 of a corresponding application icon includes the name of the application corresponding to the corresponding application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

[0166] Figure 4B A touch-sensitive surface 451 (eg, touch screen display 112) is shown having a touch-sensitive surface 451 (eg, Figure 3 tablet computer or touch pad 355) device (e.g., Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating tactile output for a user of device 300.

[0167] Although some of the examples below are given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the principal axis (for example, Figure 4B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 4B 460 corresponds to 468 and 462 corresponds to 470) in contact with touch-sensitive surface 451 (e.g., Figure 4B Thus, when the touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g., Figure 4B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is separated, the device is used to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0168] In addition, although the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap gestures, finger swipe gestures), it should be understood that in some embodiments, one or more of these finger inputs are replaced by 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 contact), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detecting contact, followed by ceasing to detect contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or a mouse and finger contact are optionally used simultaneously.

[0169] Figure 5AAn exemplary personal electronic device 500 is shown. Device 500 includes a body 502. In some embodiments, device 500 may include a body 502 relative to devices 100 and 300 (e.g., Figures 1A to 4B ) some or all of the features described in the foregoing. In some embodiments, device 500 has a touch-sensitive display screen 504, referred to hereinafter as touch screen 504. As an alternative or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more strength sensors for detecting the intensity of contact (e.g., touch) applied. One or more strength sensors of touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of touch. The user interface of device 500 can respond to touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 500.

[0170] Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related patent applications: International Patent Application Serial No. PCT / US2013 / 040061, filed on May 8, 2013, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” published as WIPO Patent Publication No. WO / 2013 / 169849; and International Patent Application Serial No. PCT / US2013 / 069483, filed on November 11, 2013, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” published as WIPO Patent Publication No. WO / 2014 / 105276, each of which is hereby incorporated by reference in its entirety.

[0171] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 500.

[0172] Figure 5B An exemplary personal electronic device 500 is shown. In some embodiments, the device 500 may include a reference Figure 1A , Figure 1B and Figure 3 Some or all of the components described. Device 500 has a bus 512 that operatively couples an I / O portion 514 to one or more computer processors 516 and a memory 518. I / O portion 514 may be connected to a display 504, which may have a touch-sensitive component 522 and optionally a strength sensor 524 (e.g., a contact strength sensor). In addition, I / O portion 514 may be connected to a communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular and / or other wireless communication technologies. Device 500 may include input mechanisms 506 and / or 508. For example, input mechanism 506 is optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, input mechanism 508 is optionally a button.

[0173] In some examples, input mechanism 508 is optionally a microphone. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, orientation sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and / or combinations thereof, all of which are operably connected to I / O portion 514.

[0174] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions, which when executed by one or more computer processors 516 may, for example, cause the computer processors to perform the techniques described below, including processes 700, 900, 1100, and 1300 (Figures 7, 9, 11, and 13). A computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with an instruction execution system, apparatus, and device. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memory such as flash memory, solid-state drives, and the like. The personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other components or additional components in a variety of configurations.

[0175] As used herein, the term "indicative representation" refers to an optional feature of the apparatus 100, 300, and / or 500 ( Figure 1A , Figure 3 and FIG. 5A to FIG. 5B ) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

[0176] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface with which a user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the particular user interface element is adjusted according to the detected input. In the case that a touch-screen display (e.g., Figure 1A A touch-sensitive display system 112 or Figure 4AIn some implementations of the touch screen 112 in FIG. 1 , a contact detected on the touch screen acts as a “focus selector” such that when an input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus moves from one area of ​​the user interface to another area of ​​the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when 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, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

[0177] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted off, before or after contact starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the value at the top 10% of the intensity of the contact, the half-maximum value of the intensity of the contact, the 90% maximum value of the intensity of the contact, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation) rather than to determine whether to perform the first operation or the second operation.

[0178] Figure 5C Detecting multiple contacts 552A-552E on touch-sensitive display screen 504 using multiple intensity sensors 524A-524D is shown. Figure 5C Also included is an intensity graph that shows the current intensity measurements of intensity sensors 524A-524D relative to intensity units. In this example, the intensity measurements of intensity sensors 524A and 524D are each 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are each 7 intensity units. In some implementations, the cumulative intensity is the sum of the intensity measurements of multiple intensity sensors 524A-524D, which is 32 intensity units in this example. In some embodiments, each contact is assigned a corresponding intensity, which is a portion of the cumulative intensity. Figure 5DThe cumulative strength assigned to contacts 552A-552E based on their distance from the center of force 554 is shown. In this example, each of contacts 552A, 552B, and 552E is assigned a contact strength of 8 strength units of the cumulative strength, and each of contacts 552C and 552D is assigned a contact strength of 4 strength units of the cumulative strength. More generally, in some embodiments, each contact j is assigned a corresponding strength Ij, which is a portion of the cumulative strength A, according to a predefined mathematical function Ij=A·(Dj / ΣDi), where Dj is the distance of the corresponding contact j from the center of force, and ΣDi is the sum of the distances of all corresponding contacts (e.g., i=1 to the last) from the center of force. The reference may be performed using an electronic device similar to or equivalent to device 100, 300, or 500. Figure 5C-5D In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, the intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity map is not part of the displayed user interface, but is included in the Figure 5C-5D To assist the readers.

[0179] In some embodiments, a portion of a gesture is identified for determining characteristic strength. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting position and reaches an end position, where the contact strength increases. In this example, the characteristic strength of the contact at the end position is optionally based only on a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end position). In some embodiments, a smoothing algorithm is optionally applied to the strength of the swipe contact before determining the characteristic strength of the contact. For example, a smoothing algorithm optionally includes one or more of the following: an unweighted sliding average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and / or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow peaks or depressions in the strength of the swipe contact to achieve the purpose of determining the characteristic strength.

[0180] The intensity of contact on the touch-sensitive surface is optionally characterized relative to one or more intensity thresholds such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and / or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform an operation typically associated with clicking a button of a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform an operation different from the operation typically associated with clicking a button of a physical mouse or touchpad. In some embodiments, when a contact having a characteristic intensity lower than the light press intensity threshold (e.g., and higher than a nominal contact detection intensity threshold, contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector according to the movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally speaking, unless otherwise stated, these intensity thresholds are consistent between different groups of user interface illustrations.

[0181] An increase in contact feature intensity from an intensity below a light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. An increase in contact feature intensity from an intensity below a deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. An increase in contact feature intensity from an intensity below a contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting contact on the touch surface. A decrease in contact feature intensity from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting contact lifted from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

[0182] In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a corresponding press input or in response to detecting a corresponding press input performed using a corresponding contact (or multiple contacts), wherein the corresponding press input is detected at least in part based on detecting that the strength of the contact (or multiple contacts) increases to above a press input strength threshold. In some embodiments, the corresponding operation is performed in response to detecting that the strength of the corresponding contact increases to above the press input strength threshold (e.g., a "down stroke" of the corresponding press input). In some embodiments, the press input includes an increase in the strength of the corresponding contact to above the press input strength threshold and the strength of the contact subsequently decreases to below the press input strength threshold, and the corresponding operation is performed in response to detecting that the strength of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "up stroke" of the corresponding press input).

[0183] Figure 5E-Figure 5HDetection of a gesture is shown, the gesture comprising contact 562 with an intensity from below Figure 5E The light press intensity threshold in L ”) increases to a strength higher than Figure 5H The deep compression intensity threshold in D ”). On the displayed user interface 570 including application icons 572A-572D displayed in the predefined area 574, when the cursor 576 is displayed above the application icon 572B corresponding to application 2, a gesture performed using contact 562 is detected on the touch-sensitive surface 560. In some embodiments, the gesture is detected on the touch-sensitive display 504. The intensity sensor detects the intensity of the contact on the touch-sensitive surface 560. The device determines whether the intensity of the contact 562 is within the deep press intensity threshold (for example, “IT D ”) reaches a peak above. Contact 562 is maintained on touch-sensitive surface 560. In response to detecting the gesture, and according to the intensity increasing to a deep press intensity threshold (e.g., “IT D ”) above contact 562, displays scaled representations 578A-578C (e.g., thumbnails) of documents recently opened for application 2, such as Figure 5F-5H In some embodiments, the intensity is a characteristic intensity of the contact compared to one or more intensity thresholds. It should be noted that the intensity map for contact 562 is not part of the displayed user interface, but is included in the Figure 5E-Figure 5H To assist the readers.

[0184] In some embodiments, the display of representations 578A-578C includes animation. For example, representation 578A is initially displayed near application icon 572B, such as Fig. 5F As the animation progresses, representation 578A moves upward and representation 578B is displayed near application icon 572B, as shown. Figure 5G Then, representation 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed near application icon 572B, as shown in FIG. Figure 5H 578A-578C form an array above icon 572B. In some embodiments, the animation progresses according to the intensity of contact 562, such as Figure 5F-5G , where representations 578A-578C appear and increase as the strength of contact 562 approaches a deep press strength threshold (eg, “IT D ”) increases and moves upward. In some embodiments, the intensity according to which the animation progresses is the characteristic intensity of the contact. The reference may be performed using an electronic device similar to or equivalent to device 100, 300, or 500. Figure 5E-Figure 5H The operation described.

[0185] In some embodiments, the device employs intensity hysteresis to avoid unexpected inputs sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold that has a predefined relationship to a press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, a press input includes an increase in the intensity of the corresponding contact to above the press input intensity threshold and a subsequent decrease in the intensity of the contact to below the hysteresis intensity threshold corresponding to the press input intensity threshold, and a corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the hysteresis intensity threshold (e.g., an "upward stroke" of the corresponding press input). Similarly, in some embodiments, a press input is detected only when the device detects that the contact intensity increases from an intensity equal to or below the hysteresis intensity threshold to an intensity equal to or above the press input intensity threshold and, optionally, that the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., an increase in contact intensity or a decrease in contact intensity, depending on the circumstances).

[0186] For ease of explanation, optionally, a description of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture including a press input is triggered in response to detecting any of the following: contact intensity increasing to above the press input intensity threshold, contact intensity increasing from an intensity below a hysteresis intensity threshold to an intensity above the press input intensity threshold, contact intensity decreasing to below the press input intensity threshold, and / or contact intensity decreasing to below a hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operation is optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

[0187] As used herein, an "installed application" refers to a software application that has been downloaded to an electronic device (e.g., device 100, 300, and / or 500) and is ready to be launched (e.g., become open) on the device. In some embodiments, a downloaded application becomes an installed application using an installer that extracts program portions from a downloaded software package and integrates the extracted portions with the operating system of a computer system.

[0188] As used herein, the term "open application" or "executing application" refers to a software application that has retained state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or executing application is optionally any of the following types of applications:

[0189] the active application currently displayed on the display of the device on which the application is being used;

[0190] Background applications (or background processes), which are not currently displayed but one or more processes of the application are being processed by one or more processors; and

[0191] - A suspended or dormant application that is not running but has state information stored in memory (volatile and non-volatile, respectively) and can be used to resume execution of the application.

[0192] As used herein, the term "closed application" refers to a software application that does not have retained state information (e.g., the state information of a closed application is not stored in the memory of the device). Therefore, closing an application includes stopping and / or removing the application process of the application and removing the state information of the application from the memory of the device. Generally speaking, when in a first application, opening a second application does not close the first application. When the second application is displayed and the first application stops being displayed, the first application becomes a background application.

[0193] Attention is now turned to embodiments of a user interface ("UI") and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

[0194] User interface and associated processes

[0195] Cellular Identifier Settings UI

[0196] Users interact with electronic devices in a variety of different ways, including viewing information about the use of electronic devices and / or electronic devices. In some embodiments, the electronic device displays a setting user interface for configuring one or more cellular identifiers (e.g., SIM cards or eSIMs) that can be used by the electronic device, thereby allowing the user to view and edit one or more settings of the one or more cellular identifiers that can be used by the electronic device. The embodiments described below provide a method for an electronic device to present a setting user interface for viewing and changing how the electronic device utilizes one or more cellular identifiers that can be used by the electronic device. Enhanced interaction with the device reduces the amount of time required for the user to perform an operation, thereby reducing the power consumption of the device and extending the battery life of battery-powered devices. It should be understood that people use devices. When a person uses a device, this person is optionally referred to as a user of the device.

[0197] Figure 6A-6R An exemplary method of presenting a setting user interface associated with a cellular identifier by an electronic device according to some embodiments of the present disclosure is shown. The embodiments in these figures are used to illustrate the process described below, including reference Figure 7A-Figure 7I.The process described.

[0198] Fig. 6A An exemplary device 500 having a touch screen 504 is shown, such as that shown in FIG. Figure 5A-5H The touch screen 504 optionally displays one or more user interfaces including various contents. Fig. 6A In the example shown, the touch screen 504 displays an indication 602 of a process for setting up a cellular plan on the electronic device. In some embodiments, the indication 602 is presented in response to a cellular identifier (e.g., SIM, eSIM, etc.) being introduced to the electronic device 500 or in response to a user's selection of an affordance for setting up a new cellular identifier (e.g., in a setup user interface). In some embodiments, the device 500 displays the indication 602 as part of an initial setup process for the device 500. In some embodiments, the device 500 displays the indication 602 in response to the introduction of a second cellular identifier to the device 500 when the device 500 is already configured to use a first cellular identifier. Fig. 6A Touch screen 504 in the example optionally displays a "continue" affordance 604 that is selectable to initiate the process for configuring a new cellular identifier, and a "not now" affordance 606 that is selectable to abort initiating the process for configuring a new cellular identifier. Fig. 6A As shown, the user optionally (eg, using contact 603 ) selects “Continue” indication 604 .

[0199] In some embodiments, in response to selection of the “Continue” indication 604, the electronic device presents a user interface for adding a cellular identifier to the electronic device 500 (or configuring the added cellular identifier) ​​based on the captured image. Figure 6B As shown, touch screen 504 presents instructions 608 to the user, the instructions (e.g., "Scan QR code to add eSIM") for capturing an image (e.g., of a QR code) associated with a cellular identifier. Electronic device 504 presents viewfinder 610 and image capture enable representation 612 simultaneously with instruction 608 for capturing an image. In some embodiments, electronic device 500 is capable of accessing or adding a cellular identifier, such as an eSIM, based on the captured image of the QR code associated with the eSIM. If electronic device 500 successfully identifies the eSIM based on the captured QR code, the electronic device optionally presents a user interface for changing one or more settings associated with the cellular identifier accessible to the electronic device, such as described below with reference to FIG. Fig.6D The user interface described.

[0200] If the electronic device 500 does not successfully identify the eSIM based on the captured image (e.g., the image is blurry, the QR code is invalid, etc.), or if the eSIM successfully identified using the captured image requires a password or other authentication credentials to be added to the device 500, then the electronic device 500 optionally presents a different user interface for adding a SIM to the electronic device, such as Figure 6C The user interface shown in Figure 1 is as follows. Figure 6C As shown, the electronic device 500 presents a user interface for authenticating the added cellular identifier using a password. Figure 6C The user interface in includes an indication of an associated telephone number 614 of the cellular identifier, a text input field 616, and a dial pad 618 (or keyboard) at which a user can enter a password (or other authentication credentials) associated with the cellular identifier to authenticate access to the cellular identifier on the electronic device 500. In response to a correct password, the electronic device 500 is optionally able to use the cellular identifier to perform functions; in response to an incorrect password, the electronic device 500 is optionally unable to use the cellular identifier to perform functions, and adding the cellular identifier to the device 500 is optionally unsuccessful. In some embodiments, before entering the password, the user can enter identification information of the cellular identifier, such as a telephone number associated with the cellular identifier.

[0201] Once the electronic device 500 successfully identifies a cellular identifier and / or is granted access to a cellular identifier, a settings user interface for changing settings associated with the cellular identifier accessible to the electronic device can optionally be presented. Fig.6D 4 shows a cellular identifier setting user interface for setting a tag associated with each cellular identifier of the electronic device 500. Fig.6D As shown, electronic device 500 presents an affordance 620 for changing a label of a first cellular identifier identifying the electronic device, and an affordance 620 for changing a second cellular identifier (eg, Figure 6A-6C622 of a label identifying a cellular identifier added to device 500 (e.g., a second cellular identifier added to device 500). The newly added cellular identifier is optionally labeled as "secondary" by default, and the existing cellular identifier is optionally labeled as "primary" by default, but in some embodiments, when a new cellular identifier is added to electronic device 500, the newly added cellular identifier is labeled as "primary" by default, and the existing cellular identifier is labeled as "secondary" by default. The enabling representation 620 for changing the label identifying a first cellular identifier includes an indication of a telephone number associated with the first cellular identifier and a label of the first cellular identifier (e.g., "primary"). The enabling representation 622 for changing the label identifying a second cellular identifier includes an indication of a telephone number associated with the second cellular identifier and a label of the second cellular identifier (e.g., "secondary"). As Fig.6D As shown, the user selects (e.g., using contact 603) second enable indication 622 to edit the label of the second cellular identifier.

[0202] In response to the user's selection of affordance 622, electronic device 500 presents a user interface for editing a tag associated with the second cellular identifier, such as Fig. 6E The user interface includes an indication 624 of a second cellular identifier, a plurality of selectable affordances for setting the label to one of a plurality of predefined cellular identifier labels (e.g., “primary” 626a, “secondary” 626b, “data” 626c, and “travel” 626d), and an affordance 628 that the user can select for inputting a custom label for the cellular identifier. Fig. 6E Each affordance 626a-d includes the name of the label of the cellular identifier (e.g., "primary," "secondary," "data," and "travel") and a representative indication of the cellular identifier. The indication of the cellular identifier is optionally presented in the user interface of the electronic device 500 in association with the function of the cellular identifier, as will be referred to in the reference Figures 10A-11Q The indication of the cellular identifier is optionally based on the text of the cellular identifier label, such as including the first letter of the cellular identifier label, such as using an indication with a "D" for the "Data" label 626c. Fig. 6E As shown, a user selects (eg, using contact 603) affordance 628 for creating a custom tag for a cellular identifier.

[0203] In response to Fig. 6E In response to the user's selection, the electronic device 500 presents a user interface for creating a custom tag for the cellular identifier, such as Fig. 6F The user interface includes an indication 630 of a cellular identifier, a text input field 632, and a soft keyboard 634. Figure 6GAs shown, the user enters the tag “Personal,” such as via one or more contacts 603 at a soft keyboard 634 .

[0204] Figure 6H Shown in Fig. 6F The user interface presented by electronic device 500 after the user creates a custom “personal” tag for the second cellular identifier includes affordance 634 associated with the custom cellular identifier tag “personal”. Figure 6H As shown, the indicator associated with the label "personal" and the indicator associated with the label "primary" include the first two letters of these labels, rather than only the initial letters of the labels, so that the user can distinguish between these labels with the same initial letters. In some embodiments, the device 500 uses enough letters of the conflicting labels until the indicators of the conflicting labels are not the same. The remaining labels "auxiliary", "data" and "travel" continue to be indicated with indicators including the initial letters of these labels, as long as labels with the same initial letters are not used. In some embodiments, when two displayed labels have the same first three letters, the indicator is updated to include the first letter of the label, followed by a number (for example, the indicators for "primary" and "private" are P1 and P2, respectively). In some embodiments, multi-word labels are possible, and the indicator is updated to include the initial letters of the words of the label (for example, the indicator for "data roaming" is DR).

[0205] After configuring the tag for the second cellular identifier as "personal", as Figure 6H As shown, the user optionally navigates back to the settings user interface for updating the tags associated with each cellular identifier, as shown in FIG. Fig.6I As shown. Fig.6I As shown, affordance 622 associated with the second cellular identifier is updated to indicate that the second cellular identifier is marked as “personal”.

[0206] In response to detecting Fig.6I , the electronic device 500 optionally presents a setting user interface for setting the functions to be performed using each cellular identifier associated with the device. Figure 6J As shown, electronic device 500 presents a user interface for setting functions to be performed using the "personal" cellular identifier. The user is able to select among affordances such as "Second number for phone / SMS" 636a, "Primary number for phone / SMS" 636b, and "Data only" 636c. As shown, the user (e.g., using contact 603) selects "Primary number for phone / SMS" 636b, which makes the "personal" cellular identifier the primary cellular identifier for phone and messaging functions on device 500.

[0207] In some embodiments, the "primary number for phone / SMS" is the cellular identifier that the electronic device 500 uses by default for phone calls and SMS messaging, the "secondary number for phone / SMS" is configured to perform phone and SMS operations in non-default situations (e.g., the user requests to use the secondary cellular identifier, the primary cellular identifier is not available, the user requests to initiate communication with a contact associated with the secondary cellular identifier), and the "data-only" cellular identifier is configured to perform only cellular data operations and is optionally the default cellular identifier for performing data operations on the electronic device 500. Figure 6J As shown, "Second number for phone / SMS" is listed as the first option because the "Personal" SIM is currently set as the "Second number for phone / SMS" because the existing cellular identifier is the "Primary number for phone / SMS" by default. In some embodiments, other default configurations and list orders are possible. In some embodiments, the electronic device configures one cellular identifier as the primary number for phone / SMS and another cellular identifier as the secondary number for phone / SMS. In some embodiments, rather than configuring the cellular identifiers as secondary numbers for phone / SMS, the electronic device configures one of the cellular identifiers for data only.

[0208] After setting the functions to be performed using the "personal" cellular identifier on device 500, device 500 displays a user interface presenting function settings for multiple cellular identifiers available for use by electronic device 500, such as Figure 6K As shown in Figure 6KAs shown, the user interface includes an indication 638a of the functionality associated with a “personal” cellular identifier. The indication 638a includes text identifying a label for the cellular identifier (e.g., “personal”), a visual indication of the cellular identifier (e.g., an icon with the letters “Pe”), an indication of a telephone number associated with the cellular identifier (e.g., “555-987-6543”), and text indicating the functionality settings of the cellular identifier (e.g., “default number for phone calls and SMS”). In some embodiments, the electronic device 500 is configured to communicate using a data-based enhanced messaging service that is optionally associated with a user account of the electronic device 500. The electronic device 500 optionally uses the cellular identifier designated as the “default number for phone calls and SMS” to send messages using the data-based enhanced messaging service, even when sending messages to contacts associated with different cellular identifiers using the data-based enhanced messaging service. The user interface also includes an indication 638b of the functionality associated with the “primary” cellular identifier. Indication 638b includes text identifying the label of the cellular identifier (e.g., "Primary"), a visual indication of the cellular identifier (e.g., an icon with the letters "Pr"), an indication of the telephone number associated with the cellular identifier (e.g., "555-123-4567"), and text indicating the functional settings of the cellular identifier (e.g., "Secondary number for phone calls and SMS"). As described above, because both "Personal" and "Primary" begin with the letters "P", the indications of these cellular identifiers include the first two letters of the labels of these cellular identifiers (e.g., "Pe" and "Pr").

[0209] As previously described, indications of the cellular identifiers of device 500 are optionally used in other user interfaces presented by electronic device 500 to indicate one or more functions to be performed by the corresponding cellular identifier associated with the visual indication. Figure 6L A contact user interface is shown for contacts associated with a "primary" cellular identifier. Figure 6LAs shown, the contact user interface includes an indication 640 of the contact's name (e.g., "Mary Smith"), a first phone number affordance 642a of a first phone number associated with the contact, a second phone number affordance 642b of a second phone number associated with the contact, and a plurality of affordances 646a-646d that are selectable to perform various actions with respect to the contact (e.g., "Send Message" 646a, "Share Contact" 646b, "Add to Favorites" 646c, "Share My Location" 646d). The phone number affordances 642a-642b each include an indication 644 of a cellular identifier associated with the contact (e.g., a "primary" cellular identifier indicated by a "Pr" indication). The phone number affordances 642a-642b are selectable to initiate a phone call to the corresponding phone number indicated by the affordance using the cellular identifier associated with the contact, as indicated by indication 644 by default.

[0210] When a user changes the label of a cellular identifier (e.g., “Primary,” “Personal,” etc.), a visual indication of the cellular identifier (e.g., an icon including “Pr,” “Pe,” etc.) is optionally updated across multiple user interfaces of the electronic device to match the new label of the cellular identifier. Figure 6M As shown, when a user renames the "primary" cellular identifier (associated with the telephone number 555-123-4567) to "business," the indication of that cellular identifier in the settings user interface is updated to reflect this change. Figure 6M The user interface shown is similar to Figure 6K The user interface shown is substantially the same, except that the "primary" cellular identifier has been renamed "Business." Based on the updated label of the cellular identifier, the electronic device 500 presents the "Business" label in the user interface and updates the indication of the cellular identifier to include a "B" (rather than a "Pr"). Because "Business" and "Personal" begin with different letters, the indication of the "primary" cellular identifier has been updated from "Pr" to "P" because indicating the cellular identifier by the first letter of the cellular identifier's label is sufficient to distinguish one cellular identifier from another.

[0211] Similarly, Figure 6N A contact user interface is shown for a contact associated with a "business" cellular identifier that was previously labeled as a "primary" cellular identifier. Figure 6N The contacts user interface shown in is basically similar to Figure 6L , except that indicator 644 is updated to reflect that the "primary" cellular identifier has been renamed "business". Similarly, indicator 644 includes Figure 6L The "B" shown in the figure is not "Pr".

[0212] Fig.6O The electronic device 500 is shown presenting a cellular identifier setting user interface, through which a new cellular identifier can be added to the device 500. In some embodiments, the cellular identifier setting user interface can be accessed from a setting user interface of the electronic device, which includes an affordance that can be selected to navigate to various other setting user interfaces of the electronic device (e.g., notification settings, general settings, display settings, sound settings, passwords and authentication settings, etc.). Fig.6O As shown, the user (e.g., using contact 603) selects an affordance 648 (e.g., "Add new eSIM") for adding a new cellular identifier to the electronic device. In response to the user's selection, the electronic device presents a user interface for adding a new cellular identifier, such as Figure 6B The camera user interface shown and / or Figure 6C The password user interface shown.

[0213] Figure 6P 638d, the electronic device 500 presents the cellular identifier settings user interface. Figure 6P As shown, the electronic device 500 optionally does not enable the "travel" cellular identifier for performing any actions because, in some embodiments, only two cellular identifiers can be activated on the device 500 at any given moment, thus indicating that the cellular identifier is "not activated." Therefore, the cellular identifier setting user interface optionally includes an "activate" enable representation 650, which can be selected to activate the "travel" cellular identifier, which enables the electronic device 500 to perform one or more functions using the "travel" cellular identifier.

[0214] like Figure 6Q As shown, the user selects (e.g., using contact 603) "activate" affordance 650. In response, device 500 activates the "travel" cellular identifier to allow electronic device 500 to perform operations using the "travel" cellular identifier, such as Figure 6R As shown. Figure 6RAs shown, the "travel" cellular identifier becomes the default number for phone calls and SMS (e.g., because it was the most recently activated cellular identifier), the "personal" cellular identifier becomes the "data-only" cellular identifier (e.g., because it was previously the primary number for phone calls / SMS), and the "business" cellular identifier is deactivated (e.g., because it was a secondary number for phone calls / SMS). Indications 638a, 638c, and 638d are updated according to these new functional settings for the cellular identifiers. In addition, indication 638c of the "business" cellular identifier is updated to include an "activate" affordance 650 that can be selected to activate the "business" cellular identifier for use in performing operations on the electronic device.

[0215] Figure 7A-Figure 7I 700 is a flowchart illustrating a method 700 of presenting a settings user interface associated with a cellular identifier according to some embodiments of the present disclosure. The method 700 is optionally performed on an electronic device (such as device 100, device 300, device 500), as described above with reference to Figure 1A-1B , Figure 2-Figure 3 , Figure 4A-4B and Figure 5A-5H Some operations in method 700 are optionally combined, and / or the order of some operations is optionally changed.

[0216] As described below, method 700 provides a method for presenting a settings user interface associated with a cellular identifier. The method reduces the cognitive burden on the user when interacting with the device user interface of the present disclosure, thereby creating a more efficient human-machine interface. For battery-powered electronic devices, improving the efficiency of user interaction with the user interface saves power and increases the time between battery charges.

[0217] In some embodiments, the electronic device (e.g., electronic device 500) communicates with a display and one or more input devices (e.g., a mobile device including a touch screen (e.g., a tablet, smart phone, media player, or wearable device) or a computer including one or more of a keyboard, a mouse, a trackpad, and a touch screen). In some embodiments, the electronic device has cellular communication capabilities (such as cellular transmit / receive hardware) and the ability to communicate with a cellular network. The electronic device optionally receives (702) input corresponding to a request to set a first cellular identifier for the electronic device (e.g., a physical SIM (Subscription Identity Module) card for the electronic device, an eSIM (e.g., an embedded SIM), etc.), such as via one or more input devices. Fig.6O Selection of the “Add New eSIM” button 648 is shown. In some embodiments, the electronic device can have more than one cellular identifier (e.g., SIM card, eSIM, etc.), such as in Figure 6A-6CIn some embodiments, the input corresponding to the request to set the first cellular identifier is the introduction of a cellular identifier to the electronic device (e.g., installing a new SIM or eSIM). In some embodiments, the input corresponding to the request to set the first cellular identifier is the selection of an affordance or button that, when activated, causes the electronic device to display a cellular identifier setup or setup user interface. In some embodiments, the setup of the first cellular identifier is not initiated until two cellular identifiers are added to the electronic device.

[0218] In some embodiments, in response to receiving the request to set the first cellular identifier for the electronic device, the electronic device initiates (704) a process to set the first cellular identifier for the electronic device (e.g., Figure 6A-6J In some embodiments, the process of setting the first cellular identifier is performed when the first cellular identifier is first introduced to the device or later (for example, to update one or more settings of the first cellular identifier), such as in Fig.6O as shown in .

[0219] In some embodiments, the process for setting a first cellular identifier for an electronic device includes receiving (708) input, via one or more input devices, a first label defining the first cellular identifier of the electronic device (e.g., a text nickname for the cellular identifier, such as "primary," "secondary," "data," "phone," "work," "personal," "domestic," "international," etc.), such as Figure 6G , wherein the electronic device displays an indicator based on the first label, such as Figure 6L In some embodiments, the electronic device presents a user interface that includes one or more labels from a plurality of selectable predefined labels, such as a text or image derived from the label of the first cellular identifier, such as an icon including the first one or more letters of the label of the cellular identifier, to represent the first cellular identifier. Fig. 6E , labels 626a-d (e.g., "primary," "secondary," "data," "phone," "work," "personal," "home," "international," etc.), and / or a text input user interface (e.g., a text box and optional soft keyboard), such as Figure 6F-6GAs shown. The label is optionally displayed as an indicator (e.g., an icon, thumbnail, text, or image) adjacent to the first cellular identifier and optionally adjacent to an indication of a telephone number associated with the cellular identifier. In some embodiments, an indicator (e.g., an icon) is automatically generated based on a label representing the first cellular identifier (e.g., a user-defined nickname for the cellular identifier). For example, a "primary" cellular identifier label is optionally indicated by an indicator such as an icon with text "P", "Pr", or "P2". When the electronic device performs a function (e.g., making a call, sending a message, downloading or uploading data, interacting with a contact) using the first cellular identifier, the electronic device optionally presents the indicator in one or more user interfaces.

[0220] The electronic device optionally receives (710) input via one or more input devices selecting a corresponding set of one or more functions (e.g., making and receiving phone calls, sending text messages, downloading or uploading data, storing and recalling contact information of one or more contacts, etc.) for the first cellular identifier (e.g., Figure 6J 603), these functions such as Figure 6J The functions represented by the enable indications 636a-c in the figure are shown, where the electronic device is able to use the first cellular identifier of the electronic device to perform multiple functions, including one or more selected functions. The user optionally selects which functions of the electronic device are performed by the first cellular identifier by default. In some embodiments, the electronic device includes two or more cellular identifiers, which have different functions selected for each cellular identifier. For example, the electronic device optionally includes a "main" cellular identifier and a "data" cellular identifier. During the setup, the user optionally selects "data upload and download" as the function of the "data" cellular identifier, and optionally selects functions such as phone calls and text messages as the functions of the "main" cellular identifier. When the electronic device is used to upload and download data (e.g., web browsing, sending and receiving emails, accessing cloud storage, etc.), the "data" cellular identifier is optionally used by default to perform data upload and download. When the electronic device is used to make a phone call, the "main" cellular identifier is optionally used by default to perform the phone call. In some embodiments, the electronic device is able to use a cellular identifier different from the default cellular identifier selected for a given function to perform the function. For example, if reception is poor or unavailable under the "data" cellular identifier, the electronic device can use the "primary" cellular identifier to upload or download data. In addition, in some embodiments, each contact is associated with one of the cellular identifiers so that communications with the individual are performed using the cellular identifier associated with the contact rather than the default cellular identifier for such communications.

[0221] In some embodiments, in response to receiving input selecting a corresponding set of one or more functions for the first cellular identifier (712), such as detecting Figure 6J In contact 603, based on determining that the corresponding set of one or more functions is a first set of one or more functions (e.g., primary number 636b for phone / SMS), the electronic device initiates (712) a process of enabling the first cellular identifier to be used for the first set of one or more functions, such as Figure 6K and determining that the corresponding set of one or more functions is a second set of one or more functions that is different from the first set of one or more functions (e.g., a secondary number 636a for phone / SMS, such as Figure 6J As shown), the electronic device initiates (714) a process of enabling the first cellular identifier to be used for a second set of one or more functions, such as Figure 6K In some embodiments, the first set of one or more functions includes at least one function that is not included in the second set of one or more functions. In some embodiments, the second set of one or more functions includes at least one function that is not included in the first set of one or more functions. In some embodiments, the first set of one or more functions and the second set of one or more functions include one or more functions in common. In some embodiments, the first set of one or more functions and the second set of one or more functions are mutually exclusive.

[0222] The above-described manner of setting the first cellular identifier at the electronic device allows the electronic device to be set up to utilize the first cellular identifier to perform multiple functions, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by utilizing the first cellular identifier to perform the selected function without providing explicit user input using the first cellular identifier for the selected function each time the selected function is to be performed), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0223] In some embodiments, the corresponding set of one or more functions is one of a voice and messaging function, a data function, and a primary cellular identifier function (718), such as Figure 6J636a-c in the instructions. The primary cellular identifier function optionally includes voice, messaging, and data functions, and the cellular identifier selected for performing the primary cellular identifier function is optionally the default cellular identifier for performing those functions. In some embodiments, the primary cellular identifier is used for voice, messaging, and data functions by default unless these functions are unavailable (e.g., the primary cellular identifier has a bad signal or no service). When the primary cellular identifier is not available to perform the corresponding function, a different cellular identifier configured for the corresponding function optionally performs the corresponding function. For example, the primary cellular identifier is optionally used by default to make a phone call when it is able to make a phone call. When the primary cellular identifier is unavailable, the secondary cellular identifier configured for voice communication is optionally used to make a phone call.

[0224] The above-described manner of selecting the function of the first cellular identifier among the voice, messaging, data, and primary cellular identifier functions allows the electronic device to be configured to utilize the first cellular identifier to perform multiple functions, which simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by utilizing the first cellular identifier to perform the selected function without providing explicit user input using the first cellular identifier for the selected function each time the selected function is to be performed), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0225] In some embodiments, before initiating setting a first cellular identifier for an electronic device (e.g., by Figure 6P Prior to the process of the "travel" cellular identifier indicated by indication 638d in the example above, the electronic device is configured to use a second cellular identifier (e.g., Figure 6P The electronic device may be configured with a "personal" cellular identifier (indicated by indication 638a in FIG. 1 ) to perform the primary cellular identifier function (720). For example, only the second cellular identifier is configured on the electronic device, or both the first cellular identifier and the second cellular identifier are configured on the electronic device and the first cellular identifier is configured for the secondary cellular identifier function.

[0226] In some embodiments, the process of setting up a first cellular identifier for an electronic device includes (722) configuring (724) the electronic device to use the first cellular identifier to perform primary cellular identifier functions (e.g., Figure 6R In some embodiments, the user changes the settings to set the functionality of the first cellular identifier to the primary cellular identifier functionality (e.g., the default cellular identifier for performing voice, messaging, and / or data functions). The setup process for the first cellular identifier optionally includes configuring (726) the electronic device to use the second cellular identifier to perform the secondary cellular identifier functionality (e.g., data only) (e.g., as shown in FIG. 6A ). Figure 6R 638a). In some embodiments, when the function of the first cellular identifier is updated to the primary cellular identifier function, the electronic device automatically updates the function of the second cellular identifier to a secondary (e.g., non-default) cellular function (e.g., voice, messaging, and / or data function). In some embodiments, the user is able to update the function of the secondary cellular identifier. For example, while the function of the first cellular identifier is still the primary cellular identifier function, the second cellular identifier function is optionally updated to pure data (e.g., while the first cellular identifier is still the default cellular identifier for voice and messaging functions, the second cellular identifier becomes the default cellular identifier for data functions) or as the default cellular identifier for one or more contacts stored on the electronic device (e.g., the electronic device uses the second cellular identifier to perform voice and messaging functions for one or more specified contacts by default, and uses the first cellular identifier for voice and messaging operations for all other contacts and phone numbers by default).

[0227] The above-described manner of configuring the second cellular identifier to perform the secondary cellular identifier function in response to configuring the first cellular identifier to perform the primary cellular identifier function allows the electronic device to continue to use the second cellular identifier as the secondary cellular identifier when the first cellular identifier is configured as the primary cellular identifier, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by updating the settings of the second cellular identifier when the settings of the first cellular identifier are updated without the user having to enter additional input to configure the second cellular identifier as the secondary cellular identifier), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0228] In some embodiments, configuring the electronic device to use the second cellular identifier to perform the secondary cellular identifier function includes configuring the electronic device to use the second cellular identifier (e.g., Figure 6R The "personal" cellular identifier indicated by indication 638a in FIG. 1 is used only for cellular data (728). In some embodiments, only when the function of the first cellular identifier is updated to the primary cellular identifier function, the electronic device automatically updates the function of the second cellular identifier to the data function, and the electronic device optionally uses the first cellular identifier to perform voice and messaging functions, and optionally uses the second cellular identifier to perform data operations.

[0229] The above-described manner of configuring the second cellular identifier to perform a cellular data function in response to configuring the first cellular identifier to perform a primary cellular identifier function allows the electronic device to continue to use the second cellular identifier for a data function when the first cellular identifier is configured as a primary cellular identifier, which simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by updating the settings of the second cellular identifier when the settings of the first cellular identifier are updated without requiring the user to enter additional input to configure the second cellular identifier for the cellular data function), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0230] In some embodiments, the process of setting up a first cellular identifier for an electronic device includes (730): requesting (732) access credentials (e.g., a PIN, password, passcode, QR code authentication, or other authentication) for allowing access to the first cellular identifier, such as in Figure 6B-6C In some embodiments, the electronic device presents a user interface for entering access credentials. For example, the electronic device presents a dial pad for accepting a PIN, a soft keyboard for accepting a password or a passcode, a camera user interface for accepting a QR code, or a user interface suitable for accepting another form of authentication. The process optionally includes receiving (734) via one or more input devices an access credential (e.g., Figure 6B Image 610 or Figure 6C 616) (e.g., the electronic device detects that a user enters access credentials), and in response to receiving the entered access credentials (736), based on determining that the entered access credentials are correct, allowing (738) the process of setting the first cellular identifier for the electronic device to proceed, such as in Fig.6D . In some embodiments, when the user provides correct access credentials, the electronic device is able to use the first cellular identifier to perform one or more functions, and the setup process continues. Based on determining that the entered access credentials are incorrect, the electronic device abandons (740) allowing the process of setting the first cellular identifier for the electronic device to continue. In some embodiments, when the user provides incorrect access credentials, the electronic device is unable to use the first cellular identifier to perform one or more functions, and the setup process stops. In some embodiments, when the user provides incorrect access credentials, the electronic device presents a message indicating that the credentials are incorrect. The electronic device optionally presents an enabling representation that can be selected to display a user interface for accepting the credentials again, so that the user can try to enter the access credentials next time.

[0231] The above-described manner of authenticating the first cellular identifier allows the electronic device to use the first cellular identifier in a secure manner, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by ensuring that the user of the electronic device is first authorized to access the first cellular identifier and then configures the settings of the first cellular identifier), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0232] In some embodiments, the input corresponding to the request to set the first cellular identifier for the electronic device includes capturing an image (610) (742) of a graphic corresponding to the first cellular identifier via a camera of the electronic device, such as in Figure 6B The QR code optionally includes access credentials for installing the eSIM on the electronic device, thereby allowing the eSIM to be used as the first cellular identifier.

[0233] The above-described manner of enabling a user to authenticate the first cellular identifier by capturing an image allows the electronic device to authenticate the first cellular identifier without requiring manual authentication input from the user, which simplifies the interaction between the user and the device and enhances the operability of the device, which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0234] In some embodiments, in response to capturing an image (610) (744) of a graphic corresponding to a first cellular identifier via a camera of the electronic device (e.g., a user captures an image of a QR code associated with an eSIM or another type of cellular identifier), such as in Figure 6B As shown in: Based on determining that the first cellular identifier is successfully identified using the image, the electronic device initiates (746) a process of setting the first cellular identifier for the electronic device, such as in Fig.6D , and based on determining that the first cellular identifier was not successfully identified using the image (e.g., the image is not an image of a graphic corresponding to the cellular identifier, the image does not clearly capture a graphic corresponding to the cellular identifier, or the graphic corresponding to the first cellular identifier is invalid), the electronic device requests (748) manual input (such as in the form of a dial pad 618) via one or more input devices (e.g., via interaction with the soft dial pad 618 presented on the touch screen 504). Figure 6CIn some embodiments, the electronic device presents information about the first cellular identifier (e.g., the electronic device presents a user interface for entering access credentials such as a PIN, password, passcode, or other authentication). In some embodiments, the user interface includes a field for entering text associated with an identification of the cellular identifier (e.g., a serial number or some other identifying name, number, or code) and a field for entering the access credentials. That is, the text associated with the identification of the cellular identifier and the access credentials are not necessarily the same. In some embodiments, the electronic device also presents an affordance that is selectable to capture another image of a graphic corresponding to the first cellular identifier.

[0235] The above-described manner of allowing the user to manually input information about the first cellular identifier when authentication by image capture is unsuccessful allows the electronic device to provide an alternative way for the user to authenticate the first cellular identifier when authentication using an image does not work, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by allowing the user to use an alternative authentication method when camera authentication fails), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0236] In some embodiments, in response to receiving input of a first label defining a first cellular identifier of the electronic device (e.g., a text nickname of the cellular identifier, such as "primary," "secondary," "data," "phone," "work," "personal," "domestic," "international," etc.), the electronic device generates (750) an indicator (e.g., text, an image, or an icon) corresponding to the first cellular identifier based on the first label (e.g., the content of the indicator is selected based on the text of the label, such as including the first letter of the label (e.g., the indicator includes "P" or "P1" based on the label "primary"), the first two letters of the label (e.g., the indicator includes the text "Pr" based on the label "primary"), or the first letters of the first two words of the label (e.g., the indicator includes the text "UD" based on the label "unlimited data")), as described above. Figure 6H Examples of generating an indicator corresponding to a first cellular identifier are described in further detail.

[0237] In some embodiments, the indicator (e.g., Figure 6L The indicator 644 shown in FIG. 1 is displayed by the electronic device as a user interface in at least one or more user interfaces (such as in FIG. 1 ) outside the process of setting the first cellular identifier for the electronic device. Figure 6LIn some embodiments, the indicator is displayed in one or more communication user interfaces to indicate which cellular identifier is being used to perform the communication functions of the communication user interface. In some embodiments, the indicator is displayed in one or more of a messaging user interface, a phone user interface, a voicemail user interface, and the like. For example, the indicator is displayed next to a visual indication of a communication performed using the first cellular identifier (e.g., an indication of a message, an indication of a voicemail, an indication of an incoming or outgoing phone call, and the like), such as in a Figure 6L In some embodiments, the contact user interface presents multiple phone numbers for corresponding contacts and includes a single indication of the cellular identifier associated with the contact, rather than Figure 6L Shown is a plurality of indicators 644. An indicator of an associated cellular identifier optionally may be selected to cause the electronic device to present selectable options for changing which cellular identifier the corresponding contact is associated with.

[0238] The above-described manner of generating an indicator corresponding to a user-defined label for a first cellular identifier and presenting the indicator in one or more other user interfaces of the electronic device allows the electronic device to communicate to the user which cellular identifier is used to perform a corresponding operation on the electronic device, which simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by notifying the user which cellular identifier is used to perform a corresponding operation without requiring the user to provide input to display cellular identifier information), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0239] In some embodiments, generating an indicator corresponding to the first cellular identifier includes (754) generating an indicator corresponding to the first cellular identifier based on determining Figure 6M An indicator having a first number of characters (e.g., starting from the first character of the first tag) of a "business" cellular identifier (e.g., indicated by indication 638c in FIG. 1 ) will associate the indicator with the cellular identifier corresponding to the business identifier (e.g., indicated by Figure 6M The electronic device generates (756) an indicator having a first number of characters (e.g., one character) corresponding to the first cellular identifier to distinguish it from an existing second indicator of a second label of the second cellular identifier (e.g., a “personal” cellular identifier indicated by indication 638a in the electronic device). In some embodiments, the label of the second cellular identifier and the label of the first cellular identifier begin with different letters, and therefore, using the first letter of the label as the indicator of the cellular identifier can distinguish them. For example, if the labels of the first cellular identifier and the second cellular identifier are “primary” and “secondary”, respectively, the corresponding indicators of these labels are optionally “P” and “S”, respectively. Based on determining to generate an indicator corresponding to the first cellular identifier (e.g., indicated by indication 638a in the electronic device), the electronic device generates (756) an indicator having a first number of characters (e.g., one character) corresponding to the first cellular identifier. In some embodiments, the label of the second cellular identifier and the label of the first cellular identifier begin with different letters, and therefore, using the first letter of the label as the indicator of the cellular identifier can distinguish them. For example, if the labels of the first cellular identifier and the second cellular identifier are “primary” and “secondary”, respectively, the corresponding indicators of these labels are optionally “P” and “S”, respectively. Figure 6K In the embodiment of the present invention, the electronic device generates (758) an indicator corresponding to the first cellular identifier having a second number of characters greater than the first number of characters (e.g., two), such as in the embodiment of the present invention, wherein the indicator has a first number of characters that does not distinguish the indicator from an existing second indicator corresponding to a second label of the cellular identifier (e.g., the label of the second cellular identifier and the label of the first cellular identifier begin with the same letter, so that using only the first letter of the label as the indicator does not produce a different label). Figure 6K As shown in . In some embodiments, the electronic device uses the first two or more characters of the label as an indicator, or uses the first letter and a unique number for the label. For example, if the labels of the first cellular identifier and the second cellular identifier are "main" and "personal", the corresponding indicators of these labels are optionally "Pr" and "Pe". For another example, if the labels of the first cellular identifier and the second cellular identifier are "main" and "shared", the corresponding indicators of these labels are optionally "Pri" and "Pro". In some embodiments, when the maximum number of characters (e.g., 3) in front of each label is the same, the electronic device uses numbers to distinguish the indicators from each other. For example, if the labels of the first cellular identifier and the second cellular identifier are "main" and "private", the corresponding indicators of these labels are optionally "P1" and "P2". In this way, the electronic device can provide a unique indicator for each cellular identifier for use in various user interfaces associated with one or more functions of the electronic device with the cellular identifier. When presenting a user interface associated with a function, these unique indicators of the cellular identifier enable the electronic device to convey to the user which cellular identifier is being used to perform various functions.

[0240] The above-described manner of generating unique indicators of the first cellular identifier and the second cellular identifier allows the electronic device to provide distinguishing information to the user, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by clearly presenting an indication of which cellular identifier is being used to perform a corresponding function at the electronic device, enabling the user to perform the function using the cellular identifier they intended to use), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0241] In some embodiments, after the first cellular identifier is set for the electronic device, the electronic device displays (760) a representation of the first cellular identifier on a display (e.g., Figure 6P 638c) and a representation of a second cellular identifier (e.g., Figure 6P 638d) (e.g., displayed in a cellular settings user interface).

[0242] In some embodiments, the second cellular identifier (e.g., Figure 6P 638d in the electronic device) is currently not activated on the electronic device (e.g., the second cellular identifier is not configured to perform a function on the electronic device), and a representation of the second cellular identifier is displayed (762) simultaneously with an affordance (650) for activating the second cellular identifier on the electronic device (e.g., the electronic device optionally also presents an indication of the inactive state of the second cellular identifier), such as in Figure 6P as shown in .

[0243] In some embodiments, while a representation of the first cellular identifier (638c) and a representation of the second cellular identifier (638d) are displayed on the display, the electronic device receives (764) via one or more input devices an input (e.g., a tap or touch received at a touch screen, a click received by a mouse or trackpad, a shortcut entered at a keyboard, a dial pad, or a soft keyboard, voice input, etc.) corresponding to a selection of an enabling representation (650) for activating the second cellular identifier. Figure 6Q ), such as in Figure 6Q as shown in .

[0244] In some embodiments, in response to receiving input corresponding to a selection of an indication for activating a second cellular identifier (e.g., the “travel” cellular identifier indicated by indication 638d), the electronic device activates (766) the second cellular identifier on the electronic device, such as in Figure 6R In some embodiments, activating the second cellular identifier configures the second cellular identifier to perform the primary cellular identifier function (e.g., the second cellular identifier is used for voice, messaging, and data operations by default). In some embodiments, activating the second cellular identifier configures the second cellular identifier to perform the secondary cellular function (e.g., the second cellular identifier is used for voice, messaging, and data operations when the primary cellular identifier is not available). In some embodiments, activating the second cellular identifier configures the second cellular identifier to perform the function that it was previously configured to perform when it was last activated on the electronic device.

[0245] The above-described manner of presenting an indication of available but inactivated cellular identifiers allows the electronic device to provide the user with the ability to change which cellular identifiers are activated on the electronic device, which simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by saving information related to inactivated cellular identifiers rather than requiring the user to go through the setup process from scratch for the inactivated cellular identifiers), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0246] In some embodiments, input corresponding to a request to set a first cellular identifier is received during an initial setup process of the electronic device (e.g., when the electronic device is configured for first use, the initial setup process guides the user through various device settings and user account logins, including a process for configuring one or more cellular identifiers available for use with the electronic device). Figure 6A-6K An example of the initial setup process is described in more detail.

[0247] The above-described manner of presenting a user interface for configuring a cellular identifier during an initial setup process of an electronic device allows the electronic device to provide a user with the ability to set cellular identifier settings before the user uses the electronic device, which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0248] In some embodiments, the initial setup process of the electronic device is the first setup process of a new electronic device (770). The initial setup process is optionally displayed when the electronic device is set up for the first time or after its memory has been erased. Figure 6A-6K An example of an initial setup process for a new electronic device is described in more detail.

[0249] The above-described manner of presenting a user interface for configuring a cellular identifier during an initial setup process of an electronic device allows the electronic device to provide a user with the ability to set up cellular identifier settings before the user uses the electronic device for the first time, which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0250] In some embodiments, a process (772) of setting a first cellular identifier for an electronic device is initiated in response to detecting a second cellular identifier at the electronic device (e.g., when the second cellular identifier is introduced to the electronic device). In some embodiments, when a SIM card is inserted into a mobile device or an eSIM is activated on an electronic device, the electronic device presents a cellular identifier setting user interface for configuring a second cellular identifier and an existing cellular identifier (e.g., a first cellular identifier). When an electronic device operates using one cellular identifier, the electronic device is optionally configured to perform all cellular identifier functions (e.g., voice, messaging, data) using the cellular identifier. When an electronic device operates using two or more cellular identifiers, the electronic device is configured to perform various cellular identifier functions using various cellular identifiers available to the electronic device. Reference 6A-6A above. Figure 6J An example of a process for setting a cellular identifier is described in more detail.

[0251] The above-described manner of initiating a setup process for the first cellular identifier in response to detecting the first cellular identifier allows the electronic device to provide the ability to set up the cellular identifier when the cellular identifier is first introduced into the electronic device, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by presenting a cellular identifier setup user interface without requiring the user to manually navigate to the cellular identifier user interface), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0252] In some embodiments, in response to input detected in a cellular settings user interface of the electronic device (e.g., Fig.6O The user may select the enable indication 648 using contact 603 to initiate a process of setting a first cellular identifier for the electronic device (774). The user may optionally select a cellular settings user interface to set the first cellular identifier. In some embodiments, the first cellular identifier is set for the first time from the settings user interface. In some embodiments, the first cellular identifier has already been set, and the user is able to go to the settings user interface to update one or more settings related to the setting of the cellular identifier (e.g., activate or deactivate the first cellular identifier, select one or more functions to be performed using the first cellular identifier, change the label of the first cellular identifier, etc.).

[0253] The above-described manner of presenting the cellular identifier settings user interface in the settings user interface allows the electronic device to present the cellular identifier settings user interface to the user in response to a user request to present the cellular identifier settings user interface, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by allowing the user to conveniently set the first cellular identifier or change one or more settings associated with the first cellular identifier), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0254] In some embodiments, the process of setting a first cellular identifier for an electronic device includes (776) receiving (778) input corresponding to a request to specify a first cellular identifier by name via one or more input devices, such as Figure 6J 603 is used to select a "primary number for phone calls / SMS" option 636b (e.g., a primary cellular identifier name, a secondary cellular identifier name, or another name). In some embodiments, designating a cellular identifier as a primary cellular identifier causes the electronic device to use the cellular identifier to perform voice, messaging, and / or data functions by default. In some embodiments, designating a cellular identifier as a secondary cellular identifier causes the electronic device to use the cellular identifier to perform voice, messaging, and / or data functions when the primary cellular identifier is unable (e.g., no signal, deactivated, etc.) to perform the function.

[0255] In some embodiments, in response to receiving an input corresponding to a request to specify a first cellular identifier by name (e.g., Figure 6J In the example of selecting option 636b using contact 603 (780), based on determining that the name is the primary cellular identifier name, the electronic device is configured (782) to use the first cellular identifier to perform the messaging function, such as Figure 6K In some embodiments, the electronic device uses the primary cellular identifier to send and receive messages using a messaging service or platform (such as a messaging platform associated with the electronic device, associated with a user account of the electronic device, etc.). For example, the electronic device uses the primary cellular identifier to send and receive messages using an enhanced messaging service. Based on determining that the name is not the primary cellular identifier name, configuring the electronic device includes abandoning (784) using the first cellular identifier to perform messaging functions, such as Figure 6K The electronic device optionally does not use the secondary cellular identifier to send and receive messages using a messaging service or platform (such as a messaging platform associated with the electronic device, associated with a user account of the electronic device, etc.). In some embodiments, when the primary cellular identifier is not available, the electronic device uses the secondary cellular identifier to send messages to the contact using a different messaging service (e.g., SMS).

[0256] The above-described manner of using the primary cellular identifier to perform messaging functions allows the electronic device to associate a user account for a messaging service with the primary cellular identifier, which simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by using the primary cellular identifier to log into the user account for the messaging service), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0257] It should be understood that Figure 7A-Figure 7I The specific order in which the operations in the description are described is merely exemplary and is not intended to indicate that the order is the only order in which the operations may be performed. A person of ordinary skill in the art will recognize many ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (e.g., methods 900, 1100, 1300, and 1500) are also applicable in a similar manner to the details of the processes described above in conjunction with Figure 7A-Figure 7I The method 700 described above. For example, the cellular identifier setting described above with reference to the method 700 optionally has one or more features of the cellular identifier setting of the electronic device communicating with other electronic devices, the indication of the cellular identifier, the operations performed using the cellular identifier, etc. described herein with reference to other methods described herein (e.g., methods 900, 1100, 1300, and 1500). For the sake of brevity, these details are not repeated here.

[0258] The operations in the above information processing method are optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (for example, in combination with Figure 1A to Figure 1B , Figure 3 , FIG. 5A to FIG. 5H In addition, the above reference Figure 7A-Figure 7I The described operations are optionally performed by Figure 1A-1B. For example, display operations 708, 752, and 760 and receiving operations 702, 708, 710, 734, 764, 766, 768, and 778 are optionally implemented by event classifier 170, event identifier 180, and event handler 190. Event monitor 171 in event classifier 170 detects contact on touch screen 504, and event distributor module 174 transmits event information to application 136-1. The corresponding event identifier 180 of application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first position on the touch screen corresponds to a predefined event or sub-event, such as a selection of an object on a user interface. When a corresponding predefined event or sub-event is detected, event identifier 180 activates event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, event handler 190 accesses corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly know how to update the content based on the GUI updater 178. Figure 1A to Figure 1B The components depicted in the figure are used to implement other processes.

[0259] Wearable device cellular identifier settings

[0260] Users interact with electronic devices in a variety of different ways, including viewing information about the use of electronic devices and / or electronic devices. In some embodiments, a first electronic device (e.g., a wearable device, such as a smart watch) can utilize a first cellular identifier to perform operations regardless of how the connection with a second electronic device (e.g., a mobile device) is, and when the first electronic device is connected to a second electronic device, a second cellular identifier can be utilized to perform operations. The embodiments described below provide a method in which a first electronic device presents instructions for operations using a first cellular identifier and a second cellular identifier based on a connection state with a second electronic device. Enhanced interaction with the device reduces the amount of time required for the user to perform an operation, thereby reducing the power consumption of the device and extending the battery life of a battery-powered device. It should be understood that people use devices. When a person uses a device, this person is optionally referred to as a user of the device.

[0261] Figure 8A-8U An exemplary method of a first electronic device accessing a first cellular identifier regardless of how the first electronic device is connected to a second electronic device according to some embodiments of the present disclosure, and an exemplary method of a first electronic device accessing a second cellular identifier when the first electronic device is connected to the second electronic device are shown. The embodiments in these figures are used to illustrate the processes described below, including reference to 9A to 9H The process described.

[0262] Fig. 8A An exemplary device 500a having a touch screen 504 is shown, such as in reference Figure 5A-5H The touch screen 504 optionally displays one or more user interfaces including various contents. As shown in the figure, the electronic device 500a is a wearable device, such as a smart watch. Fig. 8A In the example shown, the touch screen 504 displays a user interface for associating a cellular identifier with the electronic device 500a. The user interface includes a first enable representation 802a that is selectable to associate a "personal" cellular identifier with the electronic device 500a and a second enable representation 802b that is selectable to associate a "business" cellular identifier with the electronic device 500a (e.g., the cellular identifier described with reference to method 700). The electronic device 500a will optionally be able to utilize the selected cellular identifier to perform functions even if the electronic device is not communicating with the second electronic device 500b. In some embodiments, the second electronic device is a smart phone and is a device capable of utilizing multiple cellular identifiers, such as described with reference to method 700. In some embodiments, the device 500a is an accessory to the device 500b. As Fig. 8A As shown, when the user interface shown is presented at the first electronic device 500a, the first electronic device 500a communicates with the second electronic device 500b. The second electronic device 500b has access rights to both the "personal" cellular identifier and the "business" cellular identifier. Figure 8B As shown, the user (e.g., using contact 803) selects a second enabling indication 802b for enabling the first electronic device 500a to utilize a "business" cellular identifier to perform an operation, even if the first electronic device 500a is not communicating with the second electronic device 500b. In some embodiments, when device 500a is not communicating with device 500b, it is only capable of utilizing a single cellular identifier (e.g., a "business" cellular identifier, i.e., one of the cellular identifiers that device 500b is configured to use), and when it is communicating with device 500a, it is capable of utilizing multiple cellular identifiers (e.g., two cellular identifiers that device 500b is configured to use), as will be further described below.

[0263] Figure 8C Shown in Figure 8B After selecting the "business" cellular identifier for device 500a in the first electronic device 500a, the first electronic device 500a presents a user interface for initiating a telephone call to one of the multiple contacts whose contact information is stored on the first electronic device 500a. Figure 8C As shown, the first electronic device 500a presents Figure 8C1. When the user interface is shown, the first electronic device 500a is communicating with the second electronic device 500b. The touch screen 504 displays a first enabling representation 804a that is selectable to communicate with a first contact associated with a "business" cellular identifier (e.g., "Mary Smith"), a second enabling representation 804b that is selectable to communicate with a second contact associated with a "business" cellular identifier (e.g., "Alex Garcia"), and a third enabling representation 804c that is selectable to communicate with a third contact associated with a "personal" cellular identifier (e.g., "John Brown"). When the first electronic device 500a is communicating with the second electronic device 500b, all enabling representations 804a-c are optionally selectable to initiate a phone call to the associated contact regardless of which cellular identifier the contact is associated with.

[0264] Fig.8D FIG. 5 shows a first electronic device 500a presenting a user interface for initiating a phone call to one of a plurality of contacts whose contact information is stored on the first electronic device 500a. Fig.8D As shown, the first electronic device 500a presents Fig.8D When the user interface is shown, the first electronic device 500a is not communicating with the second electronic device 500b. The touch screen 504 displays a first enable representation 804a that is selectable to communicate with a first contact associated with the “business” cellular identifier (e.g., “Mary Smith”) and a second enable representation 804b that is selectable to communicate with a second contact associated with the “business” cellular identifier (e.g., “Alex Garcia”). The third enable representation 804d that was previously selectable to communicate with a third contact associated with the “personal” cellular identifier (e.g., “John Brown”) has a deactivated (e.g., grayed out) appearance. When the first electronic device 500a is not communicating with the second electronic device 500b, the “personal” cellular identifier is optionally unavailable for use by the first electronic device 500a. Fig.8D As shown, the user selects (eg, using contact 803) a third affordance 804d associated with a third contact.

[0265] In some embodiments, in response to a user selecting a contact associated with a cellular identifier that is not currently available for use by the first electronic device 500a, the first electronic device presents a warning user interface 806a, such as Fig. 8EAs shown. The warning user interface 806a optionally includes a message indicating which cellular identifier the selected contact is associated with, and an indication that a phone call cannot be initiated (e.g., indicating that the default cellular identifier for the selected contact is "personal", but the device 500a is currently only able to communicate using the "business" cellular identifier). In some embodiments, in response to the user selecting a contact associated with a cellular identifier that is not currently available to the first electronic device 500a, the first electronic device instead presents the warning user interface 806b, as shown. Fig.8F shown. Fig.8F The alert user interface 806b in includes a message indicating which cellular identifier the selected contact is associated with, and an enable indication 808 that allows the user to select to use a different cellular identifier to call the selected contact (e.g., use a cellular identifier that is currently activated on the device 500a that is different from the cellular identifier associated with the selected contact).

[0266] Figure 8G-Figure 8H The first electronic device 500a is shown presenting a settings user interface. The settings user interface includes a first enable representation 810a that can be selected to present clock settings, a second enable representation 810b that can be selected to present cellular settings, and a third enable representation 810c that can be selected to transform the first electronic device 500a into an airplane mode (e.g., a mode that disables the cellular identifier configured on the device 500a). The second enable representation 810b includes an indication of the cellular identifier activated on the first electronic device 500a (e.g., an icon with a "B"). Figure 8H As shown, the user (eg, using contact 803) selects a second affordance 810b for presenting a cellular setting for device 500a.

[0267] Figure 8I The first electronic device 500a responds to Figure 8H The cellular settings user interface is displayed. Figure 8I As shown, when the first electronic device 500a presents the cellular settings user interface, the first electronic device 500a is not connected to the second electronic device 500b. The cellular settings user interface optionally presents an option for changing which cellular identifier the first electronic device 500a has access to when it is not connected to the second electronic device 500b. The user interface includes a first enable representation 812a that is selectable to enable the first electronic device 500a to use a first cellular identifier ("personal"), and a second enable representation 812b that is selectable to enable the first electronic device 500a to use a second cellular identifier ("business"). However, when the first electronic device 500a is not connected to the second electronic device 500b, the first enable representation 812a associated with the first cellular identifier ("personal") is deactivated, as shown by the grayed-out appearance.

[0268] Figure 8J The first electronic device 500a is shown to present a user interface for initiating a phone call, and the user interface includes the same Fig.8D When device 500a presents Figure 8J When the user interface in the device 500a is displayed, the device 500a communicates with the device 500b. Figure 8J As shown, the user selects (e.g., using contact 803) a first affordance 804a associated with a first contact ("Mary Smith"). The first contact is associated with a "business" cellular identifier that can be used by first electronic device 500a even if first electronic device 500a is not connected to second electronic device 500b, meaning that first electronic device 500a will be able to complete the phone call even if first electronic device 500a is not connected to second electronic device 500b.

[0269] In response to selection of first affordance 804a, first electronic device 500a initiates a phone call to a first contact ("Mary Smith") using the "business" cellular identifier. While the phone call with the first contact is ongoing, first electronic device 500a presents Figure 8K The telephone user interface includes an indication 814 of the contact being called, an indication 816 of the cellular identifier being used by the first electronic device 500a to make the telephone call, an indication 818 of an option to end the telephone call, and an indication 820 of an option to add another contact to the telephone call. Figure 8L As shown, the user (e.g., using contact 803) selects enable representation 820 for adding another contact to the phone call.

[0270] In response to the selection, the first electronic device 500a presents a first enable representation 822a that is selectable to add the first contact ("Alex Garcia") to the phone call, and a second enable representation 822b that is selectable to add the second contact ("John Brown") to the phone call, such as Figure 8M As shown. Figure 8M As shown, the first contact is associated with a "business" cellular identifier and the second contact is associated with a "personal" cellular identifier. The user selects (e.g., using contact 803) a second affordance 822b for adding the second contact (the contact associated with the "personal" cellular identifier) ​​to the phone call while the call is currently being conducted using the "business" cellular identifier.

[0271] In response to Figure 8MThe first electronic device 500a presents a user interface for confirming the user's selection, such as Figure 8N 824 of the current phone call that lists the contact being called, the cellular identifier used for the phone call ("B"), and the duration of the phone call. The user interface also includes a message 826 informing the user that the default cellular identifier for the selected contact is different from the cellular identifier being used for the phone call (e.g., the cellular identifier used for the call is "B" and the default cellular identifier for the desired contact to be added to the phone call is "P"), and an affordance 828 that allows the user to select to add the selected contact to the ongoing call using the cellular identifier used for the phone call instead of the cellular identifier associated with the selected contact.

[0272] Fig.8O The first electronic device 500a is shown presenting a home screen user interface (e.g., a wake screen user interface, such as a watch face user interface displayed by the device when the device 500a first exits a low power / display off mode). The home screen user interface includes an indication of the current time 830. While presenting the home screen user interface, the first electronic device 500a detects an upward swipe from the bottom edge of the touch screen 504 toward the middle of the touch screen 504 (e.g., using contact 803).

[0273] In response to the upward swipe, the first electronic device 500a presents a control user interface, such as Figure 8P As shown. The control user interface includes an indication 832a of the signal strength of the "business" cellular identifier, an indication 832b of the signal strength of the "personal" cellular identifier, a location service indication 834, a cellular settings enable indication 836a, an airplane mode enable indication 836b, a check phone enable indication 836c, a Wi-Fi enable indication 836d, a battery enable indication 836e, and a flashlight enable indication 836f. The first electronic device 500a is capable of performing multiple operations (e.g., navigating to the cellular settings user interface, configuring Wi-Fi, activating airplane mode, viewing battery status and settings, generating an indication of the second electronic device 500b, and launching a flashlight application) in response to a user's selection of one of the enable indications presented in the control user interface. As shown Figure 8P As shown, the first electronic device 500a is connected to the second electronic device 500b, and at the same time Figure 8P The user interface shown. Cellular setup enable indication 836a indicates that the first electronic device 500a is communicating with the second electronic device 500b. The check phone enable indication 836c can be selected to generate an indication (eg, an audible or tactile indication) on the second electronic device 500b.

[0274] Figure 8Q1 shows a control center user interface when the first electronic device 500a communicates with the second electronic device 500b. Figure 8Q The Control Center user interface shown is similar to Figure 8P The control center user interface shown is substantially the same. The indication 832b of the "personal" cellular identifier indicates that the first electronic device 500a does not have access to the "personal" cellular identifier, and the indication 832b does not include an indication of the signal level of the "personal" cellular identifier. The cellular settings enable indication 836a indicates that the first electronic device 500a only has access to the "business" cellular identifier. The check phone enable indication 836c is not activated and has a grayed-out appearance.

[0275] Figure 8R-Figure 8U A user interface of a second electronic device 500b for setting and changing a cellular identifier setting of a first electronic device 500a is shown according to some embodiments of the present disclosure. Figure 8R A user interface for configuring a first electronic device 500a using a second electronic device 500b is shown. The user interface includes a setup message 838, and an affordance 840 that can be selected to continue the process of setting up the first electronic device 500a on the second electronic device 500b. Figure 8R The user interface in is optionally a user interface of an application on device 500b, which is an application for controlling various aspects of device 500a, including cellular identifier settings of device 500a, power settings of device 500a, time settings of device 500a, etc. In response to Figure 8R In the selection, the second electronic device 500b presents one or more user interfaces for setting the first electronic device 500a, such as Figure 8S The user interface shown.

[0276] Figure 8S The second electronic device 500b is shown presenting a user interface for associating a cellular identifier with the first electronic device 500a. The user interface includes a first enabling representation 842a that can be selected to add a first cellular identifier ("personal") to the first electronic device 500a, a second enabling representation 842b that can be selected to add a second cellular identifier ("business") to the first electronic device 500b, and a third enabling representation 844 that can be selected to temporarily abandon the selection of a cellular identifier for the first electronic device 500a. Figure 8S As shown, the user (eg, using contact 803) selects a second enable indication 842b for adding a "business" cellular identifier to first electronic device 500a.

[0277] Figure 8TFIG. 5 shows a first electronic device 500a setting user interface presented on a second electronic device 500b. Figure 8T As shown, the user interface includes multiple affordances that can be selected to view or change various settings of the first electronic device 500a on the second electronic device 500b, including affordance 846 for viewing and changing the cellular identifier settings of the first electronic device 500a. Affordance 846 includes an indication (e.g., an icon with a "B") of the cellular identifier (e.g., a "business" cellular identifier) ​​that is activated on the first electronic device 500a. Figure 8T As shown, the user selects (eg, using contact 803) an affordance 846 for viewing and changing cellular identifier settings for first electronic device 500a.

[0278] In response to Figure 8T The user selects in the second electronic device 500b, and the second electronic device 500b presents a cellular setting user interface, such as Figure 8U The user interface includes an indication 848 of a cellular identifier that is activated on the first electronic device 500a (e.g., a “business” cellular identifier), and an indication 850 of a cellular identifier that is not currently activated on the first electronic device 500b (e.g., a “personal” cellular identifier). Indications 848 and 850 may be selected to present more information about the respective cellular identifiers, such as the carrier associated with the cellular identifier and cellular usage of the cellular identifier over a predetermined amount of time (e.g., a billing cycle), and settings for the cellular identifier, such as an affordance for activating a “personal” cellular identifier on the first electronic device 500a.

[0279] Figure 9A-9H 1 is a flowchart illustrating a method 900 of accessing a first cellular identifier on a first electronic device regardless of how the first electronic device is connected to a second electronic device and accessing a second cellular identifier on the first electronic device when the first electronic device is connected to the second electronic device according to some embodiments of the present disclosure. Method 900 is optionally performed at an electronic device (such as device 100, device 300, device 500), as described above with reference to Figure 1A-1B , Figure 2-Figure 3 , Figure 4A-4B and Figure 5A-5H Some operations in method 900 are optionally combined, and / or the order of some operations is optionally changed.

[0280] As described below, method 900 provides a method for accessing a first cellular identifier on a first electronic device regardless of how the first electronic device is connected to a second electronic device and accessing a second cellular identifier on the first electronic device when the first electronic device is connected to the second electronic device. The method reduces the cognitive burden on the user when interacting with the device user interface of the present disclosure, thereby creating a more efficient human-machine interface. For battery-powered electronic devices, improving the efficiency of user interaction with the user interface saves power and increases the time between battery charges.

[0281] In some embodiments, a first electronic device (e.g., electronic device 500a) in communication with one or more input devices (e.g., a mobile device with a touch screen, such as a wearable device) receives (902) at the first electronic device an input (e.g., a request to compose or send a text message or to initiate a phone call) associated with a function requiring use of a corresponding cellular identifier (e.g., a request to compose or send a text message or to initiate a phone call). Fig.8D In the embodiment of the present invention, the first electronic device is associated with a second electronic device (e.g., electronic device 500b) that can use both the first cellular identifier and the second cellular identifier (904). The second electronic device is optionally a mobile device (e.g., a tablet, a smart phone, a media player, or a wearable device) or a computer with which the first electronic device is paired and is within a communication range. For example, when the first electronic device (e.g., a smart watch) is paired with the second electronic device (e.g., a smart phone), the first electronic device optionally communicates with the second electronic device and is able to maintain a communication channel with the second electronic device (e.g., within the Bluetooth range, within the Wi-Fi range, etc.). In some embodiments, the first electronic device is able to use the first cellular identifier independently of the second electronic device, and is not able to use the second cellular identifier independently of the second electronic device (906). The first cellular identifier is optionally attached to or installed on the first electronic device, and the second cellular identifier is attached to or installed on the second electronic device. When the first electronic device communicates with the second electronic device (e.g., via Bluetooth, Wi-Fi, etc.), the first electronic device is able to perform functions using the second cellular identifier via the connection between the first electronic device and the second electronic device.

[0282] In some embodiments, in response to receiving an input associated with a function requiring use of a corresponding cellular identifier (908), such as Figure 8J In the embodiment of the present invention, the first electronic device selects the enable indication 804a by contact 803, and based on determining that the function requires the use of the first cellular identifier (e.g., the "business" cellular identifier) ​​(e.g., to perform the function that the first cellular identifier is set to perform), the first electronic device performs (910) the function without considering whether the first electronic device is in communication with the second electronic device, such as in Figure 8KIn some embodiments, the first electronic device is capable of performing a function using the first cellular identifier without using the second electronic device. For example, if a contact stored on the first electronic device is associated with the first cellular identifier, calling the contact requires using the first cellular identifier. Fig.8D Initiating a phone call to "John Brown" by selecting the indication 804d) requires using a second cellular identifier (e.g., a "personal" cellular identifier) ​​and the first electronic device communicating with the second electronic device, the first electronic device performing (912) the function. Fig.8D In the example shown, first electronic device 500a and second electronic device 500b are not communicating with each other. In contrast, if first electronic device 500a and second electronic device 500b are communicating with each other, then in response to selection of affordance 804d (e.g., using contact 1003), second electronic device 500a may communicate with each other in a manner similar to Figure 8J-Figure 8K Initiate communication in the manner of the example shown. In some embodiments, when the first electronic device communicates with the second electronic device, both the first cellular identifier and the second cellular identifier are available to the first electronic device. In some embodiments, the first electronic device is able to use the second cellular identifier to perform one or more functions by communicating with the second electronic device (e.g., via Bluetooth, Wi-Fi, etc.). For example, if the second cellular identifier is configured to perform voice and messaging functions and the first cellular identifier is configured to perform data-only functions, then making a phone call requires the use of the second cellular identifier. Based on determining that the function (e.g., initiating a phone call to "John Brown" in response to selection of enable indication 804a) requires the use of a second cellular identifier (e.g., a "personal" cellular identifier), and the first electronic device is not communicating with the second electronic device (e.g., the second electronic device is powered off, in airplane mode, out of wireless communication range), such as in Fig.8D As shown in , the first electronic device abandons (914) executing the function, such as in Fig. 8E In some embodiments, the first electronic device optionally presents a visual indication (e.g., text, image, etc.) indicating that the desired function cannot be performed when the first electronic device is not communicating with the second electronic device. In some embodiments, the first electronic device presents an option to use the first cellular identifier to perform the function instead. For example, if a contact stored on the first electronic device is attached to the second cellular identifier and the user attempts to call the contact, the first electronic device presents a message that the contact cannot be called or presents an option to call the contact using the first cellular identifier instead.

[0283] The above-described manner of utilizing the first cellular identifier to perform a function at the first electronic device regardless of whether the first electronic device is communicating with the second electronic device and utilizing the second cellular identifier to perform a function when the first electronic device is communicating with the second electronic device allows the first electronic device to perform a function using the second cellular identifier when communicating with the second electronic device, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by performing operations associated with the two cellular identifiers without providing explicit user input to switch between cellular identifiers), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0284] In some embodiments, the first electronic device receives (916) input at the first electronic device (e.g., selecting affordance 804d using contact 803) for executing a function associated with a default corresponding cellular identifier (e.g., a request to compose or send a text message or initiate a phone call). One of the first cellular identifier and the second cellular identifier is optionally configured to execute the function by default. For example, the function is to call a specific contact in a contact list stored on the first electronic device, and when the user initiates a phone call to the specific contact, the first electronic device uses the corresponding cellular identifier to make the call by default.

[0285] In some embodiments, in response to receiving an input for performing a function associated with a default corresponding cellular identifier (e.g., Fig.8D In the embodiment of the present invention, contact 803 is used to select an indication 804d)(918) (for example, touch input received at a touch screen of the first electronic device, voice input received at a microphone of the first electronic device, or another input), and based on determining that the default corresponding cellular identifier is a second cellular identifier (for example, a "personal" cellular identifier) ​​and the first electronic device is in communication with a second electronic device, the first electronic device uses the second cellular identifier to perform (920) the function (for example, the first electronic device is able to use the second cellular identifier to perform the function via its connection to the second electronic device). Fig.8D In the example shown, first electronic device 500a and second electronic device 500b are not communicating with each other. In contrast, if first electronic device 500a and second electronic device 500b are communicating with each other, selection of affordance 804d will optionally cause first electronic device 500a to communicate with each other in a manner similar to Figure 8J-Figure 8K Initiate communication in the manner of the example shown in . According to determining that the default corresponding cellular identifier is the second cellular identifier and the first electronic device is not communicating with the second electronic device, such as in Fig.8D As shown in , the first electronic device provides (922) a warning indicating that the second cellular identifier is not activated on the first electronic device, such as in Fig. 8EIn some embodiments, the first electronic device cannot utilize the second cellular identifier to perform the function without being connected to the second electronic device. In some embodiments, after displaying a warning that the second cellular identifier is not activated on the first electronic device, the first electronic device presents an enabling representation that allows the first cellular identifier to be used to perform the function.

[0286] The above-described manner of alerting the user when the second cellular identifier is not available on the first electronic device allows the first electronic device to communicate to the user why a function that is typically performed using the second cellular identifier is not performed, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by providing a specific error message to the user so that the user can avoid using a specific cellular identifier when the user does not intend to use the cellular identifier), which also prevents the electronic device from displaying information about the specific cellular identifier (for example, allowing a contact to learn a phone number associated with a specific cellular identifier that is not a cellular identifier associated with the contact), and prevents the electronic device from using the specific cellular identifier when the user does not intend to use the cellular identifier, which in some cases results in usage fees from the service provider of the cellular identifier.

[0287] In some embodiments, providing an alert indicating that the second cellular identifier is not activated on the first electronic device includes providing an option for using the first cellular identifier to perform a function associated with the second cellular identifier (e.g., Fig.8F The first electronic device optionally presents a message indicating that the second cellular identifier is not available and an option to perform the function using the first cellular identifier instead. In some cases, the user may not want to perform the function using the first cellular identifier for privacy reasons (e.g., the user does not want a particular contact to know the phone number of the first cellular identifier, so they choose not to use the first cellular identifier to make a phone call to that contact).

[0288] The above-described manner of providing the user with an option to perform a function using the first cellular identifier when the second cellular identifier is not available allows the first electronic device to provide the user with a method for performing a function associated with the second cellular identifier even when the second cellular identifier is not available, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by presenting an option to perform the function using the first cellular identifier within a user interface for performing the function, rather than requiring the user to change the cellular identifier settings to configure the first cellular identifier to perform the function), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0289] In some embodiments, based on determining that a first cellular identifier is specified for use by the first electronic device in a settings user interface for the first electronic device displayed on the second electronic device, such as in Figure 8U As shown in , enabling the first electronic device to use the first cellular identifier independently of the second electronic device, and disabling the first electronic device to use the second cellular identifier independently of the second electronic device (926). The user is optionally able to control one or more settings of the first electronic device from the second electronic device, including specifying a cellular identifier that the first electronic device can use independently of the second electronic device. In some embodiments, when the first cellular identifier is specified to be used by the first electronic device independently of the second electronic device, the first electronic device is automatically configured to use the second cellular identifier not independently of the second electronic device. Based on determining that the second cellular identifier is specified for use by the first electronic device in a settings user interface for the first electronic device displayed on the second electronic device, such as in Figure 8U As shown in , the first electronic device is enabled to use the second cellular identifier independently of the second electronic device and the first electronic device is disabled from using the first cellular identifier independently of the second electronic device (928). In some embodiments, when the second cellular identifier is designated to be used by the first electronic device independently of the second electronic device, the first electronic device is automatically configured to use the first cellular identifier not independently of the second electronic device.

[0290] The above-described manner of providing an indication within the user interface of the second electronic device as to which cellular identifier is activated on the first electronic device allows the user to configure the first electronic device from the second electronic device, which simplifies the interaction between the user and the device and enhances the operability of the device (e.g., the user may prefer to perform functions on the second electronic device), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0291] In some embodiments, the first electronic device receives (930) input corresponding to a request to view a cellular settings user interface of the first electronic device via one or more input devices (e.g., selection using a touch screen, voice input, etc., such as Figure 8H The cellular settings user interface of the first electronic device is optionally included in a settings application or user interface that includes other settings of the first electronic device (such as date and time settings, display settings, sound settings, etc.).

[0292] In some embodiments, in response to receiving input corresponding to a request to view a cellular settings user interface, the first electronic device displays (932) a cellular settings user interface, such as in Figure 8IAs shown in , the cellular settings user interface includes: based on determining that the first electronic device is communicating with the second electronic device (e.g., via Wi-Fi, Bluetooth, etc.), an indication indicating that the first cellular identifier is activated on the first electronic device (e.g., indication 812a of the "personal" cellular identifier is presented as having an active appearance of indication 812b of the "business" cellular identifier) ​​and an indication indicating that the second cellular identifier is activated on the first electronic device (e.g., indication 812b) (934). Figure 8I In the example shown, the first electronic device 500a and the second electronic device 500b are not communicating with each other, and the indication 812a of the “personal” cellular identifier is grayed out. In contrast, if the first electronic device 500a and the second electronic device 500b were communicating with each other, the indication 812a of the “personal” cellular identifier would have the same non-grayed-out appearance that, for example, the indication 812b of the “business” cellular identifier would have. In some embodiments, the indication indicating that the first cellular identifier is activated on the first electronic device and the indication indicating that the second cellular identifier is activated on the first electronic device optionally include text or images indicating the activation status of the respective cellular identifiers, and optionally include an indication of the signal strength of the respective cellular identifiers. Based on determining that the first electronic device is not communicating with the second electronic device, such as Figure 8I As shown (for example, the second electronic device is powered off, in airplane mode, or is at a distance from the first electronic device that exceeds the range of the communication channel between the first electronic device and the second electronic device), the cellular setup user interface includes an indication (812b) indicating that the first cellular identifier is activated on the first electronic device (for example, text or an image indicating the activation state of the first cellular identifier). In some embodiments, the indication also includes an indication of the signal strength of the first cellular identifier. The cellular setup user interface optionally includes an indication (812a)(936) indicating that the second cellular identifier is not activated on the first electronic device (for example, text or an image indicating the inactivation state of the second cellular identifier), as shown. Figure 8I as shown. In some embodiments, the first electronic device also displays a separate indication that the second electronic device is not communicating with the first electronic device. In some embodiments, the user pays for access to one cellular identifier on the first electronic device 500a, and the user is able to change which cellular identifier is associated with the first electronic device 500a when the first electronic device 500a is communicating with the second electronic device 500b, but the user cannot make this change when the first electronic device 500a is not communicating with the second electronic device. In some embodiments, the user pays for access to two cellular identifiers on the first electronic device 500a, and the user is able to change which cellular identifier is associated with the first electronic device 500a regardless of whether the first electronic device 500a is communicating with the second electronic device 500b.

[0293] The above-described manner of indicating the activation or inactivation status of the first cellular identifier and the second cellular identifier in the cellular settings user interface allows the first electronic device to communicate to the user which cellular identifiers are available for performing functions on the first electronic device, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, presenting the activation or inactivation status of the cellular identifier in the settings user interface allows the user to understand the status of the cellular identifier before making changes to the settings), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0294] In some embodiments, input associated with a function requiring use of the corresponding cellular identifier is received while the first electronic device is displaying a representation of the corresponding cellular identifier (938) (e.g., an optional enabling representation for performing the function includes a representation of the corresponding cellular identifier or is displayed adjacent to the representation of the corresponding cellular identifier, such as an indication of the corresponding cellular identifier similar to the indication described above with reference to method 700), such as Fig.8D The "P" indication of the "personal" cellular identifier included in the indication 804d in the first electronic device is determined to be usable for performing the function on the first electronic device, such as in the Figure 8C As shown in , the representation of the corresponding cell identifier (for example, included in Figure 8C The “P” indication of the “Personal” cellular identifier in indication 804c in the first electronic device is displayed (940) with a first visual characteristic (e.g., with text, an icon, a color scheme, etc. indicating that the corresponding cellular identifier is available). For example, the representation of the corresponding cellular identifier is optionally displayed in color. Based on determining that the corresponding cellular identifier is not available to perform the function on the first electronic device, such as in Fig.8D As shown in , the representation of the corresponding cellular identifier (e.g., indication 804d) is displayed (942) with a second visual characteristic different from the first visual characteristic (e.g., with text, icon, color scheme, etc. indicating that the corresponding cellular identifier is not available). For example, the representation of the corresponding cellular identifier is optionally displayed in gray.

[0295] The above-described manner of changing the visual features of the corresponding cellular identifier when the first electronic device receives input for performing a function using the corresponding cellular identifier allows the first electronic device to communicate to the user whether the corresponding cellular identifier is available in a user interface for performing a function using the corresponding cellular identifier, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by presenting an indication of the status of the corresponding cellular identifier in situations where the user may wish to use the corresponding cellular identifier), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0296] In some embodiments, the first electronic device receives (944) a request to display a user interface via one or more input devices, the user interface including one or more representations associated with one or more contacts (e.g., a recent communications user interface including representations of recent communications with contacts, such as phone calls or text messages, or a contacts user interface including representations of contacts on the first electronic device), such as Fig.8D The user interface shown.

[0297] In some embodiments, in response to receiving the request to display the user interface, the first electronic device displays (946) the user interface, such as Fig.8D The user interface shown includes a first representation (e.g., 804a, 804b, or 804d) associated with a first contact (e.g., a representation of a message or call sent to or received from the first contact). For example, the messaging user interface includes a representation of a messaging conversation with the first contact. Based on determining that the first representation (e.g., 804a or 804b) associated with the first contact is associated with a cellular identifier activated on the first electronic device (e.g., a "business" cellular identifier), the first representation is displayed with a first visual feature (948). In some embodiments, the first representation associated with the first contact is displayed with a visual feature (e.g., a color, pattern, text, or image) indicating that the cellular identifier associated with the first contact is activated on the first electronic device. For example, the representation associated with the first contact is displayed in full color. Based on determining that the first representation (e.g., 804d) associated with the first contact is associated with a cellular identifier that is not activated on the first electronic device (e.g., a "personal" cellular identifier), the first representation is displayed with a second visual feature different from the first visual feature (950). In some embodiments, the first representation associated with the first contact is displayed with a visual feature (e.g., color, pattern, text, or image) indicating that the cellular identifier associated with the first contact is not activated on the first electronic device. For example, the representation associated with the first contact is displayed in gray.

[0298] The above-described manner of changing the appearance of the representation of a contact based on the activation or inactivation state of the cellular identifier associated with the contact allows the first electronic device to communicate to the user whether the first electronic device is able to use the cellular identifier associated with the contact to perform communication operations with the contact, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by presenting the state of the cellular identifier in the user interface for communicating with the contact using the cellular identifier, rather than requiring the user to figure out the state of the cellular identifier in some other way), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0299] In some embodiments, the user interface also includes a second representation (804d) (952) associated with the second contact (e.g., a representation of a message or call sent to or received from the first contact). For example, the messaging user interface includes a representation of a messaging conversation with the first contact. The first representation (804a) associated with the first contact is associated with a cellular identifier (e.g., "business") activated on the first electronic device, and the first representation is displayed (954) with a first visual feature (e.g., a color, shape, image, or text indicating the activation state of the cellular identifier activated on the first electronic device). For example, the first representation (804a) associated with the first contact is displayed in color. The second representation (804d) associated with the second contact is associated with a cellular identifier (e.g., "personal") that is not activated on the first electronic device, and the second representation (804d) is displayed (956) with a second visual feature (e.g., a color, shape, image, or text indicating the inactivation state of the cellular identifier that is not activated on the first electronic device). For example, the second representation associated with the second contact is displayed in gray.

[0300] The above-described manner of changing the appearance of the representation of a contact based on the activation or inactivation state of the cellular identifier associated with the contact allows the first electronic device to communicate to the user whether the first electronic device is able to use the cellular identifier associated with the contact to perform communication operations with the contact, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by presenting the state of the cellular identifier in the user interface for communicating with the contact using the cellular identifier, rather than requiring the user to figure out the state of the cellular identifier in some other way), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0301] In some embodiments, during the setup process of the first electronic device, the first electronic device receives (958) input via one or more input devices for activating, on the first electronic device, a corresponding cellular identifier of the first cellular identifier and the second cellular identifier that are activated on the second electronic device (e.g., Figure 8B When setting up the first electronic device for subsequent use, the user is prompted to select one of the first cellular identifier and the second cellular identifier to activate on the first electronic device for use on the first electronic device, even when the first electronic device and the second electronic device are not communicating with each other.

[0302] In some embodiments, in response to receiving input for activating a corresponding cellular identifier on the first electronic device (e.g., detecting Figure 8B803) (960), based on determining that the corresponding cellular identifier is a first cellular identifier (962), the first electronic device enables (964) the first electronic device to use the first cellular identifier (e.g., a "business" cellular identifier) ​​independently of the second electronic device, such as in Figure 8J-Figure 8K The first electronic device is optionally configured to use the first cellular identifier even when the first electronic device is not communicating with the second electronic device. The first electronic device optionally enables (966) the first electronic device to not be able to use the second cellular identifier (e.g., a "personal" cellular identifier) ​​independently of the second electronic device, such as Figure 8D-Figure 8F As shown. When the first electronic device and the second electronic device are communicating with each other, the first electronic device is optionally capable of using the second cellular identifier, but when the first electronic device and the second electronic device are not communicating with each other, the first electronic device is not capable of using the second cellular identifier. Based on determining that the corresponding cellular identifier is the second cellular identifier (968), the first electronic device enables (970) the first electronic device to use the second cellular identifier independently of the second electronic device. The first electronic device is optionally configured to use the second cellular identifier even when the first electronic device is not communicating with the second electronic device. The first electronic device optionally enables (972) the first electronic device to not be able to use the first cellular identifier independently of the second electronic device. In some embodiments, when the first electronic device and the second electronic device are communicating with each other, the first electronic device is capable of using the first cellular identifier, but when the first electronic device and the second electronic device are not communicating with each other, the first electronic device is not capable of using the first cellular identifier. Although in reference to Figure 8A-8U In the example shown, the first electronic device 500a is able to use a "business" cellular identifier independent of its connection to the second electronic device 500b, but in some embodiments, rather than selecting a "business" cellular identifier, a "personal" cellular identifier is selected for use by the first electronic device 500a regardless of its connection to the second electronic device 500b.

[0303] The above-described manner of presenting a user interface on a second electronic device for selecting a cellular identifier to activate on a first electronic device allows the first electronic device to be configured from the second electronic device, which simplifies the interaction between the user and the device and enhances the operability of the device (e.g., the user may prefer to use the second electronic device to change settings), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0304] In some embodiments, during a communication with a first contact using the first corresponding cellular identifier (e.g., during a phone call with the first contact using the first corresponding cellular identifier), the first electronic device receives (974) via one or more input devices a request to add a second contact to the communication (e.g., Figure 8L In some embodiments, the first corresponding cellular identifier is the default cellular identifier of the first electronic device, the default cellular identifier for voice and messaging functions, the default cellular identifier for the first contact, or has been selected by the user for making phone calls. For another example, the user adds the second contact to the messaging conversation with the first contact.

[0305] In some embodiments, in response to receiving a request to add a second contact to the communication (976), based on determining that the second contact is associated with the first corresponding cellular identifier (e.g., the first corresponding cellular identifier is the default cellular identifier for the first electronic device, the default cellular identifier for voice and messaging functions, or the default cellular identifier for the second contact), the first electronic device adds (978) the second contact to the communication using the first corresponding cellular identifier (e.g., calling the second contact to add them to a conference call with the user and the first contact, or adding the second contact to a messaging conversation between the first contact and the user). Figure 8M In the example shown, the user (e.g., using contact 803) selects option 822b to add "John Brown" to the call, but the user can also select option 822a to add "Alex Garcia" to the call. If the user were to select option 822a to add "Alex Garcia" to the call, then in response to the selection, the first electronic device 500a optionally initiates a phone call to "Alex Garcia" to add the contact to the phone call with "Mary Smith" without presenting the contact. Figure 8N , because both "Alex Garcia" and "Mary Smith" are associated with the "business" cellular identifier. Based on determining that the second contact is associated with a second corresponding cellular identifier that is different from the first corresponding cellular identifier (e.g., the second corresponding cellular identifier is a default cellular identifier for the first electronic device, a default cellular identifier for voice and messaging functions, or a default cellular identifier for the second contact) (980), such as in Figure 8N, the first electronic device abandons (982) adding the second contact to the communication, and the first electronic device provides (984) a warning indicating that if the second contact is added to the communication, the first corresponding cellular identifier will be used for communication with the second contact (e.g., displaying text or an image, presenting a sound or tactile sensation, etc. to indicate that although the second cellular identifier is the default cellular identifier for communicating with the second contact, the first cellular identifier will be used for the communication), such as in Figure 8N In some cases, the user will not want to use the first cellular identifier to communicate with the second contact for privacy reasons, such as not wanting the second contact to know the phone number associated with the first cellular identifier.

[0306] The above-described manner of alerting a user when a user requests to add a contact to a communication being performed using a cellular identifier that is not associated with the contact allows the first electronic device to inform the user how the first electronic device performs communication functions with respective contacts, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by providing a specific warning message to the user, enabling the user to avoid using a specific cellular identifier to call a contact that is not associated with the specific cellular identifier), which also prevents the electronic device from displaying information about the specific cellular identifier (for example, allowing the contact to learn a phone number associated with a specific cellular identifier that is not a cellular identifier associated with the contact), and prevents the electronic device from using the specific cellular identifier when the user does not intend to use the cellular identifier, which in some cases results in usage fees from the service provider of the cellular identifier.

[0307] It should be understood that Figure 9A-9H The specific order in which the operations in the description are described is merely exemplary and is not intended to indicate that the order is the only order in which the operations may be performed. A person of ordinary skill in the art will recognize many ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (e.g., methods 700, 1100, 1300, and 1500) are also applicable in a similar manner to the details of the processes described above in conjunction with Figure 9A-9H The method 900 described above. For example, the manner in which the first electronic device interacts with the cellular identifier associated with the second electronic device described above with reference to method 900 optionally has one or more features of the cellular identifier setting user interface, indication of the cellular identifier, operations performed using the cellular identifier, etc. described herein with reference to other methods described herein (e.g., methods 700, 1100, 1300, and 1500). For the sake of brevity, these details are not repeated here.

[0308] The operations in the above information processing method are optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (for example, in combination with Figure 1A to Figure 1B , Figure 3 , FIG. 5A to FIG. 5H In addition, the above reference Figure 9A-9H The described operations are optionally performed by Figure 1A-1B . For example, display operations 932 and 946 and receiving operations 902, 916, 930, 944, 958 and 974 are optionally implemented by event classifier 170, event identifier 180 and event handler 190. Event monitor 171 in event classifier 170 detects contact on touch screen 504, and event distributor module 174 transmits event information to application 136-1. The corresponding event identifier 180 of application 136-1 compares the event information with the corresponding event definition 186 and determines whether the first contact at the first position on the touch screen corresponds to a predefined event or sub-event, such as a selection of an object on a user interface. When a corresponding predefined event or sub-event is detected, event identifier 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally utilizes or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly know how to update the content displayed by the application based on the GUI updater 178. Figure 1A to Figure 1B The components depicted in the figure are used to implement other processes.

[0309] Presenting a visual indication of a cellular identifier in a communication-related user interface

[0310] Users interact with electronic devices in many different ways, including using network connections to communicate with other electronic devices. In some embodiments, the electronic device displays an indication of which cellular identifier has been used or will be used to complete a communication function. The embodiments described below provide methods for electronic devices to present visual indications of cellular identifiers in user interfaces related to communication. Enhanced interaction with the device reduces the amount of time required for the user to perform an operation, thereby reducing the power consumption of the device and extending the battery life of battery-powered devices. It should be understood that people use devices. When a person uses a device, this person is optionally referred to as a user of the device.

[0311] Figures 10A-10MM An exemplary method of presenting a visual indication of a cellular identifier associated with a communication function by an electronic device according to some embodiments of the present disclosure is shown. The embodiments in these figures are used to illustrate the process described below, including reference Figure 11A-Figure 11Q The process described.

[0312] Fig. 10A An exemplary device 500 having a touch screen 504 is shown, such as that shown in FIG. Figure 5A-5H The touch screen 504 optionally displays one or more user interfaces including various contents. Fig. 10A In the example shown, touch screen 504 displays a user interface for configuring electronic device 500 to present a voicemail associated with a cellular identifier available to device 500. Fig. 10A As shown in legend 1002, when the electronic device 500 presents a user interface for configuring the electronic device to present voicemail, the "personal" cellular identifier represented by the indicator with a "P" is configured as a default number for phone calls and SMS, the "business" cellular identifier represented by the indicator with a "B" is configured as a secondary number for phone calls and SMS, and the "travel" cellular identifier represented by the indicator with a "T" is not activated.

[0313] Fig. 10A The user interface shown in includes a first enabling representation 1004a that is selectable to initiate a process of setting up a voice mailbox associated with a first cellular identifier (e.g., a "personal" cellular identifier represented by an indicator with a "P"), and a second enabling representation 1004b that is selectable to initiate a process of setting up a voice mailbox associated with a second cellular identifier (e.g., a "business" cellular identifier represented by an indicator with a "B"). Fig. 10A As shown, the user selects (e.g., using contact 1003) a second enable indication 1004 to initiate the process of setting up voicemail associated with the second cellular identifier.

[0314] Fig. 10B A voicemail user interface is shown after a voicemail associated with a second cellular identifier (e.g., a “business” cellular identifier) ​​has been set up. The voicemail user interface includes a plurality of enable representations 1006a-1006c associated with voicemails received by the electronic device using the “business” cellular identifier, and an enable representation 1004a that is selectable to additionally set up a voicemail for another cellular identifier (e.g., a “personal” cellular identifier) ​​activated on the electronic device 500. The enable representations 1006a-1006c associated with voicemails received by the electronic device using the “business” cellular identifier include a visual indication of the “business” cellular identifier (e.g., an icon with a “B”), which enables the user to recognize that these voicemails were received using the “business” cellular identifier. Each enable representation 1006a-1006c is selectable to play the corresponding voicemail indicated by the corresponding enable representation. As shown Fig. 10BAs shown, the user selects (eg, using contact 1003) an affordance 1004a for setting up voicemail associated with a "personal" cellular identifier.

[0315] Fig. 10C A voicemail user interface is shown after a voicemail associated with a first cellular identifier (e.g., a “personal” cellular identifier) ​​and a voicemail associated with a second cellular identifier (e.g., a “business” cellular identifier) ​​have been set up. The voicemail user interface includes a plurality of enable representations 1006a-1006c associated with voicemails received by the electronic device using the “business” cellular identifier, and an enable representation 1008 associated with voicemails received by the electronic device using the “personal” cellular identifier. The enable representations 1006a-1006c associated with voicemails received by the electronic device using the “business” cellular identifier include a visual indication of the “business” cellular identifier (e.g., an icon with a “B”), which enables the user to recognize that these voicemails were received using the “business” cellular identifier. Similarly, in Fig. 10C In the example shown, the affordance 1008 associated with a voicemail received by the electronic device using a "personal" cellular identifier includes an indication of the "personal" cellular identifier (e.g., an icon with a "P"), which enables the user to recognize that the voicemail was received using the "personal" cellular identifier. However, in some embodiments, the indication of the "personal" cellular identifier is not displayed next to the voicemail associated with the "personal" cellular identifier because the "personal" cellular identifier is configured as a default number for phone calls and SMS, and it is expected that the user will understand that, by default, the voicemail is associated with the default number for phone calls and SMS (e.g., the "personal" cellular identifier) ​​unless it is indicated as being associated with a "business" cellular identifier. Each affordance 1006a-1006c and 1008 can be selected to play the corresponding voicemail indicated by the corresponding affordance.

[0316] Fig. 10D 4 shows a recent call user interface on a device 500 according to some embodiments of the present disclosure. Fig. 10D As shown, the recent call user interface includes a plurality of affordances 1010a-b associated with recent calls placed or received using a "business" cellular identifier, affordance 1012 associated with recent calls made using a "personal" cellular identifier, and affordance 1014 associated with recent video conference calls that have been made using a "personal" cellular identifier. Affordances 1010a and affordance 1010b associated with recent calls placed or received using a "business" cellular identifier include an indication of the "business" cellular identifier (e.g., an icon with the letter "B"). Fig. 10DIn the example shown, affordances 1012 associated with a recent call made or received using a “personal” cellular identifier and affordances 1014 associated with a recent video conference call made or received using a “personal” cellular identifier do not include an indication of the “personal” cellular identifier because the “personal” cellular identifier is the default number used for phone calls and SMS. In some embodiments, the cellular identifier that is the default number for phone calls and SMS is the cellular identifier used for these operations and the default cellular identifier for video conferencing by default. Electronic device 500 optionally does not present an indication of the default cellular identifier for phone calls and SMS along with an indication of communications performed using the default cellular identifier because the user is expected to understand that the default cellular identifier is used for phone calls and SMS unless otherwise specified.

[0317] Fig. 10E A recent call user interface is shown according to some embodiments of the present disclosure. Fig. 10E The user interface shown in is basically similar to Fig. 10D , except that affordance 1016 associated with a telephone call placed or received using a “personal” cellular identifier includes an indication of the “personal” cellular identifier (e.g., an icon with the letter “P”). Fig. 10E As shown, affordances 1014 associated with a recent video conference call placed or received using a “personal” cellular identifier do not include an indication of the “personal” cellular identifier. In some embodiments, the cellular identifier that is the default number for phone calls and SMS is always used for video conference calls, and thus there is no indication of that cellular identifier in affordances 1014 associated with video conference calls because the user is expected to know which cellular identifier to use for video conference calls. In some embodiments, an indication of the cellular identifier (e.g., an icon with a “P”) is included in affordances 1014 associated with video conference calls. As shown in FIG. Fig. 10E As shown, the user (e.g., using contact 1003) selects affordance 1010b associated with a phone call made or received using a "business" cellular identifier. In response to the selection, electronic device 500 initiates a phone call to the contact (e.g., "Alex Garcia") participating in the phone call, as shown. Fig.10F shown.

[0318] Fig.10F FIG. 4 shows a phone call user interface on a device 500 according to some embodiments of the present disclosure. The phone call user interface is presented when the electronic device 500 is used for a phone call. Fig.10FAs shown in legend 1002 of , during the phone call, the "business" cellular identifier is used for the phone call and the "personal" cellular identifier is disabled because, in some embodiments, when one cellular identifier is used for a phone call, another cellular identifier activated on the electronic device is temporarily disabled until the phone call ends. In some embodiments, the cellular identifier not used for the phone call remains enabled on the electronic device to perform other operations (e.g., sending or receiving messages, downloading or uploading cellular data, receiving another phone call, etc.).

[0319] The phone call user interface includes an indication 1018 of the contacts participating in the phone call, an indication 1020 of the cellular identifier used for the phone call, and an affordance 1022 for initiating a video conference call with the contacts on the phone call. In some embodiments, if the user chooses to initiate a video conference call, the electronic device 500 initiates the video conference call using a cellular identifier that is configured as a default number for phone calls and SMS (e.g., a "personal" cellular identifier), regardless of which cellular identifier is being used for the phone call and / or regardless of which cellular identifier is associated with the contacts participating in the video conference call. Fig.10F As shown, the user (e.g., using contact 1003) selects enable indication 1022 for initiating a video conference call with the contact.

[0320] Figure 10G FIG. 5 shows a video conference call user interface according to some embodiments of the present disclosure. The video conference call user interface is presented when the electronic device 500 is used for a video conference call. Figure 10G As shown in legend 1002 of , during a video conference call, a "personal" cellular identifier is used for the video conference call and a "business" cellular identifier is disabled because, in some embodiments, when one cellular identifier is used for the video conference call, another cellular identifier activated on the electronic device is disabled. In some embodiments, the cellular identifier not used for the video conference call remains enabled on the electronic device to perform other operations (e.g., sending or receiving messages, downloading or uploading cellular data, receiving phone calls, etc.).

[0321] Although the phone call Fig.10F The use of a "business" cellular identifier is shown, but in Figure 10G In the example shown, a "personal" cellular identifier is used to make a video conference call. In some embodiments, the cellular identifier that is the default number for phone calls and SMS is always used by the electronic device to make a video conference call, regardless of which cellular identifier is associated with the contact with whom the electronic device makes a video conference call. In some embodiments, the electronic device can use any activated cellular identifier to make a video conference call.

[0322] Figure 10H-10I A contact user interface on a device 500 according to some embodiments of the present disclosure is shown. The contact user interface includes an indication 1026 of the name of the contact ("Mary Smith"), a first telephone number 1028a for the contact, a first indication 1030a of a cellular identifier associated with the contact, a second telephone number 1028b for the contact, a second indication 1030b of a cellular identifier associated with the contact, and an enable indication 1032 for editing information associated with the contact. Because a "business" cellular identifier is associated with the contact, including two telephone numbers associated with the contact, the indications 1028a-b of the two telephone numbers each include an indication 1030a-b of the "business" cellular identifier. Unless otherwise specified by the user, the cellular identifier associated with the contact is, optionally, the cellular identifier used by the electronic device 500 to initiate communications with the contact. As shown in FIG. Fig.10I As shown, the user (e.g., using contact 1003) selects enable representation 1032 for editing information associated with the contact.

[0323] In response to Fig.10I , the electronic device 500 presents a user interface for editing the information associated with the contact ("Mary Smith"), such as Fig.10J As shown. In addition to other settings for the contact, the user interface includes an indication 1034 of the contact whose information is to be edited and an affordance 1036 that can be selected to change which cellular identifier is associated with the contact. Affordance 1036 for changing the cellular identifier associated with the contact includes a visual indication 1038 of the cellular identifier (e.g., the "business" cellular identifier) ​​that is currently set as the default cellular identifier for the contact. Fig.10J As shown, the user selects (e.g., using contact 1003) an affordance 1036 for changing the cellular identifier that is set as the default cellular identifier for the contact. Fig.10J , the electronic device 500 presents a user interface for changing the cellular identifier associated with the contact, as will be described below with reference to Figure 10K Describe in more detail.

[0324] Figure 10KA user interface for changing a cellular identifier associated with a contact according to some embodiments of the present disclosure is shown. The user interface includes an indication 1040 of the contact whose information is being edited, an enable indication 1042a that is selectable to use a most recently used cellular identifier when initiating communication with the contact, an enable indication 1042b that is selectable to set a first cellular identifier (e.g., a "personal" cellular identifier) ​​as the default cellular identifier for the contact, and an enable indication 1042c that is selectable to set a second cellular identifier (e.g., a "business" cellular identifier) ​​as the default cellular identifier for the contact. The second enable indication 1042b includes a visual indication 1044a of the first cellular identifier, and the third enable indication 1042c includes a visual indication 1044b of the second cellular identifier. As shown in FIG. Figure 10K As shown, the third enable indication 1042c includes a check mark, indicating that the electronic device 500 is currently configured to use a second cellular identifier (e.g., a "business" cellular identifier) ​​by default to initiate communications with the contact. That is, the electronic device 500 will use the "business" cellular identifier to communicate with the contact except in certain circumstances, such as when the user requests to use a different cellular identifier, when the type of communication is associated with a different cellular identifier (e.g., the electronic device always uses the "data-only" cellular identifier for enhanced data-based messaging and video conferencing calls), or when the cellular identifier associated with the contact is unavailable (e.g., deactivated, no service, etc.). If the user were to select the "most recently used" enable indication 1042a, the electronic device 500 would optionally initiate communications with the contact using the cellular identifier that the electronic device 500 most recently used for communications with the contact. As shown Figure 10K As shown, the user selects (e.g., using contact 1003) a second affordance 1042b for setting the "personal" cellular identifier as the cellular identifier associated with the contact. Changing the setting in this manner causes electronic device 500 to use the "personal" cellular identifier by default to initiate communications with the contact unless the user enters input for using a different cellular identifier when initiating communications.

[0325] like Fig.10L As shown, in response to the user's selection, the electronic device 500 presents a check mark in the second enable representation 1042b to indicate that the electronic device 500 is configured to use the first cellular identifier (e.g., the "personal" cellular identifier) ​​to initiate communication with the contact. Figure 10M The contacts user interface is shown after the electronic device 500 has been configured to use a "personal" cellular identifier when initiating communications with the contacts. Figure 10M The contacts user interface shown in is basically similar to Fig.10I, with the differences noted herein. The indications 1030a-b of the cellular identifier associated with the contact are updated to reflect that the cellular identifier associated with the contact is a "personal" cellular identifier.

[0326] Fig.10N A recent call user interface of device 500 is shown according to some embodiments of the present disclosure. Fig.10N The user interface shown is basically similar to Figure 10D-10E The user interface shown in Figure 1 is as follows. Fig.10N As shown, a user selects (e.g., using contact 1003) an affordance 1010b associated with a contact (e.g., "Alex Garcia"). Contact 1003 has an intensity 1046a that exceeds a predetermined intensity threshold 1048a and is detected at a time 1046b that exceeds a predetermined time threshold 1048b. In response to contact 1003 having these characteristics, electronic device 500 presents Fig.10O In contrast, as described above in conjunction with Figure 10E-Figure 10F As described, in response to a contact not having intensity 1046a and / or time 1056b characteristics, the electronic device initiates a telephone call to the contact associated with the selected affordance. Fig.10O As shown, electronic device 500 presents an indication 1050 of a contact to be called, an indication 1052 of a default cellular identifier for the contact (e.g., a “business” cellular identifier), a first affordance 1054a for calling the contact using a first cellular identifier (e.g., a “personal” cellular identifier), and a second affordance 1054b for calling the contact using a second cellular identifier (e.g., a “business” cellular identifier). Fig.10O As shown, the user selects (eg, using contact 1003) first affordance 1054a to call the contact using a "personal" cellular identifier, which is not a cellular identifier associated with the contact.

[0327] In response to Fig.10O Based on the user selection in , the electronic device 500 uses the selected cellular identifier to make the phone call. Figure 10P A telephone user interface according to some embodiments of the present disclosure is shown. Figure 10P The phone user interface shown in is basically similar to Fig.10F , except that the visual indication 1020 of the cellular identifier used for the phone call is an indication of the "personal" cellular identifier because this is the cellular identifier selected by the user to complete the phone call. Figure 10PAs shown, legend 1002 indicates that the "personal" cellular identifier is in use and the "business" cellular identifier is disabled. As described above, in some embodiments, during the phone call, other cellular identifiers not used for the phone call are disabled on the electronic device 500. In some embodiments, other cellular identifiers remain enabled during the phone call.

[0328] Figure 10Q-Figure 10S A dial pad user interface according to some embodiments of the present disclosure is shown. The dial pad user interface includes an enable representation 1054 that can be selected to switch the cellular identifier to be used for making a call, a text input field 1056, a dial pad 1058, and an enable representation 1060 for making a call. The enable representation 1054 for switching the cellular identifier to be used for making a call includes an indication 1062 of the cellular identifier (e.g., a "personal" cellular identifier) ​​that will be used to make a call when the user selects the enable representation 1060 for making a call. In some embodiments, when the phone number entered into the text input field 1056 is not associated with a contact associated with a different cellular identifier, the electronic device 500 first presents an indication 1062 of the cellular identifier that is the default number for phone calls and SMS. For example, if the user enters a phone number for a contact associated with a "business" cellular identifier, then in response to entering the phone number and there being no other user input for using the "business" cellular identifier to make the call, the enable representation 1054 will be updated to include an indication of the "business" cellular identifier. As Figure 10Q As shown, the phone number is entered into the text input field 1056. In some embodiments, the user can enter the phone number using the dial pad 1058 or paste the phone number into the text input field 1056 using user input. Figure 10R As shown, the user (e.g., using contact 1003) selects an affordance 1054 for switching the cellular identifier to be used to make the call. In response to the user input, the user interface is as shown. Fig. 10S The illustration is updated to display an indication 1062 of a different cellular identifier (e.g., a "business" cellular identifier) ​​to be used to place the call when the user selects the "Call" affordance 1060.

[0329] Figure 10T Another dial pad user interface is shown in accordance with some embodiments of the present disclosure. Figure 10T The dial pad user interface shown is basically similar to Figure 10Q-Figure 10S1048a, and is detected at a time 1046b that exceeds a predetermined time threshold 1048b. In response to this selection made using contact 1003 having one or more of these characteristics, electronic device 500 presents a "call" affordance 1060. Figure 10U In contrast, if electronic device 500 detects a contact at “Call” affordance 1060 that is not characterized by intensity 1046a and / or time 1056b (e.g., the electronic device detects a tap), electronic device 500 places the call using a default number for phone calls and SMS (e.g., a “personal” cellular identifier) ​​without presenting the user interface. Figure 10U The user interface shown.

[0330] like Figure 10U As shown, in response to utilizing Figure 10T The "Call" enable representation 1060 is selected by contact 1003 with the time and / or intensity characteristics in the electronic device 500, and the electronic device 500 presents multiple enable representations 1064a-d for various ways to call the phone number. The first enable representation 1064a can be selected to use a first cellular identifier (e.g., a "primary" cellular identifier) ​​to make the call, the second enable representation 1064b can be selected to use a second cellular identifier (e.g., a "business" cellular identifier) ​​to make the call, the third enable representation 1064c can be selected to use cellular data (e.g., "data-based audio") to make the call, and the fourth enable representation 1064d can be selected to use cellular data to make the phone call as a video conference call (e.g., "data-based video"). In some embodiments, the phone call made via cellular data and video conference call is made using a cellular identifier (such as a "personal" cellular identifier) ​​for the default number for phone and SMS, as shown in legend 1002. Alternatively, in some embodiments, when the cellular identifier is set as a "data" cellular identifier, data-based calls and video conference calls are conducted using the data cellular identifier.

[0331] Figure 10V-Figure 10X A messaging user interface according to some embodiments of the present disclosure is shown. In some embodiments, Figure 10V-Figure 10XThe user interface shown in is presented when a user creates a new thread with a phone number or a set of phone numbers for which the electronic device 500 has no existing messaging thread corresponding thereto. The messaging user interface includes a text input field 1066 for entering a phone number to which a message is to be sent, an affordance 1068 selectable to switch a cellular identifier to be used to send the message, and a dial pad 1070. The affordance 1068 for switching a cellular identifier to be used to send the message includes an indication 1072 of the cellular identifier (e.g., a "personal" cellular identifier) ​​to be used to send the message. Figure 10V As shown, the phone number is entered into the text input field 1066. In some embodiments, the user is able to enter the phone number using a keyboard 1070, optionally including numeric soft keys, or paste the phone number into the text input field 1066 using user input. In some embodiments, when the phone number entered into the text input field 1066 is not associated with a contact associated with a different cellular identifier, the electronic device 500 first presents an indication 1042 of the cellular identifier as the default number for phone calls and SMS. For example, if the user enters a phone number for a contact that has no existing messaging thread associated with a "business" cellular identifier, then in response to entering the phone number and there being no other user input for sending the message using the "business" cellular identifier, the enable indication 1068 will be updated to include an indication of the "business" cellular identifier. As shown Figure 10W As shown, the user (e.g., using contact 1003) selects an affordance 1068 for switching the cellular identifier to be used to send the message. In response to the user input, the user interface is as shown. Figure 10X The illustration updates to show an indication 1072 of a different cellular identifier (eg, a "business" cellular identifier) ​​to be used to send the message.

[0332] Figure 10Y 1074a-1074c of a messaging conversation on the electronic device 500. Each indication 1074a-1074c includes an indication of a contact 1076a-1076c participating in the conversation and an indication 1078a-1078c of a cellular identifier used for the messaging conversation. Figure 10Y As shown, the user selects (e.g., using contact 1003) an affordance 1074b associated with a messaging conversation with "John Brown" being conducted using a "personal" cellular identifier. In response to this selection, the electronic device presents Figure 10Z The messaging user interface shown.

[0333] like Figure 10ZAs shown, the messaging user interface includes an indication 1080 of the type of message being sent, which is a data-based enhanced message (e.g., an enhanced instant message). Figure 10Z As shown in legend 1002 of , the "personal" cellular identifier is being used to send and receive messages in the displayed conversation. Because the contact "John Brown" is associated with the "personal" cellular identifier, and because the "personal" cellular identifier is the default number for phone calls and SMS, the message conversation is conducted using the enhanced data-based messaging service. In some embodiments, the cellular identifier that is the default number for phone calls and SMS is always used to send and receive enhanced data-based messaging, even for contacts associated with different cellular identifiers.

[0334] Figure 10AA shows a message inbox user interface, which is basically similar to Figure 10Y The message inbox user interface shown in Figure 1. Figure 10AA As shown, the user selects (e.g., using contact 1003) an affordance 1074c associated with a messaging conversation with "Alex Garcia" that is ongoing using the "business" cellular identifier. In response to this selection, the electronic device presents Figure 10BB The messaging user interface shown.

[0335] like Figure 10BB As shown, the messaging user interface includes an indication 1082 of the type of message being sent, that the message is a text message (e.g., not a data-based enhanced message such as a text message). Figure 10Z As shown in Figure 10BB As shown in legend 1002 of , the "business" cellular identifier is being used to send and receive messages in the displayed conversation. Because the contact "AlexGarcia" is associated with the "business" cellular identifier, and because the "personal" cellular identifier is the default number for phone calls and SMS, the message conversation is conducted using text messaging rather than data-based enhanced messaging. In some embodiments, the cellular identifier that is the default number for phone calls and SMS is always used to send and receive data-based enhanced messages. When a contact is associated with a cellular identifier that is not the default number for phone calls and SMS, in the absence of user input to alternatively utilize the cellular identifier for the default number for phone calls and SMS to send data-based enhanced messages, the electronic device 500 uses text messaging to send and receive messages to the contact.

[0336] Figure 10CC A home screen user interface of device 500 according to some embodiments of the present disclosure is shown, such as in Figure 4AThe home screen includes a plurality of icons 424-450 that can be selected to launch various applications on the electronic device 500. Figure 10CC As shown, the electronic device 500 detects an input for presenting a control user interface on the device 500 (eg, a downward swipe of contact 1203 from the upper right boundary of the touch screen 504), as shown in FIG. Figure 10DD-Figure 10GG shown.

[0337] Figure 10DD-Figure 10GG A control user interface according to some embodiments of the present disclosure is shown. The control user interface includes multiple enable representations for controlling the operation of the device 500. The control user interface includes enable representations for activating various operating modes of the electronic device, such as an airplane mode enable representation for activating or deactivating an airplane mode, a Wi-Fi enable representation for activating or deactivating Wi-Fi on an electronic device, a Bluetooth enable representation for activating or deactivating Bluetooth on an electronic device, a Do Not Disturb enable representation for activating or deactivating Do Not Disturb mode on an electronic device, and a rotation lock enable representation for preventing or allowing an image displayed on the electronic device 500 to rotate in response to the rotation of the electronic device. The control user interface also includes multiple enable representations for changing the settings of the electronic device, such as a brightness enable representation for changing the brightness of the display and a volume enable representation for changing the volume of the electronic device. The control user interface also includes a media player enable representation that can be selected to start multiple media player controls on the electronic device 500.

[0338] like Fig.10DD As shown, the control user interface also includes a cellular setting indication 1084. Fig.10EE As shown, the user (e.g., using contact 1003) selects cellular settings enable representation 1084. Contact 1003 has an intensity 1046a that exceeds a predetermined intensity threshold 1048a and is detected at a time 1046b that exceeds a predetermined intensity threshold 1048b. Alternatively, if electronic device 500 detects that there is no cellular settings at enable representation 1084, Fig.10EE In some embodiments, if the selection is detected while cellular data on all cellular identifiers is turned off, the electronic device 500 activates cellular data in response to the selection. In response to the input having the described characteristics, the electronic device presents a list 1086 of cellular identifiers available for use by the electronic device 500. The list 1086 includes a label for each cellular identifier (e.g., "Personal," "Business," and "Travel"), an indication 1088a-c of each cellular identifier, and an indication of the status of each cellular identifier. Fig.10FFAs shown, the status of the "Personal" cellular identifier is "Default number for phone calls and SMS", the status of the "Business" cellular identifier is "Secondary number for phone calls and SMS", and the status of the "Travel" cellular identifier is "Not activated". The list also includes an affordance 1090 that can be selected to activate the "Travel" cellular identifier.

[0339] The user selects (e.g., using contact 1003) an affordance 1090 for activating the "travel" cellular identifier. Figure 10GG As shown in legend 1002, in response to the selection, the "travel" cellular identifier is set to "default number for phone calls and SMS", the "personal" cellular identifier is set to "data only", and the "business" cellular identifier is set to "inactive". In some embodiments, when a cellular identifier is reactivated (e.g., such as the "travel" cellular identifier), it is automatically configured as the default number for phone calls and SMS. In some embodiments, the cellular identifier that was previously the primary number for phone calls and SMS (e.g., the "personal" cellular identifier) ​​is configured as "data only". In some embodiments, the cellular identifier that was previously the secondary number for phone calls and SMS (e.g., the "business" cellular identifier) ​​becomes inactive.

[0340] Figure 10HH shows a substantially similar Fig. 10D , Fig. 10E and Fig.10N The recent call user interface of the recent call user interface. Figure 10HH As shown in legend 1002 of FIG. 5 , the “Business” cellular identifier associated with contact “Alex Garcia” is not activated on electronic device 500. The user selects affordance 1010b associated with a recent call from “Alex Garcia” (e.g., using contact 1003). In some embodiments, in response to the selection, the electronic device presents Fig.10II The user interface includes a warning 1092 that the default cellular identifier for the contact is not available on the electronic device, and a "Cancel" affordance 1094 that is selectable to navigate back to a previously displayed user interface (e.g., a recent call user interface). In some embodiments, in response to Figure 10HH In the selection, the electronic device 500 alternatively presents Figure 10JJThe user interface includes a warning 1092 that the default cellular identifier for the contact is not available on the electronic device, a “Cancel” affordance 1094 selectable to navigate back to a previously displayed user interface (e.g., a recent call user interface), and an affordance 1096 selectable to place the call using a different cellular identifier (e.g., a “travel” cellular identifier) ​​activated on the electronic device.

[0341] Figure 10KK Shown with Fig. 10H , 10I A contacts user interface substantially similar to the contacts user interface shown in 10M. The contacts user interface includes an indication 1026 of the contact's name, an indication 1028e of the contact's first telephone number, an indication 1028f of the contact's second telephone number, a first indication 1030e of a cellular identifier associated with the contact (e.g., "business"), and a second indication 1030f of a cellular identifier associated with the contact (e.g., "business"). Because the contact is associated with the "business" cellular identifier, both of the contact's telephone numbers are associated with the "business" cellular identifier, and the indications 1028e-f of the two telephone numbers each include an indication 1030e-f of the "business" cellular identifier. The user interface also includes an enable indication 1098 that is selectable to send a message to the contact. As shown in FIG. Figure 10KK As shown, the user (e.g., using contact 1003) selects enable representation 1098. In response to this selection, electronic device 500 presents multiple enable representations 1098-2, 1098-4, and 1098-6 that can be selected to send messages to contacts. The first enable representation 1098-2 can be selected to send an SMS to the contact. The second enable representation 1098-4 can be selected to send a data-based enhanced message (e.g., an enhanced instant message) to the contact. The third enable representation 1098-6 can be selected to send an email to the contact. Figure 10LL As shown, the user (e.g., using contact 1003) selects the second enable representation to send a data-based enhanced message to the contact.

[0342] Figure 10MM shows a basically similar Figure 10BB The messaging user interface shown is a messaging user interface, and the user interface is responsive to Figure 10LL The selection is displayed based on the selection detected in the Figure 10MMAs shown in legend 1002 of , the “personal” cellular identifier is being used to send and receive messages in the displayed conversation. Although the contact “Alex Garcia” is associated with the “business” cellular identifier, because the user entered input for sending a data-based enhanced message to “Alex Garcia,” the message is sent using the “data-only” cellular identifier. The user interface displays previous messages that were sent and received as text messages, as shown in indication 1082. These text messages were sent and received using the “business” cellular identifier while the cellular identifier was active because that cellular identifier was the default cellular identifier for the contact. Figure 10LL In response to user input in the message, the user interface also displays an indication 1098-8 that the most recently sent message is a data-based enhanced message (e.g., an enhanced instant message).

[0343] Figure 11A-Figure 11Q 1 is a flow chart illustrating a method 1100 of presenting a visual indication of a cellular identifier associated with a communication function according to some embodiments of the present disclosure. The method 1100 is optionally performed on an electronic device (such as device 100, device 300, device 500), as described above with reference to Figure 1A-1B , Figure 2-Figure 3 , Figure 4A-4B and Figure 5A-5H Some operations in method 1100 are optionally combined, and / or the order of some operations is optionally changed.

[0344] As described below, method 1100 provides a method for presenting a visual indication of a cellular identifier associated with a communication function. The method reduces the cognitive burden on a user when interacting with a device user interface of the present disclosure, thereby creating a more efficient human-machine interface. For battery-powered electronic devices, improving the efficiency of user interaction with the user interface saves power and increases the time between battery charges.

[0345] In some embodiments, an electronic device (e.g., electronic device 500) in communication with a display and one or more input devices (e.g., a mobile device (e.g., a tablet, smart phone, media player, or wearable device) including a touch screen or a computer including one or more of a keyboard, a mouse, a trackpad, and a touch screen) receives (1102) input via the one or more input devices for displaying a communication user interface, such as Fig. 10DThe user interface shown is for displaying representations of a plurality of communications sent or received by the electronic device during a first time period (e.g., a messaging user interface displaying representations of messaging conversations with one or more other electronic devices, a phone user interface displaying representations of recent calls, etc.). The electronic device is optionally capable (1104) of using the primary cellular identifier to perform (1106) a first set of functions including the communications, such as Fig. 10D 1002. In some embodiments, the default cellular identifier for the communication under consideration (e.g., phone call, text messaging, video call, etc.) is the primary cellular identifier. In some embodiments, if the contact participating in the communication is specified to utilize a different cellular identifier for the communication to occur, then the communication is optionally performed using the different cellular identifier by default. The electronic device optionally uses the secondary cellular identifier to perform (1108) a second set of functions that are different from the first set of functions, such as Fig. 10D As shown in the legend 1002. In some embodiments, the electronic device is configured to use the second cellular identifier by default to implement functions other than the communication shown in the communication user interface. For example, the electronic device optionally uses the secondary cellular identifier by default to upload and download data, or performs communication operations in certain non-default conditions (e.g., communicating with contacts associated with the secondary cellular identifier, performing communication functions when the primary cellular identifier is not available).

[0346] In some embodiments, in response to receiving an input for displaying a communication user interface, the electronic device displays (1110) a communication user interface on a display, including simultaneously displaying multiple representations (1010a, 1010b, 1012, and 1014) of communication items (e.g., communications performed by the device (e.g., previous phone calls, messages, voicemails, etc.)) or representations of users with whom communication can be performed via one of the cellular identifiers, including a first representation (1012)(1112) of a communication item associated with a primary cellular identifier (e.g., a communication item performed using the primary cellular identifier (e.g., a previous phone call, voicemail, or previously received message)). In some embodiments, initiating a reply communication (e.g., a phone call or message) causes the electronic device to initiate the reply communication using the primary cellular identifier. The communication user interface optionally includes a second representation (1010a)(1114) of a communication item associated with a secondary cellular identifier (e.g., a communication item performed using the secondary cellular identifier (e.g., a previous phone call, voicemail, or previously received message)). In some embodiments, initiating a reply communication (e.g., a phone call or a message) causes the electronic device to initiate a reply communication using the secondary cellular identifier. The second representation optionally includes a corresponding visual indication (e.g., an indicator of the secondary cellular identifier, such as the "B" icon included in indication 1010a), wherein the corresponding visual indication distinguishes the second representation from the first representation (e.g., the first representation does not include the visual indication). In some embodiments, the first representation includes a visual indication different from the visual indication included in the second representation, such as an indicator of the primary cellular identifier. The communication user interface optionally includes a third representation (1010b) (1116) of a communication item associated with the secondary cellular identifier (e.g., a communication item performed using the secondary cellular identifier (e.g., a previous phone call, voicemail, or previously received message)). In some embodiments, initiating a reply communication (e.g., a phone call or a message) causes the electronic device to initiate a reply communication using the secondary cellular identifier. The third representation (1010b) optionally includes a corresponding visual indication (e.g., an indicator of a secondary cell identifier, such as a "B" indication of indication 1010b), wherein the corresponding visual indication distinguishes the third representation from the first representation (e.g., the first representation does not include the visual indication). In some embodiments, the first representation includes a visual indication that is different from the visual indication included in the third representation, such as an indicator of a primary cell identifier.

[0347] The above-described manner of displaying representations of communications performed using the secondary cellular identifier with a visual indication that distinguishes them from communications performed using the primary cellular identifier allows the electronic device to indicate to the user that the electronic device has used the secondary cellular identifier for communication operations during the first time period, which simplifies interaction between the user and the device and enhances the operability of the device (e.g., by presenting indications of communication functions performed using the secondary cellular identifier in an intuitive manner in a communication user interface), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0348] In some embodiments, the first representation of the communication item associated with the primary cellular identifier includes a visual indication of the primary cellular identifier that is different from corresponding visual indications (e.g., an indicator of the primary cellular identifier) ​​included in the second representation and the third representation (1118). In some embodiments, the indicator is automatically generated from a user-defined label for the primary cellular identifier. For example, if the primary cellular identifier is labeled "communication" and the secondary cellular identifier is labeled "data", the indicator of the primary cellular identifier includes a "C" and the indicator of the secondary cellular identifier includes a "D", such as in Fig. 10E as shown in .

[0349] The above-described manner of including an indication of the primary cellular identifier within a representation of a communication item associated with the primary cellular identifier allows the electronic device to confirm in a communication user interface that the communication item associated with the primary cellular identifier is associated with the primary cellular identifier, which simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by including an indication of the primary cellular identifier in the communication user interface, rather than requiring the user to confirm in a different manner which communications were performed using the primary cellular identifier), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0350] In some embodiments, a first representation of a communication item associated with a primary cellular identifier (e.g., Fig. 10D The representation 1012 shown does not include a visual indication of the primary cell identifier (1120). The second representation and the third representation optionally include a visual indication of the secondary cell identifier to distinguish the two representations from the first representation that does not include the visual indication.

[0351] The above-described manner of displaying representations of communication items associated with the primary cellular identifier without displaying an indication of the primary cellular identifier allows the electronic device to distinguish communications associated with the secondary cellular identifier from communications associated with the primary cellular identifier with reduced visual clutter, which simplifies interaction between the user and the device and enhances the operability of the device (e.g., by distinguishing the representations based on whether the representations include an indication of the secondary cellular identifier that allows the user to confirm within the communication user interface which cellular identifier was used for each communication shown), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0352] In some embodiments, the electronic device receives (1122) via one or more input devices corresponding to a display control area user interface (e.g., Fig.10DD The user interface shown) requests input (e.g., detecting Figure 10CC In some embodiments, the control area user interface includes a plurality of controls for controlling a plurality of functions of the electronic device. In some embodiments, the control area includes optional enabling representations for switching various settings (e.g., airplane mode, Wi-Fi, do not disturb, volume), performing various functions (e.g., flashlight, media player controls, etc.), or launching various applications (e.g., calculator, camera, etc.). In some embodiments, the control area user interface is accessible when the electronic device displays a user interface associated with an operating system (e.g., a home screen) or a user interface associated with an application in response to detecting a gesture (e.g., a swipe from a particular corner or edge of the display of the electronic device). The control area user interface optionally includes a first control 1084 for controlling a cellular identifier function of the electronic device, wherein a third cellular identifier is not currently activated on the electronic device, such as Figure 10CC As shown in legend 1002. In some embodiments, the third cellular identifier has been previously configured on the electronic device, but is not currently activated to perform one or more operations.

[0353] In some embodiments, in response to receiving a request to display a control area user interface (e.g., a voice command, a gesture (a swipe from a particular edge or corner of a touch screen of an electronic device), or another input) (e.g., detecting Figure 10CC ), the electronic device displays (1124) a control area user interface on the display, such as in Fig.10DD When displaying the control area user interface, the electronic device optionally receives (1126) an input associated with the first control (e.g., an input for selecting the first control) via one or more input devices (e.g., detecting Fig.10FFIn some embodiments, selecting the first control causes the electronic device to display a plurality of settings associated with the cellular identifier function. The input is optionally used to activate a third cellular identifier (e.g., a "travel" cellular identifier) ​​on the electronic device (e.g., configure the third cellular identifier so that the electronic device can use the third cellular identifier to perform one or more functions), such as in Fig.10FF In response to receiving an input associated with the first control for activating a third cellular identifier on the electronic device, the first electronic device activates (1128) the third cellular identifier on the electronic device (e.g., configures the third cellular identifier so that the electronic device can use the third cellular identifier to perform one or more functions), as shown in FIG. Figure 10GG As shown in Figure 1002.

[0354] The above-described manner of changing which cellular identifiers are active on an electronic device allows the electronic device to activate a third cellular identifier to perform a function using the third cellular identifier, which simplifies the interaction between the user and the device and enhances the operability of the device (for example, by allowing the user to activate the third cellular identifier without repeating the setup process for the third cellular identifier if the setup process has been previously completed), which in turn reduces power usage and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0355] In some embodiments, when a communication user interface such as Figure 10Y When the message inbox user interface shown is displayed, the first electronic device receives (1130) an input (e.g., contact 1003) via one or more input devices selecting a corresponding representation 1076b of a corresponding communication item with a corresponding contact in the communication user interface (e.g., including a touch input of a tap on the representation of the corresponding communication item, a click using a mouse or trackpad, voice input, a shortcut input using a keyboard or soft keyboard, etc.).

[0356] In some embodiments, in response to receiving an input (1132) selecting a corresponding representation 1076b of a corresponding communication item, such as in Figure 10Y As shown in , based on determining that the corresponding representation is a first representation of a communication item associated with a primary cellular identifier (e.g., a "personal" cellular identifier), the electronic device initiates (1134) a communication with the corresponding contact using the primary cellular identifier, such as Figure 10ZAs shown in legend 1002 of . For communications previously sent or received using the primary cellular identifier, the electronic device optionally initiates subsequent communications to the same contact using the primary cellular identifier in the same manner (e.g., phone call, SMS message, other messaging service, etc.). For example, if the corresponding representation is a representation of a previous outgoing phone call completed using the primary cellular identifier, then in response to selection of the corresponding representation, the electronic device initiates the phone call using the primary cellular identifier. Based on determining that the corresponding representation is a second representation of a communication item associated with a secondary cellular identifier (e.g., a “business” cellular identifier), the electronic device may select a secondary cellular identifier (e.g., a “business” cellular identifier) ​​and select the corresponding representation. Figure 10AA As shown in 1076c), the electronic device initiates (1136) communication with the corresponding contact using the secondary cellular identifier, such as Figure 10BB As shown in the legend 1002 of . For the communication previously sent or received using the secondary cellular identifier, the electronic device optionally initiates a subsequent communication to the same contact using the secondary cellular identifier in the same manner (e.g., a phone call, an SMS message, other messaging services, etc.). For example, if the corresponding representation is a representation of a previously received message, in response to the selection of the corresponding representation, the electronic device initiates the message using the secondary cellular identifier.

[0357] The above-described manner of initiating a communication using a cellular identifier associated with a previously performed communication allows an electronic device to consistently use a corresponding cellular identifier for communications associated with a particular cellular identifier, which simplifies interaction between a user and the device and enhances the operability of the device (e.g., by automatically tracking an associated cellular identifier without requiring user intervention), which in turn reduces power usage and extends the battery life of the device by enabling a user to use the device more quickly and efficiently.

[0358] In some embodiments, the electronic device receives (1138) input via one or more input devices corresponding to a request to initiate communication with a corresponding contact associated with the corresponding cellular identifier (e.g., Fig. 10E 1004 ) by contact 1003 (eg, selecting a representation 1010b of a communication item to be performed using a corresponding cellular identifier or another input for initiating communication using a corresponding cellular identifier).

[0359] In some embodiments, in response to receiving an input corresponding to a request to initiate communication with a corresponding contact (e.g., Fig. 10E In selecting representation 1010b) using contact 1003 (1140), based on determining that a corresponding cellular identifier (e.g., a "business" cellular identifier) ​​is available for communication, such as Fig. 10EAs shown in legend 1002 in FIG. 1 (e.g., the corresponding cellular identifier is activated on the electronic device and is currently connected to a network), the electronic device initiates (1142) communication with the corresponding contact using the corresponding cellular identifier (e.g., by default, the communication is initiated using the corresponding cellular identifier), such as in FIG. Fig.10F Zhongru Fig.10F As shown in the legend 1002. Based on determining that the corresponding cellular identifier is not available for communication (1144) (e.g., the corresponding cellular identifier is not activated on the electronic device and / or is not currently connected to the network), such as in Figure 10HH Zhongru Figure 10HH As shown in legend 1002 of , the electronic device abandons (1146) initiating communication with the corresponding contact using the corresponding cellular identifier, and the electronic device provides (1148) a warning 1092 indicating that the corresponding cellular identifier is not available for communication (e.g., the electronic device presents text, images, audio, etc. indicating that communication cannot be performed using the corresponding cellular identifier because the correspondin...

Claims

1. A method comprising: At an electronic device in communication with a display and one or more input devices: Simultaneously displaying on said display: a first status indicator of a first cellular identifier of the electronic device, The first status indicator indicates an activation status of the first cellular identifier, and a second status indicator of a second cellular identifier of the electronic device, The second status indicator indicates an activation status of the second cellular identifier; receiving, via the one or more input devices, input corresponding to a request to communicate with a contact while the first status indicator and the second status indicator are simultaneously displayed, wherein the contact is associated with a corresponding cellular identifier; as well as In response to receiving the input corresponding to the request to communicate with the contact, based on determining that the contact is associated with the first cellular identifier, Simultaneously displaying on said display: the first status indicator of the first cellular identifier of the electronic device, the first status indicator indicating the activation state of the first cellular identifier, and The second status indicator of the second cellular identifier of the electronic device, the second status indicator indicating an inactive state of the second cellular identifier.

2. The method according to claim 1, further comprising: In response to receiving the input corresponding to the request to communicate using the corresponding cellular identifier, based on determining that the request is a request to communicate using the second cellular identifier, simultaneously displaying on the display: the first status indicator of the first cellular identifier of the electronic device, the first status indicator indicating an inactivated state of the first cellular identifier; and The second status indicator of the second cellular identifier of the electronic device indicates the activation status of the second cellular identifier.

3. The method according to claim 1, further comprising: Simultaneously displaying on said display: a third status indicator of a wireless communication connection other than a cellular communication connection of the electronic device; and the first status indicator of the first cellular identifier and the second status indicator of the second cellular identifier, in: displaying the third status indicator at a first position adjacent to the first status indicator in response to determining that the first cellular identifier is designated as a cellular identifier to be used for data communications at the electronic device; and Based on determining that the second cellular identifier is designated as the cellular identifier to be used for data communications at the electronic device, the third status indicator is displayed at a second location different from the first location adjacent to the second status indicator.

4. The method according to claim 1, wherein: the first status indicator of the first cellular identifier is associated with a first cellular operator, The second status indicator of the second cellular identifier is associated with a second cellular operator different from the first cellular operator, and The first status indicator and the second status indicator are displayed in an area of ​​the display that also includes a third status indicator that indicates a status of a function of the electronic device other than the first cellular identifier and the second cellular identifier.

5. The method according to claim 1, further comprising: while displaying the first status indicator of the first cellular identifier and the second status indicator of the second cellular identifier, wherein the first status indicator of the first cellular identifier is displayed together with a first set of information associated with the first cellular identifier and the second status indicator of the second cellular identifier is displayed together with a first set of information associated with the second cellular identifier, receiving, via the one or more input devices, an input corresponding to a request to display a control area user interface, the control area user interface including a plurality of controls for controlling a plurality of functions of the electronic device; as well as In response to receiving the input corresponding to the request to display the control area user interface: displaying the control area user interface on the display; displaying the first status indicator of the first cellular identifier together with the first set of information associated with the first cellular identifier and a second set of information associated with the first cellular identifier; and The second status indicator of the second cellular identifier is displayed along with the first set of information associated with the second cellular identifier and a second set of information associated with the second cellular identifier.

6. The method according to claim 1, further comprising: receiving, via the one or more input devices, a sequence of one or more inputs to activate a third cellular identifier on the electronic device while displaying the first status indicator of the first cellular identifier indicating the activation status of the first cellular identifier and the second status indicator of the second cellular identifier indicating the activation status of the second cellular identifier; as well as In response to receiving the sequence of one or more inputs activating the third cellular identifier on the electronic device: activating the third cellular identifier on the electronic device; ceasing to display the first status indicator of the first cellular identifier; and Simultaneously displaying on said display: the second status indicator of the second cellular identifier of the electronic device, the second status indicator indicating the activation status of the second cellular identifier; and A third status indicator of the third cellular identifier of the electronic device, the third status indicator indicating an activation status of the third cellular identifier.

7. An electronic device comprising: one or more processors; Memory; and One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 6.

8. A computer-readable storage medium storing one or more programs, wherein the one or more programs include instructions, which, when executed by one or more processors of an electronic device, cause the electronic device to perform the method according to any one of claims 1 to 6.

Images