TECHNICAL FIELD
The present disclosure is related generally to wireless communication and, more particularly, to wireless communication in the context of gesture-based computing.
BACKGROUND
Gesture-based computing has been used for several years in the home video game industry, but is now becoming more widespread in the mobile device area. Allowing users to initiate actions without the need to make physical contact with a mobile device opens up multiple possibilities for new forms of human-device interaction.
DRAWINGS
While the appended claims set forth the features of the present techniques with particularity, these techniques, together with their objects and advantages, may be best understood from the following detailed description taken in conjunction with the accompanying drawings of which:
FIG. 1 is a gesture-based messaging device according to an embodiment;
FIG. 2 shows different gestures that may be used;
FIG. 3 shows a gesture-based messaging system according to an embodiment;
FIG. 4 shows a computing device according to an embodiment;
FIGS. 5 and 6 are flowcharts that illustrate the operation of different embodiments; and
FIG. 7 illustrates a use case for an embodiment.
DESCRIPTION
This disclosure is generally directed to a method on a gesture-based messaging device (“messaging device”). According to various embodiments, the messaging device detects a user's gesture (e.g., arm gesture, hand gesture, or finger gesture) with the messaging device using, for example, Electromyography or EMG. In some embodiments, the messaging device detects gestures that occur on the messaging device using, for example, a touch sensor; an infrared sensor, which can detect gestures in three dimensions above the computing device 304; an ultrasonic sensor; and an imager sensor (e.g., a camera). The messaging device may be implemented as a wearable device, such as a ring, wristband (e.g., a wristwatch), or pair of glasses (e.g., Google Glass™). The messaging device attempts to authenticate the user. If the messaging device authenticates the user and recognizes the gesture as indicating that a social media message is to be dictated, then the messaging device enters a social media mode, during which it listens for and receives an input of a spoken message from a user, converts the spoken message to a text message, and transmits the text message to a social media entity (e.g., Twitter®, Facebook®, or Tumblr®). The messaging device may also attempt authenticate the user based on voice recognition. In such case, the messaging device only enters the social media mode if the messaging device successfully authenticates the user based on voice recognition (in addition to gesture recognition). In some embodiments, the device does not send the message unless it receives a “send” confirmation, either spoken or by gesture.
According to an embodiment, the messaging device operates as part of a system. In this embodiment, the messaging device attempts to locate the nearest computing device (e.g., a smartphone, tablet computer, or personal computer) with which it is already paired, or with which it can pair using, for example, ad hoc pairing or proximity pairing. The messaging device establishes wireless connection with the located computing device and determines the signal strength of the wireless connection. If the signal strength is above a threshold value (indicating that the computing device is close to the messaging device), then the messaging device informs the computing device (via the wireless connection) that the computing device is to display the text message. The computing device may, in some embodiments, translate the text message from one language to another. The computing device can determine the target language based on the location of the computing device (as determined, for example, by a global positioning signal).
FIG. 1 illustrates a gesture-based messaging device 100 according to an embodiment. The messaging device 100 is capable of converting movements of the user's arm, hand, or fingers into electrical signals (e.g., using EMG). The messaging device 100 is also capable of communicating with other devices via a short range communication technology such as Bluetooth®, low-energy Bluetooth® (“BLE”), or Near Field Communication (“NFC”). In some embodiments, the messaging device 100 is capable of communicating via wireless local area network (“WLAN”) or via cellular network.
Continuing with FIG. 1, an embodiment of the gesture-based messaging device 100 includes a housing 101. The housing 101 may take a variety of forms, including a ring, wrist device (e.g., a wristwatch), and a pair of glasses. Within the housing 101 is a processor 102. Several components are communicatively linked to the processor 102, including an audio codec 104, a short-rage wireless controller 106 (e.g., a Bluetooth® controller, BLE controller, or an NFC controller), a gesture sensor 108, and a memory 110. In one embodiment, the gesture sensor 108 is an EMG circuit and is coupled to electrodes 109. Electrodes 109 are disposed proximate to the outer surface of the housing 101 such that they can make contact with a user's skin if the user wears the messaging device 100. The short-range wireless controller 106 includes a transceiver.
During operation of the messaging device 100, the short-range wireless controller 106 receives data from the processor 102 and transmits Radio Frequency (“RF”) signals representing the data via a transceiver and an antenna. Similarly, the short-range wireless controller 106 receives RF signals (via the transceiver and the antenna), converts the signals into the appropriately formatted data, and provides the data to the processor 102.
The messaging device 100 further includes a microphone 112 (e.g., a directional microphone) communicatively linked to the audio codec 104. The microphone 112 senses an input of a spoken message, converts the spoken message into audio signals, and provides the audio signals to the audio codec 104. The audio codec 104 decodes the audio signals and provides the decoded audio signals to the processor 102. The processor 102 executes a speech-to-text engine, which is stored in the memory 110, in order to convert the spoken message into a text message. The processor 102 transmits the text message via the short range wireless controller 106 to another entity such as a smartphone, tablet computer, or component of a home network. In some implementations, the processor 102 transmits the text message via WLAN or cellular network using a network transceiver 140. The messaging device 100 further includes a battery, which may be an inductively-rechargeable button cell. The elements of FIG. 1 are communicatively linked to one another via one or more data pathways 170. Possible implementations of the data pathways 170 include wires and conductive pathways on a microchip. Possible implementations of the processor 102 include a microprocessor and a controller.
Turning to FIG. 2, there are a variety of gestures that may be used with the embodiments described herein. For example, if the messaging device 100 is implemented as a ring, different finger positions (e.g., finger extended, thumb open or closed) may represent different actions. Gesture 202 could mean “Enter social media mode and prepare to listen for a Twitter® message,” while gesture 204 could mean “Enter social media mode and prepare to listen for a Tumblr® message.” Gesture 206 could mean “send the text message.” Thus, a user could speak one message to the messaging device 100, use one gesture to send it to one social media entity, then use another gesture to send the text message to another social media entity. If confirmation is not used, the messaging device 100 may send the message to the social media entity as soon as the user finishes speaking it—i.e., without further prompting.
Turning to FIG. 3, a gesture-based messaging system 300 according to an embodiment includes the gesture-based messaging device 100 of FIG. 1. The messaging device 100 is worn by a user 302 and is communicatively linked to a computing device 304 via short-range wireless communication (using the short-range wireless controller 106 of FIG. 1). Possible implementations of the computing device 304 include a smartphone, a tablet computer, and a component of a home network. As previously discussed, there are many possible implementations of the messaging device 100, including a wristband 100A. In some embodiments, the user 302 wears multiple devices, such as a ring and a wristwatch. As will be described in more detail below, the messaging device 100 and the computing device 304 may be pre-paired or may establish communication using, for example, ad hoc pairing or proximity pairing. In some embodiments, the computing device 100 performs voice authentication and language translation, and does by itself or by contacting the appropriate service on a public network 306. The computing device 100 may determine the target language for translation based on its location as indicated, for example, by global positioning system signals.
Turning to FIG. 4, an embodiment of the computing device 304 includes a processor 410, a memory 420 (which can be implemented as volatile memory or non-volatile memory), a network transceiver 440 (e.g., an IEEE 802.11x transceiver, a wired cable network transceiver, or a cellular communication transceiver), a short range wireless controller 442 (e.g., a Bluetooth® controller, such as a BLE controller, or an NFC controller), a display 460, a speaker 412, a user interface 450, and a location sensor 452 (e.g., a global positioning system sensor), and one or more antennas. Each of these elements is communicatively linked to one another via one or more data pathways 470. In some embodiments, the computing device 304 includes a gesture sensor 408, which is capable of sensing gestures of a user. Possible implementations of the gesture sensor 408 include an EMG sensor; a touch sensor, which can detect gestures on the display 460; an infrared sensor, which can detect gestures in three dimensions above the computing device 304; an ultrasonic sensor; and an imager sensor (e.g., a camera). The location sensor 452 senses the location of the computing device 304 on the Earth.
Possible implementations of the data pathways 470 include wires and conductive pathways on a microchip. Possible implementations of the processor 410 include a microprocessor and a computer.
During operation of the computing device 304, the network transceiver 440 receives data from the processor 410 and transmits RF signals representing the data via a wired connection or, if wireless, via an antenna. Similarly, the transceiver 440 receives RF signals (via an antenna if wireless), converts the signals into the appropriately-formatted data, and provides the data to the processor 410. The short-range wireless controller 442 receives data from the processor 410 and transmits RF signals representing the data via the antenna. The short-range wireless controller 442 receives RF signals via an antenna, converts the signals into the appropriately formatted data, and provides the data to the processor 410. In some cases (such as when reading back text messages), the processor transmits data to the speaker 412, which generates sound, such as an artificial voice, based on the data.
The processor 410 retrieves instructions and data from the memory 420 and, using the instructions and data, provides outgoing data to, or receives incoming data from the network transceiver 440 and the short-range wireless controller 442.
Turning to FIG. 5, a flowchart describes a process that the gesture-based messaging device 100 carries out in an embodiment. In this scenario, it will be assumed that the user makes a gesture (e.g., a hand gesture or a finger gesture) that maps to sending a message to a social media entity. At block 502, the messaging device 100 detects the gesture. At block 504, the messaging device 100 attempts to authenticate the user based on the gesture. If the messaging device 100 cannot authenticate the user, then the procedure of FIG. 5 ends. If the messaging device 100 successfully authenticates the user, it enters a social media mode—i.e., the messaging device 100 enables the social media voice entry feature—at block 506. At block 508, the messaging device 100 receives an input of a spoken message. At block 510 (if voice authentication is used), the messaging device 100 attempts to authenticate the user based on the user's voice. In doing so, the messaging device 100 may contact an external server (such as a web-based service) to help perform the authentication. If the authentication fails, then the procedure of FIG. 5 ends. If the user is successfully authenticated, then at block 512 (if the confirmation feature is used), the messaging device 100 waits for either a gesture or voice confirmation (whichever the user has set up) before sending the message. An example of a gesture confirmation is the user flicking his wrist. An example of a voice confirmation is the user speaking “send.” Once the messaging device 100 has received confirmation from the user, it converts the spoken message into a text message at block 514. At block 516, the messaging device 100 sends the text message to a social media entity (e.g., via WLAN, via cellular communication, or via a smartphone using BLE).
Turning to FIG. 6, a flowchart describes how the gesture-based messaging system 300 (FIG. 3) operates according to an embodiment. As in the case of FIG. 5, it will be assumed for FIG. 6 that the user makes a gesture (e.g., a hand gesture, finger gesture, or a touch gesture) that translates to sending a message to a social media entity. At block 602, the messaging device 100 detects the gesture. At block 604, the messaging device 100 attempts to authenticate the user based on the gesture. If the messaging device 100 cannot authenticate the user, then the procedure of FIG. 6 ends. If the messaging device 100 successfully authenticates the user, it enters a social media mode—i.e., the messaging device 100 enables the social media voice entry feature—at block 606.
In parallel with block 606 (e.g., in a background process), at block 608, the messaging device 100 determines whether any computing device with which it is already paired is available (e.g., within range and accessible by BLE). If there is such a computing device available, the messaging device 100 connects with that computing device at block 620. If no paired device is available, then the messaging device 100 looks for and connects with another computing device using a pairing procedure, such as ad hoc pairing or proximity pairing (which may be ad hoc). If proximity pairing is used, then, as soon as the user carries the messaging device 100 within a certain distance from the computing device 304 (e.g., within five feet), then the messaging device 100 pairs with the computing device 304.
At block 608, the messaging device 100 receives a voice input of a message. Referring to FIG. 7, for example, a user 702 speaks the message “Bumped into Cindy on the 4th in New York.” The messaging device 100 transmits this message to the computing device 304. At block 610 (if voice authentication is used), the computing device 304 attempts to authenticate the user's voice. In doing so, the computing device 304 may contact an external server (such as a web-based service) to help perform the authentication. If authentication fails, then the procedure of FIG. 6 ends. If the user is successfully authenticated, and if the confirmation feature is used, at block 624, the messaging device 100 waits for either a gesture or voice confirmation (whichever the user has set up) before sending the message. Once the messaging device 100 receives the confirmation, it converts the spoken message into a text message at block 628. At block 630, the messaging device 100 determines whether the signal it receives from the computing device 304 is strong enough to indicate that the computing device is close to the user (e.g., by comparing the signal strength to a predetermined threshold). If yes, then the messaging device 100 informs the computing device 304 that it is to display the text message on the display 460 (FIG. 4) at block 632. This allows the user to review the message. In the example of FIG. 7, the computing device 304 displays both the text of the message and the photo of the intended recipient. The computing device 304 then transmits the text message to the social media entity at block 634. If the messaging device 100 determines that the signal is not strong enough (block 630), the messaging device 100 informs the computing device 304 that it is to send the text message to the social media entity (block 634)—without displaying the message in this case. In some embodiments, the computing device 304 translates the text message into the appropriate language as determined, for example, by its location. The computing device 304 can determine its location by using its location sensor 452.
In an alternate embodiment, blocks 514 and 632 of FIGS. 5 and 6 can be implemented by the computing device 304 “speaking” (using a text-to-speech function) the text message.
It should be understood that the steps of the flowcharts of FIGS. 5 and 6 can be reordered. For example, the messaging device 100 may convert the spoken message to a text message prior to waiting for confirmation (e.g., blocks 514 and 512 of FIG. 5 may be switched).
It can be seen from the foregoing that a gesture-based messaging method and system have been described. It should be understood that the exemplary embodiments described therein should be considered in a descriptive sense only and not for purposes of limitation. Descriptions of features or aspects within each embodiment should typically be considered as available for other similar features or aspects in other embodiments.
While one or more embodiments of the have been described with reference to the figures, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from their spirit and scope of as defined by the following claims.
Patent Grant
9330666
