Examples described herein relate to hearing devices, and include particularly subscription-based rechargeable hearing devices.
The ear canal is generally narrow and tortuous and is approximately 26 millimeters (mm) long from the canal aperture 11 to the tympanic membrane 15 (eardrum). The lateral part 12 is referred to as the cartilaginous region due to the underlying cartilaginous tissue 16 beneath the skin. The medial part, proximal to the tympanic membrane 15, is rigid and referred to as the bony region 13 due to the underlying bone tissue 17. A characteristic first bend occurs roughly at the aperture 11 of the ear canal. A second characteristic bend occurs roughly at the bony-cartilaginous junction 8 and separates the cartilaginous region 12 and the bony region 13. The ear canal 14 is generally hidden from view (front and side) behind a backward projecting eminence known as the tragus. The ear canal is also hidden from view from the back by the presence of the pinna (also referred to as auricle). The dimensions and contours of the ear canal 14 vary significantly among individuals.
Placement of a hearing device inside the ear canal 14 is generally desirable for various electroacoustic advantages such as reduction of the acoustic occlusion effect, improved energy efficiency, reduced distortion, reduced speaker vibrations, and improved high frequency response. Canal placement may also be desirable for cosmetic reasons since the majority of the hearing impaired may prefer to wear an inconspicuous hearing device. A canal hearing device can be inserted entirely or partially inside the ear canal. In the context of this application, any hearing device inserted inside the ear canal, whether partially or completely, may be referred to as a canal hearing device. This includes what is known in the hearing aid industry as Completely In the Canal (CIC), Receiver-In-Canal, (RIC), In-The-Canal (ITC), and extended wear deep canal invisible types.
Hearing devices may include a battery, which may be disposable or rechargeable. With either disposable or rechargeable batteries, removal (e.g., for charging) or replacement of the battery may be difficult or cumbersome for some users, particularly those with impaired dexterity, due to a relatively small form factor of hearing devices. In addition, the entry cost for a hearing device may be substantially high making it cost prohibitive for a large number of potential users to purchase a hearing device. Improvements in the field of hearing devices and systems may be desirable.
A rechargeable hearing device system may include a hearing device, a charging device, and a remote server. The hearing device may include a main section and a lateral section. The main section may be positioned in the ear and may include a speaker. The lateral section may be coupled to the main section. The lateral section may incorporate a rechargeable battery cell therein. The hearing device may include memory storing identification data. A status, such as a subscription status, of the hearing device may be determined based, at least in part, on the identification data. The hearing device may receive electrical charge from the charging device based, at least in part, on the identification data. The hearing device may receive a programming signal through a programming interface. The hearing device may include wireless circuitry.
The charging device may include a charging port configured to be electrically coupled to the hearing device. The charging device may include charging circuitry to selectively provide electrical energy to the hearing device when the hearing device is coupled thereto. The charging device may be configured to provide electrical energy to the rechargeable battery cell of the hearing device upon a validation of a subscription of the hearing device. In some examples, the charging device is a computing device. In some examples, the charging device is a charging station. A software program may be configured to control the charging circuitry responsive to a determination of a valid subscription.
The charging station may include a receptacle cavity configured to receive a lateral end of the hearing device. The receptacle cavity may be configured to automatically electrically disengage the rechargeable battery cell provided within the hearing device. The rechargeable battery cell may be disengaged from the hearing device and electrically engaged to the charging station responsive to an insertion force.
The remote server may be accessible to the charging device. The remote server may be accessible through a network. The remote server may be coupled to a remote subscription database. The remote server may be configured to access and/or retrieve subscription data on the remote subscription database. The subscription data may be associated with the subscription status of the hearing device. Charging of the hearing device or a wireless service may be enabled or disabled in accordance with the subscription status.
The above and still further objectives, features, aspects and attendant advantages of the present invention will become apparent from the following detailed description of certain preferred and alternate embodiments and method of manufacture and use thereof constituting the best mode presently contemplated of practicing the invention, when taken in conjunction with the accompanying drawings, in which:
Certain details are set forth below to provide a sufficient understanding of embodiments of the invention. However, it will be appreciated by one skilled in the art that some embodiments may not include all details described. In some instances, well-known structures, hearing aid components, circuits, and controls, have not been shown in order to avoid unnecessarily obscuring the described embodiments of the invention.
The present disclosure describes examples of rechargeable hearing devices and systems which may include selectively enabled features and/or charging functionality. Certain canal hearing devices, for example hearing aids, may include conventional batteries such as zinc-air varieties, which are generally non-rechargeable, and may thus be replaced frequently by the user. Given the advanced age of the average hearing aid user and diminutive size of hearing aid batteries, it may be an inconvenient and often a frustrating task to replace the batteries due to decreased dexterity and/or impaired vision and/or generally smaller form factor of the canal hearing device. Furthermore, standard zinc-air batteries can drain prematurely due to internal discharge after removing the air-access tab, as known in the hearing aid field. Rechargeable hearing aids may be advantageous in this regard however conventional hearing aids with rechargeable batteries may be generally limited to the relatively unsightly larger devices in the form of Behind-The-Ear (BTE), In-The-Ear, and Receiver-In-The-Canal (RIC). In addition, the cost of a canal hearing device can be several thousands of dollars which may be prohibitive to many potential consumers. According to industry reports, roughly 1 in 5 hearing impaired people own a hearing device, leaving the majority without a hearing solution. The high cost of canal hearing devices may be due, in part, to the inclusion of extra features in canal hearing devices which may or may not be needed or usable by a particular individual.
Examples according to the present disclosure may provide canal hearing devices and systems, which include a rechargeable battery in a smaller form factor than some conventional and relatively larger BTE and RIC devices. Rechargeable hearing devices and systems may include functionality for selectively enabling features and/or charging the battery of the hearing device. According to some examples, canal hearing devices and systems may be configured to selectively enable charging and/or certain features of the canal hearing device in response to verification of a subscription associated with the hearing device. According to some examples, selective charging and/or enabling of features may be responsive to a validated subscription associated with the hearing device. Subscription-based models can be advantageous to defray the upfront cost ownership or use. Furthermore, a subscription-based business model may allow a consumer to subscribe to certain selected features and services, thereby eliminating costs associated with unwanted features.
The present disclosure describes examples of rechargeable hearing devices and systems which may provide functionality for selectively enabling charging and/or features of the canal hearing device. Rechargeable hearing devices and systems may include functionality for selectively enabling features and/or charging the battery of the hearing device. According to some examples, hearing devices and systems may be configured to selectively enable charging and/or certain features of the hearing device in response to verification of a status of the hearing device. According to some examples, selective charging and/or enabling of features may be responsive to a validated subscription associated with the hearing device.
A rechargeable hearing device system according to examples of the present disclosure may include, on a client side 2, a canal hearing device 1 (interchangeably referred to herein as a canal hearing device assembly or a hearing device) and a charging device 70. The charging device 70 may include a charging port. The charging device 70 may be a charging station 60 or a computing device 10. In some examples, the charging device may be configured for wirelessly charging the hearing device 1, e.g., via inductive coils provided in the charging device and the hearing device. The charging device may include functionality to selectively enable charging of the hearing device 1.
The charging station 60 adapted to supply electrical energy to the hearing device 1 upon a verification of a status of the hearing device 1. In some examples, the verification of the status may include a validation of a subscription associated with the hearing device 1. In some examples, the canal hearing device 1 is charged by coupling electrical contacts of the hearing device 1 with electrical contacts 76a and 76b of a charging station 60. In some examples, the hearing device 1 may be charged wirelessly by the charging station 60. In some examples, the charging station may be configured to selectively enable transmission of electrical energy, e.g., via the electrical contacts or wirelessly via a transmission coil, to the hearing device 1 upon verification of the status of the hearing device 1. Although examples herein relate to canal hearing devices, it will be understood that systems and methods disclosed herein may also be applicable to BTE, RIC, portable sound amplification products (PSAP), or any other type of hearing device.
In some examples, the rechargeable hearing device system may include a hearing device 1 having a main section 20, a lateral section 40, and a charging station 60. The main section 20 may include durable components, such as a microphone, a speaker 57, a wireless electronics 74, a wireless antenna 75, and sound processing circuitry. The hearing device 1 may be configured for positioning on or in the ear. The hearing device may include a memory, for example non-volatile memory. The memory may be provided in the main section or the lateral section. The memory may store identification data 82, as described herein. The lateral section 40 may incorporate a rechargeable battery cell 42 therein. In some examples, the hearing device 1 may be an integrated assembly. In some examples the hearing device 1 may include a modular main section 20 (also referred to as main module) and a modular lateral section 40 (also referred to as lateral module). The lateral module 40 may be configured for mating with the main module 20 to form a canal hearing device 1. The speaker 57 of the hearing device 1 may be configured to transmit sounds 55 into the ear canal 14 of a user 100.
The charging station 60 may be configured to provide electrical charge (also referred to herein as “electrical energy”) to the battery cell 42 within the canal hearing device assembly 1. In some examples, the charging station 60 may include a receptacle cavity for receiving part of the canal hearing device 1. The charging station 60 may include a charging port. In some examples, the charging port may be incorporated within the receptacle cavity 71 of the charging station 60 for charging of the canal hearing device 1.
The charging station 60 may include one or more electrical contacts, for example 76a and/or 76b, for establishing a direct electrical connection with one or more electrical contacts, for example 46a and/or 46b, on the exterior of the hearing device 1. In some examples, the charging station 60 may be configured to provide electrical energy wirelessly to the battery cell 42, for example by inductive coupling. That is, the charging station 60 may include an inductive coil 64 (
In some examples, the client side 2 of the rechargeable hearing device system may include, in addition to or in place of the charging station 60, a computing device 10. The computing device 10 may be a client computer, a smartphone 31, a tablet, a portable media device, or any other device capable of executing computer instructions at a client side 2. The computing device 10 includes a processor and memory for storing executable instructions. The computing device 10 may be configured to execute the instructions to perform functions as described herein. The instructions may include instructions for executing one or more software applications, e.g., client validation app 32. The computing device 10 may include communications circuitry, such as a USB interface 38 or a wireless interface (e.g., Bluetooth). In some examples, the computing device 10 may be connected to a network 85, for example the Internet, to access a remote server 80 and web services. In some examples, the computing device 10 may include a charging port for directly coupling the hearing device 1 to the computing device 10 for selectively charging and/or enabling functionality of the hearing device 1. The charging port may be implemented using a variety of communication ports, such as a USB port. Electrical contacts of the charging port for charging may be implemented using electrical contacts of the USB interface 38. The hearing device 1 may couple to the computing device 10 using the USB interface 38 for charging of the hearing device 1 in accordance with a subscription.
In some examples, the charging station 60 may include a receptacle cavity 71 to receive a lateral end of the canal hearing device 1. The receptacle cavity 71 may include features configured to constrain a movement of the hearing device 1 with respect to the charging station 60 when inserted therein. The receptacle cavity 71 may include additional features, for example a structure configured to disengage the lateral section 40 relative to the main section 20 upon insertion of the lateral section 40 into the charging station 60. In some examples, the lateral section 40 may be partially disengaged from the main section 20 to provide the canal hearing device assembly 1 in an OFF condition before and during charging. The receptacle cavity 71 may incorporate a charging port therein. The charging port may include electrical contacts 76a and 76b for transmitting electrical charge to the canal hearing device 1. The charging port may control voltage levels and temperature levels so as to optimize transmittance of electrical charge to the canal hearing device 1.
As noted above, the hearing device 1 may be modular comprising a main module 20 and a lateral module 40, for example as shown in
The lateral section 40 may include a lateral section housing 43 that is generally sized and shaped according to the battery cell 42 incorporated therein, which may, in some examples, be substantially cylindrical. In some examples, the battery cell 42 may be integrated whereby the battery cell 42 is generally non-removable from the hearing device 1. By generally non-removable it is generally implied, in the context of the present disclosure, that the integrated battery cell 42 may not be replaced frequently as in the case of primary cells. In some examples, the non-removable battery cell 42 may be partially disengaged, as shown in
The main section 20 may be coupled at its medial end 31 to an ear tip assembly 19. The ear tip assembly 19 is preferably manufactured of a flexible material, such as a polymer, and configured as a replaceable or disposable component. The ear tip assembly 19 may couple to the main section 20 by engaging with an ear tip holding tab 26 positioned generally on the medial end 31 of the main section 20.
In some examples, the lateral end of the hearing device 1 may include a handle portion 50. The handle portion may be provided on a lateral end of the main section 20 or the lateral section 40. The handle portion 50 may facilitate handling of the hearing device 1 during insertion or removal from the ear. The handle portion 50 may include a shaft 51 and a knob 52. In some examples, the handle portion 50 may include wireless electronics 74 and/or a wireless antenna 75 (collectively referred to as “wireless circuitry”). In some examples, the lateral end of the hearing device 1 may include switches 78a-c for manual activation.
In some examples, the lateral section 40 may include charging electrical contacts 46a and 46b for receiving electrical energy. The charging electrical contacts 46a and 46b may be positioned on the exterior surface of the lateral section 40, as shown in
In some examples, the lateral end of the hearing device 1 may include a communications port (not shown). The communications port may be implemented using a USB interface or any other standard so as to facilitate electrical charging and/or data communications between the charging station 60 and the hearing device 1. The hearing device 1 may include charging circuitry 77 for receiving electrical charge from a computing device 10 (e.g.,
The charging station 60 may include one or more receptacle cavities 71, each of which may be adapted for receiving the lateral end of a canal hearing device 1.
The receptacle cavity 71 of the charging station 60 may include features configured to actuate the handle portion 50, or a switch, for electrical disengagement of the battery cell 42 from the canal hearing device assembly 1. For example, the receptacle cavity 71 and features included therein may be used to switch the hearing device 1 to the OFF condition for charging as described herein.
In some examples, the charging port provided within the receptacle cavity 71 may include a thermistor element (not shown) for sensing the temperature proximate to the rechargeable battery cell 42 when the lateral end of the canal hearing device 1 is inserted within the receptacle cavity 71. The charge cycle may be continued or interrupted responsive to the temperature detected by the thermistor.
In some examples, as shown in
In some examples, the charging station 60 may include wireless electronics for wireless communications using a wireless protocol, such as Bluetooth Low Energy (BLE), Wi-Fi, and/or any other wireless protocol. The wireless electronics may transmit programming signals to the canal hearing device 1. The charging station 60 may be communicatively coupled to a wireless router 72, or any other type of device to access a network 85, for example the Internet, using Wi-Fi or Bluetooth.
In some examples, the charging device (e.g., charging station 60, computing device 10) may be communicatively coupled (e.g., via the network 85) to a remote server 80. The remote server 80 may be communicatively coupled to a storage device 87 comprising status verification data (e.g., subscription data 83). The remote server 80 may be programmed to execute software for performing functions described herein. For example, the remote server 80 may be configured to execute a remote validation app 86 for communicating status verification data from storage device 87 and/or verifying the status of the hearing device 1. The status of the hearing device 1 may be a subscription status, which may be based on any of a variety of metrics. For example, the status may be based on a number of charge cycles that the hearing device 1 has already undergone. In some examples, the status may be based on a duration of time of charging of the hearing device 1. In some examples, the hearing device 1 and/or the charging device may comprise circuitry configured to count the charge cycles of the hearing device 1. In some examples, the hearing device 1 and/or charging device may comprise a clock or timer configured to record a duration of charging time of the hearing device 1. In some examples, the hearing device 1 and/or charging device may store a subscription credit count, for example a number charge cycles or a time duration. The hearing device 1 and/or charging device may decrement the subscription credit count based on usage by the user 100. In some examples, the remote server 80 may store the subscription credit. The computing device 10 may periodically communicate with the remote server 80 to synchronize the subscription credit count based on usage, renewals, cancellations, etc. The computing device 10 may enable or disable charging and/or other functionalities of the hearing device 1 following synchronization with the remote server 80.
In some examples, the charging station 60 or computing device 10 may receive identification data 82 from the hearing device 1. The identification data 82 may be used to verify or authenticate a subscription associated with the hearing device 1. In some examples, the charging station 60 or the computing device 10 may be coupled to a remote server 80 with access to subscription data 83 via a network 85 (e.g., the Internet), as shown in
In some examples, the computing device 10 may request access to subscription data 83 from the remote server 80. The request transmitted to the remote server 80 may include identification data 82 associated with the hearing device 1 or the user 100. In some examples, the request may be initiated upon coupling of the charging port of the charging station 60 or the computing device 10 with the hearing device 1, for example upon insertion of the hearing device 1 into the charging port of the charging station 60 or the computing device 10. In some examples, the request may be initiated in response to axial insertion (e.g., by an insertion force) of the hearing device 1 into the receptacle cavity 71, whereby electrical contact is made between the electrical contacts 46a and 46b of the hearing device and the electrical contacts 76a and 76b of the hearing device 1. In some examples, the request may be initiated upon coupling the hearing device 1 to the computing device 10 using a charging cable, for example a standard connection USB cable. In response to the request, the computing device 10 may receive subscription data 83 or a subscription validation from the remote server 80. When receiving subscription data 83, the computing device 10 may determine a validity of the subscription via a client subscription validation application 30. In some examples, the computing device 10 may submit validation data to the remote server 80 for starting, renewing, canceling, or resuming a subscription.
A software application for control or validation of a subscription may be executed by any device associated with the rechargeable hearing device 1, such as the computing device 10 (e.g., client subscription validation app 30), the remote server 80 (e.g., remote subscription validation app 81), or the charging station 60 (subscription validation app 66), as shown in
The remote server 80 provided on a server side 3 may be accessible via the network 85 to any devices communicatively associated with the rechargeable hearing device 1 on a client side 2, such as the charging station 60, a computing device 10 (e.g., a smartphone 31), etc. The remote server 80 may receive requests for validation of a subscription from the charging station 60 or the computing device 10 associated with the rechargeable hearing device 1 or the user 100. The remote server 80 may access subscription data 83 from a subscription database 84. The remote server 80 may deliver subscription data 83 or validation data to the computing device that requested validation of a subscription of a user 100 or potential subscriber of the hearing device 1. Subscription data 83 may include a subscription validity determination and/or may be used to validate the subscription.
In some examples, the remote server 80 on the server side 3 may host a remote subscription validation application 81. The remote subscription validation application 81 may determine subscription validity using a subscription database 84. In some examples, a subscription validation application 66 may be executed from the charging station 60. In some examples, a client subscription validation application 30 may be executed by the local computing device 10 for determining subscription validity. For example, the subscription validation application 66 may initiate the subscription validity determination upon detection of the hearing device 1 by the charging station 60. The subscription validation application 66 may request the subscription validity determination. The request may include submitting identification data 82 associated with the hearing device 1 connected to the charging station 60. It should be understood that the charging station 60 may be included as a part of a computing device 10, which may be a personal computer, a tablet, or a Smartphone. The client subscription validation application 30 executed on the computing device 10 may be in communication with the remote subscription validation application 81 for determining subscription validity. In some examples, the remote subscription validation application 81 may receive identification data 82 and determine subscription validity using the subscription database 84. The subscription validity determination may be transmitted to the client subscription validation application 30. In some examples, the client subscription validation application 30 may transmit a request for subscription data 83 to the remote subscription validation application 81. The client subscription validation application 30 may receive the subscription data 83 and make a subscription validity determination.
In some examples, charging of the hearing device 1 by the charging station 60 or the computing device 10 may be enabled upon a determination of a valid subscription. Charging may be enabled or disabled according to the subscription validity condition, for example a valid subscription condition or an invalid subscription condition.
In some examples, the software application of the computing device 10, charging station 60, and/or the remote server 80 may include functionality to automatically detect when the charging electrical contacts 46a and 46b of the canal hearing device assembly 1 are in contact with electrical contacts 76a and 76b of the charging station 60. In some examples, the detection occurs upon coupling the hearing device 1 to the computing device 10. In some examples, the detection may occur by the wireless electronics of the charging station 60 when the canal hearing device 1 is positioned proximate thereto. Upon detection of electrical contact with the canal hearing device 1 or wireless proximity, the software application may initiate a subscription validation request, and proceed with charging if the subscription is validated. The software application may initiate a subscription validation request in response to detecting a hearing device in proximity. The subscription validation request may also be initiated in response to a user 100 activating a switch 78a-c of the canal hearing device assembly 1 and/or using a wireless service of the hearing device 1.
Identification data 82 for a hearing device 1 may include a serial number, user name or identification number, or any other kind of identification data stored in the hearing device 1. In some examples, the identification data 82 may be provided by a user 100. When the subscription validation application is executed by the charging station 60 or the computing device 10, identification data 82 may be delivered to the remote server 80 by an Internet connection. In some examples, the client subscription validation application 30 may receive or determine the subscription status from the remote server 80 for charging or programming the hearing device 1.
The remote server 80 may receive the identification data 82 and query a subscription database 84 for subscription data 83 associated with the identification data 82, as shown in
In some examples, a subscription may be determined to be invalid, for example due to a non-payment or subscription expiration. When the subscription is determined to be invalid, charging circuitry 65 of the charging station 60 or charging circuitry 77 within the hearing device 1 may be disabled to prevent charging of the hearing device 1. An indicator may alert the user 100 of the invalid subscription. The indicator may be a light or a display element in the graphical user interface 90. In some examples, the charging station 60 or the hearing device 1 may allow a limited number of charging cycles upon invalid subscription determination to allow the subscriber user 100 a reasonable time period (e.g., a grace period) to remedy the cause of invalid subscription. The limited charge may charge the battery cell 42 fully one time, or only partially charge the battery cell 42. In some examples, the hearing device 1 may be reprogrammed or disabled upon a determination of an invalid subscription. The hearing device 1 may transmit a warning message via a speaker 57 of the hearing device 1 to alert the subscriber user 100 about the need to re-validate the subscription, for example by making a payment.
Examples disclosed herein offer a subscription-based charging to allow a consumer to purchase or lease a hearing device with minimal upfront payment, while ensuring adequate revenue stream for a manufacturer or a professional dispensing the hearing device.
Although examples of the invention have been described herein, it will be recognized by those skilled in the art to which the invention pertains from a consideration of the foregoing description of presently preferred and alternate embodiments and methods of fabrication and use thereof, and that variations and modifications of this exemplary embodiment and method may be made without departing from the true spirit and scope of the invention. Thus, the above-described embodiments of the invention should not be viewed as exhaustive or as limiting the invention to the precise configurations or techniques disclosed. Rather, it is intended that the invention shall be limited only by the appended claims and the rules and principles of applicable law.
This application claims the benefit under 35 U.S.C. 119 of the earlier filing date of U.S. Provisional Application No. 62/060,349 entitled “SUBSCRIPTION-CONTROLLED CHARGING OF A HEARING DEVICE,” filed Oct. 6, 2014. The aforementioned provisional application is hereby incorporated by reference in its entirety, for any purpose.
Number | Name | Date | Kind |
---|---|---|---|
4759070 | Voroba et al. | Jul 1988 | A |
5197332 | Shennib | Mar 1993 | A |
5327500 | Campbell | Jul 1994 | A |
5553152 | Newton | Sep 1996 | A |
5645074 | Shennib et al. | Jul 1997 | A |
5659621 | Newton | Aug 1997 | A |
5701348 | Shennib et al. | Dec 1997 | A |
5785661 | Shennib et al. | Jul 1998 | A |
6137889 | Shennib et al. | Oct 2000 | A |
6212283 | Fletcher et al. | Apr 2001 | B1 |
6319207 | Naidoo | Nov 2001 | B1 |
6359993 | Brimhall | Mar 2002 | B2 |
6367578 | Shoemaker | Apr 2002 | B1 |
6379314 | Horn | Apr 2002 | B1 |
6382346 | Brimhall et al. | May 2002 | B2 |
6428485 | Rho | Aug 2002 | B1 |
6447461 | Eldon | Sep 2002 | B1 |
6473513 | Shennib et al. | Oct 2002 | B1 |
6522988 | Hou | Feb 2003 | B1 |
6546108 | Shennib et al. | Apr 2003 | B1 |
6674862 | Magilen | Jan 2004 | B1 |
6724902 | Shennib et al. | Apr 2004 | B1 |
6816601 | Lin et al. | Nov 2004 | B2 |
6840908 | Edwards et al. | Jan 2005 | B2 |
6937735 | DeRoo et al. | Aug 2005 | B2 |
6940988 | Shennib et al. | Sep 2005 | B1 |
6978155 | Berg | Dec 2005 | B2 |
7010137 | Leedom et al. | Mar 2006 | B1 |
7016511 | Shennib | Mar 2006 | B1 |
7037274 | Thoraton et al. | May 2006 | B2 |
7113611 | Leedom et al. | Sep 2006 | B2 |
7215789 | Shennib et al. | May 2007 | B2 |
7221769 | Jorgensen | May 2007 | B1 |
7260232 | Shennib | Aug 2007 | B2 |
7298857 | Shennib et al. | Nov 2007 | B2 |
7310426 | Shennib et al. | Dec 2007 | B2 |
7321663 | Olsen | Jan 2008 | B2 |
7330101 | Sekura | Feb 2008 | B2 |
7403629 | Aceti et al. | Jul 2008 | B1 |
7424123 | Shennib et al. | Sep 2008 | B2 |
7424124 | Shennib et al. | Sep 2008 | B2 |
7580537 | Urso et al. | Aug 2009 | B2 |
7664282 | Urso et al. | Feb 2010 | B2 |
7854704 | Givens et al. | Dec 2010 | B2 |
7945065 | Menzl et al. | May 2011 | B2 |
8073170 | Kondo et al. | Dec 2011 | B2 |
8077890 | Schumaier | Dec 2011 | B2 |
8155361 | Schindler | Apr 2012 | B2 |
8184842 | Howard et al. | May 2012 | B2 |
8243972 | Latzel | Aug 2012 | B2 |
8284968 | Schumaier | Oct 2012 | B2 |
8287462 | Givens et al. | Oct 2012 | B2 |
8340335 | Shennib | Dec 2012 | B1 |
8379871 | Michael et al. | Feb 2013 | B2 |
8396237 | Schumaier | Mar 2013 | B2 |
8447042 | Gurin | May 2013 | B2 |
8467556 | Shennib et al. | Jun 2013 | B2 |
8571247 | Oezer | Oct 2013 | B1 |
8718306 | Gommel et al. | May 2014 | B2 |
8767986 | Fabry | Jul 2014 | B1 |
8798301 | Shennib | Aug 2014 | B2 |
8855345 | Shennib et al. | Oct 2014 | B2 |
9060233 | Shennib et al. | Jun 2015 | B2 |
9559544 | Jakubowski | Jan 2017 | B2 |
9769577 | Shennib | Sep 2017 | B2 |
9805590 | Shennib | Oct 2017 | B2 |
20010008560 | Stonikas et al. | Jul 2001 | A1 |
20020027996 | Leedom et al. | Mar 2002 | A1 |
20020085728 | Shennib et al. | Jul 2002 | A1 |
20030007647 | Nielsen et al. | Jan 2003 | A1 |
20030137277 | Mori | Jul 2003 | A1 |
20040138723 | Malick et al. | Jul 2004 | A1 |
20040165742 | Shennib et al. | Aug 2004 | A1 |
20050190938 | Shennib et al. | Sep 2005 | A1 |
20050245991 | Faltys et al. | Nov 2005 | A1 |
20050249370 | Shennib et al. | Nov 2005 | A1 |
20050259840 | Gable et al. | Nov 2005 | A1 |
20050283263 | Eaton | Dec 2005 | A1 |
20060210104 | Shennib et al. | Sep 2006 | A1 |
20060291683 | Urso et al. | Dec 2006 | A1 |
20070019834 | Nielson | Jan 2007 | A1 |
20070076909 | Roeck et al. | Apr 2007 | A1 |
20070127757 | Darbut et al. | Jun 2007 | A2 |
20070195966 | Fink | Aug 2007 | A1 |
20070255435 | Cohen et al. | Nov 2007 | A1 |
20080240452 | Burrows et al. | Oct 2008 | A1 |
20080273726 | Yoo et al. | Nov 2008 | A1 |
20100027824 | Atamaniuk et al. | Feb 2010 | A1 |
20100040250 | Gebert | Feb 2010 | A1 |
20100119094 | Sjursen et al. | May 2010 | A1 |
20100145411 | Spitzer | Jun 2010 | A1 |
20100201513 | Vorenkamp | Aug 2010 | A1 |
20100232612 | Basseas et al. | Sep 2010 | A1 |
20100239112 | Howard et al. | Sep 2010 | A1 |
20100254554 | Fusakawa et al. | Oct 2010 | A1 |
20100284556 | Young | Nov 2010 | A1 |
20110058697 | Shennib et al. | Mar 2011 | A1 |
20110188689 | Beck et al. | Aug 2011 | A1 |
20110200216 | Lee et al. | Aug 2011 | A1 |
20110206225 | Møller et al. | Aug 2011 | A1 |
20110221391 | Won | Sep 2011 | A1 |
20110293123 | Neumeyer | Dec 2011 | A1 |
20120051569 | Blamey et al. | Mar 2012 | A1 |
20120130271 | Margolis et al. | May 2012 | A1 |
20120183164 | Foo et al. | Jul 2012 | A1 |
20120183165 | Foo et al. | Jul 2012 | A1 |
20120189140 | Hughes | Jul 2012 | A1 |
20120189146 | Wuidart | Jul 2012 | A1 |
20120213393 | Foo et al. | Aug 2012 | A1 |
20120215532 | Foo et al. | Aug 2012 | A1 |
20120302859 | Keefe | Nov 2012 | A1 |
20130010406 | Stanley | Jan 2013 | A1 |
20130243209 | Zurbruegg et al. | Sep 2013 | A1 |
20130243229 | Shennib | Sep 2013 | A1 |
20130294631 | Shennib et al. | Nov 2013 | A1 |
20140003639 | Shennib et al. | Jan 2014 | A1 |
20140029777 | Jang | Jan 2014 | A1 |
20140150234 | Shennib et al. | Jun 2014 | A1 |
20140153761 | Shennib et al. | Jun 2014 | A1 |
20140153762 | Shennib et al. | Jun 2014 | A1 |
20140254843 | Shennib | Sep 2014 | A1 |
20140254844 | Shennib | Sep 2014 | A1 |
20150003651 | Han et al. | Jan 2015 | A1 |
20150023512 | Shennib | Jan 2015 | A1 |
20150023534 | Shennib | Jan 2015 | A1 |
20150139474 | Henry et al. | May 2015 | A1 |
20160049074 | Shennib | Feb 2016 | A1 |
20160057550 | Shennib | Feb 2016 | A1 |
20170180883 | Sommer et al. | Jun 2017 | A1 |
20170332183 | Shennib | Nov 2017 | A1 |
20180025627 | Shennib | Jan 2018 | A1 |
Number | Date | Country |
---|---|---|
100955033 | Apr 2010 | KR |
1020100042370 | Apr 2010 | KR |
9907182 | Feb 1999 | WO |
2010091480 | Aug 2010 | WO |
2011128462 | Oct 2011 | WO |
2011159349 | Dec 2011 | WO |
2015009564 | Jan 2015 | WO |
2015009569 | Jan 2015 | WO |
2016025826 | Feb 2016 | WO |
Entry |
---|
“Lyric User Guide”, http://www.phonak.com/content/dam/phonak/b2b/C_M_tools/Hearing_Instruments/Lyric/documents/02-gb/Userguide_Lyric_V8_GB_FINAL_WEB.pdf, Jul. 2010. |
“Methods for Calculation of the Speech Intelligibility Index”, American National Standards Institute, Jun. 6, 1997. |
“Specification for Audiometers”, American National Standards Institute, Nov. 2, 2010. |
“User Manual—2011”, AMP Personal Audio Amplifiers. |
Abrams, “A Patient-adjusted Fine-tuning Approach for Optimizing the Hearing Aid Response”, The Hearing Review, Mar. 24, 2011, 1-8. |
Asha, “Type, Degree, and Configuration of Hearing Loss”, American Speech-Language-Hearing Association; Audiology Information Series, May 2011, 1-2. |
Convery, et al., “A Self-Fitting Hearing Aid: Need and Concept”, http://tia.sagepubl.com, Dec. 4, 2011, 1-10. |
Franks, “Hearing Measurements”, National Institute for Occupational Safety and Health, Jun. 2006, 183-232. |
Kiessling, “Hearing aid fitting procedures—state-of-the-art and current issues”, Scandinavian Audiology vol. 30, Suppl 52, 2001, 57-59. |
Nhanes, “Audiometry Procedures Manual”, National Health and Nutrition Examination Survey, Jan. 2003, 1-105. |
Traynor, “Prescriptive Procedures”, www.rehab.research.va.gov/mono/ear/traynor.htm, Jan. 1999, 1-16. |
World Health Organization, , “Deafness and Hearing Loss”, www.who.int/mediacentre/factsheets/fs300/en/index.html, Feb. 2013, 1-5. |
Wu, et al., “Selective Signal Transmission to Inlaid Microcoils by Inductive Coupling”, IEEE Transducers 2003, 12th International Conference of Solid State Sensors Transducers, Boston 2003. |
U.S. Appl. No. 15/724,854, entitled “Hearing Device and Methods for Wireless Remote Control of an Appliance” filed Oct. 4, 2017. |
Number | Date | Country | |
---|---|---|---|
20160100261 A1 | Apr 2016 | US |
Number | Date | Country | |
---|---|---|---|
62060349 | Oct 2014 | US |