Configuration parameter verification method and device based on AUTOSAR

Abstract

The invention provides a configuration parameter verification method and device based on AUTOSAR, and relates to the technical field of data verification, and the method comprises the steps: obtaining a to-be-verified configuration parameter in AUTOSAR related parameters, and determining a target function module corresponding to the to-be-verified configuration parameter; a target check code corresponding to a target functional module is determined in a check code set corresponding to each functional module of the AUTOSAR, the target check code comprises names, error levels, check types and sub-check codes of the functional modules, the names of the functional modules are used for indicating the functional modules to which the check code is applicable, and the sub-check codes are used for indicating the functional modules to which the check code is applicable; the error level is used for indicating a danger level of an error when verification fails, and the verification type and the sub-verification code are used for indicating a verification rule; and verifying the to-be-verified configuration parameter based on the verification type in the target verification code and the verification rule indicated by the sub-verification code to obtain a verification result. The method and the device are used for solving the problem that the verification accuracy of configuration parameters in all function modules of the AUTOSAR is low.

Description

Technical Field

[0001] The present application relates to the field of data verification technology, and in particular to a configuration parameter verification method and device based on AUTOSAR. Background Art

[0002] AUTOSAR (Automotive Open System Architecture) is a collaborative development framework for automotive electronic systems. Its goal is to create a shared, open standard for embedded automotive software development to improve and manage complex systems. When users configure parameters for AUTOSAR functional modules, these parameters must meet the AUTOSAR standard's requirements to proceed correctly to the next step.

[0003] Currently, commonly used verification rules are only applicable to a certain functional module of AUTOSAR, resulting in low verification accuracy for parameters of other functional modules. Summary of the Invention

[0004] In order to solve the problem of low verification accuracy of configuration parameters in various AUTOSAR functional modules, embodiments of the present application provide a configuration parameter verification method and apparatus based on AUTOSAR to improve the verification accuracy of configuration parameters in various AUTOSAR functional modules.

[0005] In a first aspect, an embodiment of the present application provides an AUTOSAR configuration parameter verification method, comprising:

[0006] Obtain the configuration parameters to be verified in the AUTOSAR related parameters, and determine the target functional module corresponding to the configuration parameters to be verified;

[0007] Determining a target check code corresponding to a target functional module from a check code set corresponding to each functional module of AUTOSAR, wherein the target check code includes: a name of the functional module, an error level, a check type, and a sub-check code, wherein the name of the functional module is used to indicate the functional module to which the check code applies, the error level is used to indicate the danger level of the error when the check fails, and the check type and the sub-check code are used to indicate a check rule;

[0008] The configuration parameter to be verified is verified based on the verification type in the target verification code and the verification rule indicated by the sub-verification code to obtain a verification result.

[0009] As an optional implementation of the embodiment of the present application, before determining the target functional module corresponding to the configuration parameter to be verified, the method further includes:

[0010] For each functional module of AUTOSAR, a sub-check code and a check type are determined based on the check rules corresponding to each configuration parameter in the functional module. The sub-check codes include: mutually exclusive configuration check code, duplicate configuration check code, and dynamic missing configuration check code. The check types include: basic check, semantic check, and grammatical check.

[0011] The names, error levels, check types, and sub-check codes of the functional modules are spliced according to a preset check code format to generate check codes corresponding to the functional modules, and the check code set is formed based on the check codes of the functional modules.

[0012] As an optional implementation of the embodiment of the present application, after obtaining the verification result, the method further includes:

[0013] Generate a verification report corresponding to the configuration parameter to be verified, the verification report including: the verification result, verification details, the path of the configuration parameter to be verified, the target verification code, and a verification code summary corresponding to the target verification code;

[0014] The verification report is visually displayed in a preset form.

[0015] As an optional implementation of the embodiment of the present application, the visual display of the verification report in a preset form includes:

[0016] The verification report is visually displayed in the form of a user interface; or, the verification report is visually displayed in the form of a log file; or, the verification report is visually displayed in the form of a Web interface.

[0017] As an optional implementation of the embodiment of the present application, determining the target check code corresponding to the target functional module from the check code set corresponding to each functional module of AUTOSAR includes:

[0018] The name of the target functional module is matched with the name of the functional module included in each verification code in the verification code set, and at least one matched verification code is determined as the target verification code.

[0019] As an optional implementation of the embodiment of the present application, obtaining the configuration parameters to be verified in the AUTOSAR-related parameters includes:

[0020] Parsing the ARXML file to obtain the configuration parameters to be verified in an initial format, wherein the ARXML file records the AUTOSAR related parameters;

[0021] The format of the configuration parameters to be verified in the initial format is converted to obtain the configuration parameters to be verified.

[0022] In a second aspect, the present invention provides an AUTOSAR-based configuration parameter verification device, comprising:

[0023] An acquisition module is used to obtain the configuration parameters to be verified in the AUTOSAR related parameters and determine the target functional module corresponding to the configuration parameters to be verified;

[0024] a determination module, configured to determine a target check code corresponding to a target functional module from a check code set corresponding to each functional module of AUTOSAR, wherein the target check code includes: a name of the functional module, an error level, a check type, and a sub-check code, wherein the name of the functional module is used to indicate the functional module to which the check code applies, the error level is used to indicate the danger level of the error when the check fails, and the check type and the sub-check code are used to indicate a check rule;

[0025] The verification module is used to verify the configuration parameters based on the verification type in the target verification code and the verification rule indicated by the sub-verification code to obtain a verification result.

[0026] As an optional implementation of the embodiment of the present application, the device further includes: a generation module for determining, for each functional module of AUTOSAR, a sub-check code and a check type based on the check rules corresponding to each configuration parameter in the functional module before determining the target functional module corresponding to the configuration parameter to be checked, the sub-check code including: a mutually exclusive configuration check code, a duplicate configuration check code, and a dynamic missing configuration check code, and the check type including: a basic check, a semantic check, and a syntactic check;

[0027] The names, error levels, check types, and sub-check codes of the functional modules are spliced according to a preset check code format to generate check codes corresponding to the functional modules, and the check code set is formed based on the check codes of the functional modules.

[0028] As an optional implementation of the embodiment of the present application, the device further includes: a display module, configured to generate a verification report corresponding to the configuration parameter to be verified after obtaining the verification result, the verification report including: the verification result, verification details, the path of the configuration parameter to be verified, the target verification code, and a verification code summary corresponding to the target verification code;

[0029] The verification report is visually displayed in a preset form.

[0030] As an optional implementation of an embodiment of the present application, the display module is specifically used to visually display the verification report in the form of a user interface; or, to visually display the verification report in the form of a log file; or, to visually display the verification report in the form of a Web interface.

[0031] As an optional implementation of the embodiment of the present application, the determination module is specifically used to match the name of the target functional module with the name of the functional module included in each verification code in the verification code set, and determine at least one matched verification code as the target verification code.

[0032] As an optional implementation of the embodiment of the present application, the acquisition module is specifically used to parse the ARXML file to obtain the configuration parameters to be verified in an initial format, and the ARXML file records the AUTOSAR related parameters;

[0033] The format of the configuration parameters to be verified in the initial format is converted to obtain the configuration parameters to be verified.

[0034] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a memory and a processor, the memory being used to store a computer program, the processor being used to execute the AUTOSAR-based configuration parameter verification method described in the first aspect or any optional implementation manner of the first aspect when calling the computer program.

[0035] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the AUTOSAR-based configuration parameter verification method described in the first aspect or any optional implementation manner of the first aspect is implemented.

[0036] In a fifth aspect, an embodiment of the present application provides a vehicle, which is equipped with the AUTOSAR-based configuration parameter verification device as described in the second aspect, or the electronic device as described in the third aspect, or the storage medium as described in the fourth aspect.

[0037] The technical solution provided by the embodiments of the present application has the following advantages compared with the prior art:

[0038] An embodiment of the present application provides an AUTOSAR-based configuration parameter verification method, apparatus, electronic device, and computer-readable storage medium, wherein the method includes: obtaining a configuration parameter to be verified from AUTOSAR-related parameters, and determining a target functional module corresponding to the configuration parameter to be verified; determining a target verification code corresponding to the target functional module from a verification code set corresponding to each functional module of AUTOSAR, the target verification code including: a name of the functional module, an error level, a verification type, and a sub-verification code, the functional module name being used to indicate the functional module to which the verification code applies, the error level being used to indicate the danger level of the error when verification fails, and the verification type and the sub-verification code being used to indicate a verification rule; and verifying the configuration parameter to be verified based on the verification type in the target verification code and the verification rule indicated by the sub-verification code to obtain a verification result. In the embodiment of the present application, the designed check code set includes the check codes of each functional module in AUTOSAR, and each check code supports all check types of the corresponding functional module. Therefore, unified management of all functional modules and check rules can be achieved, so that when the configuration parameters in each functional module are checked, the corresponding check rules can be found in the check code set for verification, thereby improving the verification accuracy and verification efficiency of the configuration parameters in each functional module. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0040] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0041] Figure 1 A flowchart of a configuration parameter verification method based on AUTOSAR according to one or more embodiments of the present application;

[0042] Figure 2 A schematic diagram of data processing according to one or more embodiments of the present application;

[0043] Figure 3 A schematic diagram of the composition of a verification code provided according to one or more embodiments of the present application;

[0044] Figure 4 A flowchart of a configuration parameter verification method based on AUTOSAR according to one or more embodiments of the present application;

[0045] Figure 5 A flowchart of a configuration parameter verification method based on AUTOSAR according to one or more embodiments of the present application;

[0046] Figure 6 A structural block diagram of an AUTOSAR-based configuration parameter verification device provided in one or more embodiments of the present application;

[0047] Figure 7 A structural block diagram of an AUTOSAR-based configuration parameter verification device provided in one or more embodiments of the present application;

[0048] Figure 8 This is a diagram of the internal structure of an electronic device provided according to one or more embodiments of the present application. DETAILED DESCRIPTION

[0049] In order to make the purpose, implementation mode and advantages of the present application clearer, the exemplary implementation mode of the present application will be clearly and completely described below in conjunction with the drawings in the exemplary embodiments of the present application. Obviously, the described exemplary embodiments are only part of the embodiments of the present application, not all of the embodiments.

[0050] Based on the exemplary embodiments described in this application, all other embodiments obtained by those of ordinary skill in the art without making any creative work shall fall within the scope of protection of the claims attached to this application. In addition, although the disclosure in this application is introduced according to one or several exemplary examples, it should be understood that each aspect of these disclosures can also constitute a complete embodiment separately. It should be noted that the brief description of the terms in this application is only for the convenience of understanding the embodiments described below, and is not intended to limit the embodiments of this application. Unless otherwise specified, these terms should be understood according to their ordinary and usual meanings.

[0051] First, the application scenarios of the embodiments of this application are described. AUTOSAR (Automotive Open System Architecture) is a collaborative development framework for automotive electronic systems. This architecture facilitates the exchange and update of vehicle electronic system software and provides a foundation for the efficient management of increasingly complex vehicle electronic and software systems. Vehicles using the AUTOSAR architecture require configuration or modification of AUTOSAR-related parameters. When users use configuration tools or manually modify AUTOSAR-related parameters, they must meet the various verification rules in the AUTOSAR standard before proceeding. Failure to do so can result in various problems, such as code generation exceptions, compilation failures, and executable program failures.

[0052] Based on this, the embodiment of the present application provides a configuration parameter verification method and device based on AUTOSAR. The embodiment of the present application generates a set of verification codes based on various verification rules to verify AUTOSAR-related parameters, so as to promptly discover various configuration errors of users, avoid errors from flowing into the next operation process, improve user configuration efficiency, and facilitate users to locate problems.

[0053] The AUTOSAR-based configuration parameter verification method provided in the embodiment of the present application can be executed by the electronic device provided in the embodiment of the present application, can also be implemented by the AUTOSAR-based configuration parameter verification device provided in the embodiment of the present application, and can also be implemented by one or more functional entities on the vehicle, which is not specifically limited in the embodiment of the present application.

[0054] The following describes in detail several specific examples the configuration parameter verification method based on AUTOSAR provided by the embodiments of the present application.

[0055] Figure 1 The configuration parameter verification method flow chart based on AUTOSAR provided in the embodiment of the present application is shown in FIG. Figure 1 As shown, the configuration parameter verification method based on AUTOSAR provided in this embodiment includes the following steps:

[0056] S11. Obtain configuration parameters to be verified from AUTOSAR related parameters, and determine target functional modules corresponding to the configuration parameters to be verified.

[0057] AUTOSAR functional modules include BSW (Basic SoftWare), ASW (Application Software), RTE (Runtime Environment), and OS (Operating System). Each functional module has associated configuration parameters, and the validation rules required for each configuration parameter may vary. Therefore, it is necessary to determine the target functional module corresponding to the configuration parameters to be validated within the AUTOSAR parameters.

[0058] Among them, the format of the configuration parameters to be verified is the format obtained after converting the original data format. Exemplarily, the ARXML file is parsed to obtain the configuration parameters to be verified in the initial format, and the AUTOSAR related parameters are recorded in the ARXML file; the configuration parameters to be verified in the initial format are format converted to obtain the configuration parameters to be verified. The data in the original format in the ARXML file can be called first-level data. The first-level data includes various data such as asw (application data), bsw (basic data), system (system data), ib (internal behavior, internal behavior data) and mod (configuration definition file data). After the first-level data is format converted, the second-level data obtained is the configuration parameters to be verified. The second-level data includes rte shared data and asw shared data. Reference Figure 2 As shown, Figure 2 A data processing diagram provided for one embodiment of the present application.

[0059] For example, the ARXML file is parsed to obtain the original parameters corresponding to the ARXML file; the original parameters are processed to obtain the configuration parameters to be verified. For example, the primary data is processed into secondary data using Python, and the structure of the verification configuration parameters is as follows:

[0060] classValidationData():

[0061] def__init__(self,autosar_asw_class,autosar_bsw_class,autosar_ib_class,autosar_system_class,autosar_mod_class):

[0062] self.autosar_asw_class=autosar_asw_class

[0063] self.autosar_bsw_class=autosar_bsw_class

[0064] self.autosar_ib_class=autosar_ib_class

[0065] self.autosar_system_class=autosar_system_class

[0066] self.autosar_mod_class=autosar_mod_class

[0067] self.asw_common_dict = {}

[0068] self.ret_common_dict = {}

[0069] pass

[0070] S12. Determine a target check code corresponding to the target functional module from a check code set corresponding to each functional module of AUTOSAR.

[0071] The target check code includes: the name of the functional module, the error level, the check type, and the sub-check code. The name of the functional module is used to indicate the functional module to which the check code applies. The error level is used to indicate the danger level of the error when the check fails. The check type and the sub-check code are used to indicate the check rules.

[0072] The check code set includes multiple sets of check codes for all functional modules. Each functional module can include at least one set of check codes. Each check code set may include: the name of the corresponding functional module, error level, check type, and sub-check codes. The sub-check codes include: mutually exclusive configuration check codes, duplicate configuration check codes, and dynamic missing configuration check codes. The check types include: basic check codes, semantic check codes, and syntactic check codes. The target check code is one of these check codes.

[0073] Exemplarily, when determining the target check code corresponding to the target functional module in the check code set corresponding to each functional module of AUTOSAR, the name of the target functional module can be matched with the name of the functional module included in each check code in the check code set, and at least one matched check code is determined as the target check code. The target check code can be one or more.

[0074] Reference Figure 3 As shown, Figure 3 A schematic diagram of the composition of the check code provided for one embodiment of the present application. Module names may include: BswM, RTE, Os, and others. Error levels may include: error, warning, prompt, etc. Check types may include: basic check, semantic check, syntax check, etc. Sub-check codes include: mutually exclusive configuration check code, repeated configuration check code, dynamic missing configuration check code, and others. Based on Figure 3 The module name, error level, check type, and sub-check code shown can obtain multiple sets of check codes. Figure 3This is only an example. The module name may include other possible module names, the error level may include other possible error levels, the verification type may include other possible verification types, and the sub-verification code may also include other possible configuration types. This embodiment does not constitute any limitation. Therefore, the AUTOSAR-based configuration parameter verification method provided in the embodiment of the present application can support all modules and all verification types. Therefore, you can unify the verification interface and the input parameters to facilitate user use and subsequent addition of verification data.

[0075] In the check code, the error level, check type, and sub-check code can all be represented by corresponding identifiers or serial numbers. For example, the error, warning, and prompt in the error level can be represented by 0, 1, and 2, respectively; the basic check, semantic check, and syntax check in the check type can be represented by 11, 12, and 13, respectively; the dynamic missing configuration check code, duplicate configuration check code, and mutually exclusive configuration check code in the sub-check code can be represented by 001, 002, and 003, respectively. For example, for the target check code: RTE013003, it represents {module name: error level: check type: sub-check code}, where the module corresponding to the target check code is the module name of the RTE target module, indicating that the module corresponding to the target check code is the RTE module, the error level is 0, indicating an error, the check type is 13, indicating a syntax check, and the sub-check code is 003, indicating a mutually exclusive configuration.

[0076] This is just an example for illustration, and does not limit the type and field length of each component identifier in the check code.

[0077] In the embodiment of the present application, the mutually exclusive configuration check code is used to determine whether the parameter to be checked is a mutually exclusive configuration, the repeated configuration check code is used to determine whether the parameter to be checked has a repeated configuration, and the dynamic missing configuration check code is used to determine whether the parameter to be checked satisfies the dynamic missing configuration. For example, when parameter A takes the value of a, the associated parameter B must take the value of b, then parameter A and parameter B meet the mutually exclusive configuration; if the configuration value of parameter P is c, the configuration value of parameter Q is not c, parameter P has not been repeatedly configured; if the configuration value of parameter M is c, the configuration value of the associated parameter N is not empty, which is a dynamic missing configuration. Basic verification is used to verify some characteristics that the parameter to be checked is not associated with other parameters, semantic verification is used to verify the relationship between multiple parameters in one or more modules, and grammatical verification is used to verify the configuration file of the parameter. For example, semantic verification can verify data in the RTE module, data in the Os module, data in the BSW module, etc. Basic verification is used to verify instance range, value range, string length, refa attribute of the string, etc. Syntactic verification can be used to verify data in the ASW module, data in the BSW module, etc.

[0078] S13. Verify the configuration parameter to be verified based on the verification type in the target verification code and the verification rule indicated by the sub-verification code to obtain a verification result.

[0079] Exemplarily, when the check rule indicated by the check type is semantic check and the check rule indicated by the sub-check code is mutually exclusive check, semantic check and mutually exclusive check are performed on the configuration parameter to be checked.

[0080] The validation rules described here can be a general term for various types of constraints such as multiple instance ranges, value ranges, string lengths, dynamic missing configurations, duplicate configurations, mutually exclusive configurations, and additional constraints. In the embodiments of this application, the validation rules are all implemented in independent files, making it convenient for users to refer to the unified interface for rule expansion.

[0081] Based on the verification code set, all modules and all parameters can be verified, thereby improving the verification execution efficiency and further improving the efficiency of user software development.

[0082] The present invention provides an AUTOSAR-based configuration parameter verification method, the method comprising: obtaining a configuration parameter to be verified from AUTOSAR-related parameters, and determining a target functional module corresponding to the configuration parameter to be verified; determining a target verification code corresponding to the target functional module in a verification code set corresponding to each functional module of AUTOSAR, the target verification code comprising: a function module name, an error level, a verification type, and a sub-verification code, the function module name being used to indicate the function module to which the verification code applies, the error level being used to indicate the danger level of the error when the verification fails, the verification type and the sub-verification code being used to indicate a verification rule; verifying the configuration parameter to be verified based on the verification type and the verification rule indicated by the sub-verification code in the target verification code, and obtaining a verification result. In the embodiment of the present invention, the verification code set designed includes the verification codes of each functional module in AUTOSAR, and each verification code supports all verification types of the corresponding functional module, thereby achieving unified management of all functional modules and verification rules, so that when verifying the configuration parameters in each functional module, the corresponding verification rule can be found in the verification code set for verification, thereby improving the verification accuracy and verification efficiency of the configuration parameters in each functional module.

[0083] Before verifying the configuration parameters to be verified in the AUTOSAR related parameters, the process of generating the verification code is also included. For example, refer to Figure 4 As shown, before step S11, steps S41 to S42 are included. This embodiment does not need to be Figure 1 The same or similar steps in the embodiment shown are described and explained in detail. Figure 1 The embodiments shown are illustrated and described.

[0084] S41 . For each functional module of AUTOSAR, determine a sub-check code and a check type based on a check rule corresponding to each configuration parameter in the functional module.

[0085] The sub-check codes include: mutually exclusive configuration check codes, repeated configuration check codes, and dynamic missing configuration check codes, etc. The check types include: basic check, semantic check, and grammatical check, etc.

[0086] The parameters of different functional modules, or different parameters of the same functional module, may have different corresponding verification rules. For example, the instance range, value range, string length, etc. may be different, and the configuration type (dynamic missing configuration, repeated configuration, mutually exclusive configuration) may also be different. Therefore, for each configuration parameter in each functional module, it is necessary to determine the corresponding sub-verification code and verification type, as well as the corresponding error level when the parameter is wrong. The error level is the error prompt information fed back to the user.

[0087] S42. Concatenate the names, error levels, check types, and sub-check codes of the functional modules according to a preset check code format to generate check codes corresponding to the functional modules, and form the check code set based on the check codes of the functional modules.

[0088] Exemplarily, the preset check code format can be {module name: error level: check type: sub-check code}, and the module name, error level, check type, and sub-check code in the preset check code format are represented by corresponding identifiers respectively, and a set of check codes corresponding to each functional module is obtained, and a set of check codes includes multiple check codes.

[0089] The verification code provided in the embodiment of the present application supports user-defined expansion, which facilitates users to customize the required verification rules according to project requirements.

[0090] In the embodiments of this application, based on a high-performance and open-source durable rules engine, the implementation of all verification rules is managed through designed verification codes. The entry of verification rules is unified through template design patterns, which facilitates management and expansion. Verification rules for all functional modules of AUTOSAR are supported. By applying a good rule engine selection, the execution efficiency of verification rules is improved. Because the rule engine itself supports cross-platform, the implemented verification rules are all implemented in Python, and the overall verification tool framework supports cross-platform and cross-system migration.

[0091] exist Figure 1 or Figure 4 On the basis of the embodiment shown, after obtaining the verification result, the verification result is also displayed. For example, Figure 1For example, after step S13, the configuration parameter verification method based on AUTOSAR further includes the following steps S51 to S52, referring to Figure 5 shown.

[0092] S51: Generate a verification report corresponding to the configuration parameters to be verified.

[0093] The verification report includes: the verification result, verification details, the path of the configuration parameter to be verified, the target verification code, and the verification code summary corresponding to the target verification code.

[0094] The verification results include pass and fail. The verification code summary is used to explain the function of the target verification code. The verification report includes: the verification result of pass or fail, verification details, the path of the configuration parameter to be verified, the name of the target functional module, the error level, the verification type, the sub-verification code, and the verification code summary corresponding to the target verification code.

[0095] For example, the structure of the verification report is as follows:

[0096] classValidationResult():

[0097] def__init__(self,validation_mark,summary,message,path,result):

[0098] self.validation_mark=validation_mark

[0099] self.summary = summary

[0100] self.message = message

[0101] self.path = path

[0102] self.result = result

[0103] S52: Visually display the verification report in a preset format.

[0104] Among them, the preset form includes: any one of: a user interface, a web interface, and a log file. For example, the verification report is visually displayed in the form of a user interface; or, the verification report is visually displayed in the form of a log file; or, the verification report is visually displayed in the form of a web interface.

[0105] That is, the verification results, verification details, the path of the configuration parameters to be verified, the name of the target functional module, the error level, the verification type, the sub-verification code, and the verification code summary corresponding to the target verification code are visually displayed in the form of a user interface; or the verification results, verification details, the path of the configuration parameters to be verified, the name of the target functional module, the error level, the verification type, the sub-verification code, and the verification code summary corresponding to the target verification code are visually displayed in the form of a log file; or the verification results, verification details, the path of the configuration parameters to be verified, the name of the target functional module, the error level, the verification type, the sub-verification code, and the verification code summary corresponding to the target verification code are visually displayed in the form of a web interface. The specific display form can be switched based on the user's settings or switching operations.

[0106] The embodiments of the present application support various functions such as adding, deleting, updating and querying verification results, and support users to access data through various methods such as log files, UI interfaces and Web displays, so as to facilitate users to quickly locate and solve problems and improve the user experience.

[0107] In an embodiment of the present application, the processing of the data to be verified can be performed based on the data management unit, the verification process can be performed based on the rule management unit, and the verification results can be managed by the result unit. Each unit functions independently and is decoupled from other units for easy management. Each unit may include at least one module.

[0108] Based on the same inventive concept, as an implementation of the above-mentioned method, an embodiment of the present application further provides an AUTOSAR-based configuration parameter verification device for executing the above-mentioned embodiment. This device embodiment corresponds to the above-mentioned method embodiment. For ease of reading, this device embodiment will no longer describe the details of the above-mentioned method embodiment one by one. However, it should be clear that the AUTOSAR-based configuration parameter verification in this embodiment can correspond to the implementation of all the contents of the above-mentioned method embodiment.

[0109] Figure 6 A schematic diagram of the structure of a configuration parameter verification device based on AUTOSAR is provided in one embodiment of the present application, as shown in FIG. Figure 6 As shown, the configuration parameter verification device 600 based on AUTOSAR provided in this embodiment includes:

[0110] An acquisition module 610 is configured to acquire configuration parameters to be verified from AUTOSAR related parameters and determine a target functional module corresponding to the configuration parameters to be verified;

[0111] a determination module 620 configured to determine a target check code corresponding to a target functional module from a check code set corresponding to each functional module of AUTOSAR, wherein the target check code includes a functional module name, an error level, a check type, and a sub-check code, wherein the functional module name indicates the functional module to which the check code applies, the error level indicates the error risk level when the check fails, and the check type and the sub-check code indicate a check rule;

[0112] The verification module 630 is configured to verify the configuration parameters based on the verification type in the target verification code and the verification rule indicated by the sub-verification code to obtain a verification result.

[0113] As an optional implementation of the embodiment of this application, refer to Figure 7 As shown, in Figure 6 On the basis of the device shown, it also includes: a generation module 710, which is used to determine, for each functional module of AUTOSAR, a sub-check code and a check type based on the check rules corresponding to each configuration parameter in the functional module before determining the target functional module corresponding to the configuration parameter to be checked, the sub-check code includes: a mutually exclusive configuration check code, a repeated configuration check code, and a dynamic missing configuration check code, and the check type includes: a basic check, a semantic check, and a grammatical check; the name, error level, check type, and sub-check code of the functional module are spliced according to a preset check code format to generate a check code corresponding to each functional module, and the check code set is formed based on the check codes of each functional module.

[0114] As an optional implementation of the embodiment of the present application, the device also includes: a display module 720, which is used to generate a verification report corresponding to the configuration parameter to be verified after obtaining the verification result, and the verification report includes: the verification result, verification details, the path of the configuration parameter to be verified, the target verification code, and the verification code summary corresponding to the target verification code; the verification report is visually displayed in a preset form.

[0115] As an optional implementation of an embodiment of the present application, the display module 720 is specifically used to visually display the verification report in the form of a user interface; or, to visually display the verification report in the form of a log file; or, to visually display the verification report in the form of a Web interface.

[0116] As an optional implementation of the embodiment of the present application, the determination module 620 is specifically used to match the name of the target functional module with the name of the functional module included in each verification code in the verification code set, and determine at least one matched verification code as the target verification code.

[0117] As an optional implementation of the embodiment of the present application, the acquisition module 610 is specifically used to parse the ARXML file, the configuration parameters to be verified in the initial format, and the ARXML file records the AUTOSAR-related parameters; perform format conversion on the configuration parameters to be verified in the initial format to obtain the configuration parameters to be verified.

[0118] In one embodiment, an electronic device is provided, including a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, it implements the steps of any one of the AUTOSAR-based configuration parameter verification methods described in the above method embodiments.

[0119] For example, Figure 8 This is a schematic diagram of the structure of the electronic device provided in the embodiment of the present application. Figure 8 As shown, the electronic device provided in this embodiment includes: a memory 81 and a processor 82, the memory 81 is used to store computer programs; the processor 82 is used to execute the steps of the configuration parameter verification method based on AUTOSAR provided in the above method embodiment when calling the computer program. Its implementation principle and technical effect are similar and will not be repeated here. It can be understood by those skilled in the art that Figure 8 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the electronic device to which the solution of the present application is applied. The specific electronic 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-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the computer program implements the steps of any one of the AUTOSAR-based configuration parameter verification methods described in the above method embodiments.

[0121] In one embodiment, a vehicle is provided. The vehicle is equipped with the AUTOSAR-based configuration parameter verification device, or electronic device, or storage medium as described in the above device embodiment.

[0122] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and 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-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in various forms, such as static random access memory (SRAM) and dynamic random access memory (DRAM).

[0123] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device that includes the element.

[0124] For ease of explanation, the above description has been made in conjunction with specific embodiments. However, the above discussion of some embodiments is not intended to be exhaustive or to limit the embodiments to the specific forms disclosed above. Based on the above teachings, various modifications and variations can be obtained. The selection and description of the above embodiments are intended to better explain the principles and practical applications, so that those skilled in the art can better use the embodiments and various different variations of the embodiments suitable for specific use considerations.

Claims

1. A configuration parameter verification method based on AUTOSAR, characterized in that: include: Obtain the configuration parameters to be verified in the AUTOSAR related parameters, and determine the target functional module corresponding to the configuration parameters to be verified; Determining a target check code corresponding to a target functional module from a check code set corresponding to each functional module of AUTOSAR, wherein the target check code includes: a name of the functional module, an error level, a check type, and a sub-check code, wherein the name of the functional module is used to indicate the functional module to which the check code applies, the error level is used to indicate the danger level of the error when the check fails, and the check type and the sub-check code are used to indicate a check rule; The configuration parameter to be verified is verified based on the verification type in the target verification code and the verification rule indicated by the sub-verification code to obtain a verification result.

2. The method according to claim 1, characterized in that Before determining the target functional module corresponding to the configuration parameter to be verified, the method further includes: For each functional module of AUTOSAR, a sub-check code and a check type are determined based on the check rules corresponding to each configuration parameter in the functional module. The sub-check codes include: mutually exclusive configuration check code, duplicate configuration check code, and dynamic missing configuration check code. The check types include: basic check, semantic check, and grammatical check. The names, error levels, check types, and sub-check codes of the functional modules are spliced according to a preset check code format to generate check codes corresponding to the functional modules, and the check code set is formed based on the check codes of the functional modules.

3. The method according to claim 1, characterized in that After obtaining the verification result, the method further includes: Generate a verification report corresponding to the configuration parameter to be verified, the verification report including: the verification result, verification details, the path of the configuration parameter to be verified, the target verification code, and a verification code summary corresponding to the target verification code; The verification report is visually displayed in a preset form.

4. The method according to claim 3, characterized in that The visual display of the verification report in a preset form includes: The verification report is visually displayed in the form of a user interface; or, the verification report is visually displayed in the form of a log file; or, the verification report is visually displayed in the form of a Web interface.

5. The method according to claim 1, wherein Determining the target check code corresponding to the target functional module from the check code set corresponding to each functional module of AUTOSAR includes: The name of the target functional module is matched with the name of the functional module included in each verification code in the verification code set, and at least one matched verification code is determined as the target verification code.

6. The method according to claim 1, characterized in that The obtaining of the configuration parameters to be verified in the AUTOSAR related parameters includes: Parsing the ARXML file to obtain the configuration parameters to be verified in an initial format, wherein the ARXML file records the AUTOSAR related parameters; The format of the configuration parameters to be verified in the initial format is converted to obtain the configuration parameters to be verified.

7. A configuration parameter verification device based on AUTOSAR, characterized in that: include: An acquisition module is used to obtain the configuration parameters to be verified in the AUTOSAR related parameters and determine the target functional module corresponding to the configuration parameters to be verified; a determination module, configured to determine a target check code corresponding to a target functional module from a check code set corresponding to each functional module of AUTOSAR, wherein the target check code includes: a name of the functional module, an error level, a check type, and a sub-check code, wherein the name of the functional module is used to indicate the functional module to which the check code applies, the error level is used to indicate the danger level of the error when the check fails, and the check type and the sub-check code are used to indicate a check rule; The verification module is used to verify the configuration parameters based on the verification type in the target verification code and the verification rule indicated by the sub-verification code to obtain a verification result.

8. An electronic device comprising: A memory and a processor, wherein the memory stores a computer program, wherein the processor implements the method for verifying configuration parameters in AUTOSAR according to any one of claims 1 to 6 when executing the computer program.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for verifying configuration parameters in AUTOSAR according to any one of claims 1 to 6 is implemented.

10. A vehicle, characterized in that: The vehicle is equipped with the AUTOSAR-based configuration parameter verification device according to claim 7, or the electronic device according to claim 8, or the storage medium according to claim 9.

Images