DESC:DESCRIPTION
FIELD OF INVENTION
[0001] Embodiments of the present disclosure relate to Electronic system and more
particularly relate to method, system and apparatus for diagnostics of Hearable.
RELATED ART
[0002] Hearable generally refers to an electronic device adopted or configured to operate
wirelessly to produce stereo/audio signals. The Hearable also refers to True wireless stereos
(TWS) that are adopted to fit to human ear. The hearable is of size and shape that reciprocate
with the human ear for externally wearing on the outer ear. Hearable is also often referred to
as Ear buds, electronic in-ear device etc in the known art. The hearable comprises speaker(s)
to produce the sound and microphone(s) to capture the sound besides other supporting
electronic circuitry and power supply (battery). Hearable comes in pair matching the pair of
human ears. Pair of Hearables together referred to as Hearable.
[0003] As is well known in the art, the Hearable is wirelessly coupled (using wireless
communication channel such as Bluetooth, for example) to mobile device such as mobile
phones, tablet, laptop, etc. Thus, Hearable operates as an extended audio input and output
(I/O) device of the mobile device without requiring holding the mobile phone close to the
human ear and/or requiring any wired connectivity with the mobile device. Hearable therefore
are configured to operate in a system as extended audio input and output device.
[0004] The system of Hearable generally comprises the hearable(s), mobile device and
optionally may including a casing as is well known in the art. The casing provides multiple
functionalities such as enabling charging of the battery providing power supply to the
Hearable and safe keeping of the hearable. The casing comprises the electronic circuitry and
interface points to provide the required functionality. Conventionally, the mobile device is
configured to interface with the Hearable to determine availability of power level (battery
charge) or level charge in the battery and to detect if the hearable is properly placed in the case
for effective charging. However, it may be often required to detect, monitor and correct other
operations of the Hearable by the user to avoid returning of the hearable for service thereby to
enhance the usage/utility of the Hearable and it stops creating e-waste. Thus there is a need for
diagnosing the Hearable for identifying and/or rectifying any issues with Hearable.
SUMMARY
[0005] According to an aspect, a system comprising a mobile device and a hearable
configured to operate as extended audio input and output device to the mobile device, the
3
hearable is adaptable to human ear on a wireless communication network, characterized in
that, the mobile device comprising diagnostic unit and a user interface, the diagnostic unit
operative to diagnose functioning of one or more elements in the hearable and the user
interface enabling participation of user in the diagnostic process. In that, the hearable
comprising SoC, CPU (Smart Diagnostic Software), Hardwares such as microphone, speaker,
and battery, in that the said one or more elements are the microphone, speaker, Bluetooth
stack, and battery.
[0006] According to another aspect, the mobile device comprises memory unit storing sample
voice signal with amplitude and the diagnostic unit is configured to receive a test voice from
the Hearable and compare the test voice with the sample voice to determine the functioning of
the microphone.
[0007] According to another aspect, the memory unit storing sample text and a corresponding
voice reading the said sample text and user interface configured to receive user interface
indicating the consent to have heard the sample text when the voice recording is played on the
hearable.
[0008] According to another aspect, the mobile device comprises battery diagnostic unit
operative to determine the rate of battery drain from the battery charge data collected at two
different time instant.
[0009] According to yet another aspect, a method in a mobile device and hearable comprising
the mobile device initiating the diagnostic process, providing a diagnostic user interface for
giving and receiving set of instructions to and from the user for performing diagnostic
operations, performing a set of operations to determine the working status of the Hearable, the
hearable receiving instruction from mobile device and performing diagnostic operations
corresponding to the received signal and mobile device presenting the status of the Hearable
on the user interface.
[0010] According to another aspect, the method of diagnosing a speaker in the hearable
comprising presenting a message on a user interface in the mobile device, instructing user to
input a predefined voice input, capturing the voice input from microphone on the hearable,
transmitting the captured voice input to the mobile device, receiving the voice input from the
hearable and comparing with a reference data and indicating success when the comparison
result is greater than a threshold.
[0011] According to yet another aspect, the method of diagnosing a microphone in the
hearable comprising presenting a message on a user interface in the mobile device, instructing
user to hear a predefined voice, sending an audio file to the hearable and playing the audio file
4
on the speaker of the hearable, receiving an input from user and indicating diagnostic as
success when the user input is “yes” and not success when the user input is “No”.
[0012] According to yet another aspect, the method of diagnosing Bluetooth connectivity of
the hearable comprising determining if the Hearable is already paired with the mobile device,
pairing the Hearable with the mobile device primary unit if it is not already paired, performing
call back operation to determine the connectivity and presenting result as “successful” if the
call back is positive and as “not successful” otherwise
[0013] According to yet another aspect, a fix button is provided to perform factory reset
operation to resolve any specific issues associated with one or more elements such as the
microphone, speaker, Bluetooth stack, and Battery of Hearable that are otherwise not resolved
through any of the above operations.
BRIEF DESCRIPTION OF DRAWINGS
[0014] FIG.1 is an example system for diagnosing Hearable.
[0015] FIG. 2 is a block diagram illustrating the manner in which the Mobile device and the
Hearable may conjunctively operate to diagnose Hearable.
[0016] FIG. 3 is a block diagram of an example Hearable in one embodiment.
[0017] FIG. 4 is a block diagram of an example mobile device in one embodiment.
[0018] FIG. 5 is a block diagram illustrating the manner in which microphone of Hearable is
diagnosed for any operational issues.
[0019] FIG. 6 is a block diagram illustrating the manner in which speaker in the Hearable is
diagnosed for any operational issues.
[0020] FIG. 7 is a block diagram illustrating the manner in Diagnostics of Bluetooth
communication is performed in an embodiment.
[0021] FIG. 8A is a block diagram illustrating the diagnostic of battery in the Hearable.
[0022] FIG. 8B illustrates the manner in which the battery diagnostic unit 804 may determine
the health of the battery in one embodiment.
[0023] FIG. 9 is a block diagram illustrating the manner in which the diagnostic unit 402 may
be configured to perform corrective operations when the diagnostic of Hearable is determined
to not success in an embodiment.
[0024] FIG. 10A-10F illustrates the exemplary user interface in an embodiment.
DETAILED DESCRIPTION OF THE PREFERRED EXAMPLES
[0025] FIG.1 is an example system for diagnosing Hearable. The system 100 is shown
comprising Hearable 110, Casing 120, mobile device 130, remote server 140 and
communication channels 150 and 160. Each element is further described below.
5
[0026] The communication channel 150 and 160 represents communication channels for short
distance and long distance respectively. In that, the communication channel 150 and 160 is a
wireless channel that may comprise any wireless communication channel adopted to operate in
compliance with the standards set forth as in Wi-Fi, Bluetooth etc. In one embodiment the
channel 150 is a Bluetooth wireless channel. The channel 160 may comprise one of cellular
channel for mobile communication like GSM, CDMA etc, radio frequency communication
channel, satellite communication channel, optical fibre communication channel and
combination thereof.
[0027] The remote server 140 receives data from the mobile device over channel 160 for
central storage and provides several services based on the stored information as further
described in the sections below. The remote server may be deployed as standalone computer,
shared computer, cloud resource, plurality of computer machines etc.
[0028] The casing 120 provides for positioning and safe keeping of Hearable when required to
be charged and or not in use. Accordingly, the casing may comprise electronic circuitry and
interface connectors to enable charging of Hearable. In one embodiment, the casing may
exchange information with mobile device over channel 150. Thus, casing may comprise
additional circuitry for transmitting and receiving data to/from the mobile device, Hearable
and processing the data thereof.
[0029] The Hearable 110 receives and transmits wireless signal carrying information/data
from and to the mobile device 130 on the channel 150. The Hearable 110 suitably converts the
received information to corresponding audio signal to produce sound/audio. Similarly, the
Hearable 110 converts the audio signal received through microphones to digital information
and transmits to the mobile device. In one embodiment, the information may also comprise
data to control, configure and monitor operation of the Hearable 110. Optionally, Hearable
110 may be configured to exchange information with the casing 120 when placed in the casing
120. In that case, the Hearable 110 may establish metal contact/wired contact (Not shown)
with the casing to exchange information and also to charge battery. Alternatively, Hearable
110 may charge the battery through any known contactless battery charging mechanism.
[0030] The mobile device 130 operates to transmit and receive data/information over channel
150 to/from Hearable 110. The data/information may comprise audio information such as
speech, voice, music, etc and additionally may contain data for managing operation/
configuration of Hearable. In one embodiment, the Mobile device 130 is configured to
determine the operational status (working conditions) of the Hearable 110 (referred to as
diagnosing, diagnostic, diagnosis and in its applicable language forms). The mobile device and
6
the Hearable exchange information to facilitate the Diagnosis of the Hearable through the
mobile device. In certain embodiment, the Mobile device and the Hearable may enter into a
diagnostic mode of operation (set of activities) either automatically or manually. In case of
automatic, the diagnostic activities may be performed in parallel with the functional mode of
operation (operating to serve the intended purpose of the Hearable). For example, the both
Mobile device and the Hearable may conjunctively operate at a predefined time instance for
diagnosis or at an instance of receiving a specific signal from the mobile device/Hearable or
on detection of being idle (no functional operations are being performed) etc. In case of
manual initiation of diagnostics, the user may instruct the mobile device to perform
diagnostics of Hearable through mobile device user interface. The manner in which the Mobile
device and the Hearable operate in conjunction to diagnose the functional status (readiness to
perform desirable operation) or issues if any on the Hearable, is further described below.
[0031] FIG. 2 is a block diagram illustrating the manner in which the Mobile device and the
Hearable may conjunctively operate to diagnose Hearable. In block 210, the mobile device
initiates the diagnostic process. The mobile device may send a particular identifier data
(signal) to the Hearable indicating the initiation of diagnostic mode of operation. The identifier
signal may be sent over channel 150. In block 220, the mobile device provides a diagnostic
user interface for giving/receiving set of instructions to/from the user for performing
diagnostic operations. The user interface provided to user may contain instruction to perform
certain participating actions during the diagnosis. The participating actions may include
providing audio inputs, acknowledging certain audio outputs, performing actions as indicated
on the user interface. In certain embodiment, the user interface may be provided for user to
initiate the diagnostic operation.
[0032] In block 230, the mobile device performs set of operations to determine the working
status of the Hearable. In that, the set of operation may include, allowing user to input the
instructions/data on the user interface, sending and receiving signals to and from Hearable etc.
In block 240, the Hearable receives instruction/command signal from mobile device and
perform diagnostic operations corresponding to the received signal. The diagnostic operation
may include activating components, playing a predefined audio, capturing audio signals
through microphone, executing set of instructions corresponding to one or more protocol like
Bluetooth protocol etc. The Hearable may send the result of the diagnostic operations to the
mobile device. The operation of block 220, 230 and 240 are repeated to determine working
condition of number of features and/or hardware elements in the Hearable. The mobile device
may initiate the repeat operation (process) for each feature or the repeat operation may be
7
automatically linked to the result of one diagnostic operation, or the user may initiate
diagnosis of multiple features one after another.
[0033] In block 250, the mobile device presents the status of the Hearable on the user
interface. In block 260, the mobile device performs operations to correct the error diagnosed in
the steps 220-240. For example, the mobile device may present the set of instructions on the
user interface for corrective measures to correct the error in the Hearable. Along with the
corrective measures, at last it displays the fix button to resolve the specific issues by sending
the factory reset command. The correction measure may include repetition of operations of
block 220-240. The manner in which Hearable is configured to diagnose operation of its one
or more element is further described below.
[0034] FIG. 3 is a block diagram of an example Hearable in one embodiment. The Hearable
300 is shown comprising primary unit 301, Diagnostic unit 302 and Audio unit 303. Each
block is further described below.
[0035] The primary unit is shown comprising antenna 310, Encoder and Decoder 320, ADC
330, amplifier 340 and 360, and DAC 350. In that, the antenna 310 receives/transmit signal
over wireless channel (channel 150, for example). The antenna 310 may comprise analog front
end circuitry (not shown) that may operate to signal conditioning, down/up convert,
demodulate etc. In one embodiment the antenna 310 and the associated analog circuitry is
configured to transmit and receive Bluetooth signal.
[0036] The encoder and decoder unit 320 encodes and decodes the data for transmission over
the antenna 310 and to extract data from signal received on the antenna 310 respectively. In
one embodiment, the encoder and decoder may be implemented to encode and decode the
signal complying with short distance communication protocol like Bluetooth protocol. In that,
the unit 320 may comprise buffer for storing the decoded data stream and/or data stream for
encoding and transmission. The decoded data is provided to the DAC 350 for converting the
digital data stream to corresponding analog signal (electric signal) and provided to amplifier
360. Similarly, ADC 330 converts the analog signal received from another amplifier 340 to
digital data stream for encoding by unit 320. The ADC 330, DAC 350 and amplifiers 340 and
360 are implemented using any know technologies and operation of the same is not described
in detail for brevity and to avoid obscuring the invention.
[0037] The audio unit 303 is shown comprising microphone 380 and the speaker 385. The
microphone (MIC) 380 operates to capture audio/sound signal (speech/music) and generate
analog electric signal that is provided to ADC 330 (through amplifier 340) for converting
analog audio signal to corresponding digital signal. Similarly, the speaker 385 operates to
8
produce audio/sound signal (speech/music) from analog electric signal that is received from
DAC 350 (through amplifier 360).
[0038] Thus, the microphone 380, amplifier 340, ADC 330, unit 320 and antenna 310 form a
path 391 that transmit the signal received on microphone over wireless channel 150. Similarly,
the speaker 385, amplifier 360, DAC 350, unit 320 and antenna 310 form other path 392 that
operate to produce sound signal corresponding to the signal received over wireless channel
150. Though not explicitly described, it is understood that the path 391 and 392 may comprise
other elements/circuitry for signal conditioning, enhancing the audio quality, control
mechanisms like volume control, detections mechanism like tap detection, signal processor to
detect embedded multiple signals, routers to route the signal to other elements etc. Thus,
primary unit 301 and the audio unit 303 together operate to provide a basic operation of
Hearable as extended wireless ear phone as desired. In certain embodiment, the primary unit
301 may also comprise battery charge level measuring circuitry that may determine the battery
charge level and embed the data into the data stream for encoding by unit 320. Accordingly,
the mobile phone, receiving such battery charge information, is configured to display the level
of battery charge on the screen.
[0039] The diagnostic unit 302 operates to perform diagnostic operations on the Hearable in
accordance with the instructions received from the mobile device. The diagnostic unit 302 is
shown interfaced to the primary unit 301 on interface path 399. The interface 399 may include
but not limited to: placing certain data stream on the buffer for encoding and decoding by the
encoder and decoder unit 320, accordingly, a sample voice signal in digital form (test voice
signal) may be placed on the buffer on the path 392 for playing out on the speaker 385, the
interface 399 may also include a path to encoder and decoder for exchanging control signal
and data etc. The diagnostic unit 302 may comprise a processor, and buffer to store predefined
commands and data sets for executing the operations for diagnosing the operation of elements
in the primary unit 301. For example, the diagnostic unit 302 may determine the operational
status of elements 310-360 and audio units 303 (380 and 385).
[0040] FIG. 4 is a block diagram of an example mobile device in one embodiment. The
mobile device 400 is shown comprising primary unit 401, Diagnostic unit 402 and User
Interface 403. Each block is further described below.
[0041] The primary unit 401 is shown comprising encoder/decoder 410 and antenna 420. The
encoder/decoder 410 operate similar to the unit 320 described in the sections above. In certain
embodiment, the encoder/decoder 410 may be implemented as master and the unit 320 may be
implemented as slave unit whenever a communication protocol demands such configuration.
9
Both the unit 320 and 410 are implemented to reciprocate in encoding, decoding, modulation
and frequency of operation adopted for transmission and reception of data between Mobile
device 400 and Hearable 300 over channel 150. In certain embodiment, for example when the
channel 150 is a Bluetooth channel, the units 320 and 410 may comprise buffer referred to as
Bluetooth stack operative to establish active communication channel for data transfer. The
buffer (not shown) may comprise Bluetooth stack implemented as part of the mobile device
and may interact with the operating system of the device optionally. The antenna 320 is shown
coupled to the encoder/decoder 410 for transmission and reception of the signal received from
unit 410 and channel 150 respectively. As is well known, the primary unit 401 is coupled to
the other source of data (external units/applications) for transfer of audio signal to Hearable
300. For example, on establishing a dedicated communication channel between 300 and 400
(often referred to as “Pairing”), the external applications operative on the mobile devices may
route the audio signals through the primary unit 401 and 301 for playing/receiving on speaker
385 and from the microphone 380 respectively.
[0042] The diagnostic unit 402 operates to diagnose the functioning (operational status) of
Hearable 300. In one embodiment, the diagnostic unit 302 is configured to reciprocate with the
diagnostic unit 402. In certain other embodiment, the diagnostic unit 402 may directly
determine operational status of one or more elements of the Hearable 300. The diagnostic unit
402 may generate command signals, sample data signal and other predetermined diagnostic
protocol signals for transmission through primary unit 401 and capture the response to
determine the health (diagnose) of several elements in the Hearable (Hearable as a whole).
[0043] The user interface 403 enables a user to input certain data (referred to as user
command) and to receive data (referred to as user messages) during the diagnostic operation.
The user interface 403 provides the instruction for user to participate in the diagnostic
procedure and presents several buttons for user to provide the user choice /desired input for
conduction of diagnostic operation. In one embodiment, the diagnostic unit 402 generates the
instruction and control signal to user interface 403 to generate messages and buttons to receive
commands from the user. In that, user interface 403 may generate graphical representation and
animations to convey the message to the user and enable user to more effectively participate in
the diagnostic process. Accordingly, the diagnostic unit 402, independently or in collaboration
with unit 302 and the user interface 403 operates to diagnose the working of Hearable 300. As
an example and not limiting thereto, the manner in which the diagnostic unit 402 determines
the operating status of microphone 380, speaker 385, Bluetooth connectivity and battery health
is further described below.
10
[0044] FIG. 5 is a block diagram illustrating the manner in which microphone of Hearable is
diagnosed for any operational issues. In block 510, the Diagnostic unit 402 presents diagnostic
user interface for receiving user input to initiate the diagnostic of microphone. The user
interface may comprise one or more screens with instructions, buttons for user to indicate the
choice and audio/video indicators. The user interface may comprise multiple screens that
change as the diagnostic process progresses. Alternatively, all required messages and user
selections may be provided on a single screen.
[0045] In block 520, the Diagnostic unit 402 receives the user input to perform diagnostic of
microphone. The user may select an option or press a button to provide the input. The activity
of user on the screen is captured and provided to the diagnostic unit 402. In block 530, the
Diagnostic unit 402 begins the test sequence to determine the working condition of the
microphone. In that, the diagnostic unit may perform several preliminary checks like current
status of the Hearable, working of communication channel, etc. For example, if the Hearable
is placed in the case, the diagnostic unit may print message to remove and wear the Hearable
for diagnostic of microphone. Accordingly, the Diagnostic unit 402 may perform preliminary
checks and also send test signals to know if the Hearable and mobile Device are ready for
conducting the diagnostic operations.
[0046] In block 540, the Diagnostic unit 402 presents a message on the user interface
instructing user to input a predefined voice data. In that, the timing of providing the voice
input through the Hearable microphone (being tested) may be controlled through beep sound
or any other time indicator graphics on the user interface. In block 550, the Hearable captures
the voice input from microphone 380. User may be input a predefined sentence or may readout
a sentence provided on user interface to provide the voice input. In one embodiment, a
predefined sentence is printed on the user interface and the user is instructed to read the
sentence after a beep sound. Accordingly, the diagnostic unit may generate a beep sound
through the speaker for user to start reading the sentence aloud. The voice is captured through
the microphone 380.
[0047] In block 560, the Hearable transmits the captured voice data over channel 150 to the
mobile device. The captured voice may be digitised and transmitted through primary unit 301.
In block 570, the Diagnostic unit 402 receives the voice data from Hearable and compares
with the reference data in the memory. In one embodiment, the received signal may be
decoded through primary unit 401. The comparison may be performed in digital domain or
analog domain. In one embodiment, a local storage buffer may store number of reference
voice data with known amplitude level. The received voice signal is compared with the
11
reference voice data. In block 580, the Diagnostic unit 402 presents the diagnostic result as
success when the comparison result indicate a match greater than a threshold and in block 590,
the Diagnostic unit 402 presents the diagnostic result not success otherwise.
[0048] FIG. 6 is a block diagram illustrating the manner in which speaker in the Hearable is
diagnosed for any operational issues. In block 610, the Diagnostic unit 402 presents diagnostic
user interface for receiving user input to initiate the diagnostic of Speaker 385. The user
interface may comprise one or more screens with instructions, buttons for user to indicate the
choice and audio/video indicators. The user interface may change as the diagnostic process
progresses. Alternatively, all required messages and user selections may be provided on a
single screen.
[0049] In block 620, the Diagnostic unit 402 receives the user input to perform diagnostic of
Speaker. On the user interface, the user may select an option or press a button to provide the
input. The activity such as user tapping on the “smart diagnostic of speaker” button on the
screen is captured and provided to the diagnostic unit 402. In block 630, the Diagnostic unit
402 begins the test sequence to determine the working condition of the Speaker. In that, the
diagnostic unit may perform several preliminary checks like current status of the Hearable,
working of communication channel, etc. For example, if the Hearable is placed in the case,
the diagnostic unit may print message to remove and wear the Hearable for diagnostic
operation. Accordingly, the diagnostic unit 402 may perform preliminary checks and also send
test signals to know if the Hearable and mobile device are ready for conducting the diagnostic
operations (like pairing is already done or not).
[0050] In block 640, the Diagnostic unit 402 displays a message on the user interface
instructing user to hear a predefined sound/voice from the Hearable and indicate yes or no on
the screen. For example, the user interface may display the text “are you able to hear the Hello
Boat” tone on your Hearable along with a tone recognition icon. In that, the timing of
providing the text message on user interface and the sending a sample sound signal to the
Hearable Speaker (being tested) may be controlled through visual timer or any other time
indicator graphics on the user interface.
[0051] In block 650, the Diagnostic unit 402 sends the audio file (may be in digital format like
MP3) to Hearable through preliminary units 301 and 401. Hearable preliminary unit 301 plays
the audio signal on the speaker 385. In certain embodiment, the audio signal may be locally
stored for playing at the instruction of mobile device, without having to transmit the audio
signal over channel 150. The audio file may contain the voice uttering a known text as shown
12
on the user interface. For example the audio signal may be a file carrying “Hello” sound
signal.
[0052] In block 660, user interface 403 receives an input from user. In that user may provide
an input on the user interface if the voice as played is heard as displayed or not. Accordingly,
the diagnostic unit may capture the user input (yes/no) on the user interface after certain time
period (say 13-14 seconds) from sending the voice signal. Optionally, the user interface may
also provide an option to perform the operations as in 650 and 660 again. In that, case, user
interface may display a button “retry” for user to repeat the process as in 650 and 660.
Accordingly, a predetermined number of times (for example say 2 times) the speaker may be
tested before disabling the “retry” button. Alternatively, “retry” button may be enabled only
when the user input is “No”.
[0053] In block 670, the Diagnostic unit 402 presents the diagnostic result as success when the
user input is “yes” and not success when the user input is “No”. In certain embodiment, the
Diagnostic unit 402 may present learning and training information to the user on the user
interface.
[0054] Similarly, FIG. 7 is a block diagram illustrating the manner in Diagnostics of Bluetooth
communication is performed in an embodiment. In block 710, the Diagnostic unit 402 presents
diagnostic user interface for receiving user input to initiate the diagnostic of Bluetooth
connectivity. In block 720, the Diagnostic unit 402 receives the user input to perform
diagnostic of Bluetooth connectivity. On the user interface, the user may select an option or
press/tap a button to provide the input. The activity such as user tapping on the “smart
diagnostic of Bluetooth” button on the screen is captured and provided to the diagnostic unit
402. In block 730, the Diagnostic unit 402 begins the test sequence to determine the
connectivity of Bluetooth. At first, the Diagnostic unit 402 may interact with operating system
of the mobile device and scan availability of Bluetooth devices in the connectivity range. The
Diagnostic unit 402 may filter the scanned devices to show only the Hearable that is being
diagnosed on the user interface.
[0055] In block 740, the Diagnostic unit 402 determines if the Hearable is already paired with
primary unit 401. For example, the Hearable may be already paired with the primary unit 401
for desired operation like playing music, voice etc. In block 750, the diagnostic unit 402 pairs
the Hearable with the primary unit if it is not already paired. For example, the Diagnostic unit
402 may initiate sequenced packet protocol (SPP) connection protocol for pairing. In block
760, the diagnostic unit 402 may perform call back operation to determine the connectivity.
13
[0056] In block 770, the Diagnostic unit 402 presents the diagnostic result as “successful”
when the call back operation is successfully completed and presents the diagnostic result as
“not successful” otherwise. In certain embodiment, the Diagnostic unit 402 may present
learning and training information to the user on the user interface.
[0057] In one embodiment, the diagnostic unit 402 is configured to determine the health of
the battery in the Hearable. The manner in which the health of the battery may be diagnosed is
further described below.
[0058] FIG. 8A is a block diagram illustrating the diagnostic of battery in the Hearable. As
shown there, the battery 810 is coupled to primary unit 301 through the ADC 820.
Accordingly, the voltage levels of the battery 810 is measured and digitised by the ADC 820.
The digital value is provided to primary unit 301 for encoding and transmitting to mobile
device. The diagnostic unit 302 is operative to control the measurement and signal
transmission of the battery information. For example, the primary unit 301 may activate the
ADC 820 to digitise the value on the path 812 and provide the digitised value on path 824.
Similarly, the diagnostic unit 302 may also send control signal to primary unit 301 (encoder
and decoder) to transmit the battery charge information as Bluetooth data packet.
[0059] The mobile device 400 is shown comprising battery diagnostic unit 804 (may be
implemented as part of the diagnostic unit 402 or may be implanted as independent unit) and
memory 830. The memory 830 stores the data received from battery 810 with time stamp. For
example, the memory may store the history data of the battery charge percentage at a
corresponding time instances. The battery health diagnostic unit 804 is operative to determine
the health of the battery using the current data received from the battery 810 and the history
data stored in the memory 830.
[0060] FIG. 8B illustrates the manner in which the battery diagnostic unit 804 may determine
the health of the battery in one embodiment. In block 850, the battery diagnostic unit 804
fetches the percentage of battery charge from battery 810. The percentage of charge and the
time stamp is stored in the memory. In block 860, battery diagnostic unit 804 waits for a
minimum time period (for example, the minimum time period may be 2 minutes). In block
870, battery diagnostic unit 804 fetches the battery charge percentage after elapsing the
minimum time period. In block 880, battery diagnostic unit 804 determines the rate of draining
of battery based on the charge percentage before and after the time period. In block 890,
battery diagnostic unit 804 presents the result as health is good if the rate of drain is less than a
threshold (for example say 3%) and as not good if the rate of drain is determined to be greater
than the threshold.
14
[0061] FIG. 9 is a block diagram illustrating the manner in which the diagnostic unit 402 may
be configured to perform corrective operations when the diagnostic of Hearable is determined
to not success in an embodiment. In block 910, the diagnostic unit 402 receives a user input to
resolve the issue determined to be present in one or more diagnostic operations. In block 920,
the diagnostic unit 402 sends factory reset command to the Hearable through primary unit 401.
In block 930, the diagnostic unit 302 in the Hearable 300 receives the command for resetting
the Hearable to factory rest mode. In block 940, the diagnostic unit 302 resets the configured
parameters to default settings/values stored in the memory. In certain embodiment, the
diagnostic unit 302 may erase the history data such as list of already paired devices etc. In
block 950, the diagnostic unit 302 sets the Hearable into pairing mode.
[0062] FIG. 10A-10F illustrates the exemplary user interface in an embodiment. In that, the
FIG. 10A-10C provides general instruction to a user on certain requirements that needs be met
for performing the diagnostic operation. For example, the FIG. 10A illustrates that, mobile
device must be enabled for Bluetooth, internet and location services such the device may
access channels 150 and 160. The FIG. 10B illustrates the requirements that the Hearable
battery is required to be charged for efficient diagnostic operations. Similarly, The FIG. 10C
illustrates the requirements that the Hearable be placed in the case for diagnostic operation.
[0063] FIG.10D provides the user interface for the user to initiate diagnostic operations
through mobile device. Thus, the user may tap on the button 1030 to initiate the diagnostic
operation. FIG.10E provides the user interface for user to select an element in the Hearable for
diagnostic. For example, elements 1060A-D may be selected for diagnostic. Further, user
interface may also indicate “success” or “issues” though tic 1070A or exclamation/cross
1070B marks respectively. FIG.10E provides the user with additional information to resolve
the issues when the diagnostic result is negative.
[0064] Accordingly the mobile device may perform diagnostic of Hearable and also perform
corrections measure without having to take the Hearable service centre and also not requiring
discarding the Hearable for issues. Thus, avoiding returning of the hearable for service thereby
to enhance the usage/utility of the Hearable.
[0065] In certain embodiment, the result of diagnostic operations may be stored in the remote
server 140 and the history of Hearable status and usage may be maintained as ready reckoner.
In curtain other embodiment, the remote server 140 may send a control signal to diagnostic
unit 402 to perform diagnostic of hearable. In that, the remote server may be configured to
initiate the diagnostic operation of the hearable at a predetermined time points.
15
[0066] Further, the remote server 140 may also be configured to determine the user activity
and initiate the diagnostic operation when the Hearable is placed in the casing. In that, the
casing 120 is enabled with additional speaker and microphone for providing test voice input
and also capture the test voice out from the speaker 385 and microphone 380 avoiding user
participation.
[0067] While various embodiments of the present disclosure have been described above, it
should be understood that they have been presented by way of example only, and not
limitation. Thus, the breadth and scope of the present disclosure should not be limited by any
of the above-discussed embodiments but should be defined only in accordance with the
following claims and their equivalents. ,CLAIMS:I/We Claim,
1. A system comprising:
a mobile device and a hearable configured to operate as extended audio input and
output device to the mobile device, the hearable is adaptable to human ear on a wireless
communication network,
characterized in that,
the mobile device comprising diagnostic unit and a user interface, the diagnostic unit
operative to diagnose functioning of one or more elements in the hearable and the user
interface enabling participation of user in the diagnostic process.
2. The system as claimed in claim 1, wherein the hearable comprising
microphone, speaker, Bluetooth stack, and battery, in that the said one or more elements are
the microphone, speaker, Bluetooth stack, and battery.
3. The system as claimed in claim 2, wherein the mobile device comprises
memory unit storing sample voice signal with amplitude and the diagnostic unit is configured
to receive a test voice from the Hearable and compare the test voice with the sample voice to
determine the functioning of the microphone.
4. The system as claimed in claim 2, wherein the mobile device comprises
memory unit storing sample text and a corresponding voice reading the said sample text and
user interface configured to receive user interface indicating the consent to have heard the
sample text when the voice recording is played on the hearable to determine the functioning
of the Speaker.
5. The system as claimed in claim 2, wherein the mobile device comprises
battery diagnostic unit operative to determine the rate of battery drain from the battery charge
data collected at two different time instant.
6. A method in a mobile device and hearable comprising:
the mobile device initiating the diagnostic process;
providing a diagnostic user interface for giving and receiving set of instructions to and
from the user for performing diagnostic operations;
performing a set of operations to determine the working status of the Hearable;
the hearable receiving instruction from mobile device and performing diagnostic
operations corresponding to the received signal; and
mobile device presenting the status of the Hearable on the user interface.
17
7. The method as claimed in claim 6, wherein the method of diagnosing a
microphone in the hearable comprising:
presenting a message on a user interface in the mobile device, instructing user to
input a predefined voice input;
capturing the voice input from microphone on the hearable;
transmitting the captured voice input to the mobile device;
receiving the voice input from the hearable and comparing with a reference data; and
indicating success when the comparison result is greater than a threshold.
8. The method as claimed in claim 6, wherein the method of diagnosing a speaker in the
hearable comprising:
presenting a message on a user interface in the mobile device, instructing user to hear
a predefined voice;
sending an audio file to the hearable and playing the audio file on the speaker of the
hearable;
receiving an input from user; and
indicating diagnostic as success when the user input is “yes” and not success when
the user input is “No”.
9. The method as claimed in claim 6, wherein the method of diagnosing
Bluetooth connectivity of the hearable comprising:
determining if the Hearable is already paired with the mobile device;
pairing the Hearable with the mobile device primary unit if it is not already paired;
performing call back operation to determine the connectivity; and
presenting result as “successful” if the call back is positive and as “not successful”
otherwise.
10. A method, system, and apparatus for radar receiver system comprising one or
more features described in the specifications and drawings.