WO2023102733A1 - 电池管理系统及其更新方法、主节点、从节点和存储介质 - Google Patents

电池管理系统及其更新方法、主节点、从节点和存储介质 Download PDF

Info

Publication number
WO2023102733A1
WO2023102733A1 PCT/CN2021/136100 CN2021136100W WO2023102733A1 WO 2023102733 A1 WO2023102733 A1 WO 2023102733A1 CN 2021136100 W CN2021136100 W CN 2021136100W WO 2023102733 A1 WO2023102733 A1 WO 2023102733A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
slave node
slave
master node
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/136100
Other languages
English (en)
French (fr)
Inventor
程康
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Contemporary Amperex Technology Co Ltd
Original Assignee
Contemporary Amperex Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Contemporary Amperex Technology Co Ltd filed Critical Contemporary Amperex Technology Co Ltd
Priority to PCT/CN2021/136100 priority Critical patent/WO2023102733A1/zh
Priority to CN202180094444.4A priority patent/CN116941093A/zh
Publication of WO2023102733A1 publication Critical patent/WO2023102733A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • H—ELECTRICITY
    • H01—ELECTRIC ELEMENTS
    • H01M—PROCESSES OR MEANS, e.g. BATTERIES, FOR THE DIRECT CONVERSION OF CHEMICAL ENERGY INTO ELECTRICAL ENERGY
    • H01M10/00—Secondary cells; Manufacture thereof
    • H01M10/42—Methods or arrangements for servicing or maintenance of secondary cells or secondary half-cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements

Definitions

  • the present application relates to the field of battery management systems, in particular to a battery management system and its update method, a master node, a slave node and a storage medium.
  • the OTA Over-the-Air Technology, over-the-air technology
  • the wireless BMS Battery Management System, battery management system
  • CAN Controller Area Network, The controller area network
  • the TBOX receives the data from the cloud and transfers it to the master node through CAN, and the master node then transfers it to the slave node through the internal CAN, and writes the protocol.
  • UDS Unified Diagnostic Services, Unified Diagnostic Services
  • the present disclosure provides a battery management system and its updating method, a master node, a slave node and a storage medium.
  • the present disclosure provides a method for updating a battery management system, including: the master node obtains system update data from the remote receiving box of the vehicle communication system; the master node sends the system update data to the At least one slave node, wherein the system update data is used to update the system software of the slave node, the master node is the master controller of the battery management system, and the slave node is the control of a battery pack of the battery management system device.
  • an OTA upgrade method based on wireless BMS power exchange technology is designed, and the data transmission between the master and slave nodes is changed from the original CAN (Controller Area Network, controller local area network) communication to wireless communication . Therefore, the reliability of communication is improved, the service life of the system is improved, and the technical problem of short service life of the system in the related technical solutions is solved.
  • CAN Controller Area Network, controller local area network
  • the master node sending the system update data to at least one slave node through wireless transmission includes: after the master node sends a frame of data to the slave node through wireless transmission, if If the master node does not receive the feedback from the slave node within the confirmation time, data retransmission is performed.
  • the master node sending the system update data to at least one slave node through wireless transmission includes: the master node sending the system update data to the slave nodes through broadcast transmission.
  • the master node sending the system update data to at least one slave node through wireless transmission includes: the master node sending the system update data to the slave nodes through unicast transmission.
  • sending the system update data to at least one slave node by the master node through wireless transmission includes: adopting time-division multiplexing to multiple slave nodes The node transmits data packets in different time periods.
  • using time-division multiplexing to transmit time-division data packets to multiple slave nodes includes: allocating data packet lengths and broadcast time intervals according to the number of currently connected slave nodes.
  • sending the system update data to at least one slave node by the master node through wireless transmission further includes: using a breakpoint on the transmitted data packet resume.
  • the adopting the resume transmission of the transmitted data packets includes: if any slave node does not respond after timeout, the master node judges that the slave node is a faulty slave node, and removes the faulty slave node, Refresh the broadcast transmission time interval, and record the faulty slave node and the breakpoint location; after other slave nodes except the faulty slave node have received the packet data, the master node will resend the data to the faulty slave node.
  • the present disclosure provides a method for updating a battery management system, including: the slave node receives system update data sent by the master node through wireless transmission, wherein the master node is the master controller of the battery management system, and the slave node The node is the controller of a battery pack of the battery management system, and the system update data is obtained by the master node from the remote receiving box of the vehicle communication system; the slave node updates the system software of the slave node according to the system update data.
  • the update of the slave node system software by the slave node according to the system update data includes: backing up the original system software program; updating the slave node system software according to the system update data; In case of failure, automatic recovery restores to the original system software program.
  • the present disclosure provides a master node, including: an update data receiving module, configured to obtain system update data from a remote receiving box of a vehicle communication system; an update data sending module, configured to transfer the system update data to the The update data is sent to at least one slave node, wherein the system update data is used to update the system software of the slave node, the master node is the master controller of the battery management system, and the slave node is a battery management system Controller for the battery pack.
  • the master node is configured to perform operations for implementing the updating method described in any of the foregoing embodiments.
  • the present disclosure provides a slave node, including: a data receiving unit, configured to receive system update data sent by the master node through wireless transmission, wherein the master node is the master controller of the battery management system, and the The slave node is a controller of a battery pack of the battery management system, and the system update data is obtained by the master node from the remote receiving box of the vehicle communication system; a software update unit is used to update the slave node system according to the system update data Software updates.
  • the slave node is configured to perform operations for implementing the update method described in any of the foregoing embodiments.
  • the present disclosure provides a computer device, including: a memory for storing instructions; a processor for executing the instructions, so that the computer device implements the update method described in any of the above embodiments operation.
  • the present disclosure provides a battery management system, including the master node according to any one of the above embodiments and the slave node according to any one of the above embodiments.
  • the present disclosure provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, any of the above implementations can be realized.
  • the update method described in the example is not limited to:
  • Fig. 1 is a schematic structural diagram of a wireless BMS system with a master-slave architecture in an embodiment of the related technology.
  • Fig. 2 is a schematic structural diagram of a wireless battery management system provided by some embodiments of the present disclosure.
  • FIG. 3 is a schematic diagram of some embodiments of an updating method for a battery management system of the present disclosure.
  • Fig. 4 is a schematic diagram of a method for updating a wireless-based transport layer protocol in some embodiments of the present disclosure.
  • FIG. 5 is a schematic diagram of another embodiment of an update method for a battery management system of the present disclosure.
  • FIG. 6 is a schematic diagram of some other embodiments of the update method of the battery management system of the present disclosure.
  • FIG. 7 is a schematic diagram of system program update in some embodiments of the present disclosure.
  • FIG. 8 is a schematic diagram of system program updating in some other embodiments of the present disclosure.
  • FIG. 9 is a schematic diagram of some embodiments of a master node of the present disclosure.
  • FIG. 10 is a schematic diagram of some embodiments of a slave node of the present disclosure.
  • FIG. 11 is a schematic structural diagram of some embodiments of a computer device of the present disclosure.
  • the relevant technical solutions mainly rely on the master node to communicate with the vehicle TBOX (Telematics Box, the remote receiving box of the vehicle communication system) based on CAN. Transfer to the slave node through the internal CAN, and the flashing protocol is based on UDS (Unified Diagnostic Services, unified diagnostic service) ON CAN, where the master node is the master controller of the battery management system, and the slave node is a battery pack of the battery management system controller.
  • UDS Unified Diagnostic Services, unified diagnostic service
  • the related art OTA upgrade system includes a receiving module, a state determination module and an update module, and the receiving module is responsible for receiving the software update package sent by the OEM (Original Equipment Manufacturer, original equipment manufacturer) platform and storing it in the flash (Non-Volatile , flash memory, non-volatile memory); the state determination module is used to diagnose whether the car is in a state where the software can be updated; the update module is responsible for burning and recording the update package in the flash into the BMU (Battery Management Unit, battery management unit) through CAN communication unit).
  • the receiving module is responsible for receiving the software update package sent by the OEM (Original Equipment Manufacturer, original equipment manufacturer) platform and storing it in the flash (Non-Volatile , flash memory, non-volatile memory); the state determination module is used to diagnose whether the car is in a state where the software can be updated; the update module is responsible for burning and recording the update package in the flash into the BMU (Battery Management Unit, battery management unit) through CAN communication unit).
  • the inventor also noticed that due to the application of battery replacement technology, the connectors connected to the battery system of the related technology and the vehicle have frequent plugging and unplugging operations, which have the problems of short life of the connectors and low communication reliability. Therefore, the OTA of the related technology The technology cannot meet the upgrade of the battery quick-change software system and cannot be directly transplanted.
  • the inventor also noticed that in related technologies, the lifespan of low-voltage connectors is a huge challenge in the battery replacement scenario. Therefore, considering the master-slave architecture of the wireless BMS system, the communication mode between the master-slave nodes is Bluetooth or other 2.4-based G's short-distance communication protocol, there is no ready-made reliable transmission protocol under this architecture.
  • the present disclosure designs an OTA upgrade method based on wireless BMS power exchange technology, which changes the data transmission between the master and slave nodes from the original CAN controller local area network communication to wireless communication. Therefore, the reliability of communication is improved, the service life of the system is improved, and the technical problem of short service life of the system in the related technical solutions is solved.
  • FIG. 2 is a schematic structural diagram of a wireless battery management system provided by some embodiments of the present disclosure.
  • the wireless battery management system of the present disclosure may include a master node 100 and multiple slave nodes 200, wherein:
  • a master node wireless module 110 and a master node Flash 120 are arranged at the master node 100, wherein: the master node is the master controller of the battery management system, and the master node 100 has CAN /FD (CAN with Flexible Data-Rate, flexible data rate CAN) communication, communicates with the vehicle-mounted TBOX 130; the master node 100 communicates with the on-board integrated SPI (Serial Peripheral Interface, serial peripheral interface) or off-board integrated CAN/ The FD communicates with the master node wireless module 110 .
  • CAN /FD CAN with Flexible Data-Rate, flexible data rate CAN
  • a slave node 200 is provided with a slave node wireless module 210 and a slave node Flash 220.
  • the slave node 200 is a controller of a battery pack of the battery management system.
  • the communication between the master node 100 and the slave node 200 may be based on a wireless short-distance communication protocol in the 2.4GHz frequency band.
  • the master node 100 and the slave node 200 themselves integrate the CAN-to-wireless transmission function, and can choose to integrate an external Flash chip, which can be quickly deployed in the current system.
  • the master node 100 can be used to obtain system update data from the remote receiving box of the vehicle communication system; the master node sends the system update data to at least one slave node through wireless transmission, wherein the The system update data is used to update the system software of the slave node, the master node is the master controller of the battery management system, and the slave node is the controller of a battery pack of the battery management system.
  • an OTA upgrade method based on wireless BMS power exchange technology is designed to change the data transmission between the master and slave nodes from the original CAN communication to wireless communication. Therefore, the reliability of communication is improved, the service life of the system is improved, and the technical problem of short service life of the system in the related technical solutions is solved.
  • the embodiment of the present disclosure changes the CAN communication interaction between the master and slave nodes in the related technical solution to wireless communication based on the 2.4G frequency band, and the communication protocol can choose protocols such as Bluetooth.
  • the embodiment of the present disclosure adds a wireless module, which provides CAN communication and wireless communication functions, and can be deployed in the current system very conveniently.
  • FIG. 3 is a schematic diagram of some embodiments of an update method for a battery management system of the present disclosure.
  • this embodiment can be executed by the battery management system of the present disclosure or the master node of the present disclosure.
  • the updating method of the battery management system of the present disclosure may include at least one of steps 31 to 32, wherein:
  • Step 31 the master node obtains system update data from the remote receiving box of the vehicle communication system.
  • step 31 may include: the master node obtains system update data from a remote receiving box of the vehicle communication system through a controller area network communication manner.
  • Step 32 the master node sends the system update data to at least one slave node through wireless transmission, wherein the system update data is used to update the system software of the slave node, and the master node is the battery management system the master controller of the battery management system, and the slave node is the controller of a battery pack of the battery management system.
  • the update method of the wireless-based transport layer protocol of the present disclosure may include: after the master node sends SF (Single frame, one frame of data) to the slave node through wireless transmission, if within the predetermined confirmation time (T_CONF), if the master node does not receive the feedback (Retry) from the slave node, it will retransmit the data; if the master node receives the feedback from the slave node within the predetermined confirmation time, the master node will The node sends FF (First Frame, first frame) data, and performs CF (Continue Frame, continuous frame) data transmission after receiving a response FC (Flow Control, flow control) message.
  • SF Single frame, one frame of data
  • FC Flow Control, flow control
  • the foregoing embodiments of the present disclosure may add a retransmission mechanism on the basis of the CANTP protocol (CAN transmission protocol) and based on the existing characteristics of wireless transmission.
  • CANTP protocol CAN transmission protocol
  • the present disclosure can turn off this function through a software protocol.
  • the above-mentioned embodiments of the present disclosure are based on the current communication mode, considering the characteristics of wireless transmission, and designing and implementing a wireless-based TP (Transport Layer) protocol on the basis of the CANTP protocol, so as to control wireless data transmission and maximize bandwidth utilization. Improve communication reliability.
  • TP Transport Layer
  • step 32 of the embodiment in FIG. 3 may include: the master node sends system update data to the slave node in a broadcast transmission manner.
  • step 32 of the embodiment in FIG. 3 may include: the master node sends system update data to the slave node in a unicast transmission manner.
  • the MAC (Media Access Control Address, Media Access Control Address) of the slave node can be used to distinguish which node needs to be updated currently.
  • the configuration MAC when the configuration MAC is 0xFF, it is a broadcast update; otherwise, it is a point-to-point update.
  • the master node when the master node adopts broadcast transmission, the master node sends the system update data to at least one slave node through wireless transmission.
  • the heating step may include: adopting time-division multiplexing, Multiple slave nodes perform time-segmented data packet transmission.
  • the step of using time-division multiplexing to transmit time-division data packets to multiple slave nodes may include: allocating data packet lengths and broadcast time intervals according to the number of currently connected slave nodes.
  • the master node when multiple nodes are updated, adopts broadcast transmission, which depends on all connection handles of the current system, and the OTA program will allocate the data packet length and broadcast time interval according to the number of slave nodes currently connected .
  • the master node broadcasts In the time interval, sending the data of the predetermined data packet length includes to the first slave node, and in the second broadcast time interval, sending the data of the predetermined data packet length includes to the second slave node, and in the third broadcast time interval, Sending data with a predetermined packet length includes to the third slave node.
  • time-division multiplexing and breakpoint resume function can be added, and the position of the breakpoint is configurable, and the unit is Sector (sector) size of Flash.
  • the step of the master node sending the system update data to at least one slave node through wireless transmission may also include: using the data packet transmitted to Resume upload from breakpoint.
  • the step of resuming the transmitted data packets may include: if any slave node fails to respond after timeout, the master node judges that the slave node is a fault slave node, and eliminates the fault From the node, refresh the broadcast transmission time interval, and record the faulty slave node and the breakpoint position; after the other slave nodes except the faulty slave node have received the packet data, the master node will resend the data to the faulty node slave node.
  • FIG. 5 is a schematic diagram of another embodiment of an updating method for a battery management system of the present disclosure.
  • this embodiment can be executed by the battery management system of the present disclosure or the slave node of the present disclosure.
  • the update method of the battery management system of the present disclosure may include at least one of steps 51 to 52, wherein:
  • Step 51 the slave node receives the system update data sent by the master node through wireless transmission, wherein the master node is the master controller of the battery management system, the slave node is the controller of a battery pack of the battery management system, and the system The update data is obtained by the master node from the remote receiving box of the vehicle communication system.
  • Step 52 the slave node updates the system software of the slave node according to the system update data.
  • step 52 may include: backing up the original system software program; updating the slave node system software according to the system update data; and automatically returning to the original system software program when the system software update fails.
  • step 52 may include: after receiving the transmitted program from the node, first write it into the external Flash, and add the corresponding verification information; after the single packet data is transmitted, it will start the verification, if If the verification fails, the master node will record the current interrupt node number and interrupt address. After other slave nodes have received the packet data, the master node will resend the data to the faulty node; if the verification is successful, it will check whether the entire data packet is received completely. If you receive a complete configuration, you can configure whether you need to wait for the update command, or directly execute the software reset to update the program.
  • step 52 may include: in order to be compatible with rollback requirements, before erasing the original program, it will be stored in the backup area, if the software upgrade fails, it will automatically restore to the version before the upgrade; when a single node is updated , the master node adopts the point-to-point propagation method; when a single node is updated, if the corresponding node does not respond after a timeout, the master node will record the faulty node, otherwise the data is received normally, the process of data reception and software upgrade will repeat the original program of erasing Before, it will be stored in the backup area. If the software upgrade fails, it will automatically restore to the steps of the version before the upgrade.
  • FIG. 6 is a schematic diagram of some other embodiments of an updating method for a battery management system of the present disclosure.
  • this embodiment can be executed by the battery management system of the present disclosure.
  • the update method of the battery management system of the present disclosure may include at least one step from step 601 to step 622, wherein:
  • Step 601 the master node receives an update request from the battery management system.
  • Step 602 judging whether the update request is a broadcast update request. If the update request is a broadcast update request, perform step 603; otherwise, if the update request is not a broadcast update request, perform step 615.
  • step 603 the OTA program of the master node determines the number of currently connected slave nodes.
  • Step 604 Separate the data packet length and broadcast interval time according to the number of currently connected slave nodes.
  • Step 605 the slave node responds to the master node.
  • Step 606 judging whether the response from the slave node times out. If the response from the slave node times out, execute step 607; otherwise, if the response from the slave node does not time out, execute step 608.
  • Step 607 the master node removes the overtime slave node, and records the timeout slave node as a faulty slave node; and then ends.
  • Step 608 the slave node receives data, and after receiving a packet of data, the slave node performs verification.
  • Step 609 check whether the package data is successfully received. If the packet data is received successfully, execute step 610; otherwise, if the packet data is not successfully received, execute step 613.
  • Step 610 write the verification flag bit as "1".
  • Step 611 judging whether the data packet is completely received.
  • execute step 612 executes step 612; otherwise, when the data packet is received incompletely, execute step 608, that is, receive the next packet of data.
  • Step 612 update the system program according to the received complete data packet; then, end.
  • step 613 the master node records the currently interrupted node number and interrupt address.
  • Step 614 judging whether the update period of the current round is over.
  • step 608 is executed, that is, the next packet of data is received.
  • Step 615 update in a single-node update manner.
  • Step 616 the slave node responds to the master node.
  • Step 617 judging whether the response from the slave node times out. If the response from the slave node times out, execute step 618; otherwise, if the response from the slave node does not time out, execute step 619.
  • Step 618 the master node records the time-out slave node as a failed slave node; and then ends.
  • step 619 the slave node receives data, and after receiving a packet of data, the slave node performs verification.
  • Step 620 check whether the package data is received successfully. If the packet data is received successfully, execute step 621; otherwise, if the packet data is not successfully received, execute step 619, that is, receive the next packet data.
  • Step 621 write the verification flag bit as "1".
  • Step 622 judging whether the data packet is received completely.
  • execute step 612 executes the data packet is received completely.
  • execute step 619 executes the next packet of data.
  • FIG. 7 is a schematic diagram of system program update in some embodiments of the present disclosure.
  • this embodiment can be executed by the battery management system of the present disclosure or the slave node of the present disclosure.
  • the updating method of the battery management system of the present disclosure may include at least one step from step 71 to step 73, wherein:
  • Step 71 the slave node judges whether to update immediately. In the case of immediate update, perform step 73; otherwise, in the case of no immediate update, perform step 72.
  • step 72 the slave node judges whether an update instruction is received; if an update instruction is received, step 73 is executed.
  • Step 73 update the system program according to the system update data.
  • FIG. 8 is a schematic diagram of system program update in other embodiments of the present disclosure.
  • this embodiment can be executed by the battery management system of the present disclosure or the slave node of the present disclosure.
  • the update method of the battery management system of the present disclosure (such as step 73 in the embodiment of FIG. 7 ) may include at least one step from step 731 to step 739, wherein:
  • step 731 the slave node executes reset and enters the Bootloader.
  • the BootLoader runs before the operation of the operating system kernel, and can initialize hardware devices, establish a memory space map, and can bootload programs and start loading.
  • Step 732 judging whether the detection check digit of the Bootloader is "1". If the detection check digit of the Bootloader is "1”, execute step 733; otherwise, if the detection check digit of the Bootloader is not "1", end.
  • Step 733 the slave node imports the original program into the Flash for backup.
  • Step 734 judging whether the backup of the original program is completed.
  • execute step 735 executes when the original program backup is completed.
  • Step 735 add 1 to the diagnosis counter.
  • Step 736 judging whether the count value of the diagnostic counter is greater than a predetermined value. If the count value of the diagnosis counter is greater than the predetermined value, end; otherwise, if the count value of the diagnosis counter is not greater than the predetermined value, after a predetermined time interval, execute step 734 again.
  • the predetermined value may be three.
  • Step 737 the slave node performs program update.
  • Step 738 judging whether the program update is successful. If the program update is successful, end; otherwise, if the program update is unsuccessful, step 739 is executed.
  • Step 739 roll back according to the original backup program in the Flash, and restore the BMU to the state when it was not updated.
  • the above-mentioned embodiments of the present disclosure design a transport layer protocol capable of wireless communication, which can support source data packetization, grouping, and timeout judgment. Important parameters can match the CAN-based transport layer protocol of the vehicle-end related technology, and the adaptability is wide.
  • the foregoing embodiments of the present disclosure design a software update protocol for a master-slave wireless BMS, which supports backup, rollback, and resume functions.
  • the above-mentioned embodiments of the present disclosure solve the problems of low compatibility between the related technology and the wireless BMS system of the master-slave architecture, and low reliability of software upgrades, and the OTA upgrade method provided by the above-mentioned embodiments of the present disclosure has strong scalability and high reuse rate.
  • FIG. 9 is a schematic diagram of some embodiments of the master node of the present disclosure.
  • the master node of the present disclosure (such as the master node 100 in the embodiment of FIG. 2) may include an update data receiving module 101 and an update data sending module 102, wherein:
  • the update data receiving module 101 is configured to acquire system update data from the remote receiving box of the vehicle communication system.
  • the update data sending module 102 is configured to send the system update data to at least one slave node through wireless transmission, wherein the system update data is used for updating the system software of the slave node, and the master node is responsible for the battery management
  • the main controller of the system, and the slave node is the controller of a battery pack of the battery management system.
  • the update data sending module 102 can be configured to send a frame of data to the slave node through wireless transmission, if the master node does not receive feedback from the slave node within the predetermined confirmation time, Data retransmission is performed.
  • the update data sending module 102 may be configured to send the system update data to the slave nodes in a broadcast transmission manner.
  • the update data sending module 102 may be configured to send the system update data to the slave nodes in a unicast transmission manner.
  • the update data sending module 102 may be used to transmit time-division multiplexed data packets to multiple slave nodes.
  • the update data sending module 102 can be used to allocate the data packet length and broadcast time interval according to the number of slave nodes currently connected.
  • the update data sending module 102 may be configured to perform resuming of the transmitted data packets.
  • the update data sending module 102 can be used to if any slave node does not respond after timeout, the master node judges that the slave node is a faulty slave node, removes the faulty slave node, refreshes the broadcast transmission time interval, and Record the faulty slave node and the location of the breakpoint; after the other slave nodes except the faulty slave node have received the packet data, the master node will resend the data to the faulty slave node.
  • the master node is configured to execute operations for implementing the update method described in any of the foregoing embodiments (eg, the embodiment in FIG. 3 ).
  • FIG. 10 is a schematic diagram of some embodiments of a slave node in the present disclosure.
  • the slave node of the present disclosure (such as the slave node 200 in the embodiment of FIG. 2 ) may include a data receiving unit 201 and a software updating unit 202, wherein:
  • the data receiving unit 201 is configured to receive system update data sent by the master node through wireless transmission, wherein the master node is the master controller of the battery management system, and the slave node is the controller of a battery pack of the battery management system , the system update data is obtained by the master node from the remote receiving box of the vehicular communication system.
  • a software update unit 202 configured to update the slave node system software according to the system update data.
  • the software update unit 202 can be used to back up the original system software program; update the slave node system software according to the system update data; in the case of system software update failure, automatically restore to the original system software program .
  • the slave node is configured to execute operations for implementing the update method described in any one of the above embodiments (such as the embodiment in FIG. 5 , FIG. 7 or FIG. 8 ).
  • FIG. 11 is a schematic structural diagram of some embodiments of a computer device of the present disclosure. As shown in FIG. 11 , the computer device includes a memory 301 and a processor 302 .
  • the memory 301 is used to store instructions, and the processor 302 is coupled to the memory 301, and the processor 302 is configured to implement the method involved in the above-mentioned embodiments (for example, any one of Fig. 3 to Fig. 8 ) based on the instructions stored in the memory.
  • the processor 302 is configured to implement the methods involved in the above embodiments (such as the embodiment in FIG. 5 , FIG. 7 or FIG. 8 ) based on instructions stored in the memory, and the computer device can be implemented as a slave node.
  • the processor 302 is configured to execute the methods involved in the above embodiments (eg, the embodiment in FIG. 3 ) based on instructions stored in the memory, and the computer device may be implemented as a master node.
  • the computer device also includes a communication interface 303 for information exchange with other devices. Meanwhile, the computer device also includes a bus 304 , and the processor 302 , the communication interface 303 , and the memory 301 communicate with each other through the bus 304 .
  • the memory 301 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory. Memory 301 may also be a memory array.
  • the storage 301 may also be divided into blocks, and the blocks can be combined into virtual volumes according to certain rules.
  • processor 302 may be a central processing unit CPU, or may be an application specific integrated circuit ASIC, or one or more integrated circuits configured to implement embodiments of the present disclosure.
  • the present disclosure also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, any of the above-mentioned embodiments (eg The update method described in any embodiment of Fig. 3-Fig. 8).
  • the embodiments of the present disclosure may be provided as methods, apparatuses, or computer program products. Accordingly, the present disclosure can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein. .
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions
  • the device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.
  • the master and slave nodes described above can be implemented as general purpose processors, programmable logic controllers (PLCs), digital signal processors (DSPs), application specific integrated circuits (ASICs), A field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
  • PLCs programmable logic controllers
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGA field programmable gate array

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Chemical & Material Sciences (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Manufacturing & Machinery (AREA)
  • Physics & Mathematics (AREA)
  • Chemical Kinetics & Catalysis (AREA)
  • Electrochemistry (AREA)
  • General Chemical & Material Sciences (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)

Abstract

本申请实施例提供一种电池管理系统及其更新方法、主节点、从节点和存储介质。所述电池管理系统的更新方法包括：主节点从车载通信系统远端接收盒获取系统更新数据；所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点，其中，所述系统更新数据用于从节点系统软件的更新，所述主节点为所述电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器。本申请将主从节点之间的数据传输由原来的CAN通信变为无线通信。由此提高了通信可靠性，提高了系统寿命。

Description

电池管理系统及其更新方法、主节点、从节点和存储介质 技术领域
本申请涉及电池管理系统领域，特别是涉及一种电池管理系统及其更新方法、主节点、从节点和存储介质。
背景技术
相关技术的无线BMS(Battery Management System，电池管理系统)的OTA(Over-the-Air Technology，空中下载技术)，例如主从架构的无线BMS系统中，主要依靠主节点基于CAN(Controller Area Network,控制器局域网络)与整车TBOX(Telematics Box，车载通信系统远端接收盒)进行通信，TBOX接收云端的数据通过CAN转给主节点，主节点再通过内CAN转给从节点，刷写协议基于UDS(Unified Diagnostic Services，统一诊断服务)ON CAN。
相关技术中，由于电动车换电技术的应用导致从节点的电芯系统与整车连接的接插件存在频繁插拔的操作，相关技术基于CAN通信的BMS存在接插件寿命短、通信可靠性低的技术问题，因此相关技术OTA技术不能满足该电芯快换式软件系统的升级，不可直接移植。
发明内容
鉴于上述问题，本公开提供一种电池管理系统及其更新方法、主节点、从节点和存储介质。
第一方面，本公开提供了一种电池管理系统的更新方法，包括：主节点从车载通信系统远端接收盒获取系统更新数据；所述主节点通 过无线传输方式将所述系统更新数据发送给至少一个从节点，其中，所述系统更新数据用于从节点系统软件的更新，所述主节点为所述电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器。
本公开实施例的技术方案中，设计了基于无线BMS换电技术的OTA升级方法，将主从节点之间的数据传输由原来的CAN(Controller Area Network,控制器局域网络)通信变为无线通信。由此提高了通信可靠性，提高了系统寿命，解决了相关技术方案中系统寿命短的技术问题。
在一些实施例中，所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点包括：所述主节点通过无线传输方式向所述从节点发送一帧数据后，若在预定确认时间内，所述主节点未收到所述从节点的反馈，则进行数据重传。
在一些实施例中，所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点包括：所述主节点采用广播传输方式，将系统更新数据发送给所述从节点。
在另一些实施例中，所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点包括：所述主节点采用单播传输方式，将系统更新数据发送给所述从节点。
在一些实施例中，所述主节点采用广播传输方式的情况下，所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点包括：采用分时复用，对多个从节点进行分时段数据包传输。
在一些实施例中，所述采用分时复用，对多个从节点进行分时段数据包传输包括：根据当前连接的从节点数目，分配数据包长度和广播时间间隔。
在一些实施例中，所述主节点采用广播传输方式的情况下，所 述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点还包括：采用对传输的数据包进行断点续传。
在一些实施例中，所述采用对传输的数据包进行断点续传包括：若任意从节点超时未应答，则所述主节点判断该从节点为故障从节点，剔除所述故障从节点，刷新广播传输时间间隔，并记录下故障从节点以及断点位置；在除所述故障从节点外其它从节点接收完该包数据后，所述主节点将重新发送数据给所述故障从节点。
第二方面，本公开提供了电池管理系统的更新方法，包括：从节点通过无线传输方式接收主节点发送的系统更新数据，其中，所述主节点为电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器，系统更新数据为所述主节点从车载通信系统远端接收盒获取的；所述从节点根据所述系统更新数据对从节点系统软件的更新。
在一些实施例中，所述从节点根据所述系统更新数据对从节点系统软件的更新包括：将原系统软件程序进行备份；根据系统更新数据对从节点系统软件进行更新；在系统软件更新失败的情况下，自动回复恢复至原系统软件程序。
第三方面，本公开提供了一种主节点，包括：更新数据接收模块，用于从车载通信系统远端接收盒获取系统更新数据；更新数据发送模块，用于通过无线传输方式将所述系统更新数据发送给至少一个从节点，其中，所述系统更新数据用于从节点系统软件的更新，所述主节点为所述电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器。
在一些实施例中，所述主节点用于执行实现如上述任一实施例所述的更新方法的操作。
第四方面，本公开提供了一种从节点，包括：数据接收单元， 用于通过无线传输方式接收主节点发送的系统更新数据，其中，所述主节点为电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器，系统更新数据为所述主节点从车载通信系统远端接收盒获取的；软件更新单元，用于根据所述系统更新数据对从节点系统软件的更新。
在一些实施例中，所述从节点用于执行实现如上述任一实施例所述的更新方法的操作。
第五方面，本公开提供了一种计算机装置，包括：存储器，用于存储指令；处理器，用于执行所述指令，使得所述计算机装置执行实现如上述任一实施例所述的更新方法的操作。
第六方面，本公开提供了一种电池管理系统，包括如上述任一实施例的主节点和如上述任一实施例所述的从节点。
第七方面，本公开提供了一种非瞬时性计算机可读存储介质，其中，所述非瞬时性计算机可读存储介质存储有计算机指令，所述指令被处理器执行时实现如上述任一实施例所述的更新方法。
上述说明仅是本公开技术方案的概述，为了能够更清楚了解本公开的技术手段，而可依照说明书的内容予以实施，并且为了让本公开的上述和其它目的、特征和优点能够更明显易懂，以下特举本公开的具体实施方式。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据附图获得其他的附图。
图1是相关技术一实施例中主从架构的无线BMS系统的结构示意图。
图2为本公开一些实施例提供的无线电池管理系统的结构示意图。
图3为本公开电池管理系统的更新方法一些实施例的示意图。
图4为本公开一些实施例中基于无线的传输层协议的更新方法的示意图。
图5为本公开电池管理系统的更新方法另一些实施例的示意图。
图6为本公开电池管理系统的更新方法又一些实施例的示意图。
图7为本公开一些实施例系统程序更新的示意图。
图8为本公开另一些实施例系统程序更新的示意图。
图9为本公开主节点一些实施例的示意图。
图10为本公开从节点一些实施例的示意图。
图11为本公开计算机装置一些实施例的结构示意图。
具体实施方式
下面结合附图和实施例对本申请的实施方式作进一步详细描述。以下实施例的详细描述和附图用于示例性地说明本申请的原理，但不能用来限制本申请的范围，即本申请不限于所描述的实施例。
在本申请的描述中，需要说明的是，除非另有说明，“多个”的含义是两个以上；术语“上”、“下”、“左”、“右”、“内”、“外”等指示的方位或位置关系仅是为了便于描述本申请和简化描述，而不是指示或暗示所指的装置或元件必须具有特定的方位、以特定的方位构造和操作，因此不能理解为对本申请的限制。此外，术语“第一”、“第二”、“第三”等仅用于描述目的，而不能理解为指示或暗示相对重要性。“垂直”并不是严格意义上的垂直，而是在误差允许范围之内。“平行”并不是严格意义上的平行，而是在误差允许范围之内。
下述描述中出现的方位词均为图中示出的方向，并不是对本申请的具体结构进行限定。在本申请的描述中，还需要说明的是，除非另有明确的规定和限定，术语“安装”、“相连”、“连接”应做广义理解，例如，可以是固定连接，也可以是可拆卸连接，或一体地连接；可以是直接相连，也可以通过中间媒介间接相连。对于本领域的普通技术人员而言，可视具体情况理解上述术语在本申请中的具体含义。
如图1所示，相关技术方案中主要依靠主节点基于CAN与整车TBOX(Telematics Box，车载通信系统远端接收盒)进行通信，TBOX接收云端的数据通过CAN转给主节点，主节点再通过内CAN转给从节点，刷写协议基于UDS(Unified Diagnostic Services，统一诊断服务)ON CAN，其中，主节点为所述电池管理系统的主控制器，从节点为电池管理系统的一个电池组的控制器。
发明人注意到：相关技术OTA升级系统包含接收模块，状态确定模块和更新模块，接收模块负责接收OEM(Original Equipment Manufacturer，原厂设备制造商)平台发送的软件更新包存储在flash(Non-Volatile，闪存，非易失性内存)中；状态确定模块用来诊断汽车是否处于软件可更新的状态；更新模块负责通过CAN通信，将flash中的更新包烧录进BMU(Battery Management Unit，电池管理单元)中。
发明人还注意到：由于换电技术的应用导致相关技术电芯系统与整车连接的接插件存在频繁插拔的操作，存在接插件寿命短，通信可靠性低的问题，因此相关技术的OTA技术不能满足该电芯快换式软件系统的升级，不可直接移植。
发明人还注意到：相关技术中，低压接插件的寿命在换电场景下是一个巨大挑战，故考虑主从架构的无线BMS系统，主从节点之间的通信方式为蓝牙或者基于其他的2.4G的短距离通信协议，此种架构下无现成的可靠的传输协议。
根据上述问题，本公开设计了基于无线BMS换电技术的OTA升级方法，将主从节点之间的数据传输由原来的CAN控制器局域网络通信变为无线通信。由此提高了通信可靠性，提高了系统寿命，解决了相关技术方案中系统寿命短的技术问题。
以下实施例为了方便说明，以本公开一些实施例的一种主从架构的无线电池管理系统为例进行说明。
请参照图2，图2为本公开一些实施例提供的无线电池管理系统的结构示意图。如图2所示，本公开无线电池管理系统可以包括主节点100和多个从节点200，其中：
在一些实施例中，如图2所示，在主节点100处设置有主节点无线模块110和主节点Flash 120，其中：主节点为所述电池管理系统的主控制器，主节点100具备CAN/FD(CAN with Flexible Data-Rate，灵活数据速率CAN)通信，与车载TBOX 130通信；主节点100通过板内集成的SPI(Serial Peripheral Interface，串行外设接口)或者板外集成的CAN/FD与主节点无线模块110通信。
在一些实施例中，如图2所示，在从节点200处设置有从节点无线模块210和从节点Flash 220。从节点200为电池管理系统的一个电池组的控制器。
在一些实施例中，主节点100和从节点200之间可以基于2.4GHz频段的无线短距离通信协议进行通信。
本公开上述实施例中，主节点100和从节点200本身集成了CAN转无线传输的功能，并且可以选择集成外置Flash芯片，可以快速部署到当前系统中。
在一些实施例中，主节点100，可以用于从车载通信系统远端接收盒获取系统更新数据；所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点，其中，所述系统更新数据用于从节点系统软件的更新，所述主节点为所述电池管理系统的主控制器，所述从节点为电池 管理系统的一个电池组的控制器。
本公开实施例的技术方案中，设计了基于无线BMS换电技术的OTA升级方法，将主从节点之间的数据传输由原来的CAN通信变为无线通信。由此提高了通信可靠性，提高了系统寿命，解决了相关技术方案中系统寿命短的技术问题。
针对相关技术的技术问题，本公开实施例将相关技术方案中主从节点之间经过CAN通信交互改为基于2.4G频段的无线通信，通信协议可以选择蓝牙等协议。本公开实施例通过增加无线模块，该模块提供CAN通信以及无线通信的功能，能够非常方便地部署到当前系统中。
请参照图3，图3为本公开电池管理系统的更新方法一些实施例的示意图。优选的，本实施例可由本公开电池管理系统或本公开主节点执行。在如图3所示，本公开电池管理系统的更新方法可以包括步骤31至步骤32中的至少一个步骤，其中：
步骤31，主节点从车载通信系统远端接收盒获取系统更新数据。
在一些实施例中，步骤31可以包括：主节点通过控制器局域网络通信方式从车载通信系统远端接收盒获取系统更新数据。
步骤32，所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点，其中，所述系统更新数据用于从节点系统软件的更新，所述主节点为所述电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器。
请参照图4，图4为本公开一些实施例中基于无线的传输层协议的更新方法的示意图。如图4所示，本公开基于无线的传输层协议的更新方法可以包括：所述主节点通过无线传输方式向所述从节点发送SF(Single frame，一帧数据)后，若在预定确认时间(T_CONF)内，所述 主节点未收到所述从节点的反馈(Retry)，则进行数据重传；若在预定确认时间内，所述主节点收到所述从节点的反馈，则主节点发送FF(First Frame，首帧)数据，并在收到响应FC(Flow Control，流控)消息后，进行CF(Continue Frame，连续帧)数据传输。
本公开上述实施例可以在CANTP协议(CAN传输协议)的基础上，基于无线传输现有的特性，加入重发机制。
在一些实施例中，如果使用的是蓝牙协议，由于链路层本身会进行重发，本公开可以通过软件协议可以关掉该功能。
本公开上述实施例基于当前通信模式下，考虑无线传输的特性，在CANTP协议的基础上设计实现基于无线的TP(Transport Layer，传输层)协议，从而可以控制无线数据传输，最大化利用带宽,提高通信可靠性。
在一些实施例中，图3实施例的步骤32可以包括：所述主节点采用广播传输方式，将系统更新数据发送给所述从节点。
在另一些实施例中，图3实施例的步骤32可以包括：所述主节点采用单播传输方式，将系统更新数据发送给所述从节点。
在一些实施例中，可以通过从节点的MAC(Media Access Control Address，媒体存取控制位址)，来区分当前需要更新哪个节点。
在一些实施例中，当配置MAC为0xFF时，为广播更新；否则为点对点更新。
在一些实施例中，所述主节点采用广播传输方式的情况下，所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点发热步骤可以包括：采用分时复用，对多个从节点进行分时段数据包传输。
在一些实施例中，所述采用分时复用，对多个从节点进行分时段数据包传输的步骤可以包括：根据当前连接的从节点数目，分配数据包长度和广播时间间隔。
在一些实施例中，多节点更新时，主节点采用广播传输的方式，该传输方式依赖于当前系统的所有连接句柄，OTA程序会根据当前连接的从节点数目，分配数据包长度和广播时间间隔。
在一些实施例中，若当前从节点数目为3，分别为第一从节点、第二从节点和第三从节点，则主节点在确定数据包长度和广播时间间隔后，在第一个广播时间间隔内，发送预定数据包长度的数据包括给第一从节点，在第二个广播时间间隔内，发送预定数据包长度的数据包括给第二从节点，在第三个广播时间间隔内，发送预定数据包长度的数据包括给第三从节点。
在一些实施例中，多节点更新时，可以加入分时复用和断点续传功能，断点的位置可配置，以Flash的Sector(扇区)大小为单位。
在一些实施例中，所述主节点采用广播传输方式的情况下，所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点的步骤还可以包括：采用对传输的数据包进行断点续传。
在一些实施例中，所述采用对传输的数据包进行断点续传的步骤可以包括：若任意从节点超时未应答，则所述主节点判断该从节点为故障从节点，剔除所述故障从节点，刷新广播传输时间间隔，并记录下故障从节点以及断点位置；在除所述故障从节点外其它从节点接收完该包数据后，所述主节点将重新发送数据给所述故障从节点。
请参照图5，图5为本公开电池管理系统的更新方法另一些实施例的示意图。优选的，本实施例可由本公开电池管理系统或本公开从节点执行。在如图5所示，本公开电池管理系统的更新方法可以包括步骤51至步骤52中的至少一个步骤，其中：
步骤51，从节点通过无线传输方式接收主节点发送的系统更新数据，其中，所述主节点为电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器，系统更新数据为所述主节点从车载通信 系统远端接收盒获取的。
步骤52，所述从节点根据所述系统更新数据对从节点系统软件的更新。
在一些实施例中，步骤52可以包括：将原系统软件程序进行备份；根据系统更新数据对从节点系统软件进行更新；在系统软件更新失败的情况下，自动回复恢复至原系统软件程序。
在一些实施例中，步骤52可以包括：从节点内部接收到传输的程序之后，先写入外置Flash中，并且加入对应的校验信息；单包数据完成传输后，会启动校验，若检验失败，主节点会记录当前中断节点号以及中断地址，待其他从节点接收完该包数据后，主节点将重新发数据给故障节点；若校验成功后会检测整个数据包是否接收完整，若接收完整可配置是否需要等待更新指令，或者直接执行软件复位，进行程序的更新。
在一些实施例中，步骤52可以包括：为了兼容回滚需求，在擦除原程序之前，会将其存在备份区域，若软件升级失败，会自动恢复至未升级前的版本；单节点更新时，主节点采用点对点传播方式；单节点更新时，若对应节点超时未应答，则主节点将记录故障节点，否则正常接收数据，数据接收以及软件升级的过程将重复执行所述在擦除原程序之前，会将其存在备份区域，若软件升级失败，会自动恢复至未升级前的版本的步骤。
请参照图6，图6为本公开电池管理系统的更新方法又一些实施例的示意图。优选的，本实施例可由本公开电池管理系统执行。在如图6所示，本公开电池管理系统的更新方法可以包括步骤601至步骤622中的至少一个步骤，其中：
步骤601，主节点接收到电池管理系统的更新请求。
步骤602，判断所述更新请求是否为广播更新请求。在所述更新请求为广播更新请求的情况下，执行步骤603；否则，在所述更新请求不 是广播更新请求的情况下，执行步骤615。
步骤603，主节点的OTA程序确定当前已连接从节点数目。
步骤604，根据当前已连接从节点数目分别数据包长度和广播间隔时间。
步骤605，从节点应答主节点。
步骤606，判断从节点的应答是否超时。在从节点的应答超时的情况下，执行步骤607；否则，在从节点的应答不超时的情况下，执行步骤608。
步骤607，主节点剔除该超时从节点，并将该超时从节点记录为故障从节点；之后结束。
步骤608，从节点进行数据接收，从节点完成一包数据的接收后，进行校验。
步骤609，校验该包数据的接收是否成功。在该包数据的接收成功的情况下，执行步骤610；否则，该包数据的接收不成功的情况下，执行步骤613。
步骤610，将校验标志位写为“1”。
步骤611，判断数据包是否接收完整。在数据包接收完整的情况下，执行步骤612；否则，数据包接收不完整的情况下，执行步骤608，即，进行下一包数据的接收。
步骤612，根据接收的完整数据包进行系统程序更新；之后，结束。
步骤613，主节点记录当前中断的节点号和中断地址。
步骤614，判断本轮更新周期是否结束。在本轮更新周期结束的情况下，执行步骤608，即，进行下一包数据的接收。
步骤615，采用单节点更新方式进行更新。
步骤616，从节点应答主节点。
步骤617，判断从节点的应答是否超时。在从节点的应答超时的情况下，执行步骤618；否则，在从节点的应答不超时的情况下，执行步骤619。
步骤618，主节点将该超时从节点记录为故障从节点；之后结束。
步骤619，从节点进行数据接收，从节点完成一包数据的接收后，进行校验。
步骤620，校验该包数据的接收是否成功。在该包数据的接收成功的情况下，执行步骤621；否则，该包数据的接收不成功的情况下，执行步骤619，即，进行下一包数据的接收。
步骤621，将校验标志位写为“1”。
步骤622，判断数据包是否接收完整。在数据包接收完整的情况下，执行步骤612；否则，数据包接收不完整的情况下，执行步骤619，即，进行下一包数据的接收。
请参照图7，图7为本公开一些实施例系统程序更新的示意图。优选的，本实施例可由本公开电池管理系统或本公开从节点执行。在如图7所示，本公开电池管理系统的更新方法(例如图6实施例的步骤612)可以包括步骤71至步骤73中的至少一个步骤，其中：
步骤71，从节点判断是否立即更新。在立即更新的情况下，执行步骤73；否则，在不立即更新的情况下，执行步骤72。
步骤72，从节点判断是否接收到更新指令；在接收到更新指令的情况下，执行步骤73。
步骤73，根据系统更新数据进行系统程序更新。
请参照图8，图8为本公开另一些实施例系统程序更新的示意 图。优选的，本实施例可由本公开电池管理系统或本公开从节点执行。在如图8所示，本公开电池管理系统的更新方法(例如图7实施例的步骤73)可以包括步骤731至步骤739中的至少一个步骤，其中：
步骤731，从节点执行复位，进入Bootloader中。
在一些实施例中，在嵌入式操作系统中，BootLoader是在操作系统内核运行之前运行，可以初始化硬件设备、建立内存空间映射图，可以引导加载程序，启动装载。
步骤732，判断Bootloader的检测校验位是否为“1”。在Bootloader的检测校验位为“1”的情况下，执行步骤733；否则，Bootloader的检测校验位不为“1”的情况下，结束。
步骤733，从节点将原程序输入Flash中备份。
步骤734，判断原程序备份是否完成。在原程序备份完成的情况下，执行步骤735；否则，在原程序备份未完成的情况下，执行步骤737。
步骤735，将诊断计数器加1。
步骤736，判断诊断计数器的计数值是否大于预定值。在诊断计数器的计数值大于预定值的情况下，结束；否则，在诊断计数器的计数值不大于预定值的情况下，在预定时间间隔后，再次执行步骤734。
在一些实施例中，所述预定值可以为3。
步骤737，从节点进行程序更新。
步骤738，判断程序更新是否成功。在程序更新成功的情况下，结束；否则，在程序更新不成功的情况下，执行步骤739。
步骤739，根据Flash中备份原程序进行回滚，将BMU恢复至未更新时的状态。
本公开上述实施例设计可无线通信的传输层协议，可以支持源数据的分包、组包和超时判断，重要参数能够匹配车端相关技术的基于CAN的传输层协议，适配性较广。
本公开上述实施例设计了主从架构无线BMS的软件更新协议，支持备份、回滚以及续传功能。
本公开上述实施例解决了相关技术与主从架构的无线BMS系统匹配性低、软件升级可靠性低的问题，且本公开上述实施例提供的OTA升级方法拓展性强，复用率高。
请参照图9，图9为本公开主节点一些实施例的示意图。如图9所示，本公开主节点(例如图2实施例的主节点100)可以包括更新数据接收模块101和更新数据发送模块102，其中：
更新数据接收模块101，用于从车载通信系统远端接收盒获取系统更新数据。
更新数据发送模块102，用于通过无线传输方式将所述系统更新数据发送给至少一个从节点，其中，所述系统更新数据用于从节点系统软件的更新，所述主节点为所述电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器。
在一些实施例中，更新数据发送模块102可以用于通过无线传输方式向所述从节点发送一帧数据后，若在预定确认时间内，所述主节点未收到所述从节点的反馈，则进行数据重传。
在一些实施例中，更新数据发送模块102可以用于采用广播传输方式，将系统更新数据发送给所述从节点。
在另一些实施例中，更新数据发送模块102可以用于采用单播传输方式，将系统更新数据发送给所述从节点。
在一些实施例中，更新数据发送模块102可以用于采用分时复用，对多个从节点进行分时段数据包传输。
在一些实施例中，更新数据发送模块102可以用于根据当前连接的从节点数目，分配数据包长度和广播时间间隔。
在一些实施例中，更新数据发送模块102可以用于采用对传输的数据包进行断点续传。
在一些实施例中，更新数据发送模块102可以用于若任意从节点超时未应答，则所述主节点判断该从节点为故障从节点，剔除所述故障从节点，刷新广播传输时间间隔，并记录下故障从节点以及断点位置；在除所述故障从节点外其它从节点接收完该包数据后，所述主节点将重新发送数据给所述故障从节点。
在一些实施例中，所述主节点用于执行实现如上述任一实施例(例如图3实施例)所述的更新方法的操作。
请参照图10，图10为本公开从节点一些实施例的示意图。如图10所示，本公开从节点(例如图2实施例的从节点200)可以包括数据接收单元201和软件更新单元202，其中：
数据接收单元201，用于通过无线传输方式接收主节点发送的系统更新数据，其中，所述主节点为电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器，系统更新数据为所述主节点从车载通信系统远端接收盒获取的。
软件更新单元202，用于根据所述系统更新数据对从节点系统软件的更新。
在一些实施例中，软件更新单元202可以用于将原系统软件程序进行备份；根据系统更新数据对从节点系统软件进行更新；在系统软件更新失败的情况下，自动回复恢复至原系统软件程序。
在一些实施例中，所述从节点用于执行实现如上述任一(例如图5、图7或图8实施例)实施例所述的更新方法的操作。
图11为本公开计算机装置一些实施例的结构示意图。如图11所示，计算机装置包括存储器301和处理器302。
存储器301用于存储指令，处理器302耦合到存储器301，处理器302被配置为基于存储器存储的指令执行实现上述实施例(例如图3-图8任一实施例)涉及的方法。
在一些实施例中，处理器302被配置为基于存储器存储的指令执行实现上述实施例(例如图5、图7或图8实施例)涉及的方法，则计算机装置可以实现为从节点。
在一些实施例中，处理器302被配置为基于存储器存储的指令执行实现上述实施例(例如图3实施例)涉及的方法，则计算机装置可以实现为主节点。
如图11所示，该计算机装置还包括通信接口303，用于与其它设备进行信息交互。同时，该计算机装置还包括总线304，处理器302、通信接口303、以及存储器301通过总线304完成相互间的通信。
存储器301可以包含高速RAM存储器，也可还包括非易失性存储器(non-volatile memory)，例如至少一个磁盘存储器。存储器301也可以是存储器阵列。存储器301还可能被分块，并且块可按一定的规则组合成虚拟卷。
此外，处理器302可以是一个中央处理器CPU，或者可以是专用集成电路ASIC，或是被配置成实施本公开实施例的一个或多个集成电路。
本公开还提供了一种非瞬时性计算机可读存储介质，其中，所述非瞬时性计算机可读存储介质存储有计算机指令，所述指令被处理器执行时实现如上述任一实施例(例如图3-图8任一实施例)所述的更新方法。
本领域内的技术人员应明白，本公开的实施例可提供为方法、 装置、或计算机程序产品。因此，本公开可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本公开可采用在一个或多个其中包含有计算机可用程序代码的计算机可用非瞬时性存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本公开是参照根据本公开实施例的方法、设备(系统)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在上面所描述的主节点和从节点可以实现为用于执行本申请所描述功能的通用处理器、可编程逻辑控制器(PLC)、数字信号处理器 (DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。
虽然已经参考优选实施例对本申请进行了描述，但在不脱离本申请的范围的情况下，可以对其进行各种改进并且可以用等效物替换其中的部件。尤其是，只要不存在结构冲突，各个实施例中所提到的各项技术特征均可以任意方式组合起来。本申请并不局限于文中公开的特定实施例，而是包括落入权利要求的范围内的所有技术方案。

Claims (16)

  1. 一种电池管理系统的更新方法，包括：
    主节点从车载通信系统远端接收盒获取系统更新数据；
    所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点，其中，所述系统更新数据用于从节点系统软件的更新，所述主节点为所述电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器。
  2. 根据权利要求1所述的更新方法，其中，所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点包括：
    所述主节点通过无线传输方式向所述从节点发送一帧数据后，若在预定确认时间内，所述主节点未收到所述从节点的反馈，则进行数据重传。
  3. 根据权利要求1或2所述的更新方法，其中，所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点包括：
    所述主节点采用广播传输方式，将系统更新数据发送给所述从节点；
    或，
    所述主节点采用单播传输方式，将系统更新数据发送给所述从节点。
  4. 根据权利要求3所述的更新方法，其中，所述主节点采用广播传输方式的情况下，所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点包括：
    采用分时复用，对多个从节点进行分时段数据包传输。
  5. 根据权利要求4所述的更新方法，其中，所述采用分时复用，对多个从节点进行分时段数据包传输包括：
    根据当前连接的从节点数目，分配数据包长度和广播时间间隔。
  6. 根据权利要求4所述的更新方法，其中，所述主节点采用广播传输方式的情况下，所述主节点通过无线传输方式将所述系统更新数据发送给至少一个从节点还包括：
    采用对传输的数据包进行断点续传。
  7. 根据权利要求6所述的更新方法，其中，所述采用对传输的数据包进行断点续传包括：
    若任意从节点超时未应答，则所述主节点判断该从节点为故障从节点，剔除所述故障从节点，刷新广播传输时间间隔，并记录下故障从节点以及断点位置；
    在除所述故障从节点外其它从节点接收完该包数据后，所述主节点将重新发送数据给所述故障从节点。
  8. 一种电池管理系统的更新方法，包括：
    从节点通过无线传输方式接收主节点发送的系统更新数据，其中，所述主节点为电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器，系统更新数据为所述主节点从车载通信系统远端接收盒获取的；
    所述从节点根据所述系统更新数据对从节点系统软件的更新。
  9. 根据权利要求8所述的更新方法，其中，所述从节点根据所述系统更新数据对从节点系统软件的更新包括：
    将原系统软件程序进行备份；
    根据系统更新数据对从节点系统软件进行更新；
    在系统软件更新失败的情况下，自动回复恢复至原系统软件程序。
  10. 一种主节点，包括：
    更新数据接收模块，用于从车载通信系统远端接收盒获取系统更新数据；
    更新数据发送模块，用于通过无线传输方式将所述系统更新数据发送给至少一个从节点，其中，所述系统更新数据用于从节点系统软件的更新，所述主节点为所述电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器。
  11. 根据权利要求10所述的主节点，其中，所述主节点用于执行实现如权利要求1-7中任一项所述的更新方法的操作。
  12. 一种从节点，包括：
    数据接收单元，用于通过无线传输方式接收主节点发送的系统更新数据，其中，所述主节点为电池管理系统的主控制器，所述从节点为电池管理系统的一个电池组的控制器，系统更新数据为所述主节点从车载通信系统远端接收盒获取的；
    软件更新单元，用于根据所述系统更新数据对从节点系统软件的更新。
  13. 根据权利要求12所述的从节点，其中，所述从节点用于执行实现如权利要求8或9所述的更新方法的操作。
  14. 一种计算机装置，包括：
    存储器，用于存储指令；
    处理器，用于执行所述指令，使得所述计算机装置执行实现如权利要求1-9中任一项所述的更新方法的操作。
  15. 一种电池管理系统，包括如权利要求10或11所述的主节点和如权利要求12或13所述的从节点。
  16. 一种非瞬时性计算机可读存储介质，其中，所述非瞬时性计算机可读存储介质存储有计算机指令，所述指令被处理器执行时实现如权利要求1-9中任一项所述的更新方法。
PCT/CN2021/136100 2021-12-07 2021-12-07 电池管理系统及其更新方法、主节点、从节点和存储介质 Ceased WO2023102733A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/136100 WO2023102733A1 (zh) 2021-12-07 2021-12-07 电池管理系统及其更新方法、主节点、从节点和存储介质
CN202180094444.4A CN116941093A (zh) 2021-12-07 2021-12-07 电池管理系统及其更新方法、主节点、从节点和存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/136100 WO2023102733A1 (zh) 2021-12-07 2021-12-07 电池管理系统及其更新方法、主节点、从节点和存储介质

Publications (1)

Publication Number Publication Date
WO2023102733A1 true WO2023102733A1 (zh) 2023-06-15

Family

ID=86729448

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/136100 Ceased WO2023102733A1 (zh) 2021-12-07 2021-12-07 电池管理系统及其更新方法、主节点、从节点和存储介质

Country Status (2)

Country Link
CN (1) CN116941093A (zh)
WO (1) WO2023102733A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119232564A (zh) * 2024-09-14 2024-12-31 孝感楚能新能源创新科技有限公司 主从通讯线路的故障确定方法、装置及系统
CN119473367A (zh) * 2025-01-17 2025-02-18 惠州市乐亿通科技股份有限公司 数据更新方法、系统、设备、介质和程序产品
CN119583345A (zh) * 2025-02-06 2025-03-07 安徽容知日新科技股份有限公司 一种物联网设备远程更新方法与物联网系统
WO2026056059A1 (zh) * 2024-09-12 2026-03-19 上能电气股份有限公司 储能电池系统、地址分配方法、装置及设备
WO2026061085A1 (zh) * 2024-09-18 2026-03-26 欣捷安汽车电子有限公司 通信时间片的调配方法、装置、系统、电子设备及计算机可读存储介质
WO2026061082A1 (zh) * 2024-09-18 2026-03-26 欣旺达动力科技股份有限公司 通讯时间片的分配方法、装置、系统及计算机可读存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108279916A (zh) * 2017-12-28 2018-07-13 宁德时代新能源科技股份有限公司 电子控制单元程序更新方法和装置
CN110896543A (zh) * 2018-09-12 2020-03-20 宁德时代新能源科技股份有限公司 电池管理系统及传输信息的方法和装置
CN112102599A (zh) * 2019-06-17 2020-12-18 硅工厂股份有限公司 无线电池管理系统、无线通信的节点和发送数据的方法
US20210098833A1 (en) * 2019-09-26 2021-04-01 Power.Global, Pbc Modular remote battery pack
WO2021101012A1 (ko) * 2019-11-19 2021-05-27 주식회사 엘지에너지솔루션 배터리 관리 시스템 및 그 제어방법
CN113568631A (zh) * 2020-04-29 2021-10-29 现代自动车株式会社 车辆中的空中下载更新设备及其方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108279916A (zh) * 2017-12-28 2018-07-13 宁德时代新能源科技股份有限公司 电子控制单元程序更新方法和装置
CN110896543A (zh) * 2018-09-12 2020-03-20 宁德时代新能源科技股份有限公司 电池管理系统及传输信息的方法和装置
CN112102599A (zh) * 2019-06-17 2020-12-18 硅工厂股份有限公司 无线电池管理系统、无线通信的节点和发送数据的方法
US20210098833A1 (en) * 2019-09-26 2021-04-01 Power.Global, Pbc Modular remote battery pack
WO2021101012A1 (ko) * 2019-11-19 2021-05-27 주식회사 엘지에너지솔루션 배터리 관리 시스템 및 그 제어방법
CN113568631A (zh) * 2020-04-29 2021-10-29 现代自动车株式会社 车辆中的空中下载更新设备及其方法

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2026056059A1 (zh) * 2024-09-12 2026-03-19 上能电气股份有限公司 储能电池系统、地址分配方法、装置及设备
CN119232564A (zh) * 2024-09-14 2024-12-31 孝感楚能新能源创新科技有限公司 主从通讯线路的故障确定方法、装置及系统
WO2026061085A1 (zh) * 2024-09-18 2026-03-26 欣捷安汽车电子有限公司 通信时间片的调配方法、装置、系统、电子设备及计算机可读存储介质
WO2026061082A1 (zh) * 2024-09-18 2026-03-26 欣旺达动力科技股份有限公司 通讯时间片的分配方法、装置、系统及计算机可读存储介质
CN119473367A (zh) * 2025-01-17 2025-02-18 惠州市乐亿通科技股份有限公司 数据更新方法、系统、设备、介质和程序产品
CN119583345A (zh) * 2025-02-06 2025-03-07 安徽容知日新科技股份有限公司 一种物联网设备远程更新方法与物联网系统
CN119583345B (zh) * 2025-02-06 2025-06-06 安徽容知日新科技股份有限公司 一种物联网设备远程更新方法与物联网系统

Also Published As

Publication number Publication date
CN116941093A (zh) 2023-10-24

Similar Documents

Publication Publication Date Title
WO2023102733A1 (zh) 电池管理系统及其更新方法、主节点、从节点和存储介质
JP7562661B2 (ja) ソフトウェアアップグレード方法、装置、およびシステム
CN202475489U (zh) 一种更新程序的无线传感器网络
CN111145523A (zh) 用电信息采集系统中微功率无线通信模块的升级方法
CN114006791A (zh) 一种低延时报文转发方法及网关
WO2010135897A1 (zh) 一种独占闪存组合设备空中固件升级方法及装置
CN113973088B (zh) 一种智能主机的mcu通信服务系统
WO2024066449A1 (zh) 通信故障处理方法、系统及设备
CN111490918B (zh) 车载以太网网络唤醒系统、方法、装置和计算机设备
CN118473929A (zh) 一种储能系统用远程升级方法、装置及介质
CN113422738B (zh) 一种智能主机的mcu通信服务方法
CN115695077A (zh) 一种总线数据接收方法、装置、电子设备及存储介质
WO2024183762A1 (zh) 测试系统
CN118473928A (zh) 基于lora通信的远程固件升级装置及其升级方法
CN117377090A (zh) 一种节点配置方法、通信装置和通信系统
CN115904439A (zh) 一种基于以太网的控制器批量刷写方法、系统及车辆
CN120457412A (zh) 一种升级检测方法及装置
CN116347425A (zh) 一种无线终端固件升级方法及系统
CN115550808A (zh) 蓝牙耳机升级方法、电子设备及可读存储介质
CN118826195A (zh) 电源管理方法、电池管理方法及设备、网管系统、介质
CN113791804A (zh) 多路仪器并行升级的方法、装置、计算机设备及存储介质
KR102952249B1 (ko) 차량용 ecu의 복구 이미지 관리 방법 및 장치
CN115065572B (zh) 一种面向车载电子系统的can fd控制器
WO2025161094A1 (zh) 全链路双重验证机制的固件升级方法、装置、设备及介质
CN119883315A (zh) 一种串行外设接口、车载域控制器的升级方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21966657

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202180094444.4

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21966657

Country of ref document: EP

Kind code of ref document: A1