Data configuration method and device, computer device and storage medium

Abstract

The application relates to a data configuration method and device, computer equipment and a storage medium. The method comprises the following steps: obtaining an original parameter name of performance file data; performing lowercase character conversion on the original parameter name to obtain a lowercase parameter name; performing searching on the original parameter name in a configured original parameter name set to obtain a first searching result; if the first searching result is a searching failure, performing searching on the lowercase parameter name in a configured lowercase parameter name set to obtain a second searching result; if the second searching result is a searching failure, performing fuzzy matching on the lowercase parameter name in the configured lowercase parameter name set to obtain a target parameter name; and performing relationship configuration on the target parameter name and the performance file data. After accessing performance file data of different equipment manufacturers, separate configuration is not required for each manufacturer, the development cost of compatibility of different equipment is reduced, and maintainability is improved.

Description

Technical Field

[0001] This application relates to the field of communication equipment management technology, and in particular to a data configuration method, apparatus, computer equipment, and storage medium. Background Technology

[0002] During the use of communication equipment, it is necessary to collect some data generated during the operation of the equipment, and transmit the collected data to the network management system in a certain format. The network management system then performs statistics on the data according to the corresponding algorithm, and feeds back the statistical results to the interface for operators to view and analyze.

[0003] Currently, the live network environment of domestic operators contains base stations from numerous communication equipment manufacturers. Operators have established corresponding performance file data collection specifications. These specifications have standardized the names of most performance parameters reported by various equipment manufacturers. However, some performance parameters still lack standardized names, such as multi-cause and multi-instance performance file data. Operators typically build a unified network management system compatible with devices from multiple manufacturers to collect, adapt, and uniformly present and report performance file data.

[0004] In traditional technologies, in order to be compatible with the performance file data of various device manufacturers, a corresponding configuration file needs to be added to the database for each manufacturer's performance file data to maximize compatibility with devices from various manufacturers. However, this approach has high development costs and poor maintainability. Summary of the Invention

[0005] Therefore, it is necessary to provide a data configuration method, apparatus, computer equipment, and storage medium that is easy to develop and maintain and compatible with performance file data from different manufacturers, in order to address the above-mentioned technical problems.

[0006] Firstly, this application provides a data configuration method. The method includes:

[0007] Get the raw parameter names from the performance file data;

[0008] The original parameter name is converted to lowercase to obtain the lowercase parameter name;

[0009] The first search result is obtained by searching the set of configured original parameter names based on the original parameter name.

[0010] If the first search result is a search failure, then a second search result is obtained by searching in the set of configured lowercase parameter names based on the lowercase parameter name.

[0011] If the second search result is a search failure, then a fuzzy match is performed in the set of configured lowercase parameter names based on the lowercase parameter name to obtain the target parameter name;

[0012] Configure the relationship between the target parameter name and the performance file data.

[0013] In one embodiment, the step of performing a fuzzy match on the configured lowercase parameter name set based on the lowercase parameter name to obtain the target parameter name includes:

[0014] Calculate the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name; wherein, the configured lowercase parameter name set includes multiple preset lowercase parameter names;

[0015] The target parameter name is obtained by filtering the maximum value based on the similarity of multiple parameter names.

[0016] In one embodiment, the step of calculating the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name includes:

[0017] The Jaccard similarity coefficient between the lowercase parameter name and each of the preset lowercase parameter names is determined as the parameter name similarity.

[0018] In one embodiment, the step of calculating the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name further includes:

[0019] The lowercase parameter name and the preset lowercase parameter name are converted into ASCII codes respectively to obtain the first encoding and the second encoding.

[0020] Calculate the similarity between the first code and the second code to obtain the similarity factor;

[0021] The similarity of the parameter names is determined by the product of the similarity factor and the Jaccard similarity coefficient.

[0022] In one embodiment, the step of filtering by maximum value based on the similarity of multiple parameter names to obtain the target parameter name includes:

[0023] If the current parameter name similarity is greater than a preset threshold, then compare the current parameter name similarity with the previous parameter name similarity.

[0024] If the current parameter name similarity is greater than the previous parameter name similarity, then the preset lowercase parameter name corresponding to the current parameter name similarity will be used as the target parameter name.

[0025] In one embodiment, after the step of configuring the relationship between the target parameter name and the performance file data, the method further includes:

[0026] Obtain the target indicator formula; wherein, the target indicator formula corresponds to the target parameter name;

[0027] The performance file data is used to calculate the performance index based on the target index formula;

[0028] If the indicator calculation fails, the target parameter name will be confirmed as the failed parameter name.

[0029] In one embodiment, after the step of confirming the target parameter name as a failed parameter name, the method further includes:

[0030] The set of configured lowercase parameter names is filtered according to the failed parameter names to obtain a set of filtered lowercase parameter names;

[0031] Fuzzy matching is performed on the set of filtered lowercase parameter names based on the lowercase parameter name until the matching terminates or the correct parameter name is obtained.

[0032] Secondly, this application also provides a data configuration apparatus. The apparatus includes:

[0033] The data acquisition module is used to obtain the raw parameter names of performance file data;

[0034] The character conversion module is used to convert the original parameter name to lowercase characters to obtain a lowercase parameter name;

[0035] The first search module is used to search in the set of configured original parameter names according to the original parameter name and obtain the first search result;

[0036] The second search module is used to search in the set of configured lowercase parameter names according to the lowercase parameter name if the first search result is a search failure, and obtain the second search result.

[0037] The fuzzy matching module is used to perform fuzzy matching in the configured lowercase parameter name set according to the lowercase parameter name if the second search result is a search failure, so as to obtain the target parameter name;

[0038] The relationship configuration module is used to configure the relationship between the target parameter name and the performance file data.

[0039] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor. The memory stores a computer program, and the processor, when executing the computer program, performs the following steps: obtaining the original parameter name of performance file data; converting the original parameter name to lowercase to obtain a lowercase parameter name; searching in a set of configured original parameter names based on the original parameter name to obtain a first search result; if the first search result is a search failure, searching in a set of configured lowercase parameter names based on the lowercase parameter name to obtain a second search result; if the second search result is a search failure, performing a fuzzy match in the set of configured lowercase parameter names based on the lowercase parameter name to obtain a target parameter name; and configuring the relationship between the target parameter name and the performance file data.

[0040] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps: obtaining the original parameter name of performance file data; converting the original parameter name to lowercase to obtain a lowercase parameter name; searching in a set of configured original parameter names based on the original parameter name to obtain a first search result; if the first search result is a search failure, searching in a set of configured lowercase parameter names based on the lowercase parameter name to obtain a second search result; if the second search result is a search failure, performing a fuzzy match in the set of configured lowercase parameter names based on the lowercase parameter name to obtain a target parameter name; and configuring the relationship between the target parameter name and the performance file data.

[0041] The aforementioned data configuration method, apparatus, computer equipment, and storage medium obtain the original parameter names of the performance file data and their corresponding lowercase parameter names. Then, they search for the original parameter names in the configured set of original parameter names. If the search fails, they search for the lowercase parameter names in the configured set of lowercase parameter names. If the search succeeds, they can maintain compatibility between parameter names with different case values. If the search fails again, they perform fuzzy matching using the configured set of lowercase parameter names to obtain the most similar target parameter name. After configuring the relationship between the performance file data and the target parameter name, the performance file data can be calculated according to the index formula corresponding to the target parameter name, thus achieving compatibility of the performance file data. When accessing performance file data from different device manufacturers, separate configuration for each manufacturer is not required, reducing the development cost of compatibility across different devices and improving maintainability. Attached Figure Description

[0042] Figure 1 This is an application environment diagram of the data configuration method in one embodiment;

[0043] Figure 2 This is a flowchart illustrating a data configuration method in one embodiment;

[0044] Figure 3 This is a flowchart illustrating the process of obtaining the target parameter name in one embodiment;

[0045] Figure 4 This is a flowchart illustrating the process of calculating parameter name similarity in one embodiment;

[0046] Figure 5 This is a flowchart illustrating the process of obtaining the target parameter name in another embodiment;

[0047] Figure 6 This is a flowchart illustrating the process of confirming the name of a failed parameter in one embodiment;

[0048] Figure 7 This is a flowchart illustrating fuzzy matching in one embodiment;

[0049] Figure 8 This is a structural block diagram of a data configuration device in one embodiment;

[0050] Figure 9 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0051] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0052] According to the KPI (Key Performance Indicator) specification document for mobile communication networks, while the document provides standardized parameter naming for most counters and indicator formulas, a small number of counters only provide a prefix to their parameter names. This lack of standardized naming leads to inconsistencies in how different manufacturers define these counter names. Although KPI data can be calculated and displayed correctly on a manufacturer's own network management system, problems arise when a network management system monitors devices from multiple manufacturers, resulting in the inability to calculate and display KPI data.

[0053] After receiving the KPI specification document, each vendor will configure and implement the corresponding counters and indicator formulas according to the document's requirements, storing the specific parameter names in a database or cache for later use. When the network management system receives the performance file data, it will first store the parameter names and data from the performance file data in the database, and then calculate and display the results based on the configured indicator formulas. If different parameter names exist at this point, the counter cannot be found during indicator calculation, leading to calculation failure and preventing the display of KPI data.

[0054] Based on this, this application provides a data configuration method, apparatus, computer equipment, and storage medium. When a network management system accesses performance file data from different equipment manufacturers, it is not necessary to configure each manufacturer individually. This enables the compatibility configuration of performance file data from different manufacturers, reducing the development cost of compatibility with different devices and improving maintainability.

[0055] This application provides a data configuration method, apparatus, computer device, and storage medium, which are specifically described through the following embodiments. First, the data configuration method in this application is described.

[0056] The data configuration method provided in this application embodiment can be applied to, for example, Figure 1In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or placed on a cloud or other network server. Server 104 can obtain performance file data reported by the communication base station to get the original parameter names of the performance file data. It then converts the original parameter names to lowercase characters to obtain lowercase parameter names, and searches for them in the configured set of original parameter names to obtain a first search result. If the first search result fails, it searches for them in the configured set of lowercase parameter names to obtain a second search result. If the second search result fails, it performs a fuzzy match in the configured set of lowercase parameter names to obtain a target parameter name. Finally, it configures the relationship between the target parameter name and the performance file data. After configuring the relationship, server 104 can calculate the performance file data according to the index formula corresponding to the target parameter name, thereby achieving compatibility with the performance file data. After the performance file data configured according to the relationship is sent to terminal 102 via the communication network, terminal 102 can visualize the performance file data for operators to view and analyze. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc. Server 104 can be implemented using a standalone server or a server cluster consisting of multiple servers.

[0057] In one embodiment, such as Figure 2 As shown, a data configuration method is provided, which can be applied to... Figure 1 Taking server 104 as an example, the following steps are included:

[0058] S100, the raw parameter name for obtaining performance file data.

[0059] Specifically, server 104 can obtain performance file data reported by the base station through the communication network. This performance file data is used to characterize the base station's key performance indicators. Understandably, the performance file data includes the original parameter names and corresponding data values ​​for multiple files. The original parameter names are the names given to the data parameters by the equipment manufacturer according to the KPI specification document. With a defined naming rule, the parameter names are fixed; however, when only the prefix of the parameter name is specified, the original parameter names specified by different manufacturers will differ.

[0060] For a specific example, the metric is calculated by RANK (rank). For each RANK, the MCS (Modulation and Coding Scheme) is the number of RBs used for orders 0-28 (64QAM). The KPI specification document gives the parameter name as RRU.TotalPrbUl64QAM._Rank._Mcs, without giving detailed names for the sub-items. RANK is divided into 1 to 4, and MCS is divided into 0 to 28. Therefore, there are 116 sub-items for this parameter. In the performance file data reported by vendor A's equipment, the original parameter name is set as RRU.TotalPrbUl64QAM.Ranki.Mcsj (i∈[1,4], j∈[0,28]). In the performance file data reported by vendor B's equipment, the original parameter name is set as RRU.TotalPrbUl64QAM.rii.mcsTablej (i∈[1,4], j∈[0,28]). The only difference between the two is the prefix.

[0061] S200 converts the original parameter name to lowercase characters to obtain the lowercase parameter name.

[0062] Specifically, the original parameter names of all counters in the acquired performance file data are converted to lowercase, resulting in the corresponding lowercase parameter names. It's understandable that during the lowercase conversion, only the parts of the original parameter name not explicitly specified in the KPI specification document can be converted, such as converting PHY.CellMaxTxPower to PHY.cellmaxtxpower; or the entire original parameter name can be converted to lowercase, such as converting PHY.CellMaxTxPower to phy.cellmaxtxpower.

[0063] S300 searches within the set of configured original parameter names based on the original parameter name and obtains the first search result.

[0064] Specifically, the configured raw parameter name set is a set of parameter names and indicator formulas for counters configured according to the KPI specification document. Each parameter name corresponds to an indicator formula, which can be used to calculate performance file data. If the calculation is successful, it can be directly stored in the database and displayed on the terminal. The parameter names in the configured raw parameter name set are parameter names that can be uniquely identified by the KPI specification document or stored pre-configured parameter names that have already been used. By searching and matching the obtained raw parameter names, it can be determined whether the current raw parameter name has been configured. If the first search result is successful, the corresponding indicator formula can be directly obtained to complete the calculation and display of performance file data.

[0065] S400, if the first search result is a search failure, then search in the set of configured lowercase parameter names according to the lowercase parameter name to obtain the second search result.

[0066] Specifically, the set of configured lowercase parameter names consists of the full lowercase string configurations of counters added according to the KPI specification document. The parameter names are pre-set lowercase parameter names, and each lowercase parameter name corresponds to an indicator formula. The configured lowercase parameter names can be converted from the configured original parameter names, maintaining a one-to-one correspondence. If a search fails using the current original parameter name, a second search is performed using the converted lowercase parameter name to re-match.

[0067] For a specific example, vendor A reports the original parameter name as PHY.CellMaxTxPower, and vendor B reports the original parameter name as PHY.CELLMaxTxPower. After lowercase character conversion in step S200, the lowercase parameter name is PHY.cellmaxtxpower. The configured lowercase parameter name set contains the corresponding indicator formula for PHY.cellmaxtxpower. At this point, calculating the performance data of vendors A and B using the obtained indicator formula can be successfully completed. Lowercase character conversion unifies parameter names from different vendors that differ only in capitalization.

[0068] S500, if the second search result is a search failure, then perform a fuzzy match in the configured lowercase parameter name set based on the lowercase parameter name to obtain the target parameter name.

[0069] Specifically, when no matching parameter name is found in the set of configured lowercase parameter names using the lowercase parameter name, it means that the current lowercase parameter name is different from all configured lowercase parameter names. In this case, a fuzzy match is performed in the set of configured lowercase parameter names to obtain the most similar configured lowercase parameter name, which is then used as the target parameter name. Since configured lowercase parameter names can also correspond to configured original parameter names, the most similar original parameter name can also be obtained. Because parameter names of the same type are similar in naming, the target parameter name obtained through fuzzy matching is highly likely to have the same data type as the current lowercase parameter name. The calculation is then successfully completed by using the indicator formula corresponding to the target parameter name to calculate the current performance file data. In some other embodiments, a fuzzy match can also be performed on the lowercase parameter name within the set of configured original parameter names.

[0070] S600 configures the relationship between target parameter names and performance file data.

[0071] Specifically, after matching the target parameter name with the current lowercase parameter name, since the current lowercase parameter name corresponds one-to-one with the current original parameter name, and the current original parameter name corresponds one-to-one with the data value in the performance file data, and the target parameter name is a preset lowercase parameter name from the configured lowercase parameter name set, and the preset lowercase parameter name corresponds one-to-one with the indicator formula, after configuring the relationship between the target parameter name and the performance file data, the original parameter name of the current performance file data can be mapped to the indicator formula. Subsequently, after calculating the performance file data using the indicator formula, the performance indicators of the current performance file data can be obtained, which is convenient for display by the network management system.

[0072] The above data configuration method obtains the original parameter names and their corresponding lowercase parameter names from the performance file data. It then searches for the original parameter names in the configured set of original parameter names. If the search fails, it searches for the lowercase parameter names in the configured set of lowercase parameter names. If the search succeeds, it ensures compatibility between parameter names with different case values. If the search fails again, it performs fuzzy matching using the configured set of lowercase parameter names to obtain the most similar target parameter name. After configuring the relationship between the performance file data and the target parameter name, the performance file data can be calculated according to the indicator formula corresponding to the target parameter name, thus achieving compatibility for the performance file data. When integrating performance file data from different device manufacturers, it eliminates the need for separate configuration for each manufacturer, reducing development costs for compatibility across different devices and improving maintainability.

[0073] In one embodiment, such as Figure 3 As shown, the steps to obtain the target parameter name by performing a fuzzy match within the configured set of lowercase parameter names based on the lowercase parameter name include:

[0074] S510, calculate the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name; wherein, the configured lowercase parameter name set includes multiple preset lowercase parameter names.

[0075] Specifically, the configured set of lowercase parameter names includes multiple preset lowercase parameter names, each corresponding to a metric formula used to calculate metric data from performance file data. During fuzzy matching, the similarity between the acquired lowercase parameter name and each preset lowercase parameter name is first calculated. Parameter name similarity characterizes the degree of similarity between two parameter names, and multiple parameter name similarities can be obtained through calculation.

[0076] S520: Filter by the maximum value based on the similarity of multiple parameter names to obtain the target parameter name.

[0077] Specifically, by filtering the multiple parameter name similarities by the maximum value, the maximum parameter name similarity can be obtained. Based on the maximum parameter name similarity, the corresponding preset lowercase parameter name can be obtained, and this preset lowercase parameter name is used as the target parameter name.

[0078] In one embodiment, the step of calculating the parameter name similarity between a lowercase parameter name and each preset lowercase parameter name includes: determining the Jaccard similarity coefficient between the lowercase parameter name and each preset lowercase parameter name as the parameter name similarity.

[0079] Specifically, this application embodiment uses the Jaccard similarity coefficient to determine the similarity of parameter names. The Jaccard similarity coefficient is used to compare the degree of similarity between two text sets. The higher the Jaccard coefficient, the higher the similarity between the two text sets. The formula for calculating the Jaccard coefficient is as follows:

[0080]

[0081] The Jaccard similarity index (J(A,B)) is calculated by dividing the number of elements in the intersection of two text sets by the number of elements in their union. If the two text sets are completely different, J(A,B) = 0; if they are completely identical, J(A,B) = 1. Therefore, the range of the Jaccard similarity index is [0,1], with higher values ​​indicating higher similarity. By calculating the Jaccard similarity index and using it as the parameter name similarity, the degree of similarity between the current lowercase parameter name and the preset lowercase parameter name can be obtained.

[0082] In one embodiment, such as Figure 4 As shown, the step of calculating the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name further includes:

[0083] S511 converts the lowercase parameter name and the preset lowercase parameter name into ASCII codes respectively, thus obtaining the first code and the second code.

[0084] Specifically, the current lowercase parameter name and the preset lowercase parameter name to be compared are converted into ASCII codes to obtain the corresponding first and second codes. It is understood that in some other embodiments, the set of configured lowercase parameter names may also pre-store the second code corresponding to the preset lowercase parameter name, which can be directly retrieved during calculation.

[0085] S512, calculate the similarity between the first code and the second code to obtain the similarity factor.

[0086] Specifically, the following formula can be used to calculate the similarity between the first and second codes:

[0087]

[0088] Where, x i and y i S represents the calculated similarity score, corresponding to the ASCII code of the i-th character, and is used as the similarity factor. In some other embodiments, methods such as calculating cosine similarity can also be used to calculate the similarity between the first and second codes.

[0089] S513, confirm the similarity of parameter names based on the product of the similarity factor and the Jaccard similarity coefficient.

[0090] Specifically, in this embodiment, the calculated similarity factor and Jaccard similarity coefficient are directly multiplied, and the product is used as the parameter name similarity. In some other embodiments, the influence of the similarity factor and Jaccard similarity coefficient on the parameter name similarity can be adjusted by adding a weighting coefficient before the similarity factor and / or Jaccard similarity coefficient.

[0091] In this embodiment, to avoid errors caused by the letter order in the parameter names, after calculating the Jaccard similarity index, the similarity factor between the lowercase parameter name and the preset lowercase parameter name is calculated. The similarity factor and the Jaccard similarity coefficient are used to determine the similarity of the parameter names simultaneously, which can reduce the errors caused by different letter orders.

[0092] In one embodiment, such as Figure 5 As shown, the steps to obtain the target parameter name by filtering the maximum value based on the similarity of multiple parameter names include:

[0093] S521, If ​​the current parameter name similarity is greater than the preset threshold, then compare the current parameter name similarity with the previous parameter name similarity.

[0094] Specifically, when the calculated parameter name similarity is too low, i.e., less than or equal to a preset threshold (e.g., 50%), it indicates that the corresponding lowercase parameter name is dissimilar to the preset lowercase parameter name, and the parameter name similarity can be discarded directly. When the parameter name similarity is greater than the preset threshold, the current parameter name similarity can be stored. For example, the current parameter name similarity and the corresponding original parameter name are stored in a name queue, where the name queue stores the correspondence between the original parameter name and the lowercase parameter name. If the previously calculated parameter name similarity is already stored in the name queue during storage, it is necessary to compare the current parameter name similarity with the previous parameter name similarity.

[0095] S522, if the similarity of the current parameter name is greater than the similarity of the previous parameter name, then the preset lowercase parameter name corresponding to the similarity of the current parameter name will be used as the target parameter name.

[0096] Specifically, the previous parameter name similarity is the parameter name similarity stored in the name queue. If the currently calculated parameter name similarity is greater than the previous parameter name similarity, the parameter name similarity stored in the name queue needs to be updated. The preset lowercase parameter name corresponding to the current parameter name similarity is used as the target parameter name and updated in the name queue. In subsequent use, the target parameter name in the name queue is the preset lowercase parameter name that is most similar to the current lowercase parameter name, and the current original parameter name corresponds one-to-one with the current lowercase parameter name. When performing a matching search again, the corresponding target parameter name can be obtained through the original parameter name.

[0097] In one embodiment, such as Figure 6 As shown, after configuring the relationship between the target parameter name and the performance file data, the data configuration method also includes:

[0098] S710, Obtain the target indicator formula; where the target indicator formula corresponds to the target parameter name.

[0099] Specifically, the target parameter name is a preset lowercase parameter name from the set of configured lowercase parameter names. Each preset lowercase parameter name corresponds one-to-one with a metric formula, allowing the matching of the corresponding target metric formula. The metric formula is used to calculate metrics on performance file data and obtain the corresponding metric data. Different types of performance file data require different metric formulas for metric data calculation.

[0100] S720 calculates performance metrics based on the target metric formula for the performance file data.

[0101] Specifically, after configuring the performance file data according to relationships, the performance file is used to calculate the performance index using the obtained target index formula. This is used to verify whether the performance file data matches the target index formula, that is, to verify whether the target parameter name obtained through fuzzy matching is correct.

[0102] S730: If the indicator calculation fails, the target parameter name will be confirmed as the failed parameter name.

[0103] Specifically, if the indicator calculation fails, it means that the target parameter name obtained by matching is incorrect. In this case, the target parameter name is confirmed as the failed parameter name, and the failed parameter name can be stored in the failure queue. The failure queue includes the original parameter name and the failed parameter name.

[0104] The above-described method for calculating indicators can be used to verify whether the most similar target parameter name obtained through fuzzy matching meets the requirements of subsequent indicator calculations. If it does not meet the requirements, the target parameter name is confirmed as a failed parameter name. In subsequent calculations, failed parameter names can be filtered out first to reduce redundant calculations.

[0105] In one embodiment, such as Figure 7 As shown, after confirming the target parameter name as the failure parameter name, the data configuration method further includes:

[0106] S810 filters the set of configured lowercase parameter names based on the failed parameter names to obtain a set of filtered lowercase parameter names.

[0107] Specifically, after obtaining the failed parameter names, the failed parameter names in the configured lowercase parameter name set are filtered out, that is, the corresponding failed parameter names are deleted, thus obtaining the filtered lowercase parameter name set. The filtered lowercase parameter name set includes multiple preset lowercase parameter names that have not been verified by indicator calculation.

[0108] S820 performs fuzzy matching on the set of filtered lowercase parameter names based on the lowercase parameter name until the matching terminates or the correct parameter name is obtained.

[0109] Specifically, during repeated fuzzy matching, the parameter similarity calculated in the first fuzzy match is used to sort the parameters and select the next most similar target parameter name. Then, based on the new target parameter name, a new target metric formula is derived, and the performance file data is calculated using this formula to verify the correctness of the new target parameter name. If all preset lowercase parameter names in the filtered lowercase parameter name set fail to verify, the matching terminates. If one preset lowercase parameter name succeeds in verification, it is used as the correct parameter name and stored in the correct queue. The next time it is used, matching can be performed directly.

[0110] The data configuration method of this application is described in detail below with a specific embodiment. The original parameter name of the RANK class parameter obtained by the network management system is RRU.TotalPrbUl64QAM.ri1.mcsTable2. After two lookup processes, no match can be found. The target parameter name with the highest matching degree is obtained through fuzzy matching. The original parameter name corresponding to the target parameter name is RRU.TotalPrbUl64QAM.Rank1.Mcs2. At this time, the performance file data is bound to the OUI (Organizationally Unique Identifier) ​​of the manufacturer's equipment at the granularity. When the device reports the performance file data for a new measurement period, the network management system will convert RRU.TotalPrbUl64QAM.ri1.mcsTable2 in the performance file data into RRU.TotalPrbUl64QAM.Rank1.Mcs2 according to the stored configuration relationship, and then participate in the calculation. If the network management system can successfully calculate the metrics, it will persist the configuration relationships at the OUI level of the vendor's equipment. If the calculation is abnormal, it will re-perform fuzzy matching and find the target parameter name with the second highest matching degree to establish a configuration relationship to participate in the calculation until the network management system can parse and calculate normally.

[0111] In one embodiment, in the performance file data reported by device A, the original parameter name of a certain performance parameter is RRC.SuccConnResume.RnaUpdate. The Jaccard similarity coefficient calculated using the Jaccard similarity algorithm is 0.8889 with the performance parameter RRC.SuccConnResume.mo-VideoCall reported by device B; and 0.2 with the performance parameter RRC.SuccConnResume.mo-Signalling. Therefore, the performance parameter RRC.SuccConnResume.RnaUpdate from device A is most similar to the performance parameter RRC.SuccConnResume.rna-Update. After fuzzy matching, a configuration relationship is established between these two parameters. When performance file data is reported by device B, the performance parameter RRC.SuccConnResume.rna-Update will be converted to RRC.SuccConnResume.RnaUpdate. In this way, the network management system only needs to build one set of performance parameter structures for device A to achieve compatibility with performance file data from both vendors A and B. When each performance file data is reported to the network management system, the configuration relationship between the network management system and the performance parameters established by that vendor can be found through the device's OUI.

[0112] In one embodiment, the original parameter name of a certain performance parameter given in the KPI specification document is PHY.CellMaxTxPower. The original parameter name of this performance parameter in the performance file data reported by vendor A is PHY.cellmaxtxpower. The correct original parameter name can be found by matching the lowercase parameter name. In the performance file data reported by vendor B, the original parameter name of this performance parameter is PHY.Cell_Max_Tx_Power. The correct original parameter name can be found after one fuzzy matching process. In the performance file data reported by vendor C, the original parameter name of this performance parameter is PHY.CellMaxTxPowrr. The "Powrr" in this name differs in structure from the "Power" in the original parameter name. The correct original parameter name can be found with a high degree of matching through multiple fuzzy matches. In cases where parameter names cannot completely match the parameter names in the specification document due to various reasons, the data configuration method of this application allows the network management system to automatically match and achieve automatic error correction.

[0113] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0114] Based on the same inventive concept, this application also provides a data configuration apparatus for implementing the data configuration method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more data configuration apparatus embodiments provided below can be found in the limitations of the data configuration method described above, and will not be repeated here.

[0115] In one embodiment, such as Figure 8 As shown, a data configuration device is provided, including: a data acquisition module 910, a character conversion module 920, a first search module 930, a second search module 940, a fuzzy matching module 950, and a relationship configuration module 960, wherein:

[0116] Data acquisition module 910 is used to acquire the original parameter names of performance file data;

[0117] The character conversion module 920 is used to convert the original parameter name to lowercase characters to obtain the lowercase parameter name;

[0118] The first search module 930 is used to search in the set of configured original parameter names based on the original parameter name to obtain the first search result;

[0119] The second search module 940 is used to search in the set of configured lowercase parameter names based on the lowercase parameter name if the first search result is a search failure, and obtain the second search result.

[0120] The fuzzy matching module 950 is used to perform fuzzy matching in the configured set of lowercase parameter names based on the lowercase parameter name if the second search result is a search failure, so as to obtain the target parameter name;

[0121] The relational configuration module 960 is used to configure the relationship between target parameter names and performance file data.

[0122] The aforementioned data configuration device obtains the original parameter names and their corresponding lowercase parameter names from the performance file data. It then searches for the original parameter names in the configured set of original parameter names. If the search fails, it searches for the lowercase parameter names in the configured set of lowercase parameter names. If the search succeeds, it ensures compatibility between parameter names with different case values. If the search fails again, it performs fuzzy matching using the configured set of lowercase parameter names to obtain the most similar target parameter name. After configuring the relationship between the performance file data and the target parameter name, the device can calculate the performance file data according to the index formula corresponding to the target parameter name, thus achieving compatibility for the performance file data. When integrating performance file data from different device manufacturers, it eliminates the need for separate configuration for each manufacturer, reducing development costs for compatibility across different devices and improving maintainability.

[0123] In one embodiment, the fuzzy matching module 950 is used to calculate the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name; wherein, the configured lowercase parameter name set includes multiple preset lowercase parameter names; and the target parameter name is obtained by filtering the maximum value according to the multiple parameter name similarities.

[0124] In one embodiment, the fuzzy matching module 950 is used to determine the Jaccard similarity coefficient between the lowercase parameter name and each preset lowercase parameter name as the parameter name similarity.

[0125] In one embodiment, the fuzzy matching module 950 is used to convert the lowercase parameter name and the preset lowercase parameter name into ASCII codes respectively to obtain the first code and the second code; calculate the similarity between the first code and the second code to obtain the similarity factor; and confirm the parameter name similarity based on the product of the similarity factor and the Jaccard similarity coefficient.

[0126] In one embodiment, the fuzzy matching module 950 is used to compare the similarity of the current parameter name with the similarity of the previous parameter name if the current parameter name similarity is greater than a preset threshold; if the current parameter name similarity is greater than the previous parameter name similarity, then the preset lowercase parameter name corresponding to the current parameter name similarity is used as the target parameter name.

[0127] In one embodiment, the data configuration device further includes: an indicator calculation module, used to obtain a target indicator formula; wherein the target indicator formula corresponds to a target parameter name; to perform indicator calculation on the performance file data according to the target indicator formula; and if the indicator calculation fails, to confirm the target parameter name as the failed parameter name.

[0128] In one embodiment, the data configuration device further includes: a loop matching module, configured to filter the set of configured lowercase parameter names based on the failed parameter names to obtain a set of filtered lowercase parameter names; and to perform fuzzy matching on the set of filtered lowercase parameter names based on the lowercase parameter names until the matching terminates or the correct parameter name is obtained.

[0129] Each module in the aforementioned data configuration device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0130] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 9 As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media. The database stores performance file data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When executed by the processor, the computer program implements a data configuration method.

[0131] Those skilled in the art will understand that Figure 9 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0132] In one embodiment, a computer device is provided, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to perform the following steps: obtaining the original parameter name of performance file data; converting the original parameter name to lowercase to obtain a lowercase parameter name; searching in a set of configured original parameter names based on the original parameter name to obtain a first search result; if the first search result fails, searching in a set of configured lowercase parameter names based on the lowercase parameter name to obtain a second search result; if the second search result fails, performing a fuzzy match in a set of configured lowercase parameter names based on the lowercase parameter name to obtain a target parameter name; and configuring the relationship between the target parameter name and the performance file data.

[0133] The aforementioned computer equipment obtains the original parameter names and their corresponding lowercase parameter names from the performance file data. It then searches for the original parameter names in the configured set of original parameter names. If the search fails, it searches for the lowercase parameter names in the configured set of lowercase parameter names. If the search succeeds, it ensures compatibility between parameter names with different case values. If the search fails again, it performs fuzzy matching using the configured set of lowercase parameter names to obtain the most similar target parameter name. After configuring the relationship between the performance file data and the target parameter name, it can calculate the performance file data according to the index formula corresponding to the target parameter name, thus achieving compatibility for the performance file data. By integrating performance file data from different device manufacturers, it eliminates the need for separate configuration for each manufacturer, reducing development costs for compatibility across different devices and improving maintainability.

[0134] In one embodiment, when the processor executes the computer program, it further implements the following steps: the step of performing fuzzy matching in a set of configured lowercase parameter names based on the lowercase parameter name to obtain the target parameter name, including: calculating the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name; wherein the set of configured lowercase parameter names includes multiple preset lowercase parameter names; and filtering by the maximum value based on the multiple parameter name similarities to obtain the target parameter name.

[0135] In one embodiment, when the processor executes the computer program, it further performs the following step: calculating the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name, including: determining the Jaccard similarity coefficient between the lowercase parameter name and each preset lowercase parameter name as the parameter name similarity.

[0136] In one embodiment, when the processor executes the computer program, it further implements the following steps: the step of calculating the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name, which further includes: converting the lowercase parameter name and the preset lowercase parameter name into ASCII codes respectively to obtain a first code and a second code; calculating the similarity between the first code and the second code to obtain a similarity factor; and confirming the parameter name similarity based on the product of the similarity factor and the Jaccard similarity coefficient.

[0137] In one embodiment, when the processor executes the computer program, it further implements the following steps: the step of filtering the maximum value based on the similarity of multiple parameter names to obtain the target parameter name, including: if the current parameter name similarity is greater than a preset threshold, then comparing the current parameter name similarity with the previous parameter name similarity; if the current parameter name similarity is greater than the previous parameter name similarity, then using the preset lowercase parameter name corresponding to the current parameter name similarity as the target parameter name.

[0138] In one embodiment, when the processor executes the computer program, it further performs the following steps: after configuring the relationship between the target parameter name and the performance file data, it further includes: obtaining a target indicator formula; wherein the target indicator formula corresponds to the target parameter name; calculating the indicator on the performance file data according to the target indicator formula; if the indicator calculation fails, the target parameter name is confirmed as a failed parameter name.

[0139] In one embodiment, when the processor executes the computer program, it further implements the following steps: after the step of confirming the target parameter name as a failed parameter name, it further includes: filtering the configured lowercase parameter name set according to the failed parameter name to obtain a filtered lowercase parameter name set; performing fuzzy matching on the filtered lowercase parameter name set according to the lowercase parameter name until the matching terminates or the correct parameter name is obtained.

[0140] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, it performs the following steps: obtaining the original parameter name of performance file data; converting the original parameter name to lowercase to obtain a lowercase parameter name; searching in a set of configured original parameter names based on the original parameter name to obtain a first search result; if the first search result fails, searching in a set of configured lowercase parameter names based on the lowercase parameter name to obtain a second search result; if the second search result fails, performing fuzzy matching in a set of configured lowercase parameter names based on the lowercase parameter name to obtain a target parameter name; and configuring the relationship between the target parameter name and the performance file data.

[0141] The aforementioned computer-readable storage medium obtains the original parameter names and their corresponding lowercase parameter names from the performance file data. It then searches for the original parameter names in the configured set of original parameter names. If the search fails, it searches for the lowercase parameter names in the configured set of lowercase parameter names. If the search succeeds, it ensures compatibility between parameter names with different case values. If the search fails again, it performs fuzzy matching using the configured set of lowercase parameter names to obtain the most similar target parameter name. After configuring the relationship between the performance file data and the target parameter name, it can calculate the performance file data according to the index formula corresponding to the target parameter name, thus achieving compatibility for the performance file data. When integrating performance file data from different device manufacturers, it eliminates the need for separate configuration for each manufacturer, reducing development costs for compatibility across different devices and improving maintainability.

[0142] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: the step of performing fuzzy matching in a set of configured lowercase parameter names based on the lowercase parameter name to obtain the target parameter name, including: calculating the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name; wherein the set of configured lowercase parameter names includes multiple preset lowercase parameter names; and filtering by the maximum value based on the multiple parameter name similarities to obtain the target parameter name.

[0143] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: calculating the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name, including: determining the Jaccard similarity coefficient between the lowercase parameter name and each preset lowercase parameter name as the parameter name similarity.

[0144] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: the step of calculating the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name, which further includes: converting the lowercase parameter name and the preset lowercase parameter name into ASCII codes respectively to obtain a first code and a second code; calculating the similarity between the first code and the second code to obtain a similarity factor; and confirming the parameter name similarity based on the product of the similarity factor and the Jaccard similarity coefficient.

[0145] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: the step of filtering the maximum value based on the similarity of multiple parameter names to obtain the target parameter name, including: if the current parameter name similarity is greater than a preset threshold, then comparing the current parameter name similarity with the previous parameter name similarity; if the current parameter name similarity is greater than the previous parameter name similarity, then using the preset lowercase parameter name corresponding to the current parameter name similarity as the target parameter name.

[0146] In one embodiment, when the computer program is executed by the processor, it further performs the following steps: after configuring the relationship between the target parameter name and the performance file data, it further includes: obtaining a target indicator formula; wherein the target indicator formula corresponds to the target parameter name; calculating the indicator on the performance file data according to the target indicator formula; if the indicator calculation fails, the target parameter name is identified as a failed parameter name.

[0147] In one embodiment, when the computer program is executed by the processor, it further implements the following steps: after the step of confirming the target parameter name as a failed parameter name, it further includes: filtering the configured lowercase parameter name set according to the failed parameter name to obtain a filtered lowercase parameter name set; performing fuzzy matching on the filtered lowercase parameter name set according to the lowercase parameter name until the matching terminates or the correct parameter name is obtained.

[0148] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0149] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0150] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A data configuration method, characterized in that, The method includes: Obtain the original parameter names of the performance file data; wherein, the performance file data is used to characterize the key performance indicators of the base station; The original parameter name is converted to lowercase to obtain the lowercase parameter name; The first search result is obtained by searching the set of configured original parameter names based on the original parameter name. If the first search result is a search failure, then a second search result is obtained by searching in the set of configured lowercase parameter names based on the lowercase parameter name. If the second search result is a search failure, then a fuzzy match is performed in the set of configured lowercase parameter names based on the lowercase parameter name to obtain the target parameter name; Configure the relationship between the target parameter name and the performance file data.

2. The data configuration method according to claim 1, characterized in that, The step of performing a fuzzy match on the configured lowercase parameter name set based on the lowercase parameter name to obtain the target parameter name includes: Calculate the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name; wherein, the configured lowercase parameter name set includes multiple preset lowercase parameter names; The target parameter name is obtained by filtering the maximum value based on the similarity of multiple parameter names.

3. The data configuration method according to claim 2, characterized in that, The step of calculating the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name includes: The Jaccard similarity coefficient between the lowercase parameter name and each of the preset lowercase parameter names is determined as the parameter name similarity.

4. The data configuration method according to claim 3, characterized in that, The step of calculating the parameter name similarity between the lowercase parameter name and each preset lowercase parameter name further includes: The lowercase parameter name and the preset lowercase parameter name are converted into ASCII codes respectively to obtain the first encoding and the second encoding. Calculate the similarity between the first code and the second code to obtain the similarity factor; The similarity of the parameter names is determined by the product of the similarity factor and the Jaccard similarity coefficient.

5. The data configuration method according to claim 2, characterized in that, The step of filtering by the maximum value based on the similarity of multiple parameter names to obtain the target parameter name includes: If the current parameter name similarity is greater than a preset threshold, then compare the current parameter name similarity with the previous parameter name similarity. If the current parameter name similarity is greater than the previous parameter name similarity, then the preset lowercase parameter name corresponding to the current parameter name similarity will be used as the target parameter name.

6. The data configuration method according to claim 1, characterized in that, After the step of configuring the relationship between the target parameter name and the performance file data, the method further includes: Obtain the target indicator formula; wherein, the target indicator formula corresponds to the target parameter name; The performance file data is used to calculate the performance index based on the target index formula; If the indicator calculation fails, the target parameter name will be confirmed as the failed parameter name.

7. The data configuration method according to claim 6, characterized in that, After the step of confirming the target parameter name as a failed parameter name, the method further includes: The set of configured lowercase parameter names is filtered according to the failed parameter names to obtain a set of filtered lowercase parameter names; Fuzzy matching is performed on the set of filtered lowercase parameter names based on the lowercase parameter name until the matching terminates or the correct parameter name is obtained.

8. A data configuration device, characterized in that, The device includes: The data acquisition module is used to acquire the original parameter names of the performance file data; wherein, the performance file data is used to characterize the key performance indicators of the base station. The character conversion module is used to convert the original parameter name to lowercase characters to obtain a lowercase parameter name; The first search module is used to search in the set of configured original parameter names according to the original parameter name and obtain the first search result; The second search module is used to search in the set of configured lowercase parameter names according to the lowercase parameter name if the first search result is a search failure, and obtain the second search result. The fuzzy matching module is used to perform fuzzy matching in the configured lowercase parameter name set according to the lowercase parameter name if the second search result is a search failure, so as to obtain the target parameter name; The relationship configuration module is used to configure the relationship between the target parameter name and the performance file data.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images