Distributed information security protection method and device of vehicle, vehicle and storage medium

Abstract

The invention relates to a distributed information safety protection method and device of a vehicle, the vehicle and a storage medium, the vehicle comprises a plurality of controllers, and corresponding safety protection processes are deployed for the plurality of controllers based on the characteristics of the controllers, and the method comprises the following steps: judging whether a preset safety event occurs in the vehicle; if the preset safety event occurs in the vehicle, determining a first target controller in which the preset safety event occurs from the plurality of controllers; and if the first target controller cannot independently process the preset security event, determining at least one auxiliary protection controller according to a security protection process corresponding to the first target controller, and performing security protection on the preset security event through the first target controller and the at least one auxiliary protection controller. Therefore, the problems of potential safety hazards and the like caused by high load of a single controller when the intelligent networked automobile encounters information security threats with large flow or more requests are solved, and the overall information security protection capability of the automobile is improved.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a distributed information security protection method, device, vehicle and storage medium for a vehicle. Background Art

[0002] As the degree of automobile networking increases, more and more parts have the function of connecting to Ethernet and in-vehicle communication. The parts involved in information security components in the networked parts often have different systems, different architectures, and uneven performance. As the functions of various controllers become more and more complex and intelligent, the information security risks are also increasing. Therefore, vehicle-side information security has become the focus of the industry.

[0003] In the related technologies, since the information security components involved in the networked components of intelligent connected vehicles have different systems, different architectures, and uneven performance, when conducting information security development, it is generally carried out with a single component.

[0004] However, if an information security attack with large traffic or many requests occurs, such as a denial-of-service (DoS) attack, the information security components of smart connected vehicles deployed on a single controller will most likely not be able to handle the processing power and load capacity. Especially during normal vehicle operation, if a single component fails or restarts due to high controller load, the risk is high and needs to be addressed urgently. Summary of the invention

[0005] The present application provides a distributed information security protection method, device, vehicle and storage medium for a vehicle to solve the security risks caused by the high load of a single controller when an intelligent connected vehicle encounters information security threats with large traffic or a large number of requests, thereby improving the overall information security protection capability of the vehicle.

[0006] In a first aspect, an embodiment of the present application provides a distributed information security protection method for a vehicle, wherein the vehicle includes multiple controllers, and corresponding security protection processes are deployed for the multiple controllers based on controller characteristics, wherein the method includes the following steps:

[0007] Determining whether a preset safety event occurs in the vehicle;

[0008] If the preset safety event occurs in the vehicle, determining a first target controller where the preset safety event occurs from the multiple controllers;

[0009] If the first target controller cannot handle the preset security event independently, at least one auxiliary protection controller is determined according to the security protection process corresponding to the first target controller, and security protection is performed on the preset security event through the first target controller and the at least one protection auxiliary controller.

[0010] Optionally, the security protection process is any one of the first to third security protection processes, wherein the first security protection process is deployed in a controller with a master control execution function, the second security protection process is deployed in a controller with a slave control execution function, and the third security protection process is deployed in a controller with a management and coordination function.

[0011] Optionally, the first target controller has a main control execution function, and the determining of at least one auxiliary protection controller according to the security protection process corresponding to the first target controller, and performing security protection on the preset security event through the first target controller and the at least one protection auxiliary controller, includes:

[0012] Reporting the preset security event to a second target controller having a management and coordination function, and waking up at least one third target controller having a slave execution function through the second target controller;

[0013] Performing task scheduling according to the allocatable resources of the at least one third target controller having a slave execution function, performing security protection on the preset security event according to the first task scheduling result, and determining whether the preset security event is in a released state through the first target controller;

[0014] If the preset security event is in a released state, the released state is reported to the second target controller, so that the second target controller performs a sleep operation based on the released state.

[0015] Optionally, the first target controller has a slave execution function, and the determining of at least one auxiliary protection controller according to the security protection process corresponding to the first target controller, and performing security protection on the preset security event through the first target controller and the at least one protection auxiliary controller, includes:

[0016] Reporting the preset security event to a fourth target controller having a master execution function, and determining whether the fourth target controller can independently handle the preset security event;

[0017] If the fourth target controller cannot handle the preset security event independently, the preset security event is reported to the fifth target controller with management and coordination function, and at least one sixth target controller with slave execution function is awakened through the fifth target controller;

[0018] Perform task scheduling according to the allocable resources of the at least one sixth target controller with a slave execution function, perform security protection on the preset security event according to the second task scheduling result, and determine whether the preset security event is in a lifted state through the first target controller;

[0019] If the preset security event is in a lifted state, report the lifted state to the fifth target controller, so that the fifth target controller performs a sleep operation based on the lifted state.

[0020] Optionally, the first target controller has a management and coordination function. Determining at least one auxiliary protection controller according to the security protection process corresponding to the first target controller, and performing security protection on the preset security event through the first target controller and the at least one auxiliary protection controller, including:

[0021] Report the preset security event to a seventh target controller with a master execution function, and determine whether the seventh target controller can handle the preset security event alone;

[0022] If the seventh target controller cannot handle the preset security event alone, wake up at least one eighth target controller with a slave execution function through the first target controller;

[0023] Perform task scheduling according to the allocable resources of the at least one eighth target controller with a slave execution function, perform security protection on the preset security event according to the third task scheduling result, and determine whether the preset security event is in a lifted state through the first target controller;

[0024] If the preset security event is in a lifted state, perform a sleep operation based on the lifted state through the first target controller.

[0025] Optionally, after performing security protection on the preset security event according to the current security protection process, it further includes:

[0026] Obtain the current task scheduling result, the current cooperative processing ability of each controller, the current cooperative storage ability of each controller, the current actual processing ability of each controller, and the current actual storage ability of each controller;

[0027] Send the current task scheduling result, the current cooperative processing ability of each controller, the current cooperative storage ability of each controller, the current actual processing ability of each controller, and the current actual storage ability of each controller to the target cloud;

[0028] Receive the software upgrade policy sent by the target cloud based on the current task scheduling result, the current cooperation processing capabilities of each controller, the current cooperation storage capabilities of each controller, the current actual processing capabilities of each controller, and the current actual storage capabilities of each controller;

[0029] Perform software upgrade operations on the software deployed inside the multiple controllers based on the software upgrade policy.

[0030] An embodiment of the second aspect of the present application provides a distributed information security protection device for a vehicle, including: The vehicle includes multiple controllers, and corresponding security protection processes are deployed for the multiple controllers respectively based on controller characteristics, including:

[0031] A judgment module, configured to judge whether a preset security event occurs in the vehicle;

[0032] A determination module, configured to, if the preset security event occurs in the vehicle, determine a first target controller that has the preset security event occur from the multiple controllers;

[0033] A protection module, configured to, if the first target controller cannot handle the preset security event alone, determine at least one auxiliary protection controller according to the security protection process corresponding to the first target controller, and perform security protection on the preset security event through the first target controller and the at least one protection auxiliary controller.

[0034] Optionally, the security protection process is any one of the first to third security protection processes, where the first security protection process is deployed on a controller with a main control execution function, the second security protection process is deployed on a controller with a slave control execution function, and the third security protection process is deployed on a controller with a management coordination function.

[0035] Optionally, the first target controller has a main control execution function, and the protection module is specifically configured to:

[0036] Report the preset security event to a second target controller with a management coordination function, and wake up at least one third target controller with a slave control execution function through the second target controller;

[0037] Perform task scheduling according to the allocable resources of the at least one third target controller with a slave control execution function, perform security protection on the preset security event according to the first task scheduling result, and judge whether the preset security event is in a lifted state through the first target controller;

[0038] If the preset security event is in a released state, report the released state to the second target controller, so that the second target controller performs a sleep operation based on the released state.

[0039] Optionally, the first target controller has a slave execution function, and the protection module is specifically used for:

[0040] Report the preset security event to a fourth target controller with a master execution function, and determine whether the fourth target controller can handle the preset security event alone;

[0041] If the fourth target controller cannot handle the preset security event alone, report the preset security event to a fifth target controller with a management and coordination function, and wake up at least one sixth target controller with a slave execution function through the fifth target controller;

[0042] Perform task scheduling according to the allocable resources of the at least one sixth target controller with a slave execution function, perform security protection on the preset security event according to the second task scheduling result, and determine whether the preset security event is in a released state through the first target controller;

[0043] If the preset security event is in a released state, report the released state to the fifth target controller, so that the fifth target controller performs a sleep operation based on the released state.

[0044] Optionally, the first target controller has a management and coordination function, and the protection module is specifically used for:

[0045] Report the preset security event to a seventh target controller with a master execution function, and determine whether the seventh target controller can handle the preset security event alone;

[0046] If the seventh target controller cannot handle the preset security event alone, wake up at least one eighth target controller with a slave execution function through the first target controller;

[0047] Perform task scheduling according to the allocable resources of the at least one eighth target controller with a slave execution function, perform security protection on the preset security event according to the third task scheduling result, and determine whether the preset security event is in a released state through the first target controller;

[0048] If the preset security event is in a released state, perform a sleep operation based on the released state through the first target controller.

[0049] Optionally, after protecting the preset security event according to the current security protection process, the protection module is further configured to:

[0050] Obtain the current task scheduling result, the current cooperation processing capacity of each controller, the current cooperation storage capacity of each controller, the current actual processing capacity of each controller, and the current actual storage capacity of each controller;

[0051] Send the current task scheduling result, the current cooperation processing capacity of each controller, the current cooperation storage capacity of each controller, the current actual processing capacity of each controller, and the current actual storage capacity of each controller to the target cloud;

[0052] Receive the software upgrade policy sent by the target cloud based on the current task scheduling result, the current cooperation processing capacity of each controller, the current cooperation storage capacity of each controller, the current actual processing capacity of each controller, and the current actual storage capacity of each controller;

[0053] Perform a software upgrade operation on the software deployed in the plurality of controllers based on the software upgrade policy.

[0054] An embodiment of the third aspect of the present application provides a vehicle, including: at least one processor; and a memory communicatively connected to the at least one processor; wherein, the memory stores instructions executable by the at least one processor, and the instructions are configured to execute the distributed information security protection method of the vehicle as described in the above embodiments.

[0055] An embodiment of the fourth aspect of the present application provides a computer-readable storage medium, on which a computer program is stored, and the program is executed by a processor to implement the distributed information security protection method of the vehicle as described in the above embodiments.

[0056] An embodiment of the fifth aspect of the present application provides a computer program product, the computer program product stores a computer program, and when the program is executed by a processor, it implements the distributed information security protection method of the vehicle as described in the above embodiments.

[0057] Accordingly, when a preset safety event occurs in the vehicle, a first target controller that has the preset safety event occur is determined from multiple controllers. At least one auxiliary protection controller is determined according to the safety protection process corresponding to the first target controller, and the preset safety event is protected by the first target controller and at least one protection auxiliary controller. Accordingly, corresponding protection policies are deployed for multiple controllers respectively based on the controller characteristics, so as to select the optimal safety protection process among multiple controllers for safety protection, solving the problems such as potential safety hazards caused by high load of a single controller when the intelligent connected vehicle encounters information security threats with large traffic or many requests, and improving the overall information security protection ability of the vehicle.

[0058] Additional aspects and advantages of the present application will be given in part in the following description, become apparent in part from the following description, or be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0060] Figure 1 is a flowchart of a distributed information security protection method for a vehicle according to an embodiment of the present application;

[0061] Figure 2 is a flowchart of a distributed information security protection method for a vehicle when the first target controller has a main control execution function according to an embodiment of the present application;

[0062] Figure 3 is a flowchart of a distributed information security protection method for a vehicle when the first target controller has a slave control execution function according to an embodiment of the present application;

[0063] Figure 4 is a flowchart of a distributed information security protection method for a vehicle when the first target controller has a management and coordination function according to an embodiment of the present application;

[0064] Figure 5 is a schematic diagram of a distributed information security protection device for a vehicle according to an embodiment of the present application;

[0065] Figure 6 is a schematic diagram of the structure of a vehicle according to an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0066] Embodiments of the present application will be described in detail below. Examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below by referring to the accompanying drawings are exemplary and are intended to explain the present application, but should not be construed as limiting the present application.

[0067] Before introducing the distributed information security protection method for vehicles in the embodiments of the present application, a distributed information security protection method for vehicles in the related art will be briefly introduced.

[0068] A vehicle networking information security protection system and method based on Tbox are disclosed in the related art. It uses security rules in a predefined security rule library to associate, analyze, and match stored data to generate an analysis result. The cloud server displays the analysis result and sends it to the in-vehicle Tbox, and realizes the linkage response of the security protection device at the vehicle terminal according to the analysis result. The abnormal data detected at the vehicle end is uploaded, and the policy rules are sent and updated on the security operation platform of the cloud server to ensure the information security protection of the vehicle.

[0069] A method and system for grading information security risks of automotive parts based on hybrid analysis are also disclosed in the related art. The method of graph theory is used to accurately reveal the dependency relationship between automotive parts. By grading the information security risks of automotive parts, it can ensure that resources and attention are concentrated on the most critical risk points, thereby achieving more efficient risk management.

[0070] However, both of the above two strategies have certain defects, as follows:

[0071] (1) The vehicle networking information security protection system and method based on Tbox almost entirely hand over the security protection process to the cloud server. For some relatively critical protection nodes, such as security rules and policy distribution, the vehicle does not take the initiative to control at all. This is mainly reflected in:

[0072] 1) Once the Tbox network connection is interrupted or the network environment is poor, each controller will lose the ability to initiate security protection, the normal operation of the vehicle and its own safety cannot be guaranteed, and almost all information security components will directly collapse.

[0073] 2) After the vehicle normally sends a dangerous message and receives a security policy, the security components still directly run in a single several controllers. Once the final conclusion drawn by the security policy exceeds the load of the controller, the controller will directly restart or malfunction, causing greater danger.

[0074] 3) Information security attacks are not sporadic attacks. Once encountering attacks such as flood access, a large number of requests are needed to the server, which is not only a test for the vehicle to request the network, but also if the cloud server system and network single bandwidth are occupied, then this security protection system will completely lose its effect.

[0075] (2) The method and system for grading information security risks of automotive parts based on hybrid analysis mainly link information security attacks to multiple controllers in the form of graph theory for the link of security risks, and analyze them with the concept of multiple controllers; however, it only serves as an analysis method to put forward corresponding security requirements for parts, and because it still focuses on the self-protection of a single controller, in the case of high-load information security protection, it will still cause the controller to restart or malfunction, thus causing greater danger.

[0076] This application precisely aims at the above problems and proposes a distributed information security protection method for vehicles. When a preset security event occurs in the vehicle, the first target controller where the preset security event occurs is determined from multiple controllers. When the first target controller cannot handle the preset security event alone, at least one auxiliary protection controller is determined according to the security protection process corresponding to the first target controller, and the preset security event is protected by the first target controller and at least one auxiliary protection controller. Thus, corresponding protection strategies are deployed for multiple controllers based on the controller characteristics, and the optimal security protection process is selected from multiple controllers for security protection, solving the problems such as security hazards caused by high load of a single controller when the intelligent connected vehicle encounters information security threats with large traffic or many requests, and improving the overall information security protection ability of the vehicle.

[0077] Specifically, Figure 1 It is a schematic flow chart of a distributed information security protection method for vehicles provided by an embodiment of this application.

[0078] In this embodiment, the vehicle includes multiple controllers, and corresponding security protection processes are deployed for multiple controllers based on the controller characteristics.

[0079] As Figure 1 shown, the distributed information security protection method for this vehicle includes the following steps:

[0080] In step S101, it is judged whether a preset security event occurs in the vehicle.

[0081] Among them, a preset security event refers to a specific situation or scenario that is preset or hypothesized based on currently known information security threat patterns and technical means and may pose a threat to the information security of intelligent connected vehicles, including but not limited to denial-of-service attacks, data tampering attacks, illegal access attempts, malware infections, and other types of cyberattacks, such as man-in-the-middle attacks, SQL injections, and various attacks on vehicle networks and systems.

[0082] Specifically, the security components on each controller continuously monitor their own operating status, network traffic, and other metrics that may indicate security threats. These security components may include collision sensors, smoke detectors, tire pressure sensors, etc. Once a controller detects an abnormal situation, such as receiving an abnormal data packet or a sudden significant drop in its processing capacity, it is considered that a preset security event has occurred.

[0083] In step S102, if a preset security event occurs in the vehicle, a first target controller that has the preset security event is determined from multiple controllers.

[0084] Among them, the first target controller refers to the controller that first identifies the existence of the preset security event when it detects that the vehicle has a preset security event.

[0085] Specifically, in the embodiments of the present application, by analyzing information such as timestamps, signal strengths, and logical relationships in the data, it is determined which controllers have shown abnormal behaviors or state changes before and after the preset security event occurs. Whichever controller first discovers the problem is the first target controller that needs to be prioritized for attention and handling. After initially determining the first target controller, further verification is required to ensure the accuracy of the judgment, which may include checking the historical records of the controller, conducting fault simulation experiments, etc. Through this process, the problem can be more accurately identified, and effective measures can be taken to ensure the safe operation of the vehicle.

[0086] In step S103, if the first target controller cannot handle the preset security event alone, at least one auxiliary protection controller is determined according to the security protection process corresponding to the first target controller, and the preset security event is protected by the first target controller and at least one auxiliary protection controller.

[0087] Specifically, when the first target controller cannot handle a preset security event alone, tasks are reasonably allocated to selected auxiliary protection controllers according to the current status (such as memory occupancy, processor load, etc.) and capabilities of each controller; for example, some controllers may be more suitable for handling computationally intensive tasks, while other controllers may be better at data storage and transmission; instructions are sent to the determined auxiliary protection controllers to wake up the security components and instruct them to participate in the handling of security events; the auxiliary protection controllers report their allocable resources to the first target controller for unified scheduling, and according to the arrangement of the first target controller, each controller starts to execute its respective tasks.

[0088] It should be noted that the embodiments of the present application can judge whether the controller where the Master, Slave or Manager software is located can handle security events independently based on multiple factors; the embodiments of the present application can be evaluated by memory occupancy (that is, the size of computer memory occupied by a program or system during operation). Before any security event occurs, the embodiments of the present application will record the initial memory usage of each controller. When a security event is detected, the corresponding software will evaluate the memory resources required to handle this event, and compare the relationship between the current remaining available memory and the memory required to handle the security event. If the remaining available memory is sufficient to support the handling of the event, it is considered that the controller can handle the security event independently.

[0089] Thus, the embodiments of the present application interconnect and issue tasks to each controller across systems and architectures through software for the information security events originally handled independently by each controller, so as to reduce the load on each controller when attacked, prevent problems caused by excessive load on a single controller, and at the same time will not affect the normal software operation of other controllers, thereby increasing the information security protection ability in the vehicle environment.

[0090] To facilitate those skilled in the art to further understand the distributed information security protection method of the vehicle in the embodiments of the present application, the following will describe in detail how to perform security protection on preset security events in combination with specific protection strategies.

[0091] Optionally, in some embodiments, the security protection process is any one of the first to third security protection processes, wherein the first security protection process is deployed on the controller with the main control execution function, the second security protection process is deployed on the controller with the slave control execution function, and the third security protection process is deployed on the controller with the management and coordination function.

[0092] It is understandable that the controller with the master execution function can be some controllers with fast processing speed, large storage and running space, and can accept a large number of requests and processing. The controller with the management and coordination function is generally the main processing or control unit of the whole vehicle; the controller with the slave execution function can be some controllers with poor storage space and processing speed, but the information security risk is high, and it is necessary to deploy corresponding information security components to deal with possible preset security events; the controller with the management and coordination function can be some controllers with strong connectivity and good communication capabilities in the whole vehicle. For example, the controller with the management and coordination function can be a communication controller such as Tbox. Among them, in order to facilitate the execution of the security protection process, the embodiment of the present application can deploy Master software in the controller with the master execution function, Slave software in the controller with the slave execution function, and Manager software in the controller with the management and coordination function. It should be noted that the above-mentioned Master software, Slave software and Manager software are only exemplary and are not intended to limit the present application. As long as the execution of the security protection process can be realized, it can be deployed in the corresponding controller. In order to avoid redundancy, it will not be described in detail here.

[0093] The following is a detailed description taking the example that the first target controller has a master control execution function, a slave control execution function, or a management and coordination function.

[0094] Optionally, in some embodiments, the first target controller has a master control execution function, determines at least one auxiliary protection controller according to the security protection process corresponding to the first target controller, and performs security protection on a preset security event through the first target controller and at least one protection auxiliary controller, including: reporting the preset security event to a second target controller with a management and coordination function, and waking up at least one third target controller with a slave control execution function through the second target controller; performing task scheduling according to the allocatable resources of at least one third target controller with a slave control execution function, and performing security protection on the preset security event according to the first task scheduling result, and judging whether the preset security event is in a released state through the first target controller; if the preset security event is in a released state, reporting the released state to the second target controller, so that the second target controller performs a sleep operation based on the released state.

[0095] It is understandable that after the first target controller detects a preset safety event and is unable to resolve it independently, it reports this situation to the second target controller with management and coordination functions. After receiving the report from the first target controller, the second target controller analyzes the status of each controller in the system. As needed, it wakes up at least one third target controller with slave control execution functions and instructs it to participate in the handling of the safety event. The third target controller reports its currently allocable resources to the second target controller. The second target controller performs task scheduling based on this information and reasonably allocates tasks to each participating third target controller. The first task scheduling result is to determine the specific tasks of each third target controller; the first target controller and at least one third target controller start to execute their respective tasks according to the task scheduling result. Each controller maintains communication, sharing the processing progress and status information in real time to ensure that all operations proceed normally; the first target controller continuously monitors the progress of the safety event handling and determines whether the preset safety event is in a resolved state. If any abnormality or problem is detected, it can request the second target controller to dynamically adjust the task allocation or increase resource support; when all tasks are completed, the first target controller determines whether the preset safety event has been successfully resolved. If it is confirmed that the safety event has been resolved, the first target controller reports the resolved state to the second target controller. After receiving the resolved state, the second target controller notifies all participating controllers to enter the sleep state and resume the normal operation mode.

[0096] For example, as Figure 2 shown, Figure 2A flowchart of a distributed information security protection method for a vehicle when the first target controller has a master execution function is provided for an embodiment of the present application. If a preset security event occurs in a controller where the Master software is deployed, the controller of the current Master software is the first target controller with a master execution function, and the Master software is first awakened by the security component of this controller; it needs to estimate whether the preset security event can be handled by this controller alone, and estimate the processing power or storage capacity required for processing. If it can, it directly processes and ends the preset security event; if it cannot be processed, the preset security event is reported to the controller where the Manager software is located; the controller where the Manager software is located wakes up the controllers where the Slave software is located after receiving the report; the Slave software reports the space and processing power in this controller that can be allocated to the preset security event processing to the controller where the Manager software is located; the controller where the Manager software is located processes the expected report according to the report from the controller where the Master software is located. The report is used to allocate and arrange tasks for the controllers where the Slave software is located; after the controller where the Slave software is located receives the task sent by the controller where the Manager software is located, it adapts the task to the system and architecture of the controller for processing; after the processing is completed, the controller where the Slave software is located returns the processing result to the controller where the Manager software is located, and the controller where the Manager software is located counts the processing results and sends them to the controller where the Master software is located after completion. The controller where the Master software is located confirms the release of the preset security event. If it is not released, the failed or incomplete task is returned to the controller where the Manager software is located for re-reporting; if it is confirmed that the event is released, it is reported to the controller where the Manager software is located; the controller where the Manager software is located puts each software into hibernation, and the preset security event of the controller where the Master is located ends.

[0097] Optionally, in some embodiments, the first target controller has a slave execution function, determines at least one auxiliary protection controller according to the security protection process corresponding to the first target controller, and performs security protection on a preset security event through the first target controller and at least one protection auxiliary controller, including: reporting the preset security event to a fourth target controller with a master execution function, and judging whether the fourth target controller can handle the preset security event independently; if the fourth target controller cannot handle the preset security event independently, reporting the preset security event to a fifth target controller with a management and coordination function, and waking up at least one sixth target controller with a slave execution function through the fifth target controller; performing task scheduling according to the allocatable resources of at least one sixth target controller with a slave execution function, and performing security protection on the preset security event according to the second task scheduling result, and judging whether the preset security event is in a released state through the first target controller; if the preset security event is in a released state, reporting the released state to the fifth target controller, so that the fifth target controller performs a sleep operation based on the released state.

[0098] It is understandable that after the first target controller detects a preset security event, if it cannot resolve the security event independently, it reports this situation to the fourth target controller with the main control execution function; after receiving the report from the first target controller, the fourth target controller evaluates its own resource status and processing capabilities to determine whether it can handle the security event alone; if it can handle it, the fourth target controller directly starts to handle the security event and notifies the first target controller to maintain the monitoring state; if it cannot handle it, the preset security event is further reported to the fifth target controller with the management and coordination function; the auxiliary protection controller, i.e., the fifth target controller, is awakened. After receiving the report from the fourth target controller, the fifth target controller analyzes the states of each controller in the system, selects a suitable auxiliary protection controller, and wakes up at least one sixth target controller with the slave control execution function as needed and instructs it to participate in the handling of the security event; the sixth target controller has the slave control execution function, and the sixth target controller reports its currently available resources to the fifth target controller. Based on this information, the fifth target controller performs task scheduling and reasonably allocates tasks to each participating sixth target controller; the second task scheduling result is to determine the specific tasks of each sixth target controller; the first target controller and at least one sixth target controller start to execute their respective tasks according to the task scheduling result; the first target controller continuously monitors the progress of the security event handling and determines whether the preset security event is in a resolved state; if any abnormality or problem is detected, it can request the fifth target controller to dynamically adjust the task allocation or increase resource support; after all tasks are completed, the first target controller determines whether the preset security event has been successfully resolved. If it is confirmed that the security event has been resolved, the first target controller reports the resolved state to the fifth target controller. After receiving the resolved state, the fifth target controller notifies all participating controllers to enter the sleep state and resume the normal operation mode.

[0099] For example, as Figure 3 shown, Figure 3The present invention provides a flowchart of a distributed information security protection method for a vehicle when the first target controller has a slave execution function according to an embodiment of the present application. If a preset security event occurs in a controller deployed by the Slave software, and the current Slave software is the first target controller with a slave execution function, the Slave software is first awakened by the security component of the controller, which needs to estimate whether the preset security event can be handled by the controller alone, and estimate the processing power or storage capacity required for processing. If it can be handled alone, the preset security event is directly processed and ended; if it cannot be handled alone, the preset security event is awakened and reported to the controller where the Master software is located, and the controller where the Master software is located determines whether the task reported by the controller where the Slave software is located can be solved alone, and estimates the resources that need to be coordinated; if it can be solved alone, it is directly solved. After the problem is solved, the result is returned to the controller where the Slave software is located. The controller where the Slave software is located ends the event after confirmation. If the problem cannot be solved alone or the controller where the Slave software is located confirms that there are still tasks for the preset security event, it will be reported to the controller where the Manager software is located. The controller where the Manager software is located wakes up the controllers where the other Slave software are located to cooperate in processing. After the controller where the Slave software is located confirms that the preset security event has not been resolved, the failed or unfinished task will be returned to the controller where the Manager software is located for re-reporting. If it has been resolved, the controller where the Manager software is located will hibernate all software, and the preset security event of the controller where the Slave is located will end.

[0100] Optionally, in some embodiments, the first target controller has a management and coordination function, determines at least one auxiliary protection controller according to the security protection process corresponding to the first target controller, and performs security protection on a preset security event through the first target controller and at least one protection auxiliary controller, including: reporting the preset security event to a seventh target controller with a master control execution function, and judging whether the seventh target controller can handle the preset security event independently; if the seventh target controller cannot handle the preset security event independently, waking up at least one eighth target controller with a slave control execution function through the first target controller; performing task scheduling according to the allocatable resources of at least one eighth target controller with a slave control execution function, and performing security protection on the preset security event according to the third task scheduling result, and judging whether the preset security event is in a released state through the first target controller; if the preset security event is in a released state, performing a sleep operation based on the released state through the first target controller.

[0101] It can be understood that after the first target controller detects a preset safety event, if it cannot resolve the safety event independently, it reports this situation to the seventh target controller with the main control execution function; after receiving the report from the first target controller, the seventh target controller evaluates its own resource status and processing capabilities to determine whether it can handle the safety event alone. If it can handle it, the seventh target controller directly starts to handle the safety event and notifies the first target controller to maintain the monitoring state; if it cannot handle it, it feeds back to the first target controller. The first target controller analyzes the states of each controller in the system and selects a suitable auxiliary protection controller; as needed, wakes up at least one eighth target controller with the slave control execution function and instructs it to participate in the handling of the safety event; the eighth target controller reports its currently allocable resources to the first target controller, and the first target controller performs task scheduling based on this information, reasonably allocating tasks to each participating eighth target controller. The third task scheduling result is to determine the specific tasks of each eighth target controller; the first target controller and at least one eighth target controller start to execute their respective tasks according to the task scheduling result; the first target controller continuously monitors the progress of handling the safety event and determines whether the preset safety event is in a resolved state; when all relevant tasks are completed, the first target controller determines whether the preset safety event has been successfully resolved; if it is confirmed that the safety event has been resolved, the first target controller notifies all participating controllers of the resolved state; the first target controller performs a sleep operation based on the resolved state.

[0102] As Figure 4 shown, Figure 4Flowchart of a distributed information security protection method for a vehicle when the first target controller has management and coordination functions; if a preset security event occurs in the controller where the Manager software is deployed, and the current Manager software is the first target controller with management and coordination functions, the Manager software is first awakened by the security component of this controller. It needs to predict whether this preset security event can be handled by this controller alone, and predict the processing capacity or storage capacity required for cooperation. If it can, it directly processes and ends this preset security event; if it cannot be handled alone, it wakes up and reports the preset security event to the controller where the Master software is located. The controller where the Master software is located makes a judgment on whether the task reported by the controller where the Manager software is located can be solved alone, and predicts the resources that need to be coordinated; if it can be solved alone, it directly solves it and returns the result to the controller where the Manager software is located. After the controller where the Manager software is located confirms, the event ends; if it cannot be solved alone or the controller where the Manager software is located confirms that there are still tasks in the preset security event, it wakes up the controllers where each Slave software is located to cooperate in processing; the controller where the Manager software is located sorts out and confirms the end of the preset security event; if it is not lifted, it returns the failed or uncompleted task to the controllers where each Slave software is located to cooperate in processing; if it has been lifted, then the controller where the Manager software is located puts each software to sleep. Thus, the preset security event of the controller where the Manager is located ends.

[0103] It should be noted that the embodiment of the present application selects an appropriate security protection process to protect the preset security event. After the preset security event ends, the embodiment of the present application reports relevant data information to the target cloud to upgrade the software, so as to improve the security protection ability of the embodiment of the present application.

[0104] Optionally, in some embodiments, after protecting the preset security event according to the current security protection process, it further includes: obtaining the current task scheduling result, the current cooperation processing capacity of each controller, the current cooperation storage capacity of each controller, the current actual processing capacity of each controller, and the current actual storage capacity of each controller; sending the current task scheduling result, the current cooperation processing capacity of each controller, the current cooperation storage capacity of each controller, the current actual processing capacity of each controller, and the current actual storage capacity of each controller to the target cloud; receiving the software upgrade policy sent by the target cloud based on the current task scheduling result, the current cooperation processing capacity of each controller, the current cooperation storage capacity of each controller, the current actual processing capacity of each controller, and the current actual storage capacity of each controller; performing software upgrade operations on the software deployed inside multiple controllers based on the software upgrade policy.

[0105] Specifically, the orchestration ability of the controller where the Manager software is located mainly relies on the update of the cloud software. After each preset security event occurs and is resolved, the controller where the Manager software is located regularly sends reports to the cloud. The cloud judges whether the orchestration effect of the controller where the Manager software is located is reasonable this time, and through technologies such as digital twins, simulates the most suitable solution multiple times to update the software. The controller where the Manger software is located will not only update the orchestration ability, but also upload the estimated processing or storage capabilities that each software reports to be required for cooperation and the actual processing or storage capabilities used to the cloud after each preset security event is completed. The cloud upgrades the software's estimated capabilities to effectively improve the analysis capabilities of each software.

[0106] Furthermore, after processing the vehicle's preset security event, by comprehensively obtaining the current task orchestration result and the cooperation, actual processing, and storage capabilities of each controller and uploading this information to the target cloud, the vehicle system can achieve more accurate status assessment and resource optimization; the software upgrade strategy formulated by the cloud based on these data can specifically improve the stability, performance, and security of the vehicle system, which not only helps prevent potential security risks and system failures, but also optimizes the user experience, reduces maintenance costs, and enhances the competitiveness of the vehicle in the market.

[0107] Thus, the embodiment of the present application realizes the distributed information security protection of the vehicle through the software orchestration part, the preset security event processing, and the vehicle-cloud interaction part. It should be noted that the software orchestration part is a necessary prerequisite for the embodiment of the present application, the preset security event processing part is the key part of concern in the embodiment of the present application, and the vehicle-cloud interaction part is an effective supplement to the preset security event processing solution.

[0108] According to the vehicle's distributed information security protection method proposed by the embodiment of the present application, when a preset security event occurs in the vehicle, the embodiment of the present application determines the first target controller that has the preset security event from multiple controllers, determines at least one auxiliary protection controller according to the security protection process corresponding to the first target controller, and performs security protection on the preset security event through the first target controller and at least one protection auxiliary controller. Thus, corresponding protection strategies are deployed for multiple controllers based on the controller characteristics, so as to select the optimal security protection process among multiple controllers for security protection, solving problems such as security hazards caused by high load of a single controller when the intelligent connected vehicle encounters information security threats with large traffic or many requests, and improving the overall information security protection ability of the vehicle.

[0109] Next, a vehicle's distributed information security protection device proposed according to the embodiment of the present application will be described with reference to the accompanying drawings.

[0110] Figure 5 It is a block diagram of a distributed information security protection device for a vehicle according to an embodiment of the present application.

[0111] As Figure 5 shown, the vehicle includes a plurality of controllers, and corresponding security protection processes are deployed for the plurality of controllers based on controller characteristics. The distributed information security protection device 10 of the vehicle includes: a judgment module 100, a determination module 200, and a protection module 300.

[0112] Among them, the judgment module 100 is used to judge whether a preset security event occurs in the vehicle;

[0113] The determination module 200 is used to, if a preset security event occurs in the vehicle, determine a first target controller that has a preset security event from the plurality of controllers;

[0114] The protection module 300 is used to, if the first target controller cannot handle the preset security event alone, determine at least one auxiliary protection controller according to the security protection process corresponding to the first target controller, and perform security protection on the preset security event through the first target controller and at least one protection auxiliary controller.

[0115] Optionally, in some embodiments, the security protection process is any one of the first to third security protection processes. Among them, the first security protection process is deployed on a controller with a main control execution function, the second security protection process is deployed on a controller with a slave control execution function, and the third security protection process is deployed on a controller with a management and coordination function.

[0116] Optionally, in some embodiments, the first target controller has a main control execution function. The protection module 300 is specifically used to: report the preset security event to a second target controller with a management and coordination function, and wake up at least one third target controller with a slave control execution function through the second target controller; perform task scheduling according to the allocable resources of at least one third target controller with a slave control execution function, and perform security protection on the preset security event according to the first task scheduling result, and judge whether the preset security event is in a released state through the first target controller; if the preset security event is in a released state, report the released state to the second target controller, so that the second target controller performs a sleep operation based on the released state.

[0117] Optionally, in some embodiments, the first target controller has a slave execution function. The protection module 300 is specifically configured to: report a preset security event to a fourth target controller with a master execution function, and determine whether the fourth target controller can handle the preset security event alone; if the fourth target controller cannot handle the preset security event alone, report the preset security event to a fifth target controller with a management and coordination function, and wake up at least one sixth target controller with a slave execution function through the fifth target controller; perform task scheduling according to the allocable resources of at least one sixth target controller with a slave execution function, perform security protection on the preset security event according to the second task scheduling result, and determine whether the preset security event is in a resolved state through the first target controller; if the preset security event is in a resolved state, report the resolved state to the fifth target controller, so that the fifth target controller performs a sleep operation based on the resolved state.

[0118] Optionally, in some embodiments, the first target controller has a management and coordination function. The protection module 300 is specifically configured to: report a preset security event to a seventh target controller with a master execution function, and determine whether the seventh target controller can handle the preset security event alone; if the seventh target controller cannot handle the preset security event alone, wake up at least one eighth target controller with a slave execution function through the first target controller; perform task scheduling according to the allocable resources of at least one eighth target controller with a slave execution function, perform security protection on the preset security event according to the third task scheduling result, and determine whether the preset security event is in a resolved state through the first target controller; if the preset security event is in a resolved state, perform a sleep operation based on the resolved state through the first target controller.

[0119] Optionally, in some embodiments, after performing security protection on the preset security event according to the current security protection process, the protection module 300 is further configured to: obtain the current task scheduling result, the current cooperation processing capabilities of each controller, the current cooperation storage capabilities of each controller, the current actual processing capabilities of each controller, and the current actual storage capabilities of each controller; send the current task scheduling result, the current cooperation processing capabilities of each controller, the current cooperation storage capabilities of each controller, the current actual processing capabilities of each controller, and the current actual storage capabilities of each controller to the target cloud; receive a software upgrade policy sent by the target cloud based on the current task scheduling result, the current cooperation processing capabilities of each controller, the current cooperation storage capabilities of each controller, the current actual processing capabilities of each controller, and the current actual storage capabilities of each controller; perform a software upgrade operation on the software deployed in the multiple controllers based on the software upgrade policy.

[0120] It should be noted that the foregoing explanation of the embodiments of the distributed information security protection method for vehicles also applies to the distributed information security protection device for vehicles in this embodiment, and will not be elaborated here.

[0121] According to the distributed information security protection device for vehicles provided by the embodiments of the present application, when a preset security event occurs in the vehicle, the embodiments of the present application determine a first target controller that has a preset security event from multiple controllers, determine at least one auxiliary protection controller according to the security protection process corresponding to the first target controller, and perform security protection on the preset security event through the first target controller and at least one protection auxiliary controller. Thus, corresponding protection policies are deployed for multiple controllers based on the controller characteristics, so as to select the optimal security protection process among multiple controllers for security protection, solve the problems such as security risks caused by high load of a single controller when the intelligent connected vehicle encounters information security threats with large traffic or many requests, and improve the overall information security protection ability of the vehicle.

[0122] Figure 6 It is a schematic structural diagram of the vehicle provided by the embodiments of the present application. The vehicle may include:

[0123] A memory 601, a processor 602, and a computer program stored on the memory 601 and executable on the processor 602.

[0124] When the processor 602 executes the program, it implements the distributed information security protection method for vehicles provided in the foregoing embodiments.

[0125] Further, the vehicle further includes:

[0126] A communication interface 603 for communication between the memory 601 and the processor 602.

[0127] The memory 601 is used to store a computer program executable on the processor 602.

[0128] The memory 601 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory.

[0129] If the memory 601, the processor 602, and the communication interface 603 are implemented independently, the communication interface 603, the memory 601, and the processor 602 can be interconnected through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 only a thick line is used to represent it in Figure 6 , but it does not mean that there is only one bus or one type of bus.

[0130] Optionally, in specific implementation, if the memory 601, the processor 602, and the communication interface 603 are integrated on a chip, the memory 601, the processor 602, and the communication interface 603 can communicate with each other through an internal interface.

[0131] The processor 602 may be a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application.

[0132] The embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored, and when the program is executed by a processor, the distributed information security protection method of the vehicle as described above is implemented.

[0133] The embodiments of the present application also provide a computer program product, the computer program product stores a computer program, and when the program is executed by a processor, the distributed information security protection method of the vehicle as described above is implemented.

[0134] In the description of this specification, the descriptions referring to terms such as "one embodiment", "some embodiments", "example", "specific example", or "some examples" mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of this application. In this specification, the schematic expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in any one or N embodiments or examples in a suitable manner. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0135] In addition, the terms "first" and "second" are used for descriptive purposes only and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of these features. In the description of this application, the meaning of "N" is at least two, such as two, three, etc., unless otherwise specifically defined.

[0136] Any process or method description shown in the flowchart or described in other ways herein can be understood to represent a module, segment, or portion of code including one or more N executable instructions for implementing a customized logical function or process. And the scope of the preferred embodiments of this application includes additional implementations, where the functions can be executed in a substantially simultaneous manner or in the reverse order according to the involved functions, rather than in the order shown or discussed, which should be understood by those skilled in the art to which the embodiments of this application belong.

[0137] It should be understood that each part of this application can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware as in another embodiment, any one or a combination of the following techniques well known in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

[0138] Those of ordinary skill in the technical field of this application can understand that all or part of the steps carried by the methods of the above embodiments can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. When the program is executed, it includes one or a combination of the steps of the method embodiments.

Claims

1. A distributed information security protection method for a vehicle, characterized in that: The vehicle includes a plurality of controllers, and corresponding safety protection processes are respectively deployed for the plurality of controllers based on controller characteristics, wherein the method includes the following steps: Determining whether a preset safety event occurs in the vehicle; If the preset safety event occurs in the vehicle, determining a first target controller where the preset safety event occurs from the multiple controllers; If the first target controller cannot handle the preset security event alone, at least one auxiliary protection controller is determined according to the security protection process corresponding to the first target controller, and security protection is performed on the preset security event through the first target controller and the at least one protection auxiliary controller.

2. The method according to claim 1, characterized in that The security protection process is any one of the first to third security protection processes, wherein the first security protection process is deployed in a controller with a master control execution function, the second security protection process is deployed in a controller with a slave control execution function, and the third security protection process is deployed in a controller with a management and coordination function.

3. The method according to claim 2, characterized in that The first target controller has a main control execution function, and the at least one auxiliary protection controller is determined according to the security protection process corresponding to the first target controller, and the preset security event is protected by the first target controller and the at least one protection auxiliary controller, including: Reporting the preset security event to a second target controller having a management and coordination function, and waking up at least one third target controller having a slave execution function through the second target controller; Performing task scheduling according to the allocatable resources of the at least one third target controller having a slave execution function, performing security protection on the preset security event according to the first task scheduling result, and determining whether the preset security event is in a released state through the first target controller; If the preset security event is in a released state, the released state is reported to the second target controller, so that the second target controller performs a sleep operation based on the released state.

4. The method according to claim 2, characterized in that: The first target controller has a slave execution function, the at least one auxiliary protection controller is determined according to the security protection process corresponding to the first target controller, and the preset security event is protected by the first target controller and the at least one protection auxiliary controller, including: Reporting the preset security event to a fourth target controller having a master execution function, and determining whether the fourth target controller can independently handle the preset security event; If the fourth target controller cannot handle the preset security event independently, the preset security event is reported to the fifth target controller with management and coordination function, and at least one sixth target controller with slave execution function is awakened through the fifth target controller; Performing task scheduling according to the allocatable resources of the at least one sixth target controller having a slave execution function, performing security protection on the preset security event according to the second task scheduling result, and determining whether the preset security event is in a released state through the first target controller; If the preset security event is in a released state, the released state is reported to the fifth target controller, so that the fifth target controller performs a sleep operation based on the released state.

5. The method according to claim 2, characterized in that: The first target controller has a management and coordination function, and the at least one auxiliary protection controller is determined according to the security protection process corresponding to the first target controller, and the preset security event is protected by the first target controller and the at least one protection auxiliary controller, including: Reporting the preset security event to a seventh target controller having a master execution function, and determining whether the seventh target controller can independently handle the preset security event; If the seventh target controller cannot process the preset security event independently, waking up at least one eighth target controller having a slave execution function through the first target controller; Performing task scheduling according to the allocatable resources of the at least one eighth target controller having a slave execution function, performing security protection on the preset security event according to the third task scheduling result, and determining whether the preset security event is in a released state through the first target controller; If the preset security event is in a released state, a sleep operation is performed based on the released state by the first target controller.

6. The method according to any one of claims 1 to 5, characterized in that After performing security protection on the preset security event according to the current security protection process, the method further includes: Obtain the current task scheduling result, the current coordinated processing capacity of each controller, the current coordinated storage capacity of each controller, the current actual processing capacity of each controller, and the current actual storage capacity of each controller; Sending the current task scheduling result, the current coordinated processing capacity of each controller, the current coordinated storage capacity of each controller, the current actual processing capacity of each controller, and the current actual storage capacity of each controller to the target cloud; Receiving a software upgrade policy sent by the target cloud based on the current task orchestration result, the current coordinated processing capability of each controller, the current coordinated storage capability of each controller, the current actual processing capability of each controller, and the current actual storage capability of each controller; The software deployed in the multiple controllers is upgraded based on the software upgrade policy.

7. A distributed information security protection device for a vehicle, characterized in that: The vehicle includes a plurality of controllers, and corresponding safety protection processes are deployed for the plurality of controllers based on the characteristics of the controllers, including: A judgment module, used to judge whether a preset safety event occurs in the vehicle; a determination module, configured to determine, if the preset safety event occurs in the vehicle, a first target controller where the preset safety event occurs from among the multiple controllers; A protection module is used to determine at least one auxiliary protection controller according to the security protection process corresponding to the first target controller if the first target controller cannot handle the preset security event independently, and to perform security protection for the preset security event through the first target controller and the at least one protection auxiliary controller.

8. A vehicle, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the distributed information security protection method for a vehicle as described in any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: The program is executed by a processor to implement a distributed information security protection method for a vehicle as described in any one of claims 1 to 6.

10. A computer program product, wherein the computer program product stores a computer program, characterized in that: When the program is executed by a processor, a distributed information security protection method for a vehicle as described in any one of claims 1 to 6 is implemented.

Images