Patent Application
20240080389
The present disclosure relates generally to computer user interfaces, and more specifically to techniques for initiating communication in the event of a crash.
Electronic devices are used to send various types of communication, such as phone calls and text messages, using cellular communication. Some electronic devices are capable of detecting motion using sensors such as accelerometers and gyroscopes.
Some techniques for initiating communication in the event of a crash using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for initiating communication in the event of a crash. Such methods and interfaces optionally complement or replace other methods for initiating communication in the event of a crash. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
In accordance with some embodiments, a method is described. The method comprises: at a computer system that is in communication with a display generation component and one or more input devices: obtaining data indicating that a crash has occurred; in response to obtaining the data indicating that a crash has occurred, displaying, via the display generation component, a call option; and in accordance with a determination that the call option has been selected via the one or more input devices, initiating a process to call a predetermined number associated with the call option.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: obtaining data indicating that a crash has occurred; in response to obtaining the data indicating that a crash has occurred, displaying, via the display generation component, a call option; and in accordance with a determination that the call option has been selected via the one or more input devices, initiating a process to call a predetermined number associated with the call option.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: obtaining data indicating that a crash has occurred; in response to obtaining the data indicating that a crash has occurred, displaying, via the display generation component, a call option; and in accordance with a determination that the call option has been selected via the one or more input devices, initiating a process to call a predetermined number associated with the call option.
In accordance with some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: obtaining data indicating that a crash has occurred; in response to obtaining the data indicating that a crash has occurred, displaying, via the display generation component, a call option; and in accordance with a determination that the call option has been selected via the one or more input devices, initiating a process to call a predetermined number associated with the call option.
In accordance with some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system comprises: means for obtaining data indicating that a crash has occurred; means for, in response to obtaining the data indicating that a crash has occurred, displaying, via the display generation component, a call option; and means for, in accordance with a determination that the call option has been selected via the one or more input devices, initiating a process to call a predetermined number associated with the call option.
In accordance with some embodiments, a computer program product is described. The computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: obtaining data indicating that a crash has occurred; in response to obtaining the data indicating that a crash has occurred, displaying, via the display generation component, a call option; and in accordance with a determination that the call option has been selected via the one or more input devices, initiating a process to call a predetermined number associated with the call option.
In accordance with some embodiments, a method is described. The method comprises: at a computer system that is in communication with a display generation component and one or more input devices: obtaining data indicating that a crash has occurred; and in response to obtaining the data indicating that a crash has occurred: in accordance with a determination that a terrestrial wireless communication network is not reachable by the computer system, displaying, via the display generation component, a non-terrestrial wireless communication option that, when selected via the one or more input devices, initiates a process for communicating via a non-terrestrial wireless communication network; and in accordance with a determination that a terrestrial wireless communication network is reachable by the computer system, forgoing display of the non-terrestrial wireless communication option.
In accordance with some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: obtaining data indicating that a crash has occurred; and in response to obtaining the data indicating that a crash has occurred: in accordance with a determination that a terrestrial wireless communication network is not reachable by the computer system, displaying, via the display generation component, a non-terrestrial wireless communication option that, when selected via the one or more input devices, initiates a process for communicating via a non-terrestrial wireless communication network; and in accordance with a determination that a terrestrial wireless communication network is reachable by the computer system, forgoing display of the non-terrestrial wireless communication option.
In accordance with some embodiments, a transitory computer-readable storage medium is described. The transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: obtaining data indicating that a crash has occurred; and in response to obtaining the data indicating that a crash has occurred: in accordance with a determination that a terrestrial wireless communication network is not reachable by the computer system, displaying, via the display generation component, a non-terrestrial wireless communication option that, when selected via the one or more input devices, initiates a process for communicating via a non-terrestrial wireless communication network; and in accordance with a determination that a terrestrial wireless communication network is reachable by the computer system, forgoing display of the non-terrestrial wireless communication option.
In accordance with some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system comprises: one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: obtaining data indicating that a crash has occurred; and in response to obtaining the data indicating that a crash has occurred: in accordance with a determination that a terrestrial wireless communication network is not reachable by the computer system, displaying, via the display generation component, a non-terrestrial wireless communication option that, when selected via the one or more input devices, initiates a process for communicating via a non-terrestrial wireless communication network; and in accordance with a determination that a terrestrial wireless communication network is reachable by the computer system, forgoing display of the non-terrestrial wireless communication option.
In accordance with some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system comprises: means for obtaining data indicating that a crash has occurred; and means for, in response to obtaining the data indicating that a crash has occurred: in accordance with a determination that a terrestrial wireless communication network is not reachable by the computer system, displaying, via the display generation component, a non-terrestrial wireless communication option that, when selected via the one or more input devices, initiates a process for communicating via a non-terrestrial wireless communication network; and in accordance with a determination that a terrestrial wireless communication network is reachable by the computer system, forgoing display of the non-terrestrial wireless communication option.
In accordance with some embodiments, a computer program product is described. The computer program product comprises one or more programs configured to be executed by one or more processors of a computer system that is in communication with a display generation component and one or more input devices, the one or more programs including instructions for: obtaining data indicating that a crash has occurred; and in response to obtaining the data indicating that a crash has occurred: in accordance with a determination that a terrestrial wireless communication network is not reachable by the computer system, displaying, via the display generation component, a non-terrestrial wireless communication option that, when selected via the one or more input devices, initiates a process for communicating via a non-terrestrial wireless communication network; and in accordance with a determination that a terrestrial wireless communication network is reachable by the computer system, forgoing display of the non-terrestrial wireless communication option.
Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
Thus, devices are provided with faster, more efficient methods and interfaces for initiating communication in the event of a crash, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for initiating communication in the event of a crash.
For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
There is a need for electronic devices that provide efficient methods and interfaces for initiating communication in the event of a crash. For example, in some embodiments, an electronic device automatically provides an option to initiate communication with an emergency number when a crash is detected. For example, in some embodiments, if a crash is detected when a cellular communication network is not available, an electronic device provides user interfaces for communicating via an alternative communication network (e.g., a satellite communication network). Such techniques can reduce the cognitive burden on a user initiates communication in the event of a crash, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.
Below,
The processes described below enhance the operability of the devices and make the user-device interfaces more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) through various techniques, including by providing improved visual feedback to the user, reducing the number of inputs needed to perform an operation, providing additional control options without cluttering the user interface with additional displayed controls, performing an operation when a set of conditions has been met without requiring further user input, and/or additional techniques. These techniques also reduce power usage and improve battery life of the device by enabling the user to use the device more quickly and efficiently. Reducing the number of inputs needed to perform an operation and providing clear feedback to the user enable the user to use the device more quickly and efficiently, which is particularly important in emergency situations and/or when a crash has occurred for several reasons. Using a device efficiently conserves battery life, which is important in emergency situations because some emergency communication features use satellite communications that can use significant energy (e.g., more energy than cellular communications) and because opportunities to recharge the device in an emergency may be limited (e.g., because a user has been involved in a crash). User interfaces that clearly indicate how to use a device quickly and efficiently are particularly important in emergency situations or when a crash has occurred because a user may be stressed and more prone to making mistakes. In an emergency situation and/or when a crash has occurred, reducing errors by providing clear instructions and feedback saves time communicating with emergency services, which can improve the likelihood that emergency assistance will be provided more quickly.
In addition, in methods described herein where one or more steps are contingent upon one or more conditions having been met, it should be understood that the described method can be repeated in multiple repetitions so that over the course of the repetitions all of the conditions upon which steps in the method are contingent have been met in different repetitions of the method. For example, if a method requires performing a first step if a condition is satisfied, and a second step if the condition is not satisfied, then a person of ordinary skill would appreciate that the claimed steps are repeated until the condition has been both satisfied and not satisfied, in no particular order. Thus, a method described with one or more steps that are contingent upon one or more conditions having been met could be rewritten as a method that is repeated until each of the conditions described in the method has been met. This, however, is not required of system or computer readable medium claims where the system or computer readable medium contains instructions for performing the contingent operations based on the satisfaction of the corresponding one or more conditions and thus is capable of determining whether the contingency has or has not been satisfied without explicitly repeating steps of a method until all of the conditions upon which steps in the method are contingent have been met. A person having ordinary skill in the art would also understand that, similar to a method with contingent steps, a system or computer readable storage medium can repeat the steps of a method as many times as are needed to ensure that all of the contingent steps have been performed.
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. In some embodiments, these terms are used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. In some embodiments, the first touch and the second touch are two separate references to the same touch. In some embodiments, the first touch and the second touch are both touches, but they are not the same touch.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad). In some embodiments, the electronic device is a computer system that is in communication (e.g., via wireless communication, via wired communication) with a display generation component. The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separate from the computer system. As used herein, “displaying” content includes causing to display the content (e.g., video data rendered or decoded by display controller 156) by transmitting, via a wired or wireless connection, data (e.g., image data or video data) to an integrated or external display generation component to visually produce the content.
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs (such as computer programs (e.g., including instructions)) and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.
A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 optionally also includes one or more optical sensors 164.
Device 100 optionally also includes one or more depth camera sensors 175.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 optionally also includes one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 optionally also includes one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo!Widgets).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs (such as computer programs (e.g., including instructions)), procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (e.g., 187-1 and/or 187-2) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definitions 186 include a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including methods 700 and 900 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, the computer system is in a locked state or an unlocked state. In the locked state, the computer system is powered on and operational but is prevented from performing a predefined set of operations in response to user input. The predefined set of operations optionally includes navigation between user interfaces, activation or deactivation of a predefined set of functions, and activation or deactivation of certain applications. The locked state can be used to prevent unintentional or unauthorized use of some functionality of the computer system or activation or deactivation of some functions on the computer system. In some embodiments, in the unlocked state, the computer system is powered on and operational and is not prevented from performing at least a portion of the predefined set of operations that cannot be performed while in the locked state. When the computer system is in the locked state, the computer system is said to be locked. When the computer system is in the unlocked state, the computer is said to be unlocked. In some embodiments, the computer system in the locked state optionally responds to a limited set of user inputs, including input that corresponds to an attempt to transition the computer system to the unlocked state or input that corresponds to powering the computer system off.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
In the embodiment illustrated in
Although
Computer system 604b displays network status indicator 605, which includes cellular status indicator 605a and internet status indicator 605b. Cellular status indicator 605a displays an indication of a current status of a connection of computer system 604b with a cellular communication network. For example, an appearance of cellular status indicator 605a can indicate whether or not computer system 604b is connected to a cellular communication network and/or the strength of the signal between computer system 604b and the cellular communication network. Internet status indicator 605b displays an indication of an internet communication network that computer system 604b can use to connect to the internet (e.g., a Wi-Fi network, LTE, 3G, 4G, or 5G). For example, an appearance of internet status indicator 605b can indicate whether or not a network is available for computer system 604b to connect to the internet, the network that computer system 604b can use to connect to the internet (if an internet communication network is available), and/or the strength of the signal between computer system 604b and the internet communication network.
In some embodiments, computer system 604a can independently connect to a cellular communication network and/or an internet communication network (e.g., without computer system 604b) in order to perform communication. In some embodiments, computer system 604a can connect to a cellular communication network and/or an internet communication network via computer system 604b in order to perform communication (e.g., computer system 604a cannot independently connect to a cellular communication network and/or an internet communication network). In some embodiments, computer system 604a displays network status indicator 605, cellular status indicator 605a, and/or internet status indicator 605b based on the ability of computer system 604a to connect to a cellular communication network and/or an internet communication network (e.g., either independently and/or via computer system 604b).
In
In response to obtaining an indication that the crash has been detected, computer system 604a displays crash detection interface 612 as shown in
In accordance with (or, optionally, in response to) a determination that a time threshold is satisfied without detecting an input (e.g., without detecting selection of communication option 612c or selection of confirmation option 612d), computer system 604a displays communication alert 612e, countdown 612f, and cancel option 612g, as shown in
In some embodiments, computer system 604a displays communication alert 612e, displays countdown 612f, displays cancel option 612g, and/or outputs a non-visual indication that a call to emergency services has been or will be initiated in accordance with (or, optionally, in response to) a determination that a threshold amount of time has passed since obtaining the indication that a crash has been detected (e.g., that crash detection interface 612 has been displayed for a threshold amount of time) without detecting an input. Outputting a non-visual indication that a call to emergency services has been or will be initiated is particularly helpful in an emergency situation such as a crash in which a user may be distracted and/or unable to view display 606a of computer system 604a.
In some embodiments, in response to detecting selection 625c of cancel option 612g, computer system 604a ceases or pauses the process of initiating a call to emergency services. For example, in response to detecting selection 625c of cancel option 612g, computer system 604a ceases countdown 612f and displays crash detection interface 612 as shown in
In response to a determination that countdown 612f has ended, computer system 604a initiates (or attempts to initiate) a call to emergency services (e.g., directly or via computer system 604b). In some embodiments, computer system 604a initiates (or attempts to initiate) a call to emergency services in response to detecting selection 625a of communication option 612c. In some embodiments, selection of communication option 612c requires moving an element (e.g., the SOS circle in 612c) from a first position (e.g., a left side of 612c) to a predetermined second position (e.g., a right side of 612c), which can help prevent accidental selection of communication option 612c. For example, in some embodiments, communication option 612c is not selected if the element is not moved to the predetermined second position (e.g., not moved far enough to the right). In
In some embodiments, as shown in
In response to establishing the call with emergency services (e.g., when emergency services answers the call and/or the call becomes active), computer system 604a updates call status indicator 612h (e.g., to “Call—Active”) as shown in
In some embodiments, as shown in
In some embodiments, when computer system 604a plays message 618, computer system 604a displays stop message option 612l, as shown in
In response to detecting selection 625d of stop message option 612l, computer system 604a stops playing message 618. In some embodiments, in response to detecting selection 625d of stop message option 612l, computer system 604a ceases display of stop message option 612l and, optionally, displays (e.g., re-displays) end call option 612j and/or call menu option 612k, as shown in
In response to detecting selection 625f of end call option 612j, computer system 604a initiates a process for ending the call with emergency services. In some embodiments, in response to detecting selection 625f of end call option 612j, computer system 604a ends the call with emergency services without detecting further input. In some embodiments, in response to detecting selection 625f of end call option 612j, computer system 604a displays prompt 612m (e.g., “End Call?), which prompts a user to confirm whether or not to end the call with emergency services while maintaining the call with emergency services. Along with prompt 612m, computer system 604a displays continue call option 612n for continuing the call with emergency services and confirm option 612o for ending the call with emergency services. In response to detecting selection of continue call option 612n (e.g., a tap on continue call option 612n and/or other input selecting continue call option 612n), computer system 604a continues the call with emergency services and, optionally, displays (e.g., returns to) crash detection interface 612 as displayed in
In some embodiments, after ending the call with emergency services (e.g., in response to selection 625e in
In some embodiments, after ending the call with emergency services (e.g., in response to selection 625e in
In response to detecting selection 625i of crash detection settings option 622a, computer system 604a displays a user interface for selecting, setting, and/or changing one or more settings and/or parameters associated with a crash detection feature of computer system 604a. In some embodiments, the crash detection feature of computer system 604a includes the ability of computer system 604a to detect a crash, to determine that a crash has occurred, and/or to perform the features described with reference to
In response to obtaining an indication that the crash has been detected, computer system 604b displays crash detection interface 626 as shown in
Response prompt 626a prompts a user to respond to the information and options displayed in crash detection interface 626 (e.g., to select communication option 626c, medical ID option 626e, or close option 626d) and informs the user that computer system 604b will initiate an emergency feature (e.g., initiate an SOS feature and/or automatically call emergency services) if computer system 604b does not detect a response. In response to detecting selection of (e.g., a tap and/or swipe on) medical ID option 626e, computer system 604b displays information of a user associated with computer system 604a that can be relevant to a medical condition of the user (e.g., name, age, weight, height, blood type, medications, allergies, medical conditions, a designated contact, and/or contact information of the designated contact). In response to detecting selection of close option 626d (e.g., a tap on close option 626d and/or other input selecting close option 626d), computer system 604b ceases display of crash detection interface 626 and, optionally, displays (e.g., returns to) user interface 610.
In accordance with (or, optionally, in response to) a determination that a time threshold is satisfied without detecting an input (e.g., without detecting selection of communication option 626c or selection of close option 626d), computer system 604b displays emergency communication indicator 626f (e.g., “Emergency SOS”), communication alert 626h, and countdown 626g, as shown in
In response to a determination that countdown 626g has ended, computer system 604b initiates (or attempts to initiate) a call to emergency services. In some embodiments, computer system 604b initiates (or attempts to initiate) a call to emergency services in response to detecting selection of (e.g., a tap and/or swipe on) communication option 626c (e.g., in
In response to establishing the call with emergency services (e.g., when emergency services answers the call and/or the call becomes active), computer system 604b updates call status indicator 626j (e.g., to “Call—Active”) and displays crash detected indicator 626m, as shown in
In some embodiments, as shown in
In some embodiments, when computer system 604b plays message 618, computer system 604b displays stop message option 626n, as shown in
In response to detecting selection 625s of stop message option 626n, computer system 604b stops playing message 618. In some embodiments, in response to detecting selection 625s of stop message option 626n, computer system 604b ceases display of stop message option 626n and, optionally, displays (e.g., re-displays) call management options 626k, as shown in
In response to detecting selection 625t of end call option 6261, computer system 604b, initiates a process for ending the call with emergency services. In some embodiments, in response to detecting selection 625t of end call option 6261, computer system 604b ends the call with emergency services without detecting further input. In some embodiments, in response to detecting selection 625t of end call option 6261, computer system 604b displays a prompt (e.g., prompt 612m) for a user to confirm whether or not to end the call with emergency services and options for continuing the call with emergency services (e.g., continue call option 612n) and/or for ending the call with emergency services (e.g., confirm option 6120).
In some embodiments, after ending the call with emergency services (e.g., in response to selection of end call option 6261 in
In some embodiments, after ending the call with emergency services (e.g., in response to selection of end call option 6261 in
In response to detecting selection 625k of emergency settings option 628a, computer system 604b displays emergency settings interface 630 as shown in
Emergency settings interface 630 includes options for selecting, setting, and/or changing one or more settings and/or parameters associated with emergency features of computer system 604b. For example, in
In response to detection selection 625l of call after crash state option 630a, computer system 604b sets a state of the crash detection feature (or call after crash feature). For example, in
In some embodiments, computer system 604b can share data about a detected crash (also referred to as “crash data”) with an application (e.g., a native application or a third party application) on computer system 604b. In
In
In response to detecting selection 625n of sharing state option 632a in
In some embodiments, the process of installing the application includes a request by the application being installed to access crash data (e.g., for computer system 604b to share crash data with the application being installed). In response to receiving the request to access crash data, computer system 604b prompts the user to grant or deny the request to access crash data. For example, in response to receiving the request to access crash data, computer system 604b displays prompt 634d shown in
In some embodiments, computer system 604b performs a setup process that includes displaying a set of one or more user interfaces that inform a user about features available on computer system 604b. In some embodiments, the setup process is performed when computer system 604b is initially turned on, when computer system 604b is first used after an upgrade (e.g., a software and/or operating system upgrade), and/or when computer system is first used after being reset.
In response to detecting selection 625p of crash detection element 638a, computer system 604b displays crash detection interface 640, as shown in
In response to detecting selection 625q of call after crash status option 640b, computer system 604b disables the capability to detect a crash and/or call emergency services after a crash is detected. After disabling the capability to detect a crash and/or call emergency services after a crash is detected, computer system detects selection 625r of done option 640d. In response to detecting selection 625r of done option 640d, computer system 604b displays (e.g., returns to) health checklist interface 638, as shown in
As described below, method 700 provides an intuitive way for initiating communication in the event of a crash. The method reduces the cognitive burden on a user for initiating communication in the event of a crash, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to initiate communication in the event of a crash faster and more efficiently conserves power and increases the time between battery charges.
The computer system obtains (702) (e.g., receives or detects) data indicating that a crash (e.g., a crash, accident, and/or impact involving a vehicle such as, for example, a car, truck, motorcycle, scooter, bus, bike, boat, train, plane, wheelchair, golf cart, or all-terrain vehicle (ATV); the crash illustrated in 600 of
In response to obtaining the data indicating that a crash has occurred, the computer system displays (704), via the display generation component, a call option (e.g., 612c, 626c, a selectable call option, an icon, a button, an affordance, and/or a user-interactive graphical user interface object). In some embodiments, the computer system initiates display of the call option in response to obtaining the data indicating that a crash has occurred (e.g., the call option is not provided, is not displayed, and/or is not available prior to obtaining the data indicating that a crash has occurred). In accordance with a determination that the call option (e.g., 612c or 626c) has been selected via the one or more input devices (e.g., in response to detecting selection of the call option, such as selection 625a), the computer system initiates (706) a process to call a predetermined number (or a contactable entity, such as a person, service, or business) associated with the call option. In some embodiments, the call option includes (e.g., is) a graphical object that moves (e.g., slides) in accordance with movement of an input (e.g., a swipe or touch and drag input). In some embodiments, selection of the call option requires moving (e.g., on a display) the graphical object by a predetermined amount and/or to a predetermined location (e.g., from a first position, such a first location and/or first orientation, to a second position, such as a predefined location and/or a predefined orientation). In some embodiments, selection of the call option requires moving the graphical object from a first position (such as a first side, left side, top side, or upper side) on a predefined region or path to a second position (such as an opposite side, right side, bottom side, or lower side) of the predefined region or path. In some embodiments, in response to detecting selection of the call option, the computer system initiates a call to the predetermined number immediately (e.g., without a predetermined delay and/or countdown) and/or automatically without requiring further input (e.g., without requiring confirmation). In some embodiments, in response to detecting selection of the call option, the computer system initiates a call to the predetermined number and displays a call user interface (e.g., without displaying an intermediate or intervening user interface). In some embodiments, the call option is associated with an emergency service, an emergency number, and/or an emergency contact (e.g., a contactable user designated as an emergency contact). Examples of numbers associated with an emergency service include 911 in the United States, 999 in the United Kingdom, 112 in Europe, 110 and/or 119 in Japan, and 000 in Australia. Displacing a call option to initiate a process to call a predetermined number in response to obtaining data indicating that a crash has occurred automatically provides a user with an option to contact the predetermined number in the event of a crash, which makes it easier and faster to contact the predetermined number with fewer inputs and reduces the chance of mistakes, particularly in an emergency, which provides improved feedback to the user, reduces the number of inputs needed to perform an operation, provides additional control options without cluttering the user interface with additional displayed controls, and performs an operation when a set of conditions has been met without requiring further user input. Providing quick and efficient access to a predetermined number enables the computer system to be more quickly and efficiently controlled, which is particularly important in emergency situations and/or when a crash has occurred because a user may be stressed and more prone to making mistakes.
In some embodiments, after (e.g., in response to) obtaining the data indicating that a crash has occurred, the computer system provides (e.g., displays and/or outputs) an indication (e.g., 612b, 614, 612e, 612p, 626b, text, an audio output, and/or a haptic output) that a crash has been detected. In some embodiments, the computer system provides the indication that a crash has been detected while concurrently displaying the call option. In some embodiments, after (e.g., in response to) obtaining the data indicating that a crash has occurred, the computer system displays a cancel option (e.g., a selectable cancel option, an icon, a button, an affordance, and/or a user-interactive graphical user interface object), e.g., concurrently with the call option, and optionally, while concurrently providing the indication that a crash has been detected. In response to detecting selection of the cancel option, the computer system ceases display of the call option, ceases attempting to call the predetermined number, and/or ceases providing the indication that a crash has been detected. Providing an indication that a crash has been detected informs the user that the computer system has detected a crash and is operating accordingly so that the user does not make additional unnecessary inputs, which provides improved feedback to the user and reduces the number of inputs needed to perform an operation. Providing quick and efficient access to a respective number enables the computer system to be more quickly and efficiently controlled, which is particularly important in a crash situation because a user may be stressed and more prone to making mistakes.
In some embodiments, after obtaining the data indicating that a crash has occurred, in accordance with a determination that a first threshold (e.g., non-zero) amount of time has elapsed (e.g., since obtaining the data indicating that a crash has occurred or since initiating display of the call option) (and, optionally, that the call option has not been selected), the computer system initiates a call to the predetermined number associated with the call option without detecting selection of the call option. In some embodiments, the first threshold amount of time is, e.g., 5 seconds, 10 seconds, 15 seconds, 30 seconds, or one minute. In some embodiments, the computer system automatically initiates a call to the predetermined number associated with the call option at a first predetermined time after obtaining the data indicating that a crash has occurred (e.g., at a non-zero amount of time, such as 5 seconds, 10 seconds, 15 seconds, 30 seconds, or one minute, after obtaining the data indicating that a crash has occurred). Initiating a call to the predetermined number without detecting selection of the call option in accordance with a determination that a threshold amount of time has elapsed automatically initiates communication with the predetermined number without requiring feedback or input from the user, which provides improved feedback to the user, reduces the number of inputs needed to perform an operation, and performs an operation when a set of conditions has been met without requiring further user input.
In some embodiments, after obtaining the data indicating that a crash has occurred (and before initiating the call to the predetermined number associated with the call option without detecting selection of the call option): in accordance with a determination that a second threshold (e.g., non-zero) amount of time has elapsed (e.g., since obtaining the data indicating that a crash has occurred or since initiating display of the call option) (and, optionally, that the call option has not been selected), the computer system starts a countdown (e.g., 612f and/or 626g) for initiating a call to the predetermined number associated with the call option without detecting selection of the call option, wherein the second threshold amount of time is less than (e.g., 3 seconds less than, 5 second less than, 10 seconds less than, or 30 seconds less than) the first threshold amount of time, and wherein the first threshold amount of time has elapsed when the countdown expires. In some embodiments, the second threshold amount of time is, e.g. 5 seconds, 10 seconds, 15 seconds, 30 seconds, or one minute). In some embodiments, the computer system automatically initiates a call to the predetermined number associated with the call option when the countdown expires. In some embodiments, after obtaining the data indicating that a crash has occurred and in accordance with a determination that the second threshold amount of time has elapsed, the computer system provides a haptic notification that a call to the predetermined number associated with the call option will be initiated without detecting selection of the call option and/or audio indicating that a call to the predetermined number associated with the call option will be initiated without detecting selection of the call option (e.g., an audio message announcing that a call to the predetermined number associated with the call option will be initiated without detecting selection of the call option). Starting a countdown for initiating a call to the predetermined number in accordance with a determination that a second threshold amount of time has elapsed enables the computer system to automatically initiate communication with the predetermined number if, e.g., the user is unable to locate or use the computer system after a crash has occurred, which provides improved feedback to the user, reduces the number of inputs needed to perform an operation, and performs an operation when a set of conditions has been met without requiring further user input.
In some embodiments, after initiating a call to the predetermined number associated with the call option without detecting selection of the call option (e.g., after a call to the predetermined number is initiated automatically due to not receiving user input such as selection of the call option or user input that acknowledges that the user is alright (e.g., selection of an “I'm okay” option) or does not want to call the predetermined number (e.g., selection of a cancel option)): after establishing a call with the predetermined number in response to initiating a call to the predetermined number associated with the call option without detecting selection of the call option (e.g., when the call is answered), the computer system outputs (e.g., plays) an audio message (e.g., 618, a predetermined audio message, a voice message, and/or a recorded audio message) that indicates that a crash has been detected. In some embodiments, the computer system plays a recorded message when the call is made automatically (e.g., in case the user of the computer system is not responsive). In some embodiments, the audio message includes information about the crash such as, e.g., that a crash was detected, a location of the crash, a time of the crash, and/or people involved in the crash. In some embodiments, while outputting the audio message, the computer system displays a selectable option (e.g., a button, icon, affordance, or user-interactive graphical object), that when selected, causes the computer system to stop playback of the audio message. Outputting an audio message that indicates that a crash has been detected informs the recipient of the call about the circumstances if, e.g., the user of the computer system is unable to communicate or locate the computer system after a crash has occurred, which reduces the number of inputs needed to perform an operation.
In some embodiments, after obtaining the data indicating that a crash has occurred, the computer system sends a communication (e.g., a text message and/or audio message) to one or more (e.g., one, two, three, four, or five) designated contacts (e.g., a person or number designated as an emergency contact) (e.g., send the communication to one or more designated contacts in response to selection 625f of 612o in
In some embodiments, in response to a determination that a call to the predetermined number has ended (and, optionally, in accordance with a determination that the call to the predetermined number was initiated automatically (e.g., without user input, such as selection of the call option)), the computer system displays an indication (e.g., 612p, 626b, 626o, text and/or a graphic) that a crash was detected. In some embodiments, the indication that a crash was detected includes an indication (e.g., text and/or a graphic) of a device (e.g., the computer system or an external computer system in communication with the computer system) that detected the crash. In some embodiments, the computer system causes display of an indication that a crash was detected on an external computer system (e.g., a device in communication with the computer system, such as a smartwatch or smartphone that is paired (e.g., has a dedicated communication channel) with the computer system). Displaying an indication that a crash was detected in response to a determination that a call to the predetermined number has ended informs the user that the computer system has detected a crash and is operating accordingly to prevent the user from making additional unnecessary or incorrect inputs, which provides improved feedback to the user and reduces the number of inputs needed to perform an operation.
In some embodiments, displaying the indication that a crash was detected includes displaying an indication of a time at which the crash was detected (e.g., “1 minute ago” in 612p, “1 minute ago” in 626o, an absolute time, such as 1:35, or a relative time, such as 15 minutes ago). Displaying an indication of a time at which the crash was detected informs the user when the crash occurred in the event that the user was unconscious for a period of time after the crash to prevent the user from making additional unnecessary on incorrect inputs, which provides improved feedback to the user and reduces the number of inputs needed to perform an operation.
In some embodiments, after obtaining the data indicating that a crash has occurred: in response to a determination that a call to the predetermined number has ended (and, optionally, in accordance with a determination that the call to the predetermined number was initiated automatically (e.g., without user input, such as selection of the call option)), the computer system displays a second call option (e.g., 612c in
In some embodiments, after obtaining the data indicating that a crash has occurred: in response to a determination that a call to the predetermined number has ended (and, optionally, in accordance with a determination that the call to the predetermined number was initiated automatically (e.g., without user input, such as selection of the call option)), the computer system displays a medical ID option (e.g., 612q in
In some embodiments, after obtaining the data indicating that a crash has occurred, the computer system disables a voice assistant functionality on the computer system (e.g., a voice assistant functionality is disabled in
In some embodiments, after initiating (e.g., either automatically or manually) a call with the predetermined number, the computer system detects a request to end the call with the predetermined number; and in response to detecting the request to end the call with the predetermined number, the computer system displays, without ending the call with the predetermined number, an option (e.g., 612m, 612o, a prompt, a selectable option, an icon, a button, an affordance, and/or a user-interactive graphical user interface object) to confirm the request to end the call with the predetermined number that, when selected, causes the computer system to end the call with the predetermined number. In some embodiments, the computer system concurrently displays the option to confirm the request to end the call with the predetermined number and an option to cancel the request to end the call with the predetermined number (e.g., to continue the call with the predetermined number). In some embodiments, in response to a request to exit a crash detection user interface (e.g., a user interface displayed in response to obtaining data indicating that a crash has occurred), the computer system displays, without exiting the crash detection user interface, an option to confirm the request to exit the crash detection user interface that, when selected, causes the computer system to exit (e.g., cease display of) the crash detection user interface. Displaying an option to confirm a request to end the call, without ending the call, prevents the user from inadvertently ending the call prematurely and having to provide additional inputs to re-initiate the call, which provides improved feedback to the user, reduces the number of inputs needed to perform an operation, and reduces errors.
In some embodiments, the computer system displays an enable-crash-detection option (e.g., 624a, 630a, 640b, a toggle button, a switch, an affordance, and/or a user interactive graphical object) that, when selected, sets a state (e.g., enabled, disabled, on, or off) of a capability (e.g., of the computer system or an external computer system) to display the call option in response to obtaining data indicating that a crash has occurred. In some embodiments, in response to detecting input selecting the enable-crash-detection option while the state of the capability to display the call option is in a first state, the computer system sets the capability to display the call option to a second state different from the first state; and in response to detecting input selecting the enable-crash-detection option while the state of the capability to display the call option is in the second state, the computer system sets the capability to display the call option to the first state. In some embodiments, the call option is displayed in response to obtaining data indicating that a crash has occurred in accordance with a determination that the capability to display the call option is in a first state (e.g., enabled or on). In some embodiments, in response to obtaining data indicating that a crash has occurred, the computer system foregoes displaying the call option in accordance with a determination that the capability to display the call option is in a second state (e.g., disabled, not enabled, or off) that is different from the first state. In some embodiments, the enable-crash-detection option is displayed on an external computer system (e.g., a device in communication with the computer system, such as a smartwatch or smartphone that is paired (e.g., has a dedicated communication channel) with the computer system). In some embodiments, the enable-crash-detection option is displayed on the external computer system in a companion application that provides selectable options for selecting settings and/or operational parameters of the computer system. In some embodiments, the enable-crash-detection option is displayed during an initialization or onboarding process (e.g., at the computer system or an external computer system that is configured to communicate with the computer system). In some embodiments, the enable-crash-detection option is displayed as part of a process of presenting safety features of the computer system and/or an external computer system in communication with the computer system. In some embodiments, the enable-crash-detection option is not displayed if the computer system is not capable of detecting that a crash has occurred (e.g., even if the computer system is capable of displaying the call option in response to obtaining data indicating that a crash detected by an external computer system has occurred. In some embodiments, the state (e.g., enabled or disabled) of the capability to display the call option in response to obtaining data indicating that a crash has occurred for the computer system is based on a setting of the state of the capability for another (e.g., an external) computer system (e.g., the state of the capability is mirrored between devices). Displaying an option to set a state of the capability to display the call option in response to obtaining data indicating that a crash has occurred provides a quick and efficient means for the user to enable or disable the capability, which reduces the number of inputs needed to perform an operation.
In some embodiments, the computer system displays a user interface (e.g., 638 and/or 640) of a health application that includes information associated with health of a user (e.g., activity data, body measurements, cycle data, hearing data, heart data, mindfulness data, mobility data, nutrition data, respiratory data, sleep data, health symptoms, vitals data, and/or health records), where displaying the enable-crash-detection option (e.g., 640b) includes displaying the enable-crash-detection option in the user interface of the health application (e.g., as part of a checklist of health-related items, such as a sequence of information, options, features, and/or user interfaces associated with health-related items). In some embodiments, the user interface of the health application includes an option that, when selected, displays a set of options related to detecting a crash, including the enable-crash detection option. In some embodiments, the set of options related to detecting a crash is a subset of a set of options related to emergency features (e.g., options for emergency SOS features that are available in a menu of emergency features, including the enable-crash detection option). Displaying the enable-crash-detection option in the user interface of the health application informs the user of the crash detection capability in a relevant location and provides a quick and efficient means for the user to enable or disable the capability, which provides improved feedback to the user and reduces the number of inputs needed to perform an operation.
In some embodiments, the enable-crash-detection option, when selected, enables a capability of the computer system to display the call option in response to obtaining data indicating that a crash has occurred without enabling a capability of a second computer system to display the call option in response to obtaining data indicating that a crash has occurred (e.g., 624a controls the capability of computer system 604a, but not the capability of computer system 604b; and/or 630a controls the capability of computer system 604b, but not the capability of computer system 604a). In some embodiments, the computer system displays a second enable-crash-detection option that, when selected, enable a capability of an external computer system to display the call option in response to obtaining data indicating that a crash has occurred (e.g., the computer system concurrently displays device-specific options for enables a capability to display the call option in response to obtaining data indicating that a crash has occurred). In some embodiments, the computer system displays the state of the capability to display the call option in response to obtaining data indicating that a crash has occurred for a first device (e.g., the computer system) and, optionally, concurrently displays the state of the capability to display the call option in response to obtaining data indicating that a crash has occurred for a second device (e.g., an external device) different from the first device (e.g., the computer system displays the state of a crash detection capability by device). Enabling a capability of the computer system to display the call option in response to obtaining data indicating that a crash has occurred without enabling a capability of a second computer system to display the call option in response to obtaining data indicating that a crash has occurred provides the user with greater control over the crash detection functionality and reduces the change of error, which provides improved feedback to the user and reduces the number of inputs needed to perform an operation.
In some embodiments, after obtaining data indicating that a crash has occurred, the computer system provides (e.g., shares) data associated with the crash to an application (e.g., an application designated in 632b in
In some embodiments, providing data associated with the crash to an application includes providing data associated with the crash to a first application without providing data associated with the crash to a second application that is different from the first application, wherein the first application and the second application have been authorized to be provided with data associated with a crash after a crash is determine to have occurred (e.g., the computer system provides data associated with the crash to only one application listed in 632b; and/or the computer system provides data associated with the crash to only one application, even if multiple applications have been granted access to receive crash detection data). In some embodiments, the computer system provides the data associated with the crash to the first application instead of the second application in accordance with a determination that the first application was granted access to receive crash detection data more recently than the second application. Providing data associated with the crash to a first application without providing data associated with the crash to a different application avoids multiple applications providing redundant services and/or functionality after a crash and reduces the amount of data that has to be shared, which conserves computing resources and saves battery life.
In some embodiments, the computer system displays a sharing option (e.g., 632a, a toggle button, a switch, an affordance, and/or a user interactive graphical object) that, when selected (e.g., 625n), sets a state (e.g., enabled, disabled, on, or off) of a parameter for providing data associated with the crash to an application; and after (e.g., in response to) obtaining the data indicating that a crash has occurred: in accordance with a determination that the state of the parameter is a first state (e.g., on or enabled), the computer system provides data associated with the crash to an application; and in accordance with a determination that the stat of the parameter is a second state (e.g., off or disabled) different from the first state, the computer system forgoes providing data associated with the crash to an application. In some embodiments, in response to detecting input selecting the sharing option while the state of the parameter for providing data associated with the crash to an application is in a first state, the computer system sets the state of the parameter for providing data associated with the crash to an application to a second state different from the first state; and in response to detecting input selecting the sharing option while the state of the parameter for providing data associated with the crash to an application is in the second state, the computer system sets the state of the parameter for providing data associated with the crash to an application to the first state. In some embodiments, if the state of the parameter is the first state (e.g., on or enabled), the computer system displays (e.g., concurrently with the sharing option) a list of applications with which the data associated with the crash can be provided. In some embodiments, in response to input selecting an application from the list of applications, the computer system designates the selected application (e.g., visually, such as with highlighting and/or a checkmark, and/or in memory). In some embodiments, providing data associated with the crash to an application in accordance with a determination that the state of the parameter is a first state includes providing data associated with the crash to the designated application in accordance with the selected application. Displacing the share option enables a user to quickly and easily select whether or not to share data after a crash to prevent unnecessarily sharing data, which conserves computing resources and saves battery life.
Note that details of the processes described above with respect to method 700 (e.g.,
In
Although no cellular network is available, computer system 604b is capable of communicating via an alternative communication network, such as, e.g., a satellite communication network, which is indicated by display of satellite communication capability indicator 605e. Because computer system 604b is capable of satellite communication, in response to a determination that the call to emergency services attempted in
In some embodiments, in response to detecting selection 825a of satellite communication option 802, computer system 604b attempts to send a message to emergency services via satellite automatically (e.g., without further user input). In some embodiments, computer system 604b attempts to send a message to emergency services via satellite automatically (e.g., without further user input) if computer system 604b does not detect a user input within a predetermined amount of time after displaying satellite communication option 802 (or, optionally, after the call to emergency services fails). In some embodiments, the message to emergency services is generated automatically with information such as, e.g., a name or identity of a user associated with computer system 604b, a location of computer system 604b, and/or an indication that a crash has been detected.
In some embodiments, computer system 604b must be connected (e.g., via wireless communication) to a satellite in order to send a message via satellite. In some embodiments, if computer system 604b is connected to a satellite when the attempt to send the message to emergency services is made, then computer system 604b sends the message via satellite and displays (e.g., updates) crash detection interface 626 as shown in
In
In some embodiments, if computer system 604b is not connected to a satellite when the attempt to send the message to emergency services is made, computer system 604b initiates a process of sending a communication via satellite. In some embodiments, the process of sending a communication via satellite includes displaying an information and/or instruction interface, such as, e.g., information interface 810 shown in
In some embodiments, in response to detecting selection 825a of satellite communication option 802, computer system 604b initiates a process for sending a communication to emergency services via satellite without attempting to send an automatically-generated message. For example, computer system 604b can prompt a user for information to generate a message prior to attempting to send a message, as shown and described with reference to
Information interface 810 includes information about generating a message to send via satellite, connecting to a satellite, and/or sending a message via satellite. In some embodiments, computer system 604b (or a portion thereof, such as an antenna) has to be physically aligned with a satellite in order to connect with the satellite for communication. Graphic 810b illustrates a user aligning a device with a satellite. In some embodiments, graphic 810b includes an animation of a graphical representation of a satellite and/or a graphical representation of a user's hand and/or device moving (e.g., from side to side) to indicate that a user may have to move computer system 604b to align with a satellite.
Feature indicator 810c indicates that information interface 810 relates to a feature of texting emergency services via satellite. Instructions 810d instructs a user to be outside to connect with a satellite (e.g., so that computer system 604b is not obstructed from a satellite by a building). Alert 810e indicates that messages sent via satellite will take longer to send than messages sent via a cellular network. Prompt 810f prompts the user to answer questions to get a faster response. Content indicator 810g indicates that a location and medical information may be shared when a message is sent.
In
In response to detecting selection 825c of report emergency option 810h, computer system 604b continues the process of sending a communication via satellite. In some embodiments the process of sending a communication via satellite includes providing one or more sets of options that a user can select to generate content of a message.
For example, in response to detecting selection 825c of report emergency option 810h, computer system 604b displays first report generation interface 812, which includes prompt 812a and first set of options 812b for responding to prompt 812a, as shown in
In some embodiments, the options for generating the message are based on a crash being detected. For example, in accordance with a determination that a crash was detected, computer system 604b displays one set of options (e.g., options that are likely to be related to a crash); and in accordance with a determination that a crash was not detected, computer system 604b displays a different set of options (e.g., a set of options that includes options related to other types of emergencies that are not related to a crash, such as being lost or trapped, a crime, a fire, or a sickness). For example, because a crash was detected, options 812b1-812b4 for describing the emergency are related to emergencies that may involve a crash.
In some embodiments, in response to detecting selection of option 812b5 (e.g., a tap on option 812b5 and/or other input selecting option 812b5), computer system 604b displays a message compose field and a keyboard that can be used to generate a custom message.
Report generation interface 812 includes skip question option 813. In some embodiments, in response to detecting selection of skip question option 813 (e.g., a tap on skip question option 813 and/or other input selecting skip question option 813), computer system 604b proceeds with the process of sending a communication via satellite without an option of set of option 812b being selected.
In response to detecting selection 825d of option 812b1 (e.g., corresponding to a response that the emergency is best described as a vehicle crash), computer system 604b displays second report generation interface 814, which includes prompt 814a and second set of options 814b for responding to prompt 814a, as shown in
In response to detecting selection 825f of option 814b2 (e.g., corresponding to a response that someone else needs help), computer system 604b continues the process of sending a communication via satellite. For example, in response to selection 825f of option 814b2, computer system 604b displays report summary interface 816, which includes a summary of a report that is generated based on a user's responses to the prompts in report generation interfaces 812 and 814 (e.g., based on selection 825d of option 812b1 and selection 825f of option 814b2). Report summary interface 816 includes notification 816a, location information 816b, response summary 816c, countdown 816d, send option 816e, and don't send option 816f. Notification 816a indicates that the information in report summary interface 816 will be sent to emergency services. Location information 816b indicates a location that will be included in the information sent to emergency services. Response summary 816c indicates emergency information based on the user's responses (e.g., selection 825d of option 812b1 and selection 825f of option 814b2) that will be included in the information sent to emergency services. Countdown 816d indicates an amount of time (e.g., number of seconds) until sending of the information in report summary interface 816 to emergency services will be automatically initiated (e.g., without further user input).
In response to detecting selection of don't send option 816f (e.g., a tap on don't send option 816f and/or other input selecting don't send option 816f), computer system 604b ceases display of report summary interface 816 without attempting to send the information in report summary interface 816 (e.g., computer system 604b displays information interface 810 shown in
In response to detecting selection 825g of send option 816e, or in response to a determination that countdown 816d has ended, computer system 604b attempts to send a message to emergency services via satellite that includes the information shown in report summary interface 816.
In some embodiments, when computer system 604b attempts to send the message, computer system 604b displays a user interface of a messaging application, such as, e.g., messaging interface 818 shown in
In
Connection element 820 includes connection status indicator 820a, alignment instructions 820b, message status 820c, and alignment element 820d. Connection status indicator 820a indicates a status of a connection between computer system 604b and a satellite. In
In response to detecting selection 825h of connection element 820, computer system 604b displays connection assistant interface 822 shown in
Connection assistant interface 822 includes alignment element 822a, connection status indicator 822b, and alignment instructions 822c. Alignment element 822a includes a graphical representation of a satellite, a graphical representation of computer system 604b, and a graphical representation of an alignment window in which computer system 604b is aligned with a satellite. The position of the representation of the satellite relative to the representation of computer system 604b provides an indication of the actual physical location of a satellite relative to computer system 604b. In
Turning to
In response to a determination that computer system 604b is connected to the satellite, computer system 604b sends message 818a and displays messaging interface 818 and connection element 820 as shown in
In
In some embodiments, computer system 604b displays connection assistant interface 822 prior to displaying interfaces for generating and/or sending a message (e.g., report generation interface 812, report generation interface 814, and/or report summary interface 816). For example, in some embodiments, computer system 604b displays connection assistant interface 822 in response to detecting selection 825a of satellite communication option 802 or in response to selection 825c of report emergency option 810h. In some embodiments, computer system 604b displays interfaces for generating and/or sending a message (e.g., report generation interface 812, report generation interface 814, and/or report summary interface 816) in response to a determination that computer system 604b is connected to a satellite (e.g., after displaying connection assistant interface 822 shown in
Prompt 824 includes: crash detection indicator 824a (e.g., “Crash Detected”), which indicates that a crash has been detected; connection status indicator 824b (e.g., “No Connection”), which indicates that there is no connection; satellite communication indication 824c (e.g., “Your phone will attempt to text emergency services via satellite”), which indicates that computer system 604b will attempt to text emergency services via satellite; and instructions 824d (e.g., “Follow instructions on your phone”) which includes a prompt to follow instructions on computer system 604b.
As described below, method 900 provides an intuitive way for sending a communication using an alternative communication network in the event of a crash. The method reduces the cognitive burden on a user for sending a communication using an alternative communication network in the event of a crash, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to send a communication using an alternative communication network in the event of a crash faster and more efficiently conserves power and increases the time between battery charges.
The computer system obtains (902) (e.g., receives or detects) data indicating that a crash (e.g., a crash, accident, and/or impact involving a vehicle such as, for example, a car, truck, motorcycle, scooter, bus, bike, boat, train, plane, wheelchair, golf cart, or all-terrain vehicle (ATV)) has occurred. In some embodiments, obtaining the data indicating that a crash has occurred includes detecting a crash and/or determining that a crash has occurred (e.g., based on detected motion, parameters, and/or conditions). In some embodiments, detecting a crash includes detecting (e.g., via one or more sensors, such as a motion sensor, accelerometer, gyroscope, inertial measurement unit, biometric sensor, and/or microphone) motion (e.g., linear and/or angular velocity and/or linear and/or angular acceleration), sound, biometric parameters (e.g., blood pressure, blood oxygen level, pulse, and/or heart rate), and/or other parameters or conditions. In some embodiments, determining that a crash has occurred includes determining that detected parameters or conditions satisfy a set of crash criteria (e.g., a motion threshold, a motion profile, a velocity threshold, a velocity profile, an acceleration threshold, an acceleration profile, a blood pressure threshold, a blood oxygen threshold, a pulse threshold, a heart rate threshold, a sound profile, a sound amplitude threshold, a sound frequency, and/or a sound frequency range). In some embodiments, the computer system detects the crash (e.g., using sensors of the computer system; the crash is detected by the computer system). In some embodiments, the computer system determines that a crash has occurred. In some embodiments, one or more external devices (e.g., one or more remote sensors, servers, and/or computer systems) that are not part of the computer system (e.g., one or more remote devices) detect a crash and/or determine that a crash has occurred. In some embodiments, one or more external devices that detect a crash and/or determine that a crash has occurred send data indicating that a crash has occurred to the computer system and/or to a remote server. In some embodiments, obtaining data indicating that a crash has occurred includes receiving data indicating that a crash has occurred (e.g., from a remote server and/or from one or more remote devices that detected and/or determined that a crash has occurred). In some embodiments, the computer system is not capable of detecting a crash and/or determining that a crash has occurred. In some embodiments, the computer system is in communication (e.g., wired communication, wireless communication, Bluetooth communication, near-field communication, and/or Wi-Fi communication) with an external computer system (e.g., a smartphone, a smartwatch, a tablet computer, one or more sensors of a vehicle, and/or a computer system of a vehicle) that is capable of detecting a crash and/or determining that a crash has occurred. In some embodiments, the computer system obtains (e.g., receives or retrieves) data indicating that a crash has occurred from the external computer system.
In response (904) to obtaining the data indicating that a crash has occurred: in accordance with a determination that a terrestrial wireless communication network (e.g., a cellular network) is not reachable by the computer system (e.g., a terrestrial wireless communication network is not available to the computer system, the computer system is not in communication with a terrestrial wireless communication network, the computer system is not connected or is unable to connect to a terrestrial wireless communication network, the computer system is not receiving a signal from a terrestrial wireless communication network that satisfies strength and/or consistency criteria for performing communication, and/or there is no terrestrial wireless communication network via which the computer system can currently perform communication either because there is no terrestrial wireless communication network with which the computer system can connect or via which the computer system is authorized to communicate), the computer system displays (906), via the display generation component, a non-terrestrial wireless communication option (e.g., 802, a selectable option, an icon, an affordance, a button, and/or a user-interactive graphical user interface object) that, when selected via the one or more input devices, initiates a process (e.g., the process described in
In some embodiments, communicating via a non-terrestrial wireless communication network includes a phone call, text message, email, audio message, video message, and/or video conference. In some embodiments, the communication is a live or real-time (e.g., full duplex real-time) communication. In some embodiments, the terrestrial wireless communication network is a cellular network associated with the computer system (e.g., provided by a cellular service provider associated with the computer system and/or a user associated with the computer system) or another cellular network (e.g., provided by another cellular service provider). In some embodiments, for a call to a designated entity (e.g., a call to an emergency service or emergency contact), the computer system can use a network provided by a network provider other than a provider associated with the computer system. In some embodiments, in response to obtaining the data indicating that a crash has occurred and in accordance with a determination that a terrestrial wireless communication network is reachable by the computer system, the computer system displays a call option (e.g., 626c) that, when selected, initiates a process to call a predetermined number via terrestrial wireless communication, without displaying the non-terrestrial wireless communication option. In some embodiments, the call option includes a selectable call option, an icon, a button, an affordance, and/or a user-interactive graphical user interface object. In some embodiments, the computer system initiates display of the call option in response to obtaining the data indicating that a crash has occurred and in accordance with a determination that a terrestrial wireless communication network is reachable by the computer system (e.g., the call option is not provided, is not displayed, and/or is not available prior to obtaining the data indicating that a crash has occurred). In some embodiments, the call option includes (e.g., is) a graphical object that moves (e.g., slides) in accordance with movement of an input (e.g., a swipe or touch and drag input). In some embodiments, selection of the call option requires moving (e.g., on a display) the graphical object by a predetermined amount and/or to a predetermined location (e.g., from a first position, such a first location and/or first orientation, to a second position, such as a predefined location and/or a predefined orientation). In some embodiments, selection of the call option requires moving the graphical object from a first position (such as a first side, left side, top side, or upper side) on a predefined region or path to a second position (such as an opposite side, right side, bottom side, or lower side) of the predefined region or path. In some embodiments, in response to detecting selection of the call option, the computer system initiates a call to the predetermined number immediately (e.g., without a predetermined delay and/or countdown) and/or automatically without requiring further input (e.g., without requiring confirmation). In some embodiments, in response to detecting selection of the call option, the computer system initiates a call to the predetermined number and displays a call user interface (e.g., without displaying an intermediate or intervening user interface).
In some embodiments, in response to obtaining the data indicating that a crash has occurred, and before displaying the non-terrestrial wireless communication option, the computer system attempts to initiate a call (e.g., as described in
In some embodiments, after initiating display of the non-terrestrial wireless communication option: in accordance with a determination that a threshold amount of time has elapsed without detecting selection of the non-terrestrial wireless communication option and that the non-terrestrial wireless communication network is reachable by the computer system, the computer system sends (e.g., the computer system automatically sends, without detecting user input), via the non-terrestrial wireless communication network, a communication (e.g., a text and/or audio communication) to the designated entity (e.g., as described with reference to
In some embodiments, after initiating display of the non-terrestrial wireless communication option: in accordance with a determination that a threshold amount of time has elapsed without detecting selection of the non-terrestrial wireless communication option and that the non-terrestrial wireless communication network is not reachable by the computer system, the computer system displays an option (e.g., 626c) that, when selected, causes the computer system to attempt (e.g., re-attempt) to initiate a call to the designated entity. In some embodiments, after initiating display of the non-terrestrial wireless communication option: in accordance with a determination that a threshold amount of time has elapsed without detecting selection of the non-terrestrial wireless communication option and that the non-terrestrial wireless communication network is not reachable by the computer system, the computer system displays an indication that the designated entity has not been contacted (e.g., a communication has not been sent to the designated entity). Displaying an option to initiate a call to a designated entity in accordance with a determination that a threshold amount of time has elapsed without detecting selection of the non-terrestrial wireless communication option enables the computer system to automatically call the designated entity without requiring user input after a crash, which reduces the number of inputs needed to perform an operation and performs an operation when a set of conditions has been met without requiring further user input.
In some embodiments, in accordance with a determination that a terrestrial wireless communication network (e.g., a cellular network) is not reachable by the computer system, the computer system causes display of (e.g., on the computer system and/or on an external computer system) an indication (e.g., 824b) that a terrestrial wireless communication network is not reachable by the computer system. In some embodiments, in response to obtaining the data indicating that a crash has occurred and in accordance with a determination that a terrestrial wireless communication network is not reachable (e.g., by the computer system or an external computer system in communication with the computer system), the computer system indicates that a crash has been detected, indicates that the external computer system will attempt to send a communication to a designated entity, and/or provides a prompt for a user to use the external computer system to communicate with the designated entity via a non-terrestrial wireless communication network. Displaying an indication that a terrestrial wireless communication network is not reachable by the computer system in accordance with a determination that a terrestrial wireless communication network is not reachable by the computer system informs the user that the terrestrial wireless communication network is not reachable and enables the user to use the computer system more efficiently by not attempting to perform communication via the terrestrial wireless communication network when it is not reachable, which provides improved feedback to the user, reduces the number of inputs needed to perform an operation, and performs an operation when a set of conditions has been met without requiring further user input.
In some embodiments, while displaying the non-terrestrial wireless communication option (e.g., 802), the computer system detects an input (e.g., 825a) corresponding to selection of the non-terrestrial wireless communication option; and in response to detecting the input corresponding to selection of the non-terrestrial wireless communication option (and, optionally, in accordance with a determination that the computer system is connected to the non-terrestrial wireless communication network), the computer system sends (e.g., the computer system automatically sends, without detecting user input), via the non-terrestrial wireless communication network, a communication (e.g., a text and/or audio communication) to the designated entity, wherein the communication includes information related to the crash (e.g., location of the crash, time of the crash, that the crash occurred, and/or people involved in the crash). Sending a communication to a designated entity with information related to the crash in response to detecting selection of the non-terrestrial wireless communication option enables the user to quickly and efficiently communicate after a crash when a terrestrial wireless communication network is not reachable, which reduces the number of inputs needed to perform an operation and saves battery life.
In some embodiments, while displaying the non-terrestrial wireless communication option (e.g., 802), the computer system detects an input (e.g., 825a) corresponding to selection of the non-terrestrial wireless communication option; in response to detecting the input corresponding to selection of the non-terrestrial wireless communication option (and, optionally, in accordance with a determination that the computer system is connected to the non-terrestrial wireless communication network), the computer system displays a set of selectable message-content options (e.g., 812b and/or 814b); the computer system detects one or more user inputs (e.g., 825d and/or 825f) that correspond to selection of one or more message-content options of the set of selectable content options; and after detecting the one or more inputs (e.g., in response to a request to send a communication via the non-terrestrial wireless communication network), the computer system sends a communication via the non-terrestrial wireless communication network that includes content corresponding to the selected one or more message-content options. Displaying a set of selectable options for generating a communication provides a quick and efficient method for a user to create a message after a crash and enables the computer system to create a low-bandwidth communication that requires less bandwidth and/or energy to send, which provides improved feedback to the user, reduces the number of inputs needed to perform an operation, and saves battery life.
In some embodiments, any of the selections, requests, and/or inputs described herein (e.g., selections 625a-625u and/or selections 825a-825k) is or includes a touch input (e.g., a tap gesture and/or a swipe gesture). In some embodiments, any of the selections, requests, and/or inputs described herein (e.g., selections 625a-625u and/or selections 825a-825k) is or includes a voice input (e.g., a voice command to select a user interface element or to activate a feature or perform a function, such as a feature or function associated with a user interface element). In some embodiments, any of the selections, requests, and/or inputs described herein (e.g., selections 625a-625u and/or selections 825a-825k) is or includes an gesture (e.g., an air gesture to select a user interface element or to activate a feature or perform a function, such as a feature or function associated with a user interface element). In some embodiments, any of the selections, requests, and/or inputs described herein (e.g., selections 625a-625u and/or selections 825a-825k) is or includes activation (e.g., a press, a rotation, and/or a movement) of a hardware device (e.g., a button, a rotatable input mechanism, a rotatable and depressible input mechanism, a mouse button, a button of a remote control, and/or a joystick). In some embodiments, any of the user interface elements described as being selected herein (e.g., an icon, affordance, button, and/or selectable option) is selected by activating a hardware device while the user interface element is in focus (e.g., highlighted, bolded, outlined, visually distinguished from other user interface elements, and/or located at or near a cursor).
Note that details of the processes described above with respect to method 900 (e.g.,
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery to users of crash detection data or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, social network IDs, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.
The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user's general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.
The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of crash detection, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.
Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, crash detection data can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the crash detection function, or publicly available information.
This application claims priority to U.S. Provisional Application No. 63/404,155, entitled “CRASH DETECTION USER INTERFACE,” filed Sep. 6, 2022, and also relates to U.S. Provisional Application No. 63/400,732, entitled “METHODS AND INTERFACES FOR INITIATING COMMUNICATIONS,” filed Aug. 24, 2022, the contents of which are hereby incorporated by reference in their entirety.
| Number | Date | Country | |
|---|---|---|---|
| 63404155 | Sep 2022 | US |
