Vehicle vulnerability fixing method and related apparatus

Abstract

The present application provides a vehicle vulnerability fixing method and a related apparatus, and is applied to the technical field of vehicle control. According to embodiments of the present application, part and component information of a vehicle can be obtained, and vulnerability detection can be performed on the vehicle; when there is a vulnerability, a suggested upgrade time is determined at least on the basis of a vulnerability rating of the vulnerability and a safety influence level of the vulnerability on the vehicle, and information of the vulnerability and the suggested upgrade time are sent to the vehicle and / or a terminal device, so that a vehicle owner can obtain the vulnerability information and the preferred upgrade time in time, which is convenient for the vehicle owner to plan a time of vehicle upgrade, vulnerability fixing can be performed as soon as possible, the vulnerability fixing efficiency can be improved, the controllability of the vehicle upgrade fixing process is improved, the participation of the user is improved, and the user experience is improved.

Description

Vehicle vulnerability repair method and related device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on December 25, 2023, with application number 202311809189.4 and invention name “Vehicle Vulnerability Repair Method and Related Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of vehicle control technology, and in particular to a vehicle vulnerability repair method and related devices. Background Art

[0003] With the rapid development of intelligent connected vehicles (ICVs), vehicles are becoming increasingly intelligent and connected, transforming them into true intelligent terminals in the era of the Internet of Everything. As in-vehicle terminal systems become increasingly complex and software code grows in length, various vulnerabilities inevitably arise. If exploited by hackers, these vulnerabilities pose significant security risks to ICVs.

[0004] To mitigate security risks, these vulnerabilities need to be fixed promptly. Some solutions rely on manual repair methods. After discovering a vulnerability, they manually search online for patches, then modify the source code, perform manual repairs, and perform testing. This results in a relatively low vulnerability repair efficiency.

[0005] Therefore, there is an urgent need for an efficient method that is suitable for the characteristics of the automotive industry and can improve the efficiency of vulnerability repair. Summary of the Invention

[0006] The present application provides a vehicle vulnerability repair method and related devices, which can obtain vehicle component information and perform vulnerability detection on the vehicle. When a vulnerability exists, the recommended upgrade time is determined based on at least the vulnerability level of the vulnerability and the security impact level of the vulnerability on the vehicle, and the vulnerability information and recommended upgrade time are sent to the vehicle and / or terminal device, thereby improving the efficiency of vulnerability repair, improving the controllability of the vehicle upgrade repair process, increasing user participation, and enhancing user experience.

[0007] In a first aspect, the present application provides a vehicle vulnerability repair method, the method comprising:

[0008] Acquiring vehicle component information, wherein the component information includes information about a first component;

[0009] Performing vulnerability detection on the vehicle based on component information of the vehicle;

[0010] In the case where the first component has a first vulnerability, determining a recommended upgrade time based at least on a vulnerability level of the first vulnerability and a safety impact level of the first vulnerability on the vehicle;

[0011] The information about the first vulnerability and the recommended upgrade time are sent to the vehicle and / or a first terminal, where the first terminal is associated with the vehicle.

[0012] The present application can perform vulnerability detection on the vehicle based on the vehicle's component information. When a vulnerability exists, the application can determine the recommended upgrade time based on at least the vulnerability level of the vulnerability and the security impact level of the vulnerability on the vehicle, and send the vulnerability information and the recommended upgrade time to the vehicle and / or terminal device, so that the vehicle owner can obtain the vulnerability information and the preferred upgrade time in a timely manner, which is convenient for the vehicle owner to plan the time for vehicle upgrades and repair the vulnerabilities as soon as possible. This can improve the efficiency of vulnerability repair, improve the controllability of the vehicle upgrade repair process, increase user participation, and enhance user experience.

[0013] In a possible implementation of the first aspect, determining the recommended upgrade time at least based on the vulnerability level of the first vulnerability and the security impact level of the first vulnerability on the vehicle includes: determining the recommended upgrade time based on the vulnerability level of the first vulnerability, the security impact level of the first vulnerability on the vehicle and current status information of the vehicle.

[0014] In another possible implementation of the first aspect, the current status information of the vehicle includes one or more of the vehicle model, vehicle component information, vehicle performance, vehicle driving status, current remaining power of the vehicle, and current signal status of the vehicle.

[0015] In this way, by combining multiple influencing factors to determine the recommended upgrade time, the optimal upgrade time can be determined, which is convenient for car owners to plan the time for vehicle upgrades, so as to repair vulnerabilities as soon as possible, improve the efficiency of vulnerability repair, and improve the controllability of the vehicle upgrade repair process, thereby increasing user participation and improving user experience.

[0016] In another possible implementation of the first aspect, the recommended upgrade time is the recommended time to upgrade the first component, and the information of the first vulnerability includes one or more of the vulnerability level of the first vulnerability, the vulnerability impact of the first vulnerability, and the recommended repair operations for the first vulnerability.

[0017] In this way, information related to the vulnerability is sent to the user, so that the user can obtain the vulnerability information of the vehicle in a timely manner, thereby increasing user participation and improving user experience.

[0018] In another possible implementation of the first aspect, the interval between the recommended upgrade time and the current moment is negatively correlated with the vulnerability level of the first vulnerability, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle.

[0019] In this way, the higher the level of the vulnerability, the greater the harm of the vulnerability, and the more quickly the vehicle needs to be upgraded to fix the vulnerability.

[0020] In another possible implementation of the first aspect, the method further includes: obtaining a vulnerability score of the first vulnerability based on the information about the first vulnerability, and determining a vulnerability level of the first vulnerability based on the vulnerability score of the first vulnerability.

[0021] In another possible implementation of the first aspect, the method further includes: receiving an upgrade instruction selected by the user, and sending an upgrade package for the first component to the vehicle when the upgrade instruction indicates that the user selects an immediate upgrade or when the user selects an upgrade at a recommended upgrade time. When the upgrade instruction indicates that the user selects a delayed upgrade, determining a recommended reminder time interval based on the vulnerability level of the first vulnerability, the security impact level of the first vulnerability on the vehicle, and the current status information of the vehicle, wherein the recommended reminder time interval is a time interval for recommending reminders to the user to upgrade the first component, and sending information about the first vulnerability and a re-determined recommended upgrade time to the vehicle and / or the first terminal based on the recommended reminder time interval. The upgrade instruction is used to indicate the time selected by the user to upgrade the first component.

[0022] In this way, users can flexibly choose whether to upgrade at the recommended upgrade time. If the user chooses to delay the upgrade, the user can be reminded to upgrade the vehicle according to the recommended reminder time interval, which is convenient for car owners to plan the time for vehicle upgrades and thus repair vulnerabilities as soon as possible. This can improve the efficiency of vulnerability repair, increase user autonomy and user participation, and enhance user experience.

[0023] In another possible implementation of the first aspect, the method further includes: determining a security impact level of the first vulnerability on the vehicle based on information of components affected by the first vulnerability and the difficulty of implementing a vulnerability attack on the vehicle through the first vulnerability.

[0024] In this way, the security impact level of the vulnerability on the vehicle is determined, and combined with the vehicle's usage scenario, the accuracy of the determined recommended upgrade time can be improved.

[0025] In another possible implementation of the first aspect, the method further includes: receiving a log of the vehicle, detecting the log of the vehicle, and if there is an abnormality in the log of the vehicle, sending a first message to the vehicle and / or the first terminal, wherein the first message is used to instruct a user to initiate a vulnerability detection instruction.

[0026] In another possible implementation of the first aspect, the method further includes: receiving a vulnerability detection instruction from the vehicle and / or the first terminal, and performing vulnerability detection on the vehicle based on the component information of the vehicle includes: performing vulnerability detection on the vehicle in response to the vulnerability detection instruction.

[0027] In this way, users are supported to actively initiate vulnerability detection commands at any time to perform vulnerability detection on the vehicle, which can improve the controllability of the vehicle upgrade and repair process, increase user participation, and enhance user experience.

[0028] In another possible implementation of the first aspect, the method further includes: receiving authorization information from the first terminal, receiving a vulnerability detection instruction from the second terminal, sending the first vulnerability information and the recommended upgrade time to the first terminal, receiving second information from the first terminal, the second information being used to instruct the second terminal to perform a vehicle upgrade operation, sending the first vulnerability information and the recommended upgrade time to the second terminal, and receiving the upgrade instruction from the second terminal. The authorization information is used to instruct the first terminal to authorize the second terminal to perform the vehicle upgrade operation, and the second terminal is an authorized terminal of the vehicle owner.

[0029] In this way, when the car owner is inconvenient or unfamiliar with the vehicle upgrade operation, the car owner can authorize his family members or trusted people to perform the vehicle upgrade operation, which is convenient for the user to repair the vehicle vulnerabilities in time, and can realize the authorized safety care of the vehicle, which can improve the controllability of the vehicle upgrade and repair process, increase user participation, and enhance user experience.

[0030] In a second aspect, an embodiment of the present application provides a vehicle vulnerability repair method, the method comprising:

[0031] Sending vehicle component information, wherein the component information includes information about the first component;

[0032] receiving information about a first vulnerability and a recommended upgrade time, where the first vulnerability is a vulnerability existing in the first component;

[0033] Receive an upgrade package for the first component from a server, and upgrade the first component.

[0034] In a possible implementation of the second aspect, the recommended upgrade time is related to a vulnerability level of the first vulnerability, a security impact level of the first vulnerability on the vehicle, and status information of the vehicle.

[0035] In another possible implementation of the second aspect, the current status information of the vehicle includes one or more of the vehicle model, vehicle component information, vehicle performance, vehicle driving status, current remaining power of the vehicle, and current signal status of the vehicle.

[0036] In another possible implementation of the second aspect, the interval between the recommended upgrade time and the current moment is negatively correlated with the vulnerability level of the first vulnerability, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle.

[0037] In yet another possible implementation of the second aspect, the vulnerability level of the first vulnerability is related to a vulnerability score of the first vulnerability, and the vulnerability score of the first vulnerability is related to information about the first vulnerability.

[0038] In another possible implementation of the second aspect, the method further includes: receiving an upgrade instruction selected by a user, and sending the upgrade instruction to a server, wherein the upgrade instruction is used to indicate a time selected by the user for upgrading the first component.

[0039] In yet another possible implementation of the second aspect, the method further includes: sending a log of the vehicle, where the log of the vehicle is used to determine an operating condition of the vehicle.

[0040] In another possible implementation of the second aspect, the method further includes: receiving a vulnerability detection instruction from a user, and sending the vulnerability detection instruction to a server, where the vulnerability detection instruction is used to instruct the server to perform vulnerability detection on the vehicle.

[0041] In a third aspect, an embodiment of the present application provides a vehicle vulnerability repair method, the method comprising:

[0042] receiving information about a first vulnerability and a recommended upgrade time, wherein the first vulnerability is a vulnerability existing in a first component of the vehicle;

[0043] receiving an upgrade instruction selected by a user, wherein the upgrade instruction is used to indicate a time selected by the user to upgrade the first component;

[0044] Send the upgrade instruction to the server.

[0045] In a possible implementation of the third aspect, the recommended upgrade time is related to a vulnerability level of the first vulnerability, a security impact level of the first vulnerability on the vehicle, and status information of the vehicle.

[0046] In another possible implementation of the third aspect, the current status information of the vehicle includes one or more of the vehicle model, component information of the vehicle, performance of the vehicle, driving status of the vehicle, current remaining power of the vehicle, and current signal status of the vehicle.

[0047] In another possible implementation of the third aspect, the interval between the recommended upgrade time and the current moment is negatively correlated with the vulnerability level of the first vulnerability, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle.

[0048] In yet another possible implementation of the third aspect, the vulnerability level of the first vulnerability is related to a vulnerability score of the first vulnerability, and the vulnerability score of the first vulnerability is related to information about the first vulnerability.

[0049] In another possible implementation of the third aspect, the method further includes: receiving first information from a server, where the first information is used to instruct the user to initiate a vulnerability detection instruction.

[0050] In another possible implementation of the third aspect, the method further includes: receiving a vulnerability detection instruction from a user, and sending the vulnerability detection instruction to a server, where the vulnerability detection instruction is used to instruct the server to perform vulnerability detection on the vehicle.

[0051] In another possible implementation of the third aspect, the method further includes: sending authorization information to a server, receiving an upgrade instruction selected by a user, and sending the upgrade instruction to the server, wherein the upgrade instruction indicates a time selected by the user for upgrading the first component. The authorization information indicates that the first terminal authorizes a second terminal to perform a vehicle upgrade operation, where the second terminal is an authorized terminal of the vehicle owner.

[0052] In another possible implementation of the third aspect, the method further includes: sending authorization information to the server, and sending second information to the server, wherein the authorization information indicates that the first terminal authorizes the second terminal to perform a vehicle upgrade operation, the second terminal being an authorized terminal of the vehicle owner, and the second information indicates that the second terminal is to perform the vehicle upgrade operation.

[0053] In a fourth aspect, an embodiment of the present application provides a vehicle upgrade device, which includes a communication unit and a processing unit. The communication unit is used to obtain vehicle component information, where the component information includes information about a first component, and to send information about the first vulnerability and the recommended upgrade time to the vehicle and / or a first terminal, where the first terminal is associated with the vehicle.

[0054] The processing unit is configured to perform vulnerability detection on the vehicle based on the component information of the vehicle, and when a first vulnerability exists in the first component, determine a recommended upgrade time based at least on a vulnerability level of the first vulnerability and a security impact level of the first vulnerability on the vehicle.

[0055] In a possible implementation of the fourth aspect, the processing unit is further used to determine a recommended upgrade time based on the vulnerability level of the first vulnerability, the security impact level of the first vulnerability on the vehicle, and the current status information of the vehicle.

[0056] In another possible implementation of the fourth aspect, the current status information of the vehicle includes one or more of the vehicle model, component information of the vehicle, performance of the vehicle, driving status of the vehicle, current remaining power of the vehicle, and current signal status of the vehicle.

[0057] In another possible implementation of the fourth aspect, the recommended upgrade time is the recommended time to upgrade the first component, and the information of the first vulnerability includes one or more of the vulnerability level of the first vulnerability, the vulnerability impact of the first vulnerability, and the recommended repair operations for the first vulnerability.

[0058] In another possible implementation of the fourth aspect, the interval between the recommended upgrade time and the current moment is negatively correlated with the vulnerability level of the first vulnerability, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle.

[0059] In another possible implementation of the fourth aspect, the processing unit is further configured to obtain a vulnerability score of the first vulnerability based on the information of the first vulnerability, and determine a vulnerability level of the first vulnerability based on the vulnerability score of the first vulnerability.

[0060] In another possible implementation of the fourth aspect, the communication unit is further used to receive an upgrade instruction selected by the user, wherein the upgrade instruction is used to indicate the time selected by the user to upgrade the first component. When the upgrade instruction indicates that the user selects to upgrade immediately or the user selects to upgrade at the recommended upgrade time, the upgrade package of the first component is sent to the vehicle, and according to the recommended reminder time interval, the information of the first vulnerability and the re-determined recommended upgrade time are sent to the vehicle and / or the first terminal.

[0061] The processing unit is further configured to determine a recommended reminder time interval based on the vulnerability level of the first vulnerability, the security impact level of the first vulnerability on the vehicle, and the current status information of the vehicle when the upgrade instruction instructs the user to choose to delay the upgrade. The recommended reminder time interval is the time interval for recommending that the user upgrade the first component.

[0062] In another possible implementation of the fourth aspect, the processing unit is further used to determine the security impact level of the first vulnerability on the vehicle based on information of components affected by the first vulnerability and the difficulty of implementing a vulnerability attack on the vehicle through the first vulnerability.

[0063] In another possible implementation of the fourth aspect, the communication unit is further configured to receive a log of the vehicle and, if an abnormality is found in the vehicle log, send a first message to the vehicle and / or the first terminal, the first message instructing a user to initiate a vulnerability detection instruction. The processing unit is further configured to detect the vehicle log.

[0064] In another possible implementation of the fourth aspect, the communication unit is further used to receive a vulnerability detection instruction from the vehicle and / or the first terminal, and the processing unit is further used to perform vulnerability detection on the vehicle in response to the vulnerability detection instruction.

[0065] In another possible implementation of the fourth aspect, the communication unit is further configured to receive authorization information from the first terminal, receive a vulnerability detection instruction from the second terminal, send the first vulnerability information and the recommended upgrade time to the first terminal, receive second information from the first terminal, send the first vulnerability information and the recommended upgrade time to the second terminal, and receive an upgrade instruction from the second terminal. The authorization information indicates that the first terminal authorizes the second terminal to perform a vehicle upgrade operation, the second terminal being an authorized terminal of the vehicle owner, and the second information indicates that the second terminal is to perform the vehicle upgrade operation.

[0066] In a fifth aspect, an embodiment of the present application provides a vehicle upgrade device, comprising a communication unit and a processing unit. The communication unit is configured to transmit vehicle component information, the component information including information about a first component; receive information about a first vulnerability existing in the first component and a recommended upgrade time; and receive an upgrade package for the first component from a server. The processing unit is configured to upgrade the first component.

[0067] In a possible implementation of the fifth aspect, the recommended upgrade time is related to the vulnerability level of the first vulnerability, the security impact level of the first vulnerability on the vehicle, and the status information of the vehicle.

[0068] In another possible implementation of the fifth aspect, the current status information of the vehicle includes one or more of the vehicle model, vehicle component information, vehicle performance, vehicle driving status, current remaining power of the vehicle, and current signal status of the vehicle.

[0069] In another possible implementation of the fifth aspect, the interval between the recommended upgrade time and the current moment is negatively correlated with the vulnerability level of the first vulnerability, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle.

[0070] In yet another possible implementation of the fifth aspect, the vulnerability level of the first vulnerability is related to a vulnerability score of the first vulnerability, and the vulnerability score of the first vulnerability is related to information about the first vulnerability.

[0071] In another possible implementation of the fifth aspect, the communication unit is further configured to receive an upgrade instruction selected by a user, where the upgrade instruction is used to indicate a time selected by the user to upgrade the first component, and send the upgrade instruction to a server.

[0072] In another possible implementation of the fifth aspect, the communication unit is further used to send a log of the vehicle, and the log of the vehicle is used to determine the operating status of the vehicle.

[0073] In another possible implementation of the fifth aspect, the communication unit is further configured to receive a vulnerability detection instruction from a user, where the vulnerability detection instruction is configured to instruct a server to perform a vulnerability detection on the vehicle and send the vulnerability detection instruction to the server.

[0074] In a sixth aspect, an embodiment of the present application provides a vehicle upgrade device, comprising a communication unit, wherein the communication unit is configured to receive information about a first vulnerability and a recommended upgrade time, wherein the first vulnerability is a vulnerability existing in a first component of the vehicle, receive an upgrade instruction selected by a user, and wherein the upgrade instruction is configured to indicate the time selected by the user to upgrade the first component, and send the upgrade instruction to a server.

[0075] In a possible implementation of the sixth aspect, the recommended upgrade time is related to the vulnerability level of the first vulnerability, the security impact level of the first vulnerability on the vehicle, and the status information of the vehicle.

[0076] In another possible implementation of the sixth aspect, the current status information of the vehicle includes one or more of the vehicle model, vehicle component information, vehicle performance, vehicle driving status, current remaining power of the vehicle, and current signal status of the vehicle.

[0077] In another possible implementation of the sixth aspect, the interval between the recommended upgrade time and the current moment is negatively correlated with the vulnerability level of the first vulnerability, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle.

[0078] In yet another possible implementation of the sixth aspect, the vulnerability level of the first vulnerability is related to a vulnerability score of the first vulnerability, and the vulnerability score of the first vulnerability is related to information about the first vulnerability.

[0079] In another possible implementation of the sixth aspect, the communication unit is further used to receive first information from a server, where the first information is used to instruct a user to initiate a vulnerability detection instruction.

[0080] In another possible implementation of the sixth aspect, the communication unit is further used to receive a vulnerability detection instruction from a user, where the vulnerability detection instruction is used to instruct the server to perform a vulnerability detection on the vehicle and send the vulnerability detection instruction to the server.

[0081] In yet another possible implementation of the sixth aspect, the communication unit is further configured to send authorization information to the server, receive an upgrade instruction selected by the user, and send the upgrade instruction to the server. The upgrade instruction indicates a user-selected time for upgrading the first component, and the authorization information indicates that the first terminal authorizes a second terminal to perform the vehicle upgrade operation, where the second terminal is an authorized terminal of the vehicle owner.

[0082] In yet another possible implementation of the sixth aspect, the communication unit is further configured to send authorization information to the server and to send second information to the server, wherein the authorization information indicates that the first terminal authorizes the second terminal to perform a vehicle upgrade operation, the second terminal being an authorized terminal of the vehicle owner, and the second information indicates that the second terminal is to perform the vehicle upgrade operation.

[0083] In a seventh aspect, an embodiment of the present application provides a server, comprising a processor and a memory, wherein the processor executes instructions stored in the memory so that the server implements the method described in any one of the first aspects above.

[0084] Optionally, the server further includes a communication interface, wherein the communication interface is used to receive and / or send data, and / or the communication interface is used to provide input and / or output for the processor.

[0085] It should be noted that the above embodiments are described using a processor (or general-purpose processor) that executes a method by calling a computer instruction. In specific implementations, the processor may also be a dedicated processor, in which case the computer instructions are pre-loaded into the processor. Alternatively, the processor may include both a dedicated processor and a general-purpose processor.

[0086] Optionally, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0087] In an eighth aspect, an embodiment of the present application provides a vehicle, comprising a processor and a memory, wherein the processor executes instructions stored in the memory so that the vehicle implements the method described in any one of the second aspects above.

[0088] Optionally, the vehicle further includes a communication interface, wherein the communication interface is used to receive and / or send data, and / or the communication interface is used to provide input and / or output for the processor.

[0089] It should be noted that the above embodiments are described using a processor (or general-purpose processor) that executes a method by calling a computer instruction. In specific implementations, the processor may also be a dedicated processor, in which case the computer instructions are pre-loaded into the processor. Alternatively, the processor may include both a dedicated processor and a general-purpose processor.

[0090] Optionally, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0091] In the ninth aspect, an embodiment of the present application provides a terminal device, which includes a processor and a memory, and the processor executes instructions stored in the memory so that the terminal device implements the method described in any one of the third aspects above.

[0092] Optionally, the terminal device further includes a communication interface, wherein the communication interface is used to receive and / or send data, and / or the communication interface is used to provide input and / or output for the processor.

[0093] It should be noted that the above embodiments are described using a processor (or general-purpose processor) that executes a method by calling a computer instruction. In specific implementations, the processor may also be a dedicated processor, in which case the computer instructions are pre-loaded into the processor. Alternatively, the processor may include both a dedicated processor and a general-purpose processor.

[0094] Optionally, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.

[0095] In the tenth aspect, an embodiment of the present application provides a computer-readable storage medium, in which instructions are stored. When the instructions are executed by a server, the server implements the method described in any one of the first aspects; when the instructions are executed by a vehicle, the vehicle implements the method described in any one of the second aspects; when the instructions are executed by a terminal device, the terminal device implements the method described in any one of the third aspects.

[0096] In the eleventh aspect, the present application provides a computer program product, which includes computer instructions. When the computer instructions are executed by a server, the server implements the method described in any one of the first aspects; when the computer instructions are executed by a vehicle, the vehicle implements the method described in any one of the second aspects; when the computer instructions are executed by a terminal device, the terminal device implements the method described in any one of the third aspects.

[0097] Optionally, the computer program product may be a software installation package or an image file. When the aforementioned method is required, the computer program product may be obtained and executed on a computing device.

[0098] The beneficial effects of the technical solutions provided in the second to eleventh aspects of this application can refer to the beneficial effects of the technical solution in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0099] The following is a brief introduction to the drawings required for describing the embodiments.

[0100] FIG1 is a schematic diagram of the architecture of a vehicle upgrade system provided by an embodiment of the present application;

[0101] FIG2 is a schematic diagram of a cloud provided by an embodiment of the present application;

[0102] FIG3 is a flow chart of a control method provided in an embodiment of the present application;

[0103] FIG4 is a schematic diagram of another vehicle vulnerability repair method provided in an embodiment of the present application;

[0104] FIG5 is a schematic diagram of another vehicle vulnerability repair method provided in an embodiment of the present application;

[0105] FIG6 is a schematic structural diagram of a vehicle upgrading device provided in an embodiment of the present application;

[0106] FIG7 is a schematic structural diagram of another vehicle upgrading device provided in an embodiment of the present application;

[0107] FIG8 is a schematic structural diagram of another vehicle upgrading device provided in an embodiment of the present application;

[0108] FIG9 is a schematic diagram of the structure of a server provided in an embodiment of the present application;

[0109] FIG10 is a schematic structural diagram of a vehicle provided in an embodiment of the present application;

[0110] FIG11 is a schematic structural diagram of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0111] The embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0112] The following is an introduction to the system architecture used in the embodiments of this application. It should be noted that the system architecture and business scenarios described in this application are intended to more clearly illustrate the technical solutions of this application and do not constitute a limitation on the technical solutions provided by this application. It is understood by those skilled in the art that with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided by this application are equally applicable to similar technical problems.

[0113] Please refer to Figure 1, which is a schematic diagram of the architecture of a vehicle upgrade system provided in an embodiment of the present application. As shown in Figure 1, the vehicle upgrade system includes a server 101, a vehicle 102 and a terminal device 103.

[0114] Server 101 is a device with centralized computing capabilities. Optionally, server 101 can be a physical device such as a server or host, or a virtual device such as a virtual machine or container. Optionally, server 101 can also be a cloud-based device, such as a single service in the cloud or a server cluster composed of multiple servers, or a local device, such as a single local service or a server cluster composed of multiple servers. Exemplarily, server 101 can perform vulnerability detection on vehicle 102 based on component information of vehicle 102. As another example, server 101 can also determine a recommended upgrade time based on at least the vulnerability level of the first vulnerability and the security impact level of the first vulnerability on the vehicle when a first vulnerability exists in a first component of vehicle 102.

[0115] Furthermore, the server 101 may also have communication capabilities. For example, the server 101 may communicate with the vehicle 102, sending information to the vehicle 102 and / or receiving information from the vehicle 102. For example, the server 101 may obtain component information of the vehicle 102, and send information about a first vulnerability and a recommended upgrade time to the vehicle 102. As another example, the server 101 may communicate with the terminal device 103, sending information to the terminal device 103 and / or receiving information from the terminal device 103. For example, the server 101 may receive a vulnerability detection instruction from the terminal device 103 and perform vulnerability detection on the vehicle 102. As another example, the server 101 may also send information about a first vulnerability and a recommended upgrade time to the vehicle 102 and / or the terminal device 103.

[0116] The vehicle 102 is a device capable of traveling. For example, the vehicle 102 includes but is not limited to vehicles of different models such as cars, trucks, buses, vans, electric vehicles, etc.

[0117] Furthermore, vehicle 102 may also have communication capabilities. For example, vehicle 102 may communicate with server 101, sending information to server 101 and / or receiving information from server 101. For example, vehicle 102 may send component information of vehicle 102 to server 101, and receive information about a first vulnerability and a recommended upgrade time from server 101. For another example, vehicle 102 may send a vulnerability detection instruction to server 101, instructing server 101 to perform vulnerability detection on vehicle 102. For another example, vehicle 102 may receive an upgrade package for a first component from the server. Furthermore, vehicle 102 may also have processing capabilities. For example, vehicle 102 may upgrade the first component based on the upgrade package for the first component.

[0118] The terminal device 103, also referred to as user equipment (UE) in some embodiments, is a device with communication capabilities. Exemplarily, the terminal device 103 can send information to the server 101 and / or receive information from the server 101. For example, the terminal device 103 can send an upgrade instruction to the server 101, where the upgrade instruction is used to indicate the time selected by the user to upgrade the first component. As another example, the terminal device 103 can send a vulnerability detection instruction to the server 101 and receive information about the first vulnerability and the recommended upgrade time from the server 101. Optionally, the terminal device 103 can interact with the user, such as presenting a user interface or receiving user input operations. For example, the terminal device 103 can receive an upgrade instruction selected by the user. Exemplarily, the terminal device 103 includes, but is not limited to, a handheld terminal, a wearable device, an entertainment device, a transportation device, etc. Among them, a handheld device includes, for example, a mobile phone, a tablet computer, a laptop computer, or a police communication device. A wearable device includes, for example, a smart bracelet, a smart watch, or smart glasses.

[0119] In one possible implementation, the server 101 establishes a communication connection with the vehicle 102 and the terminal device 103. The communication connection link may include one or more types of connection media, including a wired link (e.g., optical fiber), a wireless link, or a combination of a wired link and a wireless link. For example, the connection medium may be a wireless link, and the wireless link adopts a short-range connection technology, such as 802.11b / g technology, Bluetooth technology, ZigBee technology, radio frequency identification (RFID) technology, ultra-wideband (UWB) technology, wireless short-range communication (e.g., vehicle-mounted wireless short-range communication) technology, or vehicle-to-everything (V2X) technology. For another example, the wireless link adopts a long-range connection technology, such as global system for mobile communications (GSM), general packet radio service (GPRS), universal mobile telecommunications system (UMTS), LTE, or 5G wireless access type technology.

[0120] Optionally, the terminal device 103 may also communicate with the vehicle 102. For example, the vehicle 102 may send information such as the vehicle's vulnerability detection results to the terminal device 103. For another example, the terminal device 103 may send information such as vulnerability detection instructions or upgrade instructions to the vehicle 102.

[0121] In one possible implementation, server 101 is a cloud-based system. See Figure 2, which is a schematic diagram of a cloud-based system provided in an embodiment of the present application. As shown in Figure 2, the cloud-based system includes a software vulnerability center, a vehicle equipment software repository, and a vehicle safety operations system. Furthermore, the cloud-based system also includes a full vehicle asset library and a vehicle owner information system. The software vulnerability center has vulnerability detection capabilities, capable of detecting vulnerabilities. For example, the cloud-based system can automatically obtain open source software vulnerability announcements and vulnerability intelligence, save them to the software vulnerability center after manual review, and provide software vulnerability scanning services. The vehicle equipment software library is used to store information about software that can be installed on vehicles. For example, after a piece of software is developed, information such as the software installation package and upgrade package can be directly stored in the vehicle equipment software library. The full vehicle asset library is used to store information about vehicles and the versions of software installed on the devices, enabling vehicle lifecycle management. For example, after obtaining vehicle component information, the acquired vehicle component information is directly entered into the vehicle equipment software library. The vehicle owner information system manages vehicle owner information and supports operations such as logging in, receiving text messages, and receiving application notifications. The vehicle security operations system is used to manage the entire vehicle asset library, the vehicle owner information system, the software vulnerability center, and the vehicle equipment software warehouse. Furthermore, the cloud can also include a vehicle docking service, which is used to communicate with the vehicle, obtain component information from the vehicle, transmit the component information to the vehicle security operations center, receive first vulnerability information and recommended upgrade time from the vehicle security operations center, and send the first vulnerability information and recommended upgrade time to the vehicle.

[0122] The following describes the scenarios of the embodiments of the present application.

[0123] In some scenarios, as cars become increasingly intelligent and connected, software will become the core differentiator for smart cars. However, while these various software components create rich, tangible value and a brand-new driving experience for car owners, they also increase the complexity of the vehicle-side software systems. Complex software systems include various open source components, which may contain vulnerabilities and are susceptible to attacks and exploitation, posing significant risks to the property and life safety of car owners. To protect users' property and mitigate security risks, these open source component vulnerabilities must be promptly patched.

[0124] In some solutions, after a vulnerability is discovered through manual repair methods, people manually search for relevant patches online, then modify the source code, and perform manual repair and testing. The efficiency of vulnerability repair is relatively low.

[0125] In view of this, the embodiments of the present application provide a vehicle vulnerability repair method and related devices, which can obtain vehicle component information and perform vulnerability detection on the vehicle. When a vulnerability exists, the recommended upgrade time is determined based on at least the vulnerability level of the vulnerability, and the vulnerability information and recommended upgrade time are sent to the vehicle, so that the device software vulnerabilities throughout the entire life cycle of all vehicles can be perceived by the vehicle owner, the repair process can be controlled, and security supervision can be authorized. It can improve the efficiency of vulnerability repair, and improve the controllability of the vehicle upgrade repair process, increase user participation, and enhance user experience.

[0126] The embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0127] Please refer to Figure 3, which is a flow chart of a control method provided by an embodiment of the present application. Optionally, the method can be applied to a vehicle upgrade system, such as the vehicle upgrade system shown in Figure 1.

[0128] The control method shown in Figure 3 may include multiple steps from step S301 to step S307. It should be understood that for the convenience of description, this application describes the steps from step S301 to step S307 in this order, and is not intended to limit the execution to the above order. The embodiment of this application does not limit the order of execution, execution time, number of executions, etc. of the above one or more steps. Steps S301 to step S307 are as follows:

[0129] Step S301: The vehicle sends vehicle component information to the server.

[0130] Correspondingly, the server receives the vehicle parts information sent by the vehicle.

[0131] A vehicle is a device with travel and communication capabilities provided in embodiments of the present application. Examples of such devices include, but are not limited to, cars, trucks, buses, vans, electric vehicles, and other vehicles of various types. A server is a device with computing and communication capabilities provided in embodiments of the present application. Examples of such servers include the cloud.

[0132] In one possible implementation, a communication connection is established between the vehicle and the server. For the communication connection, see the relevant description above. Exemplarily, the vehicle can send information to the server through vehicle to everything (V2X) technology, for example, sending vehicle component information to the server. The component information includes device information on the vehicle and software information installed on the device, such as the name of the software and the currently installed software version information. Exemplarily, the component information includes information about the first component, for example, the component information includes information about the software version currently installed on the first component.

[0133] In a possible implementation, the vehicle may periodically send the vehicle parts information to the server. For example, the vehicle may send the vehicle parts information to the server every day, every two days, or every week.

[0134] Step S302: The server performs vulnerability detection on the vehicle based on the vehicle's component information.

[0135] The following describes a possible way for a server to perform vulnerability detection.

[0136] In one possible implementation, after receiving vehicle component information, the server retrieves the corresponding software package based on the component information. Exemplarily, the component information includes the currently installed software version of a first component. For example, if the first component currently has version A1 of software A installed, the server can retrieve the software package for version A1 of software A based on the currently installed software version information. Alternatively, the server can retrieve the corresponding software package from the vehicle equipment software repository shown in Figure 2.

[0137] Furthermore, the server performs vulnerability detection on the vehicle by analyzing the corresponding software package. For example, the server analyzes the software package of version A1 of software A and obtains a list of open source software used by the software package of version A1. The server can analyze whether the open source software list contains vulnerabilities based on the software vulnerability center shown in Figure 2. Optionally, the software vulnerability center can include a vulnerability library for storing the latest information on software with vulnerabilities. The server can analyze whether the first component contains a vulnerability based on the vulnerability library. For example, the vulnerability library includes version A1 of software A, indicating that version A1 of software A has a vulnerability. The server obtains the component information of the vehicle and obtains the version package of version A1 of software A based on the component information. The server analyzes the version package and determines that the vulnerability library contains version A1 of software A. Therefore, the server determines that version A1 of software A has a vulnerability.

[0138] Step S303: When the first component has a first vulnerability, the server determines a recommended upgrade time based at least on the vulnerability level of the first vulnerability and the safety impact level of the first vulnerability on the vehicle.

[0139] The recommended upgrade time is the time when the user is recommended to upgrade the first component.

[0140] Several possible implementations of how the server determines the recommended upgrade time are described below.

[0141] In the first implementation mode, when a first vulnerability exists in a first component, the server determines a recommended upgrade time based at least on the vulnerability level of the first vulnerability. The vulnerability level of the first vulnerability is related to the vulnerability score of the first vulnerability, and the vulnerability score of the first vulnerability is related to the information of the first vulnerability. Exemplarily, the interval between the recommended upgrade time and the current moment and the vulnerability level of the first vulnerability is negatively correlated, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle. For example, the higher the vulnerability level of the first vulnerability, the shorter the recommended upgrade time. The vulnerability levels are divided into 4 levels. The higher the level, the greater the harm to the equipment, and the shorter the recommended upgrade time. The recommended upgrade time corresponding to level 1 can be within 6 hours, the recommended upgrade time corresponding to level 2 can be within 4 hours, the recommended upgrade time corresponding to level 3 can be within 1 hour, and the recommended upgrade time corresponding to level 4 can be immediate upgrade.

[0142] The following describes a possible implementation method for determining the vulnerability level of a vulnerability.

[0143] In one possible implementation, a server determines that a first vulnerability exists in a first component. Based on the vulnerability information of the first vulnerability, the server obtains a vulnerability score for the first vulnerability, and then determines a vulnerability level for the first vulnerability based on the vulnerability score. The information about the first vulnerability includes one or more of the vulnerability level of the first vulnerability, the vulnerability impact of the first vulnerability, and a recommended remediation action for the first vulnerability. It should be noted that when a vulnerability is released, the industry determines a vulnerability score based on the degree of harm the vulnerability poses to the software. This vulnerability score can serve as a general vulnerability score for the vulnerability.

[0144] Optionally, vulnerability scores and levels can be determined based on industry practices and expert experience, and can also be determined based on the impact on the vehicle. For example, according to industry practice, vulnerability B has a vulnerability score of 6.5, which is a medium-risk vulnerability. However, when analyzing vulnerability B, the server determines that vulnerability B poses a significant risk to the vehicle based on the vehicle's conditions. For example, if it affects core functions such as autonomous driving, power control, or digital key, the server may determine that vulnerability B has a high-risk level.

[0145] For ease of understanding, please refer to Table 1, which shows a possible relationship between vulnerability levels and vulnerability scores.

[0146] Table 1 Relationship between vulnerability level and vulnerability score

[0147] For example, as shown in Table 1, the vulnerability score ranges from 0 to 10 points. When the vulnerability score is between 0.1 and 3.9, the vulnerability level of the vulnerability is considered to be a low-risk vulnerability (i.e., the aforementioned level 1), which is less harmful to the device. When the vulnerability score is between 4.0 and 6.9, the vulnerability level of the vulnerability is considered to be a medium-risk vulnerability (i.e., the aforementioned level 2), which is generally harmful to the device. When the vulnerability score is between 7.0 and 8.9, the vulnerability level of the vulnerability is considered to be a high-risk vulnerability (i.e., the aforementioned level 3), which is more harmful to the device. When the vulnerability score is higher than 9.0, the vulnerability level of the vulnerability is considered to be a super-risk vulnerability (i.e., the aforementioned level 4), which is extremely harmful to the device and urgently needs to be repaired.

[0148] In a second implementation mode, when a first vulnerability exists in a first component, the server determines a recommended upgrade time based at least on a safety impact level of the first vulnerability on the vehicle.

[0149] For example, the higher the security impact level of the first vulnerability on the vehicle, the shorter the recommended upgrade time. For example, the security impact level of the vulnerability on the vehicle is divided into four levels, with higher levels indicating greater harm to the vehicle, thereby determining the recommended upgrade time. For security impact level 1, the recommended upgrade time may be within 6 hours, for security impact level 2, the recommended upgrade time may be within 4 hours, for security impact level 3, the recommended upgrade time may be within 1 hour, and for security impact level 4, the recommended upgrade time may be immediate.

[0150] The following describes a possible implementation method for determining the security impact level.

[0151] Exemplarily, the server determines the security impact level of the first vulnerability on the vehicle based on information about the components affected by the first vulnerability and the difficulty of exploiting the vulnerability against the vehicle through the first vulnerability. Exemplarily, the server assesses and categorizes the security impact level based on information about the components of the vehicle-side device affected by the first vulnerability, the functions of the device and software, and the technical difficulty of exploiting the vulnerability against the vehicle through the first vulnerability, combined with historical big data analysis results and expert experience. Optionally, the server's method and results for determining the security impact level can be continuously optimized and updated based on vulnerability information.

[0152] For easier understanding, please refer to Table 2, which shows a possible safety impact level table.

[0153] Table 2 Safety impact level table

[0154] For example, as shown in Table 2, the higher the security impact level, the greater the risk to the vehicle, and the more urgent the need to fix the corresponding vulnerability. For example, if the security impact level of the first vulnerability is determined to be severe, it means that the vulnerability can be exploited remotely via a wireless network to affect the vehicle's power control system, autonomous driving system, digital key, and other core devices, seriously endangering the life or property of the vehicle owner. The first vulnerability needs to be fixed immediately or as soon as possible. Accordingly, the recommended upgrade time for the first vulnerability can be immediate.

[0155] In a third embodiment, when a first vulnerability exists in a first component, the server determines a recommended upgrade time based on at least a vulnerability level of the first vulnerability and a safety impact level of the first vulnerability on the vehicle.

[0156] Exemplarily, the higher the vulnerability level of the first vulnerability and the security impact level of the first vulnerability on the vehicle, the shorter the recommended upgrade time. For the relevant description of the vulnerability level, please refer to the aforementioned embodiment one. For example, the security impact level of the vulnerability on the vehicle is divided into 4 levels. The higher the level, the greater the harm to the vehicle. Combined with the vulnerability level of the vulnerability, the recommended upgrade time is determined. The recommended upgrade time corresponding to vulnerability level 1 and security impact level 1 can be within 6 hours, the recommended upgrade time corresponding to vulnerability level 2 and security impact level 2 can be within 4 hours, the recommended upgrade time corresponding to vulnerability level 3 and security impact level 3 can be within 1 hour, and the recommended upgrade time corresponding to vulnerability level 4 and security impact level 4 can be immediate upgrade. Optionally, when the vulnerability level is high risk or super risk and / or the security impact level is high or serious, the relevant vulnerabilities need to be repaired quickly, and a shorter recommended upgrade time can be determined to facilitate timely repair of the relevant vulnerabilities.

[0157] In a fourth embodiment, when a first component has a first vulnerability, the server determines a recommended upgrade time based on the vulnerability level of the first vulnerability, the security impact level of the first vulnerability on the vehicle, and the current status information of the vehicle. In other words, the recommended upgrade time is related to the vulnerability level, the security impact level of the first vulnerability on the vehicle, and the vehicle status information. The current status information of the vehicle includes one or more of the following: vehicle model, vehicle component information, vehicle performance, vehicle driving status, vehicle current remaining battery power, and vehicle current signal status.

[0158] For easier understanding, please refer to Table 3, which shows a possible recommended upgrade schedule.

[0159] Table 3 Recommended upgrade schedule

[0160] For example, as shown in Table 3, when the vulnerability level is extremely dangerous or high risk, or the security impact level is severe or high, as long as the vehicle is in parking state, the remaining power is higher than 50%, and the wireless signal state is strong, the owner can be notified to upgrade and repair the corresponding vulnerability as soon as possible. At this time, the recommended upgrade time can be as soon as possible or immediately. As long as the upgrade conditions are met, the upgrade can be immediate. Optionally, for vulnerabilities in other situations, such as when the vulnerability level is low risk and the security impact level is low, you can choose not to send a notification, or set the recommended upgrade time to a longer time, such as within 48 hours. It should be noted that since the remaining power, driving status, and wireless signal will affect the upgrade of the vehicle, the immediate upgrade in the embodiment of the present application is an immediate upgrade that needs to be performed when these conditions are met, that is, when these conditions are met, the owner is advised to upgrade immediately to repair the vulnerability.

[0161] It should be understood that the aforementioned implementations can be combined without being mutually exclusive. For example, in the case of implementation 2 combined with implementation 4, the server determines the recommended upgrade time based on the security impact level of the first vulnerability on the vehicle and the vehicle's current status information. Furthermore, the aforementioned implementations are illustrative examples, and in specific implementations, more factors may be used to determine the recommended upgrade time. For example, the server may also determine the recommended upgrade time based on information such as the vehicle's speed.

[0162] Optionally, when there is a vulnerability-free software version corresponding to the first vulnerability, the server determines a recommended upgrade time; when there is no vulnerability-free software version corresponding to the first vulnerability, the server sends an early warning notification to the host manufacturer to prompt the host manufacturer to fix the first vulnerability as soon as possible.

[0163] In this way, the server can determine the recommended upgrade time based on multiple influencing factors, improving the controllability of the vehicle upgrade and repair process, increasing user participation, and enhancing the user experience. Consider a possible scenario: some solutions can calculate vulnerability intelligence points based on vulnerability level, vulnerability impact coefficient, etc. However, these points are only used to reward users who conduct vulnerability intelligence mining, and are not used to evaluate vehicle vulnerability repair upgrades or calculate reminder frequency. This results in low controllability of the vehicle upgrade and repair process, low user participation, and a poor user experience.

[0164] Step S304: The server sends information about the first vulnerability and a recommended upgrade time to the vehicle.

[0165] Correspondingly, the vehicle receives the information about the first vulnerability and the recommended upgrade time sent by the server. The first vulnerability is a vulnerability in the first component of the vehicle. In this way, the vehicle can obtain the vulnerability information in a timely manner and learn the preferred upgrade time, which is convenient for the vehicle and the user of the vehicle to plan the upgrade time and thus upgrade the vulnerability as soon as possible. Consider a possible scenario where some communities and cloud services can collect vulnerability information through multiple channels. When a vulnerability is found in a product in the vehicle, the information about the vulnerability is often only informed to the OEM and the product manager. The OEM and the product manager will then promote the upgrade and repair. This will not only lengthen the vulnerability repair process, but also because the vulnerability information is not passed to the car owner in a timely manner, the repair process is not controlled by the car owner, the car owner's participation is low, and the experience is poor.

[0166] Optionally, the first vulnerability information and the recommended upgrade time may be sent in one message or in multiple messages. This application does not impose strict restrictions on the manner in which the above information is sent.

[0167] In one possible implementation, the server sends information about the first vulnerability and a recommended update time to the vehicle via an in-vehicle terminal application notification, based on the vehicle owner information associated with the vehicle. The information about the first vulnerability includes one or more of the vulnerability level of the first vulnerability, the vulnerability impact of the first vulnerability, and a recommended remediation action for the first vulnerability.

[0168] Exemplarily, the server sends a notification to the vehicle through the on-board terminal application, saying, "There is a first vulnerability in the first component of the vehicle. The level of the first vulnerability is a high-risk vulnerability and has a great impact on the safety of the vehicle. It is recommended to upgrade the software version of the first component. It is recommended to upgrade the first component within 1 hour to fix the first vulnerability." As another example, when the server detects that there is a vulnerability in the first component of the current vehicle, if the vulnerability level of the vulnerability is super-critical and the safety impact level of the vehicle is serious, the server can send a notification to the vehicle, saying, "There is a first vulnerability in the first component of the vehicle. The level of the first vulnerability is super-critical and has a very great impact on the safety of the vehicle. It is recommended to upgrade the software version of the first component. It is recommended to upgrade the first component immediately to fix the first vulnerability." Immediate upgrade here refers to immediate upgrade when the remaining power, driving status and wireless signal all meet the conditions.

[0169] Step S305: The server sends the first vulnerability information and the recommended upgrade time to the terminal device.

[0170] In response, the terminal device receives the first vulnerability information and recommended upgrade time from the server. The first vulnerability is a vulnerability in the first component of the vehicle. This allows the terminal device to promptly obtain vulnerability information and understand the preferred upgrade time, facilitating the terminal device and its user to plan vehicle upgrades and implement the vulnerability upgrade as quickly as possible. Consider a possible scenario: some solutions directly initiate a software upgrade after discovering a software vulnerability, lacking public notification and owner confirmation. This leaves the repair process beyond the control of the owner, who is unaware, less engaged, and experiences a poor user experience.

[0171] The terminal device is a device with communication capabilities provided in the embodiments of the present application, which can interact with the user, such as presenting a user interface or receiving user input operations. Exemplarily, the terminal device can be a mobile phone, a smart watch, a smart bracelet, etc.

[0172] In one possible implementation, the server sends information about the first vulnerability and a recommended upgrade time to the terminal device through vehicle application notifications, text messages, emails, and other channels based on the owner information associated with the vehicle.

[0173] For example, the server sends a message to the terminal device through vehicle application notifications, text messages, emails and other channels, saying, "There is a first vulnerability in the first component of the XX vehicle. The first vulnerability is classified as a critical vulnerability and has a very large impact on the safety of the vehicle. It is recommended to upgrade the software version of the first component. It is recommended to upgrade the first component immediately to fix the first vulnerability."

[0174] Step S306: The terminal device receives the upgrade instruction selected by the user.

[0175] For example, after receiving the information about the first vulnerability and the recommended upgrade time from the server, the terminal device may display this information on the screen of the terminal device, allowing the user to select a time to upgrade the first component. For example, the screen of the terminal device may display "A first vulnerability exists in the first component of the XX vehicle. The first vulnerability is classified as a critical vulnerability and has a significant impact on the safety of the vehicle. It is recommended to upgrade the software version of the first component. It is recommended to upgrade the first component immediately to fix the first vulnerability." The user may select a time to upgrade the first component via a mobile phone or smartwatch. If the user selects immediate upgrade, the upgrade instruction instructs the user to select immediate upgrade. If it is inconvenient for the user to upgrade the first component immediately and the user selects to postpone the upgrade, the upgrade instruction instructs the user to postpone the upgrade.

[0176] Optionally, the user can also select a time to upgrade the first component through the vehicle's onboard terminal, and the vehicle can send the user-selected upgrade instruction to the server. In other words, the vehicle can also receive the user-selected upgrade instruction, which indicates the user-selected time to upgrade the first component, and the vehicle can send the user-selected upgrade instruction to the server.

[0177] Step S307: The terminal device sends an upgrade instruction to the server.

[0178] Correspondingly, the server receives the upgrade instruction sent by the terminal device, wherein the upgrade instruction is used to indicate the time selected by the user to upgrade the first component.

[0179] Exemplarily, the terminal device sends an upgrade instruction selected by the user to the server. If the upgrade instruction indicates that the user selects to upgrade immediately, steps S308 and S309 are executed. Alternatively, if the upgrade instruction indicates that the user selects to upgrade at the recommended upgrade time, steps S308 and S309 are executed.

[0180] Furthermore, the vehicle vulnerability repair method also includes steps S310 to S312. If the upgrade instruction instructs the user to choose to delay the upgrade, steps S310 to S312 are executed.

[0181] Step S308: The server sends the upgrade package of the first component to the vehicle.

[0182] Correspondingly, the vehicle receives the upgrade package of the first component sent by the server.

[0183] For example, a server sends an upgrade package for a first component to a vehicle. The upgrade package is used to upgrade the first component to fix a first vulnerability. For example, the first component currently has version A1 of software A installed, which has a first vulnerability. The server sends an upgrade package for the first component to the vehicle, which includes version A2 of software A, which does not have the vulnerability.

[0184] Step S309: The vehicle upgrades the first component.

[0185] Exemplarily, a vehicle receives an upgrade package for a first component from a server, parses the package, and upgrades the first component based on the package. For example, the first component currently has version A1 of software A installed, which has a first vulnerability. The vehicle receives an upgrade package for the first component from the server, which includes version A2 of software A, which does not have a vulnerability. The vehicle upgrades the first component based on the package, upgrading the software A to version A2.

[0186] Step S310: The server determines a recommended reminder time interval based on at least the vulnerability level of the first vulnerability and the safety impact level of the first vulnerability on the vehicle.

[0187] For example, if the upgrade instruction instructs the user to choose to delay the upgrade, the server needs to determine the recommended reminder time interval based on at least the vulnerability level of the first vulnerability and the safety impact level of the first vulnerability on the vehicle. Optionally, the server can also determine the recommended reminder time interval based on the vulnerability level of the first vulnerability, the safety impact level of the first vulnerability on the vehicle, and the current status information of the vehicle. For the current status information of the vehicle, please refer to the relevant description of the aforementioned step S303. For example, when the remaining power of the vehicle is too low, the recommended reminder time interval can be adjusted to be longer. Among them, the recommended reminder time interval is the time interval for recommending reminding the user to upgrade the first component.

[0188] For easier understanding, please refer to Table 4, which shows a possible recommended reminder time interval table.

[0189] Table 4 Recommended reminder time intervals

[0190] For example, as shown in Table 4, when the vulnerability level is extremely dangerous and the safety impact level on the vehicle is serious, the recommended reminder time interval is 4 hours, that is, every 4 hours, the server sends the first vulnerability information and the re-determined recommended upgrade time to the vehicle and / or terminal device.

[0191] Step S311: The server sends the first vulnerability information and the re-determined recommended upgrade time to the vehicle according to the recommended reminder time interval.

[0192] For example, the server also needs to send the first vulnerability information and the re-determined recommended upgrade time to the vehicle based on the recommended reminder time interval. It should be noted that since the remaining power, driving status, and wireless signal all affect the vehicle upgrade, this information may be different at different times, so the server needs to re-determine the recommended upgrade time at that moment. For the method of determining the recommended upgrade time, please refer to the relevant description of S303 above. For example, the recommended reminder time interval is 4 hours, that is, the server sends the first vulnerability information and the re-determined recommended upgrade time to the vehicle every 4 hours.

[0193] Step S312: The server sends the first vulnerability information and the re-determined recommended upgrade time to the terminal device according to the recommended reminder time interval.

[0194] For example, the server also needs to send the first vulnerability information and the re-determined recommended upgrade time to the terminal device based on the recommended reminder time interval. It should be noted that since the remaining power, driving status and wireless signal will affect the upgrade of the vehicle, this information may be different at different times, so the server needs to re-determine the recommended upgrade time at that moment. For the method of determining the recommended upgrade time, please refer to the relevant description of S303 above. For example, the recommended reminder time interval is 4 hours, that is, the server sends the first vulnerability information and the re-determined recommended upgrade time to the terminal device every 4 hours.

[0195] Optionally, after the vehicle upgrade is completed, an upgrade completion message can be sent to the server, and the server sends a vulnerability repair success notification to the vehicle and / or terminal device to prompt the user that the relevant vulnerability has been successfully repaired, so that the user can understand the device software vulnerability repair process and repair progress throughout the vehicle's life cycle.

[0196] In one possible implementation, this vehicle vulnerability repair method can also be applied to vulnerability detection and repair in areas such as smart homes and children's smart watches. Unlike this vehicle vulnerability repair method, this method requires a separate assessment of the security impact of the vulnerability in these areas to determine a recommended upgrade time. For example, information about smart furniture components can be obtained, vulnerability detection performed on these components, a recommended upgrade time determined, and the vulnerability information and recommended upgrade time sent to the terminal device and / or smart furniture.

[0197] In the embodiment shown in FIG3 , the server can obtain the component information of the vehicle and perform vulnerability detection on the vehicle. When a vulnerability exists, the server determines the recommended upgrade time based on at least the vulnerability level of the vulnerability, and sends the vulnerability information and the recommended upgrade time to the vehicle, so that the vehicle owner can obtain the vulnerability information and the preferred upgrade time in a timely manner, which is convenient for the vehicle owner to plan the time for vehicle upgrade, so as to repair the vulnerability as soon as possible, thereby improving the efficiency of vulnerability repair, and making the device software vulnerabilities throughout the entire life cycle of the entire vehicle perceptible to the vehicle owner, thereby improving the controllability of the vehicle upgrade and repair process, improving user participation, and enhancing user experience.

[0198] FIG3 above provides multiple possible implementations. The following is an exemplary introduction to possible implementations of the present application embodiment in conjunction with FIG4 and FIG5. It should be understood that any logic or terminology not explained below can be referred to the introduction of FIG3 above.

[0199] In one possible embodiment, the terminal device and the vehicle are connected to a server. The vehicle owner can learn about vulnerability information with a relatively large impact from multiple channels through the terminal device, and thus actively initiate a vulnerability detection instruction. The terminal device sends the vulnerability detection instruction to the server, and the server performs vulnerability detection on the vehicle and returns the vulnerability detection result (or vehicle safety status) to the terminal device.

[0200] Please refer to Figure 4, which is a schematic diagram of another vehicle vulnerability repair method provided by an embodiment of the present application. As shown in Figure 4, the communication method includes one or more steps from step S401 to step S410, which are as follows:

[0201] Step S401: The terminal device sends third information to the server.

[0202] Correspondingly, the server receives the third information sent by the terminal device.

[0203] Among them, the third information is used to instruct the car owner to subscribe to vulnerability information through the terminal device. The vulnerability information includes media reports, industry reports, car manufacturer reports, or vulnerability information released from multiple channels.

[0204] Step S402: The server sends vulnerability information to the terminal device.

[0205] For example, a car owner subscribes to vulnerability information through a terminal device and may receive a media report stating that "version H1 of the software installed in the H device of model XX has a major software vulnerability that, when exploited, caused the XX accident." The server can send information about certain vulnerabilities with a wide impact to the car owner's terminal device. Based on this information, the user can determine whether to perform vulnerability testing on their vehicle. This increases user awareness of vehicle vulnerability information, enhances user engagement, and facilitates timely vulnerability testing, protecting the safety of their life and property.

[0206] Optionally, the terminal device can also obtain vulnerability information from the Internet or social applications, and when vulnerability information related to its own vehicle is discovered, it will actively initiate a vulnerability detection command to perform vulnerability detection on its own vehicle.

[0207] Step S403: The vehicle sends the vehicle log to the server.

[0208] Accordingly, the server receives the vehicle log sent by the vehicle. The vehicle log is used to determine the vehicle's operating status, for example, including operating information of the vehicle's equipment. Alternatively, the vehicle may periodically send the vehicle log to the server, for example, daily, bi-day, or weekly.

[0209] Step S404: The server detects the vehicle's log.

[0210] Exemplarily, the server analyzes the vehicle log and performs intrusion detection on the vehicle log. If an abnormality is found, step S405 is executed.

[0211] Step S405: When there is an abnormality in the vehicle log, the server sends a first message to the terminal device.

[0212] Correspondingly, the terminal device receives the first information sent by the server.

[0213] The first information is used to instruct the user to initiate a vulnerability detection instruction, and the vulnerability detection instruction is used to instruct the server to perform vulnerability detection on the vehicle.

[0214] Optionally, when there is an abnormality in the vehicle's log, the server may also send the first information to the vehicle.

[0215] Step S406: The terminal device sends a vulnerability detection instruction to the server.

[0216] Exemplarily, the terminal device receives a vulnerability detection instruction initiated by a user and sends the vulnerability detection instruction to the server.

[0217] Alternatively, the user can also initiate a vulnerability detection command through the vehicle's onboard terminal, and the vehicle sends the vulnerability detection command to the server. Correspondingly, the server receives the vulnerability detection command and performs vulnerability detection on the vehicle in response to the vulnerability detection command.

[0218] Optionally, the user can proactively initiate a vulnerability detection command at any time to perform vulnerability detection on the vehicle.

[0219] Step S407: The server obtains the vehicle parts information.

[0220] In one possible implementation, the server sends a request for retrieval to the vehicle. Upon receiving the request, the vehicle sends the vehicle's parts information to the server. It should be noted that regardless of the time at which the vehicle sends the parts information to the server, the vehicle must have recently retrieved the information. This means the server only retrieves the latest vehicle parts information.

[0221] Step S408: The server performs vulnerability detection on the vehicle based on the vehicle's component information.

[0222] See the related description of the aforementioned step S302.

[0223] Step S409: When the first component has a first vulnerability, the server determines a recommended upgrade time based at least on the vulnerability level of the first vulnerability and the safety impact level of the first vulnerability on the vehicle.

[0224] See the related description of the aforementioned step S303.

[0225] Step S410: The server sends the vulnerability detection result to the terminal device.

[0226] Exemplarily, the vulnerability detection result (or vehicle security status) indicates whether the vehicle has a vulnerability. If a first vulnerability exists in a first component of the vehicle, the vulnerability detection result also includes information about the first vulnerability and a recommended upgrade time, as described in step S305 above. If a first vulnerability exists in the first component of the vehicle, the subsequent steps are the same as steps S306 through S312 in FIG. 3 and are not further described here.

[0227] In the embodiment shown in FIG4 , the user can actively initiate a vulnerability detection instruction through the terminal device at any time. The terminal device sends the vulnerability detection instruction to the server. The server performs vulnerability detection on the vehicle and returns the vulnerability detection result to the terminal device. This can improve the controllability of the vehicle upgrade and repair process, increase user participation, and enhance user experience.

[0228] In one possible implementation, some car owners are unfamiliar with vulnerability detection and remediation. They simply care about the safety of their vehicle and wish to delegate responsibility to a family member or trusted individual. Alternatively, if a car is shared by multiple family members, a familiar family member may be authorized to perform vehicle upgrades.

[0229] Please refer to Figure 5, which is a schematic diagram of another vehicle vulnerability repair method provided by an embodiment of the present application. As shown in Figure 5, the communication method includes one or more steps from step S501 to step S511, which are as follows:

[0230] Step S501: The first terminal sends authorization information to the server.

[0231] The first terminal is one of the aforementioned terminal devices and is associated with the vehicle, for example, the vehicle owner's mobile phone. The authorization information indicates that the first terminal authorizes the second terminal to perform vehicle upgrade operations. The second terminal is an authorized terminal of the vehicle owner. For example, the second terminal may be the mobile phone of a family member authorized by the vehicle owner.

[0232] Optionally, the authorization information may also include an authorization time. The user can set the time during which the authorized terminal is authorized to perform vehicle upgrade operations. After the authorization time expires, the authorized terminal cannot continue to perform vehicle upgrade operations on the vehicle. The user can also choose to cancel the authorization. For example, if a vehicle owner authorizes a second terminal to perform vehicle upgrade operations on the vehicle, they can also cancel the second terminal's authorization of vehicle upgrade operations on the vehicle.

[0233] In this way, when it is inconvenient for the car owner to upgrade the vehicle or the car owner does not understand the concepts such as vulnerability detection and is not familiar with the vulnerability repair operations, the car owner can authorize someone trusted by the car owner to upgrade the vehicle, which is convenient for the user to upgrade the vehicle, improves the efficiency of vulnerability repair, and enhances the user experience.

[0234] Step S502: The second terminal sends a vulnerability detection instruction to the server.

[0235] See the description of step S406 above. The user of the second terminal can initiate a vulnerability detection instruction for the vehicle regularly or when important vulnerability information is learned. Optionally, the first terminal can also actively send a vulnerability detection instruction to the server.

[0236] Step S503: The server obtains vehicle component information.

[0237] See the related description of the aforementioned step S407.

[0238] Step S504: The server performs vulnerability detection on the vehicle based on the vehicle's component information.

[0239] See the related description of the aforementioned step S408.

[0240] Step S505: When the first component has a first vulnerability, the server determines a recommended upgrade time based at least on the vulnerability level of the first vulnerability and the safety impact level of the first vulnerability on the vehicle.

[0241] See the related description of the aforementioned step S409.

[0242] Step S506: The server sends the vulnerability detection result to the first terminal.

[0243] Exemplarily, the vulnerability detection result is used to indicate whether the vehicle has a vulnerability. If a first vulnerability exists in a first component of the vehicle, the vulnerability detection result also includes information about the first vulnerability and a recommended upgrade time. For related descriptions, see the aforementioned step S305.

[0244] For example, the user can choose whether to perform the vehicle upgrade operation on their own through the first terminal. For example, if the user understands the vulnerability information and knows the upgrade operation, the user can choose to perform the vehicle upgrade operation on their own. If the user does not understand the vulnerability information, is not familiar with the upgrade operation, or is busy with important matters and is not convenient to perform the vehicle upgrade operation, the user can choose to have the vehicle upgrade operation performed by an authorized second terminal. If the user chooses to perform the vehicle upgrade operation on their own, an upgrade instruction is sent to the server through the first terminal. The subsequent steps are the same as steps S306 to S312 in Figure 3 above and are not repeated here. If the user chooses to have the vehicle upgrade operation performed by an authorized second terminal, step S507 is executed.

[0245] Step S507: The first terminal sends second information to the server.

[0246] The second information is used to instruct the second terminal to perform a vehicle upgrade operation.

[0247] Step S508: The server sends the vulnerability detection result to the second terminal.

[0248] Exemplarily, the vulnerability detection result is used to indicate whether the vehicle has a vulnerability. If a first vulnerability exists in a first component of the vehicle, the vulnerability detection result also includes information about the first vulnerability and a recommended upgrade time. For related descriptions, see the aforementioned step S305.

[0249] Step S509: The second terminal sends an upgrade instruction to the server.

[0250] See the description of step S307 above. If the upgrade instruction instructs the user to select immediate upgrade, then steps S510 and S511 are executed. Alternatively, if the upgrade instruction instructs the user to select upgrade at the recommended upgrade time, then steps S510 and S511 are executed.

[0251] If the upgrade instruction instructs the user to choose to delay the upgrade, steps S310 to S312 in FIG. 3 are executed.

[0252] Step S510: The server sends an upgrade package of the first component to the vehicle.

[0253] See the related description of the aforementioned step S308.

[0254] Step S511: The vehicle upgrades the first component.

[0255] Related description of the aforementioned step S309.

[0256] Optionally, after the upgrade is complete and the vulnerability is successfully fixed, the server can notify the vehicle owner of the vulnerability fix results and the latest vehicle security status. For example, the server can send a message to the vehicle owner's terminal device stating that "Your vehicle is currently free of vulnerabilities and is in good security status."

[0257] In the embodiment shown in FIG5 , when a user is inconvenient or unfamiliar with the vehicle upgrade operation, the user can authorize other trusted users to perform vehicle upgrade operations on the vehicle through the authorization terminal, so that the user can repair vehicle vulnerabilities in a timely manner, realize the authorized security care of the vehicle, improve the controllability of the vehicle upgrade and repair process, increase user participation, and enhance user experience.

[0258] The above describes in detail the method of the embodiment of the present application. The following provides an apparatus of the embodiment of the present application.

[0259] Please refer to Figure 6, which is a schematic diagram of the structure of a vehicle upgrade device provided in an embodiment of the present application. The vehicle upgrade device 60 may include a communication unit 601 and a processing unit 602. The vehicle upgrade device 60 is used to implement the aforementioned vehicle vulnerability repair method, such as the vehicle vulnerability repair method in the embodiments shown in Figures 3, 4, or 5.

[0260] It should be noted that the division of the above-mentioned multiple units is merely a logical division based on function and does not limit the specific structure of the vehicle upgrade device 60. In a specific implementation, some functional modules may be subdivided into more small functional modules, and some functional modules may be combined into one functional module.

[0261] In one possible implementation, the communication unit 601 is configured to obtain vehicle component information and send information about the first vulnerability and a recommended upgrade time to the vehicle and / or the first terminal, wherein the component information includes information about the first component, and the first terminal is associated with the vehicle.

[0262] The processing unit 602 is used to perform vulnerability detection on the vehicle based on the component information of the vehicle, and when a first vulnerability exists in a first component, determine a recommended upgrade time based on at least the vulnerability level of the first vulnerability and the security impact level of the first vulnerability on the vehicle.

[0263] In a possible implementation, the processing unit 602 is further configured to determine a recommended upgrade time based on the vulnerability level of the first vulnerability, the security impact level of the first vulnerability on the vehicle, and current status information of the vehicle.

[0264] In one possible implementation, the current status information of the vehicle includes one or more of the vehicle model, vehicle component information, vehicle performance, vehicle driving status, vehicle current remaining power, and vehicle current signal status.

[0265] In a possible implementation, the recommended upgrade time is the recommended upgrade time for the first component, and the information about the first vulnerability includes one or more of the vulnerability level of the first vulnerability, the vulnerability impact of the first vulnerability, and the recommended repair operation for the first vulnerability.

[0266] In a possible implementation, the interval between the recommended upgrade time and the current moment is negatively correlated with the vulnerability level of the first vulnerability, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle.

[0267] In one possible implementation, the communication unit 601 is further configured to receive an upgrade instruction selected by the user, and if the upgrade instruction indicates that the user selects an immediate upgrade or an upgrade at a recommended upgrade time, send the upgrade package for the first component to the vehicle, and send information about the first vulnerability and a re-determined recommended upgrade time to the vehicle and / or the first terminal according to a recommended reminder interval. The upgrade instruction indicates the time selected by the user for upgrading the first component.

[0268] The processing unit 602 is also used to determine a recommended reminder time interval based on the vulnerability level of the first vulnerability, the safety impact level of the first vulnerability on the vehicle, and the current status information of the vehicle when the upgrade instruction instructs the user to choose to delay the upgrade. The recommended reminder time interval is the time interval for recommending the user to upgrade the first component.

[0269] In a possible implementation, the processing unit 602 is further configured to determine a security impact level of the first vulnerability on the vehicle based on information about components affected by the first vulnerability and the difficulty of implementing a vulnerability attack on the vehicle through the first vulnerability.

[0270] In one possible embodiment, the communication unit 601 is also used to receive the vehicle's log, and when there is an abnormality in the vehicle's log, send a first message to the vehicle and / or the first terminal, where the first information is used to instruct the user to initiate a vulnerability detection instruction. The processing unit 602 is also used to detect the vehicle's log.

[0271] In a possible implementation, the communication unit 601 is further configured to receive a vulnerability detection instruction from the vehicle and / or the first terminal, and the processing unit 602 is further configured to perform vulnerability detection on the vehicle in response to the vulnerability detection instruction.

[0272] In one possible implementation, communication unit 601 is further configured to receive authorization information from a first terminal, receive a vulnerability detection instruction from a second terminal, send first vulnerability information and a recommended upgrade time to the first terminal, receive second information from the first terminal, send first vulnerability information and a recommended upgrade time to the second terminal, and receive an upgrade instruction from the second terminal. The authorization information indicates that the first terminal authorizes the second terminal to perform a vehicle upgrade operation, the second terminal being the authorized terminal of the vehicle owner, and the second information indicates that the second terminal is to perform the vehicle upgrade operation.

[0273] It should be noted that the above modules (communication unit 601 and processing unit 602) are used to execute the relevant steps of the above method. For example, the communication unit 601 is used to execute the relevant contents of step S304, step S305, step S308, step S311 and step S312, and the processing unit 602 is used to execute the relevant contents of step S302, step S303 and step S310.

[0274] Please refer to Figure 7, which is a schematic diagram of the structure of another vehicle upgrade device provided in an embodiment of the present application. The vehicle upgrade device 70 may include a communication unit 701 and a processing unit 702. The vehicle upgrade device 70 is used to implement the aforementioned vehicle vulnerability repair method, such as the vehicle vulnerability repair method in the embodiments shown in Figures 3, 4, or 5.

[0275] It should be noted that the division of the above-mentioned multiple units is merely a logical division based on function and does not limit the specific structure of the vehicle upgrade device 70. In a specific implementation, some functional modules may be subdivided into more small functional modules, and some functional modules may be combined into one functional module.

[0276] In a possible implementation, the communication unit 701 is configured to send vehicle component information, receive first vulnerability information and a recommended upgrade time, and receive an upgrade package for the first component from a server.

[0277] The processing unit 702 is configured to upgrade the first component, wherein the component information includes information of the first component, and the first vulnerability is a vulnerability existing in the first component.

[0278] In a possible implementation, the recommended upgrade time is related to the vulnerability level of the first vulnerability, the security impact level of the first vulnerability on the vehicle, and the status information of the vehicle.

[0279] In one possible implementation, the current status information of the vehicle includes one or more of the vehicle model, vehicle component information, vehicle performance, vehicle driving status, vehicle current remaining power, and vehicle current signal status.

[0280] In a possible implementation, the interval between the recommended upgrade time and the current moment is negatively correlated with the vulnerability level of the first vulnerability, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle.

[0281] In a possible implementation, the vulnerability level of the first vulnerability is related to the vulnerability score of the first vulnerability, and the vulnerability score of the first vulnerability is related to the information of the first vulnerability.

[0282] In a possible implementation, the communication unit 701 is further configured to receive an upgrade instruction selected by the user and send the upgrade instruction to the server, where the upgrade instruction is used to indicate the time selected by the user to upgrade the first component.

[0283] In a possible implementation, the communication unit 701 is further configured to send a vehicle log, which is used to determine the operating status of the vehicle.

[0284] In a possible implementation, the communication unit 701 is further configured to receive a vulnerability detection instruction from a user and send the vulnerability detection instruction to a server, where the vulnerability detection instruction is configured to instruct the server to perform vulnerability detection on the vehicle.

[0285] It should be noted that the above modules (communication unit 701 and processing unit 702) are used to execute the relevant steps of the above method. For example, the communication unit 701 is used to execute the relevant content of step S301, and the processing unit 702 is used to execute the relevant content of step S309.

[0286] Please refer to Figure 8, which is a schematic diagram of the structure of another vehicle upgrade device provided in an embodiment of the present application. The vehicle upgrade device 80 may include a communication unit 801. The vehicle upgrade device 80 is used to implement the aforementioned vehicle vulnerability repair method, such as the vehicle vulnerability repair method in the embodiments shown in Figures 3, 4, or 5.

[0287] It should be noted that the division of the above-mentioned multiple units is merely a logical division based on function and does not limit the specific structure of the vehicle upgrade device 80. In a specific implementation, some functional modules may be subdivided into more small functional modules, and some functional modules may be combined into a single functional module.

[0288] In one possible implementation, communication unit 801 is configured to receive information about a first vulnerability and a recommended upgrade time, receive an upgrade instruction selected by a user, and send the upgrade instruction to a server. The first vulnerability is a vulnerability in a first component of the vehicle, and the upgrade instruction indicates the time selected by the user to upgrade the first component.

[0289] In a possible implementation, the recommended upgrade time is related to the vulnerability level of the first vulnerability, the security impact level of the first vulnerability on the vehicle, and the status information of the vehicle.

[0290] In one possible implementation, the current status information of the vehicle includes one or more of the vehicle model, vehicle component information, vehicle performance, vehicle driving status, vehicle current remaining power, and vehicle current signal status.

[0291] In a possible implementation, the interval between the recommended upgrade time and the current moment is negatively correlated with the vulnerability level of the first vulnerability, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle.

[0292] In a possible implementation, the vulnerability level of the first vulnerability is related to the vulnerability score of the first vulnerability, and the vulnerability score of the first vulnerability is related to the information of the first vulnerability.

[0293] In a possible implementation, the communication unit 801 is further configured to receive first information from a server, where the first information is used to instruct a user to initiate a vulnerability detection instruction.

[0294] In a possible implementation, the communication unit 801 is further configured to receive a vulnerability detection instruction from a user and send the vulnerability detection instruction to a server, where the vulnerability detection instruction is configured to instruct the server to perform vulnerability detection on the vehicle.

[0295] In one possible implementation, communication unit 801 is further configured to send authorization information to a server, receive an upgrade instruction selected by a user, and send the upgrade instruction to the server. The authorization information indicates that the first terminal authorizes the second terminal to perform the vehicle upgrade operation, where the second terminal is the authorized terminal of the vehicle owner, and the upgrade instruction indicates the time selected by the user for upgrading the first component.

[0296] In one possible implementation, the communication unit 801 is further configured to send authorization information to the server and second information to the server, wherein the authorization information indicates that the first terminal authorizes the second terminal to perform a vehicle upgrade operation, the second terminal being an authorized terminal of the vehicle owner, and the second information indicates that the second terminal is to perform the vehicle upgrade operation.

[0297] It should be noted that the communication unit 801 is used to execute the relevant steps of the above method, for example, the communication unit 801 is used to execute the relevant contents of step S306 and step S307.

[0298] Figure 9 is a schematic diagram of the structure of a server provided in an embodiment of the present application. A server is a device with processing and communication capabilities. The device here can be a physical device, such as a rack server, a host, etc., or a virtual device, such as a virtual machine, a container, etc.

[0299] As shown in Figure 9, the server 90 includes: a processor 901, a memory 902, and one or more programs, which may include a communication interface 903. It should be understood that the present application does not limit the number of processors and memories in the server 90.

[0300] The processor 901 is a module for performing calculations and may include a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), a digital signal processor (DSP), a microcontroller unit (MCU), or one or more integrated circuits for controlling the execution of the above program.

[0301] The memory 902 is used to provide storage space, which can optionally store application data, user data, an operating system, and computer programs. The memory 902 may include, but is not limited to, read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0302] The memory 902 may exist independently and be connected to the processor 901 via a bus. The memory 902 may also be integrated with the processor 901.

[0303] The communication interface 903 is used to provide information input or output for the at least one processor. And / or, the communication interface 903 can be used to receive data sent externally and / or send data to the outside. The communication interface 903 can be a wired link interface such as an Ethernet cable, or a wireless link (Wi-Fi, Bluetooth, general wireless transmission and other wireless communication technologies, etc.) interface. Optionally, the communication interface 903 can also include a transmitter (such as a radio frequency transmitter, antenna, etc.) coupled to the interface, or a receiver, etc.

[0304] In the embodiment of the present application, the one or more programs are stored in the memory 902 in the form of program code and are configured to be executed by the processor 901. The programs include instructions for implementing the steps in the aforementioned vehicle vulnerability repair method. For example, the vehicle vulnerability repair method shown in Figures 3, 4, or 5. That is, the memory 902 stores executable instructions, and the processor 901 executes the executable instructions to implement the aforementioned vehicle vulnerability repair method, such as the vehicle vulnerability repair method in the embodiments of Figures 3, 4, or 5. In other words, the memory 902 stores instructions for executing the vehicle vulnerability repair method.

[0305] Alternatively, executable instructions are stored in the memory 902, and the processor 901 executes the executable instructions to respectively implement the functions of one or more units (or devices) in the communication unit and the processing unit in the vehicle upgrade device shown in Figure 6 above, thereby implementing the vehicle vulnerability repair method.

[0306] Figure 10 is a schematic diagram of the structure of a vehicle provided in an embodiment of the present application. A vehicle is a device with processing and communication capabilities.

[0307] As shown in Figure 10, the vehicle 100 includes a processor 1001, a memory 1002, and one or more programs, which may include a communication interface 1003. It should be understood that the present application does not limit the number of processors and memories in the vehicle 100.

[0308] Processor 1001 is a module for performing calculations and may include a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), a digital signal processor (DSP), a microcontroller unit (MCU), or one or more integrated circuits for controlling the execution of the above program.

[0309] The memory 1002 is used to provide storage space, which can optionally store application data, user data, an operating system, and computer programs. The memory 1002 may include, but is not limited to, read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0310] The memory 1002 may exist independently and be connected to the processor 1001 via a bus. The memory 1002 may also be integrated with the processor 1001.

[0311] The communication interface 1003 is used to provide information input or output for the at least one processor. And / or, the communication interface 1003 can be used to receive data sent externally and / or send data to the outside. The communication interface 1003 can be a wired link interface such as an Ethernet cable, or a wireless link (Wi-Fi, Bluetooth, general wireless transmission and other wireless communication technologies, etc.) interface. Optionally, the communication interface 1003 can also include a transmitter (such as a radio frequency transmitter, antenna, etc.) coupled to the interface, or a receiver, etc.

[0312] In the embodiment of the present application, the one or more programs are stored in the memory 1002 in the form of program code and are configured to be executed by the processor 1001. The programs include instructions for implementing the steps in the aforementioned vehicle vulnerability repair method. For example, the vehicle vulnerability repair method shown in Figures 3, 4, or 5. That is, the memory 1002 stores executable instructions, and the processor 1001 executes the executable instructions to implement the aforementioned vehicle vulnerability repair method, such as the vehicle vulnerability repair method in the embodiments of Figures 3, 4, or 5. In other words, the memory 1002 stores instructions for executing the vehicle vulnerability repair method.

[0313] Alternatively, executable instructions are stored in the memory 1002, and the processor 1001 executes the executable instructions to respectively implement the functions of one or more units (or devices) in the communication unit and the processing unit in the vehicle upgrade device shown in Figure 7 above, thereby realizing the vehicle vulnerability repair method.

[0314] Figure 11 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. A terminal device is a device with processing and communication capabilities.

[0315] As shown in Figure 11, the terminal device 110 includes: a processor 1101, a memory 1102, and one or more programs, and may include a communication interface 1103. It should be understood that this application does not limit the number of processors and memories in the terminal device 110.

[0316] The processor 1101 is a module for performing calculations and may include a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), a digital signal processor (DSP), a microcontroller unit (MCU), or one or more integrated circuits for controlling the execution of the above program.

[0317] The memory 1102 is used to provide storage space, which can optionally store application data, user data, an operating system, and computer programs. The memory 1102 may include, but is not limited to, read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0318] The memory 1102 may exist independently and be connected to the processor 1101 via a bus. The memory 1102 may also be integrated with the processor 1101.

[0319] The communication interface 1103 is used to provide information input or output for the at least one processor. And / or, the communication interface 1103 can be used to receive data sent externally and / or send data to the outside. The communication interface 1103 can be a wired link interface such as an Ethernet cable, or a wireless link interface (Wi-Fi, Bluetooth, general wireless transmission and other wireless communication technologies, etc.). Optionally, the communication interface 1103 can also include a transmitter (such as a radio frequency transmitter, antenna, etc.) coupled to the interface, or a receiver, etc.

[0320] In an embodiment of the present application, the one or more programs are stored in the memory 1102 in the form of program code and are configured to be executed by the processor 1101. The programs include instructions for implementing the steps in the aforementioned vehicle vulnerability repair method. For example, the vehicle vulnerability repair method shown in Figures 3, 4, or 5. That is, the memory 1102 stores executable instructions, and the processor 1101 executes the executable instructions to implement the aforementioned vehicle vulnerability repair method, such as the vehicle vulnerability repair method in the embodiments of Figures 3, 4, or 5. In other words, the memory 1102 stores instructions for executing the vehicle vulnerability repair method.

[0321] Alternatively, executable instructions are stored in the memory 1102, and the processor 1101 executes the executable instructions to respectively implement the functions of the communication unit (or device) in the vehicle upgrade device shown in Figure 8 above, thereby implementing the vehicle vulnerability repair method.

[0322] The present application also provides a computer program product comprising instructions. The computer program product may be software or a program product comprising computer instructions, capable of being executed on a computing device or stored on any usable medium. The computer program instructions are used to implement the aforementioned vehicle vulnerability repair method, such as the vehicle vulnerability repair method in the embodiments of FIG. 3 , FIG. 4 , or FIG. 5 .

[0323] The present application also provides a computer-readable storage medium including instructions for implementing the aforementioned vehicle vulnerability repair method, such as the method in the embodiments of FIG. 3 , FIG. 4 , or FIG. 5 .

[0324] The computer-readable storage medium may be any available medium capable of being stored by the vehicle upgrade device, or a data storage device such as a data center containing one or more available media. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state drive).

[0325] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0326] The “at least one” mentioned in the embodiments of this application refers to one or more, and “plurality” refers to two or more. “At least one of the following items” or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, (a and b), (a and c), (b and c), or (a and b and c), where a, b, c can be single or multiple. “And / or” describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character “ / ” generally indicates that the previous and next associated objects are in an “or” relationship.

[0327] Furthermore, unless otherwise specified, ordinal numbers such as "first" and "second" in the embodiments of this application are used to distinguish multiple objects and are not used to define the order, timing, priority, or importance of multiple objects. For example, the first terminal and the second terminal are only used for ease of description and do not indicate differences in the device structure, deployment order, or importance of the first and second terminals.

[0328] Those skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware, or may be accomplished by a program to instruct the relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0329] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the protection scope of the technical solutions of the various embodiments of the present invention.

Claims

1. A vehicle vulnerability repair method, characterized in that, The method includes: Obtaining component information of a vehicle, where the component information includes information of a first component; Performing vulnerability detection on the vehicle according to the component information of the vehicle; When there is a first vulnerability in the first component, determining a recommended upgrade time based at least on the vulnerability level of the first vulnerability and the security impact level of the first vulnerability on the vehicle; Sending the information of the first vulnerability and the recommended upgrade time to the vehicle and / or a first terminal, where the first terminal is associated with the vehicle.

2. The method according to claim 1, characterized in that, The determining the recommended upgrade time based at least on the vulnerability level of the first vulnerability and the security impact level of the first vulnerability on the vehicle includes: Determining the recommended upgrade time according to the vulnerability level of the first vulnerability, the security impact level of the first vulnerability on the vehicle, and the current status information of the vehicle.

3. The method according to claim 1 or 2, characterized in that, The recommended upgrade time is the time recommended to upgrade the first component, and the information of the first vulnerability includes one or more of the vulnerability level of the first vulnerability, the impact of the first vulnerability, and the repair operation recommended for the first vulnerability.

4. The method according to any one of claims 1 to 3, characterized in that, The interval between the recommended upgrade time and the current moment is negatively correlated with the vulnerability level of the first vulnerability, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Obtaining a vulnerability score of the first vulnerability according to the information of the first vulnerability; Determining the vulnerability level of the first vulnerability according to the vulnerability score of the first vulnerability.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Receiving an upgrade instruction selected by a user, where the upgrade instruction is used to indicate the time selected by the user to upgrade the first component; When the upgrade instruction indicates that the user selects to upgrade immediately or the user selects to upgrade at the recommended upgrade time, sending an upgrade package of the first component to the vehicle; When the upgrade instruction indicates that the user selects to delay the upgrade, determining a recommended reminder time interval according to the vulnerability level of the first vulnerability, the security impact level of the first vulnerability on the vehicle, and the current status information of the vehicle, where the recommended reminder time interval is the time interval recommended to remind the user to upgrade the first component; According to the recommended reminder time interval, sending the information of the first vulnerability and the re-determined recommended upgrade time to the vehicle and / or the first terminal.

7. The method according to claim 5 or 6, characterized in that, The method further includes: Determining the security impact level of the first vulnerability on the vehicle according to the information of the component affected by the first vulnerability and the difficulty of performing a vulnerability attack on the vehicle through the first vulnerability.

8. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Receiving the log of the vehicle; Detecting the log of the vehicle; When there is an abnormality in the log of the vehicle, sending a first message to the vehicle and / or the first terminal, where the first message is used to instruct the user to initiate a vulnerability detection instruction.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Receiving a vulnerability detection instruction from the vehicle and / or the first terminal; The performing vulnerability detection on the vehicle according to the component information of the vehicle includes: In response to the vulnerability detection instruction, performing vulnerability detection on the vehicle.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: Receive authorization information from the first terminal, where the authorization information is used to indicate that the first terminal authorizes the second terminal to perform a vehicle upgrade operation, and the second terminal is the authorized terminal of the vehicle owner; Receive a vulnerability detection instruction from the second terminal; Send information about the first vulnerability and the recommended upgrade time to the first terminal; Receive second information from the first terminal, where the second information is used to indicate that the second terminal performs a vehicle upgrade operation; Send information about the first vulnerability and the recommended upgrade time to the second terminal; Receive an upgrade instruction from the second terminal.

11. A method for repairing vehicle vulnerabilities, characterized in that, The method includes: Send component information of the vehicle, where the component information includes information about the first component; Receive information about the first vulnerability and the recommended upgrade time, where the first vulnerability is a vulnerability existing in the first component; Receive an upgrade package for the first component from the server and upgrade the first component.

12. The method according to claim 11, wherein The recommended upgrade time is related to the vulnerability level of the first vulnerability, the level of security impact of the first vulnerability on the vehicle, and the status information of the vehicle.

13. The method according to claim 11 or 12, characterized in that, The interval between the recommended upgrade time and the current time is negatively correlated with the vulnerability level of the first vulnerability, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle.

14. The method according to any one of claims 11 - 13, characterized in that, The vulnerability level of the first vulnerability is related to the vulnerability score of the first vulnerability, and the vulnerability score of the first vulnerability is related to the information about the first vulnerability.

15. The method according to any one of claims 11-14, characterized in that, The method further includes: Receive an upgrade instruction selected by the user, where the upgrade instruction is used to indicate the time selected by the user to upgrade the first component; Send the upgrade instruction to the server.

16. The method according to any one of claims 11-15, characterized in that, The method further includes: Send the log of the vehicle, where the log of the vehicle is used to determine the running condition of the vehicle.

17. The method according to any one of claims 11-16, characterized in that, The method further includes: Receive a vulnerability detection instruction from the user, where the vulnerability detection instruction is used to indicate that the server performs a vulnerability detection on the vehicle; Send the vulnerability detection instruction to the server.

18. A method for repairing vehicle vulnerabilities, characterized in that, The method includes: Receive information about the first vulnerability and the recommended upgrade time, where the first vulnerability is a vulnerability existing in the first component of the vehicle; Receive an upgrade instruction selected by the user, where the upgrade instruction is used to indicate the time selected by the user to upgrade the first component; Send the upgrade instruction to the server.

19. The method according to claim 18, wherein The recommended upgrade time is related to the vulnerability level of the first vulnerability, the level of security impact of the first vulnerability on the vehicle, and the status information of the vehicle.

20. The method according to claim 18 or 19, characterized in that, The interval between the recommended upgrade time and the current time is negatively correlated with the vulnerability level of the first vulnerability, and the vulnerability level of the first vulnerability is positively correlated with the harm of the first vulnerability to the vehicle.

21. The method according to any one of claims 18-20, characterized in that, The vulnerability level of the first vulnerability is related to the vulnerability score of the first vulnerability, and the vulnerability score of the first vulnerability is related to the information about the first vulnerability.

22. The method according to any one of claims 18-21, characterized in that, The method further includes: Receive first information from the server, where the first information is used to indicate that the user initiates a vulnerability detection instruction.

23. The method according to any one of claims 18-22, characterized in that, The method further includes: Receive a vulnerability detection instruction from the user, where the vulnerability detection instruction is used to indicate that the server performs a vulnerability detection on the vehicle; Send the vulnerability detection instruction to the server.

24. The method according to any one of claims 18 - 23, characterized in that, The method further includes: Sending authorization information to a server, where the authorization information is used to instruct a first terminal to authorize a second terminal to perform a vehicle upgrade operation, and the second terminal is an authorized terminal of the owner of the vehicle; Receiving an upgrade instruction selected by a user, where the upgrade instruction is used to indicate the time for upgrading the first component selected by the user; Sending the upgrade instruction to the server.

25. The method according to any one of claims 18-23, characterized in that, The method further includes: Sending authorization information to a server, where the authorization information is used to instruct a first terminal to authorize a second terminal to perform a vehicle upgrade operation, and the second terminal is an authorized terminal of the owner of the vehicle; Sending second information to the server, where the second information is used to instruct the second terminal to perform a vehicle upgrade operation.

26. A vehicle upgrade device, characterized in that, The vehicle upgrade device includes a communication unit and a processing unit, and the communication unit and the processing unit are used to execute the method according to any one of claims 1-25.

27. A server, characterized in that, The server includes a processor and a memory, and a program is stored in the memory, and the program includes instructions for executing the method according to any one of claims 1-10.

28. A vehicle, characterized in that, The vehicle includes a processor and a memory, and a program is stored in the memory, and the program includes instructions for executing the method according to any one of claims 11-17.

29. A terminal device, characterized in that, The terminal device includes a processor and a memory, and a program is stored in the memory, and the program includes instructions for executing the method according to any one of claims 18-25.

30. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, and the computer program includes instructions for executing the method according to any one of claims 1-25.

Images