Fault code data processing method and device, electronic equipment and storage medium
By processing fault code data with a hash algorithm, generating hash key values and establishing mapping relationships, and storing them encrypted, the problem of fault code data being easily cracked and pirated is solved, thus achieving data security and product protection.
Patent Information
- Application Number
- CN202511756098.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-11-26
- Publication Date
- 2026-02-27
AI Technical Summary
The current method of storing fault code data is easily compromised by cracking the data structure and can be directly used by pirated software, posing a data security problem.
The fault code data is processed using a hash algorithm. A hash operation is performed on the fixed header information, system identifier, and fault code number to generate a hash key value. A mapping relationship between the hash key value and the fault code representation information is established and stored in an encrypted manner to ensure that the data association is hidden.
It effectively hides the relationships between data, making it difficult for attackers to obtain the data structure by analyzing the mapping relationship. Pirated software cannot directly use the data, thus improving data security and product protection.
Smart Images
Figure CN121580418A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of data security storage, and particularly relates to a fault code data processing method and device, electronic equipment and a storage medium. BACKGROUND
[0002] In a traditional fault code data storage system, data is usually stored in plaintext or simple encrypted form, for example, the system identifier is BCM, the fault code number is P012345, and the fault code representation information is system failure. After obtaining the stored file, an attacker can easily obtain the complete structure and content of the data through brute force cracking or pattern analysis, and quickly copy and use it.
[0003] Therefore, the existing fault code data storage method has the problems of direct exposure of data association relationship, easy cracking of data structure, and easy direct use by pirated software. SUMMARY
[0004] Therefore, the present application provides a fault code data processing method and device, electronic equipment and a storage medium to solve the problem of easy cracking of data structure or easy direct use by pirated software in the prior art.
[0005] The first aspect of the present application provides a fault code data processing method, comprising: Obtaining fault code data and obtaining fixed header information; wherein the fault code data comprises a system identifier, a fault code number and fault code representation information; Performing hash operation processing on the fixed header information, the system identifier and the fault code number based on a preset hash algorithm to obtain a hash key value; Establishing a mapping relationship between the hash key value and the fault code representation information, and storing the mapping relationship.
[0006] In one possible implementation, performing hash operation processing on the fixed header information, the system identifier and the fault code number based on a preset hash algorithm to obtain a hash key value comprises: Arranging the string of the fixed header information, the string of the system identifier and the string of the fault code number in sequence to obtain a composite string; Performing hash operation processing on the composite string based on a preset hash algorithm to obtain a hash key value.
[0007] In one possible implementation, establishing a mapping relationship between the hash key value and the fault code representation information, and storing the mapping relationship comprises: Establishing a mapping relationship between the hash key value and the fault code representation information, performing first encryption processing on the mapping relationship and storing it in a preset mapping dictionary; The preset mapping dictionary is encrypted for the second time and stored in a preset file.
[0008] In a possible implementation, the fixed header information is at least one of device information, user information, company information, or preset fixed information.
[0009] In a possible implementation, after the mapping relationship between the hash key value and the fault code representation information is established and stored, the following includes: In response to a data reading request, obtaining the to-be-verified fixed header information, the to-be-verified system identifier, and the to-be-verified fault code number in the data reading request; Using a hash algorithm, performing hash operation processing based on the to-be-verified fixed header information, the to-be-verified system identifier, and the to-be-verified fault code number to obtain a temporary hash key value; Based on the temporary hash key value, searching for the fault code representation information corresponding to the temporary hash key value in the mapping relationship.
[0010] In a possible implementation, based on the temporary hash key value, searching for the fault code representation information corresponding to the temporary hash key value in the mapping relationship includes: Obtaining password information; wherein the password information is generated based on at least one of the user information and / or the device information; Decrypting the mapping relationship based on the password information; wherein the mapping relationship is stored in advance after being encrypted; Based on the temporary hash key value, searching for the fault code representation information corresponding to the temporary hash key value in the decrypted mapping relationship.
[0011] In a possible implementation, based on the temporary hash key value, searching for the fault code representation information corresponding to the temporary hash key value in the mapping relationship includes: Verifying the integrity of the preset file based on a preset algorithm; wherein the mapping relationship is stored in the preset file; When the integrity of the preset file is verified, based on the temporary hash key value, searching for the fault code representation information corresponding to the temporary hash key value in the mapping relationship.
[0012] A second aspect of the embodiment of the application provides a fault code data processing apparatus, including: An obtaining module is configured to obtain fault code data and obtain fixed header information; wherein the fault code data includes a system identifier, a fault code number, and fault code representation information; A first processing module is configured to use a preset hash algorithm to perform hash operation processing based on the fixed header information, the system identifier, and the fault code number to obtain a hash key value; A second processing module is configured to establish a mapping relationship between the hash key value and the fault code representation information, and store the mapping relationship.
[0013] The third aspect of the embodiments of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the method of the first aspect when executing the computer program.
[0014] The fourth aspect of the embodiments of the present application provides a computer readable storage medium, which stores a computer program, and the computer program implements the steps of the method of the first aspect when executed by a processor.
[0015] Compared with the prior art, the embodiments of the present application have the following beneficial effects: The processing method of fault code data provided by the first aspect of the embodiments of the present application can obtain fault code data and fixed header information; then, a preset hash algorithm is used to perform hash operation processing based on the fixed header information, the system identifier and the fault code number to obtain a hash key value; further, a mapping relationship between the hash key value and the fault code representation information is established, and the mapping relationship is stored. The embodiments of the present application use a one-way encryption mode of the hash algorithm, and since the hash algorithm cannot be directly restored, it can only be enumerated by force, but the enumeration efficiency is very low, so that an attacker cannot analyze the content of the data structure by analyzing the mapping relationship. At the same time, the association relationship between the data can be effectively hidden by the hash key value. Moreover, the attacker must know the fixed header information, the system identifier and the fault code number at the same time to correctly access the data. Therefore, the processing method of fault code data in the embodiments of the present application makes the data structure not easy to be cracked, and also not easy to be directly used by pirated software, thereby ensuring data security and product security.
[0016] It can be understood that the beneficial effects of the above-mentioned second aspect to fourth aspect can be referred to the related description in the first aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS
[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can also be obtained by those skilled in the art without creating any creative labor.
[0018] Figure 1 is a flowchart of a processing method of fault code data provided by the embodiments of the present application; Figure 2 is a flowchart of another processing method of fault code data provided by the embodiments of the present application; Figure 3 is a flowchart of still another processing method of fault code data provided by the embodiments of the present application; Figure 4is a structural schematic diagram of a fault code data processing device provided by an embodiment of the present application. Figure 5 is a structural schematic diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION
[0019] In the following description, for the purposes of explanation and not limitation, specific details are set forth, such as particular sequences of acts, techniques, etc., in order to provide a thorough understanding of the embodiments of the application. However, it will be apparent to those skilled in the art that the embodiments of the present application can be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known methods, devices, circuits, and
[0020] It is to be understood that the terminology "includes", "has", "holds", "contains" or variants thereof, when utilized within the present specification and claims, denotes the presence of the stated feature but not the exclusion after the presence of one or more additional features, integers, steps, operations, elements, components and / or groups thereof.
[0021] It is also to be understood that the terminology "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items, as well as to the
[0022] As used in the description of the application and the appended claims, the term "if" can be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting" depending on the context. Similarly, the phrase "if it is determined" or "if [a described condition or event] is detected" can be interpreted to mean "upon determining" or "in response to determining" or "upon [the described condition or event] being detected" or "in response to [the described condition or event] being detected", depending on the context.
[0023] In addition, in the description of the application and the appended claims, the terms "first", "second", "third", etc. are used merely as labels for the purpose of distinguishing between different features, and are not intended to indicate or imply relative importance of the different features.
[0024] Reference within the specification of this application to "one embodiment" or "some embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the application. The appearances of the phrase "in one embodiment" or "in some embodiments" in various places within specified
[0025] The technical solutions of the application and how the technical solutions solve the above technical problems will be described in detail below with specific embodiments. It should be noted that the following embodiments can be mutually referenced, learned from or combined. For the same terms, similar features and similar implementation steps in different embodiments, they will not be described repeatedly.
[0026] Referring to Figure 1 As shown in FIG. 1, the embodiment of the application provides a flowchart of a fault code data processing method. As shown in FIG. 2, the fault code data processing method includes steps S101 to S103. Figure 1 As shown in FIG. 1, the embodiment of the application provides a flowchart of a fault code data processing method. As shown in FIG. 2, the fault code data processing method includes steps S101 to S103.
[0027] S101, acquiring fault code data and acquiring fixed header information; wherein the fault code data includes system identification, fault code number and fault code representation information.
[0028] Optionally, acquiring fault code data includes: in response to a data storage request, acquiring fault code data in the data storage request.
[0029] In some embodiments, the fixed header information is at least one of device information, user information, company information or preset fixed information.
[0030] Optionally, the fixed header information can be acquired separately or from the fault code data.
[0031] S102, using a preset hash algorithm to perform hash operation processing based on the fixed header information, the system identification and the fault code number to obtain a hash key value.
[0032] Optionally, the hash algorithm is to map input data of arbitrary length to output value of fixed length through a hash function. The hash algorithm of the embodiment of the application can be a multiple hash algorithm, which is a process of continuously applying a hash function (which can be the same function or different functions) to the same original data (or the previous hash key value) for multiple times.
[0033] S103, a mapping relationship between the hash key value and the fault code representation information is established, and the mapping relationship is stored.
[0034] Specifically, the stored mapping relationship includes the hash key value, the fault code representation information, and the correspondence between the hash key value and the fault code representation information.
[0035] The processing method of the fault code data of the embodiment of the application can obtain the fault code data and the fixed header information; then, a preset hash algorithm is used to perform hash operation processing based on the fixed header information, the system identifier, and the fault code number to obtain a hash key value; further, a mapping relationship between the hash key value and the fault code representation information is established, and the mapping relationship is stored.
[0036] The embodiment of the application uses a one-way encryption mode of the hash algorithm. Since the hash algorithm cannot be directly restored, it can only be enumerated by force, but the enumeration efficiency is very low, so that an attacker cannot analyze the content of the data structure by analyzing the mapping relationship. At the same time, the association relationship between the data can be effectively hidden by the hash key value. Moreover, the attacker must know the fixed header information, the system identifier, and the fault code number at the same time to correctly access the data. Therefore, the processing method of the fault code data of the embodiment of the application makes the data structure not easy to be cracked and not easy to be directly used by pirated software, ensuring data security and product security.
[0037] The embodiment of the application can prevent the running of pirated programs for different device information or users or other combinations, because the fault code data and / or the hash key value generated by different devices are different, and the pirated software cannot run even if it gets the data file.
[0038] In some embodiments, the preset hash algorithm is used to perform hash operation processing based on the fixed header information, the system identifier, and the fault code number to obtain the hash key value, including: The strings of the fixed header information, the strings of the system identifier, and the strings of the fault code number are arranged in sequence to obtain a composite string; The preset hash algorithm is used to perform hash operation processing on the composite string to obtain the hash key value.
[0039] Specifically, the fixed header information, the system identifier, and the fault code number are all composed of strings.
[0040] In some embodiments, the mapping relationship between the hash key value and the fault code representation information is established, and the mapping relationship is stored, including: The mapping relationship between the hash key value and the fault code representation information is established, the mapping relationship is subjected to first encryption processing and stored in a preset mapping dictionary; and The preset mapping dictionary is subjected to second encryption processing and stored in a preset file.
[0041] The preset file is a file for storing data.
[0042] Specifically, the embodiment of the application can perform first encryption processing on the mapping relationship and store the mapping relationship in a preset mapping dictionary, and perform second encryption processing on the preset mapping dictionary and store the mapping dictionary in a preset file, so that the security of data can be improved and the data can be prevented from being easily cracked.
[0043] Referring to Figure 2 As shown in the figure, the embodiment of the application provides a flowchart of another processing method of fault code data. As shown in the figure, Figure 2 The processing method of fault code data includes steps S201 to S205.
[0044] S201, acquiring fault code data and acquiring fixed header information; wherein the fault code data includes a system identifier, a fault code number, and fault code representation information.
[0045] Specifically, the implementation principle of step S201 of the embodiment of the application is consistent with the implementation principle of step S101, and will not be described here.
[0046] S202, arranging the string of the fixed header information, the string of the system identifier, and the string of the fault code number in sequence to obtain a composite string.
[0047] Specifically, the fixed header information, the system identifier, and the fault code number are all composed of strings.
[0048] The embodiment of the application generates a composite string using a three-level hash key generation system with the string of the fixed header information (HeaderString), the string of the system identifier (System String), and the string of the fault code number (ID String).
[0049] S203, performing hash operation processing on the composite string using a preset hash algorithm to obtain a hash key value.
[0050] Optionally, the composite string can generate a final hash key value through a specific algorithm containing a hash algorithm.
[0051] S204, establishing a mapping relationship between the hash key value and the fault code representation information, performing first encryption processing on the mapping relationship, and storing the mapping relationship in a preset mapping dictionary.
[0052] S205, performing second encryption processing on the preset mapping dictionary and storing the mapping dictionary in a preset file.
[0053] The embodiment of the application stores the established mapping relationship between the hash key value and the fault code representation information in the preset dynamic mapping dictionary after encryption. At the same time, the mapping dictionary is stored by twice encryption to prevent direct analysis.
[0054] The embodiment of the present application can receive a data storage request, obtain system identification, fault code number and fault code representation information in the data storage request, combine a string of fixed header information, a string of system identification and a string of fault code number to generate a composite string. A unique hash key value is generated by applying a multiple hash algorithm to the composite string. The mapping relationship between the hash key value and the fault code representation information is encrypted and stored in a mapping dictionary, and the mapping dictionary is written into a preset file after being secondly confused.
[0055] Referring to Figure 3 The embodiment of the present application provides another flow chart of a fault code data processing method. As shown in Figure 3 The fault code data processing method includes steps S301 to S306.
[0056] S301, obtaining fault code data and obtaining fixed header information; wherein the fault code data includes system identification, fault code number and fault code representation information.
[0057] S302, performing hash operation processing based on the fixed header information, the system identification and the fault code number by using a preset hash algorithm, to obtain a hash key value.
[0058] S303, establishing a mapping relationship between the hash key value and the fault code representation information, and storing the mapping relationship.
[0059] The steps S301 to S303 of the embodiment of the present application are consistent with the principles of the steps S101 to S103 of the embodiment of the present application, and will not be repeated here.
[0060] S304, obtaining to-be-verified fixed header information, to-be-verified system identification and to-be-verified fault code number in the data read request in response to the data read request.
[0061] S305, performing hash operation processing based on the to-be-verified fixed header information, the to-be-verified system identification and the to-be-verified fault code number by using a hash algorithm, to obtain a temporary hash key value.
[0062] S306, searching for fault code representation information corresponding to the temporary hash key value in the mapping relationship based on the temporary hash key value.
[0063] When the data read request is received, the embodiment of the present application uses the same rule of hash operation processing mode to obtain a temporary hash key value, so as to search for fault code representation information corresponding to the temporary hash key value in the mapping relationship. The to-be-verified fixed header information, the to-be-verified system identification and the to-be-verified fault code number all need to be correct, so as to obtain the corresponding fault code representation information.
[0064] In actual application, the embodiment of the application can verify the legality of the system identifier to be verified and the fault code number to be verified provided by the requestor.
[0065] In some embodiments, based on the temporary hash key value, the fault code representation information corresponding to the temporary hash key value is found in the mapping relationship, including: Obtaining password information; wherein the password information is generated based on at least one of the user information and / or the device information; Decrypting the mapping relationship based on the password information; wherein the mapping relationship is pre-encrypted and stored; Based on the temporary hash key value, the fault code representation information corresponding to the temporary hash key value is found in the decrypted mapping relationship.
[0066] Optionally, the password information can include first password information and second password information; the mapping relationship is pre-encrypted and stored by the first password information, the mapping dictionary is pre-encrypted and stored by the second password information, and the mapping relationship is stored in the mapping dictionary.
[0067] Optionally, the first password information and the second password information are both generated based on at least one of the user information and / or the device information.
[0068] Wherein, before decrypting the mapping relationship based on the password information, it further includes decrypting the mapping dictionary based on the second password information.
[0069] Correspondingly, decrypting the mapping relationship based on the password information includes decrypting the mapping relationship based on the first password information.
[0070] The embodiment of the application needs to decrypt the mapping dictionary and the mapping relationship in sequence to obtain the fault code representation information.
[0071] In some embodiments, based on the temporary hash key value, the fault code representation information corresponding to the temporary hash key value is found in the mapping relationship, including: Verifying the integrity of the preset file based on a preset algorithm; wherein the mapping relationship is stored in the preset file; When the integrity of the preset file is verified, based on the temporary hash key value, the fault code representation information corresponding to the temporary hash key value is found in the mapping relationship.
[0072] The embodiment of the application can decrypt and return after verifying the content integrity of the preset file, and find the fault code representation information corresponding to the temporary hash key value when the integrity of the preset file is verified.
[0073] The embodiment of the application provides an example of a fault code data processing method. For example: (1) The string of the fixed header information: "Launch_"; (2) System identification "BCM" and fault code number "P012345"; (3) Generate a composite string: "Launch_BCM_P012345"; (4) Apply SHA-3 algorithm to generate a 256-bit hash key value: 7F05D1275691EC1ACEF07457507113423936F2F786B75C04B6F70A85F15EA276; (5) Establish a mapping relationship between the hash key value and the fault code representation information: 7F05D1275691EC1ACEF07457507113423936F2F786B75C04B6F70A85F15EA276, which is fault code 12345; (6) Use AES-256 to encrypt the mapping dictionary. AES-256 is one of the most commonly used and most secure symmetric encryption algorithms, and is known as the golden rule of encryption standards.
[0074] The enhanced security implementation of the embodiments of the present application is based on the basic security implementation and increases: (1) Implementing a sharding storage mechanism, the composite string and the hash key value are stored separately; (2) Increase the integrity verification of the preset file using HMAC. Using HMAC to verify file integrity is like adding a "security seal" to the preset file. Any minor changes to the preset file will cause the "security seal" to fail to match, thus immediately exposing tampering behavior.
[0075] (3) Prevent the running of pirated programs for different device information or users or other combinations, because the fault code data and / or hash key value generated by different devices are different, and the pirated software cannot run even if it gets the data file.
[0076] The application of the embodiments of the present application can at least achieve the following technical effects: (1) Anti-explosion feature: attackers cannot obtain the original mapping relationship by analyzing the stored file, because the hash algorithm cannot be directly restored, but only through brute force enumeration, but the enumeration efficiency is very low.
[0077] (2) Association hiding: the association between data is effectively hidden by the hash key value.
[0078] (3) Multi-layer verification: the fixed header information, system identification and fault code number must be known at the same time to correctly access the data.
[0079] (4) Flexible expansion: It can adapt to application scenarios with different security levels, and can add keywords such as device information to perform hash operations together, which can prevent others from directly using the data file.
[0080] The fault code data processing method provided in this application embodiment can be applied to terminal devices such as mobile phones, tablets, wearable devices, in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, and personal digital assistants (PDAs). This application embodiment does not impose any restrictions on the specific type of terminal device.
[0081] For example, a terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a vehicle-to-everything (V2X) terminal, a computer, a laptop computer, a handheld communication device, a handheld computing device, a satellite wireless device, a wireless modem card, a set-top box (STB), customer premises equipment (CPE), and / or other devices used for communication over a wireless system, as well as next-generation communication systems, such as mobile terminals in 5G networks or mobile terminals in future evolved Public Land Mobile Network (PLMN) networks.
[0082] See Figure 4 As shown in the diagram, this application embodiment provides a structural schematic of a fault code data processing device 40. The fault code data processing device 40 includes: an acquisition module 401, a first processing module 402, and a second processing module 403. The acquisition module 401 is used to acquire fault code data and acquire fixed head information; wherein, the fault code data includes system identifier, fault code number and fault code representation information; The first processing module 402 is used to perform hash operation based on fixed header information, system identifier and fault code number using a preset hash algorithm to obtain hash key value; The second processing module 403 is configured to establish a mapping relationship between the hash key value and the fault code representation information, and store the mapping relationship.
[0083] Optionally, the first processing module 402 is configured to arrange the string of the fixed header information, the string of the system identifier, and the string of the fault code number in sequence to obtain a composite string, and perform hash operation processing on the composite string by using a preset hash algorithm to obtain the hash key value.
[0084] Optionally, the second processing module 403 is configured to establish a mapping relationship between the hash key value and the fault code representation information, perform first encryption processing on the mapping relationship, and store the mapping relationship in a preset mapping dictionary, and perform second encryption processing on the preset mapping dictionary and store the preset mapping dictionary in a preset file.
[0085] Optionally, the fault code data processing apparatus 40 further includes a data reading module. The data reading module is configured to, in response to a data reading request, acquire the to-be-verified fixed header information, the to-be-verified system identifier, and the to-be-verified fault code number in the data reading request, perform hash operation processing on the to-be-verified fixed header information, the to-be-verified system identifier, and the to-be-verified fault code number based on a hash algorithm to obtain a temporary hash key value, and search for the fault code representation information corresponding to the temporary hash key value in the mapping relationship based on the temporary hash key value.
[0086] Optionally, the data reading module is configured to acquire password information, wherein the password information is generated based on at least one of user information and / or device information, decrypt the mapping relationship based on the password information, wherein the mapping relationship is stored in advance after being encrypted, and search for the fault code representation information corresponding to the temporary hash key value in the decrypted mapping relationship based on the temporary hash key value.
[0087] Optionally, the data reading module is configured to verify the integrity of the preset file based on a preset algorithm, wherein the mapping relationship is stored in the preset file, and when the integrity of the preset file is verified, search for the fault code representation information corresponding to the temporary hash key value in the mapping relationship based on the temporary hash key value.
[0088] In applications, each module in the fault code data processing apparatus 40 can be a software program module, can be implemented by different logic circuits integrated in a processor, or can be implemented by multiple distributed processors.
[0089] The processing apparatus 40 for fault code data provided in the embodiments of the present application can execute the method provided in the embodiments of the present application, and the implementation principle is similar. The actions performed by each module in the processing apparatus 40 for fault code data in the embodiments of the present application correspond to the steps in the method of the embodiments of the present application. For the detailed function description of each module of the processing apparatus 40 for fault code data, refer to the description of the corresponding method in the foregoing, which will not be repeated here.
[0090] Referring to Figure 5 As shown in FIG. 5, the embodiments of the present application provide a structural schematic diagram of an electronic device 50. As shown in FIG. 5, the electronic device 50 provided in the embodiments of the present application includes a memory 52, a processor 51, and a computer program 53 stored in the memory 52 and executable on the processor 51. When the processor 51 executes the computer program, the steps of the method of the embodiments of the present application are implemented. Figure 5 As shown in FIG. 5, the electronic device 50 provided in the embodiments of the present application includes a memory 52, a processor 51, and a computer program 53 stored in the memory 52 and executable on the processor 51. When the processor 51 executes the computer program, the steps of the method of the embodiments of the present application are implemented.
[0091] The electronic device 50 can be a desktop computer, a notebook computer, a palm computer, a cloud server, and the like. The electronic device 50 can include, but is not limited to, the processor 51 and the memory 52. Those skilled in the art can understand that the electronic device 50 can include more or fewer components, or combine certain components, or include different components, for example, can also include an input / output device, a network access device, and the like. Figure 5 The electronic device 50 is only an example and does not constitute a limitation on the electronic device 50, and can include more or fewer components than those shown in the figure, or combine certain components, or different components, for example, can also include an input / output device, a network access device, and the like.
[0092] The processor 51 can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. The general-purpose processor can be a microprocessor or any conventional processor, etc.
[0093] The memory 52 can be an internal storage unit, such as a hard disk or a memory, in some embodiments. The memory 52 can be a removable / non-removable, volatile / non-volatile computer system storage medium, such as a non-volatile memory, for reading and writing to a non-volatile magnetic medium. The memory 52 can also be an external storage device in other embodiments, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, and the like equipped on the electronic device 50. The memory 52 is used to store an operating system, an application program, a boot loader, data, and other programs, such as program codes of computer programs, and the like. The memory 52 can also be used to temporarily store data that has been output or will be output.
[0094] It should be noted that the information interaction and execution process between the above devices / units are based on the same concept as the method embodiments of the present application, and the specific functions and technical effects brought about can be referred to the method embodiments part, which will not be repeated here.
[0095] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the above-mentioned division of functional units and modules is exemplified, and in actual application, the above-mentioned functions can be completed by different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiments can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of software functional unit. In addition, the specific name of each functional unit and module is only for easy distinction, and does not limit the protection scope of the present application. The specific working process of the unit and module in the system can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.
[0096] The embodiments of the present application also provide a computer readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in each of the above method embodiments are implemented.
[0097] The integrated unit described above, if realized in the form of a software function unit and sold or used as an independent product, can be stored in a computer-readable storage medium. Based on such understanding, the present application realizes all or part of the processes in the above-mentioned embodiment methods, which can be completed by a computer program instructing relevant hardware. The above-mentioned computer program can be stored in a computer-readable storage medium, and when executed by a processor, can realize the steps of the above-mentioned various method embodiments. The computer program includes computer program code, which can be in the form of source code, object code, executable files or some intermediate forms, etc. The computer-readable medium at least includes any entity or device capable of carrying the computer program code to the device / terminal equipment, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal and software distribution medium, such as U disk, mobile hard disk, magnetic disk or optical disk, etc.
[0098] Those skilled in the art can understand that the implementation of all or part of the processes in the above-mentioned embodiment methods can be completed by a computer program instructing relevant hardware, and the program can be stored in a computer-readable storage medium, which, when executed, can include the processes of the above-mentioned various method embodiments. The storage medium can be a magnetic disk, an optical disk, a read-only memory (Rom), a random access memory (RAM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD), etc. The storage medium can also include a combination of the above-mentioned types of memories.
[0099] The present application provides a computer program product, which, when running on a processor, causes the processor to execute the steps of the above-mentioned various method embodiments.
[0100] In the above-mentioned embodiments, the description of each embodiment has its own focus, and the parts not described or recorded in detail in a certain embodiment can be referred to the relevant description of other embodiments.
[0101] Those skilled in the art can understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized in electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.
[0102] In the embodiments provided in the present application, it should be understood that the disclosed apparatus / network device and method can be implemented by other ways. For example, the apparatus / network device embodiments described above are only schematic, for example, the division of the above modules or units is only a logical function division, and there can be another division way in actual implementation, for example, a plurality of units or components 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 between different parts can be indirect couplings or communication connections through some interfaces, devices or units, and can be electrical, mechanical or other forms.
[0103] The units described as separate components above can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.
[0104] The above embodiments are only used to illustrate the technical solutions of the present application, rather than 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 the technical solutions recorded in the foregoing embodiments can be modified, or some technical features can be replaced by equivalents; and these modifications or replacements do not make the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application.
Claims
1. A method of processing fault code data, characterized by, The method comprises the following steps: Obtaining fault code data and fixed header information; wherein the fault code data comprises system identification, fault code number and fault code representation information; Using a preset hash algorithm to perform hash operation processing based on the fixed header information, the system identification and the fault code number to obtain a hash key value; Establishing a mapping relationship between the hash key value and the fault code representation information, and storing the mapping relationship.
2. The method of claim 1, wherein, The method comprises the following steps: Arranging the strings of the fixed header information, the strings of the system identification and the strings of the fault code number in sequence to obtain a composite string; Using a preset hash algorithm to perform hash operation processing on the composite string to obtain a hash key value.
3. The method of claim 1, wherein, The method comprises the following steps: Establishing a mapping relationship between the hash key value and the fault code representation information, performing first encryption processing on the mapping relationship and storing the mapping relationship in a preset mapping dictionary; Performing second encryption processing on the preset mapping dictionary and storing the mapping dictionary in a preset file.
4. The method of claim 1, wherein, The fixed header information is at least one of device information, user information, company information or preset fixed information.
5. The method of claim 1-4, wherein, The method comprises the following steps: In response to a data reading request, obtaining the to-be-verified fixed header information, the to-be-verified system identification and the to-be-verified fault code number in the data reading request; Using the hash algorithm to perform hash operation processing based on the to-be-verified fixed header information, the to-be-verified system identification and the to-be-verified fault code number to obtain a temporary hash key value; Based on the temporary hash key value, searching for the fault code representation information corresponding to the temporary hash key value in the mapping relationship.
6. The method of claim 5, wherein, The method comprises the following steps: Obtaining password information; wherein the password information is generated based on at least one of user information and / or device information; Decrypting the mapping relationship based on the password information; wherein the mapping relationship is stored by being encrypted in advance; Based on the temporary hash key value, searching for the fault code representation information corresponding to the temporary hash key value in the decrypted mapping relationship.
7. The method of claim 5, wherein, The method comprises the following steps: Verifying the integrity of a preset file based on a preset algorithm; wherein the mapping relationship is stored in the preset file; When the preset file is verified to be complete, based on the temporary hash key value, searching for the fault code representation information corresponding to the temporary hash key value in the mapping relationship.
8. A processing device for fault code data, characterized by The method comprises the following steps: An obtaining module is configured to obtain fault code data and fixed header information; wherein the fault code data comprises system identification, fault code number and fault code representation information; The first processing module is configured to perform hash operation processing based on the fixed header information, the system identifier and the fault code number by using a preset hash algorithm to obtain a hash key value. The second processing module is configured to establish a mapping relationship between the hash key value and the fault code representation information, and store the mapping relationship.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The processor executes the computer program to implement the steps of the method according to any one of claims 1 to 7.
10. A computer-readable storage medium storing a computer program, the computer program comprising instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 9. The computer program is executed by the processor to implement the steps of the method according to any one of claims 1 to 7.