METHOD AND SYSTEM FOR OPTIMIZING POWER UTILIZATION USING AN ALTERNATE POWER CONVERTER WHEN PERFORMING VEHICLE SOFTWARE UPDATES

Abstract

A system for delivering updates to a vehicle comprises a server device configured to deliver an over-the-air (OTA) campaign update and the vehicle itself. The vehicle contains a device with software to be updated by the OTA campaign update and a low-voltage battery that supplies low-voltage power. The system further comprises a battery that provides high-voltage power and an accessory power module trained to convert the high-voltage power to low-voltage power and containing programming to estimate the available power of the low-voltage battery.The system also includes a control unit that monitors the available power, compares it to a threshold value, and, if the available power falls below the threshold, instructs the auxiliary power module to convert the high-voltage power to provide the required low-voltage electrical power. The control unit also schedules the receipt of updates based on the available power and updates the device accordingly.

Description

BACKGROUNDThe disclosure relates generally to a method and system for optimizing vehicle current usage using an internal source and / or an alternative power converter for scaled vehicle services.EVs operate based on receiving electrical energy from one or a plurality of batteries. EVs manage the electrical energy available between charging operations.Vehicles include a plurality of devices with software. Many factors change over time for a vehicle and operation in changing environments. Software updates offer great flexibility and can improve the operation of a vehicle when new insights are gained. A manufacturer or software manufacturer may offer over-the-air (OTA) campaigns to update the vehicle software.DESCRIPTIONA system for providing updates to software in a vehicle to be updated is provided. The system includes a remote server device configured to provide an over-the-air campaign update to the vehicle to be updated. The system further includes the vehicle to be updated. The vehicle to be updated includes a device including software configured to be updated by the over-the-air campaign update and a relatively low voltage battery that supplies electric power with DC power with relatively low voltage. The system further includes a relatively high voltage vehicle electrical battery that provides relatively high voltage DC electrical voltage and an accessory power module configured to convert the high voltage DC electrical power to the low voltage DC electrical power, and including programming to estimate available power of the relatively low voltage battery. The system further includes a monitoring controller, programming for monitoring the available power of the relatively low voltage battery and comparing the available power of the relatively low voltage battery to a threshold power, commanding the auxiliary power module to, when the available power of the low voltage battery is equal to or less than the threshold power, convert the electrical power to high voltage direct current to provide the electrical power to low voltage direct current. The monitoring controller further includes programming for scheduling receipt of the over-the-air campaign update based on the available power of the relatively low voltage battery; and updating the software of the device with the over-the-air campaign update.In some embodiments, the monitoring controller also includes programming for evaluating a situational perception factor, and re-evaluating the estimated available power based on the situational perception factor.In some embodiments, evaluating the situational perception factor includes evaluating a vehicle location, planning data, a feature update list, a timeline, an average power decay, or a temperature.In some embodiments, the monitoring controller further comprises programming for monitoring occurrence of a plug-in event; and recalculating the available power of the relatively low voltage battery based on the charging performed during the plug-in operation.In some embodiments, the remote server device includes programming for mapping a list of a plurality of available over-the-air campaign updates to be performed for a group of vehicles with situational perception information, and sending the list of the plurality of available over-the-air campaign updates to the group of vehicles, including sending a relevant portion of the list of the plurality of available over-the-air campaigns to the vehicle to be updated.In some embodiments, the monitoring controller further includes programming to monitor the vehicle's situational awareness information to be updated, estimate available time periods to schedule receiving a plurality of over-the-air campaign updates corresponding to the relevant portion of the list of the plurality of available over-the-air campaign updates based on the available power of the relatively low voltage battery and the situational awareness information. The monitoring controller further includes programming for scheduling to receive the plurality of over-the-air campaign updates based on the available time periods.In some embodiments, the monitoring controller further includes programming for monitoring actual power consumption during an operating period including the available periods, comparing the actual power consumption to a predictive power consumption algorithm, and adjusting the available periods based on the actual power consumption when the actual power consumption exceeds the power consumption predicted by the performance prediction algorithm.According to an alternative embodiment, a system for providing software updates in a plurality of vehicles is provided. The system includes a remote server device configured to provide over-the-air campaign update to the plurality of vehicles and the plurality of vehicles. Each of the plurality of vehicles includes a device including software configured to be updated by the over-the-air campaign update and a relatively low voltage battery supplying low voltage direct current electrical power. Each of the plurality of vehicles further includes a relatively high voltage vehicle electric battery that provides high voltage DC electric power and an accessory power module configured to convert the high voltage DC electric power to the low voltage DC electric power, and including programming to estimate an available power of the relatively low voltage battery. Each of the plurality of vehicles also includes a monitoring controller including programming for monitoring the available power of the battery at relatively low voltage. The monitoring controller is further programmed to compare the available power of the relatively low voltage battery to a threshold power, and command the auxiliary power module to, when the available power of the low voltage battery is equal to or less than the threshold power, convert the electrical power to high voltage direct current to provide the electrical power to low voltage direct current. The monitoring controller further includes programming for scheduling receipt of the over-the-air campaign update based on the available power of the relatively low voltage battery, and updating the software of the device with the over-the-air campaign update.In some embodiments, the monitoring controller also includes programming for evaluating a situational perception factor, and re-evaluating the estimated available power based on the situational perception factor.In some embodiments, the evaluation of the situation awareness factor includes the evaluation of a vehicle location, planning data, an update list for features, a timeline, an average power decay, or the temperature.In some embodiments, the remote server device includes programming for mapping a list of a plurality of available over-the-air campaign updates to be performed for a group of vehicles with situational perception information, and sending the list of the plurality of available over-the-air campaign updates to the group of vehicles, including sending a relevant portion of the list of the plurality of available over-the-air campaign updates to each of the plurality of vehicles.In some embodiments, the monitoring controller further includes programming for estimating available time periods to schedule receiving a plurality of updates of over-the-air campaigns corresponding to the relevant portion of the list of the plurality of available over-the-air campaign updates based on the available power of the relatively low voltage battery and the situational perception information. The monitoring controller further includes programming for scheduling to receive the plurality of over-the-air campaign updates based on the available time periods.In some embodiments, the monitoring controller further comprises programming to monitor the actual power consumption during an operating period including the available periods, compare the actual power consumption to a predictive power consumption algorithm, and adjust the available periods based on the actual power consumption when the actual power consumption exceeds the power consumption predicted by the performance prediction algorithm.In some embodiments, the remote server device includes programming for identifying a group of vehicles within the plurality of vehicles to be updated with a same plurality of over-the-air campaign updates, and evaluating the available power of the relatively low voltage battery of each vehicle of the group of vehicles and scheduling transmission of the plurality of over-the-air campaign updates to each vehicle of the group of vehicles at simultaneous times based on the evaluation.In some embodiments, the remote server device includes programming for identifying a group of vehicles within the plurality of vehicles to be updated with a same plurality of over-the-air campaign updates, evaluating the available power of the relatively low voltage battery of each vehicle of the group of vehicles, and scheduling the transmission of the plurality of over-the-air campaign updates to each vehicle of the group of vehicles at a sequence of times based on the evaluation.According to an alternative embodiment, a method for providing software updates in a vehicle is provided. The method includes, within the vehicle, receiving an over-the-air campaign update by the vehicle, operating a device including software configured to be updated by the over-the-air campaign update, operating a relatively low voltage battery that provides electrical power with low voltage DC current, and operating a relatively high voltage vehicle electrical battery that provides electrical power with high voltage DC current. The method further includes operating within the vehicle an accessory power module configured to convert the high voltage DC electrical power to the low voltage DC electrical power and including programming to estimate the available relatively low voltage power of the battery. The method further comprises monitoring the available power of the relatively low voltage battery, and comparing the available power of the relatively low voltage battery to a threshold power. The method further includes the computer processor, when the available power of the relatively low voltage battery is equal to or less than the power threshold, instructing the accessory power module to convert the electrical power to high voltage DC power to provide the electrical power to low voltage DC power. The method further includes, within the computerized processor, scheduling receipt of the over-the-air campaign update based on the available power of the relatively low voltage battery, and updating the software of the device with the over-the-air campaign update.In some embodiments, the method further comprises evaluating, by the computer processor in the vehicle, a situational perception factor and re-evaluating the estimated available power based on the situational perception factor.In some embodiments, evaluating the situational perception factor includes evaluating a vehicle location, planning data, an update list for features, a timeline, an average power decay, or the temperature.In some embodiments, the method further includes the computer processor in the vehicle monitoring the occurrence of a plug-in event and recomputing the available power of the relatively low voltage battery based on the charging performed during the plug-in event.In some embodiments, the method further comprises within the remote server device associating a list of a plurality of available over-the-air campaign updates for a group of vehicles with situational perception information and sending the list of the plurality of available over-the-air campaign updates to the group of vehicles including sending a relevant portion of the list of the plurality of available over-the-air campaign updates to the vehicle.The above features and advantages, as well as other features and advantages of the present disclosure, will be readily apparent from the following detailed description of the best modes for carrying out the disclosure when taken in conjunction with the accompanying drawings.BRIEF DESCRIPTION OF THE DRAWINGSFIG. 1 schematically illustrates a system for performing OTA campaigns in accordance with the present disclosure; FIG. 2 schematically illustrates the operation of a monitoring controller in a vehicle according to the present disclosure; FIG. 3 schematically illustrates the remote control device of FIG. 1 in accordance with the present disclosure; FIG. 4 schematically illustrates operation of the accessory power module (APM) of FIG. 2 in accordance with the present disclosure; FIG. 5 is a flow chart illustrating a method for determining the time at which the relatively high voltage EV battery of FIG. 2 is to begin use for powering low voltage vehicle devices in accordance with the present disclosure; FIG. 6 is a flow diagram illustrating a method of using situation awareness information to predict power consumption over a period of time to improve scheduling of OTA campaign updates according to the present disclosure; FIG. 7 is a flow diagram illustrating a method for adjusting or managing an Internet of Things (IoT) protocol connection timeline based on performance degradation and power consumption cost metrics, in accordance with the present disclosure; FIG. 8 is a flow diagram illustrating a method for coordinating information useful for scheduling IoT protocol intervals between the remote server device and the monitoring controller of FIG. 2, in accordance with the present disclosure; FIG. 9 is a flow diagram illustrating a method for the remote server device of FIG. 1 managing an OTA campaign for a cell of vehicles in accordance with the present disclosure; and FIG. 10 is a flow chart illustrating a method for pattern-based group update interval optimization based on a relatively low voltage power droop in accordance with the present disclosure.DETAILED DESCRIPTIONAn electric vehicle (EV) may include a plurality of power supply systems and corresponding energy stores or batteries. In an exemplary configuration, a vehicle may include a high voltage power supply system that provides and stores electrical energy in the form of direct current having a relatively high voltage, e.g., 400 volts, 600 volts, or 800 volts, for example. Such systems may further include an inverter that converts this higher voltage DC electrical energy into AC electrical energy used by an AC electric machine to propel the vehicle, and vice versa, such that the energy recovered from the electric machine may be stored in the battery of the high voltage grid. A vehicle may additionally have a low voltage power supply system that provides and stores electrical energy at a low voltage, e.g., 12 volts or the like, for example. Vehicle accessories such as radios, infotainment systems, vehicle controllers, etc., operate at low voltage.An electric vehicle is in the energy saving mode when the ignition is off, most vehicle systems are at rest, and the vehicle is disconnected from the charging station and operates solely with the energy stored in the vehicle. Power management is important during operation in the power save mode to preserve and prioritize the vehicle's operability and functionality and functions.An over the air (OTA) campaign can be described as a software update or data packet that can publish a company or programming source. An OTA campaign can be used to update a vehicle's software or provide content to vehicle accessory devices or systems, such as an infotainment system. An OTA campaign succeeds for a particular vehicle when the information is successfully transmitted from the source to the vehicle. An OTA campaign is unsuccessful for the vehicle if the information is not successfully transmitted to the vehicle, the transmission is incomplete, or the transmission is corrupted. In the low power mode, an OTA campaign for an electric vehicle may be unsuccessful when the vehicle does not have the necessary electrical power to power the communication and computing system required for successful receipt and processing of the OTA campaign.The information provided in an OTA campaign may be transmitted according to a number of different communication protocols. In one embodiment, an Internet of Things (IoT) protocol such as Message Queuing Telemetry Transport (MQTT) may be used for the transmission of the information. The IoT protocol is a lightweight, machine-to-machine publish-subscribe network protocol for message queues / message queue service. It is designed for connections to remote sites that have devices with limited resources or limited network bandwidth. The protocol runs over the Transmission Control Protocol / Internet Protocol (TCP / IP) or other network protocols that allow ordered, lossless, bidirectional connections. The IoT protocol allows the use of a publish / subscribe message pattern that allows one-to-many message distribution and application decoupling. The IoT protocol includes a mechanism for notifying interested parties when an abnormal connection break occurs. Other communication protocols, such as short message / messaging service (SMS), may alternatively be used to perform OTA campaigns.With the advent of end-to-end vehicle software platforms that enable frequent software updates over the air, there is a need for coexistence of push and pull functions in multiple modes. Thus, the current models are unable to download OTA campaigns with functions within a time window of 10 minutes at a minimum data rate of 5 gigabytes per second in the energy saving mode, particularly with regard to energy availability and utilization.Software updates such as OTA campaigns are important for vehicle maintenance. Unsuccessful update attempts may be costly. A method and system for dynamic power converter management in a vehicle are provided in which vehicle power usage and conversion and remote software updates in an electric vehicle are managed with the ignition off and the non-connected / non-charged state. The method includes using an accessory power module (APM) to dynamically monitor a rate of degradation of performance. The APM includes a computerized controller configured to monitor electrical, thermal, and state parameters of the vehicle power system and estimate power availability. The power supply for the vehicle accessory may be configured to operate at a relatively low voltage, e.g., 12 volts, with the power supply being via a low voltage system such as a 12 volt battery. Once the APM estimates that the availability of the low voltage grid approaches the threshold, a power converter is deployed to convert the power from a high voltage grid, e.g., EV batteries, to allow for an extended duration for the scaled power demand of low voltage accessories while the vehicle is in the low power mode.The presented method and system uses the optimization of the current source based on situational awareness. Situational information may include the location of the vehicle, the scheduling, the update list of functions, the timeline, the average power decay, the temperature, and other similar data to evaluate or re-evaluate usage of the power source based on feedback. The situational awareness may enable the system to map the use of high voltage energy such that low voltage energy is provided at certain times for certain purposes during a predetermined period of time in the low voltage mode. In one embodiment, an energy emulator analysis performed each time the ignition state is changed may be provided to a remote server to make situation detection determinations for the vehicle.Previous methods plan static communications or the operation of an interaction environment on the basis of the average behavior of the population and the duration of the ignition. The presented method and system includes dynamic transmission control protocol (TCP) optimization based on power consumption.The described method and system schedules the transmission of information during defined IoT protocol intervals. The system monitors power consumption in IoT protocol intervals. The degradation in performance may be defined as the amount of energy the vehicle has consumed in total or since a last determination. If the power decrease is greater than a defined power decrease threshold, the system may determine whether the rate of energy consumption is significant, i.e., greater than X%. If the rate of power consumption is significant, the system may adjust the IoT protocol connection time line, i.e., the occurrence of the defined IoT protocol intervals, based on cost metrics to budget the power outputs through the low-consumption mode time line. If power consumption is not significant, the system may continue with the currently defined IoT protocol intervals until the power budget is exhausted or a plug-in event occurs. In one embodiment, the IoT protocol connection adjustments may be configured to optimize successful completion of the OTA campaign update. In another embodiment, the settings of the IoT protocol connection may be configured such that an OTA campaign update is not performed at the same time as the conversion of energy from the high voltage battery of the vehicle begins. In another embodiment, adjustments to the IoT protocol connection may be configured to avoid frequent updates that contribute to high battery system power consumption.The disclosed method and system may determine an optimization of the TCP update interval based on power availability and situation awareness. A vehicle includes a plurality of functions that may be available when the system powers the respective accessories. The system may associate a list of OTA campaigns or scheduled updates for each of the plurality of auxiliary devices with situational awareness. The system may send the list of feature OTA campaigns to the respective vehicles with details. Based on the situation information and the power availability, the TCP sets the ping duration for the IoT protocol update interval based on the power availability and the time axis for the function request.A remote server device performing an OTA campaign may utilize OTA campaign management based on the determination of a state of the plurality of vehicles to be updated. A plurality of vehicles to be updated may include a relatively large number of vehicles. The bandwidth of the remote server device performing the OTA campaign may be limited so that the plurality of vehicles can be divided into cells, each cell including a cell identification number. Each of the plurality of vehicles may transmit channel status information such as the cell identification number assigned to that vehicle and the availability of the vehicle for an IoT protocol interval. The remote server device performing the OTA campaign may determine whether the operation of the number of vehicles to update in a particular cell exceeds a maximum throughput threshold. If the maximum throughput threshold is exceeded, the system may distribute a consolidated schedule for multiple OTA campaigns over a certain amount of time in the cloud and forward the campaign to the vehicle to conserve the energy budget.In one embodiment, the remote server device performing the OTA campaign may monitor the degradation of each vehicle in a cell or group, and the system may determine or modulate a time and frequency of the IoT protocol update interval ping based on the state of the group. In one example, a group may be scheduled for updates based on an average state of the vehicles in the group. In another example, a group may be scheduled for updates based on the vehicle with the greatest impairment in the group.FIG. 1 schematically shows a system 10 for carrying out OTA campaigns. The system 10 includes a remote server device 100 and a plurality of vehicles 200A, 200B, 200C. Each of the vehicles 200A, 200B, 200C is shown with a monitoring controller 210A, 210B, 210C and a wireless communication device 220A, 220B, 220C, respectively. The remote server device 100 may be remotely operated and performs OTA campaigns that provide updates to accessory devices and systems of the plurality of vehicles 200A, 200B, 200C. Each of the vehicles 200A, 200B, 200C wirelessly communicates with the remote server device 100 via the respective wireless communication device 220A, 220B, 220C.FIG. 2 schematically shows the operation of a monitoring control device 210 in a vehicle. The monitoring controller 210 is an example of one of the monitoring controllers 210A, 210B, 210C of FIG. 1. the monitoring controller 210 is a computerized device and may include a processor configured to execute programmed code, random access memory (RAM), and persistent memory such as a hard disk. A relatively high voltage EV battery 250 is shown connected to an inverter 252 which, in turn, is connected to an electric machine 254 that includes an output shaft configured to provide motive power to the vehicle. A relatively low voltage battery 230 is also depicted. The low voltage battery 230 may be configured to store and provide electrical energy at 12 volts DC. An accessory power module (APM) 240 is also depicted. The APM 240 is configured to selectively convert high voltage electrical from the high voltage battery 250 to provide low voltage electrical to the low voltage battery 230 and other vehicle accessories and systems that are supplied with electrical energy at the relatively low voltage supplied by the low voltage battery 230. The APM 240 may include a power measurement to measure or estimate the total amount of electrical energy consumed by the relatively high voltage EV battery 250 to provide the relatively low voltage electrical power. In addition, the APM 240 may include programming for a performance prediction algorithm. This algorithm may monitor factors such as electrical factors, thermal factors, and battery health factors. The algorithm may provide an output or estimate of the power availability of the batteries 230, 250. This estimate of power availability is provided to the monitoring controller 210 and provides the monitoring controller 210 a measure of how much energy is consumed by the vehicle during the low power mode of operation and when the available energy thresholds are reached during a period of the low power mode of operation.The monitoring controller 210 is in communication with the remote server device 100 via the wireless communication device 220. The monitoring controller 210 may receive data via the communication device 220 and store data from the remote server device 100, including an executable or activatable software update for a vehicle system. An example telematics device 260 and an example vehicle navigation device 270 are shown. A number of additional or alternative vehicle devices or systems may be configured to receive software updates from the remote server device 100 via the monitoring controller 210. The receipt or step of receiving an OTA campaign update from the remote server device 100 may include a wake-up event for the monitoring controller device. In the power saving mode, in which the ignition is off and there is no charging of the vehicle batteries 230, 250, the systems of the vehicle, including the monitoring controller 210, may be placed in a sleep mode or a non-functional state to reduce or eliminate the electrical power consumption of the systems. To receive the data associated with an OTA campaign update, the monitoring controller 210 is subject to a wake-up event, the monitoring controller 210 is powered for a certain duration or time period, and once the OTA campaign update is received, a next step can be performed. In one embodiment, the monitoring controller 210 may confirm that the OTA campaign update has been properly received and stored, the time period may end, and the data of the OTA campaign update may be accessed and executed when the ignition is next turned on. In another embodiment, the monitoring controller 210 may receive the data of the OTA campaign update and perform the update on one of the devices 260, 270 before the time period ends and the monitoring controller enters sleep mode again.Remote server device 100 may request or announce that an OTA campaign update is available or should be scheduled for receipt by monitoring controller 210. The monitoring controller 210 may use the request and estimate of the available power to schedule an IoT protocol interval for receiving the OTA campaign update.FIG. 3 schematically illustrates the remote server device 100 of FIG. 1. the remote server device 100 includes a computerized processing device 110, a communication device 120, an input / output coordinating device 130, and a storage device 140. It should be appreciated that the remote server device 100 may include other components and some of the components may not be present in some embodiments.The processing device 110 may include a memory, e.g., a read only memory (ROM) and a random access memory (RAM), in which processor-executable instructions are stored, and one or more processors that execute the processor-executable instructions. In embodiments where the processing device 110 includes two or more processors, the processors may operate in parallel or in a distributed manner. The processing device 110 may execute the operating system of the remote server device 100. The processing device 110 may include one or more modules that execute programmed code or computer-based processes or methods with executable steps. The illustrated modules may include a single physical device or functionality that extends across multiple physical devices. The processing device 110 may further include programming modules including an OTA campaign update module 112, a data transfer module 114, and a cell update module 116.The communication device 120 may include a communication / data connection to a bus device configured to transmit data to various components of the system, and may include one or more wireless transceivers for performing wireless communication.The input / output coordinating device 130 includes hardware and / or software configured to allow the processing device 110 to receive and / or exchange data with the onboard means of the remote server device 100, including input / output devices, a microphone, a speaker, and buttons installed on the remote server device 100.The storage device 140 is a device that stores data generated or received from the remote server device 100. The memory device 140 may include, but is not limited to, flash or solid state memory.The OTA campaign update module 112 includes programming that enables the remote server device 100 to receive and schedule OTA campaigns. The OTA campaign update module 112 may include information to determine or segment which vehicles from a group of vehicles should receive a particular update. Such a determination may include determining in which vehicles certain functions are installed, certain device generations are installed, a subscription service is active to receive updates, or other similar criteria.The communication module 114 includes programming to perform communication events with vehicles. The data transfer module 114 may include programming specific to a protocol used for the data transfer, e.g., the IoT protocol. The communication module 114 may access stored data files, establish communication with one or more vehicles, transmit the stored data files, and confirm validity of the communication. The communication module 114 may be programmed to track a list of vehicles and store data about which vehicles received which update.The cell update module 116 includes programming to create and track cells or groups of vehicles, determine a threshold throughput based on how many vehicles the remote server device 100 can update simultaneously, and share OTA campaign events according to the vehicle cells and the threshold throughput.The remote server device 100 is an example computerized device capable of executing programmed code to operate the disclosed system and method. A number of different embodiments of the remote server device 100 and the modules operable therein are conceivable, and the disclosure is not intended to be limited to the examples listed here.FIG. 4 schematically illustrates the operation of the APM 240 of FIG. 2. the APM 240 is programmed to receive input and determine an estimated available power of the vehicle battery 230. The input 241 includes the input voltage of the battery 230. Input 242 includes receiving power from battery 230. Input 243 includes the voltage output by battery 230. Input 244 includes the current from battery 230. Input 245 includes the temperature of battery 230. Output 246 includes the power output from battery 230. Output 247 is the available power of battery 230. Output 248 includes the maximum current of battery 230.FIG. 5 is a flow chart illustrating a method 300 for determining when to begin using the relatively high voltage EV battery 250 of FIG. 2 to supply low voltage vehicle devices. The method 300 may be performed within the monitoring controller 210 of FIG. 2. In another embodiment, the method 300 may be performed within the APM 240 of FIG. 2. The method 300 is initiated when the vehicle is in the low power mode and begins at step 302. In step 304, a periodic or dynamically operated estimate of accessory power module degradation is checked. This estimate of accessory power module degradation is a measure of how much power has been consumed by the relatively low voltage battery 230 during the low power mode of operation. In step 306, the estimated degradation of the accessory power module is compared to a power degradation threshold. If the estimated accessory module degradation is not yet equal to or greater than the threshold degradation, the method 300 returns to step 304, where the estimated accessory module degradation is re-estimated periodically or dynamically. If the estimate of accessory power module degradation is equal to or greater than the threshold degradation, the method 300 proceeds to step 308 where the APM 240 controls activation of the relatively high voltage EV battery 250 and converts the high voltage DC electrical power of the relatively high voltage EV battery 250 to the relatively low voltage DC electrical power used by the vehicle systems. Power may be provided from the relatively high voltage EV battery 250 for a period of time until a threshold degradation of the relatively high voltage EV battery 250 has occurred, whereupon another remedial step may be taken, such as notifying a user. In step 310, method 300 is ended. The method 300 includes example steps for managing the electrical power of a first relatively low voltage battery 230 and a second relatively high voltage battery 250. A number of additional and / or alternative steps are conceivable, and the disclosure is not intended to be limited to the examples listed herein.FIG. 6 is a flow diagram illustrating a method 400 of utilizing situation detection information to predict energy consumption over a period of time to improve scheduling of OTA campaign updates. Method 400 is initiated when the vehicle is in the low power mode and begins at step 402. In step 404, inputs regarding the operation of the batteries 230, 250 of FIG. 2 and the operation of other electrical system components are monitored and it is determined that relevant information is available for situation detection. In step 406, the inputs are processed and the situation awareness information is generated. The situation information may include the location of the vehicle, the planning of events related to energy consumption in the low power mode, a list of functions to be updated by an OTA campaign update, a timeline including factors such as historical chargings and future navigation routes input by a user, the average power drop of the vehicle, and the temperature. In step 408, the anticipated power decay over a certain period of time may be updated or re-evaluated based on the situation detection information. In step 410, a prediction map for use of the APM 240 of FIG. 2 is determined by the low power mode of operation to use relatively high voltage electrical energy to provide relatively low voltage electrical energy. At step 412, upon each key-on, an optimized power emulator analysis useful for planning OTA campaign updates is transmitted to the remote server device 100 of FIG. 2. In step 414, method 400 is ended. The method 400 includes example steps of utilizing situation detection information to plan or predict performance degradation by the low-performance mode of operation. A number of additional and / or alternative steps are conceivable, and the disclosure is not intended to be limited to the examples listed herein.FIG. 7 is a flow diagram illustrating a method 500 for adjusting or managing an IoT protocol connection timeline based on performance degradation and power consumption cost metrics. Method 500 initiates when the vehicle is in the low power mode and begins at step 502. In step 504, the monitoring controller 210 of FIG. 2 monitors power consumption at each IoT protocol interval or each wake-up event scheduled to receive an OTA campaign update. In step 506, it is determined whether the total power dissipation reaches or exceeds a power dissipation threshold. If the total power degradation does not meet or exceed the threshold, the method 500 continues to step 508. If the total power degradation satisfies or exceeds the threshold power degradation, the method 500 proceeds to step 516.In step 508, it is determined whether the current power consumption is below a threshold power consumption. The threshold for power consumption may include an external factor adjustment for variables such as time of day or temperature. If the current power consumption rate is below the power consumption threshold, the method 500 proceeds to step 510, where an IoT protocol connection timeline is adjusted based on cost metrics. If the current power consumption rate is not below the threshold power consumption, the method 500 proceeds to step 518. In step 518, a current IoT protocol interval continues until an energy budget is exhausted. Once the power budget is exhausted, the monitoring controller may switch from IoT protocol operation to alternative connection methods based on cost metrics in step 520.In step 512, a plug-in charge event is monitored. In step 514, the battery limits are recomputed depending on how much the battery is charged (e.g., the available power of the relatively low voltage battery is recomputed). The method then proceeds to step 510, where the schedule for the IoT protocol connection is adjusted based on cost metrics. In step 522, method 500 is ended. The method 500 may be repeated. The method 500 includes example steps of adjusting or managing an IoT protocol connection timeline based on performance degradation and energy consumption cost metrics. A number of additional and / or alternative steps are conceivable, and the disclosure is not intended to be limited to the examples presented herein.FIG. 8 is a flow diagram illustrating a method 600 for coordinating information useful for scheduling IoT protocol intervals between the remote server device 100 and the monitoring controller 210 of FIG. 2. Method 600 initiates when the vehicle is in the low power mode and begins at step 602. In step 604, the remote server device 100 maps a list of available OTA campaign updates to be operated for vehicles having situation awareness information. In step 606, the remote server device 100 sends the list of available OTA campaign updates to the respective vehicles. In step 608, the monitoring controller 210 in one of the vehicles monitors the situation awareness information and estimated power availability for the vehicle and estimates the available time periods in which IoT protocol intervals may be operated to receive the OTA campaign updates. In step 610, the monitoring controller 210 sets an IoT protocol interval ping duration based on the estimated power availability and the list of available OTA campaign updates. In an example calculation, a vehicle may determine that 55 minutes of IoT protocol intervals are optimal to schedule for nine days in the low power mode. In step 612, the actual power consumption is monitored and compared to the predicted power consumption values from the estimated power availability after each IoT protocol interval. If the actual power consumption is greater than the predicted power consumption values, the method 600 proceeds to step 614 where the IoT protocol interval is adjusted based on the actual power consumption. After step 614, the method 600 proceeds to step 616. If the actual power consumption is not greater than the predicted power consumption, the method 600 proceeds to step 616. In step 616, method 600 is ended. The method 600 includes example steps for the remote server device 100 and the monitoring controller 210 of FIG. 2 coordinating information useful for planning IoT protocol intervals based on energy consumption in an EV vehicle in the low power mode. A number of additional and / or alternative steps are conceivable, and the disclosure is not intended to be limited to the examples presented herein.FIG. 9 is a flow diagram illustrating a method 700 for the remote server device 100 of FIG. 1 managing an OTA campaign for a cell of vehicles 200A, 200B, 200C. The method 700 begins in step 702. In step 704, the remote server device 100 identifies an OTA campaign to be sent to at least one cell or group of vehicles and sends a query to available vehicles for information. In step 706, the cell of vehicles 200A, 200B, 200C responds to the request with information useful for coordinating the OTA campaign. The information may include a cell identification number for each vehicle 200A, 200B, 200C, a schedule for IoT protocol intervals for each vehicle 200A, 200B, 200C, the communication bandwidth available for each vehicle 200A, 200B, 200C, etc. In step 708, the remote server device 100 uses the provided information to quantify an existing vehicle cell and determine a throughput threshold or a maximum number of vehicles to update for which the remote server device 100 may simultaneously provide the OTA campaign update. If the number of vehicles in the existing vehicle cell exceeds the throughput threshold for the remote server device 100, the method 700 proceeds to step 712, where the remote server device 100 distributes the OTA campaign over a defined time axis, assigning a time "T" to each vehicle 200A, 200B, 200C, and receiving the OTA campaign update at that time. If the number of vehicles in the existing vehicle cell does not exceed the threshold throughput of the remote server device 100, the method 700 proceeds to step 710 where the remote server device sends the campaign to the existing vehicle cell at the same time. The method 700 ends with step 714. The method 700 includes example steps for the remote server device 100 of FIG. 1 managing an OTA campaign for a cell of vehicles 200A, 200B, 200C. A number of additional and / or alternative steps are conceivable, and the disclosure is not intended to be limited to the examples listed herein.FIG. 10 is a flow diagram illustrating a method 800 for pattern-based group update interval optimization based on a relatively low voltage drop. The method 800 begins with step 802. In step 804, the remote server device 100 of FIG. 1 identifies a group of vehicles 200A, 200B, 200C with a patterned feature update plan or a plan of desirable and appropriate updates common to each of the group of vehicles 200A, 200B, 200C. In step 806, the remote server device queries and manages a power availability list based on power availability information provided by each of the group of vehicles 200A, 200B, 200C. The information may be provided at power transition states, e.g., each time a wake-up event or a firing event occurs at each of the vehicles 200A, 200B, 200C. In step 808, the remote server device 100 determines whether one of the vehicles 200A, 200B, 200C experiences greater performance degradation than an average performance degradation value. If one of the vehicles experiences greater performance degradation than the average performance degradation value, the method 800 proceeds to step 810 where the remote server device 100 may send feedback to the vehicle experiencing greater performance degradation. The feedback may include information about exposure time, cycle duration, and proposed IoT protocol interval duration. If none of the vehicles experiences greater performance degradation than the average performance degradation value, the method 800 proceeds to step 812 where the feedback about the common update interval is sent from the remote server device 100 to the vehicles 200A, 200B, 200C based on a predicted feature update time line. The method 800 ends with step 814. The method 800 includes example steps for pattern-based group update interval optimization based on a relatively low voltage drop. A number of additional and / or alternative steps are conceivable, and the disclosure is not intended to be limited to the examples listed herein.While the best modes for carrying out the disclosure have been described in detail, those familiar with the art to which this disclosure relates will recognize various alternative designs and embodiments for carrying out the disclosure within the scope of the appended claims.

Claims

A system for providing updates to software in a vehicle to be updated, comprising a remote server device configured to provide an over-the-air campaign update to the vehicle to be updated; and the vehicle to be updated including: a device including software configured to be updated by the over-the-air campaign update; a relatively low voltage battery that provides electrical power with low voltage direct current; a relatively high voltage vehicle electrical battery that provides electrical power with high voltage direct current; an accessory power module configured to convert the high voltage DC electrical power to the low voltage DC electrical power, and comprising programming to estimate an available power of the relatively low voltage battery; a monitoring controller comprising programming to: monitor the available power of the relatively low voltage battery; compare the available power of the relatively low voltage battery to a power threshold; command the accessory power module, when the available power of the low voltage battery is equal to or less than the power threshold, to convert the high voltage DC electrical power to provide the low voltage DC electrical power; schedule reception of the over-the-air campaign update based on the available power of the relatively low voltage battery; and updating the software of the device with the over-the-air campaign update.The system of claim 1, wherein the monitoring controller further comprises programming for: evaluating a situational perception factor; and re-evaluating the estimated available power based on the situational perception factor.The system of claim 2, wherein evaluating the situational perception factor comprises evaluating a vehicle location, planning data, a feature update list, a timeline, an average power decay, or a temperature.The system of claim 1, wherein the monitoring controller further comprises programming for: monitoring an occurrence of a plug-in event; and recalculating the available power of the relatively low voltage battery based on the charging performed during the plug-in operation.The system of claim 1, wherein the remote server device comprises the programming for: mapping a list of a plurality of available over-the-air campaign updates to be performed for a group of vehicles with situational perception information; and sending the list of the plurality of available over-the-air campaign updates to the group of vehicles including sending a relevant portion of the list of the plurality of available over-the-air campaign updates to the vehicle to be updated.The system of claim 5, wherein the monitoring controller further comprises the programming for: monitoring the situational awareness information of the vehicle to be updated; estimating available time periods to schedule receiving a plurality of over-the-air campaign updates corresponding to the relevant portion of the list of the plurality of available over-the-air campaign updates based on the available power of the relatively low voltage battery and the situational awareness information; and scheduling for receiving the plurality of over-the-air campaign updates based on the available time periods.The system of claim 6, wherein the monitoring controller further comprises programming for: monitoring actual power consumption during an operating period including the available periods; comparing the actual power consumption to a predictive power consumption algorithm; and adjusting the available periods based on the actual power consumption if the actual power consumption exceeds the power consumption predicted by the power prediction algorithm.A system for providing software updates in a plurality of vehicles, comprising: a remote server device configured to provide an over-the-air campaign update to the plurality of vehicles; and the plurality of vehicles, each of the plurality of vehicles comprising: a device including software configured to be updated by the over-the-air campaign update; a relatively low voltage battery that provides low voltage direct current electrical power; a relatively high voltage vehicle electrical battery that provides high voltage direct current electrical power; an accessory power module configured to convert the high voltage DC electrical power to the low voltage DC electrical power, and comprising programming to estimate an available power of the relatively low voltage battery; a monitoring controller comprising programming to: monitor the available power of the relatively low voltage battery; compare the available power of the relatively low voltage battery to a threshold power; command the accessory power module, when the available power of the low voltage battery is equal to or less than the threshold power, to convert the high voltage DC electrical power to provide the low voltage DC electrical power; schedule reception of the over-the-air campaign update based on the available power of the relatively low voltage battery; and updating the software of the device with the over-the-air campaign update.The system of claim 8, wherein the monitoring controller further comprises programming for: evaluating a situational perception factor; and re-evaluating the estimated available power based on the situational perception factor.A method for providing updates to software in a vehicle, comprising: within the vehicle: receiving, by the vehicle, an over-the-air campaign update; operating a device including software configured to be updated by the over-the-air campaign update; operating a relatively low voltage battery that provides low voltage direct current electrical power; operating a relatively high voltage vehicle electrical battery that provides high voltage direct current electrical power; operating an accessory power module configured to convert the high voltage direct current electrical power to the low voltage direct current electrical power and including programming to estimate the relatively low voltage battery available power; In a computerized processor within the vehicle: monitoring the available power of the relatively low voltage battery; comparing the available power of the relatively low voltage battery to a threshold power; if the available power of the relatively low voltage battery is equal to or less than the power threshold, instructing the accessory power module to convert the electrical power to high voltage DC to provide the electrical power to low voltage DC; scheduling receipt of the over-the-air campaign update based on the available power of the relatively low voltage battery; and updating the software of the device with the over-the-air campaign update.

Images