Software update for vehicle via charging station

By calculating and comparing the charging and updating time when the vehicle is charged, and using the digital communication channel between the charging station and the vehicle to perform updates during the charging process, the problem of interruption of vehicle digital data updates is solved, and the success rate and user experience of updates are improved.

CN118906900APending Publication Date: 2024-11-08RED BEND LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410560880.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-08
Filing Date
2024-05-08
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In the automotive industry, it is difficult for the prior art to efficiently update digital data during vehicle charging, and the update process may be interrupted, affecting vehicle reliability and user experience.

Method used

By calculating the expected time for charging and updating when the vehicle is connected to the charging station, identifying that the update time is less than the charging time, and performing updates during the charging process, data transmission is reduced by using the digital communication channel between the charging station and the vehicle. Non-operating state time.

Benefits of technology

Improves the success rate and reliability of vehicle updates, reduces the risk of interruption in the update process, improves the user experience, and improves the overall availability of the vehicle.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118906900A_ABST
    Figure CN118906900A_ABST
Patent Text Reader

Abstract

A vehicle charging station includes a charging processor configured to, when a vehicle is connected to the charging station: send a request for at least one power level value to the vehicle; and in response to receiving the at least one power level value from the vehicle: calculating an expected amount of time to charge at least one battery of the vehicle; calculating an expected amount of time for performing an update of the digital data of the vehicle, wherein the expected amount of time includes an amount of time for fallback of the update; and sending an instruction for executing the update to the vehicle while charging the at least one battery in the event that the update time is identified to be less than the charging time as a function of the time comparison test.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application claims priority to Israel Patent Application No. 302761 filed on May 8, 2023, the contents of which are incorporated herein by reference in their entirety.

[0002] This application is also related to Israeli patent application no. 295320 filed on August 2, 2022. The contents of the above applications are incorporated by reference in their entirety, as if fully set forth herein. Technical Field

[0003] Some embodiments described in this disclosure relate to over-the-air software distribution, and more particularly, but not exclusively, to over-the-air software distribution in the automotive industry. Background Art

[0004] As used herein, the term over-the-air (OTA) distribution (or update) refers to the ability to distribute digital data to multiple target devices via a wireless or cellular digital communication network. Such digital data includes, but is not limited to, applications, services, and configurations. An application can be a set of computer instructions, such as a firmware image or a software application. A configuration can be a set of parameter values ​​that define the behavior of a component of a device. The component can be a hardware component, a software component, or a combination thereof. OTA distribution is used for a variety of target devices, including mobile phones and Internet of Things (IoT) devices, such as smoke detectors, smart home speakers, and light bulb controllers. Mobile operators and telecommunications third parties are increasingly using OTA updates to configure data updates in SIM cards, distribute system updates, and access services, such as wireless access protocol (WAP) or multimedia messaging services (MMS).

[0005] In the automotive industry, OTA updates may be used to update one or more of a vehicle's systems, such as the vehicle's infotainment system.

[0006] A typical process for updating some digital data on multiple target devices using OTA distribution includes a device management system that manages multiple target devices to publish data updates. The data updates can be uploaded to one or more servers accessed via the Internet or another wide area network. The target devices can download data updates from one or more servers via a cellular or other digital communication network connection and verify the data updates. Once verified, the target devices can install the data updates. In some processes, the installation of the data update will undergo a receipt confirmation, such as by prompting the user of the device to confirm. In some processes, the installation of the data update is automatic. Summary of the invention

[0007] Some embodiments described in the present disclosure provide systems and methods for updating digital data of a vehicle while the vehicle is connected to an electric vehicle charging station. Optionally, updating the digital data includes identifying that an expected amount of time for performing the update of the digital data is less than an expected charging time of the vehicle. Identifying that the expected amount of time for performing the update is less than the expected charging time facilitates completion and successful execution of the update and reduces the likelihood of placing the vehicle in a non-operating state, thereby increasing the reliability of the vehicle and improving the overall consumer experience associated with vehicle updates.

[0008] The above and other objects are achieved by the features of the independent claims. Further embodiments are evident from the dependent claims, the description and the drawings.

[0009] According to a first aspect, a vehicle charging station (charging station) includes: at least one hardware processor (station processor), which is configured to: send a request for at least one power level value to the vehicle when the vehicle is connected to the charging station; and in response to receiving at least one power level value from the vehicle: calculate the expected amount of time (charging time) for charging at least one battery of the vehicle; calculate the expected amount of time (update time) for performing an update of digital data of the vehicle, wherein the update time includes the amount of time for rolling back the update; and in a case where the update time is identified as being less than the charging time based on a time comparison test, send instructions to the vehicle for performing the update while charging at least one battery.

[0010] According to a second aspect, a method for a vehicle charging station (charging station) includes: when the vehicle is connected to the charging station: sending a request for at least one power level value to the vehicle; and in response to receiving at least one power level value from the vehicle: calculating the expected amount of time (charging time) to charge at least one battery of the vehicle; calculating the expected amount of time (update time) to perform an update of digital data of the vehicle, wherein the update time includes the amount of time for rolling back the update; and in a case where it is identified based on a time comparison test that the update time is less than the charging time, sending an instruction to the vehicle to perform the update while charging at least one battery of the vehicle.

[0011] According to a third aspect, a vehicle comprises: at least one hardware processor (vehicle processor), which is configured to: when the vehicle is connected to a vehicle charging station (charging station): provide at least one power level value to the charging station in response to a request for at least one power level value received from the charging station; and while charging at least one battery of the vehicle, perform the update in response to an instruction received from the charging station to perform the update of the digital data of the vehicle.

[0012] According to a fourth aspect, a method for a vehicle comprises: when the vehicle is connected to a vehicle charging station (charging station): providing at least one power level value to the charging station in response to receiving a request for at least one power level value from the charging station; and while charging at least one battery of the vehicle, performing the update in response to receiving an instruction from the charging station for performing an update of digital data of the vehicle.

[0013] According to a fifth aspect, a system for updating digital data in a vehicle comprises: a vehicle comprising at least one hardware processor (vehicle processor); and a vehicle charging station (charging station), the vehicle charging station (charging station) comprising at least one other hardware processor (station processor), the at least one other hardware processor (station processor) being configured to: send a request for at least one power level value to the vehicle when the vehicle is connected to the charging station; and in response to receiving at least one power level value from the vehicle: calculate an expected amount of time (charging time) for charging at least one battery of the vehicle; calculate an expected amount of time (update time) for performing an update of the digital data of the vehicle, wherein the update time includes an amount of time for rolling back the update; and in a case where it is identified according to a time comparison test that the update time is less than the charging time, send an instruction for performing the update to the vehicle, wherein the vehicle processor is configured to: provide at least one power level value to the charging station in response to receiving a request for at least one power level value from the charging station when the vehicle is connected to the charging station; and perform the update in response to receiving an instruction for performing the update from the charging station while charging at least one battery.

[0014] According to a sixth aspect, a method for updating digital data in a vehicle comprises: when the vehicle is connected to a vehicle charging station (charging station): calculating an expected amount of time (charging time) for charging at least one battery of the vehicle; calculating an expected amount of time (update time) for performing an update of the digital data of the vehicle, wherein the update time includes an amount of time for rolling back the update; and performing the update while charging at least one battery when it is identified based on a time comparison test that the update time is less than the charging time.

[0015] With reference to the first aspect and the second aspect, in a first possible implementation of the first aspect and the second aspect, the charging station further comprises at least one digital communication network interface (station data interface) connected to the station processor, the vehicle comprises at least one other hardware processor (vehicle processor), the vehicle processor and the station processor are further configured to establish at least one digital data communication channel (data channel) between the vehicle processor and the station processor via the station data interface, and the request for at least one power level value is sent to the vehicle via the data channel using the station data interface. Establishing the data channel between the vehicle processor and the station processor allows digital data to be provided to the vehicle without requiring the vehicle to be connected to another digital data communication network, thereby increasing the availability of the vehicle and increasing the reliability of performing updates. In addition, sending the request for at least one power level value to the vehicle via the data channel using the station data interface reduces the possibility of tampering with the request compared to sending the request to the vehicle via a wide area network (e.g., a cellular network). Optionally, the station data interface comprises at least one of a digital data communication interface in a charging plug of the charging station, a digital data communication interface in a charging socket of the charging station, and a wireless digital data network interface. Optionally, for example when the station data interface comprises a wireless digital data network interface, the vehicle processor is further configured to provide at least one credential value to the charging station for establishing the data channel. Using a digital data communication interface implemented in a charging plug or charging socket of the charging station, and additionally or alternatively providing one or more credential values ​​for establishing the data channel, reduces the likelihood of tampering with data transmitted via the data channel compared to using another data channel established via a wireless network without using at least one credential value, thereby increasing the reliability of the data channel and thus increasing the reliability of performing the update. Optionally, the station processor is further configured to provide updated digital data to the vehicle using the data channel for performing the update.

[0016] With reference to the first and second aspects or the first embodiments of the first and second aspects, in a second possible embodiment of the first and second aspects, the station processor is further configured to connect to at least one user application executed by at least one additional hardware processor via a station data interface. Optionally, the station processor is further configured to receive at least one user input value from at least one user application for calculating the charging time. Optionally, the station processor is further configured to send an instruction to the vehicle for performing an update in the event that at least one user confirmation value is received from at least one user application. Using one or more user input values ​​when calculating the charging time increases the accuracy of the charging time, thereby reducing the likelihood that the execution of the update must be terminated prematurely, which further increases the reliability of the execution of the update, and thus increases the reliability of the vehicle. Executing the update in the event that one or more user confirmation values ​​are received reduces the likelihood that the execution of the update must be terminated prematurely, which further increases the reliability of the execution of the update, and thus increases the reliability of the vehicle. Executing the update in the event that one or more user confirmation values ​​are received reduces the likelihood that the execution of the update must be terminated prematurely, which further increases the reliability of the execution of the update, and thus increases the reliability of the vehicle.

[0017] With reference to the first and second aspects or the first implementation of the first and second aspects, in a third possible implementation of the first and second aspects, the station processor is further configured to: send a request for at least one vehicle data value to the vehicle via the data channel; and receive at least one vehicle data value from the vehicle via the data channel. Collecting one or more vehicle data values ​​while the vehicle is connected to the charging station helps to provide diagnostic information about the vehicle and additionally or alternatively provide statistical information to a maintenance service, thereby increasing the accuracy of maintenance operations performed on the vehicle, thereby increasing the reliability and availability of the vehicle.

[0018] With reference to the first aspect and the second aspect, in a fourth possible implementation of the first aspect and the second aspect, the station processor is further configured to send a maintenance instruction to the vehicle via the data channel for performing at least one of: a diagnostic operation and a self-maintenance operation.

[0019] With reference to the first aspect and the second aspect, in a fifth possible implementation of the first aspect and the second aspect, the digital data comprises one or more computer instruction sets. Optionally, the digital data comprises one or more component configuration value sets. Executing an update of the one or more computer instruction sets and additionally or alternatively executing an update of the one or more component configuration value sets increases the reliability of the vehicle.

[0020] With reference to the third and fourth aspects, in a first possible implementation of the third and fourth aspects, the vehicle further comprises at least one digital communication network interface (vehicle data interface) connected to the vehicle processor, and the vehicle processor is further configured to provide at least one power level value to the charging station via the vehicle data interface. Using the power level value increases the accuracy of the charging time, thereby increasing the reliability of performing the update.

[0021] With reference to the third and fourth aspects or the first implementation of the third and fourth aspects, in a second possible implementation of the third and fourth aspects, performing the update includes retrieving updated digital data via a vehicle data interface. Optionally, the updated digital data is retrieved from the charging station. When the vehicle is not directly connected to another network, retrieving updated digital data from the charging station helps to perform the update. Optionally, the vehicle data interface is connected to at least one cellular data communication network, and the retrieval of the updated digital data is via at least one cellular data communication network. Optionally, the retrieval of the updated digital data is via at least one digital data communication channel (data channel) established with the charging station using the vehicle data interface. Optionally, the vehicle processor is also configured to send at least one vehicle data value to the charging station via the vehicle data interface in response to receiving a request for at least one vehicle data value from the charging station while charging at least one battery.

[0022] Referring to the third aspect and the fourth aspect, in a third possible implementation of the third aspect and the fourth aspect, the vehicle processor is also configured to, while charging at least one battery, perform the at least one operation in response to receiving a maintenance instruction from the charging station for performing at least one operation selected from a group of operations consisting of diagnostic operations and self-maintenance operations.

[0023] With reference to the third aspect and the fourth aspect, in a fourth possible implementation of the third aspect and the fourth aspect, the vehicle further comprises a human-machine interface for interacting with a user. Optionally, the vehicle processor is further configured to: receive at least one confirmation value from the user via the human-machine interface; and perform an update when at least one confirmation value is received.

[0024] With reference to the third aspect and the fourth aspect, in a fifth possible implementation of the third aspect and the fourth aspect, the digital data comprises one or more computer instruction sets. Optionally, the digital data comprises one or more component configuration value sets.

[0025] With reference to the fifth and sixth aspects, in a first possible implementation of the fifth and sixth aspects, the digital data comprises one or more computer instruction sets. Optionally, the digital data comprises one or more component configuration value sets.

[0026] With reference to the fifth and sixth aspects, in a second possible implementation of the fifth and sixth aspects, the charging time is calculated based on at least one power level value of the vehicle. Optionally, the method further comprises: when the vehicle is connected to the charging station: sending a request for at least one power level value from the charging station to the vehicle; and in response to receiving the request for at least one power level value, providing at least one power level value to the charging station by the vehicle.

[0027] With reference to the fifth and sixth aspects, in a third possible implementation of the fifth and sixth aspects, executing the update includes: sending an instruction for executing the update from the charging station to the vehicle; and while charging at least one battery, in response to receiving the instruction for executing the update from the charging station, executing the update by at least one hardware processor (vehicle processor) of the vehicle.

[0028] After reviewing the following drawings and detailed description, other systems, methods, features and advantages of the present disclosure will become apparent to those skilled in the art. All such additional systems, methods, features and advantages are intended to be included within this description and are within the scope of the present disclosure, and are protected by the accompanying claims.

[0029] Unless otherwise defined, all technical terms and / or scientific terms used herein have the same meaning as those generally understood by those of ordinary skill in the art to which the embodiments belong. Although methods and materials similar or equivalent to the methods and materials described herein can be used in the practice or testing of the embodiments, exemplary methods and / or materials are described below. In the event of a conflict, the patent specification (including limitations) shall prevail. In addition, materials, methods and examples are only illustrative and are not intended to be necessarily limited. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] With reference to the accompanying drawings, some embodiments are described herein by way of example only. With specific reference now to the drawings in detail, it should be emphasized that the details shown are by way of example and are for the purpose of illustrative discussion of the embodiments. In this regard, the description in conjunction with the drawings makes it clear to those skilled in the art how the embodiments can be practiced.

[0031] In the attached picture:

[0032] Figure 1 is a schematic block diagram of an exemplary system according to some embodiments;

[0033] Figure 2 is a flow chart schematically illustrating an optional operational flow according to some embodiments;

[0034] Figure 3 is a sequence diagram of another optional operational flow according to some embodiments;

[0035] Figure 4 is a sequence diagram of yet another optional operational flow according to some embodiments; and

[0036] Figure 5 is a sequence diagram of additional optional operational flows according to some embodiments. DETAILED DESCRIPTION

[0037] The following description focuses on providing OTA updates for digital data of a device. Some examples of digital data of a device include multiple computer instructions, such as a firmware image or a patch to a firmware image and component configuration value sets, such as configuration value sets that address security issues. The firmware image can be a monolithic software package that is, for example, burned into a non-volatile memory component and loaded by a hardware processor after a power cycle. Some portions of the following description focus on updating the firmware installed on the device, however, the following systems and methods as described herein are not limited to OTA updates of firmware and may additionally or alternatively be applied to OTA updates of other digital data, some examples of which include digital configuration data and software applications.

[0038] Additionally, while the following description focuses on performing OTA updates for a vehicle connected to a charging station, the following systems and methods may be used to perform OTA updates for other devices, such as a robotic device connected to a docking station.

[0039] As used herein, the term "electric vehicle" refers to a vehicle that includes one or more rechargeable power units (batteries). One or more batteries may be used to power one or more electric motors installed in the electric vehicle. In addition to or as a substitute for one or more electric motors, the electric vehicle may include one or more non-electric motors. The electric vehicle may not include an electric motor and the battery may have a purpose other than vehicle propulsion. Although the following description focuses on performing OTA updates in an electric vehicle connected to an electric vehicle charging station, the following systems and methods may be used to perform OTA updates for vehicles that include other types of rechargeable power units while connected to a suitable charging station.

[0040] From a management perspective, the advantage of providing OTA updates is that the end user is not required to take the device to a support workshop. However, monitoring the progress of the OTA update is critical because an interrupted OTA update that does not complete successfully may leave the device in a non-operational state. For some devices (such as mobile phones), this may cause a temporary inconvenience to the end user, but will be remedied when the OTA update is repeated. For some devices (such as vehicles), in addition to the inconvenience, this may also pose a significant safety risk, especially if it occurs while the vehicle is in motion.

[0041] One way to reduce this type of risk is to perform OTA updates only when the device is not in use, such as when the phone is muted at night or when the vehicle is parked. Automatically initiating OTA updates when the device is not in use carries the risk of the OTA update being interrupted, for example because the user turns off the device or because the power runs out, or because the user resumes using the device (such as driving a vehicle). In addition, for some devices, the OTA update process will make the device inoperable for a certain amount of time during the OTA update process. Relying on user-initiated OTA updates is also insufficient because the user may be reluctant to initiate an OTA update, which renders the device inoperable for a certain amount of time during the update. As a result, OTA updates may not be installed at the required frequency and scope, resulting in some devices operating with outdated software and lacking basic functionality, such as protection of security features.

[0042] A friendly user experience needs to be provided to increase the likelihood of performing OTA updates while ensuring that the process is uninterrupted and secure during execution. In addition, the user experience needs to maintain a high level of protection.

[0043] For this reason, in some embodiments described herein, the present disclosure proposes to identify one or more opportunities that guarantee that the device is not in use, and calculate the expected amount of time that the device will not be in use. In addition, in such embodiments, the present disclosure proposes to compare the expected amount of time that the device will not be in use with the amount of time used to perform the update, and initiate the update process when the amount of time used to perform the update is less than the expected amount of time that the device will not be in use. Calculating the amount of time that the device is expected to be out of use increases the possibility that the update process will be completed without being interrupted, thereby increasing the reliability of the device. Initiating the update process when the amount of time used to perform the update is less than the expected amount of time that the device is not in use allows the update process to be performed when the device is not in use, thereby increasing the availability of the device by reducing the amount of time that the device is inoperable due to the update process.

[0044] More specifically, in some embodiments described herein, the present disclosure proposes identifying when a device is not in use while the device is connected to a docking station. In one example, when a robotic device (e.g., a robotic vacuum cleaner) is connected to its docking station, it is expected that the device is not in use.

[0045] In another example, when a vehicle is connected to an electric vehicle charging station (charging station) for charging, the vehicle is expected to remain stationary for the duration of the charging. In some embodiments described herein, the present disclosure proposes performing an update of the digital data of the vehicle while the vehicle is connected to the charging station.

[0046] To this end, in some embodiments described herein, the present disclosure proposes to send a request for one or more power values ​​to the hardware processor of the vehicle when the vehicle is connected to the charging station, and calculate the expected amount of time (charging time) for charging one or more batteries of the electric vehicle in response to receiving one or more power values. Optionally, one or more power values ​​are used to calculate the charging time. Optionally, the charging time is the amount of time until at least one of the one or more batteries is fully charged. Optionally, the charging time is the amount of time until at least one of the one or more batteries is partially charged. Optionally, the charging time is the amount of time until at least one of the one or more batteries is charged to a threshold charge level. In addition, in such embodiments, the present disclosure proposes to calculate the expected amount of time (update time) for performing data updates of digital data of the vehicle. Optionally, the update time includes the amount of time for backing off the data update. If the data update fails, the amount of time for backing off the data update is included in the update time to reduce the possibility of the electric vehicle becoming inoperable. Optionally, the present disclosure proposes to send an instruction for performing data updates to the vehicle while charging one or more batteries of the vehicle when it is identified that the update time is less than the charging time.

[0047] Optionally, the charging station and the vehicle communicate via one or more digital communication networks, for example, via a digital data communication interface in a charging plug or a charging socket of the charging station. In the context of the present disclosure, it is not important whether the charging station has a charging plug or a charging socket for connecting to the vehicle, and the solutions described herein are applicable to any embodiment. Therefore, for the sake of brevity, the term "charging plug" is used to mean "charging plug or charging socket" hereinafter. Optionally, the charging station and the vehicle optionally establish one or more data communication channels between the charging station and the vehicle via one or more digital communication networks.

[0048] Optionally, the charging station and the vehicle communicate via one or more wireless digital communication networks (e.g., Bluetooth or Wi-Fi). Optionally, the charging station has a Wi-Fi hotspot to which the vehicle can connect.

[0049] Optionally, the charging station provides updated digital data to the vehicle for performing data updates. Optionally, the vehicle retrieves the updated digital data via one or more cellular data communication networks, some examples of which include but are not limited to a Global System for Mobile Communications (GSM) network, a Universal Mobile Telecommunications System (UMTS) network, and a fifth generation broadband cellular network technology standard (5G) network.

[0050] Optionally, the charging station is connected to one or more user applications. Optionally, the one or more user applications are executed by one or more hardware processors of the vehicle. Optionally, the one or more user applications are executed by one or more other hardware processors, such as on a mobile device, such as a mobile phone or tablet computer.

[0051] Optionally, the charging station is connected to a backend server.

[0052] In addition, in some embodiments described herein, the present disclosure provides for performing one or more other operations while the vehicle is connected to the charging station. For example, the charging station may send an instruction to the vehicle for performing a diagnostic operation. Optionally, the instruction is used to perform the diagnostic operation while charging. In another example, the charging station may send an instruction to the vehicle for performing a self-maintenance operation, such as an instruction for performing a self-repair process, such as a process for recalibrating one or more operating parameters of a component of the vehicle. In another example, the vehicle may send one or more vehicle values, such as a status value or a statistical value, to the charging station.

[0053] Before explaining at least one embodiment in detail, it should be understood that the embodiment is not necessarily limited in its application to the details of construction and arrangement of components and / or methods set forth in the following description and / or shown in the drawings and / or examples. The embodiments described herein can have other embodiments or can be practiced or implemented in various ways.

[0054] The embodiments may be systems, methods, and / or computer program products. The computer program product may include a computer-readable storage medium (or multiple media) having computer-readable program instructions thereon for causing a processor to implement aspects of the embodiments.

[0055] A computer-readable storage medium may be a tangible device that can hold and store instructions used by an instruction execution device. A computer-readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer-readable storage media includes the following: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, and any suitable combination of the foregoing. As used herein, a computer-readable storage medium is not interpreted as a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagated through a waveguide or other transmission medium (e.g., a light pulse through a fiber optic cable), or an electrical signal transmitted by a wire.

[0056] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a corresponding computing / processing device, or downloaded to an external computer or external storage device via a network (e.g., the Internet, a local area network, a wide area network, and / or a wireless network). The network can include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network, and forwards the computer-readable program instructions to be stored in a computer-readable storage medium in the corresponding computing / processing device.

[0057] The computer-readable program instructions for implementing the operation of the implementation scheme can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code, compiled locally or compiled in real time (JIT), written in any combination of one or more programming languages, the one or more programming languages ​​including: object-oriented programming languages, such as Smalltalk, C++, Java, object-oriented Fortran, etc.; interpreted programming languages, such as JavaScript, Python, etc.; and conventional process programming languages, such as "C" programming language, Fortran or similar programming languages. The computer-readable program instructions can be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer, and partially on a remote computer, or completely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer through any type of network (including a local area network (LAN) or a wide area network (WAN)), or can be connected to an external computer (e.g., through the Internet using an Internet service provider). In some embodiments, electronic circuits including, for example, programmable logic circuits, field programmable gate arrays (FPGAs), coarse-grained reconfigurable architectures (CGRAs), or programmable logic arrays (PLAs) can execute computer-readable program instructions by utilizing state information of the computer-readable program instructions to personalize the electronic circuits so as to perform aspects of the embodiments.

[0058] Various aspects of the embodiments are described herein with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to the embodiments. It should be understood that each box in the flowchart and / or block diagram, and the combination of boxes in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0059] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a means for implementing the functions / actions specified in the flowchart and / or one or more block diagram blocks. These computer-readable program instructions can also be stored in a computer-readable storage medium, which can instruct a computer, a programmable data processing device, and / or other equipment to function in a particular manner, so that the computer-readable storage medium having the instructions stored therein includes an article of manufacture, which includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.

[0060] Computer-readable program instructions may also be loaded into a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable apparatus, or other device implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0061] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functions and operations of possible implementations of the systems, methods and computer program products according to various embodiments. In this regard, each box in the flowchart or block diagram can represent a module, segment or part of an instruction, and the module, segment or part of the instruction includes one or more executable instructions for implementing a specified logical function. In some alternative embodiments, the function annotated in the box can occur in an order different from the order annotated in the figure. For example, in fact, depending on the function involved, the two boxes shown in succession can be executed substantially simultaneously, or sometimes the boxes can be executed in reverse order. It should also be noted that each box illustrated in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented by a system based on dedicated hardware that performs a specified function or action or performs a combination of dedicated hardware and computer instructions.

[0062] Reference now Figure 1 , a schematic block diagram of an exemplary system 100 according to some embodiments is shown. In such embodiments, the charging station 110 includes at least one hardware processor 111 (station processor 111) optionally connected to at least one digital communication network interface 112 (station data interface 112). Optionally, the station data interface 112 includes a digital data communication interface in the charging plug of the charging station 110, such as a serial digital data communication interface or an Ethernet network interface. Optionally, the station data interface 112 includes a wireless digital data network interface, such as a Bluetooth interface or a Wi-Fi interface. Optionally, the wireless digital data network interface includes a Wi-Fi hotspot. Optionally, the station data interface 112 is connected to a local area network, such as an Ethernet network. Optionally, the station data interface 112 is connected to a wide area network, such as the Internet. Optionally, the charging station 110 is an electric vehicle charging station.

[0063] Optionally, the system 100 includes at least one device 120. Optionally, the at least one device 120 is at least one vehicle. For clarity, the following description focuses on one vehicle; however, the following description may apply to more than one vehicle.

[0064] Optionally, the vehicle 120 includes at least one hardware processor 121 (vehicle processor 121) optionally connected to at least one other digital communication network interface 122 (vehicle data interface 122). Optionally, the vehicle processor 121 is optionally connected to the station processor 111 via the station data interface 112. Optionally, the vehicle processor 121 is connected to the station processor 111 via the vehicle data interface 122 in addition to the station data interface 112. Optionally, the vehicle data interface 122 is additionally or alternatively connected to one or more cellular networks, for example to connect to one or more non-volatile digital storage 140 (digital storage 140). Some examples of non-volatile digital storage are storage networks and network-attached storage. Optionally, the vehicle processor 121 retrieves updated digital data from the digital storage 140, optionally via the vehicle data interface 122, via one or more cellular networks. Optionally, the charging station is connected to the digital storage 140, for example via the station data interface 112. Optionally, the updated digital data includes one or more updated computer instruction sets. Optionally, the updated digital data includes one or more updated component configuration value sets for one or more components of the vehicle 120. Optionally, the vehicle data interface 122 is connected to one or more local area networks, such as an Ethernet network, or is connected via a Bluetooth interface or a Wi-Fi interface. Optionally, the vehicle data interface 122 is connected to a Wi-Fi hotspot in the station data interface 112. Optionally, the vehicle processor 121 is connected to the digital storage 140 via the local area network using the vehicle data interface 122. Connecting the digital storage 140 and the vehicle processor 121 via the local area network allows the amount of time required for the vehicle processor 121 to retrieve the updated digital data from the digital storage 140 to be reduced compared to retrieving the updated digital data from another digital storage connected to it using a wide area network (such as a cellular network). Optionally, when the vehicle 120 is not connected to the charging station 110, the station processor 111 optionally stores the updated digital data on the digital storage 140. Optionally, the vehicle processor 121 accesses the digital storage 140 via the station processor 111.

[0065] Optionally, the system 100 includes at least one other hardware processor 131 (other processor 131) that optionally executes one or more user applications. Optionally, the other processor 131 is installed in the other device 130, such as a mobile phone or tablet computer operated by the user 150. Optionally, the other processor 131 is installed in the vehicle 120.

[0066] Optionally, the station processor 111 is connected to at least one additional hardware processor 141 (backend processor). Optionally, the backend processor 141 is at least part of a backend server of the system 100. Optionally, the station processor 111 is connected to the backend processor 141 via at least one digital communication network interface of the charging station 110. Optionally, the vehicle processor 121 retrieves updated digital data from the backend processor 141.

[0067] Optionally, the vehicle 120 includes at least one human machine interface 123 (device HMI 123) optionally connected to the vehicle processor 121. For example, the device HMI 123 can be a touch screen installed in the vehicle 120. Optionally, the device HMI 123 is a button. Optionally, the user 150 provides one or more values ​​to the system 100 via the device HMI 123.

[0068] To update the digital data of the vehicle 120 , in some embodiments described herein, the system 100 implements the following optional method.

[0069] Now also refer to Figure 2 , which shows a flow chart schematically representing an optional operational process 200 according to some embodiments. It should be noted that Figure 2One possible distribution of operations between the various processors of the system 100 is shown, but the steps of the method 200 may be distributed between the processors of the system 100 in other ways. Optionally, when the vehicle 120 is connected to the charging station 110, the station processor 111 calculates in 201 the expected amount of time (charging time) for charging the battery of the vehicle 120. Optionally, before executing 201, the station processor 111 determines, for example by communicating with the backend processor 141, that updated digital data (update) for the vehicle is pending. Optionally, the update includes updated computer instructions. Optionally, the update includes an updated set of component configuration values. Optionally, in the event that an update is determined to be pending for the vehicle, 201 and subsequent steps of the method 200 are performed by the station processor 111 and additionally or alternatively by another processor. Optionally, the charging time is calculated based on user preference values, some examples of which are an identified charging cost (i.e., an identified monetary amount) and an identified battery charge level. Optionally, the charging time is calculated based on one or more other constraints, such as one or more historical values. Some examples of historical values ​​are historical charging times and historical monetary amounts. Optionally, in 201, the station processor 111 retrieves the charging times from the backend processor 141. In 210, the station processor 111 optionally accesses an expected amount of time (update time) for performing a data update of the digital data of the vehicle 120. The update time may differ between vehicle models and may additionally or alternatively depend on the software configuration of the vehicle 120, the vehicle processor workload at the time of the update, etc. Optionally, in 210, the station 111 calculates the update time. Optionally, the update time is calculated by the backend processor 141, and in 210, the station processor 111 retrieves the update time from the backend processor 141. Optionally, the update time is calculated by the other processors 131, and in 210, the station processor 111 retrieves the update time from the other processors 131. Optionally, the update time is calculated by the vehicle processor 121, and in 210, the station processor 111 retrieves the update time from the vehicle processor 121. Optionally, the update time includes an amount of time for backing off the data update. Optionally, at 220, the station processor 111 determines whether the update time is less than the charging time. In the event that the update time is identified as less than the charging time, at 230, the vehicle processor 121 optionally performs an update of one or more instruction sets.

[0070] For the sake of brevity, the noun "update" is hereinafter used to mean "data update", and the two terms are used interchangeably.

[0071] Optionally, in 250, the station processor 111 and the vehicle processor 121 establish one or more digital data communication channels between them, wherein the digital data communication channels include one or more digital data streams. For the sake of brevity, the term data channel is used hereafter to mean one or more digital data communication channels. Optionally, the station processor 111 and the vehicle processor 121 use one or more of the station data interface 112 and the vehicle data interface 122 to establish the data channel. Optionally, the station processor 111 and the vehicle processor 121 use one or more of the station data interface 112 and the vehicle data interface 122 to establish a charging interface between the station processor and the vehicle processor.

[0072] Optionally, vehicle processor 122 provides one or more credential values ​​to charging station 110 for establishing a data channel. For example, when establishing a data channel via a Wi-Fi connection, the credential value may be a username and additionally or alternatively a password. Optionally, the credential value is a certificate.

[0073] When vehicle 120 is connected to charging station 110, the steps of method 200 may be distributed in more than one way among the various processors of system 100. The following description presents some possible implementations, however it should be noted that other combinations are possible.

[0074] Now also refer to Figure 3 , which shows a sequence diagram of another optional operation flow 300 according to some embodiments. In such embodiments, in 301, the station processor 111 sends a request for one or more power level values ​​to the vehicle 120, and optionally, the vehicle processor 121 receives the request. The power level value can be the capacity of the battery of the electric device 120. Another example of a power level is the remaining percentage of the battery. In 310, the station processor 111 optionally receives one or more power values ​​from the vehicle 120, which are optionally sent by the vehicle processor 121 in response to receiving the request in 301. Optionally, in 201, the station processor 111 uses the one or more power level values ​​to calculate the charging time. Optionally, in 201, the station processor 111 retrieves the charging time from the backend processor 141. Optionally, the station processor 111 provides the one or more power level values ​​to the backend processor 141. Optionally, before performing 201, the station processor 111 determines that an update for the vehicle is pending, for example, by communicating with the backend processor 141. Optionally, in the event that an update is determined to be pending for the vehicle, 201 and other steps of method 300 are performed by station processor 111 and additionally or alternatively by another processor.

[0075] Optionally, in 320, the station processor 111 receives one or more user input values ​​from the other processors 131, such as values ​​provided by the user 150 via one or more user applications executed by the other processors 131. For example, the user input value may be an amount of time to charge, such as when the user 150 limits the amount of time to charge. Another example of a user input value is a target percentage of battery capacity, such as when the user 150 limits charging to a target percentage of battery capacity. Optionally, the station processor 111 uses the one or more user input values ​​to calculate the charging time.

[0076] Optionally, the station processor 111 provides one or more indications to the user 150 via one or more user applications. For example, the station processor 111 may provide the user 150 with one or more of the following: an expected duration of charging, an expected duration of performing an update, a description of the instruction set for the update, and an indication of whether an update is possible.

[0077] In 327, optionally, the station processor 111 sends instructions to the vehicle 120 for performing the update, optionally while charging one or more batteries of the vehicle 120. Optionally, the vehicle processor 121 receives the instructions. Optionally, the station processor 111 sends the instructions for performing the update if it is identified in 220 that the update time is less than the charging time.

[0078] In 330, the vehicle processor 121 optionally retrieves the updated digital data. Optionally, the updated digital data includes one or more updated computer instruction sets. Optionally, the updated digital data includes one or more updated component configuration value sets. Optionally, in 330, the station processor 111 optionally provides the updated digital data to the vehicle 120 via a data channel. Optionally, the updated digital data is stored on the charging station 110. Optionally, the station processor 111 optionally accesses the storage 140 via the station data interface 112 to retrieve the updated digital data for providing the updated digital data to the vehicle 120. Optionally, the vehicle processor 121 accesses the storage 140 via a cellular network, for example via the vehicle data interface 122, to retrieve the updated digital data. Optionally, the vehicle processor 121 retrieves the updated digital data from the backend processor 141.

[0079] At 230, the vehicle processor 121 optionally performs the update, optionally while charging one or more batteries of the vehicle 120. Optionally, performing the update is done while charging the one or more batteries. Optionally, performing the update is done after charging the one or more batteries has stopped.

[0080] Optionally, at 325, the station processor 111 receives one or more user confirmation values ​​from one or more user applications, such as from other processors 131. For example, the one or more user applications may display a prompt to the user 150 to confirm that the update is to be performed. Optionally, the station processor 111 receives one or more user confirmation values ​​from the vehicle processor 122. Optionally, the station processor 111 sends instructions for performing the update to the vehicle 120 upon receipt of the one or more user confirmation values.

[0081] Optionally, in 350, the station processor 111 sends a maintenance instruction to the vehicle 120 for performing one or more other operations. Some examples of another operation include, but are not limited to, diagnostic operations and self-maintenance operations of the vehicle. Optionally, the vehicle processor 121 receives the maintenance instruction. Optionally, in 355, the vehicle processor 121 performs one or more other operations, optionally while charging one or more batteries. Optionally, the vehicle processor 121 performs one or more other operations in response to receiving the maintenance instruction.

[0082] In 360, the station processor 111 optionally sends a request for one or more vehicle values ​​to the vehicle 120 via a data channel. Optionally, the vehicle processor 121 receives the request for one or more vehicle values. The vehicle value may be a status value of the vehicle 120, for example, for diagnostics. Another example of a vehicle value is a statistical value collected by the vehicle processor 121. In 365, optionally, the vehicle processor 121 sends the one or more vehicle values, optionally in response to receiving the request for one or more vehicle values.

[0083] It should be noted that 350 and 360 may be performed in any order, and thus 355 and 365 may be performed in any order.

[0084] As noted above, the steps of method 200 may be distributed among the processors of system 100 in more than one manner. Figure 4, which shows a sequence diagram of another optional operational flow 400 according to some embodiments. In such embodiments, calculating the charging time and the update time is performed by a user application executed by the other processor 131 on the other device 130. Therefore, in such embodiments, the other processor 131 requests one or more power values ​​from the device processor 121 in 301, and in 310, the device processor 121 optionally sends the one or more power values ​​to the other processor 131. Optionally, in 201, the other processor 131 optionally uses the one or more power values ​​to calculate the charging time, and in 210, the other processor 131 optionally calculates the update time. Optionally, before executing 201, the other processor 131 determines that an update is pending for the vehicle, for example, by communicating with the backend processor 141. Optionally, in the event that an update is determined to be pending for the vehicle, 201 and subsequent steps of the method 400 are performed by the other processor 131 or another processor. Optionally, in 320, the other processor 131 receives one or more user input values, and optionally further uses one or more other values ​​to calculate the charging time. Optionally, in 327, the other processor 131 sends instructions for performing data updates to the vehicle 121. Optionally, the other processor performs 327 if one or more confirmation values ​​are received from the user 150. Optionally, the other processor 131 sends instructions for performing updates if it is identified in 220 that the update time is less than the charging time.

[0085] Now also refer to Figure 5 , which shows a sequence diagram of an additional optional operational flow 500 according to some embodiments. In such embodiments, calculating the charging time and the update time is performed by the vehicle processor 121. Therefore, in such embodiments, in 310, the vehicle processor 121 optionally accesses one or more power values, and in 201, the vehicle processor 121 optionally uses the one or more power values ​​to calculate the charging time. Optionally, before executing 201, the vehicle processor 121 determines that an update is pending for the vehicle, for example, by communicating with the backend processor 141 or the station processor 111. Optionally, in the case of determining that an update is pending for the vehicle, 201 and subsequent steps of the method 500 are performed by the vehicle processor 121 and additionally or alternatively by another processor. Optionally, in 320, the vehicle processor 121 optionally receives one or more user input values. Optionally, the vehicle processor 121 receives one or more user input values ​​from other processors 131 installed in other devices 130. Optionally, the vehicle processor 121 receives one or more user input values ​​via the vehicle HMI 123. Optionally, the vehicle processor 121 further uses one or more user input values ​​to calculate the charging time.

[0086] Optionally, in 210, the vehicle processor 121 calculates the update time. Optionally, the vehicle processor 121 optionally receives the update time via the data channel from the station processor 111. In 327, optionally, the vehicle processor 121 optionally decides to perform the update if it is identified in 220 that the update time is less than the charging time.

[0087] Optionally, the vehicle processor 121 decides to perform the update if one or more user confirmation values ​​are received in 325. Optionally, the vehicle processor 121 receives one or more user confirmation values ​​from the user 150 via the vehicle HMI 123. Optionally, the vehicle processor 121 receives one or more user confirmation values ​​from the other processor 131. Optionally, the vehicle processor 121 performs the update in 230 if one or more user confirmation values ​​are received.

[0088] The description of the various embodiments has been presented for illustrative purposes and is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is selected to best explain the principles of the embodiments, practical applications or technical improvements of technologies found in the marketplace, or to enable other persons of ordinary skill in the art to understand the embodiments disclosed herein.

[0089] It is expected that during the patent term maturing from this application, many related charging stations and vehicles will be developed, and the scope of the terms "charging station" and "vehicle" is intended to include all such a priori new technologies.

[0090] As used herein, the term "about" refers to ± 10%.

[0091] The terms "including," "comprising," "having," and variations thereof mean "including but not limited to." The terms encompass the terms "consisting of" and "consisting essentially of.

[0092] The phrase "consisting essentially of means that the composition or method may include additional ingredients and / or steps, but only when the additional ingredients and / or steps do not materially alter the basic and novel characteristics of the claimed composition or method.

[0093] As used herein, the singular forms "a", "an", and "the" include plural references unless the context clearly dictates otherwise. For example, the term "a compound" or "at least one compound" may include a plurality of compounds, including mixtures thereof.

[0094] The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any implementation described as “exemplary” is not necessarily to be construed as preferred or advantageous over other implementations and / or to exclude the incorporation of features from other implementations.

[0095] As used herein, the word "optionally" means that something is provided in some embodiments but not in other embodiments. Unless multiple "optional" features conflict, any particular embodiment may include such features.

[0096] Throughout this application, various embodiments can be presented in the form of ranges. It should be understood that the description of the range format is only for convenience and simplicity, and should not be interpreted as a rigid limitation on the scope of the embodiment. Therefore, the description of the range should be considered as having specifically disclosed all possible sub-ranges and each numerical value in the range. For example, the description of the range such as from 1 to 6 should be considered as having specifically disclosed sub-ranges, such as from 1 to 3, from 1 to 4, from 1 to 5, from 2 to 4, from 2 to 6, from 3 to 6, etc., and each number in the range, such as 1, 2, 3, 4, 5 and 6. Regardless of the width of the range, it is applicable.

[0097] Whenever a numerical range is indicated herein, it is meant to include any cited numeral (fractional or integer) within the indicated range. The phrases "range / range between" a first indicated number and a second indicated number and "range / range from" a first indicated number to" a second indicated number are used interchangeably herein and are meant to include the first indicated number and the second indicated number and all fractions and integers therebetween.

[0098] It should be understood that certain features of the embodiments described in the context of separate embodiments for the sake of clarity may also be provided in combination in a single embodiment. Conversely, various features of the embodiments described in the context of a single embodiment for the sake of brevity may also be provided separately, or in any suitable sub-combination, or as appropriate in any other described embodiment. Certain features described in the context of individual embodiments should not be considered essential features of those embodiments unless the described embodiments are inoperative without those elements.

[0099] Although the embodiments have been described in conjunction with their specific embodiments, it is apparent that many alternatives, modifications and variations are apparent to those skilled in the art. Therefore, it is intended to encompass all such alternatives, modifications and variations that fall within the spirit and broad scope of the appended claims.

[0100] It is the intention of the applicant that all publications, patents and patent applications mentioned in this specification are incorporated by reference in their entirety into this specification, just as each individual publication, patent or patent application is specifically and individually noted as being incorporated by reference herein when cited. In addition, the reference or identification of any reference in this application should not be construed as an admission that this reference can be used as prior art of the present invention. In terms of the use of section headings, they should not be construed as necessary limitations. In addition, any priority document of the present application is hereby incorporated by reference herein in its entirety.

Claims

1. A vehicle charging station (charging station), include: At least one hardware processor (station processor) configured to, when a vehicle is connected to the charging station: sending a request for at least one power level value to the vehicle; and In response to receiving the at least one power level value from the vehicle: calculating an expected amount of time for charging at least one battery of the vehicle (charging time); calculating an expected amount of time for performing an update of digital data of the vehicle (an update time), wherein the update time includes an amount of time for rolling back the update; and In the event that it is identified from the time comparison test that the update time is less than the charging time, instructions for performing the update are sent to the vehicle while the at least one battery is being charged.

2. The charging station of claim 1, further comprising at least one digital communication network interface (station data interface) connected to the station processor; wherein the vehicle includes at least one other hardware processor (vehicle processor); wherein the vehicle processor and the station processor are further configured to establish at least one digital data communication channel (data channel) between the vehicle processor and the station processor via the station data interface; and Wherein the request for the at least one power level value is sent to the vehicle via the data channel using the station data interface.

3. The charging station of claim 2, wherein the station data interface comprises at least one of: a digital data communication interface in a charging plug of the charging station; A digital data communication interface in a charging socket of the charging station; and Wireless digital data network interface.

4. The charging station of claim 2, wherein the station data interface comprises a wireless digital data network interface; and The vehicle processor is further configured to provide at least one credential value to the charging station for establishing the data channel. 5 . The charging station of claim 2 , wherein the station processor is further configured to provide updated digital data to the vehicle using the data channel for performing the updating.

6. The charging station of claim 2, wherein the station processor is further configured to connect via the station data interface to at least one user application executed by at least one additional hardware processor.

7. The charging station of claim 6, wherein the station processor is further configured to receive at least one user input value from the at least one user application for use in calculating the charging time.

8. The charging station of claim 6, wherein the station processor is further configured to send instructions to the vehicle for performing the update upon receiving at least one user confirmation value from the at least one user application.

9. The charging station of claim 1, wherein the station processor is further configured to: sending a request for at least one vehicle data value to the vehicle via a data channel; and The at least one vehicle data value is received from the vehicle via the data channel.

10. The charging station of claim 1, wherein the station processor is further configured to send maintenance instructions to the vehicle via a data channel for performing at least one of: a diagnostic operation and a self-maintenance operation.

11. The charging station of claim 1, wherein the digital data comprises one or more sets of computer instructions.

12. The charging station of claim 1, wherein the digital data comprises one or more component configuration value sets.

13. A method for a vehicle charging station (charging station), wherein include: When the vehicle is connected to the charging station: sending a request for at least one power level value to the vehicle; and In response to receiving the at least one power level value from the vehicle: calculating an expected amount of time for charging at least one battery of the vehicle (charging time); calculating an expected amount of time for performing an update of digital data of the vehicle (an update time), wherein the update time includes an amount of time for rolling back the update; and In the event that it is identified from the time comparison test that the update time is less than the charging time, instructions are sent to the vehicle for performing the update while charging at least one battery of the vehicle.

14. A vehicle, include: At least one hardware processor (vehicle processor) configured to: When the vehicle is connected to a vehicle charging station (charging station): providing the at least one power level value to the charging station in response to receiving a request for the at least one power level value from the charging station; as well as The updating of the digital data of the vehicle is performed in response to receiving an instruction from the charging station to perform the updating of the digital data of the vehicle while at least one battery of the vehicle is being charged.

15. The vehicle of claim 14, further comprising at least one digital communications network interface (VDI) connected to said vehicle processor; Wherein the vehicle processor is further configured to provide the at least one power level value to the charging station via the vehicle data interface.

16. The vehicle of claim 15, wherein performing the updating comprises retrieving updated digital data via the vehicle data interface.

17. The vehicle of claim 16, wherein the updated digital data is retrieved from the charging station.

18. The vehicle of claim 16, wherein the vehicle data interface is connected to at least one cellular data communications network; and Wherein retrieving said updated digital data is via said at least one cellular data communications network.

19. The vehicle of claim 16, wherein retrieving the updated digital data is via at least one digital data communication channel (data channel) established with the charging station using the vehicle data interface.

20. The vehicle of claim 15, wherein the vehicle processor is further configured to transmit the at least one vehicle data value to the charging station via the vehicle data interface in response to receiving a request for the at least one vehicle data value from the charging station while charging the at least one battery.

21. The vehicle of claim 14, wherein the vehicle processor is further configured to perform at least one operation in response to receiving a maintenance instruction for at least one operation from the charging station while charging the at least one battery, the at least one operation being selected from a group of operations including diagnostic operations and self-maintenance operations.

22. The vehicle of claim 14, further comprising a human-machine interface for interacting with a user; The vehicle processor is further configured to: receiving at least one confirmation value from the user via the human-machine interface; and The updating is performed upon receipt of the at least one confirmation value.

23. The vehicle of claim 14, wherein the digital data comprises one or more sets of computer instructions.

24. The vehicle of claim 14, wherein the digital data includes one or more component configuration value sets.

25. A method for a vehicle, wherein include: When the vehicle is connected to a vehicle charging station (charging station): providing the at least one power level value to the charging station in response to receiving a request for the at least one power level value from the charging station; as well as The updating of the digital data of the vehicle is performed in response to receiving an instruction from the charging station to perform the updating of the digital data of the vehicle while at least one battery of the vehicle is being charged.

26. A system for updating digital data in a vehicle, wherein include: A vehicle comprising at least one hardware processor (vehicle processor); as well as A vehicle charging station (charging station), the vehicle charging station (charging station) comprising at least one other hardware processor (station processor), the at least one other hardware processor (station processor) being configured to, when the vehicle is connected to the charging station: sending a request for at least one power level value to the vehicle; and In response to receiving the at least one power level value from the vehicle: calculating an expected amount of time for charging at least one battery of the vehicle (charging time); calculating an expected amount of time for performing an update of the digital data of the vehicle (an update time), wherein the update time includes an amount of time for rolling back the update; and sending an instruction to the vehicle for performing the update if it is identified according to the time comparison test that the update time is less than the charging time; wherein the vehicle processor is configured to, when the vehicle is connected to the charging station: providing the at least one power level value to the charging station in response to receiving the request for the at least one power level value from the charging station; and The updating is performed in response to receiving the instruction to perform the updating from the charging station while the at least one battery is being charged.

27. The system of claim 26, wherein the digital data comprises one or more sets of computer instructions.

28. The system of claim 26, wherein the digital data comprises one or more component configuration value sets.

29. A method for updating digital data in a vehicle, wherein include: When the vehicle is connected to a vehicle charging station (charging station): calculating an expected amount of time for charging at least one battery of the vehicle (charging time); calculating an expected amount of time for performing an update of digital data of the vehicle (an update time), wherein the update time includes an amount of time for rolling back the update; and In the event that it is identified from the time comparison test that the update time is less than the charging time, the updating is performed while the at least one battery is being charged.

30. The method of claim 29, wherein calculating the charging time is based on at least one power level value of the vehicle.

31. The method of claim 30, further comprising when the vehicle is connected to the charging station: sending a request for the at least one power level value from the charging station to the vehicle; and The at least one power level value is provided by the vehicle to the charging station in response to receiving the request for the at least one power level value.

32. The method of claim 29, wherein performing the updating include: sending, from the charging station to the vehicle, instructions for performing the updating; as well as The updating is performed by at least one hardware processor (vehicle processor) of the vehicle in response to receiving the instruction to perform the updating from the charging station while the at least one battery is being charged.

33. The method of claim 29, wherein the digital data comprises one or more sets of computer instructions.

34. The method of claim 29, wherein the digital data comprises one or more component configuration value sets.