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

Abstract

The invention relates to a user interface on an electronic device for controlling or presenting information of a plurality of cellular recognizers. In some embodiments, an electronic device presents a setup user interface associated with a cellular identifier. In some embodiments, the first electronic device accesses the first cellular identifier irrespective 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, an electronic device presents a visual indication of a cellular identifier associated with a communication function. In some embodiments, an electronic device presents a visual indication of a status of a cellular identifier activated on the electronic device. In some embodiments, an electronic device presents prompts associated with one or more cellular recognizers that have been removed from the electronic device.

Description

[0001] This application is a divisional application of the invention patent application filed on August 30, 2019, with application number 201980059391.5 and entitled "User Interface for Controlling or Presenting Information about Multiple Cellular Identifiers on an Electronic Device". Technical Field

[0002] This disclosure relates in general to electronic devices that control or present information about multiple cellular identifiers of a device, and to user interaction with such devices. Background Technology

[0003] In recent years, user interaction with electronic devices has increased significantly. These devices can include computers, tablets, televisions, multimedia devices, mobile devices, and so on.

[0004] In some cases, users want to see information about the cellular identifier of an electronic device (e.g., SIM card, eSIMS, etc.), such as what actions can be performed using the cellular identifier. Enhancing these interactions can improve the user experience and reduce user interaction time, which is especially important when the input device is battery powered. Summary of the Invention

[0005] Some embodiments described in this disclosure relate to one or more electronic devices presenting a settings user interface associated with a cellular identifier. Some embodiments described in this disclosure relate to one or more first electronic devices accessing a first cellular identifier regardless of their connection to one or more second electronic devices, and methods by which the one or more first electronic devices access a second cellular identifier when connected to one or more second electronic devices. Some embodiments described in this disclosure relate to one or more electronic devices presenting visual indications of cellular identifiers related to communication functions. Some embodiments described in this disclosure relate to one or more electronic devices presenting visual indications of the status of active cellular identifiers on an electronic device. Some embodiments described in this disclosure relate to one or more electronic devices presenting prompts related to cellular identifiers that have been removed from one or more electronic devices. Attached Figure Description

[0006] To better understand the various embodiments described, reference should be made to the following detailed description in conjunction with the accompanying drawings, in which similar reference numerals indicate corresponding parts throughout the drawings.

[0007] Figure 1AThis is a block diagram illustrating a portable multi-functional device with a touch-sensitive display according to some embodiments.

[0008] Figure 1B This is a block diagram illustrating exemplary components for event handling according to some implementation schemes.

[0009] Figure 2 A portable multi-functional device with a touchscreen is shown according to some embodiments.

[0010] Figure 3 This is a block diagram of an exemplary multifunctional device having a display and a touch-sensitive surface according to some implementation schemes.

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

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

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

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

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

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

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

[0018] Figures 7A-7I This is a flowchart illustrating a method for presenting a setup user interface associated with a cellular identifier according to some embodiments of the present disclosure.

[0019] Figures 8A-8U Exemplary methods are shown for a first electronic device to access a first cellular identifier according to some embodiments of the present disclosure, regardless of how the first electronic device is connected to a second electronic device, and exemplary methods for a first electronic device to access a second cellular identifier when the first electronic device is connected to a second electronic device.

[0020] Figures 9A-9HThis is a flowchart illustrating methods for accessing a first cellular identifier on a first electronic device regardless of the connection between the first electronic device and a second electronic device, according to some embodiments of the present disclosure, and for accessing a second cellular identifier on the first electronic device when the first electronic device is connected to the second electronic device.

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

[0022] Figures 11A-11Q This is a flowchart illustrating a method for presenting visual indications of a cellular identifier related to communication functions according to some embodiments of this disclosure.

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

[0024] Figures 13A-13F This is a flowchart illustrating a method for presenting a visual indication of the status of an activated cellular identifier on an electronic device, according to some embodiments of this disclosure.

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

[0026] Figures 15A-15O This is a flowchart illustrating a method for presenting a prompt related to a previously removed cellular identifier according to some embodiments of this disclosure. Detailed Implementation Detailed Implementation

[0028] The following description illustrates exemplary methods, parameters, etc. However, it should be understood that such description is not intended to limit the scope of this disclosure, but is provided as a description of exemplary embodiments.

[0029] Electronic devices need to provide effective methods and interfaces for presenting information about the device's cellular identifier (e.g., SIM card, eSIM, etc.). Such technologies can reduce the cognitive burden on users of such devices and / or those who wish to control their use of them. Furthermore, such technologies can reduce processor and battery power wasted otherwise on redundant user input.

[0030] 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. For example, a first touch may be named a second touch and similarly, a second touch may 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.

[0031] The terminology used in the description of the various embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various embodiments and the appended claims, the singular forms “a” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and covers any and all possible combinations of one or more of the associated listed items. It will also be understood that the terms “includes”, “including”, “comprises”, and / or “comprising”, when used in this specification, specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0032] Depending on the context, the term "if" may optionally be interpreted as meaning "when," "at," or "in response to determination" or "in response to detection." Similarly, depending on the context, the phrases "if determination..." or "if detection [the stated condition or event]" may optionally be interpreted as meaning "in response to determination..." or "in response to detection [the stated condition or event]."

[0033] This document describes implementations of electronic devices, user interfaces for such devices, and related processes for using such devices. In some implementations, the device is a portable communication device, such as a mobile phone, that also includes other functions such as PDA and / or music player functionality. Exemplary implementations of portable multi-functional devices include, but are not limited to, those from Apple Inc. (Cupertino, California). Devices, iPod Equipment, and Device. Optionally, other portable electronic devices may be used, such as laptops or tablets with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with touch-sensitive surfaces (e.g., touchscreen displays and / or touchpads).

[0034] 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 may optionally include one or more other physical user interface devices, such as a physical keyboard, mouse, and / or joystick.

[0035] The device typically supports a variety of applications, such as one or more of the following: drawing applications, presentation applications, word processing applications, website creation applications, disk editing applications, spreadsheet applications, game applications, phone applications, video conferencing applications, email applications, instant messaging applications, fitness support applications, photo management applications, digital camera applications, digital video camcorder applications, web browsing applications, digital music player applications, and / or digital video player applications.

[0036] Various applications running on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and the 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 device's common physical architecture (such as the touch-sensitive surface) optionally utilizes a user interface that is intuitive and clear to the user to support various applications.

[0037] Now let’s turn our attention to implementation schemes for portable devices with touch-sensitive displays. Figure 1AThis is a block diagram illustrating a portable multi-functional device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a “touchscreen” for convenience, and is sometimes referred to as or called a “touch-sensitive display system.” 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 interface 118, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more haptic output generators 167 for generating haptic output on device 100 (e.g., generating haptic output on a touch-sensitive surface such as the touch-sensitive display system 112 of device 100 or the touchpad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0038] As used in this specification and claims, the term "intensity" of contact on a tactile surface refers to the force or pressure (force per unit area) of a contact (e.g., finger contact) on a tactile surface, or to a substitute (alternative) for the force or pressure of a contact on a tactile surface. The intensity of contact has a range of values ​​that includes at least four different values ​​and more typically hundreds of different values ​​(e.g., at least 256). The intensity of 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 tactile surface are optionally used to measure the force at different points on the tactile surface. In some embodiments, force measurements from multiple force sensors are combined (e.g., weighted average) to determine the estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the tactile surface. Alternatively, the size and / or variation of the contact area detected on the touch-sensitive surface, the capacitance and / or variation of the touch-sensitive surface near the contact, and / or the resistance and / or variation of the touch-sensitive surface near the contact may optionally be used as substitutes 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 an intensity threshold (e.g., the intensity threshold is described in units corresponding to the substitute measurement) has been exceeded. 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 an intensity threshold (e.g., the intensity threshold is a pressure threshold measured in units of pressure) has been exceeded. Using the intensity of the contact as an attribute of user input allows the user to access additional device functions that would otherwise be inaccessible to the user on smaller devices with limited physical space, such smaller devices being used (e.g., on a touch-sensitive display) to display power indications and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0039] As used in this specification and claims, the term "haptic output" refers to a physical displacement of the 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., the housing), or a displacement of a component relative to the center of mass of the device, which is detected by the user using the user's tactile sense. For example, when the device or a component of the device comes into contact with a touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the haptic output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical characteristics of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or touchpad) may optionally be interpreted by the user as a "press-click" or "release-click" on a physically actuated button. In some cases, the user will feel a tactile sensation, such as a "press-click" or "release-click," even when a physically actuated button associated with a touch-sensitive surface that has been physically pressed (e.g., displaced) by the user's movement does not move. For example, even when the smoothness of the tactile surface remains unchanged, the movement of the tactile surface can optionally be interpreted or sensed by the user as the "roughness" of the tactile surface. While such interpretations of touch by users will be limited by the individualized sensory perceptions of the user, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a specific 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 its components that will generate the sensory perception of a typical (or ordinary) user.

[0040] It should be understood that device 100 is merely an example of a portable multifunctional device, and device 100 may optionally have more or fewer components than those shown, may optionally combine two or more components, or may optionally have different configurations or arrangements of these components. Figure 1A The various components shown are implemented in hardware, software, or a combination of both, including one or more signal processing and / or application-specific integrated circuits.

[0041] Memory 102 optionally includes high-speed random access memory and also optionally 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.

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

[0043] RF (Radio Frequency) circuit 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuit 108 converts electrical signals into electromagnetic signals and vice versa, and communicates with communication networks and other communication devices via these electromagnetic signals. RF circuit 108 optionally includes well-known circuitry 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, Subscriber Identity Module (SIM) cards, memory, etc. RF circuit 108 optionally communicates wirelessly with networks and other devices, such as the Internet (also known 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 circuitry for detecting near-field communication (NFC) fields, such as via near-field communication radio components. Wireless communication may optionally employ 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, Pure Data (EV-DO), HSPA, HSPA+, Dual-Unit 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), and Wi-Fi (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE...). 802.11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Messaging 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 with Extended Utility (SIMPLE), Instant Messaging and Presence Service (IMPS)), and / or Short Message Service (SMS), or any other suitable communication protocol that has not been developed as of the date of this document submission.

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

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

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

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

[0048] Touchscreen 112 has a touch-sensitive surface, sensor, or sensor array that accepts input from a user based on tactile and / or haptic contact. Touchscreen 112 and display controller 156 (along with any associated modules and / or instruction set in memory 102) detect contact on touchscreen 112 (and any movement or interruption of that contact) and translate the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touchscreen 112. In an exemplary embodiment, the contact point between touchscreen 112 and the user corresponds to the user's finger.

[0049] Touchscreen 112 optionally employs LCD (Liquid Crystal Display) technology, LPD (Light Emitting Polymer Display) technology, or LED (Light Emitting Diode) technology, but other display technologies are used in other embodiments. Touchscreen 112 and display controller 156 optionally employ any of a variety of touch sensing technologies now known or to be developed hereafter, along with other proximity sensor arrays or other elements for determining one or more points of contact with touchscreen 112, to detect contact and any movement or interruption thereof. These various touch sensing technologies include, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that from Apple Inc. (Cupertino, California). and iPod The technology used.

[0050] In some embodiments of the touchscreen 112, the touch-sensitive display optionally resembles a multi-touch touchpad 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 incorporated herein by reference in its entirety. However, the touchscreen 112 displays visual output from the device 100, while the touch-sensitive touchpad does not provide visual output.

[0051] In some embodiments, the touchscreen 112 has a touch-sensitive display as described in the following patent applications: (1) U.S. Patent Application No. 11 / 381,313, filed May 2, 2006, entitled “Multipoint Touch Surface Controller”; (2) U.S. Patent Application No. 10 / 840,862, filed May 6, 2004, entitled “Multipoint Touchscreen”; (3) U.S. Patent Application No. 10 / 903,964, filed July 30, 2004, entitled “Gestures For Touch Sensitive Input Devices”; (4) U.S. Patent Application No. 11 / 048,264, filed January 31, 2005, entitled “Gestures For Touch Sensitive Input Devices”; and (5) U.S. Patent Application No. 18, 2005, entitled “Mode-Based Graphical User Interfaces For Touch Sensitive”. (6) U.S. Patent Application No. 11 / 038,590 entitled “Input Devices”; (7) U.S. Patent Application No. 11 / 228,758 entitled “Virtual Input Device Placement On A Touch Screen User Interface”, filed September 16, 2005; (8) U.S. Patent Application No. 11 / 228,700 entitled “Operation Of A Computer With A Touch Screen Interface”, filed September 16, 2005; (9) U.S. Patent Application No. 11 / 228,737 entitled “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”, filed September 16, 2005; and (10) U.S. Patent Application No. 11 / 367,749 entitled “Multi-Functional Hand-Held Device”, filed March 3, 2006. The full text of all these applications is incorporated herein by reference.

[0052] Touchscreen 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touchscreen has a video resolution of approximately 160 dpi. Users optionally interact with touchscreen 112 using any suitable object or accessory such as a stylus, finger, etc. In some embodiments, the user interface is designed to operate primarily through finger-based touch and gestures, which may be less precise than stylus-based input due to the larger contact area of ​​a finger on the touchscreen. In some embodiments, the device translates coarse finger-based input into precise pointer / cursor positions or commands to perform the user-desired actions.

[0053] In some embodiments, in addition to the touchscreen, 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 touchscreen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from the touchscreen 112, or an extension of the touch-sensitive surface formed by the touchscreen.

[0054] The device 100 also includes a power system 162 for supplying power to 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., light-emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in the portable device.

[0055] The device 100 may optionally also include one or more optical sensors 164. Figure 1AAn optical sensor 164 is shown coupled to an optical sensor controller 158 in the I / O subsystem 106. 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 an imaging module 143 (also called a camera module), the optical sensor 164 optionally captures still images or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to a touchscreen display 112 on the front of the device, allowing the touchscreen display to be used as a viewfinder for still image and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device, allowing images of the user to be optionally acquired for video conferencing while the user views other video conferencing participants on the touchscreen display. In some embodiments, the position of the optical sensor 164 can be changed by the user (e.g., by rotating the lenses and sensor within the device housing), allowing a single optical sensor 164 to be used in conjunction with the touchscreen display for both video conferencing and still image and / or video image acquisition.

[0056] The device 100 may optionally also include one or more contact strength sensors 165. Figure 1A A contact strength sensor is shown coupled to a strength sensor controller 159 in I / O subsystem 106. The contact strength sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electro-force sensors, piezoelectric sensors, optical force sensors, capacitive touch-sensitive surfaces, or other strength sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). The contact strength sensor 165 receives contact strength information (e.g., pressure information or a substitute for pressure information) from the environment. In some embodiments, at least one contact strength sensor is arranged juxtaposed with or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact strength sensor is located on the rear of device 100, opposite to the touchscreen display 112 located on the front of device 100.

[0057] The device 100 optionally also includes one or more proximity sensors 166. Figure 1AA proximity sensor 166 coupled to a peripheral device interface 118 is shown. Alternatively, the proximity sensor 166 may optionally be coupled to an input controller 160 in an I / O subsystem 106. The proximity sensor 166 may optionally perform 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", the entire contents of which are incorporated herein by reference. In some implementations, the proximity sensor is turned off and the touchscreen 112 is disabled when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

[0058] The device 100 may optionally also include one or more tactile output generators 167. Figure 1AA haptic output generator coupled to a haptic feedback controller 161 in I / O subsystem 106 is shown. The haptic output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion, such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other haptic output generating components (e.g., components for converting electrical signals into haptic outputs on the device). A contact intensity sensor 165 receives haptic feedback generation instructions from a haptic feedback module 133 and generates a haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one haptic output generator is juxtaposed or adjacent to a haptic surface (e.g., haptic display system 112) and optionally generates the haptic output by moving the haptic surface vertically (e.g., in / outward from the surface of device 100) or laterally (e.g., backward and forward in the same plane as the surface of device 100). In some embodiments, at least one haptic output generator sensor is located on the rear of the device 100, opposite to the touch screen display 112 located on the front of the device 100.

[0059] The device 100 optionally also includes one or more accelerometers 168. Figure 1A An accelerometer 168 coupled to a peripheral device interface 118 is shown. Alternatively, the accelerometer 168 may optionally be coupled to an input controller 160 in an I / O subsystem 106. The accelerometer 168 may optionally perform as described in the following U.S. patent publications: 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 on a touchscreen display in portrait or landscape view based on analysis of data received from one or more accelerometers. In addition to the accelerometer 168, the device 100 optionally includes a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information about the position and orientation (e.g., longitudinal or lateral) of the device 100.

[0060] 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 program (or instruction set) 136. Furthermore, in some embodiments, memory 102 ( Figure 1A ) or 370 ( Figure 3 Storage device / global internal state 157, such as Figure 1A and Figure 3 As shown in the figure. Device / global internal state 157 includes one or more of the following: active application state, which indicates which applications (if any) are currently active; display state, which indicates what applications, views or other information occupy various areas of the touch screen display 112; 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 orientation.

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

[0062] The communication module 128 facilitates communication with other devices via one or more external ports 124 and includes various software components for processing data received by the RF circuitry 108 and / or the external ports 124. The external ports 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) are adapted to be directly coupled to other devices or indirectly coupled via a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to… (Trademark of Apple Inc.) The same or similar and / or compatible multi-pin (e.g., 30-pin) connectors used in Apple Inc. devices.

[0063] The contact / motion module 130 optionally detects contact with the touchscreen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., touchpads or physical click-based rotary dials). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether a contact has occurred (e.g., detecting a finger press event), determining the contact intensity (e.g., the force or pressure of the contact, or an alternative to force or pressure), determining whether there is movement of the contact and tracking 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 a contact break). 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 which is represented by a series of contact data. These operations are optionally applied to single-point contact (e.g., single-finger contact) or multi-point simultaneous contact (e.g., "multi-touch" / multiple-finger contact). In some implementations, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.

[0064] In some implementations, 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., determining whether the user has “clicked” an icon). In some implementations, at least a subset of the intensity thresholds is determined based on software parameters (e.g., the intensity thresholds are not determined by the activation threshold of a specific physical actuator and can be adjusted without changing the physical hardware of device 100). For example, the mouse “click” threshold of a touchpad or touchscreen can be set to any threshold in a wide range of predefined thresholds without changing the touchpad or touchscreen display hardware. Additionally, in some specific implementations, the user of the device is provided with software settings for adjusting one or more intensity thresholds in a set (e.g., by adjusting the individual intensity thresholds and / or by adjusting multiple intensity thresholds at once using system-level clicks on the “intensity” parameter).

[0065] The touch / motion module 130 optionally detects gesture input performed by the user. Different gestures on a touch-sensitive surface have different contact patterns (e.g., different movements, timings, and / or intensities of the detected contact). 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-off (lift-away) event at the same (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 a touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and subsequently detecting a finger lift-off (lift-away) event.

[0066] The graphics module 132 includes various known software components for rendering and displaying graphics on the touchscreen 112 or other display, including components for altering the visual impact of the displayed graphics (e.g., brightness, transparency, saturation, contrast, or other visual properties). As used herein, the term "graphics" includes any object that can be displayed to a user, and non-limitingly includes text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

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

[0068] The haptic feedback module 133 includes various software components for generating instructions which are used by the haptic output generator 167 to generate haptic output at one or more locations on the device 100 in response to user interaction with the device 100.

[0069] Optionally, the text input module 134, a component of the 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 that requires text input).

[0070] GPS module 135 determines the location of the device and provides that information for use in various applications (e.g., to phone 138 for use in location-based dialing; to camera 143 as image / video metadata; and to applications that provide location-based services, such as weather desktop apps, local yellow pages desktop apps, and map / navigation desktop apps).

[0071] Application 136 optionally includes the following modules (or instruction sets) or subsets or supersets thereof:

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

[0073] • Telephone module 138;

[0074] • Video conferencing module 139;

[0075] • Email client module 140;

[0076] • Instant Messaging (IM) module 141;

[0077] Fitness support module 142;

[0078] • Camera module 143 for still images and / or video images;

[0079] • Image management module 144;

[0080] • Video player module;

[0081] Music player module;

[0082] • Browser module 147;

[0083] • Calendar module 148;

[0084] • Desktop mini-program module 149, which optionally includes one or more of the following: weather desktop mini-program 149-1, stock market desktop mini-program 149-2, calculator desktop mini-program 149-3, alarm clock desktop mini-program 149-4, dictionary desktop mini-program 149-5, and other desktop mini-programs obtained by the user and desktop mini-programs created by the user 149-6;

[0085] • Desktop app creator module 150 for creating user-created desktop apps 149-6;

[0086] • Search module 151;

[0087] • Video and music player module 152, which combines a video player module and a music player module;

[0088] • Notepad module 153;

[0089] • Map module 154; and / or

[0090] • Online video module 155.

[0091] Examples of other applications 136 that may be 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, speech recognition, and speech duplication.

[0092] In conjunction with the touchscreen 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., in the application internal state 192 of the contact module 137 stored 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 so on.

[0093] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, telephone module 138 is optionally used to input character sequences corresponding to telephone numbers, access one or more telephone numbers in contact module 137, modify entered telephone numbers, dial corresponding telephone numbers, initiate conversations, and disconnect or hang up when a conversation is completed. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0094] Combining RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touchscreen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132, text input module 134, contact module 137, and telephone module 138, video conferencing module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants based on user instructions.

[0095] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / 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 commands. Combined with image management module 144, email client module 140 makes it very easy to create and send emails containing still images or video images captured by camera module 143.

[0096] In conjunction with RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using Short Message Service (SMS) or Multimedia Messaging Service (MMS) protocols for telephone-based instant messaging or using XMPP, SIMPLE, or IMPS for internet-based instant messaging), receiving an instant message, and viewing a received instant message. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photographs, audio files, video files, and / or other attachments supported in MMS and / or Enhanced Messaging Services (EMS). As used herein, "instant message" refers to both telephone-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0097] Incorporating RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, fitness support module 142 includes executable instructions for creating fitness activities (e.g., with time, distance, and / or calorie burning goals); communicating with fitness sensors (executive devices); receiving fitness sensor data; calibrating sensors used to monitor fitness; selecting and playing music for fitness activities; and displaying, storing, and transmitting fitness data.

[0098] In conjunction with the touchscreen 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: capturing still images or videos (including video streams) and storing them in memory 102, modifying the characteristics of still images or videos, or deleting still images or videos from memory 102.

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

[0100] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the Internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as links to attachments and other files on web pages.

[0101] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and associated data (e.g., calendar entries, to-dos, etc.) according to user instructions.

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

[0103] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, the desktop applet creator module 150 can optionally be used by the user to create desktop applets (e.g., converting user-specified portions of a webpage into desktop applets).

[0104] In conjunction with the touchscreen 112, display controller 156, touch / 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) according to user instructions.

[0105] Incorporating touchscreen 112, display controller 156, touch / 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 allowing users to download and play recorded music and other sound files stored in one or more file formats such as MP3 or AAC files, as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touchscreen 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 (a trademark of Apple Inc.).

[0106] Combining the touchscreen 112, display controller 156, touch / 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 items, etc., according to user instructions.

[0107] Combining RF circuitry 108, touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 is optionally used to receive, display, modify, and store maps and map-related data (e.g., driving directions, data related to shops and other points of interest at or near a specific location, and other location-based data) according to user instructions.

[0108] Incorporating touchscreen 112, display controller 156, touch / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, email client module 140, and browser module 147, the online video module 155 includes instructions for performing the following actions: allowing users to access, browse, receive (e.g., via streaming and / or downloading), play back (e.g., on the touchscreen or on an external display connected via external port 124), send emails with links to specific online videos, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, an instant messaging module 141 is used instead of the email client module 140 to send links to specific online videos. Further descriptions of the online video application can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed 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 December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are incorporated herein by reference in their entirety.

[0109] Each of the above modules and applications 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., computer-implemented methods and other information processing methods as described herein). These modules (e.g., instruction sets) need not be implemented as separate software programs, processes, or modules; therefore, various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. For example, a video player module may optionally be combined with a music player module into a single module (e.g., Figure 1A (e.g., video and music player module 152). In some embodiments, memory 102 optionally stores subgroups of the aforementioned modules and data structures. Additionally, memory 102 optionally stores other modules and data structures not described above.

[0110] In some implementations, device 100 is a device on which the operation of a predefined set of functions is performed solely via a touchscreen and / or touchpad. By using a touchscreen and / or touchpad as the primary input control device for operating device 100, the number of physical input control devices (e.g., push-buttons, dials, etc.) on device 100 can be optionally reduced.

[0111] A predefined set of functions, uniquely performed via a touchscreen and / or touchpad, optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to the main menu, home menu, or root menu. In such embodiments, a "menu button" is implemented using a touchpad. In some other embodiments, the menu button is a physical push-button or other physical input control device, rather than a touchpad.

[0112] Figure 1B This 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 This includes an event classifier 170 (e.g., in operating system 126) and a corresponding application 136-1 (e.g., any one of the aforementioned applications 137 to 151, 155, 380 to 390).

[0113] Event classifier 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which the event information should be delivered. Event classifier 170 includes event monitor 171 and event dispatcher 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 should be delivered.

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

[0115] Event monitor 171 receives event information from peripheral device interface 118. The event information includes information about sub-events (e.g., user touches on touch-sensitive display 112 as part of a multi-touch gesture). Peripheral device 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 (via audio circuitry 110). The information received by peripheral device interface 118 from I / O subsystem 106 includes information from touch-sensitive display 112 or touch-sensitive surfaces.

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

[0117] In some implementations, the event classifier 170 also includes a hit view determination module 172 and / or an activity event recognizer determination module 173.

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

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

[0120] The hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchical structure, the hit view determination module 172 identifies the hit view as the lowest-level view in the hierarchical structure from which 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 forming an event or potential event) occurs. Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source to which it was identified as the hit view.

[0121] The activity event recognizer determination module 173 determines which views(s) within the view hierarchy should receive a specific sub-event sequence. In some embodiments, the activity event recognizer determination module 173 determines that only the hit view should receive the specific sub-event sequence. In other embodiments, the activity event recognizer determination module 173 determines that all views including the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive the specific sub-event sequence. In other embodiments, even if the touch sub-event is entirely confined to the area associated with a particular view, higher views in the hierarchy will still remain actively participating views.

[0122] Event assigner module 174 assigns event information to event identifiers (e.g., event identifier 180). In embodiments that include active event identifier determination module 173, event assigner module 174 delivers event information to the event identifier determined by active event identifier determination module 173. In some embodiments, event assigner module 174 stores event information in an event queue, which is retrieved by the corresponding event receiver 182.

[0123] 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 part of another module (such as contact / motion module 130) stored in memory 102.

[0124] In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module, such as a user interface toolkit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handlers 190 optionally utilize or invoke the data updater 176, the object updater 177, or the GUI updater 178 to update the application's internal state 192. Alternatively, one or more application views in application view 191 include one or more corresponding event handlers 190. Additionally, 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.

[0125] The corresponding event recognizer 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 recognizer 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event recognizer 180 also includes at least one subset of metadata 183 and event delivery instructions 188 (which optionally include sub-event delivery instructions).

[0126] Event receiver 182 receives event information from event classifier 170. The 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 touch movement, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a longitudinal orientation to a lateral orientation, or vice versa), and the event information includes corresponding information about the device's current orientation (also referred to as device orientation).

[0127] Event comparator 184 compares event information with predefined event or sub-event definitions and determines the event or sub-event based on the comparison, or determines or updates the state of the event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 contains definitions of events (e.g., predefined sequences 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, event 1 (187-1) is defined as a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on the displayed object, a first lift-off of a predetermined duration (touch end), a second touch (touch start) of a predetermined duration on the displayed object, and a second lift-off of a predetermined duration (touch end). In another example, event 2 (187-2) is defined as a drag on a displayed object. For example, dragging includes a touch (or contact) on the displayed object for a predetermined duration, movement of the touch on the touch-sensitive display 112, and lifting off the touch (end of touch). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0128] In some implementations, event definition 187 includes definitions of events for corresponding user interface objects. In some implementations, event comparator 184 performs a hit test to determine which user interface object is associated with the sub-event. For example, in an application view 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 the event handler associated with the sub-event and the object that triggered the hit test.

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

[0130] When the corresponding event recognizer 180 determines that the sub-event sequence 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 based on touch gestures are ignored. In this case, other event recognizers (if any) that remain active in the hit view continue to track and process the ongoing sub-events based on touch gestures.

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

[0132] In some implementations, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates the event handler 190 associated with the event. In some implementations, 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 delaying) the sub-event to the corresponding hit view. In some implementations, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with that tag retrieves the tag and executes a predefined procedure.

[0133] In some implementations, event delivery instruction 188 includes 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 the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or the actively participating view receives the event information and performs a predetermined procedure.

[0134] In some implementations, 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 implementations, 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 location 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 touch-sensitive display.

[0135] In some implementations, event handler 190 includes, or has access to, a data updater 176, an object updater 177, and a GUI updater 178. In some implementations, 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 implementations, they are included in two or more software modules.

[0136] It should be understood that the above discussion regarding event handling for user touch on a touch-sensitive display also applies to other forms of user input used to operate the multifunction device 100 using an input device, and not all user input is initiated on the touchscreen. For example, mouse movement and mouse button presses optionally in conjunction with single or multiple keyboard presses or holds; touch movements on the touchpad, such as taps, drags, scrolls, etc.; stylus input; device movement; verbal commands; detected eye movements; biometric input; and / or any combination thereof may optionally be used as input corresponding to sub-events that define the event to be identified.

[0137] Figure 2A portable multifunction device 100 with a touchscreen 112 is shown according to some embodiments. The touchscreen 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 graphics by gesturing over the graphics, for example, 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 occurs when the user breaks contact with 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 scrolling (from right to left, from left to right, up and / or down) of a finger already in contact with the device 100. In some specific embodiments or in some cases, unintentional contact with a graphic does not select the graphic. For example, a swipe gesture over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

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

[0139] In some embodiments, device 100 includes a touchscreen 112, a menu button 204, a push-button 206 for powering on / off and locking the device, one or more volume control buttons 208, a SIM card slot 210, a headset jack 212, and a docking / charging external port 124. The push-button 206 is optionally used to power on / off the device by pressing the button and holding it in the pressed state for a predefined time interval; to lock the device by pressing the button and releasing it before the predefined time interval has elapsed; and / or to unlock the device or initiate an unlocking process. In another embodiment, device 100 also accepts voice input via microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact strength sensors 165 for detecting the intensity of contact on the touchscreen 112, and / or one or more haptic output generators 167 for generating haptic outputs for a user of device 100.

[0140] Figure 3This is a block diagram of an exemplary multi-functional device with a display and a touch-sensitive surface according to some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop, desktop computer, tablet computer, multimedia player device, navigation device, educational device (such as a children's learning toy), gaming system, or control device (e.g., a home controller or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects system components and controls communication between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touchscreen display. The I / O interface 330 also optionally includes a keyboard and / or mouse (or other pointing device) 350 and a touchpad 355, and a haptic output generator 357 for generating haptic output on device 300 (e.g., similar to the reference above). Figure 1A The tactile output generator 167 and sensor 359 (e.g., optical sensor, accelerometer, proximity sensor, touch sensor and / or contact intensity sensor (similar to the one mentioned above)) are described. Figure 1A The contact strength sensor 165 is described above. The memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. The memory 370 optionally includes one or more storage devices located remotely from the CPU 310. In some embodiments, the memory 370 stores information related to the portable multifunction device 100. Figure 1A The memory 370 stores programs, modules, and data structures similar to those in the memory 102 of the portable multifunction device 100, or subsets thereof. Additionally, the memory 370 optionally stores additional programs, modules, and data structures not present in the memory 102 of the portable multifunction device 100. For example, the memory 370 of the device 300 optionally stores a drawing module 380, a rendering module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while the portable multifunction device 100 (… Figure 1A The memory 102 may optionally not store these modules.

[0141] Figure 3Each of the elements described above is optionally stored in one or more memory devices of the previously mentioned memory devices. Each of the modules described above corresponds to an instruction set for performing the functions described above. The modules or programs (e.g., instruction sets) described above need not be implemented as separate software programs, processes, or modules, and therefore various subsets of these modules may optionally be combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subgroup of the modules and data structures described above. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0142] Now let’s turn our attention to the implementation of the user interface, which is optionally implemented on, for example, a portable multifunction device 100.

[0143] Figure 4A An exemplary user interface for an application menu on a 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:

[0144] • Signal strength indicator 402 for wireless communications such as cellular signals and Wi-Fi signals;

[0145] • Time 404;

[0146] Bluetooth indicator 405;

[0147] • Battery status indicator 406;

[0148] • Tray tray 408 with icons for commonly used applications, such as:

[0149] ○ The telephone module 138 has an icon 416 labeled "telephone", which optionally includes an indicator 414 indicating the number of missed calls or voicemail messages;

[0150] ○ An icon 418 labeled "Mail" in the email client module 140, which optionally includes an indicator 410 for the number of unread emails;

[0151] ○ The icon 420 labeled "Browser" in browser module 147; and

[0152] ○ The icon 422 marked "iPod" for the video and music player module 152 (also known as the iPod module 152, a trademark of Apple Inc.); and

[0153] • Icons of other applications, such as:

[0154] ○The icon 424 of the IM module 141 marked as "Message";

[0155] ○The calendar module 148 has an icon 426 labeled "Calendar";

[0156] ○ The icon 428 of the image management module 144 is labeled "Photo".

[0157] ○ The icon 430 of camera module 143, which is labeled "camera";

[0158] ○ The icon 432 of the online video module 155, which is marked as "Online Video";

[0159] ○ The icon 434 in the Stock Market Desktop Mini Program 149-2 that is marked as "Stock Market";

[0160] ○The icon 436 of the map module 154 that is labeled "map";

[0161] ○ The icon 438 in the Weather desktop mini-program 149-1 that is marked as "Weather";

[0162] ○ The icon 440 in the alarm clock desktop mini-program 149-4 that is marked as "clock";

[0163] ○ The icon 442 of the fitness support module 142 is labeled "fitness support";

[0164] ○ The icon 444 labeled "Notepad" in Notepad module 153; and

[0165] ○ The icon 446, labeled "Settings," is used to set the settings of the device 100 and its various applications 136.

[0166] It should be pointed out that, Figure 4A The icon labels shown are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "Music" or "Music Player". Other labels may be optionally used for various application icons. In some embodiments, the label of a particular application icon includes the name of the application corresponding to that particular application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to that particular application icon.

[0167] Figure 4B A touch-sensitive surface 451 (e.g., separate from the display 450 (e.g., touchscreen display 112)) is shown. Figure 3 Devices such as tablets or touchpads (e.g., 355) Figure 3An exemplary user interface on the device 300. The device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of the sensors 359) for detecting the intensity of contact on the tactile surface 451 and / or one or more tactile output generators 357 for generating tactile outputs for the user of the device 300.

[0168] While some examples of input on a reference touchscreen display 112 (which combines a touch-sensitive surface and a display) are given below, in some implementations the device detects input on a touch-sensitive surface separate from the display, such as... Figure 4B As shown in the diagram. In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a spindle (e.g., on the display (e.g., 450)). Figure 4B The spindle corresponding to 453 in the middle (e.g., Figure 4B (452 in the example). According to these embodiments, the device detects the position corresponding to the corresponding position on the display (e.g., in the example). Figure 4B In the middle, 460 corresponds to 468 and 462 corresponds to 470) is in contact with the touch-sensitive surface 451 (e.g., Figure 4B (460 and 462 in the text). Thus, when the touch-sensitive surface (e.g., ...) Figure 4B 451) and the display of a multi-functional device (e.g., Figure 4B When 450 is separated from the touch-sensitive surface, user input detected by the device on that touch-sensitive surface (e.g., touches 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods may optionally be used for other user interfaces described herein.

[0169] Additionally, while the examples below are primarily given with reference to finger input (e.g., finger touch, single-finger tap, finger swipe), it should be understood that in some implementations, one or more of these finger inputs may be replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture may optionally be replaced by a mouse click (e.g., instead of a touch), followed by movement of the cursor along the swipe path (e.g., instead of movement of the touch). Similarly, a tap gesture may optionally be replaced by a mouse click while the cursor is over the location of the tap gesture (e.g., instead of detection of touch, followed by cessation of touch detection). Likewise, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice may optionally be used simultaneously, or mouse and finger touch may optionally be used simultaneously.

[0170] Figure 5AAn exemplary personal electronic device 500 is illustrated. Device 500 includes a body 502. In some embodiments, device 500 may include components relative to devices 100 and 300 (e.g., Figures 1A to 4B Some or all of the features described herein. In some embodiments, device 500 has a touch-sensitive display 504, referred to below as touchscreen 504. As an alternative to or complement to touchscreen 504, device 500 has a display and a touch-sensitive surface. Similar to devices 100 and 300, in some embodiments, touchscreen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). The one or more intensity sensors of touchscreen 504 (or touch-sensitive surface) can provide output data representing the intensity of the touch. The user interface of device 500 can respond to touches based on the intensity of the touch, meaning that touches of different intensities can invoke different user interface operations on device 500.

[0171] 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 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 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 incorporated herein by reference in its entirety.

[0172] In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508 (if included) may be physical. Examples of physical input mechanisms include push-buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) allow device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watch straps, bangles, trousers, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow a user to wear device 500.

[0173] Figure 5B An exemplary personal electronic device 500 is illustrated. In some embodiments, device 500 may include a reference. Figure 1A , Figure 1B and Figure 3 Some or all of the components described herein. Device 500 has a bus 512 that operatively couples I / O portion 514 to one or more computer processors 516 and memory 518. I / O portion 514 may be connected to display 504, which may have touch-sensitive components 522 and optionally have an intensity sensor 524 (e.g., a contact intensity sensor). Furthermore, I / O portion 514 may be connected to 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 may optionally be a rotatable input device or a pressable input device and a rotatable input device. In some examples, input mechanism 508 may optionally be a button.

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

[0175] 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 cause the computer processors to perform, for example, the techniques described below, including processes 700, 900, 1100, and 1300 (Figures 7, 9, 11, and 13). The computer-readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is 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 discs based on CD, DVD, or Blu-ray technology, and persistent solid-state storage such as flash memory, solid-state drives, etc. The personal electronic device 500 is not limited to... Figure 5B It can be the components and configurations, or it can include other components or additional components in a variety of configurations.

[0176] As used herein, the term "power indication" refers optionally to the power indication in devices 100, 300, and / or 500 ( Figure 1A , Figure 3 and Figures 5A to 5B A user-interactive graphical user interface object displayed on a screen. For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) optionally each constitute a functional representation.

[0177] 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 specific implementations that include a cursor or other positional 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), the cursor is positioned on a touch-sensitive surface (e.g., a...). Figure 3 The touchpad 355 or Figure 4B When an input (e.g., a press input) is detected on the touch-sensitive surface 451 of the display, the specific user interface element is adjusted according to the detected input. This applies to touchscreen displays (e.g., those capable of enabling direct interaction with user interface elements on the touchscreen display) Figure 1A The touch-sensitive display system 112 or Figure 4AIn some embodiments of the touchscreen 112, a touch detected on the touchscreen acts as a "focus selector," such that when input (e.g., a press input by touch) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touchscreen display, that particular user interface element is adjusted according to the detected input. In some embodiments, focus moves from one area of ​​the user interface to another without corresponding movement of the cursor or movement of a touch on the touchscreen display (e.g., moving focus from one button to another using tab keys or arrow keys); in these embodiments, the focus selector moves according to the movement of focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user-controlled user interface element (or a touch on the touchscreen display) that delivers the user-expected interaction with the user interface (e.g., by indicating to the device the element of the user interface that the user expects to interact with). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of the focus selector (e.g., a cursor, touch, or selection box) above the corresponding button will indicate to the user that they expect to activate the corresponding button (rather than other user interface elements shown on the device's display).

[0178] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected over 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 away, before or after contact begins to move, before contact ends, before or after contact intensity is detected to increase and / or before or after contact intensity decreases). The characteristic intensity of the contact is optionally based on one or more of the following: the maximum value of the contact intensity, the mean value of the contact intensity, the average value of the contact intensity, the value at the top 10% of the contact intensity, the half maximum value of the contact intensity, the 90% maximum value of the contact intensity, 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 contact intensity over time). In some implementations, the feature intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an action. For example, the set of one or more intensity thresholds may optionally include a first intensity threshold and a second intensity threshold. In this example, contact with a feature intensity not exceeding the first threshold results in a first action, contact with a feature intensity exceeding the first intensity threshold but not exceeding the second intensity threshold results in a second action, and contact with a feature intensity exceeding the second threshold results in a third action. In some implementations, a comparison between the feature intensity and one or more thresholds is used to determine whether to perform one or more actions (e.g., whether to perform the corresponding action or abandon performing the corresponding action) rather than to determine whether to perform the first action or the second action.

[0179] Figure 5C This demonstrates the use of multiple intensity sensors 524A-524D to detect multiple contacts 552A-552E on a touch-sensitive display 504. Figure 5C It also includes an intensity graph, which 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 both 9 intensity units, and the intensity measurements of intensity sensors 524B and 524C are both 7 intensity units. In some embodiments, the cumulative intensity is the sum of the intensity measurements of the multiple intensity sensors 524A-524D, which is 32 intensity units in this example. In some implementations, each contact is assigned a corresponding intensity, i.e., a portion of the cumulative intensity. Figure 5DThe diagram illustrates the allocation of cumulative intensity to contacts 552A-552E based on their distance from the center of force 554. In this example, each of contacts 552A, 552B, and 552E is assigned a contact intensity of 8 intensity units of the cumulative intensity, and each of contacts 552C and 552D is assigned a contact intensity of 4 intensity units of the cumulative intensity. More generally, in some specific implementations, each contact j is assigned a corresponding intensity Ij according to a predefined mathematical function Ij = A·(Dj / ΣDi), which is a portion of the cumulative intensity A, 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. Reference operations can be performed using electronic devices similar to or equivalent to devices 100, 300, or 500. Figures 5C-5D The operation described above. In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine the intensity of a single characteristic (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 within... Figures 5C-5D This is intended to assist readers.

[0180] In some implementations, a portion of the gesture is identified to determine the characteristic intensity. For example, a touch-sensitive surface optionally receives a series of swipe contacts that transition from a starting position to an ending position, where the contact intensity increases. In this example, the characteristic intensity of the contact at the ending position is optionally based only on a portion of the series of swipe contacts, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the ending position). In some implementations, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of the following: unweighted moving average smoothing algorithm, triangular smoothing algorithm, median filter smoothing algorithm, and / or exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact to achieve the purpose of determining the characteristic intensity.

[0181] Optionally, the contact intensity on a touch-sensitive surface is 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 performs an operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device performs an operation different from the operation typically associated with clicking a button on a physical mouse or touchpad. In some embodiments, when a contact with a characteristic intensity lower than the light press intensity threshold (e.g., and higher than the nominal contact detection intensity threshold, where contacts lower than the nominal contact detection intensity threshold are no longer detected) is detected, the device will move the focus selector based on the movement of the contact on the touch-sensitive surface without performing the operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent across different groups of user interface figures.

[0182] An increase in contact intensity from 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 intensity from 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 intensity from 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 a contact on the touch surface. A decrease in contact intensity from above a contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting a contact being lifted off 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.

[0183] In some embodiments described herein, one or more operations are performed in response to detecting a gesture including 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 intensity of the contact (or multiple contacts) increases to above a press input intensity threshold. In some embodiments, the corresponding operation is performed in response to detecting that the intensity of the corresponding contact increases to above a press input intensity threshold (e.g., a "downward stroke" of the corresponding press input). In some embodiments, the press input includes the intensity of the corresponding contact increasing to above a press input intensity threshold and the intensity of the contact subsequently decreasing to below the press input intensity threshold, and the corresponding operation is performed in response to detecting that the intensity of the corresponding contact subsequently decreases to below the press input threshold (e.g., an "upward stroke" of the corresponding press input).

[0184] Figures 5E-5HThe detection of gestures is shown, including gestures involving contact 562 with an intensity ranging from less than... Figure 5E The light press intensity threshold (e.g., "IT") L The intensity of ”) increases to higher than Figure 5H The deep press intensity threshold (e.g., "IT") D The intensity of the press input corresponds to the strength of the press. On the user interface 570, which includes 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, the gesture performed by 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 the intensity of the contact 562 within a deep press intensity threshold (e.g., "IT"). D The intensity reaches its peak value above 562. Contact is maintained on the touch-sensitive surface 560. In response to a detected gesture, and based on the intensity increasing to a deep press intensity threshold (e.g., "IT") during the gesture... D The above contact 562 displays the scale representation 578A-578C (e.g., thumbnails) of the document recently opened for application 2, such as... Figures 5F-5H As shown. 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... Figures 5E-5H This is intended to assist readers.

[0185] In some implementations, the display of icons 578A-578C includes animation. For example, icon 578A might initially appear near application icon 572B, such as... Figure 5F As shown, as the animation progresses, icon 578A moves upwards, and icon 578B appears near application icon 572B, as shown. Figure 5G As shown in the diagram. Then, representation 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed near application icon 572B, as shown. Figure 5H As shown in the diagram. This indicates that 578A-578C form an array above icon 572B. In some implementations, the animation progresses according to the intensity of contact 562, such as... Figures 5F-5G As shown, where 578A-578C appear and increase with the intensity of contact 562 towards the pressure threshold (e.g., "IT"). D The animation progresses upwards as it increases in intensity. In some implementations, the intensity upon which the animation progresses is based is the characteristic intensity of the contact. Reference can be performed using electronic devices similar to or equivalent to devices 100, 300, or 500. Figures 5E-5H The aforementioned operations.

[0186] In some implementations, the device employs intensity hysteresis to avoid unintended inputs sometimes referred to as "jitter," wherein the device defines or selects a hysteresis intensity threshold that has a predefined relationship with 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 percentage of the press input intensity threshold). Therefore, in some implementations, a press input includes an increase in the intensity of the corresponding contact above the press input intensity threshold and a subsequent decrease in the intensity of that contact 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 below the hysteresis intensity threshold (e.g., an "upstroke" of the corresponding press input). Similarly, in some implementations, 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 the contact intensity subsequently decreases to an intensity equal to or below the hysteresis intensity threshold, and a corresponding operation is performed in response to detecting a press input (e.g., an increase or decrease in contact intensity depending on the environment).

[0187] For ease of explanation, optionally, the description of an operation triggered in response to a press input associated with a press input strength threshold or in response to a gesture including a press input is provided in response to detecting any of the following conditions: the contact strength increases to above the press input strength threshold, the contact strength increases from below a hysteresis strength threshold to above the press input strength threshold, the contact strength decreases to below the press input strength threshold, and / or the contact strength decreases to below the hysteresis strength threshold corresponding to the press input strength threshold. Additionally, in the example where the operation is described as being performed in response to detecting a decrease in contact strength below the press input strength threshold, the operation is optionally performed in response to detecting a decrease in contact strength below a hysteresis strength threshold corresponding to and less than the press input strength threshold.

[0188] As used herein, "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 on the device (e.g., become open). In some implementations, the downloaded application becomes an installed application using an installer that extracts program portions from the downloaded software package and integrates the extracted portions with the computer system's operating system.

[0189] As used herein, the terms "open application" or "running application" refer to a software application that maintains state information (e.g., as part of device / global internal state 157 and / or application internal state 192). An open or running application is optionally any of the following types of applications:

[0190] • The active application currently displayed on the screen of the device that is using the application;

[0191] • Background applications (or background processes) that are not currently displayed but whose one or more processes are being handled by one or more processors; and

[0192] • A suspended or hibernating application that is not running but has state information stored in memory (both volatile and non-volatile) that can be used to resume the application's execution.

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

[0194] Now let’s turn our attention to the implementation of user interfaces (“UIs”) and associated processes on electronic devices (such as portable multifunction devices 100, 300 or 500).

[0195] User interface and related processes

[0196] Cellular Identifier Settings User Interface

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

[0198] Figures 6A-6R Exemplary methods for presenting a settings user interface associated with a cellular identifier in an electronic device according to some embodiments of the present disclosure are illustrated. The embodiments in these figures are used to illustrate the processes described below, including references to... Figures 7A-7IThe process described above.

[0199] Figure 6A An exemplary device 500 with a touchscreen 504 is shown, such as a reference device. Figures 5A-5H The touchscreen 504 optionally displays one or more user interfaces including various content. Figure 6A In the example shown, touchscreen 504 displays instruction 602 for the process of setting up a cellular plan on an electronic device. In some embodiments, instruction 602 is presented in response to the introduction of a cellular identifier (e.g., SIM, eSIM, etc.) into electronic device 500 or in response to a user's selection of an enablement representation for setting up a new cellular identifier (e.g., in a setup user interface). In some embodiments, device 500 displays instruction 602 as part of the initial setup process of device 500. In some embodiments, device 500 displays instruction 602 in response to the introduction of a second cellular identifier into device 500 when device 500 has been configured to use a first cellular identifier. Figure 6A The touchscreen 504 optionally displays a "Continue" indication 604 that allows initiating the process for configuring a new cellular identifier, and a "Not Now" indication 606 that allows abandoning the process for configuring a new cellular identifier. Figure 6A As shown, the user may optionally (e.g., using contact 603) select “Continue” power indication 604.

[0200] In some implementations, in response to the selection of the "Continue" enable signal 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. For example, as Figure 6B As shown, touchscreen 504 presents instruction 608 to the user, which (e.g., "Scan QR code to add eSIM") for capturing an image associated with a cellular identifier (e.g., a QR code). Electronic device 504 simultaneously presents viewfinder 610 and image capture capability display 612 along with instruction 608 for image capture. 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 a 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 a cellular identifier accessible to the electronic device, such as those referenced below. Figure 6D The aforementioned user interface.

[0201] If the electronic device 500 fails to recognize the eSIM based on the captured image (e.g., the image is blurry, the QR code is invalid, etc.), or if the eSIM is successfully recognized using the captured image, a password or other authentication credentials need to be added to the device 500, then the electronic device 500 optionally presents different user interfaces for adding a SIM to the electronic device, such as... Figure 6C The user interface shown. (As shown) Figure 6C As shown, electronic device 500 presents a user interface for a cellular identifier added using password authentication. Figure 6C The user interface includes an indication of the cellular identifier's associated phone number 614, a text input field 616, and a dial pad 618 (or keypad) where the 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 may optionally be able to use the cellular identifier to perform functions; in response to an incorrect password, the electronic device 500 may optionally be unable to use the cellular identifier to perform functions, and adding the cellular identifier to the device 500 may optionally fail. In some embodiments, the user can enter identification information of the cellular identifier, such as the phone number associated with the cellular identifier, before entering a password.

[0202] Once the electronic device 500 successfully identifies the cellular identifier and / or is granted access to the cellular identifier, it may optionally be able to present a settings user interface for changing settings associated with the cellular identifier accessible to the electronic device. For example, Figure 6D A cellular identifier setup user interface is shown for setting tags associated with each cellular identifier of the electronic device 500. (See diagram.) Figure 6D As shown, electronic device 500 presents an indication 620 for changing the tag used to identify the first cellular identifier of the electronic device, and an indication 620 for changing the tag used to identify the second cellular identifier of the electronic device (e.g., Figures 6A-6CThe indication 622 for the tag of a cellular identifier added to device 500 (optionally a second cellular identifier added to device 500) is shown. The newly added cellular identifier is optionally labeled "secondary" by default, and the existing cellular identifier is optionally labeled "primary" by default; however, in some embodiments, when a new cellular identifier is added to electronic device 500, the newly added cellular identifier is labeled "primary" by default, and the existing cellular identifier is labeled "secondary" by default. The indication 620 for changing the tag identifying the first cellular identifier includes an indication of the telephone number associated with the first cellular identifier and the tag of the first cellular identifier (e.g., "primary"). The indication 622 for changing the tag identifying the second cellular identifier includes an indication of the telephone number associated with the second cellular identifier and the tag of the second cellular identifier (e.g., "secondary"). Figure 6D As shown, the user (e.g., using contact 603) selects the second indicator 622 to edit the tag of the second cellular identifier.

[0203] In response to the user's selection of the display indicator 622, the electronic device 500 presents a user interface for editing the tag associated with the second cellular identifier, such as... Figure 6E As shown. The user interface includes a second cellular identifier indication 624, multiple optional power representations for setting the tag as one of a plurality of predefined cellular identifier tags (e.g., “primary” 626a, “secondary” 626b, “data” 626c, and “travel” 626d), and a power representation 628 that the user can select for inputting a custom tag for the cellular identifier. Figure 6E Each indicator 626a-d in the configuration includes the name of the cellular identifier's tag (e.g., "primary," "secondary," "data," and "travel") and a representative indication of the cellular identifier. This indication of the cellular identifier is optionally presented in the user interface of the electronic device 500 in association with the functionality of the cellular identifier, as shown in reference to... Figures 10A-11Q A more detailed description follows. The indication of the cellular identifier is optionally based on the text of the cellular identifier's label, such as including the first letter of the cellular identifier's label, such as using an indication with a "D" for the "Data" label 626c. Figure 6E As shown, the user (e.g., using contact 603) selects an energy representation 628 for creating a custom tag for a cellular identifier.

[0204] In response to Figure 6E In the user's selection, the electronic device 500 presents a user interface for creating custom tags for the cellular identifier, such as... Figure 6F As shown. The user interface includes a cellular indicator 630, a text input field 632, and a soft keyboard 634. Figure 6GAs shown, a user may input the label “personal” via one or more contacts 603 at a soft keyboard 634.

[0205] Figure 6H It shows in Figure 6F The user interface presented by the electronic device 500 after the user creates a custom "personal" tag for the second cellular identifier includes a power indicator 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 just the first letter, allowing the user to distinguish these labels with the same first letter. In some embodiments, device 500 utilizes enough letters of conflicting labels until the indicators of the conflicting labels are different. The remaining labels "Secondary," "Data," and "Travel" continue to be indicated using indicators that include the first letter of these labels, as long as labels with the same first letter 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 (e.g., 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 first letter of the word of the label (e.g., the indicator for "Data Roaming" is DR).

[0206] After configuring the tag used for the second cellular identifier as "personal", such as Figure 6H As shown, the user can optionally navigate back to the settings user interface used to update the tags associated with each cellular identifier, such as... Figure 6I As shown. Figure 6I As shown, the enablement display 622 associated with the second cellular identifier is updated to indicate that the second cellular identifier is marked as "personal".

[0207] In response to the detection of Figure 6I With the "Continue" selection (e.g., via contact 603), the electronic device 500 optionally presents a settings user interface for configuring the functions to be performed using each cellular identifier associated with the device. Figure 6J As shown, the electronic device 500 presents a user interface for setting the functions to be performed using the "personal" cellular identifier. The user can select from options 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 on device 500 for phone and messaging functions.

[0208] In some implementations, the "primary number for telephone / SMS" is the cellular identifier used by the electronic device 500 by default for telephone calls and SMS messaging, the "secondary number for telephone / SMS" is configured to perform telephone and SMS operations outside of default (e.g., a user requests to use the secondary cellular identifier when the primary cellular identifier is unavailable, or a user requests to initiate communication with a contact associated with the secondary cellular identifier), and the "data-only" cellular identifier is configured to perform cellular data operations only, and optionally is the default cellular identifier used 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 to "Second number for phone / SMS" because the existing cellular identifier is "Primary number for phone / SMS" by default. In some implementations, other default configurations and list orders are possible. In some implementations, the electronic device configures one cellular identifier as the primary number for phone / SMS and another cellular identifier as a secondary number for phone / SMS. In some implementations, instead of configuring a cellular identifier as a secondary number for phone / SMS, the electronic device configures one of the cellular identifiers for data only.

[0209] After configuring the functions to be performed using the "personal" cellular identifier on device 500, device 500 displays a user interface presenting the function settings of multiple cellular identifiers available for use by electronic device 500, such as... Figure 6K As shown. Figure 6KAs shown, the user interface includes indications 638a of functions associated with the “personal” cellular identifier. Indication 638a includes text identifying the cellular identifier (e.g., “personal”), a visual indication of the cellular identifier (e.g., an icon with the letters “Pe”), an indication of the phone number associated with the cellular identifier (e.g., “555-987-6543”), and text indicating the cellular identifier’s functional settings (e.g., “Default number for phone and SMS”). In some embodiments, electronic device 500 is configured to communicate using a data-based enhanced messaging service optionally associated with a user account of electronic device 500. Electronic device 500 optionally uses the cellular identifier designated as the “default number for phone 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 indications 638b of functions associated with the “master” cellular identifier. Instruction 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 letter "Pr"), an indication of the phone 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 and SMS"). As mentioned above, because both "personal" and "primary" begin with the letter "P", the instructions for these cellular identifiers include the first two letters of the label of these cellular identifiers (e.g., "Pe" and "Pr").

[0210] As previously described, the indication of the cellular identifier of device 500 may optionally be 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. For example, Figure 6L The contact user interface for the contact associated with the "primary" cellular identifier is shown. Figure 6LAs shown, the contact user interface includes an indication 640 of the contact's name (e.g., "Mary Smith"), a first phone number indication 642a of a first phone number associated with the contact, a second phone number indication 642b of a second phone number associated with the contact, and multiple indications 646a-646d selectable to perform various actions relative to the contact (e.g., "Send Message" 646a, "Share Contact" 646b, "Add to Favorites" 646c, "Share My Location" 646d). Each of the phone number indications 642a-642b includes an indication 644 of the cellular identifier associated with the contact (e.g., the "primary" cellular identifier indicated by the "Pr" indication). The phone number indications 642a-642b are selectable to initiate a telephone call to the corresponding phone number indicated by the indication using the cellular identifier associated with the contact, as indicated by the default indication 644.

[0211] When a user changes the label of a cellular device (e.g., "Main", "Personal", etc.), the visual indications of that cellular device (e.g., icons including "Pr", "Pe", etc.) optionally update across multiple user interfaces of the electronic device to match the new label of the cellular device. For example, as Figure 6M As shown, when a user renames the “primary” cellular identifier (associated with the phone number 555-123-4567) to “business”, the instructions for that cellular identifier in the settings user interface are updated to reflect this change. Figure 6M The user interface shown is Figure 6K The user interface shown is essentially the same, except that the "primary" cellular identifier has been renamed "Business". Based on the updated label of this cellular identifier, the electronic device 500 displays the "Business" label in the user interface and updates the cellular identifier's indication to include "B" (instead of "Pr"). Because "Business" and "Personal" begin with different letters, the indication of the "primary" cellular identifier has been updated from "Pr" to "P," as using the first letter of the cellular identifier's label to indicate the cellular identifier is sufficient to distinguish them from each other.

[0212] Similarly, Figure 6N A contact user interface is shown for a contact associated with the “Business” cellular identifier, which was previously labeled as the “Main” cellular identifier. Figure 6N The contact user interface shown is basically similar to Figure 6L The contact user interface shown differs in that indicator 644 has been updated to reflect that the "primary" cellular identifier has been renamed "business". Similarly, indicator 644 includes... Figure 6L The letter "B" is shown instead of "Pr".

[0213] Figure 6O An electronic device 500 is shown displaying a cellular identifier settings user interface, via which new cellular identifiers can be added to the device 500. In some embodiments, this cellular identifier settings user interface is accessible from the electronic device's settings user interface, which includes indications selectable to navigate to various other settings user interfaces of the electronic device (e.g., notification settings, general settings, display settings, sound settings, password and authentication settings, etc.). Figure 6O As shown, the user (e.g., using contact 603) selects a power indicator 648 for adding a new cellular identifier to the electronic device (e.g., "Add New eSIM"). In response to the user's selection, the electronic device presents a user interface for adding the new cellular identifier, such as... Figure 6B The camera user interface and / or shown Figure 6C The password user interface shown.

[0214] Figure 6P The image shows the cellular identifier settings user interface displayed by the electronic device 500 after the user has added and marked a new cellular identifier "trip" as indicated by instruction 638d. (See image for details.) Figure 6P As shown, electronic device 500 optionally disables the "travel" cellular identifier for performing any action because, in some embodiments, only two cellular identifiers on device 500 can be activated at any given time, thus indicating that the cellular identifier is "inactive". Therefore, the cellular identifier setting user interface optionally includes an "activate" power indicator 650, which can be selected to activate the "travel" cellular identifier, enabling electronic device 500 to perform one or more functions using the "travel" cellular identifier.

[0215] like Figure 6Q As shown, the user (e.g., using contact 603) selects "Activate" power indicator 650. In response, device 500 activates "Travel" cellular identifier to allow electronic device 500 to use "Travel" cellular identifier to perform operations, 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 is the most recently activated cellular identifier), the "Personal" cellular identifier becomes a "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). Instructions 638a, 638c, and 638d are updated according to these new functional settings of the cellular identifiers. Additionally, instruction 638c for the "Business" cellular identifier is updated to include an "Activate" indicator 650, which can be selected to activate the "Business" cellular identifier for performing operations on the electronic device.

[0216] Figures 7A-7I This is a flowchart illustrating a method 700 for presenting a setup user interface associated with a cellular identifier according to some embodiments of the present disclosure. Method 700 is optionally performed on an electronic device (such as device 100, device 300, device 500), as referenced above. Figures 1A-1B , Figures 2-3 , Figures 4A-4B and Figures 5A-5H The operations in method 700 may be optionally combined, and / or the order of some operations may be optionally changed.

[0217] As described below, method 700 provides a method for presenting a settings user interface associated with a cellular identifier. This method reduces the cognitive burden on the user when interacting with the device user interface of this 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 charging cycles.

[0218] 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 touchscreen (e.g., a tablet, smartphone, media player, or wearable device) or a computer including one or more of a keyboard, mouse, touchpad, and touchscreen). 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 via one or more input devices 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.). Figure 6O The selection of the "Add New eSIM" button 648 is shown. In some implementations, electronic devices are capable of having more than one cellular identifier (e.g., SIM card, eSIM, etc.), such as in... Figures 6A-6CAs shown in the diagram. In some embodiments, the input corresponding to the request to set up the first cellular identifier is introducing the cellular identifier into the electronic device (e.g., installing a new SIM or eSIM). In some embodiments, the input corresponding to the request to set up the first cellular identifier is a selection of an indication or button that causes the electronic device to display a cellular identifier settings or settings user interface when activated. In some embodiments, setting up the first cellular identifier is not initiated until two cellular identifiers are added to the electronic device.

[0219] In some implementations, in response to receiving a request to set a first cellular identifier for the electronic device, the electronic device initiates (704) a process to set a first cellular identifier for the electronic device (e.g., Figures 6A-6J The process illustrated (e.g., configuring a first cellular identifier for use at an electronic device, such as naming the cellular identifier, identifying the functions to be performed by the electronic device using the first cellular identifier, etc.). In some embodiments, the process of setting up the first cellular identifier is performed when the first cellular identifier is first introduced into the device or later (e.g., to update one or more settings of the first cellular identifier), such as in Figure 6O As shown in the image.

[0220] In some implementations, the process of setting a first cellular identifier for an electronic device includes receiving (708) input via one or more input devices of a first tag defining the first cellular identifier of the electronic device (e.g., a textual nickname of the cellular identifier, such as "primary," "secondary," "data," "telephone," "work," "personal," "domestic," "international," etc.). Figure 6G The input at the soft keyboard 634 shown (e.g., using contact 603) involves the electronic device displaying indicators based on a first label, such as... Figure 6L The indicator 644 (e.g., text or image derived from the tag of the first cellular identifier, such as an icon including one or more letters preceding the tag of the cellular identifier) ​​indicates the first cellular identifier. In some embodiments, the electronic device presents a user interface that includes one or more labels from a plurality of optional predefined labels, such as Figure 6E Labels 626a-d (e.g., “primary”, “secondary”, “data”, “telephone”, “work”, “personal”, “family”, “international”, etc.) and / or text input user interfaces (e.g., text boxes and optional soft keyboards), such as Figures 6F-6GAs shown. The label is optionally displayed as an indicator (e.g., icon, thumbnail, text, or image) adjacent to the first cellular identifier and optionally adjacent to an indicator of the phone number associated with the cellular identifier. In some embodiments, the indicator (e.g., icon) is automatically generated based on the label representing the first cellular identifier (e.g., a user-defined nickname for the cellular identifier). For example, the "primary" cellular identifier label is optionally indicated by an indicator such as an icon with the text "P", "Pr", or "P2". When the electronic device uses the first cellular identifier to perform functions (e.g., make a call, send a message, download or upload data, interact with a contact), the electronic device optionally presents the indicator in one or more user interfaces.

[0221] The electronic device optionally receives (710) input via one or more input devices to select a corresponding set of one or more functions for the first cellular identifier (e.g., making and receiving phone calls, sending text messages, downloading or uploading data, storing and retrieving contact information of one or more contacts, etc.). Figure 6J Contact 603 in the middle), these functions such as by Figure 6J The functionality represented by 636a-c in the specification indicates that an electronic device is capable of performing multiple functions using a first cellular identifier of the electronic device, including one or more selected functions. The user optionally selects which functions of the electronic device are performed by default using the first cellular identifier. In some embodiments, the electronic device includes two or more cellular identifiers, each with a different function selected for it. For example, the electronic device optionally includes a "primary" cellular identifier and a "data" cellular identifier. During setup, the user optionally selects "data upload and download" as the function of the "data" cellular identifier, and optionally selects functions such as telephone calling and text messaging as the functions of the "primary" 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 telephone calls, the "primary" cellular identifier is optionally used by default to perform telephone calls. In some embodiments, the electronic device is capable of performing a function using a cellular identifier different from the default cellular identifier selected for a given 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. Furthermore, in some implementations, individual contacts are associated with one of the cellular identifiers, enabling communication with that individual to be performed using the cellular identifier associated with the contact instead of the default cellular identifier for such communication.

[0222] In some implementations, in response to receiving input (712) to select a corresponding set of one or more functions for the first cellular identifier, such as detecting Figure 6J Upon 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., for a primary number 636b for telephone / SMS), the electronic device initiates (712) a process to enable the first cellular identifier to be used for the first set of one or more functions, such as Figure 6K As indicated by instruction 638a of the “personal” cellular identifier, and based on the determination that the corresponding group of one or more functions is a second group of one or more functions different from the first group of one or more functions (e.g., secondary number for telephone / SMS 636a, as...), Figure 6J As shown), the electronic device initiates (714) a process to enable the first cellular identifier to be used for one or more functions of a second group, such as Figure 6K The indication 638b of the “primary” cellular identifier is shown. In some embodiments, the first group of one or more functions includes at least one function not included in the second group of one or more functions. In some embodiments, the second group of one or more functions includes at least one function not included in the first group of one or more functions. In some embodiments, the first group of one or more functions and the second group of one or more functions include one or more shared functions. In some embodiments, the first group of one or more functions and the second group of one or more functions are mutually exclusive.

[0223] The above-described method of placing a first cellular identifier on an electronic device allows the electronic device to be configured to perform multiple functions using the first cellular identifier. This simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by using the first cellular identifier to perform selected functions without requiring explicit user input for using the first cellular identifier for each selected function). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0224] In some implementations, the corresponding set of one or more functions is one of voice and messaging functions, data functions, and primary cellular identifier functions (718), such as Figure 6JAs indicated in instructions 636a-c. The primary cellular identifier functionality optionally includes voice, messaging, and data functions, and the cellular identifier selected to perform the primary cellular identifier functions is optionally the default cellular identifier used to perform those functions. In some embodiments, the primary cellular identifier is used by default for voice, messaging, and data functions unless these functions are unavailable (e.g., the primary cellular identifier has a poor signal or no service). When the primary cellular identifier is unavailable to perform the corresponding function, a different cellular identifier configured for that function optionally performs the corresponding function. For example, the primary cellular identifier optionally defaults to making telephone calls when it is capable of making telephone calls. When the primary cellular identifier is unavailable, a secondary cellular identifier configured for voice communication optionally makes telephone calls.

[0225] The aforementioned method of selecting the function of the first cellular identifier among voice, messaging, data, and primary cellular identifier functions allows electronic devices to be configured to perform multiple functions using the first cellular identifier. This simplifies user interaction with the device and enhances device operability (e.g., by using the first cellular identifier to perform the selected function without requiring explicit user input for using the first cellular identifier for the selected function each time it is to be performed). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0226] In some implementations, the first cellular identifier is set for the electronic device (e.g., by [unclear]). Figure 6P Prior to the process of the "travel" cellular identifier indicated in instruction 638d, the electronic device is configured to use a second cellular identifier (e.g., by...). Figure 6P The instruction 638a indicates a “personal” cellular identifier to perform the primary cellular identifier function (720). For example, only a second cellular identifier is configured on the electronic device, or both a first cellular identifier and a second cellular identifier are configured on the electronic device and the first cellular identifier is configured for the secondary cellular identifier function.

[0227] In some implementations, the process of setting up a first cellular identifier for an electronic device includes (722) configuring the electronic device (724) to use the first cellular identifier to perform primary cellular identifier functions (e.g., as...). Figure 6R (As indicated by instruction 638d in the document). In some embodiments, the user changes the settings to set the function of the first cellular identifier as a primary cellular identifier function (e.g., a default cellular identifier for performing voice, messaging, and / or data functions). The setup process for the first cellular identifier optionally includes configuring the electronic device (726) to use a second cellular identifier to perform secondary cellular identifier functions (e.g., pure data) (e.g., as shown in the document). Figure 6R (As indicated in instruction 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 functions). 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 remains the primary cellular identifier function, the function of the second cellular identifier may optionally be updated to data-only (e.g., while the first cellular identifier remains 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 by default for one or more designated contacts to perform voice and messaging functions, and uses the first cellular identifier by default for all other contacts and phone numbers for voice and messaging operations).

[0228] The aforementioned method of configuring the second cellular identifier to perform the function of a secondary cellular identifier in response to configuring the first cellular identifier to perform the function of a primary cellular identifier allows the electronic device to continue using the second cellular identifier as a secondary cellular identifier when the first cellular identifier is configured as the primary cellular identifier. This 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 as a secondary cellular identifier). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0229] In some implementations, configuring an electronic device to perform secondary cellular identifier functions using a second cellular identifier includes configuring the electronic device to use the second cellular identifier (e.g., by...) Figure 6R The “personal” cellular identifier indicated in instruction 638a is used only for cellular data (728). In some embodiments, the electronic device automatically updates the function of the second cellular identifier to data function only when the function of the first cellular identifier is updated to the function of the primary cellular identifier, 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.

[0230] The aforementioned method of configuring the second cellular identifier to perform cellular data functions in response to configuring the first cellular identifier to perform primary cellular identifier functions allows the electronic device to continue using the second cellular identifier for data functions when the first cellular identifier is configured as the primary cellular identifier. This 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 cellular data functions). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0231] In some implementations, the process of setting up a first cellular identifier for an electronic device includes (730): requesting (732) access credentials (e.g., PIN, password, passphrase, QR code authentication, or other authentication) to allow access to the first cellular identifier, such as in Figures 6B-6C As shown in the diagram. 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 PINs, a soft keyboard for accepting passwords or passcodes, a camera user interface for accepting QR codes, or a user interface adapted to accept another form of authentication. The process optionally includes receiving (734) access credentials (e.g., ) via one or more input devices to allow access to the first cellular identifier. Figure 6B Image 610 or Figure 6C The password 616 in the electronic device (e.g., the electronic device detects user input access credentials), and in response to receiving the input access credentials (736), based on determining that the input access credentials are correct, the process of allowing (738) to set the first cellular identifier for the electronic device to continue, such as in Figure 6D As shown in the diagram. 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. If it is determined that the entered access credentials are incorrect, the electronic device abandons (740) allowing the process of setting up 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 a capability indication that can be selected to display a user interface for accepting credentials again, allowing the user to try entering access credentials again.

[0232] The above-described method of authenticating the first cellular identifier allows electronic devices 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 (e.g., by ensuring that the user of the electronic device is authorized to access the first cellular identifier before configuring the settings of the first cellular identifier). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

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

[0234] The aforementioned method, which allows users to authenticate the first cellular identifier by capturing images, enables electronic devices to authenticate the first cellular identifier without manual authentication input from the user. This simplifies the interaction between the user and the device and enhances the operability of the device. In turn, it reduces power consumption and extends the battery life of the device by enabling users to use the device more quickly and efficiently.

[0235] In some implementations, in response to capturing an image (610)(744) corresponding to a pattern of a first cellular identifier via a camera of an electronic device (e.g., an image of a QR code associated with an eSIM or another type of cellular identifier), such as in Figure 6B As shown: Based on the determination that the first cellular identifier was 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 Figure 6D As shown, and based on the determination that the first cellular identifier was not successfully identified using the image (e.g., the image is not an image corresponding to the graphic of the cellular identifier, the image does not clearly capture the 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) via one or more input devices (e.g., via interaction with the soft dial keypad 618 presented on the touchscreen 504). Figure 6C(As shown) 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, this user interface includes fields for entering text associated with the cellular identifier's identity (e.g., a serial number or some other identification name, number, or code) and fields for entering access credentials. That is, the text associated with the cellular identifier and the access credentials are not necessarily the same. In some embodiments, the electronic device also presents a display that can be optionally used to capture another image corresponding to the graphic of the first cellular identifier.

[0236] The aforementioned method of allowing users to manually enter information about the first cellular identifier when authentication via image capture fails allows electronic devices to provide an alternative method for users to authenticate the first cellular identifier when image-based authentication fails. This simplifies the interaction between the user and the device and enhances the device's operability (e.g., by allowing users to use an alternative authentication method when camera authentication fails). This, in turn, reduces power consumption and extends the device's battery life by enabling users to use the device more quickly and efficiently.

[0237] In some implementations, in response to receiving input of a first tag defining a first cellular identifier of an electronic device (e.g., a textual nickname of the cellular identifier, such as "primary," "secondary," "data," "telephone," "work," "personal," "domestic," "international," etc.), the electronic device generates (750) an indicator (e.g., text, image, or icon) corresponding to the first cellular identifier based on the first tag (e.g., selecting the content of the indicator based on the text of the tag, such as including the first letter of the tag (e.g., the indicator includes "P" or "P1" based on the tag "primary"), the first two letters of the tag (e.g., the indicator includes the text "Pr" based on the tag "primary"), or the first two words of the tag (e.g., the indicator includes the text "UD" based on the tag "unrestricted data"), as referenced above. Figure 6H An example of generating an indicator corresponding to the first cellular identifier is described in more detail.

[0238] In some implementations, the indicator (e.g., Figure 6L The indicator 644 shown is displayed by the electronic device in at least one or more user interfaces outside the process of setting up the first cellular identifier for the electronic device (such as in...). Figure 6LThe contact card user interface shown indicates the first cellular identifier (752). In some embodiments, this 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 telephone user interface, a voicemail user interface, etc. For example, the indicator is displayed next to visual indicators of communication performed using the first cellular identifier (e.g., message indicator, voicemail indicator, incoming or outgoing telephone call indicator, etc.), such as in... Figure 6L As shown in the diagram. In some implementations, the contact user interface presents multiple phone numbers for the corresponding contact and includes a single indication of the cellular identifier associated with that contact, instead of as shown in the diagram. Figure 6L The diagram includes multiple indicators 644. The indicator associated with the cellular identifier can optionally be selected to allow the electronic device to display an option for changing which cellular identifier the corresponding contact is associated with.

[0239] The aforementioned method of generating an indicator corresponding to a user-defined tag for a first cellular identifier and presenting that 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 the corresponding operation on the electronic device. This 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 the corresponding operation without requiring the user to provide input to display cellular identifier information). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0240] In some implementations, generating an indicator corresponding to the first cellular identifier includes (754) determining the generation of an indicator corresponding to the first cellular identifier (e.g., by...). Figure 6M The indicator 638c in the "Business" cellular identifier) ​​has a first number of characters (e.g., starting from the first character of the first tag) and the indicator will be compared with the one corresponding to the cellular identifier (e.g., by the one indicated by the first character of the first tag). Figure 6M To distinguish the second indicator of the second tag (indicated by indicator 638a of the "personal" cellular identifier) ​​from the existing second indicator of the first cellular identifier, the electronic device generates (756) an indicator corresponding to the first cellular identifier with a first number of characters (e.g., one character). In some embodiments, the tags of the second cellular identifier and the first cellular identifier begin with different letters, so using the first letter of the tag as the indicator of the cellular identifier can distinguish them. For example, if the tags of the first cellular identifier and the second cellular identifier are "primary" and "secondary" respectively, then the corresponding indicators of these tags are optionally "P" and "S" respectively. The second indicator is generated according to the determination of the first cellular identifier (e.g., by the first cellular identifier). Figure 6K The indicator 638b of the "master" cellular identifier, having a first number of characters, does not distinguish the indicator from an existing second indicator corresponding to the second tag of the cellular identifier (e.g., the tags of the second and first cellular identifiers begin with the same letter, so using only the first letter of the tag as the indicator will not produce different tags), the electronic device generates (758) a second number of characters (e.g., two) corresponding to the first cellular identifier, greater than the first number of characters, such as in Figure 6K As shown in the diagram. In some embodiments, the electronic device uses the first two or more characters of the tag as an indicator, or uses an initial letter and a unique number for the tag. For example, if the tags for the first and second cellular identifiers are “Master” and “Personal”, the corresponding indicators for these tags are optionally “Pr” and “Pe”. Similarly, if the tags for the first and second cellular identifiers are “Master” and “Shared”, the corresponding indicators for these tags are optionally “Pri” and “Pro”. In some embodiments, when the maximum number of characters preceding each tag (e.g., 3) is the same, the electronic device uses numbers to distinguish the indicators from each other. For example, if the tags for the first and second cellular identifiers are “Master” and “Private”, the corresponding indicators for these tags are optionally “P1” and “P2”. In this way, the electronic device is able to provide a unique indicator for each cellular identifier for use in various user interfaces of the electronic device associated with one or more functions of the cellular identifier. When a user interface associated with a function is presented, these unique indicators for the cellular identifiers enable the electronic device to communicate to the user which cellular identifier is being used to perform various functions.

[0241] The aforementioned method of generating unique identifiers for the first and second cellular identifiers allows electronic devices to provide distinguishing information to users, which simplifies user-device interaction and enhances device operability (e.g., by explicitly presenting an indication of which cellular identifier is being used to perform a corresponding function at the electronic device, enabling users to perform functions using the cellular identifier they intend to use). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0242] In some implementations, after a first cellular identifier is set for an electronic device, the electronic device displays (760) a representation of the first cellular identifier on a display (e.g., Figure 6P The indication of the "service" cellular identifier (638c) and the representation of the second cellular identifier (e.g., Figure 6P The “Travel” cellular identifier indicator 638d (for example, displayed in the cellular settings user interface).

[0243] In some implementations, the second cellular identifier (e.g., by...) Figure 6P The indication 638d indicates that the "travel" cellular identifier 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 the indication of the second cellular identifier is simultaneously displayed (762) with an indication (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 the image.

[0244] In some implementations, when the representation of the first cellular identifier (638c) and the representation of the second cellular identifier (638d) are displayed on the display, the electronic device receives (764) input via one or more input devices corresponding to the selection of the enable representation (650) for activating the second cellular identifier (e.g., a tap or touch received at a touchscreen, a click received by a mouse or touchpad, a shortcut entered at a keyboard, dial pad, or soft keyboard, voice input, etc.). Figure 6Q The contact 603 shown, such as in Figure 6Q As shown in the image.

[0245] In some implementations, in response to receiving an input corresponding to a selection for activating a second cellular identifier (e.g., a "travel" cellular identifier indicated by indicator 638d), the electronic device activates (766) the second cellular identifier on the electronic device, such as in Figure 6R As shown (e.g., configuring a second cellular identifier to perform one or more functions on an electronic device). In some embodiments, activating a second cellular identifier configures the second cellular identifier to perform the functions of the primary cellular identifier (e.g., the second cellular identifier is used for voice, messaging, and data operations by default). In some embodiments, activating a second cellular identifier configures the second cellular identifier to perform secondary cellular functions (e.g., the second cellular identifier is used for voice, messaging, and data operations when the primary cellular identifier is unavailable). In some embodiments, activating a second cellular identifier configures the second cellular identifier to perform the functions it was previously configured to perform when it was most recently activated on the electronic device.

[0246] The above-described method of presenting indications for available but inactive cellular identifiers allows electronic devices to provide users with the ability to change which cellular identifiers are active on the device. This simplifies the interaction between the user and the device and enhances the device's operability (e.g., by saving information associated with inactive cellular identifiers instead of requiring the user to go through the setup process from scratch for inactive cellular identifiers). This, in turn, reduces power consumption and extends the device's battery life by enabling users to use the device more quickly and efficiently.

[0247] In some implementations, input corresponding to a request to set up a first cellular identifier is received during the initial setup process of the electronic device (768) (e.g., when the electronic device is configured for first-time use, the initial setup process guides the user through various device settings and user account logins, including processes for configuring one or more cellular identifiers available for use by the electronic device). References below Figures 6A-6K An example describing the initial setup process in more detail.

[0248] The aforementioned method of presenting a user interface for configuring the cellular identifier during the initial setup process of an electronic device allows the electronic device to provide the user with the ability to set the cellular identifier before the user uses the electronic device. This, in turn, reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0249] In some implementations, the initial setup process for the electronic device is the first setup process (770) for a new electronic device. The initial setup process may optionally occur after the electronic device is first set up or after its memory has been erased. (See above reference) Figures 6A-6K An example of the initial setup process for a new electronic device is described in more detail.

[0250] The aforementioned method of presenting a user interface for configuring the cellular identifier during the initial setup process of an electronic device allows the electronic device to provide the user with the ability to set up the cellular identifier before the user uses the electronic device for the first time. This, in turn, reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0251] In some implementations, a process (772) for setting up a first cellular identifier for the electronic device is initiated in response to the detection of a second cellular identifier at the electronic device (e.g., when the second cellular identifier is introduced into the electronic device). In some implementations, when a SIM card is inserted into a mobile device or an eSIM is activated on the electronic device, the electronic device presents a cellular identifier setup user interface for configuring the second cellular identifier and existing cellular identifiers (e.g., the first cellular identifier). When the electronic device operates using a single cellular identifier, the electronic device is optionally configured to perform all cellular identifier functions (e.g., voice, messaging, data) using that cellular identifier. When the 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. (Refer to 6A-) Figure 6J An example of the process for setting up a cellular identifier is described in more detail.

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

[0253] In some implementations, in response to input detected in the cellular settings user interface of the electronic device (e.g., Figure 6O The process of setting up a first cellular identifier for an electronic device is initiated by contact 603 (selecting an indicator 648). The user optionally selects a cellular settings user interface to set up the first cellular identifier. In some embodiments, the first cellular identifier is set up for the first time from the settings user interface. In some embodiments, the first cellular identifier has already been set up, and the user can navigate to the settings user interface to update one or more settings related to the cellular identifier's settings (e.g., activating or deactivating the first cellular identifier, selecting one or more functions to be performed using the first cellular identifier, changing the tag of the first cellular identifier, etc.).

[0254] 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. This simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by allowing the user to easily set up a first cellular identifier or change one or more settings associated with the first cellular identifier). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

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

[0256] In some implementations, in response to receiving input corresponding to a request to specify a first cellular identifier using a name (e.g., Figure 6J In the process of selecting option 636b)(780) using contact 603, and determining that the name is the primary cellular identifier name, the electronic device is configured (782) to use the first cellular identifier to perform message transmission functions, such as... Figure 6K As indicated by instruction 638a. In some embodiments, the electronic device uses a 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 a primary cellular identifier to send and receive messages using an enhanced messaging service. Based on the determination that the name is not the name of the primary cellular identifier, the electronic device is configured to include relinquishing (784) the use of the first cellular identifier to perform messaging functions, such as... Figure 6K As indicated in instruction 638b, the electronic device optionally does not use a secondary cellular identifier to send and receive messages using messaging services or platforms (such as messaging platforms associated with the electronic device or a user account associated with the electronic device). In some implementations, when the primary cellular identifier is unavailable, the electronic device uses the secondary cellular identifier to send messages to contacts using different messaging services (e.g., SMS).

[0257] The above-described method of using the primary cellular identifier to perform messaging functions allows electronic devices to associate a user account for the messaging service with the primary cellular identifier. This simplifies the interaction between the user and the device and enhances the device's operability (e.g., logging into a user account for the messaging service using the primary cellular identifier). This, in turn, reduces power consumption and extends the device's battery life by enabling users to use the device more quickly and efficiently.

[0258] It should be understood that, Figures 7A-7I The specific order in which the operations described herein are performed is merely exemplary and not intended to indicate that the order is the only possible order in which these operations can be performed. Those skilled in the art will conceive of various ways to reorder the operations described herein. Furthermore, it should be noted that the details of other processes described herein in conjunction with other methods (e.g., methods 900, 1100, 1300, and 1500) are similarly applicable to the above-described combinations. Figures 7A-7I The method 700. For example, the cellular identifier setup described above with reference to method 700 optionally has one or more features of the cellular identifier setup of an electronic device communicating with other electronic devices, cellular identifier indication, operations performed using the cellular identifier, etc., as described herein with reference to other methods (e.g., methods 900, 1100, 1300, and 1500). For the sake of brevity, these details will not be repeated here.

[0259] 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 (e.g., combined with...). Figures 1A to 1B , Figure 3 , Figures 5A to 5H (as described above) or application-specific chips. Furthermore, the above references... Figures 7A-7I The described operation is optionally determined by Figures 1A-1BThe components depicted are used to implement this. For example, display operations 708, 752, and 760, and receiving operations 702, 708, 710, 734, 764, 766, 768, and 778 are optionally implemented by an event classifier 170, an event recognizer 180, and an event handler 190. An event monitor 171 in the event classifier 170 detects a touch on the touchscreen 504, and an event dispatcher module 174 transmits the event information to the application 136-1. The corresponding event recognizer 180 in the application 136-1 compares the event information with a corresponding event definition 186 and determines whether a first touch at a first location on the touchscreen corresponds to a predefined event or sub-event, such as a selection of an object on the user interface. When a corresponding predefined event or sub-event is detected, the event recognizer 180 activates the event handler 190 associated with the detection of that event or sub-event. Event handler 190 optionally utilizes or invokes data updater 176 or object updater 177 to update the application's internal state 192. In some embodiments, event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will readily understand how to... Figures 1A to 1B The components depicted in the diagram are used to perform other processes.

[0260] Wearable device cellular identification settings

[0261] Users interact with electronic devices in a variety of different ways, including viewing information about the electronic device and / or its use. In some implementations, a first electronic device (e.g., a wearable device, such as a smartwatch) can perform operations using a first cellular identifier regardless of its connection to a second electronic device (e.g., a mobile device), and when the first electronic device is connected to the second electronic device, it can perform operations using a second cellular identifier. The implementations described below provide a method for the first electronic device to present instructions for operation using a first cellular identifier and a second cellular identifier based on the connection status with the second electronic device. Enhanced interaction with the device reduces the amount of time required for users to perform operations, thereby reducing the device's power consumption and extending the battery life of battery-powered devices. It should be understood that people use devices. When a person uses a device, that person is optionally referred to as a user of the device.

[0262] Figures 8A-8U Exemplary methods are illustrated for a first electronic device to access a first cellular identifier according to some embodiments of the present disclosure, regardless of the connection between the first electronic device and a second electronic device, and exemplary methods for a first electronic device to access a second cellular identifier when the first electronic device is connected to a second electronic device. The embodiments in these figures are used to illustrate the processes described below, including references to… Figures 9A to 9H The process described.

[0263] Figure 8A An exemplary device 500a with a touchscreen 504 is shown, such as a reference device. Figures 5A-5H The touchscreen 504 optionally displays one or more user interfaces including various content. As shown, the electronic device 500a is a wearable device, such as a smartwatch. Figure 8A In the example shown, touchscreen 504 displays a user interface for associating a cellular identifier with electronic device 500a. This user interface includes a first display 802a selectable to associate a “personal” cellular identifier with electronic device 500a and a second display 802b selectable to associate a “service” cellular identifier with electronic device 500a (e.g., the cellular identifier described in reference method 700). Electronic device 500a will optionally be able to perform functions using the selected cellular identifier, even if the electronic device is not communicating with the second electronic device 500b. In some embodiments, the second electronic device is a smartphone and is a device capable of utilizing multiple cellular identifiers, as described in reference method 700. In some embodiments, device 500a is an accessory to device 500b. Figure 8A As shown, when the user interface is displayed 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 to both the "personal" cellular identifier and the "service" cellular identifier. Figure 8B As shown, a user (e.g., using contact 803) selects a second enablement 802b to enable the first electronic device 500a to perform operations using a "service" cellular identifier, even when 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 can only utilize a single cellular identifier (e.g., a "service" 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 can utilize multiple cellular identifiers (e.g., device 500b is configured to use two cellular identifiers), as will be further described below.

[0264] Figure 8C It shows in Figure 8B After selecting the "Service" cellular identifier for device 500a, the first electronic device 500a displays a user interface used to initiate a telephone call to one of several contacts whose contact information is stored on the first electronic device 500a. For example... Figure 8C As shown, in the first electronic device 500a Figure 8CWhen the user interface is shown, the first electronic device 500a communicates with the second electronic device 500b. The touchscreen 504 displays a first enablement representation 804a selectable to communicate with a first contact (e.g., "Mary Smith") associated with a "business" cellular identifier, a second enablement representation 804b selectable to communicate with a second contact (e.g., "Alex Garcia") associated with a "business" cellular identifier, and a third enablement representation 804c selectable to communicate with a third contact (e.g., "John Brown") associated with a "personal" cellular identifier. While the first electronic device 500a communicates with the second electronic device 500b, all enablement representations 804a-c are optionally selectable to initiate a telephone call to the associated contact regardless of which cellular identifier the contact is associated with.

[0265] Figure 8D A user interface is shown in which a first electronic device 500a presents a method for initiating a telephone call to one of a plurality of contacts whose contact information is stored on the first electronic device 500a. For example... Figure 8D As shown, in the first electronic device 500a Figure 8D When the user interface is shown, the first electronic device 500a is not communicating with the second electronic device 500b. The touchscreen 504 displays a first display 804a selectable to communicate with a first contact (e.g., "Mary Smith") associated with a "business" cellular identifier, and a second display 804b selectable to communicate with a second contact (e.g., "Alex Garcia") associated with a "business" cellular identifier. A third display 804d, previously selectable to communicate with a third contact (e.g., "John Brown") associated with a "personal" cellular identifier, 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 to the first electronic device 500a. Figure 8D As shown, the user (e.g., using contact 803) selects a third power indicator 804d associated with a third contact.

[0266] In some implementations, in response to a user selecting a contact associated with a cellular identifier that is currently unavailable for use by the first electronic device 500a, the first electronic device presents a warning user interface 806a, such as... Figure 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 device 500a can currently only communicate using a "service" cellular identifier). In some embodiments, in response to the user selecting a contact associated with a cellular identifier currently unavailable to the first electronic device 500a, the first electronic device switches to presenting the warning user interface 806b, such as... Figure 8F As shown. Figure 8F The warning user interface 806b includes a message indicating which cellular identifier the selected contact is associated with, and a power indication 808 that allows the selected contact to be called using a different cellular identifier (e.g., using a cellular identifier currently active on device 500a that is different from the cellular identifier associated with the selected contact).

[0267] Figures 8G-8H A settings user interface for a first electronic device 500a is shown. This settings user interface includes a first power indicator 810a selectable to display clock settings, a second power indicator 810b selectable to display cellular settings, and a third power indicator 810c selectable to switch the first electronic device 500a to airplane mode (e.g., a mode that disables the cellular identifier configured on the device 500a). The second power indicator 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 (e.g., using contact 803) selects a second display 810b for presenting the cellular settings of device 500a.

[0268] Figure 8I The first electronic device 500a is shown in response to Figure 8H The cellular settings user interface is presented based on the selection made in the settings. For example... 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 options for changing which cellular identifier the first electronic device 500a has access to when not connected to the second electronic device 500b. The user interface includes a first power indicator 812a selectable to enable the first electronic device 500a to use a first cellular identifier (“personal”), and a second power indicator 812b selectable to enable the first electronic device 500a to use a second cellular identifier (“service”). However, when the first electronic device 500a is not connected to the second electronic device 500b, the first power indicator 812a associated with the first cellular identifier (“personal”) is deactivated, as indicated by a grayed-out appearance.

[0269] Figure 8J The first electronic device 500a is shown presenting a user interface for initiating a telephone call, the user interface including features referenced above. Figure 8D The same content as the user interface described above. When device 500a presents... Figure 8J When the user interface is accessed, device 500a communicates with device 500b. For example... Figure 8J As shown, the user (e.g., using contact 803) selects a first enablement 804a associated with a first contact (“MarySmith”). The first contact is associated with a “business” cellular identifier that is available to the first electronic device 500a even if the first electronic device 500a is not connected to the second electronic device 500b, meaning that the first electronic device 500a will be able to complete the phone call even if it is not connected to the second electronic device 500b.

[0270] In response to the selection of the first enable signal 804a, the first electronic device 500a initiates a telephone call to the first contact (“Mary Smith”) using a “service” cellular identifier. While a telephone call with the first contact is in progress, the first electronic device 500a presents… Figure 8K The telephone user interface shown is illustrated. This 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 call, an indication 818 of the option to end the call, and an indication 820 of the option to add another contact to the call. Figure 8L As shown, the user (e.g., using contact 803) selects a power indicator 820 to add another contact to the phone call.

[0271] In response to this selection, the first electronic device 500a presents a first indicator 822a selectable to add a first contact (“Alex Garcia”) to the phone call, and a second indicator 822b selectable to add a second contact (“John Brown”) to the phone call, as shown below. 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 (e.g., using contact 803) selects a second enablement 822b to add the second contact (which is associated with a "personal" cellular identifier) ​​to the phone call while the call is currently being made using a "business" cellular identifier.

[0272] In response to Figure 8MIn the selection process, the first electronic device 500a presents a user interface for confirming the user's selection, such as... Figure 8N As shown. The user interface includes an indication 824 of the current phone call, which lists the contact being called, the cellular identifier used for the call (“B”), and the duration of the call. The user interface also includes a message 826 that informs the user that the default cellular identifier used for the selected contact is different from the cellular identifier currently used for the call (e.g., the cellular identifier used for the call is “B”, while the default cellular identifier for the desired contact to be added to the call is “P”), and an indication 828 that allows the user to choose to add the selected contact to the ongoing call using the cellular identifier used for the call instead of the cellular identifier associated with the selected contact.

[0273] Figure 8O A first electronic device 500a is shown presenting a home screen user interface (e.g., a wake-up screen user interface, such as a dial user interface displayed by the device when it first exits low power / display off mode). The home screen user interface includes an indication 830 of the current time. When presenting the home screen user interface, the first electronic device 500a detects an upward swipe (e.g., using contact 803) from the bottom edge of the touchscreen 504 toward the center of the touchscreen 504.

[0274] In response to the upward swipe, the first electronic device 500a displays a control user interface, such as... Figure 8P As shown. The control user interface includes a signal strength indicator 832a for a "business" cellular identifier, a signal strength indicator 832b for a "personal" cellular identifier, a location service indicator 834, a cellular settings power indicator 836a, a flight mode power indicator 836b, a phone verification power indicator 836c, a Wi-Fi power indicator 836d, a battery power indicator 836e, and a flashlight power indicator 836f. The first electronic device 500a can perform multiple operations (e.g., navigating to the cellular settings user interface, configuring Wi-Fi, activating flight mode, viewing battery status and settings, generating instructions for the second electronic device 500b, and launching the flashlight application) in response to the user's selection of one of the power indicators presented in the control user interface. Figure 8P As shown, the first electronic device 500a is connected to the second electronic device 500b, and simultaneously presents... Figure 8P The user interface is shown. Cellular setting indicator 836a indicates that the first electronic device 500a communicates with the second electronic device 500b. Optionally, telephone setting indicator 836c can be checked to generate an indication (e.g., a sound or tactile indication) on the second electronic device 500b.

[0275] Figure 8QThe control center user interface is shown when the first electronic device 500a communicates with the second electronic device 500b. Unless otherwise stated herein, Figure 8Q The control center user interface shown is Figure 8P The control center user interface shown is essentially the same. The "Personal" cellular identifier indication 832b indicates that the first electronic device 500a does not have access to the "Personal" cellular identifier, and indication 832b does not include an indication of the signal level of the "Personal" cellular identifier. The cellular settings indication 836a indicates that the first electronic device 500a only has access to the "Service" cellular identifier. The verification phone indication 836c is inactive and has a grayed-out appearance.

[0276] Figure 8R-Figure 8U A user interface for setting and changing the cellular identifier settings 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 a power indicator 840, which allows selection to continue the process of setting up the first electronic device 500a on the second electronic device 500b. Figure 8R The user interface is optionally the user interface of an application on device 500b, which is used to control various aspects of device 500a, including cellular identifier settings, power settings, and time settings. In response to... Figure 8R In the selection process, the second electronic device 500b presents one or more user interfaces for setting up the first electronic device 500a, such as... Figure 8S The user interface shown.

[0277] Figure 8S A second electronic device 500b is shown presenting a user interface for associating a cellular identifier with a first electronic device 500a. This user interface includes a first power indicator 842a selectable to add a first cellular identifier (“personal”) to the first electronic device 500a, a second power indicator 842b selectable to add a second cellular identifier (“service”) to the first electronic device 500b, and a third power indicator 844 selectable to temporarily waive the option to select a cellular identifier for the first electronic device 500a. Figure 8S As shown, the user (e.g., using contact 803) selects a second power indicator 842b to add a “service” cellular identifier to the first electronic device 500a.

[0278] Figure 8TThe user interface for setting up the first electronic device 500a is shown on the second electronic device 500b. (See diagram.) Figure 8T As shown, the user interface includes multiple display options for viewing or changing various settings of the first electronic device 500a on the second electronic device 500b, including a display option 846 for viewing and changing the cellular identifier settings of the first electronic device 500a. The display option 846 includes an indication (e.g., an icon with a "B") of the cellular identifier active on the first electronic device 500a (e.g., a "service" cellular identifier). Figure 8T As shown, the user (e.g., using contact 803) selects an indicator 846 for viewing and changing the cellular identifier settings of the first electronic device 500a.

[0279] In response to Figure 8T In the user selection, the second electronic device 500b presents the cellular settings user interface, such as... Figure 8U As shown. The user interface includes indication 848 for a cellular identifier (e.g., a "service" cellular identifier) ​​activated on the first electronic device 500a, and indication 850 for a cellular identifier (e.g., a "personal" cellular identifier) ​​not currently activated on the first electronic device 500b. Indications 848 and 850 may be used to present more information about the respective cellular identifier, such as the operator associated with the cellular identifier and the cellular usage of the cellular identifier over a predetermined amount of time (e.g., a billing cycle), and the settings of the cellular identifier, such as a power indication for activating a "personal" cellular identifier on the first electronic device 500a.

[0280] Figures 9A-9H This is a flowchart illustrating a method 900 for accessing a first cellular identifier on a first electronic device regardless of the connection between the first electronic device and a second electronic device, and for 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 this disclosure. Method 900 is optionally performed at an electronic device (such as device 100, device 300, device 500), as referenced above. Figures 1A-1B , Figures 2-3 , Figures 4A-4B and Figures 5A-5H The operations in method 900 may be optionally combined, and / or the order of some operations may be optionally changed.

[0281] As described below, method 900 provides a method for accessing a first cellular identifier on a first electronic device regardless of the connection between the first electronic device and a second electronic device, and for accessing a second cellular identifier on the first electronic device when the first electronic device is connected to the second electronic device. This method reduces the cognitive burden on the user when interacting with the device user interface of this 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 charging cycles.

[0282] In some implementations, a first electronic device (e.g., electronic device 500a) communicating with one or more input devices (e.g., a mobile device with a touchscreen, such as a wearable device) receives (902) input associated with a function requiring the use of a corresponding cellular identifier (e.g., a request to compose or send a text message or initiate a telephone call). Figure 8D The first electronic device (904) is associated with a second electronic device (e.g., electronic device 500b) capable of using both a first cellular identifier and a second cellular identifier. The second electronic device is optionally a mobile device (e.g., a tablet, smartphone, media player, or wearable device) or a computer to which the first electronic device is paired and within communication range. For example, when the first electronic device (e.g., a smartwatch) is paired with the second electronic device (e.g., a smartphone), 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 Bluetooth range, within 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 mounted on the first electronic device, and the second cellular identifier is attached to or mounted 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 and second electronic devices.

[0283] In some implementations, in response to receiving an input (908) associated with a function requiring the use of the corresponding cellular identifier, such as Figure 8J In the process of selecting the power indicator 804a using contact 803, the first electronic device executes (910) the function based on the determination that the function requires the use of a first cellular identifier (e.g., a "service" cellular identifier) ​​(e.g., the function to be executed by the first cellular identifier being set to be executed), regardless of whether the first electronic device is communicating with a second electronic device, such as in Figure 8KAs shown in the diagram. In some embodiments, the first electronic device is able to perform functions using the first cellular identifier without using a second electronic device. For example, if a contact stored on the first electronic device is associated with the first cellular identifier, calling that contact requires the use of the first cellular identifier. This functionality is determined based on factors such as (e.g., in response to...) Figure 8D In the case of initiating a telephone call to "John Brown" by selecting the option of the first electronic device (804d), a second cellular identifier (e.g., a "personal" cellular identifier) ​​is required, and the first electronic device communicates with the second electronic device, which performs (912) this function. Figure 8D In the example shown, the first electronic device 500a and the second electronic device 500b do not communicate with each other. Conversely, if the first electronic device 500a and the second electronic device 500b communicate with each other, then in response to the selection of the indication 804d (e.g., using contact 1003), the second electronic device 500a... Figures 8J-8K The example shown initiates communication in this manner. In some embodiments, both the first and second cellular identifiers are available to the first electronic device when it communicates with the second 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 functions only, then making a phone call requires the use of the second cellular identifier. Based on the determination that the function (e.g., initiating a phone call to "John Brown" in response to a selection of indicator 804a) requires the use of the second cellular identifier (e.g., the "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, or outside wireless communication range), such as in... Figure 8D As shown, the first electronic device abandons (914) performing the function, such as in Figure 8E As shown in the diagram. 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 alternatively use the first cellular identifier to perform the function. For example, if a contact stored on the first electronic device is attached to the second cellular identifier and the user attempts to call that contact, the first electronic device presents a message that the contact cannot be called or presents an option to alternatively use the first cellular identifier to call the contact.

[0284] The aforementioned method of using a first cellular identifier to perform functions at a first electronic device regardless of whether the first electronic device is communicating with a second electronic device, and using a second cellular identifier to perform functions when the first electronic device is communicating with the second electronic device, allows the first electronic device to use the second cellular identifier to perform functions while communicating with the second electronic device. This simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by performing operations associated with two cellular identifiers without providing explicit user input to switch between cellular identifiers). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0285] In some implementations, the first electronic device receives (916) input (e.g., selecting enablement display 804d using contact 803) for performing a function associated with the default corresponding cellular identifier (e.g., composing or sending a text message or initiating a telephone call). Optionally, one of the first and second cellular identifiers is configured to perform this 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 a user initiates a telephone call to that specific contact, the first electronic device uses the corresponding cellular identifier to make the call by default.

[0286] In some implementations, in response to receiving input for performing functions associated with the default corresponding cellular identifier (e.g., Figure 8D The first electronic device uses contact 803 to select a power indicator 804d)(918) (e.g., touch input received at the touchscreen of the first electronic device, voice input received at the microphone of the first electronic device, or another input), and determines that the default corresponding cellular identifier is the second cellular identifier (e.g., a "personal" cellular identifier) ​​and the first electronic device communicates with the second electronic device, the first electronic device uses the second cellular identifier to perform (920) the function (e.g., the first electronic device can use the second cellular identifier to perform the function via its connection to the second electronic device). Figure 8D In the example shown, the first electronic device 500a and the second electronic device 500b do not communicate with each other. Conversely, if the first electronic device 500a and the second electronic device 500b communicate with each other, the selection of the power indication 804d will optionally cause the first electronic device 500a to communicate in a manner similar to... Figures 8J-8K The example shown initiates communication in this manner. Based on the determination 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... Figure 8D As shown, the first electronic device provides a (922) warning indicating that the second cellular identifier is not activated on the first electronic device, such as in Figure 8EAs shown in the diagram. In some embodiments, the first electronic device cannot perform the function using the second cellular identifier when it is not 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 indication that it can choose to perform the function using the first cellular identifier.

[0287] The aforementioned method of warning the user when the second cellular identifier is unavailable on the first electronic device allows the first electronic device to communicate to the user why it is not performing a function that would normally be performed using the second cellular identifier. This simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by providing the user with specific error messages, enabling the user to avoid using the particular cellular identifier when they do not intend to use it). It also prevents the electronic device from displaying information about the particular cellular identifier (e.g., allowing a contact to know the phone number associated with a particular cellular identifier that is not associated with that contact), and prevents the electronic device from using the cellular identifier when the user does not intend to use it, which in some cases results in usage fees from the cellular identifier's service provider.

[0288] In some implementations, providing a warning indicating that the second cellular identifier is not activated on the first electronic device includes providing an option to use the first cellular identifier to perform functions associated with the second cellular identifier (e.g., Figure 8F Button 808)(924). The first electronic device optionally presents a message indicating that the second cellular identifier is unavailable and alternatively, an option to utilize the first cellular identifier to perform the function. In some cases, for privacy reasons, the user may not want to utilize the first cellular identifier to perform the function (e.g., the user does not want a specific 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).

[0289] The aforementioned method of providing the user with the option to perform functions using the first cellular identifier when the second cellular identifier is unavailable allows the first electronic device to provide the user with a way to perform functions associated with the second cellular identifier even when the second cellular identifier is unavailable. This simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by presenting the option to perform the function using the first cellular identifier within the user interface for performing the function, rather than requiring the user to change cellular identifier settings to configure the first cellular identifier to perform the function). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0290] In some implementations, a first cellular identifier is specified for use by the first electronic device according to a settings user interface displayed on the second electronic device for the first electronic device, such as in Figure 8U As shown, a first electronic device is enabled to use a first cellular identifier independently of a second electronic device, and the first electronic device is prevented from using a second cellular identifier independently of the second electronic device (926). Optionally, a user can 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 for use by the first electronic device independently of the second electronic device, the first electronic device is automatically configured not to use the second cellular identifier independently of the second electronic device. The second cellular identifier is specified for use by the first electronic device according to a settings user interface for the first electronic device displayed on the second electronic device, such as in... Figure 8U As shown, the first electronic device is enabled to use the second cellular identifier independently of the second electronic device, and the first electronic device is prevented from using the first cellular identifier independently of the second electronic device (928). In some embodiments, when the second cellular identifier is designated for use by the first electronic device independently of the second electronic device, the first electronic device is automatically configured not to use the first cellular identifier independently of the second electronic device.

[0291] The aforementioned method of providing instructions on which cellular identifier to activate on the first electronic device within the user interface of the second electronic device allows the user to configure the first electronic device from the second electronic device. This 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). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0292] In some implementations, the first electronic device receives (930) input (e.g., selection via a touchscreen, voice input, etc.) corresponding to a request to view the cellular settings user interface of the first electronic device via one or more input devices. Figure 8H (Selection of option 810b via contact 803). 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.).

[0293] In some implementations, in response to receiving input corresponding to a request to view the cellular settings user interface, the first electronic device displays (932) the cellular settings user interface, such as in Figure 8IAs shown, the cellular setup user interface includes: an indication indicating that the first cellular identifier is active on the first electronic device (e.g., an indication 812a for a "personal" cellular identifier is presented as an active appearance with an indication 812b for a "business" cellular identifier) ​​and an indication indicating that the second cellular identifier is active on the first electronic device (e.g., indication 812b) (934), based on the determination that the first electronic device is communicating with the second electronic device (e.g., indication 812b). 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. Conversely, if the first electronic device 500a and the second electronic device 500b are communicating with each other, the indication 812a of the "personal" cellular identifier will have the same ungrayed appearance as the indication 812b of the "business" cellular identifier. In some embodiments, the indications indicating that the first cellular identifier is active on the first electronic device and the indications indicating that the second cellular identifier is active on the first electronic device optionally include text or images indicating the activation status of the respective cellular identifier, and optionally include an indication of the signal strength of the respective cellular identifier. Based on the determination that the first electronic device is not communicating with the second electronic device, such as... Figure 8I As shown (e.g., the second electronic device is powered off, in airplane mode, or is more than the range of the communication channel between the first and second electronic devices), the cellular settings user interface includes an indication (812b) indicating that the first cellular identifier is active on the first electronic device (e.g., text or an image indicating the active 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 settings user interface optionally includes an indication (812a)(936) indicating that the second cellular identifier is not active on the first electronic device (e.g., text or an image indicating the inactive state of the second cellular identifier), such as... 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, a user pays for access to one cellular identifier on the first electronic device 500a, and the user can change which cellular identifier is associated with the first electronic device 500a while 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, a user pays for access to both cellular identifiers on the first electronic device 500a, and the user can 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.

[0294] The aforementioned method of indicating the active or inactive status of the first and second cellular identifiers in the cellular settings user interface allows the first electronic device to communicate to the user which cellular identifiers are available to perform functions on the first electronic device. This simplifies the interaction between the user and the device and enhances the operability of the device (for example, presenting the active or inactive status of the cellular identifiers in the settings user interface allows the user to know the status of the cellular identifiers before making changes to the settings). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0295] In some embodiments, while the first electronic device is displaying a representation of the corresponding cellular identifier, an input (938) associated with a function requiring the use of the corresponding cellular identifier is received (e.g., an optional display for performing the function includes a representation of the corresponding cellular identifier or a representation displayed as adjacent to the corresponding cellular identifier, such as an indication of the corresponding cellular identifier similar to the indication described above with reference to method 700). Figure 8D The "P" indication of the "personal" cellular identifier included in instruction 804d, based on the determination that the corresponding cellular identifier can be used to perform this function on the first electronic device, such as in Figure 8C As shown, the representation of the corresponding cellular identifier (e.g., included in Figure 8C The "P" indication of the "personal" cellular identifier in indicator 804c is displayed with a first visual feature (e.g., text, icons, color scheme, etc. indicating the availability of the corresponding cellular identifier) ​​(940). For example, the representation of the corresponding cellular identifier may optionally be displayed in color. Based on the determination that the corresponding cellular identifier cannot be used to perform this function on the first electronic device, such as in... Figure 8D As shown, the representation of the corresponding cellular identifier (e.g., indication 804d) is displayed with a second visual feature different from the first visual feature (e.g., text, icons, color schemes, etc. indicating that the corresponding cellular identifier is not available) (942). For example, the representation of the corresponding cellular identifier is optionally displayed in gray.

[0296] The aforementioned method of altering the visual characteristics of the corresponding cellular identifier when the first electronic device receives input for performing functions using the corresponding cellular identifier allows the first electronic device to convey to the user whether the corresponding cellular identifier is available in the user interface for performing functions using the corresponding cellular identifier. This simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by presenting an indication of the status of the corresponding cellular identifier when the user may wish to use the corresponding cellular identifier). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0297] 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 (such as telephone calls or text messages) with the contacts, or a contacts user interface including representations of the contacts on the first electronic device), such as Figure 8D The user interface shown.

[0298] In some implementations, in response to receiving a request to display the user interface, the first electronic device displays (946) the user interface, such as... Figure 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, a messaging user interface includes a representation of a messaging conversation with the first contact. Based on the determination that the first representation (e.g., 804a or 804b) associated with the first contact is associated with a cellular identifier (e.g., a "business" cellular identifier) ​​activated on the first electronic device, 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 visual features (e.g., 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 the determination that the first representation (e.g., 804d) associated with the first contact is associated with a cellular identifier (e.g., a "personal" cellular identifier) ​​not activated on the first electronic device, the first representation is displayed with a second visual feature different from the first visual feature (950). In some implementations, a first representation associated with the first contact is displayed to indicate visual features (e.g., colors, patterns, text, or images) that are not activated on the first electronic device by the cellular identifier associated with the first contact. For example, the representation associated with the first contact may be displayed in gray.

[0299] The aforementioned method of changing the appearance of a contact's representation based on the activation or deactivation status of the cellular identifier associated with the contact allows the first electronic device to communicate with the user whether it is capable of using the cellular identifier associated with the contact to perform communication operations with the contact. This simplifies the interaction between the user and the device and enhances the device's operability (e.g., by presenting the status of the cellular identifier in the user interface for using the cellular identifier to communicate with the contact, rather than requiring the user to find out the status of the cellular identifier in some other way). This, in turn, reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0300] In some implementations, the user interface also includes a second representation (804d) (952) associated with a second contact (e.g., a representation of a message or call sent to or received from a first contact). For example, the messaging user interface includes a representation of a messaging conversation with a first contact. A 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 with a first visual feature (954) (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. A second representation (804d) associated with the second contact is associated with a cellular identifier (e.g., "personal") not activated on the first electronic device, and the second representation (804d) is displayed with a second visual feature (956) (e.g., a color, shape, image, or text indicating the inactive state of the cellular identifier not activated on the first electronic device). For example, the second representation associated with the second contact is displayed in gray.

[0301] The aforementioned method of changing the appearance of a contact's representation based on the activation or deactivation status of the cellular identifier associated with the contact allows the first electronic device to communicate with the user whether it is capable of using the cellular identifier associated with the contact to perform communication operations with the contact. This simplifies the interaction between the user and the device and enhances the device's operability (e.g., by presenting the status of the cellular identifier in the user interface for using the cellular identifier to communicate with the contact, rather than requiring the user to find out the status of the cellular identifier in some other way). This, in turn, reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0302] In some implementations, during the setup process of the first electronic device, the first electronic device receives (958) input via one or more input devices for activating a corresponding cellular identifier in a first cellular identifier and a second cellular identifier activated on the second electronic device (e.g., Figure 8B (Contact 803 in the middle). 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.

[0303] In some implementations, in response to receiving input for activating a corresponding cellular identifier on the first electronic device (e.g., detecting...), Figure 8BIn contact 803)(960), based on determining that the corresponding cellular identifier is the first cellular identifier (962), the first electronic device enables (964) the first electronic device to use the first cellular identifier (e.g., a "service" cellular identifier) ​​independently of the second electronic device, such as in Figures 8J-8K As shown. 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 prevent the first electronic device from using the second cellular identifier (e.g., a "personal" cellular identifier) ​​independently of the second electronic device, such as Figures 8D-8F As shown. When the first electronic device and the second electronic device are communicating with each other, the first electronic device may optionally be able to use 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 may not be able to use 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 may optionally enable (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 able to use 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 may not be able to use the first cellular identifier. Although in reference Figures 8A-8U In the example shown, the first electronic device 500a can use a "service" cellular identifier independently of its connection to the second electronic device 500b. However, in some implementations, instead of selecting a "service" cellular identifier, a "personal" cellular identifier is selected for the first electronic device 500a to use, regardless of its connection to the second electronic device 500b.

[0304] The aforementioned method of presenting a user interface on the second electronic device for selecting a cellular identifier to activate on the first electronic device allows the first electronic device to be configured from the second electronic device. This 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). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0305] In some implementations, during communication with a first contact using a first corresponding cellular identifier (e.g., during a telephone call with a first contact using a first corresponding cellular identifier), a first electronic device receives (974) a request to add a second contact to the communication via one or more input devices (e.g., Figure 8L The user selects the "Add" option 820 using contact 803 (e.g., a request to add a second contact to the phone call). In some implementations, 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. Another example is when the user adds a second contact to a messaging conversation with the first contact.

[0306] In some implementations, 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 a first corresponding cellular identifier (e.g., the first corresponding cellular identifier is the default cellular identifier of 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). Although in 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 selects option 822a to add “Alex Garcia” to the call, in response to that selection, the first electronic device 500a optionally initiates a phone call to “Alex Garcia” to add that contact to the phone call with “Mary Smith”, without presenting… Figure 8N The warning shown is because both "Alex Garcia" and "Mary Smith" are associated with a "business" cellular identifier. Based on the determination that the second contact is associated with a second corresponding cellular identifier different from the first corresponding cellular identifier (e.g., the second corresponding cellular identifier is the default cellular identifier of the first electronic device, the default cellular identifier for voice and messaging functions, or the default cellular identifier for the second contact) (980), such as in Figure 8NAs shown, 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 images, presenting sound or haptic feedback, etc. to indicate that although the second cellular identifier is the default cellular identifier for communication with the second contact, the first cellular identifier will be used for the communication), such as in Figure 8N As shown in the diagram. In some cases, for privacy reasons, such as not wanting a second contact to know the phone number associated with the first cellular identifier, a user will not want to use the first cellular identifier to communicate with a second contact.

[0307] The aforementioned method of warning the user when a user requests to add a contact to a communication being performed using a cellular identifier not associated with that contact allows the first electronic device to inform the user how the first electronic device performs communication functions with each contact. This simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by providing the user with a specific warning message, enabling the user to avoid using a specific cellular identifier to call a contact not associated with that specific cellular identifier). It also prevents the electronic device from displaying information about a specific cellular identifier (e.g., allowing a contact to know the phone number associated with a specific cellular identifier that is not associated with that contact), and prevents the electronic device from using a specific cellular identifier when the user does not intend to use that cellular identifier, which in some cases results in usage fees from the cellular identifier's service provider.

[0308] It should be understood that, Figures 9A-9H The specific order in which the operations described herein are performed is merely exemplary and not intended to indicate that the order is the only possible order in which these operations can be performed. Those skilled in the art will conceive of various ways to reorder the operations described herein. Furthermore, it should be noted that the details of other processes described herein in conjunction with other methods (e.g., methods 700, 1100, 1300, and 1500) are similarly applicable to the above-described combinations. Figures 9A-9H The method 900. For example, the way the first electronic device and the cellular identifier associated with the second electronic device interact as described in the above-described method 900 optionally has one or more features of the cellular identifier setting user interface, cellular identifier instructions, operations performed using the cellular identifier, etc., as described in other methods described herein (e.g., methods 700, 1100, 1300, and 1500). For the sake of brevity, these details will not be repeated here.

[0309] 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 (e.g., combined with...). Figures 1A to 1B , Figure 3 , Figures 5A to 5H (as described above) or application-specific chips. Furthermore, the above references... Figures 9A-9H The described operation is optionally determined by Figures 1A-1B The components depicted are used to implement this. For example, display operations 932 and 946 and receiving operations 902, 916, 930, 944, 958, and 974 are optionally implemented by an event classifier 170, an event recognizer 180, and an event handler 190. An event monitor 171 in the event classifier 170 detects a touch on the touchscreen 504, and an event dispatcher module 174 transmits the event information to the application 136-1. The corresponding event recognizer 180 of the application 136-1 compares the event information with a corresponding event definition 186 and determines whether a first touch at a first location on the touchscreen corresponds to a predefined event or sub-event, such as a selection of an object on the user interface. When a corresponding predefined event or sub-event is detected, the event recognizer 180 activates the event handler 190 associated with the detection of that event or sub-event. The event handler 190 optionally utilizes or invokes a data updater 176 or an object updater 177 to update the application's internal state 192. In some implementations, event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will readily understand how this can be done based on... Figures 1A to 1B The components depicted in the diagram are used to perform other processes.

[0310] Present visual indicators of the cellular identifier in the communication-related user interface.

[0311] Users interact with electronic devices in many different ways, including communicating with other electronic devices using a network connection. In some implementations, the electronic device displays an indication of which cellular identifier has been used or will be used to perform a communication function. The implementations described below provide a method for an electronic device to present a visual indication of a cellular identifier in a communication-related user interface. Enhanced interaction with the device reduces the amount of time required for users to perform operations, thereby reducing the device's power consumption and extending the battery life of battery-powered devices. It should be understood that people use devices. When a person uses a device, that person is optionally referred to as a user of the device.

[0312] Figure 10A-Figure 10MM Exemplary methods are shown for an electronic device according to some embodiments of the present disclosure to present visual indications of a cellular identifier associated with communication functions. The embodiments in these figures are used to illustrate the processes described below, including references to... Figures 11A-11Q The process described.

[0313] Figure 10A An exemplary device 500 with a touchscreen 504 is shown, such as a reference device. Figures 5A-5H The touchscreen 504 optionally displays one or more user interfaces including various content. Figure 10A In the example shown, touchscreen 504 displays a user interface for configuring electronic device 500 to present a voicemail associated with a cellular identifier available for use by device 500. Figure 10A As shown in Figure 1002, when the electronic device 500 presents a user interface for configuring the electronic device to present a voicemail, the "personal" cellular identifier, indicated by the indicator with "P", is configured as the default number for telephone and SMS, the "business" cellular identifier, indicated by the indicator with "B", is configured as a secondary number for telephone and SMS, and the "travel" cellular identifier, indicated by the indicator with "T", is not activated.

[0314] Figure 10A The user interface shown includes a first indication 1004a selectable to initiate a process of setting up a voicemail associated with a first cellular identifier (e.g., a "personal" cellular identifier represented by an indicator with "P"), and a second indication 1004b selectable to initiate a process of setting up a voicemail associated with a second cellular identifier (e.g., a "service" cellular identifier represented by an indicator with "B"). Figure 10A As shown, a user (e.g., using contact 1003) selects a second enablement display 1004 to initiate the process of setting up a voicemail associated with a second cellular identifier.

[0315] Figure 10B A voicemail user interface is shown after a voicemail has been set up with a second cellular identifier (e.g., a "service" cellular identifier). This voicemail user interface includes multiple enablement displays 1006a-1006c associated with voicemail received by the electronic device using the "service" cellular identifier, and an enablement display 1004a that can be selected to additionally set up a voicemail for another cellular identifier (e.g., a "personal" cellular identifier) ​​activated on the electronic device 500. The enablement displays 1006a-1006c associated with voicemail received by the electronic device using the "service" cellular identifier include a visual indication of the "service" cellular identifier (e.g., an icon with a "B"), enabling the user to recognize that these voicemails are received using the "service" cellular identifier. Each enablement display 1006a-1006c can be selected to play the corresponding voicemail indicated by the corresponding enablement display. Figure 10BAs shown, the user (e.g., using contact 1003) selects a power indicator 1004a for setting up a voicemail associated with a “personal” cellular identifier.

[0316] Figure 10C A voicemail user interface is shown after voicemail has been set up with a first cellular identifier (e.g., a "personal" cellular identifier) ​​and a second cellular identifier (e.g., a "business" cellular identifier). This voicemail user interface includes multiple indications 1006a-1006c associated with voicemail received by the electronic device using the "business" cellular identifier, and an indication 1008 associated with voicemail received by the electronic device using the "personal" cellular identifier. The indications 1006a-1006c associated with voicemail 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"), enabling the user to recognize that these voicemails are received using the "business" cellular identifier. Similarly, in Figure 10C In the example shown, the enablement indicator 1008 associated with a voicemail received by an electronic device using a "personal" cellular identifier includes an indication of the "personal" cellular identifier (e.g., an icon with a "P"), which allows the user to recognize that the voicemail was received using a "personal" cellular identifier. However, in some implementations, 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 the default number for telephone and SMS, and the user is expected to understand that, by default, the voicemail is associated with the default number for telephone and SMS (e.g., the "personal" cellular identifier) ​​unless indicated as being associated with a "business" cellular identifier. Each enablement indicator 1006a-1006c and 1008 can be selected to play the corresponding voicemail indicated by the corresponding enablement indicator.

[0317] Figure 10D A recent call user interface on a device 500 according to some embodiments of this disclosure is shown. For example... Figure 10D As shown, the recent calls user interface includes multiple display indicators 1010a-b associated with recent calls made or received using a "service" cellular identifier, a display indicator 1012 associated with recent calls made using a "personal" cellular identifier, and a display indicator 1014 associated with recent video conferencing calls already made using a "personal" cellular identifier. Display indicators 1010a and 1010b associated with recent calls made or received using a "service" cellular identifier include an indication of the "service" cellular identifier (e.g., an icon with the letter "B"). Figure 10DIn the example shown, the capability indication 1012 associated with a recent call made or received using a “personal” cellular identifier and the capability indication 1014 associated with a recent video conferencing 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 telephone and SMS. In some embodiments, the cellular identifier used as the default number for telephone and SMS is the cellular identifier used by default for these operations and the default cellular identifier used for video conferencing. Electronic device 500 optionally does not present the indication of the default cellular identifier for telephone and SMS together with the indication of communications performed using the default cellular identifier, because it is expected that the user understands that the default cellular identifier is used for telephone and SMS, unless otherwise stated.

[0318] Figure 10E A recent call user interface according to some embodiments of this disclosure is shown. Figure 10E The user interface shown is basically similar to Figure 10D The user interface shown differs in that the indicator 1016 associated with telephone calls made or received using a "personal" cellular identifier includes an indication of the "personal" cellular identifier (e.g., an icon with the letter "P"). Figure 10E As shown, the capability indication 1014 associated with a recent video conferencing call made or received using a "personal" cellular identifier does not include an indication of the "personal" cellular identifier. In some embodiments, the cellular identifier that is the default number used for telephone and SMS is always used for video conferencing calls, therefore, there is no indication of that cellular identifier in the capability indication 1014 associated with the video conferencing call, as it is expected that the user will know which cellular identifier is used for the video conferencing call. In some embodiments, an indication of the cellular identifier (e.g., an icon with a "P") is included in the capability indication 1014 associated with the video conferencing call. Figure 10E As shown, a user (e.g., using contact 1003) selects an indication 1010b associated with a telephone call made or received using a "service" cellular identifier. In response to this selection, electronic device 500 initiates a telephone call to the contact involved in the call (e.g., "Alex Garcia"), as... Figure 10F As shown.

[0319] Figure 10F A telephone call user interface on a device 500 according to some embodiments of the present disclosure is shown. This telephone call user interface is presented when the electronic device 500 is used for telephone calls. Figure 10FAs shown in Figure 1002, during the phone call, the "service" cellular identifier is used for the call, and the "personal" cellular identifier is disabled because, in some embodiments, while one cellular identifier is used for the phone call, another cellular identifier activated on the electronic device is temporarily disabled until the 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.).

[0320] The telephone call user interface includes an indication 1018 of the contact participating in the telephone call, an indication 1020 of the cellular identifier used for the telephone call, and a capability indication 1022 for initiating a video conference call with the contact on the telephone call. In some embodiments, if the user selects to initiate a video conference call, the electronic device 500 initiates the video conference call using a cellular identifier configured for default numbers used for telephone and SMS (e.g., a "personal" cellular identifier), regardless of which cellular identifier is being used for the telephone call and / or regardless of which cellular identifier is associated with the contact participating in the video conference call. Figure 10F As shown, the user (e.g., using contact 1003) selects the enablement 1022 for initiating a video conference call with the contact.

[0321] Figure 10G A video conferencing call user interface according to some embodiments of the present disclosure is shown. This video conferencing call user interface is presented when the electronic device 500 is used for a video conferencing call. For example... Figure 10G As shown in Figure 1002, during a video conference call, a "personal" cellular identifier is used for the call, while a "business" cellular identifier is disabled. This is because, in some implementations, while one cellular identifier is used for the video conference call, another cellular identifier activated on the electronic device is disabled. In some implementations, cellular identifiers not used for the video conference call remain enabled on the electronic device to perform other operations (e.g., sending or receiving messages, downloading or uploading cellular data, receiving telephone calls, etc.).

[0322] Although the phone call was like Figure 10F The example shown uses a "service" cellular identifier, but... Figure 10G In the example shown, the "personal" cellular identifier is used for video conferencing calls. In some implementations, the cellular identifier used as the default number for phone calls and SMS is always used by the electronic device for video conferencing calls, regardless of which cellular identifier is associated with the contact the electronic device is video conferencing with. In some implementations, the electronic device is capable of using any active cellular identifier for video conferencing calls.

[0323] Figures 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 contact's name ("Mary Smith"), a first phone number 1028a of the contact, a first indication 1030a of the cellular identifier associated with the contact, a second phone number 1028b of the contact, a second indication 1030b of the cellular identifier associated with the contact, and a display 1032 for editing information associated with the contact. Because a "service" cellular identifier is associated with the contact, including two phone numbers associated with the contact, the indications 1028a-b of the two phone numbers each include the indications 1030a-b of the "service" 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 communication with the contact. Figure 10I As shown, the user (e.g., using contact 1003) selects an indicator 1032 for editing information associated with the contact.

[0324] In response to Figure 10I In the user selection, the electronic device 500 presents a user interface for editing information associated with the contact (“MarySmith”), such as... Figure 10J As shown. In addition to other settings for that contact, the user interface includes an instruction 1034 for contacts whose information can be edited and a display 1036 that allows selection of which cellular identifier is associated with that contact. The display 1036 for changing the cellular identifier associated with that contact includes a visual indication 1038 of the cellular identifier currently set as the default cellular identifier for that contact (e.g., a "business" cellular identifier). Figure 10J As shown, the user (e.g., using contact 1003) selects the cellular identifier display 1036 to change the default cellular identifier set for that contact. In response to... Figure 10J In the user selection process, electronic device 500 presents a user interface for changing the cellular identifier associated with that contact, as will be referenced below. Figure 10K To describe in more detail.

[0325] Figure 10KA user interface for changing the cellular identifier associated with a contact, according to some embodiments of the present disclosure, is shown. The user interface includes an indication 1040 of a contact whose information is being edited, a capability indication 1042a selectable to use the most recently used cellular identifier when initiating communication with the contact, a capability indication 1042b selectable to set a first cellular identifier (e.g., a "personal" cellular identifier) ​​as the default cellular identifier for the contact, and a capability indication 1042c selectable to set a second cellular identifier (e.g., a "business" cellular identifier) ​​as the default cellular identifier for the contact. The second capability indication 1042b includes a visual indication 1044a of the first cellular identifier, and the third capability indication 1042c includes a visual indication 1044b of the second cellular identifier. Figure 10K As shown, the third enablement indicator 1042c includes a checkmark indicating that the electronic device 500 is currently configured to use a second cellular identifier (e.g., a "service" cellular identifier) ​​by default to initiate communication with the contact. That is, except in certain circumstances, such as when a user requests the use of a different cellular identifier, when the type of communication is associated with a different cellular identifier (e.g., the electronic device always uses a "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.), the electronic device 500 will use the "service" cellular identifier to communicate with the contact. If the user selects the "recently used" enablement indicator 1042a, the electronic device 500 will optionally use the cellular identifier that the electronic device 500 most recently used for communication with that contact to initiate communication with the contact. Figure 10K As shown, the user (e.g., using contact 1003) selects a second enablement 1042b to set the "personal" cellular identifier to the cellular identifier associated with that contact. Changing the settings in this way causes the electronic device 500 to use the "personal" cellular identifier by default to initiate communication with that contact, unless the user enters input to use a different cellular identifier when initiating communication.

[0326] like Figure 10L As shown, in response to the user's selection, the electronic device 500 presents a check mark in the second display 1042b to indicate that the electronic device 500 is configured to use a first cellular identifier (e.g., a "personal" cellular identifier) ​​to initiate communication with the contact. Figure 10M The contact user interface is shown after the electronic device 500 has been configured to use a “personal” cellular identifier when initiating communication with a contact. Figure 10M The contact user interface shown is basically similar to Figure 10IThe contact user interface shown differs as noted herein. The indication 1030a-b of the cellular identifier associated with the contact is updated to reflect that the cellular identifier associated with the contact is a "personal" cellular identifier.

[0327] Figure 10N The recent call user interface of device 500 according to some embodiments of this disclosure is shown. Figure 10N The user interface shown is basically similar to Figures 10D-10E The user interface shown. (As shown) Figure 10N As shown, a user (e.g., using contact 1003) selects an energy indication 1010b associated with a contact (e.g., “Alex Garcia”). Contact 1003 has an intensity 1046a exceeding a predetermined intensity threshold 1048a, and is detected for a time 1046b exceeding a predetermined time threshold 1048b. In response to contact 1003 having these characteristics, electronic device 500 presents... Figure 10O The user interface shown. In contrast, as combined with the above... Figures 10E-10F As described, in response to a contact that does not have the characteristics of intensity 1046a and / or time 1056b, the electronic device initiates a telephone call to a contact associated with the selected power indicator. Figure 10O As shown, the electronic device 500 presents an instruction 1050 for a contact to be called, an instruction 1052 for the contact's default cellular identifier (e.g., a "business" cellular identifier), a first indication 1054a for calling the contact using a first cellular identifier (e.g., a "personal" cellular identifier), and a second indication 1054b for calling the contact using a second cellular identifier (e.g., a "business" cellular identifier). Figure 10O As shown, a user (e.g., using contact 1003) selects a first power indicator 1054a to call the contact using a “personal” cellular identifier that is not associated with the contact.

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

[0329] Figures 10Q-10S A dial pad user interface according to some embodiments of the present disclosure is shown. The dial pad user interface includes a power indicator 1054 selectable to switch the cellular identifier to be used for making calls, a text input field 1056, a dial pad 1058, and a power indicator 1060 for making calls. The power indicator 1054 for switching the cellular identifier to be used for making calls includes an indication 1062 of the cellular identifier (e.g., a "personal" cellular identifier) ​​to be used when the user selects the power indicator 1060 for making calls. In some embodiments, when a 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 as the default number for calls and SMS. For example, if the user enters a phone number of a contact associated with a "business" cellular identifier, in response to the entry of that phone number and the absence of any other user input for making the call using the "business" cellular identifier, the power indicator 1054 will be updated to include an indication of the "business" cellular identifier. Figure 10Q As shown, a phone number is entered into text input field 1056. In some implementations, the user can enter the phone number using the dial pad 1058 or paste the phone number into text input field 1056 using user input. Figure 10R As shown, the user (e.g., using contact 1003) selects the power indicator 1054 for switching the cellular identifier to be used to make the call. In response to this user input, the user interface appears as follows: Figure 10S The update shown is to display an indication 1062 of the different cellular identifiers (e.g., "Business" cellular identifiers) to be used to make the call when the user selects the "Call" capability indication 1060.

[0330] Figure 10T Another dial pad user interface according to some embodiments of this disclosure is shown. Figure 10T The dial pad user interface shown is basically similar to Figures 10Q-10SThe user interface shown differs in that it does not include the same power indicator used to switch which cellular identifier will be used to make the call. After, for example, a phone number is entered into the text input field 1056 using the dial pad 1058, the user (e.g., using contact 1003) selects the "call" power indicator 1060. Contact 1003 selecting the "call" power indicator has an intensity 1046a exceeding a predetermined intensity threshold 1048a, and is detected at a time 1046b exceeding a predetermined time threshold 1048b. In response to this selection made by contact 1003 using one or more of these characteristics, electronic device 500 presents... Figure 10U The user interface shown. Conversely, if the electronic device 500 detects a contact without the characteristics of intensity 1046a and / or time 1056b at the "Call" indication 1060 (e.g., the electronic device detects a tap), the electronic device 500 uses the default number for telephone and SMS (e.g., "personal" cellular identifier) ​​to make the call without presenting the user interface shown. Figure 10U The user interface shown.

[0331] like Figure 10U As shown, in response to utilizing having Figure 10T Contact 1003, based on the time and / or intensity characteristics of the contact, selects a “call” indication 1060. Electronic device 500 presents multiple indications 1064a-d for various methods of calling the phone number. A first indication 1064a can be selected to make the call using a first cellular identifier (e.g., a “primary” cellular identifier), a second indication 1064b can be selected to make the call using a second cellular identifier (e.g., a “service” cellular identifier), a third indication 1064c can be selected to make the call using cellular data (e.g., “data-based audio”), and a fourth indication 1064d can be selected to make the call as a video conferencing call using cellular data (e.g., “data-based video”). In some embodiments, the call made via cellular data and video conferencing uses a cellular identifier (such as a “personal” cellular identifier) ​​for a default number used for telephones and SMS, as shown in Figure 1002. Alternatively, in some implementations, when the cellular identifier is set as a "data" cellular identifier, the data cellular identifier is used for data-based calls and video conferencing calls.

[0332] Figure 10V-Figure 10X A message transmission user interface according to some embodiments of this disclosure is shown. In some embodiments, Figure 10V-Figure 10XThe user interface shown is presented when a user creates a new thread for a phone number or a set of phone numbers for which the electronic device 500 does not have a corresponding existing messaging thread. The messaging user interface includes a text input field 1066 for entering the phone number to which a message is to be sent, a power indicator 1068 selectable to switch the cellular identifier used to send the message, and a dial pad 1070. The power indicator 1068 for switching the cellular identifier to be used to send the message includes an indication 1072 of the cellular identifier to be used to send the message (e.g., a "personal" cellular identifier). Figure 10V As shown, a phone number is entered into text input field 1066. In some embodiments, the user can enter the phone number using a keyboard 1070 that optionally includes numeric soft keys, or by pasting the phone number into text input field 1066 using user input. In some embodiments, when the phone number entered into text input field 1066 is not associated with a contact associated with a different cellular identifier, electronic device 500 first presents an indication 1042 of the cellular identifier used as the default number for telephone and SMS. For example, if the user enters the phone number of a contact associated with a “business” cellular identifier who does not have an existing messaging thread, then in response to the entry of that phone number and the absence of any other user input for sending the message using the “business” cellular identifier, indication 1068 will be updated to include an indication of the “business” cellular identifier. Figure 10W As shown, the user (e.g., using contact 1003) selects the power indicator 1068 for switching the cellular identifier to be used to send the message. In response to this user input, the user interface appears as follows: Figure 10X The update shown is an indication 1072 to display the different cellular identifiers (e.g., "service" cellular identifiers) to be used to send the message.

[0333] Figure 10Y A message inbox user interface is shown. This message inbox user interface includes multiple indicators 1074a-1074c for messaging conversations on electronic device 500. Each indicator 1074a-1074c includes an indicator of the contacts 1076a-1076c involved in the conversation, and an indicator 1078a-1078c for the cellular identifier used in the messaging conversation. For example... Figure 10Y As shown, the user (e.g., using contact 1003) selects a power indicator 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 message sending user interface shown.

[0334] 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 Figure 1002, a "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, this messaging conversation uses a data-based enhanced messaging service. In some implementations, the cellular identifier that is the default number for phone calls and SMS is always used to send and receive data-based enhanced messages, even for contacts associated with different cellular identifiers.

[0335] Figure 10AA The message inbox user interface is shown; it is basically similar to... Figure 10Y The message inbox user interface shown. Figure 10AA As shown, the user (e.g., using contact 1003) selects a display 1074c associated with a messaging conversation with "Alex Garcia" being conducted using a "service" cellular identifier. In response to this selection, the electronic device presents... Figure 10BB The message sending user interface shown.

[0336] like Figure 10BB As shown, the messaging user interface includes an indication 1082 of the type of message being sent, which is a text message (e.g., not a data-based enhanced message, such as...). Figure 10Z As shown). Figure 10BB As shown in Figure 1002, the "Business" cellular identifier is 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 messaging conversation uses text messages instead of data-based augmented messages. In some implementations, the cellular identifier that is the default number for phone calls and SMS is always used to send and receive data-based augmented messages. When a contact is associated with a cellular identifier that is not the default number for phone calls and SMS, and in the absence of user input to alternatively use the cellular identifier for the default number for phone calls and SMS to send data-based augmented messages, the electronic device 500 uses text messages to send and receive messages to the contact.

[0337] Figure 10CC The main screen user interface of a device 500 according to some embodiments of the present disclosure is shown, such as in Figure 4AAs shown in the image. The main screen includes multiple icons 424-450 that can be selected to launch various applications on the electronic device 500. (As shown...) Figure 10CC As shown, electronic device 500 detects input for presenting a control user interface on device 500 (e.g., a downward swipe of touch 1203 from the upper right edge of touchscreen 504), such as... Figure 10DD - Figure 10GG As shown.

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

[0339] like Figure 10DD As shown, the control user interface also includes a cellular settings display 1084. (As...) Figure 10EE As shown, a user (e.g., using contact 1003) selects a cellular setting indicator 1084. Contact 1003 has an intensity 1046a exceeding a predetermined intensity threshold 1048a, and is detected at a time 1046b exceeding a predetermined intensity threshold 1048b. Alternatively, if electronic device 500 detects no intensity at indicator 1084... Figure 10EE If the contact of intensity 1046a and / or time 1046b is indicated, then if the cellular identifier is active when the input is detected, the electronic device deactivates cellular data on all cellular identifiers in response to the selection. In some embodiments, if the selection is detected while cellular data on all cellular identifiers is deactivated, the electronic device 500 activates cellular data in response to the selection. In response to an input having the aforementioned characteristics, the electronic device presents a list 1086 of cellular identifiers available for use by the electronic device 500. The list 1086 includes a tag for each cellular identifier (e.g., “personal,” “business,” and “travel”), indications 1088a-c for each cellular identifier, and an indication of the status of each cellular identifier. Figure 10FFAs shown, the status of the "Personal" cellular identifier is "Default number for phone and SMS", the status of the "Business" cellular identifier is "Secondary number for phone and SMS", and the status of the "Travel" cellular identifier is "Inactive". The list also includes a power indicator 1090 that can be selected to activate the "Travel" cellular identifier.

[0340] The user (e.g., using contact 1003) selects the power indicator 1090 to activate the "travel" cellular identifier. For example... Figure 10GG As shown in Figure 1002, in response to this 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 implementations, when a cellular identifier is reactivated (e.g., such as a "Travel" cellular identifier), it is automatically configured as the default number for phone calls and SMS. In some implementations, a cellular identifier previously used as a primary number for phone calls and SMS (e.g., a "Personal" cellular identifier) ​​is configured to "Data only." In some implementations, a cellular identifier previously used as a secondary number for phone calls and SMS (e.g., a "Business" cellular identifier) ​​becomes inactive.

[0341] Figure 10HH It shows something that is basically similar to the reference above. Figure 10D , Figure 10E and Figure 10N The recently called user interface. For example... Figure 10HH As shown in Figure 1002, the "business" cellular identifier associated with the contact "Alex Garcia" is not activated on electronic device 500. The user (e.g., using contact 1003) selects the enablement indicator 1010b associated with the most recent call from "Alex Garcia". In some embodiments, in response to this selection, the electronic device presents... Figure 10II The user interface shown includes a warning 1092 regarding the default cellular identifier for the contact not being available on the electronic device, and a "cancel" indicator 1094 that allows navigation back to a previously displayed user interface (e.g., the recent calls user interface). In some embodiments, in response to... Figure 10HH Among the choices, 500 electronic devices are presented as alternatives. Figure 10JJThe user interface shown is described above. The user interface includes a warning 1092 about the default cellular identifier for the contact not being available on the electronic device, a "cancel" indication 1094 that allows navigation back to a previously displayed user interface (e.g., the recent calls user interface), and an indication 1096 that allows the option to make the call using a different cellular identifier (e.g., the "travel" cellular identifier) ​​activated on the electronic device.

[0342] Figure 10KK It shows the relationship with Figure 10H , 10I This contact user interface is substantially similar to the one shown in Figure 10M. It includes an indication 1026 for the contact's name, an indication 1028e for the contact's first phone number, an indication 1028f for the contact's second phone number, a first indication 1030e for the cellular identifier (e.g., "Business") associated with the contact, and a second indication 1030f for the cellular identifier (e.g., "Business") associated with the contact. Because the contact is associated with the "Business" cellular identifier, both of the contact's phone numbers are associated with the "Business" cellular identifier, and each of the two phone number indications 1028e-f includes the "Business" cellular identifier indication 1030e-f. The user interface also includes a capability indicator 1098 selectable to send messages to the contact. Figure 10KK As shown, a user (e.g., using contact 1003) selects a power indicator 1098. In response to this selection, electronic device 500 presents multiple power indicators 1098-2, 1098-4, and 1098-6 selectable to send messages to a contact. The first power indicator 1098-2 can be selected to send an SMS to the contact. The second power indicator 1098-4 can be selected to send a data-based enhanced message (e.g., enhanced instant messaging) to the contact. The third power indicator 1098-6 can be selected to send an email to the contact. Figure 10LL As shown, the user (e.g., using contact 1003) selects a second power indicator to send a data-based enhanced message to the contact.

[0343] Figure 10MM It shows something that is basically similar to Figure 10BB The message sending user interface shown is a message sending user interface, and this user interface is responsive to... Figure 10LL The selection detected in the image is displayed. For example... Figure 10MMAs shown in Figure 1002, 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, the "Plain Data" cellular identifier is being used to send the message because the user entered input to send a data-based enhanced message to "Alex Garcia." The user interface displays previous messages sent and received as text messages, as indicated in Instruction 1082. These text messages are sent and received using the "Business" cellular identifier when it is active, as this is the default cellular identifier for this contact. Figure 10LL The user interface also displays indications 1098-8 that the most recently sent message is a data-based enhanced message (e.g., an enhanced instant message).

[0344] Figures 11A-11Q This is a flowchart illustrating method 1100 for presenting visual indications of a cellular identifier associated with communication functions according to some embodiments of this disclosure. Method 1100 is optionally performed on an electronic device (such as device 100, device 300, device 500), as referenced above. Figures 1A-1B , Figures 2-3 , Figures 4A-4B and Figures 5A-5H The operations in method 1100 may be optionally combined, and / or the order of some operations may be optionally changed.

[0345] As described below, method 1100 provides a method for presenting visual indications of a cellular identifier related to communication functions. This method reduces the cognitive burden on the user when interacting with the device user interface of this 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 charging cycles.

[0346] In some implementations, an electronic device (e.g., electronic device 500) communicating with a display and one or more input devices (e.g., a mobile device including a touchscreen (e.g., a tablet, smartphone, media player, or wearable device) or a computer including one or more of a keyboard, mouse, touchpad, and touchscreen) receives (1102) input via the one or more input devices for displaying a communication user interface, such as... Figure 10DThe user interface shown is used to display representations (1010a, 1010b, 1012, and 1014) of multiple 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 telephone user interface displaying representations of recent calls, etc.). The electronic device is optionally (1104) able to use the main cellular identifier to perform (1106) a first set of functions including these communications, such as... Figure 10D As shown in Figure 1002. In some implementations, the default cellular identifier used for the communication under consideration (e.g., telephone call, text messaging, video call, etc.) is the primary cellular identifier. In some implementations, if a contact involved in the communication is specified to use a different cellular identifier for the communication, then optionally, the different cellular identifier is used by default to perform those communications. The electronic device optionally uses a secondary cellular identifier to perform (1108) a second set of functions different from the first set of functions, such as... Figure 10D As shown in Figure 1002. In some embodiments, the electronic device is configured to utilize a second cellular identifier by default to perform functions other than the communication shown in the communication user interface. For example, the electronic device may optionally use the secondary cellular identifier by default for data uploading and downloading, or perform communication operations in some non-default settings (e.g., communicating with contacts associated with the secondary cellular identifier, performing communication functions when the primary cellular identifier is unavailable).

[0347] In some embodiments, in response to receiving input for displaying a communication user interface, the electronic device displays (1110) a communication user interface on a display, including multiple representations (1010a, 1010b, 1012, and 1014) simultaneously displaying communication items (e.g., communications performed by the device (e.g., previous phone calls, messages, voicemail, etc.)) or representations of users who can communicate with one of these cellular identifiers, including a first representation (1012) (1112) of communication items associated with the primary cellular identifier (e.g., communication items performed using the primary cellular identifier (e.g., previous phone calls, voicemail, or previously received messages)). In some embodiments, initiating a reply communication (e.g., a phone call or message) causes the electronic device to initiate a reply communication using the primary cellular identifier. The communication user interface optionally includes a second representation (1010a) (1114) of communication items associated with a secondary cellular identifier (e.g., communication items performed using the secondary cellular identifier (e.g., previous phone calls, voicemail, or previously received messages)). In some embodiments, initiating a reply communication (e.g., a telephone call or message) causes the electronic device to initiate the 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 this 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 the communication item associated with the secondary cellular identifier (e.g., a communication item performed using the secondary cellular identifier (e.g., a previous telephone call, voicemail, or a previously received message)). In some embodiments, initiating a reply communication (e.g., a telephone call or message) causes the electronic device to initiate the reply communication using the secondary cellular identifier. The third representation (1010b) optionally includes a corresponding visual indication (e.g., an indicator of the secondary cellular identifier, such as a “B” indication indicating 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 different from the visual indication included in the third representation, such as an indicator of the primary cellular identifier.

[0348] The aforementioned method of displaying a representation of communication performed using the secondary cellular identifier with a visual indication distinguishing it from communication 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 a first time period. This simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by presenting an indication of the communication functions performed using the secondary cellular identifier in an intuitive way in the communication user interface). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0349] In some embodiments, the first representation of a communication item associated with the primary cellular identifier includes a visual indication of the primary cellular identifier, which differs from the corresponding visual indications included in the second and third representations (e.g., the primary cellular identifier's indicator) (1118). In some embodiments, the indicator is automatically generated from a user-defined tag used 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 for the primary cellular identifier includes "C," and the indicator for the secondary cellular identifier includes "D," such as in... Figure 10E As shown in the image.

[0350] Including the primary cellular identifier's indication within the representation of communication items associated with the primary cellular identifier allows electronic devices to confirm in the communication user interface that communication items associated with the primary cellular identifier are linked to it. This simplifies user-device interaction and enhances device operability (e.g., by including the primary cellular identifier's indication in the communication user interface, rather than requiring the user to confirm which communications were performed using the primary cellular identifier in a different way). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0351] In some implementations, the first representation of a communication item associated with the primary cellular identifier (e.g., Figure 10D The representation 1012 shown does not include a visual indication (1120) of the primary cellular identifier. The second and third representations optionally include a visual indication of the secondary cellular identifier to distinguish these two representations from the first representation which does not include such a visual indication.

[0352] The aforementioned method of displaying representations of communication items associated with the primary cellular identifier without displaying indications of the primary cellular identifier allows electronic devices to distinguish between communications associated with the secondary cellular identifier and communications associated with the primary cellular identifier with reduced visual clutter. This simplifies user interaction with the device and enhances device operability (e.g., by distinguishing these representations based on whether they include indications of the secondary cellular identifier, allowing users to confirm within the communication user interface which cellular identifier was used for each represented communication). This, in turn, reduces power consumption and extends device battery life by enabling users to use the device more quickly and efficiently.

[0353] In some implementations, the electronic device receives (1122) a user interface corresponding to the display control area via one or more input devices (e.g., Figure 10DD The user interface shown requests input (e.g., detected input). Figure 10CC The control area user interface (contact 1003) includes multiple controls for controlling various functions of the electronic device. In some embodiments, the control area includes optional display options for toggling 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 the operating system (e.g., home screen) or an application associated with a gesture in response to a detected gesture (e.g., a swipe from a specific corner or edge of the electronic device's display). The control area user interface optionally includes a first control 1084 for controlling cellular identifier functions of the electronic device, wherein a third cellular identifier is currently not activated on the electronic device, such as... Figure 10CC As shown in Figure 1002. In some implementations, a third cellular identifier has been previously configured on the electronic device but is not currently activated to perform one or more operations.

[0354] In some implementations, in response to receiving a request to display a user interface in the control area (e.g., a voice command, a gesture (a swipe from a specific edge or corner of the touchscreen of an electronic device) or another input) (e.g., detecting...), Figure 10CC In contact 1003), the electronic device displays (1124) a user interface control area on the display, such as in Figure 10DD As shown in the diagram. When displaying the user interface of the control area, the electronic device optionally receives (1126) input associated with the first control (e.g., input selecting the first control) via one or more input devices (e.g., detecting...). Figure 10FFIn the selection of control 1090 (contact 1003). In some embodiments, selecting the first control causes the electronic device to display multiple settings associated with the cellular identifier function. This input is optionally used to activate a third cellular identifier on the electronic device (e.g., a "travel" cellular identifier) ​​(e.g., configuring the third cellular identifier so that the electronic device can use the third cellular identifier to perform one or more functions), such as in Figure 10FF As shown in the diagram. In response to receiving an input associated with the first control for activating a third cellular identifier on an electronic device, the first electronic device activates (1128) the third cellular identifier on that 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 the diagram. Figure 10GG As shown in Figure 1002.

[0355] The aforementioned method of changing which cellular identifiers are active on an electronic device allows the electronic device to activate a third cellular identifier to perform functions using that third cellular identifier. This simplifies the interaction between the user and the device and enhances the device's operability (e.g., by allowing the user to activate the third cellular identifier without repeating the setup process for the third cellular identifier if it has been previously completed). This, in turn, reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

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

[0357] In some implementations, in response to receiving input (1132) of a corresponding representation 1076b selecting a corresponding communication item, such as in Figure 10Y As shown, based on the determination that the corresponding representation is a first representation of a communication item associated with the primary cellular identifier (e.g., a "personal" cellular identifier), the electronic device initiates (1134) communication with the corresponding contact using the primary cellular identifier, such as... Figure 10ZAs shown in Figure 1002. For communications previously sent or received using the primary cellular identifier, the electronic device may optionally initiate subsequent communications to the same contact using the primary cellular identifier in the same manner (e.g., telephone calls, SMS messages, other messaging services, etc.). For example, if the corresponding representation is a representation of a previously outgoing telephone call completed using the primary cellular identifier, the electronic device initiates a telephone call using the primary cellular identifier in response to the selection of the corresponding representation. This is based on determining that the corresponding representation is a second representation of a communication item associated with a secondary cellular identifier (e.g., a "service" cellular identifier). Figure 10AA The diagram shows (1076c), where the electronic device uses a secondary cellular identifier to initiate (1136) communication with the corresponding contact, such as... Figure 10BB As shown in Figure 1002. For communications previously sent or received using the secondary cellular identifier, the electronic device may optionally initiate subsequent communications to the same contact using the secondary cellular identifier in the same manner (e.g., telephone calls, SMS messages, other messaging services, etc.). For example, if the corresponding representation is a representation of a previously received message, the electronic device uses the secondary cellular identifier to initiate the message in response to the selection of the corresponding representation.

[0358] The above-described method of initiating communication using a cellular identifier associated with a previously executed communication allows electronic devices to consistently use the appropriate cellular identifier for communication associated with a specific cellular identifier. This simplifies the interaction between the user and the device and enhances the operability of the device (e.g., by automatically tracking the associated cellular identifier without user intervention). This, in turn, reduces power consumption and extends the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0359] In some implementations, 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., Figure 10E The contact 1003 selects a representation 1010b (e.g., a representation for selecting a communication item performed using the corresponding cellular identifier or another input for initiating communication using the corresponding cellular identifier).

[0360] In some implementations, in response to receiving an input corresponding to a request to initiate communication with the corresponding contact (e.g., Figure 10E In the process of selecting representation 1010b)(1140) using contact 1003, it is determined that a corresponding cellular identifier (e.g., a "service" cellular identifier) ​​can be used for communication, such as Figure 10EAs shown in Figure 1002 (e.g., the corresponding cellular identifier is active on the electronic device and is currently connected to the network), the electronic device uses the corresponding cellular identifier to initiate (1142) communication with the corresponding contact (e.g., by default, the communication is initiated using the corresponding cellular identifier), such as in Figure 10F Zhongru Figure 10F As shown in Figure 1002. Based on the determination that the corresponding cellular identifier is unusable for communication (1144) (e.g., the corresponding cellular identifier is not activated on the electronic device and / or is not currently connected to a network), such as in... Figure 10HH Zhongru Figure 10HH As shown in Figure 1002, the electronic device abandons (1146) using the corresponding cellular identifier to initiate communication with the corresponding contact, and the electronic device provides (1148) a warning 1092 indicating that the corresponding cellular identifier is unavailable for communication (e.g., the electronic device displays text, images, audio, etc., indicating that communication cannot be performed using the corresponding cellular identifier because the corresponding cellular identifier is unavailable), such as in Figure 10II-Figure 10JJ Zhongru Figure 10II-Figure 10JJ As shown in Figure 1002.

[0361] The aforementioned method of providing a warning when communication cannot be initiated using the cellular identifier associated with the corresponding contact allows electronic devices to communicate to the user why communication was not initiated. This simplifies the interaction between the user and the device and enhances the device's operability (e.g., by automatically notifying the user why communication was not initiated, rather than requiring the user to enter a series of additional inputs to determine the reason). This, in turn, reduces power consumption and extends the device's battery life by enabling the user to use the device more quickly and efficiently.

[0362] In some implementations, providing a warning indicating that a corresponding cellular identifier (e.g., a "bu...

Claims

1. A method comprising: At an electronic device in communication with a display and one or more input devices: detecting a change in configuration of the device relative to one or more cellular identifiers when the electronic device is capable of communicating using a first cellular identifier associated with a first group of users or a second cellular identifier associated with a second group of users different from the first group of users; and In response to detecting the change in the configuration of the device relative to the one or more cellular identifiers: based on determining that the configuration change of the device includes removing the first cellular identifier from the electronic device, displaying on the display a first prompt having a selectable option, the selectable option of the first prompt, when selected, causing the first group of users to be associated with the second cellular identifier and not with the first cellular identifier; as well as Based on determining that the configuration change of the device includes removing the second cellular identifier from the electronic device, displaying a second prompt on the display having a selectable option that, when selected, causes the second group of users to be associated with the first cellular identifier and not with the second cellular identifier.

2. The method of claim 1 , wherein the first prompt includes an additional option that, when selected, denies associating the first group of users with the second cellular identifier, and the second prompt includes an additional option that, when selected, denies associating the second group of users with the first cellular identifier.

3. The method according to claim 1, comprising: In response to detecting the change in the configuration of the device relative to the one or more cellular identifiers: based on determining that the configuration change of the device includes disabling the first cellular identifier without removing the first cellular identifier from the electronic device, forgoing displaying the first prompt on the display; as well as Based on determining that the configuration change of the device includes disabling the second cellular identifier without removing the second cellular identifier from the electronic device, forgoing displaying the second prompt on the display.

4. The method according to claim 1, further comprising: upon detecting the configuration change of the device with respect to the one or more cellular identifiers, wherein the configuration change of the device with respect to the one or more cellular identifiers comprises removing the first cellular identifier without associating the first group of users with the second cellular identifier, and while the first group of users is associated with the first cellular identifier, displaying on the display a cellular setup user interface of the device, wherein the cellular setup user interface comprises a selectable affordance associated with the first cellular identifier; receiving, via the one or more input devices, a sequence of one or more inputs corresponding to the selectable affordances associated with the first cellular identifier while displaying the cellular settings user interface; as well as In response to receiving the sequence of one or more inputs, displaying on the display a third prompt having a selectable option that, when selected, causes the first group of users to be associated with the second cellular identifier and not with the first cellular identifier.

5. The method of claim 1 , wherein the configuration change of the device relative to the one or more cellular identifiers comprises removing the first cellular identifier without associating the first group of users with the second cellular identifier, the method further comprising: detecting, after detecting the change in the configuration of the device relative to the one or more cellular identifiers and when the first group of users is associated with the first cellular identifier, adding the first cellular identifier to the electronic device; receiving, after detecting the addition of the first cellular identifier to the electronic device, input via the one or more input devices corresponding to a request to communicate with a corresponding user in the first set of users; as well as In response to receiving the input, initiating communication with the corresponding user in the first set of users using the first cellular identifier.

6. The method according to claim 1, further comprising: receiving, after detecting the change in the configuration of the device relative to the one or more cellular identifiers, input via the one or more input devices corresponding to a request to communicate with a corresponding user; as well as In response to receiving the input: Based on determining that the configuration change of the device relative to the one or more cellular identifiers includes removing the first cellular identifier without associating the first group of users with the second cellular identifier: displaying, on the display, a prompt indicating that communication with the corresponding user will use the second cellular identifier instead of the first cellular identifier, based on determining that the corresponding user is in the first group of users, wherein the prompt includes a selectable option that, when selected, cancels the communication with the corresponding user; as well as Based on determining that the corresponding user is in the second group of users, initiating the communication with the corresponding user using the second cellular identifier without displaying the prompt indicating that the communication with the corresponding user will use the second cellular identifier instead of the first cellular identifier.

7. The method according to claim 6, wherein the corresponding user is in the first group of users, the method further comprising: In response to receiving the input corresponding to the request to communicate with the corresponding user: Based on determining that the configuration change of the device relative to the one or more cellular identifiers includes removing the first cellular identifier without associating the first group of users with the second cellular identifier: Determining that the respective user is associated with the first cellular identifier based on settings for the respective user indicating that the respective user is associated with a cellular identifier most recently used to communicate with the respective user: initiating said communication with said corresponding user using said second cellular identifier; and The respective user is associated with the second cellular identifier and not with the first cellular identifier.

8. The method according to claim 6, further comprising: In response to receiving the input corresponding to the request to communicate with the corresponding user: Based on determining that the configuration change of the device includes disabling the first cellular identifier without removing the first cellular identifier from the electronic device and without associating the first group of users with the second cellular identifier: Based on determining that the corresponding user is in the first group of users, a selectable option is displayed on the display, and when the selectable option is selected, the first cellular identifier is enabled.

9. The method according to claim 1, further comprising: receiving, while displaying the first prompt, input via the one or more input devices corresponding to a selection of the selectable option that, when selected, causes the first group of users to be associated with the second cellular identifier instead of the first cellular identifier; in response to receiving the input corresponding to a selection of the selectable option that, when selected, causes the first group of users to be associated with the second cellular identifier and not with the first cellular identifier, associating the first group of users with the second cellular identifier and not with the first cellular identifier; receiving, via the one or more input devices, input corresponding to a request to communicate with a respective user in the first set of users after associating the first set of users with the second cellular identifier and not with the first cellular identifier; as well as In response to receiving the input corresponding to the request to communicate with the corresponding user in the first group of users, initiating the communication with the corresponding user using the second cellular identifier.

10. The method according to claim 1, further comprising: After detecting the configuration change of the device including removing the first cellular identifier from the electronic device, detecting a configuration change of the device including adding a third cellular identifier to the electronic device; and In response to detecting the configuration change of the device including adding the third cellular identifier to the electronic device, initiating a process for setting the third cellular identifier on the electronic device, the process including displaying on the display a selectable option that, when selected, causes the first group of users associated with the removed first cellular identifier to be associated with the third cellular identifier instead of the first cellular identifier.

11. The method according to claim 1, further comprising: After detecting the configuration change of the device including removing the first cellular identifier from the electronic device, detecting a configuration change of the device including adding a corresponding cellular identifier to the electronic device; and In response to detecting the configuration change of the device including adding the corresponding cellular identifier to the electronic device: initiating a process for setting the corresponding cellular identifier based on determining that the corresponding cellular identifier is a cellular identifier not previously associated with the device, the process comprising displaying on the display a selectable option that, when selected, causes a corresponding set of users associated with another cellular identifier to be associated with the corresponding cellular identifier; as well as Based on determining that the corresponding cellular identifier is a cellular identifier previously associated with the device, initiating the process for setting the corresponding cellular identifier is abandoned.

12. The method according to claim 1, further comprising: When the electronic device is capable of communicating using the first cellular identifier or the second cellular identifier, displaying on the display one or more user interfaces configured to reflect device operation using multiple cellular identifiers on the electronic device; as well as In response to detecting the configuration change of the device: Based on determining that the configuration change of the device has resulted in the device being able to communicate using only a single cellular identifier, one or more user interfaces configured to reflect device operation using only the single cellular identifier on the electronic device are displayed on the display, which are different from the one or more user interfaces configured to reflect device operation using multiple cellular identifiers on the electronic device.

13. The method according to claim 1, further comprising: After detecting the configuration change of the device including disabling the first cellular identifier without removing the first cellular identifier from the electronic device, detecting a configuration change of the device including removing the first cellular identifier from the electronic device; and In response to detecting the configuration change of the device including removing the first cellular identifier from the electronic device, displaying the first prompt on the display with the selectable option, the selectable option of the first prompt, when selected, causing the first group of users to be associated with the second cellular identifier instead of the first cellular identifier.

14. 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 13.

15. A non-transitory 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 13.

Images