Charging packet error correction method, system, device and medium

Abstract

The application relates to the technical field of message data processing, and particularly provides a charging message error correction method, system, device and medium, aiming to solve the technical problem of low charging message error correction efficiency caused by the fact that errors are missed due to human negligence and a long time is spent when manually analyzing the charging message. For this purpose, the charging message error correction method comprises the following steps: acquiring a charging message; translating the charging message to obtain message translation data; checking the charging message according to the message translation data to obtain checking error data; and analyzing the checking error data to obtain a rectification scheme, so that a developer can correct the checking error data according to the rectification scheme.

Description

Technical Field

[0001] This invention relates to the field of message data processing technology, and specifically provides a charging message error correction method, system, device and medium. Background Technology

[0002] In electric vehicle charging systems, charging messages are the core carrier for data interaction between charging piles, electric vehicles, and the back-end management system. Therefore, during the development of charging messages, it is necessary to test them before putting them into use.

[0003] In the existing technology, during the testing of charging messages, the message file is read manually and the fields in the message are checked one by one according to the message protocol. When analyzing a large number of messages, errors are often missed due to human negligence, and the process takes a long time, resulting in the technical problem of low efficiency in correcting charging messages.

[0004] Accordingly, a new method for correcting charging messages is needed in this field to address the aforementioned problems. Summary of the Invention

[0005] In order to overcome the above-mentioned defects, this application is made to provide a solution or at least a partial solution to the technical problem in the prior art that manual analysis of messages is time-consuming and prone to errors, which leads to low efficiency in error correction of charging messages.

[0006] Firstly, this application provides a charging message error correction method, including:

[0007] Obtain charging message;

[0008] The charging message is translated to obtain message translation data;

[0009] Based on the message translation data, the charging message is verified to obtain verification error data;

[0010] The verification error data is analyzed to obtain a rectification plan, which is then used by developers to correct the verification error data.

[0011] In one technical solution of the above-mentioned charging message error correction method, the step of translating the charging message to obtain message translation data includes:

[0012] The charging message data is parsed to obtain a readable message; wherein, the readable message includes a field name and the field content corresponding to the field name;

[0013] Translate the field names to obtain the translated field names data;

[0014] The content of the field is interpreted to obtain the interpreted data;

[0015] The translated data of the field names and the interpreted data are combined to obtain the message translation data.

[0016] In one technical solution of the above-mentioned charging message error correction method, the step of parsing the charging message data to obtain a readable message includes:

[0017] Remove special characters from the charging message to obtain a standard charging message;

[0018] The standard charging message is converted into a string to obtain a readable message.

[0019] In one technical solution of the above-mentioned charging message error correction method, the step of verifying the charging message based on the message translation data to obtain verification error data includes:

[0020] For any field name and the corresponding field content in the readable message, the format of the field name is validated based on the translated data of the field name to obtain field name validation data;

[0021] Based on the translated data and the interpretation data of the field content, the value of the field content is verified to obtain field content verification data;

[0022] According to the preset verification algorithm, the checksum in the readable message is verified to obtain the checksum verification data.

[0023] In one technical solution of the above-mentioned charging message error correction method, the step of analyzing the verification error data to obtain a rectification plan includes:

[0024] The verification error data is classified to obtain the error type of the verification error data;

[0025] Based on the error type, a rectification plan corresponding to the error type is obtained from the preset correspondence between error types and rectification plans.

[0026] In one technical solution of the above-mentioned charging message error correction method, after obtaining the charging message, the method further includes:

[0027] The charging message is calculated according to the preset verification rules to obtain the actual verification value;

[0028] The actual verification value is compared with the preset verification value to obtain the encoding format verification result;

[0029] If the encoding format verification result is different, the charging message is invalid and a new charging message is obtained.

[0030] In one technical solution of the above-mentioned charging message error correction method, after verifying the charging message based on the message translation data to obtain verification error data, the method further includes:

[0031] The verification error data is evaluated based on a preset error severity level to obtain the error degree of the verification error data;

[0032] The verification error data is sorted according to the degree of error to obtain sorted verification error data;

[0033] Display the sorting and verification error data.

[0034] Secondly, this application provides a charging message error correction system, comprising: an acquisition module, a translation module, a verification module, and an analysis module, wherein,

[0035] The acquisition module is used to acquire charging messages;

[0036] The translation module is used to translate the charging message to obtain message translation data;

[0037] The verification module is used to verify the charging message based on the message translation data and obtain verification error data.

[0038] The analysis module is used to analyze the verification error data and obtain a rectification plan, so that developers can correct the verification error data according to the rectification plan.

[0039] Thirdly, this application provides a charging message error correction device, including at least one processor and a memory; wherein,

[0040] The memory stores computer-executed instructions;

[0041] The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the method described in any one of the first aspects.

[0042] Fourthly, this application provides a computer-readable storage medium storing a plurality of program codes adapted to be loaded and run by a processor to perform the method described in any one of the first aspects.

[0043] This application provides a charging message error correction method, system, device, and medium. The method includes: acquiring a charging message; translating the charging message to obtain message translation data; verifying the charging message based on the message translation data to obtain verification error data; and analyzing the verification error data to obtain a rectification plan, which allows developers to correct the verification error data according to the rectification plan, thereby improving the efficiency of charging message error correction. Attached Figure Description

[0044] The disclosure of this application will become more readily understood with reference to the accompanying drawings. It will be readily understood by those skilled in the art that these drawings are for illustrative purposes only and are not intended to limit the scope of protection of this application. Furthermore, similar numbers in the drawings are used to denote similar components, wherein:

[0045] Figure 1 This is a flowchart of a charging message error correction method according to an embodiment of this application;

[0046] Figure 2 This is a flowchart of a second embodiment of a charging message error correction method provided in this application.

[0047] Figure 3 This is a flowchart of a third embodiment of a charging message error correction method provided in this application.

[0048] Figure 4 This is a flowchart of a fourth embodiment of a charging message error correction method provided in this application;

[0049] Figure 5 This is a flowchart of a fifth embodiment of a charging message error correction method provided in this application.

[0050] Figure 6 This is a flowchart of a sixth embodiment of a charging message error correction method provided in this application;

[0051] Figure 7 This is a flowchart of Embodiment Seven of a charging message error correction method provided in this application;

[0052] Figure 8 This is a structural diagram of a charging message error correction system provided in an embodiment of this application;

[0053] Figure 9 This is a schematic diagram of the structure of a charging message error correction device provided in an embodiment of this application.

[0054] List of reference numerals in the attached diagram:

[0055] 1: Acquisition module; 2: Translation module; 3: Verification module; 4: Analysis module; 5: Processor; 6: Memory. Detailed Implementation

[0056] Some embodiments of this application are described below with reference to the accompanying drawings. Those skilled in the art should understand that these embodiments are merely illustrative of the technical principles of this application and are not intended to limit the scope of protection of this application.

[0057] In the description of this application, "module" and "processor" can include hardware, software, or a combination of both. A module can include hardware circuitry, various suitable sensors, communication ports, memory, and can also include software components, such as program code, or a combination of software and hardware. A processor can be a central processing unit, microprocessor, image processor, digital signal processor, or any other suitable processor. The processor has data and / or signal processing capabilities. The processor can be implemented in software, in hardware, or a combination of both. Non-transitory computer-readable storage media includes any suitable medium capable of storing program code, such as magnetic disks, hard disks, optical disks, flash memory, read-only memory, random access memory, etc. The term "A and / or B" means all possible combinations of A and B, such as only A, only B, or A and B. The terms "at least one A or B" or "at least one of A and B" have a similar meaning to "A and / or B" and can include only A, only B, or A and B. The singular terms "a" or "this" can also include plural forms.

[0058] Currently, manually analyzing and correcting charging messages during testing can cause the following problems:

[0059] Manually verifying each field in the charging message against the charging protocol is time-consuming and prone to errors due to oversight, thus reducing the accuracy of charging message error correction.

[0060] When it is determined that the fields in the charging message are inconsistent with the charging protocol, the errors are manually summarized, the causes are analyzed, and a rectification plan is formulated. This process is cumbersome and the rectification plan lacks a unified standard, which leads to the problem that the corrected charging message still cannot pass the test.

[0061] Based on this, in order to solve the above-mentioned technical problems, the technical concept of this application is to provide a new method for correcting errors in charging messages, so as to improve the error correction efficiency of charging messages.

[0062] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0063] Figure 1 This is a flowchart of an embodiment of a charging message error correction method provided in this application. Figure 1 As shown, the method includes:

[0064] Step S101: Obtain the charging message.

[0065] In this embodiment, during the operation of the charging pile and the back-end management system, the charging messages between the charging pile, the back-end management system and the electric vehicle can be automatically obtained by the packet capture tool.

[0066] Step S102: Translate the charging message to obtain message translation data.

[0067] In this embodiment, the charging message includes fields and their corresponding content. The fields and their corresponding content are generally data such as strings, numbers, and symbols. The true meaning of the fields and their corresponding content cannot be known from the charging message. Therefore, the fields and their corresponding content in the charging message can be translated according to a preset charging protocol to obtain message translation data.

[0068] Step S103: Verify the charging message based on the message translation data to obtain verification error data.

[0069] In this embodiment, the translation of the fields and their corresponding content in the translation data is compared one by one with the fields and their corresponding content in the charging message, and data with verification errors is recorded.

[0070] Step S104: Analyze the verification error data to obtain a rectification plan, so that the developers can correct the verification error data according to the rectification plan.

[0071] In this embodiment, by comparing the verification error data with the corresponding data in the charging protocol, a rectification plan for the verification error data is determined, and then the developers correct the verification error data according to the rectification plan.

[0072] In this embodiment, a charging message is acquired; the charging message is translated to obtain message translation data; the charging message is verified based on the message translation data to obtain verification error data; the verification error data is analyzed to obtain a rectification plan, which is then used by developers to correct the verification error data. Compared with the prior art, where manual analysis of charging messages is time-consuming and prone to errors due to human negligence, resulting in low efficiency in charging message error correction, this application automates the process by translating the charging message to obtain message translation data, then verifying the charging message based on the message translation data to obtain verification error data, then analyzing the verification error data to obtain a rectification plan, and finally having developers correct the verification error data according to the rectification plan. This process can be completed automatically without manual operation, significantly improving the efficiency of charging message error correction and reducing labor costs.

[0073] Figure 2 This is a flowchart of a second embodiment of a charging message error correction method provided in this application. Based on the above embodiments, as follows... Figure 2 As shown, the specific implementation of step S102 includes:

[0074] Step S201: Parse the charging message data to obtain a readable message.

[0075] In this embodiment, the charging message is hexadecimal data. By converting the hexadecimal data, a readable message is obtained.

[0076] In this embodiment, a readable message includes the field names and corresponding field contents in the message header, message data, and message footer.

[0077] Step S202: Translate the field names to obtain translated field name data.

[0078] In this embodiment, according to a preset message protocol, the field name is translated into Chinese, and the meaning of the field corresponding to the field name is also translated into Chinese, thereby obtaining the field name translation data.

[0079] In this embodiment, there can be multiple preset message protocols, which can be updated according to different charging protocol standards, and new field mapping relationships and data interpretation rules can be added to adapt to the charging message translation needs in different scenarios.

[0080] Step S203: Interpret the field content to obtain interpreted data.

[0081] In this embodiment, the field content is interpreted in Chinese to obtain interpreted data.

[0082] For example, the field content "500" can be translated as "charging voltage: 500V (value range 0~1000V)".

[0083] Step S204: Combine the translated data of the field names and the interpretation data to obtain the message translation data.

[0084] In this embodiment, the translated data of the field name and the interpretation data are combined into a single string to obtain the message translation data.

[0085] In this embodiment, the obtained message translation data needs to be associated with the charging message for developers to compare and view. At the same time, the message translation data can be exported as tabular data.

[0086] In this embodiment, the charging message data is parsed to obtain a readable message; wherein, the readable message includes field names and field contents corresponding to the field names; the field names are translated to obtain field name translation data; the field contents are interpreted to obtain interpretation data; the field name translation data and interpretation data are combined to obtain message translation data, so as to improve the readability of the charging message data.

[0087] Figure 3 This is a flowchart of a third embodiment of a charging message error correction method provided in this application. Based on the above embodiments, as follows... Figure 3 As shown, the specific implementation of step S201 includes:

[0088] Step S301: Remove special characters from the charging message to obtain a standard charging message.

[0089] In this embodiment, special characters are preset. Each character in the charging message is compared with the preset special characters. If the comparison is successful, the special characters are removed. After deleting all special characters in the charging message, a standard charging message is obtained.

[0090] Step S302: Convert the standard charging message into a string to obtain a readable message.

[0091] In this embodiment, the standard charging message is hexadecimal data. This hexadecimal data is converted into string data to obtain a readable message.

[0092] In this embodiment, special characters are removed from the charging message to obtain a standard charging message; the standard charging message is then converted into a string to obtain a readable message, thereby improving the translation accuracy of the charging message.

[0093] Figure 4 This is a flowchart of a fourth embodiment of a charging message error correction method provided in this application. Based on the above embodiments, as follows... Figure 4As shown, the specific implementation of step S103 includes:

[0094] Step S401: For any field name and its corresponding field content in a readable message, translate the data according to the field name, validate the format of the field name, and obtain the field name validation data.

[0095] In this embodiment, each field name and its corresponding field content in the readable message is verified individually.

[0096] In this embodiment, the field name format is validated according to the field format and field name translation data specified in the preset protocol to obtain field name validation data.

[0097] Step S402: Based on the translated and interpreted data of the field content, validate the value of the field content to obtain the field content validation data.

[0098] In this embodiment, specifically, the data value characteristics corresponding to the translated data of the field content are obtained from the interpreted data, and the data value characteristics are compared with the field content to obtain the field content verification data.

[0099] In this embodiment, if the content of the field is a fixed value, it is necessary to compare the value of the field content in the preset protocol with the field content; if the field content has a range of values, it is determined whether the value of the field content is within the range of values.

[0100] Step S403: Verify the checksum in the readable message according to the preset verification algorithm to obtain the checksum verification data.

[0101] In this embodiment, for the checksum at the end of the message, the actual checksum is obtained according to the preset checksum algorithm specified in the charging protocol, and the actual checksum is compared with the checksum to determine whether the message data is distorted.

[0102] In this embodiment, the format and integrity of the fields can also be verified to determine whether the field format meets the requirements of the charging protocol and whether the charging message is complete.

[0103] During the verification process, relevant information about erroneous data in the field name verification data, field content verification data, and verification code verification data is automatically recorded. This relevant information includes message sequence number, field name, charging message, and message translation data, ensuring the integrity and traceability of erroneous data and avoiding omissions of errors.

[0104] In this embodiment, for any field name and its corresponding field content in a readable message, the format of the field name is validated based on the translated data of the field name to obtain field name validation data; the value of the field content is validated based on the translated and interpreted data of the field content to obtain field content validation data; and the checksum in the readable message is validated based on a preset validation algorithm to obtain checksum validation data, thereby enabling accurate and rapid validation of charging messages.

[0105] Figure 5 This is a flowchart of a fifth embodiment of a charging message error correction method provided in this application. Based on the above embodiments, as follows... Figure 5 As shown, specifically, in step S104, the verification error data is analyzed to obtain the implementation method of the rectification plan, including:

[0106] Step S501: Classify the verification error data to obtain the error type of the verification error data.

[0107] In this embodiment, the verification error data is classified according to preset error types to obtain the error types of the verification error data. Among them, the preset error types include fixed value errors, range errors, and format errors, etc.

[0108] Step S502: Based on the error type, obtain the rectification plan corresponding to the error type from the preset correspondence between error types and rectification plans.

[0109] In this embodiment, there is a pre-defined correspondence between error types and rectification solutions. From this correspondence, a rectification solution matching the error type is obtained.

[0110] For example, if the error type is "charging voltage out of range", the corresponding rectification plan is to "check the charging pile voltage detection module, calibrate the voltage sensor, and adjust the charging parameters to the range specified in the protocol"; if the error type is "check code error", the corresponding rectification plan is to "retransmit the message, check whether there is interference in the transmission link, and investigate the abnormality of the message generation algorithm".

[0111] In this embodiment, the verification error data is classified to obtain the error type of the verification error data; according to the error type, the corresponding rectification plan is obtained from the preset correspondence between error type and rectification plan, and then an accurate rectification plan is obtained for the verification error data.

[0112] Figure 6 This is a flowchart of a sixth embodiment of a charging message error correction method provided in this application. Based on the above embodiments, as follows... Figure 6 As shown, specifically, after step S101, the method further includes:

[0113] Step S601: Calculate the charging message according to the preset verification rules to obtain the actual verification value.

[0114] In this embodiment, the charging message is calculated according to the preset verification rules corresponding to the charging protocol to obtain the actual verification value.

[0115] Step S602: Compare the actual check value with the preset check value to obtain the encoding format check result.

[0116] In this embodiment, the charging message is hexadecimal data, which includes a message header, message data, and a message tail. The checksum contained in the message tail is a preset check value.

[0117] In this embodiment, the actual verification value is compared with the preset verification value to determine whether the two are the same.

[0118] Step S603: If the encoding format verification result is different, the charging message is invalid and the charging message is re-acquired.

[0119] In this embodiment, if the encoding format verification result is different, the charging message may fail to be read or contain garbled characters due to encoding mismatch. In this case, the charging message is invalid and no further error correction will be performed. Instead, the next charging message will be obtained again.

[0120] In this embodiment, the charging message is calculated according to the preset verification rules to obtain the actual verification value; the actual verification value is compared with the preset verification value to obtain the encoding format verification result; if the encoding format verification result is different, the charging message is invalid and the charging message is re-acquired.

[0121] Figure 7 This is a flowchart of Embodiment Seven of a charging message error correction method provided in this application. Based on the above embodiments, as... Figure 7 As shown, specifically, after step S103, the method includes:

[0122] Step S701: Evaluate the verification error data according to the preset error severity to obtain the error degree of the verification error data.

[0123] In this embodiment, a preset severity level for the verification error data is defined, including fatal errors, critical errors, and general errors. The verification error data is evaluated based on this preset severity level to determine its degree of error. For example, "incorrect checksum" or "incorrect message start character" are fatal errors because they affect the validity of the entire message; "voltage exceeds safe range" is a critical error; and "missing recommendation fields for non-critical information" is a general error.

[0124] Step S702: Sort the verification error data according to the degree of error to obtain sorted verification error data.

[0125] In this embodiment, the verification error data is sorted from highest to lowest according to its error severity to obtain sorted verification error data.

[0126] Step S703: Display the sorting and verification error data.

[0127] In this embodiment, the sorted verification error data is displayed on the developer's terminal, and the verification error data with high error severity is displayed at the top, so that staff can prioritize viewing and handling verification error data that affects charging safety.

[0128] In this embodiment, the verification error data is evaluated according to a preset error severity level to obtain the error degree of the verification error data; the verification error data is sorted according to the error degree to obtain sorted verification error data; the sorted verification error data is displayed by classifying the verification error data to obtain the error degree, and sorting it from high to low according to the error degree, and displaying the sorted verification error data to the developers so that the developers can prioritize viewing and processing verification error data that affects charging safety, thereby improving error correction efficiency.

[0129] It should be noted that although the steps in the above embodiments are described in a specific order, those skilled in the art will understand that in order to achieve the effect of this application, different steps do not necessarily have to be executed in such an order. They can be executed simultaneously (in parallel) or in other orders, and these variations are all within the scope of protection of this application.

[0130] Furthermore, this application also provides a charging message error correction system.

[0131] Figure 8 This is a structural diagram of a charging message error correction system provided in an embodiment of this application. Figure 8 As shown, the charging message error correction system in this embodiment mainly includes an acquisition module 1, a translation module 2, a verification module 3, and an analysis module 4. The acquisition module 1 is configured to acquire charging messages. The translation module 2 is configured to translate the charging messages to obtain translated message data. The verification module 3 is configured to verify the charging messages based on the translated message data to obtain verification error data. The analysis module is configured to analyze the verification error data to obtain rectification plans, which developers can then use to correct the verification error data.

[0132] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments of this application can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable file, or some intermediate form. The computer-readable storage medium can include any entity or device capable of carrying the computer program code, a medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory, a random access memory, an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0133] Furthermore, this application also provides a charging message error correction device.

[0134] Figure 9 This is a schematic diagram of the structure of a charging message error correction device provided in an embodiment of this application. Figure 9 As shown, the charging device includes a processor 5 and a memory 6. The memory 6 can be configured to store a program for executing the charging message error correction method of the above-described method embodiments. The processor 5 can be configured to execute the program stored in the memory, which includes, but is not limited to, a program for executing the charging message error correction method of the above-described method embodiments. For ease of explanation, only the parts related to the embodiments of this application are shown. For specific technical details not disclosed, please refer to the method section of the embodiments of this application. The charging message error correction device can be a control device device comprising various electronic devices.

[0135] Furthermore, this application also provides a computer-readable storage medium. In one embodiment of the computer-readable storage medium according to this application, the computer-readable storage medium can be configured to store a program that performs the charging message error correction method of the above-described method embodiment. This program can be loaded and run by a processor to implement the above-described charging message error correction method. For ease of explanation, only the parts related to the embodiments of this application are shown; for specific technical details not disclosed, please refer to the method section of the embodiments of this application. The computer-readable storage medium can be a storage device device comprising various electronic devices. Optionally, in the embodiments of this application, the computer-readable storage medium is a non-transitory computer-readable storage medium.

[0136] Furthermore, it should be understood that since the various modules are only provided to illustrate the functional units of the device described in this application, the physical devices corresponding to these modules may be the processor itself, or a part of the processor's software, hardware, or a combination of both. Therefore, the number of modules shown in the figures is merely illustrative.

[0137] Those skilled in the art will understand that the various modules in the device can be adaptively split or combined. Such splitting or combining of specific modules will not cause the technical solution to deviate from the principles of this application; therefore, the technical solutions after splitting or combining will fall within the protection scope of this application.

[0138] The technical solution of the present invention has been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to these specific embodiments. Without departing from the principles of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after such changes or substitutions will all fall within the scope of protection of the present invention.

Claims

1. A method for correcting errors in charging messages, characterized in that, include: Obtain charging message; The charging message is translated to obtain message translation data; Based on the message translation data, the charging message is verified to obtain verification error data; The verification error data is analyzed to obtain a rectification plan, which is then used by developers to correct the verification error data.

2. The method according to claim 1, characterized in that, The process of translating the charging message to obtain message translation data includes: The charging message data is parsed to obtain a readable message; wherein, the readable message includes a field name and the field content corresponding to the field name; The field names are translated to obtain the translated field names data; The content of the field is interpreted to obtain the interpreted data; The translated data of the field names and the interpreted data are combined to obtain the message translation data.

3. The method according to claim 2, characterized in that, The step of parsing the charging message data to obtain a readable message includes: Remove special characters from the charging message to obtain a standard charging message; The standard charging message is converted into a string to obtain a readable message.

4. The method according to claim 2, characterized in that, The step of verifying the charging message based on the message translation data to obtain verification error data includes: For any field name in the readable message and the field content corresponding to the field name, the format of the field name is validated based on the translated data of the field name to obtain field name validation data; Based on the translated data and the interpretation data of the field content, the value of the field content is verified to obtain field content verification data; According to the preset verification algorithm, the checksum in the readable message is verified to obtain the checksum verification data.

5. The method according to claim 1, characterized in that, The step of analyzing the verification error data to obtain a rectification plan includes: The verification error data is classified to obtain the error type of the verification error data; Based on the error type, a rectification plan corresponding to the error type is obtained from the preset correspondence between error types and rectification plans.

6. The method according to claim 1, characterized in that, After obtaining the charging message, the method further includes: The charging message is calculated according to the preset verification rules to obtain the actual verification value; The actual verification value is compared with the preset verification value to obtain the encoding format verification result; If the encoding format verification result is different, the charging message is invalid and a new charging message is obtained.

7. The method according to claim 1, characterized in that, After verifying the charging message based on the message translation data and obtaining verification error data, the method further includes: The verification error data is evaluated based on a preset error severity level to obtain the error degree of the verification error data; The verification error data is sorted according to the degree of error to obtain sorted verification error data; Display the sorting and verification error data.

8. A charging message error correction system, characterized in that, include: The module includes an acquisition module, a translation module, a verification module, and an analysis module. The acquisition module is used to acquire charging messages; The translation module is used to translate the charging message to obtain message translation data; The verification module is used to verify the charging message based on the message translation data and obtain verification error data. The analysis module is used to analyze the verification error data and obtain a rectification plan, so that developers can correct the verification error data according to the rectification plan.

9. A charging message error correction device, comprising at least one processor and a memory; wherein, The memory stores computer-executed instructions; The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the method of any one of claims 1 to 7.

10. A computer-readable storage medium storing a plurality of program codes, characterized in that, The program code is adapted to be loaded and run by a processor to perform the method of any one of claims 1 to 7.

Images