EP4584770A2 - Interface utilisateur de détection d'accident - Google Patents

Interface utilisateur de détection d'accident

Info

Publication number
EP4584770A2
EP4584770A2 EP23782659.9A EP23782659A EP4584770A2 EP 4584770 A2 EP4584770 A2 EP 4584770A2 EP 23782659 A EP23782659 A EP 23782659A EP 4584770 A2 EP4584770 A2 EP 4584770A2
Authority
EP
European Patent Office
Prior art keywords
crash
computer system
option
call
wireless communication
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP23782659.9A
Other languages
German (de)
English (en)
Inventor
Christopher D. LAURITZEN
Pablo F. Caro
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US18/241,747 external-priority patent/US20240080389A1/en
Application filed by Apple Inc filed Critical Apple Inc
Publication of EP4584770A2 publication Critical patent/EP4584770A2/fr
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
    • G08B25/01—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems characterised by the transmission medium
    • G08B25/016—Personal emergency signalling and security systems
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/01—Detecting movement of traffic to be counted or controlled
    • G08G1/0104—Measuring and analyzing of parameters relative to traffic conditions
    • G08G1/0108—Measuring and analyzing of parameters relative to traffic conditions based on the source of data
    • G08G1/0112—Measuring and analyzing of parameters relative to traffic conditions based on the source of data from the vehicle, e.g. floating car data [FCD]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72418—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality for supporting emergency services
    • H04M1/72421—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality for supporting emergency services with automatic activation of emergency service functions, e.g. upon sensing an alarm
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72454—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to context-related or environment-related conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B21/00—Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
    • G08B21/02—Alarms for ensuring the safety of persons
    • G08B21/04—Alarms for ensuring the safety of persons responsive to non-activity, e.g. of elderly persons
    • G08B21/0407—Alarms for ensuring the safety of persons responsive to non-activity, e.g. of elderly persons based on behaviour analysis
    • G08B21/043—Alarms for ensuring the safety of persons responsive to non-activity, e.g. of elderly persons based on behaviour analysis detecting an emergency event, e.g. a fall
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B21/00—Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
    • G08B21/02—Alarms for ensuring the safety of persons
    • G08B21/04—Alarms for ensuring the safety of persons responsive to non-activity, e.g. of elderly persons
    • G08B21/0438—Sensor means for detecting
    • G08B21/0446—Sensor means for detecting worn on the body to detect changes of posture, e.g. a fall, inclination, acceleration, gait
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H04M1/724098—Interfacing with an on-board device of a vehicle
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H04M1/72433—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for voice messaging, e.g. dictaphones

Definitions

  • the present disclosure relates generally to computer user interfaces, and more specifically to techniques for initiating communication in the event of a crash.
  • a computer system configured to communicate with a display generation component and one or more input devices.
  • 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.
  • a 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 nonterrestrial 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.
  • a 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 nonterrestrial 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.
  • a 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 nonterrestrial 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.
  • FIG. 1 A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.
  • FIG. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.
  • Optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors.
  • Optical sensor 164 receives light from the environment, projected through one or more lenses, and converts the light to data representing an image.
  • imaging module 143 also called a camera module
  • optical sensor 164 optionally captures still images or video.
  • an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition.
  • an optical sensor is located on the front of the device so that the user’s image is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display.
  • the position of optical sensor 164 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 164 is used along with the touch screen display for both video conferencing and still and/or video image acquisition.
  • Device 100 optionally also includes one or more depth camera sensors 175.
  • FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I/O subsystem 106.
  • Depth camera sensor 175 receives data from the environment to create a three dimensional model of an object (e.g., a face) within a scene from a viewpoint (e.g., a depth camera sensor).
  • a viewpoint e.g., a depth camera sensor
  • depth camera sensor 175 in conjunction with imaging module 143 (also called a camera module), depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by the imaging module 143.
  • Device 100 optionally also includes one or more proximity sensors 166.
  • FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.
  • proximity sensor 166 is, optionally, coupled to input controller 160 in VO subsystem 106.
  • Proximity sensor 166 optionally performs as described in U.S. Patent Application Nos.
  • the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user’s ear (e.g., when the user is making a phone call).
  • Device 100 optionally also includes one or more tactile output generators 167.
  • FIG. 1 A shows a tactile output generator coupled to haptic feedback controller 161 in I/O subsystem 106.
  • Tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device).
  • Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that are capable of being sensed by a user of device 100.
  • At least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile output by moving the touch- sensitive surface vertically (e.g., in/out of a surface of device 100) or laterally (e.g., back and forth in the same plane as a surface of device 100).
  • at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.
  • Device 100 optionally also includes one or more accelerometers 168.
  • FIG. 1 A shows accelerometer 168 coupled to peripherals interface 118.
  • accelerometer 168 is, optionally, coupled to an input controller 160 in I/O subsystem 106.
  • Accelerometer 168 optionally performs as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety.
  • Device/global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including information obtained from the device’s various sensors and input control devices 116; and location information concerning the device’s location and/or attitude.
  • Operating system 126 e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks
  • 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.
  • 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).
  • 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.
  • 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).
  • a gesture is, optionally, detected by detecting a particular contact pattern.
  • 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).
  • 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.
  • 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.
  • GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone module 138 for use in locationbased dialing; to camera module 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 e.g., to telephone module 138 for use in locationbased dialing; to camera module 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).
  • Widget modules 149 which optionally include one or more of: weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;
  • Widget creator module 150 for making user-created widgets 149-6;
  • 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.
  • 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.
  • the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • 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).
  • device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
  • 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.
  • maps e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data
  • 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.
  • instant messaging module 141 rather than e-mail client module 140, is used to send a link to a particular online video.
  • 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.
  • 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.
  • 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.
  • a “menu button” is implemented using a touchpad.
  • the menu button is a physical push button or other physical input control device instead of a touchpad.
  • 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.
  • 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).
  • 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.
  • FIG. 1 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 subevents 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.
  • an event recognizer e.g., event recognizer 180.
  • event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173.
  • event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
  • 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.
  • a respective application view 191 includes a plurality of event recognizers 180.
  • 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.
  • 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.
  • 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.
  • the event information also includes additional information, such as location of the sub-event.
  • the event information optionally also includes speed and direction of the sub-event.
  • 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.
  • the definition for event 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.
  • the definition for event 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).
  • the event also includes information for one or more associated event handlers 190.
  • 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.
  • metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178.
  • 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.
  • 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.
  • 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.
  • FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments.
  • the touch screen optionally displays one or more graphics within user interface (UI) 200.
  • UI user interface
  • a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure).
  • selection of one or more graphics occurs when the user breaks contact with the one or more graphics.
  • the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100.
  • inadvertent contact with a graphic does not select the graphic.
  • a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.
  • Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204.
  • menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100.
  • the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
  • 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.
  • 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.
  • Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes nonvolatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1 A), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100.
  • memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1 A) optionally does not store these modules.
  • FIG. 3 Each of the above-identified elements in FIG. 3 is, optionally, stored in one or more of the previously mentioned memory devices.
  • Each of the above-identified modules corresponds to a set of instructions for performing a function described above.
  • memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.
  • FIG. 4A illustrates an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device 300.
  • user interface 400 includes the following elements, or a subset or superset thereof:
  • Tray 408 with icons for frequently used applications such as: o Icon 416 for telephone module 138, labeled “Phone,” which optionally includes an indicator 414 of the number of missed calls or voicemail messages; o Icon 418 for e-mail client module 140, labeled “Mail,” which optionally includes an indicator 410 of the number of unread e-mails; o Icon 420 for browser module 147, labeled “Browser;” and o Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled “iPod;” and
  • Icons for other applications such as: o Icon 424 for IM module 141, labeled “Messages;” o Icon 426 for calendar module 148, labeled “Calendar;” o Icon 428 for image management module 144, labeled “Photos;” o Icon 430 for camera module 143, labeled “Camera;” o Icon 432 for online video module 155, labeled “Online Video;” o Icon 434 for stocks widget 149-2, labeled “Stocks;” o Icon 436 for map module 154, labeled “Maps;” o Icon 438 for weather widget 149-1, labeled “Weather;” o Icon 440 for alarm clock widget 149-4, labeled “Clock;” o Icon 442 for workout support module 142, labeled “Workout Support;” o Icon 444 for notes module 153, labeled “Notes;” and o Icon 446 for notes module
  • icon labels illustrated in FIG. 4A are merely exemplary.
  • icon 422 for video and music player module 152 is labeled “Music” or “Music Player.”
  • Other labels are, optionally, used for various application icons.
  • a label for a respective application icon includes a name of an application corresponding to the respective application icon.
  • a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.
  • FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3) that is separate from the display 450 (e.g., touch screen display 112).
  • Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch- sensitive surface 451 and/or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.
  • one or more contact intensity sensors e.g., one or more of sensors 359
  • tactile output generators 357 for generating tactile outputs for a user of device 300.
  • the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B.
  • the touch-sensitive surface e.g., 451 in FIG. 4B
  • the touch-sensitive surface has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450).
  • the device detects contacts (e.g., 460 and 462 in FIG.
  • finger inputs e.g., finger contacts, finger tap gestures, finger swipe gestures
  • one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input).
  • 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).
  • 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).
  • 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).
  • multiple user inputs it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
  • FIG. 5A illustrates exemplary personal electronic device 500.
  • Device 500 includes body 502.
  • device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1 A-4B).
  • device 500 has touch-sensitive display screen 504, hereafter touch screen 504.
  • touch screen 504 optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied.
  • the one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data that represents the intensity of touches.
  • the user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device 500.
  • 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 November 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
  • 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.
  • 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.
  • FIG. 5B depicts exemplary personal electronic device 500.
  • device 500 can include some or all of the components described with respect to FIGS. 1 A, IB, and 3.
  • Device 500 has bus 512 that operatively couples VO section 514 with one or more computer processors 516 and memory 518.
  • I/O section 514 can be connected to display 504, which can have touch-sensitive component 522 and, optionally, intensity sensor 524 (e.g., contact intensity sensor).
  • VO section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques.
  • Device 500 can include input mechanisms 506 and/or 508.
  • Input mechanism 506 is, optionally, a rotatable input device or a depressible and rotatable input device, for example.
  • Input mechanism 508 is, optionally, a button, in some examples. [0142]
  • 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.
  • the non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like.
  • Personal electronic device 500 is not limited to the components and configuration of FIG. 5B, but can include other or additional components in multiple configurations.
  • 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 (FIGS. 1 A, 3, and 5A-5B).
  • an image e.g., icon
  • a button e.g., button
  • text e.g., hyperlink
  • the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting.
  • 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 FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input.
  • a touch-sensitive surface e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B
  • a particular user interface element e.g., a button, window, slider, or other user interface element
  • focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface.
  • the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user’s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact).
  • a focus selector e.g., a cursor, a contact, or a selection box
  • a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).
  • 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 predefined time period e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds
  • 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.
  • 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).
  • 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.
  • the computer system is in a locked state or an unlocked state.
  • 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.
  • 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.
  • FIGS. 6A-6AA illustrate exemplary user interfaces for initiating communication using a computer system in the event of a crash, in accordance with some embodiments.
  • the user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 7.
  • computer system 604a is displaying user interface 608 on display 606a (e.g., a touch-sensitive display), and computer system 604b is displaying user interface 610 on display 606b (e.g., a touch- sensitive display).
  • User interface 608 e.g., a home screen or application springboard
  • User interface 610 includes application icons that can be selected (e.g., tapped and/or otherwise selected) to open corresponding applications on computer system 604b.
  • FIG. 6A illustrates computer system 604a and computer system 604b displaying user interface 608 and user interface 610, respectively, at the time of the crash
  • the techniques described herein are applied when computer system 604a and/or computer system 604b are displaying other user interfaces at the time of the crash, such as, e.g., a clock face user interface, a wake user interface (e.g., a user interface displayed when a computer system comes out of a disabled or low-power state), a lock user interface, and/or a user interface of an application (e.g., an email application, web browsing application, maps application, navigation application, media playback application, or settings application).
  • the techniques described herein are applied when display 606a and/or display 606b are powered off, deactivated, de-energized, in a sleep state, in a dimmed state, and/or in a low-power state.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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).
  • 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).
  • computer system 604a and/or computer system 604b obtains an indication that a crash has been detected.
  • computer system 604a detects an indication (e.g., motion and/or sound) of the crash and/or determines that the crash has occurred.
  • computer system 604a sends data to computer system 604b that indicates that the crash has occurred.
  • computer system 604b detects an indication (e.g., motion and/or sound) of the crash and/or determines that the crash has occurred.
  • computer system 604b sends data to computer system 604a that indicates that the crash has occurred.
  • FIGS. 6B-6H illustrate exemplary user interfaces displayed by computer system 604a after a crash is detected, in accordance with some embodiments.
  • computer system 604a displays crash detection interface 612 as shown in FIG. 6B.
  • Crash detection interface 612 includes emergency interface indicator 612a (e.g., “SOS”), crash detection indicator 612b, communication option 612c, and confirmation option 612d.
  • Crash detection indicator 612b includes an indication, such as text (e.g., “It looks like you’ve been in a crash”), a graphic, animation, color, and/or font, that a crash has occurred.
  • computer system 604a ceases display of crash detection interface 612 (e.g., computer system 604a returns to user interface 608).
  • computer system 604a displays communication alert 612e, countdown 612f, and cancel option 612g, as shown in FIG. 6C.
  • Communication alert 612e indicates that a call to emergency services has been or will be initiated
  • countdown 612f indicates an amount of time (e.g., number of seconds) until the call to emergency services will be placed.
  • computer system 604a In accordance with (or, optionally, in response to) a determination that a time threshold is satisfied without detecting an input, computer system 604a outputs a non-visual indication that a call to emergency services has been or will be initiated. For example, in FIG. 6C, computer system 604a outputs haptic 614 and/or audio output 616 (e.g., “Making call to emergency services”).
  • haptic 614 and/or audio output 616 e.g., “Making call to emergency services”.
  • 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.
  • computer system 604a in response to detecting selection 625c of cancel option 612g, 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 FIG. 6B or FIG. 6H (e.g., displays crash detection indicator 612b, crash detection indicator 612p, and/or communication option 612c) or user interface 608.
  • crash detection interface 612 as shown in FIG. 6B or FIG. 6H (e.g., displays crash detection indicator 612b, crash detection indicator 612p, and/or communication option 612c) or user interface 608.
  • computer system 604a 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.
  • an element e.g., the SOS circle in 612c
  • 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).
  • selection 625a includes a contact on display 606a that moves from left to right on communication option 612c sufficient to select communication option 612c.
  • initiating the call to emergency services includes displaying call status indicator 612h, call recipient indicator 612i, end call option 612j, and call menu option 612k (e.g., displaying a phone call interface or an interface of a phone application).
  • Call status indicator 612h includes an indication, such as text (e.g., “Calling”, “Attempting to connect”, or “Connecting”), a graphic, animation, color, and/or font, that indicates a current status of the call.
  • Call recipient indicator 612i includes an indication of the recipient of the call, such as text (e.g., “Emergency Services”) and/or a graphical representation (e.g., an image of the recipient, an icon associated with the recipient, and/or initials of the recipient).
  • end call option 612j e.g., a tap on end call option 612j and/or other input selecting end call option 612j
  • computer system 604a in response to detecting selection of end call option 612j (e.g., a tap on end call option 612j and/or other input selecting end call option 612j)
  • computer system 604a ends the call or stops attempting to initiate the call.
  • Call menu option 612k when selected, causes computer system 604a to display selectable options that, when selected, perform corresponding functions related to a call (e.g., mute, display keypad, enable/disable speaker, and/or display contacts).
  • computer system 604a 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 FIG. 6E. [0164] In some embodiments, as shown in FIG. 6E, when the call to emergency services is established, computer system 604a plays message 618 on the call to emergency services. In some embodiments, message 618 is based on circumstances of the crash.
  • message 618 can indicate that a crash has occurred and include information about the crash, such as, e.g., one or more people who are involved in the crash and/or a location of the crash (e.g., “A crash involving John has been detected at Parkway Drive”).
  • computer system 604a plays message 618 only if the call to emergency services was initiated automatically (e.g., without detecting user input such as selection of communication option 612c).
  • Playing message 618 when the call is initiated automatically enables computer system 604a to provide information about the crash to emergency services in the event that a user of computer system 604a is unable to provide information (e.g., is injured and/or unable to locate computer system 604a) and/or does not know that the call has been placed.
  • stop message option 6121 when computer system 604a plays message 618, computer system 604a displays stop message option 6121, as shown in FIG. 6E.
  • displaying stop message option 6121 includes ceasing display of (e.g., removing) end call option 612j and/or call menu option 612k (e.g., replacing end call option 612j and/or call menu option 612k with stop message option 6121).
  • computer system 604a stops playing message 618. In some embodiments, in response to detecting selection 625d of stop message option 6121, computer system 604a ceases display of stop message option 6121 and, optionally, displays (e.g., re-displays) end call option 612j and/or call menu option 612k, as shown in FIG. 6F.
  • 604a initiates a process for ending the call with emergency services.
  • computer system 604a in response to detecting selection 625f of end call option 612j , ends the call with emergency services without detecting further input.
  • computer system 604a in response to detecting selection 625f of end call option 612j, 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.
  • prompt 612m e.g., “End Call?
  • 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.
  • computer system 604a 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 FIG. 6F. In response to detecting selection 625f of confirm option 612n, computer system 604a ends the call with emergency services.
  • 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 In response to detecting selection of 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 FIG. 6F.
  • computer system 604a ends the call with emergency services.
  • computer system 604a displays an indication that a crash was detected and, optionally, an indication of a device that detected the crash and/or an indication of when the crash was detected. For example, as shown in FIG. 6H, after ending the call with emergency services, computer system 604a displays crash detection indicator 612p (e.g., “Phone detected a crash 1 minute ago”), which indicates that a crash was detected, that the crash was detected by computer system 604b, and that the crash was detected one minute ago.
  • crash detection indicator 612p e.g., “Phone detected a crash 1 minute ago
  • computer system 604a after ending the call with emergency services (e.g., in response to selection 625e in FIG. 6F or selection 625f in FIG. 6G), provides an option to initiate (e.g., re-initiate) communication with emergency services and/or an option to provide information a user associated with computer system 604a that can be relevant to a medical condition of the user. For example, as shown in FIG. 6H, after ending the call with emergency services, computer system 604a displays communication option 612c and medical ID option 612q.
  • computer system 604a In response to detecting selection of communication option 612c (e.g., a tap or swipe on communication option 612c and/or other input selecting communication option 612c), computer system 604a attempts to initiate (e.g., re-initiate) a call to emergency services. In response to detecting selection of (e.g., a tap and/or swipe on) medical ID option 612q, computer system 604a 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).
  • 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.
  • FIGS. 6I-6L illustrate exemplary user interfaces for enabling and/or disabling a crash detection feature, such as the feature described with reference to FIGS. 6A-6H.
  • computer system 604a displays user interface 608.
  • computer system 604a displays settings interface 620 as shown in FIG. 6J.
  • Settings interface 620 includes a menu of items associated with various features, functions, and/or applications of computer system 604a, including emergency settings option 620a.
  • computer system 604a displays emergency settings interface 622 as shown in FIG. 6K.
  • Emergency settings interface 622 includes options associated with various emergency features of computer system 604a, including crash detection settings option 622a.
  • the options included in emergency settings interface 622 include an indication (e.g., text and/or a graphical representation) of the emergency feature associated with the option (e.g., “Hold side button” to call emergency services or to display an option to call emergency services, “Fall Detection”, and “Crash Detection) and an indication of a status of the feature (e.g., enabled or disabled).
  • an indication e.g., text and/or a graphical representation
  • the emergency feature associated with the option e.g., “Hold side button” to call emergency services or to display an option to call emergency services, “Fall Detection”, and “Crash Detection
  • an indication of a status of the feature e.g., enabled or disabled.
  • crash detection settings option 622a includes the text “Crash Detection” to indicate the feature associated with crash detection settings option 622a and the text “Disabled” to indicate that the crash detection feature is disabled (e.g., turned off and/or inactive).
  • computer system 604a 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.
  • 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 FIGS. 6B-6H after a crash is detected, such as making a call to emergency services (e.g., in response to obtaining an indication that a crash has occurred or been detected). For example, as shown in FIG.
  • computer system 604a since the crash detection feature is in a disabled (or off) state, computer system 604a enables (or turns on) the crash detection feature in response to detecting selection of crash detection state option 624a and, optionally, changes the appearance of crash detection state option 624a (e.g., moves the circle to the right side of crash detection state option 624a and/or changes the text “OFF” to “ON”).
  • Crash detection interface 626 includes response prompt 626a, crash detection indicator 626b, communication option 626c, medical ID option 626e, and close option 626d.
  • Crash detection indicator 626b includes an indication, such as text (e.g., “It looks like you’ve been in a crash”), a graphic, animation, color, and/or font, that a crash has occurred (e.g., similar or the same as crash detection indicator 612b).
  • computer system 604b 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).
  • 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.
  • 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.
  • computer system 604b displays emergency communication indicator 626f (e.g., “Emergency SOS”), communication alert 626h, and countdown 626g, as shown in FIG. 6N.
  • Emergency communication indicator 626f e.g., “Emergency SOS”
  • communication alert 626h indicates that a call to emergency services has been or will be initiated (e.g., when countdown 626g ends), and countdown 626g indicates an amount of time (e.g., number of seconds) until the call to emergency services will be placed.
  • computer system 604b initiates (or attempts to initiate) a call to emergency services.
  • 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 FIG. 6M or FIG. 6N).
  • initiating the call to emergency services includes displaying call status indicator 626j, call recipient indicator 626i, end call option 6261, and call management options 626k (e.g., displaying a call user interface or a user interface of a phone application).
  • Playing message 618 when the call is initiated automatically enables computer system 604b to provide information about the crash to emergency services in the event that a user of computer system 604b is unable to provide information (e.g., is injured and/or unable to locate computer system 604b) and/or does not know that the call has been placed.
  • stop message option 626n when computer system 604b plays message 618, computer system 604b displays stop message option 626n, as shown in FIG. 6P.
  • displaying stop message option 626n includes ceasing display of (e.g., removing) call management options 626k (e.g., replacing call management options 626k with stop message option 626n).
  • computer system 604b displays an indication that a crash was detected and, optionally, an indication of a device that detected the crash and/or an indication of when the crash was detected. For example, as shown in FIG. 6Q, after ending the call with emergency services, computer system 604b displays context indicator 626o (e.g., “Phone detected a crash 1 minute ago”), which indicates that a crash was detected, that the crash was detected by computer system 604b, and that the crash was detected one minute ago.
  • context indicator 626o e.g., “Phone detected a crash 1 minute ago”
  • computer system 604b In response to detecting selection of communication option 626c (e.g., a tap and/or swipe on communication option 626c), computer system 604b attempts to initiate (e.g., re-initiate) a call to emergency services.
  • computer system 604b In response to detecting selection of medical ID option 626e (e.g., a tap and/or swipe on medical ID option 626e), computer system 604b displays information of a user associated with computer system 604b 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).
  • 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.
  • crash data sharing settings interface 632 includes application menu 632b, which includes a set (e.g., a list) of application options 632b 1, 632b2, and 632b3 corresponding to respective applications with which computer system 604b can share crash data.
  • the check mark in application option 632b 1 indicates that computer system 604b is configured to share crash data with an application called “Buddy System” if a crash is detected.
  • computer system 604b in response to selection of an application option (e.g., a tap on an application option or other input selecting an application option), selects the corresponding application to share crash data with if a crash is detected. For example, in response to detecting selection of application option 632b2 (e.g., a tap on application option 632b2 and/or other input selecting application option 632b2), computer system 604b is configured to share crash data with an application named “Rapid System Response” and, optionally, visually indicates that application option 632b2 is selected (e.g., displays a check mark on the right side of application option 632b2). In some embodiments, computer system 604b is configured to (or is capable of) sharing crash data with only a single application. For example, in response to detecting selection of an application option other than a currently designated application option, computer system 604b de-selects the currently designated application option and designates the selected application option.
  • an application option e.g., a tap on an application option or other input
  • crash data sharing settings interface 632 does not display applications menu 632b (e.g., computer system 604b removes display of application menu 632b in response to the ability to share crash data with an application being disabled).
  • FIGS. 6V-6W illustrate exemplary user interfaces for granting or denying a request by an application to receive crash data from computer system 604b (e.g., a request for computer system 604b to share crash data with an application when a crash is detected).
  • computer system 604b displays application installation confirmation interface 634 corresponding to an application called Buddy System.
  • computer system 604b displays application installation confirmation interface 634 in response to a request (e.g., a user request or a system request) to install the corresponding application.
  • Application installation confirmation interface 634 includes application identifier 634a, install option 634b, and decline option 634c.
  • Application identifier 634a indicates the application that is being requested to be installed.
  • 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).
  • computer system 604b prompts the user to grant or deny the request to access crash data.
  • computer system 604b displays prompt 634d shown in FIG. 6W.
  • Prompt 634d includes description 634e, grant option 634f, and deny option 634g.
  • Description 634e describes what the user is being prompted to do.
  • computer system 604b designates the application being installed as the application with which crash data will be shared if a crash is detected (e.g., a de-selects a previously designated application).
  • Description 640a indicates that computer system 604a (e.g., watch) and computer system 604b (e.g., phone) can call emergency services, and device capability indicator 640c indicates that computer system 604a (e.g., watch) cannot detect all crashes.
  • computer system 604a e.g., watch
  • computer system 604b e.g., phone
  • device capability indicator 640c indicates that computer system 604a (e.g., watch) cannot detect all crashes.
  • computer system 604b displays crash detection interface 640 in response to detecting selection of enable option 638d, with call after crash status option 640b indicating that the capability to detect a crash and/or call emergency services after a crash is detected is disabled (e.g., call after crash status option 640b is in the off state).
  • 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 FIG. 6 A) has occurred (or, in some embodiments, that a crash has been detected).
  • 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).
  • 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.
  • 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 e.g., sound
  • biometric parameters e.g., blood pressure, blood oxygen level, pulse, and/or heart rate
  • 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).
  • 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.
  • the computer system detects the crash (e.g., using sensors of the computer system; the crash is detected by the computer system).
  • the computer system determines that a crash has occurred.
  • one or more external devices detect a crash and/or determine that a crash has occurred.
  • 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.
  • 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).
  • 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).
  • 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.
  • 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.
  • Displaing 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 occured because a user may be stressed and more prone to making mistakes.
  • the computer system 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.
  • the computer system provides the indication that a crash has been detected while concurrently displaying the call option.
  • the computer system 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.
  • the first threshold amount of time is, e.g., 5 seconds, 10 seconds, 15 seconds, 30 seconds, or one minute.
  • 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.
  • the computer system 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.
  • a second threshold e.g., non-zero
  • the second threshold amount of time is, e.g. 5 seconds, 10 seconds, 15 seconds, 30 seconds, or one minute).
  • the computer system automatically initiates a call to the predetermined number associated with the call option when the countdown expires.
  • the computer system 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).
  • 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).
  • 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.
  • 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.
  • the computer system 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 FIG. 6G).
  • the computer system sends the communication automatically (e.g., without user input) when a call to the predetermined number ends (e.g., in response to a determination that the call has ended).
  • the computer system 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.
  • 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.
  • 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).
  • 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 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 unconsious 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.
  • the computer system displays a second call option (e.g., 612c in FIG. 6H, 626c in FIG. 6Q, a selectable call option, an icon, a button, an affordance, and/or a user-interactive graphical user interface object) that, when selected, causes the computer system to initiate a process to call the predetermined number.
  • a second call option e.g., 612c in FIG. 6H, 626c in FIG. 6Q, a selectable call option, an icon, a button, an affordance, and/or a user-interactive graphical user interface object
  • the computer system causes display of an option to call the predetermined number 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).
  • the option to call the predetermined number is displayed by the computer system and the external computer system. Displaying an optino to call the predetermined number in response to a determination that a call to the predetermined number has ended enables the user to quickly and easily re-initiate communication with the predetermined number in case the initial call gets disconnected or ended accidentally, which reduces the number of inputs needed to perform an operation.
  • the computer system displays a medical ID option (e.g., 612q in FIG. 6H, 626e in FIG. 6Q, a selectable option, an icon, a button, an affordance, and/or a user-interactive graphical user interface object) that, when selected, causes the computer system to display information of a user who is associated with the computer system.
  • a medical ID option e.g., 612q in FIG. 6H, 626e in FIG. 6Q, a selectable option, an icon, a button, an affordance, and/or a user-interactive graphical user interface object
  • the information of the user includes the user’s name, the user’s age, the user’ s weight, the user’s height, a designated contact (e.g., a name of an emergency contact), and/or contact information (e.g., a phone number) of the designated contact.
  • the computer system causes display of the medical ID option 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).
  • the medical ID option is displayed by the computer system and the external computer system.
  • Displaying a medical ID option in response to a determination that a call to the predetermined number has ended enables the user of the computer system to quickly and easily show responders to the crash the user’s information or for the responders to access the user’s information if the user is unable to do so, which provides improved feedback to the user and reduces the number of inputs needed to perform an operation.
  • the computer system disables a voice assistant functionality on the computer system (e.g., a voice assistant functionality is disabled in FIGS. 6B-6H. FIGS. 6D-6H, FIGS. 6B-6G, FIGS. 6D-6G, FIGS. 6M-6Q, or FIGS. 6O-6Q).
  • the computer system disables the voice assistant functionality in response to obtaining the data indicating that a crash has occurred.
  • the computer system disables the voice assistant functionality in response to a determination that a call to the predetermined number has been initiated (e.g., either automatically or manually).
  • the computer system enables (or re-enables) the voice assistant functionality when the call to the predetermined number ends or when a user interface associated with the crash or an option to notify contact an emergency service is no longer displayed. Disabling a voice assistant functionality on the computer system after obtaining the data indicating that a crash has occurred prevents inadvertent and incorrect inputs to the voice assistant after a crash when there is high likelihood of confusion, noise, and other people that can interrupt the voice assistant functionally, which reduces the number of inputs needed to perform an operation and reduces mistakes.
  • the computer system 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.
  • 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
  • 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).
  • the computer system 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), 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.
  • 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.
  • an enable-crash-detection option e.g., 624a, 630a, 640b, a toggle button, a switch, an affordance, and/or a user interactive graphical object
  • a state e.g., enabled, disabled, on, or off
  • a capability e.g., of the computer system or an external computer system
  • the computer system 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, 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.
  • 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).
  • the computer system 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.
  • the enablecrash-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).
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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).
  • a user interface e.g., 638 and/or 640
  • 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
  • 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.
  • 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.
  • 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).
  • 624a controls the capability of computer system 604a, but not the capability of computer system 604b
  • 630a controls the capability of computer system 604b, but not the capability of computer system 604a
  • 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).
  • 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).
  • a first device e.g., the computer system
  • a second device e.g., an external 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.
  • the computer system after obtaining data indicating that a crash has occurred, provides (e.g., shares) data associated with the crash to an application (e.g., an application designated in 632b in FIG. 6T, a third-party application, an application other than an application that detected the crash, and/or an application provided and/or created by an entity other than an entity that created the computer system or an operating system on the computer system).
  • an application e.g., an application designated in 632b in FIG. 6T, a third-party application, an application other than an application that detected the crash, and/or an application provided and/or created by an entity other than an entity that created the computer system or an operating system on the computer system.
  • the data associated with the crash includes data indicating that a crash has occurred, a time of the crash, a location of the crash, and/or people involved in the crash.
  • the computer system in response to a request by an application (e.g., a third-party application) to be provided with data associated with a crash if a crash is determined to have occurred, displays an option to grant or deny the application access to data associated with the crash (e.g., to provide or not provide data associated with a crash if a crash is determined to have occurred).
  • the computer system provides data associated with a crash with an application (e.g., a third-party application) even if a capability of the computer system to display the call option in response to obtaining data indicating that a crash has occurred is disabled (e.g., a crash detection user interface is disabled).
  • the computer system provides an application (e.g., a third-party application) with data associated with crash if a crash is determined to have occurred if the computer system is a predetermined type of device (e.g., a smartphone).
  • an application e.g., a third-party application
  • the computer system is a predetermined type of device (e.g., a smartphone).
  • a computer system of a particular type can share crash detection data with a third-party application (e.g., a smartphone can share crash detection data with a third-party application, but a smartwatch that is in communication with the smartphone cannot share crash detection data with the third-party application).
  • Providing data associated with the crash to an application enables the computer system to automatically share data about the crash with an application that provides a functionality that a user desires after a crash so that the user does not have to perform additional inputs to provide the data to the application, which reduces the number of inputs needed to perform an operation.
  • 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).
  • 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.
  • 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.
  • a sharing option e.g., 632a, a toggle button, a switch, an affordance, and/or a user interactive graphical object
  • the computer system 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, 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.
  • 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.
  • method 900 optionally includes one or more of the characteristics of the various methods described above with reference to method 700. For brevity, these details are not repeated below.
  • FIGS. 8A-8N illustrate exemplary user interfaces for sending a communication using an alternative communication network in the event of a crash, in accordance with some embodiments.
  • the user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 9.
  • FIG. 8A illustrates computer system 604b described above with reference to, e.g., FIG. 6A.
  • computer system 604b displays crash detection interface 626 described above with reference to FIG. 6M.
  • computer system 604b displays crash detection interface 626 while attempting to initiate a call with emergency services after obtaining an indication that a crash has occurred.
  • computer system 604b attempts to initiate a call with emergency services and displays crash detecting interface 626 in response to detecting selection of communication option 626c (e.g., shown in FIG. 6M and FIG. 6N), which computer system 604b displays in response to obtaining an indication that a crash has occurred.
  • communication option 626c e.g., shown in FIG. 6M and FIG. 6N
  • computer system 604b attempts to initiate a call with emergency services and displays crash detecting interface 626 in response to obtaining an indication that a crash has occurred without detecting user input (e.g., in response to countdown 626g shown in FIG. 6N expiring).
  • computer system 604b is unable to connect to a terrestrial wireless communication network, such as, e.g., a cellular network or a Wi-Fi network.
  • a terrestrial wireless communication network such as, e.g., a cellular network or a Wi-Fi network.
  • computer system 604b may be in a remote location where a cellular network is not available.
  • computer system 604b displays network status indicator 605 with an appearance that indicates that no terrestrial wireless communication network is available.
  • network status indicator 605 includes cellular status indicator 605c (e.g., a horizontal broken line), which indicates that a cellular network is not available.
  • Emergency capability indicator 605d indicates that computer system 604b is capable of performing emergency communication even though a cellular network is not available.
  • emergency communication is limited to phone and/or text communication with a designated entity or number (e.g., emergency services and/or 911).
  • computer system 604b displays emergency capability indicator 605d with a first appearance (e.g., bold and/or not greyed out) if a cellular network other than a primary cellular network associated with computer system 604b is available for emergency communication, and displays emergency capability indicator 605d with a second appearance (e.g., dimmed and/or not greyed out) if no cellular network is available.
  • a first appearance e.g., bold and/or not greyed out
  • second appearance e.g., dimmed and/or not greyed out
  • 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 FIG. 8A has failed (e.g., due to the lack of cellular network availability), computer system 604b provides an option to initiate communication via satellite. For example, as shown in FIG. 8B, in response to a determination that there is no cellular connection (e.g., as indicated by call status indicator 626j), computer system 604b displays satellite communication option 802. In the embodiment illustrated in FIG.
  • computer system 604b moves end call option 6261 to the left on crash detection interface 626 and displays satellite communication option 802 to the right of end call option 6261. Displaying satellite communication option 802 provides a user with an alternative communication option after a crash has occurred if no cellular network is available.
  • computer system 604b in response to detecting selection 825a of satellite communication option 802, attempts to send a message to emergency services via satellite automatically (e.g., without further user input).
  • 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).
  • 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.
  • computer system 604b must be connected (e.g., via wireless communication) to a satellite in order to send a message via satellite.
  • computer system 604b 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 FIG. 8C.
  • crash detection interface 626 includes no cellular connection indication 804, message status indication 806, and show message option 808 (e.g., along with crash detection indicator 626b, communication option 626c, close option 626d, and medical ID option 626e described above with reference to FIGS. 6M, 6N, and 6Q).
  • No cellular connection indication 804 indicates (e.g., via text, such as “No cellular connection,” and/or a graphic) that computer system 604b does not have a cellular connection.
  • Message status indication 806 indicates (e.g., via text, such as “Emergency services have been notified via text,” and/or a graphic) that emergency services has been notified about the detected crash via a text message.
  • Show message option 808 provides the ability for the user to quickly and easily view the message that was sent to emergency services. For example, in response to detection selection 825b of show message option 808, computer system 604b displays the message that was sent to emergency services. In some embodiments, in response to detection selection 825b of show message option 808, computer system 604b displays a user interface (e.g., messaging interface 818) of a messaging application for sending, receiving, and/or displays messages between emergency services and computer system 604b (or a user associated with computer system 604b), as shown, e.g., in FIG. 8L.
  • a user interface e.g., messaging interface 818
  • computer system 604b 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.
  • 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 FIG. 8D.
  • computer system 604b in response to detecting selection 825a of satellite communication option 802, 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 FIGS. 8D-8G.
  • Information interface 810 includes information about generating a message to send via satellite, connecting to a satellite, and/or sending a message via satellite.
  • 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.
  • 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.
  • Content indicator 810g indicates that a location and medical information may be shared when a message is sent.
  • computer system 604b displays end option 811 that, when selected (e.g., via selection 825e in FIG. 8F or selection 825j in FIG. 8L), causes computer system 604b to end the process of sending a communication via satellite.
  • computer system 604b maintains display of end option 811 throughout the process of sending a communication via satellite (e.g., as shown in FIGS. 8D-8L).
  • computer system 604b continues the process of sending a communication via satellite.
  • 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.
  • first report generation interface 812 which includes prompt 812a and first set of options 812b for responding to prompt 812a, as shown in FIG. 8E.
  • First set of options 812b includes options 812b 1 -812b5 that correspond to respective responses to prompt 812a.
  • 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 812bl-812b4 for describing the emergency are related to emergencies that may involve a crash.
  • options 812bl-812b4 for describing the emergency are related to emergencies that may involve a crash.
  • computer system 604b in response to detecting selection of option 812b5 (e.g., a tap on option 812b5 and/or other input selecting option 812b5), displays a message compose field and a keyboard that can be used to generate a custom message.
  • option 812b5 e.g., a tap on option 812b5 and/or other input selecting option 812b5
  • Report generation interface 812 includes skip question option 813.
  • computer system 604b 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), proceeds with the process of sending a communication via satellite without an option of set of option 812b being selected.
  • second report generation interface 814 which includes prompt 814a and second set of options 814b for responding to prompt 814a, as shown in FIG. 8F.
  • Second set of options 814b includes options 814b 1 -814b 3 that correspond to respective responses to prompt 814a.
  • prompt 814a and second set of option 814b are based on which option is selected from first set of options 812b. For example, computer system 604b displays the particular prompt 814a and set of options 814b because option 812b 1 was selected.
  • computer system 604b displays a different prompt and/or different set of options from prompt 814a and second set of option 814b, respectively, shown in FIG. 8F in response to selection of a different option in first set of options 812b (e.g., in response to selection of option 812b2, option 812b3, or option 812b4).
  • computer system 604b 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 812b 1 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.
  • 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 812b 1 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).
  • computer system 604b 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 FIG. 8D or crash detection interface 626 shown in FIG. 8B).
  • 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 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.
  • Messaging interface 818 includes one or more messages between emergency services and a user associated with computer system 604b, including message 818a that includes the information in report summary interface 816.
  • Messaging interface 818 includes message compose field 818c, send option 818d, and keyboard 818d for composing and sending additional messages to emergency services.
  • message status indicator 818b indicates that message 818a has not been sent.
  • message 818a has not been sent because computer system 604b is not aligned with (and not connected to) a satellite.
  • computer system 604b displays connection element 820, which includes information related to aligning with a satellite, connecting to a satellite, and/or message status.
  • 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 FIG. 8H, connection status indicator 820a indicates that computer system 604b is not connected to a satellite.
  • Alignment instructions 820b indicate an action that a user can take to align with a satellite or stay aligned with a satellite. In FIG. 8H, alignment instructions 820b indicate that computer system 604b can be turned left to align with a satellite.
  • Message status 820c indicates a status of a message such as, e.g., unable to send, sending, sent, or waiting to receive. In FIG.
  • Alignment element 820d includes a graphical representation of the connection state of computer system 604b and an action that can be taken to align computer system 604b with a satellite or to remain aligned with a satellite.
  • alignment element 820d includes an arrow pointing in the counterclockwise direction, which indicates that computer system 604b is not aligned with a satellite and can be turned left to align with a satellite.
  • connection assistant interface 822 In response to detecting selection 825h of connection element 820, computer system 604b displays connection assistant interface 822 shown in FIG. 81. Similar to connection element 820, the appearance of connection assistant interface 822 is based on a current status of computer system 604b relative to a satellite. Compared to connection element 820, connection assistant interface 822 provides a larger interface for assisting a user in connecting computer system 604b with a satellite.
  • 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 FIG.
  • the representation of the satellite is on the left side of the representation of computer system 604b and to the left of the representation of the alignment window, which indicates that computer system 604b is not aligned with the satellite and that computer system 604b can be turned left to align with the satellite.
  • Alignment element 822a includes an arrow indicating that computer system can be turned left to align with the satellite.
  • Connection status indicator 822b indicates a status of a connection between computer system 604b and a satellite. In FIG. 81, connection status indicator 822b indicates that computer system 604b is not connected to a satellite.
  • Alignment instructions 822c indicate an action that a user can take to align with a satellite or stay aligned with a satellite. In FIG. 81, consistent with alignment element 822a, alignment instructions 822b indicate that computer system 604b can be turned left to align with a satellite.
  • FIG. 8J computer system 604b has been turned left relative to the position of computer system 604b in FIG. 81. As a result, computer system 604b is aligned with the satellite. In response to the change in alignment between computer system 604b and the satellite, computer system 604b displays (e.g., updates) connection assistant interface 822 to reflect the current status of computer system 604b relative to the satellite.
  • connection assistant interface 822 to reflect the current status of computer system 604b relative to the satellite.
  • the representation of the satellite is within the representation of the alignment window and the appearance of the alignment window is changed, which indicate that computer system 604b is aligned with the satellite.
  • Connection status indicator 822b indicates that computer system 604b is connected with the satellite.
  • Message status indicator 822e indicates that message 818a is being sent since computer system 604b is connected with the satellite.
  • Action indicator 822f indicates that computer system 604b is opening a messages application.
  • computer system 604b sends message 818a and displays messaging interface 818 and connection element 820 as shown in FIG. 8K.
  • message status indicator 818b indicates that the message was sent (e.g., “Today at 10:15 AM”) and computer system 604b displays connection element 820 based on the current alignment and/or connection status between computer system 604b and the satellite.
  • Connection status indicator 820a indicates that computer system 604b is connected to the satellite.
  • Alignment instructions 820b indicates that a user can keep pointing computer system 604b to the satellite (e.g., in the current direction) to send and receive messages via the satellite.
  • Message status 820c indicates that computer system 604b is sending message 818a.
  • Alignment element 820d indicates that computer system 604b is aligned with the satellite.
  • computer system 604b displays messaging interface 818 without keyboard 818e.
  • computer system 604b displays keyboard 818e, as shown in FIG. 8L.
  • computer system 604b provides the capability to send one or more additional messages to emergency services via satellite using messaging interface 818.
  • computer system 604b populates message compose field 818c, as shown in FIG. 8L.
  • computer system 604b sends a message to emergency services via satellite with the content that is in message compose field 818c at the time of selection 825k.
  • message 818a has completed sending, which is reflected in connection element 820 by message status 820c indicating that computer system 604b is waiting to receive (e.g., as opposed to “Sending” in FIG. 8K).
  • 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 81 Oh.
  • a message e.g., report generation interface 812, report generation interface 814, and/or report summary interface 816.
  • 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 81 Oh.
  • 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 FIG. 8 J).
  • a message e.g., report generation interface 812, report generation interface 814, and/or report summary interface 816
  • a satellite e.g., after displaying connection assistant interface 822 shown in FIG. 8 J.
  • FIGS. 8M and 8N illustrate exemplary user interfaces displayed by computer system 604a after a crash is detected and no terrestrial wireless communication network is available.
  • computer system 604a displays crash detection interface 612 when computer system 604a is attempting to call emergency services after a crash is detected (e.g., as described with reference to FIG. 6D).
  • computer system 604a displays prompt 824.
  • 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.
  • crash detection indicator 824a e.g., “Crash Detected”
  • connection status indicator 824b e.g., “No Connection”
  • satellite communication indication 824c e.g., “Your phone will attempt to text emergency services via satellite”
  • instructions 824d e.g., “Follow instructions on your phone” which includes a prompt to follow instructions on computer system 604b.
  • FIG. 9 is a flow diagram illustrating a method for sending a communication via an alternative communication network in the event of a crash using a computer system in accordance with some embodiments.
  • Method 900 is performed at a computer system (e.g., 100, 300, 500, 604a, 604b a smartphone, a smartwatch, a vehicle display system, a vehicle information system, a vehicle infotainment system, a tablet computer, a desktop computer, a laptop computer, and/or a head-mounted device (e.g., a head-mounted augmented reality and/or extended reality device)) that is in communication with (e.g., includes and/or is connected to) a display generation component (e.g., 606a, 606b, a display, a touch- sensitive display, a monitor, a display controller, a touch-sensitive display system, a projector, a holographic display, and/or a head-mounted display system) and one or more input devices (e.g., 606
  • 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.
  • 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.
  • 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)
  • 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).
  • 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.
  • 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 e.g., sound
  • biometric parameters e.g., blood pressure, blood oxygen level, pulse, and/or heart rate
  • 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).
  • 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.
  • the computer system detects the crash (e.g., using sensors of the computer system; the crash is detected by the computer system).
  • the computer system determines that a crash has occurred.
  • one or more external devices detect a crash and/or determine that a crash has occurred.
  • 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.
  • 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).
  • the computer system is not capable of detecting a crash and/or determining that a crash has occurred.
  • 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.
  • the computer system obtains (e.g., receives or retrieves) data indicating that a crash has occurred from the external computer system.
  • a terrestrial wireless communication network e.g., a cellular network
  • the computer system 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,
  • a non-terrestrial wireless communication network e.g., via one or more satellites, a satellite communication network, a low-bandwidth communication network, and/or a communication protocol that does not require cellular service and/or a terrestrial wireless communication network
  • a terrestrial wireless communication network e.g., a cellular network
  • the computer system e.g., a terrestrial wireless communication network is available to the computer system, the computer system is in communication with a terrestrial wireless communication network, the computer system is connected or is able to connect to a terrestrial wireless communication network, the computer system is receiving a signal from a terrestrial wireless communication network that satisfies strength and/or consistency criteria for performing communication, and/or there is a terrestrial wireless communication network via which the computer system can currently perform communication
  • the computer system forgoes (908) display of the non-terrestrial wireless communication option.
  • Displaying the non-terrestrial wireless communication option based on whether or not a terrestrial wireless communication network is reachable by the computer system informs the user that an alternative communication network is available even when a terrestrial wireless communication network is not available, enables the user to quickly and efficiently initiate communication via the non-terrestrial wireless communication network, and avoids displaying the option when unnecessary, 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.
  • communicating via a non-terrestrial wireless communication network includes a phone call, text message, email, audio message, video message, and/or video conference.
  • the communication is a live or real-time (e.g., full duplex real-time) communication.
  • 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).
  • the computer system can use a network provided by a network provider other than a provider associated with the computer system.
  • the computer system 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.
  • a call option e.g., 626c
  • the call option includes a selectable call option, an icon, a button, an affordance, and/or a user-interactive graphical user interface object.
  • 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).
  • 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).
  • 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).
  • 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.
  • the computer system in response to detecting selection of the call option, 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).
  • the computer system 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 FIG. 8 A) to a designated entity (e.g., a predetermined entity, a predetermined number, an emergency service, an emergency number, or an emergency contact).
  • a designated entity e.g., a predetermined entity, a predetermined number, an emergency service, an emergency number, or 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.
  • Attempting to initiate a call to a designated enity in response to obtaining the data indicating that a crash has occurred and before displaying the non-terrestrial wireless communication option enables the computer system to attempt using a communication method that uses less energy, is quicker, and requires fewer user inputs than communication via the non-terrestrial wireless communication network, which reduces the number of inputs needed to perform an operation, reduces energy consumption, and saves battery life.
  • the computer system 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 FIG. 8C), wherein the text 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).
  • a communication e.g., a text and/or audio communication
  • Sending a communicaion to a designated entity via the non-terrestrial wireless communication network in accordance with a determination that a threshold amount of time has elapsed enables the computer system to automatically send a communication after a crash without requiring user input, 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.
  • the computer system after sending the communication to the designated entity, displays a view-message option (e.g., 808); the computer system detects an input (e.g., 825b) corresponding to selection of the view-message option; and in response to detecting the input corresponding to selection of the view-message option, the computer system displays the communication (e.g., 818a) to the designated entity.
  • a view-message option e.g., 808
  • the computer system detects an input (e.g., 825b) corresponding to selection of the view-message option
  • the computer system displays the communication (e.g., 818a) to the designated entity.
  • displaying the communication to the designated entity includes displaying a user interface of a messaging application (e.g., a text messaging application) that includes a message conversation between a user of the computer system and the designated entity (including the communication to the designated entity, any responses from the designated entity, and any additional messages from the user of the computer system to the designated entity).
  • the user interface of the messaging application includes selectable elements (e.g., a keyboard and/or send button) for sending additional messages to the designated entity.
  • the computer system displays a selectable option that, when selected, causes the computer system to attempt (or re-attempt) to initiate a call with the designated entity.
  • Displaying a selectable option to display the communication to the designated entity frovides feedback to the user that the communication was sent and provides a quick and efficient method for displaying the communication, to which provides improved feedback to the user and reduces the number of inputs needed to perform an operation, and provides additional control options without cluttering the user interface with additional displayed controls.
  • the computer system 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.
  • an option e.g., 626c
  • Displaying an option to initiat 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.
  • the computer system 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.
  • the computer system 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).
  • a communication e.g., a text and/or audio communication
  • Sending a communication to a designated entity with information related to the crash in response to detecting selection of the nonterrestrial 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.
  • the computer system 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
  • an input
  • Displaying a set of selectable options for generating a communication provides a quick and effient 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.
  • any of the selections, requests, and/or inputs described herein is or includes a touch input (e.g., a tap gesture and/or a swipe gesture).
  • any of the selections, requests, and/or inputs described herein 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).
  • any of the selections, requests, and/or inputs described herein 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).
  • 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.
  • any of the selections, requests, and/or inputs described herein 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).
  • 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.
  • any of the user interface elements described as being selected herein 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).
  • method 700 optionally includes one or more of the characteristics of the various methods described above with reference to method 900. For brevity, these details are not repeated below.
  • 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. [0269] 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.
  • 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.
  • 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.
  • 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.
  • HIPAA Health Insurance Portability and Accountability Act
  • 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.
  • 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.
  • 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.
  • 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.
  • data de-identification can be used to protect a user’s privacy. Deidentification 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Emergency Management (AREA)
  • Business, Economics & Management (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Environmental & Geological Engineering (AREA)
  • Human Computer Interaction (AREA)
  • Public Health (AREA)
  • Health & Medical Sciences (AREA)
  • Chemical & Material Sciences (AREA)
  • Analytical Chemistry (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)
  • Information Transfer Systems (AREA)
  • User Interface Of Digital Computer (AREA)
  • Small-Scale Networks (AREA)

Abstract

La présente divulgation concerne de manière générale des techniques et des interfaces utilisateur pour initier une communication en cas d'accident.
EP23782659.9A 2022-09-06 2023-09-06 Interface utilisateur de détection d'accident Pending EP4584770A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US202263404155P 2022-09-06 2022-09-06
US18/241,747 US20240080389A1 (en) 2022-09-06 2023-09-01 Crash detection user interface
PCT/US2023/032051 WO2024054479A2 (fr) 2022-09-06 2023-09-06 Interface utilisateur de détection d'accident

Publications (1)

Publication Number Publication Date
EP4584770A2 true EP4584770A2 (fr) 2025-07-16

Family

ID=88236626

Family Applications (1)

Application Number Title Priority Date Filing Date
EP23782659.9A Pending EP4584770A2 (fr) 2022-09-06 2023-09-06 Interface utilisateur de détection d'accident

Country Status (3)

Country Link
EP (1) EP4584770A2 (fr)
CN (1) CN120019424A (fr)
WO (1) WO2024054479A2 (fr)

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3859005A (en) 1973-08-13 1975-01-07 Albert L Huebner Erosion reduction in wet turbines
US4826405A (en) 1985-10-15 1989-05-02 Aeroquip Corporation Fan blade fabrication system
KR100595926B1 (ko) 1998-01-26 2006-07-05 웨인 웨스터만 수동 입력 통합 방법 및 장치
US7218226B2 (en) 2004-03-01 2007-05-15 Apple Inc. Acceleration-based theft detection system for portable electronic devices
US7688306B2 (en) 2000-10-02 2010-03-30 Apple Inc. Methods and apparatuses for operating a portable device based on an accelerometer
US6677932B1 (en) 2001-01-28 2004-01-13 Finger Works, Inc. System and method for recognizing touch typing under limited tactile feedback conditions
US6570557B1 (en) 2001-02-10 2003-05-27 Finger Works, Inc. Multi-touch system and method for emulating modifier keys via fingertip chords
US7657849B2 (en) 2005-12-23 2010-02-02 Apple Inc. Unlocking a device by performing gestures on an unlock image
WO2013169849A2 (fr) 2012-05-09 2013-11-14 Industries Llc Yknots Dispositif, procédé et interface utilisateur graphique permettant d'afficher des objets d'interface utilisateur correspondant à une application
AU2013368443B2 (en) 2012-12-29 2016-03-24 Apple Inc. Device, method, and graphical user interface for transitioning between touch input to display output relationships
US9782083B2 (en) * 2015-09-04 2017-10-10 Polar Electro Oy Enhancing exercise safety
US10096226B2 (en) * 2016-05-10 2018-10-09 Reed Williams Systems and methods for accident notification
US11605274B2 (en) * 2018-11-01 2023-03-14 Apple Inc. Fall detection—audio looping
CN112235464B (zh) * 2019-06-28 2022-05-31 华为技术有限公司 一种基于跌倒检测的呼救方法及电子设备

Also Published As

Publication number Publication date
WO2024054479A3 (fr) 2024-04-18
CN120019424A (zh) 2025-05-16
WO2024054479A2 (fr) 2024-03-14
WO2024054479A4 (fr) 2024-06-13

Similar Documents

Publication Publication Date Title
US12299263B2 (en) User interfaces for location-related communications
US12160399B2 (en) Operational safety mode
US12278918B2 (en) Utilizing context information with an electronic device
KR102700917B1 (ko) 모바일 키 사용자 인터페이스들
JP2021525427A (ja) 電子デバイスにおけるシステムユーザインタフェースへのアクセス
US12543028B2 (en) Low-bandwidth and emergency communication user interfaces
US20240080389A1 (en) Crash detection user interface
US11785277B2 (en) User interfaces for managing audio for media items
US20240406700A1 (en) Communication via a non-terrestrial communication network
US20250377732A1 (en) Method and systems for performing operations in response to motion inputs
US20250370597A1 (en) Function accessibility
EP4381723B1 (fr) Interfaces utilisateur pour les communications à faible largeur de bande
WO2023235121A9 (fr) Procédés et interfaces utilisateur pour gérer des canaux audio
EP4584770A2 (fr) Interface utilisateur de détection d'accident
US12424228B2 (en) Methods and user interfaces for managing audio channels
AU2022235591B9 (en) Media controls user interface
WO2024253971A1 (fr) Communication par l'intermédiaire d'un réseau de communication non terrestre
WO2025259395A1 (fr) Interfaces utilisateur de sécurité d'entraînement
WO2024233015A1 (fr) Transfert de contenu entre des systèmes informatiques
EP4690854A1 (fr) Transfert de contenu entre des systèmes informatiques
WO2024253805A1 (fr) Interfaces utilisateur pour invite conditionnelle à effectuer une opération

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20250219

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC ME MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)