[go: up one dir, main page]

WO2020247049A1 - Interfaces utilisateur servant à surveiller des niveaux d'exposition au bruit - Google Patents

Interfaces utilisateur servant à surveiller des niveaux d'exposition au bruit Download PDF

Info

Publication number
WO2020247049A1
WO2020247049A1 PCT/US2020/025768 US2020025768W WO2020247049A1 WO 2020247049 A1 WO2020247049 A1 WO 2020247049A1 US 2020025768 W US2020025768 W US 2020025768W WO 2020247049 A1 WO2020247049 A1 WO 2020247049A1
Authority
WO
WIPO (PCT)
Prior art keywords
noise level
level data
data
noise
displaying
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2020/025768
Other languages
English (en)
Inventor
Nicholas Felton
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from DKPA201970534A external-priority patent/DK201970534A1/en
Application filed by Apple Inc filed Critical Apple Inc
Publication of WO2020247049A1 publication Critical patent/WO2020247049A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B21/00—Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
    • G08B21/02—Alarms for ensuring the safety of persons
    • G08B21/12—Alarms for ensuring the safety of persons responsive to undesired emission of substances, e.g. pollution alarms
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/16—Constructional details or arrangements
    • G06F1/1613—Constructional details or arrangements for portable computers
    • G06F1/163—Wearable computers, e.g. on a belt
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
    • H04R1/00—Details of transducers, loudspeakers or microphones
    • H04R1/10—Earpieces; Attachments therefor ; Earphones; Monophonic headphones
    • H04R1/1083—Reduction of ambient noise
    • G—PHYSICS
    • G10—MUSICAL INSTRUMENTS; ACOUSTICS
    • G10L—SPEECH ANALYSIS TECHNIQUES OR SPEECH SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING TECHNIQUES; SPEECH OR AUDIO CODING OR DECODING
    • G10L25/00—Speech or voice analysis techniques not restricted to a single one of groups G10L15/00 - G10L21/00
    • G10L25/03—Speech or voice analysis techniques not restricted to a single one of groups G10L15/00 - G10L21/00 characterised by the type of extracted parameters
    • G10L25/21—Speech or voice analysis techniques not restricted to a single one of groups G10L15/00 - G10L21/00 characterised by the type of extracted parameters the extracted parameters being power information

Definitions

  • the active portion in response to receiving the second noise level data: displaying the active portion in a second size based on the second noise level that that is different from the first size; in accordance with a determination that the second noise level exceeds the threshold noise level, displaying the active portion in a second color different from the first color; and in accordance with a determination that the second noise level does not exceed the threshold noise level, maintaining display of the graphical object in the first color.
  • an electronic device comprises a display device; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, via the display device, a first user interface including a graphical object that varies in appearance based on a noise level;
  • a method performed at an electronic device including a display device and a touch sensitive surface comprises: receiving: first noise level data attributable to a first device type; and second noise level data attributable to a second device type different from the first device type; displaying, via the display device, a first user interface, the first user interface including: a first representation of received noise level data that is based on the first noise level data and the second noise level data; and a first device type data filtering affordance; while displaying the first user interface, detecting a first user input corresponding to selection of the first device type data filtering affordance; and in response detecting the first user input, displaying a second representation of received noise level data that is based on the second noise level data and that is not based on the first noise level data.
  • 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.
  • FIG. 2 illustrates a portable multifunction device having 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.
  • FIGS. 5C-5D illustrate exemplary components of a personal electronic device having a touch-sensitive display and intensity sensors in accordance with some embodiments.
  • FIGS. 5E-5H illustrate exemplary components and user interfaces of a personal electronic device in accordance with some embodiments.
  • FIGS. 9A-9G illustrate user interfaces for monitoring audio exposure levels in accordance with some embodiments.
  • FIG. 11 A-l 1L illustrates user interfaces in accordance with some embodiments. DESCRIPTION OF EMBODIMENTS
  • FIGS. 1 A-1B, 2, 3, 4A-4B, 5A-5H, 6A-6AL, 8A-8L, 9A-9G, and 11 A- 11L provide a description of exemplary devices for performing the techniques for monitoring noise exposure levels.
  • FIGS. 6A-6L illustrate exemplary user interfaces for monitoring noise exposure levels.
  • FIGS. 7A-7B are a flow diagram illustrating a method for monitoring noise exposure levels using an electronic device, in accordance with some embodiments. The user interfaces in FIGS. 6A-6L are used to illustrate the processes described below, including the processes in FIGS. 7.
  • FIGS. 8A-8L illustrate exemplary user interfaces for accessing and displaying environmental noise exposure data.
  • FIGS. 9A-9G illustrate exemplary user interfaces for monitoring noise exposure levels.
  • the term“if’ is, optionally, construed to mean“when” or“upon” or“in response to determining” or“in response to detecting,” depending on the context.
  • the phrase“if it is determined” or“if [a stated condition or event] is detected” is, optionally, construed to mean“upon determining” or“in response to determining” or“upon detecting [the stated condition or event]” or“in response to detecting [the stated condition or event],” depending on the context.
  • the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions.
  • portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California.
  • Other portable electronic devices such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used.
  • FIG. 1 A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments.
  • Touch- sensitive display 112 is sometimes called a“touch screen” for convenience and is sometimes known as or called a“touch-sensitive display system.”
  • Device 100 includes memory 102 (which optionally includes one or more computer-readable storage mediums), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external port 124.
  • Device 100 optionally includes one or more optical sensors 164.
  • Device 100 optionally includes one or more contact intensity sensors 165 for detecting 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 touchpad 355 of device 300).
  • These components optionally communicate over one or more communication buses or signal lines 103.
  • the term“intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface.
  • the intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors.
  • the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure).
  • the intensity threshold is a pressure threshold measured in units of pressure.
  • the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device.
  • a touch-sensitive surface e.g., a touch-sensitive display or trackpad
  • a“down click” or“up click” of a physical actuator button is, optionally, interpreted by the user as a“down click” or“up click” of a physical actuator button.
  • a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an“up click,” a“down click,”“roughness”)
  • the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
  • Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices.
  • Memory controller 122 optionally controls access to memory 102 by other components of device 100.
  • RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication.
  • the RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio.
  • NFC near field communication
  • Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi.
  • the user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth.
  • the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus- based input due to the larger area of contact of a finger on the touch screen.
  • the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
  • 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.
  • a touch-sensitive surface e.g., touch-sensitive display system 112
  • 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.
  • Device 100 optionally also includes one or more proximity sensors 166.
  • FIG. 1 A shows proximity sensor 166 coupled to peripherals interface 118.
  • proximity sensor 166 is, optionally, coupled to input controller 160 in I/O subsystem 106.
  • Proximity sensor 166 optionally performs as described in U.S. Patent Application Nos. 11/241,839, “Proximity Detector In Handheld Device”; 11/240,788,“Proximity Detector In Handheld Device”; 11/620,702,“Using Ambient Light Sensor To Augment Proximity Sensor Output”;
  • Device 100 optionally also includes one or more accelerometers 168.
  • FIG. 1 A shows accelerometer 168 coupled to peripherals interface 118.
  • accelerometer 168 is, optionally, coupled to an input controller 160 in I/O subsystem 106.
  • Accelerometer 168 optionally performs as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S.
  • Operating system 126 e g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,
  • Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124.
  • External port 124 e.g., Universal Serial Bus (USB), FIREWIRE, etc.
  • USB Universal Serial Bus
  • FIREWIRE FireWire
  • the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
  • Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel).
  • Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact).
  • Contact/motion module 130 receives contact data from the touch-sensitive surface.
  • contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has“clicked” on an icon).
  • at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100).
  • a mouse“click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware.
  • Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
  • GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location- based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
  • applications e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location- based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
  • Contacts module 137 (sometimes called an address book or contact list);
  • Video conference module 139 • Video conference module 139;
  • Workout support module 142 • Camera module 143 for still and/or video images;
  • Calendar module 148 • Calendar module 148;
  • Widget modules 149 which optionally include one or more of: weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;
  • Video and music player module 152 which merges video player module and music player module
  • Map module 154 • Map module 154;
  • Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
  • contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name;
  • an address book or contact list e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370
  • video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
  • e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions.
  • e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
  • online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264.
  • instant messaging module 141 rather than e-mail client module 140, is used to send a link to a particular online video.
  • the predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces.
  • the touchpad when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100.
  • a “menu button” is implemented using a touchpad.
  • the menu button is a physical push button or other physical input control device instead of a touchpad.
  • Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information.
  • Event sorter 170 includes event monitor 171 and event dispatcher module 174.
  • application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing.
  • device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
  • Event monitor 171 receives event information from peripherals interface 118.
  • Event information includes information about a sub-event (e.g., a user touch on touch- sensitive display 112, as part of a multi-touch gesture).
  • Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110).
  • Information that peripherals interface 118 receives from EO subsystem 106 includes information from touch- sensitive display 112 or a touch-sensitive surface.
  • FIG. 1 Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur.
  • the application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
  • Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
  • application 136-1 includes event sorter 170.
  • event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
  • a respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information.
  • Event recognizer 180 includes event receiver 182 and event comparator 184. In some
  • event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).
  • the double tap for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase.
  • the definition for event 2 (187-2) is a dragging on a displayed object.
  • the dragging for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch- sensitive display 112, and liftoff of the touch (touch end).
  • the event also includes information for one or more associated event handlers 190.
  • data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module.
  • Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204.
  • menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100.
  • the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
  • device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124.
  • Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process.
  • device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113.
  • Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
  • FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.
  • Device 300 need not be portable.
  • device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child’s learning toy), a gaming system, or a control device (e.g., a home or industrial controller).
  • Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components.
  • CPUs processing units
  • 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 remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1 A), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100.
  • memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1 A) optionally does not store these modules.
  • Each of the above-identified elements in FIG. 3 is, optionally, stored in one or more of the previously mentioned memory devices.
  • Each of the above-identified modules corresponds to a set of instructions for performing a function described above.
  • the above- identified modules or programs (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.
  • memory 370 optionally stores a subset of the modules and data structures identified above.
  • memory 370 optionally stores additional modules and data structures not described above.
  • FIG. 4A illustrates an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device 300.
  • user interface 400 includes the following elements, or a subset or superset thereof:
  • Icon 420 for browser module 147 labeled“Browser;” and o Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled“iPod;” and
  • Icon 426 for calendar module 148 labeled“Calendar;”
  • Icon 428 for image management module 144 labeled“Photos;”
  • Icon 442 for workout support module 142 labeled“Workout Support”
  • Icon 444 for notes module 153 labeled“Notes;”
  • icon labels illustrated in FIG. 4A are merely exemplary.
  • icon 422 for video and music player module 152 is labeled“Music” or“Music Player.”
  • Other labels are, optionally, used for various application icons.
  • the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B.
  • the touch-sensitive surface e.g., 451 in FIG. 4B
  • the touch-sensitive surface has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450).
  • the device detects contacts (e.g., 460 and 462 in FIG.
  • a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact).
  • a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact).
  • multiple user inputs it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
  • FIG. 5A illustrates exemplary personal electronic device 500.
  • Device 500 includes body 502.
  • device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1 A-4B).
  • device 500 has touch-sensitive display screen 504, hereafter touch screen 504.
  • touch screen 504 optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied.
  • the one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data that represents the intensity of touches.
  • the user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device 500.
  • PCT/US2013/040061 titled“Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled“Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed November 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.
  • device 500 has one or more input mechanisms 506 and 508.
  • Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms.
  • device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.
  • FIG. 5B depicts exemplary personal electronic device 500.
  • device 500 can include some or all of the components described with respect to FIGS. 1 A,
  • Device 500 has bus 512 that operatively couples EO section 514 with one or more computer processors 516 and memory 518.
  • EO section 514 can be connected to display 504, which can have touch-sensitive component 522 and, optionally, intensity sensor 524 (e.g., contact intensity sensor).
  • intensity sensor 524 e.g., contact intensity sensor
  • EO section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques.
  • Device 500 can include input mechanisms 506 and/or 508.
  • Input mechanism 506 is, optionally, a rotatable input device or a depressible and rotatable input device, for example.
  • Input mechanism 508 is, optionally, a button, in some examples. [0142]
  • Input mechanism 508 is, optionally, a microphone, in some examples.
  • Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
  • Memory 518 of personal electronic device 500 can include one or more non- transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 700 and 1000 (FIGS. 7A-7B and 10).
  • a computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device.
  • the storage medium is a transitory computer-readable storage medium.
  • the storage medium is a non-transitory computer-readable storage medium.
  • the non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like.
  • Personal electronic device 500 is not limited to the components and configuration of FIG. 5B, but can include other or additional components in multiple configurations.
  • the term“affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1 A, 3, and 5A-5B).
  • an image e.g., icon
  • a button e.g., button
  • text e.g., hyperlink
  • a detected contact on the touch screen acts as a“focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input.
  • a particular user interface element e.g., a button, window, slider, or other user interface element
  • focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these
  • the focus selector moves in accordance with movement of focus between different regions of the user interface.
  • the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user’s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact).
  • a focus selector e.g., a cursor, a contact, or a selection box
  • a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).
  • characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like.
  • the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time).
  • the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user.
  • the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold.
  • a contact with a characteristic intensity that does not exceed the first threshold results in a first operation
  • a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation
  • a contact with a characteristic intensity that exceeds the second threshold results in a third operation.
  • a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.
  • FIG. 5C illustrates detecting a plurality of contacts 552A-552E on touch-sensitive display screen 504 with a plurality of intensity sensors 524A-524D.
  • FIG. 5C additionally includes intensity diagrams that show the current intensity measurements of the intensity sensors 524A-524D relative to units of intensity.
  • the intensity measurements of intensity sensors 524A and 524D are each 9 units of intensity, and the intensity
  • Ij A (Dj/ ⁇ Di)
  • Dj the distance of the respective contact j to the center of force
  • the operations described with reference to FIGS. 5C-5D can be performed using an electronic device similar or identical to device 100, 300, or 500.
  • a characteristic intensity of a contact is based on one or more intensities of the contact.
  • a portion of a gesture is identified for purposes of determining a characteristic intensity.
  • a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases.
  • the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location).
  • a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact.
  • the intensity of a contact 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.
  • the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad.
  • the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad.
  • the device when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch- sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold.
  • a characteristic intensity below the light press intensity threshold e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected
  • these intensity thresholds are consistent between different sets of user interface figures.
  • a decrease of 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 liftoff of the contact from the touch-surface.
  • the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
  • the press input includes an increase in intensity of the respective contact above the 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 the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an“up stroke” of the respective press input).
  • FIGS. 5E-5H illustrate detection of a gesture that includes a press input that corresponds to an increase in intensity of a contact 562 from an intensity below a light press intensity threshold (e.g.,“ITL”) in FIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“ITD”) in FIG. 5H.
  • the gesture performed with contact 562 is detected on touch-sensitive surface 560 while cursor 576 is displayed over application icon 572B corresponding to App 2, on a displayed user interface 570 that includes application icons 572A-572D displayed in predefined region 574.
  • the gesture is detected on touch-sensitive display 504.
  • the intensity sensors detect the intensity of contacts on touch-sensitive surface 560.
  • the device determines that the intensity of contact 562 peaked above the deep press intensity threshold (e.g.,“ITD”) ⁇ Contact 562 is maintained on touch-sensitive surface 560.
  • the intensity which is compared to the one or more intensity thresholds, is the characteristic intensity of a contact. It should be noted that the intensity diagram for contact 562 is not part of a displayed user interface, but is included in FIGS. 5E-5H to aid the reader.
  • the display of representations 578A-578C includes an animation.
  • representation 578A is initially displayed in proximity of application icon 572B, as shown in FIG. 5F.
  • representation 578A moves upward and representation 578B is displayed in proximity of application icon 572B, as shown in FIG. 5G.
  • representations 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed in proximity of application icon 572B, as shown in FIG. 5H.
  • Representations 578A-578C form an array above icon 572B.
  • the animation progresses in accordance with an intensity of contact 562, as shown in FIGS. 5F-5G, where the representations 578A-578C appear and move upwards as the intensity of contact 562 increases toward the deep press intensity threshold (e.g.,
  • the intensity, on which the progress of the animation is based is the characteristic intensity of the contact.
  • the device employs intensity hysteresis to avoid accidental inputs sometimes termed“jitter,” where the device defines or selects a hysteresis intensity threshold with 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).
  • 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.
  • the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an“up stroke” of the respective press input).
  • the press input is detected only when the device detects an increase in intensity of the contact 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 intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
  • the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold.
  • the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
  • UI user interfaces
  • portable multifunction device 100 such as portable multifunction device 100, device 300, or device 500.
  • device 600 includes display 602 (e.g., a display device) and rotatable and depressible input mechanism 604 (e.g., rotatable and depressible in relation to a housing or frame of the device), and microphone 606.
  • display 602 e.g., a display device
  • rotatable and depressible input mechanism 604 e.g., rotatable and depressible in relation to a housing or frame of the device
  • microphone 606 e.g., a microphone
  • device 600 is a wearable electronic device, such as smartwatch.
  • device 600 includes one or more features of devices 100, 300, or 500.
  • clock user interface 608A includes digital indication of time 610 (e.g., a representation of digital clock displaying current hour, and minute values), and multiple affordances, each affordance associated with an application stored on device 600.
  • Date affordance 612 indicates a current date and launches a calendar application upon selection.
  • Remote affordance 614 launches a remote control application upon selection (e.g., an application to control devices external to device 600).
  • Heart rate affordance 616 launches a heart rate monitoring application upon selection.
  • clock user interface 608A (e.g., a clock face interface) also includes multiple noise application affordances that upon selection, launch a noise monitoring application (e.g., noise icon 618, noise status affordance 620, noise meter affordance 622, and compact noise affordance 624).
  • a noise monitoring application e.g., noise icon 618, noise status affordance 620, noise meter affordance 622, and compact noise affordance 624.
  • the noise application on device 600 has not been installed or initialized (e.g., enabled), as a result, noise status affordance 620, noise meter affordance 622, and compact noise affordance 624 do not indicate (e.g., display) any noise data from the noise application.
  • device 600 displays, noise status affordance 620 as a setup prompt (e.g.,“tap to set up”), indicating that the noise application needs to be initialized.
  • FIG. 6A depicts device 600 receiving user input 628A (e.g., a tap) on noise status affordance 620.
  • device 600 displays the user interface 608B, as depicted in FIG. 6B.
  • User interface 608B includes a description of the functionality of the noise application, enable affordance 630 for enabling (e.g., initializing the noise application), and disable affordance 632 for disabling (e.g., maintaining the noise
  • user interface 608C includes indication of time 634 (e.g., indicating a current time of 10:09), noise level indicator 636, noise meter indicator 638, and noise status indicator 640.
  • Noise level indicator 636 provides a numeric indication (e.g., 34 DB) of a first noise level value (e.g., measured by or determined by device 600 from noise data derived from microphone 606).
  • Noise meter indicator 636 provides a graphical indication of a second noise level (e.g., measured by device 600 via microphone 606).
  • the second noise level and the first noise are the same noise level.
  • the first noise level and the second noise level are determined based on common noise data sampled at different time periods and/or rates (e.g., 1-second and 0.1-seconds, respectively).
  • Noise meter indicator 638 includes active portion 638 A (e.g., a visually emphasized portion) that varies in size and/or color according to a second noise level. As illustrate by the following figures, the size of active portion 638 A increases as a noise level increases and the color of the active portion 638 A changes relative to a second threshold level.
  • size includes a number of visually emphasized segments, a relative area occupied by a set of visually emphasized segments, or a position of the right-most edge of a set of visually emphasized segments relative to a scale.
  • each emphasized segment in active portion 638 A represents a predetermined number of decibels (e.g., 10 DB).
  • the first threshold level and the second threshold level are the same level (e.g., 80DB).
  • noise levels e.g., values, amplitudes
  • noise level indicator 636 e.g., values, amplitudes
  • noise status indicator 640 e.g., as described below
  • noise levels are measured or detected by a device external to device 600 (e.g., device 600 receives data representing a current noise level from a remote device communicatively coupled with device 600).
  • noise level indicator 636 includes a“34 DB” value and noise status indicator 640 includes a non-cautionary prompt (e.g., a check mark graphic,“OK,” and a descriptive prompt indicating relatively low risk associated with exposure at the level indicated by noise level indicator 636) indicating that the noise level is below a threshold level (e.g., 80 DB).
  • noise meter indicator 638 provides a graphical indication of a low, consistent noise level by displaying active portion 638 A in a size corresponding to two green segments (e.g., green as represented by diagonal hatching).
  • FIG. 6D depicts the state of user interface 608C in response to a sudden increase (e.g., within 200 millisecond of a spike) in ambient noise (e.g., a fire alarm goes off inside of the computer lab).
  • a sudden increase e.g., within 200 millisecond of a spike
  • ambient noise e.g., a fire alarm goes off inside of the computer lab.
  • the size of active portion 638 A of noise meter indicator 638 has increased from 2-segments to 10-segments and the color transitioned from green to yellow (e.g. yellow represented by horizontal hatching).
  • noise level indicator 636 and noise status indicator 640 maintain the their previous appearance (e.g., as depicted in FIG. 6C).
  • noise level indicator 636 and noise status indicator 640 vary with a first noise level (e.g., a noise level based on a longer 1-second period of noise level data) and the appearance of noise meter indicator 638 varies based on a second noise level (e.g., a noise level based on a shorter 0.1 -second period of noise level data). Consequently, the graphical meter changes more quickly (e.g., instantaneously) than noise level indicator 636 (and noise status indicator 640) in response to sudden changes in ambient noise level. This lagging effect is illustrated by the difference between the noise levels represented by noise level indicator 636 and noise status indicator 640 and noise meter 638.
  • the slower update makes it easier to for a user to decipher (e.g., read) a displayed noise level, while the faster update behavior of graphical meter 638 provides the user with more timely (e.g., responsive) visual feedback.
  • FIG. 6E depicts the state of user interface 608C after an elevated noise level has been sustained (e.g., a fire alarm continues to sound for a 1 -minute).
  • an elevated noise level e.g., a fire alarm continues to sound for a 1 -minute.
  • the size and color of active portion 638 A of noise meter indicator 638 remains unchanged (e.g., compared to the depiction in FIG. 6D).
  • noise level indicator 636 and noise status indicator 640 have been updated to reflect the sustained elevated ambient noise level (e.g., noise level indicator 636 indicates a 113 DB level and noise status indicator 640 includes a cautionary (e.g.,“LOUD”) prompt indicating a noise level above an 80DB threshold).
  • LOUD cautionary
  • FIG. 6F depicts the state of user interface 608C in response to a sudden decrease in ambient noise level (e.g., a fire alarm abruptly stops).
  • a sudden decrease in ambient noise level e.g., a fire alarm abruptly stops.
  • the size of active portion 638 A of noise meter indicator 638 has decrease from 10-segments to 6- segments and the color changed from yellow to green (e.g. green represented by diagonal hatching).
  • noise level indicator 636 and noise status indicator 640 maintain the their previous appearance (e.g., as depicted in FIG. 6E).
  • a noise level exceeds a notification level threshold (e.g., 80 DB, 85 DB, 90 DB, etc.) for a period of time (e.g., 3-minutes)
  • a notification level threshold e.g. 80 DB, 85 DB, 90 DB, etc.
  • device 600 emits haptic alert 642 as depicted in FIG. 6H.
  • noise data used to determine a noise level value is sampled at a first rate while device 600 displays graphical noise meter indicator 620 (e.g., FIG. 6C-6E) and noise meter affordance 622 (e.g., FIGS.
  • a second rate e.g., a lower sampling rate, 20% lower
  • device 600 is not displaying graphical noise meter indicator 638 or noise meter affordance 622 (e.g., FIG. 6H).
  • noise notification user interface 608D of FIG. 61 e.g., a warning notification
  • noise notification user interface 608D includes an explanation of the notification triggering condition (e.g.,“110 DB around 3 MIN”) and the associated hearing loss risk.
  • noise notification user interface 608D includes noise app affordance 644 for launching the noise application, multiple mute affordances 646 for suppressing display of subsequent noise notifications (e.g., display of user interface 608D) for a specified time periods (e.g., 1-hour and the remainder of the day), and dismiss affordance 648.
  • FIG. 6K depicts device 600 receiving user input 628E (e.g., tap)
  • dismiss affordance 648 In response to receiving user input 628E, device 600 displays (e.g., re-displays) clock user interface 608A.
  • selection of dismiss affordance 648 causes device 600 to suppress (e.g., to forgo displaying notification user interface 608D despite a notification triggering condition being detected by device 600) subsequent notifications for a predetermined auto-suppression period (e.g., 30 minutes).
  • notification user interface 608D includes a graphical indication of a noise exposure level (e.g. noise meter indicator 638).
  • noise status affordance 620, noise meter affordance 622, and compact noise affordance 624 now display noise level data associated with the noise application (e.g., since the noise application was initialized via user input 628B).
  • FIG. 6L depicts the state of clock user interface 608A while device 600 is in an environment with a consistent noise level of 34 DB at 10: 18 (e.g. device 600 is located in a low noise environment such as a library).
  • noise status affordance 620 includes a“34 DECIBELS” value and a non-cautionary prompt (e.g., a check mark graphic and“OK”) indicating that the noise level is below a threshold level (e.g., 80 DB).
  • a threshold level e.g. 80 DB
  • noise meter affordance 622 provides a graphical indication of low noise level by displaying active portion 622A in a size corresponding to 4 segments (out of 23 segments) in a green (e.g., green as represented by diagonal hatching). Like active portion 638 A of noise meter indicator 638, the size of active portion 622A is proportional to noise level and the color (e.g., green) indicates a noise level relative to a threshold level (e.g., green below and yellow above).
  • compact noise affordance 624 displays a combination of the information represented by noise meter affordance 622 and noise status affordance 620.
  • compact noise affordance includes a graphical indication of a low noise level by displaying active portion 624A in a size corresponding to 2 segments (out of 11 segments) in green (e.g., green as represented by diagonal hatching), numeric portion 624B includes value (e.g., 34 DB) and graphic portion 624C includes a non cautionary graphic (e.g., a check mark graphic) corresponding to the values indicate by noise status affordance 620.
  • active portion 624A in a size corresponding to 2 segments (out of 11 segments) in green (e.g., green as represented by diagonal hatching)
  • numeric portion 624B includes value (e.g., 34 DB)
  • graphic portion 624C includes a non cautionary graphic (e.g., a check mark graphic) corresponding to the values indicate by noise status affordance 620.
  • FIG. 6M depicts the state of user interface 608A in response to a sudden increase (e.g., a spike) in ambient noise at a time of 10: 19.
  • the size of active portion 622A of noise meter affordance 622 has increased from 4-segments to 17-segments and the color of active portion 622A transitions from green to yellow (e.g. yellow represented by horizontal hatching).
  • the size of active portion 624A of compact noise affordance 624 has increased from 2-segments to 8-segments and the color changed from green to yellow.
  • noise level status affordance 620, numeric portion 624B, and graphic portion 624C have maintained their previous appearance (e.g., as depicted in FIG. 6L).
  • FIG. 6N depicts the state of user interface 608A after an elevated noise level has been sustained (e.g., for 3-minutes).
  • the size and color of active portion 622A of noise meter affordance 622 remain unchanged (e.g., compared to the depiction in FIG. 6M).
  • noise status affordance 620, numeric portion 624B, and graphic portion 624C have been updated to reflect the sustained elevated ambient noise level.
  • device 600 immediately after displaying user interface 608A as depicted FIG. 6N (e.g., after device 600 detects and displays a sustained noise level of 110 DB for 3-minutes, the previously discussed notification triggering condition), device 600 does not output haptic alert (e.g., FIG. 6H) or display noise notification user interface 608D (e.g., FIG. 61), since the previous notification was dismiss within an auto-suppression period (e.g., 30 minutes).
  • haptic alert e.g., FIG. 6H
  • display noise notification user interface 608D
  • FIG. 60 depicts user interface 608A while device 600 operates in a suspended state (e.g., not currently measuring or detecting noise levels).
  • a suspended state e.g., not currently measuring or detecting noise levels.
  • user interface 608A does not indicate noise level values and noise status affordance 620 and graphic portion 624C appear in an alternative form to indicate the suspending state of device 600.
  • noise measurements are suspended upon detection of various operating conditions (e.g., water lock mode on, phone call active, speaker in-use, or watch off-wrist conditions (unless the watch has been manually unlocked)).
  • notification e.g., display of user interface 608D
  • noise measurements are disabled when a noise application feature is disabled (e.g., via device privacy setting or noise app setting).
  • FIGS. 6Z-6AA depict a series user interfaces associated with configuring a noise level threshold (e.g., a noise level threshold corresponding to the thresholds described above with respect to FIGS. 6A-60), from device 600 or from an external device coupled (e.g., wirelessly) to device 600.
  • a noise level threshold e.g., a noise level threshold corresponding to the thresholds described above with respect to FIGS. 6A-60
  • FIGS. 6AD-6AE depict user interfaces for enabling and disabling noise measurement on device 600.
  • FIGS. 6AF-6AL depict various interfaces for initializing or enabling a noise monitoring application (e.g., as describe above with respect to FIGS. 6A-60).
  • the electronic device displays (712), via the display device, a first user interface (e.g., a clock face user interface or user interface of an application) including a graphical object (e.g., a meter) that varies in appearance based on a noise level.
  • a first user interface e.g., a clock face user interface or user interface of an application
  • a graphical object e.g., a meter
  • the electronic device displays (702) a noise level notification (608D) that includes: an indication of the current noise level over the third period of time (e.g., text indicating that a current noise level over the third period of time has exceeded the third threshold noise level; text indicating the amount of time that the current noise level has exceeded the third threshold noise level) (704), and a third affordance (e.g.,“Open Noise”) (e.g., “Open Noise”) (e.g.,“Open Noise”)
  • the third threshold level is the same as the first or second threshold levels.
  • the set of noise notification criteria includes a second criterion that is met when the current noise level exceeds the third threshold noise level for at least a third period of time.
  • the electronic device receives (708) a user input corresponding to the third affordance.
  • the electronic device displays (710) the first user interface (e.g., 608C) (e.g., opening the noise app).
  • Displaying (e.g., automatically) the noise level notification in accordance with the determination that the set of noise notification criteria are met provides a user with quick and easy access to information concerning a current noise exposure level.
  • 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 to provide proper inputs and reducing user mistakes when
  • the noise level notification (e.g., 608D) further includes a fourth affordance (e.g., 646) associated with a second predetermined period and the electronic device receives an input corresponding to the fourth affordance and in response to receiving the input corresponding to the fourth affordance, the electronic device forgoes display of (e.g., suppressing display of) further instances of noise level notifications for the second predetermined time period (e.g., 1 hour, 1 ⁇ 2 hour, reminder of the day, etc.).
  • the fourth affordance in the noise level notification that enables a user to cause the electronic device to forgo displaying further instances of noise level notifications enables the user to quickly and easily suppress further noise level notifications on the electronic device.
  • Providing additional control options without cluttering the UI with additional displayed controls enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
  • the electronic device receives (714) first noise level data (e.g., noise level data corresponding to the noise level over a first period of time; an average value over the first period of time or multiple data points representing the noise level over the first period of time) (e.g., noise level“34 DB” of FIG. 6C) corresponding to a first noise level (e.g. data from a sensor of the electronic device; data from an external electronic device), the first noise level below a threshold noise level (e.g., 80 dB).
  • the first noise level data over the first period of time represents an instantaneous noise level.
  • the electronic device In response to receiving the first noise level data, the electronic device displays (716) the graphical object (e.g., 622, 638) with an active portion (e.g., emphasized or visually distinct portion based on appearance) (e.g., 622A, 638A) of a first size (e.g., a number of segments, a length, or an area relative to the object’s overall size that is proportional to the noise level) based on the first noise data and in a first color (e.g., green).
  • a first size e.g., a number of segments, a length, or an area relative to the object
  • the active portion extends from the left-most edge of the graphical object to a location between the left-most edge and right-most edge of the graphical object.
  • the graphical object includes an indication of the first noise level data other than a size of the active portion (e.g., a numeric value, a position of a point or a line along the axis of a graph). Displaying the graphical object with the active portion of the first size based on the first noise data and in the first color provides a user with easily recognizable and understandable noise exposure level information.
  • Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
  • the electronic device receives (718) second noise level data corresponding to a second noise level different from the first noise level (e.g., the second is either lower or higher than the first) (e.g., noise level“113 DB” of FIG. 6E).
  • second noise level data corresponding to a second noise level different from the first noise level (e.g., the second is either lower or higher than the first) (e.g., noise level“113 DB” of FIG. 6E).
  • the electronic device In response to receiving the second noise level data (720), the electronic device displays (722) the active portion in a second size based on the second noise level that that is different from the first size (e.g., the active portion grows or shrinks corresponding the difference between the first noise level and the second noise level) (e.g., 638 A in FIG. 6D). Displaying the active portion in the second size based on the second noise level in response to receiving the second noise level data enables a user to quickly and easily visually
  • noise exposure level information corresponding to the first noise level data and the second noise level data differentiates between noise exposure level information corresponding to the first noise level data and the second noise level data.
  • Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
  • the electronic device In response to receiving the second noise level data (720), in accordance with a determination that the second noise level exceeds the threshold noise level (e.g., the noise level has increased beyond the 80dB threshold), the electronic device displays (724) the active portion (e.g., 638A in FIG. 6D) in a second color different from the first color (e.g., change from green to yellow). Displaying the active potion in the second color different from the first color in accordance with the determination that the second noise level exceeds the threshold noise level provides visual feedback to the user that the noise exposure level has exceeded a certain threshold.
  • the active portion e.g., 638A in FIG. 6D
  • the electronic device In response to receiving the second noise level data (720), in accordance with a determination that the second noise level does not exceed the threshold noise level (e.g., the noise level remains below the 80dB threshold), the electronic device maintains (726) display of the graphical object in the first color (e.g., maintain as green).
  • the threshold noise level e.g., the noise level remains below the 80dB threshold
  • Displaying the active portion at the third second size based on the third noise level in response to receiving the third noise level data enables a user to quickly and easily visually differentiate between noise exposure level information corresponding to the third noise level data from that corresponding to the first noise level data and the second noise level data.
  • Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
  • the graphical object varies based on noise level over a first period of time (e.g., an average of noise level over a 0.1 -second window) and the first user interface further includes a second graphical object (e.g., a text indication; a graphical indication) (e.g., 620, 624, 636, 640) that varies in appearance based on the noise level over a second period of time that is different from the first period of time (e.g., averaged over a 1- second window).
  • a second graphical object e.g., a text indication; a graphical indication
  • displaying the first user interface includes displaying a first affordance that, when selected, displays a second user interface (e.g., an interface with information about the threshold noise level) (e.g., 640) in accordance with a determination that a current noise level (e.g., based on noise data for the first period of time or noise data for the second period of time) is below a second threshold noise level (e.g., a user-selected threshold).
  • the first affordance includes“OK” or a graphical element (e.g., a checkmark) when the noise level is below the threshold (e.g., 640 in FIGS. 6C, 6D, 6G; 620 in FIGS. 6L-6M).
  • the first threshold and the second threshold are the same.
  • displaying the first user interface includes displaying a second affordance (e.g., without displaying the first affordance), different from the first affordance, that, when selected, displays a third user interface (e.g., the same as the second user interface; different than the first user interface and with information about the threshold noise level) in accordance with a determination that a current noise level is above the second threshold noise level.
  • the first affordance includes“LOUD” or a graphical element (e.g., an exclamation point) when the noise level is at or above the threshold.
  • the electronic device includes one or more noise sensors (e.g., one or more pressure sensing devices such as a microphone or microphone array) (e.g., 606), and the first noise level data and the second noise level data are received from the one or more noise sensors.
  • the display device and the one or more noise sensors are located within a common housing or body of the electronic device and the first noise level data and the second noise level data represent the noise level of the physical environment where the electronic device is located.
  • the first noise level data and the second noise level data are received from a second electronic device that is different from the first electronic device (e.g., noise level data is received at the electronic device displaying the UI from a device external to the electronic device displaying the UI).
  • the electronic device samples noise level data at a first sampling rate (e.g., receiving new noise level data at a first rate).
  • the electronic device samples noise level data at a second sampling rate different from the first sampling rate.
  • the first noise level data and the second noise level data are spaced apart by a first time interval. While the first user interface is not displayed, noise level data is received at a second time interval that is longer than the first time interval.
  • the second sampling rate is 20% of the first sampling rate.
  • method 1000 optionally includes one or more of the characteristics of the various methods described above with reference to method 700.
  • information concerning noise exposure levels corresponding to one or more of the output devices described in method 1000 can be represented or provided to a user using the graphical indication (e.g., a graphical object) described above that varies in appearance based on the noise exposure level.
  • graphical indication e.g., a graphical object
  • FIGS. 8A and 8B illustrate user interfaces within a health application for accessing environmental noise data.
  • FIGS. 8A and 8B depict device 800 receiving inputs (e.g., 806A and 806B) at environmental audio levels affordance 804A and 804B,
  • device 800 Upon detecting these inputs, device 800 displays data viewing interface 808C as depicted in FIG. 8C.
  • FIGS. 8C-8I depict various techniques for displaying and manipulating stored environmental noise data via user interface 808C.
  • user interface 808C includes chart 805 displaying environmental noise exposure data (e.g., amplitudes or levels of noise a user associated with device 800 has been exposed to) over a selectable period (e.g., day, week, month, year, etc.).
  • environmental noise exposure data e.g., amplitudes or levels of noise a user associated with device 800 has been exposed to
  • a selectable period e.g., day, week, month, year, etc.
  • environmental noise exposure data associated with a specific period (e.g., day of a week) on chart 805 is selected (e.g., via user input 806C).
  • user interface 808C displays additional information about the selected environmental noise exposure data (e.g., details affordance 812).
  • device also displays data overlay 810 at a location on chart 805 corresponding to the selected environmental noise exposure data in order to provide a visual indication of the data corresponding to the information displayed by details affordance 812.
  • device 800 displays average details affordance 818 in respond to detecting selection (e.g., user input 806E) of average overlay 81 OB.
  • a depicted by FIGS. 8F-8G in response to receiving user input 806F at daily average affordance 820, device 800 displays daily average overlay 810C (e.g., a visual reference to the average environmental noise exposure levels as calculated on a daily basis).
  • device 800 displays noise classification affordance 816 (as depicted in FIG.
  • a threshold level e.g. 80 DB
  • device in response to a determination that the average noise exposure level (e.g., as indicated by average overlay 810B) is above a threshold level (e.g., 80 DB), device displays noise classification affordance 816 with a different appearance (e.g., the affordance behaves similar to noise status affordance 620 or noise status indicator 640 as describe above with respect to FIGS. 6A-60).
  • device 800 displays maximum level indicator 824A and minimum level indicator 824B (e.g., a visual references to the highest and lowest noise exposure levels within the displayed environmental noise level data on chart 805).
  • maximum level indicator 824A and minimum level indicator 824B e.g., a visual references to the highest and lowest noise exposure levels within the displayed environmental noise level data on chart 805.
  • FIGS. 8J-8K depict user interfaces for enabling and disabling noise measurement on device 800.
  • measurements on a device external to device 800 e.g., a device used to obtain environmental noise exposure data for display via the user interfaces described above
  • may be turned off or deactivated in response to disabling other features on a device external e.g., wrist detection.
  • FIGS. 9A-9G illustrate exemplary user interfaces for monitoring noise levels (e.g., exposure to noise due from media devices), in accordance with some embodiments.
  • the user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 10.
  • FIG. 9A depicts device 900 displaying user interface 904A on display 902.
  • user interface 904A includes chart 906 depicting a set of daily audio amplitude values (e.g., corresponding to the range of sound levels experienced by a user of device 900 due to use of connected audio output devices) over a 7-day period.
  • audio amplitude values are determined based on an output volume setting of device 900 (e.g., audio levels are not measured via a microphone). In some embodiments, audio amplitude values (e.g. levels of sound exposure due to device use) are estimated or extrapolated based on a known output device response (e.g., sensitivity, frequency response, etc.). As depicted in FIG.9A, chart 905 includes maximum indication 908 and minimum indication 910, representing the highest and lowest audio amplitude levels experienced by a user of device 900 due to use of connected audio output devices.
  • average affordance 914 is displayed in a selected state (e.g., it was previously selected via a user input or was selected by default upon display of user interface 904A).
  • Average affordance 914 includes a value indicating an average audio level over the set of displayed audio amplitude values (e.g.,“77 DB”).
  • Chart 905 includes an overlay line corresponding the average audio level indicated by average affordance 914 (e.g. overlay 912).
  • the average audio level is not an average of the displayed data but rather a time-based average of underlying data (e.g., an average based on how long a user was exposed to each level (e.g., sound pressure level) depicted by the data in chart 905).
  • the data depicted by chart 905 represents the audio amplitudes levels a device user has been exposed to over the course of a day or other period of time (e.g., hour, week, year, month).
  • user interface 904A includes an audio classification indicator 922, which provides a non-numeric indication (e.g., an indication including graphics and/or text) of the average audio level relative to a threshold (e.g., a predetermined 80DB threshold).
  • a threshold e.g., a predetermined 80DB threshold.
  • the audio classification indicator 922 indicates that the average audio level (e.g., 77 DB) is below an 80 DB threshold with an“OK” and a check mark graphic.
  • user interface 904A includes device type filtering affordances (e.g., affordances associated with a specific type of device) for emphasizing data in chart 905 attributable to each respective device type (e.g., emphasizing a subset of the set of daily audio amplitude values included in chart 905 of FIG. 9A).
  • Each device type filtering affordance e.g., earbuds filtering affordance 916, headphones filtering affordance 918, uncalibrated devices affordance 920
  • a device type corresponds to a single device.
  • a single device includes a pair (e.g., left and right) of connected devices.
  • FIG. 9 A depicts device 900 receiving user input 906 A (e.g., a tap) on uncalibrated device affordance 920.
  • device 900 displays user interface 904B.
  • uncalibrated device affordance 920 is replaced by Bluetooth earbuds affordance 924 and generic headphones affordance 926, each
  • an audio output device coupled (e.g., wirelessly or physically) to device 900 (e.g. audio output devices receive analog or digital audio signals generated by device 1100 and convert those into acoustic output).
  • FIG. 9B depicts device 900 receiving user input 906B (e.g., a tap) on earbuds affordance 916.
  • device 900 displays user interface 904C (e.g., an interface emphasizing audio level data associated with earbuds type output devices), as depicted in FIG. 9C.
  • earbuds type output devices are calibrated devices (e.g., devices with a known frequency response).
  • user interface 904C emphasizes audio level data attributable to one or more output devices associated with the earbuds affordance 916.
  • a set of data points e.g., ranges of audio exposure level data
  • devices corresponding to the selected device type filter e.g., earbud type devices
  • are visually distinguished e.g., by varying on or more visual property such as color, hue, saturation, texture, etc.
  • data not attributable to devices corresponding to the selected device type filter e.g., earbud type devices
  • data attributable to earbud type devices corresponds to black data points on chart 905.
  • visually distinguishing data e.g., a set of exposure levels attributable to a first device type includes de-emphasizing noise exposure levels attributable to a second device type by varying one or more visual properties (e.g., brightness, opacity, color, contrast, hue, saturation, etc.).
  • device 900 updates overlay 912 to depict an average audio level (e.g., 72 DB) based on the emphasized set of noise amplitude values (e.g., the average audio level attributable to earbud device types).
  • an average audio level e.g., 72 DB
  • FIG. 9C depicts device 900 receiving user input 906C (e.g., a tap) on headphones affordance 918.
  • device 900 displays user interface 904D (e.g., an interface emphasizing noise level data associated a headphones type output device), as depicted in FIG. 9D.
  • user interface 904D e.g., an interface emphasizing noise level data associated a headphones type output device
  • headphone type output devices are calibrated devices (e.g., devices with a known frequency response).
  • user interface 904D emphasizes audio level data attributable to one or more output devices associated with the headphones affordance 918.
  • a set of data points e.g., ranges of audio exposure level data
  • devices corresponding to the selected device type filter e.g., headphones type devices
  • are visually distinguished e.g., by varying on or more visual property such as color, hue, saturation, texture, etc.
  • data not attributable to devices corresponding to the selected device type filter e.g., headphone type devices.
  • data attributable to headphones type devices corresponds to black data points on chart 905.
  • device 900 updates overlay 912 to depict an average audio level (e.g., 90 DB) based on the emphasized set of noise amplitude values (e.g., the average audio level attributable to headphones device types).
  • Device 900 also updated, audio classification indicator 922 to indicate that the average audio level (e.g., 90 DB) has exceeded an 80 DB threshold with an“LOUD” and caution graphic.
  • Fig. 9D depicts device 900 receiving user input 906D (e.g., a tap) on generic headphones affordance 926.
  • device 900 displays user interface 904E (e.g., a warning prompt interface), as depicted in FIG. 9E.
  • user interface 904E informs a user that the audio levels based on uncalibrated devices may not be accurate. For example, device 900 cannot accurately extrapolate audio exposures levels without data characterizing the response of a given output device (e.g., a headphone frequency response curve).
  • FIG. 9E depicts device 900 receiving user input 906E (e.g., a tap) on an acknowledgement affordance (e.g.,“OK”).
  • device 900 displays user interface 904F (e.g., an interface emphasizing noise level data associated generic headphones type output devices) as depicted in FIG. 9F.
  • user interface 904F emphasizes audio level data attributable to one or more output devices associated with generic headphones affordance 926.
  • a set of data points e.g., ranges of audio exposure level data
  • devices corresponding to the selected device type filter e.g., generic headphones type devices
  • are visually distinguished e.g., by varying on or more visual property such as color, hue, saturation, texture, etc.
  • data not attributable to devices corresponding to the selected device type filter e.g., generic headphones type devices.
  • data attributable to generic headphones type devices corresponds to black data points on chart 905.
  • device 900 updates overlay 912 to depict an average audio level (e.g., 85 DB) based on the emphasized set of noise amplitude values (e.g., the average audio level attributable to generic headphones device types).
  • an average audio level e.g. 85 DB
  • FIG. 9F depicts device 900 receiving user input 906F (e.g., a tap) on day time- scale affordance 928.
  • user interface 904G e.g., an interface emphasizing noise level data associated generic headphones type output devices over a day period
  • audio level data corresponding to Saturday May 22 e.g. center day of the 7-day period displayed throughout FIGS. 9A-9F.
  • audio exposure levels corresponding to a day other than the center day are displayed by chart 905.
  • user interface 904G emphasizes audio level data attributable to one or more output devices associated with generic headphones affordance 926 over 24-hour period (e.g., a day).
  • a set of data points e.g., ranges of audio exposure level data
  • devices corresponding to the selected device type filter e.g., generic headphones type devices
  • are visually distinguished e.g., by varying on or more visual property such as color, hue, saturation, texture, etc.
  • data attributable to generic headphones type devices corresponds to black data points on chart 905.
  • FIG. 10 is a flow diagram illustrating a method for monitoring noise exposure levels using an electronic device, in accordance with some embodiments.
  • Method 1000 is performed at an electronic device (e.g., 100, 300, 500, 600, 800, 900, and 1100) with a display device and a touch-sensitive surface.
  • Some operations in method 1000 are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.
  • method 700 provides an intuitive way for monitoring noise exposure levels.
  • the method reduces the cognitive burden on a user to monitor noise exposure levels, thereby creating a more efficient human-machine interface.
  • the electronic device receives (1002) first noise level data attributable to a first device type (e.g., uncalibrated devices, such as wired headphones connected to the electronic device via a port (e.g., a headphone jack) or uncalibrated wireless headphones).
  • the electronic device receives (1002) second noise level data attributable to a second device type (e.g., calibrated devices, such as calibrated wireless headphones) different from the first device type.
  • the electronic device identifies the first and second noise level data based on one or more output signals (e.g., voltages, digital audio data, etc.) sent by the electronic device to an output device of the first type.).
  • the electronic device displays (1004), via the display device (e.g., 902), a first user interface (e.g., 904A).
  • the first user interface is displayed in response to a user request (e.g., request to view a UI of noise application through search feature of health app or notifications in discover tab of health app).
  • the first user interface includes a first representation of received noise level data that is based on the first noise level data and the second noise level data (e.g., a graph showing combined data or concurrently showing separate data for each of the first and second noise level data) (1006) (e.g., 905 in FIG. 9 A).
  • the first user interface includes a first device type data filtering affordance (1008) (e.g., 916).
  • Including the first representation of received noise level data that is based on the first noise level data and the second noise level data in the first user interface visually informs a user of the noise level data in an easily understandable and recognizable manner.
  • Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
  • the electronic device While displaying the first user interface, the electronic device detects (1012) a first user input corresponding to selection of the first device type data filtering affordance (e.g., 916, 918, 926).
  • a first user input corresponding to selection of the first device type data filtering affordance (e.g., 916, 918, 926).
  • the electronic device displays (1014) a second representation of received noise level data that is based on the second noise level data and that is not based on the first noise level data (e.g., a second representation (e.g., a separate graph, a visual emphasis on the first representation) that emphasizes noise level data from calibrated devices compared to the depiction of noise level data in the first
  • a second representation e.g., a separate graph, a visual emphasis on the first representation
  • Displaying the second representation of the received noise level data that is based on the second noise level data and that is not based on the first noise level data (e.g., as a separate graph) in response detecting the first user input enables a user to more easily view information corresponding to the second noise level data.
  • Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
  • the electronic device maintains (1016) display of the first representation of received noise level data (e.g., 905 in FIGS. 9C and 9D-9G).
  • the second representation of received noise level data is visually distinguished from the first representation of received noise level data (e.g., 905 in FIGS. 9C and 9D-9G).
  • visually distinguishing data includes de-emphasizing noise exposure levels attributable to the first device type data by varying one or more visual properties (e.g., brightness, opacity, color, contrast, hue, saturation) (e.g., 905 in FIGS. 9C and 9D-9G).
  • visually distinguishing data includes emphasizing noise exposure levels attributable to the second device type by varying one or more visual properties (e.g., brightness, opacity, color, contrast, hue, saturation) (e.g., 905 in FIGS. 9C and 9D-9G).
  • the second noise level data corresponds to noise level data attributable to a single device.
  • a single device includes a pair of linked devices (e.g., wirelessly linked left and right headphones).
  • the first noise level data corresponds to noise level data attributable to a plurality of devices (e.g., a plurality of sets of linked devices (e.g., pairs of linked wireless headphones).
  • a plurality of devices e.g., a plurality of sets of linked devices (e.g., pairs of linked wireless headphones).
  • the second noise level data includes third noise level data attributable to a third device type (e.g., data from an additional calibrated device).
  • the first user interface includes a second device type filtering affordance corresponding to the third noise level data (e.g., an additional calibrated device affordance in additions to the first calibrated device affordance) (e.g., 918).
  • the electronic device while displaying the first user interface (e.g., 904C), the electronic device detects a user input corresponding to selection of the second device type filtering affordance (e.g., 906C).
  • the electronic device in response detecting the user input corresponding to a selection of the second device type filtering affordance, displays a third representation of the third noise level data (e.g., 905 in FIG. 6D). Displaying the third representation of the third noise level data enables a user to more easily view and understand information corresponding to the third noise level data. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.
  • the first user interface includes, prior to detecting the first user input, an average noise exposure level indicator (e.g., 912, 914) indicating an average noise exposure level corresponding to the first noise level data and the second noise level data for a first time period (e.g., a day, a week) (1010).
  • the average noise level indicator includes a check mark or exclamation point,‘LOUD’ or ⁇ K’ (e.g.,
  • the electronic device in response detecting the user input corresponding to a selection of the first device type filtering affordance (e.g., 916), the electronic device updates (1018) the average noise exposure level indicator to indicate an average noise level corresponding to the second noise level data (e.g., that does not correspond to the first noise level data) (e.g., indicating the average based on only the calibrated data associated with the second device type) (e.g., 912 in FIGS. 9B-9C).
  • the average noise exposure level indicator to indicate an average noise level corresponding to the second noise level data (e.g., that does not correspond to the first noise level data) (e.g., indicating the average based on only the calibrated data associated with the second device type) (e.g., 912 in FIGS. 9B-9C).
  • the second noise level data is based, at least in part, on one or more signals transmitted from the electronic device to one or more devices of the second type (e.g., noise levels are not based on incoming signals or data (e.g., audio levels measured via a microphone).
  • noise levels are estimated based on a volume setting (e.g., volume at 100%) and a known output device response (e.g., headphones of a first type output 87dB at 100% for the particular signal being played).
  • method 700 optionally includes one or more of the characteristics of the various methods described above with reference to method 1000.
  • the graphical indication e.g., a graphical object
  • the noise exposure level information can be used to display noise exposure level information corresponding to one or more output devices.
  • FIGS. 11 A-l IF depict user interfaces (e.g., 1104A-1104F) for accessing and displaying audiogram data (e.g., sets of data representing hearing impairment at various sound frequencies).
  • audiogram data is received at device 1100 from a third-party application.
  • audiogram data is inputted manually by a device user (e.g., via series of user inputs detected by device 1100).
  • FIGS. 11 A and 1 IB illustrate user interfaces within a health application for accessing audiogram noise data.
  • FIGS. 1 lC-1 ID illustrate techniques for displaying audiogram data and selecting or visually emphasizing portions of the data (e.g., a portion associated with a left or right side).
  • this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person.
  • personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user’s health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.
  • the present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users.
  • the personal information data can be used to provide a user with an accurate assessment of personal noise exposure throughout the day.
  • other uses for personal information data that benefit the user are also contemplated by the present disclosure.
  • health and fitness data may be used to provide insights into a user’s general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.
  • the present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices.
  • such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure.
  • Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes.
  • HIPAA Health Insurance Portability and Accountability Act
  • the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data.
  • the present technology can be configured to allow users to select to“opt in” or“opt out” of participation in the collection of personal information data during registration for services or anytime thereafter.
  • users can select not to provide sound recording data for monitoring noise exposure levels.
  • users can select to limit the length of time sound recording data is maintained or entirely prohibit the development of a noise exposure profile.
  • the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.
  • personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed.
  • data de-identification can be used to protect a user’s privacy. De identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.
  • noise exposure data can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal or publicly available information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • General Health & Medical Sciences (AREA)
  • Toxicology (AREA)
  • Environmental & Geological Engineering (AREA)
  • Emergency Management (AREA)
  • Health & Medical Sciences (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • General Engineering & Computer Science (AREA)
  • Acoustics & Sound (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

La présente invention concerne de manière générale des interfaces utilisateur et des techniques servant à surveiller des niveaux d'exposition au bruit à l'aide d'un dispositif électronique. Selon certains modes de réalisation, le dispositif électronique affiche une indication graphique d'un niveau d'exposition au bruit sur une première période de temps à l'aide d'une zone de l'indication graphique qui est colorée pour représenter le niveau d'exposition au bruit, la couleur de la zone passant d'une première couleur à une seconde couleur lorsque le niveau d'exposition au bruit dépasse un premier seuil. Selon certains modes de réalisation, le dispositif électronique affiche des niveaux d'exposition au bruit attribuables à un premier type de dispositif de sortie et à un second type de dispositif de sortie et, en réponse à la sélection d'une mise à disposition de filtrage, la distinction visuelle d'un ensemble de niveaux d'exposition au bruit attribuable au second type de dispositif de sortie.
PCT/US2020/025768 2019-06-01 2020-03-30 Interfaces utilisateur servant à surveiller des niveaux d'exposition au bruit Ceased WO2020247049A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201962856016P 2019-06-01 2019-06-01
US62/856,016 2019-06-01
DKPA201970534 2019-08-27
DKPA201970534A DK201970534A1 (en) 2019-06-01 2019-08-27 User interfaces for monitoring noise exposure levels

Publications (1)

Publication Number Publication Date
WO2020247049A1 true WO2020247049A1 (fr) 2020-12-10

Family

ID=70465351

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2020/025768 Ceased WO2020247049A1 (fr) 2019-06-01 2020-03-30 Interfaces utilisateur servant à surveiller des niveaux d'exposition au bruit

Country Status (1)

Country Link
WO (1) WO2020247049A1 (fr)

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3859005A (en) 1973-08-13 1975-01-07 Albert L Huebner Erosion reduction in wet turbines
US4826405A (en) 1985-10-15 1989-05-02 Aeroquip Corporation Fan blade fabrication system
US6323846B1 (en) 1998-01-26 2001-11-27 University Of Delaware Method and apparatus for integrating manual input
US6570557B1 (en) 2001-02-10 2003-05-27 Finger Works, Inc. Multi-touch system and method for emulating modifier keys via fingertip chords
US6677932B1 (en) 2001-01-28 2004-01-13 Finger Works, Inc. System and method for recognizing touch typing under limited tactile feedback conditions
US20050190059A1 (en) 2004-03-01 2005-09-01 Apple Computer, Inc. Acceleration-based theft detection system for portable electronic devices
US20060017692A1 (en) 2000-10-02 2006-01-26 Wehrenberg Paul J Methods and apparatuses for operating a portable device based on an accelerometer
US20080159547A1 (en) * 2006-12-29 2008-07-03 Motorola, Inc. Method for autonomously monitoring and reporting sound pressure level (SPL) exposure for a user of a communication device
US7657849B2 (en) 2005-12-23 2010-02-02 Apple Inc. Unlocking a device by performing gestures on an unlock image
WO2013169849A2 (fr) 2012-05-09 2013-11-14 Industries Llc Yknots Dispositif, procédé et interface utilisateur graphique permettant d'afficher des objets d'interface utilisateur correspondant à une application
WO2014105276A1 (fr) 2012-12-29 2014-07-03 Yknots Industries Llc Dispositif, procédé et interface utilisateur graphique pour effectuer une transition entre des relations d'entrée tactile et de sortie d'affichage
US20150110277A1 (en) * 2013-10-22 2015-04-23 Charles Pidgeon Wearable/Portable Device and Application Software for Alerting People When the Human Sound Reaches the Preset Threshold
US20150110279A1 (en) * 2013-10-21 2015-04-23 Mass Moment LLC Multifunctional Wearable Audio-Sensing Electronic Device

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3859005A (en) 1973-08-13 1975-01-07 Albert L Huebner Erosion reduction in wet turbines
US4826405A (en) 1985-10-15 1989-05-02 Aeroquip Corporation Fan blade fabrication system
US6323846B1 (en) 1998-01-26 2001-11-27 University Of Delaware Method and apparatus for integrating manual input
US20020015024A1 (en) 1998-01-26 2002-02-07 University Of Delaware Method and apparatus for integrating manual input
US20060017692A1 (en) 2000-10-02 2006-01-26 Wehrenberg Paul J Methods and apparatuses for operating a portable device based on an accelerometer
US6677932B1 (en) 2001-01-28 2004-01-13 Finger Works, Inc. System and method for recognizing touch typing under limited tactile feedback conditions
US6570557B1 (en) 2001-02-10 2003-05-27 Finger Works, Inc. Multi-touch system and method for emulating modifier keys via fingertip chords
US20050190059A1 (en) 2004-03-01 2005-09-01 Apple Computer, Inc. Acceleration-based theft detection system for portable electronic devices
US7657849B2 (en) 2005-12-23 2010-02-02 Apple Inc. Unlocking a device by performing gestures on an unlock image
US20080159547A1 (en) * 2006-12-29 2008-07-03 Motorola, Inc. Method for autonomously monitoring and reporting sound pressure level (SPL) exposure for a user of a communication device
WO2013169849A2 (fr) 2012-05-09 2013-11-14 Industries Llc Yknots Dispositif, procédé et interface utilisateur graphique permettant d'afficher des objets d'interface utilisateur correspondant à une application
WO2014105276A1 (fr) 2012-12-29 2014-07-03 Yknots Industries Llc Dispositif, procédé et interface utilisateur graphique pour effectuer une transition entre des relations d'entrée tactile et de sortie d'affichage
US20150110279A1 (en) * 2013-10-21 2015-04-23 Mass Moment LLC Multifunctional Wearable Audio-Sensing Electronic Device
US20150110277A1 (en) * 2013-10-22 2015-04-23 Charles Pidgeon Wearable/Portable Device and Application Software for Alerting People When the Human Sound Reaches the Preset Threshold

Similar Documents

Publication Publication Date Title
US10764700B1 (en) User interfaces for monitoring noise exposure levels
US12143784B2 (en) User interfaces for managing audio exposure
US11228835B2 (en) User interfaces for managing audio exposure
AU2023226704B2 (en) Accessing system user interfaces on an electronic device
AU2023212604B2 (en) User interfaces for managing audio exposure
US12511021B2 (en) Device management user interface
US20190369699A1 (en) User interfaces for indicating battery information on an electronic device
EP3971698A1 (fr) Affichage et mise à jour d'un ensemble de vues d'application
EP3788776A1 (fr) Interfaces d'utilisateur pour mise à jour de réglages de connexion aux réseaux de dispositifs externes
AU2020285524B2 (en) Methods and user interfaces for sharing audio
US12008290B2 (en) Methods and user interfaces for monitoring sound reduction
US12314632B2 (en) Methods and user interfaces for monitoring sound reduction
WO2020247049A1 (fr) Interfaces utilisateur servant à surveiller des niveaux d'exposition au bruit
WO2024253986A1 (fr) Techniques de gestion de lecture de supports
WO2023239620A1 (fr) Création d'autocollant pour messagerie
EP4515573A1 (fr) Systèmes et procédés de suivi de sommeil

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20721979

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20721979

Country of ref document: EP

Kind code of ref document: A1