Method, apparatus, and vehicle for processing vehicle data

Abstract

The present invention discloses a method, apparatus and vehicle for processing vehicle data. Among them, the method includes: obtaining vehicle data by collecting vehicle parameters of different systems in the vehicle; determining the role permission of the currently logged-in user based on the role permissions of multiple pre-configured roles, where the role permission is used to represent the permission range for the logged-in user to use vehicle data; creating an approval mode that matches the role permission of the currently logged-in user based on the role permission of the currently logged-in user; if an uploaded upgrade data packet is detected, approving the upgrade data packet according to the approval mode, where the upgrade data packet is a data packet for upgrading the version of the object to be upgraded. The present invention solves the technical problem that manual review of data is prone to errors.

Description

Technical Field

[0001] The present invention relates to the field of vehicle data management, and in particular to a vehicle data processing method, device and vehicle. Background Art

[0002] With the rapid development of my country's automobile industry, different types of automobile products emerge in an endless stream, and the control parameters of each type of automobile are often different. In order to cover different types of automobile products, automobile control software implements specific types of agreements by changing the calibration data. In addition, with the update of technology, vehicle manufacturers continue to modify and improve the calibration data, and update higher versions. The accuracy of vehicle calibration data modification determines whether the various components of the vehicle can operate normally and the safety of vehicle driving. Therefore, the management of vehicle calibration data is crucial.

[0003] At present, vehicle data is mostly managed manually through calibration data management, including data modification, updating and review. Human errors are prone to occur during the review process.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet.

[0005] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0006] The embodiments of the present invention provide a method, device and vehicle for processing vehicle data, so as to at least solve the technical problem that errors are prone to occur in manual review of data.

[0007] According to one aspect of an embodiment of the present invention, a method for processing vehicle data is provided, including: obtaining vehicle data by receiving vehicle parameters from different systems; determining the role permissions of a currently logged-in user based on the role permissions of a plurality of pre-configured roles, wherein the role permissions are used to characterize the scope of permissions of the logged-in user to use vehicle data; obtaining an approval mode that matches the role permissions of the currently logged-in user based on the role permissions of the currently logged-in user; if an uploaded upgrade data packet is detected, approving the upgrade data packet according to the approval mode, wherein the upgrade data packet is a data packet for performing a version upgrade on an object to be upgraded.

[0008] Optionally, after detecting the uploaded upgrade data packet, the method further includes: parsing the upgrade data packet and verifying the parsing result; if the verification passes, submitting the upgrade data packet to an approval module, where, by verifying the upgrade data packet, it is determined whether the upgrade data packet meets the approval conditions; triggering the approval of the upgrade data packet by using an approval mode that matches the role permissions of the currently logged-in user, where the approval mode includes performing at least one approval stage on the upgrade data packet.

[0009] Optionally, the method further includes determining submitable parameter variables from a parameter file, and this step includes: receiving the uploaded parameter file, where the parameter set recorded in the parameter file includes: at least one uncalibrated parameter; selecting at least one parameter to be merged from the parameter set; generating a parameter variable to be verified when at least one parameter to be merged is merged, where the parameter set and the parameter variable to be verified are data that allow editing; comparing the parameter variable to be verified with the corresponding standard parameter, and if there is no conflict between the parameter variable to be verified and the corresponding standard variable, then verifying that the parameter variable is a safe variable, and the standard parameter is a comparison file uploaded in advance for parameter comparison; when the parameter variable to be verified is a safe variable, confirming that the parameter variable to be verified is a submitable parameter variable; submitting the submitable parameter variable to the approval module for approval.

[0010] Optionally, if the uploaded upgrade data packet is detected, approving the upgrade data packet according to the approval mode includes: triggering an upgrade instruction, where the upgrade instruction includes: a software upgrade instruction and a data upgrade instruction; in response to the upgrade instruction, obtaining the upgrade data packet, where the upgrade data packet at least includes: a first file for storing at least variable names and variable attributes, and a second file for storing variable values; detecting whether the format of the upgrade data packet meets the preset format conditions; if it meets, parsing the upgrade data packet to generate variables to be detected; determining whether the variables to be detected are variables that already exist in the first file; if the variables to be detected do not exist in the first file, extracting the variable values matching the variables to be detected from the second file and performing assignment; if the variables to be detected already exist in the first file, updating the corresponding variable values in the second file.

[0011] Optionally, after approving the upgrade data packet according to the approval mode, the method further includes: receiving the upgrade data packet to be approved, and after the upgrade data packet is approved, generating an approval parameter submission record corresponding to the upgrade data packet, where the approval parameter submission record at least includes: variable change information for which the approval of this approval stage is completed, a data file marked with a modification label; determining calibrated variables allowed to be submitted based on the approved upgrade data packet; merging the calibrated variables into the main version of the object to be upgraded.

[0012] Optionally, in the case where the approval mode is multi-level approval, if the currently logged-in user has approval authority, the upgrade data packet to be upgraded is approved based on the triggered approval instruction, and the generated approval result will be submitted to at least one approval process for the next-level approval.

[0013] According to another aspect of the embodiments of the present invention, there is also provided a processing device for vehicle data, including: a first receiving module, configured to receive the submitted vehicle data, wherein the vehicle data is obtained by collecting vehicle parameters of different systems in the vehicle; a permission verification module, configured to determine the role permission of the currently logged-in user based on the role permissions of multiple pre-configured roles, wherein the role permission is used to characterize the permission range of the logged-in user to use the vehicle data; a creation module, configured to obtain an approval mode that matches the role permission of the currently logged-in user based on the role permission of the currently logged-in user; an approval module, configured to, if an uploaded upgrade data packet is detected, approve the upgrade data packet according to the approval mode, wherein the upgrade data packet is a data packet for upgrading the version of the object to be upgraded.

[0014] Optionally, the device further includes: a parsing module, configured to parse the upgrade data packet and verify the parsing result; a second submission module, configured to, if the verification passes, submit the upgrade data packet to the approval module, wherein by verifying the upgrade data packet, it is determined whether the upgrade data packet meets the approval conditions; a triggering module, configured to trigger the approval of the upgrade data packet by using an approval mode that matches the role permission of the currently logged-in user, wherein the approval mode includes performing at least one approval stage on the upgrade data packet.

[0015] Optionally, the device further includes: a processing module, configured to determine the parameter variables that can be submitted from the parameter file, and the processing module includes: a second receiving module, configured to receive the uploaded parameter file, wherein the parameter set recorded in the parameter file includes: at least one uncalibrated parameter; a selection module, configured to select at least one parameter to be merged from the parameter set; a generation module, configured to generate the parameter variables to be verified in the case where at least one parameter to be merged is completed, wherein the parameter set and the parameter variables to be verified are data that allow editing; a comparison module, configured to compare the parameter variables to be verified with the corresponding standard parameters, and if there is no conflict between the parameter variables to be verified and the corresponding standard variables, then verify that the parameter variables are safe variables, and the standard parameters are the comparison files uploaded in advance for parameter comparison; a confirmation module, configured to confirm that the parameter variables to be verified are the parameter variables that can be submitted in the case where the parameter variables to be verified are safe variables; a second submission module, configured to submit the parameter variables that can be submitted to the approval module for approval.

[0016] According to another aspect of the embodiments of the present invention, a vehicle is further provided, which includes a processing device for vehicle data, wherein the vehicle data processing device executes the above-mentioned vehicle data processing method.

[0017] In the embodiments of the present invention, vehicle data is obtained by collecting vehicle parameters of different systems in the vehicle; based on the role permissions of multiple pre-configured roles, the role permissions of the currently logged-in user are determined, where the role permissions are used to represent the scope of permissions for the logged-in user to use vehicle data; based on the role permissions of the currently logged-in user, an approval mode matching the role permissions of the currently logged-in user is obtained; if an uploaded upgrade data packet is detected, the upgrade data packet is approved according to the approval mode, where the upgrade data packet is a data packet for version upgrading of the object to be upgraded. In this way, by uploading calibration data and using the advantages of layer-by-layer approval to conduct step-by-step review of the data, data traceability is achieved, the approval process is traceable, and comparisons, reports, etc. can be formed for the calibration data, better realizing the management of vehicle calibration data, thereby achieving the technical effect of improving the management efficiency and accuracy of vehicle calibration data, and further solving the technical problem of easy mistakes in manual review of data. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings described herein are used to provide a further understanding of the present invention, form a part of this application, and the schematic embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation to the present invention. In the drawings:

[0019] Figure 1 is a flowchart of a vehicle data processing method according to an embodiment of the present invention;

[0020] Figure 2 is a flowchart of project creation according to an embodiment of the present invention;

[0021] Figure 3 is an optional approval flowchart according to an embodiment of the present invention;

[0022] Figure 4 is an optional Label designation function setting flowchart according to an embodiment of the present invention;

[0023] Figure 5 is an optional stage parameter modification process according to an embodiment of the present invention;

[0024] Figure 6 is a data parsing and comparison flowchart according to an embodiment of the present invention;

[0025] Figure 7 is a software upgrade flowchart according to an embodiment of the present invention;

[0026] Figure 8It is a data upgrade flow chart according to an embodiment of the present invention;

[0027] Figure 9 It is a data export flow chart according to an embodiment of the present invention. Detailed implementation manners

[0028] In order to enable those skilled in the art to better understand the solution of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0029] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above drawings are used to distinguish similar objects, and do not necessarily need to describe a specific order or sequence. It should be understood that such used data can be interchanged under appropriate circumstances so that the embodiments of the present invention described herein can be implemented in an order different from those illustrated or described herein. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these process, method, product or device.

[0030] Embodiment 1

[0031] With the rapid development of the automotive industry in our country, different types of automotive products emerge in an endless stream, and the control parameters of each type of vehicle are often different. In order to cover different types of automotive products, automotive control software realizes specific type agreements through changes in calibration data. In addition, with the update of technology, vehicle manufacturers continuously modify and improve the calibration data and update to higher versions. However, since the current management of vehicle calibration data is mostly through manual management of calibration data, there are the following problems: it is very easy to have situations such as human errors during the review process.

[0032] In order to solve the above problems, the present invention provides a method for processing vehicle data, which manages vehicle calibration data and its versions by classification and with different permissions, thereby achieving the technical effects of high efficiency and high accuracy in calibration data management.

[0033] According to an embodiment of the present invention, an embodiment of a method for managing vehicle data is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0034] Figure 1 is a flowchart of a method for managing vehicle data according to an embodiment of the present invention. As Figure 1 shown, the method includes the following steps:

[0035] Step S102, receive the submitted vehicle data, where the vehicle data is obtained by collecting vehicle parameters of different systems in the vehicle;

[0036] Specifically, the vehicle parameters in the above steps may include at least one of the following: engine data, transmission data, chassis data, driving system data, and electrical system data.

[0037] Before uploading the vehicle data, the administrator creates a project according to the requirements. The flowchart of project creation in one embodiment is shown in Figure 2 , and the data categories in the project include project number, vehicle model, engine, and transmission. When creating a project, it is necessary to upload HEX&A2L (or DCM&A2L or PAR&A2L) files, which contain vehicle data of various categories in the project.

[0038] During the project creation process, an existing project development template can be selected according to the actual situation, or stage tasks can be created independently. Project development template management includes: creating project stages, editing stages, deleting, enabling / disabling, etc.

[0039] During the project creation process, according to the user's needs, project labels can be customized to facilitate viewing of projects with the same type of labels in the future (driverless, 863 projects).

[0040] There are various sorting and filtering methods for the above projects. The viewing methods include: project list method, key information retrieval, date retrieval, keyword field sorting, etc., such as sorting by vehicle model, project model, retrieving by the components and systems to which they belong, and date retrieval, etc.

[0041] Step S104, determine the role permissions of the currently logged-in user based on the role permissions of multiple pre-configured roles;

[0042] Specifically, the project administrator first sets roles for the users of this project, including team leaders and team members. Secondly, the role permissions corresponding to the roles are pre-configured. The above role permissions are used to characterize the scope of permissions for logged-in users to use vehicle data, and the permissions include at least one of the following: data modification permission, data review permission, and software upgrade data upload permission.

[0043] Furthermore, the role permissions include engine data modification, upload and / or review permissions, transmission data modification, upload and / or review permissions, chassis data modification, upload and / or review permissions, driving system data modification, upload and / or review permissions, and electrical system data modification, upload and / or review permissions, data modification, upload and / or review permissions for a certain type of vehicle, data modification, upload and / or review permissions for a certain project, etc.

[0044] Step S106, based on the role permissions of the currently logged-in user, obtain an approval mode that matches the role permissions of the currently logged-in user.

[0045] Specifically, the above approval modes include multi-level approval, automatic review, no approval, etc. The administrator can set the approval mode corresponding to the project during the project creation process.

[0046] Specifically, one optional instance of the multi-level approval mode is that the team leader of the stage will first review the submissions of the team members. After the review, the review results of the team leader will be submitted to the project manager for review. If the review is passed, the results of this review will be merged into the corresponding branch of the project.

[0047] Specifically, the automatic review mode is that when a team member with permission submits a version review, after the team leader of the stage approves it, the results of this review will be merged into the corresponding branch of the project.

[0048] Specifically, the no-approval mode is that the approval passes quickly. After a team member with permission submits a version review, the review results will be directly merged into the corresponding branch of the project.

[0049] Step S108, detect the uploaded upgrade data packet and approve the upgrade data packet according to the approval mode, where the upgrade data packet is a data packet for version upgrading of the object to be upgraded.

[0050] Specifically, the upgrade data packet includes two types of data packets: data upgrade and software upgrade. Furthermore, the data packet includes a parameter scheme or a HEX+A2L file. When the upgrade data packet is detected, it will be approved according to the pre-set approval mode and in accordance with Figure 3 the approval flow chart shown.

[0051] Through the above embodiments of the present invention, based on the role permissions of multiple pre-configured roles, determine the role permissions of the currently logged-in user, and create an approval mode that matches the role permissions of the currently logged-in user; if there is a modification of vehicle data or an uploaded upgrade data packet is detected, approve the modified data or upgrade data packet according to the approval mode. The systematic management of various vehicle calibration data is realized. By taking advantage of the multi-level approval to conduct step-by-step review of the data, it is possible to leave a record of the data and make the approval process traceable, and it is also possible to form comparisons, reports, etc. for the calibration data, so that some problems existing in the calibration data can be easily discovered, thereby improving the calibration efficiency and accuracy to a certain extent, and further solving the technical problem that manual review of data is prone to errors.

[0052] Optionally, in the above embodiments of the present invention, after detecting the uploaded upgrade data packet, parse the upgrade data packet and verify the parsing result; if the verification passes, submit the upgrade data packet to the approval module, where by verifying the upgrade data packet, it is determined whether the upgrade data packet meets the approval conditions; adopt an approval mode that matches the role permissions of the currently logged-in user to trigger the approval of the upgrade data packet, where the approval mode includes performing at least one approval stage on the upgrade data packet.

[0053] Specifically, before uploading the upgrade data, the above method further includes the Label specifying function: uploading a parameter range file and verifying the uploaded variable range. Each stage can specify a responsible person for the variable. After setting the responsible person, only the specified responsible person can perform editing operations on the variable. When not set, all team members in this stage can perform editing operations on all variables in this stage, where team members in the second stage cannot modify variables in the third stage, and team members in the third stage can modify variables in the second stage. The Label specifying function setting process is as Figure 4 shown.

[0054] The responsible person with the corresponding permissions determined by the Label specifying function can submit the imported DCM / PAR / CSV file on the project details page or directly modify the parameters using the editing tool. The stage parameter modification process is as Figure 5 shown.

[0055] After detecting the uploaded upgrade data packet, parse the upgrade data packet and verify the parsing result, and judge the calibration variables that meet the submission review requirements and those that cannot be submitted. If the data packet passes the verification and is submitted to the approval module, the approval is carried out according to the Figure 3 approval process shown. Among them, the data packet format includes but is not limited to DCM / PAR / CSV. A flowchart of data parsing and comparison in one embodiment is as Figure 6 shown.

[0056] Enter the review stage. After passing the review by the team leader and the project manager, merge the calibrated quantities of the DCM / PAR / CSV files into the specified version and upgrade the calibrated data version. When uploading the DCM / PAR / CSV files, perform verification to identify the calibrated variables that meet the submission review requirements and those that cannot be submitted.

[0057] Optionally, the method further includes determining the parameter variables that can be submitted from the parameter file. This step includes: receiving the uploaded parameter file, where the parameter set recorded in the parameter file includes: at least one uncalibrated parameter; selecting at least one parameter to be merged from the parameter set; when at least one parameter to be merged is completed, generating the parameter variables to be verified, where the parameter set and the parameter variables to be verified are data that allow editing; comparing the parameter variables to be verified with the corresponding standard parameters. If there is no conflict between the parameter variables to be verified and the corresponding standard variables, then the verified parameter variables are safe variables, and the standard parameters are the comparison files uploaded in advance for parameter comparison; when the parameter variables to be verified are safe variables, confirm that the parameter variables to be verified are the parameter variables that can be submitted; submit the parameter variables that can be submitted to the approval module for approval.

[0058] Specifically, it supports uploading parameter schemes containing uncalibrated parameter variables. Multiple parameter schemes are supported for uploading, and members can create their own draft parameter schemes; the parameter schemes are visible to members in the same stage, and the drafts are only visible to themselves.

[0059] The parameter scheme supports multiple selection and merging. When a member clicks to merge, the parameters with the status of selected in the selected parameter schemes are merged to generate the parameter variables to be verified.

[0060] The parameter variables in the parameter scheme and the parameter variables to be verified generated by merging can be edited online, supporting manual editing or restoring the historical record.

[0061] Compare the parameter variables in the parameter scheme and the parameter variables to be verified generated by merging with the standard parameter variables. The comparison file is the parameter file uploaded when creating the project. If there is no conflict in the comparison result, then the above parameter variables are safe variables and can be submitted variables, and they are submitted to the approval module for approval. If there is a conflict in the comparison result, count the number of conflicts for each variable, and display the conflict content and the number of conflicts for the parameters that cannot be submitted.

[0062] The specific display methods include data analysis and comparison reports: the variables between different versions can display an analysis and comparison view, and the comparison reports can be exported in formats such as Excel, Html, and PDF.

[0063] Optionally, if an uploaded upgrade data packet is detected, approve the upgrade data packet according to the approval mode, including: triggering an upgrade instruction, where the upgrade instruction includes: a software upgrade instruction and a data upgrade instruction; responding to the upgrade instruction to obtain an upgrade data packet, where the upgrade data packet at least includes: a first file for storing at least variable names and variable attributes, and a second file for storing variable values; detecting whether the format of the upgrade data packet meets the preset format conditions; if it meets, parse the upgrade data packet to generate variables to be detected; determining whether the variables to be detected already exist in the first file; if the variables to be detected do not exist in the first file, extract the variable values matching the variables to be detected from the second file and assign values; if the variables to be detected already exist in the first file, update the corresponding variable values in the second file.

[0064] Specifically, when performing software upgrade, two files, A2L and HEX, must be included. During the upgrade process, if the variable attributes in the A2L change, the attributes of the same variables in each branch will also be modified accordingly; if there are new variables in the A2L, the new variables will take the values from the HEX file; if a variable already exists and the value in the HEX is inconsistent with the value in the library, the value in the library will be updated to the HEX. The update range is all branches of the entire project. After the upgrade, the project version and the A2L version will be updated accordingly. The software upgrade process is as Figure 7 shown.

[0065] Specifically, for data upgrade, the HEX file must be uploaded. If the value in the library is inconsistent with the value in the uploaded HEX, the value from the uploaded HEX will be taken. The update range is all branches of the entire project. After the upgrade, the project version and the A2L version will be updated accordingly. The data upgrade process is as Figure 8 shown.

[0066] Optionally, after approving the upgrade data packet according to the approval mode, the method further includes: receiving an upgrade data packet to be approved, and after the upgrade data packet is approved, generating an approval parameter submission record corresponding to the upgrade data packet, where the approval parameter submission record at least includes: variable change information that has been approved in this approval stage, and a data file marked with a modification label; based on the approved upgrade data packet, determining the calibrated variables allowed to be submitted; merging the calibrated variables into the main version of the object to be upgraded.

[0067] Specifically, when editing the development plan, determine the calibration stage according to the actual situation. In one stage, all team members need to be configured, and in the second stage, a team leader needs to be configured for each group. Team members submit parameter reviews in a certain stage. If the team leader approves, a detailed parameter submission record will be generated in this stage. The record contains all variable change details of the stage, and the final modification results can be exported in the DCM and PAR file formats. When exporting data, you can select project branches and versions to export the configuration and data (A2L, HEX, DCM, PAR) of the project. The process is asFigure 9 as shown

[0068] When the parameter plan is uploaded to the main version during the stage task and passes the review by the team leader and the project manager, the calibrated quantity of the parameter plan will be merged into the main version, and the calibrated data version will be upgraded simultaneously.

[0069] Optionally, in the case of a multi-level approval mode, if the currently logged-in user has approval authority, the data packet to be upgraded will be approved based on the triggered approval instruction, and the generated approval result will be submitted to at least one approval process for the next-level approval.

[0070] Specifically, in the multi-level approval mode, when a team member with permission submits a version review, if the currently logged-in user has approval authority, the data packet to be upgraded will be approved based on the triggered approval instruction, and the generated approval result will be submitted to at least one approval process for the next-level approval.

[0071] In an optional embodiment, project-related reports and all approval messages and platform messages related to the current user can be viewed. The project-related reports include calibration progress reports, project comparison reports, version comparison reports, and project contribution reports, and the report formats support Excel, HTML, and PDF. When there are assigned tasks and review tasks, the message center will send notifications to the task executors. When the approval message is in the unread state, clicking the view button can directly enter the review page. In addition, when the Label value related to the user is replaced, the user will be notified and reminded to confirm. Finally, when the platform receives messages such as review notifications, review rejections, variable changes, version releases, and task changes, relevant users will be notified by email.

[0072] Embodiment 2

[0073] According to an embodiment of the present invention, a processing device for vehicle data is provided.

[0074] Optionally, the device further includes: a first receiving module, configured to receive the submitted vehicle data, where the vehicle data is obtained by collecting vehicle parameters of different systems in the vehicle; a permission verification module, configured to determine the role permission of the currently logged-in user based on the role permissions of multiple pre-configured roles, where the role permission is used to represent the permission range for the logged-in user to use the vehicle data; a creation module, configured to obtain an approval mode matching the role permission of the currently logged-in user based on the role permission of the currently logged-in user; an approval module, configured to, if an uploaded upgrade data packet is detected, approve the upgrade data packet according to the approval mode, where the upgrade data packet is a data packet for version-upgrading the object to be upgraded.

[0075] Optionally, the apparatus further includes: a parsing module, configured to parse the upgrade data packet and verify the parsing result; a second submission module, configured to submit the upgrade data packet to the approval module if the verification passes, wherein by verifying the upgrade data packet, it is determined whether the upgrade data packet meets the approval conditions; a triggering module, configured to trigger the approval of the upgrade data packet by using an approval mode that matches the role permissions of the currently logged-in user, wherein the approval mode includes performing at least one approval stage on the upgrade data packet.

[0076] Optionally, the apparatus further includes: a processing module, configured to determine the parameter variables that can be submitted from a parameter file, and the processing module includes: a second receiving module, configured to receive the uploaded parameter file, wherein the parameter set recorded in the parameter file includes: at least one uncalibrated parameter; a selection module, configured to select at least one parameter to be merged from the parameter set; a generation module, configured to generate the parameter variables to be verified when at least one parameter to be merged is merged, wherein the parameter set and the parameter variables to be verified are data that allow editing; a comparison module, configured to compare the parameter variables to be verified with the corresponding standard parameters, and if there is no conflict between the parameter variables to be verified and the corresponding standard variables, then the verified parameter variables are secure variables, and the standard parameters are comparison files uploaded in advance for parameter comparison; a confirmation module, configured to confirm that the parameter variables to be verified are the parameter variables that can be submitted when the parameter variables to be verified are secure variables; a second submission module, configured to submit the parameter variables that can be submitted to the approval module for approval.

[0077] Embodiment 3

[0078] According to an embodiment of the present invention, a vehicle is provided, and the vehicle includes a processing device for vehicle data, wherein the vehicle data processing device executes the above-mentioned vehicle data processing method.

[0079] In the above embodiments of the present invention, the descriptions of the respective embodiments have their own emphases. For parts not detailed in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

[0080] In several embodiments provided in the present application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are merely illustrative. For example, the division of the units can be a logical function division. In actual implementation, there can be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces. The indirect couplings or communication connections of the units or modules can be in electrical or other forms.

[0081] The unit described as a separation component may or may not be physically separated. The component displayed as a unit may or may not be a physical unit, that is, it may be located in one place or distributed over multiple units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0082] In addition, each functional unit in various embodiments of the present invention may be integrated into a processing unit, may exist physically separately for each unit, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0083] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage medium includes: USB flash drives, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), mobile hard disks, magnetic disks, or optical disks and other various media that can store program codes.

[0084] The above description is only a preferred embodiment of the present invention. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present invention, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present invention.

Claims

1. A method for processing vehicle data, characterized in that, Including: Receiving the submitted vehicle data, wherein the vehicle data is obtained by collecting vehicle parameters of different systems in the vehicle; Determining the role permissions of the currently logged-in user based on the role permissions of multiple pre-configured roles, wherein the role permissions are used to characterize the permission scope for the logged-in user to use the vehicle data; Obtaining an approval mode that matches the role permissions of the currently logged-in user based on the role permissions of the currently logged-in user; If an uploaded vehicle data upgrade package is detected, approving the upgrade data packet according to the approval mode, wherein the upgrade data packet is a data packet for version upgrading of the object to be upgraded; Wherein, the method further includes: determining the parameter variables that can be submitted from the parameter file, wherein determining the parameter variables that can be submitted from the parameter file includes: Receiving the uploaded parameter file, wherein the parameter set recorded in the parameter file includes: at least one uncalibrated parameter; Selecting at least one parameter to be merged from the parameter set; Generating a parameter variable to be verified in the case where at least one of the parameters to be merged is completed, wherein the parameter set and the parameter variable to be verified are data that allows editing; Comparing the parameter variable to be verified with the corresponding standard parameter. If there is no conflict between the parameter variable to be verified and the corresponding standard variable, verifying that the parameter variable is a safe variable, and the standard parameter is a comparison file uploaded in advance for parameter comparison; In the case where the parameter variable to be verified is the safe variable, confirming that the parameter variable to be verified is the parameter variable that can be submitted; Submitting the parameter variable that can be submitted to the approval module for approval.

2. The method according to claim 1, characterized in that, After detecting the uploaded upgrade data packet, the method further includes: Parsing the upgrade data packet and verifying the parsing result; If the verification passes, submitting the upgrade data packet to the approval module, wherein by verifying the upgrade data packet, it is determined whether the upgrade data packet meets the approval conditions; Triggering the approval of the upgrade data packet by using an approval mode that matches the role permissions of the currently logged-in user, wherein the approval mode includes performing at least one approval stage on the upgrade data packet; 3. The method according to claim 1, characterized in that If an uploaded upgrade data packet is detected, approving the upgrade data packet according to the approval mode includes: Triggering an upgrade instruction, wherein the upgrade instruction includes: a software upgrade instruction and a data upgrade instruction; Responding to the upgrade instruction to obtain the upgrade data packet, wherein the upgrade data packet at least includes: a first file for storing at least variable names and variable attributes, and a second file for storing variable values; Detecting whether the format of the upgrade data packet meets the preset format conditions; If it meets the conditions, parsing the upgrade data packet to generate a variable to be detected; Determining whether the variable to be detected is a variable that already exists in the first file; If the variable to be detected does not exist in the first file, extracting the variable value that matches the variable to be detected from the second file and performing assignment; If the variable to be detected already exists in the first file, update the corresponding variable value in the second file.

4. The method according to any one of claims 1 to 3, characterized in that After approving the upgrade data packet according to the approval mode, the method further includes: Receiving the upgrade data packet to be approved, and after the upgrade data packet is approved, generating an approval parameter submission record corresponding to the upgrade data packet, where the approval parameter submission record at least includes: variable change information for which the approval stage has completed approval, and a data file marked with a modification label; Based on the approved upgrade data packet, determine the calibration variables allowed to be submitted. Merge the calibration variables into the main version of the object to be upgraded.

5. The method according to claim 1, wherein In the case where the approval mode is multi-level approval, if the currently logged-in user has approval authority, approve the upgrade data packet based on the triggered approval instruction, and the generated approval result will be submitted to at least one approval process for the next-level approval.

6. A processing device for vehicle data, characterized in that Including: A first receiving module, configured to receive the submitted vehicle data, where the vehicle data is obtained by collecting vehicle parameters of different systems in the vehicle; A permission verification module, configured to determine the role permission of the currently logged-in user based on the role permissions of multiple pre-configured roles, where the role permission is used to represent the permission range for the logged-in user to use the vehicle data; A creation module, configured to create an approval mode that matches the role permission of the currently logged-in user based on the role permission of the currently logged-in user; An approval module, configured to approve the upgrade data packet according to the approval mode if an uploaded upgrade data packet is detected, where the upgrade data packet is a data packet for version upgrading of the object to be upgraded; Wherein, the device further includes: a processing module, configured to determine the parameter variables that can be submitted from a parameter file. Determining the parameter variables that can be submitted from the parameter file includes: receiving an uploaded parameter file, where the parameter set recorded in the parameter file includes: at least one uncalibrated parameter; selecting at least one parameter to be merged from the parameter set; generating a parameter variable to be verified in the case where the at least one parameter to be merged is completed; where the parameter set and the parameter variable to be verified are data allowed to be edited; comparing the parameter variable to be verified with the corresponding standard parameter, if there is no conflict between the parameter variable to be verified and the corresponding standard variable, verifying that the parameter variable is a safe variable, and the standard parameter is a comparison file uploaded in advance for parameter comparison; in the case where the parameter variable to be verified is the safe variable, confirming that the parameter variable to be verified is the parameter variable that can be submitted; submitting the parameter variable that can be submitted to the approval module for approval.

7. The device according to claim 6, wherein The device further includes: A parsing module, configured to parse the upgrade data packet and verify the parsing result; A second submission module, configured to submit the upgrade data packet to the approval module if the verification is passed, where by verifying the upgrade data packet, it is determined whether the upgrade data packet meets the approval conditions. A trigger module, configured to trigger the approval of the upgrade data packet by adopting an approval mode that matches the role permissions of the currently logged-in user, wherein the approval mode includes performing at least one approval stage on the upgrade data packet.

8. A vehicle, characterized in that, The vehicle includes a processing device for the vehicle data, wherein when the device operates, it executes the vehicle data processing method according to any one of claims 1 to 5.

Images