Call bill file analysis method and device, electronic equipment and storage medium
When the matching of the version number of the call document file and the preconfigured model file of the NetEase Tool fails, preset rules are used to determine the target model file from multiple model files for parsing, which solves the problem that the NetEase Tool cannot parse the call document file, and improves the parsing ratio of the call document file and the network optimization operation and maintenance efficiency.
Patent Information
- Application Number
- CN202410184194.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-02-19
- Publication Date
- 2025-08-19
AI Technical Summary
In the prior art, when the network optimization tool fails to update the model file in time, the base station version number cannot be changed, and the call list file cannot be parsed, resulting in the loss of analysis results and affecting the network optimization operation and maintenance work.
When the matching of the version number of the call document file and the version number of the preconfigured model file by the Network Excellence Tool fails, the target model file is determined from multiple model files through preset rules for parsing, and the most suitable model file is found in a loose matching method for parsing the call document file.
It has improved the parsing ratio of call sheet files, effectively solved the problem that the call sheet analysis tool cannot parse call sheet files, and has caused the loss of analysis results, and improved the efficiency of network optimization operation and maintenance.
Smart Images
Figure CN120508291A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a method, device, electronic device and storage medium for parsing call record files. Background Art
[0002] Network optimization tools need to parse base station call record files for analysis. The call record file encoding format is described in a model file. Different base station versions require different model files.
[0003] Related technologies parse call records by strictly matching the call record version number with the version number of the model file preconfigured in the network optimization tool. If the call record version number changes due to a base station upgrade in the live network, and the network optimization tool fails to update the model file in a timely manner, the tool will be unable to parse the call record file, resulting in loss of analysis results and impacting network optimization and maintenance. Summary of the Invention
[0004] Embodiments of the present application provide a call record file parsing method, device, electronic device, and storage medium.
[0005] In a first aspect, an embodiment of the present application provides a method for parsing a call record file, comprising:
[0006] Get the call record file to be parsed;
[0007] Matching the version number in the call record file with the version numbers of multiple model files in the call record parsing tool to obtain a matching result;
[0008] When the matching result is a matching failure, a target model file is determined from the multiple model files according to a preset rule, and the call record file is parsed.
[0009] Optionally, according to the call record file parsing method of an embodiment of the present application, determining the target model file from the multiple model files according to a preset rule includes:
[0010] Determine, from the version numbers of the multiple model files, a target version number closest to the version number in the call record file;
[0011] The model file corresponding to the target version number is determined as the target model file.
[0012] Optionally, according to the call record file parsing method of an embodiment of the present application, determining, from the version numbers of the multiple model files, a target version number closest to the version number in the call record file includes:
[0013] Determining at least one candidate model file from the multiple model files; the product corresponding to the version number of the candidate model file is the same as the product corresponding to the version number in the call record file;
[0014] From the version numbers of the candidate model files, determine a target version number that is closest to the version number in the call record file.
[0015] Optionally, according to the call record file parsing method of an embodiment of the present application, determining the model file corresponding to the target version number as the target model file includes:
[0016] When the first field in the call record file parsed based on the model file corresponding to the target version number is the same as the first field marked in the message header of the call record file, the model file corresponding to the target version number is determined as the target model file; the first field is the "message type" field.
[0017] Optionally, the method for parsing a call record file according to an embodiment of the present application further includes:
[0018] If the target model file cannot be determined from the multiple model files according to the preset rule, the call record file is discarded.
[0019] In a second aspect, an embodiment of the present application further provides an electronic device, including a memory, a transceiver, and a processor:
[0020] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:
[0021] Get the call record file to be parsed;
[0022] Matching the version number in the call record file with the version numbers of multiple model files in the call record parsing tool to obtain a matching result;
[0023] When the matching result is a matching failure, a target model file is determined from the multiple model files according to a preset rule, and the call record file is parsed.
[0024] Optionally, in an electronic device according to an embodiment of the present application, determining a target model file from the multiple model files according to a preset rule includes:
[0025] Determine, from the version numbers of the multiple model files, a target version number closest to the version number in the call record file;
[0026] The model file corresponding to the target version number is determined as the target model file.
[0027] Optionally, in an electronic device according to an embodiment of the present application, determining, from the version numbers of the multiple model files, a target version number closest to the version number in the call record file includes:
[0028] Determining at least one candidate model file from the multiple model files; the product corresponding to the version number of the candidate model file is the same as the product corresponding to the version number in the call record file;
[0029] From the version numbers of the candidate model files, determine a target version number that is closest to the version number in the call record file.
[0030] Optionally, in an electronic device according to an embodiment of the present application, determining the model file corresponding to the target version number as the target model file includes:
[0031] When the first field in the call record file parsed based on the model file corresponding to the target version number is the same as the first field marked in the message header of the call record file, the model file corresponding to the target version number is determined as the target model file; the first field is the "message type" field.
[0032] Optionally, according to an electronic device of an embodiment of the present application, when the target model file cannot be determined from the multiple model files according to a preset rule, the call record file is discarded.
[0033] In a third aspect, an embodiment of the present application further provides a device, including:
[0034] The acquisition module is used to obtain the call record file to be parsed;
[0035] The matching module is used to match the version number in the call record file with the version numbers of multiple model files in the call record parsing tool to obtain a matching result.
[0036] The parsing module is used to determine a target model file from the multiple model files according to a preset rule and parse the call record file when the matching result is a matching failure.
[0037] Optionally, the parsing module is specifically configured to: determine, from the version numbers of the multiple model files, a target version number that is closest to the version number in the call record file;
[0038] The model file corresponding to the target version number is determined as the target model file.
[0039] Optionally, the parsing module is specifically configured to: determine at least one candidate model file from the multiple model files; the product corresponding to the version number of the candidate model file is the same as the product corresponding to the version number in the call record file;
[0040] From the version numbers of the candidate model files, determine a target version number that is closest to the version number in the call record file.
[0041] Optionally, the parsing module is specifically used to: when the first field in the call record file parsed based on the model file corresponding to the target version number is the same as the first field marked in the message header of the call record file, determine the model file corresponding to the target version number as the target model file; the first field is the "message type" field.
[0042] Optionally, the parsing module is specifically configured to discard the call record file if the target model file cannot be determined from the multiple model files according to a preset rule.
[0043] In a fourth aspect, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the steps of the call record file parsing method described in the first aspect above.
[0044] The embodiments of the present application provide a call record file parsing method, device, electronic device, and storage medium. When the version number in the call record file fails to strictly match the version number of the model file pre-configured by the call record parsing tool, a most suitable model file is found from multiple pre-configured model files based on preset rules to parse the call record, thereby greatly improving the parsing ratio of the call record file, effectively solving the problem of loss of analysis results caused by the call record parsing tool's inability to parse the call record file, and improving the efficiency of network optimization and operation and maintenance. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.
[0046] Figure 1 This is a flow chart of a method for parsing a call record file provided in an embodiment of the present application;
[0047] Figure 2 This is a schematic diagram of the call record file format provided in an embodiment of the present application;
[0048] Figure 3 is a structural diagram of an electronic device provided in an embodiment of the present application;
[0049] Figure 4 It is a structural diagram of the call record file parsing device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0050] In the embodiments of this application, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.
[0051] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.
[0052] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.
[0053] Figure 1 This is one of the flow charts of the method for parsing a call log file provided in the embodiment of the present application. Figure 1 As shown, including:
[0054] Step 101: Obtain the call record file to be parsed;
[0055] Specifically, in order to implement the parsing of the call log file, the embodiment of the present application first obtains the call log file to be parsed. The call log file records the 3GPP standard interface message and the internal message between the functional modules of the base station. The file format is as follows: Figure 2 As shown, the message header uses a fixed format, while the message body varies depending on the message type. The call record file format is described by a model file. If the base station version is different, the model file will also be different.
[0056] Step 102: Match the version number in the call record file with the version numbers of multiple model files in the call record parsing tool to obtain a matching result;
[0057] Specifically, after obtaining the call bill file to be parsed, in the embodiment of the present application, the version number of the call bill file is matched with the version numbers of multiple model files pre-configured in the call bill parsing tool to obtain a matching result. Optionally, after extracting the call bill file from the existing network, the version number information can be parsed from the call bill file header and compared with the model file pre-configured in the call bill parsing tool to obtain a matching result. Optionally, the call bill parsing tool can be a network optimization tool, which mainly parses 3GPP standard messages, and the frequency of changes in the structure of such messages is very small; the current full amount of base station version model files can be pre-configured in the call bill parsing tool; the model file version number contains information such as product serial, model, specific version, etc., and through segmented value taking, the version numbers of different products are separated, and the version numbers of the evolutionary versions of the same product are adjacent.
[0058] Step 103: If the matching result is a match failure, determine the target model file from the multiple model files according to a preset rule, and parse the dialog file.
[0059] Specifically, in related technologies, when matching the version number in a call record file with the version number of a preconfigured model file in the call record parsing tool, if there is a match, the call record file is parsed using the corresponding model file. If the match fails, meaning no matching model file can be found, the call record file is discarded and not parsed. If the call record version number changes due to an upgrade of some base stations in the existing network, and the call record parsing tool fails to update the model file in a timely manner, the call record parsing tool will be unable to parse the call record file, resulting in loss of analysis results, which will impact network optimization and operation and maintenance.
[0060] In order to solve the above problems, in the embodiment of the present application, when the matching result is a matching failure, the target model file is determined from multiple model files pre-configured in the call record parsing tool according to preset rules, and the call record file is parsed; optionally, the preset rule can be to use the latest version of the model file pre-configured in the call record parsing tool as the target model file, and perform file parsing on the call record; it can also be to use the most frequently used version model file in the call record parsing tool as the target model file, and perform file parsing on the call record, or it can be other preset rules, which are not limited in the embodiment of the present application.
[0061] It should be noted that in the existing technology, during the process of parsing the call record file, the version number of the call record file and the version numbers of multiple model files pre-configured by the call record parsing tool are strictly matched, and the call record file is only parsed if the match is 100% successful; if the match fails, the parsing of the call record file is abandoned, and no parsed data of the call record file can be obtained, and further analysis of the call record and analysis and troubleshooting of the problem cannot be performed. In the present application, the target model file is determined from multiple model files pre-configured by the call record parsing tool according to preset rules, and the call record file is parsed. That is, when strict matching fails, the parsing of the call record file is not simply abandoned directly. Instead, based on the preset rules, a most suitable model file is found from multiple model files pre-configured by the call record parsing tool through loose matching to parse the call record file. Even if the parsing accuracy is not 100%, some common content in the call record can be parsed through the target model file, thereby providing data support for the analysis of call record problems, greatly improving the parsing ratio of call record files, and effectively solving the problem of loss of analysis results due to the call record parsing tool's inability to parse the call record file, improving the efficiency of network optimization and operation and maintenance, and overcoming the problem of being unable to parse the call record file when the specific base station version model file is not pre-configured in the network optimization tool.
[0062] The method of the above embodiment, when the version number in the call record file fails to strictly match the version number of the model file pre-configured by the call record parsing tool, finds the most suitable model file from multiple pre-configured model files based on preset rules to parse the call record, thereby greatly improving the parsing ratio of the call record file while ensuring correct parsing, effectively solving the problem of loss of analysis results caused by the call record parsing tool's inability to parse the call record file, and improving the efficiency of network optimization and operation and maintenance.
[0063] In one embodiment, determining a target model file from a plurality of model files according to a preset rule includes:
[0064] Determine, from the version numbers of the multiple model files, a target version number that is closest to the version number in the call record file;
[0065] The model file corresponding to the target version number is determined as the target model file.
[0066] Specifically, in the process of determining the target model file from multiple model files according to preset rules, the embodiment of the present application can, based on the characteristics of version iteration and continuation, use the version number of the model file closest to the version number of the call record file from the version numbers corresponding to the multiple model files pre-configured by the call record parsing tool as the target version number, so that the model file based on the target version number can parse the call record file to the maximum extent, while improving the call record parsing ratio, and can also effectively improve the accuracy and completeness of the call record parsing, thereby effectively improving the efficiency of network optimization and operation and maintenance, and solving the problem of loss of analysis results caused by the call record parsing tool being unable to parse the call record file. Optionally, the target version number can be a version number adjacent to the version number of the call record file.
[0067] The method of the above embodiment determines the target version number closest to the version number in the call record file from the version numbers of multiple model files pre-configured by the call record parsing tool, and then the call record file can be parsed to the maximum extent based on the target model file corresponding to the target version number. While improving the call record parsing ratio, it can also effectively improve the accuracy and completeness of the call record parsing, and solve the problem of the call record parsing tool being unable to parse the call record file and causing the loss of analysis results.
[0068] In one embodiment, determining a target version number closest to a version number in a call record file from version numbers of a plurality of model files includes:
[0069] Determine at least one candidate model file from the multiple model files; the product corresponding to the version number of the candidate model file is the same as the product corresponding to the version number in the call record file;
[0070] From the version numbers of the candidate model files, determine the target version number that is closest to the version number in the call record file.
[0071] Specifically, in the process of determining the target version number closest to the version number in the call bill file from the version numbers of multiple model files pre-configured by the call bill parsing tool, the embodiment of the present application first determines that the product corresponding to the version number of the call bill file is A (such as a 4G product), and then finds all candidate model files from the multiple model files pre-configured by the call bill parsing tool, wherein the product corresponding to the version number of the candidate model files is also A; finally, the target version number closest to the version number of the call bill file is determined from all candidate model files. That is, in the process of determining the target version number closest to the version number in the call bill file, the embodiment of the present application will preliminarily screen the multiple model files pre-configured by the call bill parsing tool based on the product corresponding to the version number of the call bill file, and the product corresponding to the version number of the screened candidate model files is also A; thus, it is only necessary to determine the target model file closest to the version number of the call bill file from the screened candidate model files, which effectively narrows the determination range of the target model file and improves the determination efficiency of the target model file. Then, the target model file determined according to the above method can also parse the call bill file more quickly, thereby improving the efficiency of network optimization and operation and maintenance.
[0072] The method of the above embodiment, in the process of determining the target version number closest to the version number in the call record file from the version numbers of multiple model files pre-configured by the call record parsing tool, preliminarily screens the multiple model files pre-configured by the call record parsing tool through the product corresponding to the version number of the call record file, and then only needs to determine the target model file closest to the version number of the call record file from the screened candidate model files, which effectively narrows the scope of determining the target model file and improves the efficiency of determining the target model file.
[0073] In one embodiment, determining the model file corresponding to the target version number as the target model file includes:
[0074] When the first field in the call record file parsed based on the model file corresponding to the target version number is the same as the first field marked in the message header of the call record file, the model file corresponding to the target version number is determined as the target model file; the first field is the "message type" field.
[0075] Specifically, in the process of determining a target model file, the embodiment of the present application, based on finding the target version number closest to the version number of the call record file from the pre-configured multiple model file versions through a loose matching method, further verifies whether the first field in the call record file parsed based on the model file corresponding to the target version number is the same as the first field marked in the message header of the call record file. Only when the first field in the call record file parsed based on the model file corresponding to the target version number is the same as the first field marked in the message header of the call record file, indicating that the selected model file can correctly parse the call record file and there is no difference in 3GPP standard messages, is the model file corresponding to the target version number determined as the target model file. This effectively avoids the time and resource consumption caused by parsing the call record file with an unverified model file, but failing to parse the call record file or incorrectly parsing the call record file. In other words, the present application combines the loose matching, candidate model file screening, and verification methods to more efficiently and accurately determine the target model file for parsing the call record file. Then, based on the determined target model file, the call record file can be effectively parsed, thereby improving the parsing efficiency and accuracy of the call record file and improving the efficiency of network optimization and operation and maintenance. Optionally, the first field is a "message type" field, or it may be other fields that can be used for verification, and no specific limitation is made in the embodiments of the present application.
[0076] The method of the above embodiment, based on finding the target version number closest to the version number of the call record file from the version numbers of multiple pre-configured model files through loose matching, also needs to verify whether the first field in the call record file parsed by the model file corresponding to the target version number and the first field marked in the message header of the call record file are the same. That is, by combining loose matching, candidate model file screening and verification, while ensuring correct parsing, the target model file used to parse the call record file is determined more efficiently and accurately, thereby improving the parsing efficiency and accuracy of the call record file and improving the efficiency of network optimization and operation and maintenance.
[0077] In one embodiment, the method for parsing a call record file further includes:
[0078] If the target model file cannot be determined from multiple model files according to the preset rule, the call record file is discarded.
[0079] Specifically, in an embodiment of the present application, when the version number in the call record file and the version number of the model file in the call record parsing tool fail to strictly match, a most suitable target model file is found from multiple pre-configured model files through loose matching based on preset rules to parse the call record. Optionally, if the target model file cannot be determined from multiple model files according to the preset rules, that is, if the candidate model file cannot be determined from the multiple model files pre-configured by the call record parsing tool or the verification fails, it indicates that the multiple model files pre-configured by the call record parsing tool cannot effectively parse the call record file, and the call record file is discarded, thereby effectively balancing the parsing ratio and parsing correctness of the call record file.
[0080] The method of the above embodiment discards the call record file when the target model file cannot be determined from multiple model files according to the preset rules, that is, when the candidate model file cannot be determined from the multiple model files pre-configured by the call record parsing tool or the verification fails, thereby effectively balancing the parsing ratio and parsing correctness of the call record file.
[0081] For example, the specific process of the method for parsing a call record file in the embodiment of the present application is as follows:
[0082] 1. Multiple model files pre-configured for the call record parsing tool.
[0083] 2. After extracting the live network call bill file, parse the version number information from the file header and compare it with the version numbers of multiple model files pre-configured in the call bill parsing tool.
[0084] 1) If there is a match, the dialog file is parsed using the corresponding model file.
[0085] 2) If no matching model is found through strict matching, other version numbers of the same base station product corresponding to the call record version number are searched from multiple model files pre-configured by the parsing tool.
[0086] a) If found, select the model file with the version closest to the current CDR file for parsing. In the parsing result, if the "Message Type" field in the message header matches the "Message Type" field obtained by calling the ASN decoding library, the model file is considered to be the model file corresponding to the current CDR file. There are no differences in 3GPP standard messages, and the model file can be correctly parsed. Copy the model file and mark it with the current CDR version number.
[0087] b) Otherwise, it means that the current network optimization tool version cannot find the model file that can be used to parse the current call record file. In this case, the log is recorded and the call record file is discarded.
[0088] Figure 3is a schematic diagram of the structure of the electronic device provided in the embodiment of the present application, such as Figure 3 As shown, the electronic device includes: a memory 320, a transceiver 300, and a processor 310, wherein:
[0089] The memory 320 is used to store computer programs; the transceiver 300 is used to send and receive data under the control of the processor; the processor 310 is used to read the computer program in the memory and perform the following operations:
[0090] Get the call record file to be parsed;
[0091] Match the version number in the call record file with the version numbers of multiple model files in the call record parsing tool to obtain a matching result;
[0092] When the matching result is a matching failure, the target model file is determined from multiple model files according to the preset rules, and the dialog file is parsed.
[0093] Among them, Figure 3 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 310 and memory represented by memory 320. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The transceiver 300 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 310 is responsible for managing the bus architecture and general processing, and the memory 320 may store data used by the processor 310 when performing operations.
[0094] The processor 310 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0095] Optionally, determining a target model file from a plurality of model files according to a preset rule includes:
[0096] Determine, from the version numbers of the multiple model files, a target version number that is closest to the version number in the call record file;
[0097] The model file corresponding to the target version number is determined as the target model file.
[0098] Optionally, determining a target version number closest to the version number in the call record file from the version numbers of the multiple model files includes:
[0099] Determine at least one candidate model file from the multiple model files; the product corresponding to the version number of the candidate model file is the same as the product corresponding to the version number in the call record file;
[0100] From the version numbers of the candidate model files, determine the target version number that is closest to the version number in the call record file.
[0101] Optionally, determining the model file corresponding to the target version number as the target model file includes:
[0102] When the first field in the call record file parsed based on the model file corresponding to the target version number is the same as the first field marked in the message header of the call record file, the model file corresponding to the target version number is determined as the target model file; the first field is the "message type" field.
[0103] Optionally, when the target model file cannot be determined from multiple model files according to a preset rule, the call record file is discarded.
[0104] It should be noted here that the above-mentioned electronic device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.
[0105] Figure 4 Schematic diagram of the structure of the bill parsing device provided in the embodiment of the present application. Figure 4 As shown, the call record parsing device 400 includes:
[0106] The acquisition module 410 is used to obtain the call record file to be parsed;
[0107] The matching module 420 is used to match the version number in the call record file with the version numbers of multiple model files in the call record parsing tool to obtain a matching result.
[0108] The parsing module 430 is used to determine a target model file from multiple model files according to a preset rule and parse the dialog file when the matching result is a match failure.
[0109] The call record parsing device provided in the embodiment of the present application, when the version number in the call record file and the version number of the model file in the call record parsing tool fail to strictly match, finds the most suitable model file from multiple pre-configured model files through loose matching based on preset rules to parse the call record, thereby providing effective data support for the analysis of call record problems, greatly improving the call record file parsing ratio, and improving the efficiency of network optimization and operation and maintenance.
[0110] Optionally, the parsing module 430 is specifically configured to:
[0111] Determine, from the version numbers of the multiple model files, a target version number that is closest to the version number in the call record file;
[0112] The model file corresponding to the target version number is determined as the target model file.
[0113] Optionally, the parsing module 430 is specifically configured to: determine at least one candidate model file from a plurality of model files; the product corresponding to the version number of the candidate model file is the same as the product corresponding to the version number in the call record file;
[0114] From the version numbers of the candidate model files, determine the target version number that is closest to the version number in the call record file.
[0115] Optionally, the parsing module 430 is specifically used to: when the first field in the call record file parsed based on the model file corresponding to the target version number is the same as the first field marked in the message header of the call record file, the model file corresponding to the target version number is determined as the target model file; the first field is the "message type" field.
[0116] Optionally, the parsing module 430 is specifically configured to discard the call record file when a target model file cannot be determined from multiple model files according to a preset rule.
[0117] The methods and devices provided in the various embodiments of the present application are based on the same application concept. Since the methods and devices solve problems based on similar principles, the implementation of the devices and methods can refer to each other, and the repeated parts will not be repeated.
[0118] It should be noted that the division of units in the embodiments of the present application is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0119] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0120] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.
[0121] On the other hand, an embodiment of the present application also provides a processor-readable storage medium, which stores a computer program. The computer program is used to enable the processor to execute the call record parsing method provided by the above-mentioned embodiments, for example, including: obtaining the call record file to be parsed; matching the version number in the call record file with the version numbers of multiple model files in the call record parsing tool to obtain a matching result; when the matching result is a matching failure, determining the target model file from multiple model files according to preset rules, and parsing the call record file.
[0122] The processor-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO)), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NANDFLASH), solid-state drives (SSDs)), etc.
[0123] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) that contain computer-usable program code.
[0124] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0125] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor-readable memory produce an article of manufacture comprising an instruction device that implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.
[0126] These processor-executable instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.
[0127] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the present application and its equivalents, the present application is intended to include these modifications and variations.
Claims
1. A method for parsing a call record file, characterized in that: include: Get the call record file to be parsed; Matching the version number in the call record file with the version numbers of multiple model files in the call record parsing tool to obtain a matching result; When the matching result is a matching failure, a target model file is determined from the multiple model files according to a preset rule, and the call record file is parsed.
2. The method for parsing a call record file according to claim 1, wherein: The determining the target model file from the multiple model files according to a preset rule includes: Determine, from the version numbers of the multiple model files, a target version number closest to the version number in the call record file; The model file corresponding to the target version number is determined as the target model file.
3. The method for parsing a call record file according to claim 2, wherein: Determining, from the version numbers of the multiple model files, a target version number closest to the version number in the call record file includes: Determining at least one candidate model file from the multiple model files; the product corresponding to the version number of the candidate model file is the same as the product corresponding to the version number in the call record file; From the version numbers of the candidate model files, determine a target version number that is closest to the version number in the call record file.
4. The method for parsing a call record file according to claim 2, wherein: Determining the model file corresponding to the target version number as the target model file includes: When the first field in the call record file parsed based on the model file corresponding to the target version number is the same as the first field marked in the message header of the call record file, the model file corresponding to the target version number is determined as the target model file; the first field is the "message type" field.
5. The method for parsing a call record file according to any one of claims 1 to 4, characterized in that: The method further comprises: If the target model file cannot be determined from the multiple model files according to the preset rule, the call record file is discarded.
6. An electronic device, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Get the call record file to be parsed; Matching the version number in the call record file with the version numbers of multiple model files in the call record parsing tool to obtain a matching result; When the matching result is a matching failure, a target model file is determined from the multiple model files according to a preset rule, and the call record file is parsed.
7. The electronic device according to claim 6, wherein: The determining the target model file from the multiple model files according to a preset rule includes: Determine, from the version numbers of the multiple model files, a target version number closest to the version number in the call record file; The model file corresponding to the target version number is determined as the target model file.
8. The electronic device according to claim 7, wherein: Determining, from the version numbers of the multiple model files, a target version number closest to the version number in the call record file includes: Determining at least one candidate model file from the multiple model files; the product corresponding to the version number of the candidate model file is the same as the product corresponding to the version number in the call record file; From the version numbers of the candidate model files, determine a target version number that is closest to the version number in the call record file.
9. The electronic device according to claim 7, wherein: Determining the model file corresponding to the target version number as the target model file includes: When the first field in the call record file parsed based on the model file corresponding to the target version number is the same as the first field marked in the message header of the call record file, the model file corresponding to the target version number is determined as the target model file; the first field is the "message type" field.
10. The electronic device according to any one of claims 6 to 9, characterized in that: Also includes: If the target model file cannot be determined from the multiple model files according to the preset rule, the call record file is discarded.
11. A call record file parsing device, characterized in that: include: The acquisition module is used to obtain the call record file to be parsed; The matching module is used to match the version number in the call record file with the version numbers of multiple model files in the call record parsing tool to obtain a matching result. The parsing module is used to determine a target model file from the multiple model files according to a preset rule and parse the call record file when the matching result is a matching failure.
12. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is configured to cause the processor to execute the method according to any one of claims 1 to 5.