Patent Description:
Bluetooth LE as defined by the Bluetooth Core Specification <NUM>, or earlier versions, does not allow for audio transport. There are a number of limitations in the protocol as defined that means that audio transport is not feasible without changing certain protocol layers:.

<CIT> discloses retransmission of a data set for a maximum number of times within a predefined period.

It is an object of the new method and hearing device to overcome the above-mentioned shortcomings.

Thus, a new method of wireless communication of data sets is provided, comprising:.

Further, a new method of wireless communication of data with different priorities is provided, comprising.

The first data category may comprise audio data sets.

The second data category may comprise various control data, such as start, stop, codec negotiation, etc., compliant with a Bluetooth LE standard protocol, such as defined by the Bluetooth core specification <NUM>, or earlier versions, and/or data from other devices, e.g. devices with sensors, such as environmental sensors, such as temperature sensors.

The first data set may be an audio data set. An audio data set comprises values of a digital audio signal, such as a sequence of discrete-time and discrete-amplitude digital audio signal values that represent continuous-time and continuous-amplitude values of an analogue audio signal that can be converted into acoustic sound. In other words, an audio data set contains digital data that are intended for conversion into sound at some point in time as is well-known in the art of streaming audio.

Preferably, audio data sets have a high priority ensuring transmission of the audio data sets before transmission of other types of data sets with lower priorities in order to ensure high fidelity, or at least acceptable, quality of sound generated based on the transmitted audio data sets.

A data set, including an audio data set, may be a data packet with two kinds of data, namely control information and data. The data is also known as payload or payload data. The control information provides information data that a network needs in order to deliver the data or payload to the intended receiver, for example: source and destination device addresses, error detection codes, and sequencing information. Typically, control information is found in packet headers and trailers, with payload data in between.

Information on whether or not a data set with the second priority is awaiting transmission to the receiver may be encoded into a single data byte, such as a single data bit.

The method may be compliant with a Bluetooth low energy standard, such as the Bluetooth Core Specification <NUM>, or earlier versions, and, preferably, transmissions of audio data sets are performed in consecutive connection events.

The method may be utilized for audio streaming of, e.g., speech and music, in compliance with a Bluetooth low energy standard, such as the Bluetooth Core Specification <NUM>, or earlier versions.

The method may further comprise allocating L2CAP channels for transmission of audio data sets, e.g. by allocating one L2CAP channel for control data relating to the audio data sets, and/or allocating one L2CAP channel for a first audio data set, and possibly allocating another L2CAP channel for a second audio data set.

Three fixed L2CAP channels may be allocated for audio transport:.

In a device that can receive one audio stream (left or right), e.g. a hearing aid, only channel <NUM>) and <NUM>) or channel <NUM>) and <NUM>) would be in use for that device. In a device with integrated stereo capabilities, e.g. a stereo headset, all three channels are used. The audio data sets can be both unidirectional or bidirectional depending on the application, the control data channel should allow for negotiation on that point.

Connection Configuration may for example be performed by:.

Transmitting device operation e.g. while streaming audio, may include:.

The method may further comprise re-transmission of an audio data set in absence of acknowledgement of receipt from a receiver of the audio data set provided that the number of attempted re-transmissions of the same audio data set is below a predetermined maximum value, e.g. equal to two.

The number of attempted re-transmissions of one or more types of data may not be limited, i.e. no maximum value is allocated to these one or more types of data; or, in other words, the maximum value allocated to these one or more types of data is infinite, e.g. 0xFFFF.

Different types of data may have different predetermined maximum values of attempted re-transmissions, e.g. audio data sets may have the maximum value two while the maximum value for data sets with a lower priority than the priority of the audio data sets.

For example, the new method may implement L2CAP flush timeouts as also defined for Bluetooth Basic Rate (BR) L2CAP channels. Preferably, this timeout corresponds to two connection events after the data is posted over HCl (meaning that a first and retry event would be allowed for L2CAP audio) for the channels bearing audio data, whereas it would stay at 0xFFFF for other channels.

On a typical link, packets will be lost at a rate that is not suitable for audio. Hence, re-transmission is preferably permitted, and, preferably, take place at a different channel. Therefore the Bluetooth LE MD feature cannot be used for re-transmission. Thus, audio data sets with flush timeout set should only be attempted once within a connection interval. In order to allow for re-transmission, the connection interval must be half of the audio frame size, so if an audio frame is <NUM>, the connection interval should be <NUM>. This is facilitated using existing link layer control packets.

The MD feature may be used for transmission of lower priority data in the same connection event, but the receiving device may not honour the MD bit, e.g. a hearing aid will not honour the MD bit.

In order to lower power consumption of the receiver, the transmitter may be configured to set the MD bit in a high-priority packet to indicate that there is low priority data pending regardless of whether the transmitter will transmit the data after the high priority data in the same connection event or not. If there is no low priority data pending, the MD bit is reset. This allows the receiver to skip connection events that have no data in between successful transmission of high-priority audio data sets in response to the received value of the MD bit. Similarly, the transmitter is allowed to skip connection events with no pending data during audio streaming to save power and/or improve interoperability with other wireless services.

Note that when sending non-audio data sets, the lack of L2CAP flush timeout means that the link will be occupied until the data is acknowledged. This would in rare cases cause dropouts in the audio, which would have to be handled by packet loss concealment on the receiving side as for example disclosed in <CIT>.

The method may further comprise transmitting synchronization data from the transmitter to at least one receiver configured for reception of audio data sets, the synchronization data containing timing information relating to a transmission delay difference between at least two different receivers connected for reception of different audio data sets.

Determining the synchronization data may be based on ping transmission from the transmitter to the at least two different receivers, e.g. ping transmission utilizing a L2CAP control channel.

Preferably, during stereo audio streaming, the transmitter communicates a time offset between the links to the receiver leading in the link so that the received audio can be delayed accordingly for proper synchronization of the two stereo channels. The time offset may be determined with a network latency measurement implementing a ping over a control channel. This ping would allow a transmitter host to compute the time offset.

Stereo audio streaming may also be performed using one link. For example, during stereo audio streaming to a headphone, both left and right L2CAP channels may be transmitted with the same link, whereby both receiver and transmitter are kept simple. The Bluetooth LE MD feature may be utilized for this purpose, since the headphone can sustain higher radio duty cycle. In this way, the same connection event will carry information on both left and right channel, and the packet structure can be kept the same as the mono or dual-sink case. This simplifies implementation on both sides, since on the transmitter host side only the connection handle for the audio will need to change compared to the dual-sink case.

The following table outlines the required number of bytes required to hold audio data sets given a certain audio frame size in ms. The values are for an audio stream running at <NUM> kbit/s. A <NUM> kbit/s audio stream will be <NUM>/<NUM> of the requirement.

To keep overhead to a minimum, it is preferred to let the LL MTU size match the L2CAP MTU plus header and MIC and be equal to the required payload size so that a method or controller implementing L2CAP audio preferably support long packets.

Advantageously, the new method facilitates transmission of audio data sets utilizing Bluetooth LE utilizing extensions of the Bluetooth LE control and link layer in a limited way, e.g. operations relating to security and link setup are performed as specified in Bluetooth core specification.

A hearing device is also provided having a communication controller that is configured for operation according to the new method according to any of the appended claims.

The hearing device may be a hearing aid, such as a BTE, RIE, ITE, ITC, CIC, etc., a binaural hearing aid, an Ear-Hook, In-Ear, On-Ear, Over-the-Ear, Behind-the-Neck, Helmet, Headguard, etc., headset, headphone, earphone, ear defender, earmuff, etc..

Preferably, the communication controller is configured for audio transmission and/or reception of audio with Bluetooth LE L2CAP, and preferably, the communication controller is configured to.

Thus, a new hearing aid is provided that is capable of performing wireless communication in compliance with a Bluetooth LE standard protocol.

A transducer is a device that converts a signal applied to the transducer in one form of energy to a corresponding output signal in another form of energy.

The input transducer may comprise a microphone that converts an acoustic signal applied to the microphone into a corresponding analogue audio signal in which the instantaneous voltage of the audio signal varies continuously with the sound pressure of the acoustic signal.

The input transducer may also comprise a telecoil that converts a varying magnetic field at the telecoil into a corresponding varying analogue audio signal in which the instantaneous voltage of the audio signal varies continuously with the varying magnetic field strength at the telecoil. Telecoils may be used to increase the signal to noise ratio of speech from a speaker addressing a number of people in a public place, e.g. in a church, an auditorium, a theatre, a cinema, etc., or through a public address systems, such as in a railway station, an airport, a shopping mall, etc. Speech from the speaker is converted to a magnetic field with an induction loop system (also called "hearing loop"), and the telecoil is used to magnetically pick up the magnetically transmitted speech signal.

The input transducer may further comprise at least two spaced apart microphones, and a beamformer configured for combining microphone output signals of the at least two spaced apart microphones into a directional microphone signal.

The input transducer may comprise one or more microphones and a telecoil and a switch, e.g. for selection of an omni-directional microphone signal, or a directional microphone signal, or a telecoil signal, either alone or in any combination, as the audio signal.

Typically, the analogue audio signal is made suitable for digital signal processing by conversion into a corresponding digital audio signal in an analogue-to-digital converter whereby the amplitude of the analogue audio signal is represented by a binary number. In this way, a discrete-time and discrete-amplitude digital audio signal in the form of a sequence of digital values represents the continuous-time and continuous-amplitude analogue audio signal.

Throughout the present disclosure, the "audio signal" may be used to identify any analogue or digital signal forming part of the signal path from the output of the input transducer to an input of the hearing loss processor.

Throughout the present disclosure, the "hearing loss compensated audio signal" may be used to identify any analogue or digital signal forming part of the signal path from the output of the hearing loss processor to an input of the output transducer possibly via a digital-to-analogue converter.

The hearing aid may comprise a transceiver comprising both a wireless transmitter and a wireless receiver. The transmitter and receiver may share common circuitry and/or a single housing. Alternatively, the transmitter and receiver may share no circuitry, and the wireless communication unit may comprise separate devices with the transmitter and the receiver, respectively.

The hearing aid may advantageously be incorporated into a binaural hearing aid system, e.g. wherein two hearing aids are interconnected utilizing the Bluetooth LE standard protocol for digital exchange of data, such as audio signals, signal processing parameters, control data, such as identification of signal processing programs, etc., etc., and optionally interconnected with other devices, such as a hand-held device, such as a tablet computer, a smart phone, e.g. an IPhone, an Android phone, a Windows phone, etc., a remote control, etc..

Typically, only a limited amount of power is available from the power supply of a hearing aid. For example, power is typically supplied from a conventional ZnO<NUM> battery in a hearing aid.

In the design of a hearing aid, the size and the power consumption are important considerations.

Signal processing in the new hearing aid may be performed by dedicated hardware or may be performed in one or more signal processors, or performed in a combination of dedicated hardware and one or more signal processors.

Likewise, the operations of the communication controller may be performed by dedicated hardware or may be performed in one or more processors, or performed in a combination of dedicated hardware and one or more processors.

As used herein, the terms "processor", "signal processor", "controller", "system", etc., are intended to refer to CPU-related entities, either hardware, a combination of hardware and software, software, or software in execution.

For example, a "processor", "signal processor", "controller", "system", etc., may be, but is not limited to being, a process running on a processor, a processor, an object, an executable file, a thread of execution, and/or a program.

By way of illustration, the terms "processor", "signal processor", "controller", "system", etc., designate both an application running on a processor and a hardware processor. One or more "processors", "signal processors", "controllers", "systems" and the like, or any combination hereof, may reside within a process and/or thread of execution, and one or more "processors", "signal processors", "controllers", "systems", etc., or any combination hereof, may be localized on one hardware processor, possibly in combination with other hardware circuitry, and/or distributed between two or more hardware processors, possibly in combination with other hardware circuitry.

Also, a processor (or similar terms) may be any component or any combination of components that is capable of performing signal processing. For examples, the signal processor may be an ASIC processor, a FPGA processor, a general purpose processor, a microprocessor, a circuit component, or an integrated circuit.

In the following, the new method and hearing aid is explained in more detail with reference to the drawings, wherein.

In the following, various examples of the new method and hearing device are illustrated. The new method and hearing device according to the appended claims may, however, be embodied in different forms and should not be construed as limited to the examples set forth herein.

It should be noted that the accompanying drawings are schematic and simplified for clarity, and they merely show details which are essential to the understanding of the new method and hearing aid, while other details have been left out.

<FIG> schematically illustrates a binaural hearing aid system comprising a left ear hearing aid <NUM> and a right ear hearing aid 10R, each of which comprises a wireless communication unit for connection to another audio-enabled communication device such as a smartphone or mobile phone, an audio-enabled tablet, a cordless phone, a TV-set etc. In the present embodiment, each of the left ear and right ear hearing aids <NUM>, 10R is connected to a smartphone <NUM> via respective wireless communication links <NUM>, 12R. The skilled person will understand that the binaural hearing aid system may comprise only a single hearing aid such as <NUM> in other embodiments of the system such the right hearing aid 10R is optional.

A unique ID identifies every device of the binaural hearing aid system. The illustrated binaural hearing aid system is configured to generally operate in accordance with Bluetooth Low Energy (Bluetooth LE) for example according to the Bluetooth Core Specification Version <NUM>. Hence, the illustrated binaural hearing aid system is configured to operate in <NUM> industrial scientific medical (ISM) band and comprises <NUM> frequency channels of <NUM> bandwidth in accordance with Bluetooth LE. However, Bluetooth LE controllers of the wireless communication units of each of the left and right ear hearing aids <NUM>, 10R and the smartphone <NUM> have been modified to enable transmission of real-time audio data sets through each of the wireless communication links <NUM>, 12R as explained in further detail below.

The left hearing aid <NUM> and the optional right hearing aid 10R may be substantially identical, expect for the above-described unique ID such that the following description of the features of the left hearing aid <NUM> also applies to the right hearing aid 10R. The left hearing aid <NUM> may comprise a ZnO<NUM> battery (not shown) that is connected for supplying power to the hearing aid circuit <NUM>. The left hearing aid <NUM> comprises an input transducer in the form of a microphone <NUM>. The microphone <NUM> outputs an analogue or digital audio signal based on an acoustic sound signal arriving at the microphone <NUM> when the left hearing aid <NUM> is operating. If the microphone <NUM> outputs an analogue audio signal the hearing aid circuit <NUM> may comprise an analogue-to-digital converter (not shown) which converts the analogue audio signal into a corresponding digital audio signal for digital signal processing in the hearing aid circuit <NUM>. In particular in a hearing loss processor <NUM> that is configured to compensate a hearing loss of a user of the left hearing aid <NUM>. Preferably, the hearing loss processor <NUM> comprises a dynamic range compressor well-known in the art for compensation of frequency dependent loss of dynamic range of the user often termed recruitment in the art. Accordingly, the hearing loss processor <NUM> outputs a hearing loss compensated audio signal to a loudspeaker or receiver <NUM>. The loudspeaker or receiver <NUM> converts the hearing loss compensated audio signal into a corresponding acoustic signal for transmission towards an eardrum of the user. Consequently, the user hears the sound arriving at the microphone; however, compensated for the user's individual hearing loss. The hearing aid may be configured to restore loudness, such that loudness of the hearing loss compensated signal as perceived by the user wearing the hearing aid <NUM> substantially matches the loudness of the acoustic sound signal arriving at the microphone <NUM> as it would have been perceived by a listener with normal hearing.

The hearing aid circuit <NUM> further includes a wireless communication unit which comprises a radio portion or circuit <NUM> that is configured to communicate wirelessly with the smartphone <NUM>. The wireless communication unit comprises a Bluetooth LE controller <NUM> performing the various communication protocol related tasks and possibly other tasks. The operation of the left hearing aid <NUM> may be controlled by a suitable operating system. The operating system may be configured to manage hearing aid hardware and software resources, e.g. including the hearing loss processor <NUM> and possible other processors and associated signal processing algorithms, the wireless communication unit, certain memory resources etc. The operating system may schedule tasks for efficient use of the hearing aid resources and may also include accounting software for cost allocation, including power consumption, processor time, memory locations, wireless transmissions, and other resources.

The operating system controls the radio circuit <NUM> to perform wireless communication with the smartphone <NUM> in accordance with the modified and therefore audio-enabled Bluetooth LE protocol. The smartphone <NUM> may operate as a master device and the left hearing aid <NUM> as a slave in connection with bi-directional data communication between the devise under the modified Bluetooth LE protocol.

The smartphone <NUM> comprises a radio portion or circuit <NUM> that is configured to communicate wirelessly with the corresponding radio portion or circuit <NUM> of the left hearing aid <NUM>. The smartphone <NUM> also comprises a wireless communication unit which comprises a Bluetooth LE controller <NUM> performing the various communication protocol related tasks in accordance with the modified Bluetooth LE protocol and possibly other tasks. Data packets or data sets for transmission over the wireless communication link <NUM> are supplied by the Bluetooth LE controller <NUM> to the radio circuit <NUM>. Data packets received by the radio portion or circuit <NUM> via RF antenna <NUM> are forwarded to the Bluetooth LE controller <NUM> for further data processing. The skilled person will appreciate that the smartphone <NUM> typically will include numerous additional hardware and software resources in addition to those schematically illustrated as is well-known in the art of mobile phones.

<FIG> is a first timing diagram <NUM> illustrating the new method of wireless communication of data sets with different priorities, e.g., between the left ear hearing aid <NUM> and the smartphone <NUM> discussed above, e.g., with the smartphone <NUM> configured as a master and the hearing aid <NUM> as a slave.

<FIG> illustrates operating conditions of the wireless communication link (<NUM> in <FIG>) with low interfering electromagnetic noise in the relevant data channels such that transmission of each data packet or data set from the transmitter is successful at the first transmission attempt and hence there is no need for re-transmission.

Consecutive connection events on the wireless communication link are indicated by Ci1, Ci2, Ci3, etc. along time axis t. The skilled person will understand that the illustrated adjacent connection events such as Ci1 and Ci2 may be separated by a considerable sleep time period for example up till <NUM> seconds in accordance with a Bluetooth LE protocol. During these sleep time periods, the radio circuit <NUM> of the left hearing aid <NUM> and the radio circuit <NUM> of the smartphone <NUM> may both be powered down to reduce power consumption. A connection event may have a duration or connection interval between <NUM> and <NUM>. The connection interval of each connection event is preferably selected as one-half of a selected audio frame size of audio data sets transmitted across the wireless communication link.

As illustrated in <FIG> by symbols "A" and "D" of data packets <NUM>, <NUM>, <NUM> or data sets, two types of data with different priorities are transmitted through the wireless communication link. Data packets designated A1 and A2 have first priority data and data packet D has a second priority that is lower than the first priority. In the illustrated example, the first or high priority data packets, <NUM>, <NUM> comprises audio data sets and the lower priority data packet <NUM> comprises various control data such as start, stop, codec negotiation, etc., compliant with the Bluetooth LE protocol according to the Bluetooth core specification <NUM>, or earlier versions. The data structure of each of the high priority data packets A1, A2 is illustrated by data packet <NUM>. The high priority data packet <NUM> comprises a header section <NUM> which may comprise <NUM> bytes. The high priority data packet <NUM> further comprises the above discussed payload data <NUM> which may comprise between <NUM> and <NUM> bytes of audio data depending on the audio frame size. A payload data size of <NUM> bytes leads to a length of about <NUM> for each of the high priority data packets which fits into the respective time windows of the connection events. The header section <NUM> preferably comprises a so-called more data (MD) field or bit, as illustrated by symbol "<NUM>". This MD field indicates whether there is low priority data packet D pending. The Bluetooth LE controller <NUM> of the transmitting device sets this MD bit if there is a low priority data packet D pending and resets the MD bit to "<NUM>" if there is no low priority data D pending. The Bluetooth LE controller <NUM> is preferably configured to set or reset the MD bit regardless of whether or not the transmitting device will actually transmit the low priority data packet D after the high priority data packet A1 in the same connection event Ci1 or not. This feature allows the receiving device to skip or eliminate connection events where no low priority data packet D is pending in-between successful high-priority data packet connection events by inspecting the MD bit.

The lower priority data packet D may have a length of <NUM> bytes. To illustrate the transmission sequence of the high priority and low priority data packets by the transmitting device, a first high priority data packet A1 is initially transmitted. Thereafter, an operation mode of the radio circuit <NUM> of the transmitting device is reversed from a transmitting mode to a receiving mode during a short pause of for example length of about <NUM>. Hence, the radio circuit <NUM> of the transmitting device comprises a Bluetooth transceiver. In the receiving mode, the radio circuit <NUM> of the transmitting device monitors the communication link and listens for an acknowledgement receipt signal transmitted from the receiving device, i.e. left ear hearing aid <NUM> in the present situation, which confirms that the high priority data packet A1 has been correctly received. The receipt of this acknowledgement signal or packet is illustrated by packet or signal <NUM> marked "Ack". Since, the previously discussed MD bit is set to "<NUM>" in the header <NUM> of the high priority data packet A1, a low priority data packet D is pending and awaiting transmission. The transmitting device therefore transmits the pending low priority data packet D <NUM> as illustrated and after another short pause, a second acknowledgement signal or packet <NUM> is received as illustrated.

The Bluetooth LE controller <NUM> of the receiving device has now safely received both the high priority data packet A1 and the low priority data packet D. The Bluetooth LE controller <NUM> can therefore safely abandon or skip the following connection event Ci2 which is otherwise used for re-transmission of the high priority data packet A1 as explained below in further detail. Hence, the wireless transceiver of the receiving device is not turned on during the second connection event Ci2 and thereby saves considerable power relative to receiving and transmitting data packets.

During the third connection event Ci3, a new high priority data packet A2 (<NUM>) is transmitted to the receiving device which thereafter acknowledges safe receipt by returning acknowledgement packet <NUM> marked "Ack" to the transmitting device. The MD bit may be set to "<NUM>" in the header <NUM> of the second high priority data packet A2 indicating that no low priority data packet D is pending. The Bluetooth LE controller <NUM> of the receiving device has now safely received the high priority data packet A2 and by inspection of the MD bit of the header of the packet A2 conclude that there is no low priority data packet D pending. Hence, the Bluetooth LE controller <NUM> therefore abandons or skips a subsequent connection event Ci4 (not shown).

<FIG> shows another exemplary timing diagram <NUM> illustrating the new method of wireless communication of data sets with different priorities. <FIG> illustrates operating conditions, e.g., of the wireless communication link <NUM> in <FIG>, with a certain amount of interfering electromagnetic noise in the relevant data channels such that transmission of individual data packets or data sets from the transmitter to the receiver fails from time to time.

As described above in connection with <FIG>, consecutive connection events of the wireless communication link are indicated by Ci1, Ci2, Ci3, Ci4, etc., along the time axis t. The skilled person will understand that the illustrated adjacent connection events, such as Ci1 and Ci2, may be separated by a considerable sleep time period or inactive period for example up till <NUM> seconds in accordance with Bluetooth LE protocol.

In <FIG>, the transmission sequence of the high priority and low priority data packets A1, A2 and D, respectively, by the transmitting device begins with transmission of a first high priority audio data packet A1. Thereafter, the transmitting device switches operation to the previously discussed receiving mode and monitors the communication link for an acknowledgement of receipt signal or package transmitted by the receiving device, i.e. the left ear hearing aid <NUM>. In the illustrated communication sequence, the transmission of the high priority data packet A1 in connection event Ci1 is successful, and the receiving device transmits the acknowledgement signal or packet Ack. No low priority data packet D is pending and awaiting transmission, so the previously discussed MD bit is set to "<NUM>" in the header of the high priority data packet A1 as indicated by "MD=<NUM>" in data packet A1 of <FIG>.

Since the high priority data has been received and no low priority data packet D is pending, the receiving device skips the next connection event Ci2, whereby power consumption is lowered in the receiving device.

In the third connection event Ci3, high priority data packet A2 is transmitted for the first time with limited success. The receiving device receives a data packet; however, a transmission error is detected, e.g. with CRC, and the receiving device transmits a not-acknowledge signal or data packet "Nack", possibly with the previously discussed MD bit set to "<NUM>", to request a re-transmission of the data packet within the same connection event Ci3. Thus, the data packet A2 is re-transmitted within the same connection event Ci3; however, in this example, also with the same result as before with detection of a transmission error in the receiving device. Optionally, the receiving device does not transmit the second "Nack" signal or packet in order to save power.

Subsequently, a first re-transmission in a subsequent connection event Ci4 is performed and this time the receiving device successfully receives the data packet A2, and the receiving device therefore transmits an acknowledge signal or packet to the transmitting device. No low priority data packet D is pending as indicated by "MD=<NUM>" in data packet A2 of <FIG>.

In the event that a transmitted data packet is lost, the receiving device does not transmit any signal, such as the "Nack" signal, and in absence of a signal from the receiving device, the connection event is preferably closed in order to save power, and therefore, preferably, no re-transmission takes place in the same connection event during which the original transmission of the data packet was performed.

<FIG> shows another exemplary timing diagram <NUM> illustrating the new method of wireless communication of data sets with different priorities wherein the maximum number of re-transmissions of a high priority data packet in a new connection event is set to one. <FIG> illustrates operating conditions, e.g., of the wireless communication link <NUM> in <FIG>, with a certain amount of interfering electromagnetic noise in the relevant data channels such that transmission of individual data packets or data sets from the transmitter to the receiver fails from time to time.

As in <FIG>, consecutive connection events of the wireless communication link are indicated by Ci1, Ci2, Ci3, Ci4, etc., along the time axis t. The skilled person will understand that the illustrated adjacent connection events, such as Ci1 and Ci2, may be separated by a considerable sleep time period or inactive period for example up till <NUM> seconds in accordance with Bluetooth LE protocol.

In the first connection event Ci1, high priority data packet A1 is transmitted for the first time with limited success. The receiving device receives a data packet; however, a transmission error is detected, e.g. with CRC, and the receiving device transmits a not-acknowledge signal or data packet "Nack", possibly with the previously discussed MD bit set to "<NUM>", to request a re-transmission of the data packet A1 within the same connection event Ci1. Thus, the data packet A1 is re-transmitted within the same connection event Ci1; however, in this example, also with the same result as before with detection of a transmission error in the receiving device. Optionally, the receiving device does not transmit the second "Nack" signal or packet in order to save power.

Subsequently, a first re-transmission in a subsequent connection event Ci2 is performed; however, still with detection of a transmission error in the receiving device and transmission of a not-acknowledge signal or data packet "Nack", possibly with the previously discussed MD bit set to "<NUM>", to request a re-transmission of the data packet A1 within the same connection event Ci2. Thus, the data packet A1 is re-transmitted within the same connection event Ci2; however, again with the result of detection of a transmission error in the receiving device.

As a result, the data packet A1 is flushed due to time out, and the transmitting device acquires the next high priority data packet A2 for transmission in connection event Ci3. The transmission is successful, and the receiving device acknowledges receipt of data packet A2. No data packets with a lower priority is awaiting transmission in the transmitting device, so that the MD bit is set to "<NUM>" in the header of the second high priority data packet A2, and thus, the receiving device skips the fourth connection event Ci4 thereby saving power.

In the illustrated example, the predetermined maximum number of re-transmissions in a new connection event of a high priority data packet is one, but a higher maximum value may be selected, for example <NUM>, <NUM> or <NUM>. Also, the transmitting device may be configured to re-transmit a low priority data packet until acknowledgement of receipt is received from the receiving device, i.e. without limiting the number of re-transmissions to a selected maximum number.

Limiting the number of re-transmissions of a particular high priority data packet to the selected maximum number facilitates maintenance of the real-time property of received data packets at the receiving device. If the number of re-transmission of a particular high priority data packet reaches the predetermined maximum number without success, the transmitting device flushes or overwrites the particular high priority data packet with a new high priority data packet that, e.g., represents current audio content, and proceeds to transmit the new high priority data packet. The loss of the former high priority data packet may be concealed by the receiving device by a suitable packet loss concealment algorithm executed, e.g., by the hearing loss processor <NUM> of the left hearing aid.

In the event that a transmitted data packet is lost, the receiving device does not transmit any signal, such as the "Nack" signal, and in absence of a signal from the receiving device, the connection event is preferably closed in order to save power, and therefore, preferably, no re-transmission takes place in the same connection event as the original transmission of the data packet.

In the timing diagram of <FIG>, a high priority data packet A1 is transmitted successfully in connection event Ci1, and the receiving device acknowledges safe receipt by transmission of an acknowledgement signal or packet "Ack" to the transmitting device. The MD bit is set to "<NUM>" in the header of the first high priority data packet A1 indicating that a new low priority data packet D1 is awaiting transmission to the receiving device, and the transmitting device proceeds to transmit the low priority data packet D1 during the same connection event Ci1. The transmission is successful and the receiving device acknowledges receipt. Since the receiving device successfully received both the high priority data packet A1 and the low priority data packet D1, the receiving device skips the second connection event Ci2, whereby power in the receiving device is saved.

In connection event cl3, a second high priority data packet A2 is transmitted successfully to the receiving device, and the receiving device acknowledges receipt. The MD bit is set to "<NUM>" in the header of the second high priority data packet A2 indicating that a new low priority data packet D2 is awaiting transmission to the receiving device, and the transmitting device proceeds to transmit the low priority data packet D2 during the same connection event Ci3. The transmission of the second low priority data packet D2 is unsuccessful and the receiving device does not acknowledge receipt as indicated by the dashed box "Nack". In the event that the data packet D2 is lost, the receiving device does not transmit anything to the transmitting device, and in the event that the receiving device receives the data packet D2, but a transmission error is detected, the receiving device may transmit the "Nack" signal.

Since no high priority data sets or packets are awaiting transmission to the receiving device, the transmitting device proceeds to make a re-transmission of the second data packets D2 with low priority during the fourth connection event Ci4, and this time with success.

In <FIG>, a high priority data packet A1 is transmitted successfully in connection event Ci1, and the receiving device acknowledges safe receipt by transmission of an acknowledgement signal or packet "Ack" to the transmitting device. The MD bit is set to "<NUM>" in the header of the first high priority data packet A1 indicating that a new low priority data packet D1 is awaiting transmission to the receiving device, and the transmitting device proceeds to transmit the low priority data packet D1 during the same connection event Ci1. The transmission of low priority data packet D2 fails, and the receiving device does not acknowledge receipt as indicated by the dashed box "Nack". In the event that the data packet D1 is lost, the receiving device does not transmit anything to the transmitting device, and in the event that the receiving device receives the data packet D1, but a transmission error is detected, the receiving device may transmit the "Nack" signal.

Since no high priority data sets or packets are awaiting transmission to the receiving device, the transmitting device proceeds to make a re-transmission of the second data packet D1 with low priority during the second connection event Ci2; however, transmission fails in connection event Ci2. In connection event Ci3, a new high priority data packet A2 is transmitted unsuccessfully and re-transmitted as already explained above. Subsequent to the successful re-transmission of the high priority data packet A2, the low priority data packet D1 is finally successfully transmitted to the receiver in connection event Ci4.

<FIG> illustrates that the priority of a data packet that is awaiting re-transmission may be increased, e.g. as a function of the number of failed re-transmission attempts, and may obtain a priority higher than a data packet with a high priority.

Subsequent to the failed re-transmission, the priority of the data packet D1 is set to the highest value, and the transmitting device proceeds to make a re-transmission of the second data packet D1 now with high priority during the second connection event Ci2; however, transmission fails in connection event Ci2. In connection event Ci3, transmission of data packet D1 again fails, but in connection event Ci4, D1 is finally successfully transmitted to the receiving device. Further, a new high priority data packet A2 is transmitted successfully to the receiving device in the same connection event Ci4.

<FIG> shows a flowchart of an example of the new method.

The illustrated method <NUM> may be utilized for streaming audio, such as speech and/or music, from a transmitter, e.g. accommodated in a smartphone that is configured for operation in compliance with a Bluetooth LE standard protocol, to a receiver, e.g. accommodated in a hearing aid or headphone or another hearing device.

According to the illustrated method <NUM>, when streaming has been requested, the audio data to be streamed are packed into audio data packets, throughout the present disclosure also denoted audio data sets, in accordance with the Bluetooth LE standard protocol, and the audio data packets are accorded a high priority so that transmissions of audio data packets are not prevented by transmissions of other data, such as control data, e.g. a command to turn up the volume of the hearing device.

The audio data packets are transmitted in sequence by.

Preferably, audio data packets of the streamed audio have a high priority ensuring transmission of the audio data packets before transmission of other types of data sets with lower priorities in order to ensure high fidelity, or at least acceptable, quality of sound generated based on the streamed audio.

<FIG> shows a flowchart of another example <NUM>' of the new method that in addition to the steps of method <NUM> illustrated in <FIG> includes.

In step <NUM>: including in the at least one data packet information, e.g. encoded in a data byte, or a data bit, whether or not a data set with the second priority is awaiting transmission to the receiver, and.

<FIG> shows a flowchart of another example <NUM>" of the new method that in addition to the steps of method <NUM> illustrated in <FIG> includes.

The additional method steps <NUM>, <NUM>, and <NUM> may also be added to the method <NUM>' as shown in <FIG> showing a flowchart of yet another example <NUM>‴ of the new method.

The allowed number of attempted re-transmissions of other types of data may be different from one or may not be limited, i.e. a maximum value different from two, or no maximum value, or an infinite maximum value, may be allocated to various other types of data.

Different types of data may have different predetermined maximum values of attempted re-transmissions, e.g. audio data sets may have the maximum value two while the maximum value for data sets with a lower priority than the priority of the audio data sets may have larger maximum values.

Claim 1:
A method of wireless transmission of data packets in compliance with a Bluetooth low energy standard by a hearing aid (<NUM>) comprising a transmitter (<NUM>), the method comprising:
transmitting a first data packet (A1) of a first data category and having a first priority from the transmitter (<NUM>) for reception by a receiver (34R) in a first connection event (Ci1),
in presence of the acknowledgement of receipt of the first data packet (A1) from the receiver, transmitting a second data packet (D1) of a second data category with a second priority, which is lower than the first priority, from the transmitter (<NUM>) to the receiver in the first connection event (Ci1),
in absence of acknowledgement of receipt of the first data packet (A1) from the receiver, re-transmitting the first data packet (A1) at most for a predetermined maximum number of times in the first connection event (Ci1).