Method and system for client-less vehicle software updates

Abstract

Systems and methods for vehicle software updates via an over-the-air (OTA) integrated charging station are provided herein. In one example, a method of an OTA integrated charging station includes establishing communication between a computing system of the OTA integrated charging station and a vehicle computing system of an electric vehicle; determining one or more vehicle details of the electric vehicle from the vehicle computing system; establishing communication between the computing system and an original equipment manufacturer (OEM) system; retrieving a software update from the OEM system based on the one or more vehicle details; and updating the vehicle computing system via a software installer of the vehicle computing system.

Description

Technical Field

[0001] The present disclosure relates to vehicle software updates, and more particularly to clientless vehicle software updates via a vehicle charging station. Background Art

[0002] For example, an electronic control unit (ECU) in an electric vehicle is responsible for managing and controlling various aspects of the vehicle's operation. An ECU in an electric vehicle includes several subsystems configured for specific functions. For example, an ECU may include a battery management system, a motor controller, a thermal management system, a charge controller, and the like. Furthermore, the ECU is equipped with software and / or firmware to execute control algorithms, respond to inputs, and manage the vehicle's various subsystems. This ECU's software and / or firmware periodically requires updates to enhance features, resolve issues, and / or otherwise update the software / firmware.

[0003] Software / firmware updates can be performed wirelessly via a wired connection or over-the-air (OTA). When performed via a wired connection, software updates are typically performed at a dealership or other maintenance or service facility equipped to service the original equipment manufacturer (OEM). However, vehicles typically visit dealerships or other maintenance facilities for scheduled maintenance procedures less frequently than required software updates. Furthermore, the cost and inconvenience of making a special trip to a dealership or maintenance facility for software updates can be a deterrent for drivers. OTA software updates offer an alternative to on-site software updates, whereby software is updated via WiFi or other wireless connections. However, in many cases, vehicles may not have reliable or regular access to WiFi or other wireless connections (such as cellular connections), or drivers may not want to incur the cost of using WiFi or cellular data to perform large software updates. Furthermore, updating software OTA requires vehicle downtime, which can be inconvenient for drivers. All of the above issues result in vehicles being updated to the latest software configuration at irregular intervals. Furthermore, pre-integrating OTA clients across multiple vehicle models requires significant processing power and storage and is very time-consuming. Consequently, OEM production runs may include vehicles that do not support OTA, which still require on-site software updates. Summary of the Invention

[0004] In one or more embodiments, a method for an OTA integrated charging station includes establishing communication between a computing system of the OTA integrated charging station and a vehicle computing system of an electric vehicle; determining one or more vehicle details of the electric vehicle from the vehicle computing system; establishing communication between the computing system and an original equipment manufacturer (OEM) system; retrieving a software update from the OEM system based on the one or more vehicle details; and installing the software update to the vehicle computing system via a software installer of the vehicle computing system.

[0005] A vehicle computing system replenishment method includes: establishing communication with an over-the-air (OTA) integrated charging station computing system; sending one or more vehicle details to the OTA integrated charging station computing system; and receiving a software update from the OTA integrated charging station computing system based on the one or more vehicle details.

[0006] In this way, the computing system of the OTA-integrated charging station can communicate with both the vehicle computing system and the OEM system. The charging station can therefore represent the vehicle when communicating with the OEM system to retrieve software updates for the vehicle. In this way, a reliable Wi-Fi or cellular data connection for the vehicle may not be a factor in obtaining OTA software updates, the vehicle can undergo frequent software updates to maintain optimal operation, and the queue of vehicles awaiting OTA software updates from the OEM system can be reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The present disclosure may be better understood by reading the following description of non-limiting embodiments with reference to the accompanying drawings, in which:

[0008] Figure 1 An exemplary software update system according to one or more embodiments of the present disclosure is shown;

[0009] Figure 2 shows an example partial view of a vehicle cabin including an instrument panel according to one or more embodiments of the present disclosure;

[0010] Figure 3 A block diagram illustrating an example onboard computing system of a vehicle configured to receive software updates from a charging station according to one or more embodiments of the present disclosure is shown;

[0011] Figure 4 A first scenario for establishing communication between a charging station and a vehicle according to one or more embodiments of the present disclosure is shown;

[0012] Figure 5 A second scenario for establishing communication between a charging station and a vehicle according to one or more embodiments of the present disclosure is shown;

[0013] Figure 6 A third scenario for establishing communication between a charging station and a vehicle according to one or more embodiments of the present disclosure is shown;

[0014] Figure 7 A method of a charging station for retrieving and installing a software update for a vehicle according to one or more embodiments of the present disclosure is shown; and

[0015] Figure 8 A method for a vehicle to install a software update from a charging station is shown according to one or more embodiments of the present disclosure. DETAILED DESCRIPTION

[0016] The following description relates to systems and methods for updating electric vehicle software via an over-the-air (OTA) client-integrated charging station. In some examples, the charging station may include an OTA integration subsystem within its computing system that communicates with the original equipment manufacturer (OEM) system to retrieve software updates for the vehicle. The charging station may also communicate with the vehicle to retrieve vehicle details to determine applicable software updates from the OEM system. The charging station may represent the vehicle when communicating with the OEM system to retrieve software updates via OTA technology. Figure 1 An exemplary vehicle software update system including a vehicle, a charging station, and an OEM system is shown. Figure 2 An example partial view of a vehicle cabin including an instrument panel is shown. Figure 3 An example onboard computing system of a vehicle configured to receive software updates from a charging station is shown. Figures 4 to 6 Various methods of establishing a communication connection between a vehicle and a charging station are shown. Figure 7 and Figure 8 A method for implementing vehicle software updates using an OTA integrated client on a charging station is shown in FIG.

[0017] The electronic control unit (ECU) of an electric vehicle is responsible for managing and controlling various aspects of the vehicle's operation. The ECU in an electric vehicle includes several subsystems, such as a battery management system, a thermal management system, etc. The ECU operates based on stored software and / or firmware, and the ECU is configured to execute instructions, algorithms, etc. to manage the vehicle's subsystems during operation. Such software and / or firmware of the ECU periodically requires updating to enhance features, resolve issues, and / or otherwise update the software / firmware. Additionally, storing a large number of currently operating software configurations may put a strain on the processing power of the OEM system, so regular software updates are preferred for both the vehicle and the OEM.

[0018] Software updates can be performed over a wired connection or wirelessly over-the-air (OTA). When performed over a wired connection, software updates are typically performed at a dealership or other maintenance or service facility equipped to service the OEM. However, vehicles typically visit dealerships or other maintenance facilities for scheduled maintenance procedures less frequently than required software updates. Furthermore, the cost and inconvenience of making a special trip to a dealership or maintenance facility for software updates can be a deterrent for drivers. OTA software updates offer an alternative to on-site software updates, whereby software is updated over Wi-Fi or other wireless connections. However, in many cases, vehicles may not have reliable or regular access to Wi-Fi or other wireless connections (such as cellular), or drivers may not want to incur the cost of using Wi-Fi or cellular data to perform large software updates. Furthermore, updating software OTA requires vehicle downtime, which can be inconvenient for drivers. All of these issues result in vehicles being updated to the latest software configuration at irregular intervals. Furthermore, pre-integrating an OTA client on every vehicle model requires significant processing power and storage and is very time-consuming. Furthermore, integrating and testing the OTA client into the vehicle's computing system requires increased manufacturing time and engineering effort. Consequently, OEM production runs may include vehicles that do not support OTA, which still require on-site software updates.

[0019] Figure 1 A vehicle software update system 100 is shown that includes a vehicle computing system 102 of an electric vehicle 101 and a computing system 142 of a charging system 141. The charging system 141 may be an electric vehicle charging station configured to provide power to the electric vehicle 101. The electric vehicle 101 may be a car, bus, truck, or a different type of machine or vehicle operated by an operator. The electric vehicle 101 may be a battery electric vehicle (BEV), a plug-in hybrid electric vehicle (PHEV), or other type of vehicle that uses electricity and is configured to have a battery therein that is charged via a charging station. Furthermore, while an electric vehicle is described herein, it should be understood that other types of vehicles that receive power via a charging station, such as hydrogen-powered vehicles, may also be applied without departing from the scope of this disclosure.

[0020] The vehicle computing system 102 includes one or more processors 106 configured to execute machine-readable instructions stored in the non-transitory memory 104. Similarly, the computing system 142 of the charging system 141 includes one or more processors 146 configured to execute machine-readable instructions stored in the non-transitory memory 144. The memory 104 and other memories mentioned herein may include one or more data storage structures, such as optical memory devices, magnetic memory devices, or solid-state memory devices, for storing programs and routines executed by the processor 106 to perform the various functions disclosed herein. The memory 104 may include any desired type of volatile and / or non-volatile memory, such as, for example, static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, read-only memory (ROM), etc.

[0021] Processor 106 and other processors mentioned herein (including processor 146) can be, for example, any suitable processor, processing unit or microprocessor. Processor 106 can be a multi-processor system and therefore can include one or more additional processors that are identical or similar to each other and communicatively coupled via an interconnect bus. Processor 106 can be single-core or multi-core, and the program executed thereon can be configured for parallel or distributed processing. In some embodiments, processor 106 can optionally include separate components distributed in two or more devices, which can be remotely located and / or configured for coordinated processing. In some examples, one or more aspects of processor 106 can be virtualized and executed by a remotely accessible networked computing device configured in a cloud computing platform.

[0022] The vehicle computing system 102 may include one or more vehicle software systems 108. The vehicle software systems 108 may each include software 110. The software 110 may be stored in the non-transitory memory 106 and may include instructions for executing programs, algorithms, and the like to control, manage, and respond to various systems of the vehicle, such as the battery management system, thermal management system, and the like. The software 110 stored in the memory may be the currently uploaded or downloaded version of the operating software specific to the vehicle. For example, the type of vehicle (including make, model, year, and the like) may inform the vehicle computing system 102 of the available operating software options.

[0023] The software 110 may include firmware, operating software, applications, services, and / or vehicle configuration data. The software 110 may be updateable. For example, a software installer 112 may be included in one or more vehicle software systems 108. The software installer 112 may be configured to install different, typically newer, versions of the software. Typically, the software installer 112 enables software flashing from an external tool at a service provider (e.g., a dealer service facility, a maintenance facility, etc.). The external tool referred to herein may be a diagnostic tool utilizing a protocol such as Unified Diagnostic Service (UDS). The newly installed software may replace the existing software with the software 110 stored in memory. One or more vehicle software systems 108 may be configured with various methods for installing software. For example, one or more vehicle software systems 108 may be configured for direct installation, whereby the source of the new operating software is connected via a dedicated data cable (e.g., an Ethernet cable) or other type of data channel. Additionally or alternatively, one or more vehicle software systems 108 may be configured for remote installation, for example, via wireless communication (such as via WiFi communication, vehicle-to-everything (V2X) communication, cellular data communication, or other types of wireless communication). As previously mentioned, OTA technology allows software updates (including, for example, bug fixes, security patches, and new features) to be delivered remotely to a vehicle without requiring the vehicle to be taken to a service station for the software update. However, as previously mentioned, storing software configurations in a queue for vehicles installed via OTA requires significant storage and processing power on the OEM system 161.

[0024] The electric vehicle 101 may be configured to couple to a charging system 141 or otherwise connect to the charging system to establish communication between the electric vehicle and the charging system. The charging system 141 may be a charging station, such as a public service station or a private charging station. The charging system 141 may provide power to the electric vehicle 101 to charge the battery of the electric vehicle. The charging system 141 may include a charging cable to deliver power to the electric vehicle 101.

[0025] As described above, charging system 141 may include computing system 142. Computing system 142 may be configured to communicate with vehicle computing system 102 via OTA technology and / or wired technology, which will be further described below. In some examples, charging system 141 may be an OTA integrated system. Computing system 142 may include non-transitory memory 144, which stores instructions executable by processor 146. Computing system 142 may also include OTA client 148. OTA client 148 may be configured for one or more types of communication programmed via OTA. OTA client 148 may include at least two subsystems. For example, OTA client 148 may include OEM communication subsystem 150 and vehicle communication subsystem 152. OEM communication subsystem 150 of OTA client 148 may be configured to communicate with OEM system 161, and vehicle communication subsystem 152 may be configured to communicate with vehicle computing system 102.

[0026] OEM system 161 may include a vehicle software module 164 stored in non-transitory memory 162. Similar to the other non-transitory memories described herein, non-transitory memory 162 may include one or more data storage structures, such as optical memory devices, magnetic memory devices, or solid-state memory devices, for storing programs and routines executable by the processor. Vehicle software module 164 may include multiple operating system software configurations for multiple vehicles, including both currently used software and software updates.

[0027] The OEM communication subsystem 150 can be configured to communicate with the OEM system 161 (specifically, the vehicle software module 164) via OTA programming (such as WiFi or cellular data) to retrieve software updates for a given vehicle. The vehicle communication subsystem 152 can be configured to communicate with one or more vehicle software systems 108 to deliver the retrieved software updates to the vehicle 101. The vehicle communication subsystem 152 can be configured to communicate via OTA programming and / or via a wired connection.

[0028] The electric vehicle 101 may also include a display screen 116, which will be referred to as Figure 2 Further described, the display screen 116 may be part of an in-vehicle infotainment system configured to display various elements, including alerts, pop-ups, etc., with which a user (eg, a driver) may interact.

[0029] Figure 2 An example partial view of the interior of a vehicle cabin 200 of a vehicle 202 in which a driver and / or one or more passengers may be seated is shown. The vehicle 202 may be Figure 1 A non-limiting example of an electric vehicle 101 is shown and described above.

[0030] Figure 2 The vehicle 202 may be a motor vehicle including drive wheels (not shown) and a power source 204 (such as an internal combustion engine and / or a battery) configured to provide torque to the drive wheels. In examples where the power source 204 includes an internal combustion engine, the internal combustion engine may include one or more combustion chambers that may receive intake air via an intake passage and exhaust combustion gases via an exhaust passage. The vehicle 202 may be a road car as well as other types of vehicles. In some examples, the vehicle 202 may include a hybrid propulsion system that includes an energy conversion device that is operable to absorb energy from vehicle motion and / or the engine and convert the absorbed energy into an energy form suitable for storage by an energy storage device. In some examples, the vehicle 202 may be an all-electric vehicle that includes a fuel cell, a solar energy capture element, and / or other energy storage system for providing electricity to the vehicle.

[0031] As shown, the vehicle 202 may include an instrument panel 206 having various displays and controls accessible to a human driver (also referred to as a user and / or occupant) of the vehicle 202. For example, the instrument panel 206 may include an onboard computing system (e.g., Figure 1 The touch screen 208 and the instrument cluster 210 of the vehicle computing system 102 of the vehicle. The touch screen 208 can receive user input to the vehicle computing system for controlling visual display output, user preferences, control parameter selection, etc. Figure 2 The example system shown includes controls that can be executed via a user interface of the onboard computing system (such as touch screen 208) without a separate control panel, but in other embodiments, the vehicle may include an additional control panel. In some embodiments, one or more hardware elements of the onboard computing system or 209, such as touch screen 208, display screen 211 (e.g., display screen 116), various control dials, knobs and buttons, memory, processor, and any interface elements (e.g., connectors or ports), may form an integrated head unit that is installed in the dashboard 206 of the vehicle. The head unit may be fixedly or removably attached to the dashboard 206. In additional or alternative embodiments, one or more hardware elements of the onboard computing system 209 may be modular and installable in multiple locations in the vehicle.

[0032] In some examples, during operation of vehicle 202, the onboard computing system may be configured to receive electronic signals from various sensors of vehicle 202. Additionally, the onboard computing system may be configured to update its software and install a new software configuration. As previously described, the onboard computing system may be configured to establish communication with an OTA client integrated charging station and receive software updates from the charging station. As an example, the charging station may determine vehicle details for vehicle 202 and then determine, via communication with the OEM system, whether updated software is available for vehicle 202. If a software update is available, the charging station may prompt vehicle 202 to display a message on display screen 211 indicating the availability of the software update, to which the user may enter a response indicating a desire to proceed with the installation of the software update.

[0033] Figure 3 A block diagram of an onboard computing system 209 integrated within a vehicle 202 is shown, wherein the onboard computing system 209 may be Figure 1 1. The onboard computing system 209 is a non-limiting example of a vehicle computing system 102 for an electric vehicle 101. In some examples, the onboard computing system 209 may be referred to herein as a controller and / or electronic controller. The onboard computing system 209 may perform one or more of the methods described herein in some embodiments. The onboard computing system 209 may include or be coupled to various vehicle systems, subsystems, hardware components, and software applications and systems that are or may be integrated into the vehicle 202.

[0034] The onboard computing system 209 may include one or more processors, including an operating system processor 314 and an interface processor 320. The operating system processor 314 may execute an operating system on the onboard computing system 209 and control input / output, display, and other operations of the onboard computing system 209. The interface processor 320 may interface with a vehicle control system 330 via an inter-vehicle system communication module 322.

[0035] The inter-vehicle system communication module 322 can output data to one or more other vehicle systems 331 and / or one or more other vehicle control elements 361, while also receiving data input from other vehicle systems 331 and other vehicle control elements 361, for example, via the vehicle control system 330. When outputting data, the inter-vehicle system communication module 322 can provide a signal corresponding to any state of the vehicle, the vehicle's surroundings, or the output of any other information source connected to the vehicle via the vehicle communication network. Vehicle data outputs may include, for example, analog signals (such as current speed), digital signals provided by separate information sources (such as a clock, a thermometer, a position sensor such as a GPS sensor, etc.), digital signals transmitted via a vehicle data network (such as an engine controller area network (CAN) bus through which engine-related information can be transmitted, a climate control CAN bus through which climate control-related information can be transmitted, and a multimedia data network through which multimedia data is transmitted between multimedia components in the vehicle). For example, the onboard computing system 209 may retrieve from the engine CAN bus the vehicle's current speed estimated by the wheel sensors, the vehicle's power status via the vehicle's battery and / or power distribution system, the vehicle's ignition status, the status of the vehicle's one or more airbags, the status of the vehicle's hazard lights, the vehicle's power source 204 (e.g., Figure 2 In addition, other connection means such as Ethernet may also be used without departing from the scope of the present disclosure.

[0036] A storage device 308 may be included in the onboard computing system 209 to store data, such as instructions executable by the operating system processor 314 and / or the interface processor 320, in a non-volatile form. The storage device 308 may store application data to enable the onboard computing system 209 to run applications for connecting to a cloud-based server and / or collecting information for transmission to a cloud-based server. The application may retrieve information collected by vehicle systems / sensors, input devices (e.g., user interface 318), data stored in one or more storage devices (such as volatile memory 319A or non-volatile memory 319B), devices communicating with the onboard computing system, and the like. The onboard computing system 209 may also include volatile memory 319A. The volatile memory 319A may be random access memory (RAM). Non-transitory storage devices, such as non-volatile storage devices 308 and / or non-volatile memory 319B (e.g., non-transitory memory), may store instructions and / or code that, when executed by a processor (e.g., operating system processor 314 and / or interface processor 320), control the onboard computing system 209 to perform one or more of the actions described in this disclosure.

[0037] A microphone 302 may be included in the onboard computing system 209 to receive voice commands from a user, measure ambient noise in the vehicle, etc. A voice processing unit 304 may process voice commands, such as those received from the microphone 302. In some embodiments, the onboard computing system 209 may also be capable of using a microphone included in the vehicle's audio system 332 to receive voice commands and sample ambient vehicle noise.

[0038] One or more additional sensors may be included in the onboard computing system or sensor subsystem 310 of 209. For example, sensor subsystem 310 may include a camera, such as a rearview camera for assisting a user in parking the vehicle and / or a cabin camera for identifying a user (e.g., using facial recognition and / or user gestures). Sensor subsystem 310 of onboard computing system 209 may communicate with and receive input from various vehicle sensors and may further receive user input. For example, input received by sensor subsystem 310 may include transmission gear position, transmission clutch position, accelerator pedal input, brake input, transmission selector position, vehicle speed, engine speed, mass air flow through the engine, ambient temperature, intake air temperature, etc., as well as input from climate control system sensors (such as heat transfer fluid temperature, antifreeze temperature, fan speed, passenger compartment temperature, desired passenger compartment temperature, ambient humidity, etc.), audio sensors for detecting voice commands issued by the user, key fob sensors for receiving commands from the vehicle's key fob and optionally tracking the vehicle's geographic location / proximity, etc.

[0039] While certain vehicle system sensors may communicate solely with the sensor subsystem 310, other sensors may communicate with both the sensor subsystem 310 and the vehicle control system 330, or may communicate indirectly with the sensor subsystem 310 via the vehicle control system 330. The navigation subsystem 311 of the onboard computing system 209 may generate, send, receive, and / or process navigation information, such as location information (e.g., via a GPS sensor and / or other sensors from the sensor subsystem 310), route guidance, traffic information, point of interest (POI) identification, and / or provide other navigation services to the driver.

[0040] The communication system 312 of the onboard computing system 209 may be capable of coupling to and / or communicating with one or more external devices 250 located outside the vehicle 202. The communication system 312 may be included as a reference Figure 1The communication system 312 is in electronic communication with the electronic controller 212 of the vehicle 202 and can be commanded by the electronic controller 212 to establish a communication connection and generate and send communications, similar to the examples above. As an example, the electronic controller 212 can command the communication system 312 to establish communication with one or more external devices 250. The external devices 250 may include other vehicles, fuel supply facilities (e.g., charging stations), RSUs arranged along the road, etc. via one or more types of communication (including wired communication and / or OTA programming such as WiFi, cellular data, and V2X). In some examples, the communication system 312 can communicate wirelessly with the external device 250 via the communication module.

[0041] The vehicle control system 330 may include controls for controlling various aspects of the various vehicle systems 331 involved in different in-vehicle functions. These controls may include, for example, controlling aspects of the vehicle audio system 332, aspects of the climate control system 334, aspects of the telecommunications system 336, etc. The vehicle control system 330 may be based on stored operating system software such as Figure 1 operating software 110) to operate.

[0042] The vehicle control system 330 may also include controls for adjusting settings of various vehicle control elements 361 (or vehicle controls, or vehicle system controls) associated with the engine and / or auxiliary elements within the cabin of the vehicle, such as one or more steering wheel controls 362 (e.g., steering wheel-mounted audio system controls, cruise controls, windshield wiper controls, headlight controls, turn signal controls, etc.), instrument panel controls, a microphone, accelerator / brake / clutch pedals, a gear shifter, door / window controls located in the driver or passenger door, seat controls, cabin light controls, audio system controls, cabin temperature controls, etc. The vehicle control elements 361 may also include internal engine and vehicle operating controls (e.g., engine controller module, actuators, valves, etc.) that are configured to receive commands via the vehicle's CAN bus to change the operation of one or more of the engine, exhaust system, transmission, and / or other vehicle systems.

[0043] The onboard computing system 209 may also include one or more antennas 306. The onboard computing system may obtain broadband wireless Internet access via the antennas 306 and may also receive broadcast signals such as radio, television, weather, traffic, and the like. In some examples, the communication system 312 may include one or more antennas, and the one or more antennas may be configured to receive communications from the vehicle or other external entities outside the vehicle 202 (including charging stations). The onboard computing system 209 may receive positioning signals, such as GPS signals, via the antennas 306. The onboard computing system may also receive wireless commands via radio frequency (RF) (such as via the antennas 306) or via infrared or other means through an appropriate receiving device. In some embodiments, the antennas 306 may be included as part of the audio system 332 or the telecommunications system 336. Additionally, in some examples, the antennas 306 may provide AM / FM radio signals to the external device 250.

[0044] Vehicle 202 also includes one or more transmitters 338. In some examples, one or more of transmitters 338 can be integrated with one or more of antennas 306 to form one or more transceivers configured to generate and transmit OTA communications and receive and process OTA communications via communication system 312.

[0045] A user may control one or more elements of the vehicle computing system 209 via the user interface 318. The user interface 318 may include a screen display (such as a touch screen) Figure 2 208 and / or display screen 211), and / or user-actuated buttons, switches, knobs, dials, sliders, and the like. For example, user-actuated elements may include steering wheel controls, door and / or window controls, instrument panel controls, audio system settings, climate control system settings, and the like. The user may also interact with one or more applications of the onboard computing system 209 via the user interface 318. In addition to receiving the user's vehicle setting preferences on the user interface 318, the vehicle settings selected by the onboard control system 330 may be displayed to the user on the user interface 318. Notifications and other messages (e.g., received messages) as well as navigation assistance may be displayed to the user on the display of the user interface. User preferences / information and / or responses to presented messages may be implemented via user input to the user interface.

[0046] Although the electronic controller 212 is shown as including an operating system processor 314, memory 319A, memory 319B, etc., in some embodiments, the electronic controller 212 may include a different number and / or configuration of components. For example, the electronic controller 212 may additionally be integrated with one or more antennas 306, one or more transmitters 338, etc.

[0047] Now go to Figures 4 to 6 , shows various scenarios for establishing a connection between a vehicle and a charging station for vehicle software updates. Specifically, Figure 4 A first scenario 400 is shown including wireless communication, Figure 5 A second scenario 500 is shown including a data channel embedded within a charging connector, and Figure 6 A third scenario 600 is shown including a dedicated data cable.

[0048] refer to Figure 4 , the first scene 400 includes a vehicle 402 and a charging station 404. The vehicle 402 may be Figure 1 The non-limiting example of the vehicle 101 and the charging station 404 may be Figure 1 4. The vehicle 402 may be a BEV, a PHEV, another type of electric vehicle, or a hydrogen-powered vehicle. Thus, the vehicle 402 may include a charging port 412. The charging port 412 may be configured to receive a charging connector 410 of a charging station 404.

[0049] As reference Figure 1 As described, in some examples, charging station 404 and vehicle 402 may each include a computing system configured for OTA software updates, such as via WiFi, cellular data, V2X, or other wireless communications. Thus, charging station 404 and vehicle 402 may establish a connection 420 therebetween. Figure 3 In some of the examples shown, connection 420 may be established when vehicle 402 is not connected to charging station 404 via charging connector 410. In other examples, connection 420 may be established wirelessly when charging connector 410 is connected to vehicle 402 via charging port 412. In yet another example, connection 420 may be established regardless of whether charging connector 410 is connected to charging port 412.

[0050] Now refer to Figure 5 , second scenario 500 includes vehicle 402 and charging station 404. In second scenario 400, charging connector 410 may be configured to have an embedded data channel (not shown) therein. Thus, when charging connector 410 is connected to vehicle 402 via charging port 412, charging connector 410 establishes a connection between vehicle 402 and charging station 404.

[0051] Thus, software updates to the vehicle computing system may be performed while the vehicle 402 is connected to the charging station 404. For example, software updates may be performed while the vehicle battery is charging. As previously mentioned, the charging station 404 may be a public or private charging station.

[0052] Now refer to Figure 6, third scenario 600 includes vehicle 402 and charging station 404 communicatively coupled via data cable 602. In some examples, data cable 602 may be configured specifically for software update management. In other examples, data cable 602 may be configured for other purposes as well as for software updates. Similar to charging connector 410, data cable 602 may be connected as a component of charging station 404. When within a distance defined by the length of data cable 602, data cable 602 may then be manually extended toward vehicle 402, for example by a user of vehicle 402. Data cable 602 may then be connected to a port of vehicle 402. In some examples, the port may be an external port. In other examples, the port may be located within the cabin of vehicle 402. For example, data cable 602 may be configured as an Ethernet cable.

[0053] In some examples, data cable 602 may be a separate cable from charging connector 410, such as Figure 6 In other examples, data cable 602 can be incorporated into charging connector 410 . In such an example, data cable 602 can be communicatively coupled to vehicle 402 when charging connector 410 is coupled to charging port 412 of vehicle 402 .

[0054] Now go to Figure 7 and Figure 8 , a method for vehicle computing system software update is shown. Figure 7 Specifically shown is a flow chart illustrating a method that may be performed by an OTA integrated charging station in communication with a vehicle computing system, and Figure 8 Specifically, a flowchart illustrating a method that can be executed by a vehicle computing system in communication with a client-integrated charging station is shown. Method 700 can be executed by a processor (e.g., processor 146 of charging system 141) based on machine-readable instructions stored in a non-transitory memory of the client-integrated charging station (e.g., non-transitory memory 144 of charging system 141). Method 800 can be executed by a processor (e.g., processor 106 of vehicle 101) based on machine-readable instructions stored in a non-transitory memory of the vehicle (e.g., non-transitory memory 104 of vehicle 101).

[0055] Starting from method 700, at 702, method 700 includes establishing communication with a vehicle computing system of a vehicle. Figures 4 to 6As described, communication between an OTA integrated charging station and a vehicle computing system can be established in various ways. For example, a data channel can be embedded within the charging connector of the charging station, and communication can be established when the charging connector is coupled to the charging port. In another example, a wireless connection can be established (e.g., via a private WiFi network). In yet another example, a dedicated data cable, separate from or embedded within the charging cable, can be coupled to the vehicle to establish communication with the vehicle computing system.

[0056] At 704, method 700 includes determining vehicle details for the vehicle. Upon establishing communication, the OTA integrated charging station may determine the vehicle details. In some examples, the charging station may receive one or more vehicle details from the vehicle computing system. The vehicle details may include current operating software, vehicle make, model, year, etc. The vehicle details may identify the vehicle to the OEM so that the correct software update can be identified.

[0057] At 706, method 700 includes establishing communication with the OEM system. Figure 1 As described above, an OEM system can store various operating software configurations and updates for different vehicles. An OTA-integrated charging station (e.g., an OEM communication subsystem 150 configured with OTA technology) can serve as a representation of the vehicle to the OEM system. The communication connection between the charging station and the OEM system can be wireless, such as an OTA connection.

[0058] At 708, method 700 includes determining whether the vehicle requires a software update. In some examples, this can be a message transmitted from the vehicle to the charging station via the established communication indicating that the vehicle has attempted an OTA software update with the OEM system, but was unable to install the software update due to one of various factors. The various reasons may include a lack of a reliable WiFi or cellular data connection during the attempted OTA software update, a connection interruption during the OTA software update, a long queue of vehicles waiting for an OTA update from the OEM system, a lack of sufficient downtime for installation resulting in a user declining the software update, etc. If the vehicle requires a software update but cannot complete the update on its own, method 700 proceeds to 710. If the vehicle does not require a software update, for example, if it is able to install the OTA software update from the OEM system, method 700 ends.

[0059] In other examples, such as when the vehicle has no connection to the OEM system and the vehicle computing system is therefore unaware of the availability of the software update, the vehicle may not indicate whether it requires a software update. In this example, method 700 proceeds directly from 706 to 710.

[0060] At 710, method 700 includes determining whether a software update is available for the vehicle. As described above, the OEM system may store multiple software update configurations for various vehicles. In some cases, based on one or more vehicle details provided, a software update may be available for the vehicle. In other cases, the software currently operating on the vehicle may be the latest software available, and the update may not be available within the OEM system. Furthermore, in examples where the vehicle attempted an OTA software update with the OEM system but was unable to install the update, the update configuration may have changed in the time period between the attempted OTA update and the time the charging station communicated with the OEM system, in which case the OEM system may identify the latest available software update for the vehicle based on the vehicle details. If a software update is available, method 700 proceeds to 712. If a software update is not available, method 700 ends.

[0061] At 712, method 700 includes retrieving a vehicle-specific software update from the OEM system. As described above, the OEM system may store software updates for multiple vehicles. An OTA-integrated charging station representing a vehicle having determined vehicle details may retrieve a software update for the vehicle from the OEM system based on one or more vehicle details retrieved from the vehicle. The software update may be retrieved from the OEM system wirelessly (e.g., via OTA) by a computing system of the charging station. The retrieved software update may be temporarily stored in a memory of the computing system of the charging station.

[0062] At 714 , method 700 includes determining whether a software update installation request has been received from the vehicle. For example, the vehicle's computing system may display an alert via a display (e.g., display 116 ) indicating that a software update is available for download. A user may then interact with the alert, for example, via a touchscreen input, to indicate whether the available software update should be downloaded to the vehicle computing system. In this case, the user input may be a request received by the charging station computing system. In other examples, the vehicle computing system's settings may be configured so that software updates are automatically downloaded, for example, at regular intervals, at any available time, or based on vehicle activity patterns. For example, if the charging station is a private residential charging station, the vehicle computing system may be aware that on most weekdays, the vehicle is inactive and charging for a period of time. During this period, if there is time to install an update while the vehicle is inactive, the vehicle computing system may send an installation request. In this case, the request may be received from the vehicle computing system according to predetermined settings. If a software update request is received, method 700 proceeds to 714 . If no request is received, method 700 ends.

[0063] In an alternative example, a software update request or a request to check for software update availability may be received before determining vehicle details and / or before establishing a connection with and retrieving a software update from an OEM system.

[0064] At 716, method 700 includes installing the software update to the vehicle computing system. In response to determining that the vehicle has requested a software update, the charging station computing system may upload the software update received from the OEM system to the vehicle computing system. As described above, the vehicle computing system may include a software installer that may receive the software update and install the software update, or otherwise communicate with the charging station computing system to install the software update.

[0065] At 718, method 700 includes determining whether the software update installation is verified. The vehicle computing system may determine whether the software update is correctly and / or completely installed. If the installation is verified, method 700 proceeds to 720. If the installation is not verified, for example, if the installation was unsuccessful for some reason, method 700 proceeds to 722.

[0066] At 722, method 700 includes employing a retry mechanism. The retry mechanism may include the charging station's computing system attempting to install the software update to the vehicle's computing system again. After employing the retry mechanism, method 700 may return to 718 to again determine whether the installation is verified. In some examples, a predetermined number of retries may be known, where, as a non-limiting example, the charging station's computing system attempts the installation three times. After the third unsuccessful installation attempt, the charging station's computing system may not retry, and a report of the unsuccessful installation may be transmitted to the OEM system.

[0067] At 720, after installation verification, method 700 includes transmitting a report of the successful software update to the OEM system. The report may include vehicle details and a software update identifier so that the OEM system can store data on which vehicles were updated with which software at a given time.

[0068] In this way, when configured with an OTA client, the charging station can allow for regular and convenient software updates to connected vehicles. Furthermore, because the charging station can represent the vehicle when communicating with the OEM system, processing demands on the vehicle's computing system can be reduced, thereby reducing the need for the vehicle to monitor for updates continuously or at regular intervals. Additionally, when a vehicle is unable to complete an OTA software update on its own due to WiFi or cellular data connection issues, the OTA-integrated charging station provides a convenient route for the vehicle to receive software updates in a timely and convenient manner. Furthermore, some vehicles may be configured to monitor for software updates at preset intervals, and the software updates may be available at a time earlier than the preset intervals. In this case, even when the vehicle is able to complete the OTA software update on its own, the charging station may allow the vehicle to receive the latest software update earlier than based on its own monitoring schedule.

[0069] In some examples, such as when the charging station is a private residential charging station, the vehicle details can be determined during a first software update session and then saved by the charging station (e.g., stored in memory), thereby alleviating the need for the charging station to communicate with the OEM system to establish a connection and determine the vehicle details before each subsequent software update. In such an example, establishing communication with the vehicle computing system can be delayed until after the software update is retrieved.

[0070] In a corresponding method 800 for a vehicle computing system, at 802, method 800 determines whether an OTA software update is unavailable for the vehicle. In some examples, the vehicle may be equipped with OTA programming that allows the vehicle to retrieve OTA software updates from the OEM system. Such OTA software updates require a reliable WiFi and / or cellular data connection to install. In examples where a reliable WiFi and / or cellular data connection is unavailable, the OTA software update may be unavailable. In some cases, the vehicle may attempt an OTA software update but may be unable to install the OTA software update due to connectivity issues. Therefore, the vehicle computing system may know that a software update is available from the OEM system but may be unable to retrieve the software update. If the OTA software update is unavailable (yes at 802), method 800 proceeds to 804. If the OTA software update is available (no at 802), method 800 proceeds to 816 to install the OTA software update from the OEM system to the vehicle.

[0071] In some examples, the determination at 802 may be an optional step, whereby method 800 may begin at 804, as described below, regardless of whether the vehicle has been unable to complete an OTA software update via the OEM system. For example, the vehicle may not be equipped for OTA software updates, such as those configured primarily for field software updates at dealerships. In such cases, as described below, the vehicle may establish communication with the charging station and receive the software update in this manner without attempting an OTA software update itself.

[0072] At 804, method 800 includes establishing communication between the vehicle computing system and the computer system of the charging station. The charging station can be an OTA client integrated charging station configured to be communicatively coupled to the vehicle via a wired connection (e.g., via a dedicated data cable or data channel embedded in the charging connector) and / or a wireless connection (e.g., via WiFi, cellular data, V2X, etc.). As previously described, the charging station can also communicate wirelessly with the OEM system.

[0073] At 806, method 800 includes determining whether the charging station is client-integrated. As previously described, the charging station can be configured as an OTA client-integrated charging station, whereby the charging station is capable of communicating with the OEM system via OTA programming to determine the availability of software updates and retrieve the software updates (if available). If the charging station is client-integrated, method 800 proceeds to 808. If the charging station is not client-integrated, method 800 ends.

[0074] At 808, method 800 includes transmitting vehicle details to a computing system of the charging station. Once communication between the charging station and the vehicle is established, the vehicle may transmit the vehicle details to the charging station. As previously described, the vehicle details may include the current operating software and may identify which software updates are available for the vehicle's make, model, year, etc.

[0075] At 810, method 800 includes determining whether a software update is available. As described with reference to method 700, the charging station may communicate with the OEM system to determine whether a software update is available for the vehicle, and if so, retrieve the software update from the OEM system. If a software update is available for the vehicle computing system, the vehicle computing system may receive a notification or other type of communication from the charging station's computing system indicating that a software update is available. For example, the notification may be displayed on a display screen within the vehicle (e.g., Figure 1 The software update is displayed on the display screen 116 of the vehicle or on a personal device (such as a smartphone) that is wirelessly connected to the vehicle computing system. If a software update is available, the method 800 proceeds to 808. If a software update is not available, the method 800 ends.

[0076] At 812 , method 800 includes determining whether an installation request has been transmitted. As described at 806 , when a software update is available, the vehicle computing system may receive a notification or other indication that a software update is available. In some examples, the vehicle computing system may be equipped with instructions stored in non-transitory memory that transmit an installation request to the charging station's computing system when one or more conditions are met. For example, one or more conditions may be a time frame, such that software updates, if available, are performed at regular intervals. Optionally, as described above, one or more conditions may be learned vehicle habits. For example, the vehicle computing system may learn that the vehicle is typically inactive for a period of time (e.g., at night) and may transmit an installation request if the vehicle is inactive during that period. In another example, the vehicle computing system may be configured to transmit an installation request upon manual input. For example, a notification indicating that a software update is available may be displayed on an infotainment system display or on a user's connected personal device (e.g., a smartphone). The user may then indicate via user input (e.g., touch input) that they wish to proceed with installing the software update, which may trigger the transmission of the installation request to the charging station's computing system. If the installation request has been transmitted, method 800 proceeds to 810 . If no installation request is transmitted, for example, if certain conditions are not met or if user input indicates that the software update will not be installed, then method 800 ends. In this way, convenience when updating software can be increased because users can select the conditions under which installation may occur or can manually select an installation time that suits their schedule.

[0077] At 814, method 800 includes receiving a software update from the charging station's computing system. The charging station's computing system may upload the software update to the vehicle computing system via the connection established at 804. In some examples, receiving the software update and installing the software update may be performed substantially simultaneously, whereby the charging station's computing system communicates with a software installer in the vehicle computing system to install the software update. In other examples, the software update may be received by the vehicle computing system and temporarily stored in memory, and then the software installer may install the update.

[0078] As described with reference to method 700 , the vehicle computing system can verify when the installation is successful. In some examples, one or more unsuccessful installation attempts may occur, in which case the vehicle computing system can receive the software update from the charging station in one or more retries. When the installation is successful, the vehicle computing system can notify the charging station's computing system.

[0079] The method described herein can increase user convenience by allowing the user to determine when to install software updates and reducing the processing power of the vehicle computing system. Because the charging station determines the availability of software updates and retrieves the software updates from the OEM system, the vehicle computing system can reduce the load on its processor because the vehicle computing system no longer needs to maintain OTA connectivity with the OEM system and monitor for available software updates.

[0080] Furthermore, the inconvenience of on-site visits is alleviated, reducing the need for vehicles to have reliable and regular access to and connectivity to WiFi or cellular data to perform OTA software updates. Additionally, the queue of vehicles awaiting OTA updates from OEM systems can be reduced, as charging stations can retrieve software updates from OEM systems based on determined or known vehicle details. Reducing the queue reduces the load and processing power of OEM systems. Furthermore, the systems and methods provided herein can increase the frequency of software updates, allowing more vehicles to have the latest software. With more comprehensive and up-to-date operating system software on various vehicles, the storage requirements for current operating software on OEM systems may be reduced.

[0081] The present disclosure also provides support for a method for over-the-air (OTA) integrated charging station, the method comprising: establishing communication between a computing system of the OTA integrated charging station and a vehicle computing system of an electric vehicle; determining one or more vehicle details of the electric vehicle from the vehicle computing system; establishing communication between the computing system and an original equipment manufacturer (OEM) system; retrieving a software update from the OEM system based on the one or more vehicle details; and installing the software update to the vehicle computing system via a software installation program of the vehicle computing system. In a first example of the method, the method further comprises: determining the availability of the software update within the OEM system based on the one or more vehicle details. In a second example of the method, optionally including the first example, the method further comprises: transmitting a notification of the availability of the software update to the electric vehicle. In a third example of the method, optionally including one or both of the first and second examples, installing the software update is performed in response to receiving an installation request from the vehicle. In a fourth example of the method, optionally including one or more or each of the first to third examples, establishing communication between the vehicle computing system and the computing system of the OTA integrated charging station comprises connecting a charging cable of the OTA integrated charging station to the electric vehicle and connecting a dedicated data cable of the charging station to the electric vehicle, the charging cable having an embedded data channel. In a fifth example of the method, optionally including one or more or each of the first to fourth examples, establishing communication between the vehicle computing system and the computing system of the OTA integrated charging station is in response to the electric vehicle being unable to retrieve software updates from the OEM system via OTA programming. In a sixth example of the method, optionally including one or more or each of the first to fifth examples, establishing communication between the vehicle computing system and the computing system of the OTA integrated charging station includes establishing an OTA connection between the vehicle computing system and the computing system of the OTA integrated charging station. In a seventh example of the method, optionally including one or more or each of the first to sixth examples, establishing communication between the computing system of the OTA integrated charging station and the OEM system includes establishing an OTA connection between the computing system of the OTA integrated charging station and the OEM system.

[0082] The present disclosure also provides support for a vehicle software update system, the vehicle software update system comprising: an electric vehicle including a vehicle computing system controlled by software; an over-the-air (OTA) integrated charging station configured to communicate with the vehicle computing system; and an original equipment manufacturer (OEM) system configured to communicate with the OTA integrated charging station, wherein the OTA integrated charging station is configured to retrieve software updates for the vehicle from the OEM system and install the software updates to the vehicle computing system. In a first example of the system, the OTA integrated charging station is configured to retrieve software updates from the OEM system via OTA programming. In a second example of the system, optionally including the first example, the OTA integrated charging station is configured to communicate with the vehicle computing system via one or more of OTA programming, a data channel embedded in a charging cable coupled to the vehicle, and a dedicated data cable coupled to the vehicle. In a third example of the system, optionally including one or both of the first and second examples, the OTA integrated charging station includes a computing system including a vehicle communication subsystem and an OEM communication subsystem. In a fourth example of the system, optionally including one or more or each of the first to third examples, the vehicle communication subsystem includes instructions stored in memory that, when executed by a processor of the computing system, cause the computing system to determine one or more vehicle details of the electric vehicle and install a software update on the vehicle computing system. In a fifth example of the system, optionally including one or more or each of the first to fourth examples, the OEM communication subsystem includes instructions stored in memory that, when executed by the processor, cause the computing system to retrieve a software update for the electric vehicle from the OEM system based on the one or more vehicle details. In a sixth example of the system, optionally including one or more or each of the first to fifth examples, the vehicle computing system includes a software installer configured to receive software updates from an OTA integrated charging station.

[0083] The present disclosure also provides support for a method for a vehicle computing system, the method comprising: establishing communication with a computing system of an over-the-air (OTA) integrated charging station; sending one or more vehicle details to the computing system of the OTA integrated charging station; and receiving a software update from the computing system of the OTA integrated charging station based on the one or more vehicle details. In a first example of the method, the method further comprises: receiving a notification of the availability of the software update from the computing system of the OTA integrated charging station. In a second example of the method, optionally including the first example, the software update is received in response to an installation request, wherein the installation request is sent to the computing system of the OTA integrated charging system based on one of user input and predetermined instructions stored in a memory. In a third example of the method, optionally including one or both of the first and second examples, establishing communication with the computing system of the OTA integrated charging station is performed in response to the vehicle being unable to retrieve the OTA software update from the OEM system. In a fourth example of the method, optionally including one or more or each of the first to third examples, the software update is received by a software installer of the vehicle computing system.

[0084] The description of the embodiments has been presented for the purpose of illustration and description. It can be performed in view of the above description or can obtain suitable modifications and changes to the embodiments by practicing the described methods. For example, unless otherwise stated, one or more of the described methods can be performed by suitable devices and / or device combinations. These methods can be performed by executing stored instructions in combination with one or more logic devices (for example, processors) in combination with one or more additional hardware elements (such as storage devices, memories, hardware network interfaces / antennas, switches, actuators, clock circuits, etc.). In addition to executing in the order described in this application, in parallel and / or simultaneously, the described methods and associated actions can also be performed in various orders. The described system is exemplary in nature and may include additional elements and / or omit elements. The subject matter of the present disclosure includes all novel and non-obvious combinations and sub-combinations of the disclosed various systems and configurations and other features, functions and / or properties.

[0085] As used in this application, an element or step described in the singular and preceded by the word "a" or "an" should be understood as not excluding a plurality of said elements or steps, unless such exclusion is specified. In addition, reference to "one embodiment" or "an example" of the present disclosure is not intended to be interpreted as excluding the existence of another embodiment that also incorporates the described features. Terms such as "first," "second," and "third" are used only as labels and are not intended to impose numerical requirements or a specific positional order on their objects. The appended claims specifically point out subject matter that is considered novel and non-obvious from the above disclosure.

Claims

1. A method for an over-the-air (OTA) integrated charging station, comprising: establishing communication between a computing system of the OTA integrated charging station and a vehicle computing system of the electric vehicle; determining one or more vehicle details of the electric vehicle from the vehicle computing system; establishing communications between the computing system and an original equipment manufacturer (OEM) system; retrieving a software update from the OEM system based on the one or more vehicle details; as well as The software update is installed to the vehicle computing system via a software installation program of the vehicle computing system. 2 . The method of claim 1 , further comprising determining availability of the software update within the OEM system based on the one or more vehicle details. 3 . The method of claim 1 , further comprising transmitting a notification of the availability of the software update to the electric vehicle. The method of claim 3 , wherein installing the software update is performed in response to receiving an installation request from the vehicle.

5. The method of claim 1 , wherein establishing communication between the vehicle computing system and the computing system of the OTA integrated charging station comprises one of connecting a charging cable of the OTA integrated charging station to the electric vehicle and connecting a dedicated data cable of the charging station to the electric vehicle, the charging cable having an embedded data channel. 6 . The method of claim 1 , wherein establishing communication between the vehicle computing system and the computing system of the OTA integrated charging station is in response to the electric vehicle being unable to retrieve the software update from the OEM system via OTA programming. 7 . The method of claim 1 , wherein establishing communication between the vehicle computing system and the computing system of the OTA integrated charging station comprises establishing an OTA connection between the vehicle computing system and the computing system of the OTA integrated charging station. 8 . The method of claim 1 , wherein establishing communication between the computing system of the OTA integrated charging station and the OEM system comprises establishing an OTA connection between the computing system of the OTA integrated charging station and the OEM system.

9. A vehicle software update system comprising: An electric vehicle comprising a vehicle computing system controlled by software; an over-the-air (OTA) integrated charging station configured to communicate with the vehicle computing system; as well as An original equipment manufacturer (OEM) system is configured to communicate with the OTA integrated charging station, wherein the OTA integrated charging station is configured to retrieve a software update for the vehicle from the OEM system and install the software update to the vehicle computing system. 10 . The vehicle software update system of claim 9 , wherein the OTA integrated charging station is configured to retrieve the software update from the OEM system via OTA programming.

11. The vehicle software update system of claim 9, wherein the OTA integrated charging station is configured to communicate with the vehicle computing system via one or more of OTA programming, a data channel embedded in a charging cable coupled to the vehicle, and a dedicated data cable coupled to the vehicle. 12 . The vehicle software update system of claim 9 , wherein the OTA integrated charging station comprises a computing system including a vehicle communication subsystem and an OEM communication subsystem.

13. The vehicle software update system of claim 12, wherein the vehicle communication subsystem includes instructions stored in memory that, when executed by a processor of the computing system, cause the computing system to determine one or more vehicle details of the electric vehicle and install the software update on the vehicle computing system.

14. The vehicle software update system of claim 13, wherein the OEM communication subsystem includes instructions stored in memory that, when executed by the processor, cause the computing system to retrieve the software update for the electric vehicle from the OEM system based on the one or more vehicle details. 15 . The vehicle software update system of claim 9 , wherein the vehicle computing system includes a software installer configured to receive the software update from the OTA integrated charging station.

Images