Remote verification of hearing device for e-commerce transaction

Abstract

Disclosed herein are examples of methods and systems for performing remote verification of a hearing device, particularly for use by a non-expert user outside the clinical environment. A status and/or functionality of the hearing device may be verified using verification criteria. Upon verifying the status and/or the functionality of the hearing device, a user may be permitted to conduct an e-commerce transaction. The status of the hearing device may include identification information associated with the hearing device and/or the user. The functionality of the hearing device may include a calibration and/or a system performance.

Description

TECHNICAL FIELD

Examples described herein relate to hearing devices, and more particularly methods and systems for remote verification of a hearing device.

BACKGROUND

An e-commerce transaction may be conducted by a hearing device user and a provider using the Internet. The user may purchase hearing aid related products and services by performing the e-commerce transaction. The provider may approve an e-commerce transaction after performing various remote verifications, such as a verification of the user's device. Performing the verification may be important so as to allow the provider to recommend compatible parts and/or prevent fraud or misuse.

Support services, such as sales support or technical support, may be provided by a manufacturer over the phone or the Internet. Support personnel typically request information before providing support. For certain technical support tasks, support personnel may request the user to perform a series of operations and report the results in order to provide the support remotely.

The performance of a hearing aid typically changes due to degradation of components over time. Performance and calibration checks for hearing aids are typically performed by professionals in clinical settings using specialized test instruments, such as a hearing aid analyzer. These specialized test instruments are cumbersome due to size, cost, and nuances unneeded in the consumer environment. The specialized test instruments are generally not available nor usable in the consumer environment. Hearing aid analyzers or calibration checkers for home use have been disclosed. However, these systems suffer from similar issues related to size, cost, and complexity. Thus, these testers, with methods and processes associated thereto, are generally not suitable for administration by a hearing aid user in the consumer environment.

BRIEF DESCRIPTION OF THE DRAWINGS

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, including the best mode presently contemplated of practicing the invention, when taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a schematic view of a remote verification system for verification of a hearing device including a remote server, a personal computing device (i.e. a personal computer, smartphone, etc.), and a portable test unit, according to some examples.

FIG. 2 is a schematic view of a remote verification system including a portable test unit for verifying a functionality of the hearing device, according to some examples.

FIG. 3 is a block diagram of a hearing device, according to some examples.

FIG. 4 is a schematic view of a remote verification system showing a hearing device in communication with a remote support computer, according to some examples.

FIG. 5 is a schematic view of a remote verification system showing a hearing device adapted to communicate with a client computing device, and client portable test unit, according to some examples.

FIG. 6 is a flow chart representation for remotely verifying a functionality of a hearing device and performing an e-commerce transaction, according to some examples.

FIG. 7 is a flow chart representation for performing an e-commerce transaction for a hearing device, according to some examples.

FIG. 8 is a flow chart representation for performing an e-commerce transaction for a hearing device after calibration check of the hearing device at the client side, according to some examples.

FIG. 9 is a flow chart representation for performing an e-commerce transaction for a hearing device, according to some examples.

FIG. 10 is a flow chart representation for providing customer support for a hearing aid user, according to some examples.

FIG. 11 is a flow chart representation for performing an e-commerce transaction for a hearing device provided on a client side, according to some examples.

FIG. 12 is a block diagram of a hearing device test system according to examples of the present disclosure.

DETAILED DESCRIPTION

Certain details are set forth below to provide a sufficient understanding of embodiments of the invention. Some embodiments, however, may not include all details described. In some instances, well-known structures may not be shown in order to avoid unnecessarily obscuring the described embodiments of the invention.

The present disclosure describes methods and systems for remote verification of a remotely accessible hearing device. A hearing aid manufacturer or provider may wish to perform a transaction remotely or provide support services upon a verification of a hearing device. The hearing device may be verified by checking whether the hearing device exists or passes certain identification, functional, and/or performance criteria. A remote verification system according to examples disclosed herein may facilitate an e-commerce transaction or a support service. The online remote verification system disclosed herein allows the provider to verify a status and/or functionality of the hearing device prior to approving the e-commerce transaction or providing the support services. The remote verification system empowers non-expert consumers to purchase or obtain hardware, accessories, features, software, and/or services for their hearing device outside a clinical setting, such as a home, an office, a nursing home, a retail store, a pharmacy, etc. generally without resorting to professional assistance.

In some examples, the status and/or functionality of the hearing device may include a calibration check of the hearing device. The calibration of the hearing device may be checked automatically without resorting to sending the hearing device to the manufacturer or a service center for calibration or calibration check. In some examples, the status and/or functionality of the hearing device may include identification information associated with the hearing device, such as a serial number or user identification/credentials. The identification information may be checked automatically without manual input or professional assistance. In some examples, the status and/or functionality of the hearing device may be a read and/or write ability from/to a memory of the hearing device.

FIG. 1 is a schematic view of a remote verification system for a hearing device including a remote server communicatively coupled to a computing device 10 (i.e. a personal computer or a smartphone 13) and the hearing device 20. The remote verification system may include an e-commerce server 70 and/or a remote server 80 on a remote side 4. Although the e-commerce server 70 and the remote server 80 are shown as separate, those skilled in the art will appreciate that there can be a single computer system (FIG. 2) that performs these functions or there can be several computer systems arranged in a central or distributed fashion to perform these functions (FIG. 1). It is understood that virtually any number of intermediary networking devices, such as switches, routers, servers, etc. may be used to facilitate communication.

The remote verification system may include a computing device 10 and a hearing device 20 on a client side 3. In some examples, the hearing device 20 may be communicatively coupled to the computing device 10 by a wired connection or a wireless connection. In some examples, the hearing device 20 may be communicatively coupled to the computing device 10 via a portable test unit 1.

The remote verification system may be implemented as part of an e-commerce platform 71. The e-commerce platform 71 may facilitate a transaction between a provider and a consumer. The e-commerce platform 71 may include an e-commerce website 72, user data 73, device data 74, and/or any other data or services to perform a transaction for a hearing device user over the Internet 65. The transaction may include a purchase of hardware, software, features, and/or a service associated with the hearing device 20. It will be understood that a purchase may include, but is not limited to, a monetary purchase. For example, purchase in exchange for currency and/or for credits, points, or free of charge. Hardware associated with the hearing device 20 may include accessories, ear tips, and/or batteries. Software associated with the hearing device 20 may include programming software, hearing test software, and/or tuning profiles. Features associated with the hearing device 20 may include wireless services or programming credits. Services associated with the hearing device 20 may include warranties, protection plans, and/or support plans for the hearing device 20.

It may be advantageous for the e-commerce platform 71 to determine a status and/or functionality of the hearing device 20 prior to approving and performing an e-commerce transaction. The e-commerce platform 71 may use the status and/or functionality of the hearing device 20 to present a set of items for sale to the consumer and/or approve a transaction. In some examples, the consumer may be eligible to purchase a set of eligible items. The eligible items may include items compatible with the consumer's hearing device 20. In some examples, the consumer may attempt to complete a transaction in which one or more items require a verification of the status and/or functionality of the hearing device 20. The e-commerce platform 71 may approve the transaction after verifying the status and/or functionality of the hearing device 20.

The status of the hearing device 20 may include identification information (e.g., identification data 26) of the hearing device 20 and/or a user associated with the hearing device 20. The identification information of the hearing device 20 may include a serial number assigned to the hearing device 20 by the manufacturer. The identification information of the consumer associated with the hearing device 20 may include user account information, customized settings of the user or the hearing device 20.

The identification information of the hearing device 20 may be used to retrieve additional information about the hearing device 20, such as a model number of the hearing device 20, a user name registered to the hearing device 20, items or services for sale that are compatible with the hearing device 20. Being able to retrieve the identification information may verify that the hearing device 20 is eligible for and/or functional and able to power on. In some examples, the identification information may be used to provide support information, such as hearing loss data, hearing aid fitting data, order history, or targeted marketing data associated with the user.

The functionality of the hearing device 20 may include hardware and/or software performance of the hearing device 20. The hardware performance may include acoustical performance and/or memory function. The acoustical performance may include electroacoustic and/or a calibration characteristics of the hearing device 20. Memory performance may include the ability to read or write to memory of the hearing device 20. Software performance may include ability to execute and/or access software of the hearing device 20.

The functionality of the hearing device 20 may be used to verify that the hearing device 20 is functioning properly or to determine a capability of the hearing device 20. A properly functioning hearing device 20 may be required for certain transactions or to provide a support service. For example, a manufacturer may wish to add a warranty service and/or protection plan to an existing user of a hearing device 20 after the initial sale. The provider may further wish to provide a warranty service and/or protection plan only for a hearing device 20 that is functioning properly at the time of request for purchase of the warranty service and/or protection plan. In some examples, the e-commerce platform 71 may verify the functionality of the hearing device 20 prior to offering the warranty service and/or protection plan to a user. In some examples, the e-commerce platform 71 may automatically verify the functionality of the hearing device 20 while conducting a transaction, for example during a checkout process. If the functionality of the hearing device 20 is verified, the transaction may be approved. If the functionality of the hearing device 20 is not verified, the transaction may be denied.

The e-commerce platform 71 may be hosted by an e-commerce server 70 provided on a remote side 4. The e-commerce server 70 may be accessible via a communications network 65, such as the Internet. The e-commerce platform 71 may include an e-commerce website 72. The e-commerce website 72 may present a user interface 31 for conducting e-commerce transactions. For example, a user on a client side 3 may use a personal computing device 10 also on the client side 3 to access the e-commerce website 71 via the Internet.

The e-commerce server 70 may be communicatively coupled to a remote server 80 for verification of a hearing device 20. The remote server 80 may be provided on the remote side 4. The remote server 80 may be accessible via a communications network 65, such as the Internet. The remote server 80 may include a verification platform 81. The verification platform may include a website 82 and/or a verification app 83. A server, such as the e-commerce server 70, or a client device may access the verification platform 81 for a verification of the hearing device 20.

The remote server 80 may be communicatively coupled to a remote database 84 on the remote side 4. The remote database 84 may include reference data 85 for verification of the hearing device 20. The reference data 85 may include entries associated with the hearing device 20, such as serial numbers, user account information, fitting parameters and/or calibration data. The entries may be used by the remote server 80 to perform a verification check of the hearing device 20. For example, entries from the remote database 84 may be compared with test results from test unit 1 or functionality data retrieved from the hearing device 20 to verify the hearing device 20.

The computing device 10 may be a personal computer, a smartphone 13, a tablet, or any other type of device with a processor 41 and memory 44 for executing an application. In some examples, the computing device 10 may include a display 42 for presenting a user interface 31 to the user. The computing device 10 may be provided on a client (user) side 3. The computing device 10 may include a network interface for accessing the remote server 80 and/or the e-commerce server 70 via the communications network 65. The computing device 10 may execute a web application 31 and/or a verification app 32 for performing a verification check using the verification platform 81. The web application 31 may be used to access the e-commerce website 72 or the verification website 82. The web application 31 may be used to execute the verification app 83. The web application 31 may be executed via a browser or executed as a standalone application with access to the Internet 65.

The computing device 10 may be communicatively coupled to a hearing device 20. The hearing device 20 may be a hearing aid (BTE, ITE, CIC, or any other type), a personal sound amplification product (PSAP), or any other type of sound delivery device worn by a consumer, in or around the ear. The hearing device 20 may include a sound processor 56, a speaker 57 and a microphone 59. In some examples, the hearing device 20 may be modular, including a lateral module and a main module. The lateral module may include a battery cell. The lateral module may partially or fully disengage from the main module. The hearing device 20 may be coupled to the computing device 10 via a wired or wireless interface. In some examples, the wired interface may include a USB connection. In some examples the wireless interface may include a Bluetooth connection.

FIGS. 2 and 12 are schematic views of a remote verification system including a portable test unit 1 for verifying a functionality of the hearing device 20. In some examples, the portable test unit 1 may be handheld or wearable. In some examples, the portable test unit 1 may weigh less than 2 ounces.

The portable test unit 1 includes a circuit board 27 with a programming interface 50 for communicating with the hearing device 20. The circuit board 27 may include audio processing electronics 8 for performing an acoustic verification check. The circuit board 27 may include a microphone 7 for receiving acoustic signals from the hearing device 20. In some examples, the portable test unit 1 may be coupled with the computing device 10 for communication with a verification app 32 of the computing device 10 for performing the verification check.

The portable test unit 1 may be an intermediary device used to facilitate communication between the hearing device 20 and the computing device 10. The portable test unit 1 may include an acoustic calibration cavity 3 for acoustic coupling with the hearing device 20. The acoustic calibration cavity 3 may be provided along an external surface 4 of the portable test unit 1 for receiving acoustic stimuli from the hearing device 20. In some examples, the acoustic calibration cavity 3 may accommodate the hearing device 20 at least partially therein. In some examples, the portable test unit 1 comprises an adapter for accommodating the hearing device 20 within the acoustic calibration cavity 3. In some examples, the adapter may be configured to enable the hearing device 20 to be coupled to the acoustic calibration cavity 3 of the portable test unit 1.

In some examples, the medial end of the hearing device 20 may be positioned within the acoustic calibration cavity 3 or the adapter. In some examples, the speaker 57 of the hearing device 20 may be oriented towards a microphone 7 of the portable test unit 1. The microphone 7 of the portable test unit 1 may be provided within the acoustic calibration cavity 3 for receiving the acoustic calibration stimuli 55 during a calibration check or verification check in conjunction with an e-commerce transaction.

The portable test unit 1 may be communicatively coupled to the hearing device 20 via a programming interface 50 using a wired interface, which may include a programming cable, or a wireless interface, which may include Bluetooth. The portable test unit 1 may retrieve identification data 26 stored in a memory 63 of the hearing device 20. The identification data 26 stored in the memory 63 of the hearing device 20 may include the serial number, fitting parameters 60, and/or user information. The identification data 26 may be retrieved using a wired or wireless connection to the hearing device 20.

In some examples, the portable test unit 1 may be communicatively coupled to the computing device 10 using a wired connection 38, such as a USB connection. In some examples, the portable test unit 1 may be communicatively coupled to the computing device 10 using a wireless connection, such as Bluetooth. The computing device 10 or the portable test unit 1 may receive or generate a test signal request. The test signal request may include instructions indicative of verification parameters, such as what kind of verification is being requested. The computing device 10 and/or portable test unit 1 may communicate with the hearing device 20 for performing the verification check.

The computing device 10 may be in communication with a remote server 80 or an e-commerce server 70 for performing an e-commerce transaction. A user of the hearing device 20 may visit an e-commerce website 72 to perform the e-commerce transaction. The e-commerce web site 72 may provide a graphical user interface 31 through which the user may interact with the remote side 4, e.g., for performing an e-commerce transaction. In some examples, a verification check step may be performed as part of a checkout process facilitated by the e-commerce website 72. In some examples, a verification check step may be performed prior to presenting, via the e-commerce website 72, a service option or items for sale to the user. During the verification check step, a status and/or a functionality of the hearing device 20 may be verified.

The computing device 10 may be in communication with a support computer 100 for providing support services. The support services may include sales support, technical support, or other customer support functions. A user of the hearing device 20 may be in communication with a customer support personnel 101 operating the support computer 100. Sales support may include selecting products or services that may be of interest to the user. Technical support may include verifying functionality, evaluating performance, or ensuring proper use of the products. Support may be automated and/or computer-based. In some examples, functions of the support computer 100 (e.g., support services) may be incorporated into and thereby provided by the remote server 80.

The computing device 10 may receive a verification check request from the remote server 80 or the support computer 100. The verification check request may be received while a user of the computing device 10 is browsing the e-commerce website and/or during a checkout process on the e-commerce website. The verification check request may be delivered to the computing device 10 by any of the remote server 80 or the support computer 100. The verification check request may include instructions for performing the verification check according to verification criteria. Verification criteria may include a calibration range, diagnostic criteria, hardware connection, identification data 26, and/or any other functionality or status of the hearing device 20.

The computing device 10 may execute a verification software application 32 for performing a verification check. The verification software application 32 may enable communication between the computing device 10 and the hearing device 20, e.g., during a verification check. In some examples, the verification software application 32 may provide a web-based user interface (also referred to as a web application 31) such as for receiving user inputs, displaying information to the user, or both, during a verification check. In some examples, operations of the verification software application 32 may run in the background without requiring user interaction and/or without the user being aware of the verification check(s) being performed. The verification software application 32 may communicate with a verification app 83 provided on the remote server 80. For example, while a user is browsing the e-commerce website 72, the e-commerce website 72 may initiate the verification app 83 to perform a verification check of the hearing device 20 while the user is browsing the e-commerce website 72 and/or attempting to conduct an e-commerce transaction.

During a verification check, verification data may be generated in response to the verification check request. The verification data may be generated by the computing device 10, the hearing device 20, or a combination of the two. In some examples, the verification data may include identification data 26, for example a serial number, retrieved from memory 63 of the hearing device 20. In some examples, the verification data may include a level of an output of a hearing device speaker 57. In some examples, the verification data may include an indication of whether the level of the output of the hearing device speaker 57 conforms to a verification criteria, for example whether the level of the output is within a valid calibration range.

A remote verification may be initiated when a verification check request is received by the computing device 10 or the hearing device 20. The computing device 10 may request the identification data 26 from the hearing device 20. Upon the hearing device 20 successfully delivering the identification data 26 to the computing device 10, verification data may be generated including the identification data 26 and/or an indication that verification was successful. The remote server 80 may receive the verification data from the computing device 10. The remote server 80 may compare the verification data to reference data 85 stored in a remote database 84 accessible to the remote server 80. If the hearing device 20 does not successfully deliver the identification data 26 to the computing device 10, verification data may be generated that indicates that the verification was unsuccessful. For example, if the hearing device 20 is out of communication range of the computing device 10, the identification data 26 may not be deliverable to the computing device and the verification may be unsuccessful.

In some examples, the verification check request may include a request for hearing device performance verification. The hearing device performance verification may include a check of memory 61, circuitry function, and/or performance checks of other components of the hearing device 20. The computing device 10 may perform the hearing device performance verification by delivering a verification check request to the hearing device 20. The verification check request may be delivered directly from the computing device 10 to the hearing device 20 or via the portable test unit 1. The verification check may be performed by a write step and a read step to verify the performance of the memory 63 of the hearing device 20. For example, if the hearing device 20 successfully performs the read step following the write step, verification data may be generated to indicate that the hearing device performance verification was successful.

In some examples, the verification check request may include a request for acoustic performance verification. The acoustic performance verification may include verifying that an output of the hearing device 20 is within a valid calibration range. The acoustic performance verification may include initiating a calibration check after placement of the hearing device 20 at least partially within the acoustic calibration cavity 3 of the portable test unit 1. The computing device 10 or the portable test unit 1 may detect the placement of the hearing device 20 at least partially within the acoustic calibration cavity 3 and automatically initiate the calibration check. In some examples, instructions may be provided to the user (e.g., via a user interface on the computing device) to place the hearing device 20 at least partially within the acoustic calibration cavity 3 and/or initiate the calibration check. When the hearing device 20 is accommodated within the acoustic calibration cavity 3, the speaker 57 of the hearing device 20 may provide an acoustic test stimuli 55 within the acoustic calibration cavity 3. The acoustic calibration cavity 3 may be configured with a controlled volume to produce a predetermined sound pressure level according to the acoustic test stimuli and the controlled cavity volume.

In some examples, the verification check request may include authentication data. The authentication data may include a passcode, for example a random alphanumeric sequence and/or an answer to a security question. The computing device 10 may receive the authentication data from the remote server 80 or generate the authentication data. The computing device 10 may deliver the authentication data to the hearing device 20. The hearing device 20 may present an audible authentication message representing the authentication data to an ear of a user wearing the hearing device 20 using speaker 57.

In some examples, the authentication data may be a random alphanumeric sequence, such as “A123.” The computing device 10 may generate or relay the random alphanumeric sequence to the user and/or the hearing device. The computing device 10 may generate the random alphanumeric sequence by executing an authentication data generator. The computing device 10 may relay a random alphanumeric sequence received from a third party computer, such as a remote server 80. In some examples, the random alphanumeric sequence may be one or more random words.

A user authentication entry in response to the audible authentication message may be registered by the computing device 10. In some examples, the user may hear the audible authentication message from the speaker 57 of the hearing device 20 and may manually enter an authentication response using the computing device 10. The manually entered authentication response may be registered by the computing device 10. The user may manually enter the authentication response using a keyboard (or keypad) or touchscreen of the computing device 10. In some examples, the user may manually enter the authentication response by selecting an answer from a set of options presented in a user interface 31 displayed on the computing device 10. When presented with a set of options in the user interface 31, the user may use a mouse coupled to the computing device to select one or more of the options in an authentication response. In some examples, the user may enter a spoken authentication response after hearing the audible authentication message from the speaker 57 of the hearing device 20. The spoken authentication response may be registered by the computing device 10. The spoken authentication response from the user may be detected from a microphone of any of the hearing device 20 (e.g., microphone 59), computing device 10, or portable test unit 1 (e.g., microphone 7). The spoken response may be converted by speech recognition software for detection by computer system for authentication.

The computing device 10 may generate verification data based on the authentication data and/or the user authentication entry for authentication by the remote server 80. The user authentication response may be authenticated using a full match, a partial match, or a correct user selection. The verification data may be used to verify the hearing device 20 presence and/or function prior to performing an e-commerce transaction. In some examples, the user authentication entry may be delivered by the computing device 10 to a remote server 80. The remote server 80 may authenticate the user authentication entry prior to performing the e-commerce transaction.

The microphone 7 of the portable test unit 1 may be provided within the acoustic calibration cavity 3 for receiving the acoustic calibration stimuli, which may be generated by the hearing device 20 responsive to test signals 29 during a calibration check. In some examples, the microphone 7 may be provided at a bottom of the acoustic calibration cavity 3. During a calibration check or a calibration, the microphone 7 may produce a sensed calibration signal in response to receiving the acoustic calibration stimuli. The microphone 7 may deliver the sensed calibration signal to an audio processing electronics 8 (APE) of the portable test unit 1. The computing device 10 may receive the sensed calibration signal and/or a sensed calibration signal level. Verification data may be generated using the sensed calibration signal and/or the sensed calibration signal level. The verification data may include the sensed calibration signal level and/or a determination of whether the sensed calibration signal level is within a valid calibration range.

The remote server 80 or the support computer 100 may verify a status and/or a functionality of the hearing device 20 based on one or more verification criteria. The verification criteria may include authorized identification data, successful performance check, and/or calibration data that is within a calibration range. The verification criteria may include comparing status and/or functionality information obtained from the hearing device 20 with reference data 85. The reference data 85 may include information indicative of authorized identification data (e.g., reference serial numbers), reference performance levels, and/or reference calibration data. The hearing device 20 may be verified based on whether it passed the one or more of the verification criteria. For example, the hearing device 20 may be verified when the serial number of the hearing device 20 of a user is determined to be valid.

In some examples, testing of individual components of the hearing device 20 may be isolated and performed separately. For example, the speaker 57 and sound processing electronics of the hearing device 20 may be checked, e.g., by requesting delivery of an acoustic calibration stimuli from the hearing device 20 to a portable test unit 1. The microphone 59 of the hearing device 20 may be bypassed or disabled while the speaker 57 and sound processing electronics are being checked. A first signal level associated with the acoustic calibration stimuli in the acoustic calibration cavity may be measured by the calibration microphone 7 provided within the acoustic calibration cavity 3 (referred to herein as “calibration microphone”). A calibration of the hearing device speaker 57 may be validated by comparing the level of the first signal measured and a first reference level stored in a memory. The memory may be provided in the portable test unit 1, the hearing device 20, the computing device 10, the remote server 80, or any other device associated with the remote verification test system.

After verifying the hearing device 20, the user may be permitted to conduct an e-commerce transaction. As discussed above, the e-commerce transaction may include a purchase of hardware, software, features, and/or services associated with the hearing device 20.

FIG. 3 is a schematic view of a hearing device 20. The hearing device 20 may be a canal hearing device including a microphone 59, a pre-amp, analog-to-digital converter, sound processor 56, which may be a digital single processor (DSP), calibration signal generator, digital-to-analog converter, and speaker 57 incorporated therein. The microphone 59 of the hearing device 20 may receive acoustic signals 53 and generate an input signal 58. Responsive to the input signal 58, the signal processor 56 may generate an output signal using the fitting parameters 60. The speaker 57 of the hearing device 20 may deliver an acoustic output 55 based on the output signal.

The hearing device 20 may receive test signals from any of the portable test unit 1 and the computing device 10. The calibration signal generator 24 (see FIG. 5) of hearing device 20 may generate an acoustic output responsive to the test signals. The acoustic output 55 may be delivered to the ear of a user using the speaker 57 of the hearing device 20. The test signals may be non-acoustic inputs to the hearing device. For example, the hearing device 20 may receive the test signals 29 wirelessly using a wireless communication device (e.g., a wireless receiver 54 and an antenna 52).

FIG. 4 is a schematic view of a remote verification system showing a wireless hearing device 20 in communication with a remote server 80 and a customer support computing device 100 (also referred to herein as “support computer”) via a network, for example the Internet 65. The customer support computing device 100 may be provided on the remote side 4. The customer support computing device 100 may be operated by a customer support personnel 101. The remote server 80 may receive a diagnostic check request from a customer support computing device 100. The diagnostic check may include a verification check of a status and/or functionality of the hearing device 20. The support personnel 101 may deliver a diagnostic check request in order to provide support to a user or enable an e-commerce transaction. The support personnel 101 may be able to ascertain desired information about the user and/or the hearing device 20, such as the serial number of the hearing device 20, user account information of the user, a calibration of the hearing device 20, and/or performance of the hearing device 20.

Upon receiving the diagnostic check request from the customer support computing device 100, the remote server 80 or the customer support computing device 100 may determine a status and/or a functionality of the hearing device 20 using the verification data and/or a verification criteria. The computing device 10 may be communicatively coupled to the hearing device 20 for delivery of the verification data or verification determination to the customer support computing device 100. In some examples, the customer support computing device 100 may execute a verification application to perform the verification of the hearing device 20.

The customer support computing device 100 may be implemented with a live chat feature on the e-commerce website 72, whereby a support personnel 101 may assist a user remotely. The customer support computing device 100 (e.g., automatically or via control by support personnel 101) may send a diagnostic check request to the hearing device 20.

FIG. 5 is a schematic view of a remote verification system showing a hearing device 20 adapted to communicate directly or indirectly with a computing device 10. For certain types of verification checks, for example a calibration check, the portable test unit 1 may be utilized to perform the verification check. For other types of verification checks, such as verifying identification information of the hearing device 20, the portable test unit 1 may not be required, although in some examples the portable test unit may provide a wired connection between the hearing device 20 and computing device 10 during the verification check. When the portable test unit 1 is required, the hearing device 20 may be acoustically and/or communicatively coupled to the portable test unit 1. The portable test unit 1 may execute or relay instructions from the computing device 10 to control the hearing device 20 and detect acoustic signals using its microphone 7. The portable test unit 1 may deliver acoustic signal measurement data to the computing device 10. The computing device 10 may generate verification data based on the acoustic signal measurement data.

In some examples, the hearing device 20 may be communicatively coupled directly (i.e., without an intermediary device) to the computing device 10 over a wired or wireless interface to perform a transaction on an e-commerce website using the computing device 10. During the checkout process on the e-commerce website 72, a verification check of the hearing device 20 may be performed. At the verification check step, the verification app 32 may be executed to detect and initiate a verification of a hearing device 20 that may be wirelessly coupled to the computing device 10. In some examples, the hearing device 20 may be worn in an ear of the user while the verification check is performed. The hearing device 20 may perform tasks associated with the verification check, for example delivering identification data and/or performing read or write procedures, wirelessly. The computing device 10 may receive data associated with the verification check from the hearing device 20 and generate verification data in accordance with the data received from the hearing device 20.

FIGS. 6-11 are flow chart representations for remotely verifying a functionality of a hearing device, according to some examples. While the various steps in these flowcharts are presented and described sequentially, one of ordinary skill will appreciate that some or all of the steps can be executed in different orders and some or all of the steps can be executed in parallel. Further, in one or more embodiments, one or more of the steps described below can be omitted, repeated, and/or performed in a different order. Accordingly, the specific arrangement of steps shown in FIGS. 6-11 should not be construed as limiting the scope of the invention.

FIG. 6 is a flow chart representation for a method, according to some examples. In step 602, a verification check request from a remote server is transmitted to a computing device which is communicatively coupled to a hearing device, wherein the computing device is associated with a user of the hearing device. In step 604, a verification data is received by the remote server from the computing device, wherein the verification data is generated by the computing device responsive to a determination by the computing device of a functionality of the hearing device. In step 606, the functionality of the hearing device is verified by the remote server.

FIG. 7 is a flow chart representation for a method, according to some examples. In step 702, a verification check request is received from a computing device from a remote server. In step 704, a functionality of the hearing device is determined by the computing device. In step 706, a verification data is transmitted by the computing device to a remote server, wherein the verification data is representative of the functionality of the hearing device. In step 708, an authorization of an e-commerce transaction is received by the computing device upon successful verification performed based on the verification data

FIG. 8 is a flow chart representation for providing customer support for a hearing aid user, according to some examples. In step 802, a request for a hearing aid verification is received by a computing device communicatively coupled to a hearing aid. In step 804, a verification data is received by the computing device from the hearing aid. The verification determination may be made at least partially based on the verification data. In step 806, the verification data is transmitted by the computing device to any of a support computer or a remote server. In step 808, an authorization for an e-commerce transaction is received by the computing device based on the verification determination.

FIG. 9 is a flow chart representation for providing customer support for a hearing aid user, according to some examples. In step 902, a request for a hearing aid verification check is transmitted to a computing device. The computing device may be communicatively coupled to a hearing aid. In step 904, a verification data associated with a calibration of the hearing aid is received. The verification data may be obtained by a portable test unit acoustically coupled to the hearing aid. An acoustic calibration cavity may be provided on an external surface of the portable test unit and a microphone may be provided within the acoustic calibration cavity. In step 906, a verification determination of a functionality of the hearing aid is received by the support computer. The verification determination may be based at least partially on whether the calibration of the hearing aid is within a valid calibration range. In step 908, an e-commerce transaction is authorized based on the verification determination.

FIG. 10 is a flow chart representation for a method, according to some examples. In step 1002, a hearing device on a client side is communicatively coupled to a computing device on the client side. The hearing device may comprise a speaker for producing audible sounds and memory for storing an identification data for the hearing device. In step 1004, the identification data stored within the memory of the hearing device is retrieved. In step 1006, a status of the hearing device is validated using identification data retrieved from the hearing device and data stored on a remote server. In step 1008, an e-commerce transaction is approved based on the validation of the status of the hearing device.

FIG. 11 is a flow chart representation for a method, according to some examples. In step 1102, an identification data stored within a memory of the hearing device is retrieved by a computing device provided on a client side. The hearing device may be provided on a client side. The hearing device may comprise a speaker for producing audible sounds. In step 1104, an approval for a transaction may be received by the computing device. A remote server provided on a remote side may be configured to validate a status of the hearing device. In step 1106, transaction data associated with the transaction is exchanged by the computing device with the remote server.

Although embodiments of the invention are described herein, variations and modifications of these embodiments 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.

Claims

1. A method comprising: communicatively coupling a hearing device on a client side to a computing device on the client side, wherein the hearing device comprises a speaker for producing audible sounds and memory for storing an identification data for the hearing device;retrieving the identification data stored within the memory of the hearing device;validating a status of the hearing device using identification data retrieved from the hearing device and data stored on a remote database; andapproving an e-commerce transaction based on the validation of the status of the hearing device.

2. A method comprising: retrieving, by a computing device provided on a client side, an identification data stored within a memory of the hearing device, wherein the hearing device is provided on a client side and the hearing device comprises a speaker for producing audible sounds;receiving, by the computing device, an approval for a transaction, wherein a remote server provided on a remote side is configured validate a status of the hearing device; andexchanging, by the computing device, transaction data associated with the transaction with the remote server.

3. A method comprising: receiving, by a remote server provided on a remote side, identification data from a computing device provided on a client side, wherein the computing device is configured to retrieve the identification data stored in a memory of the hearing device, wherein the hearing device is provided on a client side;retrieving a corresponding identification data from a remote database provided on the remote side;determining, by the remote server, an approval for an e-commerce transaction by validating a status of the hearing device using the identification data;delivering, by the remote server, the approval for the e-commerce transaction to the computing device; andexchanging, by the remote server, transaction data associated with the e-commerce transaction with the computing device.

4. A method comprising: generating an audible authentication message by a speaker of a hearing device responsive to a verification check request received form a remote server;registering, by a computing device communicatively coupled to the hearing device, a user authentication entry following presentation of the audible authentication message to a user of the hearing device; andtransmitting the user authentication entry from the computing device to the remote server;receiving an authorization for an e-commerce transaction from the remote server based on comparison between the audible authentication message and the user authentication entry.

5. The method of claim 4, wherein the audible authentication message is an audible message of a passcode.

6. The method of claim 4, further comprising receiving, by a microphone of any of the hearing device, the computing device, or a portable test unit, an audible authentication entry from the user.

7. The method of claim 6, further comprising using speech recognition to extract the user authentication entry from the audible authentication entry.

8. The method of claim 4, wherein the user authentication entry is registered using any of a mouse, keyboard, keypad, and a touch screen associated with the computing device.

9. The method of claim 8, wherein the user authentication entry is registered by presenting a set of authentication options to the user, wherein the set of authentication options comprise a correct user selection.