WIRELESS INTERFACE FOR PROGRAMMING HEARING ASSISTANCE DEVICES

TECHNICAL FIELD

This disclosure relates generally to hearing assistance devices, and more particularly to wireless communication with hearing assistance devices.

BACKGROUND

Hearing assistance devices, including hearing aids, for use in the ear, in the ear canal, completely in the canal, and behind the ear, have been developed to ameliorate the effects of hearing losses in individuals. Hearing deficiencies can range from deafness to hearing losses where the individual has impairment responding to different frequencies of sound or to being able to differentiate sounds occurring simultaneously. The hearing assistance device in its most elementary form usually provides for auditory correction through the amplification and filtering of sound provided in the environment with the intent that the individual hears better than without the amplification. Hearing assistance devices are electronic devices that provide signal processing functions such as noise reduction, amplification, and tone control. In many hearing assistance devices these and other functions can be programmably varied to fit the requirements of individual users.

One limitation of current hearing assistance device devices is that a user cannot, and current devices cannot themselves, reprogram hearing assistance device properties and communicate with a hearing assistance device to adapt to changing conditions such as the environment in which the hearing assistance device is used without the device being in wired communication with a computer. With the introduction of improved wireless communication between devices, it is now possible to reprogram or communicate with an electronic device anywhere. The introduction of wireless communication networks, specifically Local Area Networks (LAN) has expanded the options available to device manufacturers and consumers. Also, with the existence of multiple wireless communication protocols, there is a need for such an improved wireless communication with hearing assistance devices to quickly and easily adapt to existing and changing wireless communication protocols.

Therefore, there is a need in the art to provide a portable device that can communicate wirelessly, using any wireless protocol, with a hearing assistance device regardless of the physical location of a user.

SUMMARY

The present subject matter provides a means for wireless electronic communication with one or more hearing assistance devices. The system provides an interface through which parameters of a hearing assistance device can be either manually or automatically updated. For instance, the hearing assistance device can be updated with changing conditions in the environment of a user. In order for this interface to be used with any available hearing assistance device that supports wireless communication, the system must be easily adapted to support differing wireless protocols. A device is provided herein which allows for easy adaptation of the wireless protocols of a portable wireless hearing assistance device communication system.

Disclosed herein, among other things, is a device for wirelessly communicating with a hearing assistance device. According to various embodiments, the device includes a first interface for communicating with a programmer, the programmer adapted to wirelessly communicate with a computer for programming a hearing assistance device. The device also includes a second interface for wirelessly communicating with a hearing assistance device. The second interface is adapted to receive a plurality of communication modules. Each of the modules is adapted for communication with at least one specific type of hearing assistance device. The device includes a housing for the first interface, the second interface, and electrical connections between the interfaces. The housing adapted to be worn around the neck of a person wearing the hearing assistance device.

Disclosed herein, among other things, is a portable system adapted for wireless communication with one or more hearing assistance devices. According to various embodiments, the system includes a programmer for communicating with an external source for programming a hearing assistance device. The system also includes a device for wireless communication with the hearing assistance device, including an upper unit and a lower unit. The upper unit is adapted to receive a plurality of communication modules, each communication module supporting at least one communication protocol for communicating with the hearing assistance device. The lower unit has an interface for communicating with the programmer to assist in communications between the source and the hearing assistance device. The system also includes an electrical connection between the upper unit and the lower unit and a housing enclosing the upper unit, lower unit and connection. The housing is adapted to be worn by a person wearing the hearing assistance device. The housing is further adapted to provide protection from the elements for the upper unit, lower unit and connections. In an additional embodiment, the housing is adapted to physically connect to the programmer, such as a NOAHlink device, and has a connection for receiving power from the NOAHlink device. In this embodiment, the upper and lower units do not contain a power source.

Disclosed herein, among other things, is a method for wirelessly programming a hearing assistance device. A device is provided having a plurality of communication modules removably attached to an upper unit of the device. The modules support a plurality of communication protocols. A lower unit of the device communicates with a programmer. Using a communication module in the upper unit of the device, the device communicates with a hearing assistance device using at least one of the communication protocols. This communication assists in programming the hearing assistance device from an external source that communicates with the programmer.

This Summary is an overview of some of the teachings of the present application and not intended to be an exclusive or exhaustive treatment of the present subject matter. Further details about the present subject matter are found in the detailed description and appended claims. The scope of the present invention is defined by the appended claims and their legal equivalents.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments are illustrated by way of example in the figures of the accompanying drawings. Such embodiments are demonstrative and not intended to be exhaustive or exclusive representations of the present subject matter.

FIG. 1A illustrates an embodiment of a portable system adapted for wireless communication with one or more hearing assistance devices.

FIG. 1B illustrates an embodiment of a system including a wireless accessory module (WAM) device for programming a hearing assistance device.

FIG. 2A illustrates an embodiment of the upper unit that enables wireless communication with one or more hearing assistance devices.

FIG. 2B illustrates an embodiment of the upper unit showing one embodiment of a cap for technology modules.

FIG. 3 illustrates an embodiment of the technology module.

FIG. 4 illustrates an embodiment a standard connector in the upper unit for connecting the technology modules.

FIG. 5A illustrates an embodiment of battery charger that is used to power the portable system.

FIG. 5B illustrates an embodiment of battery charger with an additional charger base stabilizer.

FIG. 6 illustrates an embodiment of a WAM device with attached programmer as worn by a user.

FIG. 7 illustrates an embodiment of interconnect wiring for the WAM device showing the interface to the programmer.

FIG. 8 illustrates a flow diagram of a method for wirelessly programming a hearing assistance device, according to one embodiment.

FIG. 9 illustrates a schematic diagram of an embodiment of the interface between a WAM device and communication modules.

FIG. 10 illustrates an embodiment of a circuit board for a technology module.

FIG. 11 illustrates an embodiment of a technology module assembly.

DETAILED DESCRIPTION

The following detailed description of the present invention refers to subject matter in the accompanying drawings which show, by way of illustration, specific aspects and embodiments in which the present subject matter may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the present subject matter. References to “an”, “one”, or “various” embodiments in this disclosure are not necessarily to the same embodiment, and such references contemplate more than one embodiment. The following detailed description is demonstrative and therefore not exhaustive, and the scope of the present subject matter is defined by the appended claims and their legal equivalents.

The present subject matter includes a portable system adapted for wireless communication with one or more hearing assistance devices. The system provides a convenient way for programming and/or adjusting parameters to customize a hearing assistance device while it is worn by a user. The system provides a physical connection to a programmer at one interface. The programmer is in communication with a source, such as a computer, with an input where changes to hearing assistance device parameters can be made. According to an embodiment, the programmer includes a NOAHlink device. At a second interface, technology modules (also referred to as “communication modules”) can be plugged or inserted. Wireless communication with the hearing assistance device is initiated at this second interface. Each module supports at least one communication protocol for communicating with at least one hearing assistance device. By plugging or inserting different communication modules in the second interface, wireless communications can be established with a plurality of different hearing assistance devices manufactured by a plurality of different hearing aid manufacturers. According to various embodiments, communications modules are provided by the individual manufacturers of the hearing assistance devices, and are activated by that manufacturer's fitting software.

FIG. 1A illustrates an embodiment of a portable system adapted for wireless communication with one or more hearing assistance devices. In this embodiment, the portable system 101 includes: a lower unit 102 that provides connections and switching, an upper unit 103 to enable wireless communication with one or more hearing assistance devices, and a neck loop 104 used to conduct wires from the lower unit to the upper unit. In an embodiment, the neck loop includes a hook shaped flexible housing. The housing includes an elastomer housing, in an embodiment. The neck loop is used to place the unit on the body of a hearing-aid user. The neck loop provides rigidity while allowing for conformity to various patient body shapes. In an embodiment, the neck loop contains nine conductors plus a shield/common. The neck loop provides both the right and left channel lines to the upper unit backplane for further extensions, in various embodiments. In an embodiment, the lower unit contains switching and power management circuits as well as an LED as activity indicator. In an optional embodiment, the portable system also includes a battery charger. The portable system adapted for wireless communication with one or more hearing assistance devices is referred to herein as a wireless accessory module (WAM) system.

The lower unit 102 includes a plug in for a programmer 150. One embodiment of the programmer includes a NOAHlink device. In an embodiment, at least one 6-pin mini-DIN interface connector is used to connect to the programmer, and provides for a quick-disconnect capability. Additional holding force for the programmer is provided to supplement the pullout friction of the mini-DIM connectors in order to secure the assembly against accidental disassembly during handing, in an embodiment. In various embodiments, two six-pin mini-DIN female connectors are provided as pass-throughs in the lower unit 102, allowing the use of standard programming cables without removal of the WAM assembly from the programmer. Electrical connection between the upper and lower electronic units is accomplished by a nine-conductor shielded cable running within the conduit of neck loop 104, which allows the assembly to conform to the human anatomy by flexing at a stain relief located where the neck loop joins the lower unit. The upper unit 103 contains a microprocessor, supporting components, and a connector backplane to hold up to five technology (or communications) modules, as described. In various embodiments, additional numbers of technology modules can be held in the upper unit. In addition, a support member 165 is provided which attaches to the base of an electrical charger 160, to stabilize the charger against tipping due to additional weight and higher center of gravity caused by the WAM system. The WAM assembly obtains power from a battery in the programmer interface, requiring no additional power supply. The electrical charger 160 recharges the battery in the programmer in the depicted embodiment.

FIG. 1B illustrates an embodiment of a system including a WAM device for programming a hearing assistance device. When a hearing assistance device 180 is programmed while worn by a user, a computer 170 or other external source is used to enter the programming parameters. In various embodiments, computer 170 includes a personal computer in the form of a desk top computer, a laptop computer, a notebook computer, a hand-held computer device having a display screen, or any other computing device under the control of a program that has a display and an input device such as a mouse or keyboard. Further, computer 170 includes any processor capable of executing instructions for selecting parameters to program and/or fit a hearing assistance device. Various parameters in the hearing assistance device that can be adjusted during programming or fitting include, but are not limited to: band gain, channel gain (load and soft), output level, compression ratio, compression threshold knee points, grouped channel or band adjustments, volume control, expansion, noise management, feedback cancellation, and wind management.

The computer 170 communicates wirelessly with a programmer 162 using a designated protocol. In an embodiment, the programmer 162 includes a NOAHlink device using a standard NOAHlink protocol. The WAM device 101 includes a first interface 159 for communicating with a programmer. In the depicted embodiment, the WAM device 101 and the programmer 162 are physically connected at the interface. The WAM device 101 also includes a second interface 179 for wireless communicating with a hearing assistance device. The second interface 179 is adapted to receive a plurality of communication modules 179, each of the modules adapted for communication with at least one specific type of hearing assistance device. A housing 190 for the first interface, the second interface, and electrical connections between the interfaces, is included. The housing is adapted to be worn around the neck of a person wearing the hearing assistance device, and includes an elastomer in various embodiments. In an embodiment, the housing includes a housing for one or more printed circuit board assemblies to hold a microcontroller, switching components, power supply components, power conversion components, and additional supporting components.

The WAM device remains inactive until notified by the fitting software via the NOAHlink, allowing pass-through programming operation, in an embodiment. In various embodiments, the WAM device is an extension of the programmer, and has correspondingly the same approximate expected life cycle. The WAM device circuitry does not adversely load the programmer interface during wired programming operations. In various embodiments, the WAM device draws power from the programmer interface, requiring no additional power supply. The fitting software selects the WAM device and technology module through a discovery process, via onscreen selection, of using some combination of the two. Presence of hearing assistance devices, and the type and number (monaural or binaural) of devices is determined in software through a discovery process. The WAM system includes a physical address, according to various embodiments. WAM device and technology module firmware can be upgraded in the field via the programmer pathway. Each technology module has both a physical and wireless address, in an embodiment. The communication range of the WAM device is dependent upon the characteristics of the wireless link supported by the addressed communication module.

FIG. 2A and FIG. 2B illustrate an embodiment of the upper unit 203 that enables wireless communication with one or more hearing assistance devices. In an embodiment, the upper unit contains technology module management, electrical connections for technology modules, and housing for technology (communications) modules 205. In an embodiment, these technology modules 205 contain electric components that enable wireless communication using one or more wireless protocols. In various embodiments the wireless interface can include standard or nonstandard communications. Some examples of standard wireless interfaces include, but are not limited to, FM, AM, SSB, BLUETOOTH™, IEEE 802.11 (wireless LANs) wi-fi, 802.15 (WPANs), 802.16 (WiMAX), 802.20, and cellular protocols including, but not limited to CDMA and GSM, ZigBee, and ultra-wideband (UWB) technologies. Such protocols support radio frequency communications and some support infrared communications. It is possible that other forms of wireless interfaces can be used such as inductive, ultrasonic, optical, and others. It is understood that the standards which can be used include past and present standards. It is also contemplated that future versions of these standards and new future standards may be employed without departing from the scope of the present subject matter. In various embodiments using these interfaces, the hearing assistance device and a programmer (AKA a peripheral unit, such as the depicted NOAHlink 150 in FIG. 1A) are coupled for receiving the parameters from computer to provide programming signals to the hearing aid.

In an embodiment, the modules are identical in size and shape. In an embodiment, the modules are removable. In a further embodiment, the modules are easily removable by a user of the portable system. In an embodiment, the electrical connections for the technology modules are made through a standard connector such as (Molex SMT) with the CradleCon™ I/O Receptacle (part no. 51283-1416) in a backplane PCB for routing to a microcontroller as well as a regulator. In various embodiments, the electrical connections for the technology modules are made through any electrical connection. Any electrical connection now known or later discovered is considered within the scope of this application.

In the embodiment illustrated in FIG. 2A, five technology modules are shown. In this embodiment, the five technology modules enable the portable system to wirelessly communicate using at least five communications protocols. In an embodiment, the technology modules are covered through a click-on cap 210. The click-on cap allows access to the technology modules while protecting them against liquids and dust during use and storage. FIG. 2B illustrates one embodiment of a cap 210 for technology modules. By using removable and replaceable technology (communication) modules, the WAM device can be used to program hearing assistance devices of a variety of makes, modules and manufacturers.

FIG. 3 illustrates generally an embodiment of the technology (communications) module 305. In various embodiments, the technology modules are self contained and independent from the remaining components of the portable system. In this embodiment, the technology modules have a rectangular shape with a rounded top, and the dimensions of the technology module are 22 mm×9 mm×9 mm. Additional details of a technology module are shown in FIGS. 10 and 11. FIG. 10 illustrates an embodiment of a circuit board for a technology module. On a first side 1010 side of the circuit board, electronics for enabling communication with a hearing assistance device include hybrid circuit 1012, antenna 1014 and trimmer 1016. On a second side 1050 of the circuit board, additional components include crystal 1052 and cone 1054. FIG. 11 illustrates an embodiment of a technology module assembly. In the depicted embodiment, printed circuit board 1105 resides between first and second portions of plastic housing 1110.

The technology modules can be connected to the electrical connections for the technology modules included in the upper unit by a standard connector on the tip of the module. FIG. 4 illustrates an example of such a standard connector 400, the CradleCon™ I/O Plug, (Part No. 501091-1470). The technology module 405 is shown seated in the standard connector 400. Technology modules plug into a backplane assembly PCB on the WAM device to provide vendor-specific wireless capability, in various embodiments. In an embodiment, the technology module includes a small printed circuit board along with a connector, antenna and supporting components enclosed in a plastic housing.

FIGS. 5A and 5B illustrate additional components of the portable system. FIG. 5A illustrates an embodiment of battery charger 500 that is used to power the portable system. In this embodiment, the lower unit 502 with attached NOAHlink device 550 is fitted to stand in the battery charger 500. In this embodiment, the battery charger includes an additional foot 515 to prevent the portable system from falling over. FIG. 5B illustrates an embodiment of battery charger 500 with an additional charger base stabilizer 520. In one embodiment, the stabilizer 520 includes two additional support members 521 and a support hook 522 to provide support for the combined assembly when placed in the charger. The stabilizer permits the assembly to stand upright in the charger, so that the weight of the assembly does not cause it to tip.

FIG. 6 illustrates an embodiment of a WAM device 601 with attached programmer 650 as worn by a user 660. The device includes a lower unit 602 connected to the programmer 650 and an upper unit 603 housing replaceable technology modules adapted to communicate with a hearing assistance device 680 worn in the user's ear 690. The device further includes a flexible neck loop portion 604 with conduit and electrical connections between the lower and upper units.

FIG. 7 illustrates interconnect wiring for the WAM device 701, showing the interface to the programmer 750. One embodiment of the programmer includes a NOAHlink device, but one of skill in the art will understand that the interface can be adapted for any present or future programmer. In an embodiment, the upper unit 703 of the WAM device includes a backplane assembly printed circuit board (PCB) 710 which provides for plugging in various technology modules and interfaces with conduit and connector cables in the neck loop portion 704. These cables connect the upper unit with a second printed circuit board 712 in the lower unit 702. Lower unit 702 includes the interface with the programmer 750. This interface includes two 6-pin mini-DIN connectors, with the male connectors 714 residing on the lower unit and the female connectors residing on the programmer, according to an embodiment. According to various embodiments, the lower unit 702 further includes pass-throughs for 6-pin mini-DIM female connectors, allowing the use of standard programming cables for wired communication with a hearing assistance device without removal of the WAM assembly from the programmer.

FIG. 9 illustrates a schematic diagram of an embodiment of the interface between a WAM device and communication (or technology) modules. A circuit 900 is shown providing an interface 910 for up to five technology modules, and a connection to the lower portion of the WAM assembly 920. A controller 930 directs communication between the WAM and the technology modules. In an embodiment, communication with the technology modules takes place via the standard I²C lines provided from the lower unit in the same way as for wired programming. The fitting system enables power to the lower unit connectors. In an embodiment, an analog audio line is used to initiate wireless programming in contrast to wired programming. In an embodiment, each technology module has a separate 1.3 V power supply and remain powered down until addressed by the microcontroller included in the lower unit. 2.5 V are available but are gated by the switched 1.3 V supply. In an embodiment, the right I²C lines are switched off when the respective module is not addressed in order to avoid interference with active units. The left I²C lines are not switched and require gating. Each slot will in addition be equipped with a dedicated technology module detection line, in various embodiments. The technology module uses a Molex SMT CradleCon I/O standard connector system, in an embodiment. Connector pins on the module include, but are not limited to, a power supply pin, a ground pin, I²C clock and data for left and right pins, Tx/Rx activity indicator, and module detections. The technology module operational environment includes switching from wired to wireless programming using analog audio lines. The fitting software initiates addressing of technology modules, and modules are completely switched off and decoupled when not in use, so that only one technology module is on at a time.

Software Implementation Embodiment

To implement the WAM device function of interfacing a programmer (such as a NOAHlink device in the embodiment below) and technology modules (which enable wireless communication with a hearing assistance device), one or more controllers are programmed with software. In an embodiment, the software provides a function summarized by the following operational outline. First, fitting software applies power to the NOAHlink right connector. The microcontroller then boots the system, performs a discovery process to determine which technology modules are present in the upper unit, and waits for instructions on an audio line. Fitting software sends a wakeup audio stream to the upper unit on the right audio line. In response, the microcontroller disables left and right pass-throughs in the lower unit (connected to the NOAHlink), routing left and right I²C lines from the NOAHlink to the upper unit bus, so the NOAHlink can communicate directly with the technology modules in the upper unit. The microcontroller reduces its own clock speed to save power, and waits for signals on the activity indicator line. Fitting software then can communicate with a technology module on either I²C bus. The technology module activates LED as required via the microcontroller, using the activity indicator line. At the end of the session, the fitting software rests the WAM by removing power from the NOAHlink connectors or by instructing the WAM processor, via I²C, to enable the left and right pass-throughs.

In an embodiment, I²C addresses of the technology modules do not conflict and the addresses are coordinated. A minimum I²C data rate of 100 kbps is supported, and modules are rebooted and in idle mode within 0.5 sec after supplying power, in an embodiment. No additional power supply is used for the programmer, in an embodiment. According to various embodiments, one technology module is active at a given time. The maximum current consumption for a technology module is approximately 10 mA and quiescent current is approximately 1 mA, in an embodiment. In various embodiments the current consumption maximum for a module is 15 mA. According to various embodiments, technology modules are provided by the individual manufacturers of the hearing assistance devices, and are activated by that manufacturer's fitting software.

Software includes a software development kit (SDK) and firmware, in various embodiments. The SDK includes .NET assembly for I²C-based communications with technology modules via NOAHlink services for technology module discovery and slot control, in an embodiment. In one embodiment, the SDK uses NOAHlink kernel and himsa.com components. The firmware component runs on a microcontroller in the upper unit of the device, and is used for technology module and slot discovery, including enabling and disabling slots, and gathering and displaying slot activity and statistics, in various embodiments.

The SDK for the wireless accessory module (WAM) device includes a software component that fitting software (software for fitting a hearing assistance device to a user) will incorporate in order to allow for control over a programmer (such as a NOAHlink) hearing instrument connector bypass mechanism within the WAM device, as well as detecting and supplying power to the respective technology module. Communications with one or several specific WAM technology modules will then be controlled by software components supplied by a technology module vendor, according to various embodiments. In an embodiment, a specific technology module is communicated with via I²C using an I²C address associated with a specific technology module. As mentioned, the address for each technology module is unique. A processor in the WAM module performs discovery and maintains a table of technology modules currently installed (or plugged-in) to the WAM device. The WAM microcontroller has direct access to the connector detect lines and can begin the discovery process when power is enabled on the NOAHlink connector. Modules are switched off and decoupled when not in use, and only one technology module is “on” at a given time, in various embodiments. In an embodiment, the WAM device permits hot swapping (plugging and unplugging while powered) of technology modules. Firmware for the WAM system runs on a microcontroller in the upper unit, in an embodiment. The firmware is used for, among other things, technology module and slot discovery, enabling and disabling slots and gathering and displaying slot activity and statistics.

Additional operations are provided in the WAM system software, according to various embodiments. According to an embodiment, a “fitting application request” operation is provided, in which the fitting application software (in a remote computer, for example) logs in to the WAM software development kit (SDK), powers up the NOAHlink, downloads NOAHlink firmware, enables power to the WAM device via the right NOAHlink connector, and initiates the WAM startup operation. An audio tone is sent via the WAM SDK to trigger the bypass, and the WAM processor disables the pass-through. The fitting application instructs the WAM processor to enable a slot that has a specific I²C address. The WAM processor searches for the address in the correlation table, and if the address is found, the slot is enables and a positive result is returned. Otherwise, if there are any occupied by uncorrelated slots, the WAM processor performs a one-byte I²C read using all valid I²C addresses. If a technology module responds to any address, that address is correlated with the slot in the table, the slot is enabled, and a positive result is returned. Otherwise, if all addresses are naked, a negative result is returned. This provides for hot-swapping of modules.

According to an embodiment, a “WAM startup” operation is provided, in which the WAM SDK enables power on the right NOAHlink connector, the WAM processor boots up, enables power for all slots, and waits approximately 500 milliseconds for all modules to boot up. The WAM processor iterates through all valid I²C addresses, performing a one byte I²C read to each address. If the read is acknowledged, the address is added to the list of valid addresses. For each occupied slot N, where N=1 to 5 in this embodiment, the slot N is disabled for each uncorrelated address in the list of valid address. A zero byte I²C read is attempted to the uncorrelated address. If the read is NACKed, that address is correlated with slot N. This step also detects if more than one slot is assigned the same I²C address. According to an embodiment, a “detect line goes ‘unoccupied’” operation is provided, in which the WAM processor disables the power for the slot that went “unoccupied”, and clears the table entry referenced by the “unoccupied” slot. A “detect line goes ‘occupied’” operation is provided, in an embodiment. In this operation, the WAM processor marks the table entry of the address used by that slot as “uncorrelated”. Keeping the power off forces communication failure if the application tries communicating.

According to one embodiment, certain procedures will be performed. According to other embodiments, other procedures will be performed. In one embodiment, the WAM processor will not check the audio bypass line until the startup operation is complete. This prevents I²C bus collision with the NOAHlink device, because the NOAHlink does not have multi-master support. The discovery process will be performed whenever the WAM powers up, even if only wired communication will be used. When the application actually opens the module for the first time, the WAM SDK can query the WAM processor to verify that the address is still valid. This allows detection of when technology module A is replaced by technology module B, which has a different I²C address. However, it does not detect the case where module A is replaced by a physically different module but of the same technology, which has the same I²C address. Soft configuration values would be lost, and use of slot detect lines would allow the WAM processor to power down a slot if the module was removed. The WAM processor would need to be reset to force the discovery process again. Hot swapping would not be transparent to the fitting application, in this instance.

Methods for Wirelessly Communication with Hearing Assistance Devices

FIG. 8 illustrates a flow diagram of a method for wirelessly programming a hearing assistance device, according to one embodiment. An embodiment of the method includes providing a device having a plurality of communication modules removably attached to an upper unit of the device, at 805. The modules support a plurality of communication protocols. The method also includes communicating with a programmer using a lower unit of the device, at 810. The method further includes wirelessly communicating with a hearing assisting device using a communication module in the upper unit of the device using at least one of the communication protocols, at 815. The communication assists in programming the hearing assistance device from an external source that communicates with the programmer.

According to various embodiments, the method also includes providing a flexible conduit for housing electrical connections between the upper unit and the lower unit. In an embodiment, a neck loop is provided and adapted to be worn by a user of the hearing assistance device. The device provided includes a rechargeable power supply, in an embodiment. The method can further include recharging the rechargeable power supply without removing the supply from the system, using a recharging station having a base support member designed to prevent a tip over of the system. In an embodiment, the programmer includes a NOAHlink device, and the NOAHlink is physically connected to the lower unit of the device.

In an embodiment, each module supports at least one communication protocol for communicating with at least one hearing assistance device. By placing a different communication module in the upper unit, wireless communications can be established with a plurality of different hearing assistance devices manufactured by a plurality of different hearing aid manufacturers.

The disclosed WAM system addresses a need for a common programming platform for hearing assistance devices. By providing a physical and electrical connection to a programmer, and providing for the use of a number of proprietary technology modules (and thus protocols), the WAM system provides a standardized wireless interface that is seamless, universal and transparent to programming with cables. It allows for a use of multiple wireless technologies by use of a different module, and is thus easily adaptable for future updates and additional wireless protocols.

It is understood one of skill in the art, upon reading and understanding the present application will appreciate that variations of order, information or connections are possible without departing from the present teachings.

Additionally, one of ordinary skill in the art will understand that, the systems shown and described herein can be implemented using software, hardware, firmware, and combinations of thereof. As such, the term “system” is intended to encompass software implementations, hardware implementations, firmware implementations, and software and hardware and firmware implementations.

Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that other embodiments are possible without departing from the scope of the present subject matter.

WIRELESS INTERFACE FOR PROGRAMMING HEARING ASSISTANCE DEVICES

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

US Classifications

International Classifications

Abstract

Description

Claims

CROSS REFERENCE TO RELATED APPLICATIONS

Provisional Applications (1)