CN112578771B - Vehicle data management method and device, electronic equipment and storage medium - Google Patents
Vehicle data management method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112578771B CN112578771B CN202011474733.0A CN202011474733A CN112578771B CN 112578771 B CN112578771 B CN 112578771B CN 202011474733 A CN202011474733 A CN 202011474733A CN 112578771 B CN112578771 B CN 112578771B
- Authority
- CN
- China
- Prior art keywords
- data
- vehicle
- vehicle controller
- controller
- part number
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
- G05B23/0267—Fault communication, e.g. human machine interface [HMI]
- G05B23/027—Alarm generation, e.g. communication protocol; Forms of alarm
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The invention discloses a vehicle data management method, a vehicle data management device, electronic equipment and a storage medium, wherein the method comprises the following steps: the method comprises the steps of performing component part processing on vehicle controller electronic data to obtain controller electronic information, wherein the controller electronic information comprises the vehicle controller electronic data, a vehicle controller electronic data part number and a vehicle controller electronic data version attribute, and the vehicle controller electronic data comprises software type data and hardware type data; and establishing various engineering material data structures according to different application scenes, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to obtain an engineering material list. The problem that the management efficiency of the existing vehicle data management mode is low and errors are easy to occur can be solved.
Description
Technical Field
The present invention relates to the field of data management technologies, and in particular, to a method and an apparatus for managing vehicle data, an electronic device, and a storage medium.
Background
Conventional vehicle data management usually targets visible and touchable physical parts as main objects. With the advent of vehicle intelligence and software defined automotive, invisible and unobtrusive electronic data management of vehicle controllers has become one of the bases and difficulties for vehicle intelligence and software defined automotive.
At present, the existing vehicle data management mainly uses a hardware material number and a software material number as unique identification marks, when hardware or software is changed, the hardware material number or the software material number needs to be updated, the data management level is simple, but under the condition that materials are more and particularly software is frequently updated, the problems of low management efficiency, update error or update failure are easily caused under the condition that the software is frequently updated; in addition, a software upgrading logic is established through a corresponding relation between a vehicle controller (ECU) and a vehicle model sample, the filling or upgrading of a software program is realized through layer-by-layer calling and searching of the vehicle model sample and the controller, and the problems of low management efficiency and easiness in error occurrence exist.
Disclosure of Invention
The invention provides a vehicle data management method and device, an electronic device and a storage medium, which can solve the problems that the management efficiency of the existing vehicle data management mode is low and errors are easy to occur.
In a first aspect, a method of managing vehicle data includes:
the method comprises the steps of performing component part processing on vehicle controller electronic data to obtain controller electronic information, wherein the controller electronic information comprises the vehicle controller electronic data, a vehicle controller electronic data part number and a vehicle controller electronic data version attribute, and the vehicle controller electronic data comprises software type data and hardware type data;
and establishing various engineering material data structures according to different application scenes, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to obtain an engineering material list.
Optionally, the software-like data includes at least one of basic software, application software, calibration data, configuration parameters, boot programs, graphic data, and navigation data.
Optionally, the application scenes include a first application scene, a second application scene, a third application scene, a fourth application scene, a fifth application scene, and a sixth application scene;
the first application scene is that the software data of the vehicle controller is not required to be filled in a final assembly workshop of the whole vehicle factory; the second application scenario is that the software data needs to be filled into the vehicle controller in a final assembly workshop of the whole vehicle factory; the third application scenario is that a controller mechanical assembly is integrated with two or more controller modules; the fourth application scenario is that two or more than two central processing units are integrated on a vehicle controller circuit board; the fifth application scenario is matched filling or upgrading between different vehicle controllers; the sixth application scenario is matched filling or upgrading of different software type data for the same vehicle controller.
Optionally, the step of establishing a plurality of engineering material data structures according to different application scenarios, the vehicle controller electronic data part number, and the vehicle controller electronic data version attribute to obtain an engineering bill of materials includes:
according to the first application scene, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute, hanging a software type data part number or a hardware type data part number under the vehicle controller part number to form a hanging-down type data structure, and obtaining an engineering material list;
and/or setting the software type data part number and the vehicle controller part number to be in a parallel state according to the second application scene, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to form a parallel data structure to obtain an engineering material list;
and/or setting a virtual controller part number for each controller module integrated on one controller mechanical assembly according to the third application scenario, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute, and simultaneously attaching a controller version attribute; hanging each virtual controller part number under a controller mechanical assembly part number, hanging part of the software type data part numbers under the virtual controller part numbers, setting the rest software type data part numbers and the virtual controller part numbers to be in a parallel state, and attaching the corresponding relation between the rest software type data part numbers and each virtual controller part number behind the rest software type data part numbers; the software data part number in the parallel state and the corresponding virtual controller part number form a first correlation data structure to obtain an engineering material list;
and/or setting a virtual controller part number for each central processing unit according to the fourth application scene, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute, and attaching a controller version attribute to each central processing unit; hanging each virtual controller part number under a vehicle controller circuit board part number, hanging part of the software type data part numbers under the virtual controller part numbers, setting the rest software type data part numbers and the virtual controller part numbers to be in a parallel state, and attaching the corresponding relation of the rest software type data part numbers and each virtual controller part number behind the rest software type data part numbers; the software data part number in the parallel state and the corresponding virtual controller part number form a second associated data structure to obtain an engineering material list;
and/or according to the fifth application scene, the vehicle controller electronic data part numbers and the vehicle controller electronic data version attributes, building each vehicle controller part number in different chunks, building an upgrade document number corresponding to software at a software position in the software type data part number hung under each vehicle controller part number, and simultaneously building an association relationship among the upgrade document numbers to form a third association type data structure to obtain an engineering material list;
and/or according to the sixth application scene, the vehicle controller electronic data part numbers and the vehicle controller electronic data version attributes, constructing the matching incidence relation among the software type data part numbers of various types in the software type data of various types as attributes to form a fourth incidence data structure so as to obtain an engineering material list.
Optionally, the vehicle data management method further includes:
when a vehicle production line is off-line, reading the controller electronic information of the vehicle, and comparing whether the read controller electronic information is consistent with the controller electronic information in the engineering bill of materials or not;
and if the read controller electronic information is inconsistent with the controller electronic information in the engineering material list, alarming and recording alarm information.
Optionally, the vehicle data management method further includes:
according to the function configuration requirement proposed by the vehicle, finding out the corresponding vehicle controller from a function configuration requirement expression;
according to the found vehicle controller, searching whether the corresponding configuration parameters of the parallel data structure exist in the engineering bill of materials;
and if the configuration parameters of the corresponding parallel data structure exist, calling a configuration document corresponding to the configuration parameters, and issuing the associated configuration values in the configuration document to the vehicle.
Optionally, the vehicle data management method further includes:
when the corresponding parallel data structure exists, searching whether the matching incidence relation of the software class data part number exists in the parallel data structure;
and if the matching incidence relation of the software data part number exists, issuing the software data part number related to the matching incidence relation, the corresponding software data and the software data version attribute to the vehicle.
In a second aspect, a management apparatus of vehicle data includes:
the system comprises a component module, a hardware module and a software module, wherein the component module is used for carrying out component processing on electronic data of a vehicle controller to obtain electronic information of the controller, the electronic information of the controller comprises the electronic data of the vehicle controller, the part number of the electronic data of the vehicle controller and the version attribute of the electronic data of the vehicle controller, and the electronic data of the vehicle controller comprises software data and hardware data;
and the data structure building module is used for building various engineering material data structures according to different application scenes, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to obtain an engineering material list.
In a third aspect, an electronic device includes: a memory, a processor and a computer program stored in the memory and executable on the processor, the processor being adapted to implement the steps of the method of managing vehicle data as described in any one of the above when executing the computer program stored in the memory.
In a fourth aspect, a computer-readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of any of the vehicle data management methods described above.
The vehicle data management method, the vehicle data management device, the electronic equipment and the storage medium provided by the application are characterized in that the software data and the hardware data of the vehicle controller are subjected to component processing to obtain corresponding part numbers and version attributes, according to different application scenes, the part numbers and the version attributes corresponding to the software data and the hardware data of the vehicle controller are utilized to construct corresponding data structures in an engineering material list, the engineering material list formed by the data structures is adopted, the management mode of engineering materials is changed from the material number management mode to the data structure management mode, the multiple data structures can deal with various data filling or data upgrading scenes encountered on a vehicle production line, and the software filling or upgrading of the vehicle controller can automatically bring out corresponding data or other vehicle controllers with corresponding relations, related relations or matched related relations or different software of the same vehicle controller according to the part numbers of the vehicle controller The class data part number can improve the management efficiency of engineering materials, improve the efficiency of production line filling data or data upgrading, greatly reduce the error rate of upgrading and updating caused by huge material quantity, and improve the problem of untimely upgrading and updating.
Drawings
Fig. 1 is a schematic flow chart of a vehicle data management method provided in an embodiment of the present application;
FIG. 2 is a schematic diagram of an engineering bill of materials provided in an embodiment of the present application;
fig. 3 is a schematic diagram of an engineering bill of materials corresponding to a second application scenario provided in the embodiment of the present application;
fig. 4 is a schematic diagram of an engineering bill of materials corresponding to a third application scenario provided in the embodiment of the present application;
fig. 5 is a schematic diagram of an engineering bill of materials corresponding to a fourth application scenario provided in the embodiment of the present application;
fig. 6 is a schematic diagram of an engineering bill of materials corresponding to a fifth application scenario provided in the embodiment of the present application;
fig. 7 is a schematic diagram of an engineering bill of materials corresponding to a sixth application scenario provided in the embodiment of the present application;
fig. 8 is a schematic structural block diagram of a vehicle data management device according to an embodiment of the present application;
fig. 9 is a schematic structural block diagram of an electronic device provided in an embodiment of the present application;
fig. 10 is a schematic structural block diagram of a computer-readable storage medium according to an embodiment of the present application.
Detailed Description
In order to better understand the technical solutions provided by the embodiments of the present specification, the technical solutions of the embodiments of the present specification are described in detail below with reference to the drawings and specific embodiments, and it should be understood that the specific features in the embodiments and examples of the present specification are detailed descriptions of the technical solutions of the embodiments of the present specification, and are not limitations on the technical solutions of the embodiments of the present specification, and the technical features in the embodiments and examples of the present specification may be combined with each other without conflict.
In this document, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element. The term "two or more" includes the case of two or more.
Fig. 1 is a schematic flowchart of a vehicle data management method according to an embodiment of the present disclosure. As shown in fig. 1, the present embodiment provides a method for managing vehicle data, including:
s1: the method comprises the steps of performing component part processing on vehicle controller electronic data to obtain controller electronic information, wherein the controller electronic information comprises the vehicle controller electronic data, a vehicle controller electronic data part number and a vehicle controller electronic data version attribute, and the vehicle controller electronic data comprises software type data and hardware type data; the software data may include at least one of basic software BSW, application software SW, calibration data CAL, configuration parameters BEC, a bootstrap Bootloader, graphic data UI/UE, and navigation data, where the basic software BSW and the application software SW include corresponding program files, execution data, and the like, which are not described herein in detail; the vehicle controller ECU belongs to the hardware class data, and the electronic hardware class data can be uniformly characterized by HW. The vehicle controller electronic data part number can comprise a software type data part number, a hardware type data part number, a vehicle controller part number, a controller mechanical assembly part number and the like; the part number can be represented by P/N, and the specific number can be compiled according to the use habit and the like, which is not listed here. The vehicle controller electronic data version attribute may be characterized in the form of a version number, may be a 10-system number, and may be, for example, V4.8.04, where V denotes a version number, 4 denotes a development stage number, 8 denotes a function version number, and 04 denotes a version correction number, and this example is merely illustrative and not intended to limit the present application.
S2: and establishing various engineering material data structures according to different application scenes, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to obtain an engineering material list.
The application scenes may include a first application scene, a second application scene, a third application scene, a fourth application scene, a fifth application scene, and a sixth application scene. The first application scene is that software data filling is not needed to be carried out on the vehicle controller in a final assembly workshop of the whole vehicle factory; the second application scenario is that software data needs to be filled into the vehicle controller in a final assembly workshop of the whole vehicle factory; the third application scenario is that a controller mechanical assembly is integrated with two or more controller modules; the fourth application scenario is that two or more than two central processing units are integrated on a vehicle controller circuit board; the fifth application scenario is matched filling or upgrading among different vehicle controllers; the sixth application scenario is the matched filling or upgrading of different software data for the same vehicle controller. The types of application scenarios listed in this embodiment are only illustrative, and the application scenarios in the practical production process may not be limited to the above application scenarios.
Fig. 2 is a schematic diagram of an engineering bill of materials provided in an embodiment of the present application. As shown in fig. 2, the engineering bill of materials (EBOM) provided in this embodiment may use a vehicle type complete structure as the first-level data, a virtual layer node is hung under the vehicle type complete structure, a function group is hung under the virtual layer node, a block is hung under the function group, a vehicle controller ECU is hung under the block, a hardware HW, an application SW, a boot loader, and the like are hung under the vehicle controller ECU, the virtual layer node 1, the function group 1, the block 1, the ECU1, the ECU2, and the like shown in fig. 2 are schematic, P/N represents a corresponding part number (a specific number is not shown), and V4.8.04 and V4.8.09 are a version number of the hardware HW and a version number of the boot loader, respectively. It should be noted that the engineering bill of materials shown in fig. 2 is only partially schematic and is not meant to limit the present application.
In one possible implementation, step S2 may include one or more of the following steps; that is, in step S2, the plurality of engineering material data structures established according to different application scenarios, vehicle controller electronic data part numbers and vehicle controller electronic data version attributes may include one or more of a downward hanging type data structure, a parallel type data structure, a first relational data structure, a second relational data structure, a third relational data structure and a fourth relational data structure, and may be other types of data structures, the types of the engineering material data structures are not limited to the above listed data structures, and finally all the engineering material data structures constitute the engineering material list.
Illustratively, according to the first application scene, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute, the software type data part number or the hardware type data part number is hung below the vehicle controller part number to form a hanging-down data structure, and the engineering material list is obtained. The local data structure of the engineering bill of materials shown in fig. 2 is a hanging-down data structure, which can be used for a first application scenario, and when the first application scenario is encountered on a vehicle production line of a final assembly plant of a whole vehicle plant, the hanging-down data structure in the engineering bill of materials is called. For example, referring to fig. 2, when the vehicle controller ECU1 of a certain vehicle is installed on a vehicle production line, the software-like data of the vehicle controller ECU1 already exists according to the corresponding hanging-down data structure of the vehicle controller ECU1 in the engineering bill of materials, and does not need to be filled.
Illustratively, according to the second application scene, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute, the software class data part number and the vehicle controller part number are set to be in a parallel state, a parallel data structure is formed, and the engineering material list is obtained. Fig. 3 is a schematic diagram of an engineering bill of materials corresponding to a second application scenario provided in the embodiment of the present application. As shown in fig. 3, in the parallel data structure, the software class data part numbers (SW P/N, CAL P/N, and BEC P/N shown in fig. 3) and the vehicle controller part number (ECU 2P/N) are in a parallel state, which is equivalent to a same level relationship, and when the vehicle controller ECU2 arrives at the vehicle production line, the application software SW, the calibration data CAL, and the configuration parameters BEC corresponding to the vehicle controller ECU2 are not included, and the software class data needs to be loaded on the vehicle production line. When it needs to be explained, the version attribute of HW shown in fig. 3, that is, the version number V3.2.01 is appended after the part number P/N, the version number is only schematically represented, and some part numbers may not identify the version attribute, and are applicable to other figures, and will not be described again in the following; also hanging below the vehicle controller part number ECU 2P/N is a structural component P/N shown in FIG. 3.
Illustratively, according to the third application scenario, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute, setting a virtual controller part number for each controller module integrated on one controller mechanical assembly, and simultaneously attaching the controller version attribute; and hanging each virtual controller part number under a controller mechanical assembly part number, hanging part of software type data part numbers under the virtual controller part numbers, setting the rest software type data part numbers and the virtual controller part numbers to be in a parallel state, attaching the corresponding relation between the rest software type data part numbers and each virtual controller part number behind the rest software type data part numbers, and forming a first relational data structure by the parallel state software data part numbers and the corresponding virtual controller part numbers to obtain an engineering material list. Fig. 4 is a schematic diagram of an engineering bill of materials corresponding to a third application scenario provided in the embodiment of the present application. As shown in fig. 4, the virtual controller part number corresponding to each controller module is hung under the controller mechanical assembly part number, the control module shown in fig. 4 comprises a motor control module, a generator control module and a voltage conversion module, and the corresponding virtual controller part numbers are respectively MCU P/N, GCU P/N and DCDC P/N; the hardware type data part number HW 1P/N and the application software part number SW 1P/N are hung below a motor control module part number MCU P/N, the hardware type part number HW 2P/N and the application software part number SW 2P/N are hung below a generator control module part number GCU P/N, and the hardware type part number HW 3P/N and the application software part number SW 3P/N are hung below a voltage conversion module part number DCDC P/N; the software class data part number in parallel with the virtual controller part number comprises calibration data CAL1, calibration data CAL2, configuration parameters BEC1, configuration parameters BEC2 and configuration parameters BEC3, and the corresponding relations between the virtual controller part number and the software class data are respectively as follows: the calibration data CAL1 is associated with the motor control module MCU, the calibration data CAL2 is associated with the generator control module GCU, the configuration parameters BEC1 is associated with the motor control module MCU, the configuration parameters BEC2 is associated with the generator control module GCU, and the configuration parameters BEC3 is associated with the voltage conversion control module DCDC. When a third application scene is met on the vehicle production line of the general assembly plant of the whole vehicle factory, the first relational data structure in the engineering material list is called. Specifically, when the controller mechanical assembly of a certain vehicle is installed on the vehicle production line, according to the first relational data structure, the calibration data CAL 1and the calibration data CAL2 should be respectively filled into the motor control module MCU and the generator control module GCU, and the configuration parameters BEC1, the configuration parameters BEC2 and the configuration parameters BEC3 should be respectively written into the motor control module MCU, the generator control module GCU and the voltage conversion control module DCDC.
Illustratively, a virtual controller part number is set for each central processing unit according to the fourth application scenario, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute, and the controller version attribute is attached; and hanging each virtual controller part number under a vehicle controller circuit board part number, hanging part of software type data part numbers under the virtual controller part numbers, setting the rest software type data part numbers and the virtual controller part numbers to be in a parallel state, attaching the corresponding relation between the rest software type data part numbers and each virtual controller part number behind the rest software type data part numbers, and forming a second relational data structure by the parallel state software data part numbers and the corresponding virtual controller part numbers to obtain an engineering material list. Fig. 5 is a schematic diagram of an engineering bill of materials corresponding to a fourth application scenario provided in the embodiment of the present application. As shown in fig. 5, the virtual controller part number corresponding to each central processing unit is hung under the vehicle controller circuit board part number, and the virtual controller part numbers corresponding to the central processing units shown in fig. 5 are CPU1P/N, CPU 2P/N and CPU 3P/N respectively; hardware part number HW 4P/N and application software part number SW 4P/N are hung under the CPU part number CPU1P/N, hardware part number HW 5P/N and application software part number SW 5P/N are hung under the CPU part number CPU 2P/N; the software class data part number in parallel with the virtual controller part number comprises calibration data CAL4, calibration data CAL5, configuration parameters BEC4 and configuration parameters BEC5, and the corresponding relations between the virtual controller part number and the software class data are respectively as follows: the calibration data CAL4 is associated with CPU part number CPU1P/N, the calibration data CAL4 is associated with CPU part number CPU 2P/N, the configuration parameters BEC4 is associated with CPU part number CPU1P/N, and the configuration parameters BEC5 is associated with CPU part number CPU 2P/N. When a fourth application scene is met on the vehicle production line of the general assembly workshop of the whole vehicle factory, the second relational data structure in the engineering bill of materials is called. Specifically, when a vehicle controller board of a certain vehicle is mounted on a vehicle production line, calibration data CAL4 and calibration data CAL5 should be filled into the CPU1P/N and the CPU 2P/N, respectively, and configuration parameters BEC4 and BEC5 should be written into the CPU1P/N and the CPU 2P/N, respectively, according to the second relational data structure.
The second relational data structure can be obtained by replacing the part number of the controller mechanical assembly in the first relational data structure with the part number of the vehicle controller circuit board and replacing the part number of the virtual controller corresponding to the control module with the part number of the virtual controller corresponding to the central processing unit.
Fig. 6 is a schematic diagram of an engineering bill of materials corresponding to a fifth application scenario provided in the embodiment of the present application. As shown in fig. 6, exemplarily, according to a fifth application scenario, vehicle controller electronic data part numbers and vehicle controller electronic data version attributes, each vehicle controller part number is built in a different chunk, an upgrade document number corresponding to software is built at a position in a software type data part number hung under each vehicle controller part number, and an association relationship between each upgrade document number is built at the same time, so as to form a third association type data structure, thereby obtaining an engineering material list. As shown in fig. 6, when a fifth application scenario is encountered on the vehicle production line of the complete plant assembly plant, the third associated data structure in the engineering bill of materials is invoked. For example, when a plurality of vehicle controllers of a certain vehicle are installed on a vehicle production line and the plurality of vehicle controllers must be associated with a control system for operating the whole vehicle to normally operate, software class data of the plurality of controllers needs to be synchronously filled. Fig. 6 shows only two vehicle controllers, taking two vehicle controllers as an example, when the vehicle controller ECU 1and the vehicle controller ECU2 must operate in association, and the software class data SW 1and the software class data SW2 corresponding to the vehicle controller ECU 1and the vehicle controller ECU2 need to be synchronously filled, it is necessary to construct the ECU 1P/N and the ECU 2P/N under the chunks 1and 2 respectively, then establish the upgrade document numbers JE 1and JE2 after the software class data SW 1and the software class data SW2 hung under the ECU 1P/N and the ECU 2P/N respectively, and attach association relationships and association notification books, that is, the association notification 1 of the association JE2 and SW 2P/N is recorded in the association notification book of the SW 1P/N upgrade correspondence JE1, SW 2P/N upgrade correspondence JE2 and SW 1P/N. The vehicle controller ECU 1and the application software SW 1and SW2 of the vehicle controller ECU2 are synchronously filled.
Illustratively, according to a sixth application scenario, the vehicle controller electronic data part numbers and the vehicle controller electronic data version attributes, the matching association relations among the software class data part numbers of various types are constructed in the software class data of various types as attributes, a fourth association data structure is formed, and the engineering material list is obtained. Fig. 7 is a schematic diagram of an engineering bill of materials corresponding to a sixth application scenario provided in the embodiment of the present application. As shown in fig. 7, taking the example that the vehicle controller ECU 1and the vehicle controller ECU1 correspond to the suspended application software SW1, application software SW2, calibration data CAL 1and calibration data CAL2, the application software SW1, application software SW2, calibration data CAL 1and calibration data CAL2 respectively upgrade the corresponding JE1, JE3, JE2 and JE4, and the matching relationship of each software class data is: the application software SW1 is matched with the JE2 corresponding to the upgrade of the associated calibration data CAL1, and the application software SW2 is matched with the JE4 corresponding to the upgrade of the associated calibration data CAL 2. When different software data of the vehicle controller ECU1 are filled or upgraded, the data with matching relation can be packaged and downloaded at one time according to the matching relation.
S3: and when the vehicle production line is off-line, reading the controller electronic information of the vehicle, and comparing whether the read controller electronic information is consistent with the controller electronic information in the engineering material list. When a vehicle production line is offline, the offline vehicle needs to be finally inspected, whether the electronic data of the controller of the vehicle is consistent with the electronic information of the controller in the engineering bill of materials is checked, and therefore the electronic data in the controller in the factory vehicle is in the latest state.
S4: and if the read controller electronic information is inconsistent with the controller electronic information in the engineering bill of materials, alarming and recording alarm information.
S5: and finding out the corresponding vehicle controller from the functional configuration requirement expression according to the functional configuration requirement proposed by the vehicle.
S6: and searching whether the configuration parameter BEC of the corresponding parallel data structure exists in the engineering bill of materials according to the found vehicle controller.
S7: and if the configuration parameters BEC of the corresponding parallel data structure exist, calling the configuration document corresponding to the configuration parameters BEC, and issuing the associated configuration values in the configuration document to the vehicle.
Table 1 shows an example of the content of the configuration document corresponding to the configuration parameter BEC. As shown in table 1, expression 1 is configured: KA0a01T AND MACAW001AND MDDX000 AND configuration expression 2: KA0a01T AND MDDX002ND MDDK006 both represent configurable vehicle models corresponding to a vehicle controller BCM, AND can be KA0a01T AND macaaw 001AND MDDX000 AND KA0a01T AND MDDX002ND MDDK006, respectively, a vehicle having a configuration requirement can provide a function configuration requirement, the function configuration requirement carries a function configuration requirement expression, the function configuration requirement expression records a model of the vehicle, a controller part number to be configured AND a related configuration value, for example, a vehicle body controller identifier to be configured shown in table 1 is BCM ID, the vehicle controller part number (which may be BCM P/N as an example) may be corresponded to by the vehicle controller identifier being BCM ID, the associated configuration value corresponding to the vehicle model of configuration expression 1 is 0111, namely, the function configuration content comprises the prohibition of a driving locking function, the activation of a vehicle body anti-theft function, the activation of an emergency brake alarm function and the type of a front steering lamp which is an LED; the associated configuration value corresponding to the vehicle model in configuration expression 2 is 0100, that is, the functional configuration content is the prohibition of the driving locking function, the activation of the vehicle body anti-theft function, the prohibition of the emergency braking alarm function, and the type of the front steering lamp is a bulb.
The configuration document content corresponding to the configuration parameters shown in table 1 is only illustrative and not limited in particular.
TABLE 1
S8: and when the corresponding parallel data structure exists, searching whether the matching incidence relation of the software class data part number exists in the parallel data structure.
S9: and if the matching incidence relation of the software data part numbers exists, the software data part numbers related to the matching incidence relation, the corresponding software data and the corresponding software data version attributes are issued to the vehicle. Whether the matching incidence relation of the software data part numbers exists or not is found, different software data of the vehicle controller can be packed, downloaded and sent at one time according to the existing matching incidence relation, and the service efficiency and the service quality can be improved.
The vehicle data management method provided by the application comprises the steps of performing component processing on software data and hardware data of a vehicle controller to obtain corresponding part numbers and version attributes, constructing corresponding data structures in a project material list by using the part numbers and the version attributes corresponding to the software data and the hardware data of the vehicle controller according to different application scenes, adopting the project material list formed by the data structures, changing the management mode of the project materials from the material number management mode into the data structure management mode, enabling a plurality of data structures to cope with the scenes of various data filling or data upgrading encountered on a vehicle production line, enabling the software filling or upgrading of the vehicle controller to automatically bring out corresponding data or different software data part numbers of other vehicle controllers with corresponding relations, related relations or matched related relations or the same vehicle controller according to the part numbers of the vehicle controller, the method and the device have the advantages that the management efficiency of engineering materials is improved, the efficiency of production line filling data or data upgrading is improved, the upgrading and updating error rate caused by large material quantity can be greatly reduced, and the problem that upgrading and updating are not timely can be solved.
Fig. 8 is a schematic structural block diagram of a vehicle data management device according to an embodiment of the present application. As shown in fig. 8, the present embodiment provides a vehicle data management device, including:
the component module 1 is used for performing component processing on the electronic data of the vehicle controller to obtain electronic information of the controller, wherein the electronic information of the controller comprises electronic data of the vehicle controller, part numbers of the electronic data of the vehicle controller and version attributes of the electronic data of the vehicle controller, and the electronic data of the vehicle controller comprises software data and hardware data.
And the data structure building module 2 is used for building various engineering material data structures according to different application scenes, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to obtain an engineering material list.
Fig. 9 is a schematic structural block diagram of an electronic device according to an embodiment of the present application. As shown in fig. 9, an electronic device 900 according to an embodiment of the present application includes a memory 910, a processor 920 and a computer program 911 stored in the memory 910 and executable on the processor 920, where the processor 920 executes the computer program 911 to implement the following steps:
the method comprises the steps of performing component part processing on vehicle controller electronic data to obtain controller electronic information, wherein the controller electronic information comprises the vehicle controller electronic data, a vehicle controller electronic data part number and a vehicle controller electronic data version attribute, and the vehicle controller electronic data comprises software type data and hardware type data;
and establishing various engineering material data structures according to different application scenes, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to obtain an engineering material list.
In particular embodiments, any of the above embodiments may be implemented when processor 920 executes computer program 911.
Since the electronic device described in this embodiment is a device used for implementing a vehicle data management apparatus in this embodiment, based on the method described in this embodiment, a person skilled in the art can understand the specific implementation manner of the electronic device of this embodiment and various modifications thereof, so that how to implement the method in this embodiment by the electronic device is not described in detail herein, and as long as the person skilled in the art implements the device used for implementing the method in this embodiment, the scope of protection intended by this application falls.
Fig. 10 is a schematic structural block diagram of a computer-readable storage medium according to an embodiment of the present application. As shown in fig. 10, the present embodiment provides a computer-readable storage medium a00, on which a computer program a11 is stored, which computer program a11 implements the following steps when executed by a processor:
the method comprises the steps of performing component part processing on vehicle controller electronic data to obtain controller electronic information, wherein the controller electronic information comprises the vehicle controller electronic data, a vehicle controller electronic data part number and a vehicle controller electronic data version attribute, and the vehicle controller electronic data comprises software type data and hardware type data;
and establishing various engineering material data structures according to different application scenes, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to obtain an engineering material list.
In a specific implementation, the computer program a11, when executed by a processor, may implement any of the above embodiments.
The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present specification have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all changes and modifications that fall within the scope of the specification.
It will be apparent to those skilled in the art that various changes and modifications can be made in the present specification without departing from the spirit and scope of the specification. Thus, if such modifications and variations of the present specification fall within the scope of the claims of the present specification and their equivalents, the specification is intended to include such modifications and variations.
Claims (10)
1. A method for managing vehicle data, comprising:
the method comprises the steps of performing component part processing on vehicle controller electronic data to obtain controller electronic information, wherein the controller electronic information comprises the vehicle controller electronic data, a vehicle controller electronic data part number and a vehicle controller electronic data version attribute, and the vehicle controller electronic data comprises software type data and hardware type data;
establishing various engineering material data structures according to different application scenes, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to obtain an engineering material list;
under the condition that the application scenes comprise a first application scene and a second application scene, the first application scene is that the vehicle controller is not required to be filled with the software data in a final assembly workshop of the whole vehicle factory, the second application scene is that the vehicle controller is required to be filled with the software data in the final assembly workshop of the whole vehicle factory, and multiple engineering material data structures are established according to different application scenes, the electronic data of the vehicle controller, the electronic data part number of the vehicle controller and the electronic data version attribute of the vehicle controller to obtain an engineering material list, wherein the method comprises the following steps of:
and setting the software type data part number and the vehicle controller part number to be in a parallel state according to the second application scene, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to form a parallel data structure so as to obtain the engineering material list.
2. The method for managing vehicle data according to claim 1, wherein the software-type data includes at least one of basic software, application software, calibration data, configuration parameters, a guidance program, graphic data, and navigation data.
3. The management method of vehicle data according to claim 1, wherein the application scenes include a third application scene, a fourth application scene, a fifth application scene, and a sixth application scene;
the third application scenario is that a controller mechanical assembly is integrated with two or more controller modules; the fourth application scenario is that two or more than two central processing units are integrated on a vehicle controller circuit board; the fifth application scenario is the matching filling or upgrading between different vehicle controllers; the sixth application scenario is matched filling or upgrading of different software type data for the same vehicle controller.
4. The method for managing vehicle data according to claim 3, wherein the step of building a plurality of engineering material data structures according to different application scenarios, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to obtain an engineering material list comprises:
setting a virtual controller part number for each controller module integrated on one controller mechanical assembly according to the third application scene, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute, and attaching a controller version attribute at the same time; hanging each virtual controller part number under a controller mechanical assembly part number, hanging part of the software type data part numbers under the virtual controller part numbers, setting the rest software type data part numbers and the virtual controller part numbers to be in a parallel state, and attaching the corresponding relation between the rest software type data part numbers and each virtual controller part number behind the rest software type data part numbers; the software data part number in the parallel state and the corresponding virtual controller part number form a first correlation data structure to obtain an engineering material list;
and/or setting a virtual controller part number for each central processing unit according to the fourth application scene, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute, and simultaneously attaching a controller version attribute; hanging each virtual controller part number under a vehicle controller circuit board part number, hanging part of the software type data part numbers under the virtual controller part numbers, setting the rest software type data part numbers and the virtual controller part numbers to be in a parallel state, and attaching the corresponding relation between the rest software type data part numbers and each virtual controller part number behind the rest software type data part numbers; the software data part number in the parallel state and the corresponding virtual controller part number form a second associated data structure to obtain an engineering material list;
and/or according to the fifth application scene, the vehicle controller electronic data part numbers and the vehicle controller electronic data version attributes, building each vehicle controller part number in different chunks, building an upgrade document number corresponding to software at a software position in the software type data part number hung under each vehicle controller part number, and simultaneously building an association relationship among the upgrade document numbers to form a third association type data structure to obtain an engineering material list;
and/or according to the sixth application scene, the vehicle controller electronic data part numbers and the vehicle controller electronic data version attributes, constructing the matching incidence relation among the software type data part numbers of various types in the software type data of various types as attributes to form a fourth incidence data structure so as to obtain an engineering material list.
5. The management method of vehicle data according to claim 4, characterized by further comprising:
when a vehicle production line is off-line, reading the controller electronic information of the vehicle, and comparing whether the read controller electronic information is consistent with the controller electronic information in the engineering bill of materials or not;
and if the read controller electronic information is inconsistent with the controller electronic information in the engineering material list, alarming and recording alarm information.
6. The management method of vehicle data according to claim 4, characterized by further comprising:
according to the function configuration requirement proposed by the vehicle, finding out the corresponding vehicle controller from a function configuration requirement expression;
according to the found vehicle controller, searching whether the corresponding configuration parameters of the parallel data structure exist in the engineering bill of materials;
and if the configuration parameters of the corresponding parallel data structure exist, calling a configuration document corresponding to the configuration parameters, and issuing the associated configuration values in the configuration document to the vehicle.
7. The management method of vehicle data according to claim 6, characterized by further comprising:
when the corresponding parallel data structure exists, searching whether the matching incidence relation of the software class data part number exists in the parallel data structure;
and if the matching incidence relation of the software data part number exists, issuing the software data part number related to the matching incidence relation, the corresponding software data and the software data version attribute to the vehicle.
8. A management apparatus of vehicle data, characterized by comprising:
the system comprises a component module, a hardware module and a software module, wherein the component module is used for performing component processing on vehicle controller electronic data to obtain controller electronic information, the controller electronic information comprises the vehicle controller electronic data, a vehicle controller electronic data part number and a vehicle controller electronic data version attribute, and the vehicle controller electronic data comprises software type data and hardware type data;
the data structure building module is used for building various engineering material data structures according to different application scenes, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to obtain an engineering material list;
under the condition that the application scenes comprise a first application scene and a second application scene, the first application scene is that the vehicle controller is not required to be filled with the software data in a final assembly workshop of the whole vehicle factory, the second application scene is that the vehicle controller is required to be filled with the software data in the final assembly workshop of the whole vehicle factory, and multiple engineering material data structures are established according to different application scenes, the electronic data of the vehicle controller, the electronic data part number of the vehicle controller and the electronic data version attribute of the vehicle controller to obtain an engineering material list, wherein the method comprises the following steps of:
and setting the software type data part number and the vehicle controller part number to be in a parallel state according to the second application scene, the vehicle controller electronic data part number and the vehicle controller electronic data version attribute to form a parallel data structure so as to obtain the engineering material list.
9. An electronic device, comprising: memory, a processor and a computer program stored in the memory and executable on the processor for implementing the steps of the method for managing vehicle data according to any one of claims 1 to 7 when executing the computer program stored in the memory.
10. A computer-readable storage medium, characterized in that a computer program is stored thereon, which computer program, when being executed by a processor, carries out the steps of a method of managing vehicle data of a vehicle according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011474733.0A CN112578771B (en) | 2020-12-14 | 2020-12-14 | Vehicle data management method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011474733.0A CN112578771B (en) | 2020-12-14 | 2020-12-14 | Vehicle data management method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112578771A CN112578771A (en) | 2021-03-30 |
| CN112578771B true CN112578771B (en) | 2022-05-17 |
Family
ID=75134881
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011474733.0A Active CN112578771B (en) | 2020-12-14 | 2020-12-14 | Vehicle data management method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112578771B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113434484A (en) * | 2021-06-29 | 2021-09-24 | 青岛海尔科技有限公司 | Method, system, device and electronic device for describing functions of equipment |
| CN114326679B (en) * | 2021-12-30 | 2023-07-18 | 深蓝汽车科技有限公司 | Method and system for refreshing controller based on one-edition integrated software |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101877080A (en) * | 2009-04-30 | 2010-11-03 | 厦门敏讯信息技术股份有限公司 | Method for automatically generating configuration of bill of material (BOM) |
| DE102010050385A1 (en) * | 2009-11-09 | 2011-06-09 | GM Global Technology Operations LLC, ( n. d. Ges. d. Staates Delaware ), Detroit | Interface control module for product line managing module mounted in vehicle e.g. car, has interface viewing module that displays logical and physical views of product on display before/after assembly of product |
| CN103593727B (en) * | 2013-10-25 | 2016-08-31 | 长安标致雪铁龙汽车有限公司 | The management method of a kind of vehicle manufacturing BOM and management system |
| KR20180036090A (en) * | 2016-09-30 | 2018-04-09 | 한국항공대학교산학협력단 | Logistic automatization equipment maintenance database constructing system based on cloud server, and method thereof |
| CN110968077A (en) * | 2019-12-23 | 2020-04-07 | 奇瑞汽车股份有限公司 | Intelligent interconnection error-proofing method for automobile electronic and electric appliance control module |
-
2020
- 2020-12-14 CN CN202011474733.0A patent/CN112578771B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN112578771A (en) | 2021-03-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112578771B (en) | Vehicle data management method and device, electronic equipment and storage medium | |
| US20080092131A1 (en) | Centralized management of human machine interface applications in an object-based supervisory process control and manufacturing information system environment | |
| US20110112679A1 (en) | Product-line based content management systems and methods | |
| JP6757735B2 (en) | Systems and methods for provisioning cloud services across heterogeneous computing environments | |
| WO2019149051A1 (en) | Method for configuring automobile diagnosis function, apparatus, and automobile diagnosis device | |
| CN110244958A (en) | The method and apparatus of nominal data for more new vehicle | |
| US20180052698A1 (en) | Modifying and simulating the operating software of a technical system | |
| CN111176664A (en) | Storage cluster setting method, device, medium and equipment | |
| CN103577201A (en) | Embedded dual system updating method and system | |
| CN116737117A (en) | Model development method based on Autosar architecture | |
| CN110825409B (en) | Parameter management method, electronic device and computer storage medium | |
| CN108920171A (en) | Firmware update and device, electronic equipment | |
| CN105630547A (en) | Patch program installing method and patch program installing device | |
| CN113246883A (en) | Control method for multi-vehicle configuration, micro control unit and vehicle-mounted machine system | |
| CN106990981B (en) | Program updating method and device | |
| US10157062B2 (en) | Method for operating a microprocessor | |
| CN115630436A (en) | Super product structure tree management system developed in parallel for series ships | |
| US11210267B2 (en) | Electronic control unit comparison | |
| US10521332B1 (en) | Parametrization of a simulation model | |
| JP6945481B2 (en) | Software development equipment | |
| CN115668130A (en) | Device and method for managing an electronic control unit of a motor vehicle | |
| CN115576952B (en) | Method for realizing vehicle-mounted android platform communication structure based on Unreal | |
| CN111221542B (en) | Method, device, system, equipment and medium for generating and installing system mirror image | |
| TWI792822B (en) | Software upgrade system, software upgrade method and non-transitory recording medium | |
| CN117081976B (en) | Method and device for configuring gateway route |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |