CN109565528B

CN109565528B - Method for operating safety mode of vehicle, electronic device and computer readable storage medium

Info

Publication number: CN109565528B
Application number: CN201880003105.9A
Authority: CN
Inventors: E·C·舒尔波特; T·布洛克索姆; A·M·J·布莱; R·R·德林格尔; C·M·弗德里格; M·E·谢波德; G·L·韦恩伯格
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2017-05-16
Filing date: 2018-05-15
Publication date: 2022-05-10
Anticipated expiration: 2038-05-15
Also published as: CN109565528A; CN114650336A

Abstract

The present disclosure relates generally to implementing a safe mode of operation that manages output of notifications at an electronic device (600) when a user (604) of the device operates a vehicle. In case the vehicle moves beyond a given threshold, a safe mode of operation is entered, wherein the notification is to be suppressed. The sender may be notified by an auto-reply that the recipient is driving.

Description

Method for operating safety mode of vehicle, electronic device and computer-readable storage medium

Cross Reference to Related Applications

This application claims priority from danish patent application No. pa201770414 entitled "operative SAFETY MODE" filed on 29.5.2017, danish patent application No. PA201770413 entitled "operative SAFETY MODE" filed on 29.5.2017 and 5.16.2017, and U.S. provisional patent application No.62/507,115 entitled "operative SAFETY MODE" filed on 16.5.2017. The contents of the above-identified applications are hereby incorporated by reference in their entirety.

Technical Field

The present disclosure relates generally to electronic devices, and more particularly to techniques for operating an electronic device in various modes under various circumstances.

Background

The electronic device may receive information, including by way of example only, communications from electronic devices and/or applications of other users. Such electronic devices may output a notification indicating the arrival of information.

Disclosure of Invention

However, some modes of operation involving outputting notifications using an electronic device are often cumbersome and inefficient. For example, some prior art techniques use complex and time-consuming user interfaces that may include multiple keystrokes or keystrokes. The prior art requires more time than necessary, which results in wasted time and equipment energy for the user. This latter consideration is particularly important in battery-powered devices.

Thus, the present technology provides faster, more efficient methods and interfaces for managing notification output for electronic devices. Such methods and interfaces optionally complement or replace other methods for managing notification output. Such methods and interfaces reduce the cognitive burden placed on the user and result in a more efficient human-machine interface. For battery-driven computing devices, such methods and interfaces conserve power and increase the time interval between battery charges. For battery-driven computing devices, such methods and interfaces conserve power and increase the time interval between battery charges. For example, methods and interfaces contemplated herein provide reduced processing power, reduced memory usage, and reduced battery usage by a display at a device.

Example methods are disclosed herein. An example method includes: at an electronic device having a display: detecting one or more context parameters; initiating a safe mode of operation based on one or more contextual parameters satisfying safe mode of operation initiation criteria, the safe mode of operation initiation criteria including criteria that are satisfied when the contextual parameters indicate that the electronic device is located within a running motor vehicle; when the device is in a secure mode of operation: receiving a notification; in accordance with a determination that the notification satisfies a set of notification output criteria, causing an output corresponding to the notification; and in accordance with a determination that the notification does not satisfy the set of notification output criteria, forgoing causing output corresponding to the notification.

An example method includes: at an electronic device having a display: while in the operational safety mode: receiving a communication from a contact; in accordance with a determination that the communication satisfies a notification output criterion, outputting a notification corresponding to the communication, the notification output criterion including a criterion that is satisfied when the communication includes a notification output request; and in accordance with a determination that the communication does not satisfy the notification output criteria, forgoing outputting the notification.

An example method includes: detecting a first set of one or more contextual parameters when a first set of operational safety mode initiation criteria of the plurality of sets of operational safety mode initiation criteria is valid, the first set of operational safety mode initiation criteria comprising criteria that are met when movement of the electronic device exceeds a threshold movement value; in response to detecting the first set of one or more context parameters: in accordance with a determination that the first set of contextual parameters meets a first set of operational safety mode initiation criteria, initiating an operational safety mode; detecting a second set of one or more contextual parameters when a second set of operational safety mode initiation criteria of the plurality of sets of operational safety mode initiation criteria is valid, the second set of operational safety mode initiation criteria including criteria that are met when the electronic device is connected to a second electronic device associated with the motor vehicle; in response to detecting the second set of one or more context parameters: starting the operational safety mode in response to determining that the second set of contextual parameters meets a second set of operational safety mode start criteria; in accordance with a determination that the second set of contextual parameters does not satisfy the second set of operational safety mode enablement criteria, the operational safety mode is aborted upon satisfaction of the first set of operational safety mode enablement criteria.

Example apparatuses are disclosed herein. An example electronic device includes a display; one or more processors; and memory storing one or more programs configured for execution by the one or more processors, the one or more programs including instructions for: detecting one or more context parameters; initiating a safe mode of operation based on one or more contextual parameters satisfying safe mode of operation initiation criteria, the safe mode of operation initiation criteria including criteria that are satisfied when the contextual parameters indicate that the electronic device is located within a running motor vehicle; when the device is in a secure mode of operation: receiving a notification; in accordance with a determination that the notification satisfies a set of notification output criteria, causing an output corresponding to the notification; and in accordance with a determination that the notification does not satisfy the set of notification output criteria, forgoing causing output corresponding to the notification.

An example electronic device includes a display; one or more processors; and memory storing one or more programs configured for execution by the one or more processors, the one or more programs including instructions for: while in the operational safety mode: receiving a communication from a contact; in accordance with a determination that the communication satisfies a notification output criterion, outputting a notification corresponding to the communication, the notification output criterion including a criterion that is satisfied when the communication includes a notification output request; and in accordance with a determination that the communication does not satisfy the notification output criteria, forgoing outputting the notification.

An example electronic device includes a display; one or more processors; and memory storing one or more programs configured for execution by the one or more processors, the one or more programs including instructions for: detecting a first set of one or more contextual parameters when a first set of operational safety mode initiation criteria of the plurality of sets of operational safety mode initiation criteria is valid, the first set of operational safety mode initiation criteria comprising criteria that are met when movement of the electronic device exceeds a threshold movement value; in response to detecting the first set of one or more context parameters: in accordance with a determination that the first set of contextual parameters meets a first set of operational safety mode initiation criteria, initiating an operational safety mode; detecting a second set of one or more contextual parameters when a second set of operational safety mode initiation criteria of the plurality of sets of operational safety mode initiation criteria is valid, the second set of operational safety mode initiation criteria including criteria that are met when the electronic device is connected to a second electronic device associated with the motor vehicle; in response to detecting the second set of one or more context parameters: starting the operational safety mode in response to determining that the second set of contextual parameters meets a second set of operational safety mode start criteria; in accordance with a determination that the second set of contextual parameters does not satisfy the second set of operational safety mode enablement criteria, the operational safety mode is aborted upon satisfaction of the first set of operational safety mode enablement criteria.

Example non-transitory computer-readable storage media are disclosed herein. An example non-transitory computer-readable storage medium stores one or more programs configured for execution by one or more processors of an electronic device with a display, the one or more programs including instructions for: detecting one or more context parameters; initiating a safe mode of operation based on one or more contextual parameters satisfying safe mode of operation initiation criteria, the safe mode of operation initiation criteria including criteria that are satisfied when the contextual parameters indicate that the electronic device is located within a running motor vehicle; when the device is in a secure mode of operation: receiving a notification; in accordance with a determination that the notification satisfies a set of notification output criteria, causing an output corresponding to the notification; and in accordance with a determination that the notification does not satisfy the set of notification output criteria, forgoing causing output corresponding to the notification.

An example non-transitory computer-readable storage medium stores one or more programs configured for execution by one or more processors of an electronic device with a display, the one or more programs including instructions for: while in the operational safety mode: receiving a communication from a contact; in accordance with a determination that the communication satisfies a notification output criterion, outputting a notification corresponding to the communication, the notification output criterion including a criterion that is satisfied when the communication includes a notification output request; and in accordance with a determination that the communication does not satisfy the notification output criteria, forgoing outputting the notification.

An example non-transitory computer-readable storage medium stores one or more programs configured for execution by one or more processors of an electronic device with a display, the one or more programs including instructions for: detecting a first set of one or more contextual parameters when a first set of operational safety mode initiation criteria of the plurality of sets of operational safety mode initiation criteria is valid, the first set of operational safety mode initiation criteria comprising criteria that are met when movement of the electronic device exceeds a threshold movement value; in response to detecting the first set of one or more context parameters: in accordance with a determination that the first set of contextual parameters meets a first set of operational safety mode initiation criteria, initiating an operational safety mode; detecting a second set of one or more contextual parameters when a second set of operational safety mode initiation criteria of the plurality of sets of operational safety mode initiation criteria is valid, the second set of operational safety mode initiation criteria including criteria that are met when the electronic device is connected to a second electronic device associated with the motor vehicle; in response to detecting the second set of one or more context parameters: starting the operational safety mode in response to determining that the second set of contextual parameters meets a second set of operational safety mode start criteria; in accordance with a determination that the second set of contextual parameters does not satisfy the second set of operational safety mode enablement criteria, the operational safety mode is aborted upon satisfaction of the first set of operational safety mode enablement criteria.

Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are optionally included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

Example transitory computer-readable storage media are disclosed herein. An example non-transitory computer-readable storage medium stores one or more programs configured for execution by one or more processors of an electronic device with a display, the one or more programs including instructions for: detecting one or more context parameters; initiating a safe mode of operation based on one or more contextual parameters satisfying safe mode of operation initiation criteria, the safe mode of operation initiation criteria including criteria that are satisfied when the contextual parameters indicate that the electronic device is located within a running motor vehicle; when the device is in a secure mode of operation: receiving a notification; in accordance with a determination that the notification satisfies a set of notification output criteria, causing an output corresponding to the notification; and in accordance with a determination that the notification does not satisfy the set of notification output criteria, forgoing causing output corresponding to the notification.

An example transitory computer-readable storage medium stores one or more programs configured for execution by one or more processors of an electronic device with a display, the one or more programs including instructions for: while in the operational safety mode: receiving a communication from a contact; in accordance with a determination that the communication satisfies a notification output criterion, outputting a notification corresponding to the communication, the notification output criterion including a criterion that is satisfied when the communication includes a notification output request; and in accordance with a determination that the communication does not satisfy the notification output criteria, forgoing outputting the notification.

An example transitory computer-readable storage medium stores one or more programs configured for execution by one or more processors of an electronic device with a display, the one or more programs including instructions for: detecting a first set of one or more contextual parameters when a first set of operational safety mode initiation criteria of the plurality of sets of operational safety mode initiation criteria is valid, the first set of operational safety mode initiation criteria comprising criteria that are met when movement of the electronic device exceeds a threshold movement value; in response to detecting the first set of one or more context parameters: in accordance with a determination that the first set of contextual parameters meets a first set of operational safety mode initiation criteria, initiating an operational safety mode; detecting a second set of one or more contextual parameters when a second set of operational safety mode initiation criteria of the plurality of sets of operational safety mode initiation criteria is valid, the second set of operational safety mode initiation criteria including criteria that are met when the electronic device is connected to a second electronic device associated with the motor vehicle; in response to detecting the second set of one or more context parameters: starting the operational safety mode in response to determining that the second set of contextual parameters meets a second set of operational safety mode start criteria; in accordance with a determination that the second set of contextual parameters does not satisfy the second set of operational safety mode initiation criteria, the operational safety mode is aborted upon satisfaction of the first set of operational safety mode initiation criteria.

Thus, faster, more efficient methods and interfaces are provided for devices for managing the output of notifications, and certain modes of operation are provided when certain parameters are detected, thereby improving the effectiveness, efficiency, and user satisfaction of these devices. Such methods and interfaces may supplement or replace other methods for managing notification output that provides an operational mode.

Drawings

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 designate corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.

Fig. 1B is a block diagram illustrating exemplary components for event processing, according to some embodiments.

FIG. 2 illustrates a portable multifunction device with a touch screen in accordance with some embodiments.

Fig. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

Figure 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device according to some embodiments.

FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface separate from a display, in accordance with some embodiments.

Fig. 5A illustrates a personal electronic device, according to some embodiments.

Fig. 5B is a block diagram illustrating a personal electronic device, according to some embodiments.

Fig. 5C-5D illustrate exemplary components of a personal electronic device with a touch-sensitive display and an intensity sensor, according to some embodiments.

Fig. 5E-5H illustrate exemplary components and user interfaces of a personal electronic device, according to some embodiments.

Fig. 6A-6I illustrate examples of operating a secure mode according to some embodiments.

Fig. 7A-7D illustrate example user interfaces during a secure mode of operation, according to some embodiments.

Fig. 8 is a flow diagram illustrating an example method for operating a secure mode, including filtering output of notifications based on notification output criteria, according to some embodiments.

Fig. 9 is a flow diagram illustrating another example method for operating a secure mode, including suppressing output of notifications that do not meet notification output criteria, including criteria for an output request of a sender tag, according to some embodiments.

Fig. 10 is a flow diagram illustrating yet another example method for operating a secure mode, including initiating the secure mode of operation, according to some embodiments.

Detailed Description

The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure, but is instead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methods and interfaces for secure operations, such as initiating a secure mode of operation based on a detected context (e.g., environmental context), and methods and interfaces for managing notifications and communications during the secure mode of operation to facilitate secure operations. Such techniques may reduce the cognitive burden on users accessing and/or otherwise receiving notifications and communications, thereby improving productivity and secure use of the device. Moreover, such techniques may reduce processor power and battery power that would otherwise be wasted on redundant user inputs.

Further, the methods and interfaces disclosed herein facilitate safe use of the electronic device in certain situations, such as when the electronic device is in a vehicle (e.g., an automobile, motorcycle, airplane, boat, bicycle, etc.) and when a user of the device is operating the vehicle. As described herein, in some examples, the device operates in a safe mode of operation that reduces the temptation to send and/or receive communications (e.g., text messages, email) and reduces the urge to check the device while driving. In some examples, a safe mode of operation is enhanced in which custom behavior is customized to the driving experience to prevent driver distraction while preventing drivers from being unresponsive to communications from certain users of other electronic devices. In some examples, the device may distinguish whether the device is associated with a driver of the vehicle that may be aware of the safe mode of operation, or whether the device is associated with a passenger in the vehicle that may not necessarily need to operate the safe mode. In another aspect, in some examples, the secure mode of operation facilitates secure use and custom behavior by providing a larger and/or larger tap target to the user interface to facilitate interaction and navigation of certain applications as the electronic device detects and/or various contexts associated with the electronic device. In some examples discussed below, the electronic device includes voice control, and during the secure mode of operation, the voice control includes a detailed mode of operation that provides a higher level of voice guidance, thereby further reducing the need for the user to browse the device. In some examples, a secure mode locking device (e.g., locking a user interface and voice control) is operated to prevent potentially suspicious behavior by a user when certain circumstances are detected at an electronic device.

1A-1B, 2, 3, 4A-4B, and 5A-5H provide descriptions of exemplary devices for performing techniques for operating a secure mode. Fig. 6A to 6I show examples of the operation security mode. Fig. 8-10 are flow diagrams illustrating methods of operating a secure mode according to some embodiments. Fig. 6A to 6I are used to explain the processes described below, including the processes in fig. 8 to 10. Fig. 7A-7D illustrate example user interfaces for operating a secure mode. The user interfaces in fig. 7A to 7D are used to illustrate the processes described below, including the processes in fig. 8 to 10.

The present disclosure relates to U.S. provisional patent application No.15/596,592 entitled "UE Motion Based on Cellular Parameters," filed on 16.5.2017, which describes systems and techniques related to providing improved Motion estimation Based on Cellular Parameters, and is hereby incorporated by reference. For example, U.S. provisional patent application No.15/596,592 proposes an embodiment of a user equipment device (UE) and an associated method for enabling the UE to estimate the velocity of the UE based on cellular parameters. In some embodiments, a first speed of the UE may be estimated based on a first set of parameters associated with one or more cell-based metrics. The doppler measurement may be performed in response to the first velocity exceeding a velocity threshold for at least a period of time. In some embodiments, performing (or making) a doppler measurement may be triggered by (e.g., in response to) the first velocity exceeding a velocity threshold for at least a first time period, and receiving an indication from a motion processor of the UE that the UE is in a non-stationary state. Additionally, a second velocity of the UE may be estimated based on the first set of parameters and the doppler measurements.

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

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

Depending on the context, the term "if" is optionally to be interpreted to mean "when", "at. Similarly, the phrase "if determined … …" or "if [ stated condition or event ] is detected" is optionally to be construed to mean "upon determination … …" or "in response to determination … …" or "upon detection of [ stated condition or event ] or" in response to detection of [ stated condition or event ] ", depending on the context.

Embodiments of electronic devices, user interfaces for such devices, and related processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, but are not limited to, those from Apple Inc

Device and iPod

An apparatus, and

an apparatus. Other portable electronic devices are optionally used, such as laptops or tablets 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 is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or touchpad).

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.

The device typically supports various applications, such as one or more of the following: a mapping application, a rendering application, a word processing application, a website creation application, a disc editing application, a spreadsheet application, a gaming application, a telephone 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.

Various applications executing 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 within respective applications. As such, a common physical architecture of the device (such as a touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and transparent to the user.

Attention is now directed to embodiments of portable devices having touch sensitive displays. FIG. 1A is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to or called a "touch-sensitive display system". Device 100 includes memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral interface 118, RF circuitry 108, audio circuitry 110, speaker 111, 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. Device 100 optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on device 100 (e.g., a touch-sensitive surface, such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch panel 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

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 substitute (surrogate) for the force or pressure of a contact on the touch-sensitive surface. The intensity of the 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 the 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 forces at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine the estimated contact force. Similarly, the pressure sensitive tip of the 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 changes thereof, the capacitance of the touch-sensitive surface in the vicinity of the contact and/or changes thereof and/or the resistance of the touch-sensitive surface in the vicinity of the contact and/or changes thereof are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the surrogate measurement of contact force or pressure is used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the surrogate measurement). In some implementations, the surrogate measurement of contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). The intensity of the contact is used as a property of the user input, allowing the user to access additional device functionality that in some cases would not be accessible to the user on a smaller-sized device with limited physical area for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or physical/mechanical controls, such as knobs or buttons).

As used in this specification and claims, the term "haptic 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 a center of mass of the device that is to be detected by a user with the user's sense of touch. For example, where the device or component of the device is in contact with a surface of the user that is sensitive to touch (e.g., a finger, palm, or other portion of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in a physical characteristic of the device or component of the device. For example, movement of the touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "down click" or "up click" of a physical 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 is not moving. As another example, even when there is no change in the smoothness of the touch sensitive surface, the movement of the touch sensitive surface is optionally interpreted or sensed by the user as "roughness" of the touch sensitive surface. While such interpretation of touch by a user will be limited by the user's individualized sensory perception, many sensory perceptions of touch are common to most users. Thus, when a haptic output is described as corresponding to a particular sensory perception of a user (e.g., "click down," "click up," "roughness"), unless otherwise stated, the generated haptic output corresponds to a physical displacement of the device or a component thereof that would generate the sensory perception of a typical (or ordinary) user. Providing haptic feedback to a user using haptic output 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 error in operating/interacting with the device), thereby further reducing power usage and extending the battery life of the device by enabling the user to use the device more quickly and efficiently.

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 these components. The various components shown in fig. 1A 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.

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

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

RF (radio frequency) circuitry 108 receives and transmits RF signals, also referred to as electromagnetic signals. The RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communication networks and other communication devices via electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a Subscriber Identity Module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks such as the internet, also known as the World Wide Web (WWW), intranets, and/or wireless networks such as cellular telephone networks, wireless Local Area Networks (LANs), and/or Metropolitan Area Networks (MANs), and other devices via wireless communication. RF circuitry 108 optionally includes well-known circuitry for detecting Near Field Communication (NFC) fields, such as by short-range communication radios. The wireless communication optionally uses any of a number of communication standards, protocols, and techniques, 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 +, 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 Low Power consumption (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), Voice over Internet protocol (VoIP), Wi-MAX, 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 with extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol including communication protocols not yet developed at the time of filing date of this document.

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

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

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 a gesture on the touch screen, as described in U.S. patent application 11/322,549 (i.e., U.S. patent No.7,657,849) entitled "Unlocking a Device by Forming improvements on devices on an Unlock Image," filed on 23.12.2005, which is hereby incorporated by reference in its entirety. A long press of a button (e.g., 206) optionally turns the device 100 on or off. The functionality of one or more buttons is optionally customizable by the user. The touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an output interface between the device and the user. Display controller 156 receives electrical signals from touch screen 112 and/or transmits electrical signals to touch screen 112. Touch screen 112 displays visual output to a user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively "graphics"). In some embodiments, some or all of the visual output optionally corresponds to a user interface object.

Touch screen 112 has a touch-sensitive surface, sensor, or group of sensors that accept input from a user based on tactile sensation and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user interface objects (e.g., one or more soft keys, icons, web pages, or images) displayed on touch screen 112. In an exemplary embodiment, the point of contact between touch screen 112 and the user corresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a 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 touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that available from Apple Inc

And iPod

The technique used in (1).

The touch sensitive display in some embodiments of touch screen 112 is optionally similar to a multi-touch sensitive trackpad 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, whereas touch-sensitive touchpads do not provide visual output.

In some embodiments, the touch sensitive display of touch screen 112 is as described in the following patent applications: (1) U.S. patent application No. 11/381,313 entitled "multi point Touch Surface Controller" filed on 2006, 5/2; (2) U.S. patent application No.10/840,862 entitled "Multipoint touch screen" filed on 6.5.2004; (3) U.S. patent application No. 10/903,964 entitled "Gestures For Touch Sensitive Input Devices" filed on 30.7.2004; (4) U.S. patent application No. 11/048,264 entitled "Gestures For Touch Sensitive Input Devices" filed on 31/1/2005; (5) U.S. patent application No.11/038,590 entitled "model-Based Graphical User Interfaces For Touch Sensitive Input Devices" filed on 18.1.2005; (6) U.S. patent application No.11/228,758 entitled "Virtual Input Device On A Touch Screen User Interface" filed On 16.9.2005; (7) U.S. patent application No.11/228,700 entitled "Operation Of A Computer With A Touch Screen Interface," filed on 16.9.2005; (8) U.S. patent application No.11/228,737 entitled "Activating Virtual Keys Of A Touch-Screen Virtual Keys" filed on 16.9.2005; and (9) U.S. patent application No.11/367,749 entitled "Multi-Functional Hand-Held Device" filed 3/2006. All of these applications are incorporated herein by reference in their entirety.

The touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, finger, or the like. In some embodiments, the user interface is designed to work primarily with 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 translates the rough finger-based input into a precise pointer/cursor position or command for performing the action desired by the user.

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

The device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, Alternating Current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a Light Emitting Diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.

The device 100 optionally further includes one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to an optical sensor controller 158 in the I/O subsystem 106. The optical sensor 164 optionally includes a Charge Coupled Device (CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The optical sensor 164 receives light from the environment projected through one or more lenses and converts the light into data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that images of the user are optionally acquired for the video conference while the user views other video conference participants on the touch screen display. In some implementations, the position of the optical sensor 164 can be changed by the user (e.g., by rotating a lens and sensor in the device housing) such that a single optical sensor 164 is used with the touch screen display for both video conferencing and still image and/or video image capture.

Device 100 optionally further comprises one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to an intensity sensor controller 159 in the I/O subsystem 106. Contact intensity 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 intensity sensors (e.g., sensors for measuring the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some implementations, at least one contact intensity sensor is collocated with or proximate to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

The device 100 optionally further includes one or more proximity sensors 166. Fig. 1A shows a proximity sensor 166 coupled to the peripheral 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 optionally performs as described in the following U.S. patent applications: no.11/241,839, entitled "Proximaty Detector In Handheld Device"; no.11/240,788, entitled "Proximaty Detector In Handheld Device"; no.11/620,702, entitled "Using Ambient Light Sensor To Automation Generator Sensor Output"; no.11/586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and No.11/638,251 entitled "Methods And Systems For Automatic Configuration Of Peripherals", which is hereby incorporated by reference in its entirety. In some embodiments, the proximity sensor turns off and disables the touch screen 112 when the multifunction device is placed near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally further comprises one or more tactile output generators 167. FIG. 1A shows a haptic output generator coupled to a haptic feedback controller 161 in the I/O subsystem 106. Tactile output generator 167 optionally includes one or more electro-acoustic devices, such as speakers or other audio components; and/or an electromechanical device that converts energy into linear motion, such as a motor, solenoid, electroactive aggregator, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts an electrical signal into a tactile output on the device). Contact intensity sensor 165 receives haptic feedback generation instructions from haptic feedback module 133 and generates haptic output on device 100 that can be felt by a user of device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112), and optionally generates tactile output by moving the touch-sensitive surface vertically (e.g., into/out of the surface of device 100) or laterally (e.g., back and forth in the same plane as the surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

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

In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or set of instructions) 128, a contact/motion module (or set of instructions) 130, a graphics module (or set of instructions) 132, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and an application program (or set of instructions) 136. Further, in some embodiments, memory 102 (fig. 1A) or 370 (fig. 3) stores device/global internal state 157, as shown in fig. 1A and 3. Device/global internal state 157 includes one or more of: an active application state indicating which applications (if any) are currently active; display state indicating what applications, views, or other information occupy various areas of the touch screen display 112; sensor status, including information obtained from the various sensors of the device and the input control device 116; and location information regarding the location and/or pose of the device.

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

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 circuitry 108 and/or the external ports 124. External port 124 (e.g., Universal Serial Bus (USB)Fire wire, etc.) are adapted to be coupled directly to other devices or indirectly via a network (e.g., the internet, wireless LAN, etc.). In some embodiments, the external port is an external port

(trademark of Apple inc.) the 30-pin connectors used on devices are the same or similar and/or compatible multi-pin (e.g., 30-pin) connectors.

Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch sensitive devices (e.g., a touchpad or a 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-down event), determining contact intensity (e.g., force or pressure of contact, or a substitute for force or pressure of contact), determining whether there is movement of contact and tracking movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining whether contact has ceased (e.g., detecting a finger-up event or a contact-breaking). The contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact represented by the series of contact data optionally includes determining velocity (magnitude), velocity (magnitude and direction), and/or acceleration (change in magnitude and/or direction) of the point of contact. These operations are optionally applied to single point contacts (e.g., single finger contacts) or multiple point simultaneous contacts (e.g., "multi-touch"/multiple finger contacts). In some embodiments, the contact/motion module 130 and the display controller 156 detect contact on the touch panel.

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

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 detected contacts). Thus, the gesture is optionally detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event, and then detecting a finger-up (lift-off) event at the same location (or substantially the same location) as the finger-down event (e.g., at the location of the icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event, then detecting one or more finger-dragging events, and then subsequently detecting a finger-up (lift-off) event.

Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual characteristics) of the displayed graphics. As used herein, the term "graphic" includes any object that may be displayed to a user, including without limitation text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations and the like.

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

Haptic feedback module 133 includes various software components for generating instructions for use by one or more haptic output generators 167 to produce haptic outputs at one or more locations on device 100 in response to user interaction with device 100.

Text input module 134, which is optionally a component of graphics module 132, provides a soft keyboard for entering text in various applications such as contacts 137, email 140, IM 141, browser 147, and any other application that requires text input.

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

Application 136 optionally includes the following modules (or sets of instructions), or a subset or superset thereof:

a contacts module 137 (sometimes referred to as an address book or contact list);

a phone module 138;

a video conferencing module 139;

an email client module 140;

an Instant Messaging (IM) module 141;

fitness support module 142;

a camera module 143 for still and/or video images;

an image management module 144;

a video player module;

a music player module;

a browser module 147;

a calendar module 148;

desktop applet module 149, optionally including one or more of: a weather desktop applet 149-1, a stock market desktop applet 149-2, a calculator desktop applet 149-3, an alarm desktop applet 149-4, a dictionary desktop applet 149-5, and other desktop applets acquired by the user, and a user created desktop applet 149-6;

a desktop applet creator module 150 for forming a user-created desktop applet 149-6;

a search module 151;

a video and music player module 152 that incorporates a video player module and a music player module;

a notepad module 153;

a map module 154; and/or

Online video module 155.

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.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 is optionally used to manage contact lists or contact lists (e.g., stored in memory 102 or in application internal state 192 of contacts module 137 in memory 370), including: adding one or more names to the address book; deleting one or more names from the address book; associating one or more telephone numbers, one or more email addresses, one or more physical addresses, or other information with the name; associating the image with a name; classifying and ordering names; providing a telephone number or email address to initiate and/or facilitate communication through telephone 138, video conferencing module 139, email 140, or IM 141; and so on.

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

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephony module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate video conferences between the user and one or more other participants according to user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions to create, send, receive, and manage emails in response to user instructions. In conjunction with the image management module 144, the email client module 140 makes it very easy to create and send an email with a still image or a video image captured by the camera module 143.

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

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

In conjunction with 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, camera module 143 includes executable instructions for: capturing still images or video (including video streams) and storing them in the memory 102, modifying features of the still images or video, or deleting the still images or video from the memory 102.

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

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions for browsing the internet according to user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, email client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do, etc.) according to user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the desktop applet module 149 is a mini-application (e.g., weather desktop applet 149-1, stock market desktop applet 149-2, calculator desktop applet 149-3, alarm clock desktop applet 149-4, and dictionary desktop applet 149-5) or a mini-application created by a user (e.g., user created desktop applet 149-6) that is optionally downloaded and used by the user. In some embodiments, the desktop applet includes an HTML (hypertext markup language) file, a CSS (cascading style sheet) file, and a JavaScript file. In some embodiments, the desktop applet includes an XML (extensible markup language) file and a JavaScript file (e.g., Yahoo! desktop applet).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the desktop applet creator module 150 is optionally used by a user to create a desktop applet (e.g., convert a user-specified portion of a web page into a desktop applet).

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions for searching memory 102 for text, music, sound, images, video, 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.

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

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notepad module 153 includes executable instructions to create and manage notepads, backlogs, and the like according to user instructions.

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

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, 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 a touch screen or on an external display connected via external port 124), send an email with a link to a particular online video, and otherwise manage online video in one or more file formats, such as h.264. In some embodiments, the link to the particular online video is sent using instant messaging module 141 instead of email client module 140. Additional description of Online video applications can be found in U.S. provisional patent application 60/936,562 entitled "Portable Multi function Device, Method, and Graphical User Interface for Playing Online video," filed on.20.2007 and U.S. patent application 11/968,067 entitled "Portable Multi function Device, Method, and Graphical User Interface for Playing Online video," filed on.31.2007, both of which are hereby incorporated by reference in their entirety.

Each of the modules and applications described above corresponds to a set of executable instructions for performing one or more of the functions described above as well as the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus 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., video and music player module 152 in fig. 1A). In some embodiments, memory 102 optionally stores a subset of the modules and data structures described above. Further, memory 102 optionally stores additional modules and data structures not described above.

In some embodiments, device 100 is a device on which the operation of a predefined set of functions is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or trackpad 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.

The predefined set of functions performed exclusively by the touchscreen and/or trackpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by a user, navigates device 100 from any user interface displayed on device 100 to a main, home, or root menu. In such embodiments, a touchpad is used to implement a "menu button". In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

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

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

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

Event monitor 171 receives event information from peripheral interface 118. The event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and/or microphone 113 (via audio circuitry 110). Information received by peripheral interface 118 from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

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

In some embodiments, event classifier 170 further includes hit view determination module 172 and/or active event recognizer determination module 173.

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

Another aspect of the user interface associated with an application is a set of views, sometimes referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application view (of the respective application) in which the touch is detected optionally corresponds to a programmatic level within a programmatic or view hierarchy of applications. 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 identified as correct inputs is optionally determined based at least in part on the hit view of the initial touch that initiated the touch-based gesture.

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

The 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 implementations, the 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 thus determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if the touch sub-event is completely confined to the area associated with a particular view, the higher views in the hierarchy will remain actively participating views.

The event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers event information to event recognizers determined by active event recognizer determination module 173. In some embodiments, the event dispatcher module 174 stores event information in an event queue, which is retrieved by the respective event receiver 182.

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

In some embodiments, the application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, the respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of the event recognizers 180 are part of a separate module that is a higher-level object such as a user interface toolkit (not shown) or application 136-1 that inherits methods and other properties from it. In some embodiments, the respective event handlers 190 comprise one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

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

The event receiver 182 receives event information from the event sorter 170. The event information includes information about a sub-event such as a touch or touch movement. According to the sub-event, the event information further includes additional information, such as the location of the sub-event. When the sub-event relates to motion of a touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event comprises rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information comprises corresponding information about the current orientation of the device (also referred to as the device pose).

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

In some embodiments, event definition 187 includes definitions of events for respective user interface objects. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view that displays 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 respective event handler 190, the event comparator uses the results of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects the event handler associated with the sub-event and the object that triggered the hit test.

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

When the respective event recognizer 180 determines that the sequence of sub-events does not match any event in the event definition 186, the respective event recognizer 180 enters an event not possible, 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.

In some embodiments, the respective event recognizer 180 includes metadata 183 with configurable attributes, tags, 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 attributes, flags, and/or lists that indicate how or how event recognizers interact with each other. In some embodiments, metadata 183 includes configurable attributes, flags, and/or lists that indicate whether a sub-event is delivered to a different level in the view or programmatic hierarchy.

In some embodiments, when one or more particular sub-events of an event are identified, the respective event identifier 180 activates the event handler 190 associated with the event. In some embodiments, the respective event identifier 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and deferring) sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a marker associated with the recognized event, and the event handler 190 associated with the marker retrieves the marker and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about sub-events without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the sub-event sequence or to actively participating views. Event handlers associated with the sequence of sub-events or with actively participating views receive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, the data updater 176 updates a phone number used in the contacts module 137 or stores a video file used in the video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user interface object or updates the location of a user interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on the touch-sensitive display.

In some embodiments, one or more event handlers 190 include or have access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

It should be understood that the above discussion of event processing with respect to user touches on a touch sensitive display also applies to other forms of user input utilizing an input device to operate multifunction device 100, not all of which are initiated on a touch screen. For example, mouse movements and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holds; contact movements on the touchpad, such as tapping, dragging, scrolling, etc.; inputting by a stylus; movement of the device; verbal instructions; detected eye movement; inputting biological characteristics; and/or any combination thereof, is optionally used as input corresponding to sub-events defining the event to be identified.

Fig. 2 illustrates a portable multifunction device 100 with a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within the User Interface (UI) 200. In this embodiment, as well as other embodiments described below, a user can select one or more of these graphics by making gestures on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics will occur when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (left to right, right to left, up, and/or down), and/or a rolling of a finger (right to left, left to right, up, and/or down) that has made contact with device 100. In some implementations, or in some cases, inadvertent contact with a graphic does not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that swipes over the application icon optionally does not select the corresponding application.

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 buttons are implemented as soft keys in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu buttons 204, push buttons 206 for powering the device on/off and for locking the device, one or more volume adjustment buttons 208, a Subscriber Identity Module (SIM) card slot 210, a headset jack 212, and docking/charging external port 124. Pressing the button 206 optionally serves to turn the device on/off by pressing the button and holding the button in a pressed state for a predefined time interval; locking the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or unlocking the device or initiating an unlocking process. In an alternative embodiment, device 100 also accepts voice input through microphone 113 for activating or deactivating certain functions. Device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contacts on touch screen 112, and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.

Fig. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. The device 300 need not be portable. In some embodiments, the device 300 is a laptop, desktop, tablet, multimedia player device, navigation device, educational device (such as a child learning toy), gaming system, or control device (e.g., a home controller or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuitry (sometimes referred to as a chipset) that interconnects and controls communication between system components. Device 300 includes an input/output (I/O) interface 330 with a display 340, typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 (e.g., similar to one or more tactile output generators 167 described above with reference to fig. 1A) for generating tactile outputs on device 300, sensors 359 (e.g., optical sensors, acceleration sensors, proximity sensors, touch-sensitive sensors, and/or contact intensity sensors (similar to one or more contact intensity sensors 165 described above with reference to fig. 1A)). Memory 370 includes high speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 370 optionally includes one or more storage devices located remotely from one or more CPUs 310. In some embodiments, memory 370 stores programs, modules, and data structures similar to or a subset of the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (fig. 1A). Further, 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 drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk editing module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

Each of the above elements in fig. 3 is optionally stored in one or more of the previously mentioned memory devices. Each of the above modules corresponds to a set of instructions for performing a function described above. The modules or programs (e.g., sets of instructions) described above need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures described above. Further, memory 370 optionally stores additional modules and data structures not described above.

Attention is now directed to embodiments of user interfaces optionally implemented on, for example, portable multifunction device 100.

Figure 4A illustrates an exemplary user interface of an application menu on portable multifunction device 100 in accordance with some embodiments. A similar user interface is optionally implemented on device 300. In some embodiments, the user interface 400 includes the following elements, or a subset or superset thereof:

one or more signal strength indicators 402 of one or more wireless communications, such as cellular signals and Wi-Fi signals;

time 404;

a bluetooth indicator 405;

a battery status indicator 406;

tray 408 with icons of common applications, such as:

an icon 416 of the phone module 138 labeled "phone", the icon 416 optionally including an indicator 414 of the number of missed calls or voice messages;

an icon 418 of the email client module 140 labeled "mail", the icon 418 optionally including an indicator 410 of the number of unread emails;

icon 420 of the browser module 147, labeled "browser"; and

icon 422 labeled "iPod" for video and music player module 152 (also known as iPod (trademark of Apple inc.) module 152); and

icons for other applications, such as:

icon 424 of IM module 141 labeled "message";

icon 426 of calendar module 148 labeled "calendar";

icon 428 of image management module 144 labeled "photo";

icon 430 of camera module 143 labeled "camera";

icon 432 for online video module 155 labeled "online video";

an icon 434 of the O stock desktop applet 149-2 labeled "stock market";

icon 436 of map module 154 labeled "map";

icon 438 labeled "weather" for weather desktop applet 149-1;

icon 440 of alarm clock desktop applet 149-4 labeled "clock";

icon 442 labeled "fitness support" for fitness support module 142;

icon 444 of O notepad module 153 labeled "notepad"; and

the set application or module icon 446 labeled "set" provides access to the settings of the device 100 and its various applications 136.

It should be noted that the icon labels shown in fig. 4A are merely exemplary. For example, icon 422 of video and music player module 152 is labeled "music" or "music player". Other tabs are optionally used for the various application icons. In some embodiments, the label of the respective application icon includes a name of the application corresponding to the respective 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.

Fig. 4B illustrates an exemplary user interface on a device (e.g., device 300 of fig. 3) having a touch-sensitive surface 451 (e.g., tablet or touchpad 355 of fig. 3) separate from a display 450 (e.g., touchscreen display 112). Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting the intensity of contacts on touch-sensitive surface 451, and/or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.

Although some of the examples below will be given with reference to input on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, as shown in fig. 4B. In some implementations, the touch-sensitive surface (e.g., 451 in fig. 4B) has a primary axis (e.g., 452 in fig. 4B) that corresponds to a primary axis (e.g., 453 in fig. 4B) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in fig. 4B) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in fig. 4B, 460 corresponds to 468 and 462 corresponds to 470). As such, when the touch-sensitive surface (e.g., 451 in fig. 4B) is separated from the display (450 in fig. 4B) of the multifunction device, user inputs (e.g.,

contacts

460 and 462 and their movements) detected by the device on the touch-sensitive surface are used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for the other user interfaces described herein.

Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contact, single-finger tap gesture, finger swipe gesture), it should be understood that in some embodiments one or more of these finger inputs are replaced by inputs from another input device (e.g., mouse-based inputs or stylus inputs). For example, the swipe gesture is optionally replaced by a mouse click (e.g., rather than a contact), followed by movement of the cursor along the path of the swipe (e.g., rather than movement of the contact). As another example, a flick gesture is optionally replaced by a mouse click (e.g., instead of detecting a contact, followed by ceasing to detect a contact) while the cursor is over the location of the flick gesture. Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or mouse and finger contacts are optionally used simultaneously.

Fig. 5A illustrates an exemplary personal electronic device 500. The device 500 includes a body 502. In some embodiments, device 500 may include some or all of the features described with respect to devices 100 and 300 (e.g., fig. 1A-4B). In some embodiments, the device 500 has a touch-sensitive display screen 504, hereinafter referred to as a touch screen 504. Instead of or in addition to the touch screen 504, the device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of an applied contact (e.g., touch). One or more intensity sensors of the touch screen 504 (or touch-sensitive surface) may provide output data representing the intensity of a touch. The user interface of device 500 may respond to the touch based on the intensity of the touch, meaning that different intensities of the touch may invoke different user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related patent applications: international patent Application Ser. No. PCT/US2013/040061, entitled "Device, Method, and Graphical User Interface for Displaying User Interface Objects reforming to an Application", filed on 8.5.2013, published as WIPO patent publication No. WO/2013/169849; and International patent application Ser. No. PCT/US2013/069483 entitled "Device, Method, and Graphical User Interface for transiting Between Touch Input to Display Output Relationships", filed on 11/2013, published as WIPO patent publication No. WO/2014/105276, each of which is hereby incorporated by reference in its entirety.

In some embodiments, the device 500 has one or

more input mechanisms

506 and 508. The input mechanisms 506 and 508 (if included) may be in physical form. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, may allow for attachment of the device 500 with, for example, a hat, glasses, earrings, necklace, shirt, jacket, bracelet, watchband, bracelet, pants, belt, shoe, purse, backpack, and the like. These attachment mechanisms allow the user to wear the device 500.

Fig. 5B illustrates an exemplary personal electronic device 500. In some embodiments, the apparatus 500 may include some or all of the components described with reference to fig. 1A, 1B, and 3. The device 500 has a bus 512 that operatively couples an I/O portion 514 with one or more computer processors 516 and a memory 518. The I/O portion 514 may be connected to the display 504, which may have a touch sensitive member 522 and optionally an intensity sensor 524 (e.g., a contact intensity sensor). Further, I/O portion 514 may interface with communication unit 530 for receiving application programs and operating system data using Wi-Fi, Bluetooth, Near Field Communication (NFC), cellular, and/or other wireless communication techniques. Device 500 may include input mechanisms 506 and/or 508. For example, the input mechanism 506 is optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, the input mechanism 508 is optionally a button.

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

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, for example, cause the computer processors to perform the techniques described below, including processes 800-1000 (fig. 8-10). A computer readable storage medium may be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with an instruction execution system, apparatus, or device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer readable storage medium may include, but is not limited to, magnetic storage devices, optical storage devices, and/or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or blu-ray technology, and persistent solid state memory such as flash memory, solid state drives, and the like. The personal electronic device 500 is not limited to the components and configuration of fig. 5B, but may include other components or additional components in a variety of configurations.

As used herein, the term "affordance" refers to a user-interactive graphical user interface object that is optionally displayed on a display screen of device 100, 300, and/or 500 (fig. 1A, 3, and 5A-5B). For example, images (e.g., icons), buttons, and text (e.g., hyperlinks) optionally each constitute an affordance.

As used herein, the term "focus selector" refers to an input element that is used to indicate the current portion of the user interface with which the user is interacting. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in fig. 3 or touch-sensitive surface 451 in fig. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted according to the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in fig. 1A or touch screen 112 in fig. 4A) that enables direct interaction with user interface elements on the touch screen display, a contact detected on the touch screen serves as a "focus selector" such that when an input (e.g., a press input by the contact) is detected at a 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 is moved 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 moving the focus from one button to another using tab or arrow keys); in these implementations, the focus selector moves according to movement of the focus between different regions of the user interface. Regardless of the particular form taken by the focus selector, the focus selector is typically a user interface element (or contact on a 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 with which the user of the user interface desires to interact). For example, upon detection of a press input on a touch-sensitive surface (e.g., a touchpad or touchscreen), the location of a focus selector (e.g., a cursor, contact, or selection box) over a respective button will indicate that the user desires to activate the respective button (as opposed to other user interface elements shown on the device display).

As used in the specification and in the claims, the term "characteristic intensity" of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on a plurality of intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples acquired 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 detecting contact, before detecting contact liftoff, before or after detecting contact start movement, before or after detecting contact end, before or after detecting an increase in intensity of contact, and/or before or after detecting a decrease in intensity of contact). The characteristic intensity of the contact is optionally based on one or more of: a maximum value of the intensity of the contact, a mean value of the intensity of the contact, an average value of the intensity of the contact, a value at the top 10% of the intensity of the contact, a half-maximum value of the intensity of the contact, a 90% maximum value of the intensity of the contact, and the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether the user has performed an operation. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact whose characteristic intensity does not exceed the first threshold results in a first operation, a contact whose characteristic intensity exceeds the first intensity threshold but does not exceed the second intensity threshold results in a second operation, and a contact whose characteristic intensity exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strengths and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the respective operation or to forgo performing the respective operation) rather than to determine whether to perform the first operation or the second operation.

FIG. 5C illustrates the detection of multiple contacts 552A-552E on the touch-sensitive display screen 504 using multiple intensity sensors 524A-524D. FIG. 5C also includes an intensity map that shows current intensity measurements of the intensity sensors 524A-524D relative to intensity units. In this example, the intensity measurements of

intensity sensors

524A and 524D are each 9 intensity units, and the intensity measurements of

intensity sensors

524B and 524C are each 7 intensity units. In some implementations, the cumulative intensity is a sum of intensity measurements of the plurality of intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity, i.e., a fraction of the cumulative intensity. FIG. 5D illustrates assigning cumulative intensities to the contacts 552A-552E based on their distances from the center of the force 554. In this example, each of

contacts

552A, 552B, and 552E is assigned a strength of 8 strength units of contact of cumulative strength, and each of

contacts

552C and 552D is assigned a strength of 4 strength units of contact of cumulative strength. More generally, in some implementations, each contact j is assigned a respective intensity Ij, which is a portion of the cumulative intensity a, according to a predefined mathematical function Ij ═ a · (Dj/Σ Di), where Dj is the distance of the respective contact j from the force center, and Σ Di is the sum of the distances of all respective contacts (e.g., i ═ 1 to last) from the force center. The operations described with reference to fig. 5C-5D may be performed using an electronic device similar or identical to

device

100, 300, or 500. In some embodiments, the characteristic intensity of the contact is based on one or more intensities of the contact. In some embodiments, an intensity sensor is used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity map is not part of the displayed user interface, but is included in fig. 5C-5D to assist the reader.

In some implementations, a portion of the gesture is recognized for determining the feature intensity. For example, the touch-sensitive surface optionally receives a continuous swipe contact that transitions from a starting location and reaches an ending location where the contact intensity increases. In this example, the characteristic intensity of the contact at the end location is optionally based on only a portion of the continuous swipe contact, rather than the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is optionally applied to the intensity of the swipe contact before determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted moving average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some cases, these smoothing algorithms eliminate narrow spikes or dips in the intensity of the swipe contact for the purpose of determining the characteristic intensity.

Contact intensity on the touch-sensitive surface is optionally characterized relative to one or more intensity thresholds, such as a contact detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity that: at which intensity the device will perform the operations typically associated with clicking a button of a physical mouse or touchpad.

In some embodiments, the deep press intensity threshold corresponds to an intensity that: at which intensity the device will perform a different operation than that typically associated with clicking a button of a physical mouse or trackpad.

In some embodiments, when a contact is detected whose characteristic intensity is below a light press intensity threshold (e.g., and above a nominal contact detection intensity threshold, a contact below the nominal contact detection intensity threshold is no longer detected), the device will move the focus selector in accordance with movement of the contact on the touch-sensitive surface without performing operations associated with a light press intensity threshold or a deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface drawings.

Increasing the contact characteristic intensity from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a "light press" input. Increasing the contact characteristic intensity from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a "deep press" input. Increasing the contact characteristic intensity from an intensity below the contact detection intensity threshold to an intensity between the contact detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting a contact on the touch surface. The decrease in the characteristic intensity of the contact from an intensity above the contact detection intensity threshold to an intensity below the contact detection intensity threshold is sometimes referred to as detecting lift-off of the contact from the touch surface. In some embodiments, the contact detection intensity threshold is zero. In some embodiments, the contact detection intensity threshold is greater than zero.

In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting a respective press input performed with a respective contact (or contacts), wherein the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or contacts) above a press input intensity threshold. In some embodiments, the respective operation is performed in response to detecting an increase in intensity of the respective contact above a press input intensity threshold (e.g., a "down stroke" of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below the press input intensity threshold, and the respective operation is performed in response to detecting a subsequent decrease in intensity of the respective contact below the press input threshold (e.g., an "up stroke" of the respective press input).

5E-5H illustrate detection of a gesture that includes an intensity of contact 562 from below the light press intensity threshold in FIG. 5E (e.g., "IT" pressure threshold_L") increases in intensity above the deep press intensity threshold in FIG. 5H (e.g.," IT)_D") intensity corresponds to a press input. On the displayed user interface 570, including the application icons 572A-572D displayed in the predefined area 574, a gesture performed with the contact 562 is detected on the touch-sensitive surface 560 while a cursor 576 is displayed over the application icon 572B corresponding to application 2. In some implementations, a gesture is detected on the touch-sensitive display 504. The intensity sensor detects the intensity of the contact on the touch-sensitive surface 560. The device determines that the intensity of contact 562 is at a deep press intensity threshold (e.g., "IT_D") above peak. A contact 562 is maintained on the touch-sensitive surface 560. In response to detecting the gesture, and in accordance with the intensity rising to the deep press intensity threshold during the gesture (e.g., "IT)_D") above, scaled representations 578A-578C (e.g., thumbnails) of the documents most recently opened for application 2 are displayed, as shown in fig. 5F-5H. In some embodiments, the intensity is a characteristic intensity of the contact compared to one or more intensity thresholds. It should be noted that the intensity map for contact 562 is not part of the displayed user interface, but is included in fig. 5E-5H to assist the reader.

In some embodiments, the display of representations 578A-578C includes animation. For example, the representation 578A is initially displayed in proximity to the application icon 572B, as shown in fig. 5F. As the animation progresses, the representation 578A moves upward and a representation 578B is displayed adjacent to the application icon 572B, as shown in fig. 5G. Representation 578A then moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed adjacent to application icon 572B, as shown in fig. 5H. Representations 578A-578C are formed in an array over icon 572B. In some casesIn an embodiment, animation progresses according to the intensity of contact 562, as shown in fig. 5F-5G, where representations 578A-578C appear and press the intensity threshold deep with the intensity of contact 562 (e.g., "IT_D") increases and moves upward. In some embodiments, the intensity at which the animation progresses is a characteristic intensity of the contact. The operations described with reference to fig. 5E-5H may be performed using an electronic device similar or identical to

device

100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoid accidental input sometimes referred to as "jitter," where the device defines or selects a hysteresis intensity threshold having a predefined relationship to the press input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press input intensity threshold, or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above a press input intensity threshold and a subsequent decrease in intensity of the contact below a hysteresis intensity threshold corresponding to the press input intensity threshold, and the respective operation is performed in response to detecting a subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an "upstroke" of the respective press input). Similarly, in some embodiments, a press input is detected only when the device detects an increase in contact intensity from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press input intensity threshold and optionally a subsequent decrease in contact intensity to an intensity at or below the hysteresis intensity, and a corresponding operation is performed in response to detecting the press input (e.g., depending on the circumstances, the increase in contact intensity or the decrease in contact intensity).

For ease of explanation, optionally, a description of an operation performed in response to a press input associated with a press input intensity threshold or in response to a gesture that includes a press input is triggered in response to detection of any of the following: the contact intensity increases above the press input intensity threshold, the contact intensity increases from an intensity below the hysteresis intensity threshold to an intensity above the press input intensity threshold, the contact intensity decreases below the press input intensity threshold, and/or the contact intensity decreases below the hysteresis intensity threshold corresponding to the press input intensity threshold. Additionally, in examples in which operations are described as being performed in response to detecting that the intensity of the contact decreases below the press input intensity threshold, the operations are optionally performed in response to detecting that the intensity of the contact decreases below a hysteresis intensity threshold that corresponds to and is less than the press input intensity threshold.

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

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

the active application currently displayed on the display screen of the device that is using the application;

a background application (or background process) that is not currently displayed but one or more processes of the application are being processed by one or more processors; and

a suspended or dormant application that is not running but has state information stored in memory (volatile and non-volatile, respectively) and available to resume execution of the application.

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

Attention is now directed 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.

Fig. 6A-6I illustrate examples showing an electronic device 600 having a secure mode of operation, according to some embodiments. The examples in these figures are used to illustrate the processes described below, including the processes in fig. 8-10.

In fig. 6A, the electronic device 600 is located within an operating motor vehicle 602 (e.g., a car) driven by a user 604 (e.g., John 604) of the device 600. When device 600 is not operating in the operational security mode, device 600 operates in a normal (e.g., default or other non-operational security mode) mode in which notifications are output regardless of whether they satisfy notification output criteria associated with the operational security mode. For example, when John is seated in the non-moving vehicle in fig. 6A (e.g., as shown in the speedometer), an external contact 606 (e.g., Jane 606) sends a message (e.g., a text message) from an external electronic device 699 (e.g., 100, 300, 500) to John 604. As shown in FIG. 6A, John's device 600 receives the incoming message and outputs a notification (e.g., "New message from Jane: Hi John!"). In some cases, outputting a notification (e.g., visual, tactile, and/or audible) while the user is operating the motor vehicle is inconvenient and unsafe because it distracts the user from driving.

Turning to FIG. 6B, John is driving a vehicle traveling at 30 Miles Per Hour (MPH), with the device 600 nearby. In fig. 6B, device 600 now operates in a secure mode of operation that manages the output of certain notifications. For example, as described below, during the secure mode of operation, only notifications that meet the notification output criteria are output. As shown in fig. 6B, while John is driving, Jane 606 sends a message from external device 699 to John 604, but when the message arrives, John's device 600 does not display the notification because the notification does not meet the notification output criteria. In some embodiments, John's device 600 remains in the display off state. In some embodiments, a benefit of preventing the display of notifications (or output by tactile and/or audible output) during the safe mode of operation may be suppression of notifications to prevent driver distraction. At the same time, the operational security modes described herein allow for notifications to be output that correspond to certain (e.g., critical) messages or alerts, thereby preventing users from losing important information. In addition, the secure mode of operation provides a technique that allows the user to remain responsive to certain communications, such as by an automatic reply. For ease of discussion, the notifications discussed herein correspond to communications from external contacts, such as text messages. However, the notifications may include alerts corresponding to applications on the device (e.g., games, social media) and/or notifications based on internally generated alerts (e.g., calendar notifications, system alerts).

In some cases of fig. 6B, when the device 600 detects that it is within a moving vehicle 602, the device 600 enters a safe mode of operation (e.g., when moving inside the vehicle at a speed (e.g., 30MPH) above a predetermined threshold speed (e.g., 5 MPH)). For example, the device 600 detects the level of motion based on GPS information (or other location sensor information), information corresponding to a cell tower, and/or Wi-Fi information that exceeds a threshold level of motion indicating that the vehicle 602 is moving. In some examples, the detected motion level is a rate of change of the location coordinates, and the threshold motion level is a threshold rate of change of the location coordinates. In some examples, the detected motion level is a rate of change of a Wi-Fi network or cell tower detected at device 600, and the threshold motion level is a threshold rate of change of the Wi-Fi network. For example, the device 600 detects multiple Wi-Fi hotspots moving around, and/or multiple different Wi-Fi networks over a period of time, or multiple cell towers changing over a period of time, which may indicate that the vehicle 602 is traveling over multiple Wi-Fi networks. In some examples, the detected motion level and the threshold motion level correspond to a speed or acceleration of the vehicle 602. In some examples, device 600 accounts for hysteresis to detect whether vehicle 602 is in stop-and-go traffic and should remain or otherwise resume operating safe mode once the detected motion level falls below a threshold motion level. In some embodiments, the device 600 determines whether the context parameter indicates that the electronic device is located within an operating motor vehicle using one or more of the techniques described in U.S. provisional patent application No.15/596,592.

In some cases of fig. 6B, device 600 enters a safe-mode of operation when device 600 detects that it is located within an operating motor vehicle based on the output of navigation information. For example, the device 600 detects a change in location indicated by a navigation application from the device 600 or an output of turn-by-turn navigation instructions from the second electronic device 608.

In fig. 6B, in some cases, device 600 enters a safe mode of operation when device 600 detects that it is located within an operating motor vehicle. For example, device 600 detects that it is connected to a second electronic device 608 associated with operating motor vehicle 602. In some examples, the second electronic device 608 is a device that is typically present only in or specific to a motor vehicle. For example, the second device 608 is a receiver, a head unit, a car radio integrated on a motor vehicle, an in-vehicle technology and/or infotainment system, such as that provided by Apple, Inc

In some examples, detecting or connecting to a device of this type indicates to device 600 that it is located within motor vehicle 602. In some examples, device 600 detects a motor vehicle specific application or standard at second electronic device 608, and/or the application or standard allows second electronic device 608 to send and/or receive control signals with device 600 via a wired or wireless connection. In some cases, device 600 enters a safe mode of operation when the device receives a signal from second device 608 indicating that motor vehicle 602 is currently operating.

In some cases of FIG. 6B, the electronic device 600 initiates a secure mode of operation and updates a third party application that the device 600 is currently in the secure mode of operation. For example, the third party application is a social media platform, and notifying the application that the user is not currently available may actually enhance the user's experience by providing information to the application that may customize its functionality to the user's current situation (e.g., preventing the user from being unresponsive to other contacts in the application). In some examples, device 600 instructs the paired device (e.g., 100, 300, 500 and/or a watch connected to device 600) to mirror the secure mode of operation.

Nonetheless, in some cases of fig. 6B, device 600 enters a secure mode of operation based on manual activation through a user interface (e.g., a control center interface) provided at device 600 or a connected second electronic device 608. In some cases, manual activation and/or automatic activation based on motion level detection allows the device 600 to enter a safe mode of operation without being connected to the vehicle 602, for example, if the vehicle does not have the second electronic device 608.

Further, in some cases of fig. 6B, the secure mode of operation is turned on or off (e.g., entered or not entered) at the device 600 based on the conditions shown below in table 1. Table 1 shows an example for prioritizing various triggers that cause the secure mode of operation to be initiated. As shown below, device 600 prioritizes the second set of triggers related to the connection criteria (e.g., whether the device is connected to second electronic device 608) as compared to the first set of triggers related to the movement criteria (e.g., whether vehicle 602 is moving at or above a threshold motion level). In some examples, the movement criteria (e.g., the first set of operating security mode initiation criteria) is valid or invalid (e.g., turned off), and whether the connection criteria (e.g., the second set of operating security mode initiation criteria) is valid or invalid is determined based on a user selection at device 600. In some embodiments, the apparatus 600 detects whether the vehicle 602 is moving (e.g., meets a first set of operating safety mode initiation criteria) using one or more techniques described in U.S. provisional patent application No.15/596,592.

TABLE 1

For example, as shown above, when device 600 detects that it is connected to second electronic device 608, the device enters a safe mode of operation regardless of whether device 600 detects that vehicle 602 is moving, and regardless of whether the movement criteria are valid (e.g., (1) - (3) in table 1). For example, when device 600 is connected to second electronic device 608 and meets the connection criteria, and device 600 determines that vehicle 602 is not moving and does not meet the movement criteria, device 600 initiates the safe mode of operation anyway. However, when the device 600 detects that the vehicle 602 is moving and the connection criteria are invalid (e.g., at (7) in table 1), the device enters a safe mode of operation based on the movement criteria being met. In some embodiments, the apparatus 600 determines whether the vehicle 602 is moving (e.g., if the level of movement meets movement criteria) using one or more techniques described in U.S. provisional patent application No.15/596,592.

As further shown above, when device 600 detects that it is not connected to second electronic device 608, the device cannot enter a safe mode of operation regardless of whether device 600 detects that vehicle 602 is moving, and regardless of whether the movement criteria are valid (e.g., (4) - (6) in table 1). For example, when the device 600 is not connected to the second electronic device 608 and therefore does not meet the connection criteria, and the device 600 determines that the vehicle 602 is moving and meets the movement criteria, the device 600 cannot enter the safe mode of operation. In practice, prioritizing the connection criteria over the movement criteria may help to distinguish whether the user is driving his or her vehicle, or whether the user is a passenger of a moving vehicle, and thus may not require operation of the safety mode, thereby reducing instances of undesired activation of the operation of the safety mode. In some cases, when the device 600 detects that the vehicle 602 is not moving and the connection criteria are invalid (e.g., at (8) in table 1), the device cannot enter the operational safety mode based on not satisfying the movement criteria. In some embodiments, the apparatus 600 determines whether the vehicle 602 is not moving (e.g., if the movement level does not meet the movement criteria) using one or more techniques described in U.S. provisional patent application No.15/596,592.

In some embodiments, device 600 exits the operational safety mode of fig. 6B based on detecting that the first and/or set of operational safety mode initiation criteria are no longer satisfied (e.g., are not satisfied immediately or continuously within a predetermined time period), and/or based on a manual user request to exit the operational safety mode. In some cases, device 600 continues to intelligently initiate the operational security mode based on data collected during the learning period. For example, in some cases, the operational safety mode initiation criteria are valid by default until the user selects to deactivate one or more of the operational safety mode initiation criteria. For example, the operational safety mode learning period is valid when the count of the plurality of instances that the device 600 has entered the operational safety mode is below a threshold count. Upon exiting the operational security mode, the device 600 displays a feedback screen (not shown) that allows the user to select whether the operational security mode is intentionally or appropriated to be initiated (e.g., receive a selection of "is it sounds very good" or "is not now" option). Device 600 detects a user selection to rate the experience and stores data in a learning database based on the selection and updates the count by one instance.

In some examples, the feedback screen appears at the end of the first drive or first initiation of the operational safety mode and includes informational text explaining the features of the operational safety mode (e.g., suppressing certain notifications during the operational safety mode, whether the operational safety mode in this example is triggered by connection criteria or movement criteria). In some examples, the feedback screen allows the user to change settings related to operating the secure mode (e.g., whether a detected trigger should continue to be active or inactive, whether other triggers are selected to be active or inactive, certain contacts are whitelisted during operating the secure mode for notification output criteria). In some examples, the first detected trigger to enter the first instance of the operational safety mode is set as the active trigger unless the user chooses to deactivate the trigger (e.g., by setting and/or based on user feedback during learning). In some casesIn some cases, the device automatically disables the triggering (e.g., or a particular set of criteria for triggering) of the operational safety mode in response to determining that the learning database indicates a repeatedly selected mode corresponding to the "not now" option. In such cases, a general purpose setting or may be provided via Apple, Inc

The operational security mode is reactivated for automatic and/or manual initiation.

Turning now to fig. 6C-6I, examples of managing notification output at the device 600 when the device 600 is in the secure mode of operation of fig. 6B are shown. In some examples, notifications that occur during the secure mode of operation are prevented from being output at device 600 and/or second electronic device 608 (e.g., by instructions from device 600 to suppress output) unless the notifications meet notification output criteria. For example, in FIG. 6C, John's device 600 is in a safe mode of operation and outputs a notification corresponding to the message from Jane 606 because Jane is a white list contact, such as an emergency contact and/or favorite contact that allows notification output. In some examples, during the secure mode of operation, notifications corresponding to applications with output permissions, prioritized applications (e.g., navigation providing applications), and/or user-selected prioritized applications or contacts are allowed for notification output.

In some embodiments related to fig. 6C, a notification corresponding to Jane's message is output at John's device 600 during secure mode of operation because Jane is a contact with location sharing access rights. For example, Jane's device 699 is allowed to obtain location information for John's device 600 based on the location sharing activity status or application confirmed by John and/or John's device 600.

In some embodiments related to fig. 6C, a notification corresponding to Jane's message is output at John's device 600 during secure mode of operation because Jane 606 is the closest contact of John's device 600. In some examples, Jane 606 is classified as the closest contact (e.g., by phone or text message) based on the most recent communication with Jane 606 occurring within a predetermined time window in the past since the arrival of the message (e.g., within the past 24 hours) and/or after the secure mode of operation was initiated. In some examples, Jane's recency is based on whether John was actively engaged in a phone call (e.g., answering an incoming call, initiating an outgoing call) or sending an outgoing text message to the contact within a predetermined time window in the past. In some embodiments, allowing notifications from recent contacts may reduce instances of time critical messages being lost (e.g., canceling an appointment at the user's driving destination).

Further, in some examples, if notifications are output during the secure mode of operation, they correspond to repeated communications from a single contact within a time window (e.g., communications that exceed a threshold number of communication attempts within a predetermined time period). For example, John's device 600 outputs notifications for incoming calls or text messages that are repeated calls or text messages from a single contact. In some examples, if the notification corresponds to an incoming telephone call and the device 600 is bluetooth integrated with a second electronic device 608 that allows answering the call from a button provided at the steering wheel of the motor vehicle 602, the notification is output during the secure mode of operation. Nonetheless, in some examples, if the notification corresponds to a system alert (e.g., a battery level alert) or an emergency alert (e.g., an emergency weather alert, a government issued alert, an AMBER alert) indicating the status of the device 600, the notification is output during the safe mode of operation.

Referring now to fig. 6C-6D, in fig. 6C, during the secure mode of operation, in some examples, a notification corresponding to Jane's message is output at John's device 600 because Jane 606 is a contact included in a calendar reminder that is scheduled at the same time or about the same time as the message arrived. For example, John's device 600 includes a calendar event for lunch at 12:30 PM, where Jane is listed as an invitee. Jane's message was received at 12:15 pm and is considered to be within the allowed time period of the calendar event and is therefore output. In practice, the device 600 allows critical contacts (e.g., based on calendar invitation information and/or recency) to reach the user 604 so that the user does not miss critical information, such as regarding whether the meeting to which the user is driving is cancelled or changed. In some examples, device 600 determines that notification of Jane's message should be output based on GPS information matching John's direction of travel with the specified location of the calendar-invited meeting. In other examples as shown in FIG. 6D, external contact 610 (e.g., Emily 610) is not an invitee in the calendar invitation, and therefore, no notification corresponding to her message sent from external device 689 at or about the same time as Jane's message (e.g., 12:15 PM) is output at John's device 600. In some cases, notifications that do not satisfy the notification output condition are stored for later retrieval (e.g., retrieved by a notification center when the device exits the secure mode of operation and/or is in an unlocked state, and/or displayed on a screen such as a lock screen when the secure mode of operation is exited, as shown below at lock screen 708 of fig. 7A).

Turning now to fig. 6E-6H, in some examples, when the notification corresponds to a communication that includes a notification output request, the notification is output during the secure mode of operation. In some examples, the notification output request is a request selected by an external user at an external device that requests the device 600 to output a notification upon receiving a communication from the external device. In some examples, the contact requires permission or white list status from the device 600 to accompany or validate the outgoing request. In some examples, the contact selection notification output request received from the device 600 for an auto-reply is allowed.

For example, as shown in FIG. 6E, external contact 612 (e.g., Shannon 612) sends a message from external device 679 to John 604. John's device 600 is in a secure mode of operation and does not display a notification corresponding to the Shannon's message because the notification does not conform to the notification output criteria. However, in response to receiving her communication during the secure mode of operation, an automatic reply is provided to Shannon. As shown in fig. 6F, John's device 600 automatically responds to Shannon's message by sending an auto-reply to Shannon's device 679. In some examples, the automatic reply includes text indicating that the user 604 is currently operating the motor vehicle 602 and/or text that the notification is currently being suppressed or stored for later retrieval. In some examples, the auto-reply includes the location waypoint of the device 600. Further, in some examples, the auto-reply is a user-defined message that is personalized for a particular contact category, for all contacts allowed to receive the auto-reply, or for a particular contact. In some cases, a single auto-reply is provided for any contact that is allowed to receive an auto-reply. In some examples, the auto-reply includes instructions to circumvent suppression of notifications by providing an explicit notification output request.

Turning to FIG. 6G, after receiving the auto-reply, external contact Shannon 612 considers her message to be important and should be output at John's device 600. In this case, Shannon 612 selects the notification output request to correspond to the previously sent communication or the new communication. A benefit of allowing selection of notification output requests for previously sent communications is that the contact does not have to re-type the message in order to request output at John's device 600. As shown in fig. 6G, when a message is sent with a selected notification output request (e.g., selected at a text instant messaging application for sending communications at Shannon's device 679), John's device 600 displays a notification corresponding to Shannon's message (e.g., "Hi John | I have other recording and can't make it."), in some examples, John's device 600 indicates whether the notification that has been output is being output because it includes a notification output request.

In some examples, after receiving the auto-reply, Shannon 612 decides that the message sent or the new message being sent is not important for output at that time, and therefore does not choose to accompany the notification output request at her device 679. In that case, as shown in the depiction of fig. 6E, the message sent from Shannon's device 679 is not output for notification during John's secure mode of operation of device 600. In this way, the notification output request is associated with only a single message sent from the contact.

Turning to fig. 6H, in another example, notification output requests are implemented for the conversation thread between John 604 and Shannon 612's

devices

600, 679, respectively. For example, in fig. 6H, after Shannon's device 679 receives the auto-reply, and also after Shannon 612 selects the previous notification output request in fig. 6G, Shannon 612 sends a message to John 604 during secure mode of operation. In this case, John's device 600 outputs a new notification corresponding to the new message (e.g., "Can we meet recent instruction. In this case, when John is in secure mode of operation, Shannon 612 does not need to explicitly request notification of the output request whenever she sends a message to John. In some examples, Shannon's conversation is no longer flagged with a notification output request after a period of inactivity in the message thread, and/or after device 600 exits secure mode of operation. In such cases, Shannon 612 will need to reselect the notification output request in some cases after receiving another auto-reply when the device re-enters the same or a new operating security mode session.

In some examples, the notification output request causes John's device 600 to output the notification only when requesting to issue the notification output request from an external contact authorized by device 600 and/or authorized to receive an automated reply from device 600. In some examples, the contact is authorized to select a notification output request from their device when the contact is authorized to receive an auto-reply (as shown above in fig. 6E-6H), when the contact is the closest contact, when the contact shares a location with the recipient, and/or when the contact is a calendar invitee corresponding to a calendar event that occurs at a similar or same time. In some examples, the contact is allowed to receive an automatic reply based on one or more of the same aforementioned criteria.

Turning now to fig. 6I, in some examples, during the secure mode of operation, when device 600 detects Shannon 612 is typing a message to John 604, John's device 600 sends an operational secure mode indication to Shannon's device 679. For example, device 600 is responsive to from ShannonDevice 612 receives the indication of the potential incoming communication and provides a presence indicator to Shannon's device 612. As shown in fig. 6I, Shannon's device 612 outputs a presence indicator (e.g., a steering wheel symbol and/or "John is currently driving") to inform Shannon 612 that John 604 is currently driving, and thus allows Shannon 612 to decide whether to continue entering and sending messages immediately or later. In some examples, device 600 provides presence indicators to all contacts or contacts that meet certain criteria as described above, such as contacts that are allowed to receive automatic replies and/or have location sharing access. In some examples, when two contacts utilize a common instant messaging platform (e.g., iMessage) at their

respective devices

600, 679, a presence indicator (e.g., provided via short messages such as SMS and MMS via short messages such as Apple, Inc

Text message of the service).

Fig. 7A-7D illustrate exemplary user interfaces for operating a secure mode, according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in fig. 8-10. In fig. 7A-7D, a user interface ("UI") and associated processes are implemented on an electronic device 700, such as portable multifunction device 100, device 300, or device 500.

Fig. 7A illustrates an example user interface displayed at device 700 during a safe mode of operation, such as when the device determines that a user is operating a motor vehicle. Device 700 displays a lock screen with an operational security mode notification indication (at lock screen 702) and/or a banner (at lock screen 704) indicating that device 700 has started a lock session associated with an operational security mode. As shown in

lock screens

702, 704, and 706, the textual indication may include, for example only, "open do not disturb while driving. Notifications on the lock screen will be filtered "," currently in driving mode "," you are in driving mode ". In some examples, the operational security mode at lock screen 704 indicates that the banner is a sticky banner that holds the top of a list of scrollable notifications (e.g., notifications that meet the notification output criteria) populated below it.

In some examples, device 700 unlocks in response to the secure mode of operation of lock screen 704 notifying a touch input on the banner (e.g., a touch that forces the touch input to have a characteristic intensity that exceeds a first intensity threshold or to last for more than a predetermined amount of time). In some examples, in response to a touch input, device 700 ends the currently locked session and exits the secure mode of operation. Nonetheless, in some examples, in response to a touch input, device 700 ends the currently locked session and suspends operation in the secure mode. In some examples, the touch input provides a quick unlock gesture. In some examples, device 700 unlocks and remains in a safe-to-operate mode after receiving user confirmation that the user is not currently operating the vehicle (e.g., parking sideways).

In some examples, in response to a touch input on the operational security mode notification banner, the device displays a first affordance (not shown) that, when selected, causes the device to end the locked session and exit the operational security mode, and displays a second affordance (not shown) that, when selected, causes the device to end the locked session and suspend the operational security mode. For example, a first affordance corresponds to an "I'm not driving" option exiting the operational safety mode, and a second affordance corresponds to an "I'm parked side" option to pause the operational safety mode. In some examples, a swipe input on the security mode banner is operated to display the first affordance and the second affordance on the lock screen 704. In some cases, the suspended operational safety mode and/or the locked state automatically resumes when driving is detected, e.g., when the contextual parameters meet criteria to initiate the operational safety mode, as discussed herein.

As further shown in fig. 7A, in some examples, in response to detecting a user input to unlock device 700, device 700 displays a confirmation affordance without unlocking the device, and in response to a user confirmation, unlocks the device. In some examples, unlocking the device ends the locked session. For example, user input corresponding to a swipe up on lock screen 704 results in a confirmation action table being displayed, as shown at lock screen 706, which requires the user to confirm "i am not driving" to exit the operational safety mode. In some examples, device 700 is temporarily unlocked while remaining in a secure mode of operation. Nonetheless, in some examples, device 700 allows one unlock session per predetermined time period or period of operating the secure mode. In some examples, device 700 displays an alternative "i have parked sideways" affordance (not shown) to allow a user to access certain features, such as a map and navigation application, and automatically resume a safe mode of operation when driving is detected.

In some examples, in response to receiving user confirmation to unlock device 700, device displays lock screen 708, which displays unread notifications, including notifications that are received and not output during secure mode of operation (e.g., notifications that do not meet notification output criteria). For example, during the secure mode of operation, the lock screen 704 does not display the various notifications shown at the lock screen 708, which correspond to the normal lock screen when the secure mode of operation is not currently implemented.

Still referring to fig. 7A, in some examples, in response to receiving user confirmation to unlock device 700, the device displays home screen 710, which includes a plurality of application launch icons, which when selected, launch their underlying applications. In some examples, device 700 detects a user request for a notification center and displays the notification center (not shown), which includes a first list that precedes a second list, where the first list includes first notifications corresponding to notifications that do not satisfy the output criteria and that were not output during the secure mode of operation, and the second list includes one or more notifications (e.g., unread notifications) received prior to the locked session (prior to entering the secure mode of operation). For example, the device 700 provides a notification center that branches between notifications received before and during the last locked session and/or during the entire secure mode session of operation. In some examples, the first list includes notifications that suppress display.

Further, in some examples, when device 700 is unlocked, device 700 determines that the set of operating security mode initiation criteria are met and enters the operating security mode by re-locking the device into a second locked session. In some examples, the relock associates a first notification (not shown) in the first list with the second list. In some examples, during the second lock session, the device 700 receives a second notification (not shown) that does not meet the notification output criteria and stores the second notification in the notification center. In some examples, storing includes associating the second notification with the first list. In some examples, device 700 detects a subsequent user request to unlock and end the second lock session. Upon unlocking, device 700 detects a subsequent user request (e.g., a drop-down gesture or a swipe down of an upper portion of home screen 710) to display the notification center and to display a first list and a second list, wherein the first list includes the second notification and the second list includes the first notification. For example, the notification center displays the notification received during the last lock session. The relock device 700 starts from the notification list in the first list, for example by moving an item in the first list (e.g., if not yet read) to the second list.

With further reference to fig. 7A, when the device 700 is unlocked, the device 700 detects a request (e.g., manual activation) from a user to lock the device or a contextual parameter for initiating a secure mode of operation and resumes the secure mode of operation. In some examples, device 700 displays locked screen 704 with an operational security mode notification banner in response to a user request and/or detection of contextual parameters that meet operational security mode initiation criteria. In some examples, while still in the unlocked home screen 710, a restoration to the secure mode of operation (e.g., by manual activation of the control center) results in a secure mode of operation banner (e.g., the banner shown in fig. 7A lock screen 704) being displayed on the home screen 710. In some embodiments, device 700 determines whether the context parameter indicates that the electronic device is located within an operating motor vehicle using one or more of the techniques described in U.S. provisional patent application No.15/596,592.

Turning to fig. 7B-7D, in some examples during the secure mode of operation, device 700 displays a locked user interface 712 that includes one or

more affordances

714, 716, 718, 720, 722 corresponding to one or more enabled tasks (e.g., music, navigation, telephony, messaging, and voice control). In response to detecting a user selection of an affordance corresponding to an enabled task, device 700 displays a user interface corresponding to the enabled task. In some examples, the user's selection of the enabled task is a voice command detected at a microphone. In some examples, the user selection of the enabled task is with respect to a touch input of the affordance. As shown in locked user interface 712,

affordances

714, 716, 718, and 720 have a larger tap target area than the corresponding affordance on home screen 710 in FIG. 7A to facilitate easy navigation. In some examples, the user interface 712 specifically omits some of the application launch icons of the home screen 710 of fig. 7A that are deemed useless or unsafe to use during driving. In practice, limiting the options in the safe mode of operation allows for faster and easier selection of relevant features, thereby reducing interaction time with the device 700 and reducing the risk of driver distraction.

As shown in FIG. 7B, detecting selection of the instant messaging affordance 720 transitions the locked user interface 712 to an inbox user interface 724 that includes notifications received during a secure mode of operation that meet notification output criteria. In the current example, there are three unread notifications, which in some examples are further indicated as notification flags (not shown), which indicate the number of notifications received that meet the output criteria. In some examples, the inbox user interface 724 provides a unified inbox of messages from different types of applications that correspond to notifications from authorized contacts regardless of the application with which the notification is related to facilitate person-centric inbox. In some examples, the inbox user interface 724 allows for replying to contacts, as shown by reply screen 726. In some examples, one or more functions provided by

user interfaces

724 and 726 can be accessed through voice control. In some examples, as shown in fig. 7B, affordance target areas corresponding to tasks enabled at the

respective user interfaces

724, 726 are enlarged to facilitate easy selection and reduce the risk of driver distraction.

As shown in FIG. 7C, detecting selection of the music affordance 714 results in display of a music user interface 728 having various options (e.g., music, podcasts, radios, audiobooks). In some examples, selection of the music option results in display of a second music interface 730 that includes a fast play affordance to control music output and enter a music control interface 732. In some examples, one or more functions provided by the

music user interfaces

728, 730, 732 can be accessed through voice control. In some examples, as shown in fig. 7C, affordance target areas corresponding to tasks enabled at the

respective user interfaces

728, 730, 732 are enlarged to facilitate easy selection and reduce the risk of driver distraction.

As shown in fig. 7D, detecting selection of the navigation affordance 716 results in display of a navigation user interface 734 that includes one or more quick launch navigation affordances to request turn-by-turn navigation instructions (e.g., recent use, frequented places, location suggestions, favorites, home) for one or more predetermined destinations. Selection of the quick launch navigation affordance provides directional information, for example, as shown in

navigation screens

736, 738, and 740. In some examples, one or more functions provided by

navigation user interfaces

734, 736, 738, and 740 can be accessed through voice control. In some examples, as shown in fig. 7D, affordance target areas corresponding to tasks enabled at the

various user interfaces

734, 736, 738, and 740 are enlarged to facilitate easy selection and reduce the risk of driver distraction.

As shown in the lock user interface 712 at any of fig. 7B-7D, a selection of a voice control affordance is detected by a voice input or a touch input to initiate a voice control task that registers the voice input detected at the microphone for navigating one or more user interfaces during the secure mode of operation. In some examples, voice-controlled task locking requires the ability to unlock device 700 during a secure mode of operation. For example, voice control rejects voice commands that require full access to the home screen 710 in FIG. 7A, and responds with audible output (e.g., "sorry, i cannot help you when you drive")

In some examples, the voice control task enters a detailed mode of operation during the secure mode of operation, which is different from a normal mode of operation when the device is not in the secure mode of operation. During the detailed mode of operation, the voice control task provides more guidance and detail for navigating through various user interfaces and completing the task so that the user does not view the display screen often. For example, the detailed operating mode confirms when the message was sent and provides additional reminders when the message is not provided in the normal operating mode.

In some examples, in response to detecting a user selection of a voice control task, device 700 enables voice control with a user interface-specific context corresponding to the enabled task. For example, the voice control is associated with the user interface currently being displayed. In some examples, while displaying the user interface corresponding to the enabled task, the user interface is a first user interface and the voice control includes a first context specific to the first user interface. In response to detecting the user input to display the second user interface, device 700 transitions the display from the first user interface to the second user interface and updates the voice control with a second context specific to the second user interface, wherein the second user interface is different from the first user interface. The second context is different from the first context. In some examples, the first context and the second context are associated with an enabled task (e.g., switching between music-related

user interfaces

728, 730, 732) or unrelated (e.g., switching from any of music-related

user interfaces

728, 730, 732 to any of

navigation user interfaces

734, 736, 738, 740). In some examples, when the user interface changes, a swipe on the user interface changes the context of the voice control. In some examples, the content displayed on the screen defines a context of the voice command. In some examples, the context of the voice control includes reversible steps in the voice command stream, including reversible steps between different user interfaces of related enabled tasks or unrelated enabled tasks.

In some examples, when voice control is enabled, the device 700 determines an audio range for voice detection at the microphone and automatically modifies the acoustic model to adapt the voice detection to the determined audio range. By way of example only, the device 700 listens for voice commands when the device 700 is placed in a cup holder within an operating motor vehicle.

Fig. 8 is a flow diagram illustrating a method of using an operational security mode of an electronic device, according to some embodiments. The method 800 is performed at a device (e.g., 100, 300, 500) having a display. Some operations in method 800 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

As described below, the method 800 provides an intuitive way to implement a safe mode of operation, which may include filtering the output of notifications when certain contextual parameters are detected (e.g., contextual parameters indicating that the user of the device is driving). The method reduces the cognitive burden on the user to manage the output of notifications, thereby creating a more efficient human-machine interface. For battery-driven computing devices, enabling a user to manage notification output saves power faster and more efficiently and increases the interval between battery charges.

At block 802, the electronic device detects one or more context parameters. In some examples, the detected contextual parameters include one or more of a connection state of the device (e.g., whether the device is connected to another electronic device with certain capabilities or characteristics (e.g., second electronic device 608)), a motion of the device (e.g., GPS data or Wi-Fi antenna data indicating the motion), or a change in location of the device (e.g., GPS data indicating a change in location).

According to some embodiments, the contextual parameter includes a connection status indicating that the device is connected to a second electronic device (e.g., second electronic device 608) associated with the operating motor vehicle (e.g., operating motor vehicle 602), and the contextual parameter indicates that the electronic device is located within the operating motor vehicle (e.g., operating motor vehicle 602) (e.g., automobile, motorcycle, airplane, boat, bicycle). In some examples, the device connects to an application at a second electronic device (e.g., second electronic device 608) that can send and receive control signals with the device. In some examples, the device is wirelessly connected to the second electronic device (e.g., second electronic device 608) via bluetooth and/or Wi-Fi and/or is wired to the second electronic device (e.g., second electronic device 608) via a USB port and/or a lightning data line.

According to some embodiments, the contextual parameter includes a level of motion that exceeds a threshold level of motion, and the contextual parameter indicates that the electronic device is located within a running motor vehicle (e.g., running motor vehicle 602). In some examples, the motion level is a rate of change of location coordinates detected at the device, and the threshold motion level is a threshold rate of change of location coordinates. For example, the level of motion is based on GPS or other location sensor information. In some examples, the motion level is a rate of change of Wi-Fi networks detected at the device, and the threshold motion value is a threshold rate of change of Wi-Fi networks. For example, a device detects multiple Wi-Fi hotspots and/or multiple different Wi-Fi networks moving around within a predefined time period. In some examples, the detected context parameters and/or corresponding criteria of the operational safety mode initiation criteria account for hysteresis to detect whether the motion level rises again once the motion level falls below a threshold motion level (e.g., during stop-and-go traffic).

According to some embodiments, the context parameter includes a location state indicating a change in location detected at the device, and the context parameter indicates that the electronic device is located within a running motor vehicle (e.g., running motor vehicle 602). For example, a GPS navigation application at the device is outputting turn-by-turn navigation instructions for driving to a destination.

According to some embodiments, in response to detecting the one or more contextual parameters, the electronic device determines whether the detected one or more contextual parameters satisfy operational safety mode initiation criteria. In some examples, the device updates the third party application with the driving status in accordance with a determination that the operational safety mode initiation criteria are met. In some examples, in accordance with a determination that the operational security mode initiation criteria are met, the device instructs a paired device (e.g., 100, 300, 500, and/or a smart watch) to mirror the operational security mode. In some embodiments, an electronic device (e.g., device 600) determines whether a context parameter indicates that the electronic device is located within an operating motor vehicle using one or more of the techniques described in U.S. provisional patent application No.15/596,592.

According to some embodiments, when the electronic device is in the secure mode of operation, the device automatically exits the secure mode of operation in accordance with a determination that the secure mode of operation initiation criteria are no longer met. In some examples, a device receives a manual exit request. For example, the device receives a user request to unlock the device during the secure mode of operation, and in response to the user request, provides an option to exit (e.g., fig. 7A) the secure mode of operation or suspend the secure mode of operation, and unlock accordingly. In some embodiments, an electronic device (e.g., device 600) determines whether a context parameter indicates that the electronic device is no longer located within an operating motor vehicle using one or more of the techniques described in U.S. provisional patent application No.15/596,592.

According to some embodiments, when the electronic device is in a second mode that is not the secure mode of operation, the device receives a second notification, and in response to receiving the second notification, regardless of whether the second notification satisfies the set of notification output criteria, the device causes an output corresponding to the second notification. For example, the device operates in a default and/or normal mode, wherein a notification is output.

At block 804, operational safety mode initiation criteria are met in accordance with one or more contextual parameters, the motor vehicle initiating an operational safety mode, the safety mode initiation criteria including criteria met when the contextual parameters indicate that the electronic device is located within a running motor vehicle (e.g., operating motor vehicle 602). Activating the operational safety mode in dependence on the context parameter satisfying the operational safety mode activation criterion allows the user to quickly adopt the operational safety mode at the device and enables the user to concentrate on running the motor vehicle, thereby facilitating safe use of the device. Performing an operation when a set of conditions has been met without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user provide suitable input and reducing user error in operating/interacting with the device), and in addition, by enabling the user to use the device more quickly and efficiently, which can also reduce power usage and extend the battery life of the device.

At block 806, the electronic device receives a notification when the device is in a secure mode of operation. For example, the device receives notifications and/or communications from external devices (e.g.,

external devices

699, 689, 679). In some examples, the device receives internally generated notifications and/or alerts, such as calendar reminder notifications and/or system alerts.

According to some embodiments, at block 808, in response to receiving the notification, the electronic device determines whether the notification satisfies the set of notification output criteria.

According to some embodiments, the set of notification output criteria includes criteria that are met when the notification is from an authorized source. For example, the authorization source is a whitelisted contact, an emergency contact, a favorite contact, an application with export permissions, and/or a prioritized application, such as a navigation application or a user-selected prioritized application.

According to some embodiments, at block 810, the set of notification output criteria includes criteria that are met when the notification corresponds to a communication from a most recently communicated contact. For example, the recency of the contact is based on whether a phone, text, or any other active communication with the contact occurred within a past predetermined time window (e.g., a past 24 hours) since the arrival of the communication, and/or since the device's last initiation of the secure mode of operation. In some examples, allowing the notification from the nearest contact to be output while in the secure mode of operation allows the user to maintain the messaging while en route to the nearest contact.

According to some embodiments, at block 812, the set of notification output criteria includes criteria that are met when the notification corresponds to a communication from a contact authorized to receive location information from the device. For example, location sharing with the contact and/or an external device associated with the contact is currently open and/or granted permission. Allowing the output of notifications from contacts having location-sharing access rights while in the secure mode of operation further facilitates secure use of the device while operating the vehicle by allowing the source of incoming communications to determine whether to send the communication at a later time when the user is not operating the vehicle (e.g., if the source of the message has determined the location of the device) or whether the communication is important and relevant to the user at that time, allowing the user to remain informed while still in the secure mode of operation.

According to some embodiments, the set of notification output criteria includes criteria that are met when the notification corresponds to a communication from a repeated communication of a single contact. For example, the communication is an incoming call, which is a repeat call from a single contact.

According to some embodiments, the set of notification output criteria includes a criterion that is met when the notification corresponds to an incoming call and the device is connected to a second electronic device (e.g., second electronic device 608) associated with operating the motor vehicle (e.g., operating motor vehicle 602). In some examples, when the detected contextual parameter is a bluetooth integrated connection state of the pointing device with a running motor vehicle (e.g., running motor vehicle 602), the incoming call is not suppressed in the operational security mode. For example, the device allows a call (e.g., from any contact) to be answered with a button (e.g., a physical button) provided on a steering wheel on an operating motor vehicle (e.g., operating motor vehicle 602).

According to some embodiments, the set of notification output criteria includes a criterion that is met when the notification corresponds to a communication from a contact associated with a calendar event that coincides with a time window in which the device is in a secure mode of operation. For example, the communication is an incoming message from a contact that is included in the meeting invitation at or about the same time as the secure mode of operation is implemented on the device. In some examples, the criteria is further satisfied based on matching a location included in the meeting invitation with a direction of travel detected at the device. Allowing the notification from the contact included in the conference reclosing invitation to be output while in the secure mode of operation allows the user to maintain a messength while the user is en route to a meeting with the contact in some examples.

According to some embodiments, the set of notification output criteria includes criteria that are met when the notification corresponds to a system alert. For example, the system alarm is a CMOS alarm.

According to some embodiments, the set of notification output criteria includes criteria that are met when the notification corresponds to an emergency alert. For example, the emergency alert is a government alert and/or a weather alert.

At block 814, when the electronic device is in the secure mode of operation, in accordance with a determination that the notification satisfies the set of notification output criteria, the device causes output corresponding to the notification. For example, the device emits a visual output (e.g., causing a notification (e.g., second electronic device 608) to be displayed on a display screen and/or on another display screen associated with the second electronic device) and/or an audible output).

At block 816, when the electronic device is in the secure mode of operation, in accordance with a determination that the notification does not satisfy the set of notification output criteria, the device stops output corresponding to the notification. For example, the device suppresses the notification by preventing the notification from being displayed at the device (such as from appearing on a lock screen mode) and/or preventing an audible or tactile output from being emitted.

In accordance with some embodiments, in accordance with a determination that the notification does not satisfy the set of notification output criteria, the electronic device stores the notification. For example, unread notifications including notifications that do not meet the notification output criteria are stored for later retrieval in the unlocked state.

It should be noted that the details of the process described above with respect to method 800 (e.g., fig. 8) also apply in a similar manner to the methods described below. For example, method 900 optionally includes one or more features of the various methods described above with reference to method 800. For example, method 900 may also include detecting one or more contextual parameters (e.g., block 802, fig. 8) and/or initiating a safe mode of operation (e.g., block 804, fig. 8) based on the one or more contextual parameters satisfying the safe mode of operation initiation criteria, the safe mode of operation initiation criteria including criteria that are satisfied when the contextual parameters indicate that the electronic device is located within the operating motor vehicle. For the sake of brevity, these details are not repeated in the following.

Fig. 9 is a flow diagram illustrating a method of using an operational security mode of an electronic device, in accordance with some embodiments. The method 900 is performed at a device (e.g., 100, 300, 500) having a display. Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

As described below, the method 900 provides an intuitive way to implement a secure mode of operation that may include notifications of suppressed communications unless they include an output request to send a person flag (e.g., an explicit request when the device is in a secure mode of operation that suppresses notifications). The method reduces the cognitive burden on the user to manage the output of notifications. For battery-driven computing devices, enabling a user to manage the output of notifications faster and more efficiently conserves power and increases the interval between battery charges.

At block 902, while in a secure mode of operation, the electronic device receives a communication from a contact. For example, the communication is via a text message, a phone call, an email, or other communication from the contact's third party application.

According to some embodiments, while in the secure mode of operation, in response to receiving an indication of an incoming communication from a source and prior to receiving the incoming communication at the device, the electronic device sends a status to the source (e.g., to the source electronic device, which may be any of the

devices

100, 300, 500 and/or the

external devices

699, 689, 679) indicating that the device is in the secure mode of operation. By way of example only, the device sends a status to the source, such as a presence indicator, indicating that the device is in a safe mode of operation, that a user of the device is currently driving, and/or the location of the device. For example, the device receives the user's iMessage at the user's device (e.g., via a short message such as SMS and MMS, via a service such as that provided by Apple, Inc. (Cupertino, Calif.))

Text message) and sends status information (e.g., a steering wheel icon and/or text, such as "the user is driving") to the source device (e.g.,

external devices

699, 689, 679) that causes the status to be displayed. In some examples, the device only sends the state to any source of the indication of the incoming communication and/or to allowed sources (e.g., auto-reply sources). Sending the status to the source (e.g.,

external devices

699, 689, 679) prior to receiving the incoming communication also facilitates safe use of the device while operating by allowing the source of the incoming communication to determine whether to send the communication at a later time when the user is not operating the vehicle.

According to some embodiments, at block 904, in response to receiving a communication from a contact, the electronic device determines whether the communication satisfies notification output criteria.

According to some embodiments, when the electronic device is in a second mode that is not the secure mode of operation, the device receives a second communication, and in response to receiving the second communication, the device causes an output corresponding to the second communication regardless of whether the second communication satisfies the set of notification output criteria.

According to some embodiments, the notification output criteria include a criterion that is met when the contact is the most recent contact to communicate within a predetermined time window in the past. For example, the recency of a contact is based on telephone or text communications that have occurred within the past 24 hours. In some examples, after the recency of the contact expires, the device receives another communication from the contact while the device is in the secure mode of operation, and forgoes outputting the notification regardless of whether the notification output request is included.

According to some embodiments, the notification output criteria include a criterion that is met when the contact is an authorized contact for selecting a notification output request for a communication. In some examples, if the contact receives an automatic reply to a previous message, the contact is authorized to include a notification output request. In some examples, if the contact is a user-specified contact (e.g., a white list contact, no contacts, favorites, recent, and/or all contacts), the contact is authorized to include the notification output request.

According to some embodiments, at block 906, the notification output criteria include criteria that are met when the contact is an authorized contact for receiving an automatic reply from the device in response to a previous communication from the contact.

According to some embodiments, the authorized contact is the most recent contact that communicated within a predetermined time window in the past.

According to some embodiments, the authorized contacts are user-specified authorized contacts (e.g., white list contacts, no contacts, favorites, recent, and/or all contacts).

According to some embodiments, an authorized contact is a contact that is authorized to receive current location information corresponding to a device. For example, the contact has location sharing access to the device.

According to some embodiments, the authorized contacts are contacts associated with calendar events that coincide with a time window in which the device is in a secure mode of operation. For example, the communication is an incoming message from a contact that is included in the meeting invitation at or about the same time as the secure mode of operation is implemented on the device. In some examples, the criteria is further satisfied based on matching a location included in the meeting invitation with a direction of travel detected at the device.

At block 908, while in the secure mode of operation, in accordance with a determination that the communication satisfies notification output criteria, including criteria that are satisfied when the communication includes a notification output request (e.g., an explicit request selected on the sending device requesting that the notification should be output), the electronic device outputs a notification corresponding to the communication. For example, the device displays a notification and/or emits an audible or tactile output.

At block 910, while in the secure mode of operation, in accordance with a determination that the communication does not satisfy the notification output criteria, the electronic device foregoes outputting the notification.

According to some embodiments, at block 912, in accordance with a determination that the communication is a first communication from the contact and the contact is an authorized contact for receiving an automatic reply from the device, the electronic device sends the automatic reply to an external device associated with the contact when the notification output criteria is not satisfied (e.g., the notification is discarded from being output). In some examples, the communication is a text message and the automated reply is a text message. Sending an auto-reply allows the user on the device to avoid the occurrence of a non-response, and in some cases further facilitates safe use of the device by notifying contacts that are not available at the time (e.g., when the auto-reply indicates that the user is currently driving), allowing the contacts to determine whether to continue to attempt to reach the user now or later.

According to some embodiments, the auto-reply includes a current location (e.g., a location waypoint) detected at the device in response to receiving the communication. In some examples, the auto-reply is customizable by the user for a particular category of contacts, all contacts allowed to receive the auto-reply, and/or a particular contact. In some examples, the auto-reply is a single reply for all allowed contacts.

According to some embodiments, the auto-reply includes text indicating that the device is in a secure mode of operation. For example, the text indicates that the user is currently driving and/or that the notification is suppressed at that time. In some examples, the text indicates other means for reaching the user when necessary (e.g., call arrival user when bluetooth integration is detected that allows outgoing incoming calls).

According to some embodiments, at block 914, the electronic device receives a second communication from the contact while in the secure mode of operation and when the auto-reply is subsequently sent. In accordance with a determination that the second communication includes the second notification output request, the device outputs a second notification corresponding to the second communication, and in accordance with a determination that the second communication does not include the second notification output request, the device abandons outputting the second notification. In some examples, the second communication is the first communication with the second notification output request. For example, the contact need not re-type the previous message for which output was not obtained, but rather mark the previous message for output.

According to some embodiments, when in the operation security mode and then transmitting the auto reply, the electronic device receives a third communication excluding the notification output request from the contact person, and outputs a third notification corresponding to the third communication. For example, in some examples, the notification output request marks an entire session with a contact that was output during the current operational security mode.

It is noted that the details of the process described above with respect to method 900 (e.g., fig. 9) also apply in a similar manner to the methods described above and below. For example, method 1000 optionally includes one or more features of the various methods described above with reference to method 800. For example, method 1000 may include, while in a secure mode of operation, receiving a communication from a contact (e.g., block 902, fig. 9) and, in accordance with a determination that the communication satisfies notification output criteria, outputting a notification corresponding to the communication (e.g., block 908, fig. 9), the notification output criteria including criteria that are satisfied when the communication includes a notification output request. For the sake of brevity, these details are not repeated in the following.

Fig. 10 is a flow diagram illustrating a method of using an operational security mode of an electronic device, in accordance with some embodiments. The method 1000 is performed at a device (e.g., 100, 300, 500) having a display. Some operations in method 1000 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

As described below, the method 1000 provides an intuitive way for implementing and/or otherwise initiating a secure mode of operation. The method reduces the cognitive burden on the user to manage the output of notifications, thereby creating a more efficient human-machine interface. For battery-driven computing devices, a user is enabled to manage notification output saving power and increasing the interval between battery charges faster and more efficiently.

At block 1002, the electronic device detects a first set of one or more contextual parameters when a first set of operational security mode initiation criteria of the plurality of sets of operational security mode initiation criteria is valid, the first set of operational security mode initiation criteria including criteria that are met when movement (e.g., a rate of motion, a rate of acceleration) of the electronic device exceeds a threshold movement value. In some examples, the detected contextual parameters include one or more of a connection state of the device (e.g., whether the device is connected to another electronic device with certain capabilities (e.g., second electronic device 608)), motion of the device (e.g., GPS data or WiFi antenna data indicating motion), or a change in location of the device (e.g., GPS data indicating a change in location).

At block 1004, the electronic device initiates an operational safety mode in response to detecting the first set of one or more contextual parameters and in accordance with a determination that the first set of contextual parameters meets the first set of operational safety mode initiation criteria when a first set of operational safety mode initiation criteria of the plurality of sets of operational safety mode initiation criteria is valid, the first set of operational safety mode initiation criteria including a criterion that is met when a movement (e.g., a level of motion) (e.g., a rate of motion, a rate of acceleration) of the electronic device exceeds a threshold movement value (e.g., a threshold level of motion). In some examples, the determination regarding the first set of contextual parameters is made without regard to whether the second set of operational security mode initiation criteria are met. In some embodiments, device 600 determines whether the context parameter indicates that the electronic device is located within an operating motor vehicle (e.g., determines whether a first set of operating safety mode initiation criteria are met) using one or more techniques described in U.S. provisional patent application No.15/596,592.

According to some embodiments, the electronic device initiates the operational safety mode when the second set of operational safety mode initiation criteria is invalid, and in accordance with a determination that the first set of operational safety mode initiation criteria is satisfied (e.g., the connection criteria is invalid and the vehicle is detected to be moving). In accordance with a determination that the first set of operating safety mode initiation criteria are not met, the device foregoes initiating the operating safety mode (e.g., the connection criteria are invalid and the vehicle is detected not moving).

At block 1006, the device detects a second set of one or more contextual parameters when a second set of operating safety mode initiation criteria of the plurality of sets of operating safety mode initiation criteria is active, the second set of operating safety mode initiation criteria including when the electronic device is connected to and operating the motor vehicle (e.g., operating the motor vehicle)Vehicle 602) associated with a second electronic device (e.g., second electronic device 608). In some examples, the second electronic device (e.g., second electronic device 608) is a device that is typically present only in or specific to the motor vehicle (e.g., a receiver, a head unit, a car radio integrated on the motor vehicle, an in-vehicle technology and infotainment system, such as that provided by Apple, inc

) Such that detection or connection to a device of this type indicates that the device is located in a motor vehicle. In some examples, the second electronic device (e.g., second electronic device 608) includes a motor vehicle specific application or standard that allows the second electronic device (e.g., second electronic device 608) to send and/or receive control signals with the device via a wired or wireless connection such as bluetooth, Wi-Fi, and USB, and/or includes other features that facilitate linking the device (which may be a portable communication device such as a mobile phone) to a motor vehicle. In some examples, the detected contextual parameters include one or more of a connection state of the device (e.g., whether the device is connected to another electronic device with certain capabilities, motion of the device (e.g., GPS data indicating motion or WiFi antenna data), or a change in location of the device (e.g., GPS data indicating a change in location).

At block 1008, the device initiates the operational safety mode in response to detecting the second set of one or more contextual parameters and in accordance with a determination that the second set of contextual parameters meets the second set of operational safety mode initiation criteria when a second set of operational safety mode initiation criteria among the plurality of sets of operational safety mode initiation criteria is valid, the second set of operational safety mode initiation criteria including criteria that are met when the electronic device is connected to a second electronic device (e.g., second electronic device 608) associated with the motor vehicle. For example, the device initiates the secure mode of operation whether the first set of secure mode of operation initiation criteria is valid, invalid, satisfied, not satisfied, or any combination thereof. As described above, in some examples, the second electronic device (e.g., second electronic device 608) is a device that is typically present only in or specific to the motor vehicle (e.g., a receiver, head unit, or car radio integrated on the motor vehicle) such that detecting or connecting to this type of device indicates that the device is located in the motor vehicle.

According to some embodiments, in accordance with a determination that the second set of contextual parameters meets the second set of operational security mode initiation criteria, the electronic device initiates the operational security mode regardless of whether the first set of operational security mode initiation criteria are met (e.g., connected and moving) or not met (e.g., connected and not moving). In some examples, the device initiates the secure mode of operation without additionally considering whether the first set of secure mode of operation initiation criteria (e.g., movement criteria) is valid or invalid.

According to some embodiments, the device receives a first notification when the electronic device is in a secure mode of operation. For example, the device receives notifications and/or communications from external devices (e.g.,

external devices

699, 689, 679). In some examples, the device receives internally generated notifications and/or alerts, such as calendar reminder notifications and/or system alerts. In accordance with a determination that the first notification satisfies a set of notification output criteria, the device causes output corresponding to the first notification. For example, the device emits a visual output (e.g., causing a notification to be displayed on a display screen and/or on another display screen associated with a second electronic device (e.g., second electronic device 608)), a tactile output, and/or an audible output. In accordance with a determination that the first notification does not satisfy the set of notification output criteria, the device forgoes causing output corresponding to the first notification. For example, the device suppresses the notification by preventing the notification from being displayed at the device and/or the second electronic device (such as from appearing on a locked screen mode) and/or preventing an audible or tactile output from being emitted.

At block 1010, when a second set of operational safety mode enablement criteria of the plurality of sets of operational safety mode enablement criteria is valid, in response to detecting the second set of one or more context parameters and in accordance with a determination that the second set of context parameters does not satisfy the second set of operational safety mode enablement criteria, the device abandons enablement of the operational safety mode when the first set of operational safety mode enablement criteria is satisfied, the second set of operational safety mode enablement criteria including criteria that are satisfied when the electronic device is connected to a second electronic device (e.g., second electronic device 608) associated with the motor vehicle. For example, the connection state of the device overrides the mobility level of the device as to whether the secure mode of operation is enabled. As described above, in some examples, the second electronic device (e.g., second electronic device 608) is a device that is typically present only in or specific to the motor vehicle (e.g., a receiver, head unit, or car radio integrated on the motor vehicle) such that detecting or connecting to this type of device indicates that the device is located in the motor vehicle.

In accordance with some embodiments, in accordance with a determination that the second set of contextual parameters does not satisfy the second set of operational security mode initiation criteria, the electronic device initiates the operational security mode regardless of whether the first set of operational security mode initiation criteria is satisfied. For example, whether the device is detected as moving or not, the device may forego initiating a secure mode of operation when the device is not connected. In some examples, the device foregoes initiating the secure mode of operation without additionally considering whether the first set of secure mode of operation initiation criteria (e.g., movement criteria) is valid or invalid.

According to some embodiments, in response to detecting the second set of one or more context parameters, in accordance with a determination that the second set of context parameters do not satisfy the second set of operational safety mode initiation criteria, the electronic device aborts initiating the operational safety mode when the first set of operational safety mode initiation criteria are not satisfied. For example, the second set of context parameters indicates that the device is not connected, and the first set of context parameters indicates that the device is not moving.

According to some embodiments, the electronic device initiates the secure mode of operation in response to receiving a manual activation to initiate the secure mode of operation when both the first set of operational security mode initiation criteria and the second set of operational security mode initiation criteria are invalid, and the device aborts initiating the secure mode of operation in response to a lack of manual activation. For example, manual activation is the opening of a safe mode of operation by a setting on the control center or device.

According to some embodiments, when the electronic device is in a second mode that is not the secure mode of operation, the device receives a second notification, and in response to receiving the second notification, regardless of whether the second notification satisfies the set of notification output criteria, the device causes an output corresponding to the second notification. For example, the device operates in a default and/or normal mode in which notifications are output.

According to some embodiments, the device disables the first set of operational safety mode initiation criteria and the second set of operational safety mode initiation criteria when enabling the manual setting for manually activating the operational safety mode. For example, the device deactivates the operational safety mode based on user settings for manual activation through a control panel or control center. In some examples, manual activation disables any set triggers for entering the secure mode of operation.

According to some embodiments, the first set of operational safety mode initiation criteria is validated based on a first user selection and the second set of operational safety mode initiation criteria is validated based on a second user selection when manual setting of the operational safety mode is not enabled. For example, the user selects a trigger type to cause a safe mode of operation, such as connecting an activation trigger with an automatic (motion level based/speed based) trigger. In some examples, the connection activation trigger detects whether the device is connected to an in-vehicle technology and infotainment system, such as that provided by Apple, Inc

According to some embodiments, upon both the first set of operating security mode initiation criteria and the second set of operating security mode initiation criteria being invalid, the electronic device receives user selection of the initial set of operating security mode initiation criteria as invalid after initiating the second instance of the operating security mode in response to detecting the initial set of operating security mode initiation criteria in the plurality of sets of operating security mode initiation criteria. For example, the device receives user settings for deactivating two criteria. In some examples, the device sets the two criteria to invalid after receiving a plurality of selections of deactivation in response to a plurality of previous sessions in the secure mode of operation, the number exceeding a threshold number.

According to some embodiments, upon activation of the first instance of the operational security mode in response to detection of satisfaction of an initial one of the plurality of sets of operational security mode activation criteria, the electronic device receives a user selection of the initial one of the sets of operational security mode activation criteria as valid when both the first set of operational security mode activation criteria and the second set of operational security mode activation criteria are invalid, wherein the initial one of the sets of operational security mode activation corresponds to at least one of the first set of operational security mode activation criteria and the second set of operational security mode activation criteria. For example, the device enters an on-board mode, wherein when no trigger has been set to active, the device presents an option to select a first detected trigger (detected context parameters that meet a first set of operational safety mode initiation criteria or a second set of operational safety mode criteria) as an active trigger. In some examples, the first instance of entering the secure mode of operation is the first time the device enters the secure mode of operation.

It is noted that details of the process described above with reference to method 1000 (e.g., fig. 10) also apply in a similar manner to the method described above. For example, method 800 optionally includes one or more features of the various methods described above with reference to method 800. For example, the method 800 may include detecting a second set of one or more contextual parameters when a second set of operational safety mode initiation criteria of the plurality of sets of operational safety mode initiation criteria is valid, the second set of operational safety mode initiation criteria including criteria that are met when the electronic device is connected to a second electronic device associated with the motor vehicle (e.g., block 1006, fig. 10), and/or in response to detecting the second set of one or more contextual parameters and in accordance with a determination that the second set of contextual parameters do not meet the second set of operational safety mode initiation criteria, forgoing initiating the operational safety mode when the first set of operational safety mode initiation criteria are met (e.g., block 1010, fig. 10). For the sake of brevity, these details are not repeated in the following.

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the technology and its practical applications. Those skilled in the art are thus well able to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.

Although the present disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. It is to be understood that such changes and modifications are to be considered as included within the scope of the disclosure and examples as defined by the following claims.

As described above, one aspect of the present technology is to collect and use data available from various sources to provide secure operations, such as initiating a secure mode of operation based on a detected context, and managing notifications and communications in the secure mode of operation to facilitate secure operations. The present disclosure contemplates that, in some instances, such collected data may include personal information data that uniquely identifies or may be used to contact or locate a particular person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, twitter IDs, home addresses, data or records relating to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personal information data in the present technology may be useful to benefit the user. For example, personal information data may be used to provide a secure mode of operation and to manage notifications and communications during secure operation. Thus, using such personal information data enables the user to calculate the operational security mode and control of notifications and communications during the operational security mode. In addition, the present disclosure also contemplates other uses for which personal information data is beneficial to a user. For example, health and fitness data may be used to provide insight into the overall health condition of a user, or may be used as positive feedback for individuals using technology to pursue health goals.

The present disclosure contemplates that entities responsible for collecting, analyzing, publishing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and/or privacy practices. In particular, such entities should enforce and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as data collection and/or usage changes. Personal information from the user should be collected for legitimate and legitimate uses by the entity and not shared or sold outside of these legitimate uses. Furthermore, such acquisition/sharing should be done after receiving the user's informed consent. Furthermore, such entities should consider taking any necessary steps to defend and secure access to such personal information data and to ensure that others who have access to the personal information data comply with their privacy policies and procedures. In addition, such entities may subject themselves to third party evaluations to prove compliance with widely accepted privacy policies and practices. In addition, policies and practices should be adjusted to the particular type of personal information data collected and/or accessed, and to applicable laws and standards including specific considerations of jurisdiction. 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 transfer and accountability act (HIPAA); while other countries may have health data subject to other regulations and policies and should be treated accordingly. Therefore, different privacy practices should be maintained for different personal data types in each country.

Regardless of the foregoing, the present disclosure also contemplates embodiments in which a user selectively prevents use or access to 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, in terms of operating a vehicle, the techniques of the present invention may be configured to allow a user to opt-in to "join" or "exit" to participate in the collection of personal information data during the registration service or at any time thereafter. In another example, the user may choose not to provide user data associated with operating the secure mode (e.g., GPS data, input data, etc.). In yet another example, the user may choose to limit the length of time that user data is maintained, or to completely prohibit development of a baseline operational security mode profile. In addition to providing "opt-in" and "opt-out" options, the present disclosure contemplates providing notifications related to accessing or using personal information. For example, the user may be notified that their personal information data is to be accessed when the application is downloaded, and then be reminded again just before the personal information data is accessed by the application.

Further, it is an object of the present disclosure that personal information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting data collection and deleting data. In addition, and when applicable, including in certain health-related applications, data de-identification may be used to protect the privacy of the user. De-identification may be facilitated by removing particular identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at a city level rather than at an address level), controlling how data is stored (e.g., aggregating data on a user), and/or other methods, as appropriate.

Thus, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, this disclosure also contemplates that various embodiments may be implemented without the need to access such personal information data. That is, various embodiments of the present technology do not fail to function properly due to the lack of all or a portion of such personal information data. For example, notifications may be managed by inferring preferences based on non-personal information data or an absolute minimum amount of personal information, such as content requested by a device associated with the user, other non-personal information available to the device, or publicly available information.

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 be implemented without the need to access such personal information data. That is, various embodiments of the present technology do not fail to function properly due to the lack of all or a portion of such personal information data. For example, content may be selected and delivered to a user by inferring preferences based on non-personal information data or an absolute minimum amount of personal information, such as content requested by a device associated with the user, other non-personal information available to a content delivery service, or publicly available information.

Claims

1. An electronic device, comprising:

one or more processors; and

memory storing one or more programs configured for execution by the one or more processors, the one or more programs including instructions for:

when in the safe mode of operation:

receiving a first communication from an external device associated with a contact;

in response to receiving the first communication from the contact, determining whether the first communication satisfies notification output criteria, the notification output criteria including criteria that are satisfied when the communication includes a notification output request;

in response to determining that the first communication satisfies a notification output criterion:

outputting a first notification corresponding to the first communication;

in response to determining that the first communication does not satisfy the notification output criteria:

sending an auto-reply to the external device associated with the contact, the auto-reply including instructions to provide a notification output request to allow the contact to select the notification output request for a first communication at the external device to request the electronic device to output a first notification,

responsive to the contact selecting the notification output request for a first communication at the external device, outputting a first notification, and

in response to the contact not selecting the notification output request for a first communication at the external device, forgoing outputting a first notification;

receiving, after receiving the first communication, a second communication from the contact that does not include the notification output request; and

outputting a second notification corresponding to the second communication according to the first notification being output based on the notification output request.

2. The electronic device of claim 1, the one or more programs further comprising instructions for:

when the device is in a second mode that is not the secure mode of operation:

receiving a communication; and

in response to receiving the communication, causing an output corresponding to the communication without regard to whether the communication satisfies the notification output criteria.

3. The electronic device of claim 1, further wherein:

the notification output criteria include a criterion that is met when the contact is the most recent contact that communicated most recently within a predetermined window of time in the past.

4. The electronic device of claim 1, the one or more programs further comprising instructions for:

while in a secure mode of operation, in response to receiving an indication of an incoming communication from a source and prior to receiving the incoming communication at the device, sending a status to the source indicating that the device is in the secure mode of operation.

5. The electronic device of claim 1, further wherein:

the notification output criteria include a criterion that is satisfied when the contact is an authorized contact for selecting the notification output request for the first communication from the contact.

6. The electronic device of claim 1, further wherein:

the notification output criteria include a criterion that is met when the contact is an authorized contact that receives an automatic reply from the device in response to a previous communication from the contact.

7. The electronic device of claim 5, further wherein:

the authorized contact is the most recent contact that communicated most recently within a predetermined window of time in the past.

8. The electronic device of claim 5, further wherein:

the authorized contact is an authorized contact designated by the user.

9. The electronic device of claim 5, further wherein:

the authorized contacts are contacts authorized to receive current location information corresponding to the device.

10. The electronic device of claim 5, further wherein:

the authorized contact is a contact associated with a calendar event that coincides with a time window in which the device is in the secure mode of operation.

11. The electronic device of claim 5, the one or more programs further comprising instructions for:

in accordance with a determination that the contact is an authorized contact to receive an automatic reply from the device:

sending an automatic reply to an external device associated with the contact when the notification output criteria is not satisfied.

12. The electronic device of claim 11, further wherein:

the automatic reply includes a current location detected at the device in response to receiving the first communication from the contact.

13. The electronic device of claim 11, further wherein:

the automatic reply includes text indicating that the device is in the secure mode of operation.

14. The electronic device of claim 11, the one or more programs further comprising instructions for:

while in the secure mode of operation and after sending the auto-reply, receiving a third communication from the contact;

in accordance with a determination that the third communication includes a second notification output request, outputting a third notification corresponding to the third communication; and

in accordance with a determination that the third communication does not include the second notification output request, forgoing output of the third notification.

15. The electronic device of claim 11, the one or more programs further comprising instructions for:

while in the secure mode of operation and after sending the auto-reply, receiving a fourth communication from the contact that does not include the notification output request; and

and outputting a fourth notification corresponding to the fourth communication.

16. A non-transitory computer-readable storage medium storing one or more programs configured for execution by one or more processors of an electronic device with a display, the one or more programs including instructions for:

when in the operational safety mode:

outputting a first notification corresponding to the first communication;

after outputting the first notification, receiving a second communication from the contact that does not include the notification output request; and

17. The non-transitory computer readable storage medium of claim 16, the one or more programs further comprising instructions for:

when the device is in a second mode that is not the secure mode of operation:

receiving a communication; and

18. The non-transitory computer-readable storage medium of claim 16, wherein the notification output criteria include a criterion that is met when the contact is a most recent contact that communicated most recently within a predetermined window of time in the past.

19. The non-transitory computer readable storage medium of claim 16, the one or more programs further comprising instructions for:

20. The non-transitory computer-readable storage medium of claim 16, wherein the notification output criteria include a criterion that is met when the contact is an authorized contact for selecting the notification output request for the first communication from the contact.

21. The non-transitory computer-readable storage medium of claim 16, wherein the notification output criteria include a criterion that is met when the contact is an authorized contact to receive an automatic reply from the device in response to a previous communication from the contact.

22. The non-transitory computer-readable storage medium of claim 20, wherein the authorized contact is a most recent contact that communicated most recently within a predetermined window of time in the past.

23. The non-transitory computer-readable storage medium of claim 20, wherein the authorized contact is a user-specified authorized contact.

24. The non-transitory computer-readable storage medium of claim 20, wherein the authorized contact is a contact authorized to receive current location information corresponding to the device.

25. The non-transitory computer-readable storage medium of claim 20, wherein the authorized contact is a contact associated with a calendar event that coincides with a time window in which the device is in the secure mode of operation.

26. The non-transitory computer readable storage medium of claim 20, the one or more programs further comprising instructions for:

27. The non-transitory computer-readable storage medium of claim 26, wherein the automatic reply comprises a current location detected at the device in response to receiving the first communication from the contact.

28. The non-transitory computer-readable storage medium of claim 26, wherein the automatic reply comprises text indicating that the device is in the secure mode of operation.

29. The non-transitory computer readable storage medium of claim 26, the one or more programs further comprising instructions for:

in accordance with a determination that the third communication does not include the second notification output request, forgoing outputting the third notification.

30. The non-transitory computer readable storage medium of claim 26, the one or more programs further comprising instructions for:

and outputting a fourth notification corresponding to the fourth communication.

31. A method performed by an electronic device, comprising:

when in the operational safety mode:

outputting a first notification corresponding to the first communication,

32. The method of claim 31, further comprising:

when the device is in a second mode that is not the secure mode of operation:

receiving a communication; and

33. The method of claim 31, wherein the notification output criteria include a criterion that is met when the contact is the most recent contact that communicated most recently within a predetermined window of time in the past.

34. The method of claim 31, further comprising:

while in a secure mode of operation, in response to receiving an indication of an incoming communication from a source and prior to receiving the incoming communication at the device, sending a state to the source indicating that the device is in the secure mode of operation.

35. The method of claim 31, wherein the notification output criteria include a criterion that is met when the contact is an authorized contact for selecting the notification output request for the first communication from the contact.

36. The method of claim 31, wherein the notification output criteria include a criterion that is met when the contact is an authorized contact for receiving an automatic reply from the device in response to a previous communication from the contact.

37. The method of claim 35, wherein the authorized contact is a most recent contact that communicated most recently within a predetermined window of time in the past.

38. The method of claim 35, wherein the authorized contact is a user-specified authorized contact.

39. The method of claim 35, wherein the authorized contact is a contact authorized to receive current location information corresponding to the device.

40. The method of claim 35, wherein the authorized contact is a contact associated with a calendar event that coincides with a time window in which the device is in the secure mode of operation.

41. The method of claim 35, further comprising:

sending an automatic reply to the external device associated with the contact when the notification output criteria is not satisfied.

42. The method of claim 41, wherein the auto-reply comprises a current location detected at the device in response to receiving the first communication from the contact.

43. The method of claim 41, wherein the auto-reply comprises text indicating that the device is in the secure mode of operation.

44. The method of claim 41, further comprising:

45. The method of claim 41, further comprising:

and outputting a fourth notification corresponding to the fourth communication.