BMS direct current charging non-inductive upgrading method and device, electronic equipment and storage medium

Abstract

According to the BMS direct current charging non-inductive upgrading method and device, the electronic equipment and the storage medium, online upgrading of software firmware is synchronously carried out in the vehicle direct current charging process, and high-stability non-inductive flashing is achieved. According to the scheme, the defects of a traditional mode are effectively avoided; compared with offline UDS flashing of a 4S store, normal use of the vehicle is not affected at all; compared with remote OTA flashing, the system has the advantages that flashing failure or system reset risks caused by network problems are completely eradicated by the aid of stable and reliable charging connection, the upgrading process is independent of a CAN (controller area network) and the internet in the vehicle, and extra loads cannot be caused. Meanwhile, according to the scheme, hacker attacks are effectively defended through a safe communication mechanism, upgrading information is stored by using technologies such as a block chain, and complete historical tracing and clear three-party responsibility definition are realized. According to the scheme, a high-performance chip does not need to be upgraded for the BMS or an advanced gateway does not need to be additionally arranged for the vehicle, and the vehicle cost is remarkably reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of BMS upgrading, and in particular to a BMS direct-current charging non-inductive upgrading method and device, electronic equipment and a storage medium. BACKGROUND

[0002] At present, when the traditional technology upgrades the software of the BMS of an electric vehicle, it mainly relies on the following two technical paths: First, offline diagnosis upgrading (4S store mode): the vehicle needs to go to the service center (4S store), and the technical personnel performs software flashing on the BMS controller through a special diagnostic device (such as a diagnostic instrument) in a wired connection mode (usually through the OBD interface) according to the UDS (Unified Diagnostic Services) protocol.

[0003] Second, online remote upgrading (OTA mode): through a cellular network (4G / 5G) or Wi-Fi, the upgrade firmware package is remotely transmitted from the OTA cloud server to the T-Box (remote information processor) or network management of the vehicle, and then is transmitted to the BMS controller through the vehicle-mounted network (such as the CAN bus) for execution of the upgrade.

[0004] The above two technical paths have the following technical problems: First, user experience and efficiency problems: 4S store mode: low efficiency and poor experience. The user needs to specially arrange time to go to the store, which is time-consuming and laborious, and the vehicle cannot be used during this period, which greatly affects the user experience and vehicle operation efficiency.

[0005] OTA mode: there are usage restrictions and risks. In order to ensure that the upgrade process does not lose power, it is usually necessary to perform the upgrade in the “engine off” state. At this time, the BMS and other controllers are still working, and the power consumption is significantly increased, which is a great test for the battery power. Once the battery is depleted, the upgrade will be interrupted, causing the system to “brick”, and causing serious after-sales problems.

[0006] Second, economic efficiency and cost problems: OTA mode: significantly increases vehicle manufacturing costs. To realize the OTA function, high-performance T-Box, gateway and other hardware modules need to be added to the vehicle, and a complex cloud server cluster and security management system need to be built, and these costs will eventually be passed on to the vehicle price.

[0007] 4S store mode: increases user maintenance costs. Although the single vehicle cost may be low, the user needs to bear the time cost of going to and from the store and possible service fees.

[0008] Third, functional safety and reliability problems: OTA mode: interferes with normal vehicle functions, introduces safety risks. The upgrade process will significantly increase the CPU load of the BMS controller. If the upgrade timing is not appropriate (such as during driving or charging), it may cause insufficient resources for the BMS to handle real-time tasks, causing abnormal battery management functions, and even causing vehicle power interruption, posing a serious safety hazard. In addition, complex networks and environmental factors also reduce the reliability of the upgrade process, with a high failure rate.

[0009] Fourth, information security and ecological coordination problem: OTA mode: weak security architecture, vulnerable to attacks. Its upgrade path is long (cloud -> T-Box -> gateway -> BMS), and the attack surface is wide. In particular, the gateway, as the core of the in-vehicle network, once breached, hackers can inject malicious firmware into critical controllers such as BMS, thereby controlling the vehicle. Relying solely on network layer isolation cannot defend against attacks targeting firmware itself.

[0010] Industrial ecological gap: lack of trust and coordination mechanism. The current OTA system is built independently by each car company, forming a "data island". Battery manufacturers, BMS suppliers, charging operators and other key roles cannot participate in the verification of upgrade security, resulting in a lack of trust among multiple parties and the inability to establish industry-wide collaborative security verification and traceability capabilities.

[0011] In summary, the traditional BMS upgrade solution is difficult to balance user experience, cost control, functional safety and information security at the same time. SUMMARY

[0012] Therefore, the purpose of the present application is to provide a BMS direct current charging non-inductive upgrade method, device, electronic equipment and storage medium to alleviate the technical problem that the traditional BMS upgrade solution is difficult to balance user experience, cost control, functional safety and information security at the same time.

[0013] In a first aspect, the present application provides a BMS direct current charging non-inductive upgrade method, comprising: The vehicle manufacturer generates a BMS upgrade firmware, encrypts and digitally signs it using an asymmetric encryption private key, and uploads it to the cloud platform of the charging pile; The cloud platform decrypts the encrypted BMS upgrade firmware and verifies the digital signature. After passing, it distributes the BMS upgrade firmware to each charging pile using a blockchain network; When the vehicle is charging, the vehicle sends vehicle identification information and BMS version number to the charging pile through the charging handshake protocol, so that the charging pile determines whether the vehicle needs to perform an upgrade according to the BMS version number; If an upgrade is needed, the charging pile transmits the BMS upgrade firmware to the vehicle's BMS through the charging CAN bus during the charging process within the communication interval of the charging message. The BMS of the vehicle receives and verifies the BMS upgrade firmware after the upgrade is performed, and uploads the upgrade result information to the blockchain network for notarization.

[0014] Further, the vehicle manufacturer generates the BMS upgrade firmware, encrypts and digitally signs it using the asymmetric encryption private key, and uploads it to the cloud platform of the charging pile, including: The vehicle manufacturer sends firmware update information to the cloud platform; The cloud platform receives the firmware update information and arbitrates whether to agree to update; If the cloud platform arbitrates to agree to update, it feeds back the public key information of asymmetric encryption to the vehicle manufacturer; The vehicle manufacturer receives the public key information and calculates the corresponding asymmetric encryption private key; The vehicle manufacturer encrypts and digitally signs the BMS upgrade firmware using the asymmetric encryption private key to generate the encrypted BMS upgrade firmware; The vehicle manufacturer uploads the encrypted BMS upgrade firmware to the designated path of the cloud platform.

[0015] Further, the cloud platform decrypts the encrypted BMS upgrade firmware, including: The cloud platform decrypts the encrypted BMS upgrade firmware using the corresponding public key and verifies the digital signature.

[0016] Further, the vehicle sends vehicle identification information and BMS version number to the charging pile through the charging handshake protocol when charging in direct current, so that the charging pile determines whether the vehicle needs to perform an upgrade according to the BMS version number, including: The vehicle sends a charging application to the charging pile; The charging pile and the vehicle complete handshake interaction, and after the handshake is completed, the vehicle is requested to obtain the vehicle identification information and the BMS version number; The vehicle feeds back the vehicle identification information and the BMS version number to the charging pile; After the charging pile obtains the vehicle identification information and the BMS version number, it feeds back the vehicle identification information and the BMS version number to the cloud platform; The cloud platform determines whether the vehicle needs to be upgraded according to the vehicle identification information and the BMS version number: If the result is that no upgrade is needed, feed back to the charging pile that no upgrade is needed; If the result is that an upgrade is needed, the BMS upgrade firmware is transmitted to the charging pile; The charging pile forwards the BMS upgrade firmware to the vehicle by using a charging CAN bus during a direct current charging process after receiving the BMS upgrade firmware.

[0017] Further, the BMS of the vehicle receives and verifies the BMS upgrade firmware, performs upgrade, and uploads upgrade result information to the blockchain network for storage. The vehicle decrypts and installs the BMS upgrade firmware according to an encryption method agreed by the vehicle factory after receiving the BMS upgrade firmware of the charging pile. The vehicle confirms whether the BMS upgrade firmware is correct. If the judgment result is incorrect, the charging pile is instructed to retransmit the BMS upgrade firmware. If the judgment result is correct, the upgrade is completed.

[0018] Further, the charging CAN bus is used to multiplex and expand a PGN 5888 power storage battery reserved message field in the GB / T 27930 protocol.

[0019] Further, the upgrade result information includes a firmware version, a firmware hash value, a vehicle factory identifier, a charging pile identifier, a vehicle VIN code, an upgrade time, and an upgrade result status.

[0020] In a second aspect, the application further provides a BMS direct current charging non-inductive upgrade device, which includes: An encryption uploading unit is configured to generate a BMS upgrade firmware by a vehicle factory, encrypt and digitally sign the BMS upgrade firmware by using an asymmetric encryption private key, and upload the BMS upgrade firmware to a cloud platform of a charging pile. A decryption distribution unit is configured to decrypt the encrypted BMS upgrade firmware by the cloud platform, verify the digital signature, and distribute the BMS upgrade firmware to each charging pile by using a blockchain network after verification. A sending unit is configured to send vehicle identification information and a BMS version number to a charging pile by using a charging handshake protocol during direct current charging of a vehicle, so that the charging pile determines whether the vehicle needs to perform upgrade according to the BMS version number. A transmission unit is configured to transmit the BMS upgrade firmware to a BMS of a vehicle by using a charging CAN bus in a communication interval of a charging message during a direct current charging process of the charging pile if the vehicle needs to perform upgrade. An upgrade unit is configured to receive and verify the BMS upgrade firmware by the BMS of the vehicle, perform upgrade, and upload upgrade result information to the blockchain network for storage.

[0021] In a third aspect, the present application also provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program capable of running on the processor, and the processor executes the computer program to implement the method of the first aspect.

[0022] In a fourth aspect, the present application also provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program is run by a processor to execute the method of the first aspect.

[0023] The BMS direct-current charging non-inductive upgrading method provided by the present application comprises the following steps: a vehicle factory generates a BMS upgrading firmware, encrypts and digitally signs the BMS upgrading firmware by using an asymmetric encryption private key, and then uploads the BMS upgrading firmware to a cloud platform of a charging pile; the cloud platform decrypts the encrypted BMS upgrading firmware, verifies the digital signature, and, after passing the verification, distributes the BMS upgrading firmware to each charging pile by using a blockchain network; when a vehicle is directly charged, the vehicle sends vehicle identification information and a BMS version number to the charging pile by using a charging handshake protocol, so that the charging pile determines whether the vehicle needs to be upgraded according to the BMS version number; if the vehicle needs to be upgraded, the charging pile transmits the BMS upgrading firmware to the BMS of the vehicle by using a charging CAN bus in a communication interval of a charging message during a direct-current charging process; and the BMS of the vehicle receives and verifies the BMS upgrading firmware, performs upgrading, and uploads upgrading result information to the blockchain network for notarization. As can be seen from the above description, in the BMS direct-current charging non-inductive upgrading method, online upgrading of software firmware is simultaneously performed during a direct-current charging process of a vehicle, thereby realizing high-stability non-inductive flashing. The scheme effectively avoids the drawbacks of traditional methods: compared with offline UDS flashing in a 4S store, the scheme does not affect normal use of the vehicle at all; compared with remote OTA flashing, the scheme uses a stable and reliable charging connection to eliminate the risk of flashing failure or system reset caused by network problems, and the upgrading process is independent of a vehicle internal CAN network and the Internet, and thus does not cause additional load. At the same time, the scheme effectively prevents hacker attacks by using a secure communication mechanism, and uses technologies such as blockchain to notarize upgrading information, thereby realizing complete historical tracing and clear three-party responsibility definition (for example, if a fault is caused by a battery model, the fault can be traced back by using a digital signature record of a battery factory). In addition, the scheme does not need to use a high-performance chip for BMS upgrading or add an advanced gateway to a vehicle, thereby significantly reducing the overall vehicle cost, and taking into account user experience, cost control, functional safety and information safety, thereby solving the technical problem that traditional BMS upgrading schemes are difficult to take into account user experience, cost control, functional safety and information safety at the same time. BRIEF DESCRIPTION OF DRAWINGS

[0024] In order to make the technical solutions in the specific embodiments or prior art of the present application clearer, the drawings needed in the specific embodiments or prior art description will be briefly introduced as follows. Obviously, the drawings in the following description are some embodiments of the present application, and all other embodiments obtained by those of ordinary skill in the art without any creative work on the basis of these drawings also belong to the protection scope of the present application.

[0025] Figure 1 A flowchart of a BMS direct-current charging non-inductive upgrading method provided for an embodiment of the present application is shown in FIG. 1. Figure 2 A flowchart of BMS direct-current charging non-inductive upgrading provided for an embodiment of the present application is shown in FIG. 2. Figure 3 A phase schematic diagram of direct-current charging provided for an embodiment of the present application is shown in FIG. 3. Figure 4 A flowchart of direct-current charging provided for an embodiment of the present application is shown in FIG. 4. Figure 5 A related schematic diagram of using an asymmetric encryption private key to encrypt and digitally sign BMS upgrading firmware provided for an embodiment of the present application is shown in FIG. 5. Figure 6 A related schematic diagram of performing upgrading provided for an embodiment of the present application is shown in FIG. 6. Figure 7 A schematic diagram of overall implementation modules provided for an embodiment of the present application is shown in FIG. 7. Figure 8 A schematic diagram of a BMS direct-current charging non-inductive upgrading device provided for an embodiment of the present application is shown in FIG. 8. Figure 9 A schematic diagram of an electronic device provided for an embodiment of the present application is shown in FIG. 9. DETAILED DESCRIPTION

[0026] The technical solutions of the present application will be described in detail below with embodiments. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without any creative work also belong to the protection scope of the present application.

[0027] The conventional BMS upgrading scheme is difficult to simultaneously consider user experience, cost control, functional safety and information safety.

[0028] Based on this, in the BMS direct-current charging non-inductive upgrading method, the online upgrading of the software and firmware is synchronously performed during the direct-current charging of the vehicle, and high-stability non-inductive flashing is realized. Compared with the UDS flashing offline in the 4S store, the scheme does not affect the normal use of the vehicle; compared with the remote OTA flashing, the scheme uses the stable and reliable charging connection to eliminate the risk of flashing failure or system reset caused by network problems, and the upgrading process is independent of the vehicle internal CAN network and the Internet, and does not cause additional load. At the same time, the scheme effectively prevents hacker attacks through a safe communication mechanism, and stores the upgrading information by using the block chain technology, so that complete historical tracing and clear three-party responsibility definition (for example, if a fault is caused by a battery model problem, the fault can be traced back through the digital signature record of the battery factory). In addition, the scheme does not need to upgrade high-performance chips for the BMS or add advanced gateways to the vehicle, which significantly reduces the vehicle cost, and balances the user experience, cost control, functional safety and information security.

[0029] To facilitate the understanding of the present embodiment, first, a BMS direct-current charging non-inductive upgrading method disclosed by the present embodiment is introduced in detail.

[0030] Embodiment one: According to the present embodiment, an embodiment of a BMS direct-current charging non-inductive upgrading method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a group of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order from here.

[0031] Figure 1 is a flowchart of a BMS direct-current charging non-inductive upgrading method according to the present embodiment, as shown in Figure 1 The method comprises the following steps: Step S102, the vehicle factory generates the BMS upgrading firmware, encrypts and digitally signs it using an asymmetric encryption private key, and uploads it to the cloud platform of the charging pile; Step S104, the cloud platform decrypts the encrypted BMS upgrading firmware and verifies the digital signature, and after passing, distributes the BMS upgrading firmware to each charging pile by using the block chain network; Step S106, the vehicle sends the vehicle identification information and the BMS version number to the charging pile through the charging handshake protocol during direct-current charging, so that the charging pile judges whether the vehicle needs to perform upgrading according to the BMS version number; Step S108, if upgrading is needed, the charging pile transmits the BMS upgrading firmware to the BMS of the vehicle in the communication interval of the charging message by using the charging CAN bus during the direct-current charging process; Step S110, the BMS of the vehicle receives and verifies the BMS upgrade firmware after the upgrade is performed, and uploads the upgrade result information to the blockchain network for notarization.

[0032] In the embodiment of the application, the BMS direct-current charging inductiveless upgrade process is divided into the following stages, referring to Figure 2 : 1. The vehicle factory releases the software update firmware (i.e. BMS upgrade firmware) corresponding to the vehicle model; 2. The BMS upgrade firmware to be updated is encrypted and appended with a digital signature according to the asymmetric encryption algorithm (private key encryption, i.e. asymmetric encryption private key encryption) agreed with the official cloud platform of the charging pile, and uploaded to the cloud platform; 3. After the cloud platform obtains the encrypted BMS upgrade firmware, it is decrypted and the digital signature is verified. After verification, it is confirmed that it is the correct BMS upgrade firmware uploaded. The BMS upgrade firmware is updated to each charging pile through the blockchain; 4. When the vehicle is direct-current charging, the charging pile checks whether the current vehicle needs to be updated. If it needs to be updated, the BMS upgrade firmware is updated to the vehicle (specifically to the BMS of the vehicle) during the vehicle charging process by using the charging CAN bus.

[0033] The communication interval of the above charging message refers to the transmission in the message interaction gap in the charging handshake stage, the charging parameter configuration stage or the charging cycle of the charging process, so as to avoid affecting the normal charging process. The stages of direct-current charging are as shown in Figure 3 , and the process of direct-current charging is as shown in Figure 4 . In the process of the charging stage, the vehicle identification information and the BMS version number are added to the process 1 in the circle Figure 4 , and the BMS upgrade firmware is added to the transmission in the process 2 in the circle.

[0034] The application provides a BMS direct-current charging non-inductive upgrading method, which comprises the following steps: a vehicle factory generates BMS upgrading firmware, and uploads the BMS upgrading firmware to a cloud platform of a charging pile after the BMS upgrading firmware is encrypted and digitally signed by using an asymmetric encryption private key; the cloud platform decrypts the encrypted BMS upgrading firmware, and verifies the digital signature, and after passing the verification, the BMS upgrading firmware is distributed to each charging pile by using a block chain network; when a vehicle is directly charged, the vehicle sends vehicle identification information and a BMS version number to the charging pile by using a charging handshake protocol, so that the charging pile determines whether the vehicle needs to be upgraded according to the BMS version number; if the vehicle needs to be upgraded, the charging pile transmits the BMS upgrading firmware to the BMS of the vehicle by using a charging CAN bus in a communication interval of charging messages during the direct-current charging process; and the BMS of the vehicle receives and verifies the BMS upgrading firmware, and then performs the upgrading, and uploads the upgrading result information to the block chain network for notarization. As known from the above description, in the BMS direct-current charging non-inductive upgrading method, the online upgrading of the software firmware is simultaneously performed during the direct-current charging process of the vehicle, and high-stability non-inductive flashing is realized. The scheme effectively avoids the disadvantages of the traditional method: compared with the UDS flashing in the 4S store, the scheme does not affect the normal use of the vehicle; compared with the remote OTA flashing, the scheme uses the stable and reliable charging connection, and eliminates the risk of flashing failure or system reset caused by network problems, and the upgrading process is independent of the vehicle internal CAN network and the Internet, and does not cause additional load. Meanwhile, the scheme effectively prevents hacker attacks by using a safe communication mechanism, and uses the block chain technology to notarize the upgrading information, realizes complete historical tracing and clear three-party responsibility definition (for example, if a fault is caused by a battery model problem, the fault can be traced back by using the digital signature record of the battery factory). In addition, the scheme does not need to use a BMS upgrading high-performance chip or add a high-level gateway to the vehicle, and the whole vehicle cost is significantly reduced, and the user experience, cost control, functional safety and information safety are considered, and the technical problem that the traditional BMS upgrading scheme is difficult to simultaneously consider the user experience, cost control, functional safety and information safety is solved.

[0035] The above describes the BMS direct-current charging non-inductive upgrading method, and the specific contents involved in the method are described in detail below.

[0036] In an optional embodiment of the application, the vehicle factory generates the BMS upgrading firmware, and uploads the BMS upgrading firmware to the cloud platform of the charging pile after the BMS upgrading firmware is encrypted and digitally signed by using the asymmetric encryption private key, and the specific steps include the following steps: (1) The vehicle factory sends the firmware updating information to the cloud platform; (2) The cloud platform receives the firmware updating information and performs arbitration to determine whether to agree to update; (3) If the cloud platform agrees to update after arbitration, the cloud platform feeds back the public key information of the asymmetric encryption to the vehicle factory; (4) The car manufacturer receives the public key information and calculates the corresponding asymmetric encryption private key; (5) The car manufacturer uses an asymmetric encryption private key to encrypt and digitally sign the BMS upgrade firmware, generating the encrypted BMS upgrade firmware; (6) The vehicle manufacturer uploads the encrypted BMS upgrade firmware to the designated path on the cloud platform.

[0037] Specifically, traditionally, automakers release BMS firmware updates directly via the network to the vehicle's gateway, which then updates the BMS firmware. This frequently increases the load on the internet and the vehicle's CAN bus. A better approach is for automakers to first provide the firmware update information (including the reason for the update) to the cloud platform. Figure 5 As shown, the cloud platform arbitrates whether to update based on the firmware update information provided by the car manufacturer (the arbitration criteria include at least one of the following: the car manufacturer's authorization level, the compliance of the firmware update information format, and the cloud platform's resource load status). If the update is approved, the cloud platform sends the asymmetric encryption public key information (generated by the cloud platform) back to the car manufacturer. The car manufacturer calculates the corresponding asymmetric encryption private key (the car manufacturer calculates the corresponding asymmetric encryption private key using a pre-defined key derivation function based on the public key information). Then, the car manufacturer uses the asymmetric encryption private key to encrypt and digitally sign the BMS upgrade firmware (encryption and digital signing refer to: encrypting the BMS upgrade firmware using the asymmetric encryption private key to generate ciphertext; signing the hash value of the BMS upgrade firmware using the asymmetric encryption private key to generate a digital signature; combining the ciphertext and the digital signature to form a secure firmware data package, i.e., the encrypted BMS upgrade firmware, which avoids tampering attacks by hackers). After the car manufacturer updates the encrypted BMS upgrade firmware to the designated path on the cloud platform, the cloud platform decrypts and verifies the signature. If the verification is successful, the BMS upgrade firmware will be archived; if the verification fails, the vehicle manufacturer will be notified to update the public key and re-encrypt the transmission.

[0038] In an optional embodiment of the present invention, the cloud platform decrypts the encrypted BMS upgrade firmware, specifically including the following steps: The cloud platform uses the corresponding public key to decrypt the encrypted BMS upgrade firmware and verify the digital signature.

[0039] In an optional embodiment of the present invention, when the vehicle is DC charging, it sends vehicle identification information and BMS version number to the charging pile via a charging handshake protocol, so that the charging pile can determine whether the vehicle needs to be upgraded based on the BMS version number. Specifically, this includes the following steps: (1) The vehicle sends a charging request to the charging station; (2) The charging pile and the vehicle complete the handshake interaction, and after the handshake is completed, the charging pile requests the vehicle identification information and BMS version number from the vehicle; (3) The vehicle feeds back the vehicle identification information and the BMS version number to the charging pile; (4) After the charging pile obtains the vehicle identification information and the BMS version number, the charging pile feeds back the vehicle identification information and the BMS version number to the cloud platform; (5) The cloud platform confirms whether the vehicle needs to be upgraded according to the vehicle identification information and the BMS version number: If the judgment result is that no upgrade is needed, the charging pile is fed back that no upgrade is needed; If the judgment result is that the upgrade is needed, the BMS upgrade firmware is transmitted to the charging pile; (6) After the charging pile receives the BMS upgrade firmware, the BMS upgrade firmware is forwarded to the vehicle by using the charging CAN bus during the direct current charging process.

[0040] Specifically, the above process is as shown in Figure 6 .

[0041] In an optional embodiment of the present application, after the BMS of the vehicle receives and verifies the BMS upgrade firmware, the upgrade is performed, and the upgrade result information is uploaded to the block chain network for notarization, and the specific steps include: (1) After the vehicle receives the BMS upgrade firmware of the charging pile, the BMS upgrade firmware is decrypted and installed according to the encryption method agreed by the vehicle factory; (2) The vehicle confirms whether the BMS upgrade firmware is correct: If the judgment result is incorrect, the charging pile is informed to retransmit the BMS upgrade firmware; If the judgment result is correct, the upgrade is completed.

[0042] Specifically, the above process is as shown in Figure 6 . The overall implementation module is as shown in Figure 7 .

[0043] In an optional embodiment of the present application, the charging CAN bus is used to multiplex and expand the PGN 5888 power storage battery reserved message field in the GB / T 27930 protocol.

[0044] In an optional embodiment of the present application, the upgrade result information includes: firmware version, firmware hash value, vehicle factory identification, charging pile identification, vehicle VIN code, upgrade time, and upgrade result state.

[0045] The application utilizes the vehicle in the direct current charging process, in the traditional charging protocol, the technology of existing identity verification, handshaking protocol is additionally programmed firmware transmission protocol, and the programmed firmware is registered by the vehicle manufacturer on the official cloud platform of the charging pile, so that the direct attack of the hacker on the vehicle enterprise is effectively prevented, and the charging pile obtains the firmware data from the cloud platform, and transmits the firmware data to the corresponding vehicle during direct current charging of the corresponding vehicle, so that the purpose of data security update is achieved.

[0046] The application initiates the upgrading scene in charging: breakthrough solution of DC charging and OTA security conflict, and improvement of user experience; Multi-party governance of block chain: establishment of a trusted upgrading ecology of the whole battery industry chain; Precise decision window: embedding the upgrading into the flat area of the charging curve, and realizing the real "non-sense".

[0047] Real information security is realized, and the scheme has covered the requirements of vehicle function safety ISO 26262 ASIL-D and the information safety ISO / SAE 21434 standard.

[0048] The application has the following key points: Upgrade preparation stage (cloud platform and vehicle factory): Vehicle factory role: after the vehicle factory generates the BMS upgrading firmware, the BMS upgrading firmware is not directly pushed to the vehicle, but is interacted with the cloud platform of the charging pile. The vehicle factory uses the private key corresponding to the public key provided by the cloud platform to encrypt and digitally sign the BMS upgrading firmware, and then uploads the BMS upgrading firmware to the specified path of the cloud platform.

[0049] Cloud platform role: the cloud platform verifies the digital signature of the vehicle factory, and confirms the authenticity and integrity of the BMS upgrading firmware. After verification, the BMS upgrading firmware is distributed to each charging pile node by using the block chain technology, so that the firmware version held by all charging piles is consistent, tamper-proof, and a traceable evidence is formed.

[0050] Upgrade triggering and execution stage (charging pile and vehicle): Triggering condition: when the vehicle is directly charged, the vehicle identification information and the BMS version number are additionally transmitted in the standard charging handshaking protocol (such as GB / T 27930). The charging pile judges whether the vehicle needs to be upgraded according to the BMS version number.

[0051] Execution process: if the vehicle needs to be upgraded, the charging pile transmits the BMS upgrading firmware stored in the local and encrypted to the BMS of the vehicle through the charging CAN bus (not the internal network of the vehicle) by using the interval time of the charging message interaction.

[0052] No-sense upgrade: The entire upgrade process is completed during DC charging, making full use of the characteristics of BMS being powered on and having low load during charging. There is no additional operation and time cost for users, and it realizes true "no sense".

[0053] Security and traceability mechanism: Secure communication: Encryption and digital signature technology are used throughout the process to effectively prevent firmware from being stolen or tampered with during transmission.

[0054] Network isolation: Upgrade data is transmitted through the charging CAN, which is physically isolated from the vehicle's internal network (such as the gateway and entertainment system), cutting off the path for hackers to attack critical vehicle controllers from the Internet.

[0055] Blockchain storage: Key steps such as verification, start, and completion of the upgrade operation are recorded on the blockchain, forming an unalterable log. In the future, if there is a fault caused by the upgrade, the responsible party can be clearly traced (is it a problem with the vehicle's firmware or the charging pile transmission?).

[0056] The present application has the following invention points: Invention point one: "no sense" upgrade method based on DC charging scenario Technical problem solved: Traditional OTA upgrade affects vehicle use, increases load and power consumption, and 4S store upgrade efficiency is low.

[0057] Technical means: Use DC charging as a fixed upgrade time window, transmit firmware data in the interval of charging communication messages, and use the BMS charging power-on condition to achieve user-unaware upgrade.

[0058] Technical effect: Improves user experience, avoids the impact of upgrade on vehicle normal use, and solves the risk of battery depletion leading to upgrade failure.

[0059] Invention point two: secure transmission protocol based on charging CAN network isolation Technical problem solved: Traditional OTA uses the vehicle gateway, the network path is long, and is vulnerable to network attacks.

[0060] Technical means: Reuse and expand existing DC charging communication protocols (such as PGN5888 reserved messages in GB / T 27930), and build a point-to-point (charging pile to BMS) firmware transmission channel that is isolated from the vehicle's internal network.

[0061] Technical effect: Establishes physical-level security isolation, greatly improves the information security level of the upgrade process, and effectively defends against malicious firmware injection attacks.

[0062] Invention point three: multi-party collaborative verification and storage mechanism based on blockchain The technical problems solved are: the upgrading process is black-boxed, all parties do not trust each other, and it is difficult to trace and determine responsibility when problems occur.

[0063] The technical means are: introducing blockchain technology to connect the vehicle factory, cloud platform and charging pile operator into a trusted network. The key actions of firmware distribution, upgrade triggering and upgrade result are stored on the chain.

[0064] The technical effects are: the transparency and traceability of the upgrading process are realized, a multi-party trust system is established, and an unalterable technical basis is provided for subsequent tracing and responsibility definition.

[0065] Point four of the application is a firmware security distribution system based on asymmetric encryption and digital signature The technical problems solved are: the firmware may be tampered with or forged during transmission.

[0066] The technical means are: the vehicle factory uses a private key to encrypt and sign the firmware, and the cloud platform uses a public key to verify and decrypt. The charging pile obtains reliable firmware that has passed verification.

[0067] The technical effects are: the integrity, authenticity and confidentiality of the upgraded firmware are ensured, and malicious code injection is eliminated from the source.

[0068] Embodiment two The embodiment of the application also provides a BMS direct current charging non-inductive upgrading device, which is mainly used to execute the BMS direct current charging non-inductive upgrading method provided in embodiment one of the application. The BMS direct current charging non-inductive upgrading device provided in the embodiment of the application is specifically introduced as follows.

[0069] Figure 8 is a schematic diagram of a BMS direct current charging non-inductive upgrading device according to the embodiment of the application, as shown in Figure 8 The device mainly includes: an encrypted uploading unit 10, a decryption distribution unit 20, a sending unit 30, a transmission unit 40 and an upgrading unit 50, wherein: The encrypted uploading unit is used to generate BMS upgrading firmware by the vehicle factory, encrypt and digitally sign the BMS upgrading firmware using an asymmetric encryption private key, and upload the BMS upgrading firmware to the cloud platform of the charging pile; The decryption distribution unit is used to decrypt the encrypted BMS upgrading firmware by the cloud platform, verify the digital signature, and distribute the BMS upgrading firmware to each charging pile through a blockchain network after passing the verification; The sending unit is used to send vehicle identification information and a BMS version number to the charging pile through a charging handshake protocol when the vehicle is directly charged, so that the charging pile determines whether the vehicle needs to perform upgrading according to the BMS version number; a transmission unit configured to transmit the BMS upgrade firmware to the BMS of the vehicle via the charging CAN bus within a communication interval of the charging message if the upgrade needs to be performed during the DC charging process; an upgrade unit configured to perform the upgrade after the BMS of the vehicle receives and verifies the BMS upgrade firmware, and upload upgrade result information to the blockchain network for notarization.

[0070] The BMS DC charging non-inductive upgrade device provided by the application comprises the following steps: a vehicle factory generates BMS upgrade firmware, encrypts and digitally signs the BMS upgrade firmware using an asymmetric encryption private key, and uploads the BMS upgrade firmware to a cloud platform of a charging pile; the cloud platform decrypts the encrypted BMS upgrade firmware, verifies the digital signature, and distributes the BMS upgrade firmware to each charging pile via a blockchain network after verification; the vehicle sends vehicle identification information and a BMS version number to the charging pile via a charging handshake protocol during DC charging, so that the charging pile determines whether the vehicle needs to perform an upgrade according to the BMS version number; if the upgrade needs to be performed, the charging pile transmits the BMS upgrade firmware to the BMS of the vehicle via the charging CAN bus within a communication interval of the charging message during the DC charging process; the BMS of the vehicle receives and verifies the BMS upgrade firmware, performs the upgrade, and uploads upgrade result information to the blockchain network for notarization. As can be seen from the above description, in the BMS DC charging non-inductive upgrade device, online upgrade of software firmware is performed synchronously during DC charging of the vehicle, and high-stability non-inductive flashing is achieved. The scheme effectively avoids the drawbacks of the traditional method: compared with offline UDS flashing in a 4S store, it does not affect the normal use of the vehicle; compared with remote OTA flashing, it uses a stable and reliable charging connection to eliminate the risk of flashing failure or system reset caused by network problems, and the upgrade process is independent of the vehicle internal CAN network and the Internet, and does not cause additional load. At the same time, the scheme effectively prevents hacker attacks through a secure communication mechanism, and uses blockchain technology to notarize the upgrade information, realizes complete historical traceability and clear three-party responsibility definition (for example, if a fault is caused by a battery model problem, the fault can be traced back through the digital signature record of the battery factory). In addition, the scheme does not need to upgrade high-performance chips for the BMS or add advanced gateways to the vehicle, which significantly reduces the cost of the whole vehicle, and balances user experience, cost control, functional safety and information security, thereby solving the technical problem that the traditional BMS upgrade scheme is difficult to balance user experience, cost control, functional safety and information security at the same time.

[0071] Optionally, the encryption uploading unit is further configured to: send the firmware update information to the cloud platform by the vehicle factory; receive the firmware update information and make arbitration by the cloud platform to determine whether to agree to update; if the cloud platform agrees to update, feed back the public key information of the asymmetric encryption to the vehicle factory; receive the public key information and calculate the corresponding private key of the asymmetric encryption by the vehicle factory; encrypt and digitally sign the BMS upgrade firmware by the vehicle factory using the private key of the asymmetric encryption to generate the encrypted BMS upgrade firmware; and upload the encrypted BMS upgrade firmware to the designated path of the cloud platform by the vehicle factory.

[0072] Optionally, the decryption and distribution unit is further configured to: decrypt the encrypted BMS upgrade firmware using the corresponding public key by the cloud platform, and verify the digital signature.

[0073] Optionally, the sending unit is further configured to: send a charging application to the charging pile by the vehicle; complete handshake interaction with the vehicle by the charging pile, and request the vehicle to obtain the vehicle identification information and the BMS version number after the handshake is completed; feed back the vehicle identification information and the BMS version number to the charging pile by the vehicle; feed back the vehicle identification information and the BMS version number to the cloud platform by the charging pile after obtaining the vehicle identification information and the BMS version number; confirm whether the vehicle needs to be upgraded according to the vehicle identification information and the BMS version number by the cloud platform: if the judgment result is that the vehicle does not need to be upgraded, feed back to the charging pile that the vehicle does not need to be upgraded; if the judgment result is that the vehicle needs to be upgraded, transmit the BMS upgrade firmware to the charging pile; and forward the BMS upgrade firmware to the vehicle using the charging CAN bus during the direct current charging process by the charging pile after receiving the BMS upgrade firmware.

[0074] Optionally, the upgrading unit is further configured to: decrypt and install the BMS upgrade firmware according to the encryption method agreed by the vehicle factory by the vehicle after receiving the BMS upgrade firmware of the charging pile; confirm whether the BMS upgrade firmware is correct by the vehicle: if the judgment result is incorrect, inform the charging pile to retransmit the BMS upgrade firmware; if the judgment result is correct, complete the upgrade.

[0075] Optionally, the charging CAN bus is used for multiplexing and expanding the PGN 5888 power storage battery reserved message field in the GB / T 27930 protocol.

[0076] Optionally, the upgrade result information includes: a firmware version, a firmware hash value, a vehicle factory identifier, a charging pile identifier, a vehicle VIN code, an upgrade time, and an upgrade result state.

[0077] The device provided in the embodiment of the application has the same implementation principle and generated technical effects as the foregoing method embodiment, and for brevity of description, the part not mentioned in the device embodiment can be referred to the corresponding content in the foregoing method embodiment.

[0078] As Figure 9As shown, the electronic device 600 provided by the embodiment of the present application comprises a processor 601, a memory 602 and a bus. The memory 602 stores machine readable instructions executable by the processor 601. When the electronic device is running, the processor 601 and the memory 602 communicate through the bus. The processor 601 executes the machine readable instructions to perform the steps of the BMS DC charging non-inductive upgrading method as described above.

[0079] Specifically, the memory 602 and the processor 601 can be general memory and processor, which are not specifically limited here. When the processor 601 runs the computer program stored in the memory 602, the BMS DC charging non-inductive upgrading method as described above can be executed.

[0080] The processor 601 can be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above method can be completed by the integrated logic circuit of hardware in the processor 601 or the instruction in the form of software. The processor 601 described above can be a general processor, including a central processing unit (CPU), a network processor (NP) and the like; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component. It can implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application. The general processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module can be located in a random access memory, a flash memory, a read only memory, a programmable read only memory or an electrically erasable programmable memory, a register or other mature storage medium in the art. The storage medium is located in the memory 602, and the processor 601 reads the information in the memory 602 and combines the hardware to complete the steps of the above method.

[0081] Corresponding to the above-mentioned BMS DC charging non-inductive upgrading method, the embodiment of the present application further provides a computer readable storage medium, the computer readable storage medium stores computer executable instructions, when the computer executable instructions are called and run by a processor, the computer executable instructions cause the processor to run the steps of the above-mentioned BMS DC charging non-inductive upgrading method.

[0082] The BMS DC charging non-inductive upgrading device provided by the embodiment of the present application can be specific hardware on the equipment or software or firmware installed on the equipment, etc. The device provided by the embodiment of the present application has the same implementation principle and technical effects as the foregoing method embodiments, and for brief description, the part not mentioned in the device embodiment can be referred to the corresponding content in the foregoing method embodiments. Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above can be referred to the corresponding process in the foregoing method embodiments, which will not be repeated here.

[0083] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division, and there can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some communication interfaces, devices or units, and can be electrical, mechanical or other forms.

[0084] For another example, the flowcharts and block diagrams in the drawings show the possible implementation architecture, function and operation of the devices, methods and computer program products according to the embodiments of the present application. In this regard, each block in the flowchart or block diagram can represent a module, a program segment or a part of code, which contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in different order from that shown in the drawings. For example, two consecutive blocks can actually be executed substantially in parallel, and sometimes they can be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and the combination of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system for executing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0085] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e. may be located in one place, or may be distributed on multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0086] In addition, the functional units in the embodiments provided in the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit.

[0087] The functions, if realized in the form of software functional units and sold or used as independent products, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or the parts of the prior art that make contributions or parts of the technical solutions can be embodied in the form of software products. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing an electronic device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the BMS direct current charging non-inductive upgrading method described in the embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0088] It should be noted that: similar reference numbers and letters represent similar items in the following drawings, therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings, in addition, the terms "first", "second", "third" and the like are only used to distinguish description, and cannot be understood as indicating or implying relative importance.

[0089] Finally, it should be noted that: the above-described embodiments are only specific embodiments of the present application, used to illustrate the technical solutions of the present application, and not to limit the same, the protection scope of the present application is not limited thereto, although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any skilled person familiar with the technical field can modify or easily think of changes to the technical solutions recorded in the foregoing embodiments within the technical range disclosed by the present application, or make equivalent replacement to part of the technical features; and these modifications, changes or replacements do not make the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application. All should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for seamless DC charging upgrade of a BMS, characterized in that, include: The car manufacturer generates the BMS upgrade firmware, encrypts and digitally signs it using an asymmetric encryption private key, and then uploads it to the charging pile's cloud platform. The cloud platform decrypts the encrypted BMS upgrade firmware and verifies the digital signature. After verification, it distributes the BMS upgrade firmware to each of the charging piles using a blockchain network. When the vehicle is DC charging, it sends vehicle identification information and BMS version number to the charging pile through the charging handshake protocol, so that the charging pile can determine whether the vehicle needs to be upgraded based on the BMS version number; If an upgrade is required, the charging pile will use the charging CAN bus during the DC charging process to transmit the BMS upgrade firmware to the vehicle's BMS within the communication interval of the charging message. After receiving and verifying the BMS upgrade firmware, the vehicle's BMS performs the upgrade and uploads the upgrade result information to the blockchain network for storage.

2. The method according to claim 1, characterized in that, The vehicle manufacturer generates the BMS upgrade firmware, encrypts and digitally signs it using an asymmetric encryption private key, and then uploads it to the charging pile's cloud platform, including: The car manufacturer sends firmware update information to the cloud platform; The cloud platform receives the firmware update information and arbitrates it to determine whether to agree to the update. If the cloud platform arbitration agrees to the update, it will send the asymmetric encrypted public key information back to the car manufacturer; The car manufacturer receives the public key information and calculates the corresponding asymmetric encryption private key; The vehicle manufacturer uses the asymmetric encryption private key to encrypt and digitally sign the BMS upgrade firmware, generating the encrypted BMS upgrade firmware. The vehicle manufacturer uploads the encrypted BMS upgrade firmware to a designated path on the cloud platform.

3. The method according to claim 1, characterized in that, The cloud platform decrypts the encrypted BMS upgrade firmware, including: The cloud platform uses the corresponding public key to decrypt the encrypted BMS upgrade firmware and verify the digital signature.

4. The method according to claim 1, characterized in that, When a vehicle is DC charging, it sends its vehicle identification information and BMS version number to the charging station via a charging handshake protocol. This allows the charging station to determine whether the vehicle needs an upgrade based on the BMS version number, including: The vehicle sends a charging request to the charging station; The charging pile completes a handshake interaction with the vehicle, and after the handshake is completed, requests the vehicle identification information and the BMS version number from the vehicle; The vehicle sends the vehicle identification information and the BMS version number back to the charging pile; After obtaining the vehicle identification information and the BMS version number, the charging pile feeds the vehicle identification information and the BMS version number back to the cloud platform. The cloud platform determines whether the vehicle needs an upgrade based on the vehicle identification information and the BMS version number: If the determination result is that no upgrade is needed, then feedback is sent to the charging pile that no upgrade is needed; If the determination result indicates that an upgrade is required, the BMS upgrade firmware will be transmitted to the charging pile. After receiving the BMS upgrade firmware, the charging pile forwards the BMS upgrade firmware to the vehicle via the charging CAN bus during DC charging.

5. The method according to claim 1, characterized in that, After receiving and verifying the BMS upgrade firmware, the vehicle's BMS performs the upgrade and uploads the upgrade result information to the blockchain network for evidence storage, including: After receiving the BMS upgrade firmware from the charging pile, the vehicle decrypts and installs the BMS upgrade firmware according to the encryption method agreed upon by the vehicle manufacturer. The vehicle confirms whether the BMS firmware upgrade is correct: If the judgment result is incorrect, the charging pile is notified to retransmit the BMS upgrade firmware; If the judgment result is correct, the upgrade is completed.

6. The method according to claim 1, characterized in that, This is achieved by using the charging CAN bus to multiplex and extend the reserved message field of the PGN5888 power battery in the GB / T27930 protocol.

7. The method according to claim 1, characterized in that, The upgrade result information includes: firmware version, firmware hash value, vehicle manufacturer identifier, charging pile identifier, vehicle VIN code, upgrade time, and upgrade result status.

8. A BMS DC charging sensorless upgrade device, characterized in that, include: The encrypted upload unit is used by the vehicle manufacturer to generate BMS upgrade firmware, encrypt it with an asymmetric encryption private key and digitally sign it, and then upload it to the cloud platform of the charging pile. The decryption and distribution unit is used by the cloud platform to decrypt the encrypted BMS upgrade firmware and verify the digital signature. After verification, the BMS upgrade firmware is distributed to each of the charging piles using the blockchain network. The sending unit is used to send vehicle identification information and BMS version number to the charging pile through the charging handshake protocol when the vehicle is DC charging, so that the charging pile can determine whether the vehicle needs to be upgraded based on the BMS version number. The transmission unit is used to transmit the BMS upgrade firmware to the vehicle's BMS during the DC charging process using the charging CAN bus, within the communication interval of the charging message, if an upgrade is required. The upgrade unit is used by the vehicle's BMS to receive and verify the BMS upgrade firmware, perform the upgrade, and upload the upgrade result information to the blockchain network for storage.

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program thereon, characterized in that, The computer program is executed by the processor to perform the method of any one of claims 1 to 7.

Images