Vehicle update verification method and system, computer equipment and storage medium

Abstract

The invention relates to the technical field of vehicles, in particular to a verification method and system for vehicle updating, computer equipment and a storage medium. The vehicle update verification method comprises the steps of obtaining an update function of a target vehicle; matching a vehicle function having an association relationship with the updating function as an association function; and taking the associated function and the update function as a to-be-verified function, and verifying whether the to-be-verified function accords with a target rule so as to output an update file. By adopting the method, the vehicle updating verification efficiency can be improved, and the verification comprehensiveness can be improved so as to improve the reliability of the vehicle updating verification result.

Description

Technical Field

[0001] The present application relates to the field of vehicle technology, and in particular to a vehicle update verification method, a vehicle update verification system, a computer device, and a computer-readable storage medium. Background Art

[0002] When updating a vehicle, it is often accompanied by the tedious work of verifying the changes that have occurred to the vehicle. When engineers who are familiar with the vehicle architecture, relevant regulations, vehicle technology and other information make manual judgments, the verification efficiency is low and may also be affected by their assessment technical capabilities, technical capabilities and subjective consciousness, resulting in unreliable verification results. Summary of the invention

[0003] Based on this, it is necessary to provide a vehicle update verification method, a vehicle update verification system, a computer device and a computer-readable storage medium to address the above-mentioned technical problems, which can improve the efficiency of vehicle update verification and improve the comprehensiveness of verification to improve the reliability of vehicle update verification results.

[0004] On the one hand, a vehicle update verification method is provided, and the vehicle update verification method includes: obtaining an update function of a target vehicle; matching a vehicle function that has an association relationship with the update function as an associated function; using the associated function and the update function as functions to be verified, and verifying whether the functions to be verified comply with target rules to output an update file.

[0005] In one embodiment of the present application, matching vehicle functions that are associated with update functions as associated functions includes: obtaining control unit information of the update function; wherein the control unit information includes information of the control unit for implementing the update function; parsing other vehicle functions that can be implemented by the control unit, and using the other vehicle functions as associated functions.

[0006] In one embodiment of the present application, matching vehicle functions that are associated with the update function as associated functions includes: determining whether other vehicle functions are implemented in conjunction with the update function; and in response to the linkage implementation of other vehicle functions when the update function is implemented, treating other vehicle functions as associated functions.

[0007] In one embodiment of the present application, taking the association function and the update function as the functions to be verified includes: respectively determining whether the target function is associated with the target rule, and determining whether its control unit is associated with the target rule; wherein the target function includes the association function and the update function; in response to the target function being associated with the target rule and its control unit being associated with the target rule, taking the target function as the function to be verified.

[0008] In one embodiment of the present application, determining whether the control unit of the target function is associated with the target rule includes: in response to the target rule being associated with network security, verifying whether the communication information of the control unit implementing the target function has changed; in response to the communication information changing, determining that the control unit of the target function is associated with the target rule.

[0009] In one embodiment of the present application, verifying whether the function to be verified complies with the target rule includes: obtaining the quantization parameters of each function to be verified; determining whether the quantization parameters are within the parameter range preset by the target rule; in response to the quantization parameters being within the parameter range, determining that the function to be verified complies with the target rule.

[0010] In one embodiment of the present application, before obtaining the update function of the target vehicle, it includes: obtaining the vehicle information of the vehicle to be updated; determining whether the vehicle information meets the verification conditions; in response to the vehicle information meeting the verification conditions, using the vehicle to be updated as the target vehicle; and / or, obtaining the update function of the target vehicle includes: obtaining the historical function information and the current function information of each vehicle function of the target vehicle; comparing the historical function information and the current function information of the vehicle function; in response to the current function information of the vehicle function not matching the historical function information, using the vehicle function as the update function.

[0011] In one embodiment of the present application, verifying whether the function to be verified complies with the target rule includes: obtaining the changing resources associated with the function to be verified and analyzing whether the changing resources comply with the target rule; where the changing resources include at least one of a server, a communication protocol, an encryption qualification, underlying code, and a control unit; and / or, outputting an update file includes: based on whether the function to be verified complies with the target rule, outputting the components of the update file; where the components of the update file include at least one of whether to submit to an external agency, the relevance of the function to be verified to the vehicle authentication of the target rule, the system software identification information document of the target vehicle, and the software update information of the function to be verified.

[0012] On the other hand, a vehicle update verification system is provided. The vehicle update verification system includes: a storage module and a verification module; the storage module is used to store the association relationships between the vehicle functions of the vehicle; the verification module is connected to the storage module and is used to implement the vehicle update verification system in any one of the above embodiments.

[0013] On yet another hand, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, it implements the vehicle update verification system in any one of the above embodiments.

[0014] In another aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, it implements the vehicle update verification system in any one of the above embodiments.

[0015] The above vehicle update verification method, vehicle update verification system, computer device, and computer-readable storage medium use this method to automate vehicle update verification, thereby improving the efficiency of vehicle update verification. At the same time, when verifying the update function, this application can also verify the associated vehicle functions to improve the comprehensiveness of the verification, thereby improving the reliability of the vehicle update verification result. Brief Description of the Drawings

[0016] Figure 1 is a flowchart of an embodiment of the vehicle update verification method of the present application;

[0017] Figure 2 is a flowchart of another embodiment of the vehicle update verification method of the present application;

[0018] Figure 3 is a flowchart of yet another embodiment of the vehicle update verification method of the present application;

[0019] Figure 4 is a structural diagram of an embodiment of the vehicle update verification system of the present application;

[0020] Figure 5 is a structural diagram of an embodiment of the computer device of the present application. Detailed Embodiments

[0021] In order to make the objectives, technical solutions, and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0022] As described above, when judging whether vehicle updates will cause the vehicle to not meet the target rules, it mainly relies on engineers with strong professionalism, that is, artificial evaluation is carried out by engineers who are familiar with technologies, regulations, and the overall vehicle architecture such as vehicle-road-cloud-pipe-diagram. However, this is often subject to the subjective influence of the evaluating engineer, which may involve subjective consciousness, familiarity with the overall vehicle, and the understanding scale of regulations, etc., all of which may lead to untrustworthy evaluation results. Moreover, when engineers conduct evaluations, they also need to consume a lot of resources and have a long evaluation cycle. Even the evaluation process may have risk contents that are not covered, further exacerbating the limitations of manual vehicle update verification.

[0023] To solve the technical problems of low efficiency and poor reliability of vehicle update verification in related technologies, the present application provides a verification method for vehicle update, a verification system for vehicle update, a computer device, and a computer-readable storage medium. The verification method for vehicle update includes: obtaining the update function of a target vehicle; matching the vehicle function having an association relationship with the update function as an associated function; using the associated function and the update function as functions to be verified, and verifying whether the functions to be verified comply with the target rules to output an update file. The specific working principle of the present application is illustrated by the following examples. Optionally, the present application can be implemented by using a pre-trained large model, a designed algorithm, or AI (Artificial Intelligence), etc., to realize the automation of vehicle update verification, effectively reducing the need for human participation in the vehicle update verification process, so as to reduce the unreliability of the verification result affected by human subjectivity, that is, the present application can improve the reliability of the vehicle update verification result and is beneficial to significantly improving the verification efficiency.

[0024] Please refer to Figure 1 , Figure 1 which is a schematic flowchart of an embodiment of the verification method for vehicle update of the present application.

[0025] S101: Obtain the update function of the target vehicle.

[0026] In this embodiment, the target vehicle refers to a vehicle that has been updated but has not been fully put into mass production, or a vehicle waiting to confirm whether the update is feasible and perform an actual update, etc. It can represent a single vehicle, or a model of vehicle, or a series of vehicles, which is not limited herein. The update function refers to the vehicle function that has changed in the target vehicle.

[0027] The vehicle function refers to the control and auxiliary functions of the vehicle, such as the brake function, window control function, wiper function, speaker function, gear control function, etc., which will not be elaborated herein.

[0028] S102: Match the vehicle function having an association relationship with the update function as an associated function.

[0029] In this embodiment, it is possible to identify whether each vehicle function of the target vehicle is associated with the update function, so as to use the vehicle function having an association relationship with the update function as the associated function. Optionally, it is possible to match other vehicle functions of the target vehicle with the update function. Other vehicle functions can represent vehicle functions other than the update function, that is, vehicle functions that have not been updated.

[0030] S103: Use the associated function and the update function as functions to be verified, and verify whether the functions to be verified comply with the target rules to output an update file.

[0031] In this embodiment, the target rules may include the regulatory rules that the target vehicle needs to comply with. For example, the regulatory rules may include vehicle-related laws, regulations, regulations of institutions, etc., which are not limited here. The update file may include update information of the target rule requirements, etc.

[0032] In this embodiment, when verifying whether the vehicle update complies with the target rules, while verifying whether the updated vehicle functions affect the target vehicle's compliance with the target rules, some vehicle functions that have not been updated will also be verified together, so as to improve the comprehensiveness of the verification of the target vehicle.

[0033] Optionally, the target rules may be related to personal safety, property protection, vehicle control, data leakage, network security, etc.

[0034] That is to say, in this embodiment, the automation of vehicle update verification is realized to reduce the manual verification of compliance with the target rules, so as to reduce the risk of misjudgment caused by subjective human judgment and reduce the human skill training resources and cycle. Moreover, it can reduce the evaluation training of a large number of engineers on the target rules, and can also reduce the situation that problems are likely to occur in the evaluation process due to the evaluation and coordination of multiple engineers. Furthermore, it can improve the efficiency of vehicle update verification. At the same time, in this embodiment, when verifying the vehicle update, while verifying the updated functions, the associated functions will also be verified to improve the comprehensiveness of the verification while reducing the verification of vehicle functions unrelated to the target rules. Thus, it can reduce the situation where although the updated functions do not affect compliance with the target rules, their associated functions may affect the vehicle's compliance with the target rules but are not recognized, and further improve the reliability of the vehicle update verification result.

[0035] Furthermore, the regulatory rules included in the target rules in this embodiment can also change, so as to enhance the scalability of vehicle update verification in this embodiment. For example, with the emergence of new regulatory rules, the new regulatory rules can be added to the target rules in this embodiment; and / or, as the regulatory rules change, the target rules in this embodiment can be adaptively modified; and / or, as the regulatory rules are cancelled, the target rules can be adaptively deleted, so as to improve the generalizability of vehicle update verification in this embodiment, improve the adaptability of vehicle update verification, and enrich its application scenarios.

[0036] Please refer to Figure 2 , Figure 2 which is a schematic flowchart of another embodiment of the method for verifying vehicle update in this application.

[0037] S201: Obtain the vehicle information of the vehicle to be updated.

[0038] In this embodiment, the vehicle to be updated may represent a vehicle for which it is to be confirmed whether it can be updated according to the current update method; alternatively, it may represent a vehicle to be mass-produced after the update; alternatively, it may represent a mass-produced vehicle but awaiting verification of the update, etc., and no strict limitation is made here.

[0039] The vehicle information can at least identify the updated vehicle.

[0040] For example, the vehicle information may include at least one of the vehicle model, the function number of the update function, the purpose of the vehicle update, the name of the control unit, and the quantitative parameters before and after the change.

[0041] Ideally, libraries such as a library including the vehicle model and the vehicle functions it has, a library including the association relationships between vehicle functions, a library including the association relationships between vehicle functions and their control units, a library including the vehicle model and the purposes of previous updates, etc. can be maintained. Thus, when performing vehicle update verification, the vehicle model can be input and the information required for vehicle update verification can be obtained according to multiple libraries.

[0042] S202: Determine whether the vehicle information meets the verification conditions.

[0043] In this embodiment, when it is determined that the vehicle information of the vehicle to be updated meets the verification conditions, it can be considered that the vehicle needs to perform update verification, so step S203 is executed; when it is determined that the vehicle information of the vehicle to be updated does not meet the verification conditions, it can be considered that the vehicle does not need or temporarily does not need to perform update verification, so the process ends.

[0044] For example, the vehicle information may include at least one of the vehicle stage information, the change content information of the vehicle update, and the vehicle model. Thus, the verification conditions may include that the vehicle stage is between the R & D completion stage and the mass production stage, the change content includes software change, and the vehicle model has at least one of the verification requirements for whether it meets the target rules.

[0045] Specifically, the project code of the updated vehicle can be obtained, etc., the vehicle stage currently associated with the project code can be determined, and it can be determined whether the updated vehicle is between the R & D completion stage and the mass production stage. When the updated vehicle is between the R & D completion stage and the mass production stage, update verification is allowed for it. Such a design in this embodiment can take into account that although vehicle functions are changed during the R & D stage of the vehicle, the current change content may not be actually applied, so vehicle update verification is not performed, thereby reducing the verification of updates that are not actually applied, that is, being able to reduce useless verification work. Moreover, it can also perform verification before the updated vehicle is mass-produced, thereby being able to reduce the risk that the vehicle does not meet the target rules but has already been driven on the road, and being able to improve the reliability of vehicle update verification to improve the safety and reliability of the vehicle.

[0046] If the target rule is a software rule and regulation related to network security, etc., it can be determined whether there is a software change in the updated vehicle. If the updated vehicle does not involve software changes such as code modification and software architecture change, it can be determined that there is no need to perform an update verification on the vehicle. If the updated vehicle involves software changes, it is regarded as the target vehicle that needs to be updated and verified.

[0047] It can be determined whether the updated vehicle has a verification requirement that complies with the target rule. For example, if the target rule includes the rules and regulations of Region X, and the updated Model A vehicle is not planned to be sold in Region X, it is considered that Model A vehicle may not need to be verified whether it complies with the rules and regulations of Region X. If the target rule includes the rules and regulations of Region Y, and Model A vehicle is planned to be sold in Region Y, then Model A vehicle is verified whether it complies with the rules and regulations of Region Y.

[0048] In this way, in this embodiment, it is possible to determine whether the updated vehicle needs to be verified for vehicle update, so as to reduce the cumbersome work of verifying the update of vehicles that do not need to be verified, which is beneficial to releasing the computing resources of the vehicle update verification system.

[0049] S203: Take the vehicle to be updated as the target vehicle.

[0050] In this embodiment, in response to the vehicle information meeting the verification conditions, the vehicle to be updated is taken as the target vehicle, that is, it is taken as the vehicle that needs to be verified for vehicle update.

[0051] S204: Obtain the historical function information and current function information of each vehicle function of the target vehicle.

[0052] In this embodiment, the historical function information represents the function information of the vehicle function before the target vehicle is updated. The current function information represents the function information of the vehicle function after the target vehicle is updated.

[0053] S205: Compare the historical function information and current function information of the vehicle function.

[0054] In this embodiment, when it is determined that the historical function information of the vehicle function matches the current function information, it can be considered that the vehicle function may not have changed, so the process ends; it is also possible to obtain the next vehicle function and determine whether it is updated until all vehicle functions are traversed. When it is determined that the historical function information of the vehicle function does not match the current function information, it can be considered that the function information of the vehicle function has changed and the vehicle function may have been updated, so step S206 is executed.

[0055] S206: Take the vehicle function as the updated function.

[0056] In response to the current function information of the vehicle function not matching the historical function information, the vehicle function is taken as the updated function.

[0057] Optionally, in this embodiment, a functional information library of vehicle functions such as EBOM (electronic bill of materials) and SBOM (software bill of materials) can be created and maintained to timely maintain and update the functional information of the vehicle functions, and the functional information changes of the vehicle functions in the functional information library can be automatically compared to confirm the updated functions.

[0058] S207: Matching a vehicle function that has an associated relationship with the update function as an associated function.

[0059] In this embodiment, other vehicle functions associated with the update function may be acquired as associated functions to participate in the vehicle update verification process.

[0060] Specifically, the control unit information of the update function may be obtained, wherein the control unit information includes information of the control unit for implementing the update function. Other vehicle functions that can be implemented by the control unit are parsed, and the other vehicle functions are used as associated functions to identify the vehicle functions associated with the update function from the control unit side.

[0061] For example, the control unit of the update function Z1 is the control unit E1, and the query control unit E1 also implements the vehicle function H and the vehicle function I, so the vehicle function H and the vehicle function I are taken as the associated functions of the update function Z1. The control unit may be an EMC (electronic control unit), etc., which is not limited here.

[0062] And / or, it can be determined whether other vehicle functions are implemented in conjunction with the implementation of the update function. The other vehicle functions may refer to vehicle functions other than the update function.

[0063] In response to other vehicle functions not being implemented in conjunction with the update function, the other vehicle functions are determined to be non-associated functions. In response to other vehicle functions being implemented in conjunction with the update function, the other vehicle functions are considered as associated functions to identify the associated functions from the vehicle function implementation side.

[0064] For example, when the vehicle realizes the braking function, the transmission function will transmit the corresponding signal, and the vehicle's brake lights will also light up. When the braking function is equivalent, the transmission function and the brake light function are realized in conjunction. Therefore, it can be considered that the braking function, the transmission function, and the brake light function are associated. For example, when the braking function is an update function, the transmission function and the brake light function are associated functions.

[0065] S208: Determine whether the target function is associated with the target rule.

[0066] In this embodiment, when it is determined that the target function is associated with the target rule, it can be considered that the target function may affect whether the vehicle complies with the target rule. Therefore, it is necessary to verify the target function, and thus step S209 is executed. When it is determined that the target function is not associated with the target rule, it can be considered that the target function may have a relatively small impact on whether the vehicle complies with the target rule. Therefore, the process can end; alternatively, the next target function can be obtained to determine whether it is associated with the target rule until all target functions are traversed.

[0067] In this embodiment, the target function may include an associated function and an update function. It is possible to separately determine whether the target function is associated with the target rule to improve the comprehensiveness of verifying whether the vehicle function will affect the vehicle's compliance with the target rule.

[0068] S209: Determine whether the control unit of the target function is associated with the target rule.

[0069] In this embodiment, when it is determined that the target function is associated with the target rule, it can be considered that the control unit of the target function may affect whether the vehicle complies with the target rule. Therefore, it is necessary to verify the target function, and thus step S210 is executed. When it is determined that the control unit of the target function is not associated with the target rule, it can be considered that the control unit of the target function may have a relatively small impact on whether the vehicle complies with the target rule. Therefore, the process can end; alternatively, the next target function associated with the target rule can be obtained to determine whether its control unit is associated with the target rule until all target functions associated with the target rule are traversed.

[0070] Specifically, taking the target rule associated with network security as an example. It is possible to verify whether the communication information of the control unit implementing the target function has changed.

[0071] If so, in response to the change in communication information, it is determined that the control unit of the target function is associated with the target rule. If so, in response to the communication information not changing, it is determined that the control unit of the target function is not associated with the target rule.

[0072] Optionally, the communication information may include at least one of programming language, operating system, encryption mechanism, communication system, and communication mechanism.

[0073] For example, it is possible to determine whether the programming language of the control unit software has changed. And / or, it is possible to determine whether the operating system of the software has changed. And / or, it is possible to determine whether the encryption mechanism of the control unit software has been added or changed. And / or, it is possible to determine whether the communication system of the control unit software has been added or changed. And / or, it is possible to determine whether the communication mechanism has been added or changed. For example, if a new communication mechanism such as Bluetooth is added, it can be considered that the communication mechanism has changed.

[0074] In addition, in an alternative embodiment, the update function can be used as the target function only. When the current function is not associated with the target rule and its control unit is not associated with the target rule, it is not necessary to obtain its associated function to reduce the amount of computation.

[0075] S210: Use the target function as the function to be verified.

[0076] In this embodiment, in response to the target function being associated with the target rule and its control unit being associated with the target rule, the target function can be used as the function to be verified.

[0077] S211: Verify whether the function to be verified complies with the target rule to output an update file.

[0078] In this embodiment, it is possible to verify whether each function to be verified complies with the target rule respectively, and form an update file for the requirements of the target rule based on the verification results of each function to be verified.

[0079] Specifically, it is possible to obtain the quantization parameters of each function to be verified. Among them, the quantization parameter represents a parameter that is associated with the function to be verified and within the preset parameter range of the target rule.

[0080] Judge whether the quantization parameter is within the parameter range preset by the target rule.

[0081] In response to the quantization parameter being within the parameter range, it is determined that the function to be verified complies with the target rule. In response to the quantization parameter not being within the parameter range, it is determined that the function to be verified does not comply with the target rule.

[0082] For example, when changing relevant vehicle functions such as the network and communication of the target vehicle, the relevant parameter data of the electromagnetic wave can be used as the quantization parameter to judge whether the relevant parameters of the electromagnetic wave are within the parameter range preset by the target rule.

[0083] In an alternative embodiment, when verifying whether the function to be verified complies with the target rule, other verification contents can be included, which will not be elaborated here one by one.

[0084] Thus, in this embodiment, it is possible to verify whether the control unit of the update function will affect the vehicle's compliance with the target rule, and it is also possible to verify whether the associated function of the update function will have an impact, so as to improve the comprehensiveness of vehicle update verification. At the same time, it will also verify whether the quantization parameters of the update function and / or the associated function comply with the target rule, which can improve the reliability of the verification result while facilitating the automatic formation of the update file. And in this embodiment, it is also possible to judge and self-identify whether the updated vehicle needs to perform vehicle update verification and the target rule to be verified, which can further improve the functionality of vehicle update verification and reduce unnecessary vehicle update verification, saving computing resources.

[0085] Please refer to Figure 3 , Figure 3 which is a schematic flowchart of another embodiment of the vehicle update verification method of this application.

[0086] S301: Input the change information of the updated vehicle.

[0087] In this embodiment, the change information may include, for example, the vehicle model, the function number of the updated function, the change content, etc. as exemplified in Figure 3 . Or, as described in the previous text, by maintaining several associated libraries, databases, etc. related to the vehicle, only the vehicle model number of the updated vehicle can be input, so as to automatically extract the information required for vehicle update verification through the mapping relationship between the associated libraries and databases. In this way, the updated vehicle can be used as a vehicle to be updated for verifying whether to perform an update or as a target vehicle.

[0088] S302: Determine whether it affects compliance with the target rules.

[0089] In this embodiment, when it is determined that the target rules are not met, step S303 can be executed. When it is determined that it affects compliance with the target rules, step S304 is executed.

[0090] In this embodiment, this step can be the vehicle update verification method described in the previous embodiment, and it can be determined whether it will affect the vehicle's compliance with the target rules from aspects such as vehicle functions and control units, which will not be elaborated here.

[0091] S303: Determine whether it affects compliance with the target rules in combination with the extended information.

[0092] In this embodiment, the extended information may include a vulnerability library, an attack path for network security, etc. It can also link the vulnerability library, etc. through means such as AI (i.e., artificial intelligence), manual attention and acquisition, and use the vulnerability library, etc. as the extended information to further verify whether it will affect the vehicle's compliance with the target rules in combination with the extended information.

[0093] For example, an updated vulnerability library can be obtained, which reveals that there is a risk in version 3.5 of operating system S. Query the control unit using version 3.5 of operating system S in the target vehicle, and consider that it has a risk of affecting the vehicle's compliance with the target rules, and consider the vehicle functions implemented by its control as vehicle functions that may affect the vehicle's compliance with the target rules for further analysis. In other words, in this embodiment, risks such as vehicle functions, control units, vulnerability libraries, EBOM, SBOM, target rules, and function paths can also be analyzed and reported more comprehensively to make up for possible deficiencies that cannot be covered by humans, and further improve the comprehensiveness and result reliability of the verification of whether the vehicle meets the target rules.

[0094] S304: Perform an extended application and output an updated file.

[0095] In this embodiment, the extended application represents the output for implementing the extended requirements of the target rule.

[0096] That is, in response to determining that the vehicle update will affect compliance with the target rule, it can be considered that the extended requirements output of the target rule is executed, and an updated file is output.

[0097] Optionally, the components of the updated file can be output based on whether the function to be verified complies with the target rule.

[0098] The components of the updated file can include at least one of the following: whether it is necessary to submit to an external agency, the relevance of the function to be verified to the vehicle certification of the target rule, the system software identification information document of the target vehicle, and the software update information of the function to be verified.

[0099] Among them, whether it is necessary to submit to an external agency can include: whether it is necessary to submit to an external agency such as an approval agency for an extended report, and / or whether it is required that the external agency can supplement and issue an extended report, etc.

[0100] The relevance of the function to be verified to the vehicle certification of the target rule can include: whether the software update belongs to the vehicle certification content required by the target rule, where the function to be verified, the associated system, the update purpose, etc. formed can be analyzed; and / or whether the changes existing in the software update affect the vehicle type certifications of other vehicle types, vehicles, and / or other target rules of the current vehicle; and / or whether the function to be verified causes changes in the quantitative parameters specified by the target rule.

[0101] The system software identification information document of the target vehicle can include, for example, an RxSWIN (system software identification information) document, etc., which is not limited here.

[0102] The software update information of the function to be verified can include: software update condition requirements; and / or the software update can be carried out safely and reliably, that is, in compliance with the target rule; and / or the information that the function to be verified passes the vehicle software update verification.

[0103] For example, the output updated file can include the following content:

[0104] 1) Whether to submit the changed content to the approval agency for an extended report; 2) The purpose of the software update, the affected systems and functions, and whether they are part of the vehicle type approval content; 3) Whether this change affects other vehicle type approval items; 4) Whether there are vehicle type approval parameters affected; 5) Issue the RxSWIN (i.e., system software identification information) document; 6) Whether to request the approval agency to approve the addition of extended content; 7) Software update condition requirements; 8) Confirm that the software update will be carried out safely and reliably; 9) Confirm that the software update has passed and successfully passed the verification and validation procedures, etc.

[0105] S305: It is determined that no extended application is required.

[0106] In this embodiment, in response to both step S302 and step S303 determining that the risk of affecting compliance with the target rules is small or that compliance with the target rules is not affected, it is determined that the target vehicle does not need to make an extended application.

[0107] Furthermore, in this embodiment, the resources that may be triggered by the vehicle functions that need to be changed in the target vehicle can be exported from the existing database, and the resources required by the vehicle functions are used as the changed resources associated with the functions to be verified, and threat and risk analysis is performed on them. Among them, the changed resources may include servers, communication protocols, encryption qualifications, underlying code, control units, etc. In other words, the changed resources associated with the functions to be verified can be obtained to analyze whether the changed resources comply with the target rules, so as to improve the richness and rationality of the vehicle update verification process, and further improve the reliability of the verification results.

[0108] The existing database or the historical change database can be searched for a relatively safe asset assessment. It is also possible to execute the conditions required for the change to compare the vehicle functions, components, parameters, etc. that may be caused with the target rules, so as to issue the risks and risk levels existing in the vehicle function change or vehicle update. It is also possible to further issue an assessment conclusion on whether an extended application needs to be made for the target rules and issue an update document to facilitate the automated generation of the document.

[0109] It should be understood that although Figures 1 to 3 the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear indication in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, Figures 1 to 3At least a part of the steps may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed and completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed alternately or in turn with at least a part of other steps or sub-steps or stages of other steps.

[0110] Please refer to Figure 4 , Figure 4 which is a schematic structural diagram of an embodiment of the vehicle update verification system of the present application.

[0111] In one embodiment, the vehicle update verification system includes a storage module 11 and a verification module 12.

[0112] The storage module 11 is used to store the association relationship between vehicle functions. Among them, the storage module 11 can directly store the association relationship between vehicle functions, or can indirectly store the association relationship between vehicle functions through multiple mapped databases, etc., which is not limited here.

[0113] The verification module 12 is connected to the storage module 11 and is used to implement the vehicle update verification system in any of the above embodiments.

[0114] For the specific limitations of the vehicle update verification system, reference can be made to the limitations of the vehicle update verification method in the above text, which will not be elaborated here. Each module in the above vehicle update verification system can be implemented in whole or in part by software, hardware and their combination. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules. In one embodiment, a computer program product is provided, including a computer program. When the computer program is executed by the processor, the steps of the vehicle update verification method described above are implemented, which will not be elaborated here.

[0115] Please refer to Figure 5 , Figure 5 which is a schematic structural diagram of an embodiment of the computer device of the present application.

[0116] In one embodiment, the computer device can be a server, or the computer device can be a terminal, which is not limited here.

[0117] Taking the computer device as a server as an example, its internal structure diagram can be as Figure 5 exemplarily shown in

[0118] The computer device includes a processor, a memory, a network interface and a database connected through a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a vehicle update verification method is implemented.

[0119] Those skilled in the art will understand that Figure 5 The structure shown as an example is merely a block diagram of a portion of the structure related to the present application solution, and does not constitute a limitation on the computer device to which the present application solution is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0120] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following steps can be implemented: obtaining an update function of a target vehicle; matching vehicle functions that have an association relationship with the update function as associated functions; using the associated functions and the update function as functions to be verified, and verifying whether the functions to be verified comply with target rules, so as to output an update file.

[0121] In one embodiment, when matching a vehicle function associated with an update function as an associated function, the processor can also implement the following steps when executing a computer program: obtaining control unit information of the update function; wherein the control unit information includes information of a control unit for implementing the update function; parsing other vehicle functions that can be implemented by the control unit, and treating the other vehicle functions as associated functions.

[0122] In one embodiment, when matching a vehicle function that is associated with the update function as an associated function, the processor can also implement the following steps when executing the computer program: determine whether other vehicle functions are implemented in conjunction with the update function; in response to the linkage implementation of other vehicle functions when the update function is implemented, treat the other vehicle functions as associated functions.

[0123] In one embodiment, when the association function and the update function are used as functions to be verified, the following steps can also be implemented when the processor executes the computer program: respectively determine whether the target function is associated with the target rule, and determine whether its control unit is associated with the target rule; wherein, the target function includes the association function and the update function; in response to the target function being associated with the target rule and its control unit being associated with the target rule, use the target function as the function to be verified.

[0124] In one embodiment, when determining whether the control unit of the target function is associated with the target rule, the following steps can also be implemented when the processor executes the computer program: in response to the target rule being associated with network security, verify whether the communication information of the control unit implementing the target function has changed; in response to the communication information changing, determine that the control unit of the target function is associated with the target rule.

[0125] In one embodiment, when verifying whether the function to be verified conforms to the target rule, the following steps can also be implemented when the processor executes the computer program: obtain the quantization parameters of each function to be verified; determine whether the quantization parameters are within the parameter range preset by the target rule; in response to the quantization parameters being within the parameter range, determine that the function to be verified conforms to the target rule.

[0126] In one embodiment, before obtaining the update function of the target vehicle, the following steps can also be implemented when the processor executes the computer program: obtain the vehicle information of the vehicle to be updated; determine whether the vehicle information meets the verification conditions; in response to the vehicle information meeting the verification conditions, use the vehicle to be updated as the target vehicle; and / or, when obtaining the update function of the target vehicle, the following steps can also be implemented when the processor executes the computer program: obtain the historical function information and the current function information of each vehicle function of the target vehicle; compare the historical function information and the current function information of the vehicle function; in response to the current function information of the vehicle function not matching the historical function information, use the vehicle function as the update function.

[0127] In one embodiment, when verifying whether the function to be verified conforms to the target rule, the following steps can also be implemented when the processor executes the computer program: obtain the change resources associated with the function to be verified, and analyze whether the change resources conform to the target rule; wherein, the change resources include at least one of a server, a communication protocol, an encryption qualification, underlying code, and a control unit; and / or, when outputting an update file, the following steps can also be implemented when the processor executes the computer program: based on whether the function to be verified conforms to the target rule, output the components of the update file; wherein, the components of the update file include at least one of whether it is necessary to submit to an external institution, the relevance of the function to be verified to the vehicle authentication of the target rule, the system software identification information document of the target vehicle, and the software update information of the function to be verified.

[0128] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: obtaining an update function of a target vehicle; matching vehicle functions that have an association relationship with the update function as associated functions; using the associated function and the update function as functions to be verified, and verifying whether the functions to be verified comply with target rules to output an update file.

[0129] In one embodiment, when matching a vehicle function associated with an update function as an associated function, the following steps may also be implemented when the computer program is executed by the processor: obtaining control unit information of the update function; wherein the control unit information includes information of a control unit for implementing the update function; parsing other vehicle functions that can be implemented by the control unit, and treating the other vehicle functions as associated functions.

[0130] In one embodiment, when a vehicle function that is matched and associated with an update function is used as an associated function, the following steps may also be implemented when the computer program is executed by the processor: determining whether other vehicle functions are implemented in conjunction with the update function; and in response to other vehicle functions being implemented in conjunction with the update function, treating the other vehicle functions as associated functions.

[0131] In one embodiment, when the association function and the update function are taken as the functions to be verified, the following steps can also be implemented when the computer program is executed by the processor: respectively determining whether the target function is associated with the target rule, and determining whether its control unit is associated with the target rule; wherein the target function includes the association function and the update function; in response to the target function being associated with the target rule and its control unit being associated with the target rule, taking the target function as the function to be verified.

[0132] In one embodiment, when determining whether a control unit of a target function is associated with a target rule, the following steps may also be implemented when the computer program is executed by the processor: in response to the target rule being associated with network security, verifying whether the communication information of the control unit implementing the target function has changed; in response to the change in communication information, determining that the control unit of the target function is associated with the target rule.

[0133] In one embodiment, when checking whether the function to be checked complies with the target rule, the computer program can also implement the following steps when executed by the processor: obtaining the quantization parameter of each function to be checked; determining whether the quantization parameter is within the parameter range preset by the target rule; in response to the quantization parameter being within the parameter range, determining that the function to be checked complies with the target rule.

[0134] In one embodiment, before obtaining the update function of the target vehicle, the following steps can also be implemented when the computer program is executed by the processor: obtaining the vehicle information of the vehicle to be updated; determining whether the vehicle information meets the verification conditions; in response to the vehicle information meeting the verification conditions, taking the vehicle to be updated as the target vehicle; and / or, when obtaining the update function of the target vehicle, the following steps can also be implemented when the computer program is executed by the processor: obtaining the historical function information and the current function information of each vehicle function of the target vehicle; comparing the historical function information and the current function information of the vehicle function; in response to the current function information of the vehicle function not matching the historical function information, taking the vehicle function as the update function.

[0135] In one embodiment, when verifying whether the function to be verified meets the target rules, the following steps can also be implemented when the computer program is executed by the processor: obtaining the change resources associated with the function to be verified, and analyzing whether the change resources meet the target rules; wherein, the change resources include at least one of a server, a communication protocol, an encryption qualification, underlying code, and a control unit; and / or, when outputting an update file, the following steps can also be implemented when the computer program is executed by the processor: based on whether the function to be verified meets the target rules, outputting the composition items of the update file; wherein, the composition items of the update file include at least one of whether it is necessary to submit to an external agency, the relevance between the function to be verified and the vehicle authentication to which the target rules belong, the system software identification information document of the target vehicle, and the software update information of the function to be verified.

[0136] Those of ordinary skill in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the various embodiments provided in the present application can include non-volatile and / or volatile memories. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or an external cache. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0137] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered that the scope recorded in this specification.

[0138] The embodiments described above only represent several implementation manners of the present application. The description is relatively specific and detailed, but it should not be construed as a limitation on the scope of the invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all belong to the protection scope of the present application.

Claims

1. A vehicle update verification method, characterized in that, The verification method comprises: Get the updated function of the target vehicle; matching a vehicle function associated with the update function as an associated function; The associated function and the update function are used as functions to be verified, and whether the functions to be verified comply with target rules is verified, so as to output an update file.

2. The verification method according to claim 1, wherein The matching of the vehicle functions associated with the update function includes, as associated functions: Acquire control unit information of the update function; wherein the control unit information includes information of a control unit used to implement the update function; Other vehicle functions that can be realized by the control unit are analyzed, and the other vehicle functions are used as the associated functions.

3. The verification method according to claim 1 or 2, characterized in that, The matching of the vehicle functions associated with the update function includes, as associated functions: Determining whether other vehicle functions are implemented in conjunction with the implementation of the update function; In response to the other vehicle functions being implemented in conjunction with the implementation of the update function, the other vehicle functions are used as the associated functions.

4. The verification method according to claim 1, characterized in that, The taking the associated function and the update function as functions to be verified comprises: respectively determining whether a target function is associated with the target rule, and determining whether its control unit is associated with the target rule; wherein the target function includes the association function and the update function; In response to the target function being associated with the target rule and its control unit being associated with the target rule, the target function is used as the function to be checked.

5. The verification method according to claim 4, characterized in that, Determining whether the control unit of the target function is associated with the target rule includes: In response to the target rule being associated with the network security, verifying whether communication information of a control unit implementing the target function is changed; In response to the communication information change, a control unit determines that the target function is associated with the target rule.

6. The verification method according to claim 1, characterized in that, The checking whether the function to be checked complies with the target rule comprises: Obtaining the quantitative parameters of each of the functions to be verified; Determining whether the quantization parameter is within a parameter range preset by the target rule; In response to the quantization parameter being within the parameter range, it is determined that the function to be checked complies with the target rule.

7. The verification method according to claim 1, characterized in that The updating function of obtaining the target vehicle includes: Obtain vehicle information of the vehicle to be updated; Determining whether the vehicle information meets the verification conditions; In response to the vehicle information meeting the verification condition, taking the vehicle to be updated as the target vehicle; and / or, The update function of obtaining the target vehicle includes: Acquire historical function information and current function information of each vehicle function of the target vehicle; comparing the historical function information and the current function information of the vehicle function; In response to the current function information of the vehicle function not matching the historical function information, the vehicle function is used as the update function.

8. The verification method according to claim 1, wherein The checking whether the function to be checked complies with the target rule comprises: Acquire the changed resources associated with the function to be verified, and analyze whether the changed resources comply with the target rules; wherein the changed resources include at least one of a server, a communication protocol, an encryption qualification, an underlying code, and a control unit; and / or, The output update file includes: Output an update file component based on whether the function to be verified complies with the target rule; wherein, the update file component includes at least one of: whether to submit to an external agency, the relevance of the function to be verified to the vehicle certification to which the target rule belongs, the system software identification information document of the target vehicle, and the software update information of the function to be verified.

9. A vehicle update verification system, characterized in that, The verification system includes: A storage module for storing the association relationships between vehicle functions of a vehicle; A verification module connected to the storage module for implementing the vehicle update verification system according to any one of claims 1 to 8.

10. A computer device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the computer program, the steps of the vehicle update verification method according to any one of claims 1 to 8 are implemented.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, the steps of the vehicle update verification method according to any one of claims 1 to 8 are implemented.

Images