Data processing method and device, medium and product

Abstract

The invention provides a data processing method, which comprises the following steps: carrying out data conflict detection on key fields of a plurality of pieces of network management data from at least two management areas; under the condition that any two key fields have the data conflict, modifying at least one key field in the two key fields with the data conflict so as to eliminate the data conflict; the multiple pieces of network management data are merged into a target network management database, the target network management database comprises a plurality of management and control domains, and one management and control domain manages all the network management data in one management area. The disclosure also provides an electronic device, a computer readable medium, and a computer program product.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and in particular, to a data processing method, a network management device, a computer readable medium and a computer program product. BACKGROUND

[0002] With the continuous development of communication technology, more and more access devices are used, the types of services are more and more complex, and the number of communication networks is also growing explosively. In order to realize the centralized management of data in multiple regions, a manual method is usually used to merge the network management data in different regions to obtain complete network management data of the whole region.

[0003] However, in each region, different types of service data are represented by different identifiers. In different regions, the same identifier may be used to represent different service types, so that the merged network management data is in a data confusion state. Using the above manual processing method not only reduces the data processing efficiency, but also cannot guarantee the accuracy of data management. SUMMARY

[0004] The present disclosure provides a data processing method, a network management device, a computer readable medium and a computer program product.

[0005] In a first aspect, the present disclosure provides a data processing method, which includes: performing data conflict detection on key fields of a plurality of network management data, the plurality of network management data being from at least two management regions; in a case where data conflicts exist in any two key fields, modifying at least one key field of the two key fields with data conflicts to eliminate the data conflicts; and merging the plurality of network management data into a target network management database, the target network management database including a plurality of management domains, one management domain managing all network management data in one management region.

[0006] In a second aspect, the present disclosure provides a network management device, which includes: one or more processors; and a memory having one or more programs stored thereon, when the one or more programs are executed by the one or more processors, the one or more processors implement any of the data processing methods in the embodiments of the present disclosure.

[0007] In a third aspect, the present disclosure provides a readable storage medium, which stores a computer program, when the computer program is executed by a processor, the processor implements any of the data processing methods in the embodiments of the present disclosure.

[0008] In a fourth aspect, the present disclosure provides a computer program product, which includes a computer program, when the computer program is executed by a processor, the processor implements any of the data processing methods in the embodiments of the present disclosure.

[0009] The data processing method in the embodiment of the present disclosure automatically detects data conflicts of key fields of multiple network management data, and automatically modifies if data conflicts are found, thereby efficiently and accurately realizing the merging of network management data. Moreover, the target network management database includes multiple management and control domains, one management and control domain manages all network management data in one management area, and one management and control domain can be used to independently manage all network management data from one management area (such as avoiding confusion caused by identification), ensuring the processing accuracy of the target network management for network management data in each management and control domain, and greatly improving the data processing efficiency of the target network management. BRIEF DESCRIPTION OF DRAWINGS

[0010] In the drawings of the embodiments of the present disclosure:

[0011] Figure 1 A flowchart of a data processing method provided by the embodiments of the present disclosure is shown.

[0012] Figure 2 A composition block diagram of a network management device provided by the embodiments of the present disclosure is shown.

[0013] Figure 3 A composition block diagram of another network management device provided by the embodiments of the present disclosure is shown.

[0014] Figure 4 A flowchart of a method for merging network management data of multiple network management devices to be merged provided by the embodiments of the present disclosure is shown.

[0015] Figure 5 A flowchart of data interaction of a conflict identification module in a network management device with other devices provided by the embodiments of the present disclosure is shown.

[0016] Figure 6 A flowchart of a method for data processing of a network management device provided by the embodiments of the present disclosure is shown.

[0017] Figure 7 A flowchart of another method for data processing of a network management device provided by the embodiments of the present disclosure is shown.

[0018] Figure 8 A composition block diagram of still another network management device provided by the embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0019] In order for those skilled in the art to better understand the technical solutions of the present disclosure, the embodiments of the present disclosure are described in detail below with reference to the drawings.

[0020] The embodiments shown can be embodied in many different forms, and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to not only those skilled in the art, but also to others.

[0021] The accompanying drawings, which are included to provide a further understanding of the embodiments of the present disclosure and are incorporated in and constitute a part of this specification, illustrate embodiments of the present disclosure and together with the detailed description serve to explain the present disclosure, and should not be construed as limiting the present disclosure. The above and other features and advantages of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings.

[0022] The embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.

[0023] The terms used in the present disclosure are only used to describe specific embodiments, and are not intended to limit the present disclosure. As used in the present disclosure, the term "and / or" includes any and all combinations of one or more of the associated listed items. As used in the present disclosure, the singular forms "a" and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. As used in the present disclosure, the terms "comprising", "made of" designate the presence of the features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0024] Unless otherwise defined, all terms used in the present 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 a generally used dictionary should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and should not be interpreted in an idealized or overly formal sense, unless the present disclosure explicitly so defines.

[0025] With the continuous development of communication technology, more and more access devices are accessed, the types of services performed by various access devices are more and more complex, and the number of communication networks is also increasing explosively.

[0026] In order to uniformly manage the network management data in multiple regions, it is necessary to merge the network management data in multiple regions to improve the management efficiency of the network management data. However, since the key fields of the network management data in different regions may conflict, for example, two network element numbers in two regions are the same, usually, a manual way is used to compare the network management data in different regions one by one to filter out the network management data with data conflicts, and then the network management data is modified, and finally the modified network management data is merged to obtain network management data without data conflicts, so as to facilitate the management of the network management data.

[0027] However, in each region, different types of service data are represented by different identifiers; and in different regions, the same identifier can be used to represent different service types. When data is merged in the above manual manner, the merged network management data can be disordered, the accuracy of the modified network management data cannot be ensured, and the manual cost is increased.

[0028] To solve the above problems, the present application provides a data processing method, a network management device, a computer readable medium and a computer program product.

[0029] Figure 1 A flowchart of a data processing method provided by the embodiments of the present disclosure is shown. The data processing method is applied to a network management device. As shown in the figure, the data processing method includes but is not limited to the following steps. Figure 1

[0030] Step S101, data conflict detection is performed on the key fields of multiple network management data.

[0031] The multiple network management data come from at least two management regions. The management region represents the region that the network management device can govern. The network management device is used to manage the multiple network management data generated by the multiple network element devices in the management region.

[0032] The key field of the network management data refers to a field that cannot be repeated, such as the identifier field of the network element device, the service type field of the service data performed by the network element device, etc. If the key field of the network management data from one management region is the same as the key field of the network management data from another management region, it can be determined that there is a data conflict between the two key fields.

[0033] The network management data can also include other fields (such as fields representing service data, etc.), which can be repeated, such as a certain video data in a download service, which can be used by multiple different terminal users.

[0034] The key fields of the multiple network management data in each management region are not in data conflict, for example, in one management region, different identifiers are usually used to represent different types of service data. In different management regions, the same identifier can be used to represent different service types. If the multiple network management data in two different management regions need to be merged, the service types represented by the identifiers corresponding to the merged network management data can be disordered.

[0035] ​At this time, data conflict detection needs to be performed on the key fields of the plurality of network management data from the at least two management areas, so as to determine that there is no data duplication between the key fields in each network management data, thereby ensuring that each identifier in the combined network management data is used to represent different types of business data, in other words, ensuring the uniqueness of the meaning represented by the key fields in the combined network management data.

[0036] In step S102, at least one of the two key fields with data conflict is modified to eliminate the data conflict.

[0037] In some embodiments, at least one of the two key fields with data conflict can be modified according to a preset processing rule to eliminate the data conflict.

[0038] The preset processing rule is a rule preset for modifying the key field with data conflict. The key field is a field representing data conflict.

[0039] The preset processing rule can be used to modify both of the two key fields with data conflict, or to modify any one of the two key fields with data conflict. The specific modification depends on the application scenario corresponding to the plurality of network management data, which is not limited in the present application.

[0040] After modifying at least one of the two key fields with data conflict, there is no data conflict 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, facilitating subsequent management of the combined network management data.

[0041] In step S103, the plurality of network management data is combined into a target network management database.

[0042] The target network management database is used to store network management data governed by a target network management. The target network management database includes a plurality of control domains, and one control domain manages all network management data in one management area. The network management data in different control domains is used to be independently managed.

[0043] The control domain is a region constructed in the network management database and used to manage all network management data from the same management area. Each control domain is independent of each other and does not interfere with each other, but can be uniformly managed by the target network management.

[0044] For example, if the target network management database includes at least two management domains, the target network management device can independently manage the network management data in any one of the management domains without affecting the accuracy of the network management data in the other management domain. In addition, the target network management device can simultaneously query the network management data in each management domain to facilitate global data management.

[0045] The data processing method in the embodiments of the present disclosure can determine whether there is data conflict between the key fields of the plurality of network management data by performing data conflict detection on the key fields of the plurality of network management data, so as to modify at least one of the two key fields with data conflict according to a preset processing rule to eliminate the data conflict before data merging, thereby avoiding data conflict between the modified network management data. Since the plurality of network management data is from at least two management areas, the data stored in the target network management database can cover more data of the management areas by merging the plurality of network management data into the target network management database, thereby expanding the jurisdiction range of the target network management device. In addition, the target network management database includes a plurality of management domains, and one management domain manages all network management data in one management area. The target network management device can independently manage all network management data from one management area using one management domain. This not only ensures the accuracy of the target network management device in processing the network management data in each management domain, but also greatly improves the data processing efficiency of the target network management device.

[0046] In some exemplary embodiments, the data conflict detection on the key fields of the plurality of network management data in step S101 includes: extracting the key fields of the plurality of network management data; comparing all key fields of the same type with each other to obtain a comparison result; and determining that the two key fields compared are the same in the case that the comparison result is that the two key fields compared are the same.

[0047] All key fields of the same type means that the physical meanings represented by the key fields are the same. For example, the key fields are all used to represent the identifier of the network element device.

[0048] In some embodiments, the key field of the network management data can include a name field and a field value. When all key fields of the same type are compared with each other, the name fields in the key fields can be compared with each other first to obtain the name fields of the same type. Then, the field values of the name fields of the same type are compared with each other, so as to determine that the comparison result of the key fields is that the two key fields compared are the same in the case that the field values of the name fields of the same type are the same.

[0049] In a case where it is determined that the comparison result is the same for the two key fields of the comparison, it can be determined that there is a data conflict between the two key fields corresponding to the comparison result. For example, if the field values of the two key fields each representing the identifier of the network element device are both "1", it can be determined that the two key fields both represent the identifier of the network element device as "1", and it can be determined that there is a data conflict between the two key fields.

[0050] However, since the two key fields are from network management data of different management areas, the service data corresponding to the two key fields is data generated by different network element devices, and thus, when the two network management data are combined, at least one of the two key fields with the data conflict needs to be modified according to a preset processing rule, so that the two modified key fields are different, thereby facilitating the timely finding of the service data of the corresponding network element device in the combined network management data, so as to reduce the occurrence of data confusion.

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

[0052] The area identifier of the management area is information uniquely representing the management area, and through the area identifier, it can be determined that the network management data is from the management area corresponding to the area identifier.

[0053] When there is a data conflict, the area identifier of the management area corresponding to the key field can be added to all the key fields with the data conflict, so that there is no data conflict between the modified key fields.

[0054] For example, when there is a data conflict between the key field of the network management data from the management area A (e.g., representing that the service type performed by the network element device is type 1) and the key field of the network management data from the management area B (e.g., representing that the service type performed by the network element device is type 1), the area identifier A (or B) corresponding to the key field can be added to all the key fields representing that the service type performed by the network element device is type 1, so as to obtain the key field of the network management data from the management area A (A-type 1) and the key field of the network management data from the 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 combined network management data is improved.

[0055] In some example embodiments, the modifying, in step S102, of at least one of the two key fields with data conflicts to eliminate the data conflicts comprises: modifying the field value of at least one of the two key fields with data conflicts to the sum of the field value and a preset offset number of bits, and keeping the field value of the other key field unchanged.

[0056] 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.

[0057] When the at least one of the two key fields with data conflicts is modified in the manner of data offset, one of the key fields can be kept unchanged, and only the other key field is changed. In this way, the modified key field can be distinguished from the unchanged key field.

[0058] For example, if the key fields with 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, the second key field can be offset by 300, and the second key field is kept unchanged. In this way, the modified second key field can be different from the first key field, so as to eliminate the data conflicts.

[0059] In some embodiments, if the key fields with data conflicts include three key fields (e.g., a first key field, a second key field, and a third key field representing the field value of a same service type A, and the field values of the three key fields are all 20), and the maximum number of network management data in the management area corresponding to the second key field is 3000, the field values of the modified key fields can be obtained through multiple rounds of pairwise comparison and modification, and the field values of the modified key fields are 20, 20+3000, and 20+6000 respectively. In this way, the three key fields can be distinguished from each other, so as to facilitate subsequent data processing of the key fields.

[0060] In some example embodiments, the modifying, in step S102, of at least one of the two key fields with data conflicts to eliminate the data conflicts comprises: obtaining a plurality of preset values with a preset order; and modifying each key field to a preset value according to a predetermined processing order.

[0061] The preset order is a preset order of processing each key field. The plurality of preset values with the preset order are preset values with a sequence relationship, such as A11, A12, A13, A14, A15, …, A1n, and n is an integer greater than 1.

[0062] When the field values corresponding to the four key fields A11, A12, A13, and A14 already exist in the target network management database, if the key field of the network management data to be merged is A12 and is duplicated with A12 in the target network management database, the key field of the network management data to be merged can be modified from "A12" to "A15", so that the key fields in the merged target network management database are not duplicated, so as to facilitate the quick query and processing of the service data corresponding to the key field in the target network management database according to the key field, and improve the data processing efficiency.

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

[0064] Since each storage partition stores the network management data from the same management area, the target network management can independently manage the network management data in each management and control domain, such as querying, modifying, adding, or deleting the network management data in each management and control domain, thereby improving the processing speed of the network management data in each management and control domain.

[0065] For example, all network management data from the management area A and all network management data from the management area B need to be merged, all network management data from the management area A can be stored in the first storage partition corresponding to the first management and control domain, and all network management data from the management area B can be stored in the second storage partition corresponding to the second management and control domain, so as to reduce the confusion of the network management data from different management areas, thereby ensuring the relative independence of the merged network management data.

[0066] In some exemplary embodiments, the step S103 of merging the plurality of network management data into the target network management database comprises: merging the plurality of network management data into the target network management database based on an accumulated insertion manner.

[0067] The accumulated insertion manner is a processing manner of sequentially inserting the plurality of network management data after the previous network management data. For example, the first network management data is stored in the target network management database first, then the second network management data is stored in the target network management database at the storage address next to the first network management data, and so on, so as to sequentially store the plurality of network management data in the target network management database.

[0068] In some embodiments, the target network management database itself stores a plurality of original network management data, and then the network management data stored in the target network management database can be sequentially inserted into the storage address after the original network management data, so as to avoid the confusion of the network management data.

[0069] 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.

[0070] 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.

[0071] 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.

[0072] 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.

[0073] 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.

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

[0075] 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.

[0076] 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.

[0077] 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.

[0078] 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.

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

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

[0081] Modification module 202 is used to modify at least one of the two key fields that have data conflicts in order to eliminate the data conflicts.

[0082] The merging module 203 is used 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.

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

[0084] 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.

[0085] 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.

[0086] Figure 3 This is a block diagram illustrating the composition of another network management device provided in an embodiment of this disclosure. (See diagram below.) Figure 3 As shown, 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.

[0087] The preparation module 301 is used 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.

[0088] 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.

[0089] 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.

[0090] 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.

[0091] Conflict identification module 302: is used 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, it performs data conflict detection on the network management data of multiple network management systems to be merged input by the preparation module 301.

[0092] 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.

[0093] 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.

[0094] 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.

[0095] The conflict handling module 303 is used 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.

[0096] 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:

[0097] 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;

[0098] 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;

[0099] 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.

[0100] 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.

[0101] 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".

[0102] 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.

[0103] 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).

[0104] 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.

[0105] 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.

[0106] The merging module 304 is used to merge multiple network management data into the target network management database.

[0107] 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.

[0108] 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.

[0109] 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.

[0110] 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.

[0111] 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.

[0112] In some embodiments, the merging module 304 can also be used 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.

[0113] 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.

[0114] 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.

[0115] 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.

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

[0117] 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.

[0118] like Figure 4 As shown, the method includes, but is not limited to, the following steps:

[0119] 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, 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 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.

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

[0121] Table 1 Key Fields of Network Management Data

[0122]

[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]

[0134] 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.

[0135] 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.

[0136] 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.

[0137] In some embodiments, the conflict identification module 302 includes a front end ( Figure 3 (not shown in the image) and back end ( Figure 3 (Not shown in the image), the conflict identification module 302 will communicate via the operating system (…). Figure 3 (Not shown in the image) It interacts with a database (e.g., the database of one of multiple network management systems to be merged) to enable data conflict detection of key fields of network management data in the databases of different network management systems.

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

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

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

[0141] 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.

[0142] 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.

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

[0144] 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.

[0145] 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).

[0146] 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.

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

[0148] 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.

[0149] 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.

[0150] 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.

[0151] 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.

[0152] 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.

[0153] 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.

[0154] 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.

[0155] 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.

[0156] 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.

[0157] 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.

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

[0159]

[0160] 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.

[0161] 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 B13+300000.

[0162] 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;

[0163] 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;

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

[0165] 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.

[0166] 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.

[0167] 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.

[0168] 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.

[0169] 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.

[0170] 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.

[0171] 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.

[0172] In some embodiments, the target network management system already has three running jurisdictions (e.g., a first jurisdiction, a second jurisdiction, and a 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)). To merge the network management data of two network management systems to be merged (e.g., a fourth network management system for managing data of network elements in a fourth management area, and a fifth network management system for managing data of network elements in a fifth management area) into the target network management system, it is necessary to employ... Figure 6 The steps of the data processing method shown are used to merge network management data.

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

[0174] 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.

[0175] 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.

[0176] 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.

[0177] 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.

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

[0179] 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.

[0180] 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.

[0181] 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.

[0182] 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.

[0183] 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.

[0184] 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.

[0185] 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.

[0186] 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). 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. This requires the use of... Figure 7 The steps of the data processing method shown are used to merge network management data.

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

[0188] 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.

[0189] 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.

[0190] 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.

[0191] 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.

[0192] 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.

[0193] 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.

[0194] Figure 8 This is a block diagram of another network management device provided in an embodiment of the present disclosure.

[0195] like Figure 8 As shown, the electronic device 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.

[0196] 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.

[0197] 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.

[0198] 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.

[0199] 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.

[0200] 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.

[0201] 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.

[0202] 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.

[0203] 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.

[0204] 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.

[0205] 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.

[0206] 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.

[0207] 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.

[0208] 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: detecting data conflicts of key fields of a plurality of network management data, the plurality of network management data being from at least two management areas; in a case where data conflicts exist between any two of the key fields, modifying at least one of the two key fields with data conflicts to eliminate the data conflicts; merging the plurality of network management data into a target network management database, the target network management database comprising a plurality of management domains, one of the management domains managing all network management data in one of the management areas.

2. The method of claim 1, wherein, The detecting data conflicts of key fields of a plurality of network management data comprises: extracting key fields of the plurality of network management data; comparing all same types of the key fields with each other to obtain comparison results; in a case where the comparison results of two compared key fields are same, determining that the two same key fields have data conflicts.

3. The method of claim 1, wherein, The modifying at least one of the two key fields with data conflicts to eliminate the data conflicts comprises: adding an area identifier of a management area corresponding to the key field to at least one of the two key fields with data conflicts.

4. The method of claim 1, wherein, The modifying at least one of the two key fields with data conflicts to eliminate the data conflicts comprises: modifying a field value of one of the two key fields with data conflicts to a sum of the field value and a preset offset number, and keeping a field value of the other key field unchanged; wherein the preset offset number is greater than a maximum value of a quantity of network management data in the management area corresponding to the key field.

5. The method of claim 1, wherein, The modifying at least one of the two key fields with data conflicts to eliminate the data conflicts comprises: obtaining a plurality of preset values with a preset order, the preset order being a preset order of processing each of the key fields; modifying each of the key fields to the preset values in turn according to the predetermined processing order.

6. The method of any one of claims 1 to 5, wherein, Network management data in each of the management domains is stored in a corresponding storage partition of the target network management database.

7. The method of any one of claims 1 to 5, wherein, The merging the plurality of network management data into a target network management database comprises: merging the plurality of network management data into the target network management database based on an accumulative insertion manner.

8. The method of any one of claims 1 to 5, wherein, After the merging the plurality of network management data into a target network management database, the method further comprises: obtaining a first number of the network management data for detection; detecting a second number of the network management data newly added in the merged target network management database; in a case where the first number is equal to the second number, determining that network management data merging is successful.

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

10. A network management device, comprising a memory and a processor; the memory stores a computer program executable by the processor, and the computer program is executed by the processor to implement the data processing method according to any one of claims 1 to 9. 11.A computer readable medium having stored thereon a computer program which, when executed by a processor, implements the data processing method according to any one of claims 1 to 9. 12.A computer program product comprising a computer program which, when executed by a processor, implements the data processing method according to any one of claims 1 to 9.

Images