Vehicle seat memory from remote device

Abstract

This disclosure provides "vehicle seat memory from remote devices". A vehicle includes a controller programmed to identify seating positions in the vehicle corresponding to each of a plurality of roaming devices communicating with the vehicle. The controller is configured to: receive at least one seating profile from each of the roaming devices; and adjust seating parameters relating to each of the seating positions based on the seating profile received from the corresponding roaming device.

Description

Technical Field

[0001] This application generally relates to a system for adjusting vehicle settings based on driver and passenger settings stored in a remote device. Background Technology

[0002] Upon entering the vehicle, the driver and passengers can adjust the seats to their desired positions. The driver can also adjust the mirrors for a safe driving position. The seats can be manually activated by the driver or passenger. Some adjustment mechanisms may be purely mechanical, while others may be electrically assisted. Additionally, some vehicles may have the ability to store previous settings in memory for later retrieval. Users can reprogram buttons to remember and retrieve current settings. A drawback of this system is that settings can be overwritten by other drivers or passengers. Furthermore, the settings are only available in vehicles where they are stored. Summary of the Invention

[0003] A vehicle includes a controller programmed to: identify a seating position in the vehicle corresponding to each of a plurality of roaming devices communicating with the vehicle; receive at least one seating profile from each of the roaming devices; and adjust seating parameters for each of the seating positions based on the seating profile received from the corresponding roaming device.

[0004] The controller can also be programmed to: output an identifier associated with each of the roaming devices to a display to request input related to a seating position; and receive a response indicating a seating position corresponding to each of the roaming devices. The controller can also be programmed to: detect the position of each of the roaming devices within the vehicle; and identify a seating position corresponding to each of the roaming devices based on the position. The at least one seating profile may include a preferred rear child safety lock setting. The at least one seating profile may include a preferred rear window lock setting. The controller can also be programmed to: adjust seating parameters based on a seating profile corresponding to the driver's seating position received from the roaming devices in response to identifying a seating position that does not correspond to any of the roaming devices. The roaming devices can be configured to store seating profiles for each seating position in the vehicle. The controller can also be programmed to receive seating positions from the corresponding roaming devices. The seating position may differ from the driver's seat position. The controller can also be programmed to rescale at least one seating profile in response to a vehicle model different from the vehicle model associated with at least one seating profile.

[0005] A vehicle includes a controller programmed to: receive from a roaming device a plurality of seating profiles corresponding to each seating position in the vehicle and corresponding to a vehicle model; and, in response to identifying a seating position in the vehicle associated with the roaming device, adjust seating parameters relating to the seating position associated with the roaming device according to the corresponding seating profile.

[0006] The seating profile may include a preferred rear child safety door lock setting. The seating profile may also include a preferred rear window lock setting. The controller may also be programmed to: in response to receiving a seating profile that does not correspond to the vehicle model, rescale the seating profile so that the distances between the seat and steering wheel, and between the seat and pedals, are the same as the distances associated with the seating profile. The controller may also be programmed to: in response to a vehicle identifier that matches the received vehicle identifier, identify the seating position based on a preferred seating position received from the corresponding roaming device.

[0007] A method includes identifying a seating position corresponding to each of a plurality of roaming devices communicating with the controller. The method further includes receiving a seating profile from each of the roaming devices via the controller. The method also includes adjusting seating parameters for each seating position via the controller based on the seating profile received from the corresponding roaming device.

[0008] The method may further include: outputting a list of identifiers for each of the roaming devices to a vehicle touchscreen display; and receiving a response from the vehicle touchscreen display indicating a seating position for each of the roaming devices. The method may further include identifying the seating position for each of the roaming devices by a controller based on the strength of a signal received from each of the roaming devices. The method may further include rescaling a seating profile by a controller in response to a vehicle identifier associated with the controller being different from a vehicle identifier associated with a seating profile. The method may further include receiving a seating position from at least one of the roaming devices by a controller. Attached Figure Description

[0009] Figure 1 This is a possible configuration for the vehicle communication system.

[0010] Figure 2 It refers to the possible configurations of a vehicle for adjusting seating parameters for each seating position within the vehicle.

[0011] Figure 3 It is a flowchart of the possible sequence of operations for adjusting the seating parameters for each seating position. Detailed Implementation

[0012] This document describes embodiments of the present disclosure. However, it should be understood that the disclosed embodiments are merely examples and other embodiments may take various forms and alternatives. The drawings are not necessarily drawn to scale; some features may be exaggerated or minimized to show detail of particular components. Therefore, the specific structural and functional details disclosed herein should not be construed as limiting, but merely as a representative basis for teaching those skilled in the art to employ the invention in different ways. As will be understood by those skilled in the art, the various features shown and described with reference to any of the drawings may be combined with features shown in one or more other drawings to produce embodiments not explicitly shown or described. Combinations of the shown features provide representative embodiments for typical applications. However, various combinations and modifications of the features consistent with the teachings of this disclosure may be desired for a particular application or implementation.

[0013] Figure 1 An exemplary block topology for a vehicle-based computing system 100 (VCS) for vehicle 131 is shown. An example of such a vehicle-based computing system 100 is the SYNC system manufactured by The Ford Motor Company. Vehicle 131 with the vehicle-based computing system 100 enabled may contain a visual front-end interface 104 located within vehicle 131. If, for example, interface 104 is equipped with a touch-sensitive screen, a user can interact with said interface 104. In another illustrative embodiment, interaction occurs via button presses, a spoken dialogue system with automatic speech recognition and speech synthesis.

[0014] exist Figure 1 In the illustrated embodiment, at least one processor 103 controls at least a portion of the operation of the vehicle-based computing system 100. The processor 103 provides onboard processing of commands and routines within the vehicle 131. Furthermore, the processor 103 is connected to both a non-persistent storage device 105 and a persistent storage device 107. In this illustrative embodiment, the non-persistent storage device 105 is random access memory (RAM), and the persistent storage device 107 is a hard disk drive (HDD) or flash memory. Non-persistent memory can include both persistent memory and RAM. Generally, persistent storage device 107 can include all forms of memory that maintain data when the computer or other device is powered off. These include, but are not limited to, HDDs, CDs, DVDs, magnetic tapes, solid-state drives, portable USB drives, and any other suitable form of persistent memory.

[0015] Processor 103 may also include several different inputs that allow users and external systems to interact with processor 103. Vehicle-based computing system 100 may include: a microphone 129; an auxiliary input port 125 (for input 133); a Universal Serial Bus (USB) input 123; a Global Positioning System (GPS) input 124; a screen 104, which may be a touchscreen display; and a Bluetooth input 115. VCS 100 may also include an input selector 151 configured to allow users to switch between various inputs. Inputs from both microphone 129 and auxiliary connector 125 may be converted from analog to digital by analog-to-digital (A / D) converter 127 before being passed to processor 103. Although not illustrated, numerous vehicle components and auxiliary components that communicate with the VCS can use vehicle networks (such as, but not limited to, Controller Area Network (CAN) bus, Local Area Internet (LIN) bus, Media-Oriented System Transport (MOST) bus, Ethernet bus, or FlexRay bus) to transfer data to and from the VCS 100 (or its components).

[0016] Outputs from processor 103 may include, but are not limited to, visual display 104 and speaker 113 or stereo system outputs. Speaker 113 may be connected to amplifier 111 and receive its signal from processor 103 via digital-to-analog (D / A) converter 109. Outputs may also be made to remote Bluetooth devices such as personal navigation device (PND) 154 or USB devices such as vehicle navigation device 160 along the bidirectional data streams shown at 119 and 121, respectively.

[0017] In one illustrative embodiment, system 100 uses a Bluetooth transceiver 115 with an antenna 117 to communicate with a user's roaming device 153 (e.g., a cellular phone, smartphone, personal digital assistant (PDA), or any other device with wireless remote network connectivity). The roaming device 153 can then be used to communicate with a network 161 outside the vehicle 131, for example, via a device-tower communication path 155 with a cellular tower 157 and via a tower-to-network communication path 159. In some embodiments, the tower 157 can be a wireless Ethernet or WiFi access point defined by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards. Exemplary communication between the roaming device 153 and the Bluetooth transceiver 115 is represented by a Bluetooth signal path 114.

[0018] Pairing of the roaming device 153 and the Bluetooth transceiver 115 can be indicated via button 152 or a similar input. Therefore, the CPU is instructed that the in-vehicle Bluetooth transceiver 115 will pair with the Bluetooth transceiver in the roaming device 153.

[0019] Data can be transmitted between CPU 103 and network 161 using, for example, a data plan associated with roaming device 153, onboard audio data, or dual-tone multi-frequency (DTMF) tones. Alternatively, it may be desirable to include an onboard modem 163 with antenna 118 to establish a vehicle-to-device communication path 116 for transmitting data between CPU 103 and network 161 via voice bands. Roaming device 153 can then be used to communicate with network 161 outside vehicle 131, for example, via a device-to-tower communication path 155 with cellular tower 157 and a tower-to-network communication path 159. In some embodiments, modem 163 can establish a vehicle-tower communication path 120 directly with tower 157 to communicate with network 161. By non-limiting example, modem 163 may be a USB cellular modem, and vehicle-tower communication path 120 may be cellular communication.

[0020] In one illustrative embodiment, processor 103 is provided with an operating system that includes an application programming interface (API) for communicating with modem application software. The modem application software can access embedded modules or firmware on Bluetooth transceiver 115 to perform wireless communication with remote Bluetooth transceivers, such as those found in roaming device 153. Bluetooth is a subset of the IEEE 802 PAN (Personal Area Network) protocol. The IEEE 802 LAN (Local Area Network) protocol includes WiFi and has significant overlap with IEEE 802 PAN. Both are suitable for wireless communication within vehicles. Other wireless communication methods that can be used in this field are free-space optical communication (such as IrDA) and non-standardized consumer IR protocols or inductively coupled methods, including but not limited to near-field communication systems such as RFID.

[0021] In another embodiment, roaming device 153 includes a modem for voiceband or broadband data communication. In the voice-over data embodiment, a technique called frequency division multiplexing can be implemented when the owner of the roaming device can make a call through the device while transmitting data. At other times, when the owner is not using the device, data transmission can use the entire bandwidth (300 Hz to 3.4 kHz in one instance). While frequency division multiplexing may be common for and still in use for analog cellular communication between vehicles and the Internet, it has been largely replaced by hybrids of code division multiple access (CDMA), time division multiple access (TDMA), and space division multiple access (SDMA) for digital cellular communication, including but not limited to orthogonal frequency division multiple access (OFDMA) which may include time-domain statistical multiplexing. These are all ITU International Mobile Telecommunications (IMT) 2000 (3G) compliant standards and provide data rates of up to 2 Mbps for stationary or walking users and up to 385 Kbps for users in moving vehicles. The 3G standard is now being superseded by International Mobile Telecommunications Advanced (IMT-Advanced) (4G), which provides 100 Mbps for users in vehicles and 1 Gbps for stationary users. If the user has a data plan associated with roaming device 153, the data plan may allow for broadband transmission, and the system can use a much wider bandwidth (accelerating data transfer). In another embodiment, roaming device 153 is replaced by a cellular communication device (not shown) installed in vehicle 131. In yet another embodiment, roaming device 153 may be a wireless local area network (LAN) device capable of communicating via, for example (but not limited to), an IEEE 802.11g network (i.e., WiFi) or a WiMax network.

[0022] In one embodiment, input data may be transmitted via audio data or a data schedule through the roaming device 153, via the in-vehicle Bluetooth transceiver 115, and to the vehicle's internal processor 103. For example, in the case of some temporary data, the data may be stored on an HDD or other storage medium 107 until the data is no longer needed.

[0023] Additional sources that can interface with vehicle 131 include: a personal navigation device 154 having, for example, a USB connection 156 and / or an antenna 158; a vehicle navigation device 160 having a USB 162 or other connection; an in-vehicle GPS device 124; or a remote navigation system (not shown) having a connection to network 161. USB is one of a class of serial networking protocols. IEEE 1394 (FireWire) TM (Apple), iLINK TM (Sony) and LynxTM The backbone of device-to-device serial standards consists of protocols such as Texas Instruments, EIA (Electronic Industries Association) serial protocol, IEEE 1284 (Centronics Port), S / PDIF (Sony / Phillips Digital Interconnect Format), and USB-IF (USB Implementers Forum). Most of these protocols can be implemented for electrical or optical communication.

[0024] In addition, the CPU 103 can communicate with a variety of other auxiliary devices 165. The auxiliary devices 165 can be connected wirelessly (e.g., via auxiliary device antenna 167) or wiredly (e.g., auxiliary device USB 169). The auxiliary devices 165 may include, but are not limited to, personal media players, wireless health devices, portable computers, etc.

[0025] CPU 103 can be connected to one or more Near Field Communication (NFC) transceivers 176. NFC transceivers 176 can be configured to establish communication with compatible devices in the vicinity of NFC transceivers 176. NFC communication protocols can be used to identify compatible roaming devices in the vicinity of NFC transceivers 176.

[0026] Alternatively, CPU 103 can connect to vehicle-based wireless router 173 using, for example, a WiFi (IEEE 802.11) transceiver / antenna 171. This allows CPU 103 to connect to remote networks within range of local router 173. In some configurations, router 173 and modem 163 can be combined into a single unit. However, the features described herein can be applied to configurations where the modules are separate or integrated.

[0027] In addition to having the exemplary process executed by a vehicle computing system located within the vehicle, in some embodiments, the exemplary process may also be executed by a computing system communicating with the vehicle computing system. Such a system may include, but is not limited to, wireless devices (e.g., but not limited to, mobile phones) or remote computing systems (e.g., but not limited to, servers) connected via wireless devices. These systems may be collectively referred to as the Vehicle-Associated Computing System (VACS). In some embodiments, specific components of the VCS may execute specific parts of the process depending on a specific implementation of the system. For example, and not limitingly, if a process has steps involving sending or receiving information with a paired wireless device, it is possible that the wireless device does not execute the process because the wireless device does not “send and receive” information with itself. Those skilled in the art will understand when it is inappropriate to apply a particular VCS to a given solution. In all solutions, it is anticipated that the vehicle computing system (VCS) located at least within the vehicle itself will be able to execute the exemplary process.

[0028] Figure 2Possible configurations of a system for vehicle 200 are shown. Vehicle 200 may include a seat adjustment system 210. Seat adjustment system 210 may be configured to change the position of a seat. Seats may include front seats and rear seats. Front seats may include a driver-side seat and a passenger-side seat. Adjustments may include fore / aft adjustment, seat back position adjustment, seat height adjustment, and lumbar support adjustment. Seat adjustment system 210 may include a user interface 212 for the driver to manually position the seat. User interface 212 may include one or more switches or buttons associated with each of the adjustment parameters. In some configurations, user interface 212 may be via a touchscreen display (e.g., 104) displaying associated menu items for positioning the seat. Physical switches or buttons may be located on the corresponding seat. In some configurations, adjustment switches may be located on the nearest door or center console. Occupants can adjust the position by operating user interface 221. Seat adjustment system 210 may include a memory function configured to store the current adjustment settings when activated. The seat adjustment system 210 may include or interface with a seat sensor 214. The seat sensor 214 may be configured to measure the position or setting of the seat. For example, the seat sensor 214 may be configured to measure the backrest angle (e.g., relative to the bottom of the seat), seat height, and / or seat distance from a reference point. The seat adjustment system 210 may include or interface with a seat actuator 216. The seat actuator 216 may be configured to change the position of the seat. For example, the seat actuator 216 may be configured to adjust the fore / aft position, seat height, backrest angle, and lumbar support of the associated seat. The seat adjustment system 210 may include a controller to manage and coordinate the movement of the seat.

[0029] Vehicle 200 may include a mirror adjustment system 220. The mirror adjustment system 220 may be configured to position a mirror within the vehicle. The mirror may include a rearview mirror mounted on the windshield and side mirrors mounted on each side of the vehicle. The mirror adjustment system 220 may include a user interface 222 configured to allow a driver to adjust the mirror position. The user interface 222 may include a switch or button for activating movement of the mirror. In some configurations, the user interface 222 may be via a touchscreen display (e.g., 104) displaying associated menu items for positioning the mirror. The mirror adjustment system 220 may include a memory function configured to store current adjustment settings when activated. The mirror adjustment system 220 may include or be connected to one or more mirror actuators 226, such as an electric motor, to move the mirror to a desired position. The mirror adjustment system 220 may include or be connected to one or more mirror sensors 224 configured to measure the position of the mirror.

[0030] Vehicle 200 may include a pedal adjustment system 230. The pedal adjustment system 230 may be configured to position operating pedals, such as the brake pedal and accelerator pedal, to desired positions. The pedal adjustment system 230 may include a user interface 232 configured to allow the driver to change the position of the pedals. The user interface 232 may include a switch or button for activating the pedal adjustment system 230. In some configurations, the user interface 212 may be via a touchscreen display (e.g., 104) displaying associated menu items for pedal positioning. The pedal adjustment system 230 may include a memory function configured to store current adjustment settings when activated. The pedal adjustment system 230 may include or interface with one or more pedal actuators 236 configured to change the position of a pedal (e.g., an electric motor). The pedal adjustment system 230 may include or interface with a pedal sensor 234 configured to measure the position of the pedal.

[0031] Vehicle 200 may include a steering wheel adjustment system 240 configured to adjust the position of the steering wheel relative to the driver. For example, the steering wheel adjustment system 240 may be configured to adjust the tilt angle and distance from the driver. The steering wheel adjustment system 240 may include a user interface 242 configured to allow the driver to adjust the position of the steering wheel. In some configurations, the user interface 242 may be via a touchscreen display (e.g., 104) displaying associated menu items for positioning the steering wheel. The user interface 242 may include switches and buttons for activating the system. The steering wheel adjustment system 240 may include a memory function configured to store the current adjustment settings when activated. The steering wheel adjustment system 240 may include or be connected to one or more steering wheel actuators 246 configured to change the position of the steering wheel. The steering wheel adjustment system 240 may include one or more steering wheel position sensors 244 configured to measure the position of the steering wheel.

[0032] Vehicle 200 may include a rear window locking system 250 configured to restrict the opening and closing of the rear window from a rear seated position. The rear window locking system 250 may include a user interface 252. The user interface 252 may include a switch or button for activating the feature. In some configurations, the user interface 212 may be via a touchscreen display (e.g., 104) displaying associated menu items for activating the rear window locking feature. The rear window locking system 250 may include or be connected to one or more actuators 256 configured to restrict controls for the rear window. The rear window locking system 250 may include or be connected to one or more rear window locking sensors 254 configured to sense the state of the rear window locking feature. The rear window locking system 250 may include a memory function configured to store current adjustment settings when activated.

[0033] Vehicle 200 may include a child safety lock system 260 configured such that, when activated, a rear-seat occupant cannot open the rear door from inside the vehicle. The child safety lock system 260 may include a user interface 262. The user interface 262 may include a switch or button for activating the child safety lock feature. In some configurations, the user interface 212 may be via a touchscreen display (e.g., 104) displaying associated menu items for activating the child safety lock feature. The child safety lock system 260 may include or interface with one or more actuators configured to prevent opening the rear door from inside the vehicle. The child safety lock system 260 may include or interface with one or more sensors 264 configured to sense the state of the child safety lock feature. The child safety lock system 260 may include a memory function configured to store current adjustment settings when activated.

[0034] Vehicle 200 may include a cabin climate control system 270 configured to heat or cool the cabin of vehicle 200. The cabin climate control system 270 may include a user interface 272 configured to allow the driver to control system settings. The cabin climate control system 270 may include multi-zone climate settings that can adjust climate settings in specific zones of the vehicle. For example, a driver-side zone and a passenger-side zone may be defined. Settings may include target temperature, preferred fan speed, and preferred airflow path (e.g., leg rests, panel, defrost, or a combination thereof). Multi-zone climate settings can allow different temperatures and / or airflow in each zone. Some vehicles may include climate control adjustments for rear-seat passengers. In some configurations, the user interface 212 may be via a touchscreen display (e.g., 104) displaying associated menu items for operating the climate control system 270. The climate control system 270 may include or be associated with one or more climate control actuators 276 configured to adjust the settings of the climate control system 270. The climate control system 270 may include or be connected to one or more climate control sensors 274, which are configured to sense the state of the climate control system and the position of the climate control actuator 276.

[0035] Vehicle 200 may also include an entertainment system 280. The entertainment system may include a radio (e.g., FM, AM, satellite) configured to receive broadcast programs. Entertainment system 280 may include a user interface 282 configured to operate the entertainment system 280. In some configurations, user interface 212 may be located via a touchscreen display (e.g., 104) displaying associated menu items for operating the entertainment system 280. Entertainment system 280 may be configured to store preset channels. For example, a driver may save favorite channels in memory for easy access. Additionally, entertainment system 280 may be configured to store speaker and sound settings. For example, a driver may configure left / right and front / rear speaker balance and frequency response via equalizer functions (e.g., treble and bass settings).

[0036] Each of the above systems may include a corresponding controller configured to manage and coordinate assigned functions. The controller may be connected to a vehicle network to transmit signals between controllers. The controllers may coordinate to achieve the described functions. For example, CPU 103 may interface with display 104. CPU 103 may implement a menu structure applicable to all controllers. CPU 103 may communicate menu selections to the controllers. Additionally, CPU 103 may receive status information from each controller for display. Each of the systems may have corresponding control or target parameters. For example, parameters may define the target position or mode of the associated system.

[0037] CPU 103 can also be configured to store vehicle configuration data in non-volatile memory for later retrieval. The vehicle configuration data may include data from each of the previously described systems. The vehicle configuration data may include data relating to the seat adjustment system, mirror adjustment system, pedal adjustment system, steering adjustment system, rear window locking system, cabin climate system, and child safety lock system. The vehicle configuration data may include one or more seating profiles. Seating profiles may include parameters associated with each seating position. For example, the vehicle configuration data may include a driver's seat profile, a passenger seat profile, and a rear seat profile.

[0038] The driver's seat profile may include parameter settings (which may be referred to as seating parameters) for the seat adjustment system 210, mirror adjustment system 220, pedal adjustment system 230, steering adjustment system 240, rear window locking system 250, child safety lock system 260, climate control system 270, and entertainment system 280. Parameters from the seat adjustment system 210 may include driver's seat position parameters, including the fore / rear position associated with the driver's side seat, seat height, lumbar support setting, backrest angle, and headrest position. Parameters forming the mirror adjustment system 220 may include the positions of the rearview and side mirrors, described by horizontal and vertical angles relative to predetermined positions in each mirror. Parameters from the pedal adjustment system 230 may include the positions of the brake pedal, accelerator pedal, and clutch pedal. Parameters from the steering wheel adjustment system 240 may include the steering wheel tilt angle and reach. Parameters from the rear window locking system may include desired settings for rear window locking features. Parameters from the child safety lock system may include desired settings for child safety lock features. Parameters from the climate control system 270 may include temperature, fan speed, and airflow configuration associated with the driver's side. Parameters from the entertainment system 280 may include preset channels, speaker settings, volume settings, and equalizer settings. It should be noted that other parameters may also be included.

[0039] The passenger seat profile may include parameter settings for the seat adjustment system 210 and the climate control system 270. Parameters from the seat adjustment system 210 may include passenger seat position parameters, including the fore / aft position associated with the passenger-side seat, seat height, lumbar support setting, backrest angle, and headrest position. Parameters from the climate control system 270 may include temperature, fan speed, and airflow configuration associated with the passenger side. It should be noted that other parameters may also be included.

[0040] The rear seat profile may include parameter settings for the seat adjustment system 210, rear window locking system 250, child safety lock system 260, and climate control system 270. Parameters from the seat adjustment system 210 may include passenger seat position parameters, including fore / rear position associated with the rear seat, seat height, lumbar support setting, backrest angle, and headrest position. Parameters from the climate control system 270 may include temperature, fan speed, and airflow configuration associated with the rear seating position. Parameters from the rear window locking system may include desired settings for rear window locking features. Parameters from the child safety lock system may include desired settings for child safety lock features. For example, rear window locking parameters and child safety lock system parameters may override parameters in the driver seating profile. This may be ideal when an adult, rather than a child, is seated in the rear seat. It should be noted that other parameters may also be included.

[0041] The roaming device 153 can be configured to communicate with the vehicle 200. The roaming device 153 may include a Bluetooth transceiver. For example, the roaming device may communicate with the vehicle 200 via Bluetooth transceiver 115. The CPU 103 may transmit vehicle configuration data to the roaming device 153 for storage in the non-volatile memory of the roaming device 153. The information may also include vehicle identifiers, such as the model and model year of the vehicle 200. The roaming device 153 can be programmed with an application that manages the communication and storage / retrieval of vehicle configuration data.

[0042] The roaming device 153 can store seating profiles for each seating position of the roaming device owner in the vehicle compartment. For example, the roaming device owner may have preferred settings when sitting in the driver's seat and when sitting in the passenger seat. The driver's side position may include additional settings not available in other seating positions (e.g., mirror settings, pedal settings). In some cases, the roaming device 153 can be programmed to apply any applicable driver's side settings to the passenger side when the roaming device owner is sitting on the passenger side. For example, a person may have a preferred climate system temperature setting, which is stored as part of the vehicle configuration data regarding the driver's seat position that can be applied to the passenger seat position. The driver can press a virtual button on the display 104, which initiates the retrieval and application of current parameters for each of the aforementioned systems. The driver can press another virtual button on the display 104 to transmit the current set of parameters to the connected roaming device 153. In some configurations, multiple virtual buttons may be present to select parameter storage associated only with the driver's seat profile, passenger seat profile, or rear seat profile. In this way, the profile stored in the roaming device 153 can include a preferred profile of the device owner in any seated position in the vehicle 200.

[0043] The stored vehicle configuration data may include seating profiles for several different vehicles or vehicle models. For example, the owner of roaming device 153 may own or frequently drive different vehicles. Roaming device 153 may be configured to store vehicle configuration data associated with each vehicle. Vehicle 200 may be configured to transmit a vehicle identifier to roaming device 153 to identify the current vehicle. The vehicle identifier may be compared with a vehicle identifier associated with the vehicle configuration data. The vehicle identifier may include vehicle-specific information (e.g., vehicle identification number) and / or more general model information (e.g., F150, Fusion, Focus). Upon receiving a vehicle identifier from vehicle 200, an application running on roaming device 153 may retrieve the corresponding vehicle configuration data.

[0044] The stored information may include passenger and driver-side settings related to the roaming device owner. This allows for adjustments to the preferred configuration of any seating position in the vehicle. For each vehicle with a stored configuration, one of the seating positions can be marked as the default position for the roaming device owner. For example, the driver position can be marked as the default position for a vehicle typically driven by the roaming device owner. The passenger position can be marked as the default position for a vehicle typically ridden as a passenger by the roaming device owner. This allows for rapid configuration within vehicles already configured by the roaming device owner. For example, upon verifying that the received vehicle identifier matches a stored profile with a default seating position, the roaming device 153 can immediately send the default seating position parameters to vehicle 200.

[0045] In one possible use case, a driver approaching vehicle 200 may carry a roaming device 153. Communication can be established between vehicle 200 and roaming device 153. This communication can be established when the driver approaches vehicle 200. After communication is established, vehicle 200 can transmit identification information to roaming device 153. Roaming device 153 can search for corresponding vehicle configuration data and transmit the vehicle configuration data to vehicle 200. It can receive vehicle configuration data and transmit it to various systems. The system can then adjust the corresponding settings to match parameters according to the configuration data. In the case of a single roaming device, the system can apply only the driver's seat configuration. The system can also apply each seating configuration based on data supplied by a single roaming device.

[0046] Other use cases may involve multiple vehicle occupants with roaming devices. The vehicle communication system can be adapted to communicate with several roaming devices. For example, a second roaming device 202 can communicate with the vehicle via a Bluetooth transceiver 115. The second roaming device 202 may belong to another person. The second roaming device 202 can store a set of vehicle configuration data associated with the corresponding device owner. The stored vehicle configuration data may differ from the vehicle configuration data of the first roaming device 153. Furthermore, the vehicle configuration data stored in the second roaming device 202 may come from different vehicle models. It should be noted that although only two roaming devices have been discussed, the discussion is intended to apply to more than two roaming devices.

[0047] In some configurations, each of the roaming devices communicating with vehicle 200 can transmit a device identifier. For example, the device identifier could be the name of the device owner. The device identifier can be assigned by the device owner via an application running on the roaming device. In response to receiving a device identifier, CPU 103 can display the device identifier on display 104. When multiple device identifiers are received, display 104 can list each device identifier. CPU 103 can be programmed to allow each of the device identifiers to be assigned to a seating position in vehicle 200. For example, a device identifier can be assigned to a seating position by operating touchscreen display 104. When assigning a seating position, corresponding vehicle configuration data can be requested from the corresponding roaming device. In this way, each occupant of vehicle 200 can have a roaming device that stores vehicle configuration data for each seating position. Once the device owner's seating position is known, the corresponding seating profile can be passed to vehicle 200. Various vehicle systems can be commanded to apply parameters for each seating position. In this way, each device owner has a preferred seating configuration stored in their own personal roaming device. In practice, device owners can enter any compatible vehicle, be seated in any position, and have their personal seating preferences identified.

[0048] In other configurations, the roaming device 153 can be programmed to display a message indicating that communication with the vehicle 200 has been established. A menu of seating positions can be displayed for the device holder to select. For example, a list of items such as "driver's seat," "passenger seat," and "rear seat" can be displayed. The device holder can select their desired seating position. When selecting a seating position, the roaming device 153 can be programmed to transmit the corresponding seating profile to the vehicle 200. The roaming device 153 can also provide a seating position identifier to the seating profile to identify the seating position. The CPU 103 can then command various systems to apply the received parameters. In this way, the parameters for each seating position can be set according to the preferences of each seat occupant.

[0049] In some configurations, the vehicle communication system can be configured to automatically detect the location of each roaming device within the vehicle. The system can be configured to detect from which side and which door the roaming device entered the vehicle. For example, CPU 103 can be configured to receive signal strength from each roaming device. Signal strength indicates the magnitude of the communication signal received from the vehicle transceiver. The location of the roaming device relative to the transceiver can be determined by analyzing the signal strength. In some configurations, multiple Bluetooth transceivers can be located in various locations (e.g., each door) and can be used to monitor and compare the signal strength values ​​received from the roaming devices. In other instances, NFC transceivers can be located near each seating position. NFC can establish communication when the roaming device is within a predetermined distance of the transceiver. To facilitate the NFC protocol, roaming device holders can be positioned close to each seating position. A person entering the vehicle can place their roaming device in or near the corresponding holder and establish communication.

[0050] In some configurations, GPS data from the roaming devices and the vehicle can be used to determine the approach direction for each of the roaming devices. Additionally, information from the vehicle doors can be used to determine the entry point for each of the roaming devices. For example, sensors can detect when a door is open or closed.

[0051] The roaming device 153 can be programmed to adjust seating profiles to deliver customized seating profiles. For example, a vehicle owner may have a preferred seating profile for their owned vehicle. This setting can be achieved by adjusting various parameters over time. Vehicle configuration data for that vehicle can be stored in the vehicle owner's roaming device. A vehicle owner may rent a vehicle different from their owned vehicle. For example, the owned vehicle may be a small car, and the rented vehicle may be a large truck. Therefore, the stored vehicle configuration data may not perfectly correspond to the settings for the rented vehicle. The roaming device 153 can be configured to rescale the stored vehicle configuration data to generate a similar seating profile for the rented vehicle.

[0052] Vehicle configuration data can be standardized to obtain certain relative distances. In this configuration, standardized configuration parameters can be transmitted to the vehicle. The vehicle can then adjust the corresponding parameter settings based on vehicle measurements and calibration to achieve the standardized position. By standardizing the position, it becomes possible to provide a configuration to any vehicle. For example, occupants can switch between small economy cars and large trucks with preferred settings without having to readjust and store parameters for each type of vehicle.

[0053] Standardized vehicle configuration data may include various measurements corresponding to preferred driving or seating positions. Driver-side configuration data may include parameters indicating the seat position relative to the pedals and steering wheel. For example, seat-to-steering-wheel parameters may be indicated by the distance between the seat bottom (e.g., top / front portion) and the steering wheel (e.g., bottommost position) and the distance between the seat back and the steering wheel. Parameters may also include seat-to-pedal parameters. Seat-to-pedal parameters may include the horizontal and vertical distances between the seat bottom (e.g., top / front portion) and the pedals. Driver-side parameters may also include seat-to-mirror parameters. Parameters may include the distance between the seat bottom and the bottommost portion of the side window or windshield. Parameters may include the angle between the seat back and the seat bottom (e.g., recline angle). Seat-to-mirror parameters may include angles relative to the seat position and angles relative to the vehicle height. Other parameters may include the steering wheel angle relative to the seat or dashboard. Other parameters may include the distance between the seat bottom (e.g., top portion) and the floor, and the distance between the seat bottom (e.g., front portion) and the dashboard / front seat. Parameters may include the distance between the seat bottom and the armrest (e.g., on the center console and / or door). A subset of these parameters can be applied to passenger seating positions.

[0054] Vehicles and / or roaming devices can convert between standardized parameters and vehicle-specific parameters. Parameter data can be stored as standardized data and / or vehicle-specific data. Vehicle systems can be calibrated to allow adjustments to associated components to achieve desired parameter settings. For example, the system can use corresponding sensor signals to determine the position or state of associated components (e.g., seat position, pedal position). Each vehicle type can include vehicle-specific parameters related to standardized data. Each vehicle can have a predefined range of motion for each of its components. For example, seat height can be adjusted between a minimum and a maximum distance from the floor. Other vehicle-specific data can include the height of windows and armrests from the vehicle floor. Vehicles and / or roaming devices can access the cloud or external networks to download vehicle-specific dimensions for each vehicle for standardized operation.

[0055] Each vehicle can store or access vehicle dimensions and system dimensions. Once the desired parameters are known, the seats, mirrors, steering wheel, and pedals can be adjusted to standardized positions. The roaming device and / or vehicle can store standardized parameter values ​​and / or actual parameter values. The roaming device and / or vehicle can be configured to rescale parameters for any vehicle for which vehicle-specific data is available.

[0056] Figure 3A flowchart illustrating a set of possible operations that can be performed by the vehicle control system is shown. At operation 302, CPU 103 can establish communication with multiple roaming devices. For example, CPU 103 can transmit vehicle identification information, and the roaming device can respond with an indication that a seating profile is available. At operation 304, CPU 103 can identify the seating position of each of the roaming devices with which communication has been established. The identification of the seating position can be as described previously herein. CPU 103 can request a specific seating profile from each of the roaming devices based on the identified seating position. At operation 306, CPU 103 can receive the corresponding seating profile from each of the roaming devices. At operation 308, CPU 103 can check to determine whether the received seating profile is vehicle compatible. For example, the vehicle type can be compared with the vehicle type associated with the received seating profile. If the received seating profile is vehicle compatible, operation 310 can be performed to apply the seating profile. If the received seating profile is incompatible with the vehicle, operation 312 can be performed to scale the seating profile as described earlier in this document. At operation 314, the scaled seating profile can be applied.

[0057] At operation 316, a default seating profile can be applied to any unassigned seating location. An unassigned seating location can be one not associated with a roaming device profile. In this case, existing settings can be retained. This process can be repeated until all seating locations have been assigned and configured.

[0058] The described system offers several advantages over existing systems. Vehicle owners can store seating configurations for every seat in the vehicle. These configurations can also be retained and applied to other vehicles. Customer satisfaction is improved because customers have a consistent experience across a range of vehicles. Furthermore, customers experience the same level of comfort in any seat in any vehicle.

[0059] The processes, methods, or algorithms disclosed herein may be provided / implemented by a processing device, controller, or computer, which may include any existing programmable electronic control unit or dedicated electronic control unit. Similarly, the processes, methods, or algorithms may be stored as data and instructions executable in many forms by a controller or computer, including but not limited to information permanently stored on non-writable storage media such as ROM devices, and information modifiable stored on writable storage media such as floppy disks, magnetic tapes, CDs, RAM devices, and other magnetic and optical media. The processes, methods, or algorithms may also be implemented in a software executable object. Alternatively, the processes, methods, or algorithms may be embodied, in whole or in part, using suitable hardware components such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), state machines, controllers, or other hardware components or devices, or a combination of hardware, software, and firmware components.

[0060] While exemplary embodiments have been described above, they are not intended to describe all possible forms covered by the claims. Rather, the wording used in the specification is descriptive rather than limiting, and it should be understood that various changes may be made without departing from the spirit and scope of this disclosure. As previously described, features of various embodiments may be combined to form other embodiments of the invention that may not be explicitly described or illustrated. Although various embodiments may be described as providing advantages or superiority over other embodiments or prior art implementations in terms of one or more desired characteristics, those skilled in the art will recognize that one or more features or characteristics may be compromised to achieve desired overall system properties, depending on the specific application and implementation. These properties may include, but are not limited to, cost, strength, durability, lifecycle cost, marketability, appearance, packaging, size, maintainability, weight, manufacturability, ease of assembly, etc. Therefore, embodiments described as inferior to other embodiments or prior art implementations in terms of one or more characteristics are also within the scope of this disclosure and may be ideal for a particular application.

[0061] According to the present invention, a vehicle having a controller is provided, the controller being programmed to: identify a seating position in the vehicle corresponding to each of a plurality of roaming devices communicating with the vehicle; receive at least one seating profile from each of the roaming devices; and adjust seating parameters for each of the seating positions according to the seating profile received from the corresponding roaming device.

[0062] According to an embodiment, the controller is also programmed to: output an identifier associated with each of the roaming devices to a display to request input related to a seating position; and receive a response indicating a seating position corresponding to each of the roaming devices.

[0063] According to an embodiment, the controller is also programmed to: detect the position of each of the roaming devices within the vehicle; and identify the seating position corresponding to each of the roaming devices based on the position.

[0064] According to an embodiment, at least one seating configuration includes a preferred rear child safety lock setting.

[0065] According to an embodiment, at least one seating configuration includes a preferred rear window lock setting.

[0066] According to an embodiment, the controller is also programmed to: adjust seating parameters according to a seating profile received from the roaming device that corresponds to the driver's seating position, in response to identifying a seating position that does not correspond to any of the roaming devices.

[0067] According to an embodiment, the roaming device is configured to store seating profiles for each seating position in the vehicle.

[0068] According to an embodiment, the controller is also programmed to receive the seating position from the corresponding roaming device.

[0069] According to the embodiment, the seating position is different from the driver's seat position.

[0070] According to an embodiment, the controller is also programmed to rescale at least one seating profile in response to a vehicle model that is different from the vehicle model associated with at least one seating profile.

[0071] According to the present invention, a vehicle having a controller is provided, the controller being programmed to: receive from a roaming device a plurality of seating profiles corresponding to each seating position in the vehicle and corresponding to a vehicle model; and, in response to identifying a seating position in the vehicle associated with the roaming device, adjust seating parameters relating to the seating position associated with the roaming device according to the corresponding seating profile.

[0072] According to an embodiment, the seating configuration includes a preferred rear child safety door lock setting.

[0073] According to an embodiment, the seating configuration includes a preferred rear window lock setting.

[0074] According to an embodiment, the controller is also programmed to: in response to receiving a seating profile that does not correspond to the vehicle model, rescale the seating profile so that the distances between the seat and the steering wheel and between the seat and the pedals are the same as the distances associated with the seating profile.

[0075] According to an embodiment, the controller is also programmed to identify the seating position based on the preferred seating position received from the corresponding roaming device in response to the vehicle identifier being the same as the received vehicle identifier.

[0076] According to the present invention, a method includes: identifying a seating position corresponding to each of a plurality of roaming devices communicating with the controller; receiving a seating profile from each of the roaming devices by the controller; and adjusting seating parameters for each seating position by the controller based on the seating profile received from the corresponding roaming device.

[0077] According to an embodiment, a method includes: outputting a list of identifiers for each of the roaming devices to a vehicle touchscreen display; and receiving a response from the vehicle touchscreen display indicating the seating position for each of the roaming devices.

[0078] According to an embodiment, a method includes identifying the seating position of each of the roaming devices by a controller based on the strength of a signal received from each of the roaming devices.

[0079] According to an embodiment, a method includes rescaling a seating profile by means of a controller in response to a vehicle identifier associated with the controller being different from a vehicle identifier associated with a seating profile.

[0080] According to an embodiment, a method includes receiving a seating position from at least one of the roaming devices via a controller.

Claims

1. A vehicle, the vehicle comprising: A controller configured to: output an identifier associated with each of a plurality of roaming devices communicating with the vehicle to a display to request input relating to a seating position in the vehicle corresponding to each of the roaming devices; receive via the display a response indicating the seating position corresponding to each of the roaming devices; identify the seating position; receive at least one seating profile from each of the roaming devices; and adjust seating parameters for each of the seating positions based on the seating profile received from the corresponding roaming device.

2. The vehicle as claimed in claim 1, wherein, The controller is also configured to: detect the position of each of the roaming devices within the vehicle; and identify the seating position corresponding to each of the roaming devices based on the position.

3. The vehicle as claimed in claim 1, wherein, The at least one seating configuration includes a rear child safety lock setting.

4. The vehicle as claimed in claim 1, wherein, The at least one seating configuration file includes a rear window lock setting.

5. The vehicle as claimed in claim 1, wherein, The controller is also configured to adjust the seating parameters according to the seating profile received from the roaming device corresponding to the driver's seating position, in response to identifying a seating position that does not correspond to any of the roaming devices.

6. The vehicle as claimed in claim 1, wherein, The roaming device is configured to store seating profiles for each seating position in the vehicle.

7. The vehicle as claimed in claim 1, wherein, The controller is also configured to receive the seating position from the corresponding roaming device.

8. The vehicle as claimed in claim 1, wherein, The seating position is different from the driver's seat position.

9. The vehicle as claimed in claim 1, wherein, The controller is also configured to rescale the at least one seating profile in response to a vehicle model that is different from the vehicle model associated with the at least one seating profile.

10. The vehicle as claimed in claim 1, wherein, The at least one seating configuration includes the distance between the seat and the steering wheel, and the distance between the seat and the pedals.

11. The vehicle as claimed in claim 1, wherein, The controller is also configured to identify the seating position based on the seating position received from the corresponding roaming device in response to the vehicle identifier being the same as the received vehicle identifier.

12. A method for adjusting seating parameters, the method comprising: The vehicle's controller performs the following operations: outputs an identifier associated with each of the plurality of roaming devices communicating with the vehicle to the vehicle's touchscreen display to request input related to the seating position in the vehicle corresponding to each of the roaming devices; Receive a response from the vehicle touchscreen display indicating a seating position for each of the roaming devices; identify the seating position; receive a seating profile from each of the roaming devices; and adjust seating parameters for each seating position based on the seating profile received from the corresponding roaming device.

13. The method of claim 12, further comprising: The controller identifies the seating position for each of the roaming devices based on the strength of the signal received from each of the roaming devices.

14. The method of claim 12, further comprising: The seating profile is rescaled via the controller in response to a vehicle identifier associated with the controller being different from a vehicle identifier associated with the seating profile.

15. The method of claim 12, further comprising: The controller receives the seating position from at least one of the roaming devices.

16. The method of claim 12, wherein, The seating configuration file includes one of the following: rear child safety door lock settings, rear window lock settings, distances between the seat and the steering wheel, and distances between the seat and the pedals.

17. The method of claim 12, wherein, The method further includes: in response to the vehicle identifier being the same as the received vehicle identifier, identifying the seating position based on the seating position received from the corresponding roaming device.

Images