Source: https://patents.google.com/patent/US8929954B2/en
Timestamp: 2019-04-22 08:26:31+00:00

Document:
2013-04-29 Assigned to KOPIN CORPORATION reassignment KOPIN CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: JACOBSEN, JEFFREY J., PARKINSON, CHRISTOPHER, POMBO, STEPHEN A.
2013-12-02 Assigned to KOPIN CORPORATION reassignment KOPIN CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: IKANOS CONSULTING LTD.
The present invention related to human/computer interfaces and more particularly to a headset computing display device that accepts voice commands and tracks head motions to provide command inputs to and receive display information from a software application executed on a host computing device. An example embodiment of the present invention includes a method of, and corresponding system for, operating a native Smartphone or PC application, simultaneously displaying an output of the application through the Smartphone or PC screen and a headset computing display device, and using speech and head tracking commands to control the native application. The present invention enables hands-free operation of a Smartphone or PC application.
This application claims the benefit of U.S. Provisional Application No. 61/638,419 by Jacobsen et al., entitled “Improved Headset Computer” filed on Apr. 25, 2012, U.S. Provisional Application No. 61/653,474 by Jacobsen et al., entitled “Headset Computer (HSC) As Auxiliary Display With ASR And HT Input” filed on May 31, 2012, and U.S. Provisional Application No. 61/748,444 by Parkinson et al., entitled “Smartphone API For Processing VGH Input” filed on Jan. 2, 2013 and U.S. Provisional Application No. 61/749,155 by Parkinson et al., entitled “Smartphone Application Programming Interface (API) For Controlling HC Differently From Smartphone Display” filed on Jan. 4, 2013.
This application is related to U.S. application Ser. No. 12/774,179 by Jacobsen et al., entitled “Remote Control Of Host Application Using Motion And Voice Commands” filed May 5, 2010, which claims the benefit of U.S. Provisional Application No. 61/176,662, filed on May 8, 2009 entitled “Remote Control of Host Application Using Tracking and Voice Commands” and U.S. Provisional Application No. 61/237,884, filed on Aug. 28, 2009 entitled “Remote Control of Host Application Using Motion and Voice Commands”.
The present application relates to human/computer interfaces and more particularly to a headset computing display device that accepts voice commands and tracks head motions to provide command inputs to and receive display information from a software application executed on a remote host computing device.
Recently developed micro-displays can provide large-format, high-resolution color pictures and streaming video in a very small form factor. One application for such displays can be integrated into a wireless headset computer worn on the head of the user with a display positioned within the field of view of the user, similar in format to eyeglasses, an audio headset, or video eyewear. A “wireless computing headset” device includes one or more small high-resolution micro-displays and optics to magnify the image. The WVGA micro-displays can provide super video graphics array (SVGA) (800×600) resolution or extended graphic arrays (XGA) (1024×768) or even higher resolutions. A wireless computing headset contains one or more wireless computing and communication interfaces, enabling data and streaming video capability, and provides greater convenience and mobility than hands dependent devices.
Example embodiments of the present invention include a method of, and corresponding system for, operating a Smartphone or PC application, including executing an application on a Smartphone or PC, the executed application being native to the Smartphone or PC. The invention method and system generating an output of the native application for simultaneous display through the Smartphone or PC screen and a headset computing display device. In one embodiment, display output for the headset computing device is in a markup language. The headset computing device translates the received display output for rendering through the headset display in response to requesting and receiving the display output generated by the Smartphone or PC. The headset computing device operating in a speech recognition and head tracking user interface mode, monitors for recognized user speech (voice commands) and head tracking commands (head motions) from an end-user wearing the headset computing device. The headset computing device in response to received speech recognition and head tracking commands—end-user inputs—translates the received speech recognition and head tracking commands to equivalent Smarthphone or PC commands (e.g., touch-screen, keyboard, and/or mouse commands) and transmitting the equivalent commands to the Smartphone or PC to control the native application.
A further example embodiment of the present invention includes a method of, and corresponding system for, operating a Smartphone (or PC) including executing a native image and/or video viewing application on a Smartphone. The embodiment operates a headset computing device in a speech recognition and head tracking user interface mode, monitoring for user speech recognition and head tracking commands from an end-user at the headset computing device. The embodiment translating received speech recognition and head tracking commands to equivalent Smartphone commands at the headset computing device in response to received speech recognition and head tracking commands. The equivalent Smartphone commands include capturing an image or video on a display of the headset computing device, transmitting the equivalent Smartphone command to the Smartphone to control the native image and video viewing application, and displaying the captured image and/or video through the headset computing display device and through the Smartphone display, simultaneously.
The example embodiments may further include, the use of a markup language included with generated display output, such as Hyper Text Markup Language 5 (HTML5). Example embodiments may present to the end-user menu selections and prompts in terms of speech recognition and head tracking commands, such as audible and visual prompts. A wireless communications link between the host Smartphone or PC and the headset computing device. May use wireless communications links such as Bluetooth or Wi-Fi wireless standards.
Still further example embodiments may further still effectively enable a speech recognition and hands-free user interface and control of the native application executed on a Smartphone or PC.
Further example methods of, and corresponding devices for, displaying on a headset computer output from a Smartphone application. Embodiments execute an application on the Smartphone generating output of the executed application for display through a headset computer. The Smartphone configures and transmits instructions in a description language indicating actions for the headset computer to display the output of the executed application. Embodiments receive over low bandwidth at the headset computer the configured instructions, and in response thereto, the headset computer forms a display of the generated output based on indicated actions to perform. The actions include any of on screen notifications, messages, graphical elements, request to play one of a plurality of predefined sound sequences and control a component of the headset computer.
The actions of the respective element types, and for each element type, the instructions can indicate one of a plurality of styles predefined for the headset computer. The description language can be HTML 5 or other markup language. The formed display rendered at the headset in the headset domain can include menu selections and prompts presented in terms of a speech recognition/head tracking user interface. The menu selections and outputs can be audibly and visually presented to a user. The receiving by the headset computer and the transmitting by the Smartphone can be over a wireless communications link. The wireless communications link can be any of Bluetooth, Wi-Fi or other protocol.
Example methods can further include monitoring for input from a speech recognition/head tracking user interface at the headset computer. In response to a received speech recognition/head tracking command input, the headset computer translates the received speech recognition/head tracking command to an equivalent Smartphone command and transmits the equivalent Smartphone command to the Smartphone to control the executed application. The display by the headset computer can effectively enable speech and hands-free user interaction with the Smartphone.
FIG. 1A illustrates an example embodiment of a headset computing device communicating with a host computing device (e.g., Smartphone, PC, etc.) according to principles of the present invention.
FIG. 1B is a perspective view of an example embodiment of a headset computer.
FIG. 2 is a block diagram showing data and control communications of the example embodiment of FIGS. 1A-1B according to principles of the present invention.
FIGS. 3A-3B illustrate an example of executing a native application on a host computing device (Smartphone or PC) using the headset computing device in accordance with principles of the present invention.
FIGS. 4A-4B illustrate a further example of executing a native application on a host computing device (Smartphone or PC) using the headset computing device in accordance with principles of the present invention.
FIG. 5 is a flow diagram illustrating an example method of operating a host application using a headset computer in accordance with principles of the present invention.
FIG. 6 is a high level software diagram illustrating an example embodiment of how a headset computing device using a speech recognition and head tracking user interface may be used to control an application executed on a host computing device.
FIG. 7 is a flow diagram of embodiments of the present invention.
A Headset Computer (HSC), having computational and operational capabilities sufficient at least for use as an auxiliary display and end-user input device, is operationally connected to a “host” (or alternatively “main” or “controller”) computing device enabling a conventional software application executed on the host to be displayed simultaneously through the host and the HSC and controlled using end-user inputs received at the HSC. Host computing devices may include Smartphones, tablets or personal computers (PC's). The HSC and host can be operatively couple using wires or preferably wirelessly.
According to an example method of the present invention, a Smartphone or PC can be the primary (or main) computing device, and the HSC can be an auxiliary display and user interface to the Smartphone or PC computing device. The Smartphone or PC can run its own native software using its own display in a conventional and customary manner. The HSC alone cannot execute such a software application due to its lack of traditional user interface hardware, such as a touch screen, keyboard, and/or mouse. Therefore, in order to accommodate hands-free computing, the Smartphone or PC can execute a second class of application that, while running directly on the Smartphone or PC, is specifically designed to use the HSC as a display output for the native application and to use the Automatic Speech Recognizer (ASR) and Head-Tracker (HT) functionally built into the HSC user input devices.
In example embodiments of the present invention, the HSC contains at least sufficient computational and operational capabilities to: (i) display a screen-full of information; (ii) monitor head-gesture tracking and feed head-movement information back to the main computer (e.g., Smartphone or PC); and, (iii) monitor and process speech, feeding speech recognition results back to the main computer. By pairing the HSC with the main computer (Smartphone or PC), the main computer may effectively hold specially created hands-free applications that primarily run on the main computer, but use the display of and augmented input from the HSC.
Example embodiments of the HSC 100 can receive user input through recognizing voice commands, sensing head movements, 110, 111, 112 and hand gestures 113, or any combination thereof. Microphone(s) operatively coupled or preferably integrated into the HSC 100 can be used to capture speech commands which are then digitized and processed using automatic speech recognition (ASR) techniques. Gyroscopes, accelerometers, and other micro-electromechanical system sensors can be integrated into the HSC 100 and used to track the user's head movement to provide user input commands. Cameras or other motion tracking sensors can be used to monitor a user's hand gestures for user input commands. The voice command automatic speech recognition and head motion tracking features such a user interface overcomes the hands-dependant formats of other mobile devices.
FIG. 1B is a perspective view showing some details of an example embodiment of a headset computer 100. The example embodiment HSC 100 generally includes, a frame 1000, strap 1002, rear housing 1004, speaker 1006, cantilever, or alternatively referred to as an arm or boom 1008 with a built in microphone(s), micro-display subassembly 1010, and peripheral port 1020.
According to aspects that will be explained in more detail below, the HSC display device 100 with micro-display 1010 can enable an end-user to select a field of view 300 (FIG. 1A) within a much larger area defined by a virtual display 400. The user can typically control the position, extent (e.g., X-Y or 3D range), and/or magnification of the field of view 300.
While the example embodiments of an HSC 100 shown in FIGS. 1A-1B are monocular micro-displays presenting a single fixed display element supported within the field of view in front of the face of the user with a cantilevered boom, it should be understood that other mechanical configurations for the auxilliary display device HSC 100 are possible.
FIG. 2 is a block diagram showing high-level details of the HSC device 100, host 200 and the data that travels between them. A bi-directional communications link 150 can be established between the HSC 100 and the host computing device 200 (for more details of such a communications link see U.S. Pat. No. 8,355,671 entitled “Method And Apparatus For Transporting Video Signal Over Bluetooth Wireless Interface” issued Jan. 15, 2013, which is herein incorporated by reference in its entirety).
In an example embodiment of the present invention, an external “smart” device 200 (also referred to herein as a “host” device or “controller”) is used in conjunction with a HSC 100 to provide information and hands-free control to a user. The example embodiment uses the transmission of small amounts of data between the host 200 and HSC 100, and, thus, provides a more reliable data transfer method and control method for real-time control.
A preferred embodiment involves the collaboration between two devices, one of which is an HSC 100. The other device (controller or host) is a smart device 200, which is a device that executes an application, processes data and provides functionality to the user. Example controllers include, but are not limited to, Smartphones, tablets and laptops.
The controller 200 and HSC 100 can be paired over a suitable transport, typically a wireless bi-directional communications link, such as Bluetooth. Because the amount of data transferred by such a suitable protocol is low, the transport can be shared with other, activities requiring higher bandwidth.
The controller 200 can run software, such as a second class of application, running at a top layer of a software stack, that enables it to send instructions to the HSC 100. In order to avoid having to send data outlining the entire screen contents on the HSC 100, the controller 200 instead can send instructions that the HSC 100 can interpret using software functioning on the HSC 100. The instructions sent from the controller 200 can describe actions to perform, including on-screen notifications, messages and other graphical elements. Such instructions can also include requests to play one of a set of pre-set (predefined) sound sequences or control other components of the HSC 100.
The instructions can further include pre-set “styled elements”. Styled elements can include short-hand instructions or code relating to how to lay out a display screen, which text to display, text font, font size, and other stylistic element information such as drawing arrows, arrow styles and sizes, background and foreground colors, images to include or exclude, etc. Therefore, for each element type (notification, message, textbox, picturebox, etc.) there are multiple display styles. The styled elements can allow the controller 200 great flexibility in how information is displayed on the HSC 100. In this way, for given information, visual elements displayed on the HSC 100 can differ from the visual elements displayed on the display of controller 200.
Higher bandwidth activities can be requested while the bi-directional communications protocol is transferring display instruction. Higher bandwidth traffic can be separate from the low bandwidth traffic of the present invention. For example, the HSC 100 can be utilized for a video call, whereby a request is sent to acquire access and control of the display, camera and audio communications peripherals (microphone and speaker) and to display live video and play live audio on the HSC 100. Such requests can be part of the accessory protocol (e.g., low bandwidth instructions for HSC 100), but the high bandwidth video call traffic can be outside of it.
Through the transmission of styled elements the amount of data to be transmitted over the connection 150 is small-simple instructions on how to lay out a screen, which text to display, and other stylistic information, such as drawing arrows, or the background colors, images to include, etc. Additional data can be streamed over the same link 150, or another connection and displayed on screen 1010, such as a video stream if required by the controller 200.
In another embodiment, after the bi-directional communications link is established, a software application native to the host computing device can be executed by the host 200 processor. The native application can generate a feed of output images for display. So that the output images may be used for multiscreen display, a second class of application can be executed by the host to append the output images with a markup language, such as Hyper Text Markup Language 5 (HTML5). The host can communicate the marked-up display data to the HSC 100 for simultaneous display of application output through the displays of both the host device 200 and the HSC 100 but in respective format, layout, user-interface. The HSC 100 may process the marked-up display data to present available menu selections and prompts to the end-user of HSC 100 so that the end-user can interface through HSC 100 with the application running on the host 200 in a hands-free manner. For example, a visual prompt may include one or more text boxes indicating recognized verbal commands and/or arrows or other motion indicators indicating head tracking (and/or hand motion) commands. Audio prompts may, for example, include a text-to-speech machine recitation of recognized verbal commands.
The HSC device 100 can receive vocal input from the user via the microphone, hand movements or body gestures via positional and orientation sensors, the camera or optical sensor(s), and head movement inputs via the head tracking circuitry such as 3 axis to 9 axis degrees of freedom orientational sensing. These command inputs can be translated by software in the HSC device 100 into equivalent host device 200 commands (e.g., touch gesture, keyboard and/or mouse commands) that are then sent over the Bluetooth or other wireless interface 150 to the host 200. The host 200 then can interpret the translated equivalent commands in accordance with the host operating system and executed native application software to perform various functions.
Among the equivalent commands may be one to select a field of view 300 (FIG. 1A) within the virtual display 400 and return that selected screen data to the HSC device 100. Thus, it should be understood that a very large format virtual display area might be associated with application software or an operating system running on the host 200. However, only a portion of that large virtual display area 400 within the field of view 300 can be returned to and actually displayed by the micro-display 1010 of HSC device 100.
FIGS. 3A and 3B illustrate an example of executing a native Global Positioning System (GPS) maps-based application on a host computing device 200 (Smartphone or PC) using the headset computing device 100 in accordance to principles of the present invention.
In the present example embodiment, at least for purposes of illustration, the HSC can be equipped with sufficient processing equipment and capabilities to only process display data, monitor user speech and motion input and translate such input into equivalent commands. In the illustrative example embodiment of FIG. 3, the HSC 100 is not equipped with a GPS receiver module and does not have a direct Internet Connection.
The host computing device 200 (e.g., Smartphone or other primary computing device equipped with a GPS receiver) can generate a map screen image based on its current coordinates. Typically, a Smartphone 200 is equipped with a GPS receiver and associated processing software such that the Smartphone 200 can provide its current location. Further, the Smartphone 200 usually is equipped with Internet connectivity to enable the downloading of a relevant map graphic. The map graphic can be post-processed by a second class of application running on the Smartphone such that the post-processed marked-up graphic data is sent to the HSC 100 for rendering and display to the user through field of view 300. The post-processed data can include a set of recognized speech commands 3030 sent in text form to the HSC 100, such as “Satellite”, “Pan”, “Zoom In”, and “Quit”, as illustrated in FIG. 3A. The HSC 100, after receiving and processing the marked-up data, can start listening for the user to select one of the commands 3030 by speaking/uttering the same.
While the map is being displayed on the HSC 100 through field of view 300, head-gesture movements can be monitored by the HSC 100, translated to equivalent touch-screen or keyboard (physical or virtual) commands and fed directly back to the Smartphone 200 via the bi-directional communications link 150 for processing in accordance with the GPS map-based application. For example, if the user's head is moved left, then the Smartphone 200 may pan the map left and send an updated graphic to the HSC display 1010. In this way Smartphone 200 can perform the processing work, while the HSC 100 can provide an auxiliary display and user interface.
At the same time the user may speak a valid recognized command 3030, such as “Satellite”. The user may be made aware that “Satellite” is a valid command by being visually or audibly prompted through the HSC 100 processing the marked-up data produced from the Smartphone application, which when processed by the HSC 100 instructs the HSC 100 to listen for valid commands 3030. In recognizing the command word “Satellite” the HSC 100 can turn the spoken language into an equivalent digital command and send the digital command back to the Smartphone 200. The Smartphone 200 can then respond to the received equivalent digital command by generating a new map view and sending the new generated view to the HSC 100 for display through the field of view 300 of the micro-display 1010, as is shown in FIG. 3B. As such, the Smartphone 200 does not need to have voice recognition capabilities; this functionality can be handled by the HSC 100.
It is further envisioned that an end-user of the HSC 100 can select from an array of native applications stored in the memory or other storage device of the Smartphone 200 for hands-free operation. The HSC 100 user will be able to select which application to operate via an onscreen (HSC screen 300) menu and associated voice commands. Such a menu can be generated by the second class of application and sent to the HSC from the Smartphone 200 in the manner described above. Once executed, the second class of application can determine which native applications are compatible and can be accessed with the HSC 100.
During all of the HSC 100 operations, normal functionality of the host computing device 200 (Smartphone or PC) may continue. Such an approach allows the HSC 100 to be a much simpler device than in previously known (HSC) embodiments without giving up any functionality as perceived by the end-user. Computational intelligence is provided mainly by the host 200. However, it should be understood that all of the advances of the HSC 100 can remain available, such as providing hands-free operation and navigation using head tracking and input commands via combination of head tracking and speech commands, etc.
FIGS. 4A and 4B illustrate another example of executing a native application, for example an e-mail application, on a host computing device (Smartphone or PC) 200 using the headset computing device 100 in accordance with principles of the present invention.
In the example of FIGS. 4A and 4B, at least for purposes of illustration, the HSC 100 is equipped with sufficient processing equipment and capabilities to mostly process display data, monitor user speech and motion input and translate such inputs into equivalent commands; the HSC 100 is not equipped with an Internet connection.
The host computing device 200, here depicted as an iPhone®, generates a screen image based on its native e-mail application. (iPhone is a registered trademark of Apple Inc., Cupertino, Calif.) Typically, an iPhone (or Smartphone) 200 is equipped with an e-mail application and associated processing and communications capabilities such that the iPhone 200 can access an e-mail server via an Internet connection. The e-mail application display output 2010 a graphic feed is post-processed by a second class of applications running on the Smartphone 200, such that the post-processed marked-up graphic data is sent to the HSC 100 for rendering and display to the user through field of view 300. The post-processed data can include a set of recognized speech commands 3030 sent in text form to the HSC 100, such as “Reply”, “Reply All”, “Discard”, “Next”, “Inbox”, and “Quit”, as illustrated in FIG. 4B. The HSC 100, after receiving and processing the marked-up data can start listening for the user to speak (utter one or more of) the commands 3030.
While the e-mail application is being displayed on the HSC 100 through field of view 300, head-gesture movements can be monitored by the HSC 100, translated to equivalent touch-screen or keyboard (physical or virtual) commands, and fed directly back to the Smartphone 200 for processing in accordance with the e-mail application. For example, if the user's head is moved left—as prompted by arrow 3031, then the HSC 100 generates and transmits a corresponding Smartphone 200 compatable command. In response the Smartphone 200 may return to the “Inbox” and send an updated graphic to the HSC 100 for presentation at display 1010. In this way Smartphone 200 can perform the processing work, while the HSC 100 can provide an auxiliary display and user interface.
At the same time, the user may speak a valid recognized command 3030, such as “Reply” as previously described. Upon recognizing the command words, such as “Reply”, the HSC 100 can turn the spoken language into an equivalent digital command and send the generated command back to the Smartphone 200. The Smartphone 200 can then respond to the received equivalent command by generating an updated graphic representing a reply message and send the reply message screen view 2010 b (modified for HSC 100 domain) to the HSC 100 for display through the field of view 300 of the micro-display 1010.
FIG. 5 is a high-level flow diagram of a method 500 of operating a host computing device 200 application in accordance with principles of the present invention. In the first step, the method commences (step 501). Thereafter, the host device 200 can execute a native application (step 511), which then can generate a feed of output images, also referred to as display output (step 513). The generated feed of output images can be displayed through the host display screen (step 519) in an appropriate format. Next, user input at device 200 can be monitored for user instructions (e.g., control commands) to be executed by the native application (step 521). If user commands are detected, such as touch-screen inputs or typed inputs, then such commands can be executed according to the native application (step 511). Otherwise, it is determined whether the host 200 process is completed (step 523). If the process is not yet complete, execution can continue according to the native application (step 511). If the process is complete, then the method can end (step 530).
In parallel with steps 511 and 513 (or in series—before or after), a bi-directional communications link can be established between host device 200 and HSC 100 (step 505). Also in parallel with steps 511, 513, and 505 (or in series—before or after), the HSC 100 can be operated in an automatic speech recognition (ASR) and head tracking (HT) mode of operation during which end-user input (e.g., spoken verbal commands and/or head motion) is monitored and recognized as user commands 512. After beginning operation in ASR/HT mode 512, HSC 100 can request display output from host 200 (step 514) of the executing native application on host 200.
The HSC Auxiliary application, a second class of application, can receive the input request from the HSC 100 and the display output generated by the executed native application and then append mark-up instructions to the display output data (step 515). The appended marked-up display data can then transmitted to the HSC 100 via the established communications link (shown as 150 in FIG. 2) (step 517). The HSC 100 can next determine whether the display output (as modified/marked-up by host 200) was received (step 518). If the output was not received, then the request can be made again (step 514). If the output was received, then the received display output data can be translated for rendering through the micro-display 1010 (step 520).
Next, the translated data is rendered and displayed through the HSC display (for example, micro-display 1010) (step 522). Displaying the output generated by the native application though the host display (step 519) and through the HSC display (step 522) can occur substantially simultaneously but in respective domains/formats. After displaying the output generated by the native application though the HSC display (step 522), HSC 100 determines whether user input (ASR/HT) at the HSC has been recognized (step 524). If end-user input (ASR/HT) at HSC 100 has been detected (at step 524), then such input can be translated to equivalent host device 200 commands and transmitted to the host device as user input (step 526). If no end-user input at HSC 100 is determined, then HSC 100 determines whether the HSC 100 process is completed (step 528). If the process at HSC 100 is not yet complete, the process can continue to operate according to the ASR/HT mode (step 512). If the HSC 100 process is complete, then the method can end (step 530).
FIG. 6 is a high level software diagram indicating how a HSC 100 using a speech recognition and head tracking user interface may be used to control an application executed on a host computing device 200. A HSC software stack 6100 can include a kernal of an operating system (OS), such as a Linux kernal 6101, libraries and runtime libraries for implementing functions built into the programming language during the execution of an application, such as those of Libraries/Runtime stack 6102, application framework for implementing the standard structure of an application, such as Application Framework 6103, and an application which can run on top of the OS kernal, libraries and framework, such as HSC Display Application 6104. The HSC Display Application 6104 can allow the end-user to use the HSC 100 as an auxiliary display and hands-free user-interface and can contain an icon and menuing interface.
Applications running within the context of the HSC Display Application 6104 may include a Speech Recognition input 6121, Head Tracking input 6122, translation module 6123 for translating marked-up display output (from Host 200) and for translating ASR/HT input (at HSC 100) to equivalent Host 200 commands, and Virtual Network Connection 6124, which allows a bi-directional communications link between the HSC 100 and host device 200 to be established.
A host software stack 6200 can include a kernal of an operating system (OS), such as a Linux kernal 6201, libraries and runtime libraries for implementing functions built into the programming language during the execution of an application, such as those of Libraries/Runtime stack 6202, application framework for implementing the standard structure of an application, such as Application Framework 6203, an application which can run on top of the OS kernal, libraries and framework, such as Native Application 6204, and a second class of application that runs on top of the stack and Native Application 6204, such as HCS Auxiliary Display Interface Application 6205. As described above in detail, the HCS Auxiliary Display Interface Application 6205 can allow the end-user to use the HSC 100 as an auxiliary display and hands-free user-interface to control the Native Application 6204 executing an host 200. Applications running within the context of the HCS Auxiliary Display Interface Application 6205 may include a Virtual Network Connection 6124, which allows a bi-directional communications link between the host device 200 and HSC 100 to be established. The host software stack 6200 can be more extensive and complex than the HSC software stack 6100.
FIG. 7 shows a high-level flow diagram of an example embodiment of the present invention. FIG. 7 is a high-level flow diagram illustrating the steps of an alternate method 700 of displaying on a headset computer output from a Smartphone application. The method 700 of displaying on a headset computer output from the Smartphone application 700 can include, executing an application on the Smartphone (step 710), generating output of the executed application for display through a headset computer, including the Smartphone configuring and transmitting instructions in a description language indicating actions for the headset computer to display the output of the executed application (step 720), and receiving over a low bandwidth communications link at the headset computer the configured instructions, and in response to the received configured instructions the headset computer forming or rendering a display of the generated output based on the indicated actions to perform (the instructions), wherein the actions include any of on-screen notifications, messages, graphical elements, request to play one of a plurality of predefined sound sequences and control a component of the headset computer (step 730).
The actions can be of respective element types and for each element type the instructions can indicate one of a plurality of styles predefined for the headset computer. The styles can be style elements. The formed display rendered in the headset domain can include menu selections and prompts presented in terms of a speech recognition/head tracking user interface. Such menu selections and outputs can be visually and audibly presented to a user. The communications link between the Smartphone and headset computer can be a wireless communications link, for example Bluetooth, Wi-Fi or other communications protocol.
The alternative example process illustrated in FIG. 7 can further include, monitoring for input from a speech recognition/head tracking user interface at the headset computer, in response to receiving the speech recognition/head tracking command input, translating the received speech recognition/head tracking command to an equivalent Smartphone command at the headset computer, and transmitting the equivalent Smartphone command to the Smartphone to control the executed application. Such a method can effectively enable speech (voice command) and hands-free (head motion tracking) user control of the executed application.
Further example embodiments of the present invention may be configured using a computer program product; for example, controls may be programmed in software for implementing example embodiments of the present invention. Further example embodiments of the present invention may include a non-transitory computer readable medium containing instruction that may be executed by a processor, and, when executed, cause the processor to complete methods described herein. It should be understood that elements of the block and flow diagrams described herein may be implemented in software, hardware, firmware, or other similar implementation determined in the future. In addition, the elements of the block and flow diagrams described herein may be combined or divided in any manner in software, hardware, or firmware. If implemented in software, the software may be written in any language that can support the example embodiments disclosed herein. The software may be stored in any form of computer readable medium, such as random access memory (RAM), read only memory (ROM), compact disk read only memory (CD-ROM), and so forth. In operation, a general purpose or application specific processor loads and executes software in a manner well understood in the art. It should be understood further that the block and flow diagrams may include more or fewer elements, be arranged or oriented differently, or be represented differently. It should be understood that implementation may dictate the block, flow, and/or network diagrams and the number of block and flow diagrams illustrating the execution of embodiments of the invention.
in response to received speech recognition and head tracking commands, translating the received speech recognition and head tracking commands to equivalent Smartphone commands at the headset computer and transmitting said equivalent Smartphone command to the Smartphone to control the native application.
2. The method of claim 1, wherein the generated output for display through the headset computer includes a markup language file.
3. The method of claim 2, wherein the markup language is HyperText Markup Language 5 (HTML5).
4. The method of claim 1, wherein the translating the received output for rendering in the headset domain results in presenting to the end-user menu selections and prompts in terms of the speech recognition and head tracking user interface commands.
5. The method of claim 4, wherein the menu selections and prompts are audibly and visually presented to the end-user.
6. The method of claim 1, wherein the receiving by the headset computer and the transmitting by the headset computer are performed wirelessly.
7. The method of claim 6, wherein the receiving by the headset computer and the transmitting by the headset computer are performed wirelessly using Bluetooth or Wi-Fi standards.
8. The method of claim 1, wherein the translations by the headset computer effectively enable speech recognition and hands-free user interface with the executed native Smartphone application.
the headset translating to equivalent Smartphone commands includes translating from speech recognition and head tracked commands to touch type commands.
10. A method of claim 1, wherein the executed native Smartphone application is an image and/or video viewing application and the equivalent Smartphone commands transmitted by the headset computer include a command to display an image and/or video through the Smartphone.
11. A method of claim 1, wherein the native Smartphone application is configured to receive multi-media content driven from the headset computer.
displaying the captured image or video through the headset computer and through the Smartphone.
the headset communications module communicating the equivalent Smartphone commands to the Smartphone communications module to control the native application.
14. The dual display system of claim 13, wherein the display output includes a markup language file.
15. The dual display system of claim 14, wherein the markup language is HyperText Markup Language 5 (HTML5).
16. The dual display system of claim 13, wherein the display output for rendering through the micro-display includes menu selections and prompt in terms of speech recognition and head tracking user interface for the end-user.
17. The dual display system of claim 16, wherein the menu selections and prompts are audibly and visually presented to the end-user.
18. The dual display system of claim 13, wherein the Smartphone communications module and the headset communications module are wireless communications modules.
19. The dual display system of claim 18, wherein the wireless communications modules are Bluetooth or Wi-Fi modules.
20. The dual display system of claim 13, wherein the headset computing device effectively enables the speech recognition and head tracking user interface to control the native application.
21. The dual display system of claim 13, wherein the native application uses a touch-type user interface commands and the translation module translates the received speech recognition and head tracking user interface end-user commands to the touch-type user interface commands.
22. The dual display system of claim 13, wherein the native Smartphone application is an image and/or video viewing application and the equivalent Smartphone commands include a command to display an image and/or video through the native display of the Smartphone.
23. The dual display system of claim 13 wherein the native Smartphone application is configured to receive multi-media content from the headset computing device.
Notification of Transmittal of The International Search Report and The Written Opinion of the International Searching Authority, or the Declaration, Date of Mailing: Dec. 5, 2013 in re: PCT/US2013/036221, Title "Headset Computer (HSC) As Auxiliary Display With ASR And HT Input."

References: Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61
 Application No. 61