Collision detection user interface
By providing automated emergency communication options and non-terrestrial wireless communication interfaces in collision events, the complex and time-consuming communication process in the prior art is solved, achieving a more efficient user experience and extended battery life.
Patent Information
- Application Number
- CN202380063809.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-09-01
- Filing Date
- 2023-09-06
- Publication Date
- 2025-05-16
AI Technical Summary
The prior art uses electronic devices to initiate communications in collision events, the method is complex and time-consuming, resulting in wasting user time and device energy.
Provides a faster and more efficient method and interface by automatically providing the option to initiate communication with emergency numbers in the event of a collision and providing a user interface for a non-terrestrial wireless communication network when cellular communication is unavailable.
It reduces the cognitive burden of users, improves the efficiency of the human-computer interface, saves the power of the battery-driven device, and extends the time interval between battery charging.
Smart Images

Figure CN120019424A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to U.S. Patent Application No. 18 / 241,747, filed on September 1, 2023, entitled “CRASH DETECTION USER INTERFACE” and U.S. Provisional Patent Application No. 63 / 404,155, filed on September 6, 2022, entitled “CRASH DETECTION USER INTERFACE”. This application is related to U.S. Provisional Application No. 63 / 400,732, filed on August 24, 2022, entitled “METHODS AND INTERFACES FOR INITIATING COMMUNICATIONS”. The contents of each of these patent applications are incorporated herein by reference in their entirety. Technical Field
[0003] The present disclosure relates generally to computer user interfaces and, more particularly, to techniques for initiating communications in the event of a crash. Background Art
[0004] Electronic devices are used to transmit various types of communications, such as phone calls and text messages, using cellular communications. Some electronic devices are able to detect motion using sensors such as accelerometers and gyroscopes. Summary of the invention
[0005] However, some techniques for initiating communication using electronic devices in the event of a crash are often cumbersome and inefficient. For example, some prior art techniques use complex and time-consuming user interfaces that may include multiple key presses or keystrokes. Prior art techniques require more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.
[0006] Thus, the present technology provides a faster, more efficient method and interface for electronic devices to initiate communications in the event of a collision. Such methods and interfaces optionally supplement or replace other methods for initiating communications in the event of a collision. Such methods and interfaces reduce the cognitive burden imposed on the user and produce a more efficient human-computer interface. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges.
[0007] According to some embodiments, a method is described. The method includes: at a computer system in communication with a display generation component and one or more input devices: obtaining data indicating that a collision has occurred; in response to obtaining the data indicating that a collision has occurred, displaying a call option via the display generation component; and initiating a call to a predetermined number associated with the call option based on determining that the call option has been selected via the one or more input devices.
[0008] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system 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 collision has occurred; in response to obtaining data indicating that a collision has occurred, displaying a call option via the display generation component; and initiating a process of calling a predetermined number associated with the call option based on determining that the call option has been selected via the one or more input devices.
[0009] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system 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 collision has occurred; in response to obtaining data indicating that a collision has occurred, displaying a call option via the display generation component; and initiating a process of calling a predetermined number associated with the call option based on determining that the call option has been selected via the one or more input devices.
[0010] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: obtaining data indicating that a collision has occurred; in response to obtaining data indicating that a collision has occurred, displaying a call option via the display generation component; and initiating a process of calling a predetermined number associated with the call option based on determining that the call option has been selected via the one or more input devices.
[0011] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: a component for obtaining data indicating that a collision has occurred; a component for displaying a call option via the display generation component in response to obtaining the data indicating that a collision has occurred; and a component for initiating a process of calling a predetermined number associated with the call option based on determining that the call option has been selected via the one or more input devices.
[0012] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system 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 collision has occurred; in response to obtaining data indicating that a collision has occurred, displaying a call option via the display generation component; and initiating a process of calling a predetermined number associated with the call option based on determining that the call option has been selected via the one or more input devices.
[0013] According to some embodiments, a method is described. The method includes: at a computer system in communication with a display generation component and one or more input devices: obtaining data indicating that a collision has occurred; and in response to obtaining the data indicating that a collision has occurred: based on determining that the computer system is not reachable to a terrestrial wireless communication network, displaying via the display generation component a non-terrestrial wireless communication option that, when selected via the one or more input devices, initiates a process for communicating via the non-terrestrial wireless communication network; and based on determining that the computer system is reachable to the terrestrial wireless communication network, abandoning displaying the non-terrestrial wireless communication option.
[0014] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system 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 collision has occurred; and in response to obtaining data indicating that a collision has occurred: based on determining that the computer system is not reachable to a terrestrial wireless communication network, displaying a non-terrestrial wireless communication option via the display generation component, the non-terrestrial wireless communication option initiating a process for communicating via the non-terrestrial wireless communication network when selected via the one or more input devices; and based on determining that the computer system is reachable to the terrestrial wireless communication network, abandoning displaying the non-terrestrial wireless communication option.
[0015] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system 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 collision has occurred; and in response to obtaining data indicating that a collision has occurred: based on determining that the computer system is not reachable to a terrestrial wireless communication network, displaying a non-terrestrial wireless communication option via the display generation component, the non-terrestrial wireless communication option initiating a process for communicating via the non-terrestrial wireless communication network when selected via the one or more input devices; and based on determining that the computer system is reachable to the terrestrial wireless communication network, abandoning display of the non-terrestrial wireless communication option.
[0016] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: obtaining data indicating that a collision has occurred; and in response to obtaining data indicating that a collision has occurred: based on determining that the computer system cannot reach a terrestrial wireless communication network, displaying a non-terrestrial wireless communication option via the display generation component, the non-terrestrial wireless communication option, when selected via one or more input devices, initiating a process for communicating via the non-terrestrial wireless communication network; and based on determining that the computer system can reach the terrestrial wireless communication network, abandoning the display of the non-terrestrial wireless communication option.
[0017] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: a component for obtaining data indicating that a collision has occurred; and a component for, in response to obtaining data indicating that a collision has occurred: based on determining that the computer system cannot reach the ground wireless communication network, displaying a non-ground wireless communication option via the display generation component, the non-ground wireless communication option, when selected via one or more input devices, initiating a process for communicating via the non-ground wireless communication network; and based on determining that the computer system can reach the ground wireless communication network, abandoning the display of the non-ground wireless communication option.
[0018] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system 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 collision has occurred; and in response to obtaining data indicating that a collision has occurred: based on determining that the computer system is not reachable to a terrestrial wireless communication network, displaying a non-terrestrial wireless communication option via the display generation component, the non-terrestrial wireless communication option initiating a process for communicating via the non-terrestrial wireless communication network when selected via the one or more input devices; and based on determining that the computer system is reachable to the terrestrial wireless communication network, abandoning display of the non-terrestrial wireless communication option.
[0019] Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are optionally included in a transient computer-readable storage medium or other computer program product configured for execution by one or more processors.
[0020] Thus, a faster, more efficient method and interface for initiating communications in the event of a crash is provided for devices, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices.Such methods and interfaces may supplement or replace other methods for initiating communications in the event of a crash. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, wherein like reference numerals refer to corresponding parts throughout the drawings.
[0022] Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display according to some embodiments.
[0023] Figure 1B is a block diagram illustrating exemplary components for event processing according to some embodiments.
[0024] Figure 2 A portable multifunction device with a touch screen according to some embodiments is illustrated.
[0025] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.
[0026] Figure 4A An exemplary user interface for a menu of applications on a portable multifunction device according to some embodiments is illustrated.
[0027] Figure 4B An exemplary user interface for a multifunction device having a touch-sensitive surface separate from the display is illustrated according to some embodiments.
[0028] Figure 5A Personal electronic devices according to some embodiments are illustrated.
[0029] Figure 5B is a block diagram illustrating a personal electronic device according to some embodiments.
[0030] FIG. 6A to FIG. 6AA An exemplary user interface for initiating communications using an electronic device in the event of a collision according to some embodiments is illustrated.
[0031] Figure 7 is a flowchart illustrating a method of initiating communications using an electronic device in the event of a collision according to some embodiments.
[0032] FIG. 8A to FIG. 8N An exemplary user interface for transmitting communications using an alternative communication network in the event of a crash is illustrated in accordance with some embodiments.
[0033] Fig. 9 is a flow chart illustrating a method of transmitting communications using an alternative communication network in the event of a crash according to some embodiments. DETAILED DESCRIPTION
[0034] The following description sets forth exemplary methods, parameters, etc. However, it should be appreciated that such description is not intended to limit the scope of the present disclosure, but is provided as a description of exemplary embodiments.
[0035] It is desirable to provide an electronic device that provides an efficient method and interface for initiating communication in the event of a collision. For example, in some embodiments, when a collision is detected, the electronic device automatically provides an option to initiate communication with an emergency number. For example, in some embodiments, if a collision is detected when a cellular communication network is unavailable, the electronic device provides a user interface for communicating via an alternative communication network (e.g., a satellite communication network). Such techniques can reduce the cognitive burden of the user initiating communication in the event of a collision, thereby improving productivity. In addition, such techniques can reduce processor power and battery power that would otherwise be wasted on redundant user input.
[0036] under, Figure 1A to Figure 1B , Figure 2 , Figure 3 , Figures 4A to 4B and Figures 5A to 5B A description of an example device for performing techniques for initiating communications in the event of a crash is provided. FIG. 6A to FIG. 6AAAn exemplary user interface for initiating communications in the event of a crash is illustrated. Figure 7 is a flow chart illustrating a method of initiating communications in the event of a collision according to some embodiments. FIG. 6A to FIG. 6AA The user interface in is used to illustrate the process described below, including Figure 7 process. FIG. 8A to FIG. 8N An exemplary user interface for transmitting communications using an alternative communication network in the event of a crash is illustrated. Fig. 9 is a flow chart illustrating a method of transmitting communications using an alternative communication network in the event of a crash according to some embodiments. Fig. 8A The user interface in FIG. 8Z is used to illustrate the process described below, including Fig. 9 process.
[0037] The process described below enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device) through various techniques, including by providing improved visual feedback to the user, reducing the number of inputs required to perform an operation, providing additional control options without cluttering the user interface with additional displayed controls, performing an operation without further user input when a set of conditions have been met, and / or additional techniques. These techniques also reduce power usage and extend the battery life of the device by enabling the user to use the device more quickly and more efficiently. Reducing the number of inputs required to perform an operation and providing clear feedback to the user enables the user to use the device more quickly and more efficiently, which is particularly important for several reasons in emergency situations and / or when a collision occurs. Using the device efficiently preserves battery life, which is important in emergency situations because some emergency communication features use satellite communications, which may use a large amount of energy (e.g., more energy than cellular communications), and because the opportunity to recharge the device in an emergency may be limited (e.g., because the user has been involved in a collision). A user interface that clearly indicates how to use a device quickly and efficiently is particularly important in an emergency or when a crash occurs, as the user may be nervous and more likely to make mistakes. Reducing errors by providing clear instructions and feedback in an emergency and / or when a crash has occurred saves time in communicating with emergency services, which can increase the likelihood that emergency assistance will be provided more quickly.
[0038] In addition, in the method described herein where one or more steps depend on one or more conditions being met, it should be understood that the method can be repeated in multiple repetitions so that in the process of repetition, all conditions for determining the steps in the method have been met in different repetitions of the method. For example, if the method needs to perform the first step (if the condition is met), and perform the second step (if the condition is not met), then the ordinary technician will know that the steps stated are repeated until both the condition is met and the condition is not met (in no particular order). Therefore, the method described as having one or more steps depending on one or more conditions being met can be rewritten as a method of repeating until each condition described in the method is met. However, this does not require the system or computer-readable medium to declare that the system or computer-readable medium contains instructions for performing a contingent operation based on the satisfaction of the corresponding one or more conditions, and is therefore able to determine whether the possible situation has been met without explicitly repeating the steps of the method until all conditions for determining the steps in the method have been met. It will also be understood by ordinary technicians in the art that, similar to the method with the contingent step, the system or computer-readable storage medium can repeat the steps of the method as many times as needed to ensure that all the contingent steps have been performed.
[0039] Although the following description uses the terms "first", "second", etc. to describe various elements, these elements should not be limited by the terms. In some embodiments, these terms are used to distinguish one element from another element. For example, a first touch can be named a second touch and similarly a second touch can be named a first touch without departing from the scope of the various described embodiments. In some embodiments, the first touch and the second touch are two separate references to the same touch. In some embodiments, both the first touch and the second touch are touches, but they are not the same touch.
[0040] The terms used in the description of various described embodiments herein are only for the purpose of describing specific embodiments, and are not intended to be limiting. As used in the description of various described embodiments and in the appended claims, the singular forms "one" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more items in the associated listed items. It will also be understood that the terms "include" and / or "comprising" are used in this specification to specify the presence of stated features, integers, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their grouping.
[0041] The term "if" is optionally interpreted to mean "when," "upon," or "in response to determining," or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined that ..." or "if [a stated condition or event] is detected" are optionally interpreted to mean "upon determining that ..." or "in response to determining that ..." or "upon detecting [a stated condition or event]," or "in response to detecting [a stated condition or event]," depending on the context.
[0042] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch from Apple Inc. (Cupertino, California). Devices, iPod Equipment and Device. Optionally use other portable electronic devices, such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads). In some embodiments, the electronic device is a computer system that communicates with the display generation component (e.g., via wireless communication, via wired communication). The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separated from the computer system. As used herein, "display" content includes sending data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content to display content (e.g., video data rendered or decoded by display controller 156).
[0043] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse and / or joystick.
[0044] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.
[0045] Various applications executed on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or adjusted and / or varied within the respective applications. In this way, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and clear to the user.
[0046] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1A 1 is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to as or referred to as a "touch-sensitive display system." The device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.
[0047] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four different values and more typically includes hundreds of different values (e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).
[0048] As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical property of the device or a component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or a touchpad) is optionally interpreted by the user as a "press click" or "release click" to a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, movement of a touch-sensitive surface may optionally be interpreted or sensed by a user as "roughness" of the touch-sensitive surface even when there is no change in the smoothness of the touch-sensitive surface. While such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user.
[0049] It should be understood that device 100 is merely one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. Figure 1A The various components shown are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and / or application specific integrated circuits.
[0050] The memory 102 optionally includes high-speed random access memory, and optionally also includes non-volatile memory, such as one or more disk storage devices, flash memory devices or other non-volatile solid-state memory devices. The memory controller 122 optionally controls the access rights of other components of the device 100 to the memory 102.
[0051] The peripheral device interface 118 can be used to couple the input peripheral devices and output peripheral devices of the device to the CPU 120 and the memory 102. The one or more processors 120 run or execute various software programs (such as computer programs (e.g., including instructions)) and / or instruction sets stored in the memory 102 to perform various functions of the device 100 and process data. In some embodiments, the peripheral device interface 118, the CPU 120, and the memory controller 122 are optionally implemented on a single chip such as the chip 104. In some other embodiments, they are optionally implemented on separate chips.
[0052] RF (radio frequency) circuit 108 receives and transmits RF signals, also referred to as electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memories, and the like. RF circuit 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also referred to as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communications (NFC) fields, such as through short-range communications radio components. Wireless communication optionally uses any of a variety of communication standards, protocols and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed Downlink Packet Access (HSDPA), High Speed Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols that have not been developed as of the filing date of this document.
[0053] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into electrical signals, and sends the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to humans. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals into audio data and sends the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or sent to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., Figure 2 The headset jack provides an interface between the audio circuit 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset having both output (e.g., a single or dual-ear headset) and input (e.g., a microphone).
[0054] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / transmit electrical signals from / to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some embodiments, the input controller 160 is optionally coupled to any one of the following (or none of the following): a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g., Figure 2 208) optionally includes an increase / decrease button for volume control of the speaker 111 and / or the microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2206 in). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a touchpad as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as for tracking a user's gestures (e.g., hand gestures and / or air gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. In some embodiments, an air gesture is a gesture that is detected without the user touching an input element that is part of the device (or is independent of an input element that is part of the device) and is based on detected movement of a part of the user's body through the air, including movement of the user's body relative to an absolute reference (for example, the angle of the user's arm relative to the ground or the distance of the user's hand relative to the ground), movement relative to another part of the user's body (for example, movement of the user's hand relative to the user's shoulder, movement of one of the user's hands relative to the user's other hand, and / or movement of the user's fingers relative to another finger or part of the user's hand), and / or absolute movement of a part of the user's body (for example, a tap gesture involving moving the hand in a predetermined position, a predetermined amount and / or speed, or a shake gesture involving a predetermined speed or amount of rotation of a part of the user's body).
[0055] A quick press of the push button optionally disengages the lock of the touch screen 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, filed December 23, 2005, for "Unlocking a Device by Performing Gestures on an Unlock Image," (i.e., U.S. Patent No. 7,657,849), which is hereby incorporated by reference in its entirety. A long press of the push button (e.g., 206) optionally turns the device 100 on or off. The functions of one or more buttons are optionally user-customizable. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
[0056] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or transmits electrical signals to the touch screen. The touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.
[0057] The touch screen 112 has a touch-sensitive surface, sensor, or sensor group that accepts input from a user based on tactile and / or haptic contact. The touch screen 112 and display controller 156 (together with any associated modules and / or instruction sets in memory 102) detect contact (and any movement or interruption of the contact) on the touch screen 112 and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to the user's finger.
[0058] The touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. The touch screen 112 and display controller 156 optionally use any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112 to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as in the Apple ® from Apple Inc. (Cupertino, California). and iPod The technology used in
[0059] The touch-sensitive display in some embodiments of touch screen 112 is optionally similar to the multi-touch-sensitive touchpad described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman et al.), and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, while a touch-sensitive touchpad does not provide visual output.
[0060] The touch-sensitive display in some embodiments of the touch screen 112 is described in the following applications: (1) U.S. patent application No. 11 / 381,313, filed on May 2, 2006, "Multipoint Touch Surface Controller"; (2) U.S. patent application No. 10 / 840,862, filed on May 6, 2004, "Multipoint Touchscreen"; (3) U.S. patent application No. 10 / 903,964, filed on July 30, 2004, "Gestures For Touch Sensitive Input Devices"; (4) U.S. patent application No. 11 / 048,264, filed on January 31, 2005, "Gestures For Touch Sensitive Input Devices"; (5) U.S. patent application No. 11 / 038,590, filed on January 18, 2005, "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices”; (6) U.S. patent application Ser. No. 11 / 228,758, filed on September 16, 2005, “Virtual Input Device Placement On A Touch Screen User Interface”; (7) U.S. patent application Ser. No. 11 / 228,700, filed on September 16, 2005, “Operation Of A Computer With A Touch Screen Interface”; (8) U.S. patent application Ser. No. 11 / 228,737, filed on September 16, 2005, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”; and (9) U.S. patent application Ser. No. 11 / 367,749, filed on March 3, 2006, “Multi-Functional Hand-Held Device”. All of these applications are incorporated herein by reference in their entirety.
[0061] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, a finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may not be as accurate as stylus-based input due to the larger contact area of the finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positioning or commands for performing the actions desired by the user.
[0062] In some embodiments, in addition to the touch screen, the device 100 optionally includes a touchpad for activating or deactivating specific functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from the touch screen 112, or an extension of the touch-sensitive surface formed by the touch screen.
[0063] The device 100 also includes a power system 162 for powering the various components. The power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, a power fault detection circuit, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.
[0064] Device 100 optionally also includes one or more optical sensors 164 . Figure 1AAn optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. The optical sensor 164 optionally includes a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with the imaging module 143 (also called a camera module), the optical sensor 164 optionally captures a static image or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for static images and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that when the user views other video conference participants on the touch screen display, the image of the user is optionally obtained for video conferencing. In some embodiments, the positioning of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that a single optical sensor 164 is used with the touch screen display for both video conferencing and static image and / or video image acquisition.
[0065] Device 100 optionally also includes one or more depth camera sensors 175 . Figure 1A A depth camera sensor coupled to a depth camera controller 169 in the I / O subsystem 106 is shown. The depth camera sensor 175 receives data from the environment to create a three-dimensional model of an object (e.g., a face) within the scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with the imaging module 143 (also referred to as a camera module), the depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by the imaging module 143. In some embodiments, the depth camera sensor is located at the front of the device 100, so that an image of the user with depth information is optionally obtained for video conferencing while the user is viewing other video conference participants on the touch screen display, and a selfie with depth map data is captured. In some embodiments, the depth camera sensor 175 is located at the rear of the device, or at both the rear and front of the device 100. In some embodiments, the positioning of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that the depth camera sensor 175 is used with the touch screen display for both video conferencing and still image and / or video image acquisition.
[0066] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1AA contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite to touch screen display 112 located on the front of device 100.
[0067] Device 100 optionally also includes one or more proximity sensors 166 . Figure 1A A proximity sensor 166 is shown coupled to the peripherals interface 118. Alternatively, the proximity sensor 166 is optionally coupled to the input controller 160 in the I / O subsystem 106. The proximity sensor 166 is optionally implemented as described in the following U.S. patent application numbers: 11 / 241,839, entitled "Proximity Detector In Handheld Device"; 11 / 240,788, entitled "Proximity Detector In Handheld Device"; 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. In some embodiments, when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.
[0068] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1AA tactile output generator is shown coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component; and / or an electromechanical device for converting energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component for converting an electrical signal into a tactile output on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates a tactile output on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one tactile output generator is arranged in parallel or adjacent to a touch-sensitive surface (e.g., a touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 100) or laterally (e.g., backward and forward in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on the back of the device 100, opposite the touch screen display 112 located on the front of the device 100.
[0069] Device 100 optionally also includes one or more accelerometers 168 . Figure 1A An accelerometer 168 is shown coupled to the peripheral device interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 in the I / O subsystem 106. The accelerometer 168 is optionally implemented as described in the following U.S. Patent Publication Nos.: 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and 20060017692, entitled "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer", both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on analysis of data received from one or more accelerometers. The device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver in addition to the accelerometer 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 100.
[0070] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and an application (or instruction set) 136. In addition, in some embodiments, memory 102 ( Figure 1A ) or 370( Figure 3 ) storage device / global internal state 157, such as Figure 1A and Figure 3 . The device / global internal state 157 includes one or more of the following: active application state, which indicates which application (if any) is currently active; display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and position information related to the device's position and / or posture.
[0071] The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.), and facilitating communication between various hardware components and software components.
[0072] The communication module 128 facilitates communication with other devices through one or more external ports 124, and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.
[0073] The contact / motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger press event), determining the contact strength (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of the contact point being represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single finger contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on the touch pad.
[0074] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touchscreen display hardware, the mouse "click" threshold of a touchpad or touchscreen can be set to any one of a large range of predefined thresholds. Additionally, in some specific implementations, a software setting is provided to the user of the device for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).
[0075] The contact / motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event, and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event.
[0076] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual attributes) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including but not limited to text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.
[0077] In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes for specifying the graphics to be displayed from an application or the like, along with coordinate data and other graphics attribute data if necessary, and then generates screen image data to be output to the display controller 156.
[0078] Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator 167 to produce tactile output at one or more locations on device 100 in response to user interaction with device 100 .
[0079] Text input module 134, optionally as part of graphics module 132, provides a soft keyboard for entering text in various applications (eg, contacts 137, email 140, IM 141, browser 147, and any other application requiring text input).
[0080] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone module 138 for use in location-based dialing; to the camera module 143 as picture / video metadata; and to applications that provide location-based services, such as weather widgets, local yellow pages widgets, and map / navigation widgets).
[0081] Application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:
[0082] Contacts module 137 (sometimes called address book or contact list);
[0083] Telephone module 138;
[0084] Video conferencing module 139;
[0085] Email client module 140;
[0086] Instant messaging (IM) module 141;
[0087] Fitness support module 142;
[0088] A camera module 143 for still images and / or video images;
[0089] Image management module 144;
[0090] Video player module;
[0091] Music player module;
[0092] Browser module 147;
[0093] Calendar module 148;
[0094] Widget module 149, which optionally includes one or more of the following: weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5 and other widgets acquired by the user, and user-created widget 149-6;
[0095] A widget creator module 150 for forming a user-created widget 149-6;
[0096] Search module 151;
[0097] Video and music player module 152, which merges the video player module and the music player module;
[0098] Notepad module 153;
[0099] Map module 154; and / or
[0100] Online video module 155.
[0101] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
[0102] In combination with the touch screen 112, display controller 156, touch / motion module 130, graphics module 132 and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (for example, stored in the application internal state 192 of the contact module 137 in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses or other information with names; associating images with names; categorizing and classifying names; providing phone numbers or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing module 139, email 140 or IM 141; and the like.
[0103] In conjunction with RF circuit 108, audio circuit 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, phone module 138 is optionally used to enter a character sequence corresponding to a phone number, access one or more phone numbers in contact module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.
[0104] In combination with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact / motion module 130, the graphics module 132, the text input module 134, the contact module 137 and the telephone module 138, the video conferencing module 139 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.
[0105] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, transmitting, receiving, and managing emails in response to user instructions. In conjunction with image management module 144, email client module 140 makes it very easy to create and transmit emails with still images or video images captured by camera module 143.
[0106] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for the following: entering a character sequence corresponding to an instant message, modifying previously entered characters, sending a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the instant messages sent and / or received optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages transmitted using SMS or MMS) and Internet-based messages (e.g., messages transmitted using XMPP, SIMPLE, or IMPS).
[0107] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154 and the music player module, the fitness support module 142 includes executable instructions for creating a fitness (e.g., with time, distance and / or calorie burn goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for fitness; and displaying, storing and sending fitness data.
[0108] In conjunction with the touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132 and image management module 144, the camera module 143 includes executable instructions for: capturing still images or videos (including video streams) and storing them in the memory 102, modifying the characteristics of the still images or videos, or deleting the still images or videos from the memory 102.
[0109] In conjunction with touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions for arranging, modifying (e.g., editing) or otherwise manipulating, marking, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.
[0110] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions, including searching, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
[0111] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the email client module 140 and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying and storing calendars and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.
[0112] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is a mini-application that is optionally downloaded and used by a user (e.g., weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm widget 149-4, and dictionary widget 149-5) or a mini-application created by a user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! widget).
[0113] In combination with the RF circuitry 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 is optionally used by a user to create widgets (e.g., converting a user-specified portion of a web page into a widget).
[0114] In combination with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the search module 151 includes executable instructions for searching the memory 102 for text, music, sound, images, videos and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
[0115] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch screen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
[0116] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the notepad module 153 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.
[0117] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the GPS module 135 and the browser module 147, the map module 154 is optionally used to receive, display, modify and store maps and data associated with the maps (e.g., driving directions, data relating to stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
[0118] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions for allowing a user to access, browse, receive (e.g., by streaming and / or downloading), playback (e.g., on the touch screen or on an external display connected via external port 124), send an email with a link to a specific online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a specific online video. Additional description of online video applications can be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on June 20, 2007, for "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," and U.S. Patent Application No. 11 / 968,067, filed on December 31, 2007, for "Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos," the contents of which are hereby incorporated by reference in their entirety.
[0119] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as independent software programs (such as computer programs (e.g., including instructions)), processes, or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. For example, a video player module is optionally combined with a music player module into a single module (e.g., Figure 1A In some embodiments, the memory 102 optionally stores a subset of the above modules and data structures. In addition, the memory 102 optionally stores additional modules and data structures not described above.
[0120] In some embodiments, the device 100 is a device where the operation of a predefined set of functions on the device is performed exclusively through a touch screen and / or a touch pad. By using a touch screen and / or a touch pad as the primary input control device for operating the device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on the device 100 is optionally reduced.
[0121] A predefined set of functions that are performed exclusively through the touch screen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main menu, a home menu, or a root menu from any user interface displayed on the device 100. In such embodiments, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.
[0122] Figure 1B is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 370( Figure 3 ) includes an event classifier 170 (e.g., in the operating system 126) and a corresponding application 136-1 (e.g., any one of the aforementioned applications 137 to 151, 155, 380 to 390).
[0123] Event classifier 170 receives event information and determines the application 136-1 and the application view 191 of application 136-1 to which the event information is to be delivered. Event classifier 170 includes event monitor 171 and event distributor module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates one or more current application views displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device / global internal state 157 is used by event classifier 170 to determine which application(s) is currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information is to be delivered.
[0124] In some embodiments, the application internal state 192 includes additional information, such as one or more of the following: resumption information to be used when application 136-1 resumes execution, user interface state information indicating that information is being displayed or is ready to be displayed by application 136-1, a state queue for enabling a user to return to a previous state or view of application 136-1, and a repeat / undo queue of previous actions taken by the user.
[0125] Event monitor 171 receives event information from peripherals interface 118. Event information includes information about sub-events (e.g., user touches on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 sends information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (through audio circuit 110). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
[0126] In some embodiments, event monitor 171 transmits a request to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 sends event information. In other embodiments, peripheral device interface 118 sends event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or receiving an input for more than a predetermined duration).
[0127] In some embodiments, the event classifier 170 also includes a hit view determination module 172 and / or an active event identifier determination module 173.
[0128] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides software procedures for determining where within one or more views a sub-event has occurred. A view consists of controls and other elements that a user can see on the display.
[0129] Another aspect of the user interface associated with an application is a set of views, sometimes also referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of the respective application) in which a touch is detected optionally correspond to a programmatic level within the programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is optionally referred to as a hit view, and the set of events that are identified as correct input is optionally determined at least in part based on the hit view of the initial touch that started the touch-based gesture.
[0130] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle the sub-events. In most cases, the hit view is the lowest level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it is identified as the hit view.
[0131] Active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, higher views in the hierarchy will still remain as actively participating views.
[0132] Event distributor module 174 distributes event information to event recognizers (e.g., event recognizers 180). In embodiments including active event recognizer determination module 173, event distributor module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event distributor module 174 stores the event information in an event queue, which is retrieved by corresponding event receivers 182.
[0133] In some embodiments, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In yet another embodiment, event classifier 170 is a standalone module or is part of another module stored in memory 102, such as contact / motion module 130.
[0134] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, the corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more event recognizers in event recognizers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit or application 136-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178 and / or event data 179 received from event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in the corresponding application view 191.
[0135] The corresponding event identifier 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies the event based on the event information. The event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event identifier 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (which optionally includes sub-event delivery instructions).
[0136] Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of the touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another orientation (for example, from a longitudinal orientation to a transverse orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).
[0137] Event comparator 184 compares event information with predefined event or sub-event definitions, and determines an event or sub-event based on the comparison, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 includes the definition of an event (e.g., a predefined sequence of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in events (e.g., 187-1 and / or 187-2) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1 (187-1) is a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on a displayed object, a first lift-off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on a displayed object, and a second lift-off (touch end) of a predetermined duration. In another example, the definition of event 2 (187-2) is a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on a displayed object, movement of the touch on the touch-sensitive display 112, and lifting of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
[0138] In some embodiments, event definition 186 includes a definition of an event for a corresponding user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view displaying three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with a sub-event and the object that triggered the hit test.
[0139] In some embodiments, the definition of the corresponding event (187) also includes a delay action that delays the delivery of the event information until it has been determined that the sub-event sequence does or does not correspond to the event type of the event identifier.
[0140] When a corresponding event recognizer 180 determines that a sequence of sub-events does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.
[0141] In some embodiments, the corresponding event recognizers 180 include metadata 183 with configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact or can interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.
[0142] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from transmitting (and deferred transmission) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a flag associated with the identified event, and the event handler 190 associated with the flag obtains the flag and executes a predefined process.
[0143] In some embodiments, the event delivery instructions 188 include a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers the event information to an event handler associated with a sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or with an actively participating view receives the event information and executes a predetermined process.
[0144] In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contact module 137 or stores video files used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates new user interface objects or updates the positioning of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and transmits the display information to graphics module 132 for display on a touch-sensitive display.
[0145] In some embodiments, event handler 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
[0146] It should be understood that the above discussion of event processing of user touches on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 100, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holddowns; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events that define the event to be distinguished.
[0147] Figure 2A portable multifunction device 100 with a touch screen 112 according to some embodiments is illustrated. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more of these graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, when the user interrupts contact with one or more graphics, selection of one or more graphics will occur. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or rolling of fingers that have been in contact with the device 100 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select the graphic. For example, when the gesture corresponding to selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.
[0148] The device 100 optionally also includes one or more physical buttons, such as a "home" or menu button 204. As previously described, the menu button 204 is optionally used to navigate to any application 136 in a set of applications that are optionally executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen 112.
[0149] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and for locking the device, one or more volume adjustment buttons 208, a user identity module (SIM) card slot 210, an earphone jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and keeping the button in a pressed state for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval passes; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input for activating or deactivating certain functions through a microphone 113. The device 100 also optionally includes one or more contact strength sensors 165 for detecting the strength of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for a user of the device 100.
[0150] Figure 3300 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. Device 300 does not have to be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuits (sometimes referred to as a chipset) that interconnect system components and control communications between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or a mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above reference Figure 1A The tactile output generator 167 described above), the sensor 359 (e.g., an optical sensor, an acceleration sensor, a proximity sensor, a touch sensor, and / or a contact intensity sensor (similar to the above reference Figure 1A Memory 370 optionally includes one or more storage devices located away from CPU 310. In some embodiments, memory 370 stores data related to portable multifunction device 100 ( Figure 1A ) or a subset thereof. In addition, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.
[0151] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the previously mentioned memory device. Each module in the above-mentioned modules corresponds to the instruction set for performing the function described above. The above-mentioned modules or computer programs (for example, instruction sets or including instructions) do not have to be realized with independent software programs (such as computer programs (for example, including instructions)), processes or modules, and therefore the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores the subset of the above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.
[0152] Attention is now turned to an embodiment of a user interface that is optionally implemented on, for example, portable multifunction device 100.
[0153] Figure 4A An exemplary user interface of an application menu on portable multifunction device 100 according to some embodiments is illustrated. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:
[0154] Signal strength indicators 402 for wireless communications such as cellular signals and Wi-Fi signals;
[0155] Time 404;
[0156] Bluetooth indicator 405;
[0157] Battery status indicator 406;
[0158] A tray 408 with icons for commonly used applications, such as:
[0159] o an icon 416 of the phone module 138 labeled “Phone” which optionally includes an indicator 414 of the number of missed calls or voicemails;
[0160] o an icon 418 of the email client module 140 labeled “Mail”, which optionally includes an indicator 410 of the number of unread emails;
[0161] o An icon 420 labeled “Browser” of the browser module 147; and
[0162] o an icon 422 labeled “iPod” of a video and music player module 152 (also referred to as an iPod (trademark of Apple Inc.) module 152); and
[0163] Icons for other apps, such as:
[0164] o Icon 424 of IM module 141 labeled “Message”;
[0165] o Icon 426 labeled “Calendar” of calendar module 148;
[0166] o Icon 428 labeled “Photos” of the image management module 144;
[0167] o An icon 430 labeled “Camera” of the camera module 143;
[0168] o Icon 432 labeled “Online Video” of the online video module 155;
[0169] o an icon 434 labeled “Stock Market” of the stock market widget 149-2;
[0170] o an icon 436 labeled “MAP” of the map module 154;
[0171] o Icon 438 labeled “Weather” of the weather widget 149-1;
[0172] o An icon 440 labeled “Clock” of the alarm clock widget 149-4;
[0173] o an icon 442 labeled “Fitness Support” of the fitness support module 142;
[0174] o An icon 444 labeled "Notepad" of the notepad module 153; and
[0175] o An icon 446 of a settings application or module labeled “Settings” that provides access to settings for the device 100 and its various applications 136.
[0176] It should be noted that Figure 4A The illustrated icon labels are exemplary only. For example, the icon 422 of the video and music player module 152 is labeled "Music" or "Music Player". Other labels are optionally used for various application icons. In some embodiments, the label of the corresponding application icon includes the name of the application corresponding to the corresponding application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.
[0177] Figure 4B The example embodiment has a touch-sensitive surface 451 (eg, touch screen display 112) that is separate from a display 450 (eg, touch screen display 112). Figure 3 a tablet device or a touch pad 355) (e.g., Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating tactile output for a user of device 300.
[0178] Although some of the examples below are given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) of the main axis (for example, Figure 4B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 4B 460 corresponds to 468 and 462 corresponds to 470) in contact with touch-sensitive surface 451 (e.g., Figure 4B Thus, when the touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g., Figure 4B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is separated, the device is used to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.
[0179] Additionally, although the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap gestures, finger swipe gestures), it should be understood that in some embodiments, one or more of these finger inputs are replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of contact), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detecting contact, followed by ceasing to detect contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or mice and finger contacts are optionally used simultaneously.
[0180] Figure 5AAn exemplary personal electronic device 500 is illustrated. Device 500 includes a body 502. In some embodiments, device 500 may include a body 502 relative to devices 100 and 300 (e.g., Figures 1A to 4B ) some or all of the features described in the foregoing. In some embodiments, device 500 has a touch-sensitive display screen 504, referred to hereinafter as touch screen 504. Alternatively, or in addition to touch screen 504, device 500 also has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of contact (e.g., touch) applied. One or more intensity sensors of touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of touch. The user interface of device 500 can respond to touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 500.
[0181] Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related applications: International patent application serial number PCT / US2013 / 040061, entitled “Device, Method, and Graphical User Interface for Displaying UserInterface Objects Corresponding to an Application,” filed on May 8, 2013, published as WIPO publication number WO / 2013 / 169849; and International patent application serial number PCT / US2013 / 069483, entitled “Device, Method, and Graphical User Interface for Transitioning Between TouchInput to Display Output Relationships,” filed on November 11, 2013, published as WIPO publication number WO / 2014 / 105276, each of which is hereby incorporated by reference in its entirety.
[0182] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 500.
[0183] Figure 5B An exemplary personal electronic device 500 is depicted. In some embodiments, the device 500 may include a Figure 1A , Figure 1B and Figure 3 Some or all of the components described. Device 500 has a bus 512 that operatively couples an I / O portion 514 to one or more computer processors 516 and a memory 518. I / O portion 514 may be connected to a display 504, which may have a touch-sensitive component 522 and optionally an intensity sensor 524 (e.g., a contact intensity sensor). In addition, I / O portion 514 may be connected to a communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular and / or other wireless communication technologies. Device 500 may include input mechanisms 506 and / or 508. For example, input mechanism 506 is optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, input mechanism 508 is optionally a button.
[0184] In some examples, input mechanism 508 is optionally a microphone. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, orientation sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and / or combinations thereof, all of which are operably connected to I / O portion 514.
[0185] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described below, including processes 700 and 900 ( Figure 7 and Fig. 9). Computer-readable storage media can be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with instruction execution systems, devices, and apparatuses. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memories such as flash memory, solid-state drives, and the like. Personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other components or additional components in a variety of configurations.
[0186] As used herein, the term "indicative representation" refers to an optional feature of the apparatus 100, 300, and / or 500 ( Figure 1A , Figure 3 and FIG. 5A to FIG. 5B ) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.
[0187] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface that a user is interacting with. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the particular user interface element is adjusted according to the detected input. In the case that a touch-screen display (e.g., Figure 1A A touch-sensitive display system 112 or Figure 4AIn some implementations of the touch screen 112 in FIG. 1 , a contact detected on the touch screen acts as a “focus selector” such that when an input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus moves from one area of the user interface to another area of the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).
[0188] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted off, before or after contact starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the value at the top 10% of the intensity of the contact, the half-maximum value of the intensity of the contact, the 90% maximum value of the intensity of the contact, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation) rather than to determine whether to perform the first operation or the second operation.
[0189] In some embodiments, the computer system is in a locked state or an unlocked state. In a locked state, the computer system is powered on and is operable, but it is prevented from executing 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 the unintentional or unauthorized use of a certain function of the computer system, or to activate or deactivate some functions on the computer system. In some embodiments, in an unlocked state, the computer system is powered on and is operable, and it is not prevented from executing at least a portion of the predefined set of operations that cannot be executed when in a locked state. When the computer system is in a locked state, it is said that the computer system is locked. When the computer system is in an unlocked state, it is said that the computer is unlocked. In some embodiments, the computer system in a locked state optionally responds to a limited set of user inputs, and the limited set of user inputs includes an input corresponding to an attempt to convert the computer system to an unlocked state or an input corresponding to closing the computer system.
[0190] Attention is now turned to embodiments of a user interface ("UI") and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.
[0191] FIG. 6A to FIG. 6AA Illustrated are exemplary user interfaces for initiating communications using a computer system in the event of a crash according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Figure 7 process.
[0192] Fig. 6A Diagram 600 illustrates a collision involving vehicle 602a and vehicle 602b. Computer system 604a (e.g., smart watch) and / or computer system 604b (e.g., smart phone) are located in vehicle 602a at the time of the collision. In some embodiments, computer system 604a and computer system 604b communicate with each other via wireless and / or wired communication (such as, for example, a Wi-Fi network, Bluetooth communication, and / or a near field communication protocol).
[0193] exist Fig. 6AIn the illustrated embodiment, at the time of the collision, 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 desktop) includes application icons that can be selected (e.g., tapped and / or otherwise selected) to open corresponding applications on computer system 604a. User interface 610 (e.g., a home screen or application desktop) includes application icons that can be selected (e.g., tapped and / or otherwise selected) to open corresponding applications on computer system 604b.
[0194] although Fig. 6A Computer system 604a and computer system 604b are illustrated as displaying user interface 608 and user interface 610, respectively, when they collide, but in some embodiments, the techniques described herein are applied when computer system 604a and / or computer system 604b display other user interfaces when they collide, such as, for example, a clock face user interface, a wake-up user interface (e.g., a user interface displayed when the computer system is 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, a web browsing application, a map application, a navigation application, a media playback application, or a settings application). In some embodiments, the techniques described herein are applied when display 606a and / or display 606b is powered off, deactivated, powered off, in a dormant state, in a dimmed state, and / or in a low-power state.
[0195] Computer system 604b displays a network status indicator 605, which includes a cellular status indicator 605a and an Internet status indicator 605b. Cellular status indicator 605a displays an indication of the current state of the connection of computer system 604b to a cellular communication network. For example, the appearance of cellular status indicator 605a can indicate whether computer system 604b is connected to a cellular communication network and / or the signal strength between computer system 604b and the cellular communication network. Internet status indicator 605b displays an indication of an Internet communication network (e.g., a Wi-Fi network, LTE, 3G, 4G, or 5G) that computer system 604b can use to connect to the Internet. For example, the appearance of Internet status indicator 605b can indicate whether a network is available for computer system 604b to connect to the Internet, a network that computer system 604b can use to connect to the Internet (if the Internet communication network is available), and / or the signal strength between computer system 604b and the Internet communication network.
[0196] In some embodiments, computer system 604a can be independently connected to a cellular communication network and / or an Internet communication network (e.g., without computer system 604b) to perform communications. In some embodiments, computer system 604a can be connected to a cellular communication network and / or an Internet communication network via computer system 604b to perform communications (e.g., computer system 604a cannot be independently connected to a cellular communication network and / or an Internet communication network). In some embodiments, computer system 604a displays network status indicator 605, cellular status indicator 605a, and / or Internet status indicator 605b based on the ability of computer system 604a to connect to a cellular communication network and / or an Internet communication network (e.g., independently and / or via computer system 604b).
[0197] exist Fig. 6A In some embodiments, computer system 604a and / or computer system 604b obtains an indication that a collision has been detected. In some embodiments, computer system 604a detects an indication (e.g., motion and / or sound) of a collision and / or determines that a collision has occurred. In some embodiments, computer system 604a transmits data indicating that a collision has occurred to computer system 604b. In some embodiments, computer system 604b detects an indication (e.g., motion and / or sound) of a collision and / or determines that a collision has occurred. In some embodiments, computer system 604b transmits data indicating that a collision has occurred to computer system 604a.
[0198] FIG. 6B to FIG. 6H An exemplary user interface displayed by the computer system 604a after a collision is detected is illustrated in accordance with some embodiments.
[0199] In response to obtaining an indication that a collision has been detected, computer system 604a displays a Figure 6B 6. The collision detection interface 612 is shown. The collision detection interface 612 includes an emergency interface indicator 612a (e.g., "SOS"), a collision detection indicator 612b, a communication option 612c, and a confirmation option 612d. The collision detection indicator 612b includes an indication that a collision has occurred, such as text (e.g., "It looks like you have been in a collision"), a graphic, an animation, a color, and / or a font. In response to detecting a selection 625b of the confirmation option 612d, the computer system 604a stops displaying the collision detection interface 612 (e.g., the computer system 604a returns to the user interface 608).
[0200] Based on (or optionally in response to) determining that the time threshold is met but no input is detected (e.g., no selection of the communication option 612c or selection of the confirmation option 612d is detected), the computer system 604a displays the communication alert 612e, the countdown 612f, and the cancel option 612g, as shown in FIG. Figure 6C As shown. Communication alert 612e indicates that a call to emergency services has been initiated or will be initiated, and countdown 612f indicates the amount of time (e.g., seconds) until the call to emergency services will be placed. Based on (or optionally, in response to) determining that the time threshold is met but no input is detected, computer system 604a outputs a non-visual indication that a call to emergency services has been initiated or will be initiated. For example, in Figure 6C , the computer system 604a outputs a tactile sensation 614 and / or an audio output 616 (eg, “a call is being made to emergency services”).
[0201] In some embodiments, the computer system 604a displays a communication alert 612e, displays a countdown 612f, displays a cancel option 612g, and / or outputs a non-visual indication that a call to emergency services has been or will be initiated based on (or optionally, in response to) determining that a threshold amount of time has passed since obtaining an indication that a collision has been detected (e.g., the collision detection interface 612 has been displayed for a threshold amount of time) but no input has been detected. Outputting a non-visual indication that a call to emergency services has been or will be initiated is particularly helpful in emergency situations such as collisions in which a user may be distracted and / or unable to view the display 606a of the computer system 604a.
[0202] In some embodiments, in response to detecting the selection 625c of the cancel option 612g, the computer system 604a stops or pauses the process of initiating the call to the emergency service. For example, in response to detecting the selection 625c of the cancel option 612g, the computer system 604a stops the countdown 612f and displays the following: Figure 6B or Figure 6H A collision detection interface 612 (eg, displaying a collision detection indicator 612b, a collision detection indicator 612p, and / or a communication option 612c) or user interface 608 is shown.
[0203] In response to determining that the countdown 612f has ended, the computer system 604a initiates (or attempts to initiate) a call to emergency services (e.g., directly or via the computer system 604b). In some embodiments, the computer system 604a initiates (or attempts to initiate) a call to emergency services in response to detecting a selection 625a of the communication option 612c. In some embodiments, selection of the communication option 612c requires moving an element (e.g., the SOS circle in 612c) from a first position (e.g., the left side of 612c) to a predetermined second position (e.g., the right side of 612c), which can help prevent accidental selection of the communication option 612c. For example, in some embodiments, if the element is not moved to the predetermined second position (e.g., not moved far enough to the right), the communication option 612c is not selected. Figure 6B , selection 625a includes a contact on display 606a that moves from left to right over communication option 612c sufficient to select communication option 612c.
[0204] In some embodiments, such as Fig.6D As shown, initiating a call to emergency services includes displaying a call status indicator 612h, a call recipient indicator 612i, an end call option 612j, and a call menu option 612k (e.g., displaying a phone call interface or an interface of a phone application). The call status indicator 612h includes an indication, such as text indicating the current state of the call (e.g., "calling," "trying to connect," or "connecting"), graphics, animations, colors, and / or fonts. The 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 the recipient's initials). In some embodiments, in response to detecting a selection of the end call option 612j (e.g., a tap on the end call option 612j and / or other input selecting the end call option 612j), the computer system 604a ends the call or stops trying to initiate the call. The call menu option 612k, when selected, causes the computer system 604a to display selectable options that, when selected, perform corresponding functions related to the call (eg, mute, display a keyboard, enable / disable a speaker, and / or display contacts).
[0205] In response to establishing a call with the emergency services (e.g., when the emergency services answer the call and / or the call becomes active), the computer system 604a updates the call state indicator 612h (e.g., to "Call Active"), such as Fig. 6E shown.
[0206] In some embodiments, such as Fig. 6EAs shown, when a 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 the situation of the collision. For example, message 618 can indicate that a collision has occurred and include information about the collision, such as one or more people involved in the collision and / or the location of the collision (e.g., "a collision involving John has been detected at Parkway Drive"). In some embodiments, computer system 604a plays message 618 only when a call to emergency services is automatically initiated (e.g., when no user input such as selection of communication option 612c is detected). In the case where the user of computer system 604a cannot provide information (e.g., injured and / or cannot locate computer system 604a) and / or does not know that a call has been issued, playing message 618 when the call is automatically initiated enables computer system 604a to provide information about the collision to emergency services.
[0207] In some embodiments, when the computer system 604a plays the message 618, the computer system 604a displays a stop message option 6121, such as Fig. 6E In some embodiments, displaying the stop message option 6121 includes stopping displaying (e.g., removing) the end call option 612j and / or the call menu option 612k (e.g., replacing the end call option 612j and / or the call menu option 612k with the stop message option 6121).
[0208] In response to detecting the selection 625d of the stop message option 612l, the computer system 604a stops playing the message 618. In some embodiments, in response to detecting the selection 625d of the stop message option 612l, the computer system 604a stops displaying the stop message option 612l and optionally displays (e.g., redisplays) the end call option 612j and / or the call menu option 612k, such as Fig. 6F shown.
[0209] In response to detecting a selection 625f for the end call option 612j, the computer system 604a initiates a process for ending the call with the emergency services. In some embodiments, in response to detecting a selection 625f for the end call option 612j, the computer system 604a ends the call with the emergency services without detecting further input. In some embodiments, in response to detecting a selection 625f for the end call option 612j, the computer system 604a displays a prompt 612m (e.g., "End call?", which prompts the user to confirm whether to end the call with the emergency services while maintaining the call with the emergency services. Together with the prompt 612m, the computer system 604a displays a continue call option 612n for continuing the call with the emergency services and a confirmation option 612o for ending the call with the emergency services. In response to detecting a selection of the continue call option 612n (e.g., a tap on the continue call option 612n and / or other input selecting the continue call option 612n), the computer system 604a continues the call with the emergency services and optionally displays (e.g., returns) as Fig. 6F 612. In response to detecting selection 625f of confirmation option 612n, computer system 604a ends the call with the emergency services.
[0210] In some embodiments, after the call with emergency services is ended (e.g., in response to Fig. 6F Choose 625e or Figure 6G In the selection 625f), the computer system 604a displays an indication that a collision was detected and optionally displays an indication of the device that detected the collision and / or an indication of when the collision was detected. Figure 6H As shown, after ending the call with emergency services, computer system 604a displays a collision detection indicator 612p (e.g., "Phone detected a collision 1 minute ago") that indicates that a collision was detected, that the collision was detected by computer system 604b, and that the collision was detected one minute ago.
[0211] In some embodiments, after the call with emergency services is ended (e.g., in response to Fig. 6F Choose 625e or Figure 6G In the selection 625f), the computer system 604a provides an option to initiate (e.g., re-initiate) communication with emergency services and / or an option to provide information of a user associated with the computer system 604a, which information may be related to the user's medical condition. Figure 6HAs shown, after ending the call with the emergency service, the computer system 604a displays a communication option 612c and a medical ID option 612q. In response to detecting a selection of the communication option 612c (e.g., a tap or swipe on the communication option 612c and / or other input selecting the communication option 612c), the computer system 604a attempts to initiate (e.g., re-initiate) the call to the emergency service. In response to detecting a selection of the medical ID option 612q (e.g., a tap and / or swipe), the computer system 604a displays information of a user associated with the computer system 604a, which may be related to the user's medical condition (e.g., name, age, weight, height, blood type, medications, allergies, medical condition, designated contacts, and / or contact information of designated contacts).
[0212] FIG. 6I to FIG. 6L Illustrate a method for enabling and / or disabling a collision detection feature (such as reference 6A to 6H An exemplary user interface for the features described herein. Fig.6I In the example, the computer system 604a displays the user interface 608. In response to detecting the selection 625g of the settings application icon 608a, the computer system 604a displays the following Figure 6J The settings interface 620 shown. The settings interface 620 includes a menu of items associated with various features, functions and / or applications of the computer system 604a, including an emergency settings option 620a. In response to detecting a selection 625h of the emergency settings option 620a, the computer system 604a displays the following Figure 6K The emergency settings interface 622 is shown. The emergency settings interface 622 includes options associated with various emergency features of the computer system 604a, including a crash detection settings option 622a. The options included in the emergency settings interface 622 include indications (e.g., text and / or graphical representations) of emergency features associated with options (e.g., "press and hold side button" to call emergency services or display an option to call emergency services, "fall detection," and "crash detection") and indications of the status of the features (e.g., enabled or disabled). For example, in Figure 6K , the collision detection setup option 622a includes the text “Collision Detection” indicating the feature associated with the collision detection setup option 622a and the text “Disabled” indicating that the collision detection feature is disabled (eg, off and / or inactive).
[0213] In response to detecting a selection 625i of the collision detection settings option 622a, the computer system 604a displays a user interface for selecting, setting, and / or changing one or more settings and / or parameters associated with a collision detection feature of the computer system 604a. In some embodiments, the collision detection feature of the computer system 604a includes the computer system 604a detecting a collision, determining that a collision has occurred, and / or performing a reference after a collision is detected. FIG. 6B to FIG. 6H The ability to describe features, such as making a call to emergency services (e.g., in response to obtaining an indication that a collision has occurred or has been detected). Figure 6L As shown, in response to detecting a selection 625i for the collision detection setting option 622a, the computer system 604a displays a collision detection setting interface 624, which includes a collision detection state option 624a (e.g., a trigger button and / or switch) and a feature description 624b. The feature description 624b describes the collision detection feature associated with the collision detection setting interface 624 and / or the collision detection setting option 622a (e.g., "If you are in a car collision, the watch can automatically call emergency services. The watch can start a countdown and call emergency services when the countdown expires"). In response to detecting a selection 625j for the collision detection state option 624a, the computer system 604a sets the state of the collision detection feature. For example, in Figure 6L In the example, since the collision detection feature is in a disabled (or off) state, the computer system 604a enables (or turns on) the collision detection feature in response to detecting a selection of the collision detection state option 624a, and optionally changes the appearance of the collision detection state option 624a (e.g., moving the circle to the right of the collision detection state option 624a and / or changing the text "off" to "on").
[0214] Figure 6M to Figure 6Q An exemplary user interface displayed by computer system 604b after a collision is detected according to some embodiments is illustrated. Figure 6M to Figure 6Q The user interface shown in the reference FIG. 6B to FIG. 6H The user interface displayed by the computer system 604a is shown in addition to the user interface described in reference FIG. 6B to FIG. 6H The user interface displayed by the computer system 604a is displayed simultaneously with, or instead of, reference FIG. 6B to FIG. 6H A user interface display is depicted as being displayed by computer system 604a.
[0215] In response to obtaining an indication that a collision has been detected, the computer system 604b displays the following Figure 6MCollision detection interface 626 is shown. Collision detection interface 626 includes response prompt 626a, collision detection indicator 626b, communication option 626c, medical ID option 626e, and close option 626d. Collision detection indicator 626b includes an indication that a collision has occurred, such as text (e.g., "It looks like you have collided"), graphics, animations, colors, and / or fonts (e.g., similar or identical to collision detection indicator 612b).
[0216] The response prompt 626a prompts the user to respond to the information and options displayed in the collision detection interface 626 (e.g., select the communication option 626c, the medical ID option 626e, or the close option 626d), and if the computer system 604b does not detect a response, the user is notified that the computer system 604b will initiate an emergency feature (e.g., initiate an SOS feature and / or automatically call emergency services). In response to detecting a selection of the medical ID option 626e (e.g., a tap and / or a swipe), the computer system 604b displays information of a user associated with the computer system 604a, which may be related to the user's medical condition (e.g., name, age, weight, height, blood type, medications, allergies, medical conditions, designated contacts, and / or contact information for designated contacts). In response to detecting a selection of the close option 626d (e.g., a tap on the close option 626d and / or other input selecting the close option 626d), the computer system 604b stops displaying the collision detection interface 626 and optionally displays (e.g., returns to) the user interface 610.
[0217] Based on (or optionally, in response to) determining that the time threshold is met but no input is detected (e.g., no selection of the communication option 626c or selection of the shutdown option 626d is detected), the computer system 604b displays an emergency communication indicator 626f (e.g., "Emergency SOS"), a communication alert 626h, and a countdown 626g, as shown in FIG. Figure 6N As shown. Communication alert 626h indicates that a call to emergency services has been initiated or will be initiated (e.g., when countdown 626g expires), and countdown 626g indicates the amount of time (e.g., number of seconds) until the call to emergency services will be placed. Based on (or optionally, in response to) determining that the time threshold is met but no input is detected, computer system 604b outputs a non-visual indication that a call to emergency services has been initiated or will be initiated. For example, in Figure 6N , the computer system 604b outputs the above reference Figure 6C A tactile sensation 614 and / or an audio output 616 is depicted (eg, “a call is being made to emergency services”).
[0218] In response to determining that the countdown 626g has ended, the computer system 604b initiates (or attempts to initiate) a call to emergency services. In some embodiments, the computer system 604b initiates (or attempts to initiate) a call to emergency services in response to detecting a call to (e.g., Figure 6M or Figure 6N In some embodiments, such as Fig.6O As shown, initiating a call to emergency services includes displaying a call status indicator 626j, a call recipient indicator 626i, an end call option 626l, and a call management option 626k (e.g., displaying a call user interface or a user interface of a phone application). The call status indicator 626j includes an indication, such as text indicating the current state of the call (e.g., "call", "trying to connect" or "connect"), a graphic, an animation, a color and / or a font. The call recipient indicator 626i 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 the recipient's initials). In some embodiments, in response to detecting a selection of the end call option 626l (e.g., a tap on the end call option 626l and / or other input selecting the end call option 626l), the computer system 604b ends the call or stops trying to initiate the call. The call management options 626k include selectable options for activating corresponding features related to the call (e.g., mute, display keypad, enable / disable speaker, add call, initiate video call, and / or display contacts).
[0219] In response to establishing a call with the emergency services (e.g., when the emergency services answer the call and / or the call becomes active), the computer system 604b updates the call status indicator 626j (e.g., to "Call Active") and displays the collision detection indicator 626m, such as Figure 6P shown.
[0220] In some embodiments, such as Figure 6P As shown, when a call to emergency services is established, computer system 604b plays message 618 on the call to emergency services, as described above with reference to Fig. 6E In some embodiments, computer system 604b plays message 618 only when a call to emergency services is automatically initiated (e.g., without detecting a user input such as a selection of communication option 626c). Playing message 618 when a call is automatically initiated enables computer system 604b to provide information about the collision to emergency services in the event that the user of computer system 604b is unable to provide information (e.g., injured and / or unable to locate computer system 604b) and / or is unaware that a call has been placed.
[0221] In some embodiments, when the computer system 604b plays the message 618, the computer system 604b displays a stop message option 626n, such as Figure 6P In some embodiments, displaying the stop message option 626n includes stopping displaying (eg, removing) the call management option 626k (eg, replacing the call management option 626k with the stop message option 626n).
[0222] In response to detecting the selection 625s of the stop message option 626n, the computer system 604b stops playing the message 618. In some embodiments, in response to detecting the selection 625s of the stop message option 626n, the computer system 604b stops displaying the stop message option 626n and optionally displays (e.g., redisplays) the call management option 626k, such as Fig.6O shown.
[0223] In response to detecting selection 625t of end call option 626l, computer system 604b initiates a process for ending the call with emergency services. In some embodiments, in response to detecting selection 625t of end call option 626l, computer system 604b ends the call with emergency services without detecting further input. In some embodiments, in response to detecting selection 625t of end call option 626l, computer system 604b displays a prompt (e.g., prompt 612m) to the user to confirm whether to end the call with emergency services and options for continuing the call with emergency services (e.g., continue call option 612n) and / or ending the call with emergency services (e.g., confirm option 612o).
[0224] In some embodiments, after the call with emergency services is ended (e.g., in response to a Fig.6O or Figure 6P In response to selecting the End Call option 6261 in the call, the computer system 604b displays an indication that a collision was detected and optionally displays an indication of the device that detected the collision and / or an indication of when the collision was detected. Figure 6Q As shown, after ending the call with emergency services, computer system 604b displays contextual indicator 626o (e.g., "Phone detected a collision 1 minute ago") that indicates that a collision was detected, that the collision was detected by computer system 604b, and that the collision was detected one minute ago.
[0225] In some embodiments, after the call with emergency services is ended (e.g., in response to a Fig.6O or Figure 6PIn response to selecting the end call option 6261 in the call, the computer system 604b provides an option to initiate (e.g., re-initiate) communication with the emergency services and / or provide information about a user associated with the computer system 604b, which may be related to the user's medical condition (e.g., name, age, weight, height, blood type, medications, allergies, medical condition, designated contact, and / or contact information for the designated contact). For example, Figure 6Q As shown, after ending the call with the emergency service, the computer system 604b displays a communication option 626c and a medical ID option 626e. In response to detecting a selection of the communication option 626c (e.g., a tap and / or swipe on the communication option 626c), the computer system 604b attempts to initiate (e.g., re-initiate) the call to the emergency service. In response to detecting a selection of the medical ID option 626e (e.g., a tap and / or swipe on the medical ID option 626e), the computer system 604b displays information of a user associated with the computer system 604b, which may be related to the user's medical condition (e.g., name, age, weight, height, blood type, medications, allergies, medical condition, designated contacts, and / or contact information for designated contacts).
[0226] Figure 6R to Figure 6U Illustrate a method for enabling and / or disabling a collision detection feature (such as reference 6A to 6H Features described and / or referenced Figure 6M to Figure 6Q An exemplary user interface for the features described herein. Figure 6R 6, computer system 604b displays a settings interface 628. Settings interface 628 includes a menu of items associated with various features, functions, and / or applications of computer system 604b, including an emergency settings option 628a.
[0227] In response to detecting selection 625k of emergency setup option 628a, computer system 604b displays the following Figure 6S The emergency settings interface 630 is shown. The emergency settings interface 630 includes options associated with various emergency features of the computer system 604b, including a collision detection feature. In some embodiments, the collision detection feature of the computer system 604b includes the computer system 604a detecting a collision, determining that a collision has occurred, and / or performing a reference after a collision is detected. FIG. 6B to FIG. 6H The capabilities of the described features, such as making a call to emergency services (e.g., in response to obtaining an indication that a collision has occurred or has been detected).
[0228] The emergency settings interface 630 includes options for selecting, setting, and / or changing one or more settings and / or parameters associated with the emergency features of the computer system 604b. Figure 6S, the emergency settings interface 630 includes the text "Car Crash Detection" and "Call After Car Crash" to indicate the collision detection feature and the post-crash call state option 630a (e.g., a trigger button and / or switch) and a feature description 630b. The feature description 630b describes the collision detection feature associated with the post-crash call state option 630a (e.g., "If you are in a car collision, the phone will automatically call emergency services. An alarm will sound before the call.").
[0229] In response to detecting the selection 6251 of the post-crash call state option 630a, the computer system 604b sets the state of the collision detection feature (or post-crash call feature). Figure 6S In the embodiment, since the collision detection feature is in an enabled (or on) state, the computer system 604b disables (or turns off) the collision detection feature in response to detecting a selection of the post-collision call status option 630a, and optionally changes the appearance of the post-collision call status option 630a (e.g., moves the circle to the left of the post-collision call status option 630a).
[0230] In some embodiments, computer system 604b may share data about detected collisions (also referred to as "collision data") with applications on computer system 604b (e.g., native applications or third-party applications). Figure 6S In the example of FIG. 6 , the emergency settings interface 630 includes a crash data sharing option 630c that is associated with a setting for sharing crash data with an application. In response to detecting a selection 625m of the crash data sharing option 630c, the computer system 604b displays Figure 6T The crash data sharing settings interface 632 shown in FIG. The crash data sharing settings interface 632 includes a sharing state option 632a. The sharing state option 632a can be selected to set, change or select the state of the ability of the computer system 604b to share crash data with the application.
[0231] exist Figure 6T, the ability of the computer system 604b to share collision data with applications is enabled (e.g., turned on). When the ability of the computer system 604b to share collision data with applications is enabled, the collision data sharing settings interface 632 includes an application menu 632b, which includes a collection (e.g., a list) of application options 632b1, 632b2, and 632b3 of corresponding applications with which the computer system 604b can share collision data. The check mark in the application option 632b1 indicates that the computer system 604b is configured to share collision data with an application referred to as a "partner system" when a collision is detected. In some embodiments, in response to a selection of an application option (e.g., a tap on the application option or other input to select the application option), if a collision is detected, the computer system 604b selects the corresponding application to share collision data with it. For example, in response to detecting a 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 collision data with an application named "Quick System Response" and optionally visually indicate that application option 632b2 is selected (e.g., displaying a check mark to the right of application option 632b2). In some embodiments, computer system 604b is configured to (or is capable of) sharing collision data only with a single application. For example, in response to detecting a selection of an application option other than a currently designated application option, computer system 604b deselects the currently designated application option and designates the selected application option.
[0232] In response to detecting Figure 6T In the sharing state option 632a of the selection 625n, because the ability to share collision data with the application is enabled, the computer system 604b disables the ability to share collision data with the application. In some embodiments, such as Figure 6U As shown in , when the ability to share crash data with applications is disabled, the crash data sharing settings interface 632 does not display the application menu 632b (eg, the computer system 604b removes the display of the application menu 632b in response to the ability to share crash data with applications being disabled).
[0233] Figure 6V to Figure 6W An exemplary user interface is illustrated for granting or denying a request by an application to receive collision data from computer system 604b (eg, a request for computer system 604b to share collision data with an application when a collision is detected). Figure 6V, the computer system 604b displays an application installation confirmation interface 634 corresponding to the application called the buddy system. In some embodiments, the computer system 604b displays the application installation confirmation interface 634 in response to a request (e.g., a user request or a system request) to install the corresponding application. The application installation confirmation interface 634 includes an application identifier 634a, an installation option 634b, and a rejection option 634c. The application identifier 634a indicates the application being requested to be installed. In response to detecting a selection of the rejection option 634c (e.g., a tap on the rejection option 634c and / or other input selecting the rejection option 634c), the computer system 604b does not install the application. In response to detecting a selection 625o of the installation option 634b, the computer system 604b continues the process of installing the application.
[0234] In some embodiments, the process of installing an application includes a request from the application being installed to access collision data (e.g., causing the computer system 604b to share collision data with the application being installed). In response to receiving the request to access collision data, the computer system 604b prompts the user to grant or deny the request to access collision data. For example, in response to receiving the request to access collision data, the computer system 604b displays Figure 6W 634d shown in . Prompt 634d includes description 634e, grant option 634f and reject option 634g. Description 634e describes what the user is prompted to do. In response to selection of reject option 634g (e.g., a tap on reject option 634g and / or other input selecting reject option 634g), computer system 604b does not configure computer system 604b to be able to share collision data with the application being installed. For example, if reject option 634g is selected, the application being installed is not displayed in application menu 632b. In response to detecting selection of grant option 634f (e.g., a tap on grant option 634f and / or other input selecting grant option 634f), computer system 604b is configured to share collision data with the application being installed (e.g., display the application being installed in application menu 632b). In some embodiments, in response to detecting selection of the allow option 634f, the computer system 604b designates the application being installed as the application with which the collision data will be shared if a collision is detected (eg, deselecting a previously designated application).
[0235] In some embodiments, the computer system 604b performs a setup process that includes displaying a set of one or more user interfaces that inform the user of the features available on the computer system 604b. In some embodiments, the setup process is performed when the computer system 604b is initially turned on, when the computer system 604b is used for the first time after an upgrade (e.g., a software and / or operating system upgrade), and / or when the computer system is used for the first time after a reset.
[0236] Figure 6X An exemplary security feature interface 636 displayed during the setup process is illustrated. The security feature interface 636 includes a list of security features available on the computer system 604b, including a collision detection option 636a corresponding to the collision detection feature described herein. In some embodiments, in response to detecting a selection of the collision detection option 636a (e.g., a tap on the collision detection option 636a and / or other input selecting the collision detection option 636a), the computer system 604b displays a reference Figure 6S The emergency setting interface 630 described or referenced Figure 6Z A collision detection interface 640 is described.
[0237] Figure 6Y An exemplary health checklist interface 638 displayed during the setup process is illustrated. In some embodiments, the computer system 604b displays the health checklist interface 638 in response to detecting a selection 625u of the continue option 636b in the safety feature interface 636. The health checklist interface 638 displays information and / or options for features related to the user's health. For example, the health checklist interface 638 includes a collision detection element 638a, a description 638b describing that emergency services will be called if a collision is detected, and a device indicator 638c. The feature status indicator 638e indicates that the collision detection feature represented by the collision detection element 638a is active (e.g., enabled and / or turned on). The device indicator 638c includes a representation (e.g., text and / or image) of one or more devices that are capable of detecting a collision and / or initiating a call to emergency services after a collision is detected (if enabled to do so). In Figure 6Y , device indicator 638c indicates that the watch (eg, computer system 604a) and the phone (eg, computer system 604b) can be enabled to detect a collision and / or initiate a call to emergency services after a collision is detected.
[0238] In response to detecting the selection 625p of the collision detection element 638a, the computer system 604b displays a collision detection interface 640, such as Figure 6ZAs shown. The collision detection interface 640 includes a description 640a of the collision detection feature (e.g., "If you are in a collision, the watch and phone can call emergency services if you need help"), a post-collision call state option 640b, and a device capability indicator 640c. The post-collision call state option 640b indicates that the ability to detect a collision and / or initiate a call to emergency services after a collision is detected is enabled. The description 640a indicates that the computer system 604a (e.g., the watch) and the computer system 604b (e.g., the phone) can call emergency services, and the device capability indicator 640c indicates that the computer system 604a (e.g., the watch) cannot detect all collisions.
[0239] In response to detecting selection 625q of post-crash call status option 640b, computer system 604b disables the ability to detect a crash and / or call emergency services after a crash is detected. After disabling the ability to detect a crash and / or call emergency services after a crash is detected, computer system 604b detects selection 625r of finish option 640d. In response to detecting selection 625r of finish option 640d, computer system 604b displays (e.g., returns to) health checklist interface 638, such as Figure 6AA As shown in Figure 6AA , because the ability to detect a collision and / or call emergency services after a collision is detected is disabled, computer system 604b does not display feature status indicator 638e (or, optionally, displays feature status indicator 638e having a status such as "inactive" or "disabled"), and description 638b reflects that emergency services can (e.g., as opposed to "will") be called. Device indicator 638c indicates that the watch (e.g., computer system 604a) and phone (e.g., computer system 604b) can be enabled to detect a collision and / or initiate a call to emergency services after a collision is detected. Because the ability to detect a collision and / or call emergency services after a collision is detected is disabled, computer system 604b displays (e.g., in collision detection element 638a) an enable option 638d for enabling the ability to detect a collision and / or call emergency services after a collision is detected. In some embodiments, the computer system 604b enables the ability to detect a collision and / or call emergency services after a collision is detected in response to detecting a selection of the enable option 638d (e.g., a tap on the enable option 638d and / or other input selecting the enable option 638d). In some embodiments, the computer system 604b displays a collision detection interface 640 in response to detecting a selection of the enable option 638d, wherein the post-collision call state option 640b indicates that the ability to detect a collision and / or call emergency services after a collision is detected is disabled (e.g., the post-collision call state option 640b is in an off state).
[0240] Figure 7 1 is a flowchart illustrating a method for initiating communication using a computer system in a collision event according to some embodiments. Method 700 is performed at a computer system (e.g., 100, 300, 500, 604a, 604b, a smart phone, a smart watch, 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)), which communicates (e.g., includes and / or is connected) with 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., 606a, 606b, a touch-sensitive surface, a keyboard, a mouse, a trackpad, a joystick, a remote control, a microphone, one or more optical sensors for detecting gestures, one or more capacitive sensors for detecting hovering inputs, an accelerometer, a gyroscope, and / or an inertial measurement unit). Some operations in method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.
[0241] As described below, method 700 provides an intuitive way to initiate communication in a crash event. The method reduces the cognitive burden on a user to initiate communication in a crash event, thereby creating a more efficient human-machine interface. For battery-powered computing devices, enabling a user to initiate communication faster and more efficiently in a crash event saves power and increases the time interval between battery charges.
[0242] The computer system acquires ( 702 ) (e.g., receives or detects) information indicative of a collision (e.g., a crash, accident, and / or impact involving a vehicle such as, for example, a car, truck, motorcycle, scooter, bus, bicycle, boat, train, airplane, wheelchair, golf cart, or all-terrain vehicle (ATV); Fig. 6AIn some embodiments, obtaining data indicating that a collision has occurred includes detecting a collision and / or determining that a collision has occurred (e.g., based on detected motion, parameters, and / or conditions). In some embodiments, detecting a collision includes detecting (e.g., via one or more sensors, such as motion sensors, accelerometers, gyroscopes, inertial measurement units, biometric sensors, and / or microphones) motion (e.g., linear and / or angular velocity and / or linear and / or angular acceleration), sound, biometric parameters (e.g., blood pressure, blood oxygen level, pulse, and / or heart rate), and / or other parameters or conditions. In some embodiments, determining that a collision has occurred includes determining that the detected parameters or conditions satisfy a set of collision criteria (e.g., motion thresholds, motion curves, velocity thresholds, velocity curves, acceleration thresholds, acceleration curves, blood pressure thresholds, blood oxygen thresholds, pulse thresholds, heart rate thresholds, sound curves, sound amplitude thresholds, sound frequencies, and / or sound frequency ranges). In some embodiments, a computer system detects a collision (e.g., using a sensor of a computer system; the collision is detected by a computer system). In some embodiments, the computer system determines that a collision has occurred. In some embodiments, one or more external devices (e.g., one or more remote sensors, servers, and / or computer systems) that are not part of a computer system (e.g., one or more remote devices) detect a collision and / or determine that a collision has occurred. In some embodiments, one or more external devices that detect a collision and / or determine that a collision has occurred transmit data indicating that a collision has occurred to the computer system and / or to a remote server. In some embodiments, obtaining data indicating that a collision has occurred includes receiving data indicating that a collision has occurred (e.g., from a remote server and / or from one or more remote devices that detect and / or determine that a collision has occurred). In some embodiments, the computer system cannot detect a collision and / or determine that a collision has occurred. In some embodiments, the computer system communicates (e.g., wired communication, wireless communication, Bluetooth communication, near field communication, and / or Wi-Fi communication) with an external computer system (e.g., a smart phone, a smart watch, a tablet computer, one or more sensors of a vehicle, and / or a computer system of a vehicle) that can detect a collision and / or determine that a collision has occurred. In some embodiments, the computer system obtains (e.g., receives or retrieves) data indicating that a collision has occurred from an external computer system.
[0243] In response to obtaining data indicating that a collision has occurred, the computer system displays (704) a call option (e.g., 612c, 626c, a selectable call option, an icon, a button, an affordance, and / or a user-interactive graphical user interface object) via a display generation component. In some embodiments, the computer system initiates display of the call option in response to obtaining data indicating that a collision has occurred (e.g., the call option was not provided, displayed, and / or available prior to obtaining data indicating that a collision has occurred). Based on determining that a call option (e.g., 612c or 626c) has been selected via one or more input devices (e.g., in response to detecting a selection of the call option, such as selection 625a), the computer system initiates (706) a process of calling a predetermined number (or contactable entity, such as a person, service, or business) associated with the call option. In some embodiments, the call option includes (e.g., is) a graphical object that moves (e.g., slides) in accordance with movement of an input (e.g., a slide or touch and drag input). In some embodiments, the selection of the call option requires moving the graphical object (e.g., on the display) by a predetermined amount and / or to a predetermined position (e.g., from a first position such as a first position and / or a first orientation to a second position such as a predefined position and / or a predefined orientation). In some embodiments, the selection of the call option requires moving the graphical object from a first position on a predefined area or path (such as a first side, left side, top side, or upper side) to a second position on a predefined area or path (such as an opposite side, right side, bottom side, or lower side). In some embodiments, in response to detecting the selection of the call option, the computer system immediately (e.g., without a predetermined delay and / or countdown) and / or automatically initiates a call to a predetermined number without further input (e.g., without confirmation). In some embodiments, in response to detecting the selection of the call option, the computer system initiates a call to a predetermined number and displays a call user interface (e.g., without displaying an intermediate or intervening user interface). In some embodiments, the call option is associated with an emergency service, an emergency number, and / or an emergency contact (e.g., a contactable user designated as an emergency contact). Examples of numbers associated with emergency services include 911 in the United States, 999 in the United Kingdom, 112 in Europe, 110 and / or 119 in Japan, and 000 in Australia. Displaying a call option to initiate a process of calling a predetermined number in response to acquiring data indicating that a collision has occurred, which automatically provides the user with the option of contacting the predetermined number in the event of a collision, which makes it easier and faster to contact the predetermined number with less input and reduces the chance of error, particularly in emergency situations, which provides improved feedback to the user, reduces the number of inputs required to perform an operation, provides additional control options without cluttering the user interface with additional displayed controls, and performs an operation without requiring further user input when a set of conditions have been met.Providing quick and efficient access to predetermined numbers enables the computer system to be controlled more quickly and efficiently, which is particularly important in emergency situations and / or when a crash has occurred because the user may be stressed and more prone to error.
[0244] In some embodiments, after (e.g., in response to) acquiring data indicating that a collision has occurred, the computer system provides (e.g., displays and / or outputs) an indication that a collision has been detected (e.g., 612b, 614, 612e, 612p, 626b, text, audio output, and / or tactile output). In some embodiments, the computer system provides the indication that a collision has been detected while displaying the call option. In some embodiments, after (e.g., in response to) acquiring data indicating that a collision has occurred, the computer system displays a cancel option (e.g., a selectable cancel option, an icon, a button, an affordance, and / or a user-interactive graphical user interface object), for example, simultaneously with the call option, and optionally, while simultaneously providing an indication that a collision has been detected. In response to detecting a selection of the cancel option, the computer system stops displaying the call option, stops attempting to call the predetermined number, and / or stops providing an indication that a collision has been detected. Providing an indication that a collision has been detected notifies the user that the computer system has detected a collision and operates accordingly, so that the user does not make additional unnecessary inputs, which provides improved feedback to the user and reduces the number of inputs required to perform an operation. Providing quick and efficient access to the corresponding numbers enables the computer system to be controlled more quickly and more efficiently, which is particularly important in emergency situations because users may be stressed and more prone to errors.
[0245] In some embodiments, in the absence of detecting a selection of the call option, after acquiring data indicating that a collision has occurred, based on determining that a first threshold (e.g., non-zero) amount of time has passed (e.g., since acquiring data indicating that a collision has occurred or since initiating display of the call option) (and optionally, the call option has not been selected), in the absence of detecting a selection of the call option, the computer system initiates a call to a predetermined number associated with the call option. In some embodiments, the first threshold amount of time is, for example, 5 seconds, 10 seconds, 15 seconds, 30 seconds, or one minute. In some embodiments, the computer system automatically initiates a call to a predetermined number associated with the call option at a first predetermined time after acquiring data indicating that a collision has occurred (e.g., a non-zero amount of time after acquiring data indicating that a collision has occurred, such as 5 seconds, 10 seconds, 15 seconds, 30 seconds, or one minute). Based on determining that a threshold amount of time has passed, without detecting a selection of a call option, initiating a call to a predetermined number, which automatically initiates communication with the predetermined number without requiring feedback or input from a user, which provides improved feedback to the user, reduces the amount of input required to perform an operation, and performs an operation without requiring further user input when a set of conditions have been met.
[0246] In some embodiments, after acquiring data indicating that a collision has occurred (and before initiating a call to a predetermined number associated with the call option if selection of the call option is not detected): based on determining that a second threshold (e.g., non-zero) amount of time has passed (e.g., since acquiring data indicating that a collision has occurred or since display of the call option was initiated) (and optionally, the call option has not yet been selected), without detecting selection of the call option, the computer system begins a countdown (e.g., 612f and / or 626g) for initiating a call to the predetermined number associated with the call option, wherein the second threshold amount of time is less than (e.g., less than 3 seconds, less than 5 seconds, less than 10 seconds, or less than 30 seconds) a first threshold amount of time, and wherein the first threshold amount of time has passed when the countdown expires. In some embodiments, the second threshold amount of time is, for example, 5 seconds, 10 seconds, 15 seconds, 30 seconds, or one minute). In some embodiments, when the countdown expires, the computer system automatically initiates a call to the predetermined number associated with the call option. In some embodiments, after acquiring data indicating that a collision has occurred and based on determining that a second threshold amount of time has passed, the computer system provides a tactile notification that a call to a predetermined number associated with the call option will be initiated without detecting a selection of the call option and / or provides audio indicating that a call to a predetermined number associated with the call option will be initiated without detecting a selection of the call option (e.g., an audio message announcing that a call to a predetermined number associated with the call option will be initiated without detecting a selection of the call option). If, for example, the user is unable to locate or use the computer system after a collision has occurred, a countdown for initiating a call to the predetermined number is started based on determining that the second threshold amount of time has passed, which enables the computer system to automatically initiate communication with the predetermined number, which provides improved feedback to the user, reduces the number of inputs required to perform an operation, and performs an operation without further user input when a set of conditions have been met.
[0247] In some embodiments, after initiating a call to a predetermined number associated with a call option without detecting a selection of the call option (e.g., after automatically initiating a call to a predetermined number due to not receiving user input such as a selection of the call option or user input confirming that the user is fine (e.g., selection of an "I'm fine" option) or does not want to call the predetermined number (e.g., selection of a cancel option)): after establishing a call to the predetermined number in response to initiating a call to the predetermined number associated with the call option without detecting a selection of the call option (e.g., when the call is answered), the computer system outputs (e.g., plays) an audio message (e.g., 618, a predetermined audio message, a voice message, and / or a recorded audio message) indicating that a collision has been detected. In some embodiments, when the call is made automatically (e.g., without a response from a user of the computer system), the computer system plays a recorded message. In some embodiments, the audio message includes information about the collision, such as that the collision was detected, the location of the collision, the time of the collision, and / or the persons involved in the collision. In some embodiments, when the audio message is output, 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. If, for example, a user of the computer system is unable to communicate or locate the computer system after a collision occurs, an audio message indicating that a collision has been detected is output, which notifies the recipient of the call of the situation, which reduces the number of inputs required to perform the operation.
[0248] In some embodiments, after acquiring data indicating that a collision has occurred, the computer system transmits a communication (e.g., a text message and / or an 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., in response to Figure 6G In some embodiments, the computer system automatically transmits the communication (e.g., without user input) when the call to the predetermined number ends (e.g., in response to determining that the call has ended). Transmitting the communication to the designated contact after acquiring data indicating that a collision has occurred enables the computer system to automatically notify the contact, for example, that the user has designated a contact in an emergency, which reduces the number of inputs required to perform the operation.
[0249] In some embodiments, in response to determining that the call to the predetermined number has ended (and optionally, based on determining that the call to the predetermined number was automatically initiated (e.g., without user input, such as selection of a call option)), the computer system displays an indication that a collision was detected (e.g., 612p, 626b, 626o, text and / or graphics). In some embodiments, the indication that a collision was detected includes an indication (e.g., text and / or graphics) of a device (e.g., the computer system or an external computer system in communication with the computer system) that detected the collision. In some embodiments, the computer system causes an indication that a collision was detected to be displayed on an external computer system (e.g., a device in communication with the computer system, such as a smart watch or smart phone paired with the computer system (e.g., with a dedicated communication channel)). Displaying an indication that a collision was detected in response to determining that the call to the predetermined number has ended notifies the user that the computer system has detected a collision and operates accordingly to prevent the user from making additional unnecessary or incorrect inputs, which provides improved feedback to the user and reduces the number of inputs required to perform an operation.
[0250] In some embodiments, displaying an indication that a collision was detected includes displaying an indication of the time when the collision was detected (e.g., "1 minute ago" of 612p, "1 minute ago" of 626o, an absolute time such as 1:35, or a relative time such as 15 minutes ago). In the case where the user is unconscious for a period of time after the collision, displaying an indication of the time when the collision was detected notifies the user when the collision occurred to prevent the user from performing additional unnecessary operations on incorrect inputs, which provides improved feedback to the user and reduces the number of inputs required to perform operations.
[0251] In some embodiments, after acquiring data indicating that a collision has occurred: in response to determining that the call to the predetermined number has ended (and optionally in accordance with determining that the call to the predetermined number was automatically initiated (e.g., without user input, such as selection of a call option)), the computer system displays a second call option (e.g., Figure 6H 612c, Figure 6Q626c, selectable call options, icons, buttons, affordances, and / or user interactive graphical user interface objects), the second call option, when selected, causes the computer system to initiate a process of calling a predetermined number. In some embodiments, the computer system causes the option of calling the predetermined number to be displayed on an external computer system (e.g., a device that communicates with the computer system, such as a smart watch or smart phone that is paired with the computer system (e.g., with a dedicated communication channel)). In some embodiments, the option of calling the predetermined number is displayed by the computer system and the external computer system. Displaying the option of calling the predetermined number in response to determining that the call to the predetermined number has ended enables the user to quickly and easily re-initiate communication with the predetermined number in the event that the initial call is accidentally disconnected or ended, which reduces the number of inputs required to perform the operation.
[0252] In some embodiments, after acquiring data indicating that a collision has occurred: in response to determining that the call to the predetermined number has ended (and optionally based on determining that the call to the predetermined number was automatically initiated (e.g., without user input, such as selection of a call option)), the computer system displays a medical ID option (e.g., Figure 6H 612q in Figure 6Q 626e, a selectable option, an icon, a button, an affordance, and / or a user interactive graphical user interface object), the medical ID option, when selected, causes the computer system to display information of a user associated with the computer system. In some embodiments, the user's information includes the user's name, the user's age, the user's weight, the user's height, a designated contact (e.g., the name of an emergency contact), and / or contact information (e.g., a phone number) of a designated contact. In some embodiments, the computer system causes the medical ID option to be displayed on an external computer system (e.g., a device communicating with the computer system, such as a smart watch or smart phone paired with the computer system (e.g., with a dedicated communication channel). In some embodiments, the medical ID option is displayed by the computer system and the external computer system. Displaying the medical ID option in response to determining that a call to a predetermined number has ended enables the user of the computer system to quickly and easily display the user's information to the responder of the collision, or enables the responder to access the user's information when the user is unable to do so, which provides improved feedback to the user and reduces the number of inputs required to perform an operation.
[0253] In some embodiments, after acquiring data indicating that a collision has occurred, the computer system disables a voice assistance function on the computer system (e.g., disabling the voice assistance function in the following figure: FIG. 6B to FIG. 6H . FIG. 6D to FIG. 6H , FIG. 6B to FIG. 6G , FIG. 6D to FIG. 6G , Figure 6M to Figure 6Q or FIG. 6O to FIG. 6Q ). In some embodiments, the computer system disables the voice assistance function in response to obtaining data indicating that a collision has occurred. In some embodiments, the computer system disables the voice assistance function in response to determining that a call to a predetermined number has been initiated (e.g., automatically or manually). In some embodiments, the computer system enables (or re-enables) the voice assistance function when the call to the predetermined number ends or when the user interface associated with the collision or the option to notify contacting emergency services is no longer displayed. Disabling the voice assistance function on the computer system after obtaining data indicating that a collision has occurred prevents unintentional and incorrect input to the voice assistance after a collision when there is a high likelihood of confusion, noise, and other people who may interrupt the voice assistance function, which reduces the number of inputs required to perform operations and reduces errors.
[0254] In some embodiments, after initiating (e.g., automatically or manually) a call with a 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, without ending the call with the predetermined number, the computer system displays an option (e.g., 612m, 612o, prompt, selectable option, icon, button, affordance and / or user interactive graphical user interface object) to confirm the request to end the call with the predetermined number, which option, when selected, causes the computer system to end the call with the predetermined number. In some embodiments, the computer system simultaneously displays an 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., continue the call with the predetermined number). In some embodiments, in response to a request to exit a collision detection user interface (e.g., a user interface displayed in response to obtaining data indicating that a collision has occurred), the computer system displays an option to confirm the request to exit the collision detection user interface without exiting the collision detection user interface, which option, when selected, causes the computer system to exit (e.g., stop displaying) the collision detection user interface. Without ending the call, an option is displayed to confirm the request to end the call, which prevents the user from inadvertently ending the call prematurely and having to provide additional input to re-initiate the call, which provides improved feedback to the user, reduces the number of inputs required to perform operations, and reduces errors.
[0255] In some embodiments, the computer system displays an enable collision detection option (e.g., 624a, 630a, 640b, a trigger button, a switch, an affordance, and / or a user-interactive graphical object) that, when selected, sets the state of a capability (e.g., enabled, disabled, turned on, or turned off) of a computer system or an external computer system to display a call option in response to obtaining data indicating that a collision has occurred. In some embodiments, when the state of the capability to display the call option is in a first state, in response to detecting an input selecting the enable collision detection option, the computer system sets the capability to display the call option to a second state different from the first state; and when the state of the capability to display the call option is in a second state, in response to detecting an input selecting the enable collision detection option, the computer system sets the capability to display the call option to the first state; in some embodiments, based on determining that the capability to display the call option is in the first state (e.g., enabled or turned on), the call option is displayed in response to obtaining data indicating that a collision has occurred. In some embodiments, in response to obtaining data indicating that a collision has occurred, the computer system abandons displaying the call option based on determining that the capability to display the call option is in a second state different from the first state (e.g., disabled, not enabled, or turned off). In some embodiments, the enable collision detection option is displayed on an external computer system (e.g., a device that communicates with the computer system, such as a smart watch or smart phone that is paired with the computer system (e.g., with a dedicated communication channel). In some embodiments, the enable collision detection option is displayed on the external computer system in a companion application that provides selectable options for selecting settings and / or operating parameters of the computer system. In some embodiments, the enable collision detection option is displayed during an initialization or onboarding process (e.g., at the computer system or an external computer system that is configured to communicate with the computer system). In some embodiments, the enable collision detection option is displayed as part of a process of presenting security features of the computer system and / or an external computer system that communicates with the computer system. In some embodiments, the enable collision detection option is not displayed if the computer system cannot detect that a collision has occurred (e.g., even if the computer system is able to display a call option in response to obtaining data indicating that a collision detected by the external computer system has occurred). In some embodiments, the state (e.g., enabled or disabled) of the computer system's ability to display call options in response to obtaining data indicating that a collision has occurred is set based on the state of a capability of another (e.g., external) computer system (e.g., mirroring the state of the capability between devices). In response to obtaining data indicating that a collision has occurred, an option to set the state of the ability to display call options is displayed, which provides a user with a quick and efficient method to enable or disable the capability, which reduces the number of inputs required to perform the operation.
[0256] In some embodiments, the computer system displays a user interface (e.g., 638 and / or 640) of a health application that includes information associated with the user's health (e.g., activity data, physical examination, cycle data, hearing data, heart data, consciousness data, mobility data, nutrition data, respiratory data, sleep data, health symptoms, vital data, and / or health records), wherein displaying an enable collision detection option (e.g., 640b) includes displaying an enable collision detection option in the user interface of the health application (e.g., as part of a checklist of health-related items, such as a sequence of information, options, features, and / or user interfaces associated with health-related items). In some embodiments, the user interface of the health application includes an option that, when selected, displays a set of options related to detecting collisions, including an enable collision detection option. In some embodiments, the set of options related to detecting collisions is a subset of a set of options related to emergency features (e.g., options for an emergency SOS feature available in an emergency feature menu, including an enable collision detection option). Displaying an enable collision detection option in the user interface of the health application notifies the user of the collision detection capability in relevant locations and provides the user with a quick and efficient method to enable or disable the capability, which provides improved feedback to the user and reduces the number of inputs required to perform operations.
[0257] In some embodiments, the enable collision detection option, when selected, enables the computer system's ability to display a call option in response to obtaining data indicating that a collision has occurred, without enabling the second computer system's ability to display a call option in response to obtaining data indicating that a collision has occurred (e.g., 624a controls the ability of computer system 604a, but not the ability of computer system 604b; and / or 630a controls the ability of computer system 604b, but not the ability of computer system 604a). In some embodiments, the computer system displays a second enable collision detection option, which, when selected, enables the external computer system's ability to display a call option in response to obtaining data indicating that a collision has occurred (e.g., the computer system simultaneously displays a device-specific option for enabling the ability to display a call option in response to obtaining data indicating that a collision has occurred). In some embodiments, the computer system displays the state of the ability to display a call option in response to obtaining data indicating that a collision has occurred of a first device (e.g., the computer system), and optionally, simultaneously displays the state of the ability to display a call option in response to obtaining data indicating that a collision has occurred of a second device (e.g., an external device) different from the first device (e.g., the computer system displays the state of the collision detection capability through the device). Enabling the ability of a computer system to display a call option in response to obtaining data indicating that a collision has occurred, while not enabling the ability of a second computer system to display a call option in response to obtaining data indicating that a collision has occurred, provides the user with greater control over the collision detection function and reduces erroneous changes, which provides the user with improved feedback and reduces the number of inputs required to perform operations.
[0258] In some embodiments, after acquiring data indicating that a collision has occurred, the computer system sends a request to an application (e.g., Figure 6TIn some embodiments, the data associated with the collision include data indicating that a collision has occurred, the time of the collision, the location of the collision, and / or the people involved in the collision. In some embodiments, in response to an application (e.g., a third-party application) requesting to be provided with data associated with the collision in the case of determining that a collision has occurred, the computer system displays an option to grant or deny the application access to data associated with the collision (e.g., provide or not provide data associated with the collision in the case of determining that a collision has occurred). In some embodiments, the computer system provides data associated with the collision to the application (e.g., a third-party application), even if the computer system's ability to display the call option in response to obtaining data indicating that a collision has occurred is disabled (e.g., the collision detection user interface is disabled). In some embodiments, if a collision is determined to have occurred when the computer system is a predetermined type of device (e.g., a smart phone), the computer system provides data associated with the collision to the application (e.g., a third-party application). In some embodiments, only certain types of computer systems can share collision detection data with third-party applications (e.g., a smartphone can share collision detection data with a third-party application, but a smartwatch communicating with a smartphone cannot share collision detection data with a third-party application). Providing data associated with a collision to an application enables a computer system to automatically share data about the collision with an application that provides the functionality that the user desires after the collision, so that the user does not have to perform additional input to provide the data to the application, which reduces the number of inputs required to perform an operation.
[0259] In some embodiments, providing data associated with the collision to applications includes providing data associated with the collision to a first application and not providing data associated with the collision to a second application different from the first application, wherein after determining that a collision has occurred, the first application and the second application have been authorized to be provided with data associated with the collision (e.g., the computer system provides data associated with the collision to only one application listed in 632b; and / or the computer system provides data associated with the collision to only one application, even if multiple applications have been granted access to receive collision detection data). In some embodiments, based on determining that the first application is granted access to receive collision detection data more recently than the second application, the computer system provides data associated with the collision to the first application rather than the second application. Providing data associated with the collision to the first application and not providing data associated with the collision to different applications avoids multiple applications from providing redundant services and / or functions after a collision and reduces the amount of data that must be shared, which saves computing resources and extends battery life.
[0260] In some embodiments, the computer system displays a sharing option (e.g., 632a, a trigger button, a switch, an enable indication, 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 a collision to an application; and after (e.g., in response to) obtaining data indicating that a collision has occurred: based on determining that the state of the parameter is a first state (e.g., on or enabled), the computer system provides data associated with the collision to the application; and based on determining that the state of the parameter is a second state different from the first state (e.g., off or disabled), the computer system forgoes providing data associated with the collision to the application. In some embodiments, in response to detecting input selecting a share option when the state of a parameter for providing data associated with a collision to an application is in a first state, the computer system sets the state of the parameter for providing data associated with a collision to an application to a second state different from the first state; and in response to detecting input selecting a share option when the state of the parameter for providing data associated with a collision to an application is in a second state, the computer system sets the state of the parameter for providing data associated with a collision to an application to a first state; in some embodiments, if the state of the parameter is a first state (e.g., turned on or enabled), the computer system displays (e.g., simultaneously with the share option) a list of applications that can be used to provide data associated with a collision. In some embodiments, in response to input selecting an application from a list of applications, the computer system specifies the selected application (e.g., visually, such as with a highlight and / or a check mark, and / or in a memory). In some embodiments, providing data associated with a collision to an application based on determining that the state of the parameter is a first state includes providing data associated with a collision to a specified application based on the selected application. Disabling the sharing option enables the user to quickly and easily choose whether to share data after a collision to prevent unnecessary sharing of data, which saves computing resources and extends battery life.
[0261] It should be noted that the process described above with respect to method 700 (eg Figure 7 ) also applies in a similar manner to the methods described below. For example, method 900 optionally includes one or more of the characteristics of the various methods described above with reference to method 700. For the sake of brevity, these details are not repeated below.
[0262] FIG. 8A to FIG. 8N Illustrated are exemplary user interfaces for transmitting communications using an alternative communication network in the event of a crash according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Fig. 9 process.
[0263] Fig. 8A The above references are exemplified by Fig. 6A The computer system 604b described herein. Fig. 8A In the example, computer system 604b displays the above reference Figure 6M For example, computer system 604b displays collision detection interface 626 while attempting to initiate a call with emergency services after obtaining an indication that a collision has occurred. In some embodiments, computer system 604b attempts to initiate a call with emergency services and, in response to detecting a request for communication option 626c (e.g., Figure 6M and Figure 6N In some embodiments, the computer system 604b attempts to initiate a call with emergency services and in response to obtaining an indication that a collision has occurred without detecting user input (e.g., in response to a Figure 6N The collision detection interface 626 is displayed when the countdown 626g shown in FIG. 6 expires.
[0264] exist Fig. 8A In the embodiment of the present invention, computer system 604b cannot be connected to a ground wireless communication network, such as, for example, a cellular network or a Wi-Fi network. For example, computer system 604b may be in a remote location where a cellular network is unavailable. Because computer system 604b cannot be connected to a ground wireless communication network, computer system 604b displays a network status indicator 605 with an appearance indicating that no ground wireless communication network is available. For example, instead of displaying cellular status indicator 605a (e.g., a series of vertical bars of different lengths), network status indicator 605 includes cellular status indicator 605c (e.g., a horizontal dotted line), which indicates that a cellular network is unavailable. Emergency capability indicator 605d indicates that computer system 604b is able to perform emergency communications, even if a cellular network is unavailable. In some embodiments, emergency communications are limited to telephone and / or text communications with a specified entity or number (e.g., emergency services and / or 911). In some embodiments, computer system 604b displays emergency capability indicator 605d having a first appearance (e.g., bold and / or not grayed out) if a cellular network other than the primary cellular network associated with computer system 604b is available for emergency communications, and displays emergency capability indicator 605d having a second appearance (e.g., dimmed and / or not grayed out) if no cellular network is available. Fig. 8A No cellular network is available.
[0265] Although no cellular network is available, computer system 604b is able to communicate via an alternative communication network (e.g., a satellite communication network), as indicated by the display of satellite communication capability indicator 605e. Because computer system 604b is capable of satellite communications, in response to determining Fig. 8A If an attempted call to emergency services has failed (e.g., due to lack of cellular network availability), computer system 604b provides the option of initiating communication via satellite. Figure 8B As shown, in response to determining that a cellular connection is not present (e.g., as indicated by call status indicator 626j), computer system 604b displays satellite communication option 802. Figure 8B In the illustrated embodiment, the computer system 604b moves the end call option 6261 to the left on the collision detection interface 626 and displays the satellite communication option 802 to the right of the end call option 6261. If no cellular network is available, the satellite communication option 802 is displayed after a collision occurs, which provides the user with an alternative communication option.
[0266] In some embodiments, in response to detecting selection 825a of satellite communication option 802, computer system 604b attempts to automatically transmit a message to emergency services via satellite (e.g., without further user input). In some embodiments, if computer system 604b does not detect user input within a predetermined amount of time after displaying satellite communication option 802 (or optionally, after the call to emergency services fails), computer system 604b attempts to automatically transmit a message to emergency services via satellite (e.g., without further user input). In some embodiments, the message to emergency services is automatically generated using information such as the name or identity of a user associated with computer system 604b, the location of computer system 604b, and / or an indication that a collision has been detected.
[0267] In some embodiments, the computer system 604b must be connected (e.g., via wireless communication) to the satellite in order to transmit the message via the satellite. In some embodiments, if the computer system 604b is connected to the satellite when the attempt to transmit the message to the emergency services is made, the computer system 604b transmits the message via the satellite and displays (e.g., updates) the message. Figure 8C Collision detection interface 626 is shown.
[0268] exist Figure 8C In the collision detection interface 626, the cellular connection indication 804, the message status indication 806, and the display message option 808 are not included (for example, together with the above reference Figure 6M , 6Nand 6Q described herein). The no cellular connection indication 804 indicates (e.g., via text, such as "no cellular connection" and / or a graphic) that the computer system 604b does not have a cellular connection. The message status indication 806 indicates (e.g., via text, such as "emergency services have been notified by text" and / or a graphic) that emergency services have been notified via a text message about the detected collision. The display message option 808 provides the user with the ability to quickly and easily view messages transmitted to emergency services. For example, in response to detecting a selection 825b for the display message option 808, the computer system 604b displays the message transmitted to the emergency services. In some embodiments, in response to detecting a selection 825b for the display message option 808, the computer system 604b displays a user interface of a messaging application (e.g., a messaging interface 818) for transmitting, receiving, and / or displaying messages between the emergency services and the computer system 604b (or a user associated with the computer system 604b), such as, for example Figure 8L as shown in .
[0269] In some embodiments, if the computer system 604b is not connected to a satellite when an attempt is made to transmit a message to emergency services, the computer system 604b initiates a process of transmitting communications via a satellite. In some embodiments, the process of transmitting communications via a satellite includes displaying information and / or a command interface, such as, for example Fig.8D Information interface 810 shown in .
[0270] In some embodiments, in response to detecting the selection 825a of the satellite communication option 802, the computer system 604b initiates a process for transmitting a communication to the emergency services via a satellite without attempting to transmit an automatically generated message. For example, the computer system 604b may prompt the user for information to generate a message before attempting to transmit the message, such as referring to FIG. 8D to FIG. 8G Shown and described.
[0271] The information interface 810 includes information about generating a message to be transmitted via a satellite, connecting to a satellite, and / or transmitting a message via a satellite. In some embodiments, the computer system 604b (or a portion thereof, such as an antenna) must be physically aligned with the satellite in order to connect to the satellite for communication. Graphic 810b illustrates that a user aligns a device with a satellite. In some embodiments, the 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 one side to the other) to indicate that the user may have to move the computer system 604b to align with the satellite.
[0272] Feature indicator 810c indicates that information interface 810 relates to a feature of texting emergency services via satellite. Instructions 810d instruct the user to connect to the satellite externally (e.g., so that the computer system 604b is not blocked from the satellite by buildings). Alert 810e indicates that messages transmitted via satellite will take longer to transmit than messages transmitted via a cellular network. Prompt 810f prompts the user to answer questions to get a faster response. Content indicator 810g indicates that location and medical information can be shared when the message is transmitted.
[0273] exist Fig.8D , the computer system 604b displays an end option 811, which, when selected (e.g., via Figure 8F Choose 825e or Figure 8L In some embodiments, the computer system 604b displays the end option 811 (e.g., as shown in FIG. 8 ) throughout the process of transmitting the communication via the satellite. FIG. 8D to FIG. 8L ).
[0274] In response to detecting selection 825c of report emergency option 810h, computer system 604b continues the process of transmitting the communication via satellite.In some embodiments, the process of transmitting the communication via satellite includes providing a set of one or more options that a user may select to generate message content.
[0275] For example, in response to detecting selection 825c of report emergency option 810h, computer system 604b displays a first report generation interface 812 including a prompt 812a and a first set of options 812b for responding to prompt 812a, such as Fig. 8E The first option set 812b includes options 812b1 to 812b5, which correspond to respective responses to the prompt 812a.
[0276] In some embodiments, the options for generating the message are based on the detected collision. For example, based on determining that a collision has been detected, the computer system 604b displays a set of options (e.g., options that may be related to the collision); and based on determining that a collision has not been detected, the computer system 604b displays a different set of options (e.g., a set of options that include options related to other types of emergencies that are not related to the collision, such as being lost or trapped, crime, fire, or illness). For example, because a collision was detected, the options 812b1 to 812b4 for describing the emergency are related to an emergency that may involve a collision.
[0277] In some embodiments, in response to detecting a selection of option 812b5 (e.g., a tap on option 812b5 and / or other input selecting option 812b5), the computer system 604b displays a message composition field and keyboard that can be used to generate a customized message.
[0278] Report generation interface 812 includes skip question option 813. In some embodiments, in response to detecting a selection of skip question option 813 (e.g., a tap on skip question option 813 and / or other input selecting skip question option 813), computer system 604b proceeds with the process of transmitting the communication via the satellite without selecting an option in set of options 812b.
[0279] In response to detecting a selection 825d of option 812b1 (e.g., corresponding to a response to an emergency situation best described as a vehicle collision), computer system 604b displays a second report generation interface 814 that includes a prompt 814a and a second set of options 814b for responding to prompt 814a, such as Figure 8F As shown. The second option set 814b includes options 814b1 to 814b3, which correspond to respective responses to prompt 814a. In some embodiments, prompt 814a and second option set 814b are based on which option is selected from first option set 812b. For example, computer system 604b displays a particular prompt 814a and option set 814b because option 812b1 is selected. In some embodiments, computer system 604b displays different prompts and / or different option sets from prompt 814a and second option set 814b, respectively, in response to selection of different options in first option set 812b (e.g., in response to selection of option 812b2, option 812b3, or option 812b4), such as Figure 8F shown.
[0280] In response to detecting a selection 825f of option 814b2 (e.g., corresponding to a response that someone else needs help), computer system 604b continues the process of transmitting communications via satellite. For example, in response to selection 825f of option 814b2, computer system 604b displays a report summary interface 816 that includes a summary of a report generated based on the user's responses to prompts in report generation interfaces 812 and 814 (e.g., based on selection 825d of option 812b1 and selection 825f of option 814b2). Report summary interface 816 includes notification 816a, location information 816b, response summary 816c, countdown 816d, transmit option 816e, and do not transmit option 816f. Notification 816a indicates that the information in report summary interface 816 will be transmitted to emergency services. Location information 816b indicates a location that will be included in the information transmitted to emergency services. Response summary 816c indicates the emergency information based on the user's response (e.g., selection 825d for option 812b1 and selection 825f for option 814b2) that the response will be included in the information transmitted to the emergency services. Countdown 816d indicates the amount of time (e.g., seconds) until transmission of the information in report summary interface 816 to the emergency services will be automatically initiated (e.g., without further user input).
[0281] In response to detecting a selection of the do not transmit option 816f (e.g., a tap on the do not transmit option 816f and / or other input selecting the do not transmit option 816f), the computer system 604b stops displaying the report summary interface 816 and does not attempt to transmit the information in the report summary interface 816 (e.g., the computer system 604b displays the report summary interface 816). Fig.8D or Figure 8B The collision detection interface 626 shown in FIG. 6 is shown in FIG.
[0282] In response to detecting selection 825g of transmit option 816e, or in response to determining that countdown 816d has ended, computer system 604b attempts to transmit a message to emergency services via satellite, the message including the information shown in report summary interface 816.
[0283] In some embodiments, when computer system 604b attempts to transmit a message, computer system 604b displays a user interface of a messaging application, such as, for example Figure 8H 818. The message interface 818 includes one or more messages between the emergency service and a user associated with the computer system 604b, including a message 818a that includes the information in the report summary interface 816. The message interface 818 includes a message composition field 818c, a transmission option 818d, and a keyboard 818d for composing and transmitting additional messages to the emergency service.
[0284] exist Figure 8H In , message status indicator 818b indicates that message 818a has not been transmitted. Figure 8H In the illustrated embodiment, message 818a is not transmitted because computer system 604b is not aligned with (and not connected to) the satellite. Figure 8H , the computer system 604b displays a connection element 820 that includes information related to aligning with a satellite, connecting to a satellite, and / or message status.
[0285] The connection element 820 includes a connection status indicator 820a, an alignment instruction 820b, a message status 820c, and an alignment element 820d. The connection status indicator 820a indicates the status of the connection between the computer system 604b and the satellite. Figure 8H , connection status indicator 820a indicates that computer system 604b is not connected to a satellite. Alignment instructions 820b indicate actions a user may take to align with or maintain alignment with a satellite. Figure 8H In FIG. 8 , alignment instruction 820 b indicates that computer system 604 b may turn left to align with the satellite. Message status 820 c indicates the status of the message, for example, unable to transmit, transmitting, transmitted, or waiting to be received. Figure 8H , message status 820c indicates that message 818a cannot be transmitted. Alignment element 820d includes a graphical representation of the connection status of computer system 604b and actions that can be taken to align or maintain alignment of computer system 604b with the satellite. Figure 8H 8, consistent with the connection status indicator 820a and the alignment instruction 820b, the alignment element 820d includes an arrow pointing in a counterclockwise direction, indicating that the computer system 604b is not aligned with the satellite and can turn left to align with the satellite.
[0286] In response to detecting selection 825h of connection element 820, computer system 604b displays Figure 8I 822. Similar to the connection element 820, the appearance of the connection assistance interface 822 is based on the current status of the computer system 604b relative to the satellite. Compared with the connection element 820, the connection assistance interface 822 provides a larger interface for helping the user connect the computer system 604b to the satellite.
[0287] The connection assistance interface 822 includes an alignment element 822a, a connection status indicator 822b, and alignment instructions 822c. The alignment element 822a includes a graphical representation of a satellite, a graphical representation of the computer system 604b, and a graphical representation of an alignment window in which the computer system 604b is aligned with the satellite. The position of the representation of the satellite relative to the representation of the computer system 604b provides an indication of the actual physical location of the satellite relative to the computer system 604b. Figure 8I , the representation of the satellite is to the left of the representation of computer system 604b and to the left of the representation of the alignment window, indicating that computer system 604b is not aligned with the satellite and that computer system 604b may turn left to align with the satellite. Alignment element 822a includes an arrow indicating that the computer system may turn left to align with the satellite. Connection status indicator 822b indicates the status of the connection between computer system 604b and the satellite. Figure 8I , connection status indicator 822b indicates that computer system 604b is not connected to a satellite. Alignment instructions 822c indicate actions that a user can take to align with or maintain alignment with a satellite. Figure 8I , consistent with alignment element 822a, alignment instruction 822b instructs computer system 604b to turn left to align with the satellite.
[0288] Go to Figure 8J , computer system 604b has been relative to Figure 8I The position of computer system 604b in FIG. 6 turns left. 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 assistance interface 822 to reflect the current state of computer system 604b relative to the satellite. Figure 8J 8, the representation of the satellite is within the representation of the alignment window, and the appearance of the alignment window is changed, indicating that the computer system 604b is aligned with the satellite. The connection status indicator 822b indicates that the computer system 604b is connected to the satellite. The message status indicator 822e indicates that the message 818a is being transmitted because the computer system 604b is connected to the satellite. The action indicator 822f indicates that the computer system 604b is opening a messaging application.
[0289] In response to determining that computer system 604b is connected to the satellite, computer system 604b transmits message 818a and displays message interface 818 and connection element 820, such as Figure 8K As shown. Figure 8K8, message status indicator 818b indicates that the message is being transmitted (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 indicate that the user can keep pointing computer system 604b at the satellite (e.g., in the current direction) to transmit and receive messages via the satellite. Message status 820c indicates that computer system 604b is transmitting message 818a. Alignment element 820d indicates that computer system 604b is aligned with the satellite.
[0290] exist Figure 8K In the example shown in FIG. 8 , the computer system 604 b displays the message interface 818 without the keyboard 818 e. In response to detecting the selection 825 i of the message composition field 818 c, the computer system 604 b displays the keyboard 818 e, such as Figure 8L In some embodiments, computer system 604b provides the ability to transmit one or more additional messages to emergency services via satellite using messaging interface 818. For example, in response to detecting input on keyboard 818e, computer system 604b populates message composition field 818c, such as Figure 8L In response to detecting selection 825k of transmit option 818d, computer system 604b transmits a message to emergency services via satellite, the message having the content in message composition field 818c when selection 825k is made. Figure 8L 8, message 818a has completed transmission, which is reflected in connection element 820 by message status 820c indicating that computer system 604b is waiting to receive (e.g., Figure 8K The opposite of "teleport" in English.)
[0291] In some embodiments, the computer system 604b displays the connection assistance interface 822 before displaying an interface for generating and / or transmitting a message (e.g., the report generation interface 812, the report generation interface 814, and / or the report summary interface 816). For example, in some embodiments, the computer system 604b displays the connection assistance interface 822 in response to detecting a selection 825a of the satellite communication option 802 or in response to a selection 825c of the report emergency option 810h. In some embodiments, the computer system 604b displays the connection assistance interface 822 in response to determining that the computer system 604b is connected to a satellite (e.g., before displaying the Figure 8J After the connection assistance interface 822 shown in , an interface for generating and / or transmitting a message (eg, the report generation interface 812, the report generation interface 814, and / or the report summary interface 816) is displayed.
[0292] Figure 8M and Figure 8NAn exemplary user interface displayed by computer system 604a after a collision is detected and no terrestrial wireless communication network is available is illustrated. Figure 8M In the example of FIG. 6 , when the computer system 604a attempts to call emergency services after a collision is detected (e.g., as described in reference to FIG. 6 ), Fig.6D ), the computer system 604a displays the collision detection interface 612. In response to determining that no terrestrial wireless communication network is available, the computer system 604a displays prompt 824.
[0293] Prompt 824 includes: a collision detection indicator 824a (e.g., "Collision Detected"), which indicates that a collision has been detected; a connection status indicator 824b (e.g., "No Connection"), which indicates that there is no connection; a satellite communication indication 824c (e.g., "Your phone will attempt to text emergency services via satellite"), which indicates that the computer system 604b will attempt to text emergency services via satellite; instructions 824d (e.g., "Follow instructions on your phone"), which include a prompt to follow instructions on the computer system 604b.
[0294] Fig. 9 900 is a flowchart illustrating a method for transmitting communications via an alternative communication network in a collision event using a computer system according to some embodiments. Method 900 is performed at a computer system (e.g., 100, 300, 500, 604a, 604b, a smart phone, a smart watch, 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 communicates (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., 606a, 606b, a touch-sensitive surface, a keyboard, a mouse, a trackpad, a joystick, a remote control, a microphone, one or more optical sensors for detecting gestures, one or more capacitive sensors for detecting hovering inputs, an accelerometer, a gyroscope, and / or an inertial measurement unit). Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.
[0295] As described below, method 900 provides an intuitive way to transmit communications using an alternative communication network in the event of a crash. The method reduces the cognitive burden on a user to transmit communications using an alternative communication network in the event of a crash, thereby creating a more efficient human-machine interface. For battery-powered computing devices, enabling a user to transmit communications faster and more efficiently using an alternative communication network in the event of a crash saves power and increases the time interval between battery charges.
[0296] The computer system acquires (902) (e.g., receives or detects) data indicating that a collision (e.g., a collision, accident, and / or impact involving a vehicle such as, for example, a car, truck, motorcycle, scooter, bus, bicycle, boat, train, airplane, wheelchair, golf cart, or all-terrain vehicle (ATV)) has occurred. In some embodiments, acquiring data indicating that a collision has occurred includes detecting a collision and / or determining that a collision has occurred (e.g., based on detected motion, parameters, and / or conditions). In some embodiments, detecting a collision includes detecting (e.g., via one or more sensors such as motion sensors, accelerometers, gyroscopes, inertial measurement units, biometric sensors, and / or microphones) motion (e.g., linear and / or angular velocity and / or linear and / or angular acceleration), sound, biometric parameters (e.g., blood pressure, blood oxygen level, pulse, and / or heart rate), and / or other parameters or conditions. In some embodiments, determining that a collision has occurred includes determining that the detected parameters or conditions meet a set of collision criteria (e.g., motion threshold, motion curve, speed threshold, speed curve, acceleration threshold, acceleration curve, blood pressure threshold, blood oxygen threshold, pulse threshold, heart rate threshold, sound curve, sound amplitude threshold, sound frequency and / or sound frequency range). In some embodiments, the computer system detects the collision (e.g., using a sensor of the computer system; the collision is detected by the computer system). In some embodiments, the computer system determines that a collision has occurred. In some embodiments, one or more external devices (e.g., one or more remote sensors, servers and / or computer systems) that are not part of the computer system (e.g., one or more remote devices) detect the collision and / or determine that a collision has occurred. In some embodiments, one or more external devices that detect the collision and / or determine that a collision has occurred transmit data indicating that a collision has occurred to the computer system and / or to the remote server. In some embodiments, obtaining data indicating that a collision has occurred includes receiving data indicating that a collision has occurred (e.g., from a remote server and / or from one or more remote devices that detect and / or determine that a collision has occurred). In some embodiments, the computer system cannot detect the collision and / or determine that a collision has occurred. In some embodiments, the computer system communicates (e.g., wired communication, wireless communication, Bluetooth communication, near field communication, and / or Wi-Fi communication) with an external computer system (e.g., a smart phone, a smart watch, a tablet computer, one or more sensors of the vehicle, and / or a computer system of the vehicle) that can detect a collision and / or determine that a collision has occurred. In some embodiments, the computer system acquires (e.g., receives or retrieves) data indicating that a collision has occurred from the external computer system.
[0297] In response to (904) obtaining data indicating that a collision has occurred: based on determining that a terrestrial wireless communication network (e.g., a cellular network) is unreachable by the computer system (e.g., the terrestrial wireless communication network is not available to the computer system, the computer system does not communicate with the terrestrial wireless communication network, the computer system is not connected or cannot connect to the terrestrial wireless communication network, the computer system has not received a signal from the terrestrial wireless communication network that meets strength and / or consistency criteria for performing communications, and / or there is no terrestrial wireless communication network via which the computer system can currently perform communications because there is no terrestrial wireless communication network to which the computer system can connect or via which the computer system is authorized to communicate), the computer system displays (906) via a display generation component a non-terrestrial wireless communication option (e.g., 802, a selectable option, an icon, an affordance, a button, and / or a user-interactive graphical user interface object) that, when selected via one or more input devices, initiates a process for communicating via the non-terrestrial wireless communication network (e.g., via one or more satellites, satellite communication networks, low bandwidth communication networks, and / or communication protocols that do not require cellular service and / or terrestrial wireless communication networks) (e.g., FIG. 8C to FIG. 8L ); and based on determining that the computer system is reachable to a terrestrial wireless communication network (e.g., a cellular network) (e.g., the terrestrial wireless communication network is available to the computer system, the computer system is in communication with the terrestrial wireless communication network, the computer system is connected or capable of connecting to the terrestrial wireless communication network, the computer system is receiving signals from the terrestrial wireless communication network that meet strength and / or consistency criteria for performing communications, and / or there is a terrestrial wireless communication network via which the computer system can currently perform communications), the computer system forgoes (908) displaying non-terrestrial wireless communication options. Displaying non-terrestrial wireless communication options based on whether the terrestrial wireless communication network is reachable by the computer system informs the user that an alternative communication network is available even when the terrestrial wireless communication network is not available, enables the user to quickly and efficiently initiate communications via the non-terrestrial wireless communication network, and avoids displaying options when it is not necessary, which provides improved feedback to the user, reduces the number of inputs required to perform operations, provides additional control options without cluttering the user interface with additional displayed controls, and performs operations without requiring further user input when a set of conditions have been met.
[0298] In some embodiments, the communication via the non-terrestrial wireless communication network includes a phone call, a text message, an email, an audio message, a video message, and / or a video conference. In some embodiments, the communication is live or real-time (e.g., full-duplex real-time) communication. In some embodiments, the terrestrial wireless communication network is a cellular network associated with the computer system (e.g., provided by a cellular service provider associated with the computer system and / or a user associated with the computer system) or another cellular network (e.g., provided by another cellular service provider). In some embodiments, for a call to a specified entity (e.g., a call to an emergency service or an emergency contact), the computer system can use a network provided by a network provider different from the provider associated with the computer system. In some embodiments, in response to determining that data indicating that a collision has occurred is obtained and that the terrestrial wireless communication network can be reached according to the computer system, the computer system displays a call option (e.g., 626c), which, when selected, initiates a process of calling a predetermined number via terrestrial wireless communication without displaying a non-terrestrial wireless communication option. In some embodiments, the call option includes selectable call options, icons, buttons, affordances, and / or user interactive graphical user interface objects. In some embodiments, the computer system initiates display of a call option in response to obtaining data indicating that a collision has occurred and in accordance with determining that the computer system is unreachable to a terrestrial wireless communication network (e.g., the call option is not provided, displayed, and / or unavailable prior to obtaining data indicating that a collision has occurred). In some embodiments, the call option includes (e.g., is) a graphical object that moves (e.g., slides) in accordance with movement of an input (e.g., a swipe or touch and drag input). In some embodiments, selection of the call option requires moving the graphical object (e.g., on a display) by a predetermined amount and / or to a predetermined position (e.g., from a first position such as a first position and / or a first orientation to a second position such as a predefined position and / or a predefined orientation). In some embodiments, selection of the call option requires moving the graphical object from a first position on a predefined area or path (e.g., a first side, left side, top side, or upper side) to a second position on a predefined area or path (e.g., an opposite side, right side, bottom side, or lower side). In some embodiments, in response to detecting the selection of the call option, the computer system immediately (e.g., without a predetermined delay and / or countdown) and / or automatically initiates a call to the predetermined number without further input (e.g., without requiring confirmation). In some embodiments, in response to detecting the selection of the call option, the computer system initiates the call to the predetermined number and displays a call user interface (e.g., without displaying an intermediate or intervening user interface).
[0299] In some embodiments, in response to acquiring data indicating that a collision has occurred, and before displaying the non-terrestrial wireless communication option, the computer system attempts to initiate a call to a designated entity (e.g., a predetermined entity, a predetermined number, an emergency service, an emergency number, or an emergency contact) (e.g., Fig. 8A ). Examples of numbers associated with emergency services include 911 in the United States, 999 in the United Kingdom, 112 in Europe, 110 and / or 119 in Japan, and 000 in Australia. In response to acquiring data indicating that a collision has occurred and attempting to initiate a call to a designated entity before displaying a non-terrestrial wireless communication option, this enables the computer system to attempt to use a communication method that uses less energy, is faster, and requires less user input than communication via a non-terrestrial wireless communication network, which reduces the number of inputs required to perform operations, reduces energy consumption, and extends battery life.
[0300] In some embodiments, after initiating display of the non-terrestrial wireless communication option: based on determining that a threshold amount of time has passed without detecting a 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 transmits (e.g., the computer system automatically transmits, without detecting user input) a communication (e.g., a text and / or audio communication) to the designated entity via the non-terrestrial wireless communication network (e.g., as described in reference to Figure 8CAs described herein), wherein the text communication includes information related to the collision (e.g., the location of the collision, the time of the collision, the circumstances under which the collision occurred, and / or the persons involved in the collision). The communication is transmitted to the designated entity via the non-terrestrial wireless communication network based on determining that a threshold amount of time has passed, which enables the computer system to automatically transmit the communication after the collision without user input, which reduces the number of inputs required to perform operations and performs operations without further user input when a set of conditions have been met. In some embodiments, after transmitting the communication to the designated entity, the computer system displays a view message option (e.g., 808); the computer system detects input corresponding to a selection of the view message option (e.g., 825b); and in response to detecting input corresponding to a selection of the view message option, the computer system displays the communication to the designated entity (e.g., 818a). In some embodiments, displaying the communication to the designated entity includes displaying a user interface of a messaging application (e.g., a text messaging application), the user interface including a messaging conversation between a user of the computer system and the designated entity (including communications 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). In some embodiments, the user interface of the messaging application includes a selectable element (e.g., a keyboard and / or a send button) for transmitting an additional message to a specified entity. In some embodiments, after transmitting a communication to a specified entity, the computer system displays a selectable option that, when selected, causes the computer system to attempt (or retry) to initiate a call with the specified entity. Displaying a selectable option to display the communication to the specified entity provides feedback to the user that the communication was transmitted and provides a fast and efficient method for displaying the communication, provides improved feedback to the user and reduces the number of inputs required to perform an operation, and provides additional control options without cluttering the user interface with additional display controls.
[0301] In some embodiments, after initiating display of the non-terrestrial wireless communication option: based on determining that a threshold amount of time has passed but selection of the non-terrestrial wireless communication option has not been detected and 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., retry) to initiate a call to the specified entity. In some embodiments, after initiating display of the non-terrestrial wireless communication option: based on determining that a threshold amount of time has passed but selection of the non-terrestrial wireless communication option has not been detected and the non-terrestrial wireless communication network is not reachable by the computer system, the computer system displays an indication that the specified entity has not been contacted (e.g., a communication has not been transmitted to the specified entity). Displaying the option to initiate a call to the specified entity based on determining that a threshold amount of time has passed but selection of the non-terrestrial wireless communication option has not been detected enables the computer system to automatically call the specified entity without requiring user input after a collision, which reduces the number of inputs required to perform an operation, and performs an operation without requiring further user input when a set of conditions have been met.
[0302] In some embodiments, based on determining that the computer system is not reachable to a terrestrial wireless communication network (e.g., a cellular network), the computer system causes display (e.g., on the computer system and / or on an external computer system) an indication that the computer system is not reachable to the terrestrial wireless communication network (e.g., 824b). In some embodiments, in response to obtaining data indicating that a collision has occurred and based on a determination (e.g., by the computer system or an external computer system in communication with the computer system) that the terrestrial wireless communication network is not reachable, the computer system indicates that a collision has been detected, indicates that the external computer system will attempt to transmit communications to a designated entity, and / or provides a prompt to a user to communicate with the designated entity via a non-terrestrial wireless communication network using the external computer system. Displaying an indication that the computer system is not reachable to the terrestrial wireless communication network based on determining that the computer system is not reachable to the terrestrial wireless communication network informs the user that the terrestrial wireless communication network is not reachable and enables the user to use the computer system more efficiently, without attempting to perform communications via the terrestrial wireless communication network when the terrestrial wireless communication network is not reachable, providing improved feedback to the user, reducing the number of inputs required to perform operations, and performing operations without further user input when a set of conditions have been met.
[0303] In some embodiments, when a non-terrestrial wireless communication option is displayed (e.g., 802), the computer system detects input corresponding to selection of the non-terrestrial wireless communication option (e.g., 825a); and in response to detecting input corresponding to selection of the non-terrestrial wireless communication option (and optionally, based on determining that the computer system is connected to a non-terrestrial wireless communication network), the computer system transmits (e.g., the computer system automatically transmits, without detecting user input) a communication (e.g., a text and / or audio communication) to a designated entity via the non-terrestrial wireless communication network, wherein the communication includes information related to the collision (e.g., the location of the collision, the time of the collision, the circumstances under which the collision occurred, and / or the persons involved in the collision). Transmitting a communication with information related to the collision to a designated entity in response to detecting selection of the non-terrestrial wireless communication option enables a user to communicate quickly and efficiently after a collision when a terrestrial wireless communication network is unreachable, which reduces the number of inputs required to perform operations and extends battery life.
[0304] In some embodiments, when displaying the non-terrestrial wireless communication option (e.g., 802), the computer system detects an input corresponding to a selection of the non-terrestrial wireless communication option (e.g., 825a); in response to detecting the input corresponding to the selection of the non-terrestrial wireless communication option (and optionally, based on determining that the computer system is connected to a 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 corresponding to a selection of one or more message content options in the set of selectable content options (e.g., 825d and / or 825f); after detecting the one or more inputs (e.g., in response to a request to transmit a communication via the non-terrestrial wireless communication network), the computer system transmits a communication via the non-terrestrial wireless communication network, the communication including content corresponding to the selected one or more message content options. Displaying a set of selectable options for generating a communication provides a user with a quick and efficient method of creating a message after a collision, and enables the computer system to create a low-bandwidth communication that requires less bandwidth and / or energy to transmit, which provides improved feedback to the user, reduces the number of inputs required to perform an operation, and extends battery life.
[0305] In some embodiments, any of the selections, requests, and / or inputs described herein (e.g., selections 625a to 625u and / or selections 825a to 825k) is or includes a touch input (e.g., a tap gesture and / or a slide gesture). In some embodiments, any of the selections, requests, and / or inputs described herein (e.g., selections 625a to 625u and / or selections 825a to 825k) is or includes a voice input (e.g., a voice command to select a user interface element or activate a feature or perform a function (such as a feature or function associated with a user interface element)). In some embodiments, any of the selections, requests, and / or inputs described herein (e.g., selections 625a to 625u and / or selections 825a to 825k) is or includes a gesture (e.g., an air gesture to select a user interface element or activate a feature or perform a function (such as a feature or function associated with a user interface element)). In some embodiments, any of the selections, requests, and / or inputs described herein (e.g., selections 625a-625u and / or selections 825a-825k) is or includes activation (e.g., pressing, rotating, and / or moving) of a hardware device (e.g., a button, a rotatable input mechanism, a rotatable depressible input mechanism, a mouse button, a button of a remote control, and / or a joystick). In some embodiments, any of the user interface elements described herein as being selected (e.g., an icon, an affordance, a button, and / or a selectable option) is selected by activating a hardware device while the user interface element is in focus (e.g., highlighted, bolded, outlined, visually distinguished from other user interface elements, and / or located at or near a cursor).
[0306] Note that the above description is relative to method 900 (eg, Fig. 9 ) also applies in a similar manner to the methods described above. For example, method 700 optionally includes one or more of the characteristics of the various methods described above with reference to method 900. For the sake of brevity, these details are not repeated below.
[0307] For the purpose of explanation, the preceding description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. These embodiments are selected and described in order to best explain the principles of these technologies and their practical applications. Others skilled in the art can thus best utilize these technologies and various embodiments with various modifications suitable for the intended specific use.
[0308] Although the disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will become apparent to those skilled in the art. It should be understood that such changes and modifications are considered to be included within the scope of the disclosure and examples defined by the claims.
[0309] As described above, one aspect of the present technology is to collect and use data from various sources to improve the delivery of walking stability content or any other content that may be of interest to users. The present disclosure contemplates that, in some instances, such collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, social network IDs, home addresses, data or records related to a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identification or personal information.
[0310] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit the user. In addition, the present disclosure also anticipates other uses of personal information data that benefit the user. For example, health and fitness data can be used to provide insights into the user's overall health status, or can be used as positive feedback to individuals who use technology to pursue health goals.
[0311] The disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage or other purposes of such personal information data will comply with sound privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to the use of privacy policies and measures that are recognized as meeting or exceeding the industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be convenient for users to access and should be updated as changes in the collection and / or use of data occur. Personal information from users should be collected for legal and reasonable entity purposes and should not be shared or sold outside these legal purposes. In addition, such collection / sharing should be carried out after receiving the informed consent of the user. Additionally, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data, and ensure that other entities with access to personal information data comply with the privacy policies and procedures of other entities. In addition, such entities can subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and privacy practices. In addition, policies and practices should be adapted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including considerations of special jurisdictions. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy measures should be advocated for different types of personal data in each country.
[0312] Notwithstanding the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates that hardware elements and / or software elements may be provided to prevent or block access to such personal information data. For example, with respect to text selection, the present technology may be configured to allow a user to choose to "opt in" or "opt out" to participate in the collection of personal information data at any time during or after registration for a service. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to access or use of personal information. For example, a user may be notified that their personal information data will be accessed when downloading an application, and then be reminded again just before the personal information data is accessed by the application.
[0313] In addition, it is the intention of the present disclosure that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting the collection of data and deleting the data. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than at the address level), controlling how the data is stored (e.g., aggregating data between users), and / or other methods when appropriate.
[0314] Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without requiring access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, collision detection data may be selected and delivered to a user by inferring preferences based on non-personal information data or an absolute minimum of personal information (such as content requested by a device associated with the user, other non-personal information available to the collision detection function, or publicly available information).
Claims
1. A method, comprising: At a computer system in communication with a display generating component and one or more input devices: obtaining data indicating that a collision has occurred; in response to acquiring the data indicating that a collision has occurred, displaying, via the display generating component, a call option; as well as Based on determining that the call option has been selected via the one or more input devices, a process is initiated to call a predetermined number associated with the call option.
2. The method according to claim 1, further comprising: After acquiring the data indicating that a collision has occurred, an indication is provided that a collision has been detected.
3. The method according to any one of claims 1 to 2, further comprising: After acquiring the data indicating that a collision has occurred, based on determining that a first threshold amount of time has elapsed, a call is initiated to the predetermined number associated with the calling option without detecting a selection of the calling option.
4. The method according to claim 3, further comprising: After obtaining the data indicating that a collision has occurred: Based on determining that a second threshold amount of time has passed, without detecting a selection of the call option, starting a countdown to initiate a call to the predetermined number associated with the call option, wherein the second threshold amount of time is less than the first threshold amount of time, and wherein the first threshold amount of time has passed when the countdown expires.
5. The method according to any one of claims 3 to 4, further comprising: In the absence of detecting a selection of the call option, after initiating a call to the predetermined number associated with the call option: In the absence of detecting a selection of the call option, after establishing a call with the predetermined number in response to initiating a call to the predetermined number associated with the call option, outputting an audio message indicating that a collision has been detected.
6. The method according to any one of claims 1 to 5, further comprising: After obtaining the data indicating that a collision has occurred, a communication is transmitted to one or more designated contacts.
7. The method according to any one of claims 1 to 6, further comprising: In response to determining that the call to the predetermined number has ended, an indication that a collision was detected is displayed. The method of claim 7 , wherein displaying the indication that the collision was detected comprises displaying an indication of a time when the collision was detected.
9. The method according to any one of claims 1 to 8, further comprising: After obtaining the data indicating that a collision has occurred: In response to determining that the call to the predetermined number has ended, a second call option is displayed that, when selected, causes the computer system to initiate a process of calling the predetermined number.
10. The method according to any one of claims 1 to 9, further comprising: After obtaining the data indicating that a collision has occurred: In response to determining that the call to the predetermined number has ended, a medical ID option is displayed that, when selected, causes the computer system to display information of a user associated with the computer system.
11. The method according to any one of claims 1 to 10, further comprising: After obtaining the data indicating that a collision has occurred, a voice assistance function on the computer system is disabled.
12. The method according to any one of claims 1 to 11, further comprising: After initiating a call with the predetermined number, detecting a request to end the call with the predetermined number; as well as In response to detecting the request to end the call with the predetermined number, an option to confirm the request to end the call with the predetermined number without ending the call with the predetermined number is displayed, and the option when selected causes the computer system to end the call with the predetermined number.
13. The method according to any one of claims 1 to 12, further comprising: An enable collision detection option is displayed, which, when selected, sets a state of the ability to display the call option in response to acquiring data indicating that a collision has occurred.
14. The method according to claim 13, further comprising: A user interface of a health application including information associated with a user's health is displayed, wherein displaying the enable collision detection option includes displaying the enable collision detection option in the user interface of the health application.
15. A method according to any one of claims 13 to 14, wherein the enable collision detection option, when selected, enables the ability of the computer system to display the call option in response to obtaining data indicating that a collision has occurred, but does not enable the ability of the second computer system to display the call option in response to obtaining data indicating that a collision has occurred.
16. The method according to any one of claims 1 to 15, further comprising: After acquiring data indicating that a collision has occurred, data associated with the collision is provided to the application.
17. A method according to claim 16, wherein providing data associated with the collision to applications includes providing data associated with the collision to a first application without providing data associated with the collision to a second application different from the first application, wherein after determining that a collision has occurred, the first application and the second application are authorized to be provided with data associated with the collision.
18. The method according to any one of claims 16 to 17, further comprising: displaying a share option that, when selected, sets a state of a parameter for providing data associated with the collision to an application; as well as After obtaining the data indicating that a collision has occurred: Based on determining that the state of the parameter is a first state, providing data associated with the collision to an application; and Based on determining that the state of the parameter is a second state different from the first state, providing data associated with the collision to an application is foregone.
19. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system communicating with a display generating component and one or more input devices, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 18.
20. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 18.
21. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: A component for carrying out the method according to any one of claims 1 to 18.
22. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for performing the method according to any one of claims 1-18.
23. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: obtaining data indicating that a collision has occurred; In response to obtaining the data indicating that a collision has occurred, displaying call options via the display generating component; and Based on determining that the call option has been selected via the one or more input devices, a process is initiated to call a predetermined number associated with the call option.
24. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: obtaining data indicating that a collision has occurred; in response to acquiring the data indicating that a collision has occurred, displaying, via the display generating component, a call option; as well as Based on determining that the call option has been selected via the one or more input devices, a process is initiated to call a predetermined number associated with the call option.
25. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: means for obtaining data indicating that a collision has occurred; means for displaying, via said display generating component, call options in response to obtaining said data indicating that a collision has occurred; as well as Means for initiating a process of calling a predetermined number associated with the call option based on determining that the call option has been selected via the one or more input devices.
26. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: obtaining data indicating that a collision has occurred; In response to obtaining the data indicating that a collision has occurred, displaying call options via the display generating component; and Based on determining that the call option has been selected via the one or more input devices, a process is initiated to call a predetermined number associated with the call option.
27. A method comprising: At a computer system in communication with a display generating component and one or more input devices: obtaining data indicating that a collision has occurred; as well as In response to acquiring the data indicating that a collision has occurred: displaying, via the display generating component, a non-terrestrial wireless communication option based on determining that the computer system is not reachable by the terrestrial wireless communication network, the non-terrestrial wireless communication option, when selected via the one or more input devices, initiating a process for communicating via the non-terrestrial wireless communication network; as well as Based on determining that the computer system is reachable to a terrestrial wireless communication network, Abandoning displaying the non-terrestrial wireless communication option.
28. The method according to claim 27, further comprising: In response to acquiring the data indicating that a collision has occurred, and before displaying the non-terrestrial wireless communication option, attempting to initiate a call to a designated entity.
29. The method according to any one of claims 27 to 28, further comprising: After initiating display of the non-terrestrial wireless communication options: Based on determining that a threshold amount of time has passed without detecting a selection of the non-terrestrial wireless communication option and the non-terrestrial wireless communication network is reachable by the computer system, transmitting a communication to the designated entity via the non-terrestrial wireless communication network, wherein the text communication includes information related to the collision.
30. The method according to claim 29, further comprising: after transmitting the communication to the designated entity, displaying a view message option; detecting an input corresponding to a selection of the view messages option; as well as In response to detecting the input corresponding to selection of the view message option, the communication is displayed to the designated entity.
31. The method according to any one of claims 27 to 30, further comprising: After initiating display of the non-terrestrial wireless communication options: Based on determining that a threshold amount of time has passed without detecting a selection of the non-terrestrial wireless communication option and the non-terrestrial wireless communication network is not reachable by the computer system, displaying an option that, when selected, causes the computer system to attempt to initiate a call to the designated entity.
32. The method according to any one of claims 27 to 31, further comprising: Based on determining that the terrestrial wireless communication network is unreachable by the computer system, an indication is displayed that the terrestrial wireless communication network is unreachable by the computer system.
33. The method according to any one of claims 27 to 32, further comprising: while displaying the non-terrestrial wireless communication option, detecting an input corresponding to a selection of the non-terrestrial wireless communication option; as well as In response to detecting the input corresponding to selection of the non-terrestrial wireless communication option, transmitting a communication to the designated entity via the non-terrestrial wireless communication network, wherein the communication includes information related to the collision.
34. The method according to any one of claims 27 to 33, further comprising: while displaying the non-terrestrial wireless communication option, detecting an input corresponding to a selection of the non-terrestrial wireless communication option; responsive to detecting the input corresponding to a selection of the non-terrestrial wireless communication option, displaying a set of selectable message content options; detecting one or more user inputs corresponding to selection of one or more message content options from the set of selectable content options; as well as After detecting the one or more inputs, a communication including content corresponding to the selected one or more message content options is transmitted via the non-terrestrial wireless communication network.
35. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for executing a method according to any one of claims 27-34.
36. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; and A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 27-34.
37. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: Means for performing the method according to any one of claims 27-34.
38. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for performing the method according to any one of claims 27-34.
39. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: obtaining data indicating that a collision has occurred; and In response to acquiring the data indicating that a collision has occurred: displaying, via the display generating component, a non-terrestrial wireless communication option based on determining that the computer system is not reachable by the terrestrial wireless communication network, the non-terrestrial wireless communication option, when selected via the one or more input devices, initiating a process for communicating via the non-terrestrial wireless communication network; and Based on determining that the computer system can reach a terrestrial wireless communication network, displaying the non-terrestrial wireless communication option is foregone.
40. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: obtaining data indicating that a collision has occurred; and In response to acquiring the data indicating that a collision has occurred: displaying, via the display generating component, a non-terrestrial wireless communication option based on determining that the computer system is not reachable by the terrestrial wireless communication network, the non-terrestrial wireless communication option, when selected via the one or more input devices, initiating a process for communicating via the non-terrestrial wireless communication network; as well as Based on determining that the computer system is reachable to a terrestrial wireless communication network, Abandoning displaying the non-terrestrial wireless communication option.
41. A computer system configured to communicate with a display generation component and one or more input devices, the computer system comprising: means for obtaining data indicating that a collision has occurred; as well as means for, in response to acquiring said data indicating that a collision has occurred: displaying, via the display generating component, a non-terrestrial wireless communication option based on determining that the computer system is not reachable by the terrestrial wireless communication network, the non-terrestrial wireless communication option, when selected via the one or more input devices, initiating a process for communicating via the non-terrestrial wireless communication network; as well as Based on determining that the computer system can reach a terrestrial wireless communication network, displaying the non-terrestrial wireless communication option is foregone.
42. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: obtaining data indicating that a collision has occurred; and In response to acquiring the data indicating that a collision has occurred: displaying, via the display generating component, a non-terrestrial wireless communication option based on determining that the computer system is not reachable by the terrestrial wireless communication network, the non-terrestrial wireless communication option, when selected via the one or more input devices, initiating a process for communicating via the non-terrestrial wireless communication network; and Based on determining that the computer system can reach a terrestrial wireless communication network, displaying the non-terrestrial wireless communication option is foregone.
Citation Information
Patent Citations
Method and apparatus for integrating manual input
US20020015024A1
Gestures for touch sensitive input devices
US20060026521A1
Gestures for touch sensitive input devices
US20060026536A1
Virtual input device placement on a touch screen user interface
US20060033724A1
Multipoint touchscreen
US20060097991A1