Patent Application
20130191321
The illustrative embodiments relate to methods and apparatuses for providing charging state alerts.
While battery electric vehicles (BEVs) and hybrid electric vehicles (HEVs) have increased in popularity over the years, the length of the time to charge these vehicles can still produce situations of anxiety for owners. For example, a plug-in BEV or HEV that an owner could plug into an outlet in their garage may take over an hour to charge appropriately for the next days travel, as compared to, for example, a few minutes worth of a stop at a local gas station for refueling a gasoline powered vehicle.
Typically, these time constraints will not cause a problem, and may even be more convenient, since they can apply while a user is comfortably within a house, or even sleeping in bed. While the charging can usually occur during such times, the fact that the user is not actually present at the vehicle, to confirm that charge is being added, can result in several potential problems.
In one instance, incidental contact with a power cord can cause a vehicle to become unplugged. This could be caused by, for example, a pet or another person in the garage. Since the contact may be overlooked or unknown, the owner of the vehicle may not discover that the vehicle came unplugged until attempting to start the vehicle the next day.
In another instance, a power outage may result in a no-charge state. If the outage occurred while the owner was awake, at least the owner would have some indication that the vehicle may not be charging (based on the fact that the house has no power). People, however, often become flustered during power outages, and it may not occur to an owner until much later, or the next morning, that the power outage also resulted in a vehicle with no charge.
Additionally or alternatively, the power outage could occur while an owner was asleep. In such a case, the owner may not know about the power outage at all, until awakening to an uncharged vehicle.
In a first illustrative embodiment, a computer implemented method includes determining whether a time of day corresponds to a charging window, responsive to a determination that a vehicle is in a non-charging state. The illustrative method also includes retrieving a start time and charge requirement for an upcoming journey. The method further includes determining if sufficient time remains to charge a vehicle to the charge requirement, responsive to a determination that the time of day corresponds to the charging window. Also, the method includes alerting a user to the non-charging state, responsive to a determination that insufficient time remains to charge the vehicle to the charge requirement.
In a second illustrative embodiment, a machine readable storage medium stores instructions which, when executed by a processor, cause the processor to perform the method including determining whether a time of day corresponds to a charging window, responsive to a determination that a vehicle is in a non-charging state. The illustrative method also includes retrieving a start time and charge requirement for an upcoming journey. Further, the illustrative method includes determining if sufficient time remains to charge a vehicle to the charge requirement, responsive to a determination that the time of day corresponds to the charging window. The illustrative method also includes alerting a user to the non-charging state, responsive to a determination that insufficient time remains to charge the vehicle to the charge requirement.
In a third illustrative embodiment, a system includes a processor, in communication with a vehicle network, a local storage, in communication with the vehicle network, a vehicle power source, in communication with the vehicle network, and a transceiver, in communication with at least the processor. In this illustrative example, the processor is configured to determine whether a time of day corresponds to a charging window, responsive to a determination that a vehicle is in a non-charging state, based at least in part on information retrieved from the vehicle network. The processor is further configured to retrieve a start time and charge requirement for an upcoming journey from the local storage, and determine if sufficient time remains to charge a vehicle to the charge requirement, responsive to a determination that the time of day corresponds to the charging window, based at least in part on a difference between a current time and the start time, and at least in part on an observed rate of charging. Also, the processor is configured to alert a user to the non-charging state, responsive to a determination that insufficient time remains to charge the vehicle to the charge requirement, utilizing at least the transceiver to send a message for transmission to the user.
As required, detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention that may be embodied in various and alternative forms. The figures are not necessarily to scale; some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the present invention.
In the illustrative embodiment 1 shown in
The processor is also provided with a number of different inputs allowing the user to interface with the processor. In this illustrative embodiment, a microphone 29, an auxiliary input 25 (for input 33), a USB input 23, a GPS input 24 and a BLUETOOTH input 15 are all provided. An input selector 51 is also provided, to allow a user to swap between various inputs. Input to both the microphone and the auxiliary connector is converted from analog to digital by a converter 27 before being passed to the processor. Although not shown, numerous of the vehicle components and auxiliary components in communication with the VCS may use a vehicle network (such as, but not limited to, a CAN bus) to pass data to and from the VCS (or components thereof).
Outputs to the system can include, but are not limited to, a visual display 4 and a speaker 13 or stereo system output. The speaker is connected to an amplifier 11 and receives its signal from the processor 3 through a digital-to-analog converter 9. Output can also be made to a remote BLUETOOTH device such as PND 54 or a USB device such as vehicle navigation device 60 along the bi-directional data streams shown at 19 and 21 respectively.
In one illustrative embodiment, the system 1 uses the BLUETOOTH transceiver 15 to communicate 17 with a user's nomadic device 53 (e.g., cell phone, smart phone, PDA, or any other device having wireless remote network connectivity). The nomadic device can then be used to communicate 59 with a network 61 outside the vehicle 31 through, for example, communication 55 with a cellular tower 57. In some embodiments, tower 57 may be a WiFi access point.
Exemplary communication between the nomadic device and the BLUETOOTH transceiver is represented by signal 14.
Pairing a nomadic device 53 and the BLUETOOTH transceiver 15 can be instructed through a button 52 or similar input. Accordingly, the CPU is instructed that the onboard BLUETOOTH transceiver will be paired with a BLUETOOTH transceiver in a nomadic device.
Data may be communicated between CPU 3 and network 61 utilizing, for example, a data-plan, data over voice, or DTMF tones associated with nomadic device 53. Alternatively, it may be desirable to include an onboard modem 63 having antenna 18 in order to communicate 16 data between CPU 3 and network 61 over the voice band. The nomadic device 53 can then be used to communicate 59 with a network 61 outside the vehicle 31 through, for example, communication 55 with a cellular tower 57. In some embodiments, the modem 63 may establish communication 20 with the tower 57 for communicating with network 61. As a non-limiting example, modem 63 may be a USB cellular modem and communication 20 may be cellular communication.
In one illustrative embodiment, the processor is provided with an operating system including an API to communicate with modem application software. The modem application software may access an embedded module or firmware on the BLUETOOTH transceiver to complete wireless communication with a remote BLUETOOTH transceiver (such as that found in a nomadic device). Bluetooth is a subset of the IEEE 802 PAN (personal area network) protocols. IEEE 802 LAN (local area network) protocols include WiFi and have considerable cross-functionality with IEEE 802 PAN. Both are suitable for wireless communication within a vehicle. Another communication means that can be used in this realm is free-space optical communication (such as IrDA) and non-standardized consumer IR protocols.
In another embodiment, nomadic device 53 includes a modem for voice band or broadband data communication. In the data-over-voice embodiment, a technique known as frequency division multiplexing may be implemented when the owner of the nomadic device can talk over the device while data is being transferred. At other times, when the owner is not using the device, the data transfer can use the whole bandwidth (300 Hz to 3.4 kHz in one example). While frequency division multiplexing may be common for analog cellular communication between the vehicle and the internet, and is still used, it has been largely replaced by hybrids of Code Domain Multiple Access (CDMA), Time Domain Multiple Access (TDMA), Space-Domain Multiple Access (SDMA) for digital cellular communication. These are all ITU IMT-2000 (3G) compliant standards and offer data rates up to 2 mbs for stationary or walking users and 385 kbs for users in a moving vehicle. 3G standards are now being replaced by IMT-Advanced (4G) which offers 100 mbs for users in a vehicle and 1 gbs for stationary users. If the user has a data-plan associated with the nomadic device, it is possible that the data-plan allows for broad-band transmission and the system could use a much wider bandwidth (speeding up data transfer). In still another embodiment, nomadic device 53 is replaced with a cellular communication device (not shown) that is installed to vehicle 31. In yet another embodiment, the ND 53 may be a wireless local area network (LAN) device capable of communication over, for example (and without limitation), an 802.11g network (i.e., WiFi) or a WiMax network.
In one embodiment, incoming data can be passed through the nomadic device via a data-over-voice or data-plan, through the onboard BLUETOOTH transceiver and into the vehicle's internal processor 3. In the case of certain temporary data, for example, the data can be stored on the HDD or other storage media 7 until such time as the data is no longer needed.
Additional sources that may interface with the vehicle include a personal navigation device 54, having, for example, a USB connection 56 and/or an antenna 58, a vehicle navigation device 60 having a USB 62 or other connection, an onboard GPS device 24, or remote navigation system (not shown) having connectivity to network 61. USB is one of a class of serial networking protocols. IEEE 1394 (firewire), EIA (Electronics Industry Association) serial protocols, IEEE 1284 (Centronics Port), S/PDIF (Sony/Philips Digital Interconnect Format) and USB-IF (USB Implementers Forum) form the backbone of the device-device serial standards. Most of the protocols can be implemented for either electrical or optical communication.
Further, the CPU could be in communication with a variety of other auxiliary devices 65. These devices can be connected through a wireless 67 or wired 69 connection. Auxiliary device 65 may include, but are not limited to, personal media players, wireless health devices, portable computers, and the like.
Also, or alternatively, the CPU could be connected to a vehicle based wireless router 73, using for example a WiFi 71 transceiver. This could allow the CPU to connect to remote networks in range of the local router 73.
In addition to having exemplary processes executed by a vehicle computing system located in a vehicle, in certain embodiments, the exemplary processes may be executed by a computing system in communication with a vehicle computing system. Such a system may include, but is not limited to, a wireless device (e.g., and without limitation, a mobile phone) or a remote computing system (e.g., and without limitation, a server) connected through the wireless device. Collectively, such systems may be referred to as vehicle associated computing systems (VACS). In certain embodiments particular components of the VACS may perform particular portions of a process depending on the particular implementation of the system. By way of example and not limitation, if a process has a step of sending or receiving information with a paired wireless device, then it is likely that the wireless device is not performing the process, since the wireless device would not “send and receive” information with itself. One of ordinary skill in the art will understand when it is inappropriate to apply a particular VACS to a given solution. In all solutions, it is contemplated that at least the vehicle computing system (VCS) located within the vehicle itself is capable of performing the exemplary processes.
Although modern electric vehicles may offer the convenience of home-charging, while a user is away from a vehicle, potential problems with a power connection (e.g., without limitation, unplugging, outlet failure, power outage) can leave an owner unaware that a vehicle is not actually charging. The illustrative embodiments present some exemplary aspects of the invention which can aid in notifying a user when a power connection has been interrupted.
While all embodiments are capable of near-constant or constant notification, repeated and endless communication may annoy a user. Accordingly, it is understood that repetitive warnings can be truncated after a certain number of warnings (including a single warning) and that brief interruptions in the power supply can be accounted for in all cases. While optional, these considerations may prevent users from being overwhelmed with warnings, and may also allow brief power interruptions to go unwarned, as they may generally tend not to greatly impact the overall charge state.
If the vehicle charging ceases, the process may check a remaining amount of time needed to charge 203. In at least one implementation, the process may have a known vehicle start time (i.e., the time the next day, or later the same day, the vehicle is needed) and a known needed charge level. This information can be fully or partially input by a user, or it can be fully or partially determined based on observations of a user's travel habits.
For example, in one instance, a user may note that on weekdays the vehicle is needed at approximately 7 AM, and that a 20-mile each way round-trip journey is contemplated. Based on fuel economy statistics, and any other known information (weather, traffic, etc.) the process can “know” how much power is required to complete such a trip. This information can then be used to determine a minimum charge requirement for trip completion, with a buffer built in if desired.
Based on a current charging rate, and known minimum charge, a total time needed to charge the vehicle to the minimum level can be determined 203. Additionally, the user may only wish to charge a vehicle during certain power company “windows”. For example, power usage may be cheaper between certain hours, given a particular locale and power company guidelines. If the optimal pricing on usage is obtained from midnight to five AM, the user may only wish to charge during this window. Accordingly, in this example, even if the vehicle is not charging, the process checks to see if the time is within a charging window 205 before alerting the user of the charging interruption.
Also, in this example, the process determines whether sufficient time to charge the vehicle remains 207. For example, if a user arrived home at 3 AM and plugged in a vehicle, and needed the vehicle at 7 AM, four total hours to charge the vehicle would remain. If charging were interrupted at 3:30 AM, and the full four hours were needed to charge the vehicle, the process may determine that insufficient total time to fully charge the vehicle remains 207. In such a case, the process may alert a user 209 that the vehicle will not be fully charged to a predicted sufficient level to complete the next day's journey. In this case, the user may correct any charging interruption process, and take action to achieve the remaining charge. This can include, but is not limited to, setting a later end point for a window and sleeping in, stopping for additional power on the way to/from the destination, etc.
If sufficient time remains, the process checks to see if a no-charge condition is approaching a warning range. If a charging window was from midnight to 7 AM, and power went out at 1 AM, but only three hours was needed to charge the vehicle, the 1 AM power outage does not necessarily present a sufficient problem at 1 AM worthy of alerting a user. But as 3 or 4 AM approaches, if charging has not yet resumed, a problem could arise. In this case, as a warning range (in this example, some suitable period of time wherein sufficient time remains to charge the vehicle as needed still remains) is approached, the process may alert the user to the continued no-charging state 213, so the user can take appropriate action.
The configuration of the time range can be up to the user. Some users may want to be alerted any time charging is interrupted prior to reaching a needed charge, other users may only want to be alerted if a critical situation is imminent. The user can set conditions for warning, and can also configure a window prior to a critical point in which warnings should be sent. The particulars of these choices are all contemplated to be within the scope of the invention.
If the time of day is within the charging window, the process may additionally check to see if a suitable delay has passed since the no-charge state was detected 305. For example, it may not be desirable to notify a user for an interruption of only a few minutes in charging. In this embodiment, a delay (user or OEM defined, for example) can be set such that only delays in charging over a certain length result in user notification. If the delay has not passed, the process continues to check to see if charging is on-going or has resumed.
Once a suitable delay has passed, the process determines if a departure time is known 307. If the user has established or entered a departure time, it may be specifically or generally known to the process. If there is not a known departure time, the process may attempt to predict a departure time 309. This can be done, for example, based on previously observed behavior and will be discussed in greater detail with respect to
One a departure time is known, the process can determine an amount of time remaining prior to departure 311. The process can also check a current charge level 313, which may be additionally useful for determining if an alert should be sent to a user.
The process also checks to see if a particular required charge level is known 315. Again, this could be based on user input data (trip duration, distance, etc.). If there is insufficient information to “know” the needed charge, the process may attempt to predict a needed charge level 317, again discussed in more detail below.
Once the departure time, time remaining and needed charge level have been analyzed (and/or guessed, as appropriate) the process may determine if it is even possible, in the time remaining, to achieve the needed charge level 319. If it is not possible, the process may alert the owner to the situation 321, and then resume charge monitoring. Since the process relies on the owner to rectify a no-charging situation, the resumption of monitoring can result in additional warnings, if needed, that can help the owner perform the needed corrections.
If there is sufficient total time remaining, but the process is not yet nearing a critical point 323 (e.g., if there is more than a predetermined amount of surplus time remaining), the process may simply continue monitoring. Once there is less than the predetermined amount of surplus time remaining 323, the process may alert the owner that a critical window is approaching 325, so that the owner can take appropriate steps to rectify any problems.
In this illustrative example, the process detects that a vehicle engine has been started 401. Generally, this will correspond to the start of a trip, and a time of day and day of week are recorded 403. The recording of this information can be done so that predictions can be made for similar days of the week in following weeks, since many people follow a somewhat common schedule in terms of vehicle usage.
Also, a current power level is recorded 405. This can be used when a park state is detected to determine how much power was used during the course of a journey. In addition to the above information, a vehicle location is recorded 407. In this example, the vehicle location is also useful in predicting vehicle usage needs, since time and power needs are most likely to be common when the vehicle is departing from a common location. In other words, if the user lives in Michigan and the vehicle is parked in Ohio, then it is likely that the next day's journey will not be the typical journey for that day of the week (since the user is likely on a trip of some sort).
The process then continues to check whether or not the vehicle has entered a “park” state 409. A park state is used here as a proxy for stop detection, although other suitable determinations correlating to a journey end point may also be used. Also, in at least one embodiment, the process may require that the vehicle remain in the park state for some period of time, to ensure that more than a mere temporary stop is being made (e.g., fuel, food, etc.).
Once the process has determined that the vehicle has reached a destination, through an appropriate mechanism, the process may proceed to record the location of the destination 411 and an amount of power used to reach the destination 413. Recorded power usage can be later used to predict needed power to reach a destination. Recorded destination location can be later used to predict if a change in weather/traffic/etc. will require increased/decreased power to reach the destination. The destination can also, on a day by day basis, for example, be compared to other destinations to which the user travels on the same day of the week, to determine commonality of a certain destination, thus providing statistical likelihood of traveling to that destination.
The process first accesses a stored profile for one or more drivers of the vehicle 421. Which profile(s) is/are selected may depend on how many drivers a vehicle has, how frequently each driver uses the vehicle, etc. The process then determines if a current day of week matches any stored days of the week 423. For example, if today (or tomorrow morning, depending on the time) is Tuesday, the process will check to see if data has been stored for previous Tuesdays.
If there is data stored for similar days from previous weeks, the process may check to see if a significant non-earliest time exists 425. By significant non-earliest time, this example refers to a time, later than the earliest recorded usage time, that occurs a statistically significant number of times. For example, if a user typically goes to work at 8 AM, but one day left at 6 AM, then the earliest recorded data may be 6 AM, but the 8 AM departures would accumulate as being statistically significant. This check is made, in this example, because in the absence of such a time, the process will select the earliest known time 427, in an attempt to ensure that the user's vehicle will be suitably charged at the earliest likely moment of need.
Additionally, a buffer zone may be built in around recorded times, such that times within, for example, fifteen minutes of each other are all treated as a median time (or other suitable approximation). If there is a significant time, other than the earliest time, the process may select that time for use 429. Regardless of which time is selected, the process proceeds to retrieve an associated power requirement, saved with respect to that time 431.
Since, in this portion of this example, at least some data has been previously observed and recorded, the process can guess, even roughly, an approximation of how much power will be needed. If only one or two data points exist, the guess may have a higher likelihood of being incorrect, but if sufficient data points exist then the guess may be closer to an accurate one based on previously observed behavior.
If there is no data that matches the current day of the week 423, the process may determine whether or not the relevant day is a weekday 433. Since the majority of the population works on weekdays, the process may make some assumptions about usage until data can be recorded. If the process is implemented as soon as or soon after a vehicle is purchased, this “standard” data will only be needed on a short term basis.
If the day is a weekday, the process will select generic weekday data 437, otherwise the process will select generic weekend data 435. Next, in this example, the process determines if there is any data at all for a weekend day or a weekday 439. For example, if a vehicle process was first activated on a Wednesday, and it is the following Tuesday, there will be no Wednesday data, but there will be some saved weekday data. If there is weekday data, the process will use the closest day 441 (for example, utilizing a Monday or Wednesday for a Tuesday) or any other suitable combination of existing data. The process can then continue as previously described, substituting the data from the selected day(s) for the data that is not yet recorded for the current day of the week.
If there is no data suitable to use as a proxy for the current day of the week, the process will use a “standard time” 443. This could be, for example 7:30 AM, or any other suitable time likely to cover a significant portion of users, without creating situations likely to annoy too many users. For example, if 5 AM was selected, it would probably ensure a higher percentage of user coverage, but it may also ensure a much higher percentage of false positives on the charging results (i.e., vehicles that would be charged when they're actually needed, may not be charged by 5 AM). Based on a particular implementation's needs, the give and take between the two constraints (and any other constraints) can be considered and adjustments can be made accordingly.
Once the process has selected a departure time, it may also guess at a standard power need. In one example, this could always be “full,” but again, a full power cell may be more than most people need and may result in many false positives. The manufacturer or other implementer of the process can determine a suitable compromise likely to result in a desired number of false positives while at the same time still maintain sufficient coverage for a desired number of customers.
While exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention. Additionally, the features of various implementing embodiments may be combined to form further embodiments of the invention.
