Listening device with automatic mode change capabilities

Information

  • Patent Grant
  • 10631104
  • Patent Number
    10,631,104
  • Date Filed
    Friday, September 9, 2016
    8 years ago
  • Date Issued
    Tuesday, April 21, 2020
    4 years ago
Abstract
A hearing aid includes a casing configured to fit behind an ear of a user's head and against a side of the user's head. The hearing aid further includes a first proximity sensor associated with the casing and configured to generate a first signal that is proportional to a proximity of the casing to the ear and includes a processor coupled to the first proximity sensor and configured to select an operating mode from a plurality of operating modes in response to the first signal.
Description
FIELD

This disclosure relates generally to hearing aids, and more particularly to hearing aids having different modes and automatic mode change functionality.


BACKGROUND

Hearing aids are often designed to change states (on and off) and modes (sleep mode, normal mode, phone mode, and other known modes) as necessary. Various methods of changing states and modes have been developed. The most common method includes manual switches for turning the hearing aid on/off. While manual switches are simple to use, such switches typically offer only binary state options, such as on/off. The manual switch requires the user to remember to turn off the hearing aid at night. Failure by the user to do so can result in battery charge losses of up 50% of the total battery life. Additionally, a mechanical switch potentially exposes the internal circuitry of the hearing aid to the elements, including contaminants such as water, and provides the hearing aid with a point of potential failure.


Another more elaborate method uses algorithms that monitor the sound conditions and change modes depending on the type/amount of noise in the user's environment. However, using a software solution to determine the state/operating mode of the hearing aid requires substantial programming and software development, generates additional strain and wear on the processor and microphone, and often requires a large portion of the circuitry to remain on during the off/sleep mode in order to wake the hearing aid later, unnecessarily depleting the battery.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of an embodiment of a hearing aid including a sensor for detecting a proximity that can be used to initiate automatic mode and state changes.



FIG. 2 is a perspective view of a user's ear and a partial cross-sectional view of an embodiment of the hearing aid of FIG. 1 including an in-ear sensor for detecting proximity.



FIG. 3 is a flow diagram of an embodiment of a method of activating a hearing aid in response to detecting a proximity of a user's ear.



FIG. 4 is a flow diagram of an embodiment of a method of determining an operating mode of a hearing aid in response to detecting a proximity.





In the following description, the use of the same reference numerals in different drawings indicates similar or identical items.


DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

In a behind-the-ear hearing aid, the casings of the hearing aids are designed to fit comfortably behind one of the user's ear. For example, a hearing aid designed to fit behind a right ear may be a mirror opposite (in terms of the shape of the casing) relative to a hearing aid designed to fit behind a left ear. Hearing aids are often sold in pairs, and the user is expected to select the correct hearing aid for the correct ear. Unfortunately, the differences between the hearing aid casings can be subtle and, particularly for new users, incorrect selection of the proper hearing aid adds to the overall difficulty of adjusting to wearing hearing aids. Moreover, from a manufacturing perspective, providing two different casings (specifically for the right ear and the left ear) adds to the design cost and increases the manufacturing costs.


Embodiments of a hearing aid are described below that can be worn by a user interchangeably on either of the user's ears. The hearing aid includes one or more proximity sensors configured to detect the proximity of the user's ear or side of the head relative to the casing of the hearing aid and processing logic to determine operational states and modes of the hearing aid processor in response to detecting the proximity. In particular, one or more proximity sensors can be used to determine when the hearing aid is attached to a user's ear, and the hearing aid can be configured to transition from an off-state to an on-state based on this determination. Further, others of the one or more sensors can be used to detect the side of the user's head to determine which ear the hearing aid is attached to, and the hearing aid can be configured to select, for example, an appropriate mode (right ear/left ear) in response thereto or to select a low power or power off mode in response to detecting that the hearing aid has been removed from the user's ear.


Further, these sensors can be configured to detect proximity of a mobile phone, and the hearing aid may be configured to enter a phone mode in response thereto. In general, the casing configured to fit either ear and the associated circuitry operates to automatically configure the hearing aid for operation with respect to the ear to which the hearing aid is attached, thereby reducing manufacturing, programming, and development costs and increasing the flexibility and ease of use for the user. At the same time, replacing the manual on/off switches with an automatic mode detection system improves system reliability, improves the hearing aid's resistance to dust and water, and reduces wear and tear on the hearing aid. An example of a hearing aid is described with respect to FIG. 1 that is configured for automatic mode changes based on proximity detection.



FIG. 1 is a block diagram of an embodiment of a hearing aid 100 including sensors 122, 124, and 126, each of which is configured to sense a proximity and to provide a signal proportional the proximity to a controller 104, which is configured to initiate automatic mode and state changes in response to the signals. Hearing aid 100 includes a casing 102, which defines an enclosure for securing circuitry and which is configured to be worn behind the user's ear. The casing 102 is symmetrical and is designed to fit behind either ear. Casing 102 has a left surface designed to fit against the right side of the user's head, a right surface designed to fit against the left side of the user's head, and a front surface curved to fit against the back of the user's ear.


Hearing aid 100 includes a front sensor 122 configured to detect a proximity of an object, such as the user's ear, relative to hearing aid 100. Front sensor 122 is located on a concave-curved portion shaped to fit the back of the user's ear on a front portion of casing 102, such that the proximity is detected when the casing 102 is placed against the curvature of the back of the user's ear. Hearing aid 100 further includes a left sensor 124 located at or adjacent to a surface of the left side of the casing 102 and configured to detect proximity of the user's head relative to the left side of the hearing aid 100. Hearing aid 100 also includes right sensor 126 located at or adjacent to a surface of the right side of the casing 102 and configured to detect a proximity of the user's head relative to the right side of the hearing aid 100. Sensors 122, 124, and 126 can include various types of proximity sensors, alone or in combination, that are configured to detect proximity of an object. Alternatively, sensors 122, 124, and 126 may include temperature sensors, pressure sensors, light sensors, capacitance sensors, or other known types of sensors.


Hearing aid 100 further includes a controller 104 a first input connected an output of front sensor 122, a second input connected to an output of left sensor 124, and a third input connected to an output of right sensor. Controller 124 further includes an output connected to an input of a processor 118 and an input/output connected to a delay circuit 106.


Processor 118 includes an input coupled to a microphone 120, an output coupled to a speaker 108, and an input/output coupled to a memory 110. Hearing aid 100 may further include an analog-to-digital converter including an input connected to the output of microphone 120 and an output connected to the input of processor 118. Further, hearing aid 100 may include a digital-to-analog converter including an input connected to the output of processor 108 and an output connected to the input of speaker 108.


Memory 110 includes processor-executable instructions that, when executed by processor 118, cause the processor 118 to determine at least one of a plurality of operating modes 130, such as right ear mode 112, left ear mode 114, ideal (or optimal) mode, sleep mode, a power off mode, and other modes. Memory 110 further includes processor-executable instructions that, when executed by processor 118, cause processor to determine an operating state of hearing aid 100 from the one or more states 132. Processor 118 executes instructions to determine the state of hearing aid 100 from the one or more states 132 and to select an operating mode from the plurality of operating modes 130 in response to determining the state.


In operation, each of the front sensor 122, the left sensor 124, and the right sensor 126 generates a proximity signal that is proportional to proximity of an object to the respective sensor. Controller 104 monitors the signals from sensors 122, 124, and 126 and determines if a state/mode change to the hearing aid should be made. In particular, the controller 104 monitors the signals to detect a change that exceeds a threshold. In a particular example, the controller 104 compares a difference between a ratio of the signals and a previous ratio (stored in a volatile memory (not shown) of controller 104) to a threshold to determine when a change is significant enough to warrant a state/mode adjustment. In response to detecting a change that exceeds the threshold, controller 104 provides a mode change signal to processor 118 to cause the processor 118 to execute the operating states instructions 132 to determine the state of hearing aid 100 and to execute operating modes instructions 130 to select a suitable operating mode for the hearing aid 100.


Delay circuit 106 provides a timing or delay signal to controller 104 to delay the activation of hearing aid 100 to prevent mechanical feedback caused by introducing speaker 108 into the user's ear. In some instances, delay circuit 106 may also be used to control the controller 104 to provide a timing signal for monitoring the signal outputs of the sensors 122, 124, and 126. Memory 110 also includes sound-processing instructions 116 executable by processor 118 to shape sounds received at microphone 120 to produce modulated signals for reproduction by speaker 108 at within the user's ear.


In one example, hearing aid 100 is in an off state or a sleep state to conserve energy. When the user positions the casing 102 of the hearing aid 100 behind his ear, front sensor 122 detects a proximity to the user's ear and left sensor 124 or right sensor 126 detects a proximity to the user's head. Front sensor 122, left sensor 124, and right sensor 126 each produce output signals proportional to the proximity of the user's ear or head. If the user places hearing aid 100 on his right ear, left sensor 124 detects the proximity of the right side of the user's head that becomes relatively stable over time, whereas the right sensor 126 may detect a proximity based on the position of the user's hand relative to the right sensor 126 that is transient (as compared to the signal from the left sensor 124).


In an example, controller 104 receives input signals from front sensor 122, left sensor 124, and delay circuit 106, and provides a control signal to processor 118. In an example, in response to a signal from delay circuit 106, controller 104 waits a predetermined period before sending the control signal to processor 118 to give the user time to complete insertion of hearing aid 100 before providing modulated sound signals to speaker 108.


Processor 118 receives the control signal from controller 104, and in response to receiving the control signal, processor 118 changes the state of hearing aid 100 from an off-state to an on state, and applies a right ear operational mode to hearing aid 100 in response to determining that casing 102 is mounted to the user's right ear. After switching to the right ear operational mode, processor 118 executes one of the sound-processing (sound shaping) instructions 116 corresponding to the hearing deficit of the user's right ear to shape sound signals received from microphone 120 to generate modulated sound signals, and supply them to speaker 108 for reproduction to the user at or within the user's right ear.


While the above-discussion assumes placement within the right ear, it should be appreciated that, if the user places hearing aid 100 on his left ear, right sensor 126 and front sensor 122 detect respective proximities to the user's head and ear, respectively. In response to the proportional signals, the controller 104 and processor 118 cooperate to configure the hearing aid 100 to operate in a left ear mode 114, modulating the audio output signal to compensate for the user's hearing deficiency in his left ear.


In general, a user's hearing deficiency in one ear may differ from that of the user's other ear. Accordingly, in a conventional set of hearing aids, sound-shaping for one hearing aid may be different than that for the other. In this instance, however, the hearing aids can be picked up by the user and worn on either ear, and the hearing aid 100 automatically adapts to the correct operating mode. If the hearing aid is placed in the right ear, sound shaping algorithms designed to compensate for the hearing deficiency in the right ear are applied, and vice versa.


In the illustrated embodiment, it is assumed that the plurality of operating modes 130 include sound shaping instructions associated with both the left and the right ear (identified as left ear mode 114 and right ear mode 112). Further, it should be appreciated that the left ear mode 114 may include multiple sound-shaping instructions for different operating environments. Similarly, the right ear mode 112 may include multiple sound shaping instructions for different operating environments. In a particular example, after determining the left/right ear position of hearing aid 100, processor 118 can be configured to select one of a plurality of sound-shaping algorithms associated with the operating mode (e.g., right ear mode 114) based on detected sound signals from microphone 120. In one instance, processor 118 detects a noisy background environment (such as a crowd, bar, etc.) and selects and applies sound-shaping instructions to filter out such background noise.


In a second example, hearing aid 100 is in an on state when the user removes it from his ear. In this example, front sensor 122, left sensor 124, and/or right sensor 126 detect respective changes in the proximity, when the hearing aid is removed, and produce proportional signals corresponding to the changes. Because at least two sensors detect a change in the proximity and produce such proportional signals indicating hearing aid 100 is no longer proximate to the user's ear, controller 104 provides a control signal to processor 118 to turn off sound processing and/or to enter into a low-power mode, because hearing aid 100 is no longer being worn by the user.


In an alternative embodiment, in response to controller 104 providing the control signal, processor 118 places hearing aid 100 in a sleep mode, a recharge mode, an idle mode, or another reduced power mode. In such a mode, processor 118 deactivates or reduces power to some of the circuitry within casing 102. In particular, processor 118 shuts itself down and leaves controller 104 active to wake up the processor 118 in response to detecting a proximity using front sensor 122. In an example, controller 104 can be implemented as a low-power logic circuit that consumes less power than processor 118. Thus, turning off the processor 118 and other circuitry, while allowing controller 104 to selectively control front sensor 122, left sensor 124, and right sensor 126 to monitor for proximity, conserves battery power, extending the battery life of hearing aid 100.


By providing a hearing aid that is configured to operate and fit on either of the user's ears, overall manufacturing, programming, and development costs are reduced because a single casing and associated circuitry can be produced that can fit interchangeably. Further, the interchangeability of the casing 102 improves the flexibility and ease of use for the user, making it easier for the user to adapt to wearing the hearing aid. At the same time, replacing the manual switch with an automatic on/off system improves reliability, reduces wear and tear, and improves usability for hearing aid 100.


In another example, left and right sensors 124 and 126 can also be positioned on casing 102 at a location that facilitates detection of the proximity of a phone in order to automatically detect the presence of the phone and to control the processor 118 to enter a phone mode. The phone mode may involve utilization of a Bluetooth transceiver, a telecoil or other circuitry within the hearing aid 102 for direct reception of the audio signal, instead of audible transmission by a speaker of the phone for capture by the microphone 120. Alternatively, the audio processing by processor 118 may be adjusted to increase volume, etc. If the user is wearing hearing aid 100 on their left ear, then right sensor 126 and front sensor 122 detect proximity of casing 102 relative to the user's head and ear, respectively. When a phone is placed against the user's left ear, left sensor 124 detects a proximity of the user's ear relative to the phone. In this instance, all three sensors 122, 124, and 126 detect a proximity, and controller 104 generates a control signal, which causes processor 118 to enter a phone mode. In one example, controller 104 controls sensors 122, 124, and 126 to detect proximity substantially simultaneously. In another example, controller 104 polls sensors 122, 124, and 126 sequentially. In still another example, controller 104 may control sensors 122, 124, and 126 to operate continuously, periodically, aperiodically, or in response to a triggering event.


In one instance, hearing aid 100 turns on when front sensor 122 and either left sensor 124 or right sensor 126 detect a proximity, and turns off at any other time. Thus, the hearing aid 100 can be configured to be responsive to proximities detected by at least two of the sensors 122, 124, and 126.


In another example, hearing aid 100 can be configured to change its state in response to a change in proximity detected by one of the sensors 122, 124, and 126. In one such example, front sensor 122 detects a front proximity, and hearing aid 100 is activated in response thereto. For such turn-on state functionality, front sensor 122 works well because of its location on the curved portion of the front side of casing 102, which is designed to rest on either the right side 212 or the left side 214, helping to prevent false positives, such as a false positive due to a counter top or table surface. For example, when a user positions hearing aid 100 on the ear, the front side of casing 102 comes into contact with the curvature of the back of the user's ear, and front sensor 122 detects the proximity of the user's head. However, when hearing aid 100 is placed on the table or desk for storage over night, casing 102 tends to rest on either the left side 214 or the right side 212 such that front sensor 122 is directed substantially parallel to a surface of the table. Accordingly, front sensor 122 does not detect a proximity of the surface on which it rests or at least produces a proximity signal that falls below a pre-determined threshold proximity. In this example, left sensor 124 and right sensor 126 may also be utilized to determine the ear to which the user has attached hearing aid 100 to help determine the operating mode of hearing aid 100.


In another instance, controller 104 may be configured to turn on after front sensor 122 detects proximity of an object (such as the back of the ear) for a specific period of time, an on-time, or at a specific distance, an on-distance. Alternatively, controller 104 may also be configured to turn hearing aid 100 off after front sensor 122 does not detect proximity of the object for a specific period of time, the off-time, or at a specific distance, the off-distance. For example, the hearing aid user may be running or jumping and hearing aid 100 may bounce on their head causing front sensor 122 to detect proximity at varying distance and/or lose the proximity signal altogether. In this instance, the off-time and off-distance can be set such that controller 104 does not turn off hearing aid 100 as front sensor 122 switches between detecting a proximity and not detecting a proximity. Also the on-time and the off-time may vary from each other. For example, the off-time may be greater than the on-time so that controller 104 waits longer before turning hearing aid 100 off than when turning hearing aid 100 on. Similarly, the off-distance may vary from the on-distance. For example, the on-distance may be set at a very close proximity, so that controller 104 only turns hearing aid 100 on when it is actually placed on an ear which the front surface is shaped to fit against and the off-distance may be set at a much larger distance, such that controller 104 only turns hearing aid 100 off when hearing aid 100 has been fully removed from the user's ear. It should be understood that an on-time, off-time, on-distance, and off-distance can be set for right and left sensor 124 and 126 as well as for front sensor 122, such that controller 104 may change the state and/or mode of hearing aid 100 based on the time and distance for which the front, left, and right sensors 122, 124, and 126 detect proximities.


While hearing aid 100 depicts front sensor 122, left sensor 124, and right sensor 126, any number and combination of sensors may be used. Further, while hearing aid 100 is described as a behind-the-ear type of hearing aid casing 102, other types of hearing aids may be used that employ sensors 122, 124, and 126 to detect the state and/or mode of the hearing aid. An example of a behind-the-ear hearing aid compatible with automatic mode/state change is described below with respect to FIG. 2.



FIG. 2 is a perspective view of a user's ear and a partial cross-sectional view 200 of hearing aid 100 in FIG. 1, including an in-ear sensor 228 for detecting proximity. Casing 102 of hearing aid 100 includes a right side 212, left side 214, and a front side 216, having corresponding right sensor 126, left sensor 124 (depicted in phantom because it is on the other side of casing 102), and front sensor 122, respectively. Hearing aid 100 includes an ear tube 204 connected to casing 102 on one end and to an ear bud 202 at another end. In one instance, ear tube 204 can be configured to transport acoustic signals from a speaker within casing 102 to ear bud 202. In another instance, ear tube 204 can include wires to carry electrical signals from a digital-to-analog converter within casing 102 to a speaker in ear bud 202.


Ear bud 202 includes an in-ear sensor 228, which is communicatively coupled to processor 118 within casing 102 via a wire (not shown) that extends through tube 204. In-ear sensor 228 is similar to sensors 122, 124, and 126 of FIG. 1 and is utilized to determine when the user has completed the insertion of ear bud 202 into the ear canal of ear 210 by detecting proximity of in-ear sensor 228 relative to the user's ear canal.


In this embodiment, hearing aid 100 fits on the user's right ear 210. Front sensor 122 and left sensor 124 detect the proximity of the user's ear and head, respectively, and controller 104 causes hearing aid 200 to turn on in response to detecting the proximity, and to enter the right ear mode based on the proximity signals from left sensor 124. In this example, controller 104 activates processor 118, which does not activate the speaker in ear bud 202 until in-ear sensor 228 detects proximity of the user's ear canal. When ear bud 202 is positioned within the ear canal of ear 210, in-ear sensor 228 generates a signal indicating proximity of the ear canal relative to the ear bud 202. Controller 104 causes hearing aid 100 to change to turn on, and processor 118 causes hearing aid 100 to enter the right ear mode. Further, processor 118 begins loading sound shaping instructions corresponding to right ear mode before activating speaker 108. By delaying turning on the speaker, processor 118 reduces noise caused by mechanical vibration of the speaker 108 and feedback during the insertion process.



FIGS. 1 and 2 depict a hearing aid including sensors for automating state and mode changes in a behind-the-ear hearing aid design. Other types of hearing aid designs may also utilize such proximity sensors for automatic state changes. While the above-discussion has focused on the circuitry that is configurable to provide the state change and mode change functionality, other circuits and structures may be used to implement the hearing aid with automatic mode change functionality. An example of one possible method of activating a hearing aid is described below with respect to FIG. 3.



FIG. 3 is a flow diagram of an embodiment of a method 300 of activating a hearing aid in response to detecting proximity of a user's ear. At 302, controller 104 samples sensors to check for proximities. In one example, controller 104 applies a voltage to each of the sensors substantially simultaneously and monitors the return signals. In another example, controller 104 applies a voltage to each of the sensors sequentially and monitors the return signals. In still another example, controller applies a voltage to each of the sensors and monitors a current drawn by the sensor in response thereto. In an alternative example, the controller 104 applies a current and monitors a voltage.


Proceeding to 304, logic determines whether a front proximity (represented by a signal from the front sensor 122) exceeds a threshold proximity. The front proximity is represented by a signal that is proportional to proximity of an object relative to the front sensor 122. If the front proximity does not exceed the threshold proximity, the method 300 proceeds to 306 and the hearing aid enters or remains in the off state. If, at 304, the logic determines that the front proximity exceeds the threshold proximity, the method 300 proceeds to 308, and the controller 104 compares the proximity from the left and right sensors to a left/right proximity threshold. The left/right proximity may differ from the proximity threshold used to determine whether the front sensor 122 is proximate to the user's ear. If neither the right nor the left sensor proximity exceeds the left/right threshold, the method 300 proceeds to 306 and the hearing aid enters or remains in the off state. However, if either the right or the left sensor proximity exceeds the left/right threshold at 308, the method 300 proceeds to 310 and the hearing aid enters an on state. In one example, controller 104 generates a signal to activate processor 118, which activates other circuitry and which processes the left/right proximity signals to determine whether the hearing aid is in a left ear mode or a right ear mode. Processor 118 then loads the appropriate hearing aid profile for the left ear or the right ear for subsequently modulating sounds to compensate for the user's hearing deficiency.


Advancing to 312, processor 118 or controller 104 (depending on whether the in-ear sensor is connected to controller 104 or processor 118, for example, through an analog-to-digital converter) compares a proximity signal of in-ear sensor 228 to an in-ear threshold. If, at 312, the in-ear sensor proximity does not exceed the in-ear threshold, the method 300 proceeds to 314 and the controller 104 waits for a period of time. After the period of time elapses, the method 300 then returns to 312 and controller 104 compares the proximity from the in-ear sensor to the in-ear threshold. At 312, when the in-ear sensor proximity exceeds the in-ear threshold, the method advances to 316, and processor 118 activates the speaker 108. After activation of the speaker 108, the hearing aid 100 is in an on-state and is configured for the appropriate mode based on the detected ear.


In the above-discussion, it is assumed that the front sensor alone serves to determine the on-state of the hearing aid. However, it should be appreciated that all three sensors (front, right, and left) may be sampled to determine the on-state of the hearing aid. Further, once the hearing aid is configured and in an on-state, further automatic mode adjustments may be applied. For example, a sensor that is not pointing toward the back of the user's ear or toward the user's head may be free to detect proximity of a phone or other instrument. In some embodiments, controller 104 and processor 118 may utilize such detected proximity to adjust the operating mode of hearing aid 100.


Further, it should be appreciated that, during normal operation and as the user moves around, the hearing aid 100 may shift from time to time, for example, during rigorous exercise. To avoid undesired mode/state changes during such transient movements, the controller 104 may utilize ratios of proximities. Such ratios assume that the shift of two proximities will be somewhat proportional and/or that a difference between a measured ratio and a previously measured ratio will remain below a threshold level unless the hearing aid 100 is removed from the ear. Alternatively, the proximities may be averaged over a time window to prevent transient shifts from affecting the state/mode of the hearing aid 100.


While FIG. 3 shows one possible method of using sensors to control state changes such as on and off, it is also possible to determine the operating mode of the hearing aid, such as right ear mode, left ear mode, phone mode, or other modes using proximity sensors. One example of a method of using the sensors to determine and control mode changes is described below with respect to FIG. 4.



FIG. 4 is a flow diagram of an embodiment of a method 400 of determining an operating mode of a hearing aid in response to detecting proximity. At 402, controller 104 samples the proximity sensors to detect proximities. Proceeding to 404, if front sensor proximity does not exceed a front threshold, the method 400 proceeds to 406 and the controller 104 controls hearing aid 100 to turn off or to enter the off state. If the front sensor proximity exceeds the front threshold at 404, the method 400 proceeds to 408 and the controller 104 compares a left sensor proximity to a left threshold. At 408, if the left sensor proximity exceeds the threshold, the method 400 advances to 410 and the controller 104 controls processor 118 of hearing aid 100 to select a right ear mode. If, at 408, the left sensor proximity does not exceed the left threshold, the method 400 advances to 412.


At 412, if the right sensor proximity exceeds a right threshold, controller 104 controls processor 118 of hearing aid 100 to select a left ear mode. Otherwise, the method 400 proceeds to 406 and the hearing aid is turned off (or remains in an off-state). Alternatively, rather than proceeding to 406, controller 104 may maintain hearing aid 100 in a hold state until either the proximity of front sensor 122 or the proximities of left sensor 124 or right sensor 126 changes.


Methods 300 and 400 describe two of many possible methods of utilizing proximity sensors to trigger state/mode changes in a hearing aid. It should be understood that the order in which the blocks of methods 300 and 400 are performed may vary. For example, comparison of the left/right proximities at 408 and 412 may be reversed in terms of their order in method 400. Additionally it is also understood that some blocks of methods 300 and 400 may be combined or removed. For example, comparisons of left and right proximities at 408 and 412, respectively, may be combined. Further, with respect to the methods 300 and 400, new blocks can be added without departing from the scope of the disclosure.


In conjunction with the embodiments described above, a hearing aid is disclosed that includes a casing that is symmetrical and designed to fit either of the user's ears so that the user can position the hearing aid on either ear, as desired. The hearing aid includes multiple proximity sensors and a controller configured to determine proximity of the user (the user's ear and head) to the hearing aid. The controller cooperates with a processor of the hearing aid to turn on or turn off components based on the proximities and to select an operating mode based on the proximities. By providing a hearing aid with proximity sensors configured to select modes and determine state changes, the hearing aid can be designed to be interchangeable between the user's left and right ear and to automatically select the operating mode based on the selected ear. Thus, the hearing aid increases usability and reduces manufacturing and design costs. Additionally, by replacing mechanical switches with proximity sensors, the hearing aid can be sealed in from the elements, reducing exposure to dust and water and increasing operating life of the hearing aid.


Although the present invention has been described with reference to preferred embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the scope of the invention.

Claims
  • 1. A method of operating a listening device configured to be worn in a user's ear, the method comprising: detecting a proximity of a user's head to a casing of a listening device via a sensor carried by the casing; andautomatically switching the listening device, via at least one processor at the listening device, from a first operating mode associated with detecting the proximity of a user's head to the casing of the listening device via the sensor, to a second operating mode, wherein the switching is in response to the listening device detecting a proximity of an electronic device, wherein the second operating mode is a direct input mode that includes wirelessly receiving an audio signal from the electronic device, and wherein the audio signal is representative of audio to be output by the listening device.
  • 2. The method of claim 1 wherein the electronic device is a mobile phone, and wherein the listening device is a hearing aid.
  • 3. The method of claim 1 wherein operating the listening device in the second operating mode comprises receiving the audio signal via a Bluetooth transceiver.
  • 4. The method of claim 1, further comprising: detecting an amount of background noise of an environment of the user; andapplying a filter to the audio signal, wherein the filter comprises a set of sound-shaping instructions configured to attenuate at least a portion of the detected amount of background noise in the audio signal.
  • 5. The method of claim 4 wherein applying the filter further includes selecting the set of sound-shaping instructions from a plurality of sets of sound-shaping instructions based on the detected amount of background noise.
  • 6. The method of claim 1 wherein detecting the proximity of the electronic device is performed using a second sensor in the casing and comprises: receiving, from the second sensor, a signal indicative of a distance between the electronic device and the casing; andcomparing the signal to a threshold proximity.
  • 7. The method of claim 1 wherein detecting the proximity of the electronic device is performed using a second sensor in the casing comprises: receiving a first proximity signal and a second proximity signal from the second sensor;computing a ratio of the first and second proximity signals; andcomparing the computed ratio to a predetermined ratio of the first and second proximity signals.
  • 8. The method of claim 7, wherein the switching from the first operating mode to the second operating mode occurs in response to a difference of the computed ratio and the predetermined ratio exceeding a threshold level.
  • 9. A system comprising: a mobile device; anda device configured to be worn in an ear of a user communicable with the mobile device, the device configured to be worn in the ear of the user comprising: a speaker and at least one microphone;a plurality of sensors including at least one sensor configured to determine a proximity to the ear of the user; anda processor coupled with the plurality of sensors; anda memory coupled with the processor, the memory storing instructions that when executed by the processor, cause the processor to perform operations including: determining, via the at least one sensor configured to determine a proximity to the ear of the user that the device should be operating in a first operating mode, andchanging an operating mode of the device configured to be worn in the ear of the user from the first operating mode to a second operating mode in response to the device detecting a proximity of the mobile device within a proximity threshold, wherein the second operating mode is a direct input mode that includes wirelessly receiving an audio signal from the mobile device, and wherein the audio signal is representative of audio to be output by the device.
  • 10. The system of claim 9, wherein the second operating mode of the device configured to be worn in the ear of a user is a phone mode, and the first operating mode of the device configured to be worn in the ear of a user is one or more of a sleep mode, a normal mode, a low power mode, a right ear mode, a left ear mode, and combinations thereof.
  • 11. The system of claim 9, wherein the device configured to be worn in the ear of the user is a right ear device, and a second device configured to be worn an ear of the user is a left ear device.
  • 12. The system of claim 11, wherein the instructions further include determining proximity relative to the right ear device and the left ear device.
  • 13. The system of claim 12, wherein when the instructions further comprise changing the operation mode of the right ear device to a phone mode when the proximity relative to the right ear device is below the predetermined threshold.
  • 14. The system of claim 13, wherein the phone mode further adjusts sound output from the speaker for the right ear device.
  • 15. The system of claim 12, wherein when the instructions further comprise changing the operation mode of the left ear device to a phone mode when the proximity relative to the left ear device is below the predetermined threshold.
  • 16. The system of claim 15, wherein the phone mode further adjusts sound output from the speaker for the right ear device.
  • 17. A mobile device comprising: a processor operable to communicate with a device configured to be worn in an ear of a user;a memory coupled with the processor, wherein the memory includes instructions that, when executed by the processor, cause the processor to perform operations including: determine a proximity to the device configured to be worn in the ear of the user, wherein the device includes a plurality of sensors carried by a casing, a first of the plurality of sensors capable of determining a proximity to the mobile device and a second of the plurality of sensors capable of determining a proximity to a user's head; andcause the device configured to be worn in the ear of the user to switch from a first operating mode to a second operating mode when the proximity is below a predetermined threshold.
  • 18. The mobile device of claim 17, wherein the device configured to be work in the ear of the user is a left ear device.
  • 19. The mobile device of claim 18, wherein the second operating mode of the left ear device is a phone mode.
  • 20. The mobile device of claim 19, further comprising a speaker, wherein the instructions further cause the processor to: stop use of the speaker when the left ear device is in phone mode, anddirect all sound through the left ear device.
CROSS REFERENCE TO RELATED APPLICATION(S)

This application is a divisional of Ser. No. 13/935,744, filed Jul. 5, 2013 (now U.S. Pat. No. 9,462,397), which is a continuation of, and claims priority to U.S. patent application Ser. No. 13/244,260, entitled “LISTENING DEVICE WITH AUTOMATIC MODE CHANGE CAPABILITIES,” filed on Sep. 23, 2011 (now U.S. Pat. No. 8,515,110), which is a nonprovisional application of and claims priority to U.S. Provisional Patent Application No. 61/388,349 filed on Sep. 30, 2010 and entitled “LISTENING DEVICE WITH AUTO MODE CHANGE CAPABILITIES.” The foregoing patent and applications are incorporated herein by reference in their entireties.

US Referenced Citations (126)
Number Name Date Kind
3350643 Webb Oct 1967 A
4845755 Busch et al. Jul 1989 A
4947432 Topholm Aug 1990 A
4972487 Mangold et al. Nov 1990 A
5107473 Fuji et al. Apr 1992 A
5130665 Walden Jul 1992 A
5148153 Haymond Sep 1992 A
5303306 Brillhart et al. Apr 1994 A
5450494 Okubo et al. Sep 1995 A
5524056 Killion et al. Jun 1996 A
5524150 Sauer Jun 1996 A
5563951 Wang et al. Oct 1996 A
5608803 Magotra et al. Mar 1997 A
5651073 Isu et al. Jul 1997 A
5661812 Scofield et al. Aug 1997 A
5666426 Helms Sep 1997 A
5692058 Eggers et al. Nov 1997 A
5721783 Anderson Feb 1998 A
5727070 Coninx Mar 1998 A
5734731 Marx Mar 1998 A
5734964 Fishman et al. Mar 1998 A
5734976 Bartschi et al. Mar 1998 A
5764775 Kim Jun 1998 A
5768397 Fazio Jun 1998 A
5802183 Scheller et al. Sep 1998 A
5812598 Sharma et al. Sep 1998 A
5824022 Zilberman et al. Oct 1998 A
5867581 Obara Feb 1999 A
5873126 Singh et al. Feb 1999 A
6078675 Bowen-Nielsen et al. Jun 2000 A
6151400 Seligman Nov 2000 A
6265989 Taylor Jul 2001 B1
6330339 Ishige et al. Dec 2001 B1
6532294 Rudell et al. Mar 2003 B1
6694034 Julstrom et al. Feb 2004 B2
6741712 Bisgaard May 2004 B2
6794852 Tran et al. Sep 2004 B2
6920229 Boesen et al. Jul 2005 B2
7010133 Chalupper et al. Mar 2006 B2
7050907 Janky et al. May 2006 B1
7167571 Bantz et al. Jan 2007 B2
7301305 Tran et al. Nov 2007 B2
7324650 Fischer et al. Jan 2008 B2
7336227 Durst et al. Feb 2008 B2
7397217 Van Brocklin et al. Jul 2008 B2
7446505 Paul et al. Nov 2008 B2
7451256 Hagen et al. Nov 2008 B2
7499686 Sinclair et al. Mar 2009 B2
7519194 Niederdrank et al. Apr 2009 B2
7529545 Rader et al. May 2009 B2
7561708 Röhrlein et al. Jul 2009 B2
7593822 Stewart Sep 2009 B2
7610035 Van Bosch et al. Oct 2009 B2
7640101 Pair et al. Dec 2009 B2
7676335 Ahmed et al. Mar 2010 B2
7715576 Ribic et al. May 2010 B2
7778432 Larsen et al. Aug 2010 B2
7787647 Hagen et al. Aug 2010 B2
7826631 Fischer et al. Nov 2010 B2
7853028 Fischer et al. Dec 2010 B2
7929722 Shridhar et al. Apr 2011 B2
7933419 Roeck et al. Apr 2011 B2
8170884 Vaudrey et al. May 2012 B2
8265315 Sørensen et al. Sep 2012 B2
8379871 Michael et al. Feb 2013 B2
8457335 Imamura et al. Jun 2013 B2
8515110 Neumeyer et al. Aug 2013 B2
8526649 Foo et al. Sep 2013 B2
8611570 Neumeyer et al. Dec 2013 B2
8649538 Apfel et al. Feb 2014 B2
8654999 Mindlin, II et al. Feb 2014 B2
8761421 Apfel et al. Jun 2014 B2
8787603 Fichtl et al. Jul 2014 B2
8810392 Teller et al. Aug 2014 B1
9071917 Apfel Jun 2015 B2
9167339 Knox et al. Oct 2015 B2
9191756 Neumeyer et al. Nov 2015 B2
9462397 Neumeyer et al. Oct 2016 B2
20020070852 Trauner et al. Jun 2002 A1
20030008659 Waters et al. Jan 2003 A1
20030045283 Hagedoorn Mar 2003 A1
20030055537 Odinak et al. Mar 2003 A1
20030059076 Martin Mar 2003 A1
20030069704 Bean Apr 2003 A1
20030215105 Sacha Nov 2003 A1
20040059446 Goldberg et al. Mar 2004 A1
20040199146 Rogers et al. Oct 2004 A1
20050036637 Janssen Feb 2005 A1
20050238190 Rohrlein Oct 2005 A1
20050277994 McNamee et al. Dec 2005 A1
20050281424 Rass et al. Dec 2005 A1
20060182294 Grasbon et al. Aug 2006 A1
20060198530 Fischer et al. Sep 2006 A1
20070014423 Darbut et al. Jan 2007 A1
20070098195 Holmes May 2007 A1
20070214893 Killion et al. Sep 2007 A1
20070254728 Moallemi et al. Nov 2007 A1
20070255435 Cohen et al. Nov 2007 A1
20070274531 Camp et al. Nov 2007 A1
20080037797 Goldstein et al. Feb 2008 A1
20080136654 Toriello et al. Jun 2008 A1
20080137873 Goldstein et al. Jun 2008 A1
20080167531 McDermott et al. Jul 2008 A1
20080240477 Howard et al. Oct 2008 A1
20090074216 Bradford et al. Mar 2009 A1
20090154742 Rasmussen Jun 2009 A1
20090208024 Farver et al. Aug 2009 A1
20090262964 Havenith et al. Oct 2009 A1
20090290721 Goldstein et al. Nov 2009 A1
20100027822 Dietz Feb 2010 A1
20100054511 Wu et al. Mar 2010 A1
20100202637 Cornelisse et al. Aug 2010 A1
20100255782 Klemmensen Oct 2010 A1
20100273452 Rajann et al. Oct 2010 A1
20100296668 Lee et al. Nov 2010 A1
20110026725 Kunzle Feb 2011 A1
20110176697 Apfel et al. Jul 2011 A1
20110200215 Apfel et al. Aug 2011 A1
20110243345 Carreras et al. Oct 2011 A1
20110249836 Solum et al. Oct 2011 A1
20120082329 Neumeyer et al. Apr 2012 A1
20120130660 Neumeyer et al. May 2012 A1
20130301860 Neumeyer et al. Nov 2013 A1
20140003641 Neumeyer et al. Jan 2014 A1
20150256946 Neumeyer et al. Sep 2015 A1
20160007109 Neumeyer et al. Jan 2016 A1
Foreign Referenced Citations (9)
Number Date Country
19542961 May 1997 DE
2473664 Jan 2012 GB
1998043192 Jan 1998 WO
2006117365 Nov 2006 WO
2008071236 Jun 2008 WO
2008071236 Jun 2008 WO
2009001559 Dec 2008 WO
2010073749 Jul 2010 WO
2011159349 Dec 2011 WO
Non-Patent Literature Citations (116)
Entry
Declaration of Sayfe Kiaei Ph.D. filed in Petition for Inter Partes Review of U.S. Pat. No. 8,611,570, filed Dec. 6, 2016.
File History of U.S. Pat. No. 9,191,756, filed on Dec. 7, 2012, issued on Nov. 17, 2015.
Taylor Martin, “The Evolution of the Smartphone”, Jul. 29, 2014; Retrieved from www.pocketnow.com on Jan. 23, 2017.
File History of U.S. Pat. No. 8,654,999, filed on Apr. 12, 2011, issued on Feb. 18, 2014.
ISA Good Practice Guidance, “Good Practice Guidance for Adult Hearing Aid Fittings and Services—Background to the Document and Consultation”, Nov. 2004.
Response to May 30, 2013 Final Office Action filed Jul. 10, 2013 from U.S. Pat. No. 8,761,421 Patent Prosecution History.
Consumer Reports,—“Hear Well in a Noisy World”—Features at a glance, Jul. 2009, Consumer Reports Magazine, Retrieved from www.consumerreports.org on Nov. 18, 2016.
Prosecution History of U.S. Pat. No. 6,694,034, filed on Dec. 28, 2000, issued on Feb. 12, 2004.
Parker, Sybil P., “McGraw-Hill Dictionary of Scientific and Technical Terms”, Fifth Edition, 1974, 1994, McGraw-Hill, USA.
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 14/853,904, dated Oct. 26, 2016, 16 pages.
Berger, Elliott. “Dangerous Decibels: How Loud is Too Loud.” Web, <www.dangerousdecibels.org/education/information-center/decibel-exposure-time-guidelines/>, accessed Dec. 23, 2013, 3 pages.
Resound Alera: End User Brochure, instructional brochure, 2010, M101100-GB-10.02 Rev.A, GN ReSound Group, USA 7 pages.
International Searching Authority, International Search Report and Written Opinion, PCT Patent Application PCT/US2011/001077, dated Nov. 15, 2011, 9 pages.
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 13/007,568, dated May 30, 2013, 19 pages.
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 13/176,738, dated May 22, 2014, 11 pages.
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 13/290,269, dated May 1, 2015, 23 pages.
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 13/708,009, dated Jul. 30, 2014, 9 pages.
United States Patent and Trademark Office, Final Office Action, U.S. Appl. No. 13/935,744, dated Jun. 10, 2015, 9 pages.
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/007,568, dated Dec. 12, 2012, 19 pages.
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/176,738, dated Feb. 18, 2015, 5 pages.
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/176,738, dated Jan, 16, 2014, 13 pages.
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/176,738, dated Jul. 18, 2013, 16 pages.
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/290,269, dated Feb, 1, 2016, 28 pages.
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/290,269, dated Nov. 18, 2014, 20 pages.
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/708,009, dated Jan. 21, 2014, 7 pages.
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/935,744, dated Aug, 7, 2015, 10 pages.
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/935,744, dated Dec. 26, 2014, 6 pages.
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 13/935,744, dated Feb. 20, 2015, 10 pages.
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 13/007,568, dated Feb. 14, 2014, 5 pages.
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 13/176,738, dated Jun. 17, 2015, 9 pages.
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 13/244,260, dated May 1, 2013, 12 pages.
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 13/708,009, dated Feb. 27, 2015, 5 pages.
United States Patent and Trademark Office, Restriction Requirement, U.S. Appl. No. 13/708,009, dated Nov. 28, 2014, 5 pages.
United States Patent and Trademark Office, Restriction Requirement, U.S. Appl. No. 13/935,744, dated Oct. 10, 2014, 6 pages.
United States Patent and Trademark Office, Restriction Requirement, U.S. Appl. No. 14/719,544, dated Aug. 27, 2015, 5 pages.
United States Patent and Trademark Office, Final Office Action, U.S Appl. No. 13/290,269, dated Sep. 19, 2016, 35 pages.
United States Patent and Trademark Office, Non-Final Office Action, U.S. Appl. No. 14/719,544, dated Mar. 28, 2016, 5 pages.
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 13/935,744, dated Jun. 2, 2016, 9 pages.
United States Patent and Trademark Office, Notice of Allowance, U.S. Appl. No. 14/719,544, dated Jul. 13, 2016, 6 pages.
Petition for Inter Partes Review of U.S. Pat. No. 9,191,756, filed Jan. 27, 2017.
Declaration of Robert K. Morrow Ph.D. filed in Petition for Inter Partes Review of U.S. Pat. No. 9,191,756, filed Jan. 27, 2017.
Petition for Inter Partes Review of U.S. Pat. No. 8,654,999 filed Jan. 27, 2017.
Declaration of Les Atlas Ph.D. filed in Petition for Inter Partes Review of U.S. Pat. No. 8,654,999, filed Jan. 27, 2017.
Petition for Inter Partes Review of U.S. Pat. No. 8,761,421 filed Dec. 21, 2016.
Declaration of Robert E Morley, Jr. D.Sc. filed in Petition for Inter Partes Review of U.S. Pat. No. 8,761,421, filed Dec. 21, 2016.
Petition for Inter Partes Review of U.S. Pat. No. 7,640,101 filed Dec. 12, 2016.
Declaration of Sayfe Kiaei Ph.D. filed in Petition for Inter Partes Review of U.S. Pat. No. 7,640,101, filed Dec. 12, 2016.
Petition for Inter Partes Review of U.S. Pat. No. 8,649,538 filed Dec. 6, 2016.
Declaration of Les Atlas Ph.D. filed in Petition for Inter Partes Review of U.S. Pat. No. 8,649,538, filed Dec. 6, 2016.
Petition for Inter Partes Review of U.S. Pat. No. 8,611,570 filed Dec. 6, 2016.
Declaration of Sayfe Kiaei Ph.D. filed in Petition for Inter Partes Review of U.S. Pat. No. 8,611,570, filed Dec. 5, 2016.
Petition for Inter Partes Review of U.S. Pat. No. 6,694,034 filed Jan. 3, 2017.
Declaration of Robert E Morley, Jr. D.Sc. filed in Petition for Inter Partes Review of U.S. Pat. No. 6,694,034 filed Jan. 3, 2017.
Petition for Inter Partes Review of U.S. Pat. No. 7,929,722 filed Feb. 17, 2017.
Declaration of Les Atlas Ph.D. filed in Petition for Inter Partes Review of U.S. Pat. No. 7,929,722 filed Feb. 17, 2017.
Petition for Inter Partes Review of U.S. Pat. No. 8,170,884 filed Feb. 21, 2017.
Declaration of Sayfe Kiaei Ph.D. filed in Petition for Inter Partes Review of U.S. Pat. No. 8,170,884 filed Feb. 21, 2017.
Patent Owner's Preliminary Response Pursuant to 37 C.F.R. 42.107 filed in Petition for Inter Partes Review of U.S. Pat. No. 8,649,538 filed Apr. 5, 2017.
Decision Instituting Inter Partes Review 37 C.F.R. 42.108 entered in Petition for Inter Partes Review of U.S. Pat. No. 8,649,538 entered Jun. 29, 2017.
Declaration of Kenneth Lassesen filed in Petition for Inter Partes Review of U.S. Pat. No. 7,640,101 filed Aug. 18, 2017.
Petitioner's Motion to Submit Supplemental Information Pursuant to 37 C.F.R. § 42.123(a) filed in Petition for Inter Partes Review of U.S. Pat. No. 7,640,101 filed Aug. 18, 2017.
Patent Owner Objections to Petitioner's Supplemental Exhibits Pursuant to 37 C.F.R. § 42.64 :b)(1) filed in Petition for Inter Partes Review of U.S. Pat. No. 7,640,101 filed Aug. 2, 2017.
Patent Owner's Opposition to Petitioner's Motion to Submit Supplemental Information Under 37 C.F.R. § 42.123(a) filed in Petition for Inter Partes Review of U.S. Pat. No. 7,640,101 filed Aug. 28, 2017.
Decision Instituting Inter Partes Review 37 C.F.R. § 42.108 entered in Petition for Inter Partes Review of U.S. Pat. No. 7,640,101 entered Jun. 29, 2017.
Decision Instituting Inter Partes Review 37 C.F.R. § 42.108 entered in Petition for Inter Partes Review of U.S. Pat. No. 8,761,421 entered Jun. 29, 2017.
Patent Owner's Preliminary Response Pursuant to 37 C.F.R. § 42.107 filed in Petition for Inter Partes Review of U.S. Pat. No. 8,654,999 filed May 8, 2017.
Exhibit 2001, “Substantially Identical Portions of Petition pp. 24-31 and 44-45 and Ex. 1008 pp. 48-56 and 69-70” filed in Petition for Inter Partes Review of U.S. Pat. No. 8,654,999 filed May 8, 2017.
Patent Owner Objections to Petitioner Evidence Pursuant to 37 C.F.R. § 42.64(b)(1) filed in Petition for Inter Partes Review of U.S. Pat. No. 8,654,999 filed Aug. 10, 2017.
Patent Owner Objections to Petitioner Evidence Pursuant to 37 C.F.R. § 42.64(b)(1) filed in Petition for Inter Partes Review of U.S. Pat. No. 9,191,756 filed Aug. 17, 2017.
Decision Instituting Inter Partes Review 37 C.F.R. § 42.108 entered in Petition for Inter Partes Review of U.S. Pat. No. 9,191,756 entered Aug. 3, 2017.
Patent Owner Response filed in Petition for Inter Partes Review of U.S. Pat. No. 8,649,538 entered Sep. 29, 2017.
Expert Declaration of Clyde “Kip” M. Brown, Jr., P.E. filed in Patent Owner Response filed in Petition for Inter Partes Review of U.S. Pat. No. 8,649,538 entered Sep. 29, 2017.
CV of Clyde “Kip” M. Brown, Jr., P.E. filed in Patent Owner Response filed in Petition for Inter Partes Review of U.S. Pat. No. 8,649,538 entered Sep. 29, 2017.
Exhibit 2003—Comparison of the Petition's arguments and Dr. Atlas's declaration for certain claim limitations filed in Patent Owner Response filed in Petition for Inter Partes Review of U.S. Pat. No. 8,649,538 entered Sep. 29, 2017.
Highlighted version of Dr. Atlas's declaration filed in Patent Owner Response filed in Petition for Inter Partes Review of U.S. Pat. No. 8,649,538 entered Sep. 29, 2017.
Deposition Transcript of Dr. Atlas, Sep. 19, 2017 filed in Patent Owner Response filed in Petition for Inter Partes Review of U.S. Pat. No. 8,649,538.
File History of U.S. Pat. No. 9,191,756, filed on Dec. 7, 2012, dated Nov. 17, 2015.
American Heritage Dictionary, published in 2011, p. 1652.
Barron's Dictionary of Computer and Internet Terms, published in 2013, p. 457.
Ira Sager, “Before IPhone and Android Came Simon, the First Smartphone”, Jun. 29, 2012; Retrieved from www.bloomberg.com on Jan. 23, 2017.
Taylor Martin, “The Evolution of the Smartphone”, Jul. 28, 2014; Retrieved from www.pocketnow.com on Jan. 23, 2017.
Sangeeta Mukherjee, “Smartphone Evolution From IBM Simon to Samsung-Galaxy S3”, May 8, 2012; Retrieved from www.ibtimes.com on Jan. 23, 2017.
B. Kasoff, “A Closer Look the Evolution of the Smart Phone”, Sep. 19, 2014; Retrieved from www.blog.wipp.org on Jan. 23, 2017.
File History of U.S. Pat. No. 8,654,999, filed on Apr. 12, 2011, dated Feb. 18, 2014.
Michael Valente, “Guideline for Audiologic Management of the Adult Patient”, Oct. 30, 2006; Retrieved from http://www.audiologyonline.com/ on Dec. 14, 2016.
ISA Good Practice Guidance, “Good Practice Guidance for Adult Hearing Aid Fittings and Services—Background to be Document and Consultation”, Nov. 2004.
Gitte Keidser et al, “Variation in preferred gain with experience for hearing-aid user”, 2008, International Journal of Audiology 47:10, 621-635, retrieved from University of Washington Libraries on Jan. 4, 2017.
Harvey Dillon et al, “The trainable hearing aid: What will it do for clients and clinicians?”, The Hearing Journal 59:4, 30-36, Apr. 2006.
Non-Final Office Action dated Dec. 12, 2012 from U.S. Pat. No. 8,761,421 Patent Prosecution History.
Response to Dec. 12, 2012 Non-Final Office Action filed Mar. 1, 2013 from U.S. Pat. No. 8,761,421 Patent Prosecution History.
Final Office Action dated May 30, 2013 from U.S. Pat. No. 8,761,421 Patent Prosecution History.
Response to May 30, 2013 Final Office Action filed Jul. 19, 2013 from U.S. Pat. No. 8,761,421 Patent Prosecution History.
File History of U.S. Pat. No. 7,640,101, filed on Jun. 24, 2004, issued on Dec. 29, 2009.
Richard B. Langley, “NMEA 0183: A GPS Receiver Interface Standard”, (1995) GPS World, 54-57.
Ken Lassesen, “Creating 16-Bit and 32-Bit Screen Savers with Visual Basic” Jun. 29, 1995, Microsoft Developer Network Technology Group, Retrieved from http://msdn.microsoft.com on Oct. 20, 2007.
Prosecution History of U.S. Pat. No. 8,649,538, filed on Feb. 8, 2011, issued on Feb. 11, 2014.
Consumer Reports,—Hearing Aid Features—Features at a glance, Jul. 2009, Consumer Reports Magazine, Retrieved from www.consumerreports.org on Nov. 18, 2016.
Bernard Widrow et al, “Microphone Arrays for Hearing Aids: An Overview”, Jan. 2003, Journal of Speech Communication, 39, 139-146.
Gary P. Rodriguez et al, “Preferred Hearing Aid Response Characteristics Under Acoustic and Telecoil Coupling conditions” Nov. 1993, American Journal of Audiology, 55-59 , Retrieved from http://aja.pubs.asha.org on Apr. 13, 2016.
Non-Final Office Action dated Jun. 4, 2013 from U.S. Pat. No. 8,611,570 Patent Prosecution History.
Response to Jun. 4, 2013 Final Office Action filed Aug. 16, 2013 from U.S. Pat. No. 8,611,570 Patent Prosecution History.
Certified English Translation of WO/2009/001559, Oct. 20, 2016.
Prosecution History of U.S. Pat. No. 6,694,034, filed on Dec. 28, 2000, issued on Feb. 17, 2004.
Tooley, Michael, “Data Communications Pocket Book” 2nd Edition 1989,1992, Butterworth-Heinemann Ltd, Linacre House, Jordan Hill Oxford OX2 8DP.
Patent File History of U.S. Pat. No. 7,929,722, filed on Nov. 18, 2008, issued on Apr. 19, 2011.
Patent File History of U.S. Pat. No. 8,170,884, filed on Jan. 8, 2008, issued on May 1, 2012.
Parker, Sybil P., “McGraw-Hill Dictionary of Scientific and Technical Terms”, Fifth Edition, 1974, 1994, McGraw-Hill, USA; p. 2053.
Non-Final Office Action dated Mar. 28, 2016 from U.S. Appl. No. 14/719,544, 5 pages.
Non-Final Office Action dated Feb. 1, 2016 from U.S. Appl. No. 13/290,269, 27 pages.
Microsoft News Center, “Microsoft Launches New MSDN Online Site for Developers”, Microsoft News Center, Mar. 30, 1999, <https://news.microsoft.com/1999/03/30/microsoft-launches-new-msdn-online-site-for-developers/#YgUAosK1KlxQGx1A.97>, Retrieved Apr. 18, 2019.
Microsoft News Center, “MSDN and MSDA Support Web Sites Honored as Two of Nation's 10 Best” Microsoft News Center, Aug. 23, 1999 <https://news.microsoft.com/1999/08/23/msdn-and-msda-support-web-sites-honored-as-two-of-nations-10-best/>, Retrieved Apr. 18, 2019.
Vbforums, “Free MSDN Library for Download (from Microsoft)” VBForums (A Developer.com Site), Apr. 2003, <http://www.vbforums.com/showthread.php?241324-Free-MSDN-Library-for-Download-(from-Microsoft)>, Retrieved Apr. 18, 2019.
Dr. Jadin, Cecilia, “Folkarts Website PDF” Retrieved 2001.
Rajah, G, “Powerpoint file as screen saver” The Hindu Business Line, Jul. 2, 2003.
Dimick, Dennis, “Adobe Acrobat Captures the Web” Washington Apple Pi Journal (Nov./Dec. 1999). Retrieved Jul. 24, 2017.
“Screen-saver in Dolphin” Dolphin Smalltalk (Jul. 15, 2003). Retrieved, Jul. 24, 2017.
Related Publications (1)
Number Date Country
20170094423 A1 Mar 2017 US
Provisional Applications (1)
Number Date Country
61388349 Sep 2010 US
Divisions (1)
Number Date Country
Parent 13935744 Jul 2013 US
Child 15261801 US
Continuations (1)
Number Date Country
Parent 13244260 Sep 2011 US
Child 13935744 US