Hands-Free, Eyes-Free Mobile Device for In-Car Use
Claim Score by NHIP
Abstract
In one embodiment, a method determines an event at a mobile device and a movement value for a speed of movement of the mobile device based on the event. The movement value is compared to a threshold. If the movement value has passed the threshold, the method enables a mode such that the mobile device is configured to announce information to a user of the mobile device and configured to receive an audible command from the user of the mobile device.

Term
Projected expiry 30 August 2030.
- Priority and filed
- Published
- Today
- Projected expiry
20 claims: 3 independent, 17 dependent
- 1Broadest claimClaim Score 86, broad(NHIP)A method comprising:determining an event at a mobile device;determining a movement value for a speed of movement of the mobile device based on the event;comparing the movement value to a threshold;and if the movement value has passed the threshold, enabling a mode such that the mobile device is configured to announce information to a user of the mobile device and configured to receive an audible command from the user of the mobile device.
- 12A computer-readable storage medium containing instructions for controlling a computer system to perform a method, the method comprising:determining an event at a mobile device;determining a movement value for a speed of movement of the mobile device based on the event;comparing the movement value to a threshold;and if the movement value has passed the threshold, enabling a mode such that the mobile device is configured to announce information to a user of the mobile device and configured to receive an audible command from the user of the mobile device.
- 20An apparatus comprising:one or more computer processors;and a computer-readable storage medium comprising instructions for controlling the one or more computer processors to perform a method, the method comprising: determining an event at a mobile device;determining a movement value for a speed of movement of the mobile device based on the event;comparing the movement value to a threshold;and if the movement value has passed the threshold, enabling a mode such that the mobile device is configured to announce information to a user of the mobile device and configured to receive an audible command from the user of the mobile device.
Independent claims3
65 paragraphs in 4 sections, as filed
BACKGROUND
p-0002Particular embodiments generally relate to mobile devices and more specifically to a hands-free, eyes-free mode for the mobile device.
p-0003When driving a car, the user may receive a telephone call. If the user answers the call, the user takes his/her hand off the steering wheel and also diverts his/her eyesight to the mobile device to answer the call, which is very dangerous. Also, laws exist that prohibit the use of mobile devices while driving. Thus, a user should pick up the mobile device and answer the call in the above manner.
p-0004One option for the user is to use a Bluetooth headset to answer the call. However, in this case, the user must press a button on the Bluetooth headset to answer the call. Further, in most cases, the user would pick up the mobile device and look at the display to see who is calling. This scenario is also dangerous because the user is either taking his/her hands off the steering wheel of the car to answer the call using the Bluetooth headset or diverting his/her eyesight to look at the mobile device. Further, Bluetooth headsets are an added expense for the user.
p-0005In another example, the mobile device's accelerometer may be used to activate the mobile device. For example, by the user taking the mobile device and moving it up to his/her ear, a telephone application may be turned on. In this case, the acceleration of the mobile device in a certain direction is used to turn on the telephone application. However, in this case, the user is still handling the mobile device, which requires the user to take his/her hand off the steering wheel and his/her eyes off the road.
SUMMARY
p-0006In one embodiment, a method determines an event at a mobile device and a movement value for a speed of movement of the mobile device based on the event. The movement value is compared to a threshold. If the movement value has passed the threshold, the method enables a mode such that the mobile device is configured to announce information to a user of the mobile device and configured to receive an audible command from the user of the mobile device.
p-0007In one embodiment, a computer-readable storage medium contains instructions for controlling a computer system to perform a method. The method determines an event at a mobile device and a movement value for a speed of movement of the mobile device based on the event. The movement value is compared to a threshold. If the movement value has passed the threshold, the method enables a mode such that the mobile device is configured to announce information to a user of the mobile device and configured to receive an audible command from the user of the mobile device.
p-0008In another embodiment, an apparatus includes one or more computer processors and a computer-readable storage medium comprising instructions for controlling the one or more computer processors to perform a method. The method determines an event at a mobile device and a movement value for a speed of movement of the mobile device based on the event. The movement value is compared to a threshold. If the movement value has passed the threshold, the method enables a mode such that the mobile device is configured to announce information to a user of the mobile device and configured to receive an audible command from the user of the mobile device.
p-0009The following detailed description and accompanying drawings provide a better understanding of the nature and advantages of the present invention.
BRIEF DESCRIPTION OF THE DRAWINGS
p-0010<figref idrefs="DRAWINGS">FIG. 1</figref> depicts an example of a mobile device according to one embodiment.
p-0011<figref idrefs="DRAWINGS">FIG. 2</figref> depicts a more detailed example of a mode controller according to one embodiment.
p-0012<figref idrefs="DRAWINGS">FIG. 3</figref> depicts a simplified flowchart of a method for enabling the hands-free, eyes-free mode according to one embodiment.
p-0013<figref idrefs="DRAWINGS">FIG. 4</figref> depicts a simplified flowchart of a method for answering a telephone call using the hands-free, eyes-free mode according to one embodiment.
p-0014<figref idrefs="DRAWINGS">FIG. 5</figref> depicts a simplified flowchart of a method for receiving voice commands in the hands-free, eyes-free mode according to one embodiment.
p-0015<figref idrefs="DRAWINGS">FIG. 6</figref> depicts a simplified flowchart of a method for processing a second call while a first call has been connected according to one embodiment.
DETAILED DESCRIPTION
p-0016Described herein are techniques for a hands-free, eyes-free mode for a mobile device. In the following description, for purposes of explanation, numerous examples and specific details are set forth in order to provide a thorough understanding of embodiments of the present invention. Particular embodiments as defined by the claims may include some or all of the features in these examples alone or in combination with other features described below, and may further include modifications and equivalents of the features and concepts described herein.
p-0017<figref idrefs="DRAWINGS">FIG. 1</figref> depicts an example of a mobile device <b>100</b> according to one embodiment. Mobile device <b>100</b> may be a device that can receive or make telephone calls using a transceiver <b>108</b>. For example, mobile device <b>100</b> includes a cellular telephone, personal computer, laptop computer, personal digital assistant (PDA), tablet computer, and other mobile devices that can receive or make calls.
p-0018Particular embodiments use a mode that enables a user to operate mobile device <b>100</b> in a hands-free and eyes-free manner. The hands-free manner is where the user can operate mobile device <b>100</b> without touching mobile device <b>100</b> with his/her hands during operation. The eyes-free manner is where the user does not need to look at a display of mobile device <b>100</b> to operate mobile device <b>100</b>. Thus, the hands-free, eyes-free mode allows a user to operate mobile device <b>100</b> without touching mobile device <b>100</b> and looking at mobile device <b>100</b>. For example, as will be described in more detail below, a user may answer telephone calls or perform other actions without touching or looking at mobile device <b>100</b>.
p-0019In one embodiment, a movement value is used to activate the hands-free, eyes-free mode. For example, the speed of movement of mobile device <b>100</b> is determined. A global positioning satellite (GPS) sensor <b>102</b> may be used to determine the speed at which the mobile device is moving. For example, if mobile device <b>100</b> is situated in a moving car, GPS sensor <b>102</b> is able to determine the speed at which mobile device <b>100</b> (and also the car) is traveling. In this situation, mobile device <b>100</b> may be stationary in the moving car; however, the car is moving and the speed of movement of the car is measured by GPS sensor <b>102</b> of mobile device <b>100</b>. In one embodiment, the speed of movement measured is different from the acceleration of mobile device <b>100</b>. Acceleration is the change in velocity of time. The instantaneous speed of an object is the magnitude of its instantaneous velocity or the scalar equivalent of velocity. In one embodiment, the speed of movement may be the instantaneous speed of mobile device <b>100</b>. However, in other embodiments, speed (absolute number hit), acceleration, weight (e.g., weight of someone sitting in a seat), and presence (e.g. IR or motion sensors), touch (e.g. steering wheel may be used.
p-0020GPS sensor <b>102</b> may communicate with satellites to determine the speed of movement. In one example, GPS sensor <b>102</b> may calculate the speed using algorithms that compute speed by a combination of movement per unit time and computing the doppler shift (e.g., the difference between the expected frequency of the satellite signal and the actual frequency of the incoming signal) in the signals from the satellites.
p-0021A mode controller <b>104</b> then uses the movement value to determine if the hands-free, eyes-free mode should be activated. For example, when the movement value passes a certain threshold, then the hands-free, eyes-free mode may be activated. In one example, if the movement value indicates mobile device <b>100</b> is moving at a speed greater than a programmed threshold (e.g., 5 miles per hour (mph)), then mode controller <b>104</b> may activate the hands-free, eyes-free mode.
p-0022In one example, a user may set a monitoring phase that will monitor whether the hands-free, eyes-free mode should be activated. For example, the user may enable an application on mobile device <b>100</b> to perform the monitoring actively or in the background. The monitoring may be performed while mobile device <b>100</b> is in a turned on mode or a powered down mode. The powered down mode may be when mobile device <b>100</b> is in a stand by or low power mode. In the monitoring phase, mode controller <b>104</b> may communicate with a transceiver <b>108</b> to intercept telephone calls that are received and determine which mode should be used to answer the telephone call. For example, if mobile device <b>100</b> is traveling at a speed of movement greater than the threshold, then the hands-free, eyes-free mode may be activated. If the speed of movement is not greater than the threshold, then the telephone call may be processed normally.
p-0023A processor <b>106</b> may be used to control operations of mobile device <b>100</b>. For example, processor <b>106</b> interacts with a speech recognizer <b>108</b> and a speech synthesizer <b>110</b>. Speech recognizer <b>108</b> is configured to recognize utterances of a user, such as phrases or words, received from microphone <b>112</b>. Speech recognizer <b>106</b> may convert the speech into a digital form that can be processed. A person of skill in the art will recognize how to recognize speech according to the teachings and disclosures herein.
p-0024Speech synthesizer <b>108</b> is configured to output utterances, such as words or phrases, through a speaker <b>114</b>. Speech synthesizer <b>108</b> may synthesize words or phrases and output them through microphone <b>112</b>. A person of skill in the art will recognize how to synthesize speech according to the teachings and disclosures herein. The use of speech synthesizer <b>108</b> and speech recognizer <b>106</b> will be described in more detail below.
p-0025In one example as will be described in more detail below, when in the hands-free, eyes-free mode, speaker <b>114</b> is used to output announcements to a user requesting input from the user. For example, speaker <b>114</b> may announce that a telephone call has been received from a caller. Microphone <b>112</b> may then be used to receive a voice command from the user. Processor <b>106</b> may then process the voice command. For example, the user may request that the call be answered and then the call is answered. Speaker mode may be enabled when the call is answered where the speech from the caller is output through speaker <b>114</b>. In this case, the user does not need to touch or look at mobile device <b>100</b> to answer the call. Other actions may also be performed using the hands-free, eyes-free mode, and will be described in more detail below.
p-0026<figref idrefs="DRAWINGS">FIG. 2</figref> depicts a more detailed example of mode controller <b>104</b> according to one embodiment. Mode controller <b>104</b> may interact with GPS sensor <b>102</b>. Although a GPS sensor is being described, other methods of determining the speed of movement of mobile device <b>100</b> may be used. A GPS sensor interface <b>202</b> is used to interact with GPS sensor <b>102</b>. For example, GPS sensor interface <b>202</b> may send a request for a speed of movement value from GPS sensor <b>102</b>. When GPS sensor <b>102</b> receives the request, GPS sensor <b>102</b> determines the speed of movement for mobile device <b>100</b> and sends the speed of movement value back to GPS interface <b>202</b>.
p-0027GPS sensor interface <b>202</b> may send the request at different times. For example, a request monitor <b>204</b> is used to determine when requests are sent. In one example, request monitor <b>204</b> may determine that a request should be sent when a telephone call is received at mobile device <b>100</b>. Requests may also be sent at other times, such as periodically or when other events occur.
p-0028In another embodiment, GPS sensor <b>102</b> may send the speed of movement value to GPS sensor interface <b>202</b> without receiving a request. For example, GPS sensor <b>102</b> may send the speed of movement value periodically. Also, when the speed of movement becomes a non-zero value (i.e., when movement is detected), then GPS sensor <b>102</b> may send the speed of movement value periodically. Additionally, GPS sensor <b>102</b> may send an indication to GPS sensor interface <b>202</b> that the speed of movement value is above a certain amount and this can prompt GPS sensor interface <b>202</b> to start sending requests upon an event occurring.
p-0029When the speed of movement value is received at GPS interface <b>202</b>, a threshold comparison block <b>206</b> is used to compare the speed of movement value to a threshold. The threshold may be a programmable value that may be set at any value. The value may be set by a user of mobile device <b>100</b> or by another party. In one example, the threshold may be expressed in miles per hour or another unit of speed measurement. For example, the threshold may be set to a value (e.g., 5 mph) that would indicate that the user of mobile device <b>100</b> is in a moving object.
p-0030Threshold comparison block <b>206</b> may output a control signal based on the comparison. For example, when the speed of movement value passes the threshold (e.g., goes above the threshold), then threshold comparison block <b>206</b> may output a signal to a mode changer <b>208</b> indicating that the speed of movement value has passed the threshold. For example, if the threshold is 5 miles per hour, when the speed of movement value goes above 5 miles per hour, then mode changer <b>208</b> is notified that the threshold has been passed. Mode changer <b>208</b> may then change the mode of operation to the hands-free, eyes-free mode.
p-0031Different uses for the hands-free, eyes-free mode will now be described. A general method will be described using the hands-free, eye-free mode and then more specific methods, such as answering telephone calls, will be described.
p-0032<figref idrefs="DRAWINGS">FIG. 3</figref> depicts a simplified flowchart <b>300</b> of a method for enabling the hands-free, eyes-free mode according to one embodiment. At <b>302</b>, a request for monitoring the movement is received. For example, a user may activate monitoring for the hands-free, eyes-free mode. In one example, if activated, at some point, the mode may become enabled. However, if not activated, then the hands-free, eyes-free mode may not be enabled. The activation may be an indication by a user that possible enabling of the hands-free, eyes-free mode is desired. The activation may be set by invoking an application for the hands-free, eyes-free mode, where the application may run in the background or be actively running on mobile device <b>100</b>. When the input is received, then request monitor <b>204</b> may cause the application to read the speed of movement value from GPS sensor <b>102</b> when an event occurs and then perform any other action in the hands-free, eyes-free mode.
p-0033At <b>304</b>, an event to request the speed of movement value is determined. For example, the event may be the activation, a telephone call, an internal trigger (e.g., when monitoring is performed periodically), a trigger phrase, or other events.
p-0034At <b>306</b>, mode controller <b>104</b> determines the speed of movement value. For example, a request may be sent to GPS sensor <b>102</b> for the speed of movement value. GPS sensor <b>102</b> would then measure the speed of movement of mobile device <b>100</b>.
p-0035When the speed of movement value is received, at <b>308</b>, mode controller <b>104</b> determines if the speed of movement value has passed the threshold. For example, it is determined if the speed of movement value of mobile device <b>100</b> is greater than a certain speed.
p-0036If the speed of movement value has not passed the threshold, the process may reiterate to <b>304</b> to wait for another event to occur. For example, another telephone call may be received. Also, if the speed of movement value has not passed the threshold, other actions may be performed with mobile device <b>100</b>, such as a user may answer the telephone call using normal methods, such as picking up the telephone and answering the call by pressing an answer call button.
p-0037If the speed of movement value is above the threshold, at <b>310</b>, mode controller <b>104</b> enables the hands-free, eyes-free mode for mobile device <b>100</b>.
p-0038At <b>312</b>, mobile device <b>100</b> announces information to the user to allow operation of mobile device <b>100</b>. For example, information is output such that the user does not need to look at mobile device <b>100</b>.
p-0039At <b>314</b>, mobile device <b>100</b> receives a voice command from the user. For example, microphone <b>112</b> may receive a phrase from the user. Speech recognizer <b>108</b> may recognize a phrase and provide the phrase to processor <b>106</b>.
p-0040At <b>316</b>, mobile device <b>100</b> performs an action based on the voice command received. For example, processor <b>106</b> may process the voice command based on recognition of the phrase received.
p-0041The hands-free, eyes-free mode may be used to process telephone calls along with performing other actions. A specific example for receiving a telephone call will now be described. <figref idrefs="DRAWINGS">FIG. 4</figref> depicts a simplified flowchart <b>400</b> of a method for answering a telephone call using the hands-free, eyes-free mode according to one embodiment. The method assumes that a user has activated monitoring for enabling the hands-free, eyes-free mode.
p-0042At <b>402</b>, mobile device <b>100</b> receives a telephone call. For example, the telephone call may be received through transceiver <b>108</b>. In one embodiment, mode controller <b>104</b> may intercept the call handling of a telephone call. In this case, the telephone does not ring until mode controller <b>104</b> releases the call handling for further processing.
p-0043At <b>404</b>, mode controller <b>104</b> checks the speed of movement value. For example, as described below, GPS sensor <b>102</b> may be queried for the speed of movement value. It is assumed in this case, that a comparison indicates that the speed of movement value is above the threshold. Although the check and comparison are described, the check and comparison may have been performed before the telephone call was received. For example, once the speed of movement of mobile device <b>100</b> went over the threshold, it may be noted (e.g., a flag is set) that the hands-free, eyes-free mode should be enabled upon receiving a telephone call.
p-0044At <b>406</b>, mode controller <b>104</b> enables the hands-free, eyes-free mode. In this case, actions are performed such that the user does not need to look at mobile device <b>100</b> or touch mobile device <b>100</b>. In one example, the speaker telephone is enabled in mobile device <b>100</b>. Also, in one case, the volume settings for mobile device <b>100</b> may also be overridden. For example, the volume settings to output audio from speaker <b>114</b> may be increased such that the user can hear any announcements. Also, if mobile device <b>100</b> is in a mode that does not allow audible announcements, such as a silent mode or vibrate mode, this mode may be overridden. Although these modes may be overridden, it should be noted that the user can configure mode controller <b>104</b> to not override these modes.
p-0045At <b>408</b>, mobile device <b>100</b> causes an announcement of the telephone call through speaker <b>114</b>. The announcement may be generated through speech synthesizer <b>110</b> and may include the caller ID of a caller for the telephone call. An example announcement may be “You have received a telephone call from <Caller ID information>. Would you like to answer the call?” The caller ID information may be determined from the incoming caller's telephone number. The name of the caller is then looked up in the address book of mobile device <b>100</b> and inserted into the announcement. If a name cannot be found, the telephone number may be announced.
p-0046At <b>410</b>, mobile device <b>100</b> determines if the answer command was received. For example, speech recognizer <b>108</b> may listen for certain utterances, such as words or phrases, that could be received from the user. For example, the user may indicate that the call should be answered with an answer command. The answer command may be “answer telephone” or “yes”. Also, ignoring the telephone call may be associated with the phrases “ignore” or “no”. Other words or phrases may also be used.
p-0047In one example, speech recognizer <b>108</b> may be able to distinguish voice commands while in a noisy environment. For example, when a user is riding in a moving car, the background noise may be very loud due to wind, radio, or other noises. Speech recognizer <b>108</b> may distinguish voice commands from the undesirable noise to improve performance.
p-0048If the answer command is not received, then, at <b>412</b>, mobile device <b>100</b> may ignore the call. For example, the telephone call may be sent to voicemail or other actions may be performed other than answering the telephone call.
p-0049If the answer command is received, at <b>414</b>, mobile device <b>100</b> answers the telephone call. For example, if call handling was interrupted by mode controller <b>104</b>, the call handling is released. Then, processor <b>106</b> may connect the caller with the user. At <b>416</b>, mobile device <b>100</b> enables the speaker telephone for the call. In this case, the speaker telephone is used in the telephone conversation.
p-0050Mobile device <b>100</b> may also use the hands-free, eyes-free mode to receive commands when not processing telephone calls. <figref idrefs="DRAWINGS">FIG. 5</figref> depicts a simplified flowchart <b>500</b> of a method for receiving voice commands in the hands-free, eyes-free mode according to one embodiment.
p-0051At <b>502</b>, the hands-free, eyes-free mode is activated. For example, a user may have activated the request monitoring and the speed of movement may have surpassed the threshold. At this point, the hands-free, eyes-free mode may remain enabled until the speed of movement goes below the threshold. At that point, the hands-free, eyes-free mode may be disabled. This process may continue as the speed of movement is detected over various intervals.
p-0052At <b>504</b>, mobile device <b>100</b> monitors for a voice phrase trigger. For example, mobile device <b>100</b> may be put into a mode in which certain voice phrases can trigger enablement of the hands-free, eyes-free mode. For example, a phrase such as “wake up telephone” may be used to trigger the hands-free, eyes-free mode. For example, mobile device <b>100</b> may, when not in use, transition to a powered-down mode or standby mode. In the powered-down mode, mobile device <b>100</b> may still be on but may not be active. In this case, a trigger may be used to power up mobile device <b>100</b>. Also, using the voice phrase trigger also does not cause false positives when other conversation around mobile device <b>100</b> occurs. For example, a user may not want to have an action performed using mobile device <b>100</b> and thus needs to enable mobile device <b>100</b> to receive voice commands.
p-0053At <b>506</b>, mobile device <b>100</b> determines if the voice phrase trigger is received. If not, the process may reiterate to continue monitoring. In one embodiment, the monitoring may be performed while mobile device <b>100</b> is in the active, standby, or powered-down mode.
p-0054If the voice phrase trigger is received, at <b>508</b>, mobile device <b>100</b> enables microphone <b>112</b> to receive voice commands For example, any recognized voice commands that are now received will be processed by mobile device <b>100</b>.
p-0055At <b>510</b>, mobile device <b>100</b> receives a voice command. For example, microphone <b>112</b> may receive an utterance, which is recognized by speech recognizer <b>108</b>. Processor <b>106</b> may then determine what the voice command represents.
p-0056At <b>512</b>, mobile device <b>100</b> then causes an action to be performed corresponding to the voice command. For example, various voice commands may correspond to different actions. Once the voice command is recognized, a corresponding action is looked up and the action may then be performed. In one example, once the hands-free, eyes-free mode is enabled after the voice trigger is received, the user may request that a telephone call be made. While the telephone call is being requested, mobile device <b>100</b> may also make announcements through speaker <b>114</b>. For example, if a question needs to be asked, then speech synthesizer <b>110</b> will synthesize the announcement and output it through speaker <b>114</b>. This may take the place of any actions that a user previously would have had to look at or touch mobile device <b>100</b>.
p-0057In one example, the user may want to look up a telephone number of a restaurant. The user would enable the hands-free, eyes-free mode by stating the voice phrase trigger of “Wake up telephone.” The user would then speak the voice command “What is the telephone number to restaurant <restaurant name>?” Mobile device <b>100</b> may interpret this voice command with a search for the telephone number of the restaurant. Once the restaurant telephone number is found, then mobile device <b>100</b> outputs an announcement through speaker <b>114</b> with the restaurant's telephone number. For example, the announcement may be “The restaurant's telephone number is 123-4567.” Thus, the user has performed a search on mobile device <b>100</b> and does not need to look at the result on mobile device <b>100</b>, but rather is announced the result making the search hands-free and eyes-free.
p-0058Mobile device <b>100</b> may also be used to answer a second call that is received. <figref idrefs="DRAWINGS">FIG. 6</figref> depicts a simplified flowchart <b>600</b> of a method for processing a second call while a first call has been connected according to one embodiment. At <b>602</b>, a second call is received while a first call is connected. For example, the user may be on a telephone call with a first caller. The first telephone call may have been connected via the hands-free, eyes-free mode. However, it is not necessary that the first telephone call was connected via the hands-free, eyes free mode. For example, while the user is connected to the first telephone call, the speed of movement of mobile device <b>100</b> may exceed the threshold thus activating the hands-free, eyes-free mode.
p-0059To answer the second telephone call, speaker <b>114</b> needs to be used to announce the receiving of the second telephone call. This is because the eyes-free mode should not require that the user look at mobile device <b>100</b> to determine who the second caller is. Before announcing the second caller, at <b>604</b>, microphone <b>112</b> may be disabled. Microphone <b>112</b> is disabled because particular embodiments do not want the first caller to hear the announcement that the second caller is calling. At <b>606</b>, once microphone <b>112</b> is disabled, speaker <b>114</b> announces a telephone call has been received from a second caller.
p-0060At <b>608</b>, the first telephone call may be put on hold and microphone <b>112</b> is enabled. This allows a voice command to be received from the user. At <b>610</b>, a voice command may be received regarding the second call. If a voice command that is received indicates that the second call should be ignored, at <b>610</b>, mobile device <b>100</b> returns the connection to the first telephone call.
p-0061At <b>612</b>, if the user desires to answer the second telephone call, mobile device <b>100</b> connects the second telephone call to the user. The first telephone call may be put on hold or may be disconnected.
p-0062Accordingly, a hands-free, eyes-free mobile device <b>100</b> is provided. The hands-free, eyes-free mode is enabled based on speed of movement detected. The speed of movement may be detected using a GPS sensor. The hands-free, eyes-free mode allows a user who may be driving a car or any other moving vehicle to perform actions with mobile device <b>100</b>. For example, telephone calls may be answered. Also, effectively, a car kit is provided in which the user can interact with mobile device <b>100</b> to have other actions performed.
p-0063By providing the hands-free, eyes-free mode, a user may not need to purchase a Bluetooth headset. For example, to use mobile device <b>100</b> in a moving vehicle, the user would not have to activate a Bluetooth headset. Additionally, use of a Bluetooth headset may also require the user to move their hands off of the steering wheel and thus may be more dangerous than using the hands-free, eyes-free mode of mobile device <b>100</b>.
p-0064Particular embodiments can be implemented in the form of control logic in software or hardware or a combination of both. The control logic, when executed by one or more computer processors, may be operable to perform a method described in particular embodiments. A “computer-readable storage medium” for purposes of particular embodiments may be any medium that can store instructions or control logic for controlling the one or more computer processors to perform a method described in particular embodiments in connection with an instruction execution computer system, apparatus, or device.
p-0065As used in the description herein and throughout the claims that follow, “a”, “an”, and “the” includes plural references unless the context clearly dictates otherwise. Also, as used in the description herein and throughout the claims that follow, the meaning of “in” includes “in” and “on” unless the context clearly dictates otherwise.
p-0066The above description illustrates various embodiments of the present invention along with examples of how aspects of the present invention may be implemented. The above examples and embodiments should not be deemed to be the only embodiments, and are presented to illustrate the flexibility and advantages of the present invention as defined by the following claims. Based on the above disclosure and the following claims, other arrangements, embodiments, implementations and equivalents may be employed without departing from the scope of the invention as defined by the claims.
Contents4
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2013080167A1 | Cited by | United States of America | Pre-grant |
| US11393472B2 | Cited by | United States of America | Applicant |
| USRE48749E | Cited by | United States of America | Search report |
| US9830913B2 | Cited by | United States of America | Applicant |
| EP2760015A1 | Cited by | European Patent Office (EPO) | Search report |
| US10283117B2 | Cited by | United States of America | Search report |
| US10772030B2 | Cited by | United States of America | Search report |
| US9978369B2 | Cited by | United States of America | Applicant |
| US11037560B2 | Cited by | United States of America | Search report |
| US9653080B2 | Cited by | United States of America | Applicant |
| US8996381B2 | Cited by | United States of America | Applicant |
| US2016293168A1 | Cited by | United States of America | Pre-grant |
| US9530409B2 | Cited by | United States of America | Applicant |
| US8768707B2 | Cited by | United States of America | Search report |
| US9280981B2 | Cited by | United States of America | Applicant |
| US9002412B1 | Cited by | United States of America | Search report |
| US2019304449A1 | Cited by | United States of America | Search report |
| US10657967B2 | Cited by | United States of America | Applicant |
| US2012316870A1 | Cited by | United States of America | Pre-grant |
| CN110992952A | Cited by | China | Search report |
| US9142219B2 | Cited by | United States of America | Search report |
| US2005043948A1 | Cites | United States of America | Pre-grant |
| US2006190097A1 | Cites | United States of America | Pre-grant |
| US2008057977A1 | Cites | United States of America | Pre-grant |
| US2009111544A1 | Cites | United States of America | Pre-grant |
| US2009286514A1 | Cites | United States of America | Pre-grant |
| US2009312038A1 | Cites | United States of America | Pre-grant |
| US2010111269A1 | Cites | United States of America | Pre-grant |
| US2010203830A1 | Cites | United States of America | Pre-grant |
| US2010210301A1 | Cites | United States of America | Pre-grant |
| US2010216509A1 | Cites | United States of America | Pre-grant |
| US2011065428A1 | Cites | United States of America | Pre-grant |
| US2011065484A1 | Cites | United States of America | Pre-grant |
| US2012064865A1 | Cites | United States of America | Pre-grant |
| US2012289217A1 | Cites | United States of America | Pre-grant |
| US2012329444A1 | Cites | United States of America | Pre-grant |
| US2013029654A1 | Cites | United States of America | Pre-grant |
| US2013137404A1 | Cites | United States of America | Pre-grant |
| US2013157607A1 | Cites | United States of America | Pre-grant |
| US6600975B2 | Cites | United States of America | Pre-grant |
| US7505784B2 | Cites | United States of America | Pre-grant |
| US7873392B2 | Cites | United States of America | Pre-grant |
| US8355751B2 | Cites | United States of America | Pre-grant |
2 priority claims, no other members on record
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 87152010 | United States of America | A | |
| US20100871520 | – | – | – |
53 transactions on the USPTO file
Abandoned after 2 non-final rejections, 2 final rejections and 1 RCE.
- Non-final rejections
- 2
- Final rejections
- 2
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Email NotificationEML_NTR | EML_NTR | |
| Mail Abandonment for Failure to Respond to Office ActionAbandonedMABN2 | MABN2 | |
| Aband. for Failure to Respond to O. A.AbandonedABN2 | ABN2 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Interview Summary - Applicant Initiated - ConferenceMEXAC | MEXAC | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Interview Summary - Applicant Initiated - ConferenceEXAC | EXAC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Sent to Classification ContractorPGPC | PGPC | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
2 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Information on status: application discontinuationABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTIONSTCB | STCB | |
| AssignmentAS | AS |
Numbers
- Publication
- 20120052907
- Publication, DOCDB
- 2012052907
- Publication, EPODOC
- US2012052907
- Application
- 12871520
- Application, DOCDB
- 87152010
- Application, EPODOC
- US20100871520
Titles
- English
- Hands-Free, Eyes-Free Mobile Device for In-Car Use
Classification
- CPC, 10
- H04M1/6041
- H04W4/48
- G10L15/26
- H04M1/6075
- H04M1/663
- H04M2250/10
- H04M2250/74
- H04W4/027
- H04W4/026
- H04M1/72463
- IPC, 4
- G10L21 00
- H04M1 00
- H04W4 48
- H04W68 00
- USPC, 5
- 455556100
- 455567000
- 455569200
- 704275000
- 704E21001