Method and system for optimizing power utilization using alternative power converters when operating vehicle software updates

Abstract

Methods and systems for optimizing power utilization using alternative power converters when operating vehicle software updates. A system for providing updates in a vehicle includes a server device and a vehicle configured to provide OTA activity updates. The vehicle includes a device including software to be upgraded by over-the-air activity updates, and a low voltage battery providing low voltage power. The system further includes a battery providing high voltage power, and an accessory power module configured to convert the high voltage power to low voltage power and including programming to estimate available power of the low voltage battery. The system further includes a controller that monitors the available power, compares the available power to a threshold, and commands the accessory power module to convert the high voltage power to provide the low voltage electrical power when the available power is less than the threshold. The controller further schedules a reception update based on the available power and updates the device with the update.

Description

Technical Field

[0001] The present disclosure generally relates to a method and system for optimizing vehicle power utilization using internal sources and / or replacing electric vehicle (EV) power converters for scaled vehicle services. Background Art

[0002] An EV operates based on receiving electrical power from one or more batteries. The EV manages the available electrical power between charging events.

[0003] Vehicles include multiple devices with software. Many factors change over time for vehicles and operations in changing environments. Software updates provide important flexibility and can improve the operation of the vehicle as lessons are learned. Manufacturers or software publishers can provide over-the-air (OTA) activities to update the vehicle's software. Summary of the invention

[0004] A system for providing updates to software in a vehicle to be updated is provided. The system includes a remote server device configured to provide over-the-air active updates 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 upgraded via over-the-air active updates and a relatively low voltage battery providing relatively low voltage DC power. The system further includes a relatively high voltage electric vehicle battery providing relatively high voltage DC power, and an accessory power module configured to convert the relatively high voltage DC power to relatively low voltage DC power and including programming to estimate the available power of the relatively low voltage battery. The system further includes a supervisory controller including programming to perform the following steps: monitoring the available power of the relatively low voltage battery, comparing the available power of the relatively low voltage battery to a threshold power level, and when the available power of the relatively low voltage battery is equal to or less than the threshold power level, commanding the accessory power module to convert the relatively high voltage DC power to provide the relatively low voltage DC power. The supervisory controller further includes programming to schedule receipt of over-the-air activity updates based on available power of the relatively low-voltage battery and to update software of the device using the over-the-air activity updates.

[0005] In some embodiments, the supervisory controller further includes programming to evaluate contextual awareness factors and re-evaluate the estimated available power based on the contextual awareness factors.

[0006] In some embodiments, evaluating contextual awareness factors includes evaluating vehicle location, schedule data, feature update lists, timelines, average power degradation, or temperature.

[0007] In some embodiments, the supervisory controller further includes programming to monitor for occurrences of insertion events and recalculate available power for the relatively low-voltage battery based on charging performed during the insertion event.

[0008] In some embodiments, the remote server device includes programming for performing the following steps: mapping a list of multiple available air activity updates to be operated for a vehicle group using contextual awareness information, and sending the list of multiple available air activity updates to the vehicle group, including sending relevant portions of the list of multiple available air activity updates to the vehicle to be updated.

[0009] In some embodiments, the supervisory controller further includes programming to monitor the situational awareness information of the vehicle to be updated, and estimate an available time period based on the available power of the relatively low voltage battery and the situational awareness information, in which to schedule receiving a plurality of air activity updates corresponding to a relevant portion of the list of a plurality of available air activity updates. The supervisory controller further includes programming to schedule receiving the plurality of air activity updates based on the available time period.

[0010] In some embodiments, the supervisory controller further includes programming for monitoring actual power consumption throughout an operating period including an available time period, comparing the actual power consumption to a predictive power algorithm, and adjusting the available time period based on the actual power consumption when the actual power consumption exceeds the power consumption predicted by the predictive power algorithm.

[0011] According to an alternative embodiment, a system for providing updates to software in a plurality of vehicles is provided. The system includes a remote server device and a plurality of vehicles, the remote server device being configured to provide over-the-air active updates to the plurality of vehicles. Each of the plurality of vehicles includes: a device including software configured to be upgraded via over-the-air active updates, and a relatively low voltage battery providing relatively low voltage DC power. Each of the plurality of vehicles further includes a relatively high voltage electric vehicle battery providing relatively high voltage DC power, and an accessory power module configured to convert the relatively high voltage DC power to relatively low voltage DC power and including programming to estimate the available power of the relatively low voltage battery. Each of the plurality of vehicles further includes a supervisory controller including programming to monitor the available power of the relatively low voltage battery and compare the available power of the relatively low voltage battery to a threshold power level. The supervisory controller further includes programming to command the accessory power module to convert the relatively high voltage DC power to provide the relatively low voltage DC power when the available power of the relatively low voltage battery is equal to or less than the threshold power level. The supervisory controller further includes programming to schedule receipt of over-the-air activity updates based on available power of the relatively low-voltage battery and to update software of the device using the over-the-air activity updates.

[0012] In some embodiments, the supervisory controller further includes programming to evaluate a contextual awareness factor and to re-evaluate the estimated available power based on the contextual awareness factor.

[0013] In some embodiments, evaluating contextual awareness factors includes evaluating vehicle location, schedule data, feature update lists, timelines, average power degradation, or temperature.

[0014] In some embodiments, the remote server device includes programming for mapping a list of multiple available air activity updates to be operated for multiple vehicles and sending the list of multiple available air activity updates to a group of vehicles, including sending a relevant portion of the list of multiple available air activity updates to each of the multiple vehicles.

[0015] In some embodiments, the supervisory controller further includes programming to perform the following steps: estimating an available time period based on the available power of the relatively low voltage battery and the context awareness factor, in which available time period, scheduling reception of a plurality of air activity updates corresponding to the relevant portion of the list of the plurality of available air activity updates. The supervisory controller further includes programming to schedule reception of the plurality of air activity updates based on the available time period.

[0016] In some embodiments, the supervisory controller further includes programming for monitoring actual power consumption throughout an operating period including an available time period, comparing the actual power consumption to a predictive power algorithm, and adjusting the available time period based on the actual power consumption when the actual power consumption exceeds the power consumption predicted by the predictive power algorithm.

[0017] In some embodiments, the remote server device includes programming for performing the following steps: identifying a vehicle group within the plurality of vehicles to be updated using the same plurality of air activity updates, evaluating the available power of a relatively low voltage battery of each of the vehicle groups, and simultaneously transmitting the plurality of air activity updates to each of the vehicle groups based on the evaluation schedule.

[0018] In some embodiments, the remote server device includes programming for performing the following steps: identifying a vehicle group within the plurality of vehicles to be updated using the same plurality of air activity updates, evaluating the available power of a relatively low voltage battery of each of the vehicle groups, and transmitting the plurality of air activity updates to each of the vehicle groups in a time sequence based on the evaluation schedule.

[0019] According to an alternative embodiment, a method for providing updates to software in a vehicle is provided. The method includes receiving an over-the-air active update by the vehicle in the vehicle, operating a device including software configured to be upgraded via an over-the-air active update, operating a relatively low voltage battery providing relatively low voltage direct current power, and operating a relatively high voltage electric vehicle battery providing relatively high voltage direct current power. The method further includes operating an accessory power module in the vehicle, the accessory power module being configured to convert relatively high voltage direct current power to relatively low voltage direct current power, and including programming to estimate the available power of the relatively low voltage battery. The method further includes, in a computerized processor in the vehicle, 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 level. The method further includes, in the computerized processor, commanding the accessory power module to convert the relatively high voltage direct current power to provide the relatively low voltage direct current power when the available power of the relatively low voltage battery is equal to or less than the threshold power level. The method further includes, in the computerized processor, scheduling receiving over-the-air active updates based on the available power of the relatively low voltage battery, and updating the software of the device using the over-the-air active updates.

[0020] In some embodiments, the method further includes, within a computerized processor within the vehicle, evaluating a situational awareness factor, and re-evaluating the estimated available power based on the situational awareness factor.

[0021] In some embodiments, evaluating contextual awareness factors includes evaluating vehicle location, schedule data, feature update lists, timelines, average power degradation, or temperature.

[0022] In some embodiments, the method further includes, within a computerized processor within the vehicle, monitoring for occurrence of a plug-in event, and recalculating available power of the relatively low-voltage battery based on charging performed during the plug-in event.

[0023] In some embodiments, the method further includes, within the remote server device, mapping a list of multiple available air activity updates to be operated for the vehicle group using the contextual awareness information, and sending the list of multiple available air activity updates to the vehicle group, including sending relevant portions of the list of multiple available air activity updates to the vehicles.

[0024] The present invention may also include the following technical solutions:

[0025] 1. A system for providing updates to software in a vehicle to be updated, comprising:

[0026] a remote server device configured to provide over-the-air activity updates to the vehicle to be updated; and

[0027] The vehicles to be updated include:

[0028] Devices including software configured to be upgraded via over-the-air updates;

[0029] A relatively low voltage battery that provides relatively low voltage DC power;

[0030] a relatively high voltage electric vehicle battery providing relatively high voltage DC power;

[0031] an accessory power module configured to convert relatively high voltage DC power to relatively low voltage DC power and including programming to estimate available power of a relatively low voltage battery;

[0032] Supervisory controller, including programming to:

[0033] Monitors available power from a relatively low voltage battery;

[0034] comparing available power from a relatively low voltage battery to a threshold power level;

[0035] commanding the accessory power module to convert the relatively high voltage DC power to provide relatively low voltage DC power when the available power of the relatively low voltage battery is equal to or less than a threshold power level;

[0036] Scheduling receipt of over-the-air activity updates based on available power of a relatively low voltage battery; and

[0037] Use over-the-air active updates to update your device's software.

[0038] 2. The system according to claim 1, wherein the supervisory controller further comprises programming for performing the following steps:

[0039] Assessing situational awareness factors; and

[0040] The estimated available power is re-evaluated based on context-aware factors.

[0041] 3. A system according to technical solution 2, wherein evaluating contextual awareness factors includes evaluating vehicle location, scheduling data, feature update list, timeline, average power degradation or temperature.

[0042] 4. The system according to claim 1, wherein the supervisory controller further comprises programming for performing the following steps:

[0043] monitoring the occurrence of insert events; and

[0044] Based on the charging performed during the insertion event, the available power of the relatively low voltage battery is recalculated.

[0045] 5. The system according to claim 1, wherein the remote server device includes programming for performing the following steps:

[0046] mapping a plurality of available air activity updates to be operated for the vehicle group using the situational awareness information; and

[0047] Sending the list of the plurality of available air activity updates to the group of vehicles includes sending a relevant portion of the list of the plurality of available air activity updates to the vehicles to be updated.

[0048] 6. The system according to claim 5, wherein the supervisory controller further comprises programming for performing the following steps:

[0049] Monitor situational awareness information of vehicles to be updated;

[0050] estimating an available time period in which to schedule receiving the plurality of air activity updates corresponding to the associated portion of the list of a plurality of available air activity updates based on available power of the relatively low voltage battery and the contextual awareness information; and

[0051] Receiving the plurality of air activity updates is scheduled based on an available time period.

[0052] 7. The system according to claim 6, wherein the supervisory controller further comprises programming for performing the following steps:

[0053] monitoring actual power consumption throughout an operating period including an available time period;

[0054] Comparing actual power consumption to a predicted power algorithm; and

[0055] When the actual power consumption exceeds the power consumption predicted by the predictive power algorithm, the available time period is adjusted based on the actual power consumption.

[0056] 8. A system for providing updates to software in a plurality of vehicles, comprising:

[0057] a remote server device configured to provide over-the-air activity updates to the plurality of vehicles; and

[0058] The plurality of vehicles, each of the plurality of vehicles comprising:

[0059] Devices including software configured to be upgraded via over-the-air updates;

[0060] A relatively low voltage battery that provides relatively low voltage DC power;

[0061] a relatively high voltage electric vehicle battery providing relatively high voltage DC power;

[0062] an accessory power module configured to convert relatively high voltage DC power to relatively low voltage DC power and including programming to estimate available power of a relatively low voltage battery;

[0063] Supervisory controller, including programming to:

[0064] Monitors available power from a relatively low voltage battery;

[0065] comparing available power from a relatively low voltage battery to a threshold power level;

[0066] commanding the accessory power module to convert the relatively high voltage DC power to provide relatively low voltage DC power when the available power of the relatively low voltage battery is equal to or less than a threshold power level;

[0067] Scheduling receipt of over-the-air activity updates based on available power of a relatively low voltage battery; and

[0068] Use over-the-air active updates to update your device's software.

[0069] 9. The system according to claim 8, wherein the supervisory controller further comprises programming for performing the following steps:

[0070] Assessing situational awareness factors; and

[0071] The estimated available power is re-evaluated based on context-aware factors.

[0072] 10. A system according to technical solution 9, wherein evaluating situational awareness factors includes evaluating vehicle location, scheduling data, feature update list, timeline, average power degradation or temperature.

[0073] 11. The system according to claim 9, wherein the remote server device includes programming for performing the following steps:

[0074] mapping a list of a plurality of available air activity updates to be operated for the plurality of vehicles; and

[0075] Sending the list of the plurality of available air activity updates to the plurality of vehicles includes sending a relevant portion of the list of the plurality of available air activity updates to each of the plurality of vehicles.

[0076] 12. The system according to claim 11, wherein the supervisory controller further comprises programming for performing the following steps:

[0077] estimating an available time period based on the available power of the relatively low voltage battery and the context awareness factor, in which the plurality of air activity updates corresponding to the associated portion of the list of available air activity updates are scheduled to be received; and

[0078] Receiving the plurality of air activity updates is scheduled based on an available time period.

[0079] 13. The system according to claim 12, wherein the supervisory controller further comprises programming for performing the following steps:

[0080] monitoring actual power consumption throughout an operating period including an available time period;

[0081] Comparing actual power consumption to a predicted power algorithm; and

[0082] When the actual power consumption exceeds the power consumption predicted by the predictive power algorithm, the available time period is adjusted based on the actual power consumption.

[0083] 14. The system according to claim 8, wherein the remote server device includes programming for performing the following steps:

[0084] identifying a group of vehicles within the plurality of vehicles to be updated with the same plurality of over-the-air activity updates;

[0085] assessing the available power of a relatively low voltage battery of each of the group of vehicles; and

[0086] Based on the evaluation, the plurality of air activity updates are scheduled to be transmitted simultaneously to each of the group of vehicles.

[0087] 15. The system according to claim 8, wherein the remote server device includes programming for performing the following steps:

[0088] identifying a group of vehicles within the plurality of vehicles to be updated with the same plurality of over-the-air activity updates;

[0089] assessing the available power of a relatively low voltage battery of each of the group of vehicles; and

[0090] Based on the evaluation, the plurality of air activity updates are scheduled for transmission in a time sequence to each of the group of vehicles.

[0091] 16. A method for providing updates to software in a vehicle, comprising:

[0092] In the vehicle:

[0093] Receive air activity updates from vehicles;

[0094] operating a device including software configured to be upgraded via over-the-air updates;

[0095] operating a relatively low voltage battery providing relatively low voltage DC power;

[0096] operating a relatively high voltage electric vehicle battery providing relatively high voltage direct current power;

[0097] operating an accessory power module configured to convert relatively high voltage DC power to relatively low voltage DC power and including programming to estimate available power of a relatively low voltage battery; and

[0098] In a computerized processor within the vehicle:

[0099] Monitors available power from relatively low voltage batteries;

[0100] comparing available power from a relatively low voltage battery to a threshold power level;

[0101] commanding the accessory power module to convert the relatively high voltage DC power to provide relatively low voltage DC power when the available power of the relatively low voltage battery is equal to or less than a threshold power level;

[0102] Scheduling receipt of over-the-air activity updates based on available power of a relatively low voltage battery; and

[0103] Use over-the-air active updates to update your device's software.

[0104] 17. The method according to technical solution 16 further comprises, in a computerized processor in the vehicle:

[0105] Assessing situational awareness factors; and

[0106] The estimated available power is re-evaluated based on context-aware factors.

[0107] 18. A method according to technical solution 17, wherein evaluating situational awareness factors includes evaluating vehicle location, scheduling data, feature update list, timeline, average power degradation or temperature.

[0108] 19. The method according to technical solution 16 further comprises, in a computerized processor in the vehicle:

[0109] monitoring the occurrence of insert events; and

[0110] Based on the charging performed during the insertion event, the available power of the relatively low voltage battery is recalculated.

[0111] 20. The method according to technical solution 16 further comprises, in the remote server device:

[0112] mapping a plurality of available air activity updates to be operated for the vehicle group using the situational awareness information; and

[0113] Sending the list of the plurality of available air activity updates to the group of vehicles includes sending relevant portions of the list of the plurality of available air activity updates to the vehicles.

[0114] The above features and advantages and other features and advantages of the present disclosure are readily apparent from the following detailed description of the best modes for carrying out the disclosure when taken in connection with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0115] Figure 1 Schematically illustrates a system for operating an OTA campaign according to the present disclosure;

[0116] Figure 2 schematically illustrates the operation of a supervisory controller within a vehicle according to the present disclosure;

[0117] Figure 3 Schematically illustrates the Figure 1 Remote server equipment;

[0118] Figure 4 Schematically illustrates the Figure 2 Operation of the accessory power module (APM);

[0119] Figure 5 It is a diagram illustrating the determination of when to start using according to the present disclosure Figure 2 A flow chart of a method for using a relatively high voltage EV battery to power low voltage vehicle equipment;

[0120] Figure 6 is a flow chart illustrating a method to utilize contextual awareness information to predict power usage over a period of time to improve scheduling of OTA activity updates in accordance with the present disclosure;

[0121] Figure 7 is a flow chart illustrating a method of adjusting or managing an Internet of Things (IoT) protocol connection timeline based on power degradation and power consumption cost metrics according to the present disclosure;

[0122] Figure 8 It is a diagram for illustrating the use of Figure 2 A flowchart of a method for a remote server device and a supervisory controller to coordinate information useful for scheduling IoT protocol intervals;

[0123] Fig. 9 It is a diagram for illustrating the use of Figure 1 A flowchart of a method for a remote server device to manage OTA activities of a vehicle unit; and

[0124] Fig.10 is a flow chart illustrating a method for updating interval optimization based on relatively low voltage power degradation for a pattern-based group according to the present disclosure. DETAILED DESCRIPTION

[0125] An electric vehicle (EV) may include multiple power systems and corresponding energy storage devices or batteries. In an exemplary configuration, the vehicle may include a high voltage power system that, for example, provides and stores electrical energy with direct current at a relatively high voltage (e.g., 400 volts, 600 volts, or 800 volts). Such a system may further include a power inverter that is useful for converting the higher voltage direct current electrical energy into alternating current electrical energy for use by an alternating current motor useful for powering the vehicle, and vice versa, so that the energy recovered by the motor can be stored by the battery of the high voltage power system. The vehicle may additionally include a low voltage power system that, for example, provides and stores electrical energy at a low voltage (e.g., 12 volts or the like). Vehicle accessory devices (such as radios, infotainment systems, vehicle controllers, etc.) operate at low voltages.

[0126] An EV can be described as being in a low power operating mode when the vehicle ignition is off, most vehicle systems are in sleep mode, and the vehicle is disconnected from the charging unit and operates solely on energy stored by the vehicle. During operation in the low power operating mode, power management is important in order to maintain and prioritize the operability and functionality of the vehicle and its features.

[0127] Over-the-air (OTA) activity can be described as a software update or data packet that a company or programming source can release. OTA activities can be used to update the software on the vehicle or provide content for vehicle accessory devices or systems such as infotainment systems. When the information is successfully transmitted from the source to the vehicle, the OTA activity is successful for the particular vehicle. When the information is not successfully transmitted to the vehicle, the transmission is incomplete, or the transmission is corrupted, the OTA activity is unsuccessful for the vehicle. When in a low-power operating mode, if the vehicle does not have power available to maintain the communication and computing systems useful for successfully receiving and processing OTA activities, then OTA activities for EVs may not be successful.

[0128] The information provided in the OTA activity can be communicated according to a plurality of various communication protocols. In one embodiment, an Internet of Things (IoT) protocol such as Message Queue Telemetry Transport (MQTT) can be used to implement the transmission of information. The IoT protocol is a lightweight, publish-subscribe, machine-to-machine network protocol for message queues / message queue services. It is designed for connection to remote locations with devices that have resource constraints or limited network bandwidth. The protocol runs on the Transmission Control Protocol / Internet Protocol (TCP / IP), or on other network protocols that provide ordered, lossless, bidirectional connections. The IoT protocol enables the use of a publish / subscribe messaging pattern that provides one-to-many message distribution and decoupling of applications. The IoT protocol includes a mechanism to notify interested parties when an abnormal disconnection occurs. Other communication protocols, such as short message / messaging service (SMS), can be used alternatively to implement OTA activities.

[0129] With the advent of end-to-end vehicle software platforms that allow frequent over-the-air software updates, there is a need for multi-mode push / pull features to coexist. For example, current models are not feasible in terms of power availability and utilization of feature OTA activities, particularly in low power mode at a minimum data rate of 5 Gigabytes per second to download features within a 10 minute time window.

[0130] Software updates, such as OTA activities, are important for maintaining vehicles. Unsuccessful update attempts can be costly. A method and system for dynamic power converter management in a vehicle are provided, wherein vehicle power utilization and conversion and remote software updates are managed in an electric vehicle in an ignition-off and unplugged / uncharged state. The method includes dynamically monitoring the power degradation rate using an accessory power module (APM). The APM includes a computerized controller configured to monitor electrical, thermal, and health status parameters of the vehicle power system and estimate power availability. The electrical power for vehicle accessories can be configured to operate at a relatively low voltage, such as 12 volts, using power supplied by a low voltage system such as a 12 volt battery. Once the APM estimates that the power availability of the low voltage power system is close to a threshold, a power converter is used to convert power from a high voltage power system (e.g., an EV battery pack) to facilitate the extended length of the scaled feature requirements of low voltage accessories when the vehicle is in a low power operating mode.

[0131] The disclosed method and system utilize power source optimization based on contextual awareness. Contextual awareness information may include vehicle location, schedule, feature update list, timeline, average power degradation, temperature, and other similar data to evaluate or re-evaluate power source usage based on feedback. Contextual awareness may enable the system to map the use of high voltage energy to provide low voltage energy for specific purposes at specific times during a predetermined low power mode timeline. In one embodiment, the power simulator analysis performed at each ignition state change may be provided to a remote server to perform contextual awareness determination of the vehicle.

[0132] Methods utilized in the prior art pre-schedule static data transfers / operations of an interactive environment based on average group behavior and ignition off duration.The disclosed method and system include dynamic transmission control protocol (TCP) optimization based on power consumption.

[0133] The disclosed method and system schedule the transmission of information during a defined IoT protocol interval. The system monitors power consumption at IoT protocol intervals. Power degradation can be defined as how much energy has been consumed by the vehicle overall or since the last determination. If the power degradation is greater than a defined threshold power degradation, the system can determine whether the power consumption rate is significant, i.e., greater than X%. If the power consumption rate is significant, the system can adjust the IoT protocol connection timeline based on a cost metric, i.e., the occurrence of the defined IoT protocol interval, to budget energy expenditure through a low power mode timeline. If the power consumption rate is not significant, the system can continue with the currently defined IoT protocol interval until the energy budget is consumed or until an insertion event occurs. In one embodiment, the adjustment to the IoT protocol connection can be configured to optimize the successful completion of OTA activity updates. In another embodiment, the adjustment to the IoT protocol connection can be configured to avoid performing OTA activity updates while initially busy converting power from a relatively high voltage EV battery. In another embodiment, the adjustment to the IoT protocol connection can be configured to avoid frequent updates that contribute to high energy draw from the battery system.

[0134] The disclosed method and system can determine TCP update interval optimization based on power availability and contextual awareness. The vehicle includes multiple features available based on the system providing power to appropriate accessory devices. The system can map a list of feature OTA activities or scheduled updates to each of the multiple accessory devices using contextual awareness. The system can send a list of feature OTA activities with details to the corresponding vehicle. Based on the sensing information and power availability, TCP sets the IoT protocol update interval ping duration based on power availability and feature request timeline.

[0135] A remote server device operating OTA activities can utilize OTA activity management based on determining the status of multiple vehicles to be updated. The multiple vehicles to be updated may include a relatively large number of vehicles. The bandwidth of the remote server device operating OTA activities may be limited, so the multiple vehicles can be divided into units, each of which includes a unit identification number. Each of the multiple vehicles can send channel state information to operate the IoT protocol interval, and the channel state information such as the unit identification number assigned to the vehicle and the availability of the vehicle. The remote server device operating OTA activities can determine whether the number of vehicles to be updated served in a particular unit exceeds a maximum throughput threshold. If the maximum throughput threshold is exceeded, the system can distribute the merged multi-OTA activity timeline across a defined time period at the cloud, and push the activities to the vehicle to save energy budget.

[0136] In one embodiment, a remote server device operating an OTA activity can monitor the degradation of each of the vehicles in a unit or group, and the system can determine or modulate the time and frequency of the IoT protocol update interval ping based on the state of the group. In one example, the group can be scheduled for updates based on the average condition of the vehicles in the group. In another example, the group can be scheduled for updates based on the vehicle with the greatest degradation in the group.

[0137] Figure 1 A system 10 for operating OTA activities is schematically illustrated. 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 illustrated as including a supervisory controller 210A, 210B, 210C and a wireless communication device 220A, 220B, 220C, respectively. The remote server device 100 can be remotely operated and operates OTA activities to provide updates to accessory devices and systems of the plurality of vehicles 200A, 200B, 200C. Each of the vehicles 200A, 200B, 200C communicates wirelessly with the remote server device 100 via a corresponding wireless communication device 220A, 220B, 220C.

[0138] Figure 2 The operation of the supervisory controller 210 in the vehicle is schematically illustrated. The supervisory controller 210 is Figure 1210A, 210B, 210C. The supervisory controller 210 is a computerized device and may include a processor configured to operate a programming code, a random access memory (RAM), and a persistent memory such as a hard drive. A relatively high voltage EV battery 250 is illustrated, which is connected to a power inverter 252, which in turn is connected to a motor 254, which includes an output shaft configured to provide power to the vehicle. A relatively low voltage battery 230 is also illustrated. The relatively low voltage battery 230 can be configured to store and provide electrical energy at 12 volts DC. An accessory power module (APM) 240 is also illustrated. The APM 240 is configured to selectively convert relatively high voltage electrical power from the relatively high voltage EV battery 250 to provide relatively low voltage electrical power to the relatively low voltage battery 230 and other vehicle accessories and systems, which are supplied with electrical power at a relatively low voltage supplied by the relatively low voltage battery 230. The APM 240 may include power metering to measure or estimate the total amount of electrical energy consumed by the relatively high voltage EV battery 250 to supply relatively low voltage electrical power. Further, the APM 240 may include programming to operate a predictive power algorithm. The algorithm may monitor factors such as electrical factors, thermal factors, and battery health status 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 supervisory controller 210, and the supervisory controller 210 is provided with a measurement of how much energy the vehicle consumes during the low power operating mode and when a threshold amount of available energy will be reached throughout the time period of the low power operating mode.

[0139] The supervisory controller 210 communicates with the remote server device 100 via the wireless communication device 220. The supervisory controller 210 can receive data via the communication device 220 and store data from the remote server device 100, the data including executable or activatable software updates for the vehicle system. An exemplary telematics device 260 and an exemplary vehicle navigation device 270 are illustrated. A plurality of additional or alternative vehicle devices or systems may be configured to receive software updates from the remote server device 100 via the supervisory controller 210. The receiving or method steps of receiving OTA activity updates from the remote server device 100 may include a wake-up event of the supervisory controller. In the low-power operating mode, when the ignition is turned off and charging of the vehicle battery 230, 250 does not occur, the vehicle system including the supervisory controller 210 may be placed in a sleep mode or non-functional state to reduce or eliminate the electrical power drawn from the system. In order to receive data related to the OTA activity update, the supervisory controller 210 undergoes a wake-up event, electrical power is supplied to the supervisory controller 210 for a duration or time period, and once the OTA activity update is received, the next method step may occur. In one embodiment, the supervisory controller 210 may confirm that the OTA activity update was properly received and stored, the time period may end, and the data from the OTA activity update may be accessed and executed the next time the ignition is turned on. In another embodiment, the supervisory controller 210 may receive data from the OTA activity update and may execute the update on one of the devices 260, 270 before the time period ends and the supervisory controller returns to sleep mode.

[0140] The remote server device 100 may request or announce that an OTA activity update is available or should be scheduled for receipt by the supervisory controller 210. The supervisory controller 210 may utilize the request and estimate of available power to schedule IoT protocol intervals to receive OTA activity updates.

[0141] Figure 3 Schematically illustrates Figure 1 The remote server device 100 includes a computerized processing device 110, a communication device 120, an input / output coordination device 130, and a memory storage device 140. Note that the remote server device 100 may include other components, and some of the components are not present in some embodiments.

[0142] The processing device 110 may include a memory storing processor executable instructions, such as a read-only memory (ROM) and a random access memory (RAM), and one or more processors executing processor executable instructions. In an embodiment in which 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 an operating system of a remote server device 100. The processing device 110 may include one or more modules that execute a programming code or a computerized process or method including executable steps. The illustrated modules may include functionality of a single physical device or across multiple physical devices. The processing device 110 may further include programming modules, including an OTA active update module 112, a data transfer module 114, and a unit update module 116.

[0143] The communication device 120 may include a communication / data connection to a bus device configured to transmit data to the different components of the system, and may include one or more wireless transceivers for performing wireless communications.

[0144] The input / output coordination device 130 includes hardware and / or software configured to enable the processing device 110 to utilize the onboard resources of the remote server device 100 to receive and / or exchange data, including input / output devices, microphones, speakers, and buttons installed to the remote server device 100.

[0145] The memory storage device 140 is a device that stores data generated or received by the remote server device 100. The memory storage device 140 may include, but is not limited to, a flash memory or a solid-state memory.

[0146] The OTA activity update module 112 includes programming to enable the remote server device 100 to receive and schedule OTA activities. The OTA activity update module 112 may include information to determine or segment which vehicles among a group of vehicles should get a particular update. Such a determination may include determining which vehicles have a particular feature installed, have a particular generation of equipment installed, have a subscription service activated for receiving updates, or other similar criteria.

[0147] The data transfer module 114 includes programming to perform data transfer events with vehicles. The data transfer module 114 may include programming specific to the protocol used for data transfer (e.g., an IoT protocol). The data transfer module 114 may access stored data files, establish communications with one or more vehicles, transmit stored data files, and confirm the validity of the data transfer. The data transfer module 114 may include programming to track a list of vehicles and store data related to which vehicles have received which updates.

[0148] The unit update module 116 includes programming to set up and track units or groups of vehicles, determine a threshold throughput based on how many vehicles the remote server device 100 can update simultaneously, and divide OTA activity events by vehicle unit and threshold throughput.

[0149] Remote server device 100 is provided as an exemplary computerized device capable of executing programming code to operate the disclosed systems and methods. Multiple different embodiments of remote server device 100 and modules operable therein are contemplated, and the present disclosure is not intended to be limited to the examples provided herein.

[0150] Figure 4 Schematically illustrates Figure 2 Operation of the APM 240 of the vehicle. The APM 240 is illustrated as including programming to receive inputs and determine the estimated available power of the vehicle battery 230. Input 241 includes the voltage entering (in of) the battery 230. Input 242 includes the current entering the battery 230. Input 243 includes the voltage leaving (out of) the battery 230. Input 244 includes the current leaving the battery 230. Input 245 includes the temperature of the battery 230. Output 246 includes the power leaving the battery 230. Output 247 is the available power of the battery 230. Output 248 includes the maximum current of the battery 230.

[0151] Figure 5 It is a graphic to determine when to start using Figure 2 A flowchart of a method 300 for powering low voltage vehicle equipment with a relatively high voltage EV battery 250. The method 300 may be Figure 2 In another embodiment, the method 300 may be performed within the supervisory controller 210. Figure 22. The method 300 is operated within the APM 240 of the vehicle. When the vehicle is in the low power operating mode, the method 300 is activated and begins at step 302. At step 304, an estimate of periodic or dynamic operation of accessory power module degradation is checked. This estimate of accessory power module degradation is a measure of how much power has been used from the relatively low voltage battery 230 so far during the low power operating mode. At step 306, the estimate of accessory power module degradation is compared to a threshold power degradation. If the estimate of accessory power module degradation is not yet equal to or greater than the threshold power degradation, the method 300 returns to step 304, where the estimate of accessory power module degradation is periodically or dynamically re-estimated. If the estimate of accessory power module degradation is equal to or exceeds the threshold power 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 relatively high voltage DC power of the relatively high voltage EV battery 250 into relatively low voltage DC power utilized by the vehicle systems. Power may be supplied by the relatively high voltage EV battery 250 for a period of time until a threshold amount of power degradation of the relatively high voltage EV battery 250 has occurred, at which point some other remedial steps may be taken, such as alerting a user. At step 310, the method 300 ends. The method 300 includes exemplary steps for managing electrical power from the first relatively low voltage battery 230 and from the second relatively high voltage EV battery 250. A number of additional and / or alternative steps are contemplated, and the present disclosure is not intended to be limited to the examples provided herein.

[0152] Figure 6 4 is a flow chart illustrating a method 400 for utilizing contextual awareness information to predict power usage over a period of time to improve the scheduling of OTA activity updates. The method 400 is initiated when the vehicle is in a low power operating mode and begins at step 402. At step 404, monitoring is performed on the Figure 2 The inputs are processed and contextual awareness information is generated. The contextual awareness information may include vehicle location, a schedule of events related to power usage in the low power operating mode, a list of features to be updated by OTA activity updates, a timeline of factors such as historical charging events and future navigation routes entered by the user, average power degradation of the vehicle, and temperature. At step 408, the predicted power degradation over a time period may be updated or re-evaluated based on the contextual awareness information. At step 410, a determination is made as to whether power usage in the low power operating mode is appropriate. Figure 2The APM 240 is used to utilize the relatively high voltage electric power to supply the relatively low voltage electric power. At step 412, at each ignition on event, the optimized power simulator analysis useful for scheduling OTA activity updates is transmitted to Figure 2 The remote server device 100 of FIG. 414 ends the method 400. The method 400 includes exemplary steps for planning or predicting power degradation by utilizing contextual awareness information through a low power operating mode. A number of additional and / or alternative steps are contemplated, and the present disclosure is not intended to be limited to the examples provided herein.

[0153] Figure 7 is a flow chart illustrating a method 500 for adjusting or managing IoT protocol connection timelines based on power degradation and power consumption cost metrics. The method 500 is initiated when the vehicle is in a low power operating mode and begins at step 502. At step 504, Figure 2 The supervisory controller 210 monitors power consumption at each IoT protocol interval or at each wake-up event scheduled to receive OTA activity updates. At step 506, a determination is made whether the total power degradation meets or exceeds the threshold power degradation. If the total power degradation does not meet or exceed the threshold power degradation, the method 500 proceeds to step 508. If the total power degradation meets or exceeds the threshold power degradation, the method 500 proceeds to step 516.

[0154] At step 508, it is determined whether the current power consumption rate is less than a threshold power consumption. The threshold power consumption value may include external factor adjustments for variables such as time of day or temperature. If the current power consumption rate is less than the threshold power consumption, the method 500 proceeds to step 510, where the IoT protocol connection timeline is adjusted based on the cost metric. If the current power consumption rate is not less than the threshold power consumption, the method 500 proceeds to step 518. At step 518, the current IoT protocol interval continues until the energy budget is consumed. At step 520, once the energy budget is consumed, the supervisory controller may switch from IoT protocol operation to an alternative connection method based on the cost metric.

[0155] At step 512, an insertion charging event is monitored. At step 514, the battery limits are recalculated based on how much battery charging occurs (e.g., the available power of a relatively low voltage battery is recalculated). The method then proceeds to step 510, where the IoT protocol connection timeline is adjusted based on the cost metric. At step 522, method 500 ends. Method 500 may be repeated. Method 500 includes exemplary steps for adjusting or managing IoT protocol connection timelines based on power degradation and power consumption cost metrics. A number of additional and / or alternative steps are envisioned, and the present disclosure is not intended to be limited to the examples provided herein.

[0156] Figure 8 It is a graphic Figure 2 A flowchart of a method 600 in which a remote server device 100 and a supervisory controller 210 coordinate information useful for scheduling IoT protocol intervals. When a vehicle is in a low-power operating mode, the method 600 is initiated and starts at step 602. At step 604, the remote server device 100 maps a list of available OTA activity updates to be operated for the vehicle using contextual awareness information. At step 606, the remote server device 100 sends a list of available OTA activity updates to the corresponding vehicle. At step 608, the supervisory controller 210 in one of the vehicles monitors the contextual awareness information of the vehicle and the estimated power availability, and estimates the available time period in which the IoT protocol interval is operated to receive the OTA activity update. At step 610, the supervisory controller 210 sets the IoT protocol interval ping duration based on the estimated power availability and the list of available OTA activity updates. In an exemplary calculation, the vehicle may determine that a 55-minute IoT protocol interval is optimal for a nine-day budget in a low-power operating mode. At step 612, after each IoT protocol interval, the actual power consumption is monitored and compared with the predicted power consumption value from the estimated power availability. If the actual power consumption is greater than the predicted power consumption value, 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. At step 616, the method 600 ends. The method 600 includes Figure 2 The remote server device 100 and the supervisory controller 210 coordinate information useful for scheduling IoT protocol intervals based on power consumption in the EV vehicle in the low power operating mode. A number of additional and / or alternative steps are envisioned, and the present disclosure is not intended to be limited to the examples provided herein.

[0157] Fig. 9 It is a graphic Figure 1Flowchart of a method 700 for managing OTA activities of vehicle 200A, 200B, 200C units by a remote server device 100. Method 700 starts at step 702. At step 704, the remote server device 100 identifies the OTA activities to be sent to at least one vehicle unit or group, and sends a query to available vehicles for information. At step 706, the units of vehicles 200A, 200B, 200C respond to the query with information useful for coordinating the operation of OTA activities. The information may include a unit identification number for each vehicle 200A, 200B, 200C, a schedule of IoT protocol intervals for each vehicle 200A, 200B, 200C, and the communication bandwidth available for each vehicle 200A, 200B, 200C. At step 708, the remote server device 100 uses the provided information to quantify the existing vehicle units and determine a throughput threshold or the maximum number of vehicles to be updated for which the remote server device 100 can provide OTA activity updates simultaneously. If the number of vehicles in the existing vehicle unit exceeds the throughput threshold of the remote server device 100, the method 700 proceeds to step 712, where the remote server device 100 distributes the OTA activity across a defined timeline, where each vehicle 200A, 200B, 200C is assigned a time "T" and receives the OTA activity update at that time. If the number of vehicles in the existing vehicle unit does not exceed the throughput threshold of the remote server device 100, the method 700 proceeds to step 710, where the remote server device pushes the activity to the existing vehicle units simultaneously. The method 700 ends at step 714. The method 700 includes Figure 1 The remote server device 100 of the present invention manages exemplary steps of OTA activities of vehicle 200A, 200B, 200C units. A variety of additional and / or alternative steps are envisioned, and the present disclosure is not intended to be limited to the examples provided herein.

[0158] Fig.10 8 is a flow chart illustrating a method 800 for updating interval optimization based on relatively low voltage power degradation for a pattern-based group. The method 800 begins at step 802. At step 804, Figure 1The remote server device 100 identifies the vehicle 200A, 200B, 200C group using a patterned feature update schedule or a schedule that is common and expected and appropriately updated for each of the vehicle 200A, 200B, 200C groups. At step 806, the remote server device queries and maintains a power availability list based on power availability information provided by each of the vehicle 200A, 200B, 200C groups. This information can be provided in a power conversion state, for example, each time a wake-up event occurs on each of the vehicles 200A, 200B, 200C or an ignition-on event occurs. At step 808, the remote server device 100 determines whether any of the vehicles 200A, 200B, 200C is experiencing a power degradation greater than the average power degradation value. If one of the vehicles is experiencing a power degradation greater than the average power degradation value, the method 800 proceeds to step 810, where the remote server device 100 can send feedback to the vehicle experiencing greater power degradation. The feedback may include exposure time information, cycle life information, and a recommended IoT protocol interval duration. If no vehicle is experiencing power degradation greater than the average power degradation value, the method 800 proceeds to step 812, where common update interval feedback is sent by the remote server device 100 to the vehicles 200A, 200B, 200C based on the predicted feature update timeline. The method 800 ends at step 814. The method 800 includes exemplary steps for pattern-based groups to update interval optimization based on relatively low voltage power degradation. A number of additional and / or alternative steps are envisioned, and the present disclosure is not intended to be limited to the examples provided herein.

[0159] 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 practicing the disclosure within the scope of the appended claims.

Claims

1. A system for providing updates to software in a vehicle to be updated, comprising: a remote server device configured to provide over-the-air activity updates to vehicles to be updated; and The vehicles to be updated include: Devices including software configured to be upgraded via over-the-air updates; A relatively low voltage battery that provides relatively low voltage DC power; a relatively high voltage electric vehicle battery providing relatively high voltage DC power; an accessory power module configured to convert relatively high voltage DC power to relatively low voltage DC power and including programming to estimate available power of a relatively low voltage battery; Supervisory controller, including programming to: Monitors available power from relatively low voltage batteries; comparing available power from a relatively low voltage battery to a threshold power level; commanding the accessory power module to convert the relatively high voltage DC power to provide relatively low voltage DC power when the available power of the relatively low voltage battery is equal to or less than a threshold power level; Scheduling receipt of over-the-air activity updates based on available power of a relatively low voltage battery; and Use over-the-air active updates to update your device's software.

2. The system of claim 1, wherein the supervisory controller further comprises programming to: Assessing situational awareness factors; and The estimated available power is re-evaluated based on context-aware factors. 3 . The system of claim 2 , wherein evaluating contextual awareness factors comprises evaluating vehicle location, scheduling data, feature update lists, timelines, average power degradation, or temperature.

4. The system of claim 1, wherein the supervisory controller further comprises programming to: monitoring the occurrence of insert events; and Based on the charging performed during the insertion event, the available power of the relatively low voltage battery is recalculated.

5. The system of claim 1, wherein the remote server device includes programming to: mapping a plurality of available air activity updates to be operated for the vehicle group using the situational awareness information; and Sending the list of the plurality of available air activity updates to the group of vehicles includes sending a relevant portion of the list of the plurality of available air activity updates to the vehicles to be updated.

6. The system of claim 5, wherein the supervisory controller further includes programming to: Monitor situational awareness information of vehicles to be updated; estimating an available time period in which to schedule receiving the plurality of air activity updates corresponding to the associated portion of the list of a plurality of available air activity updates based on available power of the relatively low voltage battery and the contextual awareness information; and Receiving the plurality of air activity updates is scheduled based on an available time period.

7. The system of claim 6, wherein the supervisory controller further includes programming to: monitoring actual power consumption throughout an operating period including an available time period; Comparing actual power consumption to a predicted power algorithm; and When the actual power consumption exceeds the power consumption predicted by the predictive power algorithm, the available time period is adjusted based on the actual power consumption.

8. A system for providing updates to software in a plurality of vehicles, comprising: a remote server device configured to provide over-the-air activity updates to the plurality of vehicles; and The plurality of vehicles, each of the plurality of vehicles comprising: Devices including software configured to be upgraded via over-the-air updates; A relatively low voltage battery that provides relatively low voltage DC power; a relatively high voltage electric vehicle battery providing relatively high voltage DC power; an accessory power module configured to convert relatively high voltage DC power to relatively low voltage DC power and including programming to estimate available power of a relatively low voltage battery; Supervisory controller, including programming to: Monitors available power from relatively low voltage batteries; comparing available power from a relatively low voltage battery to a threshold power level; commanding the accessory power module to convert the relatively high voltage DC power to provide relatively low voltage DC power when the available power of the relatively low voltage battery is equal to or less than a threshold power level; Scheduling receipt of over-the-air activity updates based on available power of a relatively low voltage battery; and Use over-the-air active updates to update your device's software.

9. The system of claim 8, wherein the supervisory controller further includes programming to: Assessing situational awareness factors; and The estimated available power is re-evaluated based on context-aware factors.

10. A method for providing updates to software in a vehicle, comprising: In the vehicle: Receive air activity updates from vehicles; operating a device including software configured to be upgraded via over-the-air updates; operating a relatively low voltage battery providing relatively low voltage DC power; operating a relatively high voltage electric vehicle battery providing relatively high voltage direct current power; operating an accessory power module configured to convert relatively high voltage DC power to relatively low voltage DC power and including programming to estimate available power of a relatively low voltage battery; and In a computerized processor within the vehicle: Monitors available power from relatively low voltage batteries; comparing available power from a relatively low voltage battery to a threshold power level; commanding the accessory power module to convert the relatively high voltage DC power to provide relatively low voltage DC power when the available power of the relatively low voltage battery is equal to or less than a threshold power level; scheduling receiving over-the-air activity updates based on available power of a relatively low voltage battery; and Use over-the-air active updates to update your device's software.

Images