Plate end encryption communication processing method and device, electronic equipment and vehicle

Abstract

The invention provides a board end encryption communication processing method and device, electronic equipment and a vehicle. The method comprises the following steps: receiving a communication message sent by a sending end through plate end encryption communication, and recording the communication message in a database; whether the communication message is a default message or not is judged, and when the sending end breaks down, the default message is sent through board end encryption communication; in response to determining that the communication message is a default message, judging whether the default message is received for the first time; in response to determining that the default message is received for the first time, recording a message fault; or, in response to determining that the default message is not received for the first time, stopping the message fault recording. According to the message fault recording method and device, message fault recording can be carried out on the default message received for the first time, recording of the message fault of the default message not received for the first time is stopped, in this way, the message fault is recorded for one time corresponding to the default message, fewer storage resources are occupied, and the probability of false alarm of the fault can be reduced.

Description

Technical Field

[0001] The present application relates to the field of communication processing technology, and in particular to a method, device, electronic equipment and vehicle for processing board-side encrypted communication. Background Art

[0002] Security Onboard Communication (SecOC) is an information security component in the vehicle software package, which is designed to improve the security of vehicle network communications. If a communication code is found to be faulty, the default code will be used to fill and send it.

[0003] However, during the current execution of encrypted communication on the board side, fault information will be continuously recorded for the received default code, which results in too much fault information being recorded, affecting the use effect. Summary of the invention

[0004] In view of this, the purpose of the present application is to propose a method, device, electronic device and vehicle for processing board-side encrypted communication, so as to solve the problem of excessive fault information recorded for default codes during current board-side encrypted communication.

[0005] Based on the above purpose, this application provides a method for processing board-side encrypted communication, including:

[0006] Receive the communication message sent by the sending end through the board-side encrypted communication, and record the communication message in the database;

[0007] Determine whether the communication message is a default message, wherein the sending end will send the default message through board-side encrypted communication when a failure occurs;

[0008] In response to determining that the communication message is a default message, determining whether the default message is received for the first time;

[0009] In response to determining that the default message is received for the first time, recording a message failure; or,

[0010] In response to determining that the default message is not received for the first time, message fault recording is stopped.

[0011] Based on the same inventive concept, the present application also provides a processing device for board-side encrypted communication, including:

[0012] The message recording module is configured to receive the communication message sent by the sending end through the board-side encrypted communication, and record the communication message in the database;

[0013] A default message determination module is configured to determine whether the communication message is a default message, wherein the sending end will send the default message through board-side encrypted communication when a fault occurs;

[0014] The fault recording module is configured to, in response to determining that the communication message is a default message, determine whether the default message is received for the first time; in response to determining that the default message is received for the first time, record a message fault; or, in response to determining that the default message is not received for the first time, stop recording message faults.

[0015] Based on the same inventive concept, the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor implements the method as described above when executing the computer program.

[0016] Based on the same inventive concept, the present application also provides a vehicle, comprising the device as described above or the electronic device as described above.

[0017] From the above, it can be seen that the board-side encrypted communication processing method, device, electronic device and vehicle provided in the present application will continuously judge the communication message sent by the sending end. If the communication message is a default message, the default message will be recorded, and if the default message is received for the first time, the message fault will be recorded. If it is not received for the first time, the message fault will be stopped. In this way, the message fault will be recorded once for the default message, so that the storage resources occupied by the message fault record are less, and the adverse use effects brought to the user by repeatedly recording the message fault can be avoided, and the probability of false alarm faults can be reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the present application or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0019] Figure 1 A flowchart of a method for processing board-side encrypted communication according to an embodiment of the present application;

[0020] Figure 2 It is a structural block diagram of a processing device for board-side encrypted communication according to an embodiment of the present application;

[0021] Figure 3 A schematic diagram of the structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to make the objectives, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0023] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present application should be the usual meanings understood by people with ordinary skills in the field to which the present application belongs. The "first", "second" and similar words used in the embodiments of the present application do not represent any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing in front of the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0024] Glossary:

[0025] SecOC: Security Onboard Communication, which means board-side encrypted communication.

[0026] CANFD: CAN with Flexible Data-Rate, variable-rate CAN.

[0027] CMAC: Cipher Block Chaining-Message Authentication Code, a message authentication code based on a symmetric key block encryption algorithm.

[0028] ECU: electronic Control Unit, electronic controller.

[0029] GW: gateway.

[0030] HUT: Head Unit Terminal, host controller.

[0031] API: Application Programming Interface, application programming interface.

[0032] DTC: Diagnostic Trouble Code, diagnostic trouble code.

[0033] RID: Routine ID, readable function.

[0034] SecOC is a security protection mechanism for CANFD (CAN with Flexible Data-Rate) signals. In layman's terms, two additional signals are added to the end of the message, one is the freshness value, and the other is the locally calculated CMAC (Cipher Block Chaining-Message Authentication Code, a message authentication code based on a symmetric key block encryption algorithm) value. The sender will calculate these two values ​​locally using the key and then give them to the receiver.

[0035] After receiving the message, the receiver will calculate the freshness value and CMAC value locally because all ECUs have the same preset key. After the calculation is completed, it will be compared with the freshness value and CMAC value sent. After the comparison, if the values ​​are the same, then the verification passes. If the comparison is inconsistent, then the verification fails and the message is discarded. If the verification of several consecutive frames of messages fails and is discarded, the function will perform timeout processing.

[0036] Default code: The default code is a redundant processing mechanism in SecOC. When the sender is calculating the CMAC value, such as API interface call failure, key calculation call failure, etc., when the CMAC value cannot be calculated, the default code will be used to fill the CMAC value. Assuming that the CMAC value is a 6-byte data, it is a calculated random value under normal circumstances. However, with the default code filling, this string of data is 3E 3E 3E3E 3E 3E; the receiving end will definitely pass the verification of this data. Because when the CMAC value verification fails and the fault type is not caused by the attacker, the default code will be used to protect the function.

[0037] Generally, attackers exploit loopholes in the signal transmission process to attack the target, rather than affecting the function due to problems in the sender's own mechanism, so there is a default code mechanism.

[0038] For the default code mechanism: Secoc is the master-slave structure, the gateway GW is the master node, and it will send synchronization messages to each slave node at regular intervals to synchronize the local counters of each component; between each ECU, secoc is filled after the interactive message. This interactive message is called a security message.

[0039] When the receiving end receives a safety message with five frames of errors and a synchronization message with nine frames of errors, it needs to record the DTCs of safety message verification failure and synchronization message verification failure.

[0040] When the receiving end receives a safety message filled with a default code, it will record the DTC that the safety message filled with the default code has passed the verification, and when it receives five safety messages filled with the default code, it will record the DTC that the safety message verification has failed, because the default code is also considered a fault state. When a synchronization message filled with a default code is received, it will record the DTC that the synchronization message filled with the default code has passed the verification, and when it receives nine synchronization messages filled with the default code, it will record the DTC that the synchronization message verification has failed, because the default code is also considered a fault state.

[0041] Because the default code is difficult to eliminate once it occurs, the sender will usually record two DTCs: default code and verification failure. If the gateway GW makes a mistake, the default code will be filled in the synchronization message and the safety message sent by the gateway GW, and the receiver will record 4 DTCs.

[0042] When a device on the sending end fails, the default code is used to fill the insulation and send it, which will cause the receiving end to record too much fault information according to the default code. The fault information only needs to be recorded once, and repeated recording will occupy storage resources. In addition, if the fault information is continuously recorded on the vehicle production line, it will often cause the vehicle to be unable to come off the production line, seriously affecting the vehicle production process.

[0043] Based on the above situation, the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0044] The board-side encrypted communication processing method proposed in the embodiment of the present application is applied to the receiving end, such as Figure 1 As shown, the method includes:

[0045] Step 101, receiving a communication message sent by a sending end through board-side encrypted communication, and recording the communication message in a database.

[0046] In specific implementation, the sending end may be a gateway as a master node, or other slave nodes (including various ECUs or HUTs) connected to the gateway. The receiving end includes (any ECU or HUT).

[0047] When the sending end is normal, it will use the key corresponding to the sending end to calculate the freshness value and CMAC value based on the encrypted communication on the board, add the calculated freshness value and CMAC value to the end of the communication message, and send it to the receiving end. The receiving end uses the same key to calculate the corresponding freshness value and CMAC value based on the encrypted communication on the board, and compares them with the freshness value and CMAC value in the communication message sent by the sending end to determine whether they are consistent. If they are consistent, the verification passes, and if they are inconsistent, the verification fails. After the verification passes, the communication message will be recorded and stored in the local database of the receiving end.

[0048] Step 102, determining whether the communication message is a default message, wherein the sending end will send the default message through board-side encrypted communication when a failure occurs.

[0049] In specific implementation, after receiving the default message, the receiving end will verify the default message, and also use the same key to calculate the corresponding freshness value and the corresponding CMAC value based on the board-side encrypted communication, and compare them with the freshness value and CMAC value in the received default message. If they are consistent, the verification passes, and if they are inconsistent, the verification fails. If the default message verification fails, it proves that there is a serious fault and the fault is reported directly; if the default message verification succeeds, the default message will be recorded and stored in the local database of the receiving end.

[0050] If the sender confirms that a device on the sender side has failed, it needs to use the default message as the communication message and also needs to add the corresponding freshness value and CMAC value and send it to the receiver. After the receiver receives the default message, it can know that there may be a device failure on the sender side.

[0051] Step 103, in response to determining that the communication message is a default message, determining whether the default message is received for the first time.

[0052] In specific implementation, it is determined whether the received default message is the first frame default message, if yes, it is determined that the default message is received for the first time, otherwise it is not the first time the default message is received.

[0053] Step 104: In response to determining that the default message is received for the first time, record a message failure.

[0054] Alternatively, in step 105, in response to determining that the default message is not received for the first time, message fault recording is stopped.

[0055] In specific implementation, the message fault is recorded only for the default message received for the first time, and no record is made for the default message received subsequently, so as to avoid the situation that repeated recording of message faults may easily lead to false fault reports.

[0056] Through the above scheme, the communication message sent by the sender will be continuously judged. If the communication message is a default message, the default message will be recorded, and if the default message is received for the first time, the message failure will be recorded. If it is not received for the first time, the message failure will be stopped. In this way, the message failure will be recorded once for the default message, so that the storage resources occupied by the message failure record are less, and the adverse use effect brought to the user by repeatedly recording the message failure can be avoided, and the probability of false alarm failure can be reduced.

[0057] In some embodiments, the step of recording the communication message in a database in step 101 includes:

[0058] Step 1011, determining whether the number of the communication messages is less than or equal to a number threshold.

[0059] In specific implementation, the corresponding quantity threshold may be preset; or the remaining storage space of the receiving end may be retrieved, and the quantity threshold is determined according to the remaining storage space, and the remaining storage space is positively correlated with the quantity threshold.

[0060] In addition, a quantity threshold table of various receiving end models may be pre-stored, and then the corresponding quantity threshold is determined from the table according to the receiving end model.

[0061] Step 1012: In response to determining that the number of the communication messages is less than or equal to the number threshold, the communication messages are recorded in a database using a readable ID (RID).

[0062] Alternatively, in step 1013, in response to determining that the number of the communication messages is greater than the number threshold, all the communication messages are grouped, and the communication messages are recorded in a database according to the groups.

[0063] In specific implementation, for the readable function, corresponding space will be allocated for recording all the communication messages received this time, which requires a large space, so the database can only record the communication messages with a small number of received messages for the readable function. Since the group record adopts a rolling record method for each group, and the number of groups will be less than the number of communication messages received at one time, the database can use the group record method to record and store the communication messages with a large number of received messages.

[0064] The communication messages include: synchronization messages sent by a master node (eg, a gateway) for time synchronization, and / or security messages sent by a slave node (eg, other ECUs) for interaction.

[0065] Through the above scheme, no matter the number of received communication messages is large or small, the database can use the most appropriate method to record and store them to ensure the accuracy of the records.

[0066] In some embodiments, in step 1012, the communication message is recorded in the database using a readable function, wherein the readable function records when the communication message is received, and if the communication message is continuously received, the record is continuously updated through the readable function, and when the record is full, the received new communication message is used to overwrite the earliest recorded communication message.

[0067] Step 1012 includes:

[0068] Step 10121, verify each of the communication messages and record the verification passing time.

[0069] In specific implementation, the verification process for the communication message is as follows: when the sending end is normal, the sending end will use the key corresponding to the sending end to calculate the freshness value and CMAC value based on the board-side encrypted communication, add the calculated freshness value and CMAC value to the end of the communication message, and send it to the receiving end. The receiving end uses the same key to calculate the corresponding freshness value and the corresponding CMAC value based on the board-side encrypted communication, and compares them with the freshness value and CMAC value in the communication message sent by the receiving sender to determine whether they are consistent. If they are consistent, it proves that the verification of the communication message has passed, and the verification passing time of the communication message will be recorded at this time. For example, the communication message frame 0x236 passed the verification at 6:01 pm on August 21, 2024.

[0070] Step 10122, allocating a data message with a predetermined number of characters to each communication message through a readable function.

[0071] Step 10123, using the partial data message of the first number of characters in the data message, record the verification passing time corresponding to the communication message in the database.

[0072] Step 10124, using the remaining second character number of the data message in the data message, record the sender address corresponding to the communication message in the database; wherein the sum of the first character number and the second character number is the predetermined character number.

[0073] In specific implementation, the corresponding predetermined number of characters (for example, 4 bytes, 8 bytes, 16 bytes) can be set according to the data volume of the communication message. The first number of characters is used to record the verification passing time corresponding to the communication message, and the remaining second number of characters is used to record the sender address.

[0074] For example, the predetermined number of characters is 8 bytes, of which the first 6 bytes record the verification passing time, and the last 2 bytes record the sender address (e.g., for the message frame 0x236, the verification passing time is 6:01 p.m. on August 21, 2024, and the sender ID is 236, and the corresponding 8-byte record is 20 24 08 21 18 01 0236). Alternatively, the first 2 bytes record the sender address, and the last 6 bytes record the verification passing time.

[0075] Through the above scheme, the communication message can be accurately recorded based on the readable function, thereby ensuring the accuracy of the communication message recording.

[0076] In some embodiments, after step 1012, the method further includes:

[0077] Step 1012', receiving the login data corresponding to the readable function, calling the access interface of the readable function, and entering the record data corresponding to the readable function.

[0078] In specific implementation, the corresponding login data includes: a login identifier (for example, 27) and a login password (for example, 1234). After the login data is input into the receiving end, if it is determined that the login data is correct, the access interface of the readable function will be directly called, and the access interface is the entry point for the record data (including: communication message and message fault information) corresponding to the readable function in the database. The record data corresponding to the readable function in the database is entered through the access interface.

[0079] Step 1012, receiving read data for the recorded communication message, retrieving the communication message recorded in the recorded data and outputting it.

[0080] In a specific implementation, the corresponding read data includes: a read identifier (for example, 22) and a corresponding read data type code (for example, a default message in a read communication message, the data type code corresponding to the default message is F1CC). After the read data is input into the receiving end, the corresponding read communication message will be retrieved from the record data in the database and output, and displayed on the display screen for the user to view.

[0081] Through the above scheme, under the premise of ensuring the security of recorded data, the user can read the corresponding recorded communication message through the above method, providing the user with a reading scheme to facilitate the user to read and view.

[0082] In some embodiments, step 1013 includes:

[0083] Step 10131, determine the number of senders corresponding to all communication messages, and set the number of groups in the database according to the number of senders, wherein each sender corresponds to at least one group.

[0084] In specific implementation, the corresponding sender can be a gateway, each ECU or HUT. In this way, a group can be set for each sender in the data to store the communication message (for example, synchronization message and / or security message) corresponding to the sender. The number of corresponding groups should be greater than or equal to the number of senders, that is, at least one group is set for each sender.

[0085] Step 10132, record each of the communication messages in the group corresponding to the sender of the communication message in the database.

[0086] In a specific implementation, for each communication message in at least one received communication message, the sender of the communication message is determined, and then the corresponding group is retrieved according to the determined sender, and the communication message is stored in the corresponding group.

[0087] Through the above scheme, the received communication messages can be recorded and stored according to the groups determined by the sender, and the communication messages sent by the same sender can be stored in one group, which can further save the storage space of the database.

[0088] In some embodiments, the communication messages include: synchronization messages and / or security messages.

[0089] The communication messages include: synchronization messages sent by a master node (eg, a gateway) for time synchronization, and / or security messages sent by a slave node (eg, other ECUs) for interaction.

[0090] Step 10131 includes:

[0091] Determine the number of senders corresponding to all communication messages, set a first group for storing security messages for each sender in the database, and set a second group for storing synchronization messages of each sender, wherein the number of first groups is equal to the number of senders.

[0092] In the specific implementation, since the security messages are interactive messages of each sender, they are different from each other, so it is necessary to set a first group for each sender. The corresponding synchronization messages are time synchronization messages. The synchronization messages are uniformly sent by the master node and are relatively consistent, so it is sufficient to set a second group for storage. The synchronization messages do not need to distinguish between each sender.

[0093] Step 10132 includes:

[0094] Step 101321, in response to determining that the communication message is a synchronization message, storing the synchronization message in the second group in the database.

[0095] And / or, step 101321, in response to determining that the communication message is a security message, determining a target first group corresponding to the sender of the security message from a database, and storing the security message in the target first group.

[0096] In specific implementation, when storing in the database, the type of the received communication message will be determined. If it is a synchronization message, it can be directly stored in the second group without looking at the sender of the communication message; if it is a security message, the sender of the communication message will be determined, and the corresponding target first group will be determined from the multiple first groups in the database according to the determined sender, and the communication message will be stored in the target first group.

[0097] For example, the security messages sent by the gateway are 0x123, 0x124, 0x125, and 0x126. These four frames of communication messages will be recorded in the first target group corresponding to the gateway. If the first group is full, the earliest security message will be deleted during the rolling storage, and then the new security message will be stored.

[0098] Through the above scheme, synchronization messages and security messages are stored in different grouping methods. Security messages are stored according to the corresponding first group determined by the sender. In this way, security messages from the same sender can be stored in the same first group, which can save space and facilitate calling and reading. For synchronization messages, a second group is used for storage, which further saves storage space for synchronization messages.

[0099] In some embodiments, the step of recording the communication message in a database in step 101 includes:

[0100] In response to the database being full, determining the oldest historical communication message stored in the database, and overwriting the oldest historical communication message stored with the communication message.

[0101] In specific implementation, the space occupied by the new communication message to be stored can be recorded as needed, the earliest historical communication message corresponding to the occupied space can be selected from the database, these historical communication messages can be deleted, and then the new communication message can be stored.

[0102] Through the above solution, it is ensured that the communication messages stored in the database are all the latest communication messages, avoiding the problem of being unable to continue storing after the database is full, and it is convenient to use.

[0103] The following is a specific example of a method for processing encrypted communication on the board side of the present application:

[0104] There are two corresponding processes for recording communication messages:

[0105] The first method is to record and store a small number of received communication messages (for example, less than or equal to 27). The corresponding receiving end is HUT. The specific execution process is as follows:

[0106] The communication message received by HUT is the interactive SECOC security message. The corresponding security message ID number is 2. Each security message should be allocated an 8-byte data for recording.

[0107] If the security message is a default security message, the first 6 bytes of the 8 bytes are the time when the default security message passed the verification, and the last 2 bytes are the ID of the default security message. For example, if the default security message 0x236 is verified by HUT at 6:01 pm on August 21, 2024, this set of data will be recorded as 20 24 08 21 18 01 02 36.

[0108] If the storage space of the HUT is small and the number of communication messages to be verified is too large, this allocation method requires a larger space to be allocated for recording, which takes up more space and is inconvenient to use. For example, for 27 communication messages, a space of 27*8=216 bytes needs to be allocated for recording, which takes up more space.

[0109] After recording the corresponding communication message, you can read it as follows:

[0110] For a readable RID, first enter 27+login password to enter the RID, and then use 22+read content symbol to read it out. For example, after logging into the RID, if you want to call the default message of the record, since the RID of the default message is F1CC, you can enter 22F1CC to read the relevant records of the default message.

[0111] The second method is to record the communication messages in a grouped manner for a large number of received communication messages (for example, more than 27). The corresponding receiving end is the HUT. The specific execution process is as follows:

[0112] The HUT receives 30 communication messages (including synchronization messages and / or safety messages) from various senders, but the 30 communication messages may correspond to five or six senders, that is, there may be a situation where one sender sends multiple communication messages.

[0113] For example, there are 30 communication messages, and the sender only has 5 messages. Then 6 groups can be set, which are also 6 8-byte groups for recording. Among them, 5 groups record security messages, and 1 group records synchronization messages.

[0114] For example, the gateway GW sends 4 frames of secoc security messages to the HUT. The HUT will determine the corresponding grouping of the GW, and the corresponding 4 frames of security messages are 0x123, 0x124, 0x125, and 0x126. Then this grouping will record these 4 frames of messages in a rolling manner, and the latest security message will overwrite the old security message. Since this grouping data is specially set for the GW node, after all, if there is a problem with the GW node, then all the security messages sent by this GW node must be filled with the default code, so that there will be no confusion and errors.

[0115] The above two solutions are both ways of recording communication messages. The following is the recording process of the message fault DTC when it is determined to be the default message during the recording process:

[0116] When a safety message filled with a default code (i.e., a default safety message) or a synchronization message filled with a default code (i.e., a default synchronization message) is received, only one DTC of the message failure is recorded. If five safety messages filled with default codes or nine synchronization messages filled with default codes are received, no DTC of verification failure is recorded. This can reduce the probability of false faults when the vehicle is on the production line, and reduce the situation where the vehicle cannot get off the production line due to continuous fault reporting.

[0117] It should be noted that the method of the embodiment of the present application can be performed by a single device, such as a computer or server. The method of this embodiment can also be applied to a distributed scenario and completed by multiple devices cooperating with each other. In the case of such a distributed scenario, one of the multiple devices can only perform one or more steps in the method of the embodiment of the present application, and the multiple devices will interact with each other to complete the described method.

[0118] It should be noted that the above describes some embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0119] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a processing device for board-side encrypted communication.

[0120] refer to Figure 2 , the device comprises:

[0121] The message recording module is configured to receive the communication message sent by the sending end through the board-side encrypted communication, and record the communication message in the database;

[0122] A default message determination module is configured to determine whether the communication message is a default message, wherein the sending end will send the default message through board-side encrypted communication when a fault occurs;

[0123] The fault recording module is configured to, in response to determining that the communication message is a default message, determine whether the default message is received for the first time; in response to determining that the default message is received for the first time, record a message fault; or, in response to determining that the default message is not received for the first time, stop recording message faults.

[0124] In some embodiments, the message recording module includes:

[0125] A quantity determination unit, configured to determine whether the quantity of the communication messages is less than or equal to a quantity threshold;

[0126] a readable function recording unit, configured to, in response to determining that the number of the communication messages is less than or equal to the number threshold, record the communication messages in a database using a readable function; or,

[0127] The grouping recording unit is configured to group all the communication messages in response to determining that the number of the communication messages is greater than the number threshold, and record the communication messages according to the groups in a database.

[0128] In some embodiments, the readable function recording unit is specifically configured as follows:

[0129] Verifying each of the communication messages and recording the verification passing time;

[0130] Allocating a data message with a predetermined number of characters to each communication message through a readable function;

[0131] Using a portion of the data message of the first number of characters in the data message, recording the verification passing time corresponding to the communication message in a database;

[0132] The sending end address corresponding to the communication message is recorded in a database using the partial data message of the second character number remaining in the data message; wherein the sum of the first character number and the second character number is the predetermined character number.

[0133] In some embodiments, the message recording module further includes: a readable function reading unit configured to:

[0134] After recording the communication message in the database using the readable function, receiving the login data corresponding to the readable function, calling the access interface of the readable function, and entering the record data corresponding to the readable function;

[0135] The read data for the recorded communication message is received, and the communication message recorded in the recorded data is retrieved and outputted.

[0136] In some embodiments, the group recording unit includes:

[0137] The grouping subunit is configured to determine the number of senders corresponding to all communication messages, and set the number of groups in the database according to the number of senders, wherein each sender corresponds to at least one group;

[0138] The recording subunit is configured to record each of the communication messages in a group corresponding to the sender of the communication message in the database.

[0139] In some embodiments, the communication messages include: synchronization messages and / or security messages;

[0140] The grouping subunit is specifically configured as follows:

[0141] Determine the number of senders corresponding to all communication messages, set a first group for storing security messages for each sender in the database, and set a second group for storing synchronization messages of each sender, wherein the number of the first group is equal to the number of senders;

[0142] The recording subunit is specifically configured as follows:

[0143] In response to determining that the communication message is a synchronization message, storing the synchronization message in the second group in a database; and / or,

[0144] In response to determining that the communication message is a safety message, a target first group corresponding to a sender of the safety message is determined from a database, and the safety message is stored in the target first group.

[0145] In some embodiments, the message recording module is further configured to:

[0146] In response to the database being full, determining the oldest historical communication message stored in the database, and overwriting the oldest historical communication message stored with the communication message.

[0147] For the convenience of description, the above device is described in terms of functions divided into various modules. Of course, when implementing the present application, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0148] The device of the above embodiment is used to implement the corresponding method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.

[0149] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described in any of the above embodiments when executing the program.

[0150] Figure 3A more specific schematic diagram of the hardware structure of an electronic device provided in this embodiment is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 in the device.

[0151] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0152] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0153] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0154] The communication interface 1040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0155] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0156] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.

[0157] The electronic device of the above embodiment is used to implement the corresponding method in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be described in detail here.

[0158] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments, the present application also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the method described in any of the above embodiments.

[0159] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0160] The computer instructions stored in the storage medium of the above embodiments are used to enable the computer to execute the method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0161] Based on the same concept, corresponding to any of the above-mentioned embodiment methods, the present application also provides a computer program product, including computer program instructions. When the computer program instructions are run on a computer, the computer executes the method described in any of the above embodiments, which has the beneficial effects of the corresponding method embodiments and will not be repeated here.

[0162] Based on the same inventive concept, the present application also provides a vehicle, including the device described in the above embodiment or the electronic device described in the above embodiment. The beneficial effects of the embodiments with the corresponding device or electronic device are not described in detail here.

[0163] It is understandable that before using the technical solutions of each embodiment of the present application, the type, scope of use, usage scenarios, etc. of the personal information involved will be informed to the user in an appropriate manner, and the user's authorization will be obtained.

[0164] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly remind the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can independently choose whether to provide personal information to the electronic device, application, server, storage medium or other software or hardware that performs the operation of the technical solution of the present application according to the prompt message.

[0165] As an optional but non-limiting implementation, in response to receiving the user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0166] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation method of this application. Other methods that meet relevant laws and regulations may also be applied to the implementation method of this application.

[0167] A person skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present application is limited to these examples. In line with the concept of the present application, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present application as described above, which are not provided in detail for the sake of simplicity.

[0168] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present application difficult to understand, the known power supply / ground connection with the integrated circuit (IC) chip and other components may or may not be shown in the provided drawings. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present application difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform to be implemented in the embodiments of the present application (that is, these details should be fully within the scope of understanding of those skilled in the art). In the case of elaborating specific details (e.g., circuits) to describe exemplary embodiments of the present application, it is obvious to those skilled in the art that the embodiments of the present application can be implemented without these specific details or when these specific details are changed. Therefore, these descriptions should be considered to be illustrative rather than restrictive.

[0169] Although the present application has been described in conjunction with specific embodiments of the present application, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

[0170] The embodiments of the present application are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the present application. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included in the protection scope of the present application.

Claims

1. A method for processing board-side encrypted communication, characterized in that: include: Receive the communication message sent by the sending end through the board-side encrypted communication, and record the communication message in the database; Determine whether the communication message is a default message, wherein the sending end will send the default message through board-side encrypted communication when a failure occurs; In response to determining that the communication message is a default message, determining whether the default message is received for the first time; In response to determining that the default message is received for the first time, recording a message failure; or, In response to determining that the default message is not received for the first time, message fault recording is stopped.

2. The method according to claim 1, characterized in that The recording of the communication message in the database includes: Determining whether the number of the communication messages is less than or equal to a number threshold; In response to determining that the number of the communication messages is less than or equal to the number threshold, recording the communication messages in a database using a readable function; or, In response to determining that the number of the communication messages is greater than the number threshold, all the communication messages are grouped, and the communication messages are recorded in a database according to the groups.

3. The method according to claim 2, characterized in that The step of recording the communication message in a database using a readable function includes: Verifying each of the communication messages and recording the verification passing time; Allocating a data message with a predetermined number of characters to each communication message through a readable function; Using a portion of the data message of the first number of characters in the data message, recording the verification passing time corresponding to the communication message in a database; The sending end address corresponding to the communication message is recorded in a database using the partial data message of the second character number remaining in the data message; wherein the sum of the first character number and the second character number is the predetermined character number.

4. The method according to claim 2 or 3, characterized in that: After recording the communication message in the database using the readable function, the method further includes: Receiving login data corresponding to a readable function, calling an access interface of the readable function, and entering record data corresponding to the readable function; The read data for the recorded communication message is received, and the communication message recorded in the recorded data is retrieved and outputted.

5. The method according to claim 2, characterized in that: The step of grouping all the communication messages and recording the communication messages in a database according to the groups includes: Determine the number of senders corresponding to all communication messages, and set the number of groups in the database according to the number of senders, wherein each sender corresponds to at least one group; Each of the communication messages is recorded in a group corresponding to the sender of the communication message in a database.

6. The method according to claim 5, characterized in that The communication messages include: synchronization messages and / or security messages; The determining the number of senders corresponding to all communication messages and setting the number of groups in the database according to the number of senders includes: Determine the number of senders corresponding to all communication messages, set a first group for storing security messages for each sender in the database, and set a second group for storing synchronization messages of each sender, wherein the number of the first group is equal to the number of senders; The step of recording each of the communication messages in a group corresponding to the sender of the communication message in the database includes: In response to determining that the communication message is a synchronization message, storing the synchronization message in the second group in a database; and / or, In response to determining that the communication message is a safety message, a target first group corresponding to a sender of the safety message is determined from a database, and the safety message is stored in the target first group.

7. The method according to claim 1, characterized in that The recording of the communication message in the database includes: In response to the database being full, determining the oldest historical communication message stored in the database, and overwriting the oldest historical communication message stored with the communication message.

8. A processing device for board-side encrypted communication, characterized in that: include: The message recording module is configured to receive the communication message sent by the sending end through the board-side encrypted communication, and record the communication message in the database; A default message determination module is configured to determine whether the communication message is a default message, wherein the sending end will send the default message through board-side encrypted communication when a fault occurs; The fault recording module is configured to, in response to determining that the communication message is a default message, determine whether the default message is received for the first time; in response to determining that the default message is received for the first time, record a message fault; or, in response to determining that the default message is not received for the first time, stop recording message faults.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 7 is implemented.

10. A vehicle, characterized in that: Includes the device according to claim 8 or the electronic device according to claim 9.

Images