A vehicle end error code management method, system, device and storage medium

Abstract

The application relates to the technical field of vehicle-mounted computers, and provides a vehicle-end error code management method, a system, equipment and a storage medium, the method comprises the following steps: acquiring a vehicle terminal and a server end; the server end receives release information of a first application software, the release information comprising first software feature information and first error code information; the server end selects a registration strategy based on the first software feature information, and registers the release information to a registration information table; the vehicle terminal sends second software feature information of a second application software to the server end based on a starting instruction of the second application software; the server end searches the registration information table based on the second software feature information, determines second error code information, and sends the second error code information to the vehicle terminal; and the vehicle terminal receives the second error code information and temporarily stores the second error code information in a temporary storage space. The application can effectively avoid the confusion of error codes of vehicle-mounted application software, improve the positioning efficiency of running faults of the vehicle-mounted application software, and greatly reduce the difficulty of vehicle maintenance in the later period.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of vehicle-mounted computers, in particular to a vehicle-side error code management method, system, device and storage medium. BACKGROUND

[0002] When running errors occur in many software running on vehicles, the error types or error causes and other information are fed back in the form of error codes, which is the main way to understand software running errors. Error codes are widely used in vehicles, for example, instruments, central controls, head-up displays, streaming media audition and other software development and design related to user experience.

[0003] In the prior art, error codes are used to represent a specific running error, which has the following disadvantages: there is no unified standard for error codes under different software development frameworks, error code definitions vary between different versions of the same system or software, error codes of different software are repeated and cannot be updated and synchronized, which easily leads to confusion of error codes of vehicle application software, increases the difficulty of fault positioning through error codes and causes difficulty in vehicle maintenance. SUMMARY

[0004] In view of the above-mentioned confusion of error codes of vehicle application software in the prior art, the difficulty of fault positioning through error codes and the difficulty in vehicle maintenance, the present application provides a vehicle-side error code management method, system, device and storage medium to solve the above technical problems.

[0005] In a first aspect, the present application provides a vehicle-side error code management method, comprising:

[0006] obtaining a vehicle terminal and a server side, the server side being provided with a registration information table;

[0007] the server side receives release information of a first application software, the release information including first software feature information and first error code information;

[0008] the server side selects a registration strategy based on the first software feature information, and registers the release information to the registration information table according to the registration strategy;

[0009] the vehicle terminal sends second software feature information of a second application software to the server side based on a start instruction of the second application software;

[0010] the server side searches the registration information table based on the second software feature information to determine second error code information matched with the second software feature information, and sends the second error code information to the vehicle terminal;

[0011] The vehicle terminal receives the second error code information sent by the server end and temporarily stores it in a preset temporary storage space.

[0012] Further, the registration information table includes a plurality of corresponding relationships between historical software feature information and historical error codes, and the server end selects a registration strategy based on the first software feature information and registers the release information to the registration information table according to the registration strategy.

[0013] According to the first software feature information, the historical software feature information in the registration information table is matched, and a registration strategy is selected according to the matching result;

[0014] If any of the historical software feature information in the registration information table is inconsistent with the first software feature information, the first strategy is determined as the registration strategy;

[0015] If the historical software feature information in the registration information table is consistent with the first software feature information, the second strategy is determined as the registration strategy.

[0016] Further, the first strategy includes:

[0017] The corresponding relationship between the first software feature information and the first error code information is added to the registration information table, wherein the first software feature information is taken as new historical software feature information, and the first error code information is taken as new historical error code information.

[0018] Further, the second strategy includes:

[0019] An artificial judgment request is issued to determine whether to overwrite the registration information table;

[0020] Based on the feedback result of the artificial judgment request, if the feedback result includes confirmation of overwriting, the corresponding relationship between the first software feature information and the first error code information is overwritten and written to the registration information table, otherwise the second strategy is ended.

[0021] Further, the server end searches the registration information table based on the second software feature information to determine the second error code information matched with the second software feature information.

[0022] The historical software feature information includes historical software name and historical software version number, and the second software feature information includes second software name and second software version number.

[0023] The historical software feature information is searched in the registration information table.

[0024] If the search result includes the target software feature information, the target software feature information includes the second software name and the second software version number, and the historical error code information corresponding to the target software feature information is taken as the second error code information.

[0025] If any of the historical software feature information includes at most one of the second software name and the second software version number, the current method step is ended, and the second software name and the second software version number are recorded.

[0026] Further, after the vehicle terminal receives the second error code information sent by the server end and temporarily stores it in a preset temporary storage space, the method further includes:

[0027] The vehicle terminal matches the temporary storage space based on the error code fed back by the second application software, and obtains an error code matching result.

[0028] If the error code matching result includes the error code, the error code information corresponding to the error code is displayed, otherwise, error information is sent to the server end.

[0029] In a second aspect, the present application provides a vehicle machine error code management system, comprising a vehicle terminal and a server end, wherein the vehicle terminal is used for:

[0030] receiving the release information of the first application software, the release information including the first software feature information and the first error code information;

[0031] selecting a registration strategy based on the first software feature information, and registering the release information to the registration information table according to the registration strategy;

[0032] based on the second software feature information sent by the vehicle terminal, searching the registration information table to determine the second error code information matched with the second software feature information, and sending it to the vehicle terminal.

[0033] Further, the vehicle terminal is used for sending the second software feature information of the second application software to the server end based on the start instruction of the second application software, and receiving the second error code information sent by the server end and temporarily storing it in a preset temporary storage space.

[0034] In a third aspect, the present application provides an electronic device, comprising:

[0035] one or more processors;

[0036] a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, the electronic device implements one of the vehicle end error code management methods in the above-mentioned scheme.

[0037] In a fourth aspect, the present application provides a computer readable storage medium, having stored thereon a computer program, which, when executed by a processor of a computer, causes the computer to perform the vehicle terminal error code management method in any of the above solutions.

[0038] The vehicle terminal error code management method, system, device and storage medium as described above, firstly registers the release information of the first application software to the server end, and stores the different error code information and the software feature information of the application software applicable thereto in the registration information table of the server end in correspondence with each other, and subsequently based on the second application software actually running on the vehicle terminal, the second error code information applicable to the second application software is called and temporarily stored in the vehicle terminal for use when the second application software runs, solving the problems that the error code in the prior art has no unified benchmark under different software development frameworks, and the error code definition between different versions of the same system or software is changing, and effectively avoiding the confusion of the error code of the vehicle-mounted application software, improving the running fault positioning efficiency of the vehicle-mounted application software, and greatly reducing the difficulty of vehicle maintenance in the later period.

[0039] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and are not limiting to the present application. BRIEF DESCRIPTION OF DRAWINGS

[0040] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application. It is clear that the accompanying drawings in the following description are only some embodiments of the present application, and those skilled in the art can obtain other drawings according to these drawings without creative labor. In the drawings:

[0041] Figure 1 is a flow chart of the vehicle terminal error code management method according to an exemplary embodiment of the present application;

[0042] Figure 2 is a structural schematic diagram of the vehicle terminal error code management system according to an exemplary embodiment of the present application;

[0043] Figure 3 shows a structural schematic diagram of a computer system of an electronic device suitable for implementing embodiments of the present application. DETAILED DESCRIPTION

[0044] The present application will be described with reference to the attached drawings and preferred embodiments, which are given by way of example and are not meant to limit the present application in any way. Other advantages and novel features of the present application will become apparent from the following detailed description, when considered in conjunction with the drawings. The application can be practiced by other than the described embodiments, which are presented for purposes of illustration and not of limitation and the present application is limited only by the claims.

[0045] It is also to be understood that the following description is only illustrative of the present application and is not intended to limit the present application in any way.

[0046] In the following description, numerous specific details are discussed in order to provide a thorough understanding of the embodiments of the present application. However, the embodiments of the present application can be practiced without these specific details. In other instances, well-known structures and devices are not described in detail in order not to obscure the understanding of this description.

[0047] In one embodiment, the present application exemplarily provides a vehicle terminal error code management method, as shown in Figure 1 Figure 1 is a flow chart of the vehicle terminal error code management method according to an exemplary embodiment of the present application, which comprises at least the following steps:

[0048] In step S110, a vehicle terminal and a server terminal are obtained, and the server terminal is provided with a registration information table.

[0049] In step S120, the server terminal receives release information of a first application software, and the release information comprises first software feature information and first error code information.

[0050] In step S130, the server terminal selects a registration strategy based on the first software feature information, and registers the release information to the registration information table according to the registration strategy.

[0051] In step S140, the vehicle terminal sends second software feature information of a second application software to the server terminal based on a start instruction of the second application software.

[0052] In step S150, the server terminal searches the registration information table based on the second software feature information, to determine second error code information matched with the second software feature information, and sends the second error code information to the vehicle terminal.

[0053] ​Step S160, the vehicle terminal receives the second error code information sent by the server and stores it in the preset temporary storage space.

[0054] For step S120, it is worth noting that the release information includes but is not limited to the information carried by the application software release, installation or initial run to describe its own properties and functions, in some embodiments, it can also be directly provided to the server side by manual input.

[0055] In this embodiment, the release information of the first application software includes first software feature information and first error code information, wherein the first software feature information includes but is not limited to software name, version number and other features that can be used to distinguish the application software, and the first error code information includes but is not limited to the error code dictionary applicable to the first application software, that is, error code and error code description, such as the character segment "0001:'system exception'" in the form of key-value pair, in which "0000" is the error code and "system exception" is the error code description. In different application software, the same error code may correspond to different error code descriptions, which is one of the reasons for the confusion of error codes when the same vehicle runs multiple application software. In this embodiment, by storing the different error code information and the software feature information of the application software applicable thereto in the registration information table of the server side in the subsequent steps, and then calling the application software actually running on the vehicle terminal, the confusion of error codes can be effectively avoided.

[0056] For steps S110-S160, it should be understood that the vehicle terminal includes but is not limited to the running body of various vehicle-mounted application software such as vehicles, vehicle central control, car machine, etc., and the server side includes but is not limited to computer devices, servers, computing platforms or other devices or equipment with computing functions set on vehicles, clouds, and third-party platforms with the above functions or similar functions.

[0057] In the above steps, the description of "first" and "second" in the first application software and the second application software is only used to distinguish the steps in which they are located, that is, the first application software and the second application software can be but are not limited to different application software, or the same application software in the method steps. It can be understood that the application software here refers to vehicle-mounted application software.

[0058] It can be seen that for the above steps, first, the release information of the first application software is registered to the server side, different error code information is stored in the registration information table of the server side corresponding to the software feature information of the application software applicable thereto, and subsequent second application software actually run by the vehicle terminal is used to call the second error code information applicable to the second application software and temporarily store the second error code information in the vehicle terminal for use when the second application software runs, solving the problems that the error code in the prior art has no unified benchmark under different software development frameworks, and the error code definition between different versions of the same system or software is changing, which can effectively avoid the confusion of the error code of the vehicle-mounted application software, improve the running fault positioning efficiency of the vehicle-mounted application software, and greatly reduce the difficulty of vehicle maintenance.

[0059] In the embodiment, the registration information table includes the correspondence between the plurality of historical software feature information and historical error code, the server side selects a registration strategy based on the first software feature information, and registers the release information to the registration information table according to the registration strategy, and the steps include:

[0060] According to the first software feature information, the historical software feature information in the registration information table is matched, and the registration strategy is selected according to the matching result;

[0061] If any one of the historical software feature information in the registration information table is inconsistent with the first software feature information, the first strategy is determined as the registration strategy;

[0062] If the historical software feature information in the registration information table is consistent with the first software feature information, the second strategy is determined as the registration strategy.

[0063] For the above steps, it can be understood that registration is to add the release information to the registration information table according to the format and method specified by the registration strategy, and the registration strategy includes the information adding method. In this process, the selection of the registration strategy is based on all the historical software feature information already existing in the registration information table. According to whether the first software feature information is consistent with the historical software feature information, it can be determined whether the first software feature information already exists in the registration information table, and then different registration strategies are adopted, which is beneficial to avoid the repetition and redundancy of the software feature information and the error code information in the server side.

[0064] Specifically, in the embodiment, the implementation scheme of the first strategy and the second strategy is specifically shown, wherein the first strategy includes:

[0065] The first software feature information and the first error code information are added to the registration information table, wherein the first software feature information is taken as new historical software feature information, and the first error code information is taken as new historical error code information.

[0066] It can be understood that in the first strategy, since the first software feature information uploaded to the server side is brand new, there is no data conflict problem, and it is directly written into the registration information table to complete registration.

[0067] The second strategy includes:

[0068] An artificial judgment request is issued to determine whether to overwrite the registration information table;

[0069] Based on the feedback result of the artificial judgment request, if the feedback result includes confirmation of overwriting, the corresponding relationship between the first software feature information and the first error code information is overwritten and written into the registration information table, otherwise the second strategy is ended.

[0070] In the second strategy, since there is historical software feature information corresponding to the first software feature information in the registration information table, it means that the first software feature information and its corresponding error code information have been registered in the registration information table, but the error code information may change. At this time, the first software feature information has at least two possibilities, one is repeated uploading, and the other is uploading after updating, so the server side needs to determine whether to overwrite the original data according to the artificial judgment.

[0071] In this embodiment, an implementation scheme is also exemplarily shown in which the server side searches the registration information table based on the second software feature information to determine the second error code information matched with the second software feature information. In this implementation scheme, the historical software feature information includes a historical software name and a historical software version number, and the second software feature information includes a second software name and a second software version number. The implementation scheme includes the following steps:

[0072] In the registration information table, the historical software feature information is searched;

[0073] If the search result includes target software feature information which includes both the second software name and the second software version number, the historical error code information corresponding to the target software feature information is taken as the second error code information;

[0074] If any historical software feature information includes at most one of the second software name and the second software version number, the current method step is ended, and the second software name and the second software version number are recorded.

[0075] For the above steps, at least the software name and software version number of the application software are taken as the software feature information, and it is worth noting that the same set of error code information can be applicable to multiple application softwares, thereby corresponding to multiple sets of software feature information, and the same application software can also have multiple versions, each of which corresponds to different error code information, and therefore taking the software name and software version number as the feature can accurately determine the error code information currently applicable to the second application software, so as to ensure the accuracy of the error code call of the second application software in the subsequent running process.

[0076] In the embodiment, after the vehicle terminal receives the second error code information sent by the server end and temporarily stores it in the preset temporary storage space, the method further comprises:

[0077] The vehicle terminal matches the temporary storage space based on the error code fed back by the second application software to obtain an error code matching result;

[0078] If the error code matching result includes the error code fed back by the software, the error code information corresponding to the error code is displayed, otherwise error information is sent to the server end.

[0079] For the above steps, it can be understood that the application software running on the vehicle terminal can directly call the error code information from the temporary storage space. For example, in some application environment, the music playing software of the vehicle terminal such as the car machine occurs an error when running, and since it has received the corresponding error code information from the server end and stored it in the temporary storage space such as the car machine storage disk when starting, the relevant error information can be displayed on the car machine by the error code fed back by the music playing software, for example, the music playing software runs abnormally, feeds back error code 0001, and the car machine matches the corresponding error code information such as "0001-Abnormal running" corresponding to the error code 0001 in the temporary storage space. It can be seen that by pre-configuring the applicable error code information for the application software running on the vehicle terminal, the application software can quickly find the corresponding error code information when reporting errors through error codes, which can effectively avoid error code redundancy and confusion and improve fault positioning efficiency.

[0080] It is worth noting that the temporary storage space refers to the storage space of the vehicle terminal for storing error code information fed back from the server end, and the content in the temporary storage space can be periodically deleted according to a preset period, or deleted according to the operation instruction of the user, or deleted based on the closing action of the second application software, since the specific implementation is not necessary for the implementation of the present application, it is not limited.

[0081] As described above, in the vehicle terminal error code management method provided in the present application, first, the release information of the first application software is registered to the server terminal, and different error code information is stored in the registration information table of the server terminal in correspondence with the software feature information of the application software to which the error code information is applicable. Subsequently, based on the second application software actually run by the vehicle terminal, the second error code information applicable to the second application software is called and temporarily stored in the vehicle terminal for use when the second application software is run, thereby solving the problems in the prior art that the error codes have no unified benchmark under different software development frameworks, and the error code definitions vary between different versions of the same system or software, effectively avoiding the confusion of error codes of the vehicle-mounted application software, improving the running fault positioning efficiency of the vehicle-mounted application software, and greatly reducing the difficulty of vehicle maintenance in the later period.

[0082] In an embodiment, the present application also specifically provides a vehicle machine error code management system, as shown in Figure 2 Figure 2 is a structural schematic diagram of the vehicle machine error code management system according to an exemplary embodiment of the present application. The vehicle machine error code management system includes a vehicle terminal 201 and a server terminal 202, and the vehicle terminal 201 and the server terminal 202 in the system correspond one-to-one to the vehicle terminal error code management method in the above-mentioned embodiments. That is, in the present embodiment, the server terminal 202 is configured to:

[0083] receive the release information of the first application software, the release information including the first software feature information and the first error code information;

[0084] select a registration strategy based on the first software feature information, and register the release information to the registration information table according to the registration strategy;

[0085] based on the second software feature information sent by the vehicle terminal 201, search the registration information table to determine the second error code information matched with the second software feature information, and send the second error code information to the vehicle terminal 201.

[0086] In the present embodiment, the vehicle terminal 201 is configured to:

[0087] based on the start instruction of the second application software, send the second software feature information of the second application software to the server terminal 202, and receive the second error code information sent by the server terminal 202 and temporarily store the second error code information in a preset temporary storage space.

[0088] ​As described above, the vehicle-machine error code management system provided by the application first registers the release information of the first application software to the server end, stores the different error code information and the software feature information of the application software applicable thereto in the registration information table of the server end in correspondence with each other, and then based on the second application software actually running on the vehicle terminal, calls the second error code information applicable to the second application software and temporarily stores the second error code information in the vehicle terminal for use when the second application software runs, thereby solving the problems that the error codes in the prior art have no unified benchmark under different software development frameworks, and the error code definitions between different versions of the same system or software are changing, and effectively avoiding the confusion of the error codes of the vehicle-mounted application software, improving the running fault positioning efficiency of the vehicle-mounted application software, and greatly reducing the difficulty of vehicle maintenance.

[0089] It should be noted that the vehicle-machine error code management system provided by the above embodiment and the vehicle-terminal error code management method provided by the above embodiment belong to the same concept, and the specific manner in which each terminal performs the operation has been described in detail in the method embodiment, which will not be described here. The vehicle-machine error code management system provided by the above embodiment can be used in actual application, and the above functions can be completed by different functional modules according to the needs, i.e., the internal structure of the device is divided into different functional modules to complete all or part of the functions described above, and this is not limited herein.

[0090] An embodiment of the application further provides an electronic device, including: one or more processors; a storage device configured to store one or more programs, when the one or more programs are executed by the one or more processors, the electronic device implements the vehicle-terminal error code management method provided in each of the above embodiments.

[0091] Figure 3 The structure of the computer system of the electronic device suitable for implementing the embodiments of the application is shown. It should be noted that, Figure 3 The computer system 300 of the electronic device shown is only an example, and should not limit the functions and use range of the embodiments of the application.

[0092] As Figure 3As shown, the computer system 300 includes a central processing unit (CPU) 301 which can perform various appropriate actions and processes in accordance with a program stored in a read-only memory (ROM) 302 or a program loaded from the storage section 308 into a random access memory (RAM) 303, such as performing the methods described in the above embodiments. In the RAM 303, various programs and data required for the operation of the system are also stored. The CPU 301, the ROM 302, and the RAM 303 are connected to each other through a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0093] Connected to the I / O interface 305 are an input section 306 including a keyboard, a mouse, etc.; an output section 307 including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 308 including a hard disk, etc.; and a communication section 309 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 309 performs communication processing via a network such as the Internet. A drive 310 is also connected to the I / O interface 305 as necessary. A removable recording medium 311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is attached to the drive 310 as necessary, so that a computer program read therefrom is installed into the storage section 308 as necessary.

[0094] In particular, according to embodiments of the present application, the processes described above with reference to the flowcharts can be implemented as a computer software program. For example, embodiments of the present application include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing a computer program for executing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via the communication section 309, and / or installed from the removable recording medium 311. When the computer program is executed by the central processing unit (CPU) 301, various functions defined in the system of the present application are performed.

[0095] It should be noted that the computer-readable medium in the embodiments of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination thereof. The computer-readable storage medium may, for example, be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination thereof. More specific examples of the computer-readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this application, the computer-readable signal medium can include a data signal propagated in a baseband or as a carrier wave in a propagated data signal, in which the computer-readable computer program is carried. Such a propagated data signal can take on many forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination thereof. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, which can send, propagate, or transmit the program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted in any suitable medium, including but not limited to wireless, wired, or the like, or any suitable combination thereof.

[0096] The flowcharts and block diagrams in the drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. Each block in the flowcharts or block diagrams can represent a module, a program segment, or a portion of code, which contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions noted in the blocks can occur in a different order than that shown in the figures. For example, two blocks noted in succession can actually be executed substantially concurrently, or they can sometimes be executed in reverse order, depending on the functionality involved. It should also be noted that each block in the flowcharts or block diagrams, and combinations of blocks in the flowcharts or block diagrams, can be implemented by special-purpose hardware-based systems, which perform the specified functions or operations, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0097] The units described in the embodiments of the present application can be implemented in the form of software, or can be implemented in the form of hardware, and the described units can also be arranged in a processor. In some cases, the names of the units do not constitute a limitation on the units themselves.

[0098] Another aspect of the present application also provides a computer readable storage medium, which stores a computer program. When the computer program is executed by a processor of a computer, the computer performs the vehicle-side error code management method as described above. The computer readable storage medium can be included in the electronic device described in the above embodiments, or can exist separately and not be assembled into the electronic device.

[0099] Another aspect of the present application also provides a computer program product or a computer program, which includes computer instructions stored in a computer readable storage medium. A processor of a computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions, so that the computer device performs the vehicle-side error code management method provided in each of the above embodiments.

[0100] The above embodiments only exemplarily illustrate the principles and effects of the present application, and are not used to limit the present application. Any person skilled in the art can modify or change the above embodiments without departing from the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by those skilled in the art without departing from the spirit and technical thought of the present application should be covered by the claims of the present application.

Claims

1. A method for managing vehicle-side error codes, characterized in that, include: The vehicle terminal and server are obtained, and the server has a registration information table. The server receives the release information of the first application software, the release information including the first software feature information and the first error code information; The server selects a registration strategy based on the first software feature information and registers the release information to the registration information table according to the registration strategy. The vehicle terminal sends the second software feature information of the second application software to the server based on the launch command of the second application software; The server searches the registration information table based on the second software feature information to determine the second error code information that matches the second software feature information, and then sends it to the vehicle terminal. The vehicle terminal receives the second error code information sent by the server and temporarily stores it in a preset temporary storage space; The vehicle terminal matches the temporary storage space based on the error code fed back by the second application software to obtain the error code matching result; If the error code matching result includes the error code, then the error code information corresponding to the error code is displayed; otherwise, an error message is sent to the server.

2. The vehicle-side error code management method according to claim 1, characterized in that, The registration information table includes a correspondence between multiple historical software feature information and historical error codes. The steps of the server selecting a registration strategy based on the first software feature information and registering the release information to the registration information table according to the registration strategy include: Based on the first software feature information, the historical software feature information in the registration information table is matched, and a registration strategy is selected based on the matching result; If any of the historical software feature information in the registration information table is inconsistent with the first software feature information, then the first strategy will be determined as the registration strategy. If the historical software feature information in the registration information table is consistent with the first software feature information, then the second strategy will be determined as the registration strategy.

3. The vehicle-side error code management method according to claim 2, characterized in that, The first strategy includes: The correspondence between the first software feature information and the first error code information is added to the registration information table, wherein the first software feature information is used as new historical software feature information, and the first error code information is used as new historical error code information.

4. The vehicle-side error code management method according to claim 2, characterized in that, The second strategy includes: Issue a manual judgment request to determine whether the registration information table has been overwritten; Based on the feedback results of the manual judgment request, if the feedback results include confirmation coverage, the correspondence between the first software feature information and the first error code information is written to the registration information table; otherwise, the second strategy ends.

5. The vehicle-side error code management method according to claim 2, characterized in that, The step of the server-side retrieving the registration information table based on the second software feature information to determine the second error code information that matches the second software feature information includes: The historical software feature information includes the historical software name and the historical software version number, and the second software feature information includes the second software name and the second software version number; The historical software feature information is retrieved from the registration information table; If the search results include target software feature information, and the target software feature information includes both the second software name and the second software version number, then the historical error code information corresponding to the target software feature information is used as the second error code information; If any of the historical software feature information includes at most one of the second software name and the second software version number, then the current method step ends, and the second software name and the second software version number are recorded.

6. A vehicle-mounted error code management system, characterized in that, It includes a vehicle terminal and a server, wherein the server is configured with a registration information table, and the server is used for: Receive the release information of the first application software, the release information including the first software feature information and the first error code information; A registration strategy is selected based on the first software feature information, and the release information is registered to the registration information table according to the registration strategy; Based on the second software feature information sent by the vehicle terminal, the registration information table is retrieved to determine the second error code information that matches the second software feature information, and then sent to the vehicle terminal. The vehicle terminal is used for: Receive the second error code information sent by the server and temporarily store it in a preset temporary storage space; Based on the error codes fed back by the second application software, the temporary storage space is matched to obtain the error code matching results; If the error code matching result includes the error code, then the error code information corresponding to the error code is displayed; otherwise, an error message is sent to the server.

7. The vehicle error code management system according to claim 6, characterized in that: The vehicle terminal is used to send the second software feature information of the second application software to the server based on the startup command of the second application software; and to receive the second error code information sent by the server and temporarily store it in a preset temporary storage space.

8. An electronic device, characterized in that, The electronic device includes: One or more processors; A storage device for storing one or more programs, which, when executed by one or more processors, cause the electronic device to implement the vehicle-side error code management method as described in any one of claims 1 to 5.

9. A computer-readable storage medium, characterized in that, It stores a computer program, which, when executed by the computer's processor, causes the computer to perform the vehicle-side error code management method as described in any one of claims 1 to 5.

Images