Data interaction methods, devices, systems, readable storage media, and electronic devices
By setting up safety monitoring strategies between the hardware domains of the vehicle's electronic systems, generating and verifying backup data, the problems of isolation and insufficient monitoring between subsystems are solved, the stability and security of the system are improved, and the risk of failure is reduced.
Patent Information
- Application Number
- CN202611435521.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2026-08-14
- Filing Date
- 2026-09-15
- Publication Date
- 2026-11-17
AI Technical Summary
The lack of isolation between different subsystems in a vehicle's electronic system means that failures in lower-safety-level subsystems can affect higher-safety-level subsystems. Furthermore, the lack of effective safety monitoring and data switching capabilities impacts system safety and stability.
Security monitoring policies are set up between hardware domains. Backup data is generated by receiving business instructions. The business data and backup data are verified. If the conditions are met, the target data is sent to achieve data backup and verification, ensuring the flexibility and efficiency of communication.
It improves the monitoring and stability of communication between hardware domains, reduces the risk of system failure caused by data transmission interruption, achieves stable operation under failure conditions, and has high development efficiency and low hardware resource requirements.
Smart Images

Figure CN123123366A_ABST
Abstract
Description
[0001] This disclosure claims priority to Singapore Patent Application No. 10202602848X, filed on August 14, 2026, entitled “Data Interaction Method, Apparatus, System, Readable Storage Medium and Electronic Device”, the entire contents of which are incorporated herein by reference. Technical Field
[0002] This disclosure relates to integrated circuit technology, and in particular to a data interaction method, system, apparatus, readable storage medium, and electronic device. Background Technology
[0003] As vehicle electronic systems become increasingly complex, they integrate a series of functional subsystems, such as Advanced Driver Assistance Systems (ADAS), In-Vehicle Infotainment (IVI), and Safety Islands. These subsystems have different Automotive Safety Integrity Level (ASIL) requirements. In a safety architecture geared towards driver automation, it is essential to ensure the safety and reliability of business interactions between subsystems of different safety levels.
[0004] In the aforementioned vehicle electronic system architecture, different subsystems often lack adequate isolation. When a low-security-level subsystem faces malicious attacks, abnormal operations, or malfunctions, it may affect the high-security-level subsystems it interacts with. After a malfunction occurs, the lack of sufficient security monitoring capabilities between subsystems prevents timely detection and isolation of affected subsystems, and the inability to effectively and automatically switch and recover the data required by the subsystems, leading to subsystem failure and impacting the security and stability of the entire system. Summary of the Invention
[0005] To address the aforementioned technical problems, this disclosure provides a data interaction method, system, apparatus, readable storage medium, and electronic device to resolve the issue of the inability to guarantee the security and stability of system operation when data communication occurs between subsystems in a vehicle electronic system architecture.
[0006] In a first aspect, this disclosure provides a data interaction method applied to a security domain. The method includes: receiving a service instruction; generating backup data based on the service instruction; receiving service data sent by a first hardware domain; verifying the service data and the backup data respectively to obtain a first verification result and a second verification result; determining whether the current condition meets preset data transmission conditions based on the first verification result and the second verification result; if the condition meets the data transmission conditions, determining target data from the service data and the backup data based on the first verification result and the second verification result, and sending the target data to a second hardware domain.
[0007] A second aspect of this disclosure provides a data interaction system, including: a first hardware domain, a second hardware domain, and a security domain; the security domain is located on a communication link between the first hardware domain and the second hardware domain; the security domain is used to execute the above-described data interaction method.
[0008] A third aspect of this disclosure provides a data interaction device, comprising: a first receiving module for receiving a service instruction; a generating module for generating backup data based on the service instruction; a second receiving module for receiving service data sent by a first hardware domain; a verification module for verifying the service data and the backup data respectively to obtain a first verification result and a second verification result; a determining module for determining, based on the first verification result and the second verification result, whether a preset data transmission condition is met; and a sending module for determining, if the data transmission condition is met, target data from the service data and the backup data based on the first verification result and the second verification result, and sending the target data to a second hardware domain.
[0009] A fourth aspect of this disclosure provides a vehicle including the data interaction system described above.
[0010] A fifth aspect of this disclosure provides a computer-readable storage medium storing a computer program that, when executed, implements the data interaction method described above.
[0011] A sixth aspect of this disclosure provides an electronic device comprising: a processor; a memory for storing processor-executable instructions; and a processor configured to read executable instructions from the memory and execute the instructions to implement the data interaction method described above.
[0012] A seventh aspect of this disclosure provides a computer program product including computer program instructions that, when executed by an instruction processor, perform the aforementioned data interaction method.
[0013] Based on the data interaction method, system, apparatus, readable storage medium, and electronic device provided in this disclosure, by receiving service instructions, generating backup data based on the service instructions, receiving service data sent by a first hardware domain, verifying the service data and backup data respectively to obtain a first verification result and a second verification result, if the first verification result and the second verification result meet preset data transmission conditions, determining target data from the service data and backup data based on the first verification result and the second verification result, and sending the target data to a second hardware domain, a security monitoring strategy can be set between different hardware domains. This allows for backup and verification of data transmitted between hardware domains, enabling more flexible and efficient monitoring and protection of communication between hardware domains. Thus, in the event of a problem in one hardware domain, backup data can ensure the normal operation of another hardware domain, reducing the risk of system hardware and software failures caused by data transmission interruptions and improving the stability of hardware domain operation. Furthermore, the implementation of this disclosure is simple, has high development efficiency, does not require virtual machines, has low hardware resource requirements, and uses backup data to cover various fault types, making the solution highly versatile. Attached Figure Description
[0014] Figure 1 This is a flowchart illustrating a data interaction method provided in an exemplary embodiment of this disclosure; Figure 2 This is a flowchart illustrating a data interaction method provided in another exemplary embodiment of this disclosure; Figure 3 This is a schematic diagram of the structure of a data interaction system provided in an exemplary embodiment of this disclosure; Figure 4 This is a schematic diagram of the structure of a data interaction system provided in another exemplary embodiment of this disclosure; Figure 5 This is a schematic diagram of the structure of a data interaction device provided in an exemplary embodiment of the present disclosure; Figure 6 This is a schematic diagram of the structure of a data interaction device provided in another exemplary embodiment of this disclosure; Figure 7 This is a schematic diagram of the structure of a vehicle provided in an exemplary embodiment of this disclosure; Figure 8 This is a structural diagram of an electronic device provided in an exemplary embodiment of this disclosure. Detailed Implementation
[0015] To explain this disclosure, exemplary embodiments of the disclosure will now be described in detail with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the disclosure, and not all of them. It should be understood that the disclosure is not limited to exemplary embodiments.
[0016] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values of the components and steps set forth in these embodiments do not limit the scope of this disclosure.
[0017] Application Overview The relevant vehicle electronic system architecture often has the following problems in its various subsystems: 1. Security isolation issues. Different subsystems often lack adequate isolation. When a low-security subsystem faces malicious attacks, abnormal operations, or malfunctions, it may affect the high-security subsystems that interact with it.
[0018] 2. Safety monitoring issues. After a failure occurs, there is a lack of sufficient safety monitoring capabilities between subsystems, making it impossible to detect and isolate affected subsystems in a timely manner.
[0019] 3. Safety and fault tolerance issues. After a failure occurs, the data required by the subsystem cannot be effectively switched and recovered automatically, causing the subsystem to fail and affecting the safety and stability of the entire system.
[0020] The solutions to the above problems include: establishing development standards, that is, conducting development, testing, and verification processes for critical systems based on defined ASIL levels; deploying different functional modules in independent virtual machines, each with independent resources and operating environment, thereby reducing mutual interference between different modules; adding error correction codes (ECC) or cyclic redundancy checks (CRC) to verify and protect communication data; and implementing redundant design for critical logic to monitor for faults.
[0021] Of the various solutions mentioned above, the standard-based approach has a complex and inefficient development process. Virtualization introduces additional performance overhead, increasing the complexity of managing and allocating virtual machine resources. Communication verification mechanisms have limited coverage of fault types. Redundancy protection and detection solutions require additional hardware overhead, lack versatility, and have high system complexity.
[0022] To address the aforementioned issues, the data interaction method provided in this disclosure, by setting up security monitoring strategies between communicating hardware domains, backs up and verifies the data transmitted between hardware domains. This allows for more flexible and efficient monitoring and protection of communication between hardware domains. Thus, even if one hardware domain experiences a problem, the backup data can enable the other hardware domain to operate normally, reducing the risk of system hardware and software failures caused by data transmission interruptions and improving the stability of hardware domain operation. This disclosure offers a simple implementation, high development efficiency, eliminates the need for virtual machines, has low hardware resource requirements, and utilizes backup data to cover various fault types, resulting in high versatility in application.
[0023] Exemplary methods Figure 1 This is a flowchart illustrating a data interaction method provided in an exemplary embodiment of this disclosure. This embodiment can be applied to security domains between different hardware domains, and these security domains can be implemented by various hardware modules. The implementation form of the security domain is not limited; for example, it can include dedicated hardware modules such as chips and circuits, or it can include general-purpose devices such as computers and smartphones. Figure 1 As shown, the method includes the following steps 101-106: Step 101: Receive service instructions.
[0024] In one embodiment, the first hardware domain and the second hardware domain described below can be included in various types of system architectures. For example, in a vehicle electronic system, a safety-assisted driving subsystem, an intelligent entertainment cockpit subsystem, a safety island subsystem, etc., can each be considered as a hardware domain. As another example, in a System-on-Chip (SoC) chip, each processor, memory, and other hardware component can each be considered as a hardware domain.
[0025] The aforementioned business instructions are issued from any hardware domain according to the needs of the business scenario. For example, if the first hardware domain is DDR (Double Data Rate Synchronous Dynamic Random Access Memory) and the second hardware domain is the CPU, and the DDR memory needs to return a set of data to the CPU, then the business instruction can be a data read request instruction sent by the CPU.
[0026] Step 102: Generate backup data based on business instructions.
[0027] In one embodiment, the security domain executing this embodiment can receive the aforementioned service instructions and parse them to determine the type, amount, format, and other attributes of the service data required by the second hardware domain, thereby generating backup data corresponding to the service data. Optionally, the values contained in the backup data can be generated in any way, for example, they can be fixed preset values or randomly generated values.
[0028] Step 103: Receive service data sent by the first hardware domain.
[0029] In one embodiment, the service data is data provided by the first hardware domain to the second hardware domain under a specific service scenario. For example, the service data could be sensor data returned by the DDR memory of the first hardware domain in an autonomous driving scenario.
[0030] Step 104: Verify the business data and backup data respectively to obtain the first verification result and the second verification result.
[0031] In one embodiment, the first verification result is the result of verifying the business data, and the second verification result is the result of verifying the backup data. The verification of the business data and backup data can be performed using any preset verification method. The purpose of the verification is to check whether the business data and backup data conform to the data protocol constraints under normal business scenarios. For example, for business data transmitted under preset bus protocol constraints, the received business data and backup data are checked for data volume, data format, etc., to determine whether they conform to the bus protocol constraints.
[0032] Step 105: Based on the first verification result and the second verification result, determine whether the current data transmission conditions are met.
[0033] In one embodiment, the data transmission conditions can be preset. For example, if at least one of the first and second verification results indicates that the verification has passed, it is determined that the current data transmission conditions are met.
[0034] Step 106: If the data transmission conditions are met, based on the first verification result and the second verification result, determine the target data from the business data and backup data, and send the target data to the second hardware domain.
[0035] In one embodiment, when the data transmission conditions are met, the security domain can select target data from business data and backup data according to a preset selection strategy, that is, it can send either business data or backup data as target data to the second hardware domain. The selection strategy can be preset according to actual needs; for example, if the first verification result indicates that the business data verification failed, the backup data can be sent as target data to the second hardware domain.
[0036] The data interaction method provided in this disclosure receives a service instruction, generates backup data based on the service instruction, receives service data sent by a first hardware domain, verifies the service data and backup data respectively, and obtains a first verification result and a second verification result. If the first verification result and the second verification result meet preset data transmission conditions, target data is determined from the service data and backup data based on the first verification result and the second verification result, and the target data is sent to a second hardware domain. This realizes the setting of security monitoring strategies between different hardware domains, and the backup and verification of data transmitted between hardware domains. Communication between hardware domains can be monitored and protected more flexibly and efficiently. Thus, if a problem occurs in one hardware domain, the backup data can enable another hardware domain to operate normally, reducing the risk of system hardware and software failures caused by data transmission interruptions and improving the stability of hardware domain operation. In addition, the implementation method of this disclosure is simple, the development efficiency is high, no virtual machine is required, the hardware resource requirements are low, and the use of backup data can cover various fault types, making the solution highly versatile.
[0037] In some alternative implementations, step 105 above may include: If at least one of the first and second verification results indicates that the verification passed, it is determined that the current data transmission conditions are met; if both the first and second verification results indicate that the verification failed, it is determined that the current data transmission conditions are not met.
[0038] In this embodiment, if at least one of the first verification result and the second verification result indicates that the verification is successful, it means that there is data that enables the second hardware domain to operate normally. The target data can be sent to the second hardware domain so that the second hardware domain will not experience operational abnormalities due to receiving erroneous data.
[0039] If both the first and second verification results indicate that the verification failed, it means that neither the business data nor the backup data can meet the normal operation requirements of the second hardware domain, and no data will be sent to the second hardware domain at this time.
[0040] The data transmission conditions provided in this embodiment can ensure that the data is sent to the second hardware domain when at least one piece of data passes verification, so that the second hardware domain can operate normally, reducing the risk of abnormal operation of the second hardware domain and the entire system due to data errors, and improving the stability of system operation.
[0041] In some alternative implementations, step 106 above may include: If the first verification result indicates that the verification passed and the second verification result indicates that the verification failed, the business data is determined as the target data. If the first verification result indicates that the verification failed, and the second verification result indicates that the verification passed, the backup data is determined as the target data. If both the first and second verification results indicate that the verification passed, the business data will be identified as the target data.
[0042] In this embodiment, if the first verification result indicates that the verification passed, and the second verification result indicates that the verification failed or passed, it means that the service data is the data required by the second hardware domain, and the service data can be sent to the second hardware domain. If the first verification result indicates that the verification failed, and the second verification result indicates that the verification passed, it means that the service data is abnormal, while the backup data meets the data required for the normal operation of the second hardware domain. The backup data can be sent to the second hardware domain to avoid the second hardware domain from malfunctioning due to receiving erroneous data.
[0043] This embodiment enables the second hardware domain to perform normal business operations based on the business data when the business data verification passes. If the business data verification fails but the backup data verification passes, the second hardware domain can continue to operate based on the backup data, and the second hardware domain is in a normal state, avoiding the risk of abnormality in the second hardware domain.
[0044] In some alternative implementations, such as Figure 2 As shown, after step 106, the method further includes: Step 107: If the first verification result indicates that the verification passed and the second verification result indicates that the verification failed, the steps of generating backup data and verifying backup data are repeated according to the preset retry cycle.
[0045] If the first verification result indicates that the verification passed, but the second verification result indicates that the verification failed, it means that the backup data was not generated as expected. In this case, you can regenerate the backup data and verify it according to steps 102 and 104 above. The retry period can be set according to actual needs, for example, 1 second.
[0046] Step 108: In response to the current time reaching the preset retry end time, and the most recent second verification result still indicating that the verification failed, switch the target device to safe operation.
[0047] The retry end time mentioned above refers to the moment when the retry stop condition is met. This retry stop condition can be determined by setting parameters such as the maximum number of retries and the maximum retry duration. When the retry stop condition is met, the steps of generating backup data and verifying the backup data are stopped. If, at the retry end time, the most recently generated backup data still fails verification, it indicates that there is a risk of failure in the functions of the first and second hardware domains for the target service. For safety, the target device is switched to safe operation mode.
[0048] The target device refers to the device containing the first and second hardware domains. For example, the target device can be a SoC chip that includes both the first and second hardware domains. In a safe state, the target device may not perform tasks specific to the business scenario, retaining only basic functions. For example, if the target device is a controller for autonomous driving, then in a safe state, the autonomous driving function will be stopped, and only basic functions such as data acquisition will be retained.
[0049] In this embodiment, when the first verification result indicates that the verification passed and the second verification result indicates that the verification failed, in addition to sending the business data to the second hardware domain, the steps of generating backup data and verifying the backup data can be performed simultaneously. If a valid backup data is still not obtained after retrying, the target device can be made to run in a safe state, thereby reducing the security risks caused by failures in the first and second hardware domains.
[0050] In some alternative implementations, step 108 above may include: If the preset retry end time is reached at the current time and the most recent second verification result still indicates that the verification failed, a recovery failure prompt message is sent to the auxiliary processor so that the auxiliary processor can control the target device to enter a safe state.
[0051] The auxiliary processor can be located either inside or outside the target device. The auxiliary processor maintains communication with both the target device and the security domain executing this embodiment. If the conditions for stopping retry are met, the security domain executing this embodiment can send a recovery failure message to the auxiliary processor. The auxiliary processor can then send a command to the target device to enter a secure state. Upon receiving this command, the target device enters and runs in a secure state.
[0052] This embodiment, by setting up an auxiliary processor, can monitor the operation of the target device, reduce the task processing burden of the target device, enable the target device to focus on executing target business, and improve the stability of the target device's operation.
[0053] In some alternative implementations, after step 105, the method further includes: If the data transmission conditions are not met, switch the target device to safe operation mode.
[0054] The description of the target device and security status can be found in the above embodiments. When data transmission conditions are not met, neither normal business data nor backup data (preventing malfunctions of the target device) can be obtained normally. In this case, the target device is at risk of malfunction. The target device can be controlled to enter a secure operating state, thereby improving the timeliness of malfunction response and reducing the risk of target device failure.
[0055] In some alternative implementations, if the data transmission conditions are not met, the target device is switched to a secure operating state, including: If the data transmission conditions are not met, a first verification failure message is sent to the auxiliary processor so that the auxiliary processor can control the target device to enter a safe state.
[0056] For a description of the auxiliary processor, please refer to the above embodiments. In the event that the data transmission conditions are not met, the security domain executing this embodiment can send a first verification failure message to the auxiliary processor. After receiving the first verification failure message, the auxiliary processor can send a command to the target device to enter a secure state. Upon receiving the command, the target device enters a secure state and begins operation.
[0057] This embodiment enables the auxiliary processor to control the target device to enter a safe state when the data transmission conditions are not met. This allows the auxiliary processor to monitor the operation of the target device, enabling the target device to focus on executing target services and improving the stability of the target device's operation.
[0058] In some alternative implementations, the aforementioned security domain includes a backup subsystem, a verification subsystem, and a decision subsystem. The connection relationships between the backup subsystem, verification subsystem, and decision subsystem can be referenced below. Figure 4 The system architecture is shown. The backup subsystem, verification subsystem, and decision subsystem can be implemented in hardware (e.g., through hardware devices such as MCUs and DSPs) or as software modules.
[0059] Step 102 above includes: using the backup subsystem to parse business instructions and generate backup data.
[0060] The backup subsystem can receive business instructions, parse them, determine the type, amount, format, and other attributes of the business data required by the second hardware domain, and then generate the corresponding backup data.
[0061] Step 104 above includes: The verification subsystem is used to verify the business data and backup data respectively, and the first verification result and the second verification result are obtained.
[0062] The verification subsystem can be pre-configured with verification algorithms, which are used to verify business data and backup data separately.
[0063] Step 105 above includes: The decision subsystem is used to judge the first and second verification results to determine whether the current data transmission conditions are met.
[0064] Step 106 above includes: If the data transmission conditions are met, the decision subsystem uses the first and second verification results to determine the target data from the business data and backup data, and then sends the target data to the second hardware domain.
[0065] The decision subsystem can connect to the second hardware domain and send target data to the second hardware domain.
[0066] This embodiment implements the various functions of the security domain in a modular manner by having the backup subsystem, verification subsystem, and decision subsystem execute the steps of this method, which helps to improve the efficiency of the security domain in executing this method.
[0067] The methods of any embodiment of this disclosure can be implemented alone or in any combination without conflict. The specific implementation can be set according to actual needs, and this disclosure does not limit them.
[0068] Exemplary System Figure 3 An exemplary structural diagram of a data interaction system 300 provided in an embodiment of this disclosure is shown.
[0069] like Figure 3 As shown, the system 300 includes: a first hardware domain 301, a second hardware domain 302, and a security domain 303; the security domain is located on the communication link between the first hardware domain and the second hardware domain.
[0070] This data interaction system can be applied in various types of scenarios. In one example, it can be applied to a SoC chip in a vehicle, where different ASIL-level hardware domains are distributed, each handling different services. These hardware domains may be different modules or different subsystems. For example, the various processors, memories, and other hardware components within the SoC chip can each function as a separate hardware domain.
[0071] The aforementioned security domain can be implemented using various hardware modules. The implementation form of the security domain is not limited; for example, it can include dedicated hardware modules such as chips and circuits, or general-purpose devices such as computers and smartphones. This security domain is separated from the other hardware domains in the system architecture and can be an independent hardware subsystem, containing independent hardware, software, power supply, clock, and other components. In one example, if the data interaction system of this embodiment is applied to a SoC chip in a vehicle, this security domain can be implemented according to the highest ASIL level. Communication between the two hardware domains is monitored by the security domain.
[0072] The security domain is used to execute the data interaction methods described in the above method embodiments. The specific execution process can be found in the above method embodiments, and will not be repeated here.
[0073] The data interaction system provided in this disclosure enables the establishment of independent security domains between different hardware domains. These security domains back up and verify data transmitted between hardware domains, allowing for more flexible and efficient monitoring and protection of communication between them. This ensures that if one hardware domain experiences a problem, the backup data can enable the other hardware domain to continue operating normally, reducing the risk of system hardware and software failures caused by data transmission interruptions and improving the stability of hardware domain operation. Furthermore, this system is simple to implement, highly efficient in development, does not require virtual machines, has low hardware resource requirements, and can cover various fault types using backup data, making the solution highly versatile.
[0074] In some alternative implementations, such as Figure 4 As shown, the aforementioned security domain includes a backup subsystem 3031, a verification subsystem 3032, and a decision subsystem 3033. The backup subsystem can connect to the first hardware domain and / or the second hardware domain through the security domain's interface. As an example, Figure 4 The backup subsystem shown is connected to the first hardware domain via a first interface and can receive service commands sent by the first hardware domain. The aforementioned verification subsystem is connected to the backup subsystem and also to the first hardware domain via the first interface. The aforementioned decision subsystem is connected to both the backup and decision subsystems, and is connected to the first hardware domain via the first interface and to the second hardware domain via a second interface. The aforementioned backup, verification, and decision subsystems can be hardware (e.g., implemented using MCUs, DSPs, or other hardware devices) or software modules.
[0075] The backup subsystem is used for: Receive business instructions; based on the business instructions, generate backup data and send the backup data to the verification subsystem.
[0076] The aforementioned business instructions are instructions issued by the first hardware domain or the second hardware domain according to the needs of the business scenario. For example, if the first hardware domain is a DDR memory and the second hardware domain is a CPU, and the DDR memory needs to return a set of data to the CPU, then the business instruction can be a data read request instruction sent by the CPU. This instruction can contain information indicating the data type, format, and data volume.
[0077] The backup subsystem can parse business instructions to determine the type, volume, format, and other attributes of the business data required by the second hardware domain, and then generate corresponding backup data. Optionally, the values included in the backup data can be generated in any way, such as fixed preset values or randomly generated values.
[0078] The verification subsystem is used to: receive service data sent by the first hardware domain; verify the service data and backup data respectively, and obtain the first verification result and the second verification result.
[0079] The business data refers to the data provided by the first hardware domain to the second hardware domain under specific business scenarios. For example, the business data could be sensor data returned by the DDR memory of the first hardware domain in an autonomous driving scenario. The first verification result is the result of verifying the business data, and the second verification result is the result of verifying the backup data. The verification of the business data and backup data can be performed using any preset verification method. The purpose of the verification is to check whether the business data and backup data conform to the data protocol constraints under normal business scenarios. For example, for business data transmitted under preset bus protocol constraints, the received business data and backup data are checked for data volume, data format, etc., to determine whether they conform to the bus protocol constraints.
[0080] The decision subsystem is used for: Based on the first and second verification results, determine whether the current data transmission conditions are met; if the data transmission conditions are met, determine the target data from the business data and backup data based on the first and second verification results, and send the target data to the second hardware domain.
[0081] The data transmission conditions can be preset. For example, if at least one of the first and second verification results indicates that the verification passed, the data transmission conditions are determined to be met. If the data transmission conditions are met, the decision subsystem can select target data from business data and backup data according to a preset selection strategy, i.e., it can send either business data or backup data as the target data to the second hardware domain. This selection strategy can be preset according to actual needs. For example, if the first verification result indicates that the business data verification failed, the backup data can be sent as the target data to the second hardware domain.
[0082] This embodiment achieves modular implementation of various functions of the security domain by setting up a backup subsystem, a verification subsystem, and a decision subsystem in the security domain, with each subsystem executing its corresponding steps. This helps to improve the efficiency of data monitoring in the security domain.
[0083] Optionally, the decision subsystem described above is also used to: determine that the current data transmission conditions are met if at least one of the first verification result and the second verification result indicates that the verification has passed; If both the first and second verification results indicate that the verification failed, it is determined that the current data transmission conditions are not met.
[0084] Optionally, the decision subsystem described above is also used to: if the first verification result indicates that the verification passed and the second verification result indicates that the verification failed, determine the business data as the target data; If the first verification result indicates that the verification failed, and the second verification result indicates that the verification passed, the backup data is determined as the target data. If both the first and second verification results indicate that the verification passed, the business data will be identified as the target data.
[0085] In some alternative implementations, such as Figure 4 As shown, the system also includes an auxiliary processor 304, which is communicatively connected to the security domain. This auxiliary processor can be any type of electronic device with logic processing capabilities; for example, an MCU can be configured as the auxiliary processor.
[0086] The verification subsystem is also used to send a first verification failure message to the auxiliary processor when it is determined that the current data transmission conditions do not meet the preset conditions.
[0087] The auxiliary processor is used to: control the data interaction system to enter a secure state in response to receiving a first verification failure message.
[0088] like Figure 4 As shown, the first verification failure message is FAIL1. After receiving this first verification failure message, the auxiliary processor can send the aforementioned command to enter the secure state to the target device (e.g., SoC) where the data interaction system is located. After receiving the command, the target device can control the data interaction system and other components to enter the secure state for operation.
[0089] A data interaction system operating in a safe state may not perform tasks specific to the business scenario, but only retain basic functions. For example, if the data interaction system is installed on the controller performing autonomous driving, then in a safe state, the controller stops performing autonomous driving functions and only retains basic functions such as data acquisition.
[0090] This embodiment enables the auxiliary processor to control the system into a safe state when the data transmission conditions are not met. This allows the auxiliary processor to monitor the system's operation, enabling the system to focus on executing target business and improving the stability of system operation.
[0091] In some alternative implementations, the decision subsystem is also used for: If the first verification result indicates that the verification passed and the second verification result indicates that the verification failed, a second verification failure message is sent to the auxiliary processor (e.g., Figure 4 (FAIL2 shown).
[0092] The second verification failure message indicates that the business data is normal, but the backup data is abnormal, requiring a backup recovery. Optionally, the decision subsystem can connect to the auxiliary processor and send the second verification failure message directly to the auxiliary processor; alternatively, the verification subsystem can forward the second verification failure message to the auxiliary processor.
[0093] The auxiliary processor is also used to: send retry commands to the security domain according to a preset retry cycle, so that the backup subsystem can regenerate backup data, and to enable the verification subsystem to verify the regenerated backup data.
[0094] The retry period can be set according to actual needs, such as 1 second. Within each retry period, the auxiliary processor sends a retry command to the security domain once. This retry command can be sent to the backup subsystem and the verification subsystem via the interface between the auxiliary processor and the security domain. Upon receiving the retry command, the backup subsystem and the verification subsystem regenerate the backup data and verify it to obtain a new second verification result.
[0095] The decision subsystem is also used to: in response to the current time reaching the preset retry end time, and the most recent second verification result still indicating that the verification failed, send a recovery failure prompt message to the auxiliary processor.
[0096] The auxiliary processor is used to control the data interaction system to enter a safe state in response to receiving a recovery failure message.
[0097] The retry end time mentioned above refers to the time when the retry stop condition is met. This retry stop condition can be determined by setting parameters such as the maximum number of retries and the maximum retry duration. When the retry stop condition is met, the steps of generating backup data and verifying the backup data are stopped. If the most recently generated backup data still fails verification at the retry end time, it indicates that there is a risk of failure in the functions of the first and second hardware domains for the target service. For safety, a recovery failure prompt message can be sent to the auxiliary processor. The auxiliary processor switches the data interaction system to a safe operating state according to the method described in the above embodiment.
[0098] In this embodiment, when the first verification result indicates that the verification passed and the second verification result indicates that the verification failed, in addition to sending the business data to the second hardware domain, the auxiliary processor can also control the security domain to perform the steps of generating backup data and verifying the backup data. If a valid backup data is still not obtained after retrying, the system can run in a secure state, thereby reducing the security risks caused by system failure.
[0099] The exemplary embodiments of this system correspond to the exemplary methods described above in terms of implementation. The corresponding content of the two can be referenced, combined, and cited from each other. The beneficial technical effects of the exemplary embodiments of this system can be found in the corresponding beneficial technical effects of the exemplary methods described above, and will not be repeated here.
[0100] Exemplary device Figure 5 This is a schematic diagram of the structure of a data interaction device provided in an exemplary embodiment of this disclosure. This embodiment can be applied to electronic devices, such as... Figure 5 As shown, the data interaction device includes: The first receiving module 501 is used to receive service instructions; The generation module 502 is used to generate backup data based on business instructions; The second receiving module 503 is used to receive service data sent by the first hardware domain; The verification module 504 is used to verify the business data and backup data respectively, and obtain the first verification result and the second verification result. The determining module 505 is used to determine whether the current data transmission conditions are met based on the first verification result and the second verification result; The sending module 506 is used to determine the target data from the business data and backup data based on the first verification result and the second verification result if the data sending conditions are met, and then send the target data to the second hardware domain.
[0101] Reference Figure 6 , Figure 6This is a schematic diagram of the structure of a data interaction device provided in another exemplary embodiment of this disclosure.
[0102] In some optional implementations, the determining module 505 includes: a first determining unit 5051, used to determine that the current data transmission condition is met if at least one of the first verification result and the second verification result indicates that the verification has passed; and a second determining unit 5052, used to determine that the current data transmission condition is not met if both the first verification result and the second verification result indicate that the verification has failed.
[0103] In some optional implementations, the sending module 506 includes: a third determining unit 5061, configured to determine the business data as the target data if the first verification result indicates that the verification passed and the second verification result indicates that the verification failed; a fourth determining unit 5062, configured to determine the backup data as the target data if the first verification result indicates that the verification failed and the second verification result indicates that the verification passed; and a fifth determining unit 5063, configured to determine the business data as the target data if both the first verification result and the second verification result indicate that the verification passed.
[0104] In some optional implementations, the device further includes: a retry module 507, used to repeatedly execute the steps of generating backup data and verifying the backup data according to a preset retry cycle if the first verification result indicates that the verification passed and the second verification result indicates that the verification failed; and a first switching module 508, used to switch the target device to a safe state operation in response to the current time reaching a preset retry end time and the most recently obtained second verification result still indicating that the verification failed.
[0105] In some optional implementations, the first switching module 508 is further configured to: in response to the current time reaching a preset retry end time and the most recently obtained second verification result still indicating that the verification failed, send a recovery failure prompt message to the auxiliary processor so that the auxiliary processor controls the target device to enter a safe state.
[0106] In some alternative implementations, the device further includes a second switching module 509, used to switch the target device to a safe operating state if the data transmission conditions are not met.
[0107] In some optional implementations, the second switching module 509 is also used to: send a first verification failure message to the auxiliary processor if the data transmission conditions are not met, so that the auxiliary processor controls the target device to enter a safe state.
[0108] In some optional implementations, the security domain includes a backup subsystem, a verification subsystem, and a decision subsystem; the generation module 502 is further configured to: use the backup subsystem to parse business instructions and generate backup data; the verification module 504 is further configured to: use the verification subsystem to verify the business data and backup data respectively, and obtain a first verification result and a second verification result; the determination module 505 is further configured to: use the decision subsystem to judge the first verification result and the second verification result, and determine whether the current data transmission conditions are met; the transmission module 506 is further configured to: if the data transmission conditions are met, based on the first verification result and the second verification result, determine the target data from the business data and backup data, and send the target data to the second hardware domain.
[0109] The exemplary embodiments of this device correspond to the exemplary method section described above in terms of implementation. The corresponding content between the two can be referenced, combined, and cited, and will not be repeated here. The beneficial technical effects corresponding to the exemplary embodiments of this device can be found in the corresponding beneficial technical effects of the exemplary method section described above, and will not be repeated here.
[0110] Exemplary vehicle Figure 7 This is a schematic diagram of a vehicle 700 provided in an embodiment of the present disclosure. The vehicle 700 includes the data interaction system 300 described in the above embodiments. The data interaction system 300 can be applied to various hardware devices such as controllers and SoC chips in the vehicle.
[0111] The beneficial technical effects that the vehicle provided in this embodiment can achieve by applying the data interaction system can be found in the corresponding beneficial technical effects of the exemplary system section above, and will not be repeated here.
[0112] Exemplary electronic devices Figure 8 The present disclosure provides a structural diagram of an electronic device 800, which includes at least one processor 801 and a memory 802.
[0113] The processor 801 may be a central processing unit (CPU) or other form of processing unit with data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 800 to perform desired functions.
[0114] The memory 802 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. Volatile memory may include, for example, random access memory (RAM) and / or cache memory. Non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 801 may execute one or more computer program instructions to implement the data interaction methods and / or other desired functions of the various embodiments of this disclosure described above.
[0115] In one example, the electronic device 800 may also include an input device 803 and an output device 804, which are interconnected via a bus system and / or other forms of connection mechanism (not shown).
[0116] The input device 803 may also include, for example, a keyboard, a mouse, etc.
[0117] The output device 804 can output various information to the outside, including, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.
[0118] Of course, for the sake of simplicity, Figure 8 Only some of the components of the electronic device 800 relevant to this disclosure are shown, omitting components such as buses, input / output interfaces, etc. In addition, the electronic device 800 may include any other suitable components depending on the specific application.
[0119] Exemplary computer program products and computer-readable storage media In addition to the methods and apparatus described above, embodiments of this disclosure may also provide a computer program product, including computer program instructions that, when executed by a processor, cause the processor to perform the steps of the data interaction methods of the various embodiments of this disclosure described in the "Exemplary Methods" section above.
[0120] Computer program products can be written in any combination of one or more programming languages to perform the operations of embodiments of this disclosure. These programming languages include object-oriented programming languages such as Java and C++, as well as conventional procedural programming languages such as C or similar languages. The program code can be executed entirely on a user's computing device, partially on a user's computing device, as a standalone software package, partially on a user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.
[0121] Furthermore, embodiments of this disclosure may also be computer-readable storage media storing computer program instructions thereon, which, when executed by a processor, cause the processor to perform the steps of the data interaction methods of the various embodiments of this disclosure described in the "Exemplary Methods" section above.
[0122] Computer-readable storage media may take the form of any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may include, but is not limited to, systems, apparatuses, or devices that are electrical, magnetic, optical, electromagnetic, infrared, or semiconductor, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: electrical connections having one or more wires, portable disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0123] The basic principles of this disclosure have been described above with reference to specific embodiments. However, the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.
[0124] Various modifications and variations can be made to this disclosure without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this disclosure and their equivalents, this disclosure is also intended to include such modifications and variations.
Claims
1. A data interaction method applied to a security domain, the method comprising: Receive service instructions; Based on the aforementioned business instructions, backup data is generated; Receive service data sent by the first hardware domain; The business data and the backup data are verified respectively to obtain a first verification result and a second verification result; Based on the first verification result and the second verification result, determine whether the current data transmission conditions are met; If the data transmission conditions are met, target data is determined from the business data and the backup data based on the first verification result and the second verification result, and the target data is sent to the second hardware domain.
2. The method of claim 1, wherein, The step of determining whether the current data transmission conditions are met based on the first verification result and the second verification result includes: If at least one of the first verification result and the second verification result indicates that the verification is successful, it is determined that the current data transmission condition is met. If both the first and second verification results indicate that the verification failed, it is determined that the current data transmission conditions are not met.
3. The method of claim 2, wherein, The step of determining the target data from the business data and the backup data based on the first verification result and the second verification result includes: If the first verification result indicates that the verification passed, and the second verification result indicates that the verification failed, the business data is determined as the target data; If the first verification result indicates that the verification failed, and the second verification result indicates that the verification passed, the backup data is determined as the target data; If both the first verification result and the second verification result indicate that the verification is successful, the business data is determined as the target data.
4. The method of claim 3, wherein, After determining the target data from the business data and the backup data based on the first verification result and the second verification result, the method further includes: If the first verification result indicates that the verification passed and the second verification result indicates that the verification failed, the steps of generating the backup data and verifying the backup data are repeated according to the preset retry cycle. If the preset retry end time is reached at the current time and the most recent second verification result still indicates that the verification failed, the target device will be switched to safe operation.
5. The method of claim 4, wherein, The response occurs when the preset retry end time is reached at the current time, and the most recent second verification result still indicates that the verification failed. Switching the target device to a safe operating state includes: In response to the current time reaching the preset retry end time, and the most recent second verification result still indicating that the verification failed, a recovery failure prompt message is sent to the auxiliary processor so that the auxiliary processor controls the target device to enter a safe state.
6. The method of claim 1, wherein, After determining whether the preset data transmission conditions are met based on the first verification result and the second verification result, the method further includes: If the data transmission conditions are not met, the target device will be switched to a safe operating state.
7. The method of claim 6, wherein, If the data transmission conditions are not met, switching the target device to a secure operating state includes: If the data transmission conditions are not met, a first verification failure message is sent to the auxiliary processor so that the auxiliary processor controls the target device to enter a safe state.
8. The method of any one of claims 1-7, wherein, The security domain includes a backup subsystem, a verification subsystem, and a decision-making subsystem; The step of generating backup data based on the business instruction includes: using the backup subsystem to parse the business instruction and generate the backup data; The step of verifying the business data and the backup data respectively to obtain a first verification result and a second verification result includes: Using the verification subsystem, the business data and the backup data are verified respectively to obtain a first verification result and a second verification result; The step of determining whether the current data transmission conditions are met based on the first verification result and the second verification result; if the data transmission conditions are met, determining the target data from the service data and the backup data based on the first verification result and the second verification result, and sending the target data to the second hardware domain, includes: Using the decision subsystem, the first verification result and the second verification result are judged to determine whether the current data transmission condition is met. If the data transmission condition is met, the target data is determined from the business data and the backup data based on the first verification result and the second verification result, and the target data is sent to the second hardware domain.
9. A data interaction system comprising: First hardware domain, second hardware domain, security domain; The security domain is located on the communication link between the first hardware domain and the second hardware domain; The security domain is used to execute the data interaction method according to any one of claims 1-8.
10. The system of claim 9, wherein, The security domain includes a backup subsystem, a verification subsystem, and a decision-making subsystem; The backup subsystem is used for: Receive business instructions; generate backup data based on the business instructions, and send the backup data to the verification subsystem; The verification subsystem is used to: receive service data sent by the first hardware domain; verify the service data and the backup data respectively to obtain a first verification result and a second verification result; The decision subsystem is used for: Based on the first verification result and the second verification result, determine whether the current data transmission conditions are met; If the data transmission conditions are met, target data is determined from the business data and the backup data based on the first verification result and the second verification result, and the target data is sent to the second hardware domain.
11. The system of claim 10, wherein, The system also includes an auxiliary processor, which is communicatively connected to the security domain. The verification subsystem is also used to: send a first verification failure message to the auxiliary processor when it is determined that the current data transmission conditions do not meet the preset conditions; The auxiliary processor is used to: control the data interaction system to enter a secure state in response to receiving the first verification failure message.
12. The system of claim 11, wherein, The decision subsystem is also used for: If the first verification result indicates that the verification passed and the second verification result indicates that the verification failed, a second verification failure message is sent to the auxiliary processor; The auxiliary processor is also configured to: send a retry instruction to the security domain according to a preset retry cycle, so that the backup subsystem regenerates the backup data, and to enable the verification subsystem to verify the regenerated backup data; The decision subsystem is also used to: in response to the current time reaching the preset retry end time, and the most recently obtained second verification result still indicating that the verification failed, send a recovery failure prompt message to the auxiliary processor; The auxiliary processor is used to control the data interaction system to enter a safe state in response to receiving the recovery failure prompt information.
13. A data interaction device applied in a security domain, the device comprising: The first receiving module is used to receive service instructions; The generation module is used to generate backup data based on the business instructions; The second receiving module is used to receive service data sent by the first hardware domain; The verification module is used to verify the business data and the backup data respectively, and obtain a first verification result and a second verification result. The determining module is used to determine whether the current data transmission conditions are met based on the first verification result and the second verification result; The sending module is configured to, if the data sending conditions are met, determine target data from the business data and the backup data based on the first verification result and the second verification result, and send the target data to the second hardware domain.
14. A vehicle comprising the data interaction system according to any one of claims 9-12.
15. A computer-readable storage medium storing a computer program, which, when executed, implements the data interaction method according to any one of claims 1-8.
16. An electronic device, the electronic device comprising: processor; Memory used to store the processor's executable instructions; The processor is configured to read the executable instructions from the memory and execute the instructions to implement the data interaction method according to any one of claims 1-8.
