A driver of a vehicle is identified and a command is sent to a mobile communications device that is associated with the identified driver and that is in proximity of the vehicle to force the mobile communications device to change modes such as to enter a hands-free or other suitable mode. The driver may be identified through one or more techniques including biometric sensing, key detection, switch controls, and so forth. Additionally, the driver and/or feature settings preferred by the current driver may be identified by receiving data from the mobile communications device. The data may identify the driver ID with preferred feature settings, the mobile communications device which has an association to a driver ID with preferred feature settings, or the data may specify the preferred feature settings.
|
13. A method comprising:
detecting an identity of a driver of a vehicle through the driver coming in physical contact with a driver identification module located within the vehicle;
detecting an identity of a mobile communication device in close proximity to the vehicle, wherein said detecting the identity of the mobile communication device in close proximity to the vehicle triggers the performance of the following steps:
determining at least one mobile telephone associated with the identity of the driver of the vehicle;
comparing the identity of the mobile communication device with the at least one mobile telephone associated with the identity of the driver; and
when the identity of the mobile communication device matches one of the at least one mobile telephone associated with the identity of the driver, then sending a command to the mobile communication device to cause the mobile communication device to change a mode.
7. A tangible computer readable storage medium having instructions for providing mode changes of a mobile communication device in a vehicle, the instructions performing acts comprising:
receiving an identification of a driver of the vehicle through the driver coming in physical contact with a driver identification module located within the vehicle;
receiving an identification of the mobile communication device in close proximity to the vehicle, wherein said receiving the identity of the mobile communication device in close proximity to the vehicle triggers the performance of the following steps:
determining at least one mobile telephone associated with the received identification of the driver of the vehicle;
comparing the received identification of the mobile communication device with the at least one mobile telephone associated with the received identification of the driver; and
when the received identification of the mobile communication device matches one of the at least one mobile telephone associated with the received identification of the driver, then sending a command to the mobile communication device to cause the mobile communication device to change a mode.
1. A system for mode changing of a mobile communication device in a vehicle, the system comprising:
a driver identification module located within the vehicle that obtains an identification of a driver of the vehicle through the driver coming in physical contact with the driver identification module;
a communication system that communicates with the mobile communication device when the mobile communication device comes into close proximity with the vehicle, wherein the communication system obtains an identification of the mobile communication device;
storage that maintains an association of driver identifiers to mobile telephone identifiers, wherein each driver identifier is associated with at least one mobile telephone identifier; and
a processor that receives the identification of the driver and the identification of the mobile communication device when the mobile communication device comes into close proximity with the communication system, wherein said receipt of the identification of the mobile communication device when the mobile communication device comes into close proximity with the communication system triggers the processor to: determine the at least one mobile telephone associated with the identification of the driver, compare the received identification of the mobile communication device with the at least one mobile telephone associated with the received identification of the driver, and when the received identification of the mobile communication device matches one of the at least one mobile telephone associated with the received identification of the driver then send a mode change command via the communication system to the mobile communication device to cause the mobile communication device to change a mode.
2. The system of
3. The system of
4. The system of
5. The system of
6. The system of
8. The tangible computer readable storage medium of
9. The tangible computer readable storage medium of
10. The tangible computer readable storage medium of
11. The tangible computer readable storage medium of
12. The tangible computer readable storage medium of
14. The method of
15. The method of
16. The method of
17. The method of
|
Embodiments are related to mobile communications devices. More particularly, embodiments are related to changing of modes of mobile communications devices and/or altering vehicle settings when the mobile communication device is in proximity of the vehicle.
Mobile communications devices such as mobile phones and mobile phone equipped data devices have become ubiquitous. For many, the mobile communications device is a vital tool for their daily lives. Mobile communications devices enable users to place and receive calls without restriction on the user's own mobility. However, users place and receive calls during situations where the call is a hindrance, particularly when driving a vehicle. When driving a vehicle, the user must manipulate the controls of the vehicle while also handling and manipulating the controls of the mobile communications device.
To address the problem of the user being required to simultaneously handle both the manual aspects of driving a vehicle and the manual aspects of using a mobile communications device to place and receive calls, hands-free functionality has been developed. The hands-free functionality allows the user to put the mobile communications device into a hands-free mode so that the user can place and receive calls without having to manually deal with the mobile communications device. The user is free to manipulate the controls of the vehicle without interference from the mobile communications device. The hands-free functionality may be exclusively included in the phone, such as speaker phone mode, may be a cradle based system that provides a physical connection of the mobile communications device to systems that allow for hands-free functions, or may be a wireless connection such as a BLUETOOTH® connection.
While the hands-free mode of operation is helpful to a driver of a vehicle, in most cases the driver must choose that the hands-free mode become active. While some users may devotedly make such a choice, others may not. Even when the hands-free mode is an option, some users may not use it when they driver either because they forget or because they simply disregard the feature. Thus, the safety and convenience benefits of hands-free mode are lost in those cases.
Furthermore, in some cases the hands-free mode may be configured between a hands-free system and multiple mobile communications devices present in a vehicle. The mobile communications device of the passenger may enter hands free mode while the mobile communications device of the driver remains in the normal, hands-required mode. Thus, the hands-free mode that is available in that situation is not being used to satisfy the ultimate need of allowing the driver to focus on driving the vehicle.
Additionally, vehicles have many features that may have various settings. For example, the position of the seat, the steering wheel, the pedals and so forth may be adjusted to suit the driver. For some vehicles, these settings may be set and later recalled so that the driver is not required to adjust the settings when another driver has previously used the vehicle. However, the driver must remember to activate the proper feature settings unless the vehicle has the ability to detect the driver by using a key fob or a biometric method.
Exemplary embodiments address these issues and others by providing mode changes of mobile communication devices based on identifying the driver and nearby mobile communication devices. Associations of drivers to mobile communication devices are maintained and when a driver and a matching mobile communication device are identified, a command is sent to the matching mobile communication device to force it to change a mode. For example, the mobile communication device may be forced to enter a hands-free mode so that the driver is able to benefit from the hands-free mode of the mobile communication device being used by the driver. Additionally or alternatively, the mobile communications device may provide data that either identifies the driver so that the preferred feature settings may be applied or provides an indication of the preferred features such as by providing a device identifier to which feature settings have been associated.
One embodiment is a system for changing of modes of mobile communication devices in a vehicle. The system includes a driver identification module that obtains an identification of a driver of the vehicle. The system further includes a communication system that communicates with the mobile communication device when the mobile communication device comes into close proximity with the communication system, wherein the communication system obtains an identification of the mobile communication device. The system includes storage that maintains an association of an identification of potential drivers to an identification of mobile telephones. Additionally, the system includes a processor that receives the identification of the driver and the identification of the mobile communication device. The processor determines from storage whether the identification of the mobile communication device is associated with the identification of the driver. When the identification of the mobile communication device is associated with the identification of the driver, then the processor sends a command via the communication system to the mobile communication device to force the mobile communication device to change a mode.
Another embodiment is a computer readable medium having instructions for providing change of modes of a mobile communication device in a vehicle. The instructions perform acts including receiving an identification of a driver of the vehicle, receiving an identification of the mobile communications device in close proximity to the vehicle, and determining whether a set of associations between identifications of potential drivers to mobile communications devices includes an association between the received identification of the driver and the received identification of the mobile communications device. When the received identification of the mobile communication device is associated with the received identification of the driver, then a command is sent to the mobile communication device to force the mobile communication device to change a mode.
Another embodiment is a method of forcing a mobile communications device to change modes. The method involves detecting an identity of a driver of a vehicle, detecting an identity of a mobile communication device in close proximity to the vehicle, and determining whether the identity of the driver is associated with the identity of the mobile communication device. When the identity of the driver is associated with the identity of the mobile communication device, then a command is sent to the mobile communication device to force the mobile communication device to change a mode.
Exemplary embodiments activate various modes of a mobile communications device that is associated with the driver of the vehicle by identifying both the current driver and those mobile communications devices that are in proximity. A command to activate a particular mode is sent to the mobile communications device of the driver. Accordingly, it is the driver that benefits from a particular mode, such as hands-free mode, without further intervention by the driver or other passenger of the vehicle.
These systems use a driver identification sensor such as a biometric sensor 110. Examples of a biometric sensor include sensor for a fingerprint 118 or retinal scanner, a weight or height measurement for the individual in the driver's seat, and the like. The biometrics of one driver differ from those of the next so that the identity of the current driver can be determined. The sensor is positioned so as to capture the biometric information of the driver as opposed to other occupants. In this example, once the sensor has determined the biometric information of the driver, the sensor 110 then provides data representing the identity of the driver to a controller 102. It will be appreciated that the sensor module 110 and controller 102 may be integrated rather than being separate components as shown.
Another example of a driver identification sensor is a key recognition module 112, such as in the ignition switch, which receives a key 120 that is inserted by the driver to open the door or to start the vehicle 100. In this scenario, keys 120 are distinguishable and one key is assigned to one driver while another key is assigned to a different driver. Thus, the module 112 recognizes which key is inserted and thereby recognizes the identity of the driver. The module may then provide data representing the identity of the driver to the controller 102. As noted above, the recognition module 112 may be integrated with the controller 120 rather than being a separate component as shown.
Another example of a driver identification sensor is a switch 114. This switch 114 may be a touch-button panel that allows the driver to touch the button assigned to that driver. Thus, when the current driver touches the button in order to configure the features of the vehicle, such as seat position, steering wheel tilt, etc., the switch 114 is made aware of the identity of the driver. The switch 114 may then provide data representing the identity of the driver to the controller 102.
The controller 102 may also maintain communication with a mobile communication device brought in proximity of the controller 102. For example, the mobile communication device 104 may broadcast its identity, or may be receptive to queries for its identity, via wireless radio frequency communication. Examples of such wireless radio frequency communication include BLUETOOTH® communication, Wi-Fi communication, and the like. Alternatively, the wireless phone may be physically connected to the controller such as via a cradle. For example, see the various manners of communicatively coupling the mobile communications device to the controller as discussed in commonly assigned U.S. Pat. No. 6,690,956 and U.S. patent application Ser. No. 10/725,579, both of which are incorporated herein by reference.
The controller 102 obtains the identity of the mobile communications device 104, such as the electronic serial number, mobile identification number, and the like, via the communication with the mobile communications device 104. The controller 102 may then exercise logic to determine whether to send a mode changing command to a particular mobile communications device 104 that happens to be in proximity based on whether or not that mobile communications device 104 is associated with the current driver that has been identified.
Upon activation of a particular mode as a result of the mobile communications device 104 receiving and acting upon the command, additional features may become active, such as an external microphone 106 and speaker 108 that provides better hands-free performance than the microphone and speaker of the mobile communications device 104. When calls are placed to or received from a mobile communications system 116 via the mobile communications device 104 that has changed to a more suitable mode such as a hands-free mode, the driver is then relieved of having to manipulate and otherwise handle the mobile communications device 104 thereby allowing the driver to focus on controlling the vehicle 100.
The processor 202 and the memory 204 are example of computer readable media which store instructions that when performed implement various logical operations. Such computer readable media may include various storage media including electronic, magnetic, and optical storage. Computer readable media may also include communications media, such as wired and wireless connections used to transfer the instructions or send and receive other data messages.
The processor 202 obtains the identity of the current driver by receiving data from a driver ID sensor, such as the module 110, 112, and 114 discussed above in relation to
The processor 202 obtains the identity of the mobile communications devices that are in proximity to it by using a communications connection 206. This communications connection 206 may be of various forms. For example, this connection may be a physical cradle within which mobile communications devices are placed inside the vehicle, such as to charge the batteries of the mobile communications device or to otherwise secure the mobile communications device within the vehicle 100. Alternatively, the communications connection 206 may be a limited range wireless communication system, such as a Bluetooth® or Wi-Fi system that has the ability to detect the presence of a mobile communications device, either by listening for mobile communications devices to broadcast their presence and/or identity or by polling for mobile communications devices by sending a query during a polling period or at a specified time such as a few seconds after a door of the vehicle 100 is closed.
The communications connection 206 may send and receive information necessary to implement the mode changing command and subsequent mode of operation. The identity of the mobile communications device 104 may be received and provided to the processor 202, such as an electronic serial number of mobile identification number. The processor 202, upon finding that a particular mobile communication device is associated with the current driver, then sends the mode changing command back to the mobile communications device via the communications connection 206. For example, the processor 202 may generate a Bluetooth® hands-free command based on a profile stored for each of the mobile communications devices 104 that are associated to a driver via the table 204.
Upon the mobile communications device 104 receiving and acknowledging the mode changing command, then the communications connection 206 may be used to carry the bi-directional audio data of a telephone call where the mobile communications device relies on the audio input/output 208 of the controller 102 upon entering a hands-free mode. In that case, the audio input/output 208 captures audio, via microphone 106, that is sent by the mobile communications device 104 and produces audio, via speaker 108, that has been received by the mobile communications device 104. If the mobile communications device 104 has its own hands-free audio abilities, then those may be used instead such that the audio capabilities of the controller 102 are not used or are omitted from the controller 102 altogether. Furthermore, the communications connection may also be used to carry more advanced data such as commands spoken by the driver when in a voice-only or similar mode, commands entered in a built-in screen of the vehicle or the controller 102 when in a video or control re-direct mode, and so forth in order to provide control of the mobile communications device 104 if such advanced features are not already being provided by a feature of the mobile communications device 104.
Once both a driver ID and at least one mobile device ID are received, the processor 202 performs a look-up of one of the IDs to see if it matches the other at look-up operation 406. Once the set of device IDs associated to the driver ID for the current driver have been found, then query operation 408 detects whether there is a match. If not, then operational flow returns to driver ID and phone ID operations 402, 404 to continue monitoring for a different driver ID and/or different phone ID.
The operational flow continues to poll for different driver IDs and/or different phone IDs in this exemplary embodiment in order to account for a change in drivers and to account for communication devices being introduced after the initial polling. For example, the driver may change without the ignition switch of the vehicle 100 ever being turned off so continuing to poll or otherwise listen for a driver ID permits detection of the new driver. Likewise, a communication device 104 may be introduced into the vehicle at some time after the initial polling period, such as by physically bringing the device 104 into the vehicle 100 or powering on the device 104 at some later time. Therefore, continuing to poll or otherwise listen for a new device ID permits detection of the new communication device.
For instances where query operation 408 detects a match between the driver ID and a device ID, the processor 202 transmits a changed mode command to the mobile communication device at command operation 410. Here, the mobile communications device 104 receives and acknowledges the command and enters the new mode. Where the mobile communications device 104 receives a request to enter a mode where the mobile communications device 104 relies upon audio input/output abilities and/or the user input abilities of the controller 102, then the new mode results in communications begin being exchanged between the mobile communications device 104 and the controller 102 to place and receive calls. As indicated above, according to an exemplary embodiment, operational flow returns to driver and phone operations 402, 404 to continue determining who the current driver is and which communications devices are in proximity.
An exemplary embodiment shown in
Another exemplary embodiment is shown in
Another exemplary embodiment is shown in
At query operation 440, the processor 202 detects whether an override-to-alternate selection has been made by the user. For example, an override option may be provided on the mobile communications device 104 itself or on the vehicle 100 such as within the system 102 to allow an alternate hands-free mode to be entered where the hands-free components of the vehicle are not chosen. If no override option has been received thus far, the processor 202 maintains the status quo. If the override option has been received, then a release from the changed mode occurs at release operation 442. In one or more embodiments the processor 202 may generate a command to release the mobile communications device 104 from the changed mode so that it may return to the previous mode or enter whatever mode the driver chooses. According to one or more embodiments, if the override is entered directly on the device 104, then the device 104 may directly respond without intervention by the processor 202 by exiting the changed mode of operation. At this point, the processor 202 may begin monitoring for alternative hands-free operation of the mobile communications device 104 of the driver at monitor operation 444. Query operation 446 then detects whether such alternate hands-free operation is occurring and if so, then continues to monitor the device 104. If query operation 446 detects that the device 104 is not engaged in an alternative hands-free mode of operation, then the processor 202 again transmits the hands-free command to the device 104 to begin hands-free communication with it.
Returning to
In another exemplary embodiment as shown in
In another exemplary embodiment as shown in
As a first example, query operation 470 may detect whether a profile that is associated with either the driver ID, phone ID, or both includes a hands-free mode entry. If not, then no hands-free command is transmitted and the system waits on another phone ID/driver ID match to occur. If there is a hands-free mode entry for the profile, then a command is transmitted at command operation 472 to instruct the device 104 to enter a hands-free mode, such as one that implicates hands-free components of the vehicle 100 or one that implicates hands-free features of the device itself or other peripherals.
As another example that may be separate from or performed in conjunction with the preceding example, query operation 474 detects whether the profile includes a text-to-speech (TTS) mode entry. If not, then no TTS command is transmitted and the system waits on another phone ID/driver ID match to occur. If there is a TTS mode entry for the profile, then a command is transmitted at command operation 476 to instruct the device 104 to enter a TTS mode. The TTS mode may allow the device 104 to output as audio any text that it receives so that text messages, emails, and the like are provided audibly for the driver rather than requiring the driver to look at a display.
As another example that may be separate from or performed in conjunction with the preceding examples, query operation 478 detects whether the profile includes a voice input mode entry. If not, then no voice input command is transmitted and the system waits on another phone ID/driver ID match to occur. If there is a voice input mode entry for the profile, then a command is transmitted at command operation 480 to instruct the device 104 to enter a voice input mode The voice input mode may allow the device 104 to receive verbal commands from the driver rather than requiring the driver to manually press keys on the device 104.
As another example that may be separate from or performed in conjunction with the preceding examples, query operation 482 detects whether the profile includes a video redirection mode entry. If not, then no video redirection command is transmitted and the system waits on another phone ID/driver ID match to occur. If there is a video redirection mode entry for the profile, then a command is transmitted at command operation 484 to instruct the device 104 to enter a video redirection mode. The video redirection mode may allow the device 104 to output to an external display system such as a display of the vehicle 100 the data representative of any display the device 104 is producing. Thus, the driver may view the screen of the vehicle 100 which may be in a more suitable location, such as on a dashboard or heads-up display so that driver does not need to look at the device 104 which may be in a less suitable location.
As another example that may be separate from or performed in conjunction with the preceding examples, query operation 486 detects whether the profile includes a control redirection mode entry. If not, then no control redirection command is transmitted and the system waits on another phone ID/driver ID match to occur. If there is a control redirection mode entry for the profile, then a command is transmitted at command operation 488 to instruct the device 104 to enter a control redirection mode. The control redirection mode may allow the device 104 to receive control signals generated by external systems, such as a virtual keypad on a dashboard display to that the driver is not required to manually press keys on the device 104.
As another example that may be separate from or performed in conjunction with the preceding examples, query operation 490 detects whether the profile includes a camera redirection mode entry. If not, then no camera redirection command is transmitted and the system waits on another phone ID/driver ID match to occur. If there is a camera redirection mode entry for the profile, then a command is transmitted at command operation 492 to instruct the device 104 to enter a camera redirection mode. The camera redirection mode may allow the device 104 to redirect its camera output to an external system such as a video display system of the vehicle 100 such as in a car visor or dashboard display. In this manner, the device 104 may be placed in many locations and provide visual feedback to the driver, such as placing the device 104 with the camera portion aimed rearward to provide a video display of the area behind the vehicle.
Thus, exemplary embodiments disclosed herein provide for forcing mobile communications devices to change mode if the current driver of the vehicle 100 is expected to be using the detected mobile communications device 104. Drivers need not manually change the mode of the communications device 104 that they are carrying with them into the vehicle 100 such that forgetfulness or disinterest of the driver does not prevent the use of the appropriate mode by the driver.
As one example of a mode change requested of systems of the vehicle 100 that may be separate from or performed in conjunction with the preceding examples, query operation 494 detects whether the profile includes a radio muting mode entry. If not, then no radio muting command is transmitted during calls and the system waits on another phone ID/driver ID match to occur. If there is a radio muting mode entry for the profile, then a command is transmitted at command operation 496 to instruct the radio of vehicle 100 to enter a muted mode while calls are being conducted using the device 104. Muting the radio provides the advantage of less ambient sound being collected during conversation, whether hands-free or otherwise. The command may be transmitted by the system 102 of the vehicle 100 upon the system detecting an incoming or outgoing call involving device 104 by maintaining status communications with the device 104. Alternatively, the radio muting mode may result in the device 104 generating a radio muting signal during calls where that signal is received and acted upon by the system 102 to trigger the radio muting.
As another example that involves responsiveness of systems of the vehicle 100 that may be separate from or performed in conjunction with the preceding examples, query operation 498 detects whether the profile includes an auto-drive mode entry. If not, then no auto-drive command is transmitted during calls and the system waits on another phone ID/driver ID match to occur. If there is an auto-drive mode entry for the profile, then a command is transmitted at command operation 500 to instruct the auto-drive system of vehicle 100 to enter an active mode while calls are being conducted using the device 104. Such auto-drive functions may include cruise control, automatic vehicle-to-vehicle spacing, automatic headlight activation, automatic wiper activation, and the like.
A system such as the example shown in
Furthermore, in the various embodiments above where the mobile communications device 104 and/or the systems of the vehicle 100 are able to change modes, the driver ID may be omitted altogether whereby the device ID is directly associated with mode changes and vehicle configurations. For example, upon the system 102 detecting that a device 104 having a particular device ID is present, the system 102 may look-up the device ID to directly determine what mode to request and/or what vehicle configurations to establish.
At monitor operation 602, the processor 202 monitors for the presence and ID of a mobile device 104. Once the mobile device 104 comes in proximity to the vehicle 100, the processor 202 looks-up the ID received form the mobile device 104 at look-up operation 604 to find the associated modes and/or vehicle configurations. Then, the processor 202 may request that the device 104 change its mode as specified in the table 700 of
Additionally, in some embodiments the mobile communication device 104 may have the capability to provide data to the system 102 rather than having the system 102 perform a look-up in a table. Thus, the mobile communication device 104 may be able to provide the user ID such that the processor 202 may utilize this user ID as the driver ID as in look-up operation 504. Thus, configuration operation 506 may be performed on the basis of the user ID provided from the device 104 rather than requiring the look-up in a table. Likewise, the mobile communication device 104 may be able to provide mode and vehicle settings data to the system 102 such that the processor 202 may utilize this mode and settings data as otherwise being looked-up in look-up operation 604. Thus, configuration operation 606 may be performed on the basis of the mode and/or vehicle settings data provided from the device 104 rather than requiring the look-up table.
While various embodiments have been particularly shown and described, it will be understood by those skilled in the art that various other changes in the form and details may be made therein without departing from the spirit and scope of the invention.
Patent | Priority | Assignee | Title |
10025684, | Sep 24 2014 | Microsoft Technology Licensing, LLC | Lending target device resources to host device computing environment |
10043516, | Sep 23 2016 | Apple Inc | Intelligent automated assistant |
10049675, | Feb 25 2010 | Apple Inc. | User profiling for voice input processing |
10079014, | Jun 08 2012 | Apple Inc. | Name recognition system |
10083690, | May 30 2014 | Apple Inc. | Better resolution when referencing to concepts |
10108612, | Jul 31 2008 | Apple Inc. | Mobile device having human language translation capability with positional feedback |
10140110, | Apr 02 2014 | Ford Global Technologies, LLC | Multiple chunk software updates |
10178220, | Oct 06 2006 | LYFT, INC | Mode changing of a mobile communication device and vehicle settings when the mobile communications device is in proximity to a vehicle |
10187505, | Dec 22 2017 | DISH NETWORK, L L C | Voice-activated call pick-up for mobile device |
10237314, | Sep 24 2014 | Microsoft Technology Licensing, LLC | Presentation of computing environment on multiple devices |
10277649, | Sep 24 2014 | Microsoft Technology Licensing, LLC | Presentation of computing environment on multiple devices |
10303715, | May 16 2017 | Apple Inc | Intelligent automated assistant for media exploration |
10311144, | May 16 2017 | Apple Inc | Emoji word sense disambiguation |
10311871, | Mar 08 2015 | Apple Inc. | Competing devices responding to voice triggers |
10332518, | May 09 2017 | Apple Inc | User interface for correcting recognition errors |
10354652, | Dec 02 2015 | Apple Inc. | Applying neural network language models to weighted finite state transducers for automatic speech recognition |
10356243, | Jun 05 2015 | Apple Inc. | Virtual assistant aided communication with 3rd party service in a communication session |
10381016, | Jan 03 2008 | Apple Inc. | Methods and apparatus for altering audio output signals |
10390213, | Sep 30 2014 | Apple Inc. | Social reminders |
10395654, | May 11 2017 | Apple Inc | Text normalization based on a data-driven learning network |
10403278, | May 16 2017 | Apple Inc | Methods and systems for phonetic matching in digital assistant services |
10403283, | Jun 01 2018 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
10410637, | May 12 2017 | Apple Inc | User-specific acoustic models |
10417266, | May 09 2017 | Apple Inc | Context-aware ranking of intelligent response suggestions |
10417344, | May 30 2014 | Apple Inc. | Exemplar-based natural language processing |
10417405, | Mar 21 2011 | Apple Inc. | Device access using voice authentication |
10431204, | Sep 11 2014 | Apple Inc. | Method and apparatus for discovering trending terms in speech requests |
10438595, | Sep 30 2014 | Apple Inc. | Speaker identification and unsupervised speaker adaptation techniques |
10445429, | Sep 21 2017 | Apple Inc. | Natural language understanding using vocabularies with compressed serialized tries |
10448111, | Sep 24 2014 | Microsoft Technology Licensing, LLC | Content projection |
10453443, | Sep 30 2014 | Apple Inc. | Providing an indication of the suitability of speech recognition |
10474753, | Sep 07 2016 | Apple Inc | Language identification using recurrent neural networks |
10482874, | May 15 2017 | Apple Inc | Hierarchical belief states for digital assistants |
10496705, | Jun 03 2018 | Apple Inc | Accelerated task performance |
10496753, | Jan 18 2010 | Apple Inc.; Apple Inc | Automatically adapting user interfaces for hands-free interaction |
10497365, | May 30 2014 | Apple Inc. | Multi-command single utterance input method |
10504518, | Jun 03 2018 | Apple Inc | Accelerated task performance |
10529332, | Mar 08 2015 | Apple Inc. | Virtual assistant activation |
10553209, | Jan 18 2010 | Apple Inc. | Systems and methods for hands-free notification summaries |
10553215, | Sep 23 2016 | Apple Inc. | Intelligent automated assistant |
10567477, | Mar 08 2015 | Apple Inc | Virtual assistant continuity |
10580409, | Jun 11 2016 | Apple Inc. | Application integration with a digital assistant |
10592604, | Mar 12 2018 | Apple Inc | Inverse text normalization for automatic speech recognition |
10593346, | Dec 22 2016 | Apple Inc | Rank-reduced token representation for automatic speech recognition |
10635296, | Sep 24 2014 | Microsoft Technology Licensing, LLC | Partitioned application presentation across devices |
10636424, | Nov 30 2017 | Apple Inc | Multi-turn canned dialog |
10643611, | Oct 02 2008 | Apple Inc. | Electronic devices with voice command and contextual data processing capabilities |
10657328, | Jun 02 2017 | Apple Inc | Multi-task recurrent neural network architecture for efficient morphology handling in neural language modeling |
10657961, | Jun 08 2013 | Apple Inc. | Interpreting and acting upon commands that involve sharing information with remote devices |
10657966, | May 30 2014 | Apple Inc. | Better resolution when referencing to concepts |
10679605, | Jan 18 2010 | Apple Inc | Hands-free list-reading by intelligent automated assistant |
10681212, | Jun 05 2015 | Apple Inc. | Virtual assistant aided communication with 3rd party service in a communication session |
10684703, | Jun 01 2018 | Apple Inc | Attention aware virtual assistant dismissal |
10686925, | Dec 22 2017 | DISH Network L.L.C. | Voice-activated call pick-up for mobile device |
10692504, | Feb 25 2010 | Apple Inc. | User profiling for voice input processing |
10699717, | May 30 2014 | Apple Inc. | Intelligent assistant for home automation |
10705794, | Jan 18 2010 | Apple Inc | Automatically adapting user interfaces for hands-free interaction |
10714095, | May 30 2014 | Apple Inc. | Intelligent assistant for home automation |
10714117, | Feb 07 2013 | Apple Inc. | Voice trigger for a digital assistant |
10720160, | Jun 01 2018 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
10726832, | May 11 2017 | Apple Inc | Maintaining privacy of personal information |
10733375, | Jan 31 2018 | Apple Inc | Knowledge-based framework for improving natural language understanding |
10733982, | Jan 08 2018 | Apple Inc | Multi-directional dialog |
10733993, | Jun 10 2016 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
10741181, | May 09 2017 | Apple Inc. | User interface for correcting recognition errors |
10741185, | Jan 18 2010 | Apple Inc. | Intelligent automated assistant |
10748546, | May 16 2017 | Apple Inc. | Digital assistant services based on device capabilities |
10755051, | Sep 29 2017 | Apple Inc | Rule-based natural language processing |
10755703, | May 11 2017 | Apple Inc | Offline personal assistant |
10769385, | Jun 09 2013 | Apple Inc. | System and method for inferring user intent from speech inputs |
10789945, | May 12 2017 | Apple Inc | Low-latency intelligent automated assistant |
10789959, | Mar 02 2018 | Apple Inc | Training speaker recognition models for digital assistants |
10791176, | May 12 2017 | Apple Inc | Synchronization and task delegation of a digital assistant |
10810274, | May 15 2017 | Apple Inc | Optimizing dialogue policy decisions for digital assistants using implicit feedback |
10818288, | Mar 26 2018 | Apple Inc | Natural assistant interaction |
10824531, | Sep 24 2014 | Microsoft Technology Licensing, LLC | Lending target device resources to host device computing environment |
10839159, | Sep 28 2018 | Apple Inc | Named entity normalization in a spoken dialog system |
10846948, | Jul 26 2012 | LEXISNEXIS RISK SOLUTIONS UK LIMITED | Driving behavior monitoring system |
10847142, | May 11 2017 | Apple Inc. | Maintaining privacy of personal information |
10878809, | May 30 2014 | Apple Inc. | Multi-command single utterance input method |
10892996, | Jun 01 2018 | Apple Inc | Variable latency device coordination |
10904611, | Jun 30 2014 | Apple Inc. | Intelligent automated assistant for TV user interactions |
10909171, | May 16 2017 | Apple Inc. | Intelligent automated assistant for media exploration |
10909331, | Mar 30 2018 | Apple Inc | Implicit identification of translation payload with neural machine translation |
10928918, | May 07 2018 | Apple Inc | Raise to speak |
10930282, | Mar 08 2015 | Apple Inc. | Competing devices responding to voice triggers |
10942702, | Jun 11 2016 | Apple Inc. | Intelligent device arbitration and control |
10942703, | Dec 23 2015 | Apple Inc. | Proactive assistance based on dialog communication between devices |
10944859, | Jun 03 2018 | Apple Inc | Accelerated task performance |
10956666, | Nov 09 2015 | Apple Inc | Unconventional virtual assistant interactions |
10978090, | Feb 07 2013 | Apple Inc. | Voice trigger for a digital assistant |
10984780, | May 21 2018 | Apple Inc | Global semantic word embeddings using bi-directional recurrent neural networks |
10984798, | Jun 01 2018 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
11009970, | Jun 01 2018 | Apple Inc. | Attention aware virtual assistant dismissal |
11010127, | Jun 29 2015 | Apple Inc. | Virtual assistant for media playback |
11010561, | Sep 27 2018 | Apple Inc | Sentiment prediction from textual data |
11023513, | Dec 20 2007 | Apple Inc. | Method and apparatus for searching using an active ontology |
11025565, | Jun 07 2015 | Apple Inc | Personalized prediction of responses for instant messaging |
11037565, | Jun 10 2016 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
11048473, | Jun 09 2013 | Apple Inc. | Device, method, and graphical user interface for enabling conversation persistence across two or more instances of a digital assistant |
11069336, | Mar 02 2012 | Apple Inc. | Systems and methods for name pronunciation |
11069347, | Jun 08 2016 | Apple Inc. | Intelligent automated assistant for media exploration |
11070949, | May 27 2015 | Apple Inc. | Systems and methods for proactively identifying and surfacing relevant content on an electronic device with a touch-sensitive display |
11080012, | Jun 05 2009 | Apple Inc. | Interface for a virtual digital assistant |
11087759, | Mar 08 2015 | Apple Inc. | Virtual assistant activation |
11089145, | Dec 22 2017 | DISH Network L.L.C. | Voice-activated call pick-up for mobile device |
11120372, | Jun 03 2011 | Apple Inc. | Performing actions associated with task items that represent tasks to perform |
11126400, | Sep 08 2015 | Apple Inc. | Zero latency digital assistant |
11127397, | May 27 2015 | Apple Inc. | Device voice control |
11133008, | May 30 2014 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
11140099, | May 21 2019 | Apple Inc | Providing message response suggestions |
11145294, | May 07 2018 | Apple Inc | Intelligent automated assistant for delivering content from user experiences |
11152002, | Jun 11 2016 | Apple Inc. | Application integration with a digital assistant |
11169616, | May 07 2018 | Apple Inc. | Raise to speak |
11170166, | Sep 28 2018 | Apple Inc. | Neural typographical error modeling via generative adversarial networks |
11204787, | Jan 09 2017 | Apple Inc | Application integration with a digital assistant |
11217251, | May 06 2019 | Apple Inc | Spoken notifications |
11217255, | May 16 2017 | Apple Inc | Far-field extension for digital assistant services |
11227589, | Jun 06 2016 | Apple Inc. | Intelligent list reading |
11231904, | Mar 06 2015 | Apple Inc. | Reducing response latency of intelligent automated assistants |
11237797, | May 31 2019 | Apple Inc. | User activity shortcut suggestions |
11257504, | May 30 2014 | Apple Inc. | Intelligent assistant for home automation |
11269678, | May 15 2012 | Apple Inc. | Systems and methods for integrating third party services with a digital assistant |
11281993, | Dec 05 2016 | Apple Inc | Model and ensemble compression for metric learning |
11289073, | May 31 2019 | Apple Inc | Device text to speech |
11301477, | May 12 2017 | Apple Inc | Feedback analysis of a digital assistant |
11307752, | May 06 2019 | Apple Inc | User configurable task triggers |
11314370, | Dec 06 2013 | Apple Inc. | Method for extracting salient dialog usage from live data |
11321116, | May 15 2012 | Apple Inc. | Systems and methods for integrating third party services with a digital assistant |
11348573, | Mar 18 2019 | Apple Inc | Multimodality in digital assistant systems |
11348582, | Oct 02 2008 | Apple Inc. | Electronic devices with voice command and contextual data processing capabilities |
11350253, | Jun 03 2011 | Apple Inc. | Active transport based notifications |
11360577, | Jun 01 2018 | Apple Inc. | Attention aware virtual assistant dismissal |
11360641, | Jun 01 2019 | Apple Inc | Increasing the relevance of new available information |
11360739, | May 31 2019 | Apple Inc | User activity shortcut suggestions |
11380310, | May 12 2017 | Apple Inc. | Low-latency intelligent automated assistant |
11386266, | Jun 01 2018 | Apple Inc | Text correction |
11388291, | Mar 14 2013 | Apple Inc. | System and method for processing voicemail |
11405466, | May 12 2017 | Apple Inc. | Synchronization and task delegation of a digital assistant |
11412082, | Oct 06 2006 | LYFT, INC. | Mode changing of a mobile communication device and vehicle settings when the mobile communications device is in proximity to a vehicle |
11423886, | Jan 18 2010 | Apple Inc. | Task flow identification based on user intent |
11423908, | May 06 2019 | Apple Inc | Interpreting spoken requests |
11431642, | Jun 01 2018 | Apple Inc. | Variable latency device coordination |
11462215, | Sep 28 2018 | Apple Inc | Multi-modal inputs for voice commands |
11468282, | May 15 2015 | Apple Inc. | Virtual assistant in a communication session |
11475884, | May 06 2019 | Apple Inc | Reducing digital assistant latency when a language is incorrectly determined |
11475898, | Oct 26 2018 | Apple Inc | Low-latency multi-speaker speech recognition |
11487364, | May 07 2018 | Apple Inc. | Raise to speak |
11488406, | Sep 25 2019 | Apple Inc | Text detection using global geometry estimators |
11495218, | Jun 01 2018 | Apple Inc | Virtual assistant operation in multi-device environments |
11496600, | May 31 2019 | Apple Inc | Remote execution of machine-learned models |
11500672, | Sep 08 2015 | Apple Inc. | Distributed personal assistant |
11516537, | Jun 30 2014 | Apple Inc. | Intelligent automated assistant for TV user interactions |
11526368, | Nov 06 2015 | Apple Inc. | Intelligent automated assistant in a messaging environment |
11532306, | May 16 2017 | Apple Inc. | Detecting a trigger of a digital assistant |
11550542, | Sep 08 2015 | Apple Inc. | Zero latency digital assistant |
11570293, | Dec 22 2017 | DISH Network L.L.C. | Voice-activated call pick-up for mobile device |
11580990, | May 12 2017 | Apple Inc. | User-specific acoustic models |
11599331, | May 11 2017 | Apple Inc. | Maintaining privacy of personal information |
11636869, | Feb 07 2013 | Apple Inc. | Voice trigger for a digital assistant |
11638059, | Jan 04 2019 | Apple Inc | Content playback on multiple devices |
11656884, | Jan 09 2017 | Apple Inc. | Application integration with a digital assistant |
11657813, | May 31 2019 | Apple Inc | Voice identification in digital assistant systems |
11657820, | Jun 10 2016 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
11670289, | May 30 2014 | Apple Inc. | Multi-command single utterance input method |
11671920, | Apr 03 2007 | Apple Inc. | Method and system for operating a multifunction portable electronic device using voice-activation |
11675829, | May 16 2017 | Apple Inc. | Intelligent automated assistant for media exploration |
11699448, | May 30 2014 | Apple Inc. | Intelligent assistant for home automation |
11705130, | May 06 2019 | Apple Inc. | Spoken notifications |
11710482, | Mar 26 2018 | Apple Inc. | Natural assistant interaction |
11727219, | Jun 09 2013 | Apple Inc. | System and method for inferring user intent from speech inputs |
11749275, | Jun 11 2016 | Apple Inc. | Application integration with a digital assistant |
11765209, | May 11 2020 | Apple Inc. | Digital assistant hardware abstraction |
11798547, | Mar 15 2013 | Apple Inc. | Voice activated device for use with a voice-based digital assistant |
11809483, | Sep 08 2015 | Apple Inc. | Intelligent automated assistant for media search and playback |
11809783, | Jun 11 2016 | Apple Inc. | Intelligent device arbitration and control |
11810562, | May 30 2014 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
11842734, | Mar 08 2015 | Apple Inc. | Virtual assistant activation |
11853536, | Sep 08 2015 | Apple Inc. | Intelligent automated assistant in a media environment |
11853647, | Dec 23 2015 | Apple Inc. | Proactive assistance based on dialog communication between devices |
11854539, | May 07 2018 | Apple Inc. | Intelligent automated assistant for delivering content from user experiences |
11886805, | Nov 09 2015 | Apple Inc. | Unconventional virtual assistant interactions |
11888791, | May 21 2019 | Apple Inc. | Providing message response suggestions |
11900923, | May 07 2018 | Apple Inc. | Intelligent automated assistant for delivering content from user experiences |
11909905, | Dec 22 2017 | DISH Network L.L.C. | Voice-activated call pick-up for mobile device |
11924254, | May 11 2020 | Apple Inc. | Digital assistant hardware abstraction |
11928604, | Sep 08 2005 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
11947873, | Jun 29 2015 | Apple Inc. | Virtual assistant for media playback |
12069199, | Oct 06 2006 | LYFT, INC. | Mode changing of a mobile communication device and vehicle settings when the mobile communications device is in proximity to a vehicle |
12073147, | Jun 09 2013 | Apple Inc. | Device, method, and graphical user interface for enabling conversation persistence across two or more instances of a digital assistant |
12080287, | Jun 01 2018 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
12087308, | Jan 18 2010 | Apple Inc. | Intelligent automated assistant |
8442758, | Feb 27 2012 | Toyota Motor Corporation | Systems and methods for a vehicle smart calendar |
8532921, | Feb 27 2012 | Toyota Motor Corporation | Systems and methods for determining available providers |
8594705, | Dec 04 2009 | System for preventing text messaging while driving | |
8594861, | Feb 27 2012 | Toyota Jidosha Kabushiki Kaisha | Systems and methods for communicating with a vehicle user |
9082237, | Jun 11 2002 | Intelligent Technologies International, Inc.; Intelligent Technologies International, Inc | Vehicle access and security based on biometrics |
9174552, | Mar 02 2007 | Denso Corporation; Nippon Soken, Inc. | Driving-environment setup system, in-vehicle device and program thereof, portable device and program thereof, management device and program thereof |
9219811, | Oct 06 2006 | LYFT, INC | Mode changing of a mobile communications device and vehicle settings when the mobile communications device is in proximity to a vehicle |
9323546, | Mar 31 2014 | Ford Global Technologies, LLC | Targeted vehicle remote feature updates |
9325650, | Apr 02 2014 | Ford Global Technologies, LLC | Vehicle telematics data exchange |
9360854, | Aug 07 2012 | Verizon Patent and Licensing Inc.; Verizon Patent and Licensing Inc | Preventing distracted driving |
9524156, | Jan 09 2014 | Ford Global Technologies, LLC | Flexible feature deployment strategy |
9609621, | Dec 04 2009 | Tracking warning, and blocking unsafe texting in moving vehicles including telematics systems | |
9661125, | Oct 06 2006 | LYFT, INC | Mode changing of a mobile communication device and vehicle settings when the mobile communications device is in proximity to a vehicle |
9663112, | Oct 09 2014 | Ford Global Technologies, LLC | Adaptive driver identification fusion |
9678640, | Sep 24 2014 | Microsoft Technology Licensing, LLC | View management architecture |
9698916, | Dec 08 2010 | Microsoft Technology Licensing, LLC | Controlling audio signals |
9716762, | Mar 31 2014 | Ford Global Technologies LLC | Remote vehicle connection status |
9766874, | Jan 09 2014 | Ford Global Technologies, LLC | Autonomous global software update |
9769227, | Sep 24 2014 | Microsoft Technology Licensing, LLC | Presentation of computing environment on multiple devices |
9860306, | Sep 24 2014 | Microsoft Technology Licensing, LLC | Component-specific application presentation histories |
9865248, | Apr 05 2008 | Apple Inc. | Intelligent text-to-speech conversion |
9966060, | Jun 07 2013 | Apple Inc. | System and method for user-specified pronunciation of words for speech synthesis and recognition |
9986419, | Sep 30 2014 | Apple Inc. | Social reminders |
ER8782, |
Patent | Priority | Assignee | Title |
20020197976, | |||
20030032460, | |||
20060052141, | |||
20060262103, | |||
20070042812, | |||
20070082706, | |||
20070120948, | |||
20070238491, | |||
20080252412, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Sep 27 2006 | ZELLNER, SAMUEL | Bellsouth Intellectual Property Corporation | CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNOR INVENTOR PREVIOUSLY RECORDED AT REEL: 018363 FRAME: 0222 ASSIGNOR S HEREBY CONFIRMS THE ASSIGNMENT | 047248 | /0019 | |
Sep 27 2006 | ZELLNER, SAMUEL, MR | Bellsouth Intellectual Property Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 018363 | /0222 | |
Oct 06 2006 | AT&T Intellectual Property I, L.P. | (assignment on the face of the patent) | / | |||
Apr 27 2007 | BELLSOUTH INTELLECTUAL PROPERTY, INC | AT&T Delaware Intellectual Property, Inc | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 023288 | /0674 | |
Apr 27 2007 | Bellsouth Intellectual Property Corporation | AT&T INTELLECTUAL PROPERTY, INC | CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE NAME PREVIOUSLY RECORDED ON REEL 023288 FRAME 0674 ASSIGNOR S HEREBY CONFIRMS THE CHANGE OF NAME | 046377 | /0092 | |
Jul 27 2007 | AT&T INTELLECTUAL PROPERTY, INC | AT&T BLS Intellectual Property, Inc | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 046377 | /0525 | |
Nov 01 2007 | AT&T BLS Intellectual Property, Inc | AT&T Delaware Intellectual Property, Inc | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 046377 | /0665 | |
Sep 18 2009 | AT&T Delaware Intellectual Property, Inc | AT&T Intellectual Property I, L P | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 023288 | /0726 | |
Jun 28 2018 | AT&T Intellectual Property I, L P | Prosper Technology, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 046556 | /0096 | |
Jan 18 2019 | Prosper Technology, LLC | LYFT, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 048097 | /0353 | |
Nov 03 2022 | LYFT, INC | JPMORGAN CHASE BANK, N A , AS ADMINISTRATIVE AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 061880 | /0237 |
Date | Maintenance Fee Events |
May 12 2011 | ASPN: Payor Number Assigned. |
Oct 28 2014 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Oct 25 2018 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Oct 25 2022 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
Date | Maintenance Schedule |
May 03 2014 | 4 years fee payment window open |
Nov 03 2014 | 6 months grace period start (w surcharge) |
May 03 2015 | patent expiry (for year 4) |
May 03 2017 | 2 years to revive unintentionally abandoned end. (for year 4) |
May 03 2018 | 8 years fee payment window open |
Nov 03 2018 | 6 months grace period start (w surcharge) |
May 03 2019 | patent expiry (for year 8) |
May 03 2021 | 2 years to revive unintentionally abandoned end. (for year 8) |
May 03 2022 | 12 years fee payment window open |
Nov 03 2022 | 6 months grace period start (w surcharge) |
May 03 2023 | patent expiry (for year 12) |
May 03 2025 | 2 years to revive unintentionally abandoned end. (for year 12) |