Message Abnormality Detection Method, Device, Equipment, Storage Medium and Program Product

Abstract

Embodiments of the present application provide a message anomaly detection method, apparatus, device, storage medium, and program product, wherein the message anomaly detection method includes: sending a charging request message to the charging device in response to a charging start signal sent by the charging device; receiving a target message based on a receiving identifier; the receiving identifier is the same as the sending identifier of the charging request message; based on the target message and the charging request message, performing an anomaly detection on the message transmitted between the battery and the charging device to obtain a message anomaly result; wherein the anomaly detection includes at least comparing the charging content in the target message and the charging request message. The battery can identify messages with abnormal charging request content transmitted between the battery and the charging device, thereby improving the charging safety of the battery.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of battery technology, and are related to, but not limited to, a message anomaly detection method, apparatus, device, storage medium, and program product. Background Art

[0002] When charging, electric vehicles communicate with charging piles through the Controller Area Network (CAN) bus to negotiate charging parameters such as charging current and voltage. However, no secure communication protocol is used for data transmission between the vehicle and the charging pile, and no encryption measures are taken for message exchanges between the vehicle and the charging pile. This poses serious information security issues and exposes them to potential network security attacks at all times. For example, a third party can use an external device to simulate an electric vehicle and send a charging request message to the charging pile, which may cause the battery to overcharge and affect its service life.

[0003] The related technology detects whether the message on the bus is abnormal, but does not identify and judge the content of the message. It is unable to identify the message with abnormal charging request content sent by a third party, resulting in the charging pile charging the vehicle based on the abnormal charging request, causing the vehicle battery to overcharge. Summary of the Invention

[0004] In order to solve the problems existing in the related technology, the embodiments of the present application provide a message anomaly detection method, device, equipment, storage medium and program product. By receiving all messages with sending identification between the battery and the charging device, these messages are compared with the charging content of the charging demand message sent by the vehicle. According to the comparison results, it can be determined whether the target message is significantly different from the charging demand message, whether the target message is an abnormal request message, and then determine whether there are false charging instructions or data maliciously sent by a third party between the battery and the charging device, thereby realizing real-time detection of abnormal charging messages between the battery and the charging device.

[0005] In a first aspect, the present application provides a message anomaly detection method, which includes: sending a charging requirement message to the charging device in response to a charging start signal sent by the charging device; receiving a target message corresponding to the receiving identifier based on a receiving identifier; the receiving identifier is the same as the sending identifier of the charging requirement message; based on the target message and the charging requirement message, performing anomaly detection on the message transmitted between the battery and the charging device to obtain a message anomaly result; wherein the anomaly detection at least includes comparing the charging content in the target message and the charging requirement message.

[0006] In the above embodiment, all messages with a sending identifier are received between the battery and the charging device (which may be on the bus) by simulating the charging device, and these messages are compared with the charging demand messages sent by the vehicle. According to the comparison results, it can be determined whether the target message is significantly different from the charging demand message, whether the target message is an abnormal request message, and then whether there are false charging instructions or data maliciously sent by a third party between the battery and the charging device. Real-time detection and active defense of charging messages between the battery and the charging device are achieved, which can effectively prevent external attacks during the charging process, thereby ensuring the safety and reliability of the electric vehicle charging process and improving the charging system's anti-attack capability.

[0007] In some embodiments, the message anomaly detection method further includes: configuring a message receiving identifier for receiving messages in the receiving filter of the battery management system of the battery, wherein the message receiving identifier is different from the sending identifier; in response to the charging start signal, the message receiving identifier is adjusted to be the same as the sending identifier to obtain a receiving identifier.

[0008] In the above embodiment, by adjusting the message receiving identifier configured in the receiving filter to receive the corresponding messages between the battery and the charging device, unnecessary message processing can be significantly reduced, thereby reducing the processing volume of the battery management system and reducing the storage space and processing time occupied by unnecessary messages. This not only improves the processing efficiency of the battery management system, but also enhances the real-time processing of the battery management system, and can quickly determine abnormal messages and take corresponding measures to reduce damage to the battery due to abnormal conditions.

[0009] In some embodiments, receiving a target message based on a receiving identifier includes: receiving a message transmitted between a battery and a charging device; matching the message identifier of each message with the sending identifier to obtain a matching result; and in response to the matching result indicating that the message identifier is the same as the sending identifier, determining the message corresponding to the message identifier as the target message.

[0010] In the above embodiment, by sending an identifier, a message with the identifier can be received between the battery and the charging device, so that the battery management system can receive the message sent between the battery and the charging device to the charging pile for adjusting the vehicle charging parameters, and can actively identify abnormal attack messages between the battery and the charging device, thereby improving the safety of the vehicle charging process.

[0011] In some embodiments, based on the target message and the charging demand message, an anomaly detection is performed on the message transmitted between the battery and the charging device to obtain a message anomaly result, including: parsing the target message to obtain the target charging request data of the target message; comparing the target charging request data with the charging request data of the charging demand message to obtain a message anomaly result.

[0012] In some embodiments, the target charging request data is compared with the charging request data of the charging demand message to obtain a message abnormality result, including: in response to the difference between the target charging request data and the charging request data being greater than a first preset threshold, determining that the message abnormality result is an abnormal message between the battery and the charging device; correspondingly, the message abnormality detection method also includes: in response to the message abnormality result being an abnormal message between the battery and the charging device, sending a charge suspension message to the charging device; the charge suspension message is used to instruct the charging device to stop charging the battery.

[0013] In the above embodiment, if the message abnormality result indicates that an abnormal message exists between the battery and the charging device, the battery can send a charge suspension message to the charging device to instruct the charging device to stop charging the battery. The abnormal situation can be discovered in time and a protection strategy can be formulated, thereby reducing the probability of battery damage due to overcharging, improving battery life, and improving the safety, stability and reliability of the charging system.

[0014] In a second aspect, an embodiment of the present application provides a message anomaly detection method, which includes: in response to connection with a battery, sending a charging start signal to the battery, so that the battery sends a charging requirement message to the charging device in response to the charging start signal; receiving a target message based on a receiving identifier; the receiving identifier is the same as the sending identifier of the charging requirement message; based on the target message and the charging requirement message, performing anomaly detection on the message transmitted between the battery and the charging device to obtain a message anomaly result; wherein the anomaly detection at least includes comparing the charging content in the target message and the charging requirement message.

[0015] In the above embodiment, during the charging process of the charging device and the vehicle, the battery management system can simulate the charging device to receive all messages with a sending identifier between the battery and the charging device, and compare these messages with the charging demand messages sent by the vehicle. According to the comparison results, it can be determined whether the target message is significantly different from the charging demand message, whether the target message is an abnormal request message, and then determine whether there are false charging instructions or data maliciously sent by a third party between the battery and the charging device. Real-time detection and active defense of charging messages between the battery and the charging device are realized, which can effectively prevent external attacks during the charging process, thereby ensuring the safety and reliability of the electric vehicle charging process and improving the charging system's anti-attack capability.

[0016] In some embodiments, the message anomaly detection method also includes: receiving a target message with a sending identifier between the battery and the charging device, and placing the target message into a receiving buffer of the charging device; in response to receiving a new target message, overwriting the target message in the receiving buffer to obtain a corresponding message set of the receiving buffer; comparing the contents of the target message in the message set to obtain a message anomaly result.

[0017] In the above embodiment, the charging device forms a message set by receiving and recording the target messages between the battery and the charging device, and can identify whether the content of the target message transmitted between the battery and the charging device is abnormal based on the content of multiple groups of message sets, thereby improving the charging safety of the charging vehicle.

[0018] In some embodiments, the target message in the receiving buffer is overwritten to obtain a corresponding message set of the receiving buffer, including: in response to the number of target messages in the receiving buffer being equal to the cache threshold of the receiving buffer, based on the receiving time of each target message in the receiving buffer, determining the message to be overwritten with the earliest receiving time; overwriting the message to be overwritten with the new target message to obtain a message set.

[0019] In the above embodiment, only a cache threshold number of target messages are retained in the receiving buffer, and the target message received earliest in the receiving buffer is overwritten by the new target message. This not only reduces the waste of cache space, but also ensures that the receiving buffer always stores the latest charging requirements of the battery.

[0020] In some embodiments, the message anomaly detection method also includes: determining multiple groups of message sets based on multiple new target messages continuously received; correspondingly, comparing the contents of the target messages in the message sets to obtain message anomaly results, including: comparing the charging request data of each target message in each group of message sets to obtain a comparison result; in response to the comparison result indicating that there is a jump in the charging request data in a preset number of consecutive groups of message sets, determining that there are abnormal messages between the battery and the charging device; the jump indicates that the difference between the charging request data of any two charging demand messages in the message set is greater than a second preset threshold.

[0021] In the above embodiment, by identifying and judging the message contents based on the received multiple sets of consecutive message sets, it is possible to promptly determine whether there is external interference or abnormal messages between the battery and the charging device, thereby improving the charging safety of the vehicle.

[0022] In some embodiments, the message anomaly detection method further includes: in response to a message anomaly result indicating that an abnormal message exists between the battery and the charging device, determining target charging request data that meets the charging condition in the charging request data of the target message currently received in the buffer; the charging condition is used to characterize the minimum value of the charging request data in the currently received buffer; charging the battery based on the target charging request data until the message anomaly result indicates that no abnormal message exists between the battery and the charging device; in response to the message anomaly result indicating that no abnormal message exists between the battery and the charging device, charging the battery based on the charging request data of the received new target message.

[0023] In the above embodiment, whether there is an abnormality between the battery and the charging device is determined by identifying the content of the charging demand message. If abnormal message content occurs, the output safety of the charging device itself is ensured by responding only to a smaller request value, and the charging safety of the charging vehicle can also be improved.

[0024] In a third aspect, an embodiment of the present application provides a message anomaly detection device, which includes: a first sending module, used to send a charging requirement message to the charging device in response to a charging start signal sent by the charging device; a receiving module, used to receive a target message based on a receiving identifier; the receiving identifier is the same as the sending identifier of the charging requirement message; a detection module, used to perform anomaly detection on the message transmitted between the battery and the charging device based on the target message and the charging requirement message, and obtain a message anomaly result; wherein the anomaly detection at least includes comparing the charging content in the target message and the charging requirement message.

[0025] In a fourth aspect, an embodiment of the present application provides a message anomaly detection device, which includes: a second sending module, for sending a charging start signal to the battery in response to being connected to the battery, so that the battery sends a charging requirement message to the charging device in response to the charging start signal; receiving a target message based on a receiving identifier; the receiving identifier is the same as the sending identifier of the charging requirement message; based on the target message and the charging requirement message, performing anomaly detection on the message transmitted between the battery and the charging device to obtain a message anomaly result; wherein the anomaly detection at least includes comparing the charging content in the target message and the charging requirement message.

[0026] In a fifth aspect, an embodiment of the present application provides a message anomaly detection device, comprising: a memory for storing executable instructions; and a processor for implementing the steps in the above-mentioned message anomaly detection method when executing the executable instructions stored in the memory.

[0027] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium having executable instructions stored thereon. When the executable instructions are executed by a processor, the steps in the above-mentioned message anomaly detection method are implemented.

[0028] In a seventh aspect, an embodiment of the present application provides a computer program product, including a computer program or instructions, which, when executed by a processor, implements the steps in the above-mentioned message anomaly detection method.

[0029] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1 This is an optional process diagram of the message anomaly detection method provided in the embodiment of the application. Figure 1 ;

[0031] Figure 2 This is an optional process diagram of the message anomaly detection method provided in the embodiment of the application. Figure 2 ;

[0032] Figure 3 This is an optional process diagram of the message anomaly detection method provided in the embodiment of the application. Figure 3 ;

[0033] Figure 4 This is a flow chart of a charging request abnormality protection strategy implemented by a battery management system according to an embodiment of the present application;

[0034] Figure 5 This is a flow chart of a charging request abnormality protection strategy for a charging pile provided in an embodiment of the present application;

[0035] Figure 6 This is a schematic diagram of the structure of a message anomaly detection device provided in an embodiment of the present application. Figure 1 ;

[0036] Figure 7 This is a schematic diagram of the structure of a message anomaly detection device provided in an embodiment of the present application. Figure 2 ;

[0037] Figure 8 It is a hardware entity diagram of the charging device in the embodiment of the present application. DETAILED DESCRIPTION

[0038] In order to make the purpose, technical solutions and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limiting this application. All other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0039] In the following description, reference is made to "some embodiments," which describe a subset of all possible embodiments. However, it will be understood that "some embodiments" may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict. Unless otherwise defined, all technical and scientific terms used in the embodiments of this application have the same meaning as commonly understood by those skilled in the art to which the embodiments of this application pertain. The terms used in the embodiments of this application are for the purpose of describing the embodiments of this application only and are not intended to limit this application.

[0040] Currently, when a vehicle is charged by a charging station, based on the current national standard DC charging protocol, no encryption is implemented when exchanging messages between the charging vehicle and the charging station over the CAN bus. This allows third parties to easily obtain and even tamper with the exchanged data in the charging messages via external devices. For example, a third party could use an external device to simulate an electric vehicle and send a charging request message containing abnormal charging data to the charging station. The charging station would then charge the vehicle based on the abnormal charging request, potentially causing battery overcharging, which would not only affect battery life but also create safety issues during charging. Specifically, a third party could use an external device to construct a message with the same ID as the vehicle. The request content in this message could differ significantly from the charging current and voltage required by the vehicle itself. Because the ID of the third-party message is the same as the ID of the charging request message sent by the vehicle, the charging device would, upon receiving the third-party message, assume that the message was sent by the vehicle and would change the charging current or voltage to the vehicle based on the data in the third-party message, causing the vehicle's battery to overcharge.

[0041] While related technologies do detect abnormalities in bus messages, they primarily focus on the message format and transmission process, for example by examining basic features like message length, period, and frequency. However, these technologies fail to identify and verify message content, failing to deeply analyze the specific contents of messages and, therefore, failing to identify malicious or abnormal charging requests on the bus.

[0042] In order to alleviate the problems existing in the relevant technology, the applicant provides a method for detecting abnormal messages between the battery and the charging device (which can be CAN bus transmission, wireless LAN transmission, Bluetooth transmission, cellular network transmission, radio frequency transmission, Ethernet transmission, fiber optic communication, etc.) without changing the existing charging protocol. The charging management system (BMS) of the battery in the vehicle connected to the charging pile can simulate the charging pile to receive the charging message for the vehicle on the bus, and compare the charging data of the message received on the bus with the charging data of the charging message sent by the vehicle. When the charging data deviates greatly, it is considered that an abnormal message has appeared on the bus. At this time, the charging process between the vehicle and the charging pile is terminated to prevent the charging pile from charging the vehicle based on the abnormal message.

[0043] Based on the above considerations, the inventors have conducted in-depth research and provided a method for detecting abnormalities in abnormal messages. The BMS of the vehicle battery can respond to the charging start signal sent by the charging device, send a charging requirement message to the charging device, receive a target message with the same sending identifier as the charging requirement message, and perform abnormality detection on the messages transmitted between the battery and the charging device based on the target message and the charging requirement message. The abnormality detection at least includes comparing the charging content in the target message and the charging requirement message to obtain a message abnormality result.

[0044] In this way, the abnormal message abnormality detection method provided in the embodiment of the present application can simulate the charging device by allowing the battery management system to receive all messages with sending identification between the battery and the charging device, and compare these messages with the charging content of the charging demand message sent by the vehicle. According to the comparison result, it can be determined whether the target message is significantly different from the charging demand message, whether the target message is an abnormal request message, and then determine whether there are false charging instructions or data maliciously sent by a third party between the battery and the charging device, thereby realizing real-time detection and active defense of charging messages between the battery and the charging device, which can effectively prevent external attacks during the charging process, thereby ensuring the safety and reliability of the electric vehicle charging process, and also improving the charging system's anti-attack capability.

[0045] In an embodiment of the present application, the message anomaly detection method can be implemented based on a message anomaly detection device, and the message anomaly detection device can be a BMS or a charging device of a battery.

[0046] In the embodiments of the present application, the charging device may be a device for charging a battery, and may be a charging pile, a charger, or various energy storage devices. The charging device may be used to power electronic devices that require battery power, such as electric vehicles, electric bicycles, drones, and electric tools. Here, the charging device may be implemented as a charging pile terminal, which may include a processor. The processor may be an integrated circuit chip in the charging device, which has signal processing capabilities. The charging device implements interaction with the battery management system (BMS) based on the processor. The chip may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.

[0047] The charging device can also be implemented as a server corresponding to the charging pile. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. The charging device and the server can be directly or indirectly connected via wired or wireless communication, which is not limited in the embodiments of this application.

[0048] The charging device here can be a DC charging station. A DC charging station is a charging device that provides DC voltage to electric vehicles, directly charging the electric vehicle's power battery. DC charging stations convert AC power to DC power and supply it directly to the electric vehicle battery, eliminating the conversion time required by the on-board charger and achieving higher charging efficiency. This is commonly referred to as "fast charging."

[0049] The battery here can be any new energy battery equipped with a battery management system. Currently, new energy batteries are increasingly being used in everyday life and industry. They are not only used in energy storage systems such as hydropower, thermal power, wind power, and solar power plants, but are also widely used in electric vehicles such as electric bicycles, electric motorcycles, and electric vehicles, as well as in aerospace and other fields. As the application areas of power batteries continue to expand, their market demand is also growing.

[0050] In the embodiments of the present application, the battery involved may be a battery cell, also known as a battery core. A battery cell refers to a basic unit that can realize the mutual conversion of chemical energy and electrical energy, and can be used to make a battery module or battery pack, thereby being used to supply power to an electrical device. A battery cell may be a secondary battery, which refers to a battery cell that can be activated by charging the active material after the battery cell is discharged and can continue to be used. The battery cell may be a lithium-ion battery, a sodium-ion battery, a sodium-lithium-ion battery, a lithium metal battery, a sodium metal battery, a lithium-sulfur battery, a magnesium-ion battery, a nickel-hydrogen battery, a nickel-cadmium battery, a lead-acid battery, etc., and the embodiments of the present application do not limit this.

[0051] In the embodiments of the present application, a battery cell may refer to a battery cell of any shape, such as a square battery cell, a round battery cell, etc. And a battery cell generally refers to a battery cell, which is one of the basic units that constitute a battery. The battery cell is the core component of the battery and is responsible for storing and releasing electrical energy. The battery cell may be: a lithium-ion battery cell (Li-ion Cell), a lithium-polymer battery cell (Li-polymer Cell), a nickel-metal hydride battery cell (NiMH Cell), etc. The embodiments of the present application do not impose any restrictions on the type of battery cell, and the specific type can be selected according to the actual application scenario.

[0052] In the embodiment of the present application, the battery cell is the core component of the battery pack. A battery pack usually includes multiple battery cells, which are combined together to provide the required power capacity and voltage. The components of the battery pack include at least: battery cells, battery management system (BMS, Battery Management System), casing, connecting harness, connector and interface, etc. These components work together to combine the battery cells into a fully functional battery pack for various application scenarios. For example, the battery pack can be used in electric vehicles, energy storage systems, portable electrical equipment, solar energy systems, wind energy systems, emergency backup power supplies, power tools or electric bicycles, etc. The embodiment of the present application does not impose any restrictions on this, and the specific selection can be made according to the actual application scenario.

[0053] It should be noted that the battery pack can use different types of battery cells, such as lithium-ion batteries, nickel-metal hydride batteries, lithium polymer batteries, etc., depending on the actual application needs and performance requirements.

[0054] In the embodiment of the present application, the battery may also be a single physical module including one or more battery cells to provide higher voltage and capacity. When there are multiple battery cells, the multiple battery cells are connected in series, in parallel or in hybrid via a busbar.

[0055] Here, the message anomaly detection method provided in the embodiment of the present application can be implemented based on the interaction between the charging device and the battery.

[0056] Figure 1 This is an optional process diagram of the message anomaly detection method provided in the embodiment of the application. Figure 1 ,like Figure 1 As shown, the message anomaly detection method provided in the embodiment of the present application can be implemented through steps S101 to S103. It should be noted that, Figure 1 The message anomaly detection method in the embodiment can be described by taking the BMS of the battery as the execution subject and the battery being the battery in the electric vehicle as an example.

[0057] Step S101: In response to a charging start signal sent by a charging device, a charging requirement message is sent to the charging device.

[0058] In some embodiments, the charging device sending a charging start signal to the battery's battery management system may mean that after the physical connection between the battery and the charging device is completed, the charging device provides a low-voltage power supply to the vehicle's BMS to enable the BMS to operate normally. The charging device then establishes a communication link and performs identity authentication to ensure that both parties can safely perform subsequent charging operations. After the charging handshake phase is completed, the vehicle and the charging device enter the charging parameter configuration phase to negotiate specific battery charging parameters. The charging device charges the battery according to the final negotiated charging parameters to ensure the safety and efficiency of the charging process. At this point, after negotiating the charging parameters, the charging device sends a charging start signal to the battery's battery management system, then obtains a charging requirement message from the battery, and charges the battery according to the charging requirements in the charging requirement message, and the battery enters the charging phase.

[0059] Step S102: Receive a target message based on a receiving identifier; the receiving identifier is the same as the sending identifier of the charging demand message.

[0060] In the embodiments of the present application, each device connected to a CAN local area network (e.g., a charging device and a vehicle) can utilize the CAN bus to transmit messages and receive various information from the CAN local area network. Each device can share CAN resources. Therefore, the BMS can receive instructions from the charging device, vehicle controller, and other electronic control units (ECUs) via the CAN bus. Therefore, in the embodiments of the present application, receiving a target message based on a receiving identifier may refer to receiving the target message via the bus between the battery and the charging device.

[0061] In the embodiment of the present application, after the vehicle is connected to the charging device, in addition to communicating through the CAN bus, messages between the vehicle and the charging device can also be transmitted through wireless local area network, Bluetooth, cellular network, radio frequency, Ethernet, fiber optic communication, etc. Therefore, the present application can also receive the target message based on the receiving identifier, or receive the target message in any of the above communication methods.

[0062] Here, the battery can send a Battery Charging Link (BCL) message to the charging device, allowing the charging device to charge the battery based on the charging requirements contained in the BCL message. The charging requirement message includes data such as the vehicle's voltage requirement, current requirement, and charging mode. The BCL sent by the battery has a unique transmission identifier, namely the message ID (Identification) of the charging requirement message. The charging device can adjust the charging voltage and charging current based on the battery charging requirement message to ensure normal charging.

[0063] Since a third-party counterfeit node may construct a message with the same message ID as the charging demand message sent by the vehicle to tamper with the vehicle's charging parameters when launching an attack on the vehicle's charging interface, the BMS in the embodiment of the present application can receive a target message between the battery and the charging device with the same sending identifier as the charging demand message sent by the vehicle, and compare the received message with the charging demand message sent by the vehicle. If the difference in charging parameters is large, it is considered that a charging message has been tampered with by a third party and charging needs to be terminated.

[0064] In some embodiments, the BMS may include a CAN controller, which may include an acceptance filter. The acceptance filter can filter messages on the CAN bus to ensure that the BMS only receives and processes messages with the same identifier as the sender. The BMS may also include a message filtering device to filter messages transmitted via any feasible communication method other than the CAN bus to ensure that the BMS only receives messages with the same identifier as the sender.

[0065] In an embodiment of the present application, in order to receive the charging demand message between the battery and the charging device, the BMS can define a new receiving message in the software logic of the BMS, set the ID of the receiving message to be initially different from the sending identifier of the message sent by the battery, and set this message to be a dynamic message. When it is necessary to receive the message, the receiving identifier of the receiving message can be dynamically modified to the sending identifier of the charging demand message in the calling function of the message sending and receiving, so as to realize the simulation of the charging pile receiving the message with the sending identifier between the battery and the charging device.

[0066] In some embodiments, when the BMS simulates a charging device receiving a message corresponding to a receiving identifier between the battery and the charging device, the BMS may filter the messages between the battery and the charging device according to the receiving identifier, and use the messages between the battery and the charging device with the same message identifier as the sending identifier as the target messages that need to be processed by the BMS.

[0067] Here, if there is no message sent by a third party between the battery and the charging device, the target message can be the charging request message sent by the vehicle to the charging device; if there is a message sent by a third party between the battery and the charging device, the target message can be the charging request message sent by the vehicle to the charging device and the message sent by the third party.

[0068] In some embodiments, the BMS can filter the messages between the battery and the charging device in real time, or it can do so every 10 seconds. The embodiment of the present application can be set according to needs.

[0069] Step S103: Based on the target message and the charging demand message, perform an anomaly detection on the message transmitted between the battery and the charging device to obtain a message anomaly result; wherein the anomaly detection at least includes comparing the charging content in the target message and the charging demand message.

[0070] In an embodiment of the present application, performing anomaly detection on messages transmitted between the battery and the charging device may refer to comparing the received target message with the charging demand message sent by the vehicle to the charging device, and obtaining a message anomaly result based on the comparison result.

[0071] Here, comparing the target message with the charging demand message refers to comparing the message content in the target message (such as charging current and charging voltage) with the charging content (such as charging parameters) of the charging demand message. If the difference between any one item (such as charging current) is greater than a threshold value (for example, it can be a difference of 10%), it indicates that there is an abnormality, and the message abnormality result is that there is an abnormal message between the battery and the charging device; if the difference between the charging current and the charging voltage are both less than the threshold value, it means that even if there is an abnormal message sent by a third party, the charging device will not cause damage to the battery when charging the battery based on the message content of the message, so it indicates that there is no abnormality, and the message abnormality result is that there is no abnormal message between the battery and the charging device.

[0072] In this embodiment of the present application, if the BMS detects an abnormal message between the battery and the charging device, it can actively stop charging. If the BMS detects no abnormal message between the battery and the charging device, it can continue to send new charging request messages to the charging device, so that the charging device can adjust its output according to the battery condition.

[0073] In the embodiment of the present application, the battery management system can simulate the charging device to receive all messages with a sending identifier between the battery and the charging device, and compare these messages with the charging content of the charging demand message sent by the vehicle. According to the comparison result, it can be determined whether the target message is significantly different from the charging demand message, whether the target message is an abnormal request message, and then determine whether there are false charging instructions or data maliciously sent by a third party between the battery and the charging device. Real-time detection and active defense of charging messages between the battery and the charging device are achieved, which can effectively prevent external attacks during the charging process, thereby ensuring the safety and reliability of the electric vehicle charging process and improving the charging system's anti-attack capability.

[0074] In the embodiment of the present application, if a charging vehicle wants to simulate a charging pile to receive messages with a sending identifier between the battery and the charging device, it is necessary to configure two BCL messages, one for sending and one for receiving, and both IDs must be the same. However, since two messages with the same ID cannot be configured in the standardized (DBC, Database CAN) file that describes the CAN bus communication protocol, data conflicts and communication confusion will occur.

[0075] Therefore, in order to receive messages between the battery and the charging device, the BMS in the embodiment of the present application can define a new receiving message in the software logic of the BMS, set the ID of the receiving message to be initially different from the sending identifier of the message sent by the battery, and set this message to be a dynamic message. When it is necessary to receive a message, the receiving message ID can be dynamically set to the ID of the charging demand message in the calling function of the message sending and receiving, so as to realize the simulation of the charging pile receiving the message with the sending identifier between the battery and the charging device.

[0076] The embodiment of the present application adopts a dynamic ID solution, adding a new receiving message with an ID that is different from the ID of the BCL message sent by the vehicle. For example, if the ID of the BCL message sent by the vehicle is 0x181056F4, the ID of the newly configured receiving message can be set to 0x181156F4. This message is also set as a dynamic message. In this way, after receiving the charging start signal sent by the charging device, the receiving message ID can be dynamically adjusted to the BCL message ID in the message sending and receiving call function, so that the BMS can simulate the charging pile receiving the BCL message.

[0077] In an embodiment of the present application, the CAN controller of the battery management system may include a receiving filter, and the filter configuration function of the CAN controller can be used to add the adjusted received message ID to the receiving filter so that the receiving filter can receive messages with the same received message ID.

[0078] Therefore, the message anomaly detection method provided in the embodiment of the present application may further include step S1 and step S2:

[0079] Step S1: configuring a message receiving identifier for receiving messages in a receiving filter of a battery management system of a battery, wherein the message receiving identifier is different from the sending identifier.

[0080] Before the charging device charges the battery, a new receiving message can be added to the receiving filter. The new receiving message ID (i.e., message receiving identifier) is different from the ID of the BCL message sent by the vehicle. The message receiving identifier is added to the receiving filter.

[0081] Here, during configuration, the message receiving identifier can be set to a dynamic ID, and the message receiving identifier can be adjusted according to needs for different types of message reception by the BMS.

[0082] Here, the message receiving identifier may be an ID of a received message pre-set in a receiving filter of the BMS, and the message receiving identifier is different from the sending identifier.

[0083] Step S2: In response to the charging start signal, the message receiving identifier is adjusted to be the same as the sending identifier to obtain a receiving identifier.

[0084] In an embodiment of the present application, after the battery starts charging, the BMS can detect whether there is an abnormal charging message sent by a third-party device between the battery and the charging device. At this time, the message receiving identifier in the BMS can be adjusted to be the same as the sending identifier corresponding to the charging demand message sent by the battery to obtain a receiving identifier. For example, the receiving identifier is also adjusted to 0x181056F4.

[0085] Correspondingly, step S102 can be implemented through step S1021:

[0086] Step S1021: Receive a target message corresponding to the sending identifier of the charging demand message between the battery and the charging device through the message receiving identifier that is the same as the sending identifier.

[0087] After adjusting the received message identifier, the embodiment of the present application can receive a message with a sending identifier between the battery and the charging device, and determine the message as a target message.

[0088] The embodiment of the present application adjusts the message receiving identifier configured in the receiving filter to receive corresponding messages between the battery and the charging device, which can significantly reduce unnecessary message processing, thereby alleviating the processing volume, reducing the storage space and processing time occupied by unnecessary messages, improving the BMS processing efficiency, enhancing the real-time performance of BMS processing, and being able to quickly respond to abnormal messages to cut off the charging circuit, thereby reducing damage to the battery due to abnormal conditions.

[0089] In some embodiments, the messages between the battery and the charging device may be matched by the ID of the battery management system to receive the target message. Therefore, step S102 may also be implemented by steps S1022 to S1024:

[0090] Step S1022: Receive messages transmitted between the battery and the charging device.

[0091] Here, all messages between the battery and the charging device are shared with each node. The BMS can theoretically receive all messages between the battery and the charging device. Here, receiving messages transmitted between the battery and the charging device may refer to receiving all messages transmitted between the battery and the charging device.

[0092] Step S1023: Match the message identifier and the sending identifier of each message to obtain a matching result.

[0093] In some embodiments, the BMS does not need to process all messages. Therefore, the battery management system can filter the messages between the battery and the charging device to obtain the messages that need to be processed. Here, filtering can refer to matching the message identifier of each received message with the adjusted message receiving identifier that is the same as the sending identifier to obtain a matching result. Here, the matching results can be the same or different. The same means that the ID of the received message is the same as the ID of the charging demand message sent by the vehicle to the charging pile. The charging pile will receive the message and change the charging parameters according to the message content of the message. If the message is sent by a third party, it will cause the battery to overcharge.

[0094] Step S1024: In response to the matching result indicating that the message identifier is the same as the sending identifier, the message corresponding to the message identifier is determined as the target message.

[0095] In an embodiment of the present application, if the matching result indicates that the message identifier is the same as the updated reception identifier, it means that the ID of the received message is the same as the ID of the charging demand message sent by the vehicle to the charging pile. The charging pile will receive the message and change the charging parameters according to the message content of the message, determine the message as the target message, detect the target message, and determine whether there is an abnormal message.

[0096] In an embodiment of the present application, if the matching result indicates that the message identifier is different from the sending identifier, it means that the ID of the received message is different from the ID of the charging demand message sent by the vehicle to the charging pile. The charging pile will not receive the message and change the charging parameters. Therefore, the BMS does not need to receive the message and can discard the message.

[0097] In an embodiment of the present application, the charging management system can be set with multiple groups of different receiving IDs to process multiple tasks at the same time, and the received messages will also match with other receiving IDs. Here, the matching result after matching with the updated receiving identifier does not affect the matching results of other receiving IDs. For example, the updated receiving identifier 0x181156F4 in the battery management system, and the other receiving identifier is 0x182F6456. The identifier ID of the currently received message is 0x182F6456. The message and the updated receiving identifier will be discarded, but will be received when it matches with another receiving identifier.

[0098] In an embodiment of the present application, the adjusted update receiving identifier can be used to receive messages with this identifier between the battery and the charging device, so that the battery management system can receive messages sent between the battery and the charging device to the charging pile for adjusting the vehicle charging parameters, and can actively identify abnormal attack messages between the battery and the charging device, thereby improving the safety of the vehicle charging process.

[0099] In some embodiments, step S103 may be implemented through steps S1031 to S1032:

[0100] Step S1031: parse the target message to obtain target charging request data of the target message.

[0101] In some embodiments, after receiving the target message, the BMS may parse the target message to obtain target charging request data, that is, the charging current and charging voltage corresponding to the target message.

[0102] Step S1032: Compare the target charging request data with the charging request data of the charging demand message to obtain a message abnormality result.

[0103] Here, the charging demand message refers to the BCL message sent by the vehicle's BMS to the charging device. The message represents the vehicle's actual charging demand. The target charging request data is compared with the charging request data of the charging demand message to obtain a first comparison result. Based on the first comparison result, it can be determined whether the message content of the target charging request is abnormal.

[0104] In some embodiments, step S1032 may be implemented by step S11:

[0105] Step S11: In response to a difference between the target charging request data and the charging request data being greater than a first preset threshold, determining that the message abnormality result is an abnormal message between the battery and the charging device.

[0106] Here, the first preset threshold value can be 10% of the charging current or charging voltage in the charging request data, that is, when the difference between the current or voltage in the target charging request data and the current or voltage in the charging request data is greater than 10% of the current or voltage in the charging request data, it indicates that the message content in the target message will cause the charging pile to receive the message and charge based on the message, which will cause the battery to overcharge. That is, the target message may be an abnormal message sent by a third-party device for attack, so the message abnormality result is that there is an abnormal message between the battery and the charging device.

[0107] At this point, the BMS can make a protection strategy, such as stopping charging to protect the vehicle battery.

[0108] Correspondingly, the message anomaly detection method provided in the embodiment of the present application may further include step S21:

[0109] Step S21: In response to the message abnormality result indicating that an abnormal message exists between the battery and the charging device, a message for suspending charging is sent to the charging device; the message for suspending charging is used to instruct the charging device to stop charging the battery.

[0110] In an embodiment of the present application, if the message abnormality result indicates that there is an abnormal message between the battery and the charging device, the BMS can send a stop charging message to the charging device to instruct the charging device to stop charging the battery. When the charging device receives the stop charging message, it stops charging the vehicle.

[0111] In some embodiments, the BMS can also control the vehicle's switch to disconnect the charging circuit to improve the safety and reliability of the charging process.

[0112] The embodiment of the present application can determine whether there are abnormal messages between the battery and the charging device based on the difference between the target message and the charging demand message, and can timely discover abnormal situations and formulate protection strategies, thereby reducing the probability of battery damage due to overcharging, improving battery life, and improving the safety, stability and reliability of the charging system.

[0113] Figure 2 This is an optional process diagram of the message anomaly detection method provided in the embodiment of the application. Figure 2 ,like Figure 2 As shown, the message anomaly detection method provided in the embodiment of the present application can be implemented through step S201. It should be noted that: Figure 2 The message anomaly detection method in the present invention is described by taking a charging device as an example of an execution subject.

[0114] Step S201: In response to connection with the battery, sending a charging start signal to the battery, so that the battery sends a charging demand message to the charging device in response to the charging start signal; based on the receiving identifier, receiving a target message corresponding to the receiving identifier; the receiving identifier is the same as the sending identifier of the charging demand message; based on the target message and the charging demand message, performing an anomaly detection on the message transmitted between the battery and the charging device to obtain a message anomaly result; wherein the anomaly detection at least includes comparing the charging content in the target message and the charging demand message.

[0115] In an embodiment of the present application, after the physical connection between the charging device and the battery is completed, a charging start signal can be sent to the battery management system of the battery, indicating that the charging device has started charging the battery and the battery has entered the charging stage. The charging requirement message sent by the battery is obtained and the battery is charged according to the charging requirement in the charging requirement message.

[0116] Before sending the charging start signal, the charging device can first provide a low-voltage power supply to the vehicle's BMS to enable the BMS to work normally. The charging device then establishes a communication link and performs identity authentication to ensure that both parties can safely perform subsequent charging operations. After the charging handshake phase is completed, the vehicle and charging device enter the charging parameter configuration phase to negotiate the specific parameters of the battery charging.

[0117] After receiving the charging start signal sent by the charging device, the battery's BMS can send a charging requirement message to the charging device, receive a target message corresponding to the sending identifier of the charging requirement message, and based on the target message and the charging requirement message, perform an anomaly detection on the message transmitted between the battery and the charging device to obtain a message anomaly result.

[0118] In the embodiment of the present application, in addition to the battery management system being able to actively detect abnormal messages between the battery and the charging device, the charging device can also determine whether there are abnormal messages between the battery and the charging device based on the received messages. Figure 3 This is an optional process diagram of the message anomaly detection method provided in the embodiment of the application. Figure 3 ,like Figure 3 As shown, the message anomaly detection method provided in the embodiment of the present application may further include steps S301 to S303:

[0119] Step S301: Receive a target message with a sending identifier between a battery and a charging device, and put the target message into a receiving buffer of the charging device.

[0120] In an embodiment of the present application, the charging device can receive a target message with a sending identifier between the battery and the charging device. The target message can be sent by the vehicle's BMS or by a third-party device simulating a vehicle. The message identifier of the third-party message sent by the third-party device for tampering with the vehicle's charging parameters is the same as the sending identifier of the charging demand message sent by the vehicle, so the charging device will also obtain the message sent by the third party and adjust the current and voltage for charging the vehicle based on the message.

[0121] In the embodiment of the present application, after receiving the target message, the charging device may place the target message into a receiving buffer of the charging device.

[0122] The receive buffer can be a random access memory (RAM) or a first-in first-out memory (FIFO).

[0123] Step S302: In response to receiving a new target message, overwrite the target message in the receiving buffer to obtain a corresponding message set in the receiving buffer.

[0124] In an embodiment of the present application, a DC charging pile needs to frequently receive and process BCL messages during the charging process. These messages contain information about the battery management system's requirements for charging voltage and current. Storing all BCL messages could occupy a significant amount of storage resources. To reduce storage overhead, an embodiment of the present application sets a buffering threshold for the charging device's receive buffer, for example, three BCL messages. The storage space of the receive buffer can be greater than or equal to the buffer space corresponding to three BCL messages.

[0125] If the number of target messages received by the charging device is greater than 3, the old target message may be overwritten by the new target message to obtain a set (ie, 3) of messages in the receiving buffer.

[0126] In an embodiment of the present application, the overwriting can be based on the reception time of the target message, that is, the new target message overwrites the target message with the earliest reception time in the receiving cache. For example, the charging vehicle starts to send a BCL message request to the charging device. When the charging device receives the first frame of the target message, it records and stores the message content. When the second and third frames are received, they are also recorded and stored in the receiving cache. When the fourth frame of the message is received, the first frame of the message is overwritten by the fourth frame of the message, and the message content stored in the receiving cache is the message content of the second, third, and fourth frames. When the fifth frame of the BCL message is received, the message content stored in the receiving cache is the message content of the third, fourth, and fifth frames. Therefore, in a single charging cycle, the charging device always records and stores the content of the last 3 frames of BCL messages.

[0127] In an embodiment of the present application, the overwriting can also be that the new target message randomly overwrites the target message in the receiving cache. If the cache threshold is 3, the target message in the receiving cache is replaced once for three consecutive times. For example, the charging vehicle starts to send a BCL message request to the charging device. When the charging device receives the first frame of the BCL message, it records and stores the message content. When the second and third frames are received, they are also recorded and stored in the receiving cache. When the fourth frame of the message is received, the second frame of the message is overwritten by the fourth frame of the message, and the message content stored in the receiving cache is the message content of the first, fourth and third frames. When the fifth frame of the BCL message is received, the third frame of the message is overwritten, and the message content stored in the receiving cache is the message content of the first, fourth and fifth frames. When the sixth frame of the BCL message is received, the third frame of the message is overwritten, and the message content stored in the receiving cache is the message content of the sixth, fourth and fifth frames, so that even if the message is not received three times, the receiving cache can contain the latest three frames of messages.

[0128] The embodiments of the present application do not impose any specific restrictions on the coverage method.

[0129] Step S303: Compare the contents of the target message in the message set to obtain a message abnormality result.

[0130] In an embodiment of the present application, a group of message sets may contain a preset threshold number of target messages, and the contents of any two target messages may be compared. If a jump occurs, it indicates that the message abnormality result is that there is an abnormal message in this group of message sets, that is, there is an abnormal message between the battery and the charging device.

[0131] In an embodiment of the present application, the charging device forms a message set by receiving and recording the target messages between the battery and the charging device, and based on the contents of multiple groups of message sets, it can identify whether the content of the target message transmitted between the battery and the charging device is abnormal, thereby improving the charging safety of the charging vehicle.

[0132] In some embodiments, step S302 may be implemented by steps S3021 and S3022:

[0133] Step S3021 : In response to the number of target messages in the receiving buffer being equal to the buffer threshold of the receiving buffer, a message to be covered having the earliest receiving time is determined based on the receiving time of each target message in the receiving buffer.

[0134] In an embodiment of the present application, if the number of target messages in the receiving buffer is equal to the cache threshold of the receiving buffer, it means that no new target message can be stored in the receiving buffer. At this time, the target message with the earliest receiving time in the receiving buffer can be overwritten by the new target message. Therefore, when the charging device receives a new target message, the target message with the earliest receiving time can be determined in the receiving buffer and the target message can be determined as the message to be overwritten.

[0135] Step S3022: Overwrite the message to be overwritten with the new target message to obtain a message set.

[0136] In the embodiment of the present application, the to-be-covered message can be overwritten by the newly received target message to obtain a group of message sets.

[0137] The embodiment of the present application overwrites the earliest received message in the receiving cache with a new target message, which not only reduces the waste of cache space, but also ensures that the latest charging requirements are always stored in the receiving cache.

[0138] In some embodiments, the message anomaly detection method provided in the embodiments of the present application further includes step S31:

[0139] Step S31: Determine multiple groups of message sets based on multiple new target messages continuously received.

[0140] In some embodiments, a vehicle sends a charging request message to a charging device at regular intervals (e.g., 50 milliseconds). Each time the charging device receives a charging request message, it overwrites a target message in its receive buffer, resulting in a new message set. Therefore, after receiving multiple charging request messages, multiple message sets may be generated.

[0141] Correspondingly, step S303 can also be implemented through steps S3031 and S3032:

[0142] Step S3031: Compare the charging request data of each target message in each message set to obtain a comparison result.

[0143] In an embodiment of the present application, the charging device can compare the charging current and charging voltage required by different target messages based on multiple target messages in each group of message sets, and can determine whether a jump occurs between different messages. If there is a jump in several consecutive groups of message sets, it may indicate that a third-party device is attacking the charging process of the vehicle, and the message abnormality result may be the existence of a message abnormality.

[0144] In an embodiment of the present application, the charging device receives and records multiple sets of target messages between the battery and the charging device, and based on the contents of the multiple sets of target messages, can identify whether the content of the charging demand message transmitted between the battery and the charging device is abnormal, thereby improving the charging safety of the charging vehicle.

[0145] In the embodiment of the present application, the charging request data of each target message in each message set is compared, that is, the charging request data of any two target messages are compared to obtain a comparison result.

[0146] Step S3032: In response to the comparison result indicating that there is a jump in the charging request data in a preset number of consecutive groups of message sets, it is determined that there are abnormal messages between the battery and the charging device; the jump indicates that the difference between the charging request data of any two charging demand messages in the message set is greater than a second preset threshold.

[0147] In an embodiment of the present application, the preset number may be 5. If the comparison result shows that there are jumps in the charging request data in 5 consecutive groups of message sets, it indicates that there are abnormal messages sent by a third-party device.

[0148] The second preset threshold value may be 10% of the minimum charging current or the minimum charging voltage in the charging request data. A difference between the charging request data of any two charging requirement messages that is greater than the second preset threshold value may refer to a difference between the charging currents of any two charging requirement messages, or a difference between the charging voltages that is greater than the minimum charging current and the minimum charging voltage in the charging request data in the group of charging requirement messages, indicating that there is a jump in the group of charging requirement messages, which can determine that there is an abnormal message between the battery and the charging device.

[0149] The embodiment of the present application identifies and judges the message content based on a set of multiple consecutive message sets received, and can promptly determine whether there is external interference or abnormal messages between the battery and the charging device, thereby improving the charging safety of the vehicle.

[0150] In some embodiments, the message anomaly detection method provided in the embodiments of the present application may further include steps S41 to S43:

[0151] Step S41: In response to the message abnormality result indicating the presence of an abnormal message between the battery and the charging device, target charging request data that meets a charging condition is determined in the charging request data of the target message currently received and buffered; the charging condition is used to represent the minimum value of the charging request data in the current receiving buffer.

[0152] In an embodiment of the present application, the charging condition is used to characterize the minimum value of the charging request data currently received in the cache. For example, there are three charging currents in three target messages, and the charging condition is satisfied when the minimum value among the three charging currents is met.

[0153] If the message abnormality result indicates that there is an abnormal message between the battery and the charging device, the minimum charging current or charging voltage among the charging request data of the target message currently received and buffered may be determined as the target charging request data.

[0154] Step S42: Charge the battery based on the target charging request data until the message abnormality result indicates that there is no abnormal message between the battery and the charging device.

[0155] In the presence of an abnormal message, the charging device uses the smallest charging current or charging voltage in the current receiving buffer to charge the battery until there is no jump in the charging request data in five consecutive groups of message sets, indicating that the message abnormality result indicates that there are no abnormal messages between the battery and the charging device. At this time, the battery is charged with the charging request data of the latest received charging demand message.

[0156] Step S43: In response to the message abnormality result indicating that there is no abnormal message between the battery and the charging device, the battery is charged based on the charging request data of the newly received charging demand message.

[0157] In an embodiment of the present application, if there is no jump in the charging request data in five consecutive message sets, it means that there may be no third-party attack on the current bus. At this time, the battery is charged with the charging request data of the latest received charging demand message.

[0158] The embodiment of the present application determines whether there is an abnormality between the battery and the charging device by identifying the content of the charging demand message. If abnormal message content occurs, the output safety of the charging device itself is ensured by only responding to a smaller request value, and the charging safety of the charging vehicle can also be improved.

[0159] The following describes an exemplary application of the embodiments of the present application in a practical application scenario.

[0160] Without changing the existing charging protocol, during the conventional DC charging process of electric vehicles, if a third party appears on the bus and uses an external device to simulate a charging vehicle to send a charging request message (i.e., a charging demand message) to the charging pile (i.e., a charging device), and the message deviates greatly from the normal charging request data of the charging vehicle, the charging vehicle can imitate the charging pile to receive the charging request message through the dynamic ID strategy of the received message (i.e., changing the message attribute to a form with variable message ID in the Davinci configuration, and dynamically changing the message ID according to actual needs in the calling function of sending and receiving messages), identify the abnormality of the received message, and actively terminate charging.

[0161] The dynamic ID strategy means that after configuring Davinci via DBC to generate the configuration code, all message IDs are fixed. Dynamic messaging, on the other hand, changes the message attributes in the Davinci configuration to a variable message ID based on the DBC configuration. This allows the message ID to be dynamically set as needed in the message sending and receiving call functions, allowing the charging pile to simultaneously send interactive messages and simulate the charging pile receiving charging request messages.

[0162] The DBC (Database CAN) file is a data file used to describe CAN communication information between all electronic control unit nodes on a CAN network. It contains the protocol data of the CAN bus and its specific meaning. The DBC file specifies the communication and control process of the vehicle's electronic systems by describing the signal transmission and processing methods between the vehicle's electronic controllers, as well as the parameter configuration of the electronic control units. For example, during driving, parameters such as vehicle speed, RPM, fuel level, and water temperature must be transmitted to the corresponding ECUs in a timely manner. These parameters are then used to implement specific operations. All of this is standardized by the DBC file.

[0163] Davinci can simplify and accelerate the configuration process of the Automotive Open System Architecture (AUTOSAR) system. Through Davinci, you can create and edit ARXML files, define and configure various AUTOSAR components to achieve automatic verification and compliance checks, and improve the quality and reliability of the system.

[0164] Here, taking the BCL message as an example, as a charging vehicle, the BCL message is a sending message, and the message ID can be 0x181056F4; on the charging pile side, the BCL message is a receiving message, and the message ID can also be 0x181056F4. If the charging vehicle wants to simulate the charging pile receiving the BCL message, it must configure two BCL messages, one for sending and one for receiving, and the IDs need to be the same. However, it is not possible to configure two messages with the same ID in the DBC. Therefore, a new receiving message can be added, and the ID of the new receiving message is different from the ID of the BCL, and this new receiving message is set as a dynamic message. In this way, the ID of the new receiving message can be dynamically set to the ID of the BCL message in the message sending and receiving call function, so that the charging pile can simulate receiving the BCL message.

[0165] Figure 4 FIG. 1 is a flow chart of a battery management system for implementing a charging request abnormality protection strategy according to an embodiment of the present application. Figure 4 As shown, the charging request abnormality protection strategy can be implemented through steps S401 to S408:

[0166] Step S401: The vehicle is physically connected to the charging pile.

[0167] Here, the completion of the physical connection between the vehicle and the charging pile may refer to the vehicle being connected to the charging gun of the charging pile.

[0168] Step S402: The charging pile performs low-voltage auxiliary powering on the vehicle.

[0169] Here, low-voltage auxiliary power-up is the initial stage of the charging process. The charging pile provides low-voltage power to the vehicle's battery management system, enabling the BMS to work normally.

[0170] Step S403: The charging pile and the vehicle perform charging handshake identification.

[0171] Charging handshake identification is the process of establishing a communication link and performing identity verification between the vehicle and the charging pile to ensure that both parties can safely perform subsequent charging operations.

[0172] Step S404: The charging pile and the vehicle configure charging parameters.

[0173] After the vehicle and charging pile complete the charging handshake phase, the vehicle and charging pile enter the charging parameter configuration phase to negotiate specific charging parameters. The vehicle's BMS can send battery parameters such as the maximum allowable charging voltage and maximum charging current to the charging pile, and the charging pile sends its maximum output capacity to the BMS. The vehicle and charging pile then negotiate the final charging parameters based on these parameters to ensure a safe and efficient charging process.

[0174] Step S405: The vehicle sends a charging demand message to the charging pile.

[0175] After configuring the charging parameters, the vehicle sends a charging request message to the charging station. This message includes the required charging voltage and current. The charging station adjusts its output based on these required values to ensure the charging process proceeds smoothly.

[0176] Step S406: Use the dynamic ID strategy to simulate the charging pile receiving the charging request message.

[0177] In the embodiment of the present application, the BMS uses a dynamic ID strategy to simulate the charging pile to synchronously receive the charging request message on the CAN bus.

[0178] Step S407: Determine whether the request content in the received charging request message deviates from the original request by more than 10%.

[0179] During the charging process, if the BMS recognizes that the request content in the received charging request message deviates by more than 10% from the request content issued by itself, it determines that the bus charging request is abnormal and executes step S408 to actively terminate charging.

[0180] If the deviation does not exceed 10%, it is considered that the message is normal, and step S405 is executed, and the vehicle BMS sends a charging demand message to the charging pile again.

[0181] Step S408: The charging management system actively terminates charging.

[0182] In the embodiment of the present application, the BMS does not need to modify the existing charging protocol. It simulates the charging pile receiving charging messages through the dynamic ID strategy of the charging vehicle receiving messages. It can actively identify abnormal message content and actively terminate charging, preventing the charging vehicle from overcharging the battery, greatly improving the safety of charging. At the same time, the BMS uses the abnormal message request identification strategy to screen and compare the abnormal message content received by the simulated charging pile with the charging request of the charging vehicle itself. If an abnormal request is identified, active protection is performed and charging is terminated, improving the interaction safety between the vehicle and the charging pile, and also improving the safety of battery charging.

[0183] During conventional DC charging, if a third party uses an external device to simulate an electric vehicle and sends a charging request message, the charging station can, without changing the existing charging protocol, proactively identify abnormal charging requests by sliding and recording the contents of the last three frames of BCL messages, and proactively protect against abnormal messages. If an abnormal request occurs, the charging station can only respond with a smaller charge request value until the abnormality disappears, at which point it will resume normal response, preventing overcharging of the charging vehicle.

[0184] Figure 5 This is a flow chart of the charging pile charging request abnormality protection strategy provided by the embodiment of the present application, such as Figure 5 As shown, the charging request abnormality protection strategy can be implemented through steps S501 to S506:

[0185] Step S501: Receive a charging demand message from a charging vehicle.

[0186] In the embodiment of the present application, after the electric vehicle plug enters the conventional DC charging process, the DC charging pile receives a charging request message through the CAN bus and outputs current and voltage according to the content of the charging request message.

[0187] In an embodiment of the present application, if the charging pile does not receive a charging demand message from the charging vehicle within 30 seconds, charging of the vehicle is terminated.

[0188] Step S502: Slide and record the message contents of the last three frames of charging requirement messages.

[0189] After receiving a charging request message from a vehicle, a DC charging station only records and stores the last three frames of the message. For example, when a DC charging station receives a BCL message, after inserting the electric vehicle into the DC charging gun, it swipes its card to begin the charging process. After a handshake and identification interaction with the DC charging station, the charging process begins. The charging vehicle begins sending a BCL message request to the DC charging station. Upon receiving the first BCL message, the DC charging station records and stores the message content. It also records and stores the BCL message content upon receiving the second and third frames. Upon receiving the fourth frame, it records and stores the message content of the second, third, and fourth frames. Upon receiving the fifth frame, it records and stores the message content of the third, fourth, and fifth frames. This continues in this manner. Throughout a single charging cycle, the DC charging station always records and stores the last three BCL message frames.

[0190] Step S503: Determine whether the requested current or voltage jump occurs five times consecutively.

[0191] Here, the DC charging pile slides and records the contents of the latest three frames of BCL messages. If the requested current or voltage jumps within the range of large-small-large or small-large-small five times in a row (i.e., the large request value in the three frames of BCL message content exceeds 10% of the small request value), it is determined that the bus charging request is abnormal and step S504 is executed. Otherwise, step S505 is executed.

[0192] Step S504: If a request exception occurs, only the minimum value in the last three charging requirement messages is responded to.

[0193] In this embodiment of the present application, if a request anomaly occurs, the charging device can respond only to the minimum value in the last three charging request messages and charge the vehicle based on this minimum value. Once the anomaly disappears, the charging station outputs current and voltage based on the content of the last charging request message. This protection strategy reduces the risk of overcharging for the vehicle and improves charging safety for both the vehicle and the charging station.

[0194] Step S505: normal response, outputting current and voltage according to the message content of the last frame of charging requirement message.

[0195] In some embodiments, when the charging pile determines that there is no abnormality in the bus charging request, the charging pile outputs the current and voltage according to the message content of the last frame of the charging requirement message.

[0196] Step S506: Determine whether the abnormality disappears.

[0197] When the charging pile is charging the vehicle based on the minimum value, the charging pile is still continuously receiving the charging demand message sent by the battery BMS. The charging pile continues to determine whether there are five consecutive requested current or voltage jumps. If not, the abnormality disappears and step S505 can be executed; otherwise, step S504 is continued.

[0198] In the embodiment of the present application, during conventional DC charging of electric vehicles, the DC charging pile exchanges messages with the vehicle battery via the CAN bus, records the content of the charging request message sent by the vehicle, and identifies whether the charging request message content is abnormal. If an abnormal request is identified, active protection is implemented to prevent overcharging of the charging vehicle, thereby improving the charging safety of the charging vehicle. At the same time, by identifying the content of the charging request message, if abnormal message content is found, the charging pile only responds to a smaller request value, ensuring the output safety of the charging pile itself and also improving the charging safety of the charging vehicle.

[0199] Figure 6 This is a schematic diagram of the structure of a message anomaly detection device provided in an embodiment of the present application. Figure 1 ,like Figure 6As shown, the message anomaly detection device 600 includes at least a first sending module 601, a receiving module 602 and a detection module 603, wherein:

[0200] The first sending module 601 is used to send a charging demand message to the charging device in response to a charging start signal sent by the charging device; the receiving module 602 is used to receive a target message based on a receiving identifier; the receiving identifier is the same as the sending identifier of the charging demand message; the detection module 603 is used to perform anomaly detection on the message transmitted between the battery and the charging device based on the target message and the charging demand message, and obtain a message anomaly result; wherein the anomaly detection at least includes comparing the charging content in the target message and the charging demand message.

[0201] In some embodiments, the message anomaly detection device also includes: a configuration module for configuring a message receiving identifier for the battery management system to receive messages in a receiving filter of the battery management system of the battery, wherein the message receiving identifier is different from the sending identifier; an adjustment module for adjusting the message receiving identifier to be the same as the sending identifier in response to the charging start signal to obtain a receiving identifier.

[0202] In some embodiments, the receiving module 602 is further used to receive messages transmitted between the battery and the charging device; match the message identifier of each message with the sending identifier to obtain a matching result; in response to the matching result indicating that the message identifier is the same as the sending identifier, determine the message corresponding to the message identifier as the target message.

[0203] In some embodiments, the detection module 603 is further configured to parse the target message to obtain target charging request data of the target message; and compare the target charging request data with the charging request data of the charging demand message to obtain a message abnormality result.

[0204] In some embodiments, the detection module 603 is also used to determine that the message abnormality result is an abnormal message between the battery and the charging device in response to the difference between the target charging request data and the charging request data being greater than a first preset threshold; correspondingly, the message abnormality detection device also includes: a first sending module, used to send a charging suspension message to the charging device in response to the message abnormality result being an abnormal message between the battery and the charging device; the charging suspension message is used to instruct the charging device to stop charging the battery.

[0205] Figure 7 This is a schematic diagram of the structure of a message anomaly detection device provided in an embodiment of the present application. Figure 2 ,like Figure 7 As shown, the message anomaly detection device 70 includes at least a second sending module 701, wherein:

[0206] The second sending module 701 is used to send a charging start signal to the battery in response to being connected to the battery, so that the battery sends a charging demand message to the charging device in response to the charging start signal; receive a target message based on a receiving identifier; the receiving identifier is the same as the sending identifier of the charging demand message; based on the target message and the charging demand message, perform anomaly detection on the message transmitted between the battery and the charging device to obtain a message anomaly result; wherein the anomaly detection at least includes comparing the charging content in the target message and the charging demand message.

[0207] In some embodiments, the message anomaly detection device also includes: the message anomaly detection device also includes: a first receiving module, used to receive a target message with a sending identifier between the battery and the charging device, and place the target message into the receiving buffer of the charging device; an overwriting module, used to overwrite the target message in the receiving buffer in response to receiving a new target message, and obtain a corresponding message set in the receiving buffer; a comparison module, used to compare the content of the target message in the message set to obtain a message anomaly result.

[0208] In some embodiments, the overwriting module is also used to determine the message to be overwritten with the earliest reception time based on the reception time of each target message in the reception buffer in response to the number of target messages in the reception buffer being equal to the cache threshold of the reception buffer; and to overwrite the message to be overwritten with the new target message to obtain a message set.

[0209] In some embodiments, the message anomaly detection device also includes: a first determination module, used to determine multiple groups of message sets based on multiple new target messages continuously received; correspondingly, a comparison module, also used to compare the charging request data of each target message in each group of message sets to obtain a comparison result; in response to the comparison result indicating that there is a jump in the charging request data in a preset number of consecutive groups of message sets, it is determined that there are abnormal messages between the battery and the charging device; the jump indicates that the difference between the charging request data of any two charging demand messages in the message set is greater than a second preset threshold.

[0210] In some embodiments, the message anomaly detection device also includes: a second determination module, which is used to determine the target charging request data that meets the charging condition in the charging request data of the target message currently received in the buffer in response to the message anomaly result indicating that there is an abnormal message between the battery and the charging device; the charging condition is used to characterize the minimum value of the charging request data in the current receiving buffer; a charging module, which is used to charge the battery based on the target charging request data until the message anomaly result indicates that there is no abnormal message between the battery and the charging device; the charging module is also used to charge the battery based on the charging request data of the received new target message in response to the message anomaly result indicating that there is no abnormal message between the battery and the charging device.

[0211] The description of the above device embodiment is similar to the description of the above method embodiment and has similar beneficial effects as the method embodiment. In some embodiments, the functions or modules included in the device provided in the embodiments of the present application can be used to perform the methods described in the above method embodiments. For technical details not disclosed in the device embodiments of the present application, please refer to the description of the method embodiments of the present application for understanding.

[0212] It should be noted that in the embodiments of the present application, if the above-mentioned message anomaly detection method is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a software product. The software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the methods of each embodiment of the present application. The aforementioned storage medium includes various media that can store program code, such as a USB flash drive, a mobile hard drive, a read-only memory (ROM), a magnetic disk, or an optical disk. In this way, the embodiments of the present application are not limited to any specific hardware, software, or firmware, or any combination of hardware, software, and firmware.

[0213] Figure 8 This is a hardware entity diagram of a message anomaly detection device in an embodiment of the present application, such as Figure 8 As shown, the hardware entity of the message anomaly detection device 800 includes: a processor 801, a communication interface 802 and a memory 803, wherein:

[0214] Processor 801 generally controls the overall operation of message anomaly detection device 800, which may implement the message anomaly detection method for a battery provided in an embodiment of the present application. Processor 801 may be a processor of a battery management system (BMS) or charging device within the battery. The processor may be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0215] The communication interface 802 enables the computer device to communicate with other terminals or servers through a network.

[0216] Memory 803 is configured to store instructions and applications executable by processor 801. It can also cache data (e.g., image data, audio data, voice communication data, and video communication data) to be processed or processed by processor 801 and various modules in message anomaly detection device 800. This can be implemented using flash memory (FLASH) or random access memory (RAM). Data can be transmitted between processor 801, communication interface 802, and memory 803 via bus 804.

[0217] Memory 803 can be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state memory, hard disk drives, optical disk drives, and the like. Memory 803 may optionally include one or more storage devices physically remote from processor 801. Memory 803 may include volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory may be read-only memory (ROM), and volatile memory may be random access memory (RAM). The memory 803 described in the embodiments of this application is intended to include any suitable type of memory.

[0218] The present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements some or all of the steps in the above method. The computer-readable storage medium may be transient or non-transient.

[0219] An embodiment of the present application provides a computer program, including computer-readable code. When the computer-readable code runs in a computer device, a processor in the computer device executes some or all of the steps for implementing the above method.

[0220] Embodiments of the present application provide a computer program product comprising a non-transitory computer-readable storage medium storing a computer program. When the computer program is read and executed by a computer, it implements some or all of the steps of the above-described method. The computer program product may be implemented in hardware, software, or a combination thereof. In some embodiments, the computer program product is embodied as a computer storage medium. In other embodiments, the computer program product is embodied as a software product, such as a software development kit (SDK).

[0221] It should be noted that the descriptions of the various embodiments above tend to emphasize the differences between the various embodiments, and their similarities or similarities can be referenced to each other. The descriptions of the above device, storage medium, computer program, and computer program product embodiments are similar to the descriptions of the above method embodiments and have similar beneficial effects as the method embodiments. For technical details not disclosed in the embodiments of the device, storage medium, computer program, and computer program product of this application, please refer to the description of the method embodiments of this application for understanding.

[0222] In order to implement the message anomaly detection method provided in the embodiment of the present application, the embodiment of the present application can also provide a message anomaly detection system, which includes a charging device and a battery, wherein the charging device is used to connect to the battery and send a charging start signal to the battery; the battery is used to send a charging demand message to the charging device based on the charging start signal sent by the charging device; the battery is also used to receive the target message based on the receiving identifier; the receiving identifier is the same as the sending identifier of the charging demand message; the battery is also used to perform anomaly detection on the message transmitted between the battery and the charging device based on the target message and the charging demand message to obtain a message anomaly result.

[0223] It should be noted that the description of the system embodiment of the present application is similar to the description of the above-mentioned method embodiment and has similar beneficial effects as the method embodiment, so it will not be repeated. For technical details not disclosed in the system embodiment, please refer to the description of the method embodiment of the present application for understanding.

[0224] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned steps / processes does not mean the order of execution, and the execution order of each step / process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The above-mentioned serial numbers of the embodiments of the present application are for description only and do not represent the advantages and disadvantages of the embodiments.

[0225] This application uses descriptions of directions or positional relationships such as "up", "down", "top", "bottom", "front", "back", "inside" and "outside" to facilitate the description of this application, and does not indicate or imply that the device referred to must have a specific direction, be constructed and operated in a specific direction. Therefore, it should not be understood as limiting the scope of protection of this application.

[0226] It should also be noted that, in the description of this application, unless otherwise specified or limited, the terms "installed," "connected," and "connected" should be understood broadly. For example, they can refer to fixed connections, detachable connections, or integral connections; they can refer to direct connections or indirect connections through an intermediary. Those skilled in the art will understand the specific meanings of these terms in this application based on the specific circumstances.

[0227] It should be noted that, in this application, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

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

[0229] The units described above as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units; they may be located in one place or distributed across multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, the functional units in the various embodiments of the present application may all be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0230] The above are merely examples of the present application and are not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, and improvements made within the spirit and scope of the present application are included in the scope of protection of the present application.

Claims

1. A message anomaly detection method, characterized in that: The message anomaly detection method includes: A message receiving identifier for receiving messages by the battery management system is configured in a receiving filter of the battery management system, wherein the message receiving identifier is different from a sending identifier for sending charging requirement messages by the battery management system to the charging device; In response to a charging start signal sent by a charging device, sending a charging request message to the charging device; In response to the charging start signal, adjusting the message receiving identifier to be the same as the sending identifier to obtain a receiving identifier; receiving a target message based on the receiving identifier; wherein the receiving identifier is the same as the sending identifier of the charging demand message; Based on the target message and the charging requirement message, an anomaly detection is performed on the message transmitted between the battery and the charging device to obtain a message anomaly result; wherein the anomaly detection at least includes comparing the charging content in the target message and the charging requirement message.

2. The message anomaly detection method according to claim 1, characterized in that: Receiving a target message based on the receiving identifier includes: receiving a message transmitted between the battery and the charging device; Matching the message identifier of each message with the sending identifier to obtain a matching result; In response to the matching result indicating that the message identifier is the same as the sending identifier, the message corresponding to the message identifier is determined as the target message.

3. The message anomaly detection method according to claim 1, characterized in that: The performing anomaly detection on the message transmitted between the battery and the charging device based on the target message and the charging demand message to obtain a message anomaly result includes: Parsing the target message to obtain target charging request data of the target message; The target charging request data is compared with the charging request data of the charging demand message to obtain the message abnormality result.

4. The message anomaly detection method according to claim 3, characterized in that: The comparing the target charging request data with the charging request data of the charging demand message to obtain the message abnormality result includes: In response to a difference between the target charging request data and the charging request data being greater than a first preset threshold, determining that the message abnormality result is an abnormal message between the battery and the charging device; Correspondingly, the message anomaly detection method further includes: In response to the message abnormality result indicating that an abnormal message exists between the battery and the charging device, a charge suspension message is sent to the charging device; the charge suspension message is used to instruct the charging device to stop charging the battery.

5. A message anomaly detection method, characterized in that: The message anomaly detection method includes: In response to connection with a battery, a charging start signal is sent to the battery, so that the battery configures a message receiving identifier of the battery management system for receiving messages in the receiving filter of the battery management system, and the message receiving identifier is different from the sending identifier of the charging requirement message sent by the battery management system to the charging device; in response to the charging start signal, a charging requirement message is sent to the charging device; in response to the charging start signal, the message receiving identifier is adjusted to be the same as the sending identifier to obtain a receiving identifier; a target message is received based on the receiving identifier; the receiving identifier is the same as the sending identifier of the charging requirement message; based on the target message and the charging requirement message, an anomaly detection is performed on the message transmitted between the battery and the charging device to obtain a message anomaly result; wherein, the anomaly detection at least includes comparing the charging content in the target message and the charging requirement message.

6. The message anomaly detection method according to claim 5, characterized in that: The message anomaly detection method further includes: receiving a target message with the sending identifier between the battery and the charging device, and placing the target message into a receiving buffer of the charging device; In response to receiving a new target message, overwriting the target message in the receiving buffer to obtain a corresponding message set in the receiving buffer; Compare the contents of the target message in the message set to obtain the message anomaly result.

7. The message anomaly detection method according to claim 6, characterized in that: The overwriting of the target message in the receiving buffer to obtain a corresponding message set of the receiving buffer includes: In response to the number of target messages in the receiving buffer being equal to a buffer threshold of the receiving buffer, determining a message to be covered having the earliest receiving time based on a receiving time of each target message in the receiving buffer; The message to be covered is covered by the new target message to obtain the message set.

8. The message anomaly detection method according to claim 6 or 7, characterized in that: The message anomaly detection method further includes: Determine multiple groups of message sets based on multiple new target messages continuously received; Correspondingly, the comparing the contents of the target message in the message set to obtain the message abnormality result includes: Comparing the charging request data of each target message in each message set to obtain a comparison result; In response to the comparison result indicating that there is a jump in the charging request data in a set of consecutive preset number of groups of messages, it is determined that there is an abnormal message between the battery and the charging device; the jump indicates that the difference between the charging request data of any two charging demand messages in the message set is greater than a second preset threshold.

9. The message anomaly detection method according to claim 6 or 7, characterized in that: The message anomaly detection method further includes: In response to the message abnormality result indicating that an abnormal message exists between the battery and the charging device, target charging request data satisfying a charging condition is determined from charging request data of a target message currently received and buffered; the charging condition is used to indicate a minimum value of the charging request data in the currently received buffer; charging the battery based on the target charging request data until the message abnormality result indicates that no abnormal message exists between the battery and the charging device; In response to the message abnormality result indicating that no abnormal message exists between the battery and the charging device, the battery is charged based on the charging request data of the received new target message.

10. A message anomaly detection device, characterized in that: The message anomaly detection device includes: a configuration module, configured to configure a message receiving identifier for receiving messages by the battery management system in a receiving filter of the battery, wherein the message receiving identifier is different from a sending identifier for sending charging demand messages by the battery management system to the charging device; a first sending module, configured to send a charging request message to the charging device in response to a charging start signal sent by the charging device; an adjustment module, configured to adjust the message receiving identifier to be the same as the sending identifier in response to the charging start signal, thereby obtaining a receiving identifier; a receiving module, configured to receive a target message based on the receiving identifier; the receiving identifier is the same as the sending identifier of the charging demand message; A detection module is used to perform anomaly detection on the message transmitted between the battery and the charging device based on the target message and the charging demand message to obtain a message anomaly result; wherein the anomaly detection at least includes comparing the charging content in the target message and the charging demand message.

11. A message anomaly detection device, characterized in that: The message anomaly detection device includes: A second sending module is used to send a charging start signal to the battery in response to being connected to the battery, so that the battery configures the battery management system's message receiving identifier for receiving messages in the receiving filter of the battery management system, and the message receiving identifier is different from the sending identifier of the battery management system for sending a charging requirement message to the charging device; in response to the charging start signal, send a charging requirement message to the charging device; in response to the charging start signal, adjust the message receiving identifier to be the same as the sending identifier to obtain a receiving identifier; receive a target message based on the receiving identifier; the receiving identifier is the same as the sending identifier of the charging requirement message; based on the target message and the charging requirement message, perform an anomaly detection on the message transmitted between the battery and the charging device to obtain a message anomaly result; wherein, the anomaly detection at least includes comparing the charging content in the target message and the charging requirement message.

12. A message anomaly detection device, characterized in that: The message anomaly detection device includes: a memory for storing executable instructions; The processor is configured to implement the steps of the message anomaly detection method according to any one of claims 1 to 9 when executing the executable instructions stored in the memory.

13. A computer-readable storage medium, characterized in that The storage medium stores executable instructions, and when the executable instructions are executed by the processor, the steps in the message anomaly detection method according to any one of claims 1 to 9 are implemented.

14. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps of the message anomaly detection method according to any one of claims 1 to 9 are implemented.

Images