Ecu information processing method and device, server, and storage medium

Abstract

The application provides an ECU information processing method and device, a server and a storage medium. The method comprises the following steps: receiving an ECU static information file sent by an agent factory terminal; analyzing the ECU static information file to obtain an ECU static information list; generating a T-BOX device number corresponding to each ECU according to the ECU static information list and a preset device number generation rule; storing the ECU static information list in a database; creating a device number list according to the ECU static information list and the T-BOX device number corresponding to each ECU; and sending the device number list to a company cloud platform, so that the company cloud platform pushes the device number list to a company management terminal. The application saves the labor and time cost, improves the maintenance efficiency and improves the accuracy.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer information, and particularly relates to an ECU information processing method and device, a server and a storage medium. BACKGROUND

[0002] At present, an electronic control unit (ECU) is usually produced by an agent factory. When the ECU is shipped, the static information of the ECU needs to be maintained and managed. In addition, when the ECU is shipped, the number of a telematics box (T-BOX) device integrated with the ECU needs to be calculated according to the static information of the ECU, and registration is completed according to the number of the T-BOX device.

[0003] In the prior art, the static information of the ECU is usually sent by an agent factory user to a company management terminal through an email for unified maintenance and management. In addition, the number of the T-BOX device is calculated manually.

[0004] However, the present application finds that the prior art at least has the following technical problems: the existing maintenance and management of the static information of the ECU through the email waste human and time costs, and the maintenance efficiency is low; and the calculation of the number of the T-BOX device is completed manually, and the efficiency is poor. SUMMARY

[0005] The present application provides an ECU information processing method, device, server and storage medium to overcome the problem of low work efficiency when the static information of the ECU is maintained and managed and the number of the T-BOX device is calculated.

[0006] In a first aspect, the present application provides an ECU information processing method, comprising: receiving an ECU static information file sent by an agent factory terminal, wherein the ECU static information file includes the static information of each ECU, and wherein the ECU static information file of the agent factory terminal is imported by an agent factory personnel through an ECU static information file import operation;

[0007] analyzing the ECU static information file to obtain an ECU static information list;

[0008] generating a telematics box (T-BOX) device number corresponding to each ECU according to the ECU static information list and a preset device number generation rule;

[0009] storing the ECU static information list to a database, wherein the database is used for maintaining and managing each ECU static information;

[0010] According to the ECU static information list and the T-BOX device number corresponding to each ECU, a device number list is created;

[0011] The device number list is sent to a company cloud platform, so that the company cloud platform pushes the device number list to a company management terminal.

[0012] In a possible implementation, the static information of each ECU in the ECU static information list includes a controller label and a product model; and the preset device number generation rule includes a T-BOX device identification, a first mapping relationship between a controller item code and a controller item code code, and a second mapping relationship between a hardware version number and a hardware version number code.

[0013] According to the ECU static information list and the preset device number generation rule, a T-BOX device number corresponding to each ECU is generated, including:

[0014] According to the product model of any target ECU, a controller item code and a hardware version number corresponding to the target ECU are obtained;

[0015] According to the controller item code corresponding to the target ECU, the first mapping relationship is queried to obtain a controller item code code corresponding to the target ECU;

[0016] According to the hardware version number corresponding to the target ECU, the second mapping relationship is queried to obtain a hardware version number code corresponding to the target ECU;

[0017] According to the T-BOX device identification, the controller item code code, the hardware version number code, and the controller label corresponding to the target ECU, a T-BOX device number corresponding to the target ECU is generated.

[0018] In a possible implementation, according to the T-BOX device identification, the controller item code code, the hardware version number code, and the controller label corresponding to the target ECU, a T-BOX device number corresponding to the target ECU is generated, including:

[0019] The T-BOX device identification is determined as the first byte of the T-BOX device number corresponding to the target ECU;

[0020] The controller item code code corresponding to the target ECU is determined as the second byte and the third byte of the T-BOX device number corresponding to the target ECU;

[0021] The hardware version number code corresponding to the target ECU is determined as the fourth byte of the T-BOX device number corresponding to the target ECU;

[0022] The last six characters of the controller tag corresponding to the target ECU are determined as the fifth byte to the tenth byte of the T-BOX device number corresponding to the target ECU.

[0023] In a possible implementation, the ECU static information file is parsed to obtain an ECU static information list, including:

[0024] Each piece of ECU static information in the ECU static information file is acquired, where the ECU static information includes at least one of the following information data: a customer purchase order number, a customer material, a shipment date, a controller tag, a product model, and a box number.

[0025] The ECU static information is stored in a preset list to obtain the ECU static information list.

[0026] Correspondingly, the ECU static information list is stored in a database, where the database is used to maintain and manage the ECU static information, including:

[0027] The ECU static information list is uploaded to a company cloud platform for display, so as to maintain and manage the ECU static information.

[0028] In a possible implementation, after the ECU static information file is parsed to obtain the ECU static information list, the method further includes:

[0029] If the ECU static information file fails to be parsed successfully, the ECU static information file is received again.

[0030] In a possible implementation, after the ECU static information list and the preset device number generation rule are used to generate the T-BOX device number corresponding to each ECU, the method further includes:

[0031] If the T-BOX device number corresponding to each ECU fails to be generated, the ECU static information file is received again.

[0032] In a possible implementation, after the ECU static information list and the preset device number generation rule are used to generate the T-BOX device number corresponding to each ECU, the method further includes:

[0033] The ECU static information file is backed up.

[0034] In a possible implementation, in response to a management operation on the preset device number generation rule, the preset device number generation rule is updated.

[0035] In a second aspect, the application provides an ECU information processing device, including:

[0036] The first receiving module is configured to receive an ECU static information file sent by the agent factory terminal, wherein the ECU static information file comprises static information of each ECU, and the ECU static information file of the agent factory terminal is imported by an agent factory personnel through an ECU static information file import operation;

[0037] The parsing module is configured to parse the ECU static information file to obtain an ECU static information list;

[0038] The generating module is configured to generate a T-BOX device number corresponding to each ECU according to the ECU static information list and a preset device number generation rule;

[0039] The storage module is configured to store the ECU static information list in a database, wherein the database is configured to maintain and manage each ECU static information;

[0040] The creating module is configured to create a device number list according to the ECU static information list and the T-BOX device number corresponding to each ECU;

[0041] The sending module is configured to send the device number list to a company cloud platform, so that the company cloud platform pushes the device number list to a company management terminal.

[0042] In a third aspect, the present application provides a server, comprising at least one processor and a memory;

[0043] The memory stores computer execution instructions;

[0044] The at least one processor executes the computer execution instructions stored in the memory, so that the at least one processor executes the ECU information processing method of the first aspect and various possible designs of the first aspect.

[0045] In a fourth aspect, the present application provides a computer storage medium, wherein the computer storage medium stores computer execution instructions, and when a processor executes the computer execution instructions, the ECU information processing method of the first aspect and various possible designs of the first aspect is realized.

[0046] In a fifth aspect, the present application provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the system clock synchronization method of the first aspect and various possible designs of the first aspect is realized.

[0047] The ECU information processing method, device, server and storage medium provided by the application, through the proxy factory platform, the ECU static information file imported by the proxy factory terminal is parsed, the ECU static information list is obtained, the ECU static information list is stored to the database, and each ECU static information is maintained and managed, the direct maintenance and management of the ECU static information are realized; according to the ECU static information list and the preset equipment number generation rule, the T-BOX equipment number is generated, the equipment number list is created according to the ECU static information list and the T-BOX equipment number corresponding to each ECU, and the equipment number list is sent to the company cloud platform, so that the company cloud platform pushes the equipment number list to the management terminal of the company personnel, so that the company cloud platform registers the T-BOX equipment number, saves the labor and time cost, and improves the maintenance efficiency. BRIEF DESCRIPTION OF DRAWINGS

[0048] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0049] Figure 1 The system architecture diagram of the ECU information processing method provided by the embodiment of the present application;

[0050] Figure 2 The flowchart of the ECU information processing method provided by the embodiment of the present application;

[0051] Figure 3 The flowchart of the ECU information processing method provided by another embodiment of the present application;

[0052] Figure 4 The structure diagram of the ECU information processing device provided by the embodiment of the present application;

[0053] Figure 5 The hardware structure diagram of the server provided by the embodiment of the present application. DETAILED DESCRIPTION

[0054] In order to make the purpose, technical scheme and advantages of the embodiments of the present application more clear, the technical scheme in the embodiments of the present application will be described clearly and completely in the following with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0055] First, the terms involved in the present application are explained:

[0056] 1、ECU: Electronic Control Unit, also known as "driving computer" and "on-board computer", which is a microcomputer controller specially used for automobiles. It is composed of microprocessors, memories, input / output interfaces, analog-to-digital converters, and large-scale integrated circuits such as shaping and driving.

[0057] 2、T-BOX: Integrated telematics box, used to transmit information collected by various sensors to provide data support, and for ECU data acquisition and data return.

[0058] In view of the problems of waste of manpower and time cost, low maintenance efficiency of the ECU static information maintenance method in the prior art, and the problems that the calculation and registration process of T-BOX device number are completed by manual operation, the accuracy cannot be guaranteed, the present application embodiment proposes the following technical concept:

[0059] By designing a proxy factory management platform, the ECU static information file is imported into the proxy factory management platform by the proxy factory personnel when shipping, and the ECU static information list is obtained by parsing, which is used for online maintenance and management of ECU static information. The proxy factory management platform generates T-BOX device number according to the preset device number generation rule, so as to register T-BOX device number on the company cloud platform. Time and manpower and time cost are saved, and accuracy is guaranteed.

[0060] Figure 1 The system architecture diagram of the ECU information processing method provided by the present application embodiment is shown in the figure. As shown in the figure, it includes: a proxy factory terminal 101, a proxy factory platform 102, a company cloud platform 103 and a company management terminal 104.

[0061] Among them, the proxy factory terminal 101 is maintained by the proxy factory personnel. The proxy factory personnel can upload the corresponding information or data to the proxy factory platform 102 by performing maintenance operation on the proxy factory terminal.

[0062] The proxy factory platform 102 is used for maintaining and processing the information or data uploaded by the proxy factory terminal 101, and sending the maintenance processing result to the company cloud platform 103.

[0063] Among them, the company cloud platform 103 is maintained by the company personnel, which is used for interaction with the proxy factory platform 102, and sends the maintenance processing result to the company management terminal 104.

[0064] The company management terminal 104 is used for receiving the information or data sent by the company cloud platform 103, and uniformly maintaining or managing the received information or data.

[0065] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0066] Figure 2 This is a flow chart of the ECU information processing method provided in one embodiment of the present application. The execution subject of this embodiment can be Figure 1 The proxy factory platform 102 in the embodiment shown can also be any other type of server or service platform, and this embodiment does not impose any special restrictions on this. Figure 2 As shown, the method includes:

[0067] S201: Receive an ECU static information file sent by an agent factory terminal, wherein the ECU static information file includes static information of each ECU, and the ECU static information file of the agent factory terminal is imported by the agent factory personnel through the ECU static information file import operation.

[0068] In this embodiment, the ECU static information may include one or more of: shipping date, customer purchase order number, customer material, box number, controller label, product model, and the like.

[0069] Specifically, the agent factory personnel scan the production barcode of the ECU through the agent factory terminal, count the static information of the ECU into an EXCEL table, obtain a static information file, and import the static information file into the agent factory platform at the agent factory terminal.

[0070] S202: Parse the ECU static information file to obtain an ECU static information list.

[0071] Specifically, each piece of ECU static information in the ECU static information file is obtained, wherein the ECU static information includes at least one of the following information data: customer purchase order number, customer material, shipping date, controller label, product model and box number; the ECU static information is stored in a preset list to obtain an ECU static information list.

[0072] For example, the ECU static information list is shown in the following table (Table 1).

[0073] Table 1 ECU static information list

[0074]

[0075] In one embodiment of the present application, after S202, the method further includes:

[0076] If the ECU static information file is not parsed successfully, S201 is re-executed, and the ECU static information file is received again.

[0077] S203: generating a T-BOX device number corresponding to each ECU according to the ECU static information list and a preset device number generation rule.

[0078] The ECU static information of each ECU in the ECU static information list includes a controller label and a product model; and the preset device number generation rule includes a T-BOX device identifier, a first mapping relationship between a controller item code and a controller item code code, and a second mapping relationship between a hardware version number and a hardware version number code.

[0079] In an embodiment of the present application, if the T-BOX device number is generated successfully, S204 is executed. If the T-BOX device number generation fails, S201 is re-executed, and the ECU static information file is received again.

[0080] The preset device number generation rule is updated in response to a management operation on the preset device number generation rule.

[0081] Specifically, the preset device number generation rule can modify the first mapping relationship and the second mapping relationship through a device number generation rule update service function in the agent factory platform.

[0082] In an embodiment of the present application, after S203, the following is further included:

[0083] The ECU static information file is backed up.

[0084] Specifically, the ECU static information file is stored in a database and backed up to a disk.

[0085] S204: storing the ECU static information list in a database, wherein the database is used to maintain and manage each ECU static information.

[0086] Specifically, the ECU static information list is stored in a database and saved to a disk.

[0087] Specifically, the ECU static information list is uploaded to the agent factory platform for display, so as to maintain and manage each ECU static information.

[0088] The ECU static information is displayed in an ECU static information management interface of the agent factory platform.

[0089] In the embodiment, the maintenance and management operation on the ECU static information can include operations of querying, adding, deleting, and modifying the ECU static information.

[0090] S205: creating a device number list according to the ECU static information list and the T-BOX device number corresponding to each ECU.

[0091] Specifically, the controller label in the static information of each ECU in the ECU static information list is obtained, a list is generated by establishing the correspondence between the controller label and the T-BOX device number, and the correspondence between each controller label and the T-BOX device number and the T-BOX related information is filled into the T-BOX device number list to obtain the device number list.

[0092] The T-BOX related information includes at least one of the following information: customer type, T-BOX type, applicant ID, applicant name, and name of the person who receives the T-BOX.

[0093] Exemplarily, the T-BOX device number list is shown in the following table (Table 2).

[0094] Table 2 T-BOX device number list

[0095]

[0096] In an embodiment of the present application, after S205, it further includes:

[0097] Send an email to the company personnel management terminal that the ECU static information file import is successful.

[0098] S206: send the device number list to the company cloud platform, so that the company cloud platform pushes the device number list to the company management terminal.

[0099] Specifically, the device number list is sent to the company cloud platform, so that the company cloud platform registers the T-BOX device number according to the device number list, realizes the automatic registration of the T-BOX device number, and improves the registration efficiency.

[0100] In an embodiment of the present application, after S206, it further includes:

[0101] Send an email to the agent factory terminal and the company management terminal that the device number list is sent successfully.

[0102] To sum up, the ECU information processing method provided in the embodiment can analyze the ECU static information file imported by the agent factory terminal through the agent factory platform, obtain an ECU static information list, and store the ECU static information list in a database, so as to maintain and manage each ECU static information, and realize direct maintenance and management of the ECU static information. According to the ECU static information list and a preset device number generation rule, a T-BOX device number is generated, a device number list is created according to the ECU static information list and the T-BOX device number corresponding to each ECU, and the device number list is sent to a company cloud platform, so that the company cloud platform pushes the device number list to a management terminal of a company staff, and the company cloud platform registers the T-BOX device number, thereby saving the labor and time cost, improving the maintenance efficiency, and improving the accuracy.

[0103] Figure 3 The ECU information processing method flowchart provided in another embodiment of the application is shown in the figure. In this embodiment, the ECU information processing method is based on the ECU information processing method of the embodiment Figure 2 Based on the embodiment, the T-BOX device number corresponding to each ECU is generated according to the ECU static information list and a preset device number generation rule, specifically including:

[0104] S301: According to the product model of any target ECU, the controller item code and the hardware version number corresponding to the target ECU are obtained.

[0105] Specifically, the characters of the product model of the target ECU except the last four characters are determined as the controller item code, and the last three characters of the product model of the target ECU are determined as the hardware version number.

[0106] For example, the product model of the target ECU is “WISE13M-02A02_C01”, the controller item code of the target ECU is “WISE13M-02A02”, and the hardware version number is “C01”.

[0107] S302: According to the controller item code corresponding to the target ECU, the first mapping relationship is queried to obtain the controller item code code corresponding to the target ECU.

[0108] In this embodiment, the first mapping relationship can be shown in the following table (Table 3).

[0109] Table 3 First mapping relationship

[0110]

[0111]

[0112] S303: According to the hardware version number corresponding to the target ECU, query the second mapping relationship to obtain the hardware version number code corresponding to the target ECU.

[0113] In this embodiment, the second mapping relationship can be as shown in the following table (Table 4).

[0114] Table 4 Second mapping relationship

[0115]

[0116] S304: According to the T-BOX device identifier corresponding to the target ECU, the controller item code, the hardware version number, and the controller label corresponding to the target ECU, generate the T-BOX device number corresponding to the target ECU.

[0117] In this embodiment, S304 specifically includes S3041-S3044, as follows:

[0118] S3041: Determine the T-BOX device identifier as the first byte of the T-BOX device number corresponding to the target ECU.

[0119] S3042: Determine the controller item code corresponding to the target ECU as the second byte and the third byte of the T-BOX device number corresponding to the target ECU.

[0120] S3043: Determine the hardware version number code corresponding to the target ECU as the fourth byte of the T-BOX device number corresponding to the target ECU.

[0121] S3044: Determine the last six characters of the controller label corresponding to the target ECU as the fifth byte to the tenth byte of the T-BOX device number corresponding to the target ECU.

[0122] Exemplarily, the product model of the target ECU is "WISE13M-02A02_C01", and the controller label is "1008845041^290D211114012345".

[0123] The first byte of the T-BOX device number is the T-BOX device identifier, which is determined as "X";

[0124] The controller item code is "WISE13M-02A02", and the corresponding code (i.e., the second byte and the third byte) of the controller item code is "06" by querying the first mapping relationship;

[0125] The hardware version number is "C01", and the corresponding code (i.e., the fourth byte) of the hardware version number is "1" by querying the second mapping relationship;

[0126] If the last six characters of the controller label are "012345", the fifth to tenth bytes are encoded as "012345";

[0127] Finally, the T-BOX device number corresponding to the target ECU is "X061012345".

[0128] In summary, the ECU information processing method provided in this embodiment obtains the controller item code and the hardware version number corresponding to the target ECU through the product model of the target ECU, obtains the second to fourth bytes of the T-BOX device number corresponding to the controller item code and the hardware version number corresponding to the target ECU through the first mapping relationship and the second mapping relationship, determines the first byte of the T-BOX device number corresponding to the target ECU through the T-BOX device identification, and finally determines the fifth byte to the tenth byte of the T-BOX device number corresponding to the target ECU through the last six characters of the controller label of the target ECU, thereby obtaining the T-BOX device number corresponding to the target ECU, improving the generation efficiency of the T-BOX device number, and ensuring the accuracy.

[0129] Figure 4 The ECU information processing device provided in this embodiment is shown in the structure diagram. Figure 4 As shown in the structure diagram, the ECU information processing device includes a first receiving module 401, an analysis module 402, a generation module 403, a storage module 404, a creation module 405, and a sending module 406.

[0130] The first receiving module 401 is configured to receive the ECU static information file sent by the agent factory terminal, wherein the ECU static information file includes the static information of each ECU, and the ECU static information file of the agent factory terminal is imported by the agent factory personnel through the ECU static information file import operation.

[0131] The analysis module 402 is configured to analyze the ECU static information file to obtain an ECU static information list.

[0132] The generation module 403 is configured to generate the T-BOX device number corresponding to each ECU according to the ECU static information list and a preset device number generation rule.

[0133] The storage module 404 is configured to store the ECU static information list to a database, wherein the database is configured to maintain and manage each ECU static information.

[0134] The creation module 405 is configured to create a device number list according to the ECU static information list and the T-BOX device number corresponding to each ECU.

[0135] The sending module 406 is configured to send the device number list to the company cloud platform, so that the company cloud platform pushes the device number list to the company management terminal.

[0136] In a possible implementation, the generating module 403 is specifically configured to: obtain the controller project code and the hardware version number corresponding to the target ECU according to the product model of the target ECU; query the first mapping relationship according to the controller project code corresponding to the target ECU to obtain the controller project code corresponding to the target ECU; query the second mapping relationship according to the hardware version number corresponding to the target ECU to obtain the hardware version number code corresponding to the target ECU; and generate the T-BOX device number corresponding to the target ECU according to the T-BOX device identifier corresponding to the target ECU, the controller project code, the hardware version number code, and the controller label corresponding to the target ECU.

[0137] In a possible implementation, the generating module 403 is further configured to: determine the T-BOX device identifier as the first byte of the T-BOX device number corresponding to the target ECU; determine the controller project code corresponding to the target ECU as the second byte and the third byte of the T-BOX device number corresponding to the target ECU; determine the hardware version number code corresponding to the target ECU as the fourth byte of the T-BOX device number corresponding to the target ECU; and determine the last six characters of the controller label corresponding to the target ECU as the fifth byte to the tenth byte of the T-BOX device number corresponding to the target ECU.

[0138] In a possible implementation, the analyzing module 402 is further configured to: obtain each piece of ECU static information in the ECU static information file, wherein the ECU static information includes at least one of the following information data: a customer purchase order number, a customer material, a shipment date, a controller label, a product model, and a box number; store the ECU static information into a preset list to obtain an ECU static information list; and correspondingly, store the ECU static information list into a database, wherein the database is used to maintain and manage the ECU static information, including: uploading the ECU static information list to the company cloud platform for display, so as to maintain and manage the ECU static information.

[0139] In one or more embodiments of the present application, continuing to refer to Figure 4 , the apparatus further comprises:

[0140] The second receiving module 407 is configured to re-receive the ECU static information file if the ECU static information file is not successfully analyzed.

[0141] In one or more embodiments of the present application, continuing to refer to Figure 4 , the apparatus further comprises:

[0142] The third receiving module 408 is configured to re-receive the ECU static information file if the T-BOX device number corresponding to each ECU fails to be generated.

[0143] In one or more embodiments of the present application, continuing to refer to Figure 4 , the apparatus further comprises:

[0144] The backup module 409 is configured to backup the ECU static information file.

[0145] In one or more embodiments of the present application, continuing to refer to Figure 4 , the apparatus further comprises:

[0146] The updating module 410 is configured to update the preset device number generation rule in response to a management operation on the preset device number generation rule.

[0147] The apparatus provided in the embodiments can be used to execute the technical solutions of the above method embodiments, and has similar implementation principles and technical effects, which will not be repeated here.

[0148] Figure 5 The hardware structure of the server provided in the embodiments of the present application is shown in FIG. 5. As shown in FIG. 5, the server 50 of the embodiments of the present application comprises a processor 501 and a memory 502, wherein Figure 5

[0149] The memory 502 is configured to store computer execution instructions.

[0150] The processor 501 is configured to execute the computer execution instructions stored in the memory to implement each step performed by the server in the above embodiments. For details, please refer to the related description in the above method embodiments.

[0151] Optionally, the memory 502 can be independent or integrated with the processor 501.

[0152] When the memory 502 is independently arranged, the server further comprises a bus 503 for connecting the memory 502 and the processor 501.

[0153] The embodiments of the present application further provide a computer storage medium, and the computer storage medium stores computer execution instructions. When the processor executes the computer execution instructions, the ECU information processing method described above is implemented.

[0154] The embodiments of the present application further provide a computer program product comprising a computer program. When the computer program is executed by the processor, the ECU information processing method described above is implemented. The embodiments of the present application further provide a computer program product comprising a computer program. When the computer program is executed by the processor, the ECU information processing method described above is implemented.​

[0155] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other manners. For example, the embodiments of the device described above are merely schematic. For example, the division of the modules is only a logical function division. There can be another division manner for the actual implementation. For example, a plurality of modules or a component can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections can be indirect couplings or communication connections through some interfaces, devices or modules, and can be in electrical, mechanical or other forms.

[0156] The modules illustrated as separated components can or can not be physically separated, and the components illustrated as modules can or can not be physical units, i.e., can be located in one place, or can be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to implement the embodiments of the present application.

[0157] In addition, each functional module in each embodiment of the present application can be integrated in one processing unit, or each module can be physically present alone, or two or more modules can be integrated in one unit. The unit of the above modules can be realized in the form of hardware, or in the form of hardware plus software function unit.

[0158] The integrated module realized in the form of software function module can be stored in a computer readable storage medium. The software function module stored in the storage medium includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute part of the steps of the method of each embodiment of the present application.

[0159] It should be understood that the processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), etc. The general-purpose processor can be a microprocessor, or the processor can also be any conventional processor and the like. The steps of the method disclosed in the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in the processor for execution.

[0160] The memory can include a high-speed RAM memory, and can also include a non-volatile storage NVM, for example at least one disk memory, and can also be a U disk, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.

[0161] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, the bus in the drawings of the present application does not limit to only one bus or one type of bus.

[0162] The storage medium described above can be realized by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk. The storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0163] An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and can write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an Application Specific Integrated Circuit (ASIC). Of course, the processor and the storage medium can also exist as discrete components in an electronic device or a host device.

[0164] Those of ordinary skill in the art can understand that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction-related hardware. The foregoing program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the foregoing storage medium includes ROM, RAM, magnetic disk or optical disk and various storage media that can store program codes.

[0165] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. An ECU information processing method characterized by, Applied to an agent factory platform, comprising: receiving an ECU static information file sent by an agent factory terminal, wherein the ECU static information file includes static information of each ECU, and the ECU static information file of the agent factory terminal is imported by an agent factory personnel through an ECU static information file import operation; parsing the ECU static information file to obtain an ECU static information list; generating a T-BOX device number corresponding to each ECU according to the ECU static information list and a preset device number generation rule; storing the ECU static information list to a database, wherein the database is used to maintain and manage each ECU static information; creating a device number list according to the ECU static information list and the T-BOX device number corresponding to each ECU; sending the device number list to a company cloud platform, so that the company cloud platform pushes the device number list to a company management terminal.

2. The method of claim 1, wherein, The static information of each ECU in the ECU static information list includes a controller label and a product model; the preset device number generation rule includes a T-BOX device identification, a first mapping relationship between a controller item code and a controller item code code, and a second mapping relationship between a hardware version number and a hardware version number code; The generation of the T-BOX device number corresponding to each ECU according to the ECU static information list and the preset device number generation rule comprises: obtaining a controller item code and a hardware version number corresponding to any target ECU according to the product model of the target ECU; querying the first mapping relationship according to the controller item code corresponding to the target ECU to obtain a controller item code code corresponding to the target ECU; querying the second mapping relationship according to the hardware version number corresponding to the target ECU to obtain a hardware version number code corresponding to the target ECU; generating the T-BOX device number corresponding to the target ECU according to the T-BOX device identification corresponding to the target ECU, the controller item code code, the hardware version number code, and the controller label corresponding to the target ECU.

3. The method of claim 2, wherein, The generation of the T-BOX device number corresponding to the target ECU according to the T-BOX device identification corresponding to the target ECU, the controller item code code, the hardware version number code, and the controller label corresponding to the target ECU comprises: determining the T-BOX device identification as the first byte of the T-BOX device number corresponding to the target ECU; determining the controller item code code corresponding to the target ECU as the second byte and the third byte of the T-BOX device number corresponding to the target ECU; determining the hardware version number code corresponding to the target ECU as the fourth byte of the T-BOX device number corresponding to the target ECU; determining the last six characters of the controller label corresponding to the target ECU as the fifth byte to the tenth byte of the T-BOX device number corresponding to the target ECU.

4. The method of claim 1, wherein, The ECU static information file is parsed to obtain an ECU static information list, including: Obtaining each ECU static information in the ECU static information file, wherein the ECU static information includes at least one of the following information data: customer purchase order number, customer material, shipment date, controller label, product model and box number; The ECU static information is stored in a preset list to obtain an ECU static information list; Correspondingly, the ECU static information list is stored in a database, wherein the database is used to maintain and manage ECU static information, including: The ECU static information list is uploaded to the company cloud platform for display to maintain and manage ECU static information.

5. The method according to any one of claims 1 to 4, characterized in that, After the ECU static information file is parsed to obtain the ECU static information list, it further includes: If the ECU static information file is not parsed successfully, the ECU static information file is received again.

6. The method according to any one of claims 1 to 4, characterized in that, After generating the T-BOX device number corresponding to each ECU according to the ECU static information list and the preset device number generation rule, it further includes: If the T-BOX device number corresponding to each ECU fails to be generated, the ECU static information file is received again.

7. The method according to any one of claims 1 to 4, characterized in that, After generating the T-BOX device number corresponding to each ECU according to the ECU static information list and the preset device number generation rule, it further includes: Backup the ECU static information file.

8. The method according to any one of claims 1 to 4, characterized in that, Further including: In response to the management operation of the preset device number generation rule, the preset device number generation rule is updated.

9. An ECU information processing apparatus characterized by comprising: Including: A first receiving module is configured to receive an ECU static information file sent by a proxy factory terminal, wherein the ECU static information file includes static information of each ECU, and the ECU static information file of the proxy factory terminal is imported by a proxy factory personnel through an ECU static information file import operation; An analysis module is configured to parse the ECU static information file to obtain an ECU static information list; A generation module is configured to generate a T-BOX device number corresponding to each ECU according to the ECU static information list and a preset device number generation rule; A storage module is configured to store the ECU static information list in a database, wherein the database is used to maintain and manage each ECU static information; A creation module is configured to create a device number list according to the ECU static information list and the T-BOX device number corresponding to each ECU; A sending module is configured to send the device number list to a company cloud platform, so that the company cloud platform pushes the device number list to a company management terminal.

10. A server, characterized by Including: At least one processor and memory; The memory stores computer execution instructions; The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the ECU information processing method according to any one of claims 1 to 8.

11. A computer storage medium, characterized in that The computer storage medium stores computer-executable instructions, and when a processor executes the computer-executable instructions, the ECU information processing method according to any one of claims 1 to 8 is implemented.

Images