EP4440158A2 - Hörgerät mit dienstmodus und zugehöriges verfahren - Google Patents

Hörgerät mit dienstmodus und zugehöriges verfahren Download PDF

Info

Publication number
EP4440158A2
EP4440158A2 EP24184373.9A EP24184373A EP4440158A2 EP 4440158 A2 EP4440158 A2 EP 4440158A2 EP 24184373 A EP24184373 A EP 24184373A EP 4440158 A2 EP4440158 A2 EP 4440158A2
Authority
EP
European Patent Office
Prior art keywords
hearing device
mode
mode request
processing unit
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP24184373.9A
Other languages
English (en)
French (fr)
Other versions
EP4440158A3 (de
Inventor
Brian Dam Pedersen
Allan Munk VENDELBO
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
GN Hearing AS
Original Assignee
GN Hearing AS
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=52016530&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=EP4440158(A2) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by GN Hearing AS filed Critical GN Hearing AS
Priority to EP24184373.9A priority Critical patent/EP4440158A3/de
Publication of EP4440158A2 publication Critical patent/EP4440158A2/de
Publication of EP4440158A3 publication Critical patent/EP4440158A3/de
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; ELECTRIC HEARING AIDS; PUBLIC ADDRESS SYSTEMS
    • H04R25/00—Electric hearing aids
    • H04R25/55—Electric hearing aids using an external connection, either wireless or wired
    • H04R25/558—Remote control, e.g. of amplification, frequency
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; ELECTRIC HEARING AIDS; PUBLIC ADDRESS SYSTEMS
    • H04R2225/00—Details of deaf aids covered by H04R25/00, not provided for in any of its subgroups
    • H04R2225/55—Communication between hearing aids and external devices via a network for data exchange
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; ELECTRIC HEARING AIDS; PUBLIC ADDRESS SYSTEMS
    • H04R25/00—Electric hearing aids
    • H04R25/55—Electric hearing aids using an external connection, either wireless or wired
    • H04R25/554—Electric hearing aids using an external connection, either wireless or wired using a wireless connection, e.g. between microphone and amplifier or using Tcoils
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; ELECTRIC HEARING AIDS; PUBLIC ADDRESS SYSTEMS
    • H04R25/00—Electric hearing aids
    • H04R25/70—Adaptation of deaf aid to hearing loss, e.g. initial electronic fitting

Definitions

  • the present disclosure relates to a hearing device and in particular to hearing device and related method for configuration or operation of a hearing device.
  • a hearing device becomes increasingly advanced.
  • Wireless communication between a hearing device and external devices such as hearing device fitting apparatus, remote controllers, tablets and smart phones, has evolved.
  • a wireless communication interface of a hearing device uses open standard-based interface.
  • a hearing device may assume any incoming data as legitimate, and may allow memory to be written or changed by an unauthorized party. Any such attacks may result in a malfunction of the hearing aid, or a battery exhaustion attack.
  • a hearing device comprising a processing unit configured to compensate for hearing loss of a user of the hearing device, a memory, and an interface.
  • the processing unit/hearing device may be configured to receive a mode request via the interface; authenticate the mode request; and place the hearing device into the requested mode if authentication of the mode request succeeds.
  • a method for configuration of a hearing device comprising a processing unit configured to compensate for hearing loss of a user of the hearing device, a memory, and an interface.
  • the method may comprise receiving a mode request via the interface; authenticating the mode request; and placing the hearing device into the requested mode if authentication of the mode request succeeds.
  • the method and hearing device as disclosed provide secure configuration of the hearing device, such as secure access to the memory of the hearing device. It is an advantage of the present disclosure that the hearing device can only be configured or updated by authorized parties. The disclosed hearing device thus has the advantage of detecting and preventing any modification by unauthorized parties.
  • the hearing device disclosed herein is advantageously protected against attacks such as spoofing attacks, man-in-the-middle attacks, and/or replay-attacks.
  • the method and apparatus as disclosed provides a secure configuration and/or update of a hearing device.
  • the present disclosure provides improved security of a hearing device.
  • Security comprise assessing threats, vulnerabilities and attacks and developing appropriate safeguards and countermeasures to protect against threats and attacks.
  • the hearing device comprises a processing unit.
  • the processing unit is configured to compensate for hearing loss or other hearing disability of a user of the hearing device.
  • the hearing device may be operated in one or more modes.
  • the one or more modes may include a first mode and/or a second mode.
  • the one or more modes may include a third mode and/or a fourth mode.
  • the one or more modes may include a default mode.
  • the first mode may be a service mode.
  • a service mode may be characterized in that a firmware part of the memory can be written in the service mode.
  • the firmware part of the memory may be write-protected in at least one other mode of the hearing device.
  • the second mode may be a fitting mode.
  • a fitting mode may be characterized in that a fitting part of the memory can be read and/or written in the fitting mode.
  • a fitting mode may be characterized in that a firmware part of the memory is write-protected.
  • the fitting part of the memory may comprise fitting data, such as hearing loss parameters, compressor parameters, filter coefficients, and/or gain coefficients.
  • the third mode may be a debug mode.
  • a debug mode may be characterized in that a debug part of the memory can be read and/or written in the fitting mode.
  • a debug mode may be characterized in that a fitting part of the memory can be read and/or written in the debug mode.
  • a debug mode may be characterized in that a firmware part of the memory can be read and/or written in the debug mode.
  • the debug part of the memory may be read-protected and/or write-protected in at least one other mode of the hearing device, such as in the default mode and/or the fitting mode.
  • the default mode may be a boot mode.
  • a boot mode may be characterized in that the hearing device is operated according to operating parameters set during booting and/or in response to user input, e.g. program selection, volume up/down, etc.
  • the default mode may be characterized in that the firmware part (or at least a part thereof) and/or the fitting part of the memory (or at least a part thereof) is write-protected and/or read-protected in the default mode.
  • the default mode may be characterized in that the debug part of the memory (or at least a part thereof) is read-protected and/or write-protected in the default mode.
  • the hearing device comprises a memory.
  • the memory may be embedded in the processing unit and/or be employed in a memory unit connected to the processing unit.
  • the memory may comprise a first memory part.
  • the first memory part may be a firmware part of the memory.
  • the firmware part of the memory may be configured to be accessed in the service mode e.g. to be written to and/or read from in the service mode.
  • the firmware part of the memory may additionally be configured to be accessed in the debug mode.
  • the memory may comprise a second memory part.
  • the second memory part may be a fitting part of the memory.
  • the fitting part of the memory may be configured to be accessed in the fitting mode e.g. to be written to and/or read from in the fitting mode.
  • the fitting part of the memory may additionally be configured to be accessed in the service mode and/or the debug mode.
  • the memory may comprise a third memory part.
  • the third memory part may be a debug part of the memory.
  • the debug part of the memory may be configured to be accessed in the debug mode e.g. to be written to or read from in the debug mode.
  • the hearing device may comprise an interface configured for enabling communication between the hearing device and another device.
  • the interface may comprise a wireless transceiver, e.g. configured for wireless communication at frequencies in the range from 2.4 to 2.5 GHz.
  • the wireless transceiver may be a Bluetooth Low Energy transceiver.
  • the interface may comprise a connector for forming a wired connection to the hearing device.
  • the interface may form a connection to one or more other devices such as a tablet and/or a smart phone and/or a fitting device.
  • the processing unit/hearing device is configured to receive a mode request via the interface.
  • the mode request may comprise a mode identifier indicative of the requested mode.
  • the mode request may be a service mode request, e.g. the mode identifier is indicative of a first/service mode.
  • the mode request may be a fitting mode request, e.g. the mode identifier is indicative of a second/fitting mode.
  • the mode request may be a debug mode request, e.g. the mode identifier is indicative of a third/debug mode. Accordingly, the mode request may be one of a service mode request, a fitting mode request, and a debug mode request.
  • the mode request may comprise a sender identifier indicative of the mode request sender.
  • the mode request may comprise a certificate, such as a digital signature, for certifying the mode request sender. This allows for direct authentication of the mode request.
  • the mode request may comprise a session identifier, e.g. an encrypted session identifier.
  • the hearing device may be paired with a sender of the mode request prior to receipt of the mode request.
  • the hearing device and the sending/client device device may have exchanged one or more of hearing device identifier, sender identifier, session identifier, etc.
  • the processing unit/hearing device is configured to authenticate the mode request and to place the hearing device into the requested mode if authentication of the mode request succeeds.
  • the processing unit may be configured to place the hearing device into a mode different from the requested mode, such as the default mode, if authentication of the mode request fails.
  • the hearing device disclosed herein has the advantage of verifying integrity of received mode requests and/or senders thereof, detecting any alteration and disregard altered mode requested.
  • the hearing device disclosed herein may advantageously allow access to specific parts of the memory only with authenticated parties, such as an authenticated fitting device, an authenticated accessory device, an authenticated external device and/or an authenticated server.
  • the processing unit may be configured to authenticate the mode request by authenticating the sender of the mode request.
  • the processing unit/hearing device may be configured to authenticate the mode request by verifying integrity of a digital signature of the mode request.
  • the processing unit may be configured to authenticate the mode request by verifying integrity of the mode request.
  • the mode request may comprise a message authentication code.
  • To verify integrity of the mode request may comprise to verify the message authentication code, e.g. with a session identifier stored in the hearing device.
  • the mode request may comprise a digital signature or certificate.
  • To verify integrity of the mode request may comprise verifying the digital signature or certificate.
  • the processing unit/hearing device may be configured to send a mode response. For example, to place the hearing device into the requested mode if authentication of the mode request succeeds may comprise sending a mode response.
  • the processing unit/hearing device may be configured to generate and/or send a mode response in response to the mode request.
  • the processing unit may be configured to obtain and/or store a session identifier (may also be denoted session key) and include the session identifier and/or an encrypted version thereof in the mode response.
  • To obtain the session identifier may comprise to generate the session identifier, e.g. as a random or pseudo-random number.
  • the hearing device and/or the processing unit may comprise a number generator, e.g.
  • a session identifier configured to generate a random or pseudo-random number as a session identifier.
  • the processing unit may be configured to encrypt the session identifier, optionally based on a hearing device key.
  • the session identifier may be a session key in the form of a symmetric key.
  • a symmetric session key may provide a lightweight processing of the security algorithms on the processing unit, such as lightweight encryption, lightweight decryption, lightweight integrity protection, etc.
  • the hearing device key may be a symmetric key or a public key of a private-public key pair.
  • the hearing device key may be stored in a permanent memory of the hearing device, e.g. during manufacture or during a fitting session.
  • the mode response may comprise the encrypted session key.
  • the session response may comprise a hearing device identifier and/or the session key.
  • the processing unit may be configured to send a hearing device identifier and/or the session key in the mode response.
  • a mode response comprising a hearing device identifier may enable the sender of the mode request to obtain the hearing device key, either from a database or by requesting the hearing device key from the manufacturer, which in turn enables the sender of the mode request to decrypt an encrypted session identifier/key and use the session identifier when sending data to the hearing device.
  • the mode request may be received in a session.
  • the processing unit/hearing devic may be configured to terminate the session if authentication of the mode request fails.
  • the mode request may comprise a signature
  • to authenticate the mode request may comprise to verify the signature of the mode request.
  • the processing unit may be configured to obtain, e.g. generate a session identifier, e.g. upon receipt of the mode request or when the hearing device is in a service mode, a fitting mode, or a debug mode.
  • the processing unit may be configured to encrypt the session identifier, e.g. with a hearing device key.
  • the processing unit may be configured to transmit the session identifier or the encrypted session identifier via the interface, e.g. as a part of the mode response or a session setup message.
  • the processing unit may be configured to store the session identifier in the hearing device.
  • the processing unit may be configured to receive data via the interface, e.g. when the hearing device is in a mode, e.g. the service mode, the fitting mode and/or the debug mode.
  • the processing unit may be configured to authenticate the received data, e.g. when the hearing device is in one or more modes, e.g. the service mode, the fitting mode and/or the debug mode.
  • the processing unit may be configured to store hearing device data in a part of the memory based on the received data if authentication of the data succeeds. For example, when the hearing device is in a service mode, the processing unit may store hearing device data, such as e.g. firmware, based on the received data in the firmware part of the memory.
  • the processing unit may, when the hearing device is in a fitting mode, store hearing device data (fitting data) based on the received data in the fitting part of the memory. In an exemplary hearing device, the processing unit may, when the hearing device is in a debug mode, store hearing device data (debug data) based on the received data in the debug part of the memory.
  • the processing unit may be configured to authenticate the received data by verifying integrity of the received data. Verifying integrity of the received data may be based on the session identifier stored in the hearing device.
  • the received data may comprise a message authentication code. To verify integrity of the received data may comprise to verify the message authentication code, e.g. with the stored session identifier.
  • the received data may comprise a digital signature. To verify integrity of the received data may comprise verifying the digital signature.
  • the data may comprise a session identifier
  • to authenticate the data may comprise to compare the session identifier of received data with the session identifier stored in the hearing device.
  • the data may be received in a session.
  • the processing unit may be configured to terminate the session if authentication of the received data fails, e.g. the processing unit may be configured to terminate the session if integrity of the received data is corrupted, i.e. verification of the integrity fails.
  • the processing unit may be configured to place the hearing device in another mode, such as the default mode, if authentication of the received data fails,
  • the hearing device/processing unit may be configured to receive a mode exit request and to place the hearing device in another mode, such as the default mode, e.g. if an authentication of the mode exit request succeeds.
  • a client device may send a mode exit request when fitting or transfer of firmware is done.
  • the disclosed method provides secure configuration and/or update of a hearing device.
  • the method may comprise placing the hearing device into a default mode if authentication of the mode request fails.
  • the method may comprise determining if operation in default mode fails, and switching to service mode if operating the hearing device in default mode fails,
  • authenticating the mode request may comprise authenticating the sender of the mode request.
  • the mode request may comprise a digital signature
  • authenticating the mode request may comprise verifying the digital signature
  • authenticating the mode request may comprise verifying integrity of the mode request.
  • the method may comprise receiving data via the interface, e.g. when the hearing device is in one or more modes, e.g. the service mode, the fitting mode and/or the debug mode.
  • the method may comprise authenticating the received data, e.g. when the hearing device is in one or more modes, e.g. the service mode, the fitting mode and/or the debug mode.
  • the method may comprise storing hearing device data in a part of the memory based on the received data if authentication of the data succeeds. For example, when the hearing device is in a service mode, the method may comprise storing hearing device data (firmware) based on the received data in the firmware part of the memory.
  • the method may, when the hearing device is in a fitting mode, comprise storing hearing device data (fitting data) based on the received data in the fitting part of the memory.
  • the method may, when the hearing device is in a debug mode, comprise storing hearing device data (debug data) based on the received data in the debug part of the memory.
  • the method may comprise placing the hearing device in another mode, such as the default mode, if authenticating the received data fails.
  • the processing unit may be configured to operate the hearing device in default mode, and switch to service mode if operating the hearing device in default mode fails,
  • Fig. 1 schematically illustrates an exemplary architecture 100 according to this disclosure.
  • the architecture 100 comprises a hearing device 101, a client device 110, and a server device 111.
  • the client device 110 may comprise a computing device acting as a client, a fitting device, a handheld device, a relay, a tablet, a personal computer, a mobile phone, and/or USB dongle plugged into a personal computer.
  • the server device 111 may comprise a computing device configured to act as a server, i.e. to serve requests from the client device 110 and/or from the hearing device 101.
  • the server device 111 may be controlled by the hearing device manufacturer.
  • the hearing device 101 may be connected to the client device 110 via a communication link 113, such as a bidirectional communication link and/or a wireless communication link.
  • the wireless communication link may be carried over a short-range communication system, such as Bluetooth, Bluetooth low energy, IEEE 802.11, Zigbee.
  • the hearing device 101 may be connected to the client device 110 over a network.
  • the hearing device 101 may be connected to the server device 111 via a communication link 114 over a network 114a, such as a bidirectional and/or wireless communication link over a network.
  • the client device 110 may be connected to the server device 111 via a communication link 112 over a network 112a, such as a bidirectional and/or wireless communication link over a network.
  • a network 112a such as a bidirectional and/or wireless communication link over a network.
  • the network 112a may be the Internet.
  • Fig. 2 schematically illustrates an exemplary hearing device 101.
  • the exemplary hearing device 101 comprises a processing unit 202 configured to compensate for hearing loss of a user of the hearing device 101.
  • the exemplary hearing device 101 comprises a memory and an interface 204.
  • the memory is in Fig. 1 illustrated in the form of a memory unit 203 external to the processing unit 202.
  • the memory may in other exemplary hearing devices be at least partly embedded in the processing unit 202 and/or in the memory unit 203.
  • the processing unit 202 is configured to receive a mode request via the interface 204.
  • the processing unit 202 comprises a receive/send unit 205 configured to send and/or receive via the interface 204.
  • the receive/send unit 205 is configured to send and receive via the interface 204 to/from an external device, such as a server device, a client device, a fitting device, an accessory, a relay device, a smart phone.
  • the processing unit 202 is configured to authenticate the mode request.
  • the processing unit 202 may comprise an authenticator 206 configured to authenticate the mode request.
  • the processing unit 202 is configured to place the hearing device into the requested mode, such as a service mode, a fitting mode or debug mode, if authentication of the mode request succeeds.
  • the processing unit 202 comprises a mode controller configured to place the hearing device into the requested mode, e.g. based on an output from the authenticator 206.
  • the processing unit 202 is configured to place the hearing device into a default mode if authentication of the mode request fails, the default mode comprising booting the hearing device and operating the hearing device according to operating parameters set during booting.
  • the operating parameters set during booting may be stored in a non-volatile part of the memory unit 203.
  • the operating parameters set during booting may comprise a default setting enabling the hearing aid to function according to a default setting programmed during production of the hearing device.
  • the hearing device comprises a microphone 210 for receiving a sound signal and converting it into converted sound signal.
  • the converted sound signal may be an electrical and digital version of the sound signal.
  • the processing unit is configured to receive and process the converted sound signal into a processed sound signal according to a hearing loss of a user of the hearing device.
  • the processed sound signal may be compressed and/or amplified or the like.
  • the hearing device further comprises an output transducer/loudspeaker, known as a receiver 212.
  • the receiver 212 is configured to receive the processed sound signal and convert it to an output sound signal for reception by an eardrum of the user.
  • Fig. 3 shows an exemplary signalling diagram 300 between a hearing device 101, and a client device 110.
  • the client device may be in the form of a fitting device.
  • the hearing device 101 receives a fitting mode request 301 via the interface 204 from the client device 110, the mode request comprising a digital signature and a mode identifier.
  • the digital signature may be a signature according to the Digital Signature Standard or other suitable standards, such as RSA. for digital signatures known in the art..
  • the hearing device 101 authenticates the mode request by verifying the digital signature. In the illustrated signalling diagram 300, the authentication succeeds, and the processing unit places the hearing device in the fitting mode including sending a fitting mode response 302 to the client device via the interface 204.
  • a firmware part of the memory is write-protected and a fitting mode part of the memory is write-enabled.
  • the client device 110 Upon receipt of the fitting mode response 302, the client device 110 sends data 303 to the hearing device 101 which receives the data and authenticates the received data 303, e.g. by use of digital signature or a session identifier/key as described earlier. If authentication of data 303 succeeds, the processing unit 202 derives hearing device data (fitting data) from the data 303 and stores hearing device data (fitting data) in a fitting part of the memory. If authentication of data 303 fails, the processing unit 202 places the hearing device in default mode.
  • the client device may send a mode exit request and the hearing device is configured to optionally authenticate the mode exit request and to place the hearing device in the default mode, optionally if authentication of the mode exit request succeeds.
  • the client device may be in the form of a smart phone or a tablet and may comprise software configured to provide the functionality of a fitting device.
  • Fig. 4 shows an exemplary signalling diagram 300' where a client device 110 is used for updating firmware of the hearing device 101, and a client device 110 in the form of a fitting device.
  • the hearing device 101 receives a service mode request 304 via the interface 204 from the client device 110.
  • the hearing device 101 authenticates the service mode request.
  • the processing unit 202 places the hearing device in the service mode including sending a service mode response 305 to the client device via the interface 204.
  • the processing unit 202 is allowed to write to a firmware part of the memory.
  • the client device 110 Upon receipt of the service mode response 305, the client device 110 sends data 306 to the hearing device 101 which receives the data and authenticates the received data 306, e.g. by use of digital signature or a session identifier/key as described earlier. Before sending data to the hearing device, the client device 110 may correspond with a server device 111 as illustrated with dotted arrows 307, 308, e.g. in order to determine the data 306 to be sent to the hearing device. If authentication of data 306 succeeds, the processing unit 202 derives hearing device data (firmware data) from the data 306 and stores hearing device data (firmware data) in a firmware part of the memory. If authentication of data 306 fails, the processing unit 202 may place the hearing device in default mode and/or terminate the session.
  • hearing device data firmware data
  • the processing unit 202 may place the hearing device in default mode and/or terminate the session.
  • the client device may send a mode exit request and the hearing device is configured to optionally authenticate the mode exit request and place the hearing device in the default mode, optionally if authentication of the mode exit request succeeds.
  • Fig. 5 illustrates an exemplary flowchart of a method 400, e.g. for configuration of a hearing device, such as hearing device 101, comprising a processing unit configured to compensate for hearing loss of a user of the hearing device, a memory, and an interface.
  • the method 400 comprises receiving 401 a mode request via the interface and authenticating 402 the mode request.
  • Authenticating 402 the mode request comprises authenticating the sender of the mode request and verifying integrity of the mode request. If authentication of the mode request succeeds 404, the method proceeds to placing 403 the hearing device into the requested mode. If authentication of the mode request fails 404, the method optionally proceeds to placing 405 the hearing device into a default mode.
  • the method After placing the hearing device in the requested mode, the method optionally proceeds to receiving 408 data via the interface, authenticating 410 the received data; and storing 412 hearing device data in a part of the memory corresponding to the requested mode and based on the received data if authentication of the data succeeds. If authenticating 410 the received data fails, the method may proceed to placing 405 the hearing device in default mode or another mode and/or terminating the session. Upon storing, the method 400 optionally comprises to evaluate 414 whether a mode exit request has been received. If so, the method proceeds to placing 405 the hearing device in default mode. If not, the method proceeds to receiving 408 data.
  • hearing devices and methods according to any one of the following items.
  • a hearing device comprising
  • Item A2 A hearing device according to item A1, wherein the processing unit is configured to place the hearing device into a default mode if authentication of the mode request fails.
  • a hearing device according to item A2, wherein the default mode comprises booting the hearing device and operating the hearing device according to operating parameters set during booting.
  • Item A4 A hearing device according to any of items A1-A3, wherein the processing unit is configured to authenticate the mode request by authenticating the sender of the mode request.
  • Item A5. A hearing device according to any of items A1-A4, wherein the processing unit is configured to authenticate the mode request by verifying integrity of the mode request.
  • Item A6 A hearing device according to any of items A1-A5, wherein the mode request is one or more of
  • a hearing device according to any of items A1-A6, wherein to place the hearing device into the requested mode if authentication of the mode request succeeds comprises sending a mode response.
  • Item A8 A hearing device according to any of items A1-A7, wherein the mode request is received in a session and the processing unit is configured to terminate the session if authentication of the mode request fails.
  • Item A9 A hearing device according to any of items A1-A8, wherein the mode request comprises a signature, and wherein to authenticate the mode request comprises to verify the signature of the mode request.
  • Item A10 A hearing device according to any of items A1-A9, wherein when the hearing device is in a service mode, the processing unit is configured to generate a session identifier, to transmit the session identifier via the interface and to store the session identifier in the hearing device.
  • Item A11 A hearing device according to any of of items A1 -A10, wherein when the hearing device is in a service mode, the processing unit is configured to receive data via the interface, wherein the processing unit is configured to authenticate the received data and store hearing device data in a part of the memory based on the received data if authentication of the data succeeds.
  • a hearing device according to item A11 as dependent on item A10, wherein the data comprises a session identifier, and wherein to authenticate the data comprises to compare the received session identifier with the session identifier stored in the hearing device.
  • Item A13 A hearing device according to item A11, wherein the data is received in a session and the processing unit is configured to terminate the session if authentication of the received data fails.
  • Item A14 Method for configuration of a hearing device comprising a processing unit configured to compensate for hearing loss of a user of the hearing device, a memory, and an interface, the method comprising:
  • Item A15 Method according to item A14, the method comprising placing the hearing device into a default mode if authentication of the mode request fails.
  • a hearing device comprising
  • Item B2 A hearing device according to Item B1, wherein the processing unit is configured to place the hearing device into a default mode if authentication of the mode request fails.
  • Item B3 A hearing device according to Item B2, wherein the default mode comprises booting the hearing device and operating the hearing device according to operating parameters set during booting.
  • Item B4 A hearing device according to any of Items B1-B3, wherein the processing unit is configured to authenticate the mode request by authenticating the sender of the mode request.
  • Item B5. A hearing device according to any of Items B1-B4, wherein the processing unit is configured to authenticate the mode request by verifying integrity of the mode request.
  • Item B6 A hearing device according to any of Items B1-B5, wherein the mode request is one or more of
  • a hearing device according to any of Items B1-B6, wherein to place the hearing device into the requested mode if authentication of the mode request succeeds comprises sending a mode response.
  • Item B8 A hearing device according to any of Items B1-B7, wherein the mode request is received in a session and the processing unit is configured to terminate the session if authentication of the mode request fails.
  • Item B9 A hearing device according to any of Items B1-B8, wherein when the hearing device is in a service mode, the processing unit is configured to generate a session identifier, to transmit the session identifier via the interface and to store the session identifier in the hearing device.
  • Item B10 A hearing device according to any of Items B1-B9, wherein when the hearing device is in a service mode, the processing unit is configured to receive data via the interface, wherein the processing unit is configured to authenticate the received data and store hearing device data in a part of the memory based on the received data if authentication of the data succeeds.
  • Item B11 A hearing device according to Item B10 as dependent on Item B9, wherein the data comprises a session identifier, and wherein to authenticate the data comprises to compare the received session identifier with the session identifier stored in the hearing device.
  • Item B12 A hearing device according to Item B10, wherein the data is received in a session and the processing unit is configured to terminate the session if authentication of the received data fails.
  • Item B13 Method for configuration of a hearing device comprising a processing unit configured to compensate for hearing loss of a user of the hearing device, a memory, and an interface, the method comprising:
  • Item B14 Method according to Item B13, the method comprising placing the hearing device into a default mode if authentication of the mode request fails.
  • Item B15 Method according to any of Item B13-B14, wherein authenticating the mode request comprises authenticating the sender of the mode request.
  • first, second, third and fourth does not imply any particular order, but are included to identify individual elements.
  • first, second, etc. does not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another.
  • first and second are used here and elsewhere for labelling purposes only and are not intended to denote any specific spatial or temporal ordering.
  • labelling of a first element does not imply the presence of a second element and vice versa.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Neurosurgery (AREA)
  • Otolaryngology (AREA)
  • Physics & Mathematics (AREA)
  • Acoustics & Sound (AREA)
  • Signal Processing (AREA)
  • Telephone Function (AREA)
  • Storage Device Security (AREA)
  • Circuit For Audible Band Transducer (AREA)
EP24184373.9A 2014-12-12 2014-12-12 Hörgerät mit dienstmodus und zugehöriges verfahren Pending EP4440158A3 (de)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP24184373.9A EP4440158A3 (de) 2014-12-12 2014-12-12 Hörgerät mit dienstmodus und zugehöriges verfahren

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
EP24184373.9A EP4440158A3 (de) 2014-12-12 2014-12-12 Hörgerät mit dienstmodus und zugehöriges verfahren
EP20155342.7A EP3668120B1 (de) 2014-12-12 2014-12-12 Hörgerät mit wartungsmodus und zugehöriges verfahren
EP14197819.7A EP3032845B1 (de) 2014-12-12 2014-12-12 Hörgerät mit Authentifizierung einer Anforderung zum Betriebsartwechsel und zugehöriges Verfahren

Related Parent Applications (3)

Application Number Title Priority Date Filing Date
EP14197819.7A Division EP3032845B1 (de) 2014-12-12 2014-12-12 Hörgerät mit Authentifizierung einer Anforderung zum Betriebsartwechsel und zugehöriges Verfahren
EP20155342.7A Division EP3668120B1 (de) 2014-12-12 2014-12-12 Hörgerät mit wartungsmodus und zugehöriges verfahren
EP20155342.7A Division-Into EP3668120B1 (de) 2014-12-12 2014-12-12 Hörgerät mit wartungsmodus und zugehöriges verfahren

Publications (2)

Publication Number Publication Date
EP4440158A2 true EP4440158A2 (de) 2024-10-02
EP4440158A3 EP4440158A3 (de) 2024-12-25

Family

ID=52016530

Family Applications (3)

Application Number Title Priority Date Filing Date
EP14197819.7A Revoked EP3032845B1 (de) 2014-12-12 2014-12-12 Hörgerät mit Authentifizierung einer Anforderung zum Betriebsartwechsel und zugehöriges Verfahren
EP20155342.7A Active EP3668120B1 (de) 2014-12-12 2014-12-12 Hörgerät mit wartungsmodus und zugehöriges verfahren
EP24184373.9A Pending EP4440158A3 (de) 2014-12-12 2014-12-12 Hörgerät mit dienstmodus und zugehöriges verfahren

Family Applications Before (2)

Application Number Title Priority Date Filing Date
EP14197819.7A Revoked EP3032845B1 (de) 2014-12-12 2014-12-12 Hörgerät mit Authentifizierung einer Anforderung zum Betriebsartwechsel und zugehöriges Verfahren
EP20155342.7A Active EP3668120B1 (de) 2014-12-12 2014-12-12 Hörgerät mit wartungsmodus und zugehöriges verfahren

Country Status (2)

Country Link
EP (3) EP3032845B1 (de)
DK (1) DK3032845T3 (de)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10785578B2 (en) 2014-12-12 2020-09-22 Gn Hearing A/S Hearing device with service mode and related method
US10104522B2 (en) 2015-07-02 2018-10-16 Gn Hearing A/S Hearing device and method of hearing device communication
US9877123B2 (en) 2015-07-02 2018-01-23 Gn Hearing A/S Method of manufacturing a hearing device and hearing device with certificate
DK3113513T3 (da) * 2015-07-02 2020-07-20 Gn Hearing As Adgangsrettighedsstyring i et høreapparat
EP3113517A1 (de) * 2015-07-02 2017-01-04 GN ReSound A/S Hörgerät mit kommunikationsprotokollierung und zugehöriges verfahren
US10158955B2 (en) 2015-07-02 2018-12-18 Gn Hearing A/S Rights management in a hearing device
DK201570433A1 (en) 2015-07-02 2017-01-30 Gn Hearing As Hearing device with model control and associated methods
US10158953B2 (en) 2015-07-02 2018-12-18 Gn Hearing A/S Hearing device and method of updating a hearing device
US10318720B2 (en) 2015-07-02 2019-06-11 Gn Hearing A/S Hearing device with communication logging and related method
DK3334190T3 (da) * 2016-12-08 2021-11-15 Gn Hearing As Høreindretninger, brugertilbehørsindretninger og fremgangsmåde til opdatering af en høreindretningskonfiguration
EP4541058A1 (de) * 2022-06-17 2025-04-23 3Shape A/S Intraorale abtastvorrichtung mit konfiguration zur authentifizierung einer modusanforderung
WO2023242390A1 (en) * 2022-06-17 2023-12-21 3Shape A/S An intraoral scanning device configured to authenticate mode request

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5083312A (en) 1989-08-01 1992-01-21 Argosy Electronics, Inc. Programmable multichannel hearing aid with adaptive filter
EP0840581A1 (de) 1995-06-28 1998-05-13 Cochlear Limited Vorrichtung und methode zur programmierung durch die stimme, sowie zum eingeben privater daten
DE19916900C1 (de) 1999-04-14 2000-09-21 Siemens Audiologische Technik Programmierbares Hörhilfegerät
US10576275B2 (en) 2001-07-06 2020-03-03 Cochlear Limited System and method for configuring an external device using operating parameters from an implanted device
US7257372B2 (en) 2003-09-30 2007-08-14 Sony Ericsson Mobile Communications Ab Bluetooth enabled hearing aid
CA2462495A1 (en) 2004-03-30 2005-09-30 Dspfactory Ltd. Method and system for protecting content in a programmable system
US8077891B2 (en) * 2006-03-31 2011-12-13 Phonak Ag Method and system for adjusting a hearing device
US20080165994A1 (en) * 2007-01-10 2008-07-10 Magnadyne Corporation Bluetooth enabled hearing aid
EP2327015B1 (de) 2008-09-26 2018-09-19 Sonova AG Drahtloses aktualisieren von hörgeräten
US8437860B1 (en) * 2008-10-03 2013-05-07 Advanced Bionics, Llc Hearing assistance system
KR102037412B1 (ko) * 2013-01-31 2019-11-26 삼성전자주식회사 이동 단말기와 연결된 보청기를 피팅(ｆｉｔｔｉｎｇ) 하는 방법 및 이를 수행하는 이동 단말기
EP2804401B1 (de) 2013-05-15 2018-11-21 GN Hearing A/S Hörgerät mit einem Authentifizierungsprotokoll
US10187733B2 (en) 2013-08-27 2019-01-22 Sonova Ag Method for controlling and/or configuring a user-specific hearing system via a communication network

Also Published As

Publication number Publication date
EP4440158A3 (de) 2024-12-25
EP3668120C0 (de) 2024-08-14
EP3668120A1 (de) 2020-06-17
DK3032845T3 (da) 2020-05-04
EP3032845A1 (de) 2016-06-15
EP3668120B1 (de) 2024-08-14
EP3032845B1 (de) 2020-02-05

Similar Documents

Publication Publication Date Title
EP4440158A2 (de) Hörgerät mit dienstmodus und zugehöriges verfahren
US10681082B2 (en) Hearing device with communication protection and related method
US10027474B2 (en) Hearing device with communication protection and related method
US11546699B2 (en) Hearing device with service mode and related method
US11284249B2 (en) Apparatus for secure hearing device communication and related method
DK201570433A1 (en) Hearing device with model control and associated methods
EP3032858B1 (de) Vorrichtung zur sicheren Hörgerätekommunikation und zugehöriges Verfahren
KR20190108888A (ko) 전자 장치 및 전자 장치에서의 인증 방법
DK201470778A1 (en) Hearing device with service mode and related method
CN111835775A (zh) 一种基于区块链的物联网设备安全调用方法、装置及设备
DK201470780A1 (en) Apparatus for secure hearing device communication and related method

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN PUBLISHED

AC Divisional application: reference to earlier application

Ref document number: 3032845

Country of ref document: EP

Kind code of ref document: P

Ref document number: 3668120

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

RIC1 Information provided on ipc code assigned before grant

Ipc: H04R 25/00 20060101AFI20241115BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20250620

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS