Patent ID: 12242678

It should be understood the reference number for any illustrated element that appears in multiple different figures has the same meaning across the multiple figures, and the mention or discussion herein of any illustrated element in the context of any particular figure also applies to each other figure, if any, in which that same illustrated element is shown.

DETAILED DESCRIPTION

FIG.1is a schematic of an example system100for providing information regarding an object106to a person P. The example system100includes a base unit102located at, or otherwise associated with, the object106, and a mobile unit104carried by the person P. The object106may include a human-selectable actuator (e.g., a switch, button, knob, slider, lever, or other device that may be actuated by a human) or any other physical object. As illustrative examples only, the object106may be an actuator or other element of an elevators, an intercom, a pedestrian semaphore, an ATM, a ticket machine, a public transportation system, or household electronics (e.g., a washing machine, dishwasher, stove, or microwave), without limitation.

The base unit102may include a base unit capacitive coupling element110, a base unit processor112, and a base unit transmitter circuitry114. The base unit capacitive coupling element110may comprise a conductive pad or other element to provide a capacitive coupling between the base unit102and the person P, e.g., when the person P comes into physical contact or proximity of base unit capacitive coupling element110. Such capacitive coupling is referred to herein as a “base unit-human capacitive coupling,” indicated as BUHCC. The base unit capacitive coupling element110may also be referred to as an antenna. As shown inFIG.1, the base unit-human capacitive coupling BUHCC defines one component of a data transmission connection DTC between the base unit102and mobile unit104and passing through the person's body PB. (The data transmission connection DTC also includes a capacitive coupling between the mobile unit104and person P, referred to as a mobile unit-human capacitive coupling MUHCC, as discussed below.)

The base unit transmitter circuitry114may include circuitry for transmitting object related data108from the base unit102to the mobile unit104via the data transmission connection DTC. For example, the base unit transmitter circuitry114may include a transmitter and driver for transmitting data (e.g., object related data108) using a low-frequency Amplitude Shift Key (ASK) format (e.g., at 125 kHz), which passes through the person's body PB via the data transmission connection DTC.

Object related data108may include or identify any information related to the object108, and may comprise (a) substantive object related data or (b) an object related identifier linked to substantive object related data. Substantive object related data (one example form of object related data108) may include, for example, information describing the object108or a function related the object108(e.g., in the case of an object108comprising an actuator, information describing a function provided by the actuator), and may be embodied in any form, for example text data, audio data (e.g., an audio file), an image file, or video data, without limitation. Alternatively, an object related identifier (another example form of object related data108) may comprise an identifier linked to substantive object related data108′ (not shown) stored by or otherwise accessible by the mobile unit104, as discussed below.

In some examples, object related data108stored by (or otherwise accessible to) base unit102may include multiple different types and/or formats of data. For example, base unit102may store object related data108for a respective object106in multiple different formats (e.g., an audio file, video file, and text file) usable by different mobile units104having different types of output devices128(e.g., speakers or display devices, without limitation). As another example, the base unit102may store object related data108for a respective object106in multiple different languages, e.g., to accommodate persons P with different language preferences.

In some examples, the base unit102may optionally include a touch/proximity detection device115including touch/proximity detection circuitry116to detect a “touch/proximity event” by the person P, the touch/proximity event comprising the person P touching or coming into proximity (e.g., a proximity allowing a capacitance-based detection of the person P) with a detection element117of the touch/proximity detection device115. In response to the touch/proximity detection device115detecting the touch/proximity event, the base unit processor112may initiate a communication sequence to transmit the object related data108(using the base unit transmitter circuitry114) via the data transmission connection DTC. The touch/proximity detection circuitry116may include capacitive touch detection circuitry.

In some examples, the detection element117may be integrated with or located adjacent or near the base unit capacitive coupling element110and/or the object106, as indicated by dashed line119, such that the touch/proximity detection device115may detect the person P touching or coming into proximity of the base unit capacitive coupling element110.

The base unit processor112may comprise any suitable processor or processors to execute instructions stored in computer-readable media related to the operation of the base unit102(e.g., instructions embodied in software and/or firmware stored in memory provided in or otherwise accessible to the base unit102). For example, the base unit processor112may execute respective instructions for performing various functions associated with (a) the base unit transmitter circuitry114(e.g., for transmitting object related data108via the base unit capacitive coupling element110), (b) the optional touch/proximity detection device115(e.g., for detecting touch/proximity events and initiating a communication sequence or other actions in response thereto), and (c) optional base unit receiver circuitry118(e.g., for receiving and decoding optional mobile unit data132received from the mobile unit104and initiating respective actions in response thereto), without limitation. The base unit processor112may comprise at least one microprocessor, microcontroller, embedded processor, digital signal processor (DSP), or other type of computer processor(s).

The mobile unit104may include a mobile unit capacitive coupling element120, a mobile unit processor122, a mobile unit receiver circuitry124, and an output device128. In some examples, the mobile unit104may comprise a single device including the mobile unit capacitive coupling element120, the mobile unit processor122, the mobile unit receiver circuitry124, and the output device128. For example, the mobile unit104may comprise an earbud, headphones, a smartphone or other handheld device including the mobile unit capacitive coupling element120, the mobile unit processor122, the mobile unit receiver circuitry124, and the output device128.

In other examples, the mobile unit104may include two or more distinct devices communicatively connected to each other, wherein the respective components of the mobile unit104—including the mobile unit capacitive coupling element120, the mobile unit processor122, the mobile unit receiver circuitry124, and the output device128—may be provided in different devices of the mobile unit104. For example, the mobile unit104may include a smartphone and an earbud wirelessly connected to the smartphone, wherein the mobile unit capacitive coupling element120, the mobile unit processor122, the mobile unit receiver circuitry124are provided in the smartphone, and the output device128(in this example comprising a speaker) is provided in the earbud.

The mobile unit capacitive coupling element120may comprise a conductive pad or other element to provide a capacitive coupling between the mobile unit104and the person P, e.g., when the mobile unit104is carried by the person P. The capacitive coupling between the mobile unit104and person P is referred to as mobile unit-human capacitive coupling MUHCC, which forms a component of the data transmission connection DTC between the base unit102and mobile unit104. Like the base unit capacitive coupling element102, the mobile unit capacitive coupling element120may also be referred to as an antenna.

As used herein, the mobile unit104being carried by the person P means the mobile unit104is worn by, carried by, or otherwise located with the person P. For example, the person P may hold the mobile unit104in their hand, e.g., wherein the mobile unit104comprises a smartphone. As another example, the mobile unit104may be secured in contact with or proximate person's body PB, e.g., wherein the mobile unit104comprises an earbud, headphones, or a watch. As another example, the mobile unit104may be carried in an article of clothing or accessory worn by the person P.

The mobile unit receiver circuitry124may include circuitry connected to mobile unit capacitive coupling element120to receive object related data108received from the base unit102via the data transmission connection DTC. For example, the mobile unit receiver circuitry124may include a receiver and demodulator for receiving and demodulating data received via a low-frequency Amplitude Shift Key (ASK) format (e.g., at 125 kHz), e.g., as transmitted by the base unit102.

The output device128may comprise any device to output human-perceptible signals, for example audible signals, visually displayed information, or haptic feedback, based on object related data108received via the data transmission connection DTC. For example, the output device128may comprise at least one speaker, e.g., provided in an earbud, headphones, or a smartphone, to output audio data to the person P, for example audio data describing the object106. As another example, the output device128may comprise a display device, e.g., provided in a smartphone or other mobile device, e.g., to visual display data describing the object106. As another example, the output device128may comprise a haptic feedback generator, e.g., to generate human-detectable vibrations.

The mobile unit processor122may comprise any suitable processor or processors to execute instructions stored in computer-readable media related to the operation of the mobile unit104(e.g., instructions embodied in software and/or firmware stored in memory provided in or otherwise accessible to the mobile unit104). For example, the mobile unit processor122may execute respective instructions for performing various functions associated with (a) the mobile unit receiver circuitry124(e.g., for receiving and decoding object related data108received from the base unit102via the mobile unit capacitive coupling element120, and causing an output of human-perceptible signals via the output device128related to the object related data108), and (b) optional mobile unit transmitter circuitry130(e.g., for transmitting optional mobile unit data132via the mobile unit capacitive coupling element120), without limitation. The mobile unit processor122may comprise at least one microprocessor, microcontroller, embedded processor, digital signal processor (DSP), or other type of computer processor(s).

In some examples, the mobile unit processor122processes object related data108received from the base unit102by the mobile unit receiver circuitry124, and causes the output device128to output human-perceptible signals based on the received object related data108. In examples in which the object related data108comprises substantive object related data (discussed above), e.g., in the form of a text file, audio file, image file, or video file, the mobile unit processor122may processes the substantive object related data and cause the output device128to output the substantive object related data in any suitable form. For example, where the output device128comprises a speaker, the mobile unit processor122may cause the output device128to output audio sound, e.g., by playing the contents of an audio file (audio sample), or by converting a text file to audio (e.g., using a text-to-speech tool) and outputting the converted audio. As another example, where the output device128comprises a screen or other display device, the mobile unit processor122may cause the output device128to visually display the contents of a text file, image file, or video file. As another example, where the output device128comprises a haptic feedback generator, the mobile unit processor122may cause the output device128to generating vibrations or other haptic feedback, e.g., according to a haptic feedback protocol (e.g., defined in the received object related data108or stored by or otherwise accessible to the mobile unit104) specifying respective haptic feedback associated with respective substantive object related data.

In examples in which the object related data108comprises an object related identifier (as discussed above), the mobile unit processor122may process the object related identifier to identify corresponding substantive object related data108′ (not shown) linked to the object related identifier, access the substantive object related data108′ (stored by or otherwise accessible to the mobile unit104), and cause the output device128to output the substantive object related data108′, e.g., in any of the manners discussed above (e.g., by outputting audio sound, visually displaying information, or by generating vibrations or other haptic feedback corresponding with the substantive object related data108′).

In some examples, the example system100optionally includes respective components to communicate mobile unit data132from the mobile unit104to the base unit102via the data transmission connection DTC passing through the person's body PB, in the opposite direction as the communication of object related data108from the base unit102to the mobile unit104via the data transmission connection DTC. In such examples, the mobile unit104may include optional mobile unit transmission circuitry130connected to the mobile unit capacitive coupling element120to transmit mobile unit data132via the data transmission connection DTC, and the base unit102may include optional base unit receiver circuitry118connected to the base unit capacitive coupling element110to receive the mobile unit data132transmitted via the data transmission connection DTC.

Mobile unit data132may include any information associated with the mobile unit104or the person P. For example, mobile unit data132may include authentication data to authenticate the mobile unit104or person P with the base unit102, e.g., as a prerequisite for the base unit102to transmit the object related data108to the mobile unit104.

As another example, mobile unit data132may indicate a requested format of object related data108, depending on the type of output device128provided at the mobile unit104(e.g., a speaker, display device, or haptic feedback generator), which information may be used by the base unit102to select a respective format (e.g., file type) of object related data108to deliver to the mobile unit104, e.g., in an example in which the base unit102has access to multiple formats (e.g., file types) of object related data108. For example, the mobile unit data132may include a request for object related data108in the form of an audio file, and accordingly the base unit102may access and transmit an audio file (as object related data108) to the mobile unit104.

As another example, mobile unit data132may indicate a requested language of the object related data108(e.g., English, Spanish, Chinese, or other language understandable to the person P), and accordingly the base unit102may select object related data108in the requested language (e.g., from a set of object related data108stored in different languages) and transmit the selected object related data108to the mobile unit104.

It should be understood that mobile unit data132may include any other type of information associated with the mobile unit104or the person P, which may be usable by the base unit102for selecting respective object related data108, the format of the object related data108, or any other aspect of the object related data108for delivery to the mobile unit104.

In some examples, respective components of the system100may utilize BodyCom™ technology by Microchip Technology Inc. of Chandler, Arizona, for example as disclosed in U.S. Patent Application Publication 2015/0044969 published Feb. 12, 2015 (“the '969 Publication”), the entire contents of which are hereby incorporate by reference. For example, base unit102disclosed herein may include any disclosed components (e.g., any hardware, software, circuitry, or other components) of example base units102,402,504, and/or604disclosed in the '969 Publication, and mobile unit104disclosed herein may include any disclosed components (e.g., any hardware, software, circuitry, or other components) of example mobile units108,408,508, and/or662/664disclosed in the '969 Publication.

In an example in which the system100includes the optional touch/proximity detection device115, the system100may generally operate in the following manner. The person P carrying the mobile unit104desires information about the object106, e.g., an actuatable (e.g., depressible) button that triggers a defined function. The person P places their finger on, or proximate, the detection element117of the touch/proximity detection device115(i.e., a touch/proximity event), which detection element117may be integrated with or located adjacent or near the base unit capacitive coupling element110and/or the object106, as discussed above. The touch/proximity detection circuitry116of the touch/proximity detection device115detects the touch/proximity event. In response, the base unit processor112initiates a communication sequence to transmit the object related data108(using the base unit transmitter circuitry114) via the data transmission connection DTC, i.e., via the base unit-human capacitive coupling BUHCC, the person's body PB, and the mobile unit-human capacitive coupling MUHCC.

In some examples, the communication sequence may include an authentication process (e.g., a challenge and response sequence) between the base unit102and the mobile unit104(involving transmission, receipt, and processing of respective messages by both the base unit102and the mobile unit104), and after successful authentication of the mobile unit104, transmission of the object related data108by the base unit102, i.e., using the base unit transmitter circuitry114to transmit the object related data108via the base unit capacitive coupling element110. The authentication process (e.g., challenge and response sequence) may involve the transmission of mobile unit data132(including authentication information) by the optional mobile unit transmitter circuitry130(transmitted via the mobile unit capacitive coupling element120and the data transmission connection DTC), and receipt of such mobile unit data132(including authentication information) by the optional base unit receiver circuitry118(received via the base unit capacitive coupling element110).

In other examples, the communication sequence triggered by the detected touch/proximity event may omit an authentication of the mobile unit104, i.e., wherein the base unit102transmits the object related data108to the mobile unit104in response to the detected touch/proximity event, without authenticating the mobile unit104.

The object related data108transmitted via the data transmission connection DTC (terminating at the mobile unit capacitive coupling element120) may be received by the mobile unit receiver circuitry124(connected to the mobile unit capacitive coupling element120), and processed by the mobile unit processor122, which causes the output device128to output human-perceptible signals based on the received object related data108, e.g., by outputting audio sound, displaying an image or video, or generating haptic feedback as discussed above.

In some examples, the system100may allow a vision impaired person P to obtain information regarding an object106. For example, where the object106comprises a pressable button to perform a respective function, the system100may allow the person P to learn the function associated with the button by touching or coming into proximity with, but not actuating, the button, thereby allowing the person P to determine whether to actuate (press) the button.

FIG.2is a schematic of an example base unit102for use in the example system100shown inFIG.1, according to one example. As shown, the example base unit102may include multiple objects106(indicated at106a-106n) and respective components for transmitting respective object related data108(indicated at108a-108n) to a mobile unit104carried by a person P (shown inFIG.1). In this example, the multiple objects106a-106ncomprise actuatable (e.g., depressible) buttons that trigger respective functions. Accordingly, the following description refers to buttons106a-106n.

The example base unit102includes a touch/proximity detection device115including touch/proximity detection circuitry116connected to respective detection elements117a-117nprovided at respective buttons106a-106nto detect a touch/proximity event at respective buttons106a-106n.

The example base unit102also includes a respective base unit capacitive coupling element110a-110nprovided at respective buttons106a-106nto allow a respective data transmission connection DTC (not shown) between respective buttons106a-106n(via the respective base unit capacitive coupling elements110a-110n) and the mobile unit104carried by the person P.

Thus, as shown inFIG.2, respective buttons106a-106nmay have both a respective detection element117a-117nand a respective base unit capacitive coupling element110a-110nintegrated with or otherwise provided on or at the respective button106a-106n. In some examples, for a respective button106a-106n, the respective detection element117a-117nand the respective base unit capacitive coupling element110a-110nmay comprise distinct conductive elements physically separate from each other, which may reduce or avoid signal interference or other unwanted effects during a transmission of respective object related data108a-108n(via a respective base unit capacitive coupling element110a-110n) while the person P is physically touching the respective detection element117a-117n.

The example base unit102also includes the base unit processor112, base unit transmitter circuitry114, base unit receiver circuitry118, and memory202storing object related data108a-108n.

The base unit transmitter circuitry114includes circuitry for transmitting respective object related data108a-108nvia respective base unit capacitive coupling elements110a-110nprovided at respective buttons106a-106n, e.g., in response to touch/proximity events detected (by the touch/proximity detection device115) at respective buttons106a-106n. For example, in response to a touch/proximity event detected at button106a(e.g., the touch/proximity detection device115detecting a touch/proximity event via the detection element117aat button106a), the base unit processor112may access object related data108a(e.g., describing the functionality associated with button106a) and control base unit transmitter circuitry114to transmit the object related data108aretrieved from memory202via the base unit capacitive coupling element110aat button106a.

The base unit receiver circuitry118is connected to the respective base unit capacitive coupling elements110a-110nto receive mobile unit data132transmitted via the data transmission connection DTC and received at a base unit capacitive coupling elements110a-110nat a respective button110a-110nat which a touch/proximity event is detected at a respective detection element117a-117n. In some examples, the base unit receiver circuitry118may include a receiver and demodulator for receiving and demodulating data received via a low-frequency Amplitude Shift Key (ASK) format (e.g., at 125 kHz), e.g., as transmitted by the mobile unit104.

The base unit processor112may execute instructions (e.g., embodied in software and/or firmware) for performing various functions associated with (a) the base unit transmitter circuitry114(e.g., for transmitting respective object related data108a-108nvia respective base unit capacitive coupling elements110a-110nat respective buttons106a-106n), (b) the touch/proximity detection device115(e.g., for detecting touch/proximity events at respective detection elements117a-117nat respective buttons106a-106n, and initiating a communication sequence or other respective actions in response thereto), and (c) base unit receiver circuitry118(e.g., for receiving and decoding optional mobile unit data132received (from the mobile unit104) via respective base unit capacitive coupling elements110a-110nat respective buttons106a-106n, and initiating respective actions in response thereto), without limitation.

Memory202may include ROM (read only memory), EPROM (erasable programmable ROM) and EEPROM (electrically erasable programmable ROM), ferroelectric RAM, Flash memory, disk storage, or any other type of memory to store object related data108a-108ncorresponding with respective buttons106a-106n.

FIG.3is a schematic of an example mobile unit104to be carried by a person P for use in the example system100shown inFIG.1, according to one example. As shown, the example mobile unit104may include the mobile unit capacitive coupling element120, mobile unit processor122, mobile unit receiver circuitry124, output device128, mobile unit transmitter circuitry130, and memory302. In some examples, the mobile unit104may be capable to communicate with multiple different base units102, e.g., wherein respective ones of the multiple different base units102may be associated with one or multiple different objects106.

As discussed above, the mobile unit capacitive coupling element120may comprise a conductive pad or other conductive element to provide a mobile unit-human capacitive coupling MUHCC between the mobile unit104and the person P.

The mobile unit receiver circuitry124may include circuitry connected to mobile unit capacitive coupling element120to receive object related data108received from the base unit102via the data transmission connection DTC. For example, the mobile unit receiver circuitry124may receive respective object related data108a-108nfrom the example base unit102shown inFIG.2in response to a touch/proximity event by the person P at a respective button106a-106n.

As discussed above, the output device128may comprise any device to output human-perceptible signals based on output object related data108received from a respective base unit102. For example, the output device128may output object related data108in the form of substantive object related data received from a respective base unit102. As another example, the output device128may output substantive object related data108′ corresponding with object related data108in the form of an object related identifier received from a respective base unit102, e.g., as discussed below regarding memory302. In some examples, the output device128may comprise at least one speaker, display device, or haptic feedback generator, as discussed herein.

The mobile unit transmitter circuitry130may include circuitry for transmitting mobile related data132from the mobile unit104to respective base unit(s)102via the data transmission connection DTC (i.e., via the mobile unit capacitive coupling element120). For example, the mobile unit transmitter circuitry130may include a transmitter and driver for transmitting data (e.g., mobile related data132and/or authentication related messages) using a low-frequency Amplitude Shift Key (ASK) format (e.g., at 125 kHz)

Memory302may store mobile unit data132, and may optionally store substantive object related data108′ and object related data identifiers310. Memory302may include ROM (read only memory), EPROM (erasable programmable ROM) and EEPROM (electrically erasable programmable ROM), ferroelectric RAM, Flash memory, disk storage, or any other type of memory to store mobile unit data132, substantive object related data108′, and/or object related data identifiers310.

As discussed above, mobile unit data132may include any information associated with the mobile unit104or the person P, for example including authentication data (for authenticating the mobile unit104with respective base unit(s)102), information indicate a requested format of object related data108corresponding with the type of output device128provided at the mobile unit104(e.g., a speaker, display device, or haptic feedback generator), or information indicating a requested language of object related data108to acquire from respective base unit(s)102.

As discussed above, in some examples the object related data108transmitted by the base unit102and received by the mobile unit104may comprise an object related identifier (as opposed to substantive object related data) linked to corresponding substantive object related data108′ stored by the mobile unit104, e.g., to reduce data storage requirements at the base unit102. In such examples, as shown inFIG.3, memory302of the mobile unit104may store (a) various substantive object related data108′ and (b) a set of object related data identifiers310linking object related identifiers (that may be received from respective base units102) to corresponding substantive object related data108′. For example, referring to the example base unit102shown inFIG.2, memory302may store multiple substantive object related data108a′-108n′ corresponding with respective buttons106a-106n. In operation, when the base unit102detects a touch/proximity event at button106a, the base unit102may transmit object related data108a(in some examples after a successful authentication of the mobile unit104) in the form of an object related identifier corresponding with button106a, and the mobile unit104may use object related data identifiers310to identify, from the multiple substantive object related data108a′-108n′, substantive object related data108a′ corresponding with the received object related identifier (e.g., data identifying the function associated with button106a) and output of the identified substantive object related data108a′ via the output device128. The substantive object related data108a′ may be in a language understood by person P, thereby allowing object related data108ato be language independent.

As discussed above, the mobile unit processor122may execute instructions (e.g., embodied in software and/or firmware) for performing various functions associated with the mobile unit104, e.g., including instructions for performing various functions associated with (a) the mobile unit receiver circuitry124(e.g., for receiving and decoding object related data108received from the base unit102via the mobile unit capacitive coupling element120, and outputting corresponding human-perceptible signals via the output device128), (b) the mobile unit transmitter circuitry130(e.g., for transmitting mobile unit data132to the base unit102), and (c) identifying substantive object related data108corresponding with object related data108received from the base unit102in the form of an object related identifier, as discussed above), without limitation. The mobile unit processor122may execute instructions (e.g., embodied in software and/or firmware) for performing various functions associated with the memory302.

In some examples, the mobile unit104may comprise a single device, e.g., a smartphone, an earbud, a headphone, or other mobile device, including the example components shown inFIG.3.

In other examples, the mobile unit104may include two or more devices wherein the example components shown inFIG.3are distributed between the two or more devices, to collectively provide the functionality of the mobile unit104. For example, e.g., as shown inFIG.4discussed below, the mobile unit104may include (a) a smartphone or other handheld or wearable device including the capacitive coupling element120, mobile unit processor122, mobile unit receiver circuitry124, mobile unit transmitter circuitry130, and memory302, communicatively coupled (e.g., by a wired or wireless connection) with (b) a separate output device128, e.g., comprising an earbud, headphone, or display device. As another example, the mobile unit104may include (a) a handheld or wearable device including the capacitive coupling element120and a first processor, communicatively coupled (e.g., by a wired or wireless connection) with (b) a smartphone, earbud, or headphones including the mobile unit receiver circuitry124, mobile unit transmitter circuitry130, output device128, and memory302, and a second processor, wherein the first and second processors collectively perform the functions of the mobile unit processor122discussed herein.

FIG.4is a schematic of an example multi-component mobile unit400to be carried by a person P for use in the example system100shown inFIG.1, according to one example. The example multi-component mobile unit400represents one example of the mobile unit104shown inFIGS.1and3. The multi-component mobile unit400includes an example base unit interface component402and an example output component404communicatively connected to each other.

The example base unit interface component402may include the mobile unit capacitive coupling element120, mobile unit processor122, mobile unit receiver circuitry124, mobile unit transmitter circuitry130, local transmitter circuitry410, and memory302(storing mobile unit data132and optionally substantive object related data108′ and object related data identifiers310, e.g., as discussed above regardingFIG.3). In some examples, the example base unit interface component402may comprise a smartphone or other handheld or wearable device.

The example output component404includes an output device128and local receiver circuitry412. In some examples, the example output component404may comprise an earbud, headphones, or other handheld or wearable device, wherein the output device128may comprise a speaker, display device, or haptic feedback generator.

The local transmitter circuitry410and local receiver circuitry412may comprise circuitry for transmitting (via wired or wireless connection) object related output signals420from the base unit interface component402to the output component404for output by the output device128. The object related output signals420may comprise object related data108received from a respective base unit102(via the base unit interface component402), substantive object related data108′ accessed from memory302, or other signals otherwise generated from object related data108by the mobile unit processor122for output by the output device128. For example, local transmitter circuitry410and local receiver circuitry412may comprise respective transmitter and receiver circuitry for wireless communication using Bluetooth, Bluetooth BLE, ZigBee, WiFi, or other short-range wireless communication protocol.

In some examples, in addition to the output device128provided in the output component404, the base unit interface component402may optionally include an auxiliary output device128′ to output the same or additional object related output signals420. For example, some object related data108may include information for multiple different output formats, e.g., audio, displayable text, or displayable video, without limitation. The multiple different output formats may be included in object related data108received from the base unit102, or the base unit interface component402may be capable to derive additional format(s) of object related data108received from the base unit102(e.g., the base unit interface component402may derive visual text data from object related data108received as audio data (e.g., using a speech-to-text tool), or retrieve additional format(s) as part of substantive object related data108′ response to object related data108from memory302. Accordingly, the multi-component mobile unit400may be capable to (simultaneously or otherwise) output both (a) a first format of respective object related data108via the output device128of the output component404(e.g., audio output by a speaker) and (b) a second format of the respective object related data108via the auxiliary output device128′ of the base unit interface component402(e.g., a text display corresponding with the audio output).

FIG.5is a flowchart of an example method500for providing object related data108from a base unit associated with an object to a mobile unit via a data transmission connection passing through the body of a person carrying the mobile unit. At502, a touch/proximity detection device of a base unit associated with an object (e.g., a button, switch, other actuator, or other type of object) detects a touch/proximity event involving a person. For example, the touch/proximity detection device may include touch/proximity detection circuitry (e.g., capacitive touch detection circuitry) to detect the person in physical contact with or in proximity with a detection element of the touch/proximity detection device, which detection element may be provided at the object.

At504, in response to detecting the touch/proximity event, the base unit initiates a communication sequence to transmit object related data from the base unit to the mobile unit carried by the person via a data transmission connection between the base unit and the mobile unit. The data transmission connection includes (a) a base unit-human capacitive coupling between the base unit and the person (e.g., between a base unit capacitive coupling element and the person) and (b) a mobile unit-human capacitive coupling between the mobile unit and the person (e.g., between a mobile unit capacitive coupling element and the person), and passes through the person's body. In some examples, the object comprises a human-selectable actuator (e.g., a button or switch), and the object related data identifies a function associated with the human-selectable actuator.

In some examples, the communication sequence involves a two-way authentication sequence between the base unit and mobile unit (e.g., including the mobile unit communicating requested authentication information to the base unit, and the base unit confirming (or denying) the received authentication information), prior to the base unit transmitting the object related data (in the event of a successful authentication of the mobile device). In other examples, the authentication sequence may be omitted.

In some examples, the base unit and mobile unit may transmit respective information (e.g., object related data, authentication related messages, and/or other information) using a low-frequency Amplitude Shift Key (ASK) format, which passes through the person's body PB via the data transmission connection DTC.

At506, the mobile unit receives the object related data transmitted via the data transmission connection DTC, and processes the received object related data. At508, the base unit outputs human-perceptible signals (e.g., audio, images, video, or haptic feedback) human-perceptible signals representing the object related data via an output device (e.g., speaker, display device, or haptic feedback generator). In some examples, the object related data comprises audio data, and the mobile unit outputs the received audio data (or audio data derived therefrom) via a speaker.

In some examples, the object related data transmitted by the base unit comprises substantive object related data, wherein the mobile unit may output such substantive object related data (received from the base unit) via the output device. In other examples, the object related data transmitted by the base unit comprises an object related identifier, wherein the mobile unit may identify and access (e.g., from memory of the mobile unit) substantive object related data linked to the object related identifier, and output the accessed substantive object related data via the output.

Although example embodiments have been described above, other variations and embodiments may be made from this disclosure without departing from the spirit and scope of these embodiments.