US20140270243A1

US20140270243A1 - Mobile device to vehicle integration

Info

Publication number: US20140270243A1
Application number: US14/202,582
Authority: US
Inventors: Paul Bennett
Original assignee: Commercial Vehicle Group Inc
Current assignee: Commercial Vehicle Group Inc; CVG Management Corp
Priority date: 2013-03-15
Filing date: 2014-03-10
Publication date: 2014-09-18
Also published as: WO2015138408A1; US9296320B2; US20140275834A1; US20140265479A1; US20140265419A1

Abstract

One or more embodiments of techniques or systems for mobile device to vehicle integration are provided herein. An armrest can include a docking station for a mobile device and an integration component can be configured to communicatively couple the mobile device with an input component, multimedia component, display component, fob component, warning component, etc. This integration enables an occupant of a vehicle to seamlessly interact with the mobile device through features of the vehicle, rather than through a mobile device interface. In one or more embodiments, mobile device data or mobile device applications are used to supplement integration, such as through voice commands, etc. For example, a warning can be provided if it is determined that the vehicle is speeding. As another example, personalized multimedia settings can be stored and programmed to the vehicle when the mobile device is docked.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/787,239 (Attorney Docket No. 104308.265) entitled “Seating Apparatus Systems”, filed on Mar. 15, 2013. The entirety of the above-noted application is incorporated by reference herein.

BACKGROUND

Generally, mobile devices, such as cell phones or smart phones can be difficult to use while navigating a vehicle. For example, if a smart phone is touch screen based, it may be difficult for a driver of a vehicle to operate the smart phone while driving the vehicle, because the driver may need to glance at the smart phone to input gestures via the touch screen. Additionally, mobile devices can be equipped with Bluetooth, or other such connectivity, for example.

SUMMARY

This summary is provided to introduce a selection of concepts in a simplified form that are described below in the detailed description. This summary is not intended to be an extensive overview of the claimed subject matter, identify key factors or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
One or more embodiments of techniques or systems for integrating a mobile device with a vehicle are provided herein. As an example, a mobile device can be docked in a docking station located within an armrest of a vehicle. While docked within the docking station, mobile device to vehicle integration can be enabled. This means that one or more features generally available on the mobile device can be accessed using one or more features of the vehicle. For example, when a call is received on a mobile device, such as a cell phone, smart phone, etc., an occupant of the vehicle can answer the call using a voice command on vehicles equipped with such voice recognition features. As another example, an occupant of the vehicle can play music stored on the mobile device through controls located on a dashboard of the vehicle. In other words, the mobile device can be used to customize one or more features of the vehicle. For example, when the mobile device is docked, settings associated with a seat of the vehicle can be adjusted. In other words, the phone or mobile device can act as a ‘key fob’, enabling a vehicle occupant to customize seat settings, multimedia settings, temperature settings, etc. In one or more embodiments, a position of a seat can be adjusted based on mobile device data. For example, the mobile device could be searched for mobile device data or mobile device applications, such as a social networking application or a dating website, and height data associated with the social networking application could be received and used to automatically adjust a seat for the occupant or mobile device user. In one or more embodiments, a mobile device can interact with or utilize mobile device data, mobile device applications, etc. to provide a warning to an occupant or adjust settings for the occupant. For example, if a mobile device user has a speed trap application for locating speed traps, a vehicle could provide an occupant of the vehicle with a warning when the vehicle is approaching a speed trap area.
In one or more embodiments, a system for mobile device to vehicle integration is provided. The system can comprise a seat, an armrest comprising a docking station for a mobile device, an input component, a display component, and an integration component. Upon docking the mobile device within the docking station, the integration component can be configured to communicatively couple the mobile device to the input component, the multimedia component, the display component, etc. In this way, the mobile device can be integrated with the vehicle so that an occupant of the vehicle may experience a seamless experience with the mobile device by interacting with features of the vehicle, rather than by interacting with an interface of the mobile device. In this way, safer driving can be promoted by ‘hiding’ a mobile device within a docking station cavity, thereby mitigating an occupant of a vehicle, such as a driver, from interfacing with the mobile device, while providing a safer alternative, such as a voice command, for example.
The following description and annexed drawings set forth certain illustrative aspects and implementations. These are indicative of but a few of the various ways in which one or more aspects are employed. Other aspects, advantages, or novel features of the disclosure will become apparent from the following detailed description when considered in conjunction with the annexed drawings.

DESCRIPTION OF THE DRAWINGS

Aspects of the disclosure are understood from the following detailed description when read with the accompanying drawings. It will be appreciated that elements, structures, etc. of the drawings are not necessarily drawn to scale. Accordingly, the dimensions of the same may be arbitrarily increased or reduced for clarity of discussion, for example.

FIG. 1 is an illustration of an example schematic diagram of a system for mobile device to vehicle integration, according to one or more embodiments.

FIG. 2 is an illustration of an example system comprising an armrest docking station on a seat, according to one or more embodiments.

FIG. 3 is an illustration of an example system comprising a seat with integrated speakers, according to one or more embodiments.

FIG. 4 is an illustration of an example system comprising an armrest docking station, according to one or more embodiments.

FIG. 5 is an illustration of an example flow diagram of a method for mobile device to vehicle integration, according to one or more embodiments.

FIG. 6 an illustration of an example computer-readable medium or computer-readable device comprising processor-executable instructions configured to embody one or more of the provisions set forth herein, according to one or more embodiments.

FIG. 7 an illustration of an example computing environment where one or more of the provisions set forth herein are implemented, according to one or more embodiments.

DETAILED DESCRIPTION

Embodiments or examples, illustrated in the drawings are disclosed below using specific language. It will nevertheless be understood that the embodiments or examples are not intended to be limiting. Any alterations and modifications in the disclosed embodiments, and any further applications of the principles disclosed in this document are contemplated as would normally occur to one of ordinary skill in the pertinent art.
It will be appreciated that for one or more of the figures herein, one or more boundaries, such as boundary 714 of FIG. 7, for example, are drawn with different heights, widths, perimeters, aspect ratios, shapes, etc. relative to one another merely for illustrative purposes, and are not necessarily drawn to scale. For example, because dashed or dotted lines are used to represent different boundaries, if the dashed and dotted lines were drawn on top of one another they would not be distinguishable in the figures, and thus are drawn with different dimensions or slightly apart from one another, in one or more of the figures, so that they are distinguishable from one another. As another example, where a boundary is associated with an irregular shape, the boundary, such as a box drawn with a dashed line, dotted lined, etc., does not necessarily encompass an entire component in one or more instances. Conversely, a drawn box does not necessarily encompass merely an associated component, in one or more instances, but encompasses at least a portion of one or more other components as well.
FIG. 1 is an illustration of an example schematic diagram of a system 100 for mobile device to vehicle integration, according to one or more embodiments. The system 100 can comprise a seat 110, an armrest 120, an integration component 130, and a display component 140. The armrest 120 can comprise a docking station cavity that houses a docking station 122 for a mobile device. The docking station 122 can be recessed within the docking station cavity such that a mobile device is substantially enclosed or surrounded by the armrest 120 while the mobile device is docked. The seat 110 can comprise a headset component (not shown) that can comprise a microphone or one or more speakers. In one or more embodiments, the seat 110 can comprise the microphone or one or more of the speakers. In one or more embodiments, the system 100 can comprise a vehicle information component 102, an input component 104, a learning component (not shown), or an inference component (not shown). Additionally, the system 100 can comprise a multimedia component 112, a warning component 114, or a fob component 116.
When the mobile device is docked with the docking station 122, the integration component 130 can communicatively couple the mobile device with one or more components of the system 100. For example, the integration component 130 can communicatively couple the mobile device with the seat 110, microphone, one or more speakers, the display component 140, vehicle information component 102, input component 104, multimedia component 112, warning component 114, or fob component 116. This means that the integration component 130 enables an occupant of a vehicle to interact with a mobile device that is docked within the docking station 122 of the armrest 120 via one or more features of the vehicle, such as voice commands, buttons, vehicle interfaces, etc. For example, an occupant can issue voice commands to the mobile device and in response to the voice command, a mobile device to vehicle integration system can provide an output, such as through one or more speakers or on a display component 140 associated with the vehicle. If an occupant issues a voice command, such as “call home”, the integration component 130 can relay that voice command to the mobile device, where the display component 140 can display confirmation of the call and/or one or more speakers may notify the occupant that the mobile device is dialing, and put the call through to a Bluetooth system of the vehicle.
The docking station 122 can comprise a variety of connectors for one or more mobile devices, such as universal serial bus (USB), micro USB, mini USB, lightning connector, etc. In one or more embodiments, the docking station 122 can be configured to charge a mobile device that is docked to the docking station 122. The docking station 122 can be recessed, such as within an armrest 120, such that the mobile device is physically secure. In this way, safer driving can be promoted because the armrest docking station 122 ‘hides’ a mobile device within a mobile device cavity such that direct or physical interaction with the mobile device can be limited or inhibited, for example.
In one or more embodiments, the input component 104 can be associated with one or more features of a vehicle, thereby enabling input to the mobile device to be provided through features of the vehicle. The input component 104 can be configured to communicatively couple features of the vehicle to the mobile device to vehicle integration system or components thereof. For example, the input component 104 can be a voice recognition module for a vehicle configured to allow an occupant of the vehicle to issue commands by speaking. In other words, the input component 104 can be configured to receive one or more voice commands from an occupant of the vehicle via a microphone. Additionally, the input component 104 can comprise buttons located within the vehicle. For example, buttons on a dashboard, radio, seat, window, etc. can be used to accept inputs from a user or an occupant of the vehicle. An occupant can press one or more buttons within the vehicle to access one or more features of a mobile device, such as answering a call, for example. In this way, the input component 104 can be configured to accept an input on behalf of the mobile device utilizing one or more features from the vehicle, where the integration component 130 can relay the input to the mobile device or a response to the input from the mobile device to one or more outputs or features of the vehicle, such as the display component 140 or one or more speakers, for example.
It will be appreciated that the input component 104 can be configured to accept an input on behalf of a mobile device by way of an access control panel on a car, one or more armrest controls, a vehicle menu, buttons on a steering wheel, via voice activated features or commands, etc. In one or more embodiments, one or more portions of the input component 104 can be located in convenient positions for a driver or an occupant of the vehicle, such as at eye level, on the steering wheel, on an armrest 120, on a back of a seat (for a backseat occupant), etc.
In one or more embodiments, other inputs can be detected. For example, a vehicle information component 102 can be configured to detect information related to the vehicle, an occupant of the vehicle, a driver of the vehicle, etc. It will be appreciated that one or more components of a mobile device to vehicle integration system can be configured to utilize information from one or more other components of the system to facilitate integration, as will be described herein. As an example, the multimedia component 112 can use vehicle information gathered from the vehicle information component 102 to enable or disable one or more features of a docked mobile device.
The display component 140 can be a heads up display, a dashboard display, a console display, a multi-information display, or comprise one or more displays. The speakers, microphone, or headset component can be removable, over the ear, or integrated into the seat 110. Additionally, such speakers, microphones, or headsets can be removable such that they are portable or compatible for use in one or more other applications, and plug into a headset jack, microphone jack or speaker jack, for example. In one or more embodiments, headsets, such as aftermarket headsets, removable headsets, gaming headsets, or Bluetooth headsets are compatible with the system 100. The microphone, one or more of the speakers, or the headset can be wired or wireless, and utilize Bluetooth technology for connectivity, for example. In one or more embodiments, one or more of the speakers or the headset can feature noise cancelling. For example, the headset can be configured to enable noise cancelling when an alert is received from the mobile device, such as a call, a text message, an email, an application alert, etc. In one or more embodiments, the headset can be configured to enable noise cancelling when a text message or email is being read by the multimedia component 112, as will be described herein.
In one or more embodiments, the integration component 130 can be configured to enable a user or an occupant of a vehicle to seamlessly interact with a mobile device that is docked within the docking station 122 of the armrest 120. The integration component 130 can be configured to communicatively couple a mobile device to a vehicle, aspects related to the vehicle, such as a position of a seat 110, multimedia settings, temperature control for the vehicle, a display component 140, a vehicle information component 102, an input component 104, a multimedia component 112, a warning component 114, a fob component 116, or one or more other components, such as an inference component or a learning component, for example. This means that a user or occupant can dock a mobile device at a mobile device to vehicle integration system within a vehicle, and interact with the mobile device using one or more features of the vehicle. For example, if the vehicle is equipped with voice detection, voice recognition, or voice commands, an occupant can issue commands to the mobile device by speaking, rather than entering commands through a tactile interface, such as a keyboard or touchscreen, thereby promoting safer driving because voice commands are generally hands free. In this way, a microphone or one or more speakers, such as those integrated into a headset component, the seat 110, or the vehicle, can be used to receive audio input from an occupant of the vehicle or provide auditory feedback for an occupant.
The integration component 130 can be configured to couple a mobile device with a vehicle such that one or more inputs can be accepted from a user or an occupant through buttons on the vehicle. For example, when the mobile device is docked and a phone call is received, an occupant could answer the call by hitting a button on the dash. Similarly, the integration component 130 can be configured to enable a display component 140 associated with the vehicle, such as a heads up display, to alert the occupant that the mobile device is receiving the phone call. Additionally, the integration component 130 could be configured to incorporate audio feedback with the alert. For example, the integration component 130 could prompt one or more speakers, such as one or more speakers associated with the headset component to play a notification, ringtone, etc. when the phone call is received.
In one or more embodiments, the integration component 130 can enable a touch screen display or a display of a vehicle to display one or more features or portions of a mobile device. For example, if a home screen of a mobile device has a weather application or a text message application, the integration component 130 can be configured to relay weather information associated with the weather application or texts associated with the text message application to the display component 140, which can display the weather or one or more of the texts. Further, a touch screen display of the vehicle could be associated with the input component 104 and the display component 140 of the mobile device to vehicle integration system and configured to both accept inputs from occupants of the vehicle and display outputs from the mobile device. The integration component 130 can be configured to port content from a mobile device to a display component 140. For example, the integration component 130 could enable the display component 140 of the car to play a slide show of pictures stored on the mobile device based on inputs entered through the input component 104.
Additionally, the integration component 130 can be configured to route alerts from a mobile device to a display component 140. For example, when a phone call, text, email, status, etc. is received by the mobile device, an alert associated with the mobile device can be sent by the integration component 130 to an output component, such as a display component 140 or one or more speakers. This means that the integration component 130 enables a docked mobile device to alert an occupant of a vehicle by way of sound or a display. In this way, the integration component 130 enables the display component 130 or one or more speakers to notify an occupant of an alert, such as an adjustment to the mobile device, power on, power off, volume up, volume down, text received, text sent, phone call received, phone call placed, charging of the mobile device, docking, undocking, locking, unlocking, email received, email sent, a state of the mobile device, such as on a call, call ended, unread email, accept call, reject or deny call, send to voicemail, etc.
The display component 140 can be configured to display an alert, a confirmation of an input, or a response to an input. For example, an alert may be received when a call is received by the mobile device. An occupant can accept the call by hitting a button for the input component 104, and the display component 140 can confirm the ‘answer call’ input. Additionally, the display component 140 can display caller information or the response to the ‘answer call’ input.
In one or more embodiments, the integration component 130 can be configured to read a text message or an email to an occupant of the vehicle via one or more speakers, such as speakers integrated with the seat 110. The display component 140 can be configured to display an alert or a response to an input pertaining to the text message. When the mobile device is docked and a text message is received, the integration component 130 can forward an alert associated with the text message to the display component 140. Accordingly, the display component 140 can display a notification that a text message has arrived. In response, a driver or occupant can hit a button, such as a button on a dash of the vehicle associated with the input component 104 to send an input, such as a read the text back command, to the mobile device via the mobile device to vehicle integration system. The input can be routed back to the mobile device via the integration component 130. When the mobile device receives the input or the read the text back command, the integration component 130 can facilitate reading of the text over one or more speakers of the vehicle, such as speakers integrated into a headset of a seat 110, for example.
In one or more embodiments, the display component 140 may not be identical to a display of the mobile device. In such a scenario, the integration component 130 can be configured to generate a format for content, such as a phone call, text message, email, etc., to be displayed on the display component 140. This enables a display of a vehicle or the display component 140 to integrate features of the mobile device utilizing features of the vehicle or display the alert from the mobile device based on the format generated by the integration component 130. As an example, if a dashboard display of the vehicle is only ten characters long and the text message is longer than ten characters, the integration component 130 can adapt content, such as a text message to scroll across the dashboard display.
In one or more embodiments, the multimedia component 112 can be configured to route communication between the mobile device to vehicle integration system and the mobile device. For example, the multimedia component 112 can be configured to route a phone call, text message, email, etc. from the mobile device to the integration component 130. The multimedia component 112 can be configured to receive metadata associated with a communication, such as a caller, a call duration, text recipient, email recipient, etc. Further, the display component 140 can be configured to display such metadata associated with corresponding communications, for example. Additionally, the multimedia component 112 can be configured to enable a user or an occupant to change one or more settings related to media, such as adjust a volume, change a track, pause, play, stop a track from playing, change a station, etc. based on an input. For example, an occupant could dock a mobile device in the docking station 122, and issue a command for the mobile device to play music by pushing a button or utilizing the input component 104. The multimedia component 112 could be configured to receive the input from the input component 104 and initiate playback via routing the command to the integration component 130. When the mobile device receives the play music command, the integration component 130 can route music from the mobile device to the multimedia component 112 to one or more speakers of the vehicle. Additionally, the multimedia component 112 can pass artist or song information from the mobile device to the display component 140. In this way, the multimedia component 112 can be configured to enable integration of media features of a mobile device with features of a vehicle, such as by adjusting a volume, changing a track, pausing, playing, or stopping a music player on the mobile device based on the input.
In one or more embodiments, the multimedia component 112 can be configured to initiate a request for assistance based on an input received through the input component 104. For example, an occupant can hold a button down to initiate the request, whereby the multimedia component 112 may then contact a third party for cab assistance. The multimedia component 112 can initiate a call to facilitate assistance. For example, if a vehicle has a flat tire, the multimedia component 112 can be configured to detect the flat tire through the integration component 130, and place the call automatically. In other words, if a driver of a vehicle is driving along, and a low tire pressure is detected in a tire of the vehicle, the multimedia component 112 can automatically call a tow truck for the driver or prompt an occupant whether or not to call.
In one or more embodiments, the warning component 114 can be configured to generate a warning based on mobile device data of a docked mobile device. For example, if the mobile device has a speed trap application installed, the warning component 114 can search that application for speed traps and issue a warning to a driver of the vehicle based on a location of the vehicle. In this example, if a driver docks a mobile device equipped with a speed trap application, the warning component 114 can interface with the mobile device via the integration component 130 and determine one or more speed traps in the area. When the driver approaches a speed trap area, the warning component 114 can issue a warning to the driver. The warning can be communicated to the driver of the vehicle via the display component 140, such as by flashing a display or a light on a dash, for example. The warning can also be communicated by playing a sound on one or more speakers, such as speakers incorporated into a headset on the seat 110, for example.
The warning component 114 can provide warnings based on a speed of a vehicle, a speed limit of an environment in which the vehicle is travelling, speed traps, or other applications installed on mobile devices. In one or more embodiments, the warning component 114 can be configured to issue a warning to the driver based on road conditions or weather, for example. In other words, the warning component 114 can issue a warning when the weather forecast (e.g., based on a weather app on the mobile device) is associated with a temperature drop or precipitation. Accordingly, the warning component 114 may warn a driver when it is about to rain, snow, or the temperature drops (e.g., potentially creating a hazardous driving environment, such as icy roads).
In one or more embodiments, the warning component 114 can interface with the vehicle information component 102 to disable one or more features of the mobile device based on vehicle information or mobile device data. For example, when the vehicle information component 102 notes that a driver is taking many turns, such as over a threshold within a time, the warning component 114 can issue a warning to the driver that out bound text messages will be disabled. Here, the vehicle information component 102 or multimedia component 112 can be configured to disable outbound texts such that a driver of a vehicle cannot send texts on a temporary basis. In this way, safer driving can be promoted. As another example, the vehicle information component 102 can be used to disable texting when a vehicle is in drive or in motion by interfacing with the multimedia component 112, which can disable features of the mobile device related to texting, among other things. It will be appreciated that the warning component 114 can be configured to issue warnings when one or more features are disabled, where such warnings can be communicated to an occupant via the display component or one or more speakers, for example.
In one or more embodiments, the fob component 116 can be configured to remember, learn, or infer one or more settings or preferences for one or more occupants of the vehicle. In doing so, it will be appreciated that the fob component 116 can be configured to interact with one or more other components of the mobile device to vehicle integration system. As an example, the fob component 116 can be configured to adjust a position of a seat within a vehicle, such as seat 110, based on one or more user preferences stored in the mobile device. When a driver sits in the seat 110 and makes one or more adjustments, for example, the integration component 130 can relay adjustment information to the fob component 116, which then stores a corresponding seat profile in the mobile device so that the next time the mobile device is docked, the seat 110 will automatically adjust to the position stores in the seat profile. In this way, the fob component 116 can be configured to customize one or more features of the vehicle, by adjusting one or more settings or one or more features associated with the vehicle. Additionally, the display component 140 can be configured to display confirmation that the seat will (re)adjust to conform to the positioning associated with the seat profile. In one or more embodiments, audio confirmation can be provided via one or more speakers associated with the seat 110.
In one or more embodiments, the fob component 116 can be configured to infer positioning or height associated with a driver of a vehicle based on mobile device data. For example, the fob component 116 can search the mobile device data or mobile device applications for a social networking or dating application. In this example, the fob component 116 can determine a height of a driver based on a height listed in a corresponding social networking or dating profile. Accordingly, the fob component 116 can interface with the integration component 130 to adjust seat positioning based on an inferred, learned, or estimated height of a driver, for example. It will be appreciated that the fob component 116 may be configured to learn, retain, or remember one or more preferences for one or more other occupants of a vehicle. For example, if a driver adjusts the driver seat according to a first seat configuration and a passenger adjusts a passenger seat according to a second seat configuration, the fob component 116 can be configured to learn both configurations and adjust the respective seats accordingly when the mobile device is docked. In one or more embodiments, a seat configuration can be stored on the fob component 116. In other embodiments, the seat configuration can be stored on the mobile device.
In one or more embodiments, the fob component 116 can comprise an inference component (not shown) configured to infer attributes or one or more desired preferences for an occupant of the vehicle. For example, the inference component can be configured to identify an image of a driver on a social networking site or application, infer an estimated height of the driver based on the identified image, and adjust one or more seat preferences based on the estimated height or the identified image of the driver. As an example, the display component 140 could be configured to prompt the driver with the estimated height to confirm whether or not the estimated height is correct. If a driver confirms the estimated height is correct, the fob component 116 can be configured to adjust the seat 110 according to an estimated seat profile using the estimated height. If the driver indicates that the estimated height is incorrect, the fob component 116 can be configured to retain seat settings inputted by the driver.
Additionally, mobile device data can be used to infer whether or not to enable or disable one or more features of the vehicle. For example, the fob component 116 can access weather information on the mobile device via the integration component 130 to determine an outside temperature. In one or more embodiments, the fob component 116 can be configured to roll one or more windows, such as power windows down when the temperature is about 70° C. Additionally, the fob component can be configured to roll the windows up when the vehicle is travelling above or below a threshold speed. For example, when the vehicle information component 102 indicates that the vehicle is traveling above 50 mph, the fob component can be configured to roll the windows up to mitigate noise. In one or more embodiments, the fob component 116 can be configured to enable heat or heated seats when the outside temperature is below a threshold temperature. For example, when mobile device data indicates that the outside temperature is less than 50° C., the fob component 116 can be configured to enable heated seats or heat in the vehicle. The display component 140 can be configured to alert occupants of the vehicle when the fob component 116 enables one or more features of the vehicle, such as the heated seats, temperature control, temperature vents, etc. In this way, the mobile device to vehicle integration system enables the mobile device to act as a fob to remember, learn, or infer one or more user settings or preferences.
It will be appreciated that the fob component 116 can be configured to learn or infer other settings or preferences, such as door settings, trunk settings, horn honk on lock, etc. Additionally, the fob component 116 can be configured to determine a variety of factors associated with features of the vehicle, such as a day, season, time of day, etc. by interacting with the integration component 130. In this way, the fob component 116 can be utilized to customize preferences for occupants of a vehicle.
In one or more embodiments, the fob component 116 can comprise a learning component configured to learn, remember, etc., one or more settings or one or more preferences for future recall. Accordingly, when an occupant docks a mobile device in a docking station 122, the fob component can be configured to load one or more user preferences to a vehicle. If settings are changed, the fob component can associate the mobile device with a set of user preferences corresponding to the changed settings. The fob component 116 can be configured to associate the mobile device with a first set of user preferences for a first user and a second mobile device with a second set of user preferences different than the first set of user preferences. This enables the mobile device to vehicle integration system to customize settings, such as seat settings for different occupants with different mobile devices.
FIG. 2 is an illustration of an example system 200 comprising an armrest docking station on a seat, according to one or more embodiments. In one or more embodiments, the system 200 can comprise a seat 110 comprising one or more integrated speakers 210. The system can comprise an armrest 120, where the armrest 120 comprises a docking station 122 recessed within a docking station cavity 222. One or more temperature vents is seen at 240, such as those controlled by the fob component 116.
FIG. 3 is an illustration of an example system 300 comprising a seat with integrated speakers, according to one or more embodiments. The system 300 can comprise a seat 110, one or more integrated speakers/microphone 210, and a headrest component 310.
FIG. 4 is an illustration of an example system 400 comprising an armrest docking station, according to one or more embodiments. The system 400 can comprise an armrest 120, where a docking station 122 can be recessed within a docking station cavity 222. Additionally, one or more temperature vents 240 can be used to control a temperature within a vehicle, as described with reference to the fob component 116.
FIG. 5 is an illustration of an example flow diagram of a method 500 for mobile device to vehicle integration, according to one or more embodiments. At 502, a mobile device can be docked within a docking station cavity of an armrest. At 504, one or more features of the mobile device can be integrated with one or more features of a vehicle by communicatively coupling the mobile device with the vehicle. At 506, one or more user preferences can be loaded to the vehicle. Additionally, one or more warnings can be provided based on mobile device data.
Still another embodiment involves a computer-readable medium comprising processor-executable instructions configured to implement one or more embodiments of the techniques presented herein. An embodiment of a computer-readable medium or a computer-readable device that is devised in these ways is illustrated in FIG. 6, wherein an implementation 600 comprises a computer-readable medium 608, such as a CD-R, DVD-R, flash drive, a platter of a hard disk drive, etc., on which is encoded computer-readable data 606. This computer-readable data 606, such as binary data comprising a plurality of zero's and one's as shown in 606, in turn comprises a set of computer instructions 604 configured to operate according to one or more of the principles set forth herein. In one such embodiment 600, the processor-executable computer instructions 604 are configured to perform a method 602, such as the method 500 of FIG. 5. In another embodiment, the processor-executable instructions 604 are configured to implement a system, such as the system 100 of FIG. 1. Many such computer-readable media are devised by those of ordinary skill in the art that are configured to operate in accordance with the techniques presented herein.
As used in this application, the terms “component”, “module,” “system”, “interface”, and the like are generally intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more components residing within a process or thread of execution and a component may be localized on one computer or distributed between two or more computers.
Further, the claimed subject matter is implemented as a method, apparatus, or article of manufacture using standard programming or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. Of course, many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter.
FIG. 7 and the following discussion provide a description of a suitable computing environment to implement embodiments of one or more of the provisions set forth herein. The operating environment of FIG. 7 is only one example of a suitable operating environment and is not intended to suggest any limitation as to the scope of use or functionality of the operating environment. Example computing devices include, but are not limited to, personal computers, server computers, hand-held or laptop devices, mobile devices, such as mobile phones, Personal Digital Assistants (PDAs), media players, and the like, multiprocessor systems, consumer electronics, mini computers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
Generally, embodiments are described in the general context of “computer readable instructions” being executed by one or more computing devices. Computer readable instructions are distributed via computer readable media as will be discussed below. Computer readable instructions are implemented as program modules, such as functions, objects, Application Programming Interfaces (APIs), data structures, and the like, that perform particular tasks or implement particular abstract data types. Typically, the functionality of the computer readable instructions are combined or distributed as desired in various environments.
FIG. 7 illustrates a system 700 comprising a computing device 712 configured to implement one or more embodiments provided herein. In one configuration, computing device 712 includes at least one processing unit 716 and memory 718. Depending on the exact configuration and type of computing device, memory 718 may be volatile, such as RAM, non-volatile, such as ROM, flash memory, etc., or a combination of the two. This configuration is illustrated in FIG. 7 by dashed line 714.
In other embodiments, device 712 includes additional features or functionality. For example, device 712 also includes additional storage such as removable storage or non-removable storage, including, but not limited to, magnetic storage, optical storage, and the like. Such additional storage is illustrated in FIG. 7 by storage 720. In one or more embodiments, computer readable instructions to implement one or more embodiments provided herein are in storage 720. Storage 720 also stores other computer readable instructions to implement an operating system, an application program, and the like. Computer readable instructions are loaded in memory 718 for execution by processing unit 716, for example.
The term “computer readable media” as used herein includes computer storage media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions or other data. Memory 718 and storage 720 are examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVDs) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by device 712. Any such computer storage media is part of device 712.
The term “computer readable media” includes communication media. Communication media typically embodies computer readable instructions or other data in a “modulated data signal” such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” includes a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
Device 712 includes input device(s) 724 such as keyboard, mouse, pen, voice input device, touch input device, infrared cameras, video input devices, or any other input device. Output device(s) 722 such as one or more displays, speakers, printers, or any other output device are also included in device 712. Input device(s) 724 and output device(s) 722 are connected to device 712 via a wired connection, wireless connection, or any combination thereof. In one or more embodiments, an input device or an output device from another computing device are used as input device(s) 724 or output device(s) 722 for computing device 712. Device 712 also includes communication connection(s) 726 to facilitate communications with one or more other devices.
According to one or more aspects, a system for mobile device to vehicle integration is provided, comprising a seat paired with a microphone and one or more speakers. The system can comprise an armrest comprising a docking station for a mobile device, where the docking station can be recessed within a docking station cavity within the armrest. The system can comprise an input component configured to accept an input on behalf of the mobile device, where the input component can be configured to accept the input via the microphone. The system can comprise a multimedia component configured to send the input to the mobile device or receive an alert from the mobile device. The system can comprise a display component configured to display the alert from the mobile device, a current state of the mobile device, or a response to the input. The system can comprise an integration component configured to communicatively couple the mobile device to the input component, the multimedia component, the microphone, one or more of the speakers, or the display component.
In one or more embodiments, the docking station can be configured to charge the mobile device. The system can comprise a vehicle information component configured to receive vehicle information, where the integration component can be configured to communicatively couple the mobile device to the vehicle information component, and the multimedia component can be configured to disable one or more features of the mobile device based on the vehicle information. The seat can comprise a headset component comprising the microphone or one or more of the speakers, where the headset component can be removable from the seat. The display component can comprise a heads up display.
The integration component can be configured to route a phone call from the mobile device to the integration component, route a text message from the mobile device to the integration component, route an email from the mobile device to the integration component, enable noise cancelling based on receiving the alert from the mobile device, initiate a request for assistance based on the input, adjust a volume, change a track, pause, play, or stop a music player on the mobile device based on the input. Additionally, the display component can be configured to display the alert, the current state of the mobile device, or the response to the input based on the routing.
According to one or more aspects, a system for mobile device to vehicle integration is provided, comprising a seat paired with a microphone and one or more speakers. The system can comprise an armrest comprising a docking station for a mobile device, where the docking station can be recessed within a docking station cavity within the armrest. The system can comprise an input component configured to accept an input on behalf of the mobile device, where the input component can be configured to accept the input via the microphone. The system can comprise a warning component configured to generate a warning based on mobile device data associated with the mobile device. The system can comprise a display component configured to display the warning, an alert from the mobile device, a current state of the mobile device, or a response to the input. The system can comprise an integration component configured to communicatively couple the mobile device to the input component, the warning component, the multimedia component, the microphone, one or more of the speakers, or the display component.
In one or more embodiments, the multimedia component can be configured to route a phone call from the mobile device to the integration component, route a text message from the mobile device to the integration component, or route an email from the mobile device to the integration component. The integration component can be configured to generate a format for the phone call, the text message, or the email. The display component can be configured to display the alert from the mobile device based on the format generated by the integration component.
According to one or more aspects, a system for mobile device to vehicle integration is provided, comprising a seat paired with a microphone and one or more speakers. The system can comprise an armrest comprising a docking station for a mobile device, where the docking station can be recessed within a docking station cavity within the armrest. The system can comprise an input component configured to accept an input on behalf of the mobile device, where the input component can be configured to accept the input via the microphone. The system can comprise a fob component configured to adjust a position of the seat based on mobile device data associated with the mobile device. The system can comprise a display component configured to display an alert from the mobile device, a current state of the mobile device, or a response to the input. The system can comprise an integration component configured to communicatively couple the mobile device to the input component, the warning component, the multimedia component, the microphone, one or more of the speakers, or the display component.
In one or more embodiments, the fob component can be configured to associate the mobile device with a first set of user preferences. Additionally, the fob component can be configured to associate a second mobile device with a second set of user preferences different than the first set of user preferences. The fob component can be configured to adjust a temperature of an associated vehicle based on the mobile device data. The fob component can be configured to adjust multimedia settings of an associated vehicle based on the mobile device data. The fob component can be configured to infer the position of the seat based on the mobile device data.
Although the subject matter has been described in language specific to structural features or methodological acts, it is to be understood that the subject matter of the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example embodiments.
Various operations of embodiments are provided herein. The order in which one or more or all of the operations are described should not be construed as to imply that these operations are necessarily order dependent. Alternative ordering will be appreciated based on this description. Further, it will be understood that not all operations are necessarily present in each embodiment provided herein.
As used in this application, “or” is intended to mean an inclusive “or” rather than an exclusive “or”. In addition, “a” and “an” as used in this application are generally construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Also, at least one of A and B and/or the like generally means A or B or both A and B. Further, to the extent that “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising”.
Further, unless specified otherwise, “first”, “second”, or the like are not intended to imply a temporal aspect, a spatial aspect, an ordering, etc. Rather, such terms are merely used as identifiers, names, etc. for features, elements, items, etc. For example, a first channel and a second channel generally correspond to channel A and channel B or two different or two identical channels or the same channel.
Also, although the disclosure has been shown and described with respect to one or more implementations, equivalent alterations and modifications will occur based on a reading and understanding of this specification and the annexed drawings. The disclosure includes all such modifications and alterations and is limited only by the scope of the following claims.

Claims

What is claimed is:

1. A system for mobile device to vehicle integration, comprising:

a seat paired with a microphone and one or more speakers;

an armrest comprising a docking station for a mobile device, the docking station recessed within a docking station cavity within the armrest;

an input component configured to accept an input on behalf of the mobile device, the input component configured to accept the input via the microphone;

a multimedia component configured to:

send the input to the mobile device; or

receive an alert from the mobile device;

a display component configured to display:

the alert from the mobile device;

a current state of the mobile device; or

a response to the input; and

an integration component configured to communicatively couple the mobile device to the input component, the multimedia component, the microphone, one or more of the speakers, or the display component.

2. The system of claim 1, the docking station configured to charge the mobile device.

3. The system of claim 1, comprising a vehicle information component configured to receive vehicle information, the integration component configured to communicatively couple the mobile device to the vehicle information component, the multimedia component configured to disable one or more features of the mobile device based on the vehicle information.

4. The system of claim 1, the seat comprising a headset component comprising the microphone or one or more of the speakers, the headset component removable from the seat.

5. The system of claim 1, the display component comprising a heads up display.

6. The system of claim 1, the multimedia component configured to:

route a phone call from the mobile device to the integration component;

route a text message from the mobile device to the integration component; or

route an email from the mobile device to the integration component.

7. The system of claim 6, the display component configured to display the alert, the current state of the mobile device, or the response to the input based on the routing.

8. The system of claim 1, the multimedia component configured to enable noise cancelling based on receiving the alert from the mobile device.

9. The system of claim 1, the multimedia component configured to initiate a request for assistance based on the input.

10. The system of claim 1, the multimedia component configured to adjust a volume, change a track, pause, play, or stop a music player on the mobile device based on the input.

11. A system for mobile device to vehicle integration, comprising:

a seat paired with a microphone and one or more speakers;

a warning component configured to generate a warning based on mobile device data associated with the mobile device;

a display component configured to display:

the warning;

an alert from the mobile device;

a current state of the mobile device; or

a response to the input; and

an integration component configured to communicatively couple the mobile device to the input component, the warning component, the microphone, one or more of the speakers, or the display component.

12. The system of claim 11, the integration component configured to:

route a phone call from the mobile device to the integration component;

route a text message from the mobile device to the integration component; or

route an email from the mobile device to the integration component.

13. The system of claim 12, the integration component configured to generate a format for the phone call, the text message, or the email.

14. The system of claim 13, the display component configured to display the alert from the mobile device based on the format generated by the integration component.

15. A system for mobile device to vehicle integration, comprising:

a seat paired with a microphone and one or more speakers;

a fob component configured to adjust a position of the seat based on mobile device data associated with the mobile device;

a display component configured to display:

an alert from the mobile device;

a current state of the mobile device; or

a response to the input; and

an integration component configured to communicatively couple the mobile device to the input component, the fob component, the microphone, one or more of the speakers, or the display component.

16. The system of claim 15, the fob component configured to associate the mobile device with a first set of user preferences.

17. The system of claim 16, the fob component configured to associate a second mobile device with a second set of user preferences different than the first set of user preferences.

18. The system of claim 15, the fob component configured to adjust a temperature of an associated vehicle based on the mobile device data.

19. The system of claim 15, the fob component configured to adjust multimedia settings of an associated vehicle based on the mobile device data.

20. The system of claim 15, the fob component configured to infer the position of the seat based on the mobile device data.