Data processing method, and device, medium and product

Abstract

Provided in the present disclosure is a data processing method, comprising: performing data conflict detection on key fields of a plurality of pieces of network management data, wherein the plurality of pieces of network management data are from at least two management areas; when there is a data conflict between any two key fields, modifying at least one of the two key fields between which there is a data conflict, so as to eliminate the data conflict; and merging the plurality of pieces of network management data into a target network management database, wherein the target network management database comprises a plurality of management and control domains, and one management and control domain manages all network management data in one management area. Further provided in the present disclosure are an electronic device, a computer-readable medium, and a computer program product.

Description

Data processing methods, equipment, media and products

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411215896.5, filed with the Chinese Patent Office on August 30, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to, but is not limited to, the field of communication technology. Background Technology

[0004] With the continuous development of communication technology, the number of access devices is increasing, the types of services are becoming more complex, and the number of communication networks is also growing explosively. In order to achieve centralized management of data in multiple areas, manual methods are usually used to merge network management data from different areas to obtain complete network management data for the entire region.

[0005] However, since different types of business data are represented by different identifiers in each region, and the same identifier may be used to represent different business types in different regions, the merged network management data may be chaotic. The manual processing method described above will not only reduce data processing efficiency, but also fail to guarantee the accuracy of data management. Summary of the Invention

[0006] This disclosure provides a data processing method, network management device, computer-readable medium, and computer program product.

[0007] In a first aspect, embodiments of this disclosure provide a data processing method, the method comprising: performing data conflict detection on key fields of multiple network management data, the multiple network management data coming from at least two management areas; in the event that any two key fields have data conflicts, modifying at least one of the two key fields with data conflicts to eliminate the data conflicts; merging the multiple network management data into a target network management database, the target network management database including multiple control domains, one control domain managing all network management data in one management area.

[0008] Secondly, embodiments of this disclosure provide a network management device, including: one or more processors; and a memory storing one or more programs thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any one of the data processing methods in the embodiments of this disclosure.

[0009] Thirdly, embodiments of this disclosure provide a readable storage medium storing a computer program that, when executed by a processor, implements any of the data processing methods described in this disclosure.

[0010] Fourthly, embodiments of this disclosure provide a computer program product, which includes a computer program that, when executed by a processor, implements any of the data processing methods described in the embodiments of this disclosure. Attached Figure Description

[0011] In the accompanying drawings of the embodiments disclosed herein:

[0012] Figure 1 is a schematic flowchart of a data processing method provided in an embodiment of this disclosure;

[0013] Figure 2 is a block diagram of a network management device provided in an embodiment of this disclosure;

[0014] Figure 3 is a block diagram of another network management device provided in an embodiment of this disclosure;

[0015] Figure 4 is a flowchart illustrating a method for merging network management data of multiple network management systems to be merged, provided in an embodiment of this disclosure.

[0016] Figure 5 is a schematic diagram of the process of data interaction between the conflict identification module and other devices in a network management device according to an embodiment of this disclosure;

[0017] Figure 6 is a flowchart illustrating a method for data processing by a network management device according to an embodiment of this disclosure;

[0018] Figure 7 is a flowchart illustrating another method for data processing using a network management device according to an embodiment of this disclosure;

[0019] Figure 8 is a block diagram of another network management device provided in an embodiment of this disclosure. Detailed Implementation

[0020] To enable those skilled in the art to better understand the technical solutions of this disclosure, the embodiments of this disclosure will be described in detail below with reference to the accompanying drawings.

[0021] The present disclosure will be described more fully below with reference to the accompanying drawings; however, the embodiments shown may be embodied in different forms, and the present disclosure should not be construed as limited to the embodiments set forth below. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will enable those skilled in the art to fully understand the scope of the disclosure.

[0022] The accompanying drawings of the embodiments disclosed herein are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the detailed embodiments to explain this disclosure and do not constitute a limitation thereof. The above and other features and advantages will become more apparent to those skilled in the art from the description of the detailed embodiments with reference to the accompanying drawings.

[0023] Where there is no conflict, the various embodiments of this disclosure and the features thereof in the embodiments may be combined with each other.

[0024] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the disclosure. The term "and / or" as used in this disclosure includes any and all combinations of one or more of the associated enumerated entries. The singular forms "a" and "the" as used in this disclosure are also intended to include the plural forms, unless the context clearly indicates otherwise. The terms "comprising," "made of," etc., as used in this disclosure specify the presence of features, integrals, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components, and / or groups thereof.

[0025] Unless otherwise specified, all terms used in this disclosure (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and this disclosure, and will not be interpreted as having an idealized or overly formal meaning, unless expressly so defined in this disclosure.

[0026] With the continuous development of communication technology, there are more and more access devices, and the types of services performed by each access device are becoming more and more complex, resulting in an explosive growth in the number of communication networks.

[0027] To achieve unified management of network management data across multiple regions, it is necessary to merge the data from these regions to improve management efficiency. However, since key fields in the network management data from different regions may conflict (e.g., two network element numbers may be identical in two regions), a manual process is typically used to compare the network management data from different regions one by one to identify conflicting data. This conflicting data is then modified, and finally merged to obtain conflict-free network management data, facilitating network administrator management.

[0028] However, different types of business data are represented by different identifiers in each region; and different regions may use the same identifier to represent different business types. When the above-mentioned manual method is used to merge data, it will also lead to data disorder in the merged network management data, making it impossible to guarantee the accuracy of the modified network management data. At the same time, it will also increase labor costs.

[0029] To at least address the aforementioned problems, this application provides a data processing method, a network management device, a computer-readable medium, and a computer program product.

[0030] Figure 1 is a schematic flowchart of a data processing method provided in an embodiment of this disclosure. This data processing method is applied to a network management device. As shown in Figure 1, the data processing method includes, but is not limited to, the following steps S101 to S103.

[0031] Step S101: Perform data conflict detection on key fields of multiple network management data.

[0032] In this process, multiple network management data originate from at least two management regions. A management region is a region that can be governed by the network management system to be merged. The network management system to be merged is used to manage multiple network management data generated by multiple network element devices within its management region.

[0033] Key fields in network management data are fields that cannot be duplicated, such as the identifier field of network elements and the service type field of the service data performed by the network elements. If a key field from network management data from one management area is the same as a key field from network management data from another management area, then a data conflict can be determined between these two key fields.

[0034] Network management data can also include other fields (such as fields that represent business data), which can be repeated. For example, they can all be video data from the download business, and can be used by multiple different end users.

[0035] There are no data conflicts between key fields of multiple network management data within each management area. For example, different identifiers are typically used to represent different types of business data within a single management area. However, the same identifier may be used to represent different business types in different management areas. If it is necessary to merge multiple network management data from two different management areas, there may be confusion regarding the business types represented by the identifiers in the merged network management data.

[0036] At this point, it is necessary to perform data conflict detection on the key fields of multiple network management data from at least two management areas to determine whether there is any data duplication among the key fields in each network management data, thereby ensuring that each identifier in the merged network management data is used to represent different types of business data. In other words, it ensures the uniqueness of the meaning represented by the key fields in the merged network management data.

[0037] Step S102: If there is a data conflict between any two key fields, at least one of the two key fields with the data conflict shall be modified to eliminate the data conflict.

[0038] In some embodiments, at least one of two key fields that have data conflicts can be modified according to preset processing rules to eliminate the data conflict.

[0039] The preset processing rules are pre-defined rules used to modify key fields that have data conflicts. Key fields are fields that indicate data conflicts.

[0040] The preset processing rule can be used to modify both key fields that have data conflicts, or it can be used to modify either of the two key fields that have data conflicts, depending on the application scenario corresponding to the multiple network management data. This application does not impose any restrictions on this.

[0041] After modifying at least one of the two key fields that have data conflicts, there are no data conflicts between the modified key fields (or between the modified key fields and other unmodified key fields), so that the key fields of each network management data can represent a unique physical meaning, which facilitates the subsequent management of the merged network management data.

[0042] Step S103: Merge multiple network management data into the target network management database.

[0043] The target network management database stores the network management data under the jurisdiction of the target network management system. The target network management database includes multiple control domains, with each control domain managing all network management data within a specific management area. All network management data from the same management area corresponds to the same control domain, while network management data from different control domains are managed independently.

[0044] One of the control domains is a region built in the network management database to manage all network management data from the same management area. Each control domain is independent of the others and does not interfere with them, but they can all be managed uniformly by the target network management system.

[0045] For example, if the target network management database includes at least two control domains, the target network management system can independently manage the network management data in any one control domain without affecting the accuracy of the network management data in the other control domain. Furthermore, the target network management system can simultaneously query the network management data in each control domain for global data management.

[0046] The data processing method in this embodiment detects data conflicts in key fields of multiple network management data to determine whether there are any conflicts between them. Before merging the data, at least one of the conflicting key fields is modified according to preset processing rules to eliminate the conflicts, thus preventing data conflicts between the modified network management data. Since the multiple network management data originate from at least two management regions, merging them into a target network management database allows the database to cover data from more management regions, expanding the target network management's jurisdiction. Furthermore, the target network management database includes multiple control domains, with each domain managing all network management data within a single management region. This allows for independent management of all network management data from a single management region using a single control domain, ensuring the accuracy of the target network management's processing of data within each control domain and significantly improving its data processing efficiency.

[0047] In some exemplary embodiments, step S101, which involves detecting data conflicts in key fields of multiple network management data, includes: extracting key fields from multiple network management data; comparing all similar key fields pairwise to obtain comparison results; and determining that the two identical key fields conflict if the comparison results show that the two identical key fields are the same.

[0048] In this context, all key fields of the same type indicate that they represent the same physical meaning. For example, they may all be key fields used to identify network element devices.

[0049] In some embodiments, the key fields of network management data may include name fields and field values. When comparing all key fields of the same type in pairs, the name fields of each key field can be compared in pairs first to obtain name fields of the same type. Then, the field values ​​of each name field of the same type can be compared in pairs. Thus, if it is determined that the field values ​​of name fields of the same type are the same, the comparison result of the key fields is determined to be that the two key fields being compared are the same.

[0050] If the comparison results show that the two key fields being compared are identical, it can be determined that there is a data conflict between the two key fields. For example, if the corresponding field value of each of the two key fields that represent the identifier of a network element is "1", then it can be known that both key fields represent the identifier of the network element as "1", and it can be determined that there is a data conflict between the two key fields.

[0051] However, since these two key fields come from network management data in different management areas, the corresponding service data are generated by different network element devices. Therefore, when merging the two network management data, it is necessary to modify at least one of the two key fields with data conflicts according to the preset processing rules so that the two key fields are different after modification. This will make it easier to find the service data of the corresponding network element device in the merged network management data in a timely manner, thereby reducing the occurrence of data confusion.

[0052] In some exemplary embodiments, the modification of at least one of the two key fields with data conflict in step S102 to eliminate the data conflict includes: adding a region identifier of the management area corresponding to the key field in at least one of the two key fields with data conflict.

[0053] Among them, the area identifier of the management area is the only information that identifies the management area. Through the area identifier, it can be clearly determined that the network management data comes from the management area corresponding to the area identifier.

[0054] When data conflicts exist, the region identifier of the management area corresponding to the key field can be added to all key fields with data conflicts to ensure that there are no more data conflicts between the modified key fields.

[0055] For example, when there is a data conflict between the key fields of network management data from management area A (e.g., indicating that the service type performed by the network element is type 1) and the key fields of network management data from management area B (e.g., indicating that the service type performed by the network element is type 1), the area identifier A (or B) corresponding to the key field can be added to all key fields indicating that the service type performed by the network element is type 1. This will obtain the key fields of the network management data from management area A (A-type 1) and the key fields of the network management data from management area B (B-type 1), so that the network management data in different management areas can be distinguished and the processing efficiency of the merged network management data can be improved.

[0056] In some exemplary embodiments, step S102, modifying at least one of the two key fields that have data conflicts to eliminate the data conflict, includes: modifying the field value of at least one of the two key fields that have data conflicts to the sum of the field value and a preset offset number of bits, while keeping the field value of the other key field unchanged.

[0057] Among them, the preset offset number of bits is greater than the maximum number of network management data in the management area corresponding to the key field.

[0058] When modifying at least one of two key fields that have data conflicts using data offset, one of the key fields can be kept unchanged while only the other key field is changed. In this way, the modified key field can be distinguished from the unmodified key field.

[0059] For example, if the key fields that cause data conflicts include a first key field and a second key field, and the maximum number of network management data in the management area corresponding to the first key field is 300, then only the first key field can be offset by 300, while keeping the second key field unchanged. In this way, the modified second key field will be different from the first key field, thereby eliminating the data conflict.

[0060] In some embodiments, if the key fields with data conflicts include three key fields (e.g., the field value of the first key field, the second key field, and the third key field, all representing the same business type A, with a field value of 20), and the maximum number of network management data in the management area corresponding to the second key field is 3000, then through multiple rounds of pairwise comparisons and modifications, the modified field values ​​of each key field can be obtained as: 20, 20+3000, and 20+6000, respectively. This allows the three key fields to be distinguished, facilitating subsequent data processing of each key field.

[0061] In some exemplary embodiments, step S102, which modifies at least one of two key fields that have data conflicts to eliminate the data conflict, includes: obtaining a plurality of preset values ​​in a preset order; and sequentially modifying each key field to the preset value according to a predetermined processing order.

[0062] The preset order is the pre-defined order in which each key field is processed. Multiple preset values ​​with a preset order are preset values ​​with a sequential relationship, such as A11, A12, A13, A14, A15, ..., A1n, where n is an integer greater than 1.

[0063] If the target network management database already contains field values ​​corresponding to the four key fields A11, A12, A13, and A14, and the key field of the network management data to be merged is A12, which is a duplicate of A12 in the target network management database, the key field of the network management data to be merged can be changed from "A12" to "A15". This will ensure that the key fields in the merged target network management database are not duplicated, allowing for quick querying and processing of the business data corresponding to the key field stored in the target network management database, thereby improving data processing efficiency.

[0064] In some exemplary embodiments, the network management data in each control domain is stored in the corresponding storage partitions of the target network management database.

[0065] Since each storage partition stores network management data from the same management area, the target network management system can independently manage the network management data in each management domain. For example, it can perform operations such as querying, modifying, adding, or deleting the network management data in each management domain, thereby improving the processing speed of network management data in each management domain.

[0066] For example, if it is necessary to merge all network management data from management area A and all network management data from management area B, then all network management data from management area A can be stored in the first storage partition corresponding to the first control domain, and all network management data from management area B can be stored in the second storage partition corresponding to the second control domain. This reduces the confusion of network management data from different management areas and ensures the relative independence of the merged network management data.

[0067] In some exemplary embodiments, merging multiple network management data into the target network management database in step S103 includes: merging multiple network management data into the target network management database based on an incremental insertion method.

[0068] The cumulative insertion method involves sequentially inserting multiple network management data items after the preceding network management data items. For example, the first network management data item is first stored in the target network management database, then the second network management data item is stored in the next storage address of the first network management data item in the target network management database, and so on, until multiple network management data items are sequentially stored in the target network management database.

[0069] In some embodiments, if the target network management database itself stores multiple original network management data, then the network management data subsequently stored in the target network management database can be accumulated and inserted into the storage address after these original network management data to avoid network management data confusion.

[0070] For example, if the target network management database contains 100 original network management records, and 10 more network management records managed by the network management system to be merged need to be merged into the target network management database, then these 10 network management records need to be stored in the 101st to 110th storage addresses of the target network management database. This will make the merged network management data clear, accurate, and easy to manage.

[0071] In some exemplary embodiments, after merging multiple network management data into the target network management database in step S103, the method further includes: obtaining the first number of the multiple network management data being detected; detecting the second number of newly added network management data in the merged target network management database; and determining that the network management data merging is successful if the first number equals the second number.

[0072] The first number represents the number of network management data entries to be merged into the target network management database, and the second number represents the number of new network management data entries added to the target network management database when the data merging is completed.

[0073] For example, if there are 30 network management data entries to be merged, and the target network management database already stores 50 network management data entries, then before merging the data, it is necessary to perform data conflict detection on these 30 network management data entries to confirm whether there are any data conflicts between the key fields of these 30 network management data entries and the key fields of the 50 network management data entries already stored in the target network management database.

[0074] Furthermore, after completing the data merging, it is necessary to determine whether the number of newly added network management data entries in the target network management database is equal to 30. If it is equal to 30, it means that all the network management data to be merged has been stored in the target network management database. If it is not equal to 30, it means that there is an anomaly such as loss of network management data or incorrect merging of network management data during the above data merging process. In this case, it is necessary to issue a reminder message in a timely manner to inform the operation and maintenance personnel that there is an anomaly in the network management data merging process, so that the operation and maintenance personnel can further process the network management data.

[0075] In some exemplary embodiments, network management data includes: backup data, and / or, dynamic data.

[0076] Among them, backup data is the data obtained by backing up multiple network management data generated by the network management system to be merged within a preset time period; dynamic data is the real-time business data generated by the network management system to be merged during operation.

[0077] During the process of merging network management data, data can be merged based on backup data (i.e., offline data) and / or dynamic data (i.e., online data), enabling the merging of multiple network management data in different application scenarios.

[0078] The key fields of each network management data include at least one of the following: the network element's object identifier (OID), the network element's identification code (e.g., the network element's universally unique identifier (UUID), the network element's name, the network element's network address (e.g., the Internet Protocol (IP) address), the service data identifier, and the service protection group identifier.

[0079] By merging multiple network management data from different application scenarios based on the aforementioned key fields of various types, the merged network management data can be applied to different application scenarios.

[0080] Figure 2 is a block diagram of a network management device provided in an embodiment of this disclosure. As shown in Figure 2, the network management device 200 includes, but is not limited to, the following modules.

[0081] The conflict detection module 201 is configured to perform data conflict detection on key fields of multiple network management data, which come from at least two management areas.

[0082] Modify module 202 to modify at least one of the two key fields that have data conflicts in order to eliminate the data conflict.

[0083] The merging module 203 is configured to merge multiple network management data into a target network management database. The target network management database includes multiple control domains, and each control domain manages all network management data in a management area.

[0084] It should be noted that the network management device in this embodiment can implement any of the data processing methods in this disclosure.

[0085] According to the network management device of this disclosure embodiment, a conflict detection module performs data conflict detection on key fields of multiple network management data to determine whether there are data conflicts between the key fields of the multiple network management data. This allows the modification module to modify at least one of the two key fields that conflict before data merging, in the event of a data conflict between any two key fields, to eliminate the data conflict and thus prevent data conflicts from occurring between the modified network management data. Since the multiple network management data come from at least two management areas, merging multiple network management data into the target network management database using the merging module enables the data stored in the target network management database to cover data from more management areas, expanding the jurisdiction of the target network management. Furthermore, the target network management database includes multiple control domains, with each control domain managing all network management data from one management area. This allows for independent management of all network management data from one management area using a single control domain, ensuring the accuracy of the target network management's processing of network management data in each control domain and significantly improving the data processing efficiency of the target network management.

[0086] It should be clarified that this disclosure is not limited to the specific configurations and processes described in the foregoing embodiments and shown in the figures. For the sake of convenience and brevity, detailed descriptions of known methods are omitted here, and the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0087] Figure 3 is a block diagram of another network management device provided in this embodiment. As shown in Figure 3, the network management device 300 includes, but is not limited to, the following modules: preparation module 301, conflict identification module 302, conflict handling module 303, and merging module 304.

[0088] The preparation module 301 is configured to acquire network management data of multiple network management systems to be merged. Each network management system to be merged is used to manage the data of multiple network element devices within a management area.

[0089] For example, the network management systems to be merged include U31 network management systems and / or Unified Management Expert (UME) network management systems. U31 network management systems can be those with significantly different software versions compared to the target network management system, or they can be those with the same software version as the target network management system; this application does not impose any restrictions on this.

[0090] In some embodiments, the UME network management system can also be used as the target network management system, thereby merging network management data from multiple management areas that are not originally covered by the UME network management system into the UME network management system, so as to expand the management area of ​​the UME network management system.

[0091] In some embodiments, the preparation module 301 is further configured to upgrade the software version of the network management system to be merged, so as to use the upgraded network management system data as the network management system data to be merged; or, to back up multiple network management system data generated by the network management system to be merged, and obtain backup data.

[0092] Conflict identification module 302: Configured to set the network management data that needs to be detected for data conflict according to the user policy (or, default policy), as well as the key fields of the network management data; then, perform data conflict detection on the network management data of multiple network management systems to be merged input by the preparation module 301.

[0093] The network management data includes backup data and / or dynamic data. Dynamic data refers to real-time service data generated during the operation of the network management system to be merged. Key fields of the network management data include at least one of the following: network element OID, network element UUID, network element name, network element IP address, service data identifier, and service protection group identifier.

[0094] In some embodiments, the conflict identification module 302 extracts key fields from multiple network management data; performs pairwise comparisons on all similar key fields to obtain comparison results; and determines that there is a data conflict in the corresponding key fields if the comparison results are the same.

[0095] In some embodiments, after determining that there is a data conflict in the corresponding key fields, the key fields of the network management data with data conflicts can be displayed in the form of a list, so that the operation and maintenance personnel can quickly determine the relevant content of the network management data with data conflicts through the list. Compared with the manual verification of network management data, it can speed up the management of network management data and reduce the occurrence of data omission anomalies.

[0096] The conflict handling module 303 is configured to modify at least one of the two key fields that have a data conflict in order to eliminate the data conflict, according to a preset processing rule, when any two key fields have a data conflict.

[0097] In some embodiments, the conflict handling module 303 may modify at least one of the two key fields that have data conflicts using any of the following modification methods:

[0098] 1) In at least one of the two key fields that have data conflicts, add the region identifier of the management region corresponding to the key field;

[0099] 2) Modify the value of one of the two critical fields with data conflicts to the sum of the field value and the preset offset bits, while keeping the value of the other critical field unchanged; wherein the preset offset bits are greater than the maximum number of network management data in the management area corresponding to the critical field;

[0100] 3) Obtain multiple preset values ​​in a preset order; modify each key field to the preset value in turn according to the predetermined processing order.

[0101] For example, if the preset offset bits are set to 300,000, at least one of the two key fields with data conflicts can be shifted backward by 300,000 bits to obtain the modified key field. For example, if the key field with data conflicts is the OID of the network element, the modified key field is OID + 300,000.

[0102] For example, if the key field with data conflict is the network element name A, and the area identifier of the management area corresponding to the key field is area M, then the modified key field is "area M + A".

[0103] In some embodiments, if the network management data corresponding to the key field with data conflict is backup data, the key field can be obtained by scanning the backup data, and the field value in the key field can be modified in batches to obtain the modified key field.

[0104] If the network management data corresponding to the key fields with data conflicts is dynamic data, the modified key fields can be obtained by querying the database storing the dynamic data (e.g., the database of the network management data to be merged) and batch modifying the field values ​​in the obtained key fields (e.g., by using database languages ​​(e.g., Structured Query Language, SQL statements) to batch modify the field values).

[0105] By automatically modifying key fields with data conflicts as described above, the problem that cannot be modified manually can be solved (e.g., manual modification cannot modify key identifying fields such as network element names), and the speed of modifying key fields can be improved, thereby greatly saving labor costs.

[0106] After completing the above modifications, the conflict handling module 303 will send the modified network management data back to the database of its original network management system to be merged, so that the merging module 304 can merge the data according to the modified network management data.

[0107] The merging module 304 is configured to merge multiple network management data into a target network management database.

[0108] Among them, the target network management database is the database of the target network management system, which is used to store the merged network management data.

[0109] For example, if the network management systems to be merged include three management areas (e.g., three cities, three communities, etc.), a first control domain named A can be first constructed in the target network management system, and a first storage partition can be set in the target network management system database. This first storage partition is the storage partition corresponding to the first control domain. Then, all network management data from management area A is stored in the first storage partition to merge multiple network management data from the network management systems to be merged in management area A into the target network management system.

[0110] Similarly, using the above merging method, all network management data from management area B and management area C are merged into the target network management database. Correspondingly, a second control domain named B and a third control domain named C are constructed in the target network management database; a second storage partition is set in the target network management database, corresponding to the second control domain; a third storage partition is set in the target network management database, corresponding to the third control domain; then, all network management data from management area B is stored in the second storage partition, and all network management data from management area C is stored in the third storage partition, thereby achieving the merging of network management data from the three management areas.

[0111] The merged target network management system can independently manage network elements in three management areas (A, B, and C) based on three separate control domains, thereby expanding the control scope of the target network management system. Furthermore, since the three control domains are independent of each other and the corresponding storage partitions have the same data storage format, the management efficiency of the target network management system for each network element can be greatly improved. In addition, the values ​​in the key fields of each network management data in the target network management database are globally unique, which can speed up the query speed of network management data.

[0112] In some embodiments, the target network management system can also merge multiple network management system data into the target network management system database based on an incremental insertion method, so that the network management system data of the network management system to be merged with a small amount of data can be quickly merged into the target network management system database, thereby speeding up the data merging process.

[0113] In some embodiments, the merging module 304 can also be configured to verify the merged network management data. For example, the merging module 304 obtains the first count of the multiple network management data being tested; detects the second count of the newly added network management data in the target network management database after merging; if the first count is equal to the second count, it determines that the network management data merging is successful; if the first count is not equal to the second count, it determines that the network management data merging has failed.

[0114] The reasons for network management data merging failure may include: the loss of some network management data during the data merging process, and / or the merging of several network management data entries with the same key fields from different management areas.

[0115] If it is determined that the network management data merging fails, the network management device 300 needs to be used again to merge multiple network management data using the above data processing method until the first number and the second number are the same, so as to ensure the accuracy of the merged network management data.

[0116] By using network management device 300 to automatically merge the network management data of multiple network management systems to be merged, compared with the manual processing method in the existing technology, the merging time of network management data can be greatly shortened, thereby improving the merging efficiency of network management data of multiple network management systems to be merged.

[0117] In some exemplary embodiments, Figure 4 is a flowchart illustrating a method for merging network management data of multiple network management systems to be merged, as provided in this disclosure.

[0118] The network management systems to be merged include: a first network management system, a second network management system, and a third network management system. The first network management system corresponds to the management area M and is used to manage 10,000 network element devices. The second network management system corresponds to the management area N and is used to manage 8,000 network element devices. The third network management system corresponds to the management area P and is used to manage 5,000 network element devices.

[0119] As shown in Figure 4, the method includes, but is not limited to, the following steps S401 to S406.

[0120] In step S401, the preparation module 301 upgrades the software versions of the first network management system to be merged, the second network management system to be merged, and the third network management system to be merged, respectively, so that the software versions of the three network management systems to be merged are the same; and backs up the network management data in the databases of the above three network management systems to be merged, thereby obtaining the backup data of the network management data of each network management system to be merged.

[0121] Table 1 shows the key fields of the network management data in the databases of each network management system to be merged.

[0122] Table 1 Key Fields of Network Management Data

[0123] As shown in Table 1, key fields for network management data can be set for three dimensions: network element, protection group, and service. The key fields that can be set for the network element dimension include: network element UUID, network element OID, network element name, and network element IP address.

[0124] The key fields that can be set for the protection group dimension include: business protection group identifier; this business protection group identifier is used to identify the backup business channel that protects the normal business channel. When the normal business channel cannot transmit business data, the backup business channel can be used to transmit business data to ensure the effective transmission of business data.

[0125] Key fields that can be set for the business dimension include: business data identifier, which is used to characterize the type of business data.

[0126] By employing multiple key fields across different dimensions, network management data can be comprehensively segmented, facilitating the querying and processing of multiple network management data sets and improving the efficiency of network management data processing.

[0127] In step S402, the conflict identification module 302 performs data conflict detection on the key fields of the network management data in the database of each network management system to be merged, based on preset key fields, in order to determine the key fields where data conflicts exist.

[0128] Before data merging, the key fields of the network management data in the database of each network management system to be merged are unique. In other words, there are no duplicate key fields in the database of each network management system to be merged.

[0129] In some embodiments, the conflict identification module 302 extracts all key fields of the network management data in the databases of the three network management systems to be merged, and performs pairwise comparisons on all similar key fields to obtain comparison results; if the comparison results are the same, it determines that there is a data conflict in the corresponding key fields, and obtains all key fields.

[0130] In some embodiments, all key fields of the network management data in the database of the first network management system to be merged can be compared with all key fields of the network management data in the database of the second network management system to be merged to obtain a first comparison result; then, all key fields of the network management data in the database of the first network management system to be merged can be compared with all key fields of the network management data in the database of the third network management system to be merged to obtain a second comparison result; finally, all key fields of the network management data in the database of the second network management system to be merged can be compared with all key fields of the network management data in the database of the third network management system to be merged to obtain a third comparison result. Combining the above three comparison results, all key fields with data conflicts can be determined.

[0131] For example, Table 2 shows a comparison table of key fields in network management data that have data conflicts.

[0132] Table 2: Comparison of Key Fields in Network Management Data with Data Conflicts

[0133] As shown in Table 2, the key fields of the network management data of each network management system to be merged are compared using the network element UUID, network element OID, network element name, and network element IP address as key fields. Specifically, the key fields of the network management data of the first network management system to be merged (management area M, e.g., network element UUID A11, network element OID B12) conflict with the key fields of the network management data of the second network management system to be merged (management area N). Therefore, the key fields with conflicting data are: network element UUID A11 and network element OID B12.

[0134] Similarly, if the key field of the network management data of the first network management system to be merged in the management area M (e.g., the network element OID is C12) conflicts with the key field of the network management data of the third network management system to be merged in the management area P, then the key field that conflicts with the data can be identified as: the network element OID is C12.

[0135] If the key fields of the network management data of the second network management system to be merged in the management area N (e.g., network element name is D13, network element IP address is E14) conflict with the key fields of the network management data of the third network management system to be merged in the management area P, then the key fields that conflict with the data can be identified as: network element name is D13, network element IP address is E14.

[0136] In some embodiments, the conflict identification module 302 includes a front end (not shown in FIG3) and a back end (not shown in FIG3). The conflict identification module 302 interacts with the database (e.g., the database of one of the multiple network management systems to be merged) through the operating system (not shown in FIG3) to realize data conflict detection of key fields of network management data in the databases of different network management systems.

[0137] Figure 5 is a schematic diagram illustrating the data interaction process between a conflict identification module in a network management device according to an embodiment of this disclosure and other devices. As shown in Figure 5, the data interaction process includes the following steps S502 to S511.

[0138] In step S501, the front end of the conflict identification module 302 sends a connection request to the database.

[0139] Among them, the database is the first database to be merged into the network management system.

[0140] In step S502, the database sends a connection response to the front end of the conflict identification module 302, so that the front end of the conflict identification module 302 can successfully establish a data connection with the database and obtain the dynamic network management data stored in the database.

[0141] While performing steps S501 to S502, the conflict identification module 302 can also perform steps S503 to S504 to obtain backup data of the second network management system to be merged stored in the operating system.

[0142] In step S503, the front end of the conflict identification module 302 sends a backup data request to the operating system.

[0143] In step S504, the operating system sends a backup data response to the front end of the conflict identification module 302 so that the conflict identification module 302 can obtain the backup data of the second network management system to be merged.

[0144] The backup data of the second network management system to be merged includes: key fields of the backup network management data of the second network management system to be merged (e.g., using the network element OID as the key field).

[0145] In step S505, the front end of the conflict identification module 302 queries the back end of the conflict identification module 302 for network management data with network element OID as the key field in the database of the first network management system to be merged.

[0146] In step S506, the backend of the conflict identification module 302 sends a query request to the database.

[0147] The query request is used to request network management data with network element OID as the key field in the database of the first network management system to be merged.

[0148] In step S507, the database sends a query response back to the backend of the conflict identification module 302 so that the network management data in the database of the first network management system to be merged is stored with the network element OID as the key field.

[0149] In step S508, the conflict identification module 302 queries the backup data of the second network management system to be merged, and obtains the network management data with network element OID as the key field in the backup data of the second network management system to be merged.

[0150] In step S509, the backend of the conflict identification module 302 compares the key fields of the network management data in the backup data of the second network management system to be merged with the key fields of the network management data in the database of the first network management system to be merged to determine whether there is a data conflict.

[0151] In step S510, if a data conflict is determined to exist, the backend of the conflict identification module 302 sends the key field of the data conflict (i.e., the OID of the conflicting network element) to the frontend of the conflict identification module 302.

[0152] In step S511, the front end of the conflict identification module 302 displays the key fields where data conflicts exist, as well as the network element name corresponding to the key fields where data conflicts exist, in the display interface.

[0153] By processing the network management data of each network management system to be merged in the above manner, the key fields with data conflicts in the network management data of each network management system to be merged can be quickly and accurately identified. This allows the subsequent conflict handling module to modify the key fields with data conflicts to eliminate the data conflicts.

[0154] In step S403, if there is a data conflict between any two key fields, the conflict handling module 303 modifies at least one of the two key fields to eliminate the data conflict according to the preset processing rules.

[0155] The conflict handling module 303 can first establish a communication connection with the databases of each network management system to be merged. Then, using the key field with data conflict (such as the conflicting network element OID) as an index, it queries the databases of each network management system to be merged and modifies the key field stored in the queried database to obtain the modified key field. This ensures that the key fields in the databases of each network management system to be merged no longer have data conflicts.

[0156] For example, Table 3 shows a comparison table of key fields of network management data before and after modification in the embodiments of this disclosure.

[0157] Table 3: Comparison of key fields in network management data before and after modification.

[0158] As shown in Table 3, if the key field of the network management data to be merged in the management area M (e.g., the network element UUID is A11) is a key field with data conflict, then its network element UUID can be changed from A11 to A15.

[0159] If the key field of the network management data to be merged in the management area M (e.g., the network element OID is B12) is a key field with data conflict, then its network element OID can be changed from B12 to B12+300000.

[0160] If the key field of the network management data to be merged in the management area M (e.g., the network element OID is C12) is a key field with data conflict, then its network element OID can be changed from C12 to C12+300000;

[0161] If the key field of the network management data to be merged in the management area of ​​region N (e.g., the network element name is D13) is a key field with data conflict, then its network element name can be changed from D13 to region N-D13;

[0162] If a critical field (e.g., network element IP address E14) in the network management data to be merged in the management area N is a critical field with data conflict, then its network element IP address can be changed from E14 to E15.

[0163] In step S404, the conflict resolution module 303 automatically backs up and saves the modified network management data in the storage space of the conflict resolution module 303.

[0164] In step S405, the merging module 304 constructs three control domains, each corresponding to a management area; then, the modified network management data to be merged for each management area is stored in the corresponding control domain.

[0165] The three control domains are: a first control domain, a second control domain, and a third control domain. The first control domain corresponds to the first network management system to be merged, and the first control domain corresponds to the first storage partition in the target network management database; the second control domain corresponds to the second network management system to be merged, and the second control domain corresponds to the second storage partition in the target network management database; the third control domain corresponds to the third network management system to be merged, and the third control domain corresponds to the third storage partition in the target network management database.

[0166] When storing data, simply store the modified network management data of the first network management system to be merged in the first storage partition, the modified network management data of the second network management system to be merged in the second storage partition, and the modified network management data of the third network management system to be merged in the third storage partition to achieve the merging of network management data and obtain the target network management system and the target network management system database.

[0167] In step S406, the merging module 304 also needs to obtain the sum of the number of all network management data entries of the first, second, and third network management systems to be merged before the data merge, and use this sum as the first entry count; then, it detects the second entry count of the newly added network management data in the target network management database after the merge; if the first entry count is equal to the second entry count, it is determined that the network management data merge is successful.

[0168] If the first number is not equal to the second number, it indicates that the network management data merging has failed, thus prompting the operations and maintenance personnel that there is data loss or data merging error during the network management data merging process, so that the operations and maintenance personnel can further process the network management data.

[0169] By merging the network management data of the three network management systems to be merged in the above manner, key fields with data conflicts in the network management data of each network management system to be merged can be automatically modified to avoid data chaos caused by duplicate data between network management data stored in the target network management database. Furthermore, by automatically modifying key fields with data conflicts in batches, the data processing speed can be greatly improved, eliminating the need for manual data merging and improving the efficiency of network management data merging.

[0170] In some embodiments, there are already three running jurisdictions in the target network management system (e.g., the first jurisdiction, the second jurisdiction, and the third jurisdiction, each jurisdiction corresponding to a management area (i.e., the first jurisdiction corresponds to the first management area, the second jurisdiction corresponds to the second management area, and the third jurisdiction corresponds to the third management area)). In order to merge the network management data of two network management systems to be merged (e.g., the fourth network management system used to manage the data of network elements in the fourth management area, and the fifth network management system used to manage the data of network elements in the fifth management area) into the target network management system, the steps of the data processing method shown in Figure 6 are required to merge the network management data.

[0171] Figure 6 is a flowchart illustrating a method for data processing using a network management device according to an embodiment of this disclosure. As shown in Figure 6, the method includes, but is not limited to, the following steps S601 to S605.

[0172] In step S601, the preparation module 301 upgrades the software versions of the fourth network management system and the fifth network management system to the same version as the target network management system. Then, it backs up the network management data in the fourth network management system, the fifth network management system and the target network management system respectively to obtain the backup data of the fourth network management system, the backup data of the fifth network management system and the backup data of the target network management system.

[0173] In some embodiments, the preparation module 301 may also export the key fields of the network management data in the fourth network management system, the fifth network management system and the target network management system in the form of a data list, so as to facilitate subsequent data verification.

[0174] In step S602, the conflict identification module 302 performs data conflict detection on the key fields of each network management data in the backup data of the fourth network management system, the backup data of the fifth network management system, and the backup data of the target network management system, in order to identify the key fields where data conflicts exist.

[0175] The conflict identification module 302 can extract all key fields from the backup data of the fourth network management system, the backup data of the fifth network management system, and the backup data of the target network management system; then, it compares all similar key fields pairwise to obtain comparison results; if the comparison results are the same, it determines that there is a data conflict in the corresponding key fields.

[0176] In some embodiments, the backup data of each of the above network management systems can also be replaced with the dynamic data of each network management system to achieve online dynamic merging of network management system data.

[0177] In step S603, if there is a data conflict between any two key fields, the conflict handling module 303 modifies at least one of the two key fields to eliminate the data conflict according to the preset processing rules.

[0178] For example, if it is determined that there are key fields with data conflicts in the backup data of the target network management system, then the key fields with data conflicts can be modified in batches in the network management data of the backup data of the target network management system.

[0179] For example, if it is determined that there are key fields with data conflicts in the backup data of the fourth network management system, then the key fields with data conflicts can be modified in batches in the network management data of the backup data of the fourth network management system.

[0180] In step S604, the merging module 304 creates a fourth control domain and a fifth control domain on the target network management system, imports all network management data from the backup data of the modified fourth network management system into the fourth control domain, and imports all network management data from the backup data of the modified fifth network management system into the fifth control domain.

[0181] The fourth control domain corresponds to the fourth storage partition in the target network management database, and the fifth control domain corresponds to the fifth storage partition in the target network management database. All network management data in the backup data of the modified fourth network management can be stored in the fourth storage partition, and all network management data in the backup data of the modified fifth network management can be stored in the fifth storage partition.

[0182] In step S605, the merging module 304 obtains the sum of the number of all network management data of the fourth network management system before the data merging and the number of all network management data of the fifth network management system before the data merging, and uses this sum as the first count; then, it detects the second count of newly added network management data in the target network management database after merging; if the first count is equal to the second count, it is determined that the network management data merging is successful.

[0183] By adopting the above data processing method, the network management data of multiple network management systems to be merged can be merged into a target network management system that already exists in multiple running jurisdictions. This expands the control scope of the target network management system, enabling the management of data of network elements in multiple management areas to be managed by a single target network management system. This allows the data generated by network elements in multiple management areas to be managed in a unified manner, thereby improving data management efficiency.

[0184] In some embodiments, the network management system to be merged is a network management system with a software version lower than that of the target network management system (for example, the network management system to be merged is UME network management system A with software version 1.0, while the target network management system is UME network management system B with software version 2.0). In order to facilitate the management of network management data, it is necessary to merge the network management data in the network management system to be merged into the target network management system. The steps of the data processing method shown in Figure 7 are required to merge the network management data.

[0185] Figure 7 is a flowchart illustrating another method for data processing using a network management device according to an embodiment of this disclosure. As shown in Figure 7, the method includes, but is not limited to, the following steps S701 to S705.

[0186] In step S701, the preparation module 301 obtains the software version of UME network management A and the software version of UME network management B respectively; when it is determined that the software version of UME network management A is lower than the software version of UME network management B, the software version of UME network management A is upgraded, and the network management data of the upgraded UME network management A is backed up to obtain the backup data.

[0187] In step S702, the conflict identification module 302 performs data conflict detection on the key fields of the network management data in the backup data of the upgraded UME network management A and the key fields of the network management data in UME network management B, in order to identify the key fields where data conflicts exist.

[0188] In step S703, if there is a data conflict between any two key fields, the conflict handling module 303 modifies at least one of the two key fields to eliminate the data conflict according to the preset processing rules.

[0189] In step S704, the merging module 304 merges the network management data in the backup data of the modified UME network management A into the database of UME network management B based on the cumulative insertion method.

[0190] In step S705, the merging module 304 obtains the number of network management data entries in the backup data of the UME network management A before modification as the first number; then, it checks the second number of newly added network management data entries in the database of the merged UME network management B; if the first number equals the second number, it is determined that the network management data merging is successful.

[0191] By merging the network management data of the two UME network management systems using the above-mentioned cumulative insertion method, the uniqueness of the values ​​of each key field in the database of the merged UME network management system B can be achieved, thereby improving the data query speed. Furthermore, compared with the conventional manual merging method, the network management data merging method in this disclosure can shorten the original manual time of 1-5 days to less than 30 minutes, which can greatly improve the efficiency of network management data merging and reduce labor costs.

[0192] Figure 8 is a block diagram of another network management device provided in an embodiment of this disclosure.

[0193] As shown in Figure 8, the network management device can be an electronic device, which includes at least one processor 801, at least one memory 802, and one or more I / O interfaces 803. The processor 801, memory 802, and I / O interfaces 803 are interconnected via a bus 804. The memory 802 stores one or more computer programs, which are executed by the at least one processor 801 to enable the at least one processor 801 to implement any of the data processing methods described in the above embodiments.

[0194] The modules in the aforementioned electronic devices can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0195] This disclosure also provides a computer-readable storage medium storing a computer program thereon, wherein the computer program, when executed by a processor, implements any of the data processing methods described in the above embodiments. The computer-readable storage medium may be a volatile or non-volatile computer-readable storage medium.

[0196] This disclosure also provides a computer program product, including computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code, wherein when the computer-readable code is run in the processor of an electronic device, the processor in the electronic device executes the above-described data processing method.

[0197] The data processing method in this embodiment automatically detects data conflicts in key fields of multiple network management data. If a data conflict is found, it is automatically modified, thereby efficiently and accurately merging network management data. Furthermore, the target network management database includes multiple control domains, and each control domain manages all network management data in a management area. This allows for the independent management of all network management data from a management area using a single control domain (e.g., avoiding confusion caused by identifiers), ensuring the accuracy of the target network management system's processing of network management data in each control domain, and greatly improving the data processing efficiency of the target network management system.

[0198] Those skilled in the art will understand that all or some of the steps, systems, and devices disclosed above, as well as the functional modules / units, can be implemented as software, firmware, hardware, or suitable combinations thereof. In hardware implementations, the division between functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed collaboratively by several physical components.

[0199] Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit (ASIC). Such software may be distributed on a computer-readable storage medium, which may include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable program instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), static random access memory (SRAM), flash memory or other memory technologies, portable compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically contain computer-readable program instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.

[0200] The computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0201] Computer program instructions used to perform the operations of this disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuitry, such as programmable logic circuitry, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), is personalized by utilizing the status information of the computer-readable program instructions to implement various aspects of this disclosure.

[0202] The computer program product described herein can be implemented specifically through hardware, software, or a combination thereof. In one alternative embodiment, the computer program product is specifically embodied in a computer storage medium; in another alternative embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0203] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0204] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0205] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0206] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those marked in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, the execution order of which may be determined based on the functions involved in each block. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0207] Example embodiments have been disclosed herein, and while specific terminology has been used, it is intended and should be interpreted only in a general illustrative sense and is not intended to be limiting. In some instances, it will be apparent to those skilled in the art that features, characteristics, and / or elements described in conjunction with particular embodiments may be used alone, or in combination with features, characteristics, and / or elements described in conjunction with other embodiments, unless otherwise expressly indicated. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the scope of this disclosure.

Claims

1. A data processing method, comprising: Data conflict detection is performed on key fields of multiple network management data, where the multiple network management data originate from at least two management regions; In the event of a data conflict between any two of the key fields, at least one of the two key fields with the data conflict shall be modified to eliminate the data conflict; Multiple network management data are merged into a target network management database, which includes multiple control domains, and one control domain manages all network management data in one control area.

2. The method according to claim 1, wherein, The data conflict detection of key fields in multiple network management data includes: Extract key fields from multiple network management data; Perform pairwise comparisons on all similar key fields to obtain the comparison results; If the comparison results show that the two key fields being compared are the same, it is determined that the two identical key fields constitute a data conflict.

3. The method according to claim 1, wherein, The modification of at least one of the two key fields that have a data conflict to eliminate the data conflict includes: In at least one of the two key fields where data conflict exists, add the region identifier of the management region corresponding to the key field.

4. The method according to claim 1, wherein, The modification of at least one of the two key fields that have a data conflict to eliminate the data conflict includes: Modify the value of one of the two key fields that have data conflicts to the sum of the field value and the preset offset bits, while keeping the value of the other key field unchanged; Wherein, the preset offset number of bits is greater than the maximum number of network management data in the management area corresponding to the key field.

5. The method according to claim 1, wherein, The modification of at least one of the two key fields that have a data conflict to eliminate the data conflict includes: Obtain multiple preset values ​​in a preset order, wherein the preset order is a pre-defined order in which each of the key fields is processed; According to the predetermined processing order, each of the key fields is modified to the preset value in turn.

6. The method according to any one of claims 1 to 5, wherein, The network management data in each of the aforementioned control domains is stored in the corresponding storage partitions of the target network management database.

7. The method according to any one of claims 1 to 5, wherein, The step of merging multiple network management data sets into the target network management database includes: Based on the cumulative insertion method, multiple network management data are merged into the target network management database.

8. The method according to any one of claims 1 to 5, wherein, After merging the multiple network management data into the target network management database, the method further includes: Obtain the first number of the multiple network management data items being detected; Detect the second newly added record of the network management data in the merged target network management database; If the first number equals the second number, the network management data merging is considered successful.

9. The method according to any one of claims 1 to 5, wherein, The network management data includes: backup data, and / or, dynamic data.

10. A network management device, comprising a memory and a processor; the memory storing a computer program executable by the processor, wherein the computer program, when executed by the processor, implements the data processing method as described in any one of claims 1 to 9.

11. A computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the data processing method as described in any one of claims 1 to 9.

12. A computer program product comprising a computer program that, when executed by a processor, implements the data processing method as described in any one of claims 1 to 9.

Images