Network element configuration data merging method, apparatus, system, electronic device, and medium

Abstract

Embodiments of the present application disclose a network element configuration data merging method, device, system, electronic equipment and medium. The network element configuration data merging method comprises: loading a pre-configured and station template; obtaining an and station rule according to the and station template; adjusting configuration data to be merged according to the and station rule; and performing a merging operation on the adjusted configuration data to be merged, so that the merging of multi-mode station configuration data can be realized in various complex reconstruction scenes on site, and the efficiency of station merging is improved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of communication technology, and in particular to a method, apparatus, system, electronic device and medium for merging network element configuration data. Background Technology

[0002] With the rollout of 5G services, operators are considering building networks based on existing site resources to improve site service processing capabilities, such as simultaneously supporting 2G / 3G / 4G / 5G services. This could involve merging multiple existing sites into a new one, or combining two or more operational sites into a single facility. Site merging requires considering the specific circumstances of each site and merging its configuration data.

[0003] However, merging sites, especially merging site configuration data, currently presents numerous challenges. This involves site equipment, transmission data, and wireless data. In actual field operations, the rules for merging configuration data vary depending on the specific upgrade scenario, requiring extensive modifications to device parameters and configuration data. Consequently, merging site configuration data necessitates users memorizing numerous commands and parameters to modify the device configuration data. Furthermore, it requires modifying the configuration file for each device separately and then downloading it back to the device. When the configuration files are complex and the number of devices is large, this significantly increases the workload of site merging. Therefore, how to achieve multi-mode site merging under various complex upgrade scenarios in the field has become an urgent problem to be solved. Summary of the Invention

[0004] The purpose of one or more embodiments of this specification is to provide a method, apparatus, system, electronic device and medium for merging network element configuration data, which can realize the merging of site configuration data in various complex on-site transformation scenarios and improve the efficiency of site merging.

[0005] To solve the above-mentioned technical problems, one or more embodiments of this specification are implemented as follows:

[0006] In a first aspect, a method for merging network element configuration data is provided, the method comprising: loading a pre-configured site merging template; obtaining site merging rules according to the site merging template; adjusting the configuration data to be merged according to the site merging rules; and performing a merging operation on the adjusted configuration data to be merged.

[0007] Secondly, a network element configuration data merging device is proposed, comprising: a loading module for loading a pre-configured merging template; a merging rule acquisition module for acquiring merging rules according to the merging template; an adjustment module for adjusting the configuration data to be merged according to the merging rules; and a merging operation module for performing a merging operation on the adjusted configuration data to be merged.

[0008] Thirdly, a network management system is proposed, which includes the network element configuration data merging device as described above.

[0009] Fourthly, an electronic device is proposed, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the network element configuration data merging method described above.

[0010] Fifthly, a storage medium is proposed for computer-readable storage, wherein the storage medium stores one or more programs, which, when executed by one or more processors, implement the steps of the network element configuration data merging method described above.

[0011] As can be seen from the technical solutions provided in one or more embodiments of this specification, the network element configuration data merging method provided in this specification first loads a pre-configured site merging template. Different site merging sites correspond to different content in their respective templates. The template includes the network element model version number of the site. Based on the network element model version number, the corresponding version of the network element model can be found, and the corresponding merging rules can be located. Thus, the merging rules can be obtained according to the template. It is understood that different site merging sites can correspond to different template contents, different network element models, and different merging rules. After the merging rules are found, the configuration data to be merged can be adjusted according to the rules, and the adjusted configuration data to be merged is then merged. Different merging templates are pre-configured before configuration data merging based on different modification scenarios, configuration data storage locations, and relationships between different site merging sites. Furthermore, different site merging sites can use different merging rules to adjust the configuration data to be merged before merging the configuration data. As can be seen, when merging configuration data, the pre-configured template is loaded directly. Taking into account the actual situation of different merged sites, different merge rules are adopted to speed up the merging of configuration data, which simplifies the complex site merging process and speeds up the merging work efficiency. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in one or more embodiments or prior art of this specification, the accompanying drawings used in the description of one or more embodiments or prior art will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1This is a schematic diagram illustrating the steps of a method for merging network element configuration data provided in an embodiment of the present invention.

[0014] Figure 2 This is a schematic diagram illustrating the steps of another method for merging network element configuration data provided in an embodiment of the present invention.

[0015] Figure 3 This is a schematic diagram illustrating the steps of another method for merging network element configuration data provided in an embodiment of the present invention.

[0016] Figure 4 This is a schematic diagram illustrating the steps of another method for merging network element configuration data provided in an embodiment of the present invention.

[0017] Figure 5 This is a schematic diagram illustrating the steps of another method for merging network element configuration data provided in an embodiment of the present invention.

[0018] Figure 6 This is a schematic diagram illustrating the steps of another method for merging network element configuration data provided in an embodiment of the present invention.

[0019] Figure 7 This is a schematic diagram illustrating the steps of another method for merging network element configuration data provided in an embodiment of the present invention.

[0020] Figure 8 This is a schematic diagram illustrating the steps of another method for merging network element configuration data provided in an embodiment of the present invention.

[0021] Figure 9 This is a schematic diagram illustrating the steps of another method for merging network element configuration data provided in an embodiment of the present invention.

[0022] Figure 10 This is a schematic diagram of the structure of a network element configuration data merging device provided in an embodiment of the present invention.

[0023] Figure 11 This is a schematic diagram of the structure of a network management system provided in an embodiment of the present invention.

[0024] Figure 12 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention.

[0025] Figure 13 This is a schematic diagram of the station merging rule definition in another method for merging network element configuration data provided in an embodiment of the present invention.

[0026] Figure 14 This is a schematic diagram of the station-to-station template definition in another method for merging network element configuration data provided in an embodiment of the present invention. Detailed Implementation

[0027] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described one or more embodiments are merely some embodiments of this specification, and not all embodiments. All other embodiments obtained by those skilled in the art based on one or more embodiments of this specification without creative effort should fall within the protection scope of this document.

[0028] The network element configuration data merging method provided in this invention is a method for merging configuration data of paralleled sites. It can merge site configuration data in various complex on-site modification scenarios, improving the efficiency of site merging. The network element configuration data merging method and its various steps provided in this specification will be described in detail below.

[0029] It should be noted that the sites mentioned in this application can include migration sites and target sites. The number of migration sites is not limited and can be one or more. The target site is where the final merged configuration data is stored and used. The target site can be a newly opened site, or an already opened site that is not among the migration sites, or it can be among the migration sites. The network element configuration data merging method proposed in this application applies to all of them.

[0030] Example 1

[0031] Reference Figure 1 The diagram illustrates the steps of a network element configuration data merging method according to an embodiment of the present invention. It is understood that the network element configuration data merging method provided in this embodiment treats the merging site as a network element. This merging method is also applicable to merging network element configuration data, and can solve various complex modification scenarios at merging sites to achieve the merging of configuration data between merging sites. This network element configuration data merging method includes the following steps:

[0032] Step 10: Load the pre-configured station merging template;

[0033] The network element configuration data merging method proposed in the embodiments of this specification takes into account the different transformation scenarios that may occur at the actual site of the merged site, involving site equipment, transmission data, and wireless data. It pre-configures site templates and merging rule sets for the merged sites. The merging template is the same template, but the content reflected in the merging template varies depending on the different situations of the merged sites.

[0034] See Figure 14 As shown, the site merging template includes the network element model version number of the merging site, the merging relationship of the merging sites, the storage location of the configuration data of the merging sites, and the extended information that the protocol needs to be planned.

[0035] The site consolidation template includes information about the consolidation site, including configurations for the corresponding transformation scenario and the network element model version number. This version number allows for the lookup of the corresponding network element model. Since the network element model and consolidation rule set are configured together, finding the network element model for the consolidation site allows access to the corresponding consolidation rule set, which can then be used to adjust the configuration data. Therefore, different configurations can be tailored to different transformation scenarios for the consolidation site. Furthermore, the template also allows for planning the equipment, transmission, and wireless parameters of the consolidation site for future adjustments.

[0036] Users can plan the merging operations of one or more sites under different scenarios in the site merging template. A site merging group can include one migration site and one target site. Merging operations of configuration data for one or more sites with the same target site can be combined into a single merging task. Multiple merging tasks can be executed concurrently. The merging operations of multiple sites within a single merging task can be serial, meaning that only one migration site and one target site are merged at a time, completing the merging operations of multiple sites within a single merging task sequentially.

[0037] At the start of the site merging task, a site merging template is used as input. The template is loaded and parsed to obtain relevant information about the sites to be merged. To improve merging efficiency, the sites performing the merging operation in the task can belong to the same network element model version.

[0038] Step 20: Obtain the merging rules based on the merging template;

[0039] As mentioned above, after obtaining the network element model version number of the merged site based on the merged site template, the corresponding network element model can be found. The network element model and the merged site rule set are configured together. Therefore, after loading the network element model package with the corresponding model version number of the target site, the network element model and merged site rule set corresponding to the merged site can be parsed to obtain the merged site.

[0040] The site merging rule set is pre-configured based on different network element models. As the name suggests, the site merging rule set includes multiple site merging rules. Configuration data can be merged uniformly according to the site merging rules. Alternatively, the same site merging rule can be used, or the configuration data can be adjusted using the site merging rules as described in the steps below before merging the adjusted configuration data. Another approach is to merge the management units in the configuration data one by one, or adjust the management units in the configuration data separately and then merge them one by one.

[0041] Step 30: Adjust the configuration data to be merged according to the merging rules;

[0042] The system queries the configuration data of the sites to be merged and adjusts the configuration data. Based on the merging scenario configured in the merging template, it searches for the corresponding merging rule in the merging rule set. If found, the configuration data of the merging site is adjusted. If not found, the configuration data of the merging site is not merged by default.

[0043] Before merging the configuration data of the merged sites, conflicts between the configuration data need to be handled, such as conflicts between data identifier IDs, conflicts between corresponding wireless service IDs in configuration data with related relationships, and the replanning or adjustment of site equipment, transmission parameters, etc. Therefore, it is necessary to use merging rules to adjust the configuration data to be merged before the merging operation.

[0044] Understandably, before making adjustments, the configuration data of the merged sites is copied twice, one to the configuration editing area and the other to the original area. Adjustments are then made only to the configuration data in the editing area.

[0045] Step 40: Perform a merge operation on the adjusted configuration data to be merged.

[0046] The adjusted configuration data to be merged is then merged to successfully combine the configuration data from different sites to the target site. Therefore, adjusting the configuration data of the sites to be merged before the merge operation avoids conflicts during the merge process and prevents data corruption after the merge, thus improving the efficiency of merging configuration data and saving manpower and time costs.

[0047] See Figure 2 As shown, in some embodiments, the network element configuration data merging method provided in this specification includes site management objects as the configuration data to be merged. Step 30: Adjusting the data to be merged according to the site merging rules, specifically including:

[0048] Step 300: Adjust the site management objects according to the site merging rules, and ensure that the granularity of the site merging rules corresponds one-to-one with that of the site management objects.

[0049] In mobile communication systems, especially 5G cellular mobile communication systems, model-driven architecture supports the operation of the entire system. Based on the network element model, each service defines its own model. Within the network element model, services define the dependencies and relationships between site management objects (MOs). Based on this, merging rules define the specifications followed by adjustment actions. Each service at a merged site executes the merging rules according to the specifications within the network element model at the granularity of the site management object (MO). That is, one site management object (MO) is adjusted by one merging rule, and subsequent merging operations are performed at the granularity of the site management object (MO).

[0050] Adjusting the site management object (MO) according to the site merging rules mainly includes conflict handling, such as conflicts in the site management object identifier (MOID) or radio service IDs, followed by merging and migrating the site's configuration data to the target site. Additionally, merging sites may involve replanning or adjusting the equipment and transmission parameters of the merged sites. After adjusting the cell number on the site side, it's necessary to ensure consistency with the cell information on the controller side, such as the cell number for GSM.

[0051] See Figure 13 As shown in Example 1, each site merging rule includes a site merging rule definition XML file and a site merging rule execution algorithm LUA script file. The execution algorithm of the site merging rule in this example performs a merge operation on each site management object immediately after it is adjusted, and completes the adjustment and merging operations of site management objects in sequence.

[0052] Example 1

[0053] The set of merging rules is stored in the network element model package. Each merging rule includes an XML file defining the merging rule and a LUA script file for calculating the merging rule algorithm.

[0054] (1) The XML file name for the merge rule definition is *-mergeRules.xml, and the encoding is UTF-8.

[0055] For example: / home / model / CUDU / V1.10.30.00B06_ITRAN02B07build27 / brs / cm / merge / NRNeigh borRelation-mergeRules.xml;

[0056] The merging rule definition XML file includes the following information:

[0057] ruleId: The rule's ID, which is unique within the same site. Naming convention: MG-Domain-NFC Name-Serial Number.

[0058] For example, "MG-Radio-ncs-1001".

[0059] mergeMoc: The definition of the site management object (MO) currently being processed for merging. Only one migration object is configured per rule. The value must include the full path of the network element model, such as " / ManagedElement / Equipment / RfLink".

[0060] Dependency: Defines the relevant MOCs (Moments of Interest) that the merging operation's algorithms depend on. Multiple algorithms can depend on these objects. Values ​​must include the full path of the network element model, such as:

[0061] " / ManagedElement / Equipment / ReplaceableUnit / RfPort".

[0062] `relationIndex`: This field contains references to related relationships in the attribute field of the object currently being migrated. Multiple `relationIndex` items can be defined, such as " / ManagedElement / Transport / sctp; / ManagedElement / Transport".

[0063] errors: Custom error message statements. Multiple error messages and message levels can be defined, including Critical, Error, and Warn.

[0064] arithmetic: Definition of the merging rule calculation algorithm, which can define merging rule calculation algorithms for multiple migration scenarios.

[0065] extend: Defines the static extension parameter for the parallel station rules.

[0066] (2) The LUA script file for the station merging rule calculation algorithm. The filename is by default named after the ruleId in the XML definition file of the station merging rule. For example, if the ruleId of the station merging rule definition is "MG-Radio-ncs-0001", then the LUA script file corresponding to the station merging rule will be named "MG-Radio-ncs-0001.lua" by default. The LUA script file is stored in the lua subdirectory of the current directory of the XML definition file of the station merging rule, such as:

[0067] / home / model / CUDU / V1.10.30.00B06_ITRAN02B07build27 / brs / cm / merge / lua / MG-Radio-ncs-1001.lua".

[0068] When a site management object (MO) has multiple parallel site scenarios, the site rules can define multiple LUA script files for these scenarios. The script file naming convention is: MG-Domain-NFC Name-Serial Number-Scenario Type, such as "MG-Radio-ncs-1001-1.lua". When a LUA script can support multiple parallel site scenarios simultaneously, the serial numbers of the multiple parallel site scenarios are connected by underscores "_", such as "MG-Radio-ncs-1002-2_3.lua".

[0069] See Figure 3As shown, in some embodiments, in the network element configuration data merging method provided in this specification, step 30: adjusting the site management object according to the site merging rules specifically includes:

[0070] Step 310: Adjust the site management objects sequentially according to their execution order until all site management objects have been adjusted.

[0071] Subsequent merging operations at the granularity of the site management object (MO) can be performed either immediately after each site management object is adjusted, or all site management objects can be adjusted before a unified merging operation is performed at the granularity of the site management object (MO).

[0072] The execution order of site management objects (MOs) can be determined based on the priority sequence of the association relationships between the site management objects (MOs) of the merged sites.

[0073] The relationships between site management objects (MOs) can be defined in the network element model. These relationships include dependencies and business connections between MOs, such as parent-child relationships and reference relationships, which can be retrieved from the network element model. Furthermore, some business relationships and algorithm dependencies can be defined in the site merging rules' XML file based on the relationships retrieved from the network element model.

[0074] See Figure 4 As shown, in some embodiments, the site management object is the site management object of the currently merged site. Step 310: Adjust the site management objects sequentially according to their execution order until all site management objects have been adjusted. The network element configuration data merging method provided in this specification embodiment further includes:

[0075] Step 320: Determine if there is a next merging station;

[0076] If so, proceed to step 330: after adjusting the site management objects included in the next site to be merged according to the site merging rules, return the judgment step on whether there is a next site to be merged, until the configuration data of all sites to be merged are adjusted.

[0077] When a site merging task involves multiple migration sites, after the configuration data merging operation of one migration site is completed, the second migration site in the site merging task will continue to be executed until the configuration data merging operation of all migration sites in the site merging task is completed.

[0078] The site merging task can be an atomic operation. The site merging task is considered successful only after all the configuration data merging operations of all the migration sites in the site merging task have been successfully completed.

[0079] See Figure 5 As shown, in some embodiments, before step 310: sequentially adjusting the site management objects according to their execution order, the network element configuration data merging method provided in this specification embodiment further includes:

[0080] Step 50: Obtain the network element model and merging rule set corresponding to the merged sites;

[0081] As mentioned earlier, the merging module obtains the network element model corresponding to the merging site and the merging rule set that matches the network element model. The merging rule set is a collection that includes the merging rules of the site management objects in the corresponding network element model.

[0082] Step 60: Generate the execution order of site management objects based on the network element model and the site merging rule set.

[0083] After generating the association relationships of site management objects (MOs) based on the network element model and the site merging rule set, a priority sequence of the association relationships can be formulated, and then the execution order of the site management objects can be determined based on the priority sequence of the association relationships.

[0084] See Figure 6 As shown in the embodiments of this specification, in the method for merging network element configuration data, step 50: given that the network element model corresponding to the merged site and the pre-configured merge rule set are obtained, step 20: obtaining the merge rules according to the merge template, specifically including:

[0085] Step 200: Obtain the site merging rules corresponding to the site management object from the site merging rule set according to the site merging template.

[0086] The site merging rule set is configured to correspond to the network element model. It includes the merging rules for each site management object. The network element model version number of the merging site is recorded in the merging template. The corresponding network element model can be found based on the version number, and thus the merging rule set for that model can be located.

[0087] See Figure 7 As shown, in some embodiments, in the network element configuration data merging method provided in this specification, step 60: generating the execution order of site management objects based on the network element model and the site merging rule set specifically includes:

[0088] Step 600: Generate the association relationships between site management objects based on the network element model and the site merging rule set;

[0089] In the network element model, business definitions establish the dependencies and associations between site management objects (MOs). For example, relationships between site management objects include parent-child relationships and reference relationships, which can be read from the network element model. Additionally, some business relationships and algorithm dependencies can be defined in the site merging rules' XML file based on the associations read from the network element model.

[0090] Step 610: Determine the execution order based on the priority of the association relationship.

[0091] After determining the relationships among the site management objects (MOs), a priority sequence for these relationships is established. The priority strategy is as follows:

[0092] (1) In the network element model, the parent site management object MO is processed with priority over the child site management object MO.

[0093] (2) In the network element model, the site management object MO that is referenced is processed first over the referenced site management object MO.

[0094] (3) In the network element model, the site management object MO referenced by the business association relationship is processed first than the referenced site management object MO.

[0095] (4) In the merging rule algorithm, the site management object MO that depends on the query is processed first, while the site management object MO that is currently performing the merge operation is processed first.

[0096] See Figure 8 As shown, in some embodiments, the network element configuration data merging method provided in this specification includes step 600: Given the association between the network element model and the site merging rule set generated for the site management objects, step 30: adjusting the configuration data to be merged according to the site merging rules, specifically including:

[0097] Step 340: When the site management object identifier of one of the site management objects is adjusted, the other site management objects in the site management objects associated with one of the site management objects are also adjusted according to the association relationship.

[0098] During adjustments, the identifiers of associated site management objects can be adjusted simultaneously. For example, if the MOID of a site management object is adjusted, the identifiers of other associated site management object MOs can be automatically adjusted based on the parent-child relationship, reference relationship, and business association relationship of the site management object MOs in the network element model. Subsequent adjustments to associated site management object MOs will no longer consider the MOID adjustment. Furthermore, conflicts in business IDs, reference fields, etc., of site management objects can be handled based on the association relationships.

[0099] See Figure 9As shown, in some embodiments, after step 40: performing a merging operation on the adjusted configuration data to be merged, the network element configuration data merging method provided in this specification embodiment further includes:

[0100] Step 70: Make further adjustments to the configuration data after the merge operation in the configured workspace.

[0101] Further adjustments were made to the configuration data after the merging operation to ensure the normal and smooth use of the target site's configuration data.

[0102] After the site merging task is successfully completed, if the target site is already operational, the configuration data of the merged target site will be compared with the original target site configuration data. The incremental changes and the target site configuration data will be written to the workspace configured in the network management system. Users can further adjust the target site configuration data in the workspace, such as performing validity checks and data activation. If the target site is not operational, the target site configuration data will be imported into a virtual site created by the network management system. Users can further adjust the target site configuration data in the workspace, such as ensuring the merged data meets validity constraints, performing offline validity checks, and exporting data for activation.

[0103] Example 2

[0104] The following is Example 2 of performing a site merging operation using the network element configuration data merging method provided in this application, where the target site has already been activated.

[0105] 1. Prerequisites:

[0106] (1) After SRD is converted to ITRAN, ITRAN site A is not opened. The subnet number is 135797531, the network element ID is 5551, the network element model version is V1.0, and the open standard is GSM / UMTS / LTE / NB.

[0107] (2) ITRAN site B has been opened in the current network, with subnet number 135797531, network element ID 5552, network element model version V1.0, and opening system NR;

[0108] 2. Task Execution

[0109] Step 1: Fill in the site consolidation template, including site configuration information (SiteCfg) and expansion planning adjustment information (*_ExtendInfo), where the site configuration information (see...) Figure 14 )include:

[0110] (1) Work Scenario: Parallel Station Scenario

[1000]

[0111] (2) Work sub-scene: Default scene

[1000]

[0112] (3) Migration station network element ID: 5551

[0113] (4) URL where migration site data is stored:

[0114] ftp: / / ManagedElementType=ITBBU,SubNetwork=135797531,ManagedElement=5551

[0115] Note: FTP indicates an offline data source, stored on an FTP server.

[0116] (5) The URL where the target site's data is stored:

[0117] pca: / / ManagedElementType=ITBBU,SubNetwork=135797531,ManagedElement=5552

[0118] Note: pca represents an online site, stored in the configured workspace.

[0119] Step 2: Create a parallel workstation task, import the parallel workstation template, associate it with workspace AAA, save and execute.

[0120] Step 3: Parse the site merging template and read the information of the migration site A and the target site B, as well as the site merging operation expansion plan adjustment information.

[0121] Step 4: Load the model information and merging rule set of the site management object MO in the network element model package V1.0.

[0122] Step 5: Generate the execution sequence of adjustment and merging operations for the site management object (MO) in the network element model V1.0 version under the default merging scenario based on the model information and the definition information of the merging rules.

[0123] Step 6: Query the data of target site B to the work area, and copy the target site configuration data twice, storing one copy in the editing area and the other in the original area.

[0124] Step 7: Download the configuration data of the migration site A from the FTP server, query the configuration data of the migration site A, and perform the adjustment and merging operations of the site management object MO in the order of the adjustment operations of the site management object MO in the network element model. Execute the merging operation algorithm of the site management object MO.

[0125] Step 8: After merging the configuration data of migration site A, determine if there is a second migration site. If there is, continue to execute the second migration site; otherwise, consider the site merging task to be completed.

[0126] Step 9: After the station merging task is completed, if the station merging task is successful, the target station configuration data in the editing area and the target station configuration data in the original area will be compared for differences. Read-only fields will be filtered and the incremental changes will be written to the associated work area AAA of the station merging task.

[0127] Step 10: The user makes further adjustments to the configuration data of site B in the work area AAA, such as Master refresh value, frequency shift adjustment, etc.

[0128] Step 11: The user performs a validity check on site B in work area AAA, such as constraint validity issues, and then makes fine adjustments.

[0129] Step 12: The user executes the configuration data activation and station merging operation for site B in work area AAA.

[0130] Example 3

[0131] The following is Example 3 of performing a site merging operation using the network element configuration data merging method provided in this application, where the target site has already been activated.

[0132] 1. Prerequisites:

[0133] (1) After SRD is converted to ITRAN, ITRAN site A is not opened. The subnet number is 135797531, the network element ID is 5551, the network element model version is V1.0, and the open standard is GSM\UMTS\LTE\NB.

[0134] (2) Configure the new ITRAN site C. It is not yet activated. The subnet number is 135797531, the network element ID is 5553, the network element model version is V1.0, and the activation type is NR.

[0135] 2. Execution of station merging tasks

[0136] Step 1: Fill in the site consolidation template, including site configuration information (SiteCfg) and expansion planning adjustment information (*_ExtendInfo). The site configuration information includes:

[0137] (1) Work Scenario: Parallel Station Scenario

[1000]

[0138] (2) Work sub-scene: Default scene

[1000]

[0139] (3) Migration station network element ID: 5551

[0140] (4) URL where migration site data is stored:

[0141] ftp: / / ManagedElementType=ITBBU,SubNetwork=135797531,ManagedElement=5551

[0142] Note: FTP indicates an offline data source, stored on an FTP server.

[0143] (5) URL where the target site's configuration data is stored:

[0144] ftp: / / ManagedElementType=ITBBU,SubNetwork=135797531,ManagedElement=5553

[0145] Note: FTP indicates an offline data source, stored on an FTP server.

[0146] Step 2: Create a parallel workstation task, import the parallel workstation template, associate it with the workspace BBB, save and execute.

[0147] Step 3: Parse the site merging template and read the information of the migration site A and the target site C, as well as the site merging operation expansion plan adjustment information.

[0148] Step 4: Read the model information and site merging rule set information of the site management object MO in the loaded network element model package V1.0.

[0149] Step 5: Generate the execution sequence of adjustment and merging operations for the site management object (MO) corresponding to the network element model V1.0 version under the default merging scenario based on the information of the network element model and the information defined by the merging rules.

[0150] Step 6: Download the configuration data of target site C from the FTP server, query the configuration data of target site C and store it in the work area, and copy the configuration data of target site C twice, storing it in the editing area and the original area respectively.

[0151] Step 7: Download the configuration data of the migration site A from the FTP server, query the configuration data of the migration site A, and execute the adjustment and merging operation of the site management object MO according to the execution order of the adjustment and merging operation of the site management object MO corresponding to the network element model. Execute the merging operation algorithm of the site management object MO.

[0152] Step 8: After merging the configuration data of migration site A, determine if there is a second migration site. If there is, continue to the second migration site; otherwise, the site merging task is considered complete.

[0153] Step 9: After the site merging task is completed, if the task merging is successful, and it is determined that the target site is not in operation, the target site data in the editing area is written into the RANDPS of the network management system to create a virtual site C.

[0154] Step 10: The user further adjusts the configuration data of virtual site C in the associated work area BBB, such as Master refresh value, frequency shift adjustment, etc.

[0155] Step 11: The user performs offline validation and constraint validation of virtual site C in the work area BBB to make further adjustments.

[0156] Step 12: The user exports the configuration data of virtual site C in the workspace BBB.

[0157] Step 13: The user creates a data activation process for site C in the SPU to complete the site merging operation.

[0158] The above analysis shows that the network element configuration data merging method provided in this specification first loads a pre-configured site merging template. Different site merging sites correspond to different template contents. The template includes the network element model version number of the site. Based on the version number, the corresponding version of the network element model can be found, and the corresponding merging rules can be located. Thus, the merging rules can be obtained based on the template. It can be understood that different site merging sites can correspond to different template contents, different network element models, and different merging rules. After the merging rules are found, the configuration data to be merged can be adjusted according to the rules, and then the adjusted configuration data to be merged is merged. Different merging templates are pre-configured before configuration data merging based on different modification scenarios, configuration data storage locations, and relationships between different site merging sites. Furthermore, different site merging sites can use different merging rules to adjust the configuration data to be merged before merging the configuration data. As can be seen, when merging configuration data, the pre-configured template is loaded directly. Taking into account the actual situation of different merged sites, different merge rules are adopted to speed up the merging of configuration data, which simplifies the complex site merging process and speeds up the merging work efficiency.

[0159] Example 2

[0160] Reference Figure 10 As shown, this is a network element configuration data merging device 10 provided in an embodiment of the present invention. The device includes: a loading module 100, a merging rule acquisition module 200, an adjustment module 300, and a merging operation module 400. Wherein:

[0161] Loading module 100 is used to load pre-configured parallel station templates;

[0162] The network element configuration data merging method proposed in the embodiments of this specification takes into account the different transformation scenarios that may occur at the actual site of the merged site, involving site equipment, transmission data, and wireless data. It pre-configures site templates and merging rule sets for the merged sites. The merging template is the same template, but the content reflected in the merging template varies depending on the different situations of the merged sites.

[0163] See Figure 14 As shown, the site merging template includes the network element model version number of the merging site, the merging relationship of the merging sites, the storage location of the configuration data of the merging sites, and the extended information that the protocol needs to be planned.

[0164] The site consolidation template includes information about the consolidation site, including configurations for the corresponding transformation scenario and the network element model version number. This version number allows for the lookup of the corresponding network element model. Since the network element model and consolidation rule set are configured together, finding the network element model for the consolidation site allows access to the corresponding consolidation rule set, which can then be used to adjust the configuration data. Therefore, different configurations can be tailored to different transformation scenarios for the consolidation site. Furthermore, the template also allows for planning the equipment, transmission, and wireless parameters of the consolidation site for future adjustments.

[0165] Users can plan the merging operations of one or more sites under different scenarios in the site merging template. A site merging group can include one migration site and one target site. Merging operations of configuration data for one or more sites with the same target site can be combined into a single merging task. Multiple merging tasks can be executed concurrently. The merging operations of multiple sites within a single merging task can be serial, meaning that only one migration site and one target site are merged at a time, completing the merging operations of multiple sites within a single merging task sequentially.

[0166] At the start of the site merging task, a site merging template is used as input. The template is loaded and parsed to obtain relevant information about the sites to be merged. To improve merging efficiency, the sites performing the merging operation in the task can belong to the same network element model version.

[0167] The merging rule acquisition module 200 is used to acquire merging rules based on the merging template;

[0168] As mentioned above, after obtaining the network element model version number of the merged site based on the merged site template, the corresponding network element model can be found. The network element model and the merged site rule set are configured together. Therefore, after loading the network element model package with the corresponding model version number of the target site, the network element model and merged site rule set corresponding to the merged site can be parsed to obtain the merged site.

[0169] The site merging rule set is pre-configured based on different network element models. As the name suggests, the site merging rule set includes multiple site merging rules. Configuration data can be merged uniformly according to the site merging rules. Alternatively, the same site merging rule can be used, or the configuration data can be adjusted using the site merging rules as described in the steps below before merging the adjusted configuration data. Another approach is to merge the management units in the configuration data one by one, or adjust the management units in the configuration data separately and then merge them one by one.

[0170] The adjustment module 300 is used to adjust the configuration data to be merged according to the merging rules;

[0171] The system queries the configuration data of the sites to be merged and adjusts the configuration data. Based on the merging scenario configured in the merging template, it searches for the corresponding merging rule in the merging rule set. If found, the configuration data of the merging site is adjusted. If not found, the configuration data of the merging site is not merged by default.

[0172] Before merging the configuration data of the merged sites, conflicts between the configuration data need to be handled, such as conflicts between data identifier IDs, conflicts between corresponding wireless service IDs in configuration data with related relationships, and the replanning or adjustment of site equipment, transmission parameters, etc. Therefore, it is necessary to use merging rules to adjust the configuration data to be merged before the merging operation.

[0173] Understandably, before making adjustments, the configuration data of the merged sites is copied twice, one to the configuration editing area and the other to the original area. Adjustments are then made only to the configuration data in the editing area.

[0174] The merge operation module 400 is used to perform merge operations on the adjusted configuration data to be merged.

[0175] The adjusted configuration data to be merged is then merged to successfully combine the configuration data from different sites to the target site. Therefore, adjusting the configuration data of the sites to be merged before the merge operation avoids conflicts during the merge process and prevents data corruption after the merge, thus improving the efficiency of merging configuration data and saving manpower and time costs.

[0176] In some embodiments, the network element configuration data merging device provided in this specification includes site management objects (MOs) as the configuration data to be merged, and the adjustment module 300 specifically includes:

[0177] The site management objects are adjusted according to the site merging rules, and the granularity of the site merging rules corresponds one-to-one with that of the site management objects.

[0178] In mobile communication systems, especially 5G cellular mobile communication systems, model-driven architecture supports the operation of the entire system. Based on the network element model, each service defines its own model. Within the network element model, services define the dependencies and relationships between site management objects (MOs). Based on this, merging rules define the specifications followed by adjustment actions. Each service at a merged site executes the merging rules according to the specifications within the network element model at the granularity of the site management object (MO). That is, one site management object (MO) is adjusted by one merging rule, and subsequent merging operations are performed at the granularity of the site management object (MO).

[0179] Adjusting the site management object (MO) according to the site merging rules mainly includes conflict handling, such as conflicts in the site management object identifier (MOID) or radio service IDs, followed by merging and migrating the site's configuration data to the target site. Additionally, merging sites may involve replanning or adjusting the equipment and transmission parameters of the merged sites. After adjusting the cell number on the site side, it's necessary to ensure consistency with the cell information on the controller side, such as the cell number for GSM.

[0180] See Figure 13 As shown in Example 1, each site merging rule includes a site merging rule definition XML file and a site merging rule execution algorithm LUA script file. The execution algorithm of the site merging rule in this example performs a merge operation on each site management object immediately after it is adjusted, and completes the adjustment and merging operations of site management objects in sequence.

[0181] Example 1

[0182] The set of merging rules is stored in the network element model package. Each merging rule includes an XML file defining the merging rule and a LUA script file for calculating the merging rule algorithm.

[0183] (1) The XML file name for the merge rule definition is *-mergeRules.xml, and the encoding is UTF-8.

[0184] For example: / home / model / CUDU / V1.10.30.00B06_ITRAN02B07build27 / brs / cm / merge / NRNeigh borRelation-mergeRules.xml;

[0185] The merging rule definition XML file includes the following information:

[0186] ruleId: The rule's ID, which is unique within the same site. Naming convention: MG-Domain-NFC Name-Serial Number.

[0187] For example, "MG-Radio-ncs-1001".

[0188] mergeMoc: The definition of the site management object (MO) currently being processed for merging. Only one migration object is configured per rule. The value must include the full path of the network element model, such as " / ManagedElement / Equipment / RfLink".

[0189] Dependency: Defines the relevant MOCs (Moments of Interest) that the merging operation's algorithms depend on. Multiple algorithms can depend on these objects. Values ​​must include the full path of the network element model, such as:

[0190] " / ManagedElement / Equipment / ReplaceableUnit / RfPort".

[0191] `relationIndex`: This field contains references to related relationships in the attribute field of the object currently being migrated. Multiple `relationIndex` items can be defined, such as " / ManagedElement / Transport / sctp; / ManagedElement / Transport".

[0192] errors: Custom error message statements. Multiple error messages and message levels can be defined, including Critical, Error, and Warn.

[0193] arithmetic: Definition of the merging rule calculation algorithm, which can define merging rule calculation algorithms for multiple migration scenarios.

[0194] extend: Defines the static extension parameter for the parallel station rules.

[0195] (2) The LUA script file for the station merging rule calculation algorithm. The filename is by default named after the ruleId in the XML definition file of the station merging rule. For example, if the ruleId of the station merging rule definition is "MG-Radio-ncs-0001", then the LUA script file corresponding to the station merging rule will be named "MG-Radio-ncs-0001.lua" by default. The LUA script file is stored in the lua subdirectory of the current directory of the XML definition file of the station merging rule, such as:

[0196] / home / model / CUDU / V1.10.30.00B06_ITRAN02B07build27 / brs / cm / merge / lua / MG-Radio-ncs-1001.lua".

[0197] When a site management object (MO) has multiple parallel site scenarios, the site rules can define multiple LUA script files for these scenarios. The script file naming convention is: MG-Domain-NFC Name-Serial Number-Scenario Type, such as "MG-Radio-ncs-1001-1.lua". When a LUA script can support multiple parallel site scenarios simultaneously, the serial numbers of the multiple parallel site scenarios are connected by underscores "_", such as "MG-Radio-ncs-1002-2_3.lua".

[0198] In some embodiments, in the network element configuration data merging device provided in the embodiments of this specification, the adjustment module 300 is further used for:

[0199] Adjust the site management objects sequentially according to their execution order until all site management objects have been adjusted.

[0200] Subsequent merging operations at the granularity of the site management object (MO) can be performed either immediately after each site management object is adjusted, or all site management objects can be adjusted before a unified merging operation is performed at the granularity of the site management object (MO).

[0201] The above analysis shows that the network element configuration data merging method provided in this specification first loads a pre-configured site merging template. Different site merging sites correspond to different template contents. The template includes the network element model version number of the site. Based on the version number, the corresponding version of the network element model can be found, and the corresponding merging rules can be located. Thus, the merging rules can be obtained based on the template. It can be understood that different site merging sites can correspond to different template contents, different network element models, and different merging rules. After the merging rules are found, the configuration data to be merged can be adjusted according to the rules, and then the adjusted configuration data to be merged is merged. Different merging templates are pre-configured before configuration data merging based on different modification scenarios, configuration data storage locations, and relationships between different site merging sites. Furthermore, different site merging sites can use different merging rules to adjust the configuration data to be merged before merging the configuration data. As can be seen, when merging configuration data, the pre-configured template is loaded directly. Taking into account the actual situation of different merged sites, different merge rules are adopted to speed up the merging of configuration data, which simplifies the complex site merging process and speeds up the merging work efficiency.

[0202] Example 3

[0203] See Figure 11As shown, a network management system 1 provided in an embodiment of the present invention includes a network element configuration data merging device 10 as described above. The network element configuration data merging device 10 may include:

[0204] Loading module 100 is used to load pre-configured parallel station templates;

[0205] The network element configuration data merging method proposed in the embodiments of this specification takes into account the different transformation scenarios that may occur at the actual site of the merged site, involving site equipment, transmission data, and wireless data. It pre-configures site templates and merging rule sets for the merged sites. The merging template is the same template, but the content reflected in the merging template varies depending on the different situations of the merged sites.

[0206] See Figure 14 As shown, the site merging template includes the network element model version number of the merging site, the merging relationship of the merging sites, the storage location of the configuration data of the merging sites, and the extended information that the protocol needs to be planned.

[0207] The site consolidation template includes information about the consolidation site, including configurations for the corresponding transformation scenario and the network element model version number. This version number allows for the lookup of the corresponding network element model. Since the network element model and consolidation rule set are configured together, finding the network element model for the consolidation site allows access to the corresponding consolidation rule set, which can then be used to adjust the configuration data. Therefore, different configurations can be tailored to different transformation scenarios for the consolidation site. Furthermore, the template also allows for planning the equipment, transmission, and wireless parameters of the consolidation site for future adjustments.

[0208] Users can plan the merging operations of one or more sites under different scenarios in the site merging template. A site merging group can include one migration site and one target site. Merging operations of configuration data for one or more sites with the same target site can be combined into a single merging task. Multiple merging tasks can be executed concurrently. The merging operations of multiple sites within a single merging task can be serial, meaning that only one migration site and one target site are merged at a time, completing the merging operations of multiple sites within a single merging task sequentially.

[0209] At the start of the site merging task, a site merging template is used as input. The template is loaded and parsed to obtain relevant information about the sites to be merged. To improve merging efficiency, the sites performing the merging operation in the task can belong to the same network element model version.

[0210] The merging rule acquisition module 200 is used to acquire merging rules based on the merging template;

[0211] As mentioned above, after obtaining the network element model version number of the merged site based on the merged site template, the corresponding network element model can be found. The network element model and the merged site rule set are configured together. Therefore, after loading the network element model package with the corresponding model version number of the target site, the network element model and merged site rule set corresponding to the merged site can be parsed to obtain the merged site.

[0212] The site merging rule set is pre-configured based on different network element models. As the name suggests, the site merging rule set includes multiple site merging rules. Configuration data can be merged uniformly according to the site merging rules. Alternatively, the same site merging rule can be used, or the configuration data can be adjusted using the site merging rules as described in the steps below before merging the adjusted configuration data. Another approach is to merge the management units in the configuration data one by one, or adjust the management units in the configuration data separately and then merge them one by one.

[0213] The adjustment module 300 is used to adjust the configuration data to be merged according to the merging rules;

[0214] The system queries the configuration data of the sites to be merged and adjusts the configuration data. Based on the merging scenario configured in the merging template, it searches for the corresponding merging rule in the merging rule set. If found, the configuration data of the merging site is adjusted. If not found, the configuration data of the merging site is not merged by default.

[0215] Before merging the configuration data of the merged sites, conflicts between the configuration data need to be handled, such as conflicts between data identifier IDs, conflicts between corresponding wireless service IDs in configuration data with related relationships, and the replanning or adjustment of site equipment, transmission parameters, etc. Therefore, it is necessary to use merging rules to adjust the configuration data to be merged before the merging operation.

[0216] Understandably, before making adjustments, the configuration data of the merged sites is copied twice, one to the configuration editing area and the other to the original area. Adjustments are then made only to the configuration data in the editing area.

[0217] The merge operation module 400 is used to perform merge operations on the adjusted configuration data to be merged.

[0218] The adjusted configuration data to be merged is then merged to successfully combine the configuration data from different sites to the target site. Therefore, adjusting the configuration data of the sites to be merged before the merge operation avoids conflicts during the merge process and prevents data corruption after the merge, thus improving the efficiency of merging configuration data and saving manpower and time costs.

[0219] The above analysis shows that the network element configuration data merging method provided in this specification first loads a pre-configured site merging template. Different site merging sites correspond to different template contents. The template includes the network element model version number of the site. Based on the version number, the corresponding version of the network element model can be found, and the corresponding merging rules can be located. Thus, the merging rules can be obtained based on the template. It can be understood that different site merging sites can correspond to different template contents, different network element models, and different merging rules. After the merging rules are found, the configuration data to be merged can be adjusted according to the rules, and then the adjusted configuration data to be merged is merged. Different merging templates are pre-configured before configuration data merging based on different modification scenarios, configuration data storage locations, and relationships between different site merging sites. Furthermore, different site merging sites can use different merging rules to adjust the configuration data to be merged before merging the configuration data. As can be seen, when merging configuration data, the pre-configured template is loaded directly. Taking into account the actual situation of different merged sites, different merge rules are adopted to speed up the merging of configuration data, which simplifies the complex site merging process and speeds up the merging work efficiency.

[0220] Example 4

[0221] See Figure 12 As shown, an electronic device provided by an embodiment of the present invention includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the following... Figures 1 to 9 The steps of the network element configuration data merging method shown can be specifically performed as follows:

[0222] Step 10: Load the pre-configured station merging template;

[0223] The network element configuration data merging method proposed in the embodiments of this specification takes into account the different transformation scenarios that may occur at the actual site of the merged site, involving site equipment, transmission data, and wireless data. It pre-configures site templates and merging rule sets for the merged sites. The merging template is the same template, but the content reflected in the merging template varies depending on the different situations of the merged sites.

[0224] See Figure 14 As shown, the site merging template includes the network element model version number of the merging site, the merging relationship of the merging sites, the storage location of the configuration data of the merging sites, and the extended information that the protocol needs to be planned.

[0225] The site consolidation template includes information about the consolidation site, including configurations for the corresponding transformation scenario and the network element model version number. This version number allows for the lookup of the corresponding network element model. Since the network element model and consolidation rule set are configured together, finding the network element model for the consolidation site allows access to the corresponding consolidation rule set, which can then be used to adjust the configuration data. Therefore, different configurations can be tailored to different transformation scenarios for the consolidation site. Furthermore, the template also allows for planning the equipment, transmission, and wireless parameters of the consolidation site for future adjustments.

[0226] Users can plan the merging operations of one or more sites under different scenarios in the site merging template. A site merging group can include one migration site and one target site. Merging operations of configuration data for one or more sites with the same target site can be combined into a single merging task. Multiple merging tasks can be executed concurrently. The merging operations of multiple sites within a single merging task can be serial, meaning that only one migration site and one target site are merged at a time, completing the merging operations of multiple sites within a single merging task sequentially.

[0227] At the start of the site merging task, a site merging template is used as input. The template is loaded and parsed to obtain relevant information about the sites to be merged. To improve merging efficiency, the sites performing the merging operation in the task can belong to the same network element model version.

[0228] Step 20: Obtain the merging rules based on the merging template;

[0229] As mentioned above, after obtaining the network element model version number of the merged site based on the merged site template, the corresponding network element model can be found. The network element model and the merged site rule set are configured together. Therefore, after loading the network element model package with the corresponding model version number of the target site, the network element model and merged site rule set corresponding to the merged site can be parsed to obtain the merged site.

[0230] The site merging rule set is pre-configured based on different network element models. As the name suggests, the site merging rule set includes multiple site merging rules. Configuration data can be merged uniformly according to the site merging rules. Alternatively, the same site merging rule can be used, or the configuration data can be adjusted using the site merging rules as described in the steps below before merging the adjusted configuration data. Another approach is to merge the management units in the configuration data one by one, or adjust the management units in the configuration data separately and then merge them one by one.

[0231] Step 30: Adjust the configuration data to be merged according to the merging rules;

[0232] The system queries the configuration data of the sites to be merged and adjusts the configuration data. Based on the merging scenario configured in the merging template, it searches for the corresponding merging rule in the merging rule set. If found, the configuration data of the merging site is adjusted. If not found, the configuration data of the merging site is not merged by default.

[0233] Before merging the configuration data of the merged sites, conflicts between the configuration data need to be handled, such as conflicts between data identifier IDs, conflicts between corresponding wireless service IDs in configuration data with related relationships, and the replanning or adjustment of site equipment, transmission parameters, etc. Therefore, it is necessary to use merging rules to adjust the configuration data to be merged before the merging operation.

[0234] Understandably, before making adjustments, the configuration data of the merged sites is copied twice, one to the configuration editing area and the other to the original area. Adjustments are then made only to the configuration data in the editing area.

[0235] Step 40: Perform a merge operation on the adjusted configuration data to be merged.

[0236] The adjusted configuration data to be merged is then merged to successfully combine the configuration data from different sites to the target site. Therefore, adjusting the configuration data of the sites to be merged before the merge operation avoids conflicts during the merge process and prevents data corruption after the merge, thus improving the efficiency of merging configuration data and saving manpower and time costs.

[0237] Figure 9 This is a schematic diagram of the structure of a server 900 according to an embodiment of this specification. At the hardware level, the server includes a processor 920, and optionally also includes an internal bus 940 and a memory 920.

[0238] The memory 920 is used to store programs. Specifically, the program may include program code, which includes computer operation instructions. The memory may include main memory and non-volatile memory, and provide instructions and data to the processor. The memory 920 may include main memory, such as high-speed random-access memory (RAM), and may also include non-volatile memory, such as at least one disk storage device. Of course, the server may also include other hardware required for other business operations.

[0239] Processor 910 reads the corresponding computer program from non-volatile memory into memory and then runs it. Processor 910 executes the program stored in memory. Processor 910 and memory 920 can be interconnected via internal bus 940, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus 940 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 9 The term "processor" is represented by a single double-headed arrow, but this does not imply a single bus or a single type of bus. A processor may be an integrated circuit chip with signal processing capabilities. In implementation, a processor can function through integrated logic circuits in its hardware or through software instructions. The aforementioned processors can be general-purpose processors, including Central Processing Units (CPUs), Network Processors (NPs), etc.; they can also be Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate Arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor can be a microprocessor or any conventional processor.

[0240] The technical solution and embodiments of this specification provide a method for merging network element configuration data. First, a pre-configured site merging template is loaded. Different site merging sites correspond to different template contents. The template includes the network element model version number of the site. Based on the version number, the corresponding version of the network element model can be found, and the corresponding merging rules can be located. Thus, the merging rules can be obtained based on the template. It is understood that different site merging sites can correspond to different template contents, different network element models, and different merging rules. After the merging rules are found, the configuration data to be merged can be adjusted according to the rules, and then the adjusted configuration data to be merged is merged. Different merging templates are pre-configured before configuration data merging based on different modification scenarios, configuration data storage locations, and relationships between site merging sites. Furthermore, different site merging sites can use different merging rules to adjust the configuration data to be merged before merging the configuration data. As can be seen, when merging configuration data, the pre-configured template is loaded directly. Taking into account the actual situation of different merged sites, different merge rules are adopted to speed up the merging of configuration data, which simplifies the complex site merging process and speeds up the merging work efficiency.

[0241] Example 5

[0242] This invention provides a storage medium for computer-readable storage, wherein the storage medium stores one or more programs, which can be executed by one or more processors to achieve, for example... Figures 1 to 9 The steps of the network element configuration data merging method shown can be specifically performed as follows:

[0243] Step 10: Load the pre-configured station merging template;

[0244] The network element configuration data merging method proposed in the embodiments of this specification takes into account the different transformation scenarios that may occur at the actual site of the merged site, involving site equipment, transmission data, and wireless data. It pre-configures site templates and merging rule sets for the merged sites. The merging template is the same template, but the content reflected in the merging template varies depending on the different situations of the merged sites.

[0245] See Figure 14 As shown, the site merging template includes the network element model version number of the merging site, the merging relationship of the merging sites, the storage location of the configuration data of the merging sites, and the extended information that the protocol needs to be planned.

[0246] The site consolidation template includes information about the consolidation site, including configurations for the corresponding transformation scenario and the network element model version number. This version number allows for the lookup of the corresponding network element model. Since the network element model and consolidation rule set are configured together, finding the network element model for the consolidation site allows access to the corresponding consolidation rule set, which can then be used to adjust the configuration data. Therefore, different configurations can be tailored to different transformation scenarios for the consolidation site. Furthermore, the template also allows for planning the equipment, transmission, and wireless parameters of the consolidation site for future adjustments.

[0247] Users can plan the merging operations of one or more sites under different scenarios in the site merging template. A site merging group can include one migration site and one target site. Merging operations of configuration data for one or more sites with the same target site can be combined into a single merging task. Multiple merging tasks can be executed concurrently. The merging operations of multiple sites within a single merging task can be serial, meaning that only one migration site and one target site are merged at a time, completing the merging operations of multiple sites within a single merging task sequentially.

[0248] At the start of the site merging task, a site merging template is used as input. The template is loaded and parsed to obtain relevant information about the sites to be merged. To improve merging efficiency, the sites performing the merging operation in the task can belong to the same network element model version.

[0249] Step 20: Obtain the merging rules based on the merging template;

[0250] As mentioned above, after obtaining the network element model version number of the merged site based on the merged site template, the corresponding network element model can be found. The network element model and the merged site rule set are configured together. Therefore, after loading the network element model package with the corresponding model version number of the target site, the network element model and merged site rule set corresponding to the merged site can be parsed to obtain the merged site.

[0251] The site merging rule set is pre-configured based on different network element models. As the name suggests, the site merging rule set includes multiple site merging rules. Configuration data can be merged uniformly according to the site merging rules. Alternatively, the same site merging rule can be used, or the configuration data can be adjusted using the site merging rules as described in the steps below before merging the adjusted configuration data. Another approach is to merge the management units in the configuration data one by one, or adjust the management units in the configuration data separately and then merge them one by one.

[0252] Step 30: Adjust the configuration data to be merged according to the merging rules;

[0253] The system queries the configuration data of the sites to be merged and adjusts the configuration data. Based on the merging scenario configured in the merging template, it searches for the corresponding merging rule in the merging rule set. If found, the configuration data of the merging site is adjusted. If not found, the configuration data of the merging site is not merged by default.

[0254] Before merging the configuration data of the merged sites, conflicts between the configuration data need to be handled, such as conflicts between data identifier IDs, conflicts between corresponding wireless service IDs in configuration data with related relationships, and the replanning or adjustment of site equipment, transmission parameters, etc. Therefore, it is necessary to use merging rules to adjust the configuration data to be merged before the merging operation.

[0255] Understandably, before making adjustments, the configuration data of the merged sites is copied twice, one to the configuration editing area and the other to the original area. Adjustments are then made only to the configuration data in the editing area.

[0256] Step 40: Perform a merge operation on the adjusted configuration data to be merged.

[0257] The adjusted configuration data to be merged is then merged to successfully combine the configuration data from different sites to the target site. Therefore, adjusting the configuration data of the sites to be merged before the merge operation avoids conflicts during the merge process and prevents data corruption after the merge, thus improving the efficiency of merging configuration data and saving manpower and time costs.

[0258] The above analysis shows that the network element configuration data merging method provided in this specification first loads a pre-configured site merging template. Different site merging sites correspond to different template contents. The template includes the network element model version number of the site. Based on the version number, the corresponding version of the network element model can be found, and the corresponding merging rules can be located. Thus, the merging rules can be obtained based on the template. It can be understood that different site merging sites can correspond to different template contents, different network element models, and different merging rules. After the merging rules are found, the configuration data to be merged can be adjusted according to the rules, and then the adjusted configuration data to be merged is merged. Different merging templates are pre-configured before configuration data merging based on different modification scenarios, configuration data storage locations, and relationships between different site merging sites. Furthermore, different site merging sites can use different merging rules to adjust the configuration data to be merged before merging the configuration data. As can be seen, when merging configuration data, the pre-configured template is loaded directly. Taking into account the actual situation of different merged sites, different merge rules are adopted to speed up the merging of configuration data, which simplifies the complex site merging process and speeds up the merging work efficiency.

[0259] In summary, the above description is merely a preferred embodiment of this specification and is not intended to limit the scope of protection of this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

[0260] The systems, apparatuses, modules, or units described in one or more of the above embodiments may be implemented by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer. Specifically, a computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0261] Computer-readable storage media include both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0262] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0263] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0264] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

Claims

1.A method for merging configuration data of network elements, the method comprising: loading a pre-configured merge template, the merge template comprising a version number of a network element model of a merge site, the merge site comprising a migration site and a target site; obtaining the version number of the network element model of the merge site according to the merge template; searching for a corresponding network element model and a merge rule set based on the version number of the network element model, wherein the merge rule set comprises a plurality of merge rules; adjusting configuration data to be merged of the merge site according to the merge rules; and merging the adjusted configuration data to be merged. 2.The method of claim 1, wherein the configuration data to be merged comprises site management objects, and the adjusting of the configuration data to be merged according to the merge rules comprises: adjusting the site management objects according to the merge rules, and the merge rules correspond to the site management objects one by one in terms of granularity. 3.The method of claim 2, wherein the adjusting of the site management objects according to the merge rules comprises: adjusting the site management objects in sequence according to an execution order of the site management objects until the adjustment of all the site management objects is completed. 4.The method of claim 3, wherein the site management objects are site management objects of the current merge site, and after the adjustment of all the site management objects is completed, the method further comprises: determining whether there is a next merge site; if yes, adjusting site management objects included in the next merge site according to the merge rules, and returning to the determining step until the adjustment of all the configuration data of the merge sites is completed. 5.The method of claim 3 or 4, wherein before the adjusting of the site management objects in sequence according to the execution order of the site management objects, the method further comprises: obtaining a network element model corresponding to the merge site and a pre-configured merge rule set; and generating the execution order of the site management objects based on the network element model and the merge rule set. 6.The method of claim 5, wherein the obtaining of the merge rules according to the merge template comprises: obtaining, according to the merge template, merge rules corresponding to the site management objects from the merge rule set. 7.The method of claim 5, wherein the generating of the execution order of the site management objects based on the network element model and the merge rule set comprises: generating an association relationship between the site management objects based on the network element model and the merge rule set; and determining the execution order according to a priority of the association relationship. ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ 8.The method of claim 7, wherein the adjusting the configuration data to be merged according to the merging rules is based on generating the association between the site management objects based on the network element model and the merging rule set, and the adjusting the configuration data to be merged according to the merging rules comprises: when the site management object identifier of one of the site management objects is adjusted, adjusting the other site management objects associated with the one of the site management objects according to the association. 9.The method of claim 1, wherein the method further comprises: after the merging operation on the adjusted configuration data to be merged, further adjusting the configuration data after the merging operation in the configured workspace. 10.An apparatus for merging configuration data of network elements, comprising: a template generating module configured to load a pre-configured merging template, the merging template comprising a network element model version number of a merging site, the merging site comprising a migration site and a target site; a merging rule obtaining module configured to obtain the network element model version number of the merging site according to the merging template; a network element model and a merging rule set corresponding to the network element model version number are found based on the network element model version number, wherein the merging rule set comprises a plurality of merging rules; an adjusting module configured to adjust configuration data to be merged of the merging site according to the merging rules; and a merging operation module configured to perform a merging operation on the adjusted configuration data to be merged. 11.The apparatus of claim 10, wherein the configuration data to be merged comprises site management objects, and the adjusting module is specifically configured to: adjust the site management objects according to the merging rules, and the merging rules correspond to the site management objects one by one in terms of granularity. 12.The apparatus of claim 11, wherein the adjusting module is further configured to: sequentially adjust the site management objects according to an execution order of the site management objects until the adjustment of all the site management objects is completed. 13.A network management system comprising the apparatus for merging configuration data of network elements according to any one of claims 10 to 12. 14.An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method for merging configuration data of network elements according to any one of claims 1 to 9 when executing the computer program. 15.A storage medium for computer-readable storage, wherein the storage medium stores one or more programs, and the one or more programs are executable by one or more processors to implement the steps of the method for merging configuration data of network elements according to any one of claims 1 to 9. ​ ​ ​ ​ ​ ​ ​ ​ ​

Images