Whole vehicle information management method, device and equipment and storage medium

Abstract

The invention discloses a whole vehicle information management method, device and equipment and a storage medium, and the method comprises the steps: carrying out the digital coding of each electronic control unit of a vehicle, and defining the tracing information needed by each electronic control unit on the basis of the digital coding; and carrying out segmented arrangement on the obtained traceability information of the electric control unit according to bytes, and uploading the traceability information subjected to segmented arrangement to a whole vehicle electric appliance data server according to a byte format so as to manage the whole vehicle information. According to the invention, the information of the vehicle electronic control unit can be traced completely, and the updating and maintenance of the electric appliances of the vehicle can be monitored conveniently when the vehicle is used.

Description

Technical Field

[0001] The present invention relates to the field of automobile manufacturing, and in particular to a whole vehicle information management method, device, equipment and storage medium. Background Art

[0002] At present, the development of the automobile industry is increasingly leaning towards intelligence. There are more and more ECU control units in the whole vehicle, and the frequency of ECU hardware and software version updates is also getting faster and faster. In addition, various installations and modifications on the market side make it increasingly difficult to trace the ECU information of the vehicle on the client side. Not only the update of the software version needs to be traced, but also the traceability of the unauthorized replacement and modification of the hardware is of top priority, especially for some ECUs that are bound one-to-one to the whole vehicle, the traceability requirements are more complicated.

[0003] Therefore, how to completely trace the information of the vehicle's electronic control unit is a technical problem that urgently needs to be solved. Summary of the invention

[0004] The main purpose of the present invention is to provide a vehicle information management method, device, equipment and storage medium, which can completely trace the information of the vehicle's electronic control unit, and also facilitate monitoring of the vehicle's electrical appliance updates and maintenance when the vehicle is in use.

[0005] In a first aspect, the present application provides a vehicle information management method, wherein the method comprises the steps of:

[0006] Digitally encode each electronic control unit of the vehicle, and define the traceability information required for each electronic control unit based on the digital code;

[0007] The acquired traceability information of the electric control unit is segmented and sorted by bytes, and the segmented traceability information is uploaded to the vehicle electrical data server in a byte format to manage the vehicle information.

[0008] In combination with the first aspect above, as an optional implementation method, an electronic control unit IEA CODE dictionary comparison table is created;

[0009] Based on the dictionary comparison table, each electronic control unit is digitally encoded to trace the attribute information of the electronic control unit.

[0010] In combination with the first aspect above, as an optional implementation method, a different code is added to the first position of each electronic control unit code to differentiate the traceability information required for each electronic control unit, wherein the traceability information includes: hardware number, software number, serial number, vehicle body number, address, format, user identification number UIN, integrated circuit card identification code ICCID, unique identification code IMEI and international mobile user identity code IMSI.

[0011] In combination with the first aspect above, as an optional implementation method, at the terminal electrical inspection station, the vehicle electrical inspection equipment is used to read the traceability information of all the electronic control units of the vehicle;

[0012] The read electronic control unit traceability information is automatically segmented and sorted according to a set number of bytes as a group.

[0013] In combination with the first aspect above, as an optional implementation method, when the vehicle is offline for electrical inspection, the vehicle electrical inspection equipment is used to communicate with each electronic control unit of the vehicle to check whether the software and hardware information of the electronic control unit meets the definition.

[0014] In combination with the first aspect above, as an optional implementation method, based on the corresponding storage location reserved behind the electronic control unit code, the sorted traceability information is stored in a data format with a set number of bytes as a group, and according to the correspondence between the storage address of the electronic control unit and the electronic control unit code, a traceability file is generated and transmitted to the vehicle electrical data server.

[0015] In combination with the first aspect above, as an optional implementation method, the ECU traceability information is transmitted to the after-sales information quality COVRET system to maintain the vehicle ECU.

[0016] In a second aspect, the present application provides a vehicle information management device, the device comprising:

[0017] A definition module, which is used to digitally encode each electronic control unit of the vehicle and define the traceability information required for each electronic control unit based on the digital encoding;

[0018] The processing module is used to segment and organize the acquired traceability information of the electric control unit by bytes, and upload the segmented traceability information to the vehicle electrical data server in the byte format to manage the vehicle information.

[0019] In a third aspect, the present application further provides an electronic device, comprising: a processor; a memory, wherein the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the method described in any one of the first aspects is implemented.

[0020] In a fourth aspect, the present application further provides a computer-readable storage medium storing computer program instructions, which, when executed by a computer, enables the computer to execute any of the methods described in the first aspect.

[0021] The present application provides a vehicle information management method, device, equipment and storage medium, wherein the method includes the steps of: digitally encoding each electronic control unit of the vehicle, and defining the traceability information required for each electronic control unit based on the digital encoding; arranging the acquired traceability information of the electronic control unit by segment by byte, and uploading the segmented traceability information to the vehicle electrical data server in the format of bytes to manage the vehicle information. The present application can completely trace the information of the vehicle's electronic control unit, and also facilitates monitoring the vehicle's electrical updates and maintenance when the vehicle is in use.

[0022] It is to be understood that the foregoing general description and the following detailed description are exemplary only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0024] Figure 1 A flow chart of a vehicle information management method provided in an embodiment of the present application;

[0025] Figure 2 A schematic diagram of a vehicle information management device provided in an embodiment of the present application;

[0026] Figure 3 A schematic diagram of the flow of traceability information of an electronic control unit provided in an embodiment of the present application;

[0027] Figure 4 A schematic diagram of an electronic device provided in an embodiment of the present application;

[0028] Figure 5 A schematic diagram of a computer-readable program medium provided in an embodiment of the present application. DETAILED DESCRIPTION

[0029] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.

[0030] Furthermore, the drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. Some of the blocks shown in the drawings are functional entities and do not necessarily correspond to physically or logically separate entities.

[0031] The embodiments of the present application are further described in detail below in conjunction with the accompanying drawings.

[0032] Reference Figure 1 , Figure 1 FIG. 1 is a flow chart of a vehicle information management method provided by the present invention, such as Figure 1 As shown, the method comprises the steps of:

[0033] Step S101: digitally encode each electronic control unit of the vehicle, and define the traceability information required for each electronic control unit based on the digital code.

[0034] Specifically, an electronic control unit IEA CODE dictionary comparison table is created; based on the dictionary comparison table, each electronic control unit is digitally encoded to trace the attribute information of the electronic control unit (hardware number, software number, calibration number, configuration (Dote) number and production batch information, etc.).

[0035] For easy understanding, an example is given to create an electronic control unit IEA CODE dictionary comparison table, and a CODE definition is given for each electronic control unit to trace the hardware number, software number, calibration number, configuration (Dote) number and production batch information of the electronic control unit. It can be understood that all electronic control units (ECUs) are equivalent to a digital coding management according to IEA CODE, which is 2 bits (for example: the code is: 4R, the corresponding ECU type is: AAS, and its Chinese name is: reversing radar control box, and for example: the code is 6S, the corresponding ECU type is: ADML, and its Chinese name is: key detection control box, for example: the code is: 8W, the corresponding ECU type is: AFS, and its Chinese name is: headlight follow-up steering control, see Table 1 for details). Among them, IEA is an electronic and electrical ECU part (Intergration Electrical Architecture), and CODE is the code.

[0036] Among them, the electronic control unit IEA CODE dictionary comparison table 1 (partial content) is as follows:

[0037] Table 1

[0038] IEA CODE ECU type Chinese name 4R AAS Reversing radar control box 6S ADML Key detection control box 8W AFS Headlight Adaptive Steering Control 6J ALARM Burglar alarm 8Y AMPLI Sound Power Amplifier 9K ARTIV ADAS radar 2M AVAS Electric car sound simulator 4V AVE Electronic anti-theft lock 2E AVM 360-degree reversing image 4P ESP Anti-lock brake hydraulic unit

[0039] It should be noted that the complete traceability of the vehicle's ECU information includes the hardware number, software number, serial number, and the vehicle body number that some ECUs require to be written.

[0040] On the basis of the digital coding, the traceability information required for each electronic control unit is defined, that is, the first digit is added before the IEA CODE to distinguish the information type. It can be understood that the two-digit code of each ECU is preceded by a different code, which represents the information corresponding to this ECU. For example, adding 1 in front represents the hardware number of this ECU, adding 9 represents the software number, and the two variables 4 and D together represent the serial number (because some serial numbers may be very long), etc. For example, the part represented by 4P in the ECU dictionary is the ESP brake hydraulic unit, then 14P represents the hardware number of this part, 94P represents the software number, 54P represents the production date, etc., which is convenient for transmission during the entire traceability process.

[0041] It needs to be explained that a different code is added to the first position of each electronic control unit code to differentiate the traceability information required for each electronic control unit.

[0042] In addition, it should be noted that the electronic traceability information of ECU generally includes basic information such as hardware number, software number, production date, serial number, etc. Some ECU electronic control units also need to trace the VIN of the vehicle they are installed in, and some need to link with the background data. Supplementary information such as UIN. This application conducts differentiated classification management in the development stage of ECU, and defines the writing DID (data identifier) ​​and format of the basic information, VIN, and supplementary information that each ECU needs to trace (DID corresponds to the IEA address, that is, what information should be represented at the position of this identifier. For example, for the ESP hydraulic unit mentioned above, the manufacturer and supplier must simultaneously define which DID stores the information of the parts and the traceability information that needs to be collected in the CG system (vehicle electrical data server). For example, if the hardware number supplier stores some bits of DID F080, then the manufacturer reads DID F080 when obtaining it and synchronizes the corresponding bits to 14P of the traceability information of the vehicle.). In this way, the same path and format are used for processing during the entire process of writing, exporting, reading and storing the traceability information, so that the traceability information is one-to-one and orderly.

[0043] The traceability information required for each electronic control unit is defined, and the brake hydraulic unit ESP is taken as an example as shown in Table 2.

[0044] Table 2

[0045]

[0046]

[0047] For some electronic control unit parts with special requirements, such as ECU based on network security regulations, it is necessary to trace UIN (user identification number), ICCID (integrated circuit card identification code), IMEI (unique identification code), IMSI (international mobile subscriber identity code) and other information. New information types can be added at any time according to needs, as shown in Table 3: OTA (over-the-air download technology) receiving module BSRF (IEA CODE is L9) needs to add relevant information fields 4L9 / DL9 / KL9 / LL9 / NL9 / RL9 / SL9 / ML9.

[0048] Table 3

[0049]

[0050] It should be noted that some traceability information is very long, so 2 segments are reserved. This solution is designed with a field of 13 bytes: 1-bit information category code (added first digit code) + 2-bit part ECU code (digital code) + 10-bit information content.

[0051] Step S102: The acquired traceability information of the electric control unit is segmented and sorted by bytes, and the segmented traceability information is uploaded to the vehicle electrical data server in a byte format to manage the vehicle information.

[0052] Specifically, at the terminal electrical inspection station, the vehicle electrical inspection equipment is used to read all the electronic control unit traceability information of the vehicle; the read electronic control unit traceability information is automatically segmented and sorted into groups of a set number of bytes.

[0053] In one embodiment, when the vehicle is offline for electrical inspection, the vehicle electrical inspection equipment is used to communicate with each electronic control unit of the vehicle to check whether the software and hardware information of the electronic control unit meets the definition.

[0054] It is understandable that all vehicle manufacturers will check whether the software download of all ECUs on the vehicle is successful, whether there are electrical defects, fault codes, etc. when the vehicle is commercially launched. This process is usually called offline electrical inspection, or simply electrical inspection. During the electrical inspection, COC-EV will communicate with each ECU of the vehicle to check whether the software and hardware information meets the definition.

[0055] That is, by using the communication process between COC-EV and each ECU during the electrical inspection, the manufacturing information other than the software and hardware number is read from each ECU, and the data information is classified, stored, and uploaded. The traceability of each ECU of the vehicle is required by regulations. This method can reduce the need to abandon the physical barcode traceability scheme and adopt electronic information traceability, which is more convenient and accurate.

[0056] Specifically, at the terminal electrical inspection station, after using COCev to read the traceability information of the vehicle ECU, it is automatically sorted according to the 13-byte standard, that is, 13 bytes are grouped and sorted in sections. Each 13 bytes is a section of information. For example, WK4131000N000, the first digit is the distinguishing code (W), the second and third digits are digital codes (K4), and the last 10 digits are the content, which is parsed to obtain the VSM parts of this vehicle.

[0057] It should be explained that due to some special traceability information, the bytes will exceed 13 bytes, and the spaces in the middle will be used to represent the bytes exceeding 13 bytes, for example: D4A...533, and ML9...94667. That is to say, their length is still the same as 13 bytes, but they are represented by spaces in the middle. When identifying, you only need to identify the first three digits to identify the complete ECU information.

[0058] Based on the corresponding storage location reserved behind the electronic control unit code, the sorted traceability information is stored in a data format with a set number of bytes as a group, and a traceability file is generated and transmitted to the vehicle electrical data server according to the correspondence between the storage address of the electronic control unit and the electronic control unit code.

[0059] In one embodiment, the ECU traceability information is transmitted to an after-sales information quality COVRET system to maintain the vehicle ECU.

[0060] It is understandable that a storage location is reserved behind the corresponding CODE (the parts supplier writes its own information including hardware number / software number / serial number, etc., and writes the information that the vehicle manufacturer needs to trace, such as the vehicle body number, flash date, UIN activation code, etc. when the vehicle manufacturer is initialized; all information is read and stored when the vehicle is offline for electrical inspection.), and the segmented 13-byte traceability information is stored in the format of 13 bytes per group, and the traceability file is generated according to the correspondence between the part storage address and the IEA CODE and passed to the CG system. The basic data required for the vehicle to perform electrical initialization and electrical inspection comes from the CG system. The system serves as a server for the electrical data of the whole vehicle, and provides the upstream vehicle definition as the input of the initialization device during initialization; after the electrical inspection, the vehicle electrical data collected by the electrical inspection equipment (including the traceability information of each electronic control unit) is received, stored and uploaded to the vehicle after-sales information management system (COVRET). The after-sales information quality COVRET system is used for after-sales service. The advantage of storing the CG system is that the traceability information storage is mainly used for after-sales. The CG system collects it at the end of the production line and then passes it to the after-sales information management system for after-sales network query.

[0061] To sum up, traceability can not only realize the life cycle management of goods from procurement, production, sales, storage and other links, but also realize the functions of "safety early warning, source traceability, flow tracking, information query, responsibility identification, and product recall".

[0062] This application uses electronic information for tracing, and classifies and combines all traceability information, and stores it in a fixed format (13 bytes per group, i.e. 13*N). By giving each product a unique electronic traceability code and associating it with the vehicle (inter-association refers to the association between parts and vehicles, because the traceability information is generated separately for each vehicle and is unique), the risk of counterfeiting and selling fakes is avoided. By tracing through the system and managing the update and replacement of the vehicle's electronic control unit in real time, the rights and interests of consumers can be better protected, and favorable evidence can be produced when the interests of the enterprise are infringed.

[0063] Reference Figure 2 , Figure 2 FIG. 1 is a schematic diagram of a vehicle information management device provided by the present invention, such as Figure 2 As shown, the device comprises:

[0064] Definition module 201: It is used to digitally encode each electronic control unit of the vehicle, and define the traceability information required for each electronic control unit based on the digital encoding.

[0065] Processing module 202: It is used to organize the acquired ECU traceability information by segments according to bytes, and upload the segmented traceability information to the vehicle electrical data server in the byte format to manage the vehicle information.

[0066] Furthermore, in a possible implementation manner, the definition module is also used to create an electronic control unit IEA CODE dictionary comparison table;

[0067] Based on the dictionary comparison table, each electronic control unit is digitally encoded to trace the attribute information of the electronic control unit.

[0068] Furthermore, in a possible implementation, the definition module is also used to add a different code in the first position of each electronic control unit code to differentiate the traceability information required for each electronic control unit, wherein the traceability information includes: hardware number, software number, serial number, vehicle body number, address, format, user identification number UIN, integrated circuit card identification code ICCID, unique identification code IMEI and international mobile user identity code IMSI.

[0069] Furthermore, in a possible implementation manner, the processing module is also used to read the traceability information of all the electronic control units of the whole vehicle using the whole vehicle electrical inspection equipment at the terminal electrical inspection station;

[0070] The read electronic control unit traceability information is automatically segmented and sorted according to a set number of bytes as a group.

[0071] Furthermore, in a possible implementation, the processing module is also used to communicate with each electronic control unit of the vehicle using the vehicle electrical inspection equipment when the vehicle is offline for electrical inspection, so as to check whether the software and hardware information of the electronic control unit meets the definition.

[0072] Furthermore, in a possible implementation, the processing module is also used to store the sorted traceability information in a data format with a set number of bytes as a group based on the corresponding storage location reserved after the electronic control unit code, and generate a traceability file according to the correspondence between the storage address of the electronic control unit and the electronic control unit code, and transmit it to the vehicle electrical data server.

[0073] Furthermore, in a possible implementation manner, the processing module is also used to transmit the electronic control unit traceability information to the after-sales information quality COVRET system to maintain the vehicle electronic control unit.

[0074] Reference Figure 3 , Figure 3 The figure shows a schematic diagram of the traceability information flow of the electronic control unit provided by the present invention. Figure 3 As shown:

[0075] Create an ECU IEA CODE dictionary comparison table, and give a CODE definition for each ECU to trace the ECU's hardware number, software number, calibration number, configuration (Dote) number, and production batch information. It can be understood that managing all ECUs according to IEA CODE is equivalent to giving them a digital code of 2 bits.

[0076] Add the first digit before IEA CODE to distinguish the information type, and define the writing DID (data identifier) ​​and format of the basic information, VIN, and supplementary information required for each ECU to be traced. In this way, the same path and format are used for processing during the entire process of writing, exporting, reading, and storing the traceability information, so that the traceability information is one-to-one and in order.

[0077] It can be understood that the two-digit code of each ECU is preceded by a different code, which represents the information corresponding to this ECU. For example, adding 1 in front represents the hardware number of this ECU, adding 9 represents the software number, and so on.

[0078] After COCev reads the traceability information of the vehicle ECU, it automatically organizes it according to the 13-byte standard, stores the traceability information in the 13*N data format and uploads it to the CG system.

[0079] The basic data required for electrical initialization and electrical inspection of the vehicle all come from the CG system. The system acts as a server for the electrical data of the entire vehicle. During initialization, it provides the upstream vehicle definition as the input of the initialization device. After the electrical inspection, it receives the vehicle electrical data collected by the electrical inspection equipment (including the traceability information of each electronic control unit), stores it and uploads it to the vehicle after-sales information management system (COVRET).

[0080] It is understandable that when suppliers are developing ECUs, they need to synchronize the content, address, format, etc. of the traceability information with the manufacturer. After the parts are installed on the vehicle, at the terminal electrical inspection station, COC-EV will read the information of all ECUs in the vehicle and generate a traceability file according to the defined rules (digital coding and definition of ECU traceability information) according to the correspondence between the part storage address and the IEA CODE and pass it to the CG system. The CG system passes the traceability information to the after-sales information quality COVRET system for after-sales service. Refer to the following Figure 4 An electronic device 400 according to this embodiment of the present invention will be described. Figure 4 The electronic device 400 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0081] like Figure 4 As shown, the electronic device 400 is in the form of a general computing device. The components of the electronic device 400 may include but are not limited to: at least one processing unit 410, at least one storage unit 420, and a bus 430 connecting different system components (including the storage unit 420 and the processing unit 410).

[0082] The storage unit stores program codes, which can be executed by the processing unit 410, so that the processing unit 410 executes the steps according to various exemplary embodiments of the present invention described in the above “Embodiment Method” section of this specification.

[0083] The storage unit 420 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 421 and / or a cache memory unit 422 , and may further include a read-only memory unit (ROM) 423 .

[0084] The storage unit 420 may also include a program / utility 424 having a set (at least one) of program modules 425, such program modules 425 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0085] Bus 430 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0086] The electronic device 400 may also communicate with one or more external devices (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 400, and / or communicate with any device that enables the electronic device 400 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 450. Furthermore, the electronic device 400 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 460. As shown, the network adapter 460 communicates with other modules of the electronic device 400 via a bus 430. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 400, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0087] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0088] According to the solution of the present disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the above method of the present specification is stored. In some possible implementations, various aspects of the present invention can also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary implementations of the present invention described in the above "Exemplary Method" section of the present specification.

[0089] refer to Figure 5As shown, a program product 500 for implementing the above method according to an embodiment of the present invention is described, which can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

[0090] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0091] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0092] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0093] Program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0094] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to an exemplary embodiment of the present invention, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0095] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

[0096] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the process in the flowchart. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

Claims

1. A vehicle information management method, characterized in that: include: Digitally encode each electronic control unit of the vehicle, and define the traceability information required for each electronic control unit based on the digital code; The acquired traceability information of the electric control unit is segmented and sorted by bytes, and the segmented traceability information is uploaded to the vehicle electrical data server in a byte format to manage the vehicle information.

2. The method according to claim 1, characterized in that The digital coding of each electronic control unit of the vehicle includes: Create an electronic control unit IEA CODE dictionary comparison table; Based on the dictionary comparison table, each electronic control unit is digitally encoded to trace the attribute information of the electronic control unit.

3. The method according to claim 1, characterized in that Based on the digital coding, the traceability information required for each electronic control unit is defined, including: A different code is added to the first position of each electronic control unit code to differentiate the traceability information required for each electronic control unit, wherein the traceability information includes: hardware number, software number, serial number, vehicle body number, address, format, user identification number UIN, integrated circuit card identification code ICCID, unique identification code IMEI and international mobile user identity code IMSI.

4. The method according to claim 1, characterized in that: The acquired electronic control unit traceability information is segmented and sorted by bytes, including: At the terminal electrical inspection station, the vehicle electrical inspection equipment is used to read the traceability information of all the electronic control units of the vehicle; The read electronic control unit traceability information is automatically segmented and sorted according to a set number of bytes as a group.

5. The method according to claim 4, characterized in that Also includes: During the off-line electrical inspection of the vehicle, the vehicle electrical inspection equipment is used to communicate with each electronic control unit of the vehicle to check whether the software and hardware information of the electronic control unit meets the definition.

6. The method according to claim 1, characterized in that The segmented traceability information is uploaded to the vehicle electrical data server in byte format, including: Based on the corresponding storage location reserved behind the electronic control unit code, the sorted traceability information is stored in a data format with a set number of bytes as a group, and a traceability file is generated and transmitted to the vehicle electrical data server according to the correspondence between the storage address of the electronic control unit and the electronic control unit code.

7. The method according to claim 1, characterized in that After uploading the segmented traceability information to the vehicle electrical appliance data server in byte format, the following steps are included: The ECU traceability information is transmitted to the after-sales information quality COVRET system to maintain the vehicle ECU.

8. A vehicle information management device, characterized in that: include: A definition module, which is used to digitally encode each electronic control unit of the vehicle and define the traceability information required for each electronic control unit based on the digital encoding; The processing module is used to segment and organize the acquired traceability information of the electric control unit by bytes, and upload the segmented traceability information to the vehicle electrical data server in the byte format to manage the vehicle information.

9. An electronic device, characterized in that: The electronic device comprises: processor; A memory having computer-readable instructions stored thereon, wherein when the computer-readable instructions are executed by the processor, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer program instructions are stored therein, and when the computer program instructions are executed by a computer, the computer is caused to execute the method according to any one of claims 1 to 7.

Images